ASAP Deliverable Sample

Global ASAP Key Deliverables
Copyright 2000 SAP AG. All rights reserved

Table of Contents
Page
3
4
5
6
7
8
9
10
Purpose
Phase 1: Global Program Setup
5.1.1 Program Charter
5.1.2 Program Organization
5.1.3 Program Plans
5.1.4 Program Procedures, Standards and Tools
5.1.5 Template Project Setup
5.1.6 Quality/Risk Management Review Program Setup
11
Phase 2: Global Business Blueprint
12
13
14
15
16
17
18
19
20
21
5.2.1 OCM Risk Assessment and Mitigation Plans

5.2.2 Early Roll-Out Preparation
5.2.3 Template Team Training Blueprint
5.2.4 Template Plans
5.2.5 Global Business Requirements
5.2.6 Global Business Blueprint Report
5.2.7 Global Systems Environment
5.2.8 Template Systems Environment Setup
5.2.9 Preparations for Local Project Delivery Systems
5.2.10 Quality/Risk Management Blueprint
22
Phase 3: Global Realization
23
24
25
26
27
28
29
30
5.3.1 Customer Competence Center

5.3.2 Template Team Training - Realization
5.3.3 Configured and Confirmed Template
5.3.4 Global System Management Procedures
5.3.5 Global RICE Development
5.3.6 Template Integration Testing
5.3.7 Final Roll-Out Preparation
5.3.8 Quality/Risk Management - Realization
31
Phase 4: Global Maintenance and Support
32
33
34
35
36
37
5.4.1Correction of the Template Solution

5.4.2 Requirements for Next Template/Version
5.4.3 Continuous Improvement within Program
5.4.4 Updated Business Case and Total Cost of Ownership
5.4.5 Future Plans
5.4.6 Quality/Risk Management Main & Support
Purpose of This Document

A key objective of Global ASAP is to provide recommended deliverables to
support the activities-based methodology. This list of deliverable definitions will to
be used by program/project team leads at the beginning of an implementation
program and throughout. This will help to ensure an understanding of the
methodology in terms that are easy to relate to and help to establish the program
time line.
Deliverables are defined as a result evidence of which is provided by
something tangible such as a document or by observation or by measurement,
which is important to the success of the project or program. This differs from
milestones that are described as An event of special importance, usually
representing the completion of a major phase of project work. Reviews are often
scheduled at milestones.
Deliverables will not replace the content-rich roadmaps, but provide a front-end
that identifies the WBS number of the applicable work steps in the roadmap. It is
for this reason that description of outcomes, and roles associated with outcomes,
are not included in the document, as this would be redundant to what is already
in the roadmap.
Where currently available, best in class examples are attached as links to the
deliverable description.

Phase 1: Global Program Setup Key Deliverables
The purpose of the Global Program Setup Phase is to initiate a global implementation and
management program.
The key deliverables for this phase include:
Program Charter
Program Organization
Program Plans
Program Procedures, Standards and Tools
Template Project Setup
Quality/Risk Management Review
Phase
ID #
Title
Global Program Setup
5.1.1
Program Charter
Description
The Program Charter, which is the summary document of the Program Definition workpackage of the CSS
Implementation Assistant, provides a solid foundation upon which to begin implementation planning for the
program. It helps reduce risk and helps to ensure a successful implementation. The Program Charter is a
comprehensive document containing business objectives ands goals, strategies, analysis of risk, and
relationship to other improvement initiatives of the enterprise. This document will contain important
information to properly position the program in the organization, both for those working on the program, as
well as those who will eventually be impacted by the implementation of mySAP.com components solutions.
It includes results from the approved High level scoping together with the approved Program Definition (the
detailed definition of the program elements) including the completed Customer Solution Map, Enterprise IT
Strategy, Implementation Strategy, Risk Assessment, Program Management Approach, and Business
Case. An important decision to be documented as part of the program charter is the methodology to be
used. This Program Charter identifies how the implementation will be conducted, as well as the impacts
and the expected value generation.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Program Scope/Optimum Solution Set

Implementation Scope
Enterprise IT Strategy
Implementation Approach
Program Management Approach
Organization Change Management Strategy
Business Case
Risk Assessment and Action Plan
CSS 2.4
CSS 3.2.1
CSS 3.3.1
CSS 3.4.1
CSS 3.6.1
CSS 3.6.2
CSS 3.7.1
CSS 3.5.1
Link to
Sample
Additional Information
The Customer Solution Strategy Roadmap is the first of three roadmaps that comprise Global ASAP. Many
companies consider this strategy definition effort phase 0 of the global program, and the output is a
prerequisite of a successful global implementation. The starting point for the Customer Solution Strategy
roadmap is a business vision, based on the customer-defined business goals and strategies. It is
necessary that the Strategy Team define the business vision/goals prior to beginning the Customer Solution
Strategy. The ultimate deliverable of the Customer Solution Strategy roadmap is a detailed program
strategy that has been documented in an approved Program Charter.

