Project preparation : is the first and initial phase of the ASAP roadmap where you are just starting the project. You will perform activities such as preparation of the initial scope, high-level timelines and plans, project charters, identification of project team members, project kick-off, etc.
Business blueprint : is the second phase in the implementation where you will try, identify, and document business requirements and goals to prepare the foundation for future stages of the project. Ideally, you will organize ‘business requirement gathering’ workshops with the various business/functional users of the company, lead them through the discussion with structured business functionality questionnaires, understand their existing business processes, and identify and document their requirements in the wake of this new implementation. A ‘sign-off’ at the end of the phase ensures an agreement to move forward outlining the scope of the project. It is understood that whatever is explicitly stated in the business blueprint document is the only scope; no implied scope will be considered for system configuration in the next phase.
Realization : is the third phase where the implementing team breaks down the business processes identified in the second phase and configures the SAP settings. Initially, you will do a Baseline Configuration, test the system functionality and if necessary make changes to the baseline configuration, and close the phase with Final Configuration, signalling that all the business processes have been captured and configured in the system.
Final Preparation : is the penultimate phase in the project. This phase also serves to resolve all crucial open issues. A ‘go-live check’ is also conducted to analyze whether the system has been properly configured. This phase is marked by the following activities:
End-to-testing of the configured system (User Acceptance Test—UAT)
Training of the end users (Usually follows the concept ‘Train-the-Trainer’)
System management activities (creation of users, user profiles, allocation of roles to profiles, etc.)
Cut-over (data migration activities)
An ‘internal help desk’ should be staffed and supported mainly by employees of the enterprise. Setting up a help desk involves, among other things, installing office and technical equipment and defining OSS users. Problems that cannot be solved by this internal help desk are forwarded to SAP via the SAPNet/OSS system. On successful completion of this phase, you are ready to run your business in your production system.
Go-Live and Support : is the final and fifth phase of the project where the configured system is declared ‘live’ for day-to-day business use. Users make productive (live) business transactions in the system and all the issues cropping up in the wake of going live are supported and resolved by a support team immediately.
0 Komentar
Penulisan markup di komentar