ASAP Methodology in Implementing ERP

22
SAP Implementation Methodology

description

 

Transcript of ASAP Methodology in Implementing ERP

Page 1: ASAP Methodology in Implementing ERP

SAP Implementation Methodology

Page 2: ASAP Methodology in Implementing ERP

Page 2

Business Benefits of ERP

Improve alignment of strategies and operations

Standardize the business processes in the organization.

Achieve better efficiency of operation.

Adopt best practices, processes and systems

Set up and Implement an integrated and up to date IT SAP system

Rationalize multiple non-integrated systems into one common solution

Replace a high percentage of manual tasks with an automated solution through SAP

Provide immediate access to enterprise information

Page 3: ASAP Methodology in Implementing ERP

Page 3

Projects from another perspective

“An estimated 68% of corporate IT projects are neither on time nor budget, and they don’t deliver the originally stated business goals. Some even claim that during the last two years, $100 billion to $150 billion of U.S. IT projects have failed altogether.”

Mark Jeffery and Ingmar Leliveld: Best Practices in IT Portfolio Management, MITSloan Management Review, Spring 2004

Page 4: ASAP Methodology in Implementing ERP

Page 4

Ingredients of Success

Adequate budget including training, documentation and conversion.

Alignment with Business Goals: The strategic objectives of the program should be in

alignment with organization’s business goals.

Clear and concise Deliverables

End-User Involvement People need to be involved from beginning to end.

Top-down control without bottom-up involvement is a recipe for disaster.

Adequate Training: Training is not an expense; it is investment in human

resource.

Change Management: When changes are prepared for and introduced

gradually, it does not make people insecure and resentful; it turns them into advocates

Page 5: ASAP Methodology in Implementing ERP

Page 5

Typical questions when you starting the project

How to best use selectedsolution capabilities?

Do we have internal capabilities

and capacity tostaff the project?

How and where do we start?

Who does whatin this project?

How expensive will this project be? How

do we keep the costs low?

How to manageproject and business

risks involved?

How do we assure success?

How to buildinternal

expertise?

Page 6: ASAP Methodology in Implementing ERP

Page 6

Delivering Successful Solutions

AcceleratedSAP Methodology

Description

Accelerated SAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3.

Accelerated SAP contains a multitude of tools, accelerators and useful information to assist all team members in implementing R/3. Quality checks are incorporated at the end of each phase to easily monitor deliverables and critical success factors.

Page 7: ASAP Methodology in Implementing ERP

Page 7

Phase 1 : Project Preparation

Goal Setting Define project goals & objectives

Implementation strategy 1.Clarify the scope of implementation 2.Establish the project organization and relevant committees and assign

resources

Implementation Sequence Define sequence in project has to be

executed

Team Core team+ project team+

consultant team

Sign Off At the end of phase every above steps will be documented & will be signed off

with the client

During this phase the team goes through initial planning and preparation for SAP project.

Page 8: ASAP Methodology in Implementing ERP

Page 8

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 in Phase 1 help you to identify and plan the primary focus areas that need to be considered.

Page 9: ASAP Methodology in Implementing ERP

Page 9

Phase 2 : Business Blueprint

SCOPE DOCUMENTThis document will consists of

questionnaire of entire business

process

AS IS 1.Understanding the business Process

from the core team. 2.Based on the input ASIS document has to be created

according to module wise

TO BE 1.In this process will map the business

process in SAP based on ASIS 2.Module wise TOBE document has to

be created

GAP ANALYSIS 1.The GAP b/w ASIS process & TOBE process

is called GAP analysis ie., The inputs or the business process which can’t mapped into

standard SAP will be analyzed here 2.GAP document has to be created

SIGN OFF Each process above has to be

taken sign off from client

The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops.

Page 10: ASAP Methodology in Implementing ERP

Page 10

Business Blueprint

The purpose of this phase is to create the Business Blueprint, which is detailed documentation 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 business within the SAP System

