asap roadmap overview

5/12/2018 ASAP Roadmap Overview - slidepdf.com

http://slidepdf.com/reader/full/asap-roadmap-overview 1/42

ASAP ImplementationRoadmap



Methodology ± why? ASAP Overview

ASAP Roadmap Structure

ASAP Content OverviewHow to access Roadmap

Project Management in ASAP



¥ SAP America 2004, PM Methodology Web Session

Projects from another perspective

³An estimated 68% of corporate IT projects areneither on time nor budget, and they don¶tdeliver the originally stated business goals.Some even claim that during the last twoyears, $100 billion to $150 billion of U.S. ITprojects have failed altogether.´

Mark Jeffery and Ingmar Leliveld: Best Practices in IT Portfolio Management,

MITSloan Management Review, Spring 2004




Typical questions when you starting the project

How to best use selectedsolution capabilities?

Do we have internalcapabilities

and capacity tostaff the project?

How and where

do we start?

Who does whatin this project?

How expensive willthis project be? How

do we keep the costs low?

How to manageproject and business

risks involved?

How do we assuresuccess?

How to buildinternalexpertise?




Industr y Best Practices to mitigate project failure risk

TOP 10 MOST UTILIZED PRACTICES in IT projects

1. Regularly use project management methodologies: 96%

2. Conduct regular strategic planning meetings to achieve alignment: 93%

3. Conduct internal customer satisfaction surveys: 86%

4. Create and use performance metrics: 81%

5. Regularly use portfolio management or other project prioritization methodology: 80%

6. Perform financial audits: 79%

7. Use leadership development programs: 79%

8. Make the CIO a member of the corporate board or executive committee: 76%

9. Employ internal relationship managers/account executives to work with the business: 75%

10. Conduct post-implementation audits: 74%

(Percentages refer to number of respondents using this practice.)

Source: Richard Pastore and Lorraine Cosgrove Ware: The Best Practices, CIO Magazine May 2004




Delivering Successful Solutions

AcceleratedSAP Methodology

Description

http://service.sap.com/asap

AcceleratedSAP methodology is proven, repeatable and successfulapproach to implement SAP solutions across industries andcustomer environments.

AcceleratedSAP provides content, tools and expertise fromthousands of successful implementations.

More info




Project Management expertise

Management of the implementation project

Aligned with industry standards and procedures (PMI PMBOK ® )

Specific to implementation of SAP solutions

Key components for success

AcceleratedSAP - proven methodology

Aligns customer¶s businessrequirements to SAPsolutions

SAP Solution Composer

Offers AcceleratedSAProadmap composed to fitspecific project needs

SAP Roadmaps

Facilitates efficient solutiondesign, documentation,configuration, testing andoperations

SAP Solution Manager

AcceleratedSAP toolset




Key components for success

AcceleratedSAP - proven methodology

N e w T o o l s e t

Facilitates efficient solutiondesign, configuration, testingand operation

Delivered offline in SAP ServiceMarketplace and in SAP SolutionManager

V a l u e S A P T o o l s e t

Aligns customer¶s businessrequirements to SAP solutions

SAP Solution Composer SAP Roadmaps SAP Solution Manager

AcceleratedSAP methodology

Provides proven, comprehensive, repeatable and rich implementationmethodology to streamline projects

PMI aligned framework with templates and tools for performing effectiveproject management

SAP Solution Map

Composer

Implementation

Assistant

Q&Adb, BPML, Diagram

Explorer

Evolved to Evolved to Replaced by




Methodology

PeopleandExpertise

Content

andTools

ConsultingServices

SAP Consulting

Where Methodology fits

Achieve your

implementation

goals through

leveraging SAP

experts, services,

methodology,content and tools.




Content: AcceleratedSAP RoadmapsGuidance and navigation for your implementation team

Definition

Benefits

More info

ASAP roadmaps outline the activities involved in

implementing, upgrading, or enhancing SAP solutionsenriched with set of deliverables, accelerators, roledescriptions and additional guides

Transparent, proven approach helping the project team to really work as a team and to reduceimplementation time, costs and risks