Phase
ID #
Title
5.1.2
Program Organization
Description
The purpose of this deliverable is to define and communicate the roles and responsibilities of people
involved in the global implementation program and to inform those members about their duties, expected
deliverables and program duration. The recommended Program Organization structure for the corporate
and overall program management of a global SAP implementation consists of:
Program Sponsor and Executive Steering Committee
Program Leadership Team
Program Manager(s) and Program Management Office (PMO)
Regional Program Manager (Optional)
Global Support/Account Manager(s)
Program Controls Manager(s)
Business Process Managers
Template Project Manager(s)
Global Rollout Manager
Technical Team Manager(s)
Change Management Team Leader(s)
The PMO is an organization that is responsible for the overall management of the program from the start to
the completion of the program. It consists of the Program Manager(s) supported by Global
Support/Account Manager(s) and a Program Controls Manager, with administrative support as required.
The Program Leadership Team encompasses the PMO with expanded representation and responsibility for
business process design/configuration, global template development and rollout, and, technical
architecture and supporting infrastructure.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Named Program Sponsor and Steering Committee

Program Leadership Team
1.1.1.3
1.1.1.4
Link to
Sample
Main Input for this deliverable comes from the Customer Solution Strategy Define High Level Program
Organization (CSS 3.6.1.2) In addition, recommendations for the program organization are derived from the
size and duration of the program as well as the experience level of the team and input from the
Implementation Partner.

Phase
ID #
Title
5.1.3
Program Plans
Description
Program plans organize program activities into a time perspective and form the program framework. The
correlation between program success and good planning is vital. The main purpose of Initial Program
Phase
# Title
Planning is to ensure that allID
parties
involved have the same understanding of the program objectives,
Global
Program
Setup
5.1.4
Programteam
Procedures,
and
Tools Planning provides the
targets and scope. The Program Leadership
facilitatesStandards
good project
planning.
control that allows comparison of where the program is supposed to be, so that corrective action can be
taken when there is a deviation. Good planning is essential to make critical deadlines.
Description
Program
planning
goesstandards
beyond creation
of the work
budget and
resource
plan. Eachof
work
streamand
It is essential
to create
and procedures
forplan,
the program
to ensure
a consistency
approach
(PMO,
OCM,
Technical,
Business
Process,
Training)
defines
and
executes
planning
for
activities
deliverables and to enable the repeatable process that is an inherent benefit of Global ASAP. Thethat are
particular tothat
their
of responsibility.
These
plans are
separate butthroughout
must closely
so that the
guidelines
arearea
established
also ensure
effective
communication
theintegrated
global program.
work is done in parallel.
Standards are defined as the rules or principles determined by the Leadership team that provide the
measure of quality for the work being done or simply put the accepted norms. Procedures are the
established way of doing things, a series of steps followed in a regular definite order. Program procedures
detail how the program content will be delivered by the program organization.
Determining the standards and procedures is an administrative activity geared to planning and monitoring
Program
Manager
Owner
the work of the
program.
The result is a set of procedures and standards that is effective worldwide and is
the basis upon which the global template development and subsequent local or national projects are
implemented.
Deliverable Outputs
Link to
Roadmap
Link to
Sample
Program
Plan Controls Manager
1.1.1.8
Owner WorkProgram
Program Resource Plan
1.1.1.8
Program Budget
1.1.1.8
Global Roll-Out Schedule
1.1.1.6
CCC
Implementation
Plan
1.1.3
Deliverable Outputs
Link to
Link to
Organizational Change Management Plan
1.1.1.9
Roadmap Sample
Communications Plan
1.1.1.10
Global Documentation Standards and Management Plan
1.1.2.1
Status Meetings Plan
1.1.1.12
Global Escalation Procedures
1.1.2.2
Program Team Training Plan
1.2.6
Scope Management Plan
1.1.2.3
Program Tools Infrastructure
1.1.2.4
Additional
Language
andInformation
Translation Policy
1.1.2.5
Main Input for thisProcess
deliverable
comes from the
Customer Solution Strategy Roadmap
Program
Decision-Making
for Development
Objects
1.1.2.6
Management
Approach
(CSS 3.6.1),
Organizational Change Management approach
(CSS 3.6.2) and
Global Planning
and Monitoring
Standards
1.1.2.7
Implementation
Approach (CSS 3.4) work package/activities.
Global Quality Standards
1.1.2.8
Interaction Points for Global and Local Teams
1.1.2.9
Standards for Handling KPIs
1.1.2.10
Template Versioning Standards
1.2.7
Phase
ID #
Title
5.1.5
Template Project Setup
Description
A Global Implementation program is the portfolio of projects aimed at implementing an organization-wide
SAP solution that should be planned and managed in a coordinated way. The projects together should
achieve the goal of delivering a set of defined business objectives that are well integrated in the
organizations global and local business strategies. The Global Program is designed to provide a uniform
rollout concept to local sites. The goal is to have a pre-configured central system in the form of one or
many templates and to roll it out locally as often as necessary.
A pre-configured global system, in the sense of a global template is the sum of all common (across
enterprise) customizing settings, models, etc. These are included in one R/3 system as the sole source of
reference for productive systems on the global and local levels.
A global program is usually comprised of multiple template projects. Each project is set up to create one or
more global templates which are subsets of the Global Template System which is the SAP system installed
at corporate headquarters that contains all global templates and shared data. The scope of the Global
Template System will likely require several Template Projects. Template Projects may be run concurrently
or subsequently and are managed as individual projects with their own Project Management Team.
Just as there are global and local business requirements, there are aspects of the template project that are
not governed by program planning, organization, standards and procedures. The Template Project Setup
deliverable defines in detail these template project specific elements.
Owner
Template Project Manager
Deliverable Outputs
Link to
Roadmap
Project Charter
Project Organization
Project Plans
Project Procedures and Standards
Project Team Working Environment
Project Team Training Plan
Planned and Procured Training and Demo Systems
Template Project Kickoff Meeting
1.2.1
1.2.4
1.2.3
1.2.7
1.2.5
1.2.6
1.2.8
1.2.9
Link to
Sample
Main input for this deliverable comes from the Program Charter and its outputs (Program Scope,
Implementation Approach, Program Management Approach), from the Program Organization, from the
Program Plans and from the Program Procedures and Standards. This will build the frame in which the
template project will be set up.
Phase
ID #
Title
Description
Quality management and risk management activities are recommended toward the end of each phase of
the implementation. Quality management is a major task for the Program Leadership Team who will
conduct a management review to assess whether sufficient progress has been made for the program or
project to begin the next phase. The quality of work will be an important consideration in the decision
making process.
The Quality Review assesses the following:
Adherence to the project implementation strategy; and use of the Global AcceleratedSAP
methodology and tools
Program progress compared to plan; milestone achievement
Deliverables quality, and conformance to the documented approval process
Program/Project Team, Steering Committee, and any other program dynamics; for example,
assessing the team structure and performance
Additionally, SAP recommends using the review services offered by the SAP Review Program.
Experienced SAP consultants conduct these reviews. Per definition, reviews are done by an external
specialist and not by the project team. SAP specialists who are not involved in the day-to-day business of
the project, visit the project as independent and objective auditors to assess the status and progress of all
activities. Potential risks to the project goals are identified and appropriate corrective actions are
recommended.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Internal Management Review

