SAP Platform Value & Adoption Roadmap

Transcription

SAP Platform Value and Adoption RoadmapWorkshop SlidesSAP Active Global Support, February 2014

Transition to SAP HANA - From Strategy to Value RealizationComplete lanExecution 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 RealizationThis lanExecution 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”PlatformStrategyPurpose of the “Platform Strategy Part”: Ensure that the capabilities of SAP Platform powered by SAP HANA and the related business and IT benefits andopportunities for your company are understoodScope & Approach: Proof that the new strategy makes sense commercially Deliverables: Aligned Platform Strategy &Value Proposition Definition of follow-up activities to further explore theopportunities for business and IT and to defineconcrete transition stepsCore elements of the SAP Platform, and the SAP platformValue PropositionProof how you can get there How to get the skills and resources in a sustainable way torealize the value Support engagement model, agile benefit drivenmethodologies and our control center objectives 2014 SAP AG or an SAP affiliate company. All rights reserved.4

SAP Platform Value and Adoption RoadmapHigh-levelRoadmap“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 lowScope & 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 ITDeliverables: BusinessValueBWRisk / Value evaluation matrixERPSRM SCMRisk /EffortsIdentification of the best migration sequence for fastbusiness value realization201320142015 2016ERPBW Transition risks and effortsSCMSRM 2014 SAP AG or an SAP affiliate company. All rights reserved.5

SAP HANA Adoption Roadmap for LiverpoolEvaluation CriteriaEvaluation Criteria The evaluation criteria below were used in order to get to the SAP HANA adoption roadmap:#CriteriaExemplary Questions0Boundary Condition:Technical feasibility Is the application available on SAP HANA? Can the scalability requirements for the application be met with the available technical architecture andhardware for SAP HANA?1Business 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?2Value for IT Are there pain points or cost drivers in IT from the current solution (e.g. replication of data, complexity ofarchitecture, license cost)?3Effort/duration and risk oftransition 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, disruptivechanges 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.Conclusion6

Transition PrioritiesBusiness and IT BenefitsCANDIDATESRoadmap based on Benefits, Efforts/Risks andRelease Strategy:IDEAL CANDIDATESECCCRMHighJan 2014:BW (ABC) PoC 1 on ABC: Transfer to the Project HEC migration to SAPHANASUPMFeb 2014: CUSTOMER to complete ECC EhP6 SP07 implementationNO CANDIDATESWAIT FOR BENEFITSSCMMay 2014: Upgrade Migration of SUPM to SAP HANASep 2014: Migration of BW (ABC) to SAP HANALowNov 2014:GRCHighLow PoC on ECC: Transfer to the Project HEC migration to SAPHANANov 2014: Re-evaluate situation for SCM and EWMEffort and Risk Of Transition to SAP HANA 2014 SAP AG or an SAP affiliate company. All rights reserved.7

High-Level Transition Plan - EXAMPLE2014Q1BW- Migration to HANASystem ABC- Functional impl. project- Migration to HANAQ2Q32015Q4Q1Q22016Q3Q4Q1Q2Q3Q4 eWM- SP 9 for eWM 7.02- Migration to HANAECC- EhP7- HANA migration, UC conversionCRM- Upgrade to xxx and HANA MigrationSRM- HANA migration - ?BPC- New implementation on HANAChanges already plannedChanges related to HANA 2014 SAP AG or an SAP affiliate company. All rights reserved.8

Motivation, Scope and ApproachAgenda Day 1 – SAP Platform Value and Adoption RoadmapTimeTopicLead09:00 – 09:3001 – Kick-off for the roadmap workshop- Scope and approach of the workshopSAP09:30 – 10:3002 – 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:3003 - Mission & Core Value Proposition of the SAP Platform- Core Platform Elements- Unparalleled Value Proposition- Engagement model (agile and benefit driven)- Control Center ApproachSAP11: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 ExperienceSAP14:30 – 17:0005 – 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 ApproachAgenda Day 2 – SAP Platform Value and Adoption RoadmapTimeTopicLead09:00 – 11:0006 - 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)SAP11:00 – 13:0007 – 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 review14:00 – 17:0008 – 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 innovationsSAP to prepare, jointdiscussion with inputfrom CUSTOMER onopportunities 2014 SAP AG or an SAP affiliate company. All rights reserved.10

Motivation, Scope and ApproachAgenda Day 3 – SAP Platform Value and Adoption RoadmapTimeTopicLead09:00 – 12:0009 – Evaluation of the key systemsPer system: System specific criteria evaluation- Technical Feasibility- Business Value- IT Value- Transition risks & effortsJoint evaluation13:00 – 16:0010 – 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 evaluation16:00 – 17:0011 – Wrap-Up- Short summary on results and findings- Next stepsAll 2014 SAP AG or an SAP affiliate company. All rights reserved.11

Transition to SAP HANA - From Strategy to Value RealizationOne workshop for the completesolution landscapePlatformStrategy- One delivery unit – one workshop- 3 days onsite- Results:High-levelRoadmapa) Platform strategyb) Customer-specific adoptionroadmapOptional preparation stepsExecuted per systemDetailedPlanResults:ExecutionExecution:SAP AGS offering for transition toHANA- 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 codeadj. methodology,.12