Achieve better results since you base your project on the experiences others made before. Both hard factsas well as soft skills are addressed

Knowledge management - use the Implementation Roadmap for SAP solutions to gather knowledge on howto organize and run your implementation projects

http://service.sap.com/roadmaps

Usage

Provide content (work packages, activities, tasks,deliverables, accelerators) that can be used during theentire project lifecycle.

Target GroupCustomers, Partners, SAP Consulting

AvailabilityThe roadmaps are made available through: SAP SolutionManager and SAP Service Marketplace




AcceleratedSAP Implementation Methodology

Phase 1: Project PreparationDuring this phase the team goes through initial planning and preparation for SAP

project.

Phase 2: Business BlueprintThe purpose of this phase is to achieve a common understanding of how thecompany intends to run SAP to support their business. The result is the BusinessBlueprint, a detailed documentation of the results gathered during requirementsworkshops.

Phase 3: Realization

The purpose of this phase is to implement all the business process requirementsbased on the Business Blueprint. The system configuration methodology is provided intwo work packages: Baseline (major scope); and Final configuration (remaining scope).

Phase 4: Final PreparationThe purpose of this phase is to complete the final preparation (including testing, enduser training, system management and cutover activities) to finalize your readiness to golive. The Final Preparation phase also serves to resolve all critical open issues. Onsuccessful completion of this phase, you are ready to run your business in your live SAPSystem.

Phase 5: Go Live & SupportThe purpose of this phase is to move from a project-oriented, pre-productionenvironment to live production operation.




SAP Standard Roadmaps (1/2)

ImplementationRoadmap for SAP Solutions provides themethodological framework for the project team to leverage in theimplementation of a SAP solution. It covers, among other things, thenecessary project management, requirements gathering, design,configuration of business processes, technical implementation, testprocedures, training and organization change management.

In this roadmap deliverables represent the main objects within aproject. Each deliverable then provides outline of the Outputs

(components creating the deliverable) and relevant Methods thatrepresent the activities and tasks the project team conducts

Implementation

DescriptionRoadmap Type

The Global Template Roadmap describes how to organize and howto run a project in which a corporate template is developed. TheGlobal Template Roadmap is geared to more compleximplementation or harmonization projects, typically involving more

than one kind of SAP solution, and a variety of sites, possibly indifferent countries. The corporate template is rolled out to other sitesin a follow-up project.

Global Template




SAP Standard Roadmaps (2/2)

This roadmap is designed to help you carry out the customizingactivities required for an upgrade. These customizing activities areessential if you want to continue to use the same functions in your business application components after an upgrade.

Upgrade

DescriptionRoadmap Type

The Solution Management Roadmap provides a methodology for theimplementation of the technical infrastructure and its operation. TheSolution Management Roadmap complements the Implementation

Roadmap.

Solution Management




Roadmaps Add Value to the Implementation

What to do,and when to

do it

Why you should do itand how to do it

Accelerators

Who does it

When used properly, a roadmap will provide guidance on the following:




Enforcing standards

M ethodology alone will not make your project

successful. You need to enforce it ± appoint methodology champion for the project.





ASAP Content Overview

How to access Roadmap





Source: Implementation Roadmap ² Activity based (ABR)

Each work package comprises severalactivities. Activities contain the tasksthat project team members need to carryout, in order to fulfill the project goals. Atthis level, you can find more acceleratorscontaining information relevant for your implementation project.

Activity(Level 3)

Each ASAP Roadmap phase is made up

of several work packages with topics.

The work packages are designed to

realize the main objectives of eachRoadmap phase. Work packages are

made up of activities and tasks.

Work Package(Level 2)

Each Roadmap is divided into several

large phases, each of which represents

a major milestone in the project plan.

Phase(Level 1)

DescriptionStructure

Each activity is made up of severaltasks. The task describes the stepsProject team members are required toperform the tasks.

Task(Level 4)

Level 1

Level 2

Level 3

Level 4




Source: Implementation Roadmap ² Deliverable based (DBR)

