Category Archives: 1.1 ASAP


1.1 Customized ASAP Methodology

Company ABC follows the ASAP Methodology for SAP Implementation and Rollout programs. However the methodology is customized to leverage the Company ABC Global Delivery Model (GDM) and the requirements of the engagement. For the purpose of this engagement, only the Project Preparation and Business Blueprint stages are in scope. However the complete methodology is presented for a complete overview.

Company ABC has categorized the rollout track-wise as the Business Process Design, Technical Requirements, Data Migration and Training Tracks. The Rollout Track will be governed by the Company ABC Project Management Methodology. The subsequent sections explain the various phases of project as proposed by Company ABC.

ASAP Implementation Methodology for Implementation and Rollouts

The proposed Company ABC approach involves appropriate pieces of the project work being done at our offshore facilities. This approach differentiates Company ABC in that our mature Global Delivery Model (GDM) allows us to do the work where it makes the most sense. Our experience in delivering projects in this manner acknowledges that many ERP implementation project activities require hands-on, face-to-face interaction onsite. There are, however, other tasks which do lend themselves very readily to a combined onsite – offshore delivery model. The Company ABC Global Delivery Model lowers cost, enhances quality and speeds time to completion.

Phase 1: Project Preparation

The objectives of the Program Preparation phase involve aligning the program to the overall organization strategy, drafting overall project plan, resources for various phases, and conducting fit- gap analysis. The participants for this phase would be Company ABC and the client Team, Business Process Owners and super users.




· Conduct stakeholder interviews

· Identify drivers for rollout

· Understand existing systems landscape

· Discuss and agree on scope and detailed project-plan

· Finalize roles and team structure for project tasks

· Develop roadmap

· Identify Milestones

· Formalized Resource Requirements

· Project Team Roles and Responsibilities

· Project Standards

· Preliminary Training and/or Overviews

· Finalize Project Plan

· Finalize Budget

· Experience from past rollouts projects enables quick problem definition and roadmap preparation tailored to the client’s needs.

· Conduct workshops and interviews with project stakeholders

· Questionnaires for interviews and workshops to help determine scope and key pain points

Table 1. Project Preparation Snapshot

Phase 2: Business Blueprint

The objectives of the Business Blueprint phase are to lock down scope, define functional specifications, define required customizations and prepare data migration plan.

Activities during the Business blueprinting stage




· Define to-be business processes

· Develop reference template for US and Canada

· Conduct an as-is business process study

· Develop future IT landscape

· Prioritize customizations

· Finalize scope, gather requirements for conversion, customization and reporting

· Prepare Training Material and impart training

· Plan for development and documentation of requirements for data mapping, cleansing, conversion and validation

· Organizational and Master Data Design

· Detailed Process Analysis

· Gap Resolution

· Process and Solution Documentation

· Authorization Design and Approach

· Development Request Documentation

· Test Strategy

· Templates for gap analysis, functional requirements, high-level design and detailed-design documents

· Knowledge of industry best-practices

Table 2. Business Blueprinting Snapshot

Phase 3: Business Realization

The realization phase includes developing functional and technical specifications, work flow, system test plans, baseline and the final configuration. Additional activities also include creation of reports, forms; data cleansing, data migration and integration testing.

Activities during the Business Realization stage




· Complete custom development

· Final system configuration

· Functional/unit testing

· Conduct data clean-up activities

· Finalize cutover strategy

· Develop test plans and test cases

· Build integration test environment

· Build UAT environment

· Develop security roles


· RICE objects, forms and workflows

· Baseline and final configuration

· Converted data

· Unit test plans/scripts

· Cutover strategy and high-level plan

· Integration testing

· Security roles and profiles

· Performance monitoring plan

· Detailed strategy/plan for final prep and UAT

· Company ABC development methodology

· Best practices from Company ABC consultants

· SAP Solution Manager (optional)

· Templates for creating knowledge repository for specific industry.

· Experience in client system and business processes

· CMM Level 5 Quality Processes

Table 3. Business Realization Snapshot

Phase 4: Final Preparation

The final preparation involves validation of the solution design and development, extensive testing across the complete business cycle, user acceptance testing and preparation for Go–live & Support.

Activities during the Final Preparation stage




· Lead UAT

· Assist UAT activities

· Trial cutover

· Prepare for Go-Live including, security profile setup, helpdesk process

· Complete production data conversion

· Completed UAT; including documented test cases/scenarios

· Organization prepared for cutover

· Final configuration guide and support structure

· Impact analysis for “Go/No-Go” decision, including Go-Live success criteria

· Security roles/profile in production environment

· Production data conversion completed


· Company ABC consultants best practices

· Templates from Company ABC

· Checklists

· Use of testing tools like CATT for stress/ volume testing

· Test script templates enabling efficient remote execution

· Online Web-based issue tracker with context search

Table 4. Business Realization Snapshot

Phase 5: Go-live & Support

Go live & support involves transporting the customized system to the production environment and monitoring the live system.

Activities during Go-Live stage




· Execute business and systems cutover

· Activate helpdesk

· Transition to post go-live warranty support

· Finalize project documentation

· Handover to support organization

· Begin continuous improvement process

· Live production system

· Business and systems cutover

· Final configuration guide

· Service model

· Stable production system – acceptance documentation and go-live success checklist

· Production hand-off completed

· Established Procedures to ensure flawless cutover and data migration

· Extended business hours leveraging GDM to provide system support

· Proven handover methodology

Table 5. Go-Live Snapshot

1.2 Company ABC Training Methodology

Training Methodology is an integral part of the ASAP methodology at different phases of the project, namely Blue print, Realization, Final preparation & Go-Live support phases. Company ABC facilitates the Training process for the project but the client is responsible for training the users.

Provided below is the training methodology, that Company ABC follows for all its SAP Implementation/ Rollout engagements. Company ABC proposes a Training spanning across the entire SAP Rollout engagement. However considering the small number of users and already existing template in Dubai, the training activities will be redefined after discussions with Mittal Steel.

Training Project Phases Deliverables



Design Program

Audience analysis

Existing materials review

Hardware/software requirements

Identify tools

Identify standards

Work plan

Training strategy

Team onboarding



Develop Program

Pilot Program

Design Program

Course materials


Job aids

Training environment

Training data

Course schedule

Role/course mapping

Course pilots

Facilities/software tests


End-user registration

Course evaluation form

Administer training data base

Deliver courses

Course evaluations

Post Appraise Program

Provide Ongoing Support

Course evaluation summaries

Recommendations for improvement

Maintenance processes

Maintenance of training materials and data bases

Transition to permanent owners



ASAP Methodology

The ASAP methodology adheres to a specific road map that addresses the following five general phases:

1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work environment is set up;

2. Blueprint, in which the business processes are defined and the business blueprint document is designed;

3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;

4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and

5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation support is provided.

ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team.

Effective Communication

Weekly update meetings ensure full communication between the project team, the client project team, and project management. These meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline.

Ensuring Quality and Mitigating Risk

Project quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence the next phase of the project have been completed.

In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience gained on other projects has been taken into account and that the optimum system design has been utilized.