Transition to SAP HANA - From Strategy to Value RealizationBig anExecution 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 HANAImplementing Innovation – Supported E2E by SAP MaxAttentionConception Definitionof ScopeRapid Prototyping Definition of BusinessObjectives Definition of TechnicalObjectives Proof of Concept Cost-Benefit Analysis Business Case CreationProject Planning Targeted TechnicalInfrastructureDeployment Quality ManagementOperate HypercareHardware Setup and Transition to OCC Prerequisite SoftwareInfrastructure TestingInnovation Control Center - ICC MonitorVersions Cutover Planning andEngineeringServiceTransitionto SAP HANA Measure and Report Business DowntimeTestingCyclesKPIsObjectivesMigrationto SAP HANATechnical Infrastructure for SAP HANA Regression Testing Optimize Transition Roadmap Performance Testing Issue Management Resource Planning Operational Readiness ChangeOperationsControlManagementCenter 2014 SAP AG or an SAP affiliate company. All rights reserved. 14

Transition to the SAP Platform – Offering of SAP Active Global SupportHolistic Methodology Based on SAP Solution ManagerConcept &Project SetupRealizationPostGo-Live Project ureBlueprintDefine, drive and control milestones and Q-gatesMigration Tasks Architecture & InfrastructureDefine the infrastructure and landscape architecture to fulfill requirements of themigration and the operation after GoLive Migration TasksEnsure that migration tasks are executed along a proven plan and approach andbased on best practices for procedures and configurationsAdjustment of custom code – back to standard HANA-aware Performance & ScalabilityEnsure performance, throughput, scalability, availability. Define the technicalarchitecture and diness Operational ReadinessEnsure that procedures, tools and skills are adequate to run the new solution safelyand efficientlyOne end-to-end methodology – implemented in SAP Solution Manager 2014 SAP AG or an SAP affiliate company. All rights reserved.15

Transition to SAP HANAThe Foundation: SAP Solution Manager lizationProject trackingProject definitionQ – Gate Def.Issue trackingTechnical architecture options of DB’sQ-Gate management / issue trackingIssue trackingInfrastructure setup & configurationDetailed target SAP landscape definitionVerificationDetailed technical infrastructure definitionDetailed Migration planMigration of non-prod systemsMigration testsDetailed Migration Method definitionSandbox MigrationsFunctional regressionsPerformance, HA, Sec. testsTest scope determinationCut-over rehearsalDetailed test planningPerformance Baseline - KPISizingProduction cut-overMigration master plan definitionmigration scope, architecture and technical infrastructurePerformanceScalabilityMigration& TestArchitectureInfrastructureProjectMgmt.Concept &Project SetupPerformance Verification & OptimizationPerformanceOptimizationSource Scalability checkProceduresOperations proceduresToolsTool roadmapRoles & SkillsRoles & Skills, training planInventoryPerformanceMonitoringOperations proceduresHyper care /OptimizationTool implementationTrainingsOperations handoverDefinition of future conceptSLA verification 2014 SAP AG or an SAP affiliate company. All rights reserved.16

Delivery Model – New Services from SAP AGSMapping of the Main New Services to the RoadmapProject trackingProject definitionQ – Gate Def.Issue trackingQ-Gate management / issue trackingTIC for MigrationMigration master plan definitionmigration scope, architecture and technical infrastructureTechnical architecture options of DB’sService 1 – Migration Planning WorkshopPerformanceScalabilityMigration& TestArchitectureInfrastructureOptional: Landscape architecture Detailed target SAP landscape definitionDetailed technical infrastructure definitionIntegration ValidationInfrastructure setup & configurationVerificationData Consistency / Exception Management/System Integration/ Volume processing / Performance & ScalabilityDetailed Migration planMigration of non-prod systemsMigration testsDetailed Migration Method definitionSandbox MigrationsFunctional regressionsPerformance, HA, Sec. testsTest scope determinationService 2a – Performance baselineCut-over rehearsalDetailed test planningService 2b – Performance optimizationPerformance Baseline - KPISizingPerformance Verification & OptimizationProceduresOperations proceduresToolsTool roadmapRoles & SkillsRoles & Skills, training planInventoryDefinition of future conceptService 3 – tionSource Scalability checkService 4a – Operational readinessIssue trackingProduction cut-overBlueprintService 5 – GoLive SupportProjectMgmt.Concept &Project SetupServ. bundle 4b : Operational readinessOperations proceduresTool implementationHyper care /OptimizationTrainingsOperations handoverSLA verification 2014 SAP AG or an SAP affiliate company. All rights reserved.17

Transition to HANA – Offering of SAP Active Global SupportFlexible Delivery ModelThe 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 maintenanceDelivery 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 YouSAP 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, andSAP 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 forthin 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 andother countries.Please see dex.epx#trademark for additional trademark information and notices. 2014 SAP AG or an SAP affiliate company. All rights reserved.20

Establish a consistent platform strategy leveraging SAP HANA High-level Roadmap 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