SAP Managed Cloud as a Service (MCaaS)

Transcription

1 SAP Managed Cloud as a Service (MCaaS) The impact of MCaaS on the Total Cost of Ownership (TCO) of running SAP 1 MEASURE 2 ANALYZE 3 OPTIMIZE VMS AG July 2013

2 Content KEY FINDINGS Executive Summary IN DEPTH ANALYSIS MCaaS Savings Explained in Detail METHODOLOGY Evaluation Parameters, Approach & Assumptions P. 2

3 Overview: SAP s Managed Cloud as a Service Subscription delivery of traditional SAP solutions SAP s Managed Cloud as a Service enables subscription delivery of traditional SAP solutions on a partner s private hosted cloud, including application management services. The customer enjoys a fully outsourced solution with the following key benefits: P. 3 SAP provides: Term license for SAP solutions for use within packaged software services Support for partner and end-customers solution deployments MCaaS partner creates: Subscription solutions hosted on partner s private cloud Customized offering, tailored to individual customer needs Application migration, implementation, management & support services Strategic: Increased flexibility and agility in responsiveness to business changes and changing requirements Financial: Faster time to value and an overall 30% lower TCO over 5 years, plus conversion of CAPEX into OPEX that delivers an optimized cash flow Operational: Better utilization of information systems with increased focus on high value IT initiatives, instead of lower value system maintenance

4 Summary of TCO Savings & Impact Areas MCaaS enables savings of 30% over a 5-year TCO lifecycle Primary drivers for the TCO reduction are the combined result of key MCaaS components: SAP TCO Stack elements from bottom to top in chronological order of the TCO lifecycle Economies of scale from Cloud-based infrastructure Scalability increase/decrease system usage on demand without wasted or underutilized systems for backup, dev, and QA 17% MCaaS Savings 30% Flexibility business process changes can quickly be reflected in IT infrastructure Speed Fast deployment and provisioning speeds time to value and lowers wait time, improving productivity Lower costs from application management services 18% 32% 10% 11% Upgrade Projects Continuous Improvement Projects Operations Pooled Resources Expertise is spread across multiple customers, thereby making it cheaper on a per customer basis than if customers staffed dedicated SAP resources 11% 22% Hardware/Software Ongoing Cost Automation / Standardization Combines automated processes for provisioning, management and monitoring with virtualization across customers, along with standardized packages for implementation, upgrades, and patches 10% 12% On-Premise 20% 7% 0% MCaaS Implementation Hardware/Software Investment P. 4 Based on VMS TCO benchmarking data for over 2,900 SAP customer deployments, see savings detail section and methodology appendix for additional details

5 Timing of MCaaS Financial Impacts Cost Impact Timing & Cash Flow Optimization with MCaaS The 30% savings in TCO accumulates over the course of 5 years, as shown in the chart on the right. Since MCaaS extends the benefit of infrastructure hosting to software licenses as well, the upfront capital costs are nearly eliminated When compared to traditional on-premise deployment options, MCaaS cost savings are mostly front-loaded, with 51% of the savings realized in the first year, and the remaining savings realized over the remaining years 100% 80% 60% 40% 20% 0% MCaaS Expenses as a % of On-Premise Over 5 Years 60% 65% 68% 70% 49% Year 1 Year 2 Year 3 Year 4 Year 5 On top of the overall 30% TCO reduction, a more even distribution of payments with MCaaS helps to optimize overall cash flow On-premise deployments require more up-front cash outlay (31% of total) while MCaaS has a more evenly distributed cash flow impact of (approximately 20% per year) The impact from MCaaS on cash flow optimization is also greater than onpremise since the large initial outlays associated with on-premise deployments are less discounted from a time-value of money perspective, and are therefore more expensive, dollar for dollar Comparative Distribution of Cash Flows Over 5 Years On-Premise MCaaS Year 1 Year 2 Year 3 Year 4 Year 5 P. 5 Based on VMS TCO benchmarking data for over 2,900 SAP customer deployments, see savings detail section and methodology appendix for additional details

6 Content KEY FINDINGS Executive Summary IN DEPTH ANALYSIS MCaaS Savings Explained in Detail METHODOLOGY Evaluation Parameters, Approach & Assumptions P. 6

