Continuing our discussion from the part 1 of this series, where we discussed the general introduction to SAP BPC, let's get into the BPC implementationi methodology I have been involved with.
Point # 2: Implementation methodology:
Generally SAP recommends ‘ASAP' methodology for its implementation partners & customers. For more details about ASAP methodologies please visit here.
http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm
Keeping this in mind, let's understand what can be the best for SAP BPC implementation scenarios. Broadly thinking, We can have 2 situations,
- a. Implementing SAP BPC as standalone software.
- b. Implementing SAP BPC in an SAP environment (ECC, BI, CRM) -
- a. As a fresh implementation for all the components
- b. Only BPC implementations.
For the case of Point # a & #b.b. I recommend the following.
https://weblogs.sdn.sap.com/weblogs/images/251767692/Arpan1.GIF" width="628" height="96" border="0" alt="image" />
‘Preparation',' Design & Plan' are analogues to the ‘Project Preparation' & ‘Business Blueprint' in the classical ASAP phases. During the ‘Preparation' phase do cover the technical prerequisites & the Client team training. The next 3 phases ‘Configure', ‘Development' & ‘Tune' are encompasses the ‘Realization' phase in ASAP. ‘Training' is not there as a separate phase in ASAP whereas ‘Deployment' phase is analogues to the ‘Final Preparation' & ‘Go Live & Support' phases in ASAP.
All the SAP project managers will be well aware of the first 2 phases and it does holds good here. Only extra 2 cents from my side is to make sure to allow enough time to be spent on the design phase before beginning to build. Changing a Config in BPC later is quite a challenge. Now, let us discuss the next 3 phases in details. The whole ASAP - Realization phase has been broken down into ‘Configure', ‘Development' & ‘Tune'. Please see below BPC launch page, where I have grouped Development and configuration work area.
https://weblogs.sdn.sap.com/weblogs/images/251767692/Arpan2.GIF" width="355" height="285" border="0" alt="image" />
Basically, during the initial few days you would like to setup your AppSet, Application(s), Dimensions, Work status, BPF, Security etc which encompasses your environment. After you nailed down the initial setup and achieved at least 80% of your configuration setup, you want to open up your system for report creation, portal configuration, develop input templates, BPF setup, data loads integration etc. The 2nd phase or ‘Development' supposed to encompass all of those.
In the 3rd phase of the project, before you get into the user testing & related, make sure you switch on your audit, full blown security etc and then compare your system performance and optimize. Without the 'Audit' switched on, the performance testing has no value according to me. ‘Tuning' is a very important phase BPC project need to follow seriously considering the way the tool is built.
Training has occupied the next phase as; BPC is ‘Zero foot print' software. A well planned training phase usually takes less time compare to other SAP tool. And the Cost/Benefit ratio for a BPC ‘Training' phase is very low. This does make it all the more sensible thing to consider it as a separate phase.
Deployment phase is analogues to the ‘Final Preparation', ‘Go-live & Support' in ASAP methodology.
Now for the other scenario, above #b.a, following ASAP methodology as a top tier planning and considering the above point at the internal BPC rollout team level makes the project well managed.
ps. All the above information is what I am confortable with. By no means, this will work for every situation or projects or everybody will agree to this. I strongly recommend please align these with your project need.
