QSandS NTUA SAP Methodology

25
Quality Systems & Software SAP Methodology

Transcript of QSandS NTUA SAP Methodology

Page 1: QSandS NTUA SAP Methodology

Quality Systems & Software

SAP Methodology

Page 2: QSandS NTUA SAP Methodology

2QS&S

SAP Upgrade Methodology

The use of structured methodologies have been around for decades. Today, there are dozens, if not hundreds, of methodologies available for use.

In SAP world, you have the most popular ASAP (Accelerated SAP) methodology. Based on the experience of multiple successful implementations, ASAP methodology is developed to ensure the successful, on-time SAP implementation.

Many consulting firms claim to have their own Implementation Methodologies - but, most are simply the variations of ASAP Methodologies.

We at QS&S adhere to ASAP Methodology. What makes QS&S different is that we have built many 'Accelerators' embedded within the methodology to jump-start the implementation, significantly reducing the implementation complexities and time. 'Accelerators' are pre-designed configuration objects or techniques, which are required for majority of implementations

Methodology

There are various structured methodologies to implement SAP

We follow ASAP Methodology – enhanced with our ‘Accelerators’!

Page 3: QSandS NTUA SAP Methodology

3QS&S

SAP Upgrade Methodology

Accelerated SAP (ASAP) methodology utilized by QS&S is one developed originally by SAP for its customers. The key features of this methodology is that it is designed for rapid implementations with active participation by client team members.

The methodology is composed of distinct phases which have a specific focus in the overall implementation. These include:

• Project Preparation

• Blueprint

• Realization

• Prepare for Production

• Post Go-live Support

Methodology

We follow ASAP implementation methodology

Page 4: QSandS NTUA SAP Methodology

4QS&S

Developed by SAP specifically for SAP implementation

Available to SAP customers as part of license fee

Tight integration with Solution Manager

Designed for active participation by client team members

Large number of accelerators provided by SAP

• Pre-designed configuration objects or techniques, which are required for the majority of implementations.

• QS&S has developed its own accelerators to jump-start the implementation, significantly reducing the implementation complexities and time.

Upgrade MethodologyMethodology

Why We Chose ASAP

Page 5: QSandS NTUA SAP Methodology

5QS&S

SAP implementation accelerators

Pre-configured modules and sub-routines

Topical optimizers

Productivity improvement frameworks

Solution architecture templates

SAP best practice library

QS&S Approach – Proprietary Toolkit

We have a developed extensive proprietary library of accelerators, methods and routines to save customer cost and time

We believe that our proprietary toolkit could provide significant overall cost & time savings.

Page 6: QSandS NTUA SAP Methodology

6QS&S

Rapid SAP Upgrade Approach

• Upgrade project pre-planningAddress technical and environment requirementsConduct the assessment processIdentify any high-level business process improvementsAssess short-term and long-term directions Environment requirements and necessary hardware &

softwareHigh-level scope and planCompleted upgrade assessment documentImpact on people, their jobs, roles, and responsibilities

Page 7: QSandS NTUA SAP Methodology

7QS&S

Rapid SAP Upgrade Approach (cont.)

• Project preparationDefine the upgrade scope and project planEstablish the project organization and standardsDefine new roles and responsibilities for all team membersPerform technical and security requirements planningAnalyze the present environment contentsPerform the necessary upgrade preparationsDecide on tools, templates, and documentation standards for the project

Page 8: QSandS NTUA SAP Methodology

8QS&S

Rapid SAP Upgrade Approach (cont.)

• Business blueprintInventory a list of interfaces, reports, data conversions, and third-party toolsInventory a list of security profiles and activity groupsRevisit business processes and determine which processes are within the scope of the projectReview new functionality and document new functionality impactsLocate all test scripts and update as neededIdentify all new, changed, and deleted transactions as a result of new release functionalityFinalize the upgrade project scope

Page 9: QSandS NTUA SAP Methodology

9QS&S

Rapid SAP Upgrade Approach (cont.)

• Realization of DEV and QAUpgrade the DEV and QA environmentsPerform configuration and technical changesConduct functional and technical integration testsDelta training preparation and deliveryGUI rollout/desktop deploymentImplement security strategyPrepare production supportCreate end-user documentation and training materials

