Uploaded by Digvijay Garg

SAP Platform Value & Adoption Roadmap

advertisement
SAP Platform Value and Adoption Roadmap
Workshop Slides
SAP Active Global Support, February 2014
Transition to SAP HANA - From Strategy to Value Realization
Complete Approach
Platform
Strategy
High-level
Roadmap
Detailed
Plan
Execution
• Understand the value and benefit of SAP HANA to Business and IT
• Proof how to manage the transition
 Establish a consistent platform strategy leveraging SAP HANA
• Evaluate technical feasibility, migration risks & efforts, and Business & IT value per system
• Define a customer specific adoption roadmap driven by business value – best migration sequence
 Develop an overall high-level value and transition roadmap
• Create a detailed plan for the transition of one or multiple systems to SAP HANA
• Focus: Migration approaches/project plan and Technical Architecture for SAP HANA
 Develop a detailed transition plan per system
• Execute the detailed migration plan, with the help of SAP Active Global Support
 SAP Landscape is successfully and safely transitioned to SAP HANA
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
2
Transition to SAP HANA - From Strategy to Value Realization
This Workshop
Platform
Strategy
High-level
Roadmap
Detailed
Plan
Execution
• Understand the value and benefit of SAP HANA to Business and IT
• Proof how to manage the transition
 Establish a consistent platform strategy leveraging SAP HANA
• Evaluate technical feasibility, migration risks & efforts, and Business & IT value per system
• Define a customer specific adoption roadmap driven by business value – best migration sequence
 Develop an overall high-level value and transition roadmap
• Create a detailed plan for the transition of one or multiple systems to SAP HANA
• Focus: Migration approaches/project plan and Technical Architecture for SAP HANA
 Develop a detailed transition plan per system
• Execute the detailed migration plan, with the help of SAP Active Global Support
 SAP Landscape is successfully and safely transitioned to SAP HANA
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
3
SAP Platform Value and Adoption Roadmap
“Platform Strategy Part”
Platform
Strategy
Purpose of the “Platform Strategy Part”:
•
Ensure that the capabilities of SAP Platform powered by SAP HANA and the related business and IT benefits and
opportunities for your company are understood
Scope & Approach:
•
Proof that the new strategy makes sense commercially
•
•
Deliverables:
•
Aligned Platform Strategy &
Value Proposition
•
Definition of follow-up activities to further explore the
opportunities for business and IT and to define
concrete transition steps
Core elements of the SAP Platform, and the SAP platform
Value Proposition
Proof how you can get there
•
How to get the skills and resources in a sustainable way to
realize the value
•
Support engagement model, agile benefit driven
methodologies and our control center objectives
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
4
SAP Platform Value and Adoption Roadmap
High-level
Roadmap
“Roadmap Part”
Purpose of the “Roadmap Part”:
•
Create a transition roadmap, which presents system migrations in the context of planned business releases
•
Migrate those systems first, where expected business benefit is high, and risks and efforts are low
Scope & Approach:
•
As-Is status of business scenarios and technical setup
•
Planned business releases, and requirements
•
Detailed evaluation of:
•
Technical migration feasibility
•
Value and opportunities for business and IT
Deliverables:
•
•
Business
Value
BW
Risk / Value evaluation matrix
ERP
SRM SCM
Risk /
Efforts
Identification of the best migration sequence for fast
business value realization
2013
2014
2015 2016
ERP
BW
•
Transition risks and efforts
SCM
SRM
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
5
SAP HANA Adoption Roadmap for Liverpool
Evaluation Criteria
Evaluation Criteria
 The evaluation criteria below were used in order to get to the SAP HANA adoption roadmap:
