ASAP Methodology for Implementation

Purpose
The ASAP methodology for implementation is a phased, deliverable-oriented methodology that
streamlines implementation projects, minimizes risk, and reduces total cost of implementation.
ASAP takes a disciplined approach to project management, organizational change management,
solution management, and other disciplines applied in the implementation of SAP solutions. The
methodology supports project teams with templates, tools, questionnaires, and checklists, including
guidebooks and accelerators. ASAP empowers companies to exploit the power of the accelerated
features and tools already built into SAP solutions.
Benefits of ASAP include:

Faster implementations with streamlined and focused methodology

More reliable projects, thanks to proven tools, accelerators, and best practices

Lower risk

More efficient use of resources

Reduced costs

Effective project management based on Project Management Institute standards

Phases
The ASAP methodology delivers the following phases:

1. Project preparation

In the project preparation phase, the project team defines project

goals, a high-level scope, and a project plan. Executive sponsorship is
secured, and the project standards and organization are set up. The
implementation strategy is defined and approved. At the same time, the
project procedures, standards, organization, and staffing are finalized.
Roles and responsibilities of the entire project team are agreed upon and
documented. The objectives of the project are validated, and all initiation
activities are documented in the project charter.

2. Business blueprint

During this business blueprint phase, solution and technical designs

are documented in the business blueprint. Lead by solution and industry
experts from the SAP Consulting organization, a series of structured
process workshops are planned and executed to arrive at the to-be
delivered" SAP enterprise solution. All available documentation for
standard, delivered support for SAP business scenarios and all relevant
preconfigured support for best practices are reviewed and discussed with
SAP experts. All functional and technical requirements, coupled with
project issues and gaps, are documented in the SAP Solution Manager
application management solution.

3. Realization

In the realization phase, the SAP software system is configured and

tested in a number of cycles. Initially, the baseline configuration, which
represents the core business process settings, is performed, tested, and

confirmed. This is followed with a series of configuration and

development cycles, to implement the entire end-to-end solution. The
solution is tested in a number of cycle tests and in a focused end-to-end
integration test. Configuration is documented in SAP Solution Manager.
All development such as enterprise services, interfaces, data conversion
programs, reports, and any required enhancements are built and
documented in SAP Solution Manager. Legacy data conversion programs
are created and tested. The production system is installed during
realization.
4. Final preparation

Within the final preparation phase, all systems are known to function
correctly following the approved integration test. Technically, all
integration issues should now be resolved. Detailed transition and
cutover plans are created. The customer support organization is put in
place. The production system is set up with transports and customer
data. At the end of this phase, the production system is switched on and
business operations start in the new environment.

5. Go-live support

The purpose of the go-live support phase is to move from a

preproduction environment to live production operation. An easily
accessible production support organization must be in place to support
the end-user community, not just for the first critical days of production
operations, but also for long-term support.

6. Run

The primary goal of the run phase is to ensure the operability of the
solution. Operability is the ability to maintain IT solutions in a functioning
and operating condition, guaranteeing systems availability and required
performance levels to support the execution of the enterprises business
operations. The recommended starting point of the phase is an
assessment of solution operation after the go-live support phase to
identify the relevant SAP standards for solution operations to be
established or improved in the phase. The central operation platform is
SAP Solution Manager, with the documented solution based on the
transferred project documentation.

Work Streams
The ASAP methodology is structured around the key project work streams that are outlined in the
picture below. For each work stream, the methodology lists the number of deliverables that are to
be produced in each phase of the project.

The deliverables in later phases leverage or build upon deliverables completed in earlier stages.
The roadmap is structured as a work breakdown structure (WBS) that represents a complete list
of deliverables that need to be completed by the project team.
The ASAP methodology for implementation projects represents a standardized work breakdown
structure that provides the foundation for defining implementation project work in a deliverableoriented, hierarchical manner and managing the project work to completion.
ASAP methodology contains a standard set of templates, samples, accelerators, guidelines, and
checklists for use by project teams in effectively managing and completing SAP solution
implementation projects.