Asap img

1,963 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,963
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
47
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Asap img

  1. 1. Implementation Roadmap Content: Phase 1 - Project Preparation Phase 2 - Business Blueprint Phase 3 - Realization Phase 4 - Final Preparation Phase 5 - Go Live & Support  SAP AG 2001© SAP AG TSCM52 24-2
  2. 2. Implementation Roadmap: Unit Objectives Upon completion of this unit, you will be able to: Outline the purpose and content of the work packages in each phase of the ASAP Roadmap Identify the main roles and responsibilities of each phase of the ASAP Roadmap Explain and demonstrate the major tools & accelerators supporting each phase of the ASAP Roadmap  SAP AG 2001© SAP AG TSCM52 24-3
  3. 3. Overview Diagram: Implementation Roadmap (1) Implementation Phase 1 Roadmap Project Preparation Phase 2 Business Blueprint Phase 3 Realization Phase 4 Final Preparation Legend: Phase 5 Unit Unit Go Live & Support Topic Topic  SAP AG 1999© SAP AG TSCM52 24-4
  4. 4. Phase 1: Project Preparation: Objectives On completion of this topic, you will be able to: Explain the activities and tasks that are important in the Project Preparation phase of your implementation project Highlight the tasks essential from the project team perspective Identify the importance of the Sample Scope Document for Phase 2: Business Blueprint  SAP AG 2001© SAP AG TSCM52 24-5
  5. 5. The Purpose of Phase 1: Project Preparation ASAP Roadmap Project Preparation Final Preparation Go Live & Business Realization Blueprint Support  SAP AG 2001 The purpose of this phase is to provide initial planning and preparation for your SAP project. Although each SAP implementation project has its own unique objectives, scope and priorities, the steps in Phase 1 help identify and plan the primary focus areas to be considered. As you prepare for your SAP implementation, there are important issues you must address at the beginning of the project, including: Defining your project goals and objectives Clarifying the scope of your implementation Defining your implementation strategy Defining the overall project schedule and implementation sequence Establishing the project organization and committees Assigning resources. By addressing these issues early in your implementation, you help ensure that the project proceeds efficiently, and that you have established a solid foundation for a successful SAP implementation.© SAP AG TSCM52 24-6
  6. 6. Project Preparation - Roles & Key Focus Phase Content Initial Proj Project Training Project Tech. Req. Req. Role QC Planning Procedures Plans Kickoff Planning Groupings Steering Sign-Off ****************** Proj. Charter Sponsors and Change Mgmt Kickoff Sign-Off Implementation Plan Meeting Strategy Quality Check/ Proj. Mgmt. Proj. ****************** Proj. Mgmt. Kickoff Sign-Off Standards & Meeting Procedures ****************** Consultant Plan / Budget/ Comm./ Doc., Kickoff Resources Issue Mgmt Meeting Proj. Team Customer Standards ****************** ID Tech Technical Implementation Deployment Project Team Requirements/ Strategy Strategy Standards Procure HrdWr Project Team Training Training Plan Organization / Change Mgmt. Project Team Change Kickoff Plan Plan Org. Change Meeting Management Training Security System Authoriz. Standards  SAP AG 2001 There are ten primary roles in an SAP implementation; details of each are in the Implementation Assistant. Steering Committee - members include Project Sponsors, the SAP Consulting Manager (and/or the TeamSAP Coach), and project managers. The committee is also the primary source for the company’s long-term goals and vision, sets priorities, approves scope, and resolves company-wide issues. Project Sponsors - Directly communicates the companys long-term goals and visions and are members of the steering committee. Project Management - TeamSAP Project Manager and Customer Project Manager Consultant - TeamSAP Members, application, cross application, business process Technical - Customer or consultants for System Administration and Technical, Help Desk Provider Training - Training & Documentation, Project Manager/Lead, Training and Documentation Developer/Instructor, Training Coordinator, Training Technology Administrator Change -These are dedicated individuals assigned to manage the Organizational Change Management processes: Risk Assessment, Communication, Sponsorship and Leadership, Skills Development, Knowledge Transfer, or Business Optimization. Security - Authorization, Administration, or Internal Auditor responsible for managing the system security and authorization environment and may be combined with other (technical) administrative roles. Shared items are marked by the ************ brackets.© SAP AG TSCM52 24-7
  7. 7. Documents of an ASAP Project 1 2 3 4 5 Project Charter Q&Adb Master Lists Cutover System Substructures: Microsoft Excel Plan Performance Project Spreadsheets for Business Strategy Development, Organization, Volume Review Plan Organization Test Business Processes and General Settings Authorizations Master Data Stress Scope Business Process Test Cross Application Technical Project Development BPP Progr. Operations Team Develp. Config. Manual Org. Plan EU Testing Training Stand. & Business Material Plan Proced. Blueprint Conduct Microsoft Word Unit testing Documents Test scenario End User Integration Training  SAP AG 2001Phase 1 - Project Preparation Change Charter - Goals and objectives of Organizational Change Management Project Plan - This is a first cut focusing on milestones and Work Packages; details to come. Scope - Sets the initial definition of the project; input from sales cycle. Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and how of the project.Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities Cutover Plan - The details of how to move to the production environment and go live Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going livePhase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.© SAP AG TSCM52 24-8
  8. 8. Phase 1: Project Preparation - Work Packages (1) Initial Project Project Planning Procedures Project Kickoff QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The purpose of this work package is to allow you to start detailed planning for the project. There are many basic issues to resolve at this early stage to ensure the projects success. You should start planning as early as possible in Phase 1, and make key decisions now.© SAP AG TSCM52 24-9
  9. 9. Create and Issue Project Charter Project Preparation Tasks Load Documents into Roadmap Check Documents from Discovery and Evaluation Organize Workshop for Detailing Program Charter Define Project Mission Statement Create Initial Project Plans Identify Project Objectives and Measurements Develop the Change Strategy and Charter Assemble and Approve Project Charter Accelerators: Project Charter White Paper Project Plan Budget / Resource Plan (Sample)  SAP AG 2001 The purpose of this activity is to define key elements that give overall strategic direction to the project team for the SAP System implementation. These tasks provide a solid foundation for the project, and as such, their results should be communicated to all project team members. The input for this activity should be the documents created during the Discovery & Evaluation phase. Load Documents into Roadmap, Check Documents from Discovery and Evaluation, and Organize Workshop for Detailing Program Charter serve as synchronization and interfacing tasks between the Customer Solution Strategy (CSS) of Discovery & Evaluation and the Implementation Roadmap.© SAP AG TSCM52 24-10
  10. 10. Review and Refine Implementation Strategy Project Preparation Tasks Inputs Review and Confirm Implementation Plan Implementation proposals SAP Project Check Strategy for Corporate Rollout Project charter Data gathered from the sales cycle Global Implementation Strategy Output SAP Implementation Strategy Accelerators: Verify the use of Preconfigured Systems (PCS) as Implementation Accelerator Sample Scope Document  SAP AG 2001 The purpose of this activity is to review in detail the implementation strategy for the Project. One must determine if any changes are needed in terms of Project objectives or methodology. The overall implementation approach and methodology should now be finalized and confirmed. For some Projects, it is necessary to also review the overall corporate SAP implementation strategy, especially if there are multiple, simultaneuous SAP implementation Projects in process throughout the company. For local rollout projects as part of a global program, the objective of this activity is to understand and review the global SAP product implementation strategy.© SAP AG TSCM52 24-11
  11. 11. Review and Confirm Implementation Plan Project Preparation With specific focus on: Company Business Objectives Key Implementation Assumptions Overall Scope - Use accelerator “Sample Scope Document” Sample Scope Document Define Business Process Scope at: KEY Level 1 • Level 1 - SAP Reference Structure Level 2 Level 3 Level 4 • Level 2 - Enterprise Area • Level 3 - Scenario Structure In Scope BP Owner / Consult KPI mySAP.com • Level 4 - Process Group Master Data Business Process Procurement Production Sales and Distribution  SAP AG 2001 The purpose of this task is to review the implementation proposal(s), with specific focus on company business objectives, overall scope, and key implementation assumptions. The sample scope document is used as a basis for outlining the scope of the Project (accelerator Sample Scope Document). This document may have already been created as a result of pre-sales activities.© SAP AG TSCM52 24-12
  12. 12. Determine Project Organization Project Preparation Tasks Plan and Set up Environment Define Project Organization and Create Teams Assign People to Core Change Team Roles Conduct Project Team Transition Meeting Create the Extended Change Team Accelerators: Project Room Requirements White Paper IT Infrastructure Document  SAP AG 2001 The purpose of this activity is to create the project organization structure and finalize roles and responsibilities. Both company employees and consultants will need assignment. An important aspect of this activity is the set up of a common working area for the project team. It is crucial for team members to work in an open environment where they are in direct contact, so that they can discuss the various integration issues and resolve them quickly. This common work area is generally referred to as a project team room.© SAP AG TSCM52 24-13
  13. 13. Phase 1: Project Preparation - Work Packages (2) Initial Project Project Procedures Project Kickoff Planning QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The purpose of this work package is to establish the principal elements that determine how the SAP implementation project is to be accomplished. These activities set the groundwork for project kickoff, and provide a baseline of information to be referenced throughout the implementation. For all project team members to operate in an effective manner, it is necessary that project standards and procedures are established at the beginning of the project, and then communicated to all team members. In case of a local rollout project, reference should be made to the global implementation program. By setting the standards, you: Avoid redundant and unnecessary work Maintain consistency Facilitate communication© SAP AG TSCM52 24-14
  14. 14. Define Project Management Standards and Procedures Project Preparation Avoid redundancy and unnecessary work Maintain consistency Facilitate communication Facilitate knowledge transfer to the customer Ensure the entire team understands what is required of them Tasks build upon one another through the phases Define Project Documentation Create Issue Management Plan  SAP AG 2001 The purpose of this activity is to establish the basic standards and procedures for the project. Some will apply throughout each phase of the project, while others will only apply at certain times and/or specific phases. It is important to address these issues during Phase 1 and to establish clear guidelines. Some of the key issues that ASAP recommends be defined are: •Steering committee meeting schedule •How change management is handled •Project monitoring and status reporting •Meeting schedules for core team and extended project team •Overall project communication methods and processes •Project documentation In case of local rollout projects as part of a global program, two additional key issues to be defined are: •Interaction points between local and global teams •Feedback process from local rollout team to global team© SAP AG TSCM52 24-15
  15. 15. Define Strategy for Using SAP Services Project Preparation Post Sales Implementation Go Live ASAP Roadmap Quality Checks Project Final Preparation Business Preparation Go Live & Realization Support Blueprint SAP Review Program 1 2 3 4 5 GoLive Check EarlyWatch Solution Review  SAP AG 2001 The purpose of this task is to define the strategy for using the SAP Services during the implementation phases, as well as for Continuous Business Improvement during production operation of the SAP System. SAP provides services for certain tasks from the ASAP Roadmap. SAP Services can speed up these tasks and help to reach a higher level of quality in the implementation project, as well as in production operation. These services, which are closely linked with the project phases, are tailored to meet your individual needs.© SAP AG TSCM52 24-16
  16. 16. Define Implementation Standards and Procedures Project Preparation Define System Configuration Standards Define Testing Strategies Define Post-Implementation Service and Support Strategy Define System Authorization Standards for Project Team Define Change Request Management Define System Enhancement and Modification Approval Process Define ABAP Development Standards Define Support Package Strategy Define Upgrade Strategy  SAP AG 2001 The purpose of this activity is to establish the overall implementation standards and procedures for the project. Some of these elements should be established by the technical members of the project team, and others by the business or functional members. All team members should have input in this process, and should understand the basic procedures once these have been defined. As with project management standards and procedures, it is important to address the implementation standards during Phase 1 and to establish clear guidelines. Some of the key issues to be defined are: •Overall configuration standards for the project •Initial system authorization standards •How system enhancements are handled •How and when testing occurs© SAP AG TSCM52 24-17
  17. 17. Define System Landscape Strategy Project Preparation Quality Development System Assurance Production System System Data conversions Transport Copy ation SAP Client 000 DEV QAS PRD Three database infrastructure with Development, Quality Assurance DEV Development/Customizing System and Production Systems Complete testing of development QAS Quality Assurance System and upgrades possible PRD Production System Suitable development environment  SAP AG 2001 A three-system infrastructure is the ideal solution for most customers: It affords you unlimited testing of your development. You can implement system upgrades without disturbing your live system. With a separate quality assurance system, you can integrate developments and run consistency checks on objects for a transport before they are introduced to the production system. This three-system solution supports the R/3 System Landscape (System and Client Deployment Strategy) which has the following aims: Development, quality assurance and production should take place in separate environments. In the event of data loss, you should be able to restore a client with consistent data. Transport systems for setting up and maintaining the system infrasturcture are predefined. The infrastructure supports the import of business data from an existing system.© SAP AG TSCM52 24-18
  18. 18. Phase 1: Project Preparation - Work Packages (3) Initial Project Project Planning Procedures Project Kickoff QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The purpose of this work package is to create a project team training plan including business processes, SAP system functionality, and change management. During this phase, level one or awareness training should be conducted for the project team. This phase also includes defining an end user training and documentation strategy. This strategy needs to be developed by reference to, and to support, the overall implementation strategy and project plan.© SAP AG TSCM52 24-19
  19. 19. Create Project Team Training Plan Project Preparation ASAP Roadmap Project Final Preparation Go Live & Preparation Business Realization Support Blueprint SAP Training Courses: ● comprise level 1 (awareness), level 2 (readiness) & level 3 (proficiency) Accelerator: ● should ideally have been completed for levels 1 & 2 before starting the Business Process Workshops ■ Training Services for the Project Team ● address function and use of the SAP product Note! ● Management and project team may have training needs in addition to SAP product. These should also be addressed in the training plan  SAP AG 2001 The purpose of this activity is to create a training plan for the project team involved in the SAP implementation. While training costs can be viewed as relatively expensive, it is critically important that the project team be given this training. Once initial training is completed, the project team has a much better understanding of basic SAP functions, how configuration works, and how to maximize SAP’s impact to meet your business requirements. This initial training does not cover user training – it will be addressed later in the implementation. Key factors during this activity include: Background of each team member Specific area of business involvement of team member (application or technical) Timing of team member participation during the implementation. This key factor information can be used to determine the appropriate classes for each team member, thereby avoiding redundancy, or time spent in classes that are not applicable, and to make sure the course material is timed accordingly. When developing this plan, decide which courses are to be conducted at an SAP training center, or at the company site. The project team training plan is regularly updated throughout the life of the implementation.© SAP AG TSCM52 24-20
  20. 20. End User Training and Documentation Strategy Project Preparation Tasks Develop End User Needs Assessment Develop End User Training and Documentation Project Plan Develop End User Proposal and Conduct Project Proposal Meeting Accelerators: End User Training and Documentation Needs Assessment End User Training and Documentation Methodology  SAP AG 2001 The purpose of this activity is to develop an end user training and documentation strategy and to develop a work plan. You will begin with an assessment of the needs of the end users, develop a project work plan, and then create a project plan that will be the basis of your end user training and documentation implementation.© SAP AG TSCM52 24-21
  21. 21. Phase 1: Project Preparation - Work Packages (4) Initial Project Project Planning Procedures Project Kickoff QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The objective of this work package is to identify the technical requirements needed to implement the SAP technical environment, clarify the customer’s expectations, review hardware sizing, and procure the required hardware. During the planning, keep in mind that all required SAP systems are unlikely to be procured and installed at the same time. The development system is the initial system and is needed at the start of an SAP implementation project. Early on, this may be the only SAP system in the system landscape. Other required SAP systems, such as the quality assurance and production systems, are not needed until a later phase; therefore, part of the planning includes taking expected delivery lead-times into consideration so that subsequent systems and hardware can be ordered in time.© SAP AG TSCM52 24-22
  22. 22. Technical Requirements Planning for Local Projects Project Preparation Identify Technical Requirement Procure Hardware  SAP AG 1999 Identify technical requirements: The purpose of this activity is to identify the technical infrastructure needed to implement R/3, and to clarify the customers expectations. Procure Hardware: The purpose of this activity is to procure the hardware needed for the SAP environment and place the hardware order with the appropriate vendor(s). Carefully plan the procurement of the subsequent systems (quality assurance and production systems, additional application servers, storage devices, etc.) to avoid unexpected lead times that could impact the SAP implementation schedule. Hardware procurement lead-times can vary from days, weeks, to even months.© SAP AG TSCM52 24-23
  23. 23. Phase 1: Project Preparation - Work Packages (5) Initial Project Project Planning Project Kickoff Procedures QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The purpose of this work package is to formally announce the initiation of the SAP project to the whole organization. This kickoff meeting should include the presentation of the overall goals, detailed task plans, and processes. Consultants, steering committee, senior management, project managers from the company, SAP and any other implementation partners must be involved. The kickoff meeting is focused on the organization as a whole, while the project team standards meeting is focused on the project team. It is important that – as part of the Change Management – the kickoff meeting is followed by regular communication to the rest of the organization about the progress, achievements, etc. In case of a local rollout project as part of a global program, reference should be made to the global implementation program; the global rollout manager and the global rollout core team must be involved as well.© SAP AG TSCM52 24-24
  24. 24. Kickoff Meeting Project Preparation Motivate the individuals involved and bring them together as a team Explain the implementation strategy, timeline, and project goals and objectives Clarify team member roles, responsibilities, and common objectives Project Introduction to the Whole Organization  SAP AG 2001 The first purpose of this activity is to inform all staff members involved about the start of the project. The goal here is to: - Introduce the people involved in the project - Present the functionality and benefits of the new solution - Introduce SAP and the implementation partners and explain their roles in the process - Explain the project plan and the different deliverables throughout the process - Show commitment of the Executive Management to this project - Generate some positive excitement amongst the end-user community The second purpose of this activity is to arrange and conduct a meeting amongst all people directly involved in the project to accomplish the following goals: - Motivate the individuals involved and bring them together as a team - Explain the implementation strategy, timeline, and project goals and objectives - Clarify team member roles, responsibilities, and common objectives - Outline Key Organizational Change Management goals and objectives This milestone activity is a critical checkpoint that officially launches the SAP implementation project to the entire organization. Be sure to allow adequate time for questions and answers, as some issues could require clarification. In case of a local rollout project as part of global program, reference should be made to the global implementation program.© SAP AG TSCM52 24-25
  25. 25. Phase 1: Project Preparation - Work Packages (6) Initial Project Project Planning Procedures Project Kickoff QC Create Training Plans Technical Req. Req. Planning  SAP AG 2001 The purpose of this work package is to provide final verification of all prior project planning and deliverables from this phase. It is critical that regular quality checks be performed throughout the phase, as tasks are completed. All issues regarding scope, project environment, and initial technical setup must be addressed. There are two types of quality reviews mentioned in this work package. The first is an internal review conducted by the project leadership team. The second is an independent external review using the SAP Review Program.© SAP AG TSCM52 24-26
  26. 26. Perform Quality Check and Obtain Approval QC Perform Internal Quality Check Project Preparation Review Obtain Approval Accelerators: SAP Service SAP Project Review Program  SAP AG 1999 Perform Internal Quality Check: The purpose of this activity is to collect all deliverables and to review them together for completeness and accuracy. Quality checks are performed as specific tasks are completed. However, it is also critical to review deliverables in total because individual results from one task can have an adverse impact on another area of the project. Project Preparation Review: The purpose of this activity is to recognize potential project risk areas during the Project Review at an early stage. This reduces the possibility of an extended project timeline. It leads to a faster implementation and increases the customer’s level of confidence. Obtain Approval: The purpose of this activity is to obtain the approval from the customer. Upon completion of this activity, signoff is obtained and the project proceeds to the next phase.© SAP AG TSCM52 24-27
  27. 27. Overview Diagram: Implementation Roadmap (2) Implementation Phase 1 Roadmap Project Preparation Phase 2 Business Blueprint Phase 3 Realization Phase 4 Final Preparation Legend: Phase 5 Unit Unit Go Live & Support Topic Topic  SAP AG 1999© SAP AG TSCM52 24-28
  28. 28. Phase 2: Business Blueprint: Objectives Upon completion of this topic, you will be able to: Explain the activities and tasks that are important in the Business Blueprint Phase of the SAP implementation project Explain the importance of the Question and Answer Database (Q&Adb)  SAP AG 2001© SAP AG TSCM52 24-29
  29. 29. The Purpose of Phase 2: Business Blueprint ASAP Roadmap Project Preparation Final Preparation Go Live & Business Realization Support Blueprint  SAP AG 2001 The purpose of this phase is to create the Business Blueprint, which is a detailed documentation of the results gathered during requirements workshops. The Business Blueprint details the agreed business process requirements of the company. It documents the common understanding of how the company intends to run its business within the SAP system. During this phase, you also: Refine the original project goals and objectives Define the Baseline scope Refine the overall project schedule and implementation sequence© SAP AG TSCM52 24-30
  30. 30. Business Blueprint - Roles & Key Focus Phase Content Project Org. Chg. Project Team Config Chg. Org. BusinessRole QC Mgmt. Mgmt. Training Sys Admn Structure Proc. Def. Proc. Def.Groupings Steering Determine Steering Meetings Sign-Off Enhancements Sponsors *************** Org. Impact/ Attend PTT Sign-Off Risk / Sponsor Review, Status Meetings Comm./ Doc., Org. Structure Approve Tech Assemble Bus Quality Check/ Proj. Mgmt. Proj. Guidelines/ & Steering Issue Mgmt. Design Blueprint Sign-Off Workshops Meetings Project Consultant ************** IMG/Master *************** Records Requirements Customer Attend PTT BP/ARICE Tech Design/ Deficient Set up Dev Areas Refine Project Technical Env/ Install ************** Plan h/w, printers, networks Training EUT & Doc. Training Effectiveness strategy/delvy. Org Structure Org Team Bldg. Org. Impact/ Change Activities Risk / Sponsor Guidelines/ Optimization Attend PTT Workshops Analysis Attend PTT Set up Proper Security Authoriz.  SAP AG 2001 These are the primary roles in an SAP implementation (all the roles are defined in the Implementation Assistant). Steering Committee - members include Project Sponsors, the SAP Consulting Manager (and/or the TeamSAP Coach), and project managers. The committee is also the primary source for the company’s long-term goals and vision, sets priorities, approves scope, and resolves company-wide issues. Project Sponsor - Directly communicates the company’s long-term goals and visions and are members of the steering committee. Project Management - TeamSAP Project Manager and Customer Project Manager Consultant - TeamSAP Members, application, cross application, business process Customer - Project Team Members (business process, power users) Technical - Customer or consultants for System Administration and Technical, help desk provider Training - Training & Documentation, Project Manager/Lead, Training and Documentation Developer/Instructor, Training Coordinator, Training Technology Administrator Change -These are dedicated individuals assigned to manage the organizational change management processes: Risk Assessment, Communication, Sponsorship and Leadership, Skills Development, Knowledge Transfer or Business Optimization. Security - Authorization, Administration, or Internal Auditor responsible for managing the system security and authorization environment and may be combined with other (technical) administrative roles. Shared items are marked by the ************ brackets.© SAP AG TSCM52 24-31
  31. 31. Documents of an ASAP Project 1 2 3 4 5 Project Charter Q&Adb Master Lists Cutover System Substructures: Microsoft Excel Plan Performance Project Spreadsheets for Business Strategy Development, Organization, Volume Review Plan Organization Test Business Processes and General Settings Authorizations Master Data Stress Scope Business Process Test Cross Application Technical Project Development BPP Progr. Operations Team Develp. Config. Manual Org. Plan EU Testing Training Stand. & Business Material Plan Proced. Blueprint Conduct Microsoft Word Unit testing Documents Test scenario End User Integration Training  SAP AG 2001Phase 1 - Project Preparation Change Charter - Goals and objectives of Organizational Change Management Project Plan - This is a first cut focusing on milestones and Work Packages; details to come. Scope - Sets the initial definition of the project; input from sales cycle. Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and how of the project.Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities Cutover Plan - The details of how to move to the production environment and go live Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going livePhase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.© SAP AG TSCM52 24-32
  32. 32. Phase 2: Business Blueprint - Work Packages (1) Project Management Organizational Change Management Design Training Plans Technical Design Planning QM Establish Development System Environment Organizational Business Process Structure Definition Definition  SAP AG 2001© SAP AG TSCM52 24-33
  33. 33. Project Management Project Management Checklist • Prepare and attend status meetings Documentation • Prepare and attend steering committee meeting • Correct project Configuration variances • Refine project plan • Change Management • Team-building activities  SAP AG 2001 The purpose of this work package is to establish a proper cycle of project management activities, which ensure that the implementation project is on target. It determines all project planning, controlling and updating activities. It also identifies where changes in the relationship between business processes and the organizational structure need to be managed, in consultation with departmental management. The same work package is also in the subsequent phases. The Project Review Program is provided as an SAP service. Reviews can be scheduled throughout the duration of the project. A review provides an independent and objective management verification of a company´s SAP product implementation project, identifies any risks to the project goals and recommends appropriate corrective actions.© SAP AG TSCM52 24-34
  34. 34. Organizational Change Management Business Blueprint Activities Initiate and Conduct OCM Risk Assessment Determine potential Set priorities, Establish and take bearing all possible steps designed to risks outcomes in mind minimize risks Plan and Establish Sponsorship and Leadership Process Plan and Establish Measure/evaluate effectivity of steps taken Communication Process Implement Business Optimization Process Accelerators: n OCM Implementation White Paper n Communications White Paper n Organizational Optimization White Paper  SAP AG 2001 The purpose of the Organizational Change Management work package is to address the organizational and human resource factors that have an impact on the SAP implementation. The Organizational Change Management work package includes a series of change processes that allow the change team to manage organizational risks. These Organizational Change Management processes ensure that the change team understands and manages the company’s perceptions of and responses to the changes that will occur after the implementation of the SAP System. During the Blueprint Phase the Organizational Change Management creates the foundation for a well integrated Organizational Change Management program.© SAP AG TSCM52 24-35
  35. 35. Design Training Plans Business Blueprint Activities Conduct Project Team Training Analyze End User Training and Documentation Strategy Prototype End User Training and Documentation Deliverables Accelerators: Project Team Training Template Curriculum Planner Training Environment Setup and Considerations Knowledge Warehouse (Information)  SAP AG 2001 The purpose of this work package is to finalize and conduct level 2 of the project team training. During the training business blueprint phase, the end user training and documentation strategy is carefully analyzed. The training team develops the training curriculum and selects the delivery tools. End user training and documentation prototypes are demonstrated during this phase. The purpose of the Conduct Project Team Training activity is to conduct Level 2 project team training so that team members can obtain an overview of the business processes or technical features in their area. This training is a prerequisite to the detailed business process courses and detailed technical courses (Level 3 training), and enables the project team to start to match their company requirements with SAP functions during the Business Blueprint phase. The purpose of the Analyze End User Training and Documentation Strategy activity is to analyze the end user training and documentation strategy, and finalize the plan for developing the training content, training documentation, and training delivery. The purpose of the Prototype End User Training and Documentation Deliverables activity is to design and develop a training and documentation prototype, and analyze and determine the system requirements necessary for conducting training. The tasks involved with this activity will occur at times simultaneously with the tasks in Analyze End User Training and Documentation Strategy.© SAP AG TSCM52 24-36
  36. 36. Phase 2: Business Blueprint - Work Packages (2) Project Management Organizational Change Management Training in the Business Blueprint Phase Technical Design Planning QM Establish Development System Environment Organizational Business Process Structure Definition Definition  SAP AG 2001 The purpose of the Technical Design Planning work package is to •Further define the planning that was started in phase one. •Document the technical design. You should anticipate the future needs of additional SAP systems and hardware as the project continues and begin the technical design planning for them as early as possible. The purpose of the Establish Development System Environment work package is to install and set up the development system for the start of implementation. For local rollout projects, as part of a global implementation project, the Global Solution Package will be used to set up this environment. Please refer to the task Getting Familiar with Global Solution Package in Phase one of the Rollout Roadmap.© SAP AG TSCM52 24-37
  37. 37. Technical Design Planning Business Blueprint Activities Create Technical Design Establish Development Environment Upg r Sra ade tegy Activities Set up Development Environment System Administration Procedures Accelerators: IT Infrastructure Document SAP Web Installation Guides SAP Software and License Keys  SAP AG 2001 Create Technical Design: The purpose of this activity is to define and document your technical design. It is recommended that you seek support from your hardware partner for this work. Set Up Development Environment: The purpose of this activity is to install and configure the technical environment for the development system. This activity includes installing the hardware, verifying the technical environment, installing the SAP software and frontend components, and configuring and securing the technical environment of the SAP System. System Administration Procedures: The purpose of this activity is to define and verify the system administration procedures for the development system. It is an ongoing process throughout the Business Blueprint phase.© SAP AG TSCM52 24-38
  38. 38. SAP Service Marketplace The SAP Service Marketplace is SAP´s one-stop Internet platform that provides personalized access to all services necessary to design, build and maintain a high quality solution Support Services Benefits Easy, one-stop access to Submit messages, access support packages and SAP SAP services - anytime, notes anywhere A full range of services to Request remote service sessions like Early Watch ensure solution completeness KEY COMPONENTS Consulting & Education Services Information that is easy to Request hardware sizing, consulting find and understand, as you navigate easily Online booking of training sessions worldwide through well-organized topics - and you can Information Services personalize the site to suit your needs Detailed information around the SAP solutions SAP related new offerings Download best practices materials For customers http://service.sap.com Available now and Partners  SAP AG 2001© SAP AG TSCM52 24-39
  39. 39. Phase 2: Business Blueprint - Work Packages (3) Project Management Organizational Change Management Training in the Business Blueprint Phase Technical Design Planning QM Establish Development System Environment Organizational Business Process Structure Definition Definition  SAP AG 2001 The purpose of this work package is to define the enterprise organizational structure using SAP organizational units, such as company codes and sales organizations. In conducting the organization structure workshop, topics such as the following need to be addressed: •What enterprise areas and business processes will be used in the system? •Which organizational units within the company will be affected by the implementation? For a rollout project, many of the organizational structure elements may already have been included in the template. For the part remaining, documentation for the intended solution including naming conventions will usually be provided by the global solution package from the Global Template project. The organizational structure(s) will then have to be reviewed, validated and completed.© SAP AG TSCM52 24-40
  40. 40. Define Business Organization Structure Business Blueprint Tasks Schedule and Prepare Organization SAP Reference Model Structure Workshop Conduct Organization 1 Business Strategy Structure Workshop 1 Organization Recommend and Approve Organization Structure Accelerators: Organization Structure Presentation Enterprise Modeling - Consultants Handbook Sample Scope Document  SAP AG 2001 The purpose of this activity is to prepare for business organization structure workshops to define the organizational structure of the company within the system. The organizational structure is established to give structure to the logistic and financial enterprise areas.© SAP AG TSCM52 24-41
  41. 41. Q&Adb Structure SAP Reference Structure 1 Business Strategy 1 KPI 1 mySAP.com 1 Organization 1 General Settings 1 Master Data 1 Business Processes 1 Cross-application 1 Training and Documentation 1 User Roles 1 Basis 1 Development QAdb Report QAdb Issues QAdb User QAdb Documents  SAP AG 2001 The section under Business Strategy sections contain items designed to collect information about the general business strategy and the implementation. The Key Performance Indicators (KPI) substructure is designed to assist you measure, analyze and improve the value added process and business performance in your enterprise. The mySAP.com substructure is there to assist you analyze and document how you might implement the SAP Internet solution in your enterprise. The Organization substructure contains items that describe the R/3 system organization structure. This is the framework in which the R/3 System is configured. The General Settings section contains elements of the R/3 Implementation Guide (IMG). This is of overall importance for Business Blueprint phase to set up the R/3 system properly. The Master Data section contains items that describe the master data structure that controls the behavior and implementation of an R/3 System. The Business Processes area of the Q&Adb contains the process structure items as represented in the SAP Reference Structure. The Cross-application section refers to all data objects (tables, entities or processes) that relate to more than one business application. The Training and Documentation section collects information about the planned training and documentation standards in an SAP product implementation. The User Role node provides all the SAP user roles (based on Release 4.6B of the R/3 System). The project team can use these roles to analyze the project-specific requirements for user profiles. The content of the Development area is created automatically by the application. It is designed to hold all functional specification documentation data that you entered in the Associated Items box The Documents substructure of the Q&Adb allows you to store and manage all documents related to the entire life cycle of your SAP System. For example the Business Blueprint document and drafts thereof would be stored here.© SAP AG TSCM52 24-42
  42. 42. Associated Items 1 SAP Reference Structure Associated Items 1 Business Strategy Business Analysis 1 KPI 1 mySAP.com Question 1 Organization CI Template 1 General Settings BP Transaction 1 Master Data User Roles 1 Business Processes Project Documentation SAP Documentation 1 Cross-application IDES Documentation 1 Training and Documentation 1 User Roles 1 Basis 1 Development QAdb Report QAdb Issues QAdb User QAdb Documents  SAP AG 2001 The Question(s) enable you to gather requirements on specific business scenarios and their processes. A question may appear within several structures. The answer to a question on a specific occurrence within any structure is visible on all other occurrences using that question. While answers given to a question are visible at all occurrences, questions can only be answered and answers can only be changed at the current structure level. These questions are open-ended and promote the flow of information between you and the consultants who will configure your system. Using your answers as a guide, consultants define your company’s requirements in detail and adapt process models to reflect your company’s needs. The User Roles enable consultants in the Blueprint phase to identify, adapt and describe SAP- delivered user roles based on project-specific requirements. The CI template sections form the heart of the Business Blueprint document. It is important to provide as much information as possible when entering your answers in these sections. In some cases the information may not be known at the Blueprint stage, if this occurs, it should be noted in the CI template answers. For example, when you enter the Authorization Considerations question during the Business Blueprint phase only high level information is available. As this changes, the Q&Adb should be updated with detailed authorization requirements. During the initial Q&Adb setup, you specified the path to SAP and IDES documentation. This documentation is available for view only and cannot be changed. If an SAP or IDES document is available for a selected function, the name of the document displays in the Associated Items box. Click the document to view it. You may add, view, or delete documentation to the Project Documentation folder in the Associated Items box. It is recommended that all documents are put into the Project Documentation directory so that they can then be found in the Q&Adb directory.© SAP AG TSCM52 24-43
  43. 43. Associated Items 2 SAP Reference Structure Associated Items Information Technical Analysis Status Functions Conversions Not Yet Processed Input / Output Interfaces In Process Organizational Units Reports On Hold Project Documentation Forms Completed Key Performance Indicator Other Development Predefined Where used Enterprise Area Where used Scenario Note: Availability of Associated Items Objects depends on Structure Level  SAP AG 2001 The Associated Items frame which appears on the right side of the Q&Adb application screen represents a user interface work area and a display area for user-specific information. The range of possible associated items are indicated above. However, note that the actual associated items displayed at any one time in the Q&Adb will be those linked to the SAP reference structure item currently selected. The Technical Analysis tab allows you to specify development requirements for your project. This information is used to draw up a technical specification from the Development List (DL) that forms the basis of programming. There are specific functional and technical specification templates for each of the areas on the Technical Analysis tab.© SAP AG TSCM52 24-44
  44. 44. Compose Project Structure SAP Project Reference Structure SAP Product Reference Structure CRM BBP R/3 SAP Reference Structure SAP Reference Structure SAP Reference Structure SAP Reference Structure 1 Business Strategy 1 Business Strategy 1 KPI 1 KPI 1 mySAP.com 1 mySAP.com 1 Organization 1 Organization 1 General Settings 1 General Settings 1 Master Data 1 Master Data 1 Business Processes 1 Business Processes 1 Cross-Application Components 1 Cross-Application Components 1 User Roles 1 User Roles 1 Training and Documentation 1 Training and Documentation 1 Basis Components 1 Basis Components 1 Development 1 Development  SAP AG 2001 You can map SAP Reference Structures of various mySAP.com components in a Q&Adb. This enables you to create a Business Blueprint for a mySAP.com solution that consists of more than one mySAP.com component. •Compose Project Structure: The project manager can group together SAP Reference Structures of various variants, such as R/3, APO, and BW. This enables the project team to process the entire implementation scope in one Q&Adb. •Before the project reference structure is created, the SAP Reference Structure on the left of the Q&Adb screen area only contains structure items from level 1; in other words, the structure still has to be "filled." The project manager and business process team can define the project scope under Administration -> Compose project structure. The Create Project Reference Structure dialog box displays the SAP Reference Structures of all variants installed as indicated on the right under “SAP Product Reference Structure”. •The structure items selected as in scope can then be transferred from the SAP Product Reference Structure to the SAP Project Reference Structure (from right to left) and processed in the Q&Adb.© SAP AG TSCM52 24-45
  45. 45. Scoping Edit View Reports ... ... Set in scope Project scope ... SAP Reference Structure SAP Reference Structure 1 Structure Item A 1 Structure Item A 2 Structure Item B 2 Structure Item C 2 Structure Item C 3 Structure Item E 3 Structure Item D 3 Structure Item E  SAP AG 2001 Before you begin answering questions, decide which structure items are valid and appropriate for your business. Setting these items In Scope delimits the information gathering of the Q&Adb to your specific business. Any one or all hierarchy items can be set in scope by right-clicking on that item in the tree view and choosing Set in scope. In Scope areas appear in yellow for easy identification. In Scope status can be removed from individual hierarchy items as necessary by clicking the checked Set in scope menu item. If you would like to see only the items in scope, choose View-> Project scope.© SAP AG TSCM52 24-46
  46. 46. Set Owner SAP Reference Structure Select Owner 1 Structure Item Business Owner 2 Structure Item Consultant 3 Structure Item  SAP AG 2001 An Owner is person who is responsible for one or many Structure items on different levels. You can assign an owner from the customer’s project team and/or a consultant to each structure item. You can: •Generate View by Owner This view displays only the structure items assigned to a particular owner. For example, you can display structure items for which you are the owner or for which you have assigned a particular team member as owner. •Use the Owner report option This means that only those structure items that are assigned to you or to one of your team members are included in the report. •Include the name of the owner for each structure item in your report Setting ownership ensures that a warning message appears if a user changes a structure item which is assigned to another owner.© SAP AG TSCM52 24-47
  47. 47. Issues Database Edit View Reports Administrative Issues All by Classification All Issues All by Project Phase Current View All Issues Closed Issues .... Listing in Open Issues Issue Editor and Documentation EXCEL Table Unsolved Problems Details Priority, Status, Project phase, Priority, Responsible Action Item Prority, Resolution Effort Category, Planned, Actual, Remainung  SAP AG 1999 Documents MS-XL, MS-Word, MS-PP The Issues substructure helps the project management team to record, monitor, and manage open questions or unforeseen problems that arise during implementation. Issues may hinder project progress or even jeopardize its success if a solution is not found. They may have an impact on the project scope, budget, timeline, and resources. When you log on, the system informs you of any outstanding issues for which you are responsible. You can choose to go directly to your open issues. The system will also display a message telling you if you have been informed about an issue.© SAP AG TSCM52 24-48
  48. 48. Business Strategy Business Blueprint SAP Reference Structure Business Analysis Status 1 Business Strategy Question Project Documentation 2 General Enterprise Strategy 2 Markets 2 Procurement Strategy  SAP AG 1999 In this substructure, you can gather information on your enterprise’s general business strategy. Using questions and customer input templates, you are able to, for example, analyze your business strategy, describe your corporate culture and give details of your competitive and market position. The information you enter here is of strategic importance to your enterprise and essential for mapping your enterprise specific requirements to the SAP System.© SAP AG TSCM52 24-49
  49. 49. mySAP.com Business Blueprint SAP Reference Structure Business Analysis Status 1 mySAP.com Question CI Template 2 The Marketplace Project Documentation 3 Buy Side 3 Sell Side 2 Workplace  SAP AG 2001 In the mySAP.com substructure, you can analyze and document how to implement your SAP Internet solution in your enterprise. The questions and CI templates contained here focus on the Workplace and the Marketplace. The project documentation stored in this substructure provide guidelines for successfully implementing mySAP.com. Customer Input (CI) templates exist for all structure items. Using these templates you can document and analyze the main areas of the mySAP.com substructure. The information you enter here is essential for drawing up your Business Blueprint.© SAP AG TSCM52 24-50
  50. 50. Organizational Structure Business Blueprint SAP Reference Structure Business Analysis Information 1 Organization Question Status CI Template 2 Cross-application.... Project Documentation 3 Company Code SAP Documentation IDES Documentation 3 Controlling Area ... 2 Procurement....  SAP AG 2001 The Organization structure level contains items that describe the system organization structure in which framework the SAP system is configured. In the Q&Adb, questionnaires facilitate gathering requirements on the company’s structure and processes that allow an initial mapping of the company’s business to a proposed SAP organizational structure. The answers to the questions form part of the Business Blueprint. The second level contains the available enterprise areas (e.g. Sales and Distribution). It is not recommended that you change or enhance this level of the organization structure. A third level further defines the organization (e.g. Sales area data).© SAP AG TSCM52 24-51
  51. 51. Reports (Business Organization Structure) Business Blueprint Edit View Reports Scope document Business strategy mySAP.com Business Blueprint - Reports All KPI - Scope document Organizational structure - Business strategy General settings Master data - mySAP.com mySAP.com Business processes Cross-application - Business Blueprint components User roles - Master lists Training and BPML documentation OSL Development DL Master lists AL Organizational Structure List - Status Business Process Master Issues List Development List Users Authorization List Status Report Administrative  SAP AG 2001 Issues Reports allows you to display project documentation in different forms, and creates a report structure in the Q&Adb.© SAP AG TSCM52 24-52
  52. 52. Phase 2: Business Blueprint - Work Packages (4) Project Management Organizational Change Management Training in the Business Blueprint Phase Technical Design Planning QM Establish Development System Environment Organizational Business Process Structure Definition Definition  SAP AG 2001 Business Process Definition The purpose of this work package is to determine the company requirements based on SAP business processes, to provide the required functions. The business process definitions create your Business Blueprint. In the case of a local rollout (an implementation project itself part of an overall, global implementation comprising a number of implementation projects), most of the company requirements should already have been determined at the global, program level and mapped to the corresponding SAP settings. Note that you must have defined your organizational structure before proceeding to business processes. In case of a local rollout, the Global Solution Package must have been delivered. This is the definition of the core requirement common across all implementations in a company’s multi site and/or multi national implementation of SAP product.© SAP AG TSCM52 24-53
  53. 53. Business Process Definition Business Blueprint INPUT Business Process OUTPUT Definition Business Process Questions Business Analysis Business Questions CI Template Blueprint SAP Reference BP Transactions Structure Master Technical Analysis Organizational Structure Functional Lists Specifications  SAP AG 2001 After the definition of the organizational structure, you define the business processes of the company in terms of the R/3 System. The Q&Adb is the tool supporting the definition of the business processes. You can use the CI (Customer Input) template and the business process questions within the Q&Adb to support the preparation and completion of the business process definition. For detailed analysis, you can access external tools for modeling the business processes via the Q&Adb. Generating the Business Blueprint gives you the company’s business process requirements in one document. Generating the Business Process Master List gives you the business processes which are in scope for Customizing in the Realization Phase.© SAP AG TSCM52 24-54

×