#
Criteria
Exemplary Questions
0
Boundary Condition:
Technical feasibility
• Is the application available on SAP HANA?
• Can the scalability requirements for the application be met with the available technical architecture and
hardware for SAP HANA?
1
Business value
• Are there pain points or cost drivers in the business resulting from the current solution (e.g. performance,
duplication of data)?
• Are there business requirements for “big data”, more real-time business or higher speed and agility?
• Are there business opportunities to (re)build processes?
2
Value for IT
• Are there pain points or cost drivers in IT from the current solution (e.g. replication of data, complexity of
architecture, license cost)?
3
Effort/duration and risk of
transition
• What is the effort/duration for testing, training and technical transition?
- How large is the difference between current state and target state (release level, Unicode, disruptive
changes with the new release)?
- How many business scenarios are used? How many users?
• How business critical is the application?
• How risky is the transition in general?
- How many customers are already live with the application on HANA?
- How many customers have used the proposed migration approach?
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Conclusion
6
Transition Priorities
Business and IT Benefits
CANDIDATES
Roadmap based on Benefits, Efforts/Risks and
Release Strategy:
IDEAL CANDIDATES
ECC
CRM
High
Jan 2014:
BW (ABC)
 PoC 1 on ABC: Transfer to the Project HEC + migration to SAP
HANA
SUPM
Feb 2014:
 CUSTOMER to complete ECC EhP6 SP07 implementation
NO CANDIDATES
WAIT FOR BENEFITS
SCM
May 2014:
 Upgrade + Migration of SUPM to SAP HANA
Sep 2014:
 Migration of BW (ABC) to SAP HANA
Low
Nov 2014:
GRC
High
Low
 PoC on ECC: Transfer to the Project HEC + migration to SAP
HANA
Nov 2014:
 Re-evaluate situation for SCM and EWM
Effort and Risk Of Transition to SAP HANA
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
7
High-Level Transition Plan - EXAMPLE
2014
Q1
BW
- Migration to HANA
System ABC
- Functional impl. project
- Migration to HANA
Q2
Q3
2015
Q4
Q1
Q2
2016
Q3
Q4
Q1
Q2
Q3
Q4
…
…
eWM
- SP 9 for eWM 7.02
- Migration to HANA
ECC
- EhP7
- HANA migration, UC conversion
CRM
- Upgrade to xxx and HANA Migration
SRM
- HANA migration - ?
BPC
- New implementation on HANA
Changes already planned
Changes related to HANA
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
8
Motivation, Scope and Approach
Agenda Day 1 – SAP Platform Value and Adoption Roadmap
Time
Topic
Lead
09:00 – 09:30
01 – Kick-off for the roadmap workshop
- Scope and approach of the workshop
SAP
09:30 – 10:30
02 – <CUSTOMER>’s expectations, priorities and boundary conditions
- Expectations for the introduction of the SAP platform
- Current pain points, future requirements, planned extensions
- Fixed boundary conditions
<CUSTOMER>
10:30 – 11:30
03 - Mission & Core Value Proposition of the SAP Platform
- Core Platform Elements
- Unparalleled Value Proposition
- Engagement model (agile and benefit driven)
- Control Center Approach
SAP
11:30 – 14:30
(incl. Lunch)
04 – SAP platform powered by SAP HANA – overview of key capabilities
- HANA in-memory innovation platform
- Integration and Orchestration
- The Ultimate User Experience
SAP
14:30 – 17:00
05 – Platform Technical Deployment
- Infrastructure and Data Center Operations
- (Deployment, Cloud Management, HA/DR)
SAP to prepare
/ Joint discussion
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
9
Motivation, Scope and Approach
Agenda Day 2 – SAP Platform Value and Adoption Roadmap
Time
Topic
Lead
09:00 – 11:00
06 - Managing the SAP Platform
- E2E Application Lifecycle Management: Two Value Release per Year
- Zero Downtime Upgrades / Transitions
- Getting less but high quality Custom Code
- Best Practices & Platform Support (ICC)
SAP
11:00 – 13:00
07 – Status of current landscape at <CUSTOMER>
- Overview of business scenarios (current and planned)
- Roles of the different systems in the solution landscape
- Per system: system load, DB sizes & growth rates
- Custom code (areas and rough volume)
SAP to prepare
/ Joint review
14:00 – 17:00
08 – Potential business and IT benefits for <CUSTOMER>
- SAP’s application roadmap
- Business scenario recommendations
- Opportunities to address current pain points
- Opportunities to extend current business scenarios to leverage current/planned SAP innovations
SAP to prepare, joint
discussion with input
from <CUSTOMER> on
opportunities
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
10
Motivation, Scope and Approach
Agenda Day 3 – SAP Platform Value and Adoption Roadmap
Time
Topic
Lead
09:00 – 12:00
09 – Evaluation of the key systems
Per system: System specific criteria evaluation
- Technical Feasibility
- Business Value
- IT Value
- Transition risks & efforts
Joint evaluation
13:00 – 16:00
10 – Creation of a roadmap for <CUSTOMER>
Conduct a roadmap for XX, based on
- the results of the system evaluation
- the release plan, functional enhancement and rollout plan of <CUSTOMER>
Joint evaluation
16:00 – 17:00
11 – Wrap-Up
- Short summary on results and findings
- Next steps
All
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
11
Transition to SAP HANA - From Strategy to Value Realization
One workshop for the complete
solution landscape
Platform
Strategy
- One delivery unit – one workshop
- 3 days onsite
- Results:
High-level
Roadmap
a) Platform strategy
b) Customer-specific adoption
roadmap
Optional preparation steps
Executed per system
Detailed
Plan
Results:
Execution
Execution:
SAP AGS offering for transition to
HANA
- Clarify on Custom Code Mgmt.
- Data Center Readiness
-…
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Detailed execution plan, landscape,
transition methods, custom code
adj. methodology,..
12
Transition to SAP HANA - From Strategy to Value Realization
Big Picture
Platform
Strategy
High-level
Roadmap
Detailed
Plan
Execution
• Understand the value and benefit of SAP HANA to Business and IT
• Proof how to manage the transition
 Establish a consistent platform strategy leveraging SAP HANA