Page 10: QSandS NTUA SAP Methodology

10QS&S

Rapid SAP Upgrade Approach (cont.)

• Realization of productionFinalize documentation and trainingRevise/create documentation and training materialsPerform end-user training focused on “change areas”Conduct stress testsApply hot packages, OSS notes, and configuration changesCommunicate the plan to end usersExecute the production cutover plan

Page 11: QSandS NTUA SAP Methodology

11QS&S

Rapid SAP Upgrade Approach (cont.)

• Go-live and supportUpgrade the production systemMaintain a support organization for the short and long termCreate policies and procedures for handling support callsManage the roles and responsibilities of your support teamEducate end users on the support processObtain written signoff for the productive system

Page 12: QSandS NTUA SAP Methodology

12QS&S

Plan Build Test Support

Continuous Improvement

Upgrade Methodology

Project Prep Blue Print Go-Live Post Go-live

Preparing Organizationfor Change

ContinuousImprovement

Methodology

Realization

Finalizing Business Processes

TestingNew System

Implement

Rapid SAP Upgrade - Project Stages

Page 13: QSandS NTUA SAP Methodology

13QS&S

ASAP Methodology

Project Preparation

• The purpose of this phase is to provide initial planning and preparation for your SAP System project. Although each project has unique objectives, scope and priorities, the steps in this Phase help you to identify and plan the primary topics that need to be considered. As you prepare for your SAP System, you must address several important issues at the beginning of the project.

• These include:– SAP Hardware Environments/Installation– Team finalization– Project Planning– Project Kickoff meeting

Methodology

Page 14: QSandS NTUA SAP Methodology

14QS&S

ASAP MethodologyProject Preparation

• Review Project Enterprise Charter

• Draft Project Team Organization

• Develop detailed project plan

• Develop Risk Management plan

• Develop Issue Management plan

• Develop Training strategy

• Define project strategies

• Define Data Conversion Strategies

• Define Reporting / Data warehouse strategy

• Roll-out Strategy

• Technical Architecture Strategy

• SAP Competency Strategy

Major Activities

• Project Charter – Mission Statement, Business Case, Business Drivers

• Organizational Project Team Structure

• Project Plan

• Project team training schedule

• Project Risks / Critical Success Factors Assessment

• Risk Management Plan

• Technical Infrastructure Organization

• Implementation Standards and procedures

Key Deliverables

Methodology

Page 15: QSandS NTUA SAP Methodology

15QS&S

ASAP Methodology

Blueprint Phase

• This phase will be one of the most important phases. We settle on our strategy on how to build our new home! We finalize so-called blue-print. The next phase will be an execution phase.

• During this phase, the core business processes will be reviewed and refined and outline process flow will be configured within the SAP system. The goal is by the end of the blueprinting phase to have defined the business scenarios necessary and to have the main business flows configured within SAP for an end of blueprint walkthrough.

• QS&S will conduct workshops to address design of the SAP system hierarchy and other fundamental system elements that are core to the system operation and integration.

• We will seek validation and sign-off from the key users to ensure that the documented requirements reflect what is to be configured in the SAP system.

• The key deliverable in this phase is the business blueprint which represents a definition of the core processes in scope for the implementation and initial validation of the SAP core processes which will act as the base for the subsequent addition of more complexity.

• Key Deliverable - At the end of Business Blueprint phase, we would have a deliverable –“Blueprint document”. This document will act as a “basis” for all further activities in the project.

Methodology

Page 16: QSandS NTUA SAP Methodology

16QS&S

ASAP MethodologyBlueprint

Methodology

• Set up and install SAP Sandbox environment

• Conduct Team SAP training

• Develop SAP Organization structure

• Define Global parameters

• Process requirements

• Perform process and functional gap analysis and resolution

• Define enterprise standards process

• Define IT/Development requirements

Major Activities

• Business Process Master List (BPML) – baseline

• IT development Scope / Requirements

• Global Reports

• Standard Interfaces List

• Standard Conversions List

• Enhancements list

• Preliminary Sandbox configuration for early prototyping

• Global Organization Structure

• Realization Plan

