GENESIS ASAP Methodology Overview

October 2007

AcceleratedSAP Methodology

Description AcceleratedSAP methodology is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. AcceleratedSAP provides content, tools and expertise from thousands of successful implementations.

More infohttp://service.sap.com/asap

AcceleratedSAP - proven methodologyAcceleratedSAP methodologyProvides proven, comprehensive, repeatable and rich implementation methodology to streamline projectsPMI aligned framework with templates and tools for performing effective project management

AcceleratedSAP toolsetSAP Solution Composer SAP Roadmaps SAP Solution Manager

Aligns customers business requirements to SAP solutions

Offers AcceleratedSAP roadmap composed to fit specific project needs

Facilitates efficient solution design, documentation, configuration, testing and operations

ASAP Implementation MethodologyThe individual phases of the ASAP Implementation Roadmap are:

AcceleratedSAP Implementation MethodologyPhase 1: Project PreparationDuring this phase the project is formally initiated and initial planning completed for the SAP solution implementation project.

Phase 2: Business BlueprintThe purpose of this phase is to gather business requirements and achieve a common understanding of how the company intends to run SAP to support their business. The result is the Business Blueprint, a detailed documentation of the business design.

Phase 3: RealizationThe purpose of this phase is to build & test the solution defined in the Business Blueprint. The system configuration is delivered in two groups: Baseline (core scope); and Final configuration (remaining scope). This is then followed by Integration Testing.

Phase 4: Final PreparationThe purpose of this phase is to complete the final preparation (including performance testing, end user training, system management and cutover activities) and gain authorization to cut over to new solution. On successful completion of this phase, the business is ready to go-live with the SAP solution.

Phase 5: Go Live & SupportThe purpose of this phase is to complete solution confirmation of the live productive solution and close the project with the business successfully running the new solution.

ASAP Implementation at the glanceProject Preparation Business Blueprint

Realization

Final Preparation

Go Live & Support

1Project Charter Project Plan Mgmt. Plans Project Team OrgStandards & Procedures

2Solution Requirements

3Solution Build Developments Authorizations Portal(Content, Structure, UI)

4Cut Over Plan Technical Operations Manual

5Solution Information & Support

Enterprise Structure Master Data Business Process Configuration

BPP Config. Plan Business Business Blueprint Blueprint DocumentsDevelopment Specs

Test Plans(Unit, Scenario, & Integration Tests)

Test Execution

Performance & Infrastructure Tests

Project Closeout Report

TechnicalRequirements

Documents

& DesignSAP Solution Manager

End User Training Materials

Learning Maps

Deliver End User Training

Project Preparation PhaseDescriptionDuring this phase the project is formally initiated and initial planning completed for the SAP implementation.

Key DeliverablesProject CharterProject Budget Change Management Strategy

Milestones Business case approved QA gate 1 successfully achieved Project kick-off Project Team Training completed Project Team On-boarding Project logistics finalized QA gate 2 successfully achieved

Project Communications Strategy Stakeholder Management Strategy

Blueprint PhaseDescriptionThe purpose of this phase is to gather business requirements, understand any design gaps and determine how to resolve these. The result is the Business Blueprint, a detailed documentation of the business design for SAP.

Key DeliverablesProject Scope DocumentBlueprint Design Document List of Development Objects Configuration Spreadsheets Functional Specifications for DEV objects To-Be System Landscape

Milestones Completion of Design Workshops Sign-off Blueprint Design QA Gate 3 successfully achieved

Organizational Impact AnalysisEnd User Training Strategy Data Migration Strategy End-User Security Strategy Internal Controls Review

Blueprint Phase Workshop ApproachWorkshops will be used to achieve the following: Provide knowledge about specific SAP concepts and definitions Understand business requirements and capture the design implications Identify gaps between global template and existing business processes and between requirements and SAP functionality Identify change impacts resulting from the implementation of SAP Workshops Deliverables/Outputs: Business Session Summary (BSS) Key Design Decisions Gaps