• Evaluate technical feasibility, migration risks & efforts, and Business & IT value per system
• Define a customer specific adoption roadmap driven by business value – best migration sequence
 Develop an overall high-level value and transition roadmap
• Create a detailed plan for the transition of one or multiple systems to SAP HANA
• Focus: Migration approaches/project plan and Technical Architecture for SAP HANA
 Develop a detailed transition plan per system
• Execute the detailed migration plan, with the help of SAP Active Global Support
 SAP Landscape is successfully and safely transitioned to SAP HANA
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
13
Transition to SAP HANA
Implementing Innovation – Supported E2E by SAP MaxAttention
Conception

Definition
of Scope
Rapid Prototyping

Definition of Business
Objectives

Definition of Technical
Objectives

Proof of Concept

Cost-Benefit Analysis

Business Case Creation
Project Planning

Targeted Technical
Infrastructure
Deployment

Quality Management
Operate

Hypercare
Hardware Setup and
 Transition to OCC
 Prerequisite Software
Infrastructure Testing
Innovation Control Center - ICC
 Monitor
Versions
 Cutover Planning and
Engineering
Service
Transition
to SAP HANA
 Measure and Report
 Business Downtime
Testing
Cycles
KPIs
Objectives
Migration
to SAP HANA
Technical Infrastructure for SAP HANA
 Regression Testing
 Optimize
 Transition Roadmap
 Performance Testing
 Issue Management
 Resource Planning
 Operational Readiness
 Change
Operations
ControlManagement
Center
© 2014 SAP AG or an SAP affiliate company. All rights reserved.

14
Transition to the SAP Platform – Offering of SAP Active Global Support
Holistic Methodology Based on SAP Solution Manager
Concept &
Project Setup
Realization
Post
Go-Live
 Project Management
Project
Management
Architecture
Infrastructure
Blueprint
Define, drive and control milestones and Q-gates
Migration Tasks
 Architecture & Infrastructure
Define the infrastructure and landscape architecture to fulfill requirements of the
migration and the operation after GoLive
 Migration Tasks
Ensure that migration tasks are executed along a proven plan and approach and
based on best practices for procedures and configurations
Adjustment of custom code – back to standard + HANA-aware
 Performance & Scalability
Ensure performance, throughput, scalability, availability. Define the technical
architecture and infrastructure
Performance
Scalability
Operational
Readiness
 Operational Readiness