Each d eliverables comprises severaloutputs. Outputs are document or tangible items that are results of aprocess. The output supports thecompletion of a desired d eliverable as astandalone component.

Output(Level 3)

Each phase is made up of several

deliverables with topics. The

d eliverables represent the main objectswithin a project. A d eliverables are further

comprised of outputs.

Deliverable(Level 2)

Each Roadmap is divided into several

large phases, each of which represents

a major milestone in the project plan.

Phase(Level 1)

Level 1

Level 2

Level 3

DescriptionStructure

T he Deliverable-based Roadmap will also have a µreferences¶

tab to provide a link to the activities & tasks (method)

associated with creating the deliverable.




Improved Implementation Roadmap

Activity based Impl. Roadmap

Deliverable Based Impl. Roadmap

Implementation Roadmap




Implementation Roadmap - Structure

PhaseDeliverable Group 1

Deliverable

O: Output .1O: Output .2

M: Activity 1.1Task 1.1.1

Task 1.1.2

M: Activity 1.2

Task 1.2.1

Deliverable Group 2Milestone A

Deliverable consists

of several outputs

Methods (activities

and tasks) that

create or contribute

to creation of the

deliverable




Easy navigation in the roadmap

Attributes used to classify roadmap nodes and accelerators to enable easynavigation and user specific views.

Following attributes are used Flavors ± represents SAP Solutions (mySAP ERP, mySAP CRM, «.)

Subject Areas ± knowledge domains in the implementation project (Project Management,Org. Change Management, Technical Implementation, «)

Project Roles ± filter activities, tasks or outputs

Showing only relevant areas of the roadmap (by user preference) Activity based view

Deliverable based view




ReferencesRelationship between Outputs and relevant Activities or Tasks

PhaseDeliverable Group 1Deliverable

O: Output .1O: Output .2


Task 1.1.2

M: Activity 1.2

Task 1.2.1


References point from Tasks or Activities

(where tasks are not available) to the relevant

Outputs that are being produced (or contributed to) by the performed task or

activity.




Deliverable: Methods and Outputs relationship




Project Roles and Subject Areas


O: Output .1

O: Output .2


Task 1.1.2

M: Activity 1.2

Deliverable Group 2

Milestone A

Subject Area ±

deliverable is part

of a discipline,

domain or subject

area in the project

AttributeStructure

Project Roles

- project role isinvolved or performs

the activity producing

an Output

ProjectRoles assigned to

Outputs and Tasks (or

Activity where tasks not

available)




Roadmap Flavor ² Solution Relevant Nodes


O: Output .1

O: Output .2


Task 1.1.2

M: Activity 1.2

Task 1.2.1


Flavor ± assigned

to all nodes

applicable for given

solution (flavor)

AttributeStructure

Flavor assigned to eachindividual node with exception

of Outputs and Methods node

(gray nodes)




PM Processes happen throughout the project

Each phase has Phase Start, Deliverable Creation/Acceptance

and Closure tasks




AcceleratedSAP and PM process alignmentPM deliverables are mapped to ASAP phases

Description

More info


ProjectProject

ManagementManagement

MethodologyMethodology

ASAP Alignment PrinciplesInitiating and Planning deliverables inProject Prep and Business Blueprint

Requirements Planning, which is replacedby Blueprint

Executing/Controlling deliverables inRealization, Final Prep and partly in Go

Live and Support

Final Customer Acceptance occurs inGo Live & Support

Discovery/EvaluationInitiating

Project

Preparation

Planning

Executing/

Controlling

Closing

Business

Blueprint

Realization

Final

Preparation

Go Live

& Support

Project Charter

Project Plan

Management Plans

Requirements Planning

Final Customer Acceptance

Project Closeout Report

Lessons Learned

ASAPASAP

ImplementationImplementation

RoadmapRoadmap

Closing happens in Go Live & Support




ASAP Structure

The individual phases of the ASAP Implementation Roadmap are:

1. Project Preparation - project formally initiated and planning well under

way.

2. Business Blueprint - project team gathers requirements and conducts

conceptual design of the solution.

3. Realization - system solution built and integration tested, end users