External (SAP) Review Program Findings Presentation
Updated Risk Assessment and Action Plan
Decision to Proceed Documented
1.3.1
1.3.2
1.3.1
1.3.3
Link to
Sample
Refer to the SAP Risk Management Program for guidance on conducting risk assessments, analyzing
costs determining mitigation plans
Phase 2: Global Business Blueprint Key Deliverables

The purpose of this phase is process and organizational requirements, solution design and global
template system readiness.
10

The primary objectives for this phase are:
1. Create the Global Business Blueprint.
2. Develop the global environment.
3. Install and configure the technical environment for the Template System.
Phase
ID #
Title
key deliverables
phase
include:
GlobalThe
Business
Blueprintfor this
5.2.1
OCM
Risk Assessment and Mitigation Plans
OCM Risk Assessment and Mitigation Plans
Description
Early Roll Out Preparation
Organizational Change Management is the systematic management of changes to an organization caused

by theimplementation
mySAP.com.
organization must consider the organizational and human
TemplateofTeam
Training The
Blueprint
resource issues associated with such an implementation. Regardless of scope, it is certain the
Template
implementation
will resultPlans
in changes to some or all processes. Potentially it will also result in changes to
job roles,
responsibility,
departmental
boundaries, and organizational structures, thus carrying with it a risk
Global Business Requirements

that the change will not be accepted by the organization. A plan is developed that addresses the changes,
and provides
steps
toBusiness
mitigate any
negative
impacts. The main components of all OCM activity are
Global
Blueprint
Report
communications, sponsorship, organizational optimization and team management.
Global Systems Environment

To manage the risks in a way that minimizes the companys exposure to risk associated with the potential
arising
Template
Environment
Setup
changes
from theSystems
implementation
project,
SAPs risk management program is the application of a
systematic methodology which:
Preparations for Local Project Delivery System
strategic advice
and direction
Provides
Quality/Risk
Management
Reviewfor managing change arising from the project in the
organization
Identifies potential risks
Creates plans for their minimization
Identifies opportunities
Creates plans for their optimization
Executes those plans
Owner
Change Team Lead
Deliverable Outputs
Link to
Roadmap
Risk Assessment Process

Risk Assessment Tool
Risk Assessment Strategy and Mitigation Plans
OCM Communication Plan
Sponsorship and Leadership Process
2.1.2.2
2.1.2.3
2.1.2.6
2.1.2.8
2.1.2.10
Link to
Sample
Main input is the Change Management Charter as part of the overall Program Charter.
costs determining mitigation plans.
11
Phase
ID #
Title
Global Business Blueprint
5.2.2
Early Roll-Out Preparation
Description
Early roll-out preparation pertains to planning and staging done in the Global project in preparation for the
roll-out projects that are to follow. Tasks occur before the roll-out project has officially started, but assumes
that some preliminary personnel have been identified. In a global project during Global Business Blueprint,
the initial preparation begins for the roll-out project, however the roll-out project has no official budget or
staff. It is at this point that the roll-out planning criteria, preliminary schedule and modeling concerns begin
to be addressed. Early roll-out planning provides a link for local projects to the global planning process.
This allows for mutual agreement and understanding on both the global and locals levels and promotes
early buy-in from the roll-out site management team.
The global blueprinting process and template development must also proceed by including appropriate
local input during the global project. It is also imperative that roll-out sites participate in business process
workshops so that local requirements are taken into consideration in regard to enterprise process and
organizational standardization.
Owner
Global Roll-out Manager
Deliverable Outputs
Link to
Roadmap
Global Rollout Plans

