1. Planning for Enterprise Systems

2. Objectives describe enterprise systems planning
discuss Accelerated SAP approach

3. What is implementation?
Opportunity:
Integrate disparate systems
Provide real time information
Adopt proven systems
Enforce standards
Reengineer business processes
Restructure organization
Working solution:
Use of enterprise systems for managing information flows

4. Critical Success Factors
commitment from top management
empowered teams with ability to make decisions
strong project management leadership
adaptable organization
defined business direction
best people = best results

5. Systems Development Life Cycle (SDLC)
1. Feasibility
6. Operations
2. Analysis
5. Implementation
3. Design
4. Coding

6. Enterprise System Implementation Phases
1. Initiation
6. Operations
2. Planning
1.      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. Transition
Analysis &
process design
4. Realization

7. Project 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 success
project measures (how organization knows when project is completed and/or making progress)

8. Scoping the implementation: four types of projects
Initial implementations
no prior enterprise system
Subsequent rollouts in other areas
different business units or geographic locations
Upgrades to existing system
Enhancements
new functional areas or modules added to core system

9. Blueprinting mission objectives processes MAPPING enterprise system
resources

10. Data-driven approach processes MAPPING enterprise system resources
forms &
reports
MAPPING
data
elements
enterprise
system
resources

11. Big bang Implementing all targeted functionality at same time
Advantages:
Integrated configuration and testing
Better opportunity for changing organizational structure
Disadvantages:
Extreme change
Complex project management

12. Phased Implementing targeted functionality in phases Advantages:
By module, geography, or business unit
Advantages:
Less disruptive to business
Projects are easier to manage
Disadvantages
User buy-in wanes
More testing and integration issues

14. ASAP Implementation Continuous Change Project Preparation Final
Go Live &
Business
Realization
Support
Blueprint
ASAP Implementation
Phase 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.

15. Accelerated SAP (ASAP)
An approach resulting in a quick, cost effective implementation of R/3
Minimizes the length of time between installation and production start up
Maximizes the utilization of SAP and customer resources
Incorporates a process oriented approach to training
Involves the user community
Results in a repeatable “model” that can be used with other implementations of R/3

16. implementation deliverables1 2 3 4 5
Business Process
Master
List
Enhancements .
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 Template
The 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 Document
This 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 List
The 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 Document
The Baseline scope document defines the business processes and requirements that will be configured and played back during the Baseline confirmation session.
Authorizations
Project
System
Reports
Performance
Plan
Interfaces
Processes
Scope
Baseline
Procedures
Reports
Test Plan
Org .
structure
Scope
Test
Cases
Interfaces
Train .
Mat .
Conversion Go
Live
Plan
Business
Blueprint

17. Phase 1: Project Preparation
Explain roles and procedures
Prepare the Project Charter
Define schedule, budget, and resources
Provide initial training for project team
Define technical requirements
Prepare 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.

18. Phase 2: Business Blueprint
Assess customer requirements through the interviews, questionnaires, and models of the Business Blueprint
Provide training for project team
Install development system
Review the Business Blueprint
The 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.

19. Phase 3: Realization Customizing Final Integration Test 3
Customize the "Baseline" system, which covers 100 % of the organizational structure and 60% of all daily business operations
Check that this Customizing realizes your business processes (first integration test)
Final Integration Test
Check other business processes which may be indirectly affected
Design, develop, and test interfaces, reports, and data conversions
o      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

20. Phase 4: Final Preparation
Planning for the going live data
Training end users
Testing: integration, volume, and stress
Establishing an internal Help Desk
Cutover to production environment
o      Final preparation involves planning the following:
–   Testing
–   End-user training
–   System management
–   Cutover tasks
o      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.

21. Phase 5: Go Live and Support
Start of production operation
Setting up support
Verifying the accuracy of the production system
Measuring business benefits
Optimizing performance
o      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.

22. Example of Project Duration
PHASE
Pct 1
Project Preparation
12% 2
Business Blueprint
15% 3
Realization
46%
Baseline
12%
Final Configuration
13%
Integration Test
21% 4
Final Preparation
19% 5
Go Live & Support 8%
Total
100%

23. Summary described enterprise systems planning
discussed Accelerated SAP approach