2Objectives describe enterprise systems planning discuss Accelerated SAP approach
3What is implementation? Opportunity:Integrate disparate systemsProvide real time informationAdopt proven systemsEnforce standardsReengineer business processesRestructure organizationWorking solution:Use of enterprise systems for managing information flows
4Critical Success Factors commitment from top managementempowered teams with ability to make decisionsstrong project management leadershipadaptable organizationdefined business directionbest people = best results
5Systems Development Life Cycle (SDLC) 1. Feasibility6. Operations2. Analysis5. Implementation3. Design4. Coding
6Enterprise System Implementation Phases 1. Initiation6. Operations2. Planning1. Initiation—This is the phase in which the business case for the implementation is made, as well as major decisions about the project scope and implementation strategy. Also, this phase usually includes the selection of methodology, software and hardware vendors, and consulting partners.2. Planning—The planning phase is focused on setting up the project administration, determining the staffing arrangements, setting goals and objectives, acquiring resources, and establishing metrics for the implementation project.3. Analysis and process design—This phase involves analyzing the organization and its current processes, redesigning those processes as needed, and creating a mapping from the organization “as is” to the organization “to be.”4. Realization—The realization phase entails installing a base system, customizing it to the organization, extending it if necessary, and testing the implementation.5. Transition—This is usually a relatively short phase during which the organization’s former information systems are replaced with the enterprise system.6. Operation—The operation phase involves ongoing efforts to monitor system performance and tune the system as appropriate. It also involves the continuing process of training employees on the enterprise system.5. TransitionAnalysis &process design4. Realization
7Project Charter mission of project (main goals) project objectives (measurable desired outcomes)business drivers (environmental forces driving project)issues, barriers, or restraining forces that may inhibit the project’s successproject measures (how organization knows when project is completed and/or making progress)
8Scoping the implementation: four types of projects Initial implementationsno prior enterprise systemSubsequent rollouts in other areasdifferent business units or geographic locationsUpgrades to existing systemEnhancementsnew functional areas or modules added to core system
9Blueprinting mission objectives processes MAPPING enterprise system resources
10Data-driven approach processes MAPPING enterprise system resources forms &reportsMAPPINGdataelementsenterprisesystemresources
11Big bang Implementing all targeted functionality at same time Advantages:Integrated configuration and testingBetter opportunity for changing organizational structureDisadvantages:Extreme changeComplex project management
12Phased Implementing targeted functionality in phases Advantages: By module, geography, or business unitAdvantages:Less disruptive to businessProjects are easier to manageDisadvantagesUser buy-in wanesMore testing and integration issues
14ASAP Implementation Continuous Change Project Preparation Final Go Live &BusinessRealizationSupportBlueprintASAP ImplementationPhase 1: Project Preparation - Provides initial planning and preparation for your R/3 project.Phase 2: Business Blueprint - In this phase, you create the Business Blueprint, which is detailed documentation of the results gathered during requirements workshops. Furthermore, the Business Blueprint serves to document the business process requirements of the company. On this basis, you will achieve a common understanding of how the company intends to run their business within the R/3 System.Phase 3: Realization - In this phase, you implement all the business and process requirements based on the Business Blueprint. You configure the system step by step in two work packages, Baseline and Final configuration.Phase 4: Final Preparation - In this phase, you complete testing, end user training, system management and cutover activities to finalize your readiness to go live. Furthermore, the Final Preparation phase serves to resolve all critical open issues. Upon successful completion of this phase, you will be ready to run your business in your live R/3 System.Phase 5 Go Live and Support - Transition from a project-oriented, pre-production environment to successful and live production operation.
15Accelerated SAP (ASAP) An approach resulting in a quick, cost effective implementation of R/3Minimizes the length of time between installation and production start upMaximizes the utilization of SAP and customer resourcesIncorporates a process oriented approach to trainingInvolves the user communityResults in a repeatable “model” that can be used with other implementations of R/3
16implementation deliverables 12345Business ProcessMasterListEnhancements.During the five phases of an ASAP project, different types of documents are created to record the deliverables from each phase. This is particularly relevant in Phase 2. The following documents are important: Customer Input TemplateThe customer input template from the Q & A database is used to collect company requirements during the business scenario requirements gathering sessions in the Business Blueprint phase. Business Blueprint DocumentThis is the main deliverable of the Business Blueprint phase. The Business Blueprint document provides written documentation of the results of the requirements gathering sessions. The purpose of this documents is to verify that a proper understanding of requirements has been communicated. The Business Blueprint also finalizes the detailed scope of the project. Business Process Master ListThe Business Process Master List is an R/3 representation of the project scope that is refined during the Realization phase into the project's applicable business scenarios and R/3 transactions. Baseline Scope DocumentThe Baseline scope document defines the business processes and requirements that will be configured and played back during the Baseline confirmation session.AuthorizationsProjectSystemReportsPerformancePlanInterfacesProcessesScopeBaselineProceduresReportsTest PlanOrg.structureScopeTestCasesInterfacesTrain.Mat.ConversionGoLivePlanBusinessBlueprint
17Phase 1: Project Preparation Explain roles and proceduresPrepare the Project CharterDefine schedule, budget, and resourcesProvide initial training for project teamDefine technical requirementsPrepare executive kickoff meeting– Explain ASAP roles and procedures ASAP defines roles and procedures which should be observed.– Prepare the Project Charter The Project Charter clarifies your business-related project goals.– Define your schedule, budget, and resources Use the corresponding ASAP tools.– Provide initial training for project team This training corresponds to the Level 1 training in the SAP training curriculum.– Define technical requirements Evaluate your hardware sizing requirements and create an appropriate hardware supply contract.– Prepare executive kickoff meeting The task of this meeting should be to stimulate motivation, and outline procedures and responsibilities.
18Phase 2: Business Blueprint Assess customer requirements through the interviews, questionnaires, and models of the Business BlueprintProvide training for project teamInstall development systemReview the Business BlueprintThe Business Blueprint document is a detailed assessment of the customer's business process requirements based on interviews, questionnaires, and workshops, and helps create a single picture from all the different company perspectives.
19Phase 3: Realization Customizing Final Integration Test 3 Customize the "Baseline" system, which covers 100 % of the organizational structure and 60% of all daily business operationsCheck that this Customizing realizes your business processes (first integration test)Final Integration TestCheck other business processes which may be indirectly affectedDesign, develop, and test interfaces, reports, and data conversionso The Realization phase sets up the business processes you require, by performing Customizing according to your Business Blueprint.o Configure the system in two parts:– Baseline (majority of functional scope, as defined in ASAP's Question and Answer Database)– Final (remaining functional scope, usually of a more complex nature)This lets you confirm the essential functions before moving on to other areas.o The implementation objectives of this phase are:– Complete R/3 implementation– Testing– R/3 System operability– The project team gaining detailed knowledge of their R/3 System
20Phase 4: Final Preparation Planning for the going live dataTraining end usersTesting: integration, volume, and stressEstablishing an internal Help DeskCutover to production environmento Final preparation involves planning the following:– Testing– End-user training– System management– Cutover taskso Final preparation is also the phase in which important open issues are resolved.o On successful completion of this phase, you are ready to run your company's business with R/3.
21Phase 5: Go Live and Support Start of production operationSetting up supportVerifying the accuracy of the production systemMeasuring business benefitsOptimizing performanceo In phase 5, you move from a preproduction environment to a live production operation.o Set up a support organization for users, not just for the first days of production but also long term. During this phase, users of R/3 have many questions. Therefore, there should be a solid user support organization that is easily accessible to all users.o This is also the phase in which to monitor system transactions and to optimize overall system performance.At the completion of this phase, the implementation project is closed.
22Example of Project Duration PHASEPct1Project Preparation12%2Business Blueprint15%3Realization46%Baseline12%Final Configuration13%Integration Test21%4Final Preparation19%5Go Live & Support8%Total100%
23Summary described enterprise systems planning discussed Accelerated SAP approach