Rollout Site Sponsors Decision to Proceed
Project Organization and Roles
Technical Site Readiness Assessed
2.2.1
2.2.2.1
2.2.2.2
12
Link to
Sample
Phase
ID #
Title
5.2.3
Template Team Training - Blueprint
Description
The purpose of Template Team Training is to insure that the Template Project team members are
adequately trained in order to produce the Global Business Blueprint and then ultimately to implement the
system. Training must reflect the scope of the implementation and the needs of team members. Key
members of global rollout implementation teams may be available at this time and can benefit from this
training.
In the Global Business Blueprint phase, Level 1 and 2 SAP courses, both functional and technical, are
delivered to all business process owners and team members, as well as technical team members. Level 2
courses describe the business processes in the application areas. The technical courses provide baseline
knowledge and entry-level skills of the programming language, concepts, tools, and application programs.
When training is completed, it is necessary to assess the project team mastery of material and their
readiness and capability to proceed.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Training
Training Assessment
2.4.1
2.4.1.4
Input for this deliverable comes from Phase 1, Create Project Team Training Plan (1.2.6).
13
Link to
Sample
Phase
ID #
Title
5.2.4
Template Plans
Description
Prior to Global Program Setup, during the strategy study, numerous decisions regarding the Global
Program were determined, including the Implementation Approach (CSS 3.4.1), which details the
Implementation Strategy that addresses appropriate enterprise standardization and the global template roll
out strategy. In Phase 1, Global Template Project Setup, template scope (functional scope to be covered by
the Template Project) was further refined and initial planning was done.
In preparation for design of the global template, there is also an option to assess current live productive
systems to determine which of the existing solution is beneficial for adoption to the global template as a
starting point for modeling. The assessment determines if certain processes/scenarios are subject to
redesign or can be used as a starting point for modeling.
In the Global Business Blueprint phase, Template Plans, including recommendations from the productive
system assessment are reviewed, revised, fully detailed and approved.
Owner
Deliverable Outputs
Link to
Roadmap
Productive System Assessment

Updated Plans and Template Approach
Validated Template Requirements and Goals
2.5.1
2.5.2.2
2.5.2.1
Link to
Sample
Key inputs to this deliverable are the results of activities performed during the Customer Solution Strategy
Define Implementation Scope (CSS 3.2.1) and Define Implementation Approach (CSS 3.4.1). Additionally
activities preformed in Phase 1 of the Global Template Roadmap provide input Template Project Charter
(1.2.1), Verify Project Scope (1.2.2), and Prepare Template Project Plan (1.2.3).
14
Phase
ID #
Title
5.2.5
Global Business Requirements
Description
The Global Business Blueprint phase is the solution design phase where Global SAP business
process/scenario requirements are detailed. These processes will be standard throughout the enterprise.
Workshops are conducted to define the global organization structure, business processes/scenarios and
master data. In addition, global reporting, conversions, interfaces and developments are identified along
with internationalism impacts. Throughout this process, gaps are identified and solutions recommended.
Inputs into this process are business drivers and critical success factors identified during the strategy
definition, Solution Maps and KPIs along with the preliminary instance strategy.
The SAP Solution Manager is a portal that integrates content, tools, and methodologies necessary for the
solution-oriented evaluation, implementation, quick adaptation and continuous improvement of the
mySAP.com e-business platform. One of the key components is an implementation tool that contains the
functionality to blueprint, configure and test mySAP.com.
Business scenarios and processes are put into scope in phase 1 and then evaluated to detail what will be
in scope down to the process step level in Phase 2. Project standards and templates assigned in the
Solution Project in Phase 1 are used to document all business requirements in Phase 2.
Owner
Business Process Manager/ Technical Team Manager
Deliverable Outputs
Link to
Roadmap
Business Process Workshop Guidelines

Business Process Improvements
Global Organization Structure Requirements
Global Business Process Requirements
Global Master Data Requirements
Global Report and Form Requirements
Global Interface Requirements
Global Conversion Requirements
Global Enhancement Requirements
Global Parameters Requirements
Internationalization Impact Analysis
User Roles Specifications
2.6.1.3
2.6.2.1
2.6.2.2
2.6.2.3
2.6.2.5
2.6.2.4
2.6.2.11
2.6.2.10
2.6.2.9
2.6.2.6
2.6.2.8
2.6.2.7
Link to
Sample
Input for this deliverable comes from Phase 1 where the project scope (identified during CSS Define
Implementation Scope, CSS 3.2.1) is reviewed and verified.
Tools within the Solution Manager used to document business/scenario requirements are the Process
Library, project structure and document management. Document management in the Solution Manager
consists predefined templates including Customer Input Templates (CITs) to document process flows and
functional requirements as well as technical requirements and templates for scenario descriptions,
diagrams
and installation
guides.
Copyright
2000 SAP AG.
All rights reserved
15
Phase
ID #
Title
5.2.6
Global Business Blueprint Report
Description
The key deliverable of phase 2 is the Global Business Blueprint which is the conceptual master plan
representing the entire program. It serves as the basis for organization, configuration and development
activities in the next phase. All information regarding how the company intends to run its business running
mySAP.com is spelled out in the Blueprint. It includes comprehensive documentation of the global
business processes, master data and organization structure requiring standardization across the enterprise
as well as other objectives identified during the requirements workshops to be included in the global
template. It also describes the global parameters, interface programs, data conversions, enhancements
and global reporting requirements.
The Global Business Blueprint is generated from the Solution Manager. At completion, the blueprint is
checked to insure that integration across different business areas is consistent and that the business model
is complete and is consistent with the planned system landscape and technical design. Completion of the
blueprint signifies that the final project scope is frozen. Finally the scope of the first global template is
confirmed.
Owner
Deliverable Outputs
Link to
Roadmap
Global Template Scope

