Integrated Business Planning Implementation
Implementation of Blueshift's ONE Solution is more than a software installation. It is a tailored, process driven Integrated Business Planning transformation project.
IBP Transformation Scope
The IBP transformation scope of an implementation includes:
- Current state process blueprinting and gap analysis to Blueshift best-practice IBP;
- Tailored future state IBP process blueprinting;
- Full project duration IBP consultation tailored to the client’s specific customer accounts and challenges;
- Change management;
- Process and system coaching and training.
See also: Integrated Business Planning
Delivery of the ONE System has the following project scope:
- System blueprinting to align the business on the configuration of the solution in line with the agreed process blueprint;
- System stand-up and configuration in line with the System Blueprint including settings, field naming, views and interface options;
- Data initialisation including transactional and promotional history, and data validation and reconciliation;
- Interface development, testing and deployment.
See also: Technical Information
Named User Licencing
User licencing is based on the total number of named users.
Single Module Only
There are no separate modules; IBP is only possible with a single end to end solution.
An Integrated Business Planning transformation project involving Blueshift's ONE Solution typically takes 6-9 months to implement.
The project phases are outlined below. Depending on business, account and system complexity and maturity an IBP implementation may be achievable in a faster timeframe or may take longer.
1. Blueprint & Prototype
The Blueprint & Prototype phase is where the process deep dive occurs. It includes detailed as-is investigation, gap analysis, and capturing of the tailored, best-practice IBP future state.
The Blueprint & Prototype phase usually takes approximately 10 – 12 weeks to complete. The build phase is usually begun in parallel using best practice assumptions.
The Blueprint & Prototype phase is complete when the business signs off on the future state IBP Blueprint, prototype and the UAT scenarios.
The build phase usually takes approximately 20 weeks and involves system blueprinting, system stand-up, configuration, data initialisation, interface development and testing and data validation.
The Rapid Application Development model is used in this phase giving the business both continuous visibility of the installation and the flexibility to change as the layers unfold.
The Build phase is complete when the business signs off data validation and that the system passes the agreed UAT scenarios.
The Migration phase includes the production instance stand-up, user training, final forecast and promotional build, go-live, and heightened project team support for the new IBP process.
The phase usually takes approximately 10 weeks and can overlap with the build phase – for example the forecast and promotion build and user training can occur before build sign-off.
The Migrate phase is complete when there is 100% adherence to the agreed IBP Blueprint.
Solution Project Team
The selection of members for the Solution Project Team is a critical success factor. Successful, on-time, on-budget, process-fitted solutions are always delivered by dedicated experts with in depth domain knowledge.
Below is an outline of a typical project team. Solution teams are always collaboratively tailored to each client’s specific requirements.
Overall Project Management.
As an IBP industry subject matter expert, understand current state and lead the change for best practice to-be IBP process. To document the agreed future state process and throughout the entire project bring the business on the journey with the system to enable IBP.
To oversee the process and system marriage, to design and oversee development of interfaces and change requests, to oversee project delivery from a system perspective, to act as the key point of contact inside Blueshift for the project phase.
To engage the Business Project Team and thoroughly document the business processes and functional interface requirements. To deep dive ERP interface requirements from a technical perspective and facilitate functional interface design. To aid with interface development and debugging from an ERP perspective throughout the project.
To provide development of all inbound and outbound interfaces from a Blueshift perspective.
Technical design and development of inbound and outbound ERP interfaces. Note: it may be required to have an ERP Solution Architect as well if the developer is not up skilled enough.
Thorough system testing during SIT phase to ensure adherence to business processes detailed in the Blueprint phase. To ensure system stability and adherence to performance criteria. To aid with user training, and to manage and document the UAT project phase.
To provide in-person hands-on system training for end users.
Critical Success Factors
Successful IBP implementations share common characteristics.
Senior management ownership, buy-in, and impetus for change.
Business wide understanding of (and buy-in to) the IBP process and tools.
A culture that is open to change.
A strong and experienced project team.
Focused attention on data quality and validation.
Company wide trust in the Consensus Business Plan, the one-number forecast.