7 VMS MCaaS Study July 2013 High Level Overview of Key Benefit Areas 30% Cost Reduction along with optimization of Cash Flow The MCaaS TCO impacts are greatest in the following areas: Upfront hardware & software investment is almost completely eliminated, going from 12% of TCO down to 0.1%. MCaaS extends OpEx subscription for hardware inherent in outsourced infrastructure hosting by adding in OpEx subscription pricing for SAP software as well. In contrast, ongoing cost for hardware and software (where the license payments have been moved to as operation cost) increases from an 11% to a 20% share. This is below 100% increase (72% cost increase) due to better allocation and provisioning of hardware and licenses. Implementation as well as later continuous improvement projects and upgrades benefit from the cloud operation model with savings in the range of 37-39%. In both private and public, the cloud operation model provides flexibility and speed in resource provisioning which is needed to enable application implementation or change processes. Whether it s the initial technical implementation, a test system needed to check out an application change, fast replication of test data, or additional machines needed during an upgrade process, in all these cases, the rapid deployment of resources speeds up project execution, enables early testing, and saves costs in FTE time waiting for systems to be available. Spending in Operations (especially application management and support) is reduced by 29%. Not only does the cloud computing model provide resources faster, it makes provisioning easier via automation of IT processes. Virtualization is a large part of this saving effect as well as centralized management resources and talent pooling. The key to success are automation and software defined landscape management. SAP TCO model Level 1 Weight* MCaaS triggered savings Hardware/Software Investment 12% 99% Implementation 10% 34% Hardware/Software Ongoing Cost 11% -72% Operations 32% 29% Continuous Improvement Projects 18% 37% Upgrade Projects 17% 39% Consolidated (Overall savings) 30% * Weight = Share of cost for operation On-Premise P. 7

8 VMS MCaaS Study July 2013 Detailed Savings in SAP MCaaS Deployments Initial investments & implementation costs savings SAP TCO model Level 1 SAP TCO Model Level 2 MCaaS savings MCaaS Effects Explained Hardware/Software Investment Technical Infrastructure 95% System Software 100% Application Software 100% Small amount of infrastructure and deployment still needed, but the largest part of a typical onpremise deployment investment is eliminated. No upfront investment needed for applications, only for some infrastructure and implementation. Technical Setup & Process Design 90% Technical implementation of hardware and software is virtually eliminated as cloud deployment uses pre-defined infrastructure and pre-installed software. Organizational Change 0% No effect, organizational change management is still needed. Business Setup 0% No effect, business process design is also still needed. Implementation Project Management 20% Testing 35% More flexibility when additional resources are needed, and lower project overhead (technical implementation, etc.), can help projects stay on-time and on-budget and reduce effort needed. Having one provider that knows the customer s business and offers long term consulting rates which are better than the market. Provisioning of test systems and test data is easier to accomplish with additional resources and ondemand infrastructure that scales up and down as needed. Training 35% Training systems are cheaper to provide. Refreshes can be done easier, faster, more often in the cloud operating model. P. 8 Based on VMS TCO benchmarking data for over 2,900 SAP customer deployments, see methodology appendix for additional details

9 VMS MCaaS Study July 2013 Detailed Savings in SAP MCaaS Deployments Ongoing investments, operations, and upgrade projects costs savings SAP TCO model Level 1 SAP TCO Model Level 2 MCaaS savings MCaaS Effects Explained Hardware/Software Ongoing Cost Technical Infrastructure 35% System Software -123% Application Software -95% Changes in the infrastructure are much easier to provide. Increases and decreases in infrastructure needs can be managed more effectively; over-provisioning of resources to meet max capacity vs. low utilization of overall capacity during times of normal demand is no longer an issue. System software (database) and application software ongoing costs increase since there are continuous payments made in a subscription model. These increases in ongoing costs can largely offset the upfront investment savings but the positive cash flow implications are an added benefit. Operations Continuous Improvement Projects Upgrade Projects System Operations 53% The huge impact on operations is caused by the efficiency of the cloud computing operations model. Virtualized environments, automated processes, and centralized resources enable high level of costs savings. Application Operations 22% Talent pooling and SAP expertise availability enable more customers to be supported by less FTEs, resulting in a net savings across customer implementations. Continuous Business Improvement Continuous Technical Improvement Rollouts 40% Application Upgrade 36% System Upgrade 55% 34% 90% When MCaaS is used, you are able to quickly add another resource that you need. The simple expansion and scaling of SAP instances, in the case of higher demand due to an increasing number of users or new functions, is based on the ability to expand the capacity of cloud infrastructure. The provisioning and management of SAP training and test systems can be simplified and accelerated using cloning and recovery functions. Also, the lead time for setting up new SAP systems decreases. Consolidation of services from one service provider will enable larger volumes of consulting utilization and therefore the ability to negotiate lower overall consulting rates. P. 9 Based on VMS TCO benchmarking data for over 2,900 SAP customer deployments, see methodology appendix for additional details

10 Content KEY FINDINGS Executive Summary IN DEPTH ANALYSIS MCaaS Savings Explained in Detail METHODOLOGY Evaluation Parameters, Approach & Assumptions P. 10

11 VMS MCaaS Study July 2013 Customer Profile For The TCO Comparison A manufacturing company choosing between on-premise and MCaaS P. 11 Key facts about the TCO comparison: The basis for the comparison is the a manufacturing company with about $1.5B in revenue, based in the United States with a production plant in Asia and sales offices round the world. The SAP software to be licensed includes core ERP, BW and CRM. The user community is about 1,500 named users, split into the different license categories as shown in the chart to the right. All systems are run in the usual 3-stage-model with development, quality assurance and production for each application (ERP, BW, CRM). The comparison focuses on the TCO for a traditional in-house operations model (on-premise) vs. the MCaaS approach: On-premise: Data center (Wintel or Unix, DB Oracle) on premise, IT and application management in-house MCaaS: Data center, IT and applications operations out of a managed private cloud, technology and application all SAP (including HANA or Sybase database) SLAs as described on the right apply for both scenarios, on-premise or MCaaS, in the same way Incident & Problem Management Application Support SLA for Production Systems Office times USA System Support 7*24h Availability 99,50% RTO (recovery time objective) RPO (recovery point objective) Dialog response time ERP SAP Landscape Named users (total) 1,500 SAP Licenses: Professional / limited prof. / ESS Storage used 800 / 200 / TB SAPS 80,000 System Landscape SAP Systems (all in 3 stage mode, DEV QA PROD) ERP BW CRM Fully used (not HR), 1,000 users, 600 active users per day Reporting via Bex and HTTP, 500 users, 100 active per day Globally used, 300 users, 200 active per day 8h 4h 90% < 1 second