SAP Audited Business Blueprint
Global Business Blueprint Report
2.10.1.3
2.10.1.4
2.10.1.5
Link to
Sample
Main input for this deliverable is from workpackage 2.6 Global Business Process Definition where
business process, master data, organization structure requirements are identified along with RICE
developments.
16
Phase
ID #
Title
5.2.7
Global Systems Environment
Description
The high level enterprise IT strategy was defined during the Customer Solution Strategy phase prior to the
Global Program kickoff. This included distributed application alternatives, system architecture, network,
user interface, translation management and legacy system strategies.
Granular planning takes place in the Global Business Blueprint phase. It is necessary to validate in detail
the decisions made earlier and to define the complete requirements for the global system environment in
order to optimally serve business requirements through integrating business aspects, system topology,
software components and languages. Detailed planning also takes place for development, system
operation and management.
Owner
Technical Team Manager
Deliverable Outputs
Link to
Roadmap
Instance Strategy Validated

Validated System Landscape Strategy
Software and Hardware Standards
Transport Management Strategy
Client Deployment Strategy
Global System Release and Upgrade Strategy
Global ABAP Development Project Plans
Global Security Strategy
2.7.1
2.7.3
2.7.2
2.7.4
2.7.4.1
2.7.5
2.7.6
2.7.7
Link to
Sample
Input for this deliverable comes from Customer Solution Strategy Roadmap, Enterprise IT Strategy (CSS
3.3)
17
Phase
ID #
Title
5.2.8
Template Systems Environment Setup
Description
The Global template system is the SAP system installed at corporate headquarters that contains all global
templates and shared data. It serves as a central source for all configuration and information considered
common, which is to be rolled out to regional, divisional or local systems. Planning for the system
landscape, security, transport management, client deployment, etc was finalized earlier in the Global
Business Blueprint Phase. Early in Phase 2, the template sandbox system is installed. Prior to the
conclusion the Blueprint Phase, the Global template development (DEV) system is set-up and ready for
configuration and development efforts that will take place during the Realization phase.
Owner
Deliverable Outputs
Link to
Roadmap
Technical Requirements
Translation Requirements
Hardware On Order
Approved Technical Design
Installed Hardware/Software
Established Security
Link to
Sample
2.8.2
2.8.3
2.8.4
2.8.5
2.3.1/2.8.6
2.3.1.5/2.8.6.5
Input for this deliverable comes from Customer Solution Strategy Roadmap, Enterprise IT Strategy (CSS
3.3)
18
Phase
ID #
Title
Global Realization
5.2.9
Preparations for Local Project Delivery System
Description
This key deliverable concerns the identification of the technical requirements for the SAP technical
environment needed to deliver the global template solution to the local rollout projects. It consists of
reviewing hardware sizing according to the defined IT Strategy and procurement of the required hardware.
Expected delivery lead-times should be taken into consideration so that hardware is ordered in time and
set up and tested before final rollout preparation activities are starting.
Owner
Deliverable Outputs
Link to
Roadmap
Technical Requirements
Hardware on Order
2.9.1
2.9.2
19
Link to
Sample
Phase
ID #
Title
5.2.10
Description
making process.
recommended.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap

2.11.1
2.11.2
2.11.1
2.11.3
Link to
Sample
20
Phase 3: Global Realization Key Deliverables

The purpose of this phase is to implement business and process requirements based on the
Global Business Blueprint.
1. Template configuration and confirmation
2. Global system management
3. Identify, develop and test development objects
4. Plan and execute the template integration test
5. Rollout preparation
21

6. Install and configure the production system environment
Phase
Customer Competency Center (CCC)

Template Team Training
Realization Phase
ID # Title
Global Realization
5.3.1 Customer
Configured and Confirmed
Template Competence Center
Global System Management Procedures
Description
deliverable
Globalconsists
RICE Development
This key
of setting up the Customer Competence Center Organization (CCC) as
defined
in
the
CCC
Implementation
Plan. Starting from the Implementation Plan and the defined scope of
Template Integration Testing

the CCC, the functions & processes have to be detailed and documented, the roles and responsibilities of
Final Roll-out
the persons
involved
in thesePreparation
functions & processes have to be defined and documented into job
descriptions, the appropriate resources hired (internally or externally) and trained (covering CCC processes
Management
& tools and theQuality/Risk
designed Global
TemplateReview
solution), and the necessary infrastructure for an efficient
operation put in place.
The result is a fully operational CCC. It is important to start early in the Realization Phase with the set-up
of the CCC, so that it is fully operational by end of Realization, ready to take over the maintenance and
enhancement of the global template and the support to the local roll-out teams. In particular, the template
enhancement and release process should be clearly defined and communicated to the local rollout teams.
This covers:
The identification of localization process to consider for global template
The incorporation of local configuration into global template
The schedule coordination for release planning
The split of responsibilities between the CCC and the local roll-out teams during the template roll-out
process should also be clearly defined and communicated in order to ensure a smooth roll-out process.
Owner
CCC Manager
Deliverable Outputs
Link to
Roadmap
CCC Functions and Processes