The workshops structure will be as follows: Organizational Hierarchy Reviews Master data reviews Business process reviews Local Blueprint workshops Business Blueprint playback

Blueprint Approach

1 2 hours Business + Core Team Education Front-End

4 - 6 hours

1 2 hours Detailed Review

2 - 3 days

1 2 hours

Core Team

Detailed Analysis

Working Sessions

Working Sessions Present proposed Blueprint process to group.

Cover Bootcamp material Introduce key decisions required High-level Global Template review

Thorough walk thru of Global Template process; Deeper dive on Fit GAPS, etc.; Gain detailed understanding on Master Data, Processes & Configuration data

Present Findings; Obtain guidance on areas needing more detail

Complete details on configuration data, process changes, interdependencies, etc.

Final Review

Sequence For PlanningWorkshop Held, Then: ----Timing+ 2 Days + 5 Days + 3 Days + 2 Days

Areas to be CompletedWOF Draft, Finalization & Distribution All Actions Items Closed All Deliverables Revised Playback Held

Realization PhaseDescriptionThe purpose of this phase is to build & test the business requirements defined in the Business Blueprint.

Key DeliverablesCutover Plan is finalizedStress/Volume testing is completed Training Plan is finalized and Training material is prepared Integration testing is executed and results are signed off Organizational impacts have been analyzed and a plan developed to address issues

Milestones Completion of Build sub-phase Completion of Integration Testing Completion of User Acceptance Testing

Completion of SOX/IA review PRD system is ready QA Gate 4 successfully achieved

What is Realization?Realization is a project phase that begins with the development of a detail design based on the requirements defined and approved in Blueprinting. As the detailed design is approved, it will be translated into software configuration and programs which will be unit, functional and integration tested. Complementary deliverables such as training courseware will be built. Major areas of work and deliverables are: Configuration, scripting (BPPs) and unit testing Development and testing of enhancements, interfaces, forms and reporting Developing and testing of data conversion programs Design and execution of functional testing Design and execution of integration testing

Design, configure and test end-user security roles and profiles Project communications and change readiness assessments Development of role based courseware

Realization: Key Sub-PhasesIntegration Test 2ALL Development Objects ready for testing (remaining reports and forms) All security profiles and development objects need to be ready or project will be delayed. End-user roles have been created and unit tested and are available in the QA environment

Build1. Unit Test Global Template on local Dev in local language 2. Configure local processes in DEV 3. Development Objects created in Dev system 4. Unit test local design 5. Solution Manager project has been updated with all in scope scenarios, processes and steps 6. Build end-user security profiles 7. Create test scripts for local development/ configuration/ processes 8. Creation of all BPPs 9. All transports have been logged and identified for transport to QA environment 10. Project manager approval of transports to QA environment

Functional Test1. Short Process Chains 2. Test performed at Process and Process Step level with Solution Manager Test Workbench 3. Timing of processes during functional test can help with test master data 4. User-exists, workflows, load programs and Security profiles have been unit tested in DEV 5. Testing performed in QA system 6. All transports from DEV to QA complete 7. Test data has been identified and loaded into the test client

Integration Test 1

Integration Test 31. User Acceptance Test 2. Site or Super users perform test locally 3. Stress test of network 4. Full volume production data load required for testing 5. End-user roles have been created and unit tested and are available in the QA environment 6. Production data has been converted to the QA test client 7. End-users have been properly trained for test execution (Basic Navigation, SAP specific training)

1. Value Chains (End to End 1. Integrated process/Test scenarios) have been finalized and loaded into Solution Manager Project 2. Synchronized with Solution Manager: Scenario within 2. Solution Manager= Value Chain process flow in ARIS 3. All interfaces ready for integration testing (on completion of Unit and Functional Test) 4. All functional tests have been 3. executed with 90% of test scripts passed and no major open issues related to testing remain 5. Integration testing scenario variations have been defined and scripts have been prepared 6. Integration Test plans are generated 7. Full data conversions completed more than once successfully

