SAPC-BAIO-066-Key Topics in Getting System Ready

ASAP Focus MethodologyKey Topics Getting the System Ready

CSE Portfolio and Operations

© SAP AG 2008 / Page 2

Objectives

At the end of this presentation you will: Understand what the key topics regarding getting system ready

of the ASAP Focus Methodology are

Know which activities are addressing the key topics

What risks are associated

And which accelerators are provided to mitigate those risks


1. Introduction

2. Get System ready: Delta requirements

3. Get System ready: Solution Preparation

4. Get System ready: FRICE

Agenda


What is a key topic

A key topic is a group of activities that is:

Related to high risk

An implementation major effort driver

A look at activities, across the phases of the ASAP Focus Methodology, for the purpose of better understanding the specific approach


Key topics in the ASAP Focus Methodology

Positioning with the customer the Solution and the Approach (Evaluation Roadmap)

Getting the System ready Delta requirements Solution Preparation Forms adaptations, Reports adaptation, Interface development,

Conversion, Enhancements (FRICE)

Getting the Data ready Data migration

Getting the People ready Organizational Change Management User Acceptance Key/ End-User Training Data People

system


1. Introduction


3. Get System ready: Solution preparation


Agenda


General approach to Delta requirements

Why is this a key topic? Delta requirements are the main ‘source of evil’. Proper expectation

management with the customer is crucial to the overall success of the project. The value of the pre-determined solution is quickly lost once you increase the scope with delta requirements.

Winning Conditions Delta requirements are kept to max. 10% of the initial offering Delta requirements can include

Scope differences Data Migration activities Development of additional reporting Required forms designing Authorizations

Customer’s project team has read and approved the Blueprint in writing Customer has resources available and empowered to decide which delta

requirements need to be handled now or in a later phase


Delta requirements – Risks

Risk P I

Amount of delta requirements grow beyond a reasonable level (>10% of overall project effort) quickly eating up the efficiency gained trough a pretested, -documented, -configured solution.

Required stakeholders don‘t attend the delta requirements sessions or are not empowered to take decisions on behalf of the company, which leads to wrong definition of requirements

Customer misunderstands the predefined scope or the delta requirements definition which leads to unexpected additional requirements during realization causing a loop back to delta design

Integration issues of some delta requirements are underestimated causing delays in realization (e.g. additional order type in SD has impact on account determination and CO-PA)

Duration of Delta Requirements sessions gets too long to be affordable in the pre sales cycle

High Medium Low

P = Probability I = Impact


ASAP Focus Methodology Overview

RealizationFinal

PreparationGo Live & Support

EvaluationPre-Project Activities

Delta Requirements

Evaluation Roadmap Implementation Roadmap

time

Project Preparation

Customer Qualification

Position Solution & Services

Delta Requirements

Sessions

Create Preliminary

Proposal

Finalize Proposal

Customer Signs offBlueprint

Assemble Statement of

Work

General Project Management

Data MigrationWorkshopActivities

Project Team Training

Position OCM

Set Up System Environment

Project Standards & Procedures


ConductKick off Meeting

DEV Infrastructure

Setup


Review ProjectPreparation

Phase

QAInfrastructure

Setup

Validate Org.Structure &General Settings

Delta Realization

Validate Solution

Organizational Change

Management

Integration &Acceptance

Tests

Prepare Cutover & Production

Support

Review Realization

Phase


End User Training

Check Org.Change

Readiness

Create & StaffHelp Desk

Check SystemReadiness

Cutover toProduction

ProductionSupport


Project Closing

Customerqualified

StartContractsignature

Projectkick-off

Go-Live

Go Live Readiness

Check

© SAP AG 2008 / Page 10

ASAP Focus Methodology Overview – Get System Ready

RealizationFinal



Delta Requirements


time

Project Preparation



Delta Requirements

Sessions

Create Preliminary

Proposal

Finalize Proposal





Position OCM





DEV Infrastructure

Setup



Phase

QAInfrastructure

Setup


Delta Realization

Validate Solution


End User Training

Check Org.Change

Readiness




ProductionSupport


Project Closing

Go Live Readiness

Check

Present Solution & Services

Present Implementation Approach

Present Data Migration Approach

Present Organizational Change Readiness

Prepare Prototype System

Present and Refine Solution in Detail

Assess Data Complexity

Document Delta Requirements

Configure Deltas

Adapt Forms Reports

Set up User Roles and Authorizations

Establish Interfaces

…Assemble

Statement of Work

© SAP AG 2008 / Page 11

Contains list of assumptions & a how-to guide on running the Delta Requirement Sessions.A

ccel

erat

ed w

ith

Document Delta Requirements during Delta Requirement Sessions. Separate Template are provided for Processes Forms, Reports and Interfaces.

Customer Specification Documents (CSD)

Delta Requirements Guiding Principles

Use the Solution Map in parallel with your prototype system. This will give your customer a better visual representation of the solutions and will be more capable to faster and more reliably identify gaps