Page 11: ASAP Methodology in Implementing ERP

Page 11

Phase 3 : Realization

BaselineMajor scope

Final ConfigurationRemaining scope

SIGN OFF Each process above has to be

taken sign off from client

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

Page 12: ASAP Methodology in Implementing ERP

Page 12

Realization

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

Page 13: ASAP Methodology in Implementing ERP

Page 13

Phase 4 : Final Preparation

Unit Testing Testing within each module

Integration TestingIntegrate testing of modules ie.,

combine testing of all the modules

User Training

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

Cut over Strategy legacy system will be migrated to

SAP system.

SIGN OFF Each process above has to be

taken sign off from client

Page 14: ASAP Methodology in Implementing ERP

Page 14

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 successful completion of this phase, you are ready to run your business in your live SAP System.

Page 15: ASAP Methodology in Implementing ERP

Page 15

Phase 5 : Go Live & Support

Production Support

Monitor System Transactions

Optimize Performance

The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

Help Desk & Competency Center

Page 16: ASAP Methodology in Implementing ERP

Page 16

Go Live and Support

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

Page 17: ASAP Methodology in Implementing ERP

Page 17

NEW GlobalASAP Local Rollout RoadmapFinalPreparation

Project Preparation Business Blueprint

Realization

Project Mgt OCM + Training System PrepProcesses Data Cutover

Setup of Local ProjectOrganization

Adaption of Strategic Framework

Establish OCM Procedures + Responsibles

Infrastructure Requirementsand Design

Early Adoption of BestBusiness Practice Proceesses

Training andDocumentation Strategy

Data ManagementStandards Implementation

Data Cleansingand Data Preparation

Completion Check & Prepare for Next Phase

General Project Management

Local Business BlueprintDocumentation

Security Requirements

Infrastructure Planning

System Operation Stategy

Early Adoption of BestBusiness Practice Processes

Training Planning

Data Cleansingand Data Preparation

Completion Check & Prepare for Next Phase

OCM OrganizationalAlignment + Change Analysis

General Project Management

OCM

Training Preparation

Configuration &Development

Unit / Process / Integration / Business Acceptance Testing

Early Adoption of BestBusiness Practice Processes

Infrastructure Implementation

Data Preparation & Data Migration Simulation

Completion Check & Prepare for Next Phase

Cutover Planning & Preparation

Business TransitionPlanning for Cutover

General Project Management

OCM

End User Training

End User Practice in the System

Data Migration to Production

Infrastructure Finalization

Cutover Management

Business Simulation

Pre-Go-Live Operations

Completion Check & Prepare for Next Phase

Final Cutover andControlled Process GoLive

GoLive and Support

General Project Management

OCM

Project Closing

System Support

Business Support

Page 18: ASAP Methodology in Implementing ERP

Page 18

Project Management expertiseManagement 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 business requirements to SAP solutions

SAP Solution Composer

Offers AcceleratedSAP roadmap composed to fit specific project needs

SAP Roadmaps

Facilitates efficient solution design, documentation, configuration, testing and operations

SAP Solution Manager

AcceleratedSAP toolset

Page 19: ASAP Methodology in Implementing ERP

Page 19

Roadmap Adds Value to the Implementation

What to do, and when to

do it

Who participates

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

Knowledge Area

Why and how you should do it

Accelerators,Samples, Templates

Page 20: ASAP Methodology in Implementing ERP

Page 20

Implementation Roadmap - Structure

PhaseDeliverable Group 1

DeliverableO: Output α.1

O: Output α.2

M: Activity 1.1

Task 1.1.1

Task 1.1.2M: Activity 1.2

Task 1.2.1

Deliverable Group 2 Milestone A

Deliverable consists of several

outputs

Methods (activities and tasks) that

create or contribute to creation of the

deliverable

Page 21: ASAP Methodology in Implementing ERP

Page 21

Hope we will not end up like this

Page 22: ASAP Methodology in Implementing ERP

Page 22

THANK YOU