CCC Roles and Responsibilities
CCC Staffed to Support First Rollout Sites
CCC Infrastructure Needs
3.2.1
3.2.2
3.2.3
3.2.4
Link to
Sample
Key input to this deliverable is the CCC Implementation Plan (1.1.3 in Global Template Roadmap)
established during Global Program Setup as part of key deliverable, Program Plans.
22
Phase
ID #
Title
Global Realization
5.3.2
Template Team Training Realization Phase
Description
The purpose of Template Team Training is to insure that the Template Project team members are
adequately trained in order to implement the system. Training must reflect the scope of the implementation
and the needs of team members. Key members of global rollout implementation teams may be available at
this time and can benefit from this training.
In the Global Realization Phase, Level 3 SAP courses, both functional and technical, are delivered to all
business process owners and team members, as well as technical team members. Level 3 courses
describe each of the business processes in detail, including configuration information. The Level 3
technical courses teach advanced topics of the programming language, concepts, and tools for the area of
focus.
When training is completed, it is necessary to assess the project team mastery of material and their
readiness and capability to proceed.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Training
Training Assessment
3.3.1
3.3.1.5
Input for this deliverable comes from Phase 1, Create Project Team Training Plan, 1.2.6
23
Link to
Sample
Phase
ID #
Title
Global Realization
5.3.3
Configured and Confirmed Template
Description
The purpose of this deliverable is to implement business and process requirements based on the Global
Business Blueprint. The Global Template contains all the configuration settings, documentation, test data,
transports and custom developments that are standard across the enterprise.
The objective is the final implementation of the business requirements into the SAP system(s) and their
validation through detailed test cases and template scenarios. Template scenarios will also be used for
presentation to key decision-makers in order to provide them with the relevant information about Global
Template configuration to obtain final signoff. The formal signoff confirms that the business processes
included in the template configuration are configured appropriately in the SAP system. Template
configuration will be appropriately documented using IMG notes.
Owner
Deliverable Outputs
Link to
Roadmap
Template Configuration Plan

Configured Template (Global and Local Requirements)
Template Transported to QA System
Unit Tested Template
Action Plan for Outstanding Issues
Template Confirmed with Scenarios
3.4.1
3.4.2/3.4.3
3.4.3.3
3.4.3.4
3.4.3.5
3.4.4
Link to
Sample
Main input for this deliverable comes from the key deliverable 2.6 Global Business Requirements.
Requirements have been documented in the Solution Manager The IMG will be used as central tool for the
configuration work and its documentation. Transport Management System (TMS) will be used to transport
customizing settings to the QA environment for testing.
24
Phase
ID #
Title
Global Realization
5.3.4
Global System Management Procedures
Description
Global System Management Procedures deal with service level commitments, system administration
procedures and process and systems integrity. They concern the Global Template System first, but should
also address the entire SAP landscape of the Global Program.
It is essential that service level commitments for the global template development system be put in place
prior to the configuration and development of the SAP System. Hardware and software failure scenarios
should be defined and procedures for recovery described and put into effect.
Responsibilities and procedures for the SAP system administration are defined and documented in the
system operations manual.
Mechanisms are implemented and procedures established concerning the system infrastructure and the
global template solution security. This covers network, database, operating system, access to R/3 systems,
interfaces, configuration changes and access to R/3 business application components and application
data.
Owner
Deliverable Outputs
Link to
Roadmap
Disaster Recovery Procedures

Service Level Commitments
System Administration Functions
Global Security Strategy
3.5.1.2
3.5.1.3
3.5.2
3.5.3
25
Link to
Sample
Phase
ID #
Title
Global Realization
5.3.5
Global RICE Development
Description
The purpose of this deliverable is to complement the standard solution will all necessary additional development
in order to meet business and process requirements based on the Global Business Blueprint. It also addresses
the development for the integration of the implemented solution into the existing legacy systems (interface
programs) and for the migration of existing legacy systems to the implemented solution (conversion programs)
according to the defined legacy system strategy.
The development covers the detailed technical specification based on the functional specification delivered in
the Global Business Blueprint Phase, the realization, testing, approval and the migration to the QA environment
of each identified development object. It is essential for the quality of the integration tests that all development
work is complete, accurate and in place to support final template integration testing.
Owner
Deliverable Outputs
Link to
Roadmap
Developed, Tested and Migrated Global Reports

Developed, Tested and Migrated Global Forms
Developed, Tested and Migrated Global Interface Programs
Developed, Tested and Migrated Global Conversion Programs
Developed, Tested and Migrated Global Enhancements
3.9.1/3.9.2
3.10.1/3.10.2
3.7.1/3.7.2
3.6.1/3.6.2
3.8.1/3.8.2
Link to
Sample
Main input for this deliverable comes from the key deliverable 2.6 Global Business Requirements.
Requirements have been documented through the Solution Manager, and other associated project
documents. Different tools can be used to realize development depending on the type of development:
ABAP, ABAP Query, SAPScript, Report Painter, Report Writer, BW, etc.. TMS will be used to transport
development work to the QA environment for testing.
26
Phase
ID #
Title
Global Realization
5.3.6
Template Integration Testing
Description
Integration testing represents the testing of a chain of transactions that collectively represents a significant
business process or scenario within the customer business environment. Integration testing also involves
output documents, interfaces, procedures, organizational design and security profiles, and primarily
focuses on representative business flows and high-impact business conditions. The purpose of the
integration test is to ensure that the SAP solution fulfills the customers requirements and operates
seamlessly across the various enterprise areas. The testing of the Global Template may include selected
functions that are placeholders in the sense that local choices may provide another solution.
It is key for the quality and success of the integration testing that the template solution is finalized and
sufficiently stabilized through detailed unit and scenario testing prior to integration testing. It has to be
ensured that the test environment is closed for any changes to the delivered template solution and that
transports are restricted to error corrections and are only imported on demand. An efficient issue resolution
process needs to be in place to record testing issues, track their resolution and closure through successful
re-testing. Template integration test results are reviewed and approved indicating that the global template
meets global business requirements and is ready to be delivered to the local roll-out projects.
Owner
Deliverable Outputs
Link to
Roadmap
Template Integration Test Plan

