Scribd
Upload
134 views5 pages

Project Preparation: Asap Project Preparation, Business Blueprint, Realization, Final Preparation, Go Live and Support

The document outlines the five phases of an ASAP implementation project for SAP software: project preparation, business blueprint, realization, final preparation, go live and support. It describes the key activities and roles in each phase.

Uploaded by

ruifalmeida_40616449
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
134 views5 pages

Project Preparation: Asap Project Preparation, Business Blueprint, Realization, Final Preparation, Go Live and Support

The document outlines the five phases of an ASAP implementation project for SAP software: project preparation, business blueprint, realization, final preparation, go live and support. It describes the key activities and roles in each phase.

Uploaded by

ruifalmeida_40616449
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

ASAP

Project Preparation, Business Blueprint, Realization, Final Preparation, Go Live and


Support
Project Preparation
- project managers set up the implementation project(s). They draw up a rough

draft of the project, appoint the project team and hold a kickoff meeting. The
kickoff meeting is critical, since at this time the project team and process
owners become aware of the project charter and objectives and are allocated
their responsibilities, lasting throughout the project
The project manager is responsible for planning and carrying out the project.
The application consultant creates the Business Blueprint by identifying the
business process requirements, configures the R/3 System together with the
business process team, transfers knowledge to the customer team members
and assists the business process team with testing.
The business process team lead at the customer site manages the work
involved in analyzing and documenting the enterprise's business processes.
This person directs and works with the business process team members,
process owners, and users in order to develop the R/3 design, configure the
system and validate the design. Furthermore, this person ensures that the
R/3 implementation is tested and documented, and obtains agreement from
both the business process owners and users.
The technical team lead at the customer site is responsible for managing the
completion of all technical project deliverables. The technical team lead
works with the Project Manager to complete the technical requirements
planning, and to plan and manage the technical scope and resources
schedule. The technical team lead is also responsible for the overall
technical architecture of the R/3 System.
The development project lead is responsible for managing the definition,
development and testing of necessary conversions, interfaces, reports,
enhancements and authorizations.
The R/3 system administrator is responsible for configuring, monitoring,
tuning, and troubleshooting the R/3 technical environment on an ongoing
basis, as well as performing checks, tasks, and backups within the technical
environment, scheduling and executing the R/3 transport system and
Computing Center Management System (CCMS). The R/3 system
administrator manages and executes the R/3 installations, upgrades and
system patches.

An example of an accelerator in ASAP is the "Project Staffing User Guide", which outlines all of the
project roles, expectations, time commitments and responsibilities for everyone involved in the
implementation. It also contains pre-defined organizational chart templates for the implementation team.

Business Blueprint
- In this phase you document and define the scope of your R/3 implementation and
create the Business Blueprint. The Business Blueprint is a detailed documentation of
your company's requirements in Winword format. Application consultants and the
Business Process Teams achieve a common understanding of how the enterprise
intends to run its business within the R/3 System, by carrying out requirementsgathering workshops.
During Phase 2, the project team completes R/3 Level 2 training; this is
recommended as early as possible and before the workshops start.
Fig. : Elements of the Business Blueprint

The project team selects the processes that best fit your business from R/3's
functional offering, using the following tools:

AcceleratedSAP Implementation Assistant


Question and Answer Database (Q&Adb)
Business Process Master List (BPML)
R/3 Structure Modeler
Business Navigator and external modeling tools

Defining the Business Processes

Realization
- The purpose of Phase 3 is to configure the R/3 System, in order to have an
integrated and documented solution which fulfills your business process
requirements.
In this phase, configuration of your system is carried out in two steps: Baseline and
Final Configuration. The Baseline configuration is designed to configure about 80%
of your daily business transactions and all of your master data, and organizational
structure. The remaining configuration is done in process-oriented cycles. The
Business Blueprint is used as the guide for the system configuration, done using the
Implementation Guide, which will be described in detail in this chapter. After this,
data transfer programs, as well as interfaces, need to be tested.
Fig. 3-1: Main work packages of Phase 3

Business Process Master List (BPML)


The Business Process Master List (BPML) is initially created in Phase 2 as a report from the Q&Adb. It is
used to identify, plan, schedule, and monitor the configuration and testing of all R/3 business scenarios
and processes within the scope of an implementation. The Business Process Master List is comprised of
Excel worksheets that collectively facilitate the configuration and testing of R/3.

Final Preparation
- The purpose of this phase is to complete the final preparation of the R/3 System
for going live. This includes testing, user training, system management and cutover
activities, to finalize your readiness to go live. This Final Preparation phase also
serves to resolve all crucial open issues. On successful completion of this phase,
you are ready to run your business in your productive R/3 System.
In Phase 4, your end users go through comprehensive training. The last step will be
to migrate data to your new system. In particular a going-live check is carried out
and an R/3 Help Desk set up.

Go Live and Support


Now you are ready to go live with your productive system! Afterwards, the project
team focuses on supporting the end users, for which training may not be
completed. It is also necessary to establish procedures and measurements to review
the benefits of your investment in R/3 on an ongoing basis. Key SAP Services to
support you in this phase include

The Online Service System (OSS)


Remote Consulting
EarlyWatch Services

These services encompass a series of remote analyses of specific R/3 System


settings, with recommendations for improving system performance.
Fig. Xx: Post go-live activities during productive operation

The last phase of the implementation project is concerned with supporting and
optimizing the operative R/3 System, both the technical infrastructure and load
distribution as well as the business processes. Activities such as the following are
carried out:

Production support facilities are defined, for example, checking system


performance on a daily basis
Validation of business processes and their configuration
Follow-up training for users
Signoffs, etc.

This phase can also include a series of follow-up projects for adding new application
components or automating and improving business processes, such as with SAP
Business Workflow. The project manager monitors the fulfillment of the enterprise
goals and the return on investment.
During Phase 5, the first EarlyWatch session should be held, where experts from
SAP analyze the systems technical infrastructure. The aim is to ensure that the
system functions as smoothly as possible. The purpose of SAP's EarlyWatch
Service is to improve the performance of your live R/3 System by preventing system
bottlenecks. The underlying concept of SAP EarlyWatch Service is prevention:
taking appropriate action before a problem situation develops.
Regular analysis of live R/3 Systems by teams of experts ensures that potential
problems can be recognized and remedied at an early stage. This maintains system
availability and performance at a high level. SAP EarlyWatch measures the server,
database, applications, configuration and system load. The results are recorded in a
status report with recommendations for system tuning.

You might also like