Ensure that procedures, tools and skills are adequate to run the new solution safely
and efficiently
One end-to-end methodology – implemented in SAP Solution Manager
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
15
Transition to SAP HANA
The Foundation: SAP Solution Manager Roadmap
Operational
Readiness
Blueprint
Post
Go-Live
Realization
Project tracking
Project definition
Q – Gate Def.
Issue tracking
Technical architecture options of DB’s
Q-Gate management / issue tracking
Issue tracking
Infrastructure setup & configuration
Detailed target SAP landscape definition
Verification
Detailed technical infrastructure definition
Detailed Migration plan
Migration of non-prod systems
Migration tests
Detailed Migration Method definition
Sandbox Migrations
Functional regressions
Performance, HA, Sec. tests
Test scope determination
Cut-over rehearsal
Detailed test planning
Performance Baseline - KPI
Sizing
Production cut-over
Migration master plan definition
migration scope, architecture and technical infrastructure
Performance
Scalability
Migration
& Test
Architecture
Infrastructure
Project
Mgmt.
Concept &
Project Setup
Performance Verification & Optimization
Performance
Optimization
Source Scalability check
Procedures
Operations procedures
Tools
Tool roadmap
Roles & Skills
Roles & Skills, training plan
Inventory
Performance
Monitoring
Operations procedures
Hyper care /
Optimization
Tool implementation
Trainings
Operations handover
Definition of future concept
SLA verification
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
16
Delivery Model – New Services from SAP AGS
Mapping of the Main New Services to the Roadmap
Project tracking
Project definition
Q – Gate Def.
Issue tracking
Q-Gate management / issue tracking
TIC for Migration
Migration master plan definition
migration scope, architecture and technical infrastructure
Technical architecture options of DB’s
Service 1 – Migration Planning Workshop
Performance
Scalability
Migration
& Test
Architecture
Infrastructure
Optional: Landscape architecture planning
Operational
Readiness
Post
Go-Live
Realization
Detailed target SAP landscape definition
Detailed technical infrastructure definition
Integration Validation
Infrastructure setup & configuration
Verification
Data Consistency / Exception Management/System Integration
/ Volume processing / Performance & Scalability
Detailed Migration plan
Migration of non-prod systems
Migration tests
Detailed Migration Method definition
Sandbox Migrations
Functional regressions
Performance, HA, Sec. tests
Test scope determination
Service 2a – Performance baseline
Cut-over rehearsal
Detailed test planning
Service 2b – Performance optimization
Performance Baseline - KPI
Sizing
Performance Verification & Optimization
Procedures
Operations procedures
Tools
Tool roadmap
Roles & Skills
Roles & Skills, training plan
Inventory
Definition of future concept
Service 3 – Post
GoLive
Performance
Monitoring
Performance
Optimization
Source Scalability check
Service 4a – Operational readiness
Issue tracking
Production cut-over
Blueprint
Service 5 – GoLive Support
Project
Mgmt.
Concept &
Project Setup
Serv. bundle 4b : Operational readiness
Operations procedures
Tool implementation
Hyper care /
Optimization
Trainings
Operations handover
SLA verification
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
17
Transition to HANA – Offering of SAP Active Global Support
Flexible Delivery Model
The SAP offering is delivered as a flexible package consisting of
 The methodology implemented in SAP Solution Manager
 This is the backbone of each transition!
Methodology used by all roles – SAP TQM, consultants, customer experts, partners
 Consistent approach and quality across all involved parties
 Best Practices templates and guidelines for each of the tasks
 Onsite services and remote offerings: Expert Guided Implementations, remote service
 Enablement: Guided procedures, trainings, remote expert sessions,….
Plus:
 Reduction of custom code – back to standard
 Analysis, evaluation, reduction – SAP can take responsibility for code maintenance
Delivery model can be tailored in a flexible way to the concrete customer situation
(partners, division of work, priorities in the project,….)
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
18
Thank You
SAP Active Global Support
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
© 2014 SAP AG or an SAP affiliate company. All 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.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth
in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP 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
other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
20
Download