Frozen Template System
Completed Integration Testing
Action Plan for Outstanding Issues
3.11.1
3.11.2.2
3.11.2
3.11.2.4
Link to
Sample
Main input for this deliverable comes from the key deliverable 2.6 Global Business Requirements, 3.2
Configured and Confirmed Template and 3.5 Global RICE Development. Automation of test scenarios can
be realized using CATT. Test planning, issue and progress tracking is supported by the Solution Manager.
27
Phase
ID #
Title
Global Realization
5.3.7
Final Roll-Out Preparation
Description
This key deliverable consists of finalizing the global roll-out plan that will define and help support the
implementation of the global template in the local entities and of putting together a template solution
package ready to be delivered to the local sites. The solution package includes the template configuration,
developments, documentation and the template installation guide. The solution package is tested in order
to confirm its completeness and to validate the delivery process as outlined in the template installation
guide. In addition, a template roll-out training material and instructor guide should help train the local rollout teams on the roll-out approach and their interaction with the template project team.
Owner
Global Roll-out Manager
Deliverable Outputs
Link to
Roadmap
Confirmed Final Roll-out Plan

Template Installation Guide
Established Template Delivery System
Delivered and Tested Global Solution Package
Roll-out Training Materials
Local Training Workshops
3.12.1
3.12.2.4
3.12.2
3.12.3
3.12.4
3.13.1
Link to
Sample
Main input for this deliverable comes from the key deliverables 2.2 Early Roll-out Preparation for the Global
Roll-out Plan, 2.6 Global Business Requirements, 3.2 Configured and Confirmed Template and Global
RICE Development for the content of the Global Solution Package. In order to package the Global
Template customizing settings, BC-Sets can be used.
28
Phase
ID #
Title
Global Realization
5.3.8
Description
making process.
recommended.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap

3.14.1
3.14.2
3.14.1
3.14.3
Link to
Sample
29
Phase 4: Global Maintenance and Support Key Deliverables

The purpose of this phase is to provide global maintenance and support for sites where SAP is in
production while additional versions of the template, and additional rollouts are in development.
1. Provide support to local rollout team during implementation and to local sites after going live.
2. Provide input for new template versions.
3. Continuous improvement.
4. Define long-term plans.
5. Enable the formal program, as defined by the program scope, to be closed.
Correction of the Template Solution
Requirements for Next Template/Version
Continuous Improvement within Program
Updated Business Case and Total Cost of Ownership
30
Future Plans
Phase
ID #
Title
Global Maintenance &

Support
5.4.1
Correction of the Template Solution
Description
Local implementation teams start the realization of the local SAP system by adapting and enhancing the
global template when it is delivered from the global template team. During this process there can be issues,
problems, or change requests that require quick resolution by the Customer Competence Center. This key
deliverable addresses the issue management process between the Customer Competence Center (CCC),
the global support organization, and the local implementation teams.
The impact of the issue on a global scale needs to be investigated and a solution approach decided.
Potentially the correction can impact all local sites using the template version in question. The severity of
the issue will mandate when action must be taken. Technically, the resolution can lead to another
component of a next global support package (adding to/changing the current template version) or to a
component in the next template version. In urgent cases, up-front local repair might be needed which will
later be replaced by the new/revised global solution.
The roll-out project can only make changes to configuration and development objects that are classified as
"local." If changes are required for global objects, the local team must request these changes through the
CCC. This ensures the integrity and consistency of all SAP systems within the scope of the
implementation program.
Owner
CCC Manager
Deliverable Outputs
Link to
Roadmap
Identified and Prioritized Issues

Template Corrections
Communicated and Implemented Changes
4.2.4.1/4.2.4.2
4.2.4.4/4.2.4.5
4.2.4.3/4.2.4.6
4.2.4.7
The usage an issue management tool is highly recommended for an organized template correction
process.
31
Link to
Sample
Phase
ID #
Title

Support
5.4.2
Requirements for Next Template/Version
Description
This key deliverable deals with the preparation, the scheduling and the realization of new versions of the
global template that are in line with the global roll-out plan. Requirements for new template versions can
come from several sources:
Local units which have requests for changes, enhancements, and corrections that are considered
within the defined scope of the global template
New functionality delivered by a new SAP release, which should be used in the new template
version
Locally realized solutions that are relevant for future global template versions which should
therefore be integrated into the global template
These requirements in the form of requests and locally suggested solutions have to be collected, analyzed
and evaluated. The evaluation should consider costs, effort of integration into the existing template and
effort of integration into the local deployment. The relevant changes should be covered by the new
template version. The final result is that the next Template Project is initiated and Phase 1, Global Template
Project Setup, 1.2, begins for the new project.
Owner
Deliverable Outputs
Link to
Roadmap
Identified and Prioritized Improvements

Analyzed and Evaluated Solutions
Next Template Project Initiated
4.3.1
4.3.2
4.3.3
Link to
Sample
The template version upgrade plan has to take into consideration the established global rollout plan as an
output of the key deliverable, Final Rollout Preparation and the overall Implementation Strategy as outlined
in the Program Charter
32
Phase
ID #
Title