Solution Map and Solution Composer

● Overview document to list all objects for forms, reports, interfaces & Data Migration (basic scope + delta requirements)FRICE master list

Delta Requirements – ASAP Focus Roadmap Accelerators

© SAP AG 2008 / Page 12

1. Introduction




Agenda

© SAP AG 2008 / Page 13

General approach to Solution Preparation

Why is this a key topic? Installation of the Solution and the Solution Components is a commodity in

ASAP Focus approach. However a one or two week time in a 10 -12 weeks of implementation is a considerable duration and any delay in hardware delivery can

Winning Conditions Early anticipate the Installation activities by preparing as much as possible

beforehand. Usage of Solution Manager can accelerate System preparation activities.

© SAP AG 2008 / Page 14

Solution Preparation – Risks

Risk P I

A delay in hardware delivery can put in risk the time lines, resources and budget of the project.

Underestimation of Solution installation can lead to delays. A delay of a week in a 10-12 weeks project is a risk that should be taken under consideration

High Medium Low


© SAP AG 2008 / Page 15


RealizationFinal



Delta Requirements


time

Project Preparation



Delta Requirements

Sessions

Create Preliminary

Proposal

Finalize Proposal


Assemble Statement of

Work




Position OCM





DEV Infrastructure

Setup



Phase

QAInfrastructure

Setup

Validate Org..Structure &General Settings

Delta Realization

Validate Solution

Organizational Change

Management

Integration &Acceptance

Tests

Prepare Cutover & Production

Support

Review Realization

Phase


End User Training

Check Org.Change

Readiness




ProductionSupport


Project Closing

Go Live Readiness

Check

Order Best Practices

Anticipate Solution Preparation

Install System Hardware

Install Solution

Install Local tools

Prepare Solution for Realization

Perform Initial Trial for Data Migration

© SAP AG 2008 / Page 16

Acc

eler

ated

wit

h A how-to presentation provided within the roadmap can guide you of how to anticipate delays in Solution installation

Solution Preparation Presentation

Solution Preparation – ASAP Focus Roadmap Accelerators

Usage of Project Templates to create the project and the structure of the Solution within Solution manager tool accelerates considerably the Solution preparation.

Solution Manager Project Templates

© SAP AG 2008 / Page 17

1. Introduction




Agenda

© SAP AG 2008 / Page 18

General approach to FRICE

Why is this a key topic? Feedback from current projects shows that Forms, Reports, Interfaces,

Conversions, Enhancements can be up to 50% of the overall project effort.

Winning Conditions SAP Preconfigured Smart Forms are used as templates Standard reports are used whenever possible Interface specifications are clearly described by the customer migration spreadsheets are supplied in the pre-project activities phase and the

customer extracts data from his legacy systems before project team is on site No enhancements (like user exits). Configuration kind of Deltas can be accelerated by the usage of Solution

Manager

© SAP AG 2008 / Page 19

FRICE – Risks (excluding Data Migration)

Risk P I

Customer looking at forms or reports with his own data during the business validation workshops suddenly realize that additional requirements or changes to the agreed content/layout is required. This creates an additional amount of work and a loop back to delta design.

Interface specifications are incomplete leading to misunderstanding and delay in delta realization

High Medium Low


© SAP AG 2008 / Page 20

Acc

eler

ated

wit

h Document Delta Requirements during Delta Requirement Sessions. Separate Template are provided for Processes Forms, Reports and Interfaces.

Customer Specification Documents (CSD)

FRICE – ASAP Focus Roadmap Accelerators

Delta Configuration can be accelerated with the use of relevant functionality provided by Solution Manager Tool

Solution Manager Configuration Functionality

© SAP AG 2008 / Page 21

Summary

In this Session you learned

What are the major risks implied in getting the system ready and how to mitigate them How to accelerate activities related to getting the system ready

© SAP AG 2008 / Page 22

Sophia Ersi FilaktouCSE Portfolio and Operations

ASAP Focus Mailbox

Contact

© SAP AG 2008 / Page 24

Thank you!

© SAP AG 2008 / Page 25

Copyright 2008 SAP AGAll rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission 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.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

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

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

© SAP AG 2008 / Page 26


RealizationFinal



Delta Requirements


time

Project Preparation



Delta Requirements

Sessions

Create Preliminary

Proposal

Finalize Proposal





Position OCM





DEV Infrastructure

Setup



Phase

QAInfrastructure

Setup


Delta Realization

Validate Solution


End User Training

Check Org.Change

Readiness




ProductionSupport


Project Closing

Go Live Readiness

Check

Present Solution & Services

Present Implementation Approach

Present Data Migration Approach

Present Organizational Change Readiness

Prepare Prototype System

Present and Refine Solution in Detail

Assess Data Complexity

Document Delta Requirements

Configure Deltas

Adapt Forms Reports

Set up User Roles and Authorizations

Establish Interfaces

… …

Order Best Practices

Anticipate Solution preparation