trained

4. Final Preparation - authorization to cut over to new system solution

5. Go Live and Support - solution confirmation and project closure

Each phase has a set of deliverables that are produced duringthe duration of the phase and serve as the input to follow-upphases. Each deliverable provides list of Outputs it consist of and Methods that are used to produce the deliverable.




Project Preparation

The purpose of this phase is to provide initial planning and preparation for your SAP project.Although each SAP project has its own unique objectives, scope, and priorities; the steps inPhase 1 help you to identify and plan the primary focus areas that need to be considered.




Business Blueprint

The purpose of this phase is to create the Business Blueprint, which is detaileddocumentation of the results gathered during requirements workshops. Furthermore,the Business Blueprint documents the business process requirements of the company.With this, you can better understand how the company intends to run its businesswithin the SAP System




Realization

The purpose of this phase is to implement business and process requirements based onthe Business Blueprint. The objectives are final implementation in the system, an overalltest, and the release of the system for production (live) operation. In addition, the projectteam receives relevant knowledge.




Final Preparation

The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cut-over activities), to finalize your readiness to go live.The Final Preparation phase also serves to resolve all crucial open issues. On successfulcompletion of this phase, you are ready to run your business in your live SAP System.




Go Live and Support

The purpose of this phase is to cut over to live productive operationand to continuously support and improve live operations




SAP Roadmaps ² Today

Delivery mechanism

Solution Management

Implementation

Global Template

Upgrade

Implementation

Deliverables Based ± implementation roadmap oriented to deliverables that the project team needs to prepare in order to implement the solution

Legend:

Activity/Task Based ± roadmap presented as sequence of activities that the project team performs to implement the solution

Primary toolset for ASAP

roadmap delivery tocustomers and partners

Primary toolset for

customers and partners

without access to SAP

Solution Manager system




SAP Roadmaps ² September 2004

Delivery mechanism

Solution Management

Implementation

Global Template

Upgrade

Deliverables Based ± implementation roadmap oriented to deliverables that the project team needs to prepare in order to implement the solution

Legend:

Activity/Task Based ± roadmap presented as sequence of activities that the project team performs to implement the solution

Primary toolset for ASAP

roadmap delivery tocustomers and partners

Primary toolset for

customers and partners

without access to SAP

Solution Manager system




How SAP delivers ASAP Roadmaps

AcceleratedSAP Roadmaps delivered

via SAP Service Marketplace andSAP Solution Manager (Improved

Implementation Roadmap delivered

in Solution Manager 3.2 and higher).




Roadmap Resources & Support

Central location for all Roadmap questions and material


Support

Should you experience any issues with the roadmap please report theissue via SAP Support in component SV-ASA

Discussion forums

Post your questions on the Roadmap pages in Service Marketplace




No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarksor registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting an additional warranty.

© Copyright 2004 SAP AG. All Rights Reserved



¥ SAP America 2004 PM Methodology Web Session

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne dieausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige

Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation.

IBM,DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS,

AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern.

Oracle ist eine eingetragene Marke der Oracle Corporation.

UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems,

Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of

Technology.

Java ist eine eingetragene Marke von Sun Microsystems, Inc.

JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten

Technologie.

MaxDB ist eine Marke von MySQL AB, Schweden.

SAP,R

/3, mySAP, mySAP.com, xApps, xApp und weitere im Text erwähnte SAP-Produkte und-Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der

SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligenFirmen.Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede

aufweisen.

In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die vorliegenden Angaben werden von SAP AGund ihren Konzernunternehmen (ÄSAP-Konzern³) bereitgestellt und dienen ausschließlich Informationszwecken.Der SAP-Konzern übernimmt

keinerlei Haftung oder Garantie für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und

Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Aus

den in dieser Publikation enthaltenen Informationen ergibt sich keine weiterführende Haftung.

© Copyright 2004 SAP AG. Alle Rechte vorbehalten

asap roadmap overview

Documents

tools sap america

operations sap america

comroadmaps sap america

project team

leveraging sap experts

methodology fits

implementation projects

implementation time