Support
5.4.3
Continuous Improvement within Program
Description
The purpose of this key deliverable is to define and implement a process to ensure continuous
improvements regarding the quality of the template solution package, the quality of the template and rollout training and the quality and efficiency of the roll-out process. In addition, the globally designed business
processes need to be reviewed in regards to how local sites have complied with enterprise requirements.
It is key for the long-term success and acceptance of the Program that the feedback, from the local
implementation team after the first local organization has implemented the template solution for productive
use, is captured and turned into concrete improvement measures. Subsequent rollouts will benefit from the
lessons learned by a more streamlined and efficient rollout leading to savings in time and cost for the rollout projects.
Owner
Program Manager, Change Team Lead
Deliverable Outputs
Link to
Roadmap
Identified Improvements in Organization, Methodology, Training, Business

Processes
Proposal and Action Plan for Future Improvements
4.4.1
33
4.4.1
Link to
Sample
Phase
ID #
Title

Support
5.4.4
Updated Business Case and Total Cost of Ownership
Description
The purpose of this key deliverable is to review the business benefits and costs associated with the
implementation achieved to date and to measure local results against the global business case throughout
the entire roll-out phase. This is an iterative process and should be conducted on an ongoing basis.
Periodic results from the local units are collected and measured against the business case target
definitions and the ROI analysis calculation.
Business case target deviations should be documented and analyzed to identify actions to avoid future,
growing deviations. Target, investment, or process design corrections can be necessary and can impact
future rollouts.
Owner
Program Controls Manager
Deliverable Outputs
Link to
Roadmap
Comparison of Actual Business Benefits Projected Benefits

Comparison of Actual Costs to Projected
Revised Business Case & Total Cost of Ownership
4.4.2.1
4.4.2.2
4.4.2.3
Link to
Sample
Main input for this deliverable comes from the key deliverable 1.1 Program Charter and in particular from
the initially established Business Case (3.7.1 Prepare Business Case from the CSS Roadmap).
34
Phase
ID #
Title

Support
5.4.5
Future Plans
Description
This key deliverable addresses business process requirements that were not addressed as part of the
scope of the original implementation program. Changes in business conditions, technologies, products and
company strategy can give rise to new opportunities for continuous improvement. Changes going beyond
initial scope of the program are most likely to occur in multi-year Programs and dynamic business sectors.
A plan has to be established which identifies and defines how and when future process requirements are to
be addressed.
In parallel to the plan for future business requirements, the long-term strategy for service and support,
ensured by the Customer Competence Center, has to be realigned. Staffing of the CCC and system
performance must correspond to the progress of the roll out to local units and the future business
requirements. Long term planning is necessary to provide skilled resources in time. The long-term strategy
for service and support can also lead to outsourcing parts or all service & support functions.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap
Identified Improvements Beyond Scope of Current Program

Long Term Service and Support Strategy
4.5.1
4.5.2
Link to
Sample
Inputs for future plans may be a result of improvements identified in the Continuous Improvement within
Program analysis. Also, changes may arise as consequences of major deviations from initial business
case (Updated Business Case and Total Cost of Ownership). Main input for the long term service and
support strategy is the CCC Implementation Plan established during Global Program Setup as part of key
deliverable Program Plans, and the outcome of key deliverable Customer Competence Center.
35
Phase
ID #
Title

Support
5.4.6
Description
project to begin the next phase which is the next Template Project. The quality of work will be an important
consideration in the decision making process.
recommended.
Owner
Program Manager
Deliverable Outputs
Link to
Roadmap

4.6.1
4.6.2
4.6.1
4.6.3
Link to
Sample
costs determining mitigation plans.
36

ASAP Deliverable Sample

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ASAP Deliverable Sample

Transféré par

Droits d'auteur :

Formats disponibles

Global ASAP Key Deliverables

Global ASAP Key Deliverables

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Phase 2: Global Business Blueprint

5.2.1 OCM Risk Assessment and Mitigation Plans

Phase 3: Global Realization

5.3.1 Customer Competence Center

Phase 4: Global Maintenance and Support

5.4.1Correction of the Template Solution

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Purpose of This Document

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Program Procedures, Standards and Tools

Template Project Setup

Quality/Risk Management Review

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Global Program Setup

Program Scope/Optimum Solution Set

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Global Program Setup

Program Manager(s) and Program Management Office (PMO)

Regional Program Manager (Optional)

Global Support/Account Manager(s)

Program Controls Manager(s)

Business Process Managers

Template Project Manager(s)

Global Rollout Manager

Technical Team Manager(s)

Change Management Team Leader(s)

Named Program Sponsor and Steering Committee

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Global Program Setup

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Global Program Setup

Template Project Setup

Template Project Manager

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Global Program Setup

Program progress compared to plan; milestone achievement

Deliverables quality, and conformance to the documented approval process

Internal Management Review

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

Phase 2: Global Business Blueprint Key Deliverables

Copyright 2000 SAP AG. All rights reserved

Global ASAP Key Deliverables

OCM Risk Assessment and Mitigation Plans

Early Roll Out Preparation

Organizational Change Management is the systematic management of changes to an organization caused

Global Business Requirements

Global Systems Environment

Preparations for Local Project Delivery System

Identifies potential risks

Creates plans for their minimization

Creates plans for their optimization

Executes those plans