12 VMS MCaaS Study July 2013 SAP TCO Model Overview The SAP TCO model covers the whole SAP lifecycle Important components of the SAP TCO model: The basis of this study is the SAP TCO model. This model covers the total cost of the entire lifecycle of SAP software. The study covers CAPEX (investment cost) as well as OPEX (operational cost) elements. Hardware/Software Investment covers all costs to set up a technical environment to run SAP on. Implementation covers the initial application customization and setup. Hardware/Software Ongoing Cost covers all HW/SW related cost, which occur continuously over time. In the MCaaS model this is the continuous payments for licenses. In the case of on-premise, the maintenance payments for HW and SW. Operations covers the usual day-to-day work to keep things running. It includes job management, system surveillance, etc. Continuous Improvement Projects cover all kind of changes, triggered by changing needs of users or the business. Upgrade Projects cover all SAP triggered changes by new software releases but also similar activities by database vendors, OS vendors, etc. This study does not include end user operations, WAN or workplace-pc related cost. The study is based on an installation lifecycle calculation of 5 years. The model is detailed hierarchically by a total of 3 levels (on the right only levels 1 and 2 are shown), each enabling a more detailed view on the subject. P. 12

13 VMS MCaaS Study July 2013 Methodology & Assumptions WHAT S IN WHAT S OUT The SAP TCO model includes all elements necessary to run SAP in the enterprise but excludes end user equipment and WAN network elements to reach them. The study also excludes initial business process (re)design efforts when implementing SAP for the first time. Those efforts are largely driven by the status and demand of an enterprise but not by the hardware, software or infrastructure used. However the cost for actually making the setup of system and applications is covered. Using cloud or outsourcing will effect the management structure. New roles for governance and a demand management are needed. On the other hand the need for management of internal employees and all the HR administration will decrease. So VMS considers this as cost neutral. There is an additional saving s potential triggered by HANA when migrating the BW functionality back into ERP. In order to provide a fair comparison, the study considers BW to be implemented and used for both scenarios. SAP maintenance is assumed as the standard 22% for SAP Enterprise Support. The comparison works for SAP landscapes which are around the size of the profile on slide 11 (up to 2 times more users or one third of the users), but not for SAP landscapes which are much bigger. SAPS or storage can grow or shrink by even a factor of 3.5. SAVINGS AS PERCENTAGES VMS shows savings as precise percentages (e.g. 22% savings on implementing SAP) rather than as a range (15%-30%). The VMS TCO model enables calculation of the typical savings for the specific defined profile, which is diluted by showing ranges. Of course, a new SAP customer might end up with slightly different percentages, since the real world implementation will not exactly match the prototyped profile. THE COMPARISON BASE MCaaS is compared against the typical scenario of systems in use today: various Linux, Windows-based and Unix implementations. Most of them are already using virtualization like AIX or VMware. Data for the comparison base comes from the VMS Benchmarkbase. The Benchmarkbase holds real life usage, quality and cost data of more than 2,900 SAP environments. It includes a broad variety of industries and geographies. It generally reflects the current dissemination of SAP s products in use. The comparison group does not include any on-premise mainframe-based installations. From a CAPEX point of view this would lead to tremendous savings when switching from mainframe to cloud. This is a reasonable step but rather rare. Therefore, the focus of this study is on mainstream effects, not on special or uncommon scenarios. P. 13

14 VMS AG Burgstrasse Heidelberg Office Berlin: Wörther Strasse Berlin Germany Copyright ff VMS AG All rights reserved, including those regarding reproduction, copying or other use or communication of the contents of this document or parts thereof. This publication may only be reproduced, processed using electronic retrieval systems, or copied in its entirety. We reserve the right to update or modify the contents. VMS references and indicates its own trademarks as is practical and appropriate to do so. Other trademarks used in this document are trademarks of their respective owners and will be respected by VMS. VMS registered trademarks are: VMS, the VMS logo, DNA-level benchmark, VMS Report, VMS Monitor, VMS Process Dashboard, VMS IT Dashboard, VM Solutions, Cloud Worthiness Index, CWI. Tel: Fax: [email protected] Photo Credits: Birkenzweig, eliteglobalbusiness, harry_nl, Nick Saltmarsh, pcshow98, twentyeight on Download April 2009 florianmarquart on Download Sept Royaltyfree images of istockphoto.