ASAP Methodology

The structure of the methodology: It has five phases. The phases have several work packages Each work Package contain activities The activities in turn have tasks. The Phases: Phase I: Project Preparation A phase in which the companies project team is finalized and trained in the ASAP methodology, a project plan is completed, project standards and procedures are determined, and the hardware order is reviewed.

Phase II: Business Blueprint A phase that builds a framework for understanding the business goals of the company and developing written documentation of the processes required to support those goals.

Phase III: Realization A phase in which blueprint requirements are configured and tested in the R/3 System. The company's business requirements are evaluated and transformed into the To-Be R/3 business solution. This transformation process is an iterative evaluation and refinement process where each business process is: ConfirmedThe Company's business requirements are evaluated to determine how they can be handled in the R/3 System. RefinedEach business process is refined into an optimal Business Process Procedure. FinalizedEach Business Process Procedure, along with its applicable configuration, is optimized to the companys business and information needs.

Phase IV: Final Preparation A phase that builds a framework for completing final testing, training end users, and preparing for cut-over of both the data and the system to a production environment.

Phase V: Go live and support A phase that outlines activities involved in reviewing the accuracy of the system and refining the system to ensure that the business environment is fully supported.

The Work Package for each phases:

Phase I: Project Preparation Initial Project Planning

The purpose of this is to allow the project team to start detailed planning for the project. This package includes activities like: 1. Creating and Issue project charter

2. Review and Refine Implementation Strategy 3. Establish Project Team Working Environment 4. Determine Project Organization 5. Prepare Project Plan 6. Create Project Team Training Plan

Project Procedures The purpose of this work package is to establish standard and procedures for the implementation of the project. It defines system landscape strategy. The procedures facilitate communication within the project team. This package contains tasks like: 1. Identify Project Communication Plan 2. Define Project Documentation 3. Create Issue Management Plan 4. Create Scope Management Plan 5. Create Team Building Plan 6. Define Project Planning and Monitoring Standards 7. Define Strategy for Using R/3 Services 8. Determine Quality Assurance Standards

Project Kickoff The project kick-off serves as an announcer for the implementation of the project. The Kick-off Meeting is focused on the company as a whole, while the Project Team Standards Meeting is focused on the project team. Technical Requirements Planning The purpose of this work package is to identify the technical requirements needed to implement the R/3 system, clarify the customers expectations, and to review hardware sizing and procure hardware. Quality Check Project Preparation Phase The purpose of this work package is to provide final verification of all prior project planning and deliverables from this phase.

Phase II: Business Blueprint Project Management Business Blueprint Phase The purpose of this package is to conduct steering committee, and project team meetings. It determines all the planning, controlling and updating activities of the project. It also has General Project Management activities. Project Team Training Business Blueprint Phase The purpose of this work package is to train the project team (key users) to implement the system.

Develop System Environment The purpose of this work package is to install the development systems. Also this is for designing and testing the system administration procedures for the development system and Initializing the IMG. Business Organization Structure The purpose of this activity is to prepare the business organization structure of the company within the system. This includes:

Scheduling Organizational Structure Workshop Requirements Distributing Organization Structure Guidelines Conducting Organization Structure Workshop Recommendation and Approval of the Organization Structure
Business Process Definition The purpose of this work package is to define the company requirements based on SAP business processes, to provide the required functions. This includes:

Conduct workshops for the business blueprint Plan the user training Complete the business blueprint Business Blueprint Review and Sign Off
Quality Check Business Blueprint Phase The purpose of this work package is final verification of all deliverables from the Blueprint phase. Also, it is for obtaining approval from the steering committee for this phase.

Phase III: Realization Project Management Realization Phase The purpose of this package is to conduct steering committee, and project team meetings. Also to establish a cycle of project management activities to ensure that the implementation project is on schedule. Project Team Training Realization Phase The purpose of this work package is to train the project team to implement the R/3 system. This includes product training for Phase Three. Baseline Configuration and Confirmation The purpose of this work package is to configure and confirm settings from the Baseline for scenarios, processes, and functions. This includes:

1. Developing Plans for Baseline Configuration 2. Configuring Initial Settings and Organizational Structure 3. Configuring and Validate Baseline 4. Preparing Baseline Confirmation 5. Performing Baseline Confirmation

System Management

The purpose of this work package is to prepare for productive operation. The activities include:

1. Develop System Test Plans 2. Define Service Level Commitment 3. Establish System Administration Functions 4. Set Up Quality Assurance Environment 5. Define Productive System Design 6. Define Productive System Management 7. Set Up Productive Environment