Final Preparation PhaseDescriptionThe purpose of this phase is to complete the final preparations to migrate to new system. On successful completion of this phase, the business is ready to go-live with the new SAP solution.

Key Deliverables

Go-No Go decision meetingPRD support model implemented End-user training complete Data Migration testing complete

Milestones Training complete Cutover simulation test executed Approval to begin cutover attained PRD Support model implemented QA Gate 5 successfully achieved

Go-Live & Support PhaseDescriptionThe purpose of this phase is to complete the cutover to the new SAP system and stabilize the system. The project will then be closed when the business is successfully running the new solution.

Key Deliverables

Go-Live achievedPost-Implementation review completed

Milestones Go-Live achieved Completion of 1st month-end close System stabilized and handed over to long-term support group QA Gate 6 successfully achieved

Project Management in ASAP key principlesTerminology and process fully aligned with industry standards PMI PMBOK. Each Phase has a clearly defined start and finish. Uses Project Management Methodology (PMM) as the guiding principle for project management activities. ASAP delivers abbreviated version of Project Management Methodology (deliverables and related outputs). The methods are detailed in PMM. Every SAP partner can integrate their own methodology process with ASAP PM deliverables (as long as their PM process is PMI aligned). Focus on all Project Management areas (Integration, Scope, Time, Cost, Quality, HR, Communications, Risk and Procurement Management). Project team is encouraged to collect and document lessons learned. SAP specific Project Management templates for consistency.

PM Processes happen throughout the project

Each ASAP phase has Phase Start, Deliverable Creation/Acceptance and Closure tasks

Quality Gates

PMO QA ObjectivesThe PMO Quality Assurance process intends to measure and manage the status, risk and quality of SAP projects across AES consistently SAP implementation projects are high in complexity and are high risk for potential failure. The success of the AES program involves the identification and management of these implementation risks across all projects Detailed quality reviews for each project phase provides accurate information for making conscious decisions to timelines, scope and designs Confirmation of design at key project stages ensures that individual projects meet the original goals defined and the AES goals for improved financial controls and reporting The QA process will be proactive and performed during and at the start/end of each project phase. The QA process will provide information to the projects in a timely manner to make decisions in order to mitigate risk and be successful.

This is not a Quality Audit but a useful tool to make projects successful

PMO QA ApproachThe approach uses gating criteria for entering and exiting phases of the SAP implementation projects Each gate will have different criteria based on the phase, e.g.:

Deliverables that need to be complete for this phase Pre-requisites for the next phase Open items or issue managementProjects will report progress against the ASAP methodology deliverables and the criteria specified for the gate on a weekly basis using the project reporting template To deliver the proactive approach, Gate Meetings will be scheduled prior AND on the scheduled time to pass through the gate Each Gate criteria will be judged to be Red or Yellow or Green (High Risk/ Manageable Risk/ Low Risk) Risk mitigation plans will be created and project resources can be focused appropriately for Red and Yellow criteria. Project Leadership Team (PLT) and Genesis Global PMO will agree on necessary changes to the project approach, as necessary, to mitigate the identified risk Key Gates will require the sign off of both local business sponsors and Global Business Owners to ensure the project is SOX compliant, delivering the solution stated in the business case/project charter and in the AES global project goals

Quality Gates: DefinitionG oliv e

1

Project Preparation

2

BluePrint

3

Realization

4

Final Prep

5

Support

6

The intent of a Gate is to measure the readiness of a project to start or end a phase of an implementation project

The status of the project when the project when passing through the gate will determine the project risk

The amount of project risk will determine if the project should continue to the next phase or continue and fix problems by extending a phase

Each Gate has been numbered and has its own criteria

Each SAP project will follow the same phases and will pass through the same gates at different times

Quality Gates: Gate Criteria