Key Deliverables

Page 17: QSandS NTUA SAP Methodology

17QS&S

ASAP Methodology

Realization Phase• During the Realization phase, project teams will focus on configuring the SAP functionality. Specific

tasks include:– Configuring the SAP system (i.e., transactions, tables, screens, reports) to meet the business

requirements developed during the preparation and blueprinting phases– Developing interface, reporting, and enhancement programs where necessary– Documenting configuration decisions as the basis for end-user training and on-going system support – Developing strategies and plans to accomplish system testing and end-user training– Identifying and establishing data standards

• The entire QS&S implementation team and key users will be involved in regular periodic reviews to ensure that configuration decisions meet the business expectations.

• After the initial configuration, the project team will focus on fine-tuning and testing the configuration to ensure that it meets defined requirements. Specific tasks include:– Conducting a demonstration of the configured system for management and key users– Fine-tuning the configuration based on user feedback– Completing and testing the configuration– Developing and testing interface, data conversion, reporting, and enhancement programs– Developing end-user training and documentation

• Key Deliverable - At the end of Realization phase, we would have an SAP system ready and tested by development team and business users. The deliverable will be “User Acceptance Decision”.

Methodology

Page 18: QSandS NTUA SAP Methodology

18QS&S

ASAP MethodologyRealization

Methodology

• Baseline configuration – Process prototyping and configuration, Global configuration,

• Detail definition of development

• Conversions and Interfaces Planning and design

• Conduct systems test

• Prepare and conduct end-user training

• Develop training plans

• Security authorizations

• Develop Implementation plan

Major Activities

• Configure TO-BE System

• Integration Test plan

• Systems Test Plan

• Implementation strategy – site readiness assessment

• Testing Methodology

• Process Procedures

• Training Materials

• Knowledge Transfer Assessment

Key Deliverables

Page 19: QSandS NTUA SAP Methodology

19QS&S

ASAP Methodology

Preparation for Production

• During the final phase of the project and before going live, the project teams will focus on moving the system into production and preparing the organization to "go live".

Methodology

Page 20: QSandS NTUA SAP Methodology

20QS&S

ASAP MethodologyPreparation for Production

Methodology

• Validate Business Process lists

• Prepare cut-over plan

• Conduct Post-implementation project review

Major Activities

• Cut-over plan

• Go/No-Go decision

• Risk Assessment and Mitigation Plans

Key Deliverables

Page 21: QSandS NTUA SAP Methodology

21QS&S

ASAP Methodology

Post Go-live Support

• As one of my clients compared this phase as - “The baby is handed over to the parents for continuous care and nurture!”

• After the system goes live the project team consultants will remain to assist with any post implementation support issues, further design refinements and roll-out support.

• Our goal is to position company to be self-sufficient.

• Configuration workshops will be conducted to ensure configuration knowledge transfer occurs.

Methodology

Page 22: QSandS NTUA SAP Methodology

22QS&S

ASAP MethodologyPost Go-live Support

Methodology

• Production Support (Help Desk)

• Validate Live Business process lists

• Optimize System Tuning

• Daily Operations Support and Administration

• Execute Archiving Strategy

• Conduct Post Implementation Project Review

• Review Benefits Measurement (compare against approved business case)

Major Activities

• SAP Competency Center Support Structure

• Benefits Realization Analysis

• Post Implementation Project Review

Key Deliverables

Page 23: QSandS NTUA SAP Methodology

23QS&S

This document is exclusively intended for Internal Use only.

This document contains information that is proprietary and confidential to Quality Systems & Software (QS&S). Distribution,

quotations and duplications – even in the form of extracts – for third parties is only permitted upon prior written consent of QS&S.

Any other company and product names mentioned are used for identification purposes only, and may be trademarks of their

respective owners.

Disclaimer

Page 24: QSandS NTUA SAP Methodology

24QS&S

“Your Partner in Business & Technology Excellence”

Page 25: QSandS NTUA SAP Methodology

25QS&S

Please feel free to contact us for more information or clarifications.

Thank You.

QuestionsMitresh KundaliaDirector - SAP Practice

W QSandS.com

E [email protected]

M (408) 242-7588