Final Configuration and Confirmation The purpose of this work package is to finalize and configure the system. The final configuration is an iterative process in which the business requirements of an enterprise is set up and confirmed. The processes and functions are grouped together as cycles (two or more) based on the value chains in the enterprise for the final configuration. Technical requirement Work packages. These packages contain tasks for the development work that is required for the implementation. The tasks is under these packages: Develop Conversion Programs Develop Application Interface Programs Develop Enhancements Create Reports Create Layout Sets

1. 2. 3. 4. 5.

Establish Authorization Concept The purpose of this work package is to create an authorization design that meets requirements, for users to do their jobs, and easy user maintenance. Establish Archiving Management The purpose of this work package is to establish archiving procedures to remove data not required in the R/3 system, but which must be accessible from the R/3 system. Final Integration Test The purpose of this work package is to plan and execute the final integration test. This is important for the functional verification of the productive system. It is a simulation of live operations. The test includes verification of dependencies of business processes on the value chain plus interfaces, output and print functions, and enhancements. End User Documentation and Training Material The purpose of this work package is to develop user documentation and training for Phase Four. The package includes the following activities:

1. Prepare User Documentation Development Plan 2. Create User Documentation 3. Develop User Training Materials 4. Prepare for User Training

Quality Check Realization Phase The purpose of this activity is to check the status of deliverables for completeness and accuracy. Phase IV: Final Preparation Project Management Final Preparation Phase The purpose of this package is to continue project management in the final preparation phase. End user training The purpose of this work package is to ensure that all users are adequately trained before the go live date. Training must reflect the scope of the implementation and the needs of the individual user. System Management The purpose of this work package is to perform the relevant technical activities to prepare for productive operation. These activities cover monitoring the productive infrastructure needs, determining required system administration activities, and testing the production system. The testing activities include:

1. Volume Test 2. Stress Test 3. System Administration Tests 4. Disaster Recovery Test 5. Backup and Restore Procedure Test 6. Printing Tests

Detailed Project Planning The purpose of this work package is to identify issues that impact the initial plan for production support and cut over prepared in Phase III. Cut Over The purpose of this work package is to obtain final approval from the Steering Committee for the system to go live. The tasks are:

1. 2. 3. 4. 5.

Transport to Production Environment Convert Master Data Convert Transaction Data Perform Manual Entries Final Approval for Going Live
Quality Check Final Preparation Phase The purpose of this activity is to check the status of deliverables for completeness and accuracy.

Phase V: Go live and support

Production Support The purpose of this work package is to provide support to R/3 users and to optimize system performance. The activities are: 1. Provide Production Support 2. Validate Live Business Process Results Project End The purpose of this is to verify the completion of the project and for a formal sign off. The tasks include: 1. Review and Close Open Issues 2. Review Business Benefits 3. Sign off and Close Issue List

Tools for the methodology:

Questions and Answers Database Open Issues Data Base Business Process Procedures R/3 Reference Model R/3 Procedure Model Implementation Guide Profile Generator Session Manager Presentation of the Organization Structure Structure Modeler documentation Knowledge Corner

Reports/ Documentation

Business overview Reports Business Process reports Blueprint Reports Business Process Master list Report Issues Reports Configuration Documentation End User Procedure Documentation Basis Documentation

Records Meeting Minutes Sign off forms (Phases I, II, III, IV, and V) Sales-to-Consulting Checklist Monthly Project Status Report Weekly team member status Report Weekly Project Status Report Sign off form - Basis Sign off form - Technical Requirement Final Sign off

Templates/Checklist/guidelines/ For Documentation and Records Phase I.

Enterprise area scope document (review the implementation proposal) Team Organization Chart Template (project organization structure) Sales-to-Consulting Checklist (project organization structure) Project work plan Report Meeting Agenda Template Meeting Minutes template Identify Monthly Project Status Report Template Weekly team member status Report Template Weekly Project Status Report Template Issues Form Template Change Request Form Template Change Request Log Template Project Kick off Agenda Template Project Activity Sign off Form Template

Phase II

Printing Questionnaire Checklist for system administration List of Daily Check (Basis) Daily Tasks form (Basis) Template List of Reorganization Reports (Basis) Executive Summary of Business Blueprint Presentation Template End-User Training Scope Questionnaire Template

Phase III

Technical Failure Testing Checklist Project Team Training Schedule Template User Procedure Template Sample sign off sheet for End user Documents Volume Test Plan Template Stress Test Plan Template

Phase IV

Technical Failure Testing Checklist

Phase V

Final Project Sign off Template

Testing Strategy

1. Conduct Volume Test 2. Conduct Stress Test 3. Conduct System Administration Tests 4. Conduct Disaster Recovery Test 5. Conduct Backup and Restore Procedure Test 6. Conduct Printing