TCO Study on VblockAbout the impact of Vblock on the TCO of running SAP
May 12, 2010
VMS AG
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
Summary Introduction
• In this study, VMS compiles the research about one of the latest concepts in bringing virtualization technology and services into the SAP market space: Vblock.
• The comparison of Vblock to today’s existing SAP landscapes is built on the SAP TCO model which includes all components (hardware, software, operations) and the complete life cycle (plan purchase install roll out
PURPOSE AND CONTENT METHODOLOGY
May
20
10
• VMS compared SAP on Vblock with other options to run an SAP landscape.
• Origin of the savings are the steps shown below, developing from a traditional non-virtualized environment into a Vblock architecture:
complete life cycle (plan, purchase, install, roll-out, operate, maintain, fix, change and improve) of SAP systems. It needs to be stressed that “total” includes the application related cost as well, not only data center cost.
• The TCO of existing landscapes is taken from the VMS Benchmarkbase, which holds more than 2,000 SAP y
on V
blo
ck -
, ,environments with their actual cost.
• TCO for Vblock is extrapolated from the features of the offering derived as well from the VMS Benchmarkbase.
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
GBase Cost Level Traditional Setup
Typical average traditional Unix-like or
Windows based SAP l d
x86 basedcost level
With t i t li ti
Virtualized Environment
Virtualized EnvironmentSingle source for purchasing and
support,h
V
Con
tent
and
Des
ign
© 2
P. 3
SAP landscape (non virtualized)
Without virtualization homogenous management tool set
Key Findings13% Cost Reduction on Running SAP
VMS expects that using the Vblock infrastructure lowers TCO of running SAP by 12-14%.
Main drivers for the TCO reduction are:
• The flexibility of the approach reduces effort from the start on Planning
SAP TCO model (Level 1)
Vblock triggered savings
Impact on SAP TCO
Hardware/Software Investment 9 - 19%
May
20
10
The flexibility of the approach reduces effort from the start on. Planning does not need to decide for fixed hardware assignments for years, changes are easy to accomplish.
• Vblock virtualization brings better utilization of hardware, reduces power and floor space consumption. But compared to savings in the area of upgrade, rollout and improvement projects, the latter have much more impact to SAP system TCO
Implementation 22 - 32%
Hardware/Software Ongoing Cost 2 - 5%
Operations 3 - 4%
C ti I t y on
Vb
lock
-
impact to SAP system TCO.
• Flexibility extends in project scenarios like rollout, upgrade and change: Building additional test systems, resetting test systems on the fly, adding training systems requires no change in hardware but only reconfiguration and assignment of resources.
• Decoupling SAP systems from hardware by virtualization enables more
Continuous Improvement Projects 20 - 25%
Upgrade Projects 26 - 36%
Table 1: Overall TCO Impact
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
• Decoupling SAP systems from hardware by virtualization enables more focused planning of each: the technical infrastructure (Vblock building blocks) and the SAP systems
• Savings in the area of ongoing cost are smaller, since the majority of the effort there is related to the SAP application itself, which is not affected so much by Vblock.
Vblock is a technology and architecture offering. And it makes better use of hardware investment as expected.
But the major savings when looking at Total Cost of Ownership (TCO) are in the area of time and effort for upgrade and continuous change projects.
V
Con
tent
and
Des
ign
© 2
• While the overall complexity of IT landscapes grows with the wealth of business processes supported, Vblock reduces complexity in building infrastructure and managing SAP systems.
• A homogenous set of management software is integral part of Vblock and is announced to be extended.P. 4
This is important because overall more than 80% of today’s IT cost is not systems but system and application management.
Who will benefitDynamic comes in very different time dimensions
Dynamics Effect Who benefits
It is easy to imagine and approved by the figures that more dynamic SAP environments benefit more from Vblock than rather static environments.
May
20
10
milliseconds to seconds
Virtualization helps to exploit machine resources better and to potentially gain better response times
Almost everybody
minutes to hours Virtualization allows to provide significantly more resources for typical peak operations like ERP runs,
About 60% of all SAP using companies have such peak operationsy
on V
blo
ck -
HR salary calculations, month end closure or building BW cubes Industry-wise, these are typically industries
with large customer databases like Utilities, Telecoms, Retail, Banking, Insurance
days to weeks TCO-wise this is the most important effect. While the more technical short time scale effects save on
About 78% of all SAP using companies face continuous changes in their landscape due to V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
hardware cost, the capability of super fast provisioning of new SAP instances or systems brings down operational (FTE) cost, which becomes the more and more dominant part in each TCO framework
g prollouts, functional extensions, release changes, process automation, etc.
Industry-wise, VMS Benchmarkbase shows this to be a challenge especially in Telecom, Services and regulated environments like
V
Con
tent
and
Des
ign
© 2Healthcare
months to years Standardized hardware (building block model of Vblock on x86) can be easily exchanged between SAP and non-SAP environments
Companies in large scale growth, shrink, split & merger situations
P. 5 Table 2: Dynamics of SAP
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
FocusThe purpose of this study
BACKGROUND
• VMS has analyzed more than 2,000 SAP systems by the means of comparison to Best Practice.
• VMS best practice analyses are based upon detailed measurement data, collected by the VMS May
20
10
DataCollector (installed on the customers’ SAP systems), along with cost data from the VMS AdaptiveTCO workbench.
WHAT WE AIM AT HERE
Th l f th t d i t l b t t ti l b fit f th Vbl k hit t y on
Vb
lock
-
• The goal of the study is to learn about potential benefits of the Vblock architecture.
• The term „potential“ is used, because Vblock has not yet been rolled out in numbers and for a TCO-relevant period of time to enable a study “old” vs. “new” based on real life measurement.
• However, Vblock brings elements together which are well known to VMS in their individual impact on the TCO of running SAP landscapes, such as:V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
g p ,
• Using x86 (Intel architecture 64bit systems)
• Using virtualization on the level of operating systems, networks and storage
• Using integrated sets of management software to administrate virtual environments
V
Con
tent
and
Des
ign
© 2
P. 7
• The difference made by Vblock is that it brings these elements together into a homogeneous approach.
• The impact of Vblock on TCO is highlighted by comparing a traditional infrastructure setup with a Vblock setup. This will be explained on the following pages on methodology in more detail.
SAP TCO ModelSAP TCO model covers the whole SAP lifecycle
• The basis of this study is the SAP TCO model.
• It covers the total cost (TCO = total cost of ownership) of the entire lifecycle of SAP software.
It i t t d hi hi ll b t t l f 3 l l ( th May
20
10
• It is structured 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.
• In order to understand the impact of Vblock better, VMS even drilled down into another VMS-defined level of detail where applicable. (see detailed findings pages) The drill-y
on V
blo
ck -
where applicable. (see detailed findings pages) The drilldown helps readers to understand their flow of resources when running SAP.
• The study covers CAPEX and OPEX elements. The actual IT cost situation makes OPEX the more relevant area to focus at.
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
• The study is based on an installation lifecycle calculation of 5 years.
V
Con
tent
and
Des
ign
© 2
P. 8 Table 3: SAP TCO Model
Methodology FAQ
WHAT’S IN – WHAT’S OUT
• The SAP TCO model includes all elements necessary to run SAP in the enterprise but exclude end user equipment and WAN network elements to reach them.
THE COMPARISON BASE
• Vblock is compared against the typical scenario of systems in use today: various Unix, Linux and Windows-based implementations with a variety of M
ay 2
01
0
• The study as well 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.
• Vblock defines a change in landscape architecture. Such a change
p ydatabase products running on dedicated servers.
• Data for the comparison base comes from the VMS Benchmarkbase. The Benchmarkbase holds real life usage, quality and cost data of more than 2,000 SAP environments. It includes a broad variety of i d t i d hi It fl t tt ll y
on V
blo
ck -
triggers the need for education of staff. A one time effort. Since the steepness of the learning curve is very individual and depends where the individual IT team is coming from, it is not considered in this TCO model. The impact of the change is well addressed by offering management tools. In the past the biggest stumbling blocks have been new technologies without appropriate tools – which Vblock avoids explicitly.
industries and geographies. It reflects pretty well the current dissemination of SAP’s products in use. The reference group’s split is shown on the next slide.
• The comparison group does not include any mainframe-based installations From a CAPEX point V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
GADVANCED STORAGE FEATURES
• Modern storage equipment comes with a lot of software which can reduce TCO significantly. This applies especially for the storage types which EMC supports for Vblock architecture. Such features are e.g. de-d plication fo data ol me ed ction
mainframe based installations. From a CAPEX point of view this would lead to even more tremendous savings when switching from mainframe to x86 based hardware. We see this step as reasonable but rather rare and we wanted to focus on mainstream effects, not on specialties in this study.
V
Con
tent
and
Des
ign
© 2duplication for data volume reduction, …
• However these features are not reserved for Vblock and might as well be used in Unix-like or traditional x86 environments. Since this is a study about Vblock, we tried to avoid mixing all effects and did not take such features into account that are available outside Vblock as well.
P. 9
Reference GroupSplitting up the members of the VMS Benchmarkbase
Revenue of companies:
Revenue (billion €) Share
The reference group for this study represents quite well the SAP penetration of these industries (exception is IT –because IT providers are more likely customers of VMS for optimization of SAP):
May
20
10
< 0.1 2%
< 0.25 2%
< 0.5 9%
Reference Group Share
Manufacturing 41%
Utilities 13%y on
Vb
lock
-
< 1 8%
< 2 11%
< 5 22%
Finance 5%
Services 12%
IT 13%VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
< 10 9%
< 25 22%
< 50 6%Table 5: Distribution according to the number of systems
HealthCare 9%
Others 7%
V
Con
tent
and
Des
ign
© 2
Table 4: Distribution according to the revenue of companies
P. 10
> 50 9%
Forming ProfilesTypical SAP landscapes are defined as profiles
STARTING POINT
• Although SAP is a standard software and the TCO model is universally valid, each single company and each SAP installation is unique.
May
20
10
SOLUTION
• For the purpose of the study, VMS defined three different profiles which:
• represent typical SAP customer landscape componentsy on
Vb
lock
-
• represent typical SAP customer landscape components
• provide criteria to explain the differences
• are based upon real data, commonly found.
• The TCO model is a more abstract model to group different cost aspects
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
over the SAP lifecycle. With the help of these three company profiles, readers may find themselves within the model more easily.
V
Con
tent
and
Des
ign
© 2
P. 11
Profiles for TCO Study Three groups: Global player, local player, SME
Global Player(Affiliated Group)
Local Player*(Large Company)
SME(Mid‐sized Company)
Revenue > 10 Bill. € < 10 Bill. € < 1 Bill. €
May
20
10
Employees > 50,000 < 50,000 < 5,000
Organization Holding company with several subsidiaries 1 company 1 company
Concurrent user 2,500 1,500 500
y on
Vb
lock
-
Systems**4 SAP systems:
ERP/BW/CRM/Portal(Part of all SAP systems)
4 SAP systems: ERP/BW/CRM/Portal
(Part of all SAP systems)
2 SAP systems:ERP/BW
Named user 14,000 7,500 2,500
Users/day 5,000 3,000 1,000VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
/ y , , ,
Database [TB], P systems only*** 12 5 2.5
Data Center RAID5, mirrored on a distant (>10 km) location
RAID5, mirrored on a distant (>10 km) location RAID5, mirrored
V
Con
tent
and
Des
ign
© 2
P. 12
SAPS 247,000 114,000 54,000
* Local Player means that the major part of the company is located in one country.
** Only part of the whole SAP landscape is focused, because this will be the bundle for Vblock
*** Assumption: Q-systems need the same space as the P-systems
Table 6: Prototype Profiles
Methodology FAQ II
PERCENTAGES
• VMS shows savings as precise percentages (e.g. 22% savings on implementing SAP for a global player) rather than as a range (15%-30%).
May
20
10
• The VMS TCO model allows to calculate the typical savings for the specific defined profile, which we don’t want to dilute by showing ranges. Of course a new Vblock user might come up with slightly different percentages in the end, since the real world implementation will not exactly be identical to the prototyped profile.
y on
Vb
lock
-V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
V
Con
tent
and
Des
ign
© 2
P. 13
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
SAP TCO Vblock Level 1 AggregationOverview of TCO Lifecycle with Vblock-triggered Savings
SAP TCO model Vblock triggered savings
Level 1 Global player Local player SMEMay
20
10
Hardware/Software Investment 19% 14% 9%
Implementation 22% 24% 32%
y on
Vb
lock
-
Hardware/Software Ongoing Cost 5% 3% 2%
Operations 4% 3% 3%
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
GContinuous Improvement Projects 20% 18% 25%
Upgrade Projects 26% 24% 36%
T bl 7 L l 1 A ti
V
Con
tent
and
Des
ign
© 2
P. 15
Table 7: Level 1 Aggregation
SAP TCO Vblock Level 2 AggregationOverview of TCO Lifecycle with Vblock-triggered Savings
SAP TCO model Vblock triggered savings
Level 1 Level 2 Global player Local player SME
Hardware/Software Investment Technical Infrastructure 38% 35% 30%
System Software - - -
May
20
10
Application Software - - -
Implementation Process Design 70% 67% 59%
Organizational Change - - -
Technical Setup 87% 85% 78%
Business Setup - - -y on
Vb
lock
-
Project Management - - -
Testing 35% 30% 23%
Training 35% 30% 23%
Hardware/Software Ongoing Cost Technical Infrastructure 23% 17% 12%
System Software - - -VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
System Software - - -
Application Software - - -
Operations System Operations 22% 19% 17%
Application Operations - - -
Continuous Improvement Projects Continuous Business Improvement 18% 17% 26%
V
Con
tent
and
Des
ign
© 2
P. 16
Continuous Technical Improvement 50% 50% 50%
Rollouts 22% 18% 10%
Upgrade Projects Application Upgrade 19% 17% 26%
System Upgrade 81% 75% 64%
Table 8: Level 2 Aggregation
Soft FactsQuality benefit and savings beyond the SAP cost model
The SAP TCO model contains SAP related costs only. Here we mention some other cost related facts which do not affect the SAP TCO but affect business process cost and quality factors in the enterprise:
• Less and reduced planned downtimes for maintenance activities May
20
10
(e.g. due to VMware VMotion).
• Increased security and compliance due to standardization and template building.
• Reduced complexity due to preconfigured and centralized IT resources leads to more standardized IT services. Standardized services tend to have better y
on V
blo
ck -
to more standardized IT services. Standardized services tend to have better quality and leave less room for failure.
• Saving complete configurations for later use (e.g. in case of disaster recovery) reduces risk and shortens downtimes.
• SLA Management is better supported by resource configuration, i i i t i d tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
provisioning, metering and reporting.
• All current applications that run in a VMware environment also run in a Vblock environment. That means in addition to SAP almost all other IT applications can be hosted and operated on a Vblock as well – which leads back to reduced complexity in the IT architecture.
V
Con
tent
and
Des
ign
© 2
P. 17
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
Hardware/Software Investment
SAP TCO model VMS Vblock triggered savingsIssue
Level 1 Level 2 Level 3 Details Global player Local player SMEHardware/Software Investment
Technical Infrastructure
Computing Hardware Application Server 86% 85% 77% 1, 2, 3, 4
May
20
10
Database Server 86% 85% 77% 1, 2, 3, 4Storage 10% 5% 0% 1, 2, 3Backup Hardware 61% 64% 63% 5, 6Print Hardware - - -Archiving Hardware - - -y
on V
blo
ck -
gNetwork - - -End-User Environment - - -
System Software
Computing Software Operating System - - -
ent
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
Database - - -Tools - - -Backup Software - - -Print Software - - -
h f e/Sof
twar
e In
vest
meV
Con
tent
and
Des
ign
© 2
P. 19
Archiving Software - - -End-User Environment - - -
Application Software Licenses - - -
Tabl
e 9:
Har
dwar
e
Hardware/Software InvestmentPotential Cost Reduction: up to 19%
Issue # Issue Area Effect
(1) Planning Simple resizing and reconfiguration based on real demand lowers the demand on “requirements prediction” capabilities of the planning team
(2) Pre-integrated Introduction of pre-engineered tested and validated Vblock units with defined May
20
10
(2) Pre integrated package
Introduction of pre engineered, tested, and validated Vblock units with defined performance, capacity and availability – no testing or proof of concept are required
(3) Investment Cost/performance efficient Intel-based Cisco UCS blades
(4) System availability
Built-in cluster-like functionality (VMware High-Availability & VMware Fault Tolerance) with next to zero administrative work replaces the need for cluster solutions based on
h dy on
Vb
lock
-
spare hardware
(5) SystemLandscapeRecovery
Integrated backup concept through close integration of backup infrastructure within Vblock. Consistent backups cross SAP landscapes out of the box
High efficiency for backup and recovery with EMC Avamar Virtual Edition for VMware
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
Disaster recovery requirements are fulfilled with EMC RecoverPoint. Capabilities include policy based management, application integration and bandwidth reduction
(6) Softwarelicense cost
Reduction in cost for third-party virtualization management tools. Additional cost for VMware and EMC Ionix.Baseline: neutral effect on cost
V
Con
tent
and
Des
ign
© 2
P. 20
Implementation
SAP TCO model VMS Vblock triggered savingsIssue
Level 1 Level 2 Level 3 Details Globalplayer
Local player SME
Implementation Process Design Planning of Infrastructure
*Process Design is limited here to the technical M
ay 2
01
0
Infrastructure70% 67% 59% 1, 5Blueprint/
Conceptual Design
Organizational Change
Change Management - - -
technical components (infrastructure and landscape blueprint) but omits all kind of business process (re)design efforts of the company when y
on V
blo
ck -
Technical Setup Installation 87% 85% 78% 3, 4Technical Configuration - - -
Technical Operations - - -
starting to implement SAP
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
Technical Conceptual Design
- - -
Implementation Business Setup All level 3elements - - -
emen
tatio
n
V
Con
tent
and
Des
ign
© 2
P. 21
Project Management
All level 3elements - - -
Testing Testing35% 30% 23% 2, 4
Training Training Tabl
e 10
:Im
ple
ImplementationPotential Cost Reduction: 23% - 32%
Issue # Issue Area Effect
(1) Planning Reduced efforts for planning, blueprint and conceptual design of the SAP infrastructure as Vblock is already pre-configured regarding compute, storage and
t k O l l i f th i t ti i t th i ti IT l d i i dMay
20
10
network. Only planning for the integration into the existing IT landscape is required
(2) Installation process
Simple setup, installation and reconfiguration of virtual machines
Quick and easy installation of SAP systems due to the usage of pre configured y on
Vb
lock
-
Quick and easy installation of SAP systems due to the usage of pre-configured templates
(3) SAP system management
Creation of individual templates to provide test- and training systems
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G(4) Simplificationof hardware landscape
Surrounding systems of a SAP landscape (e.g. FTP Server, Print Server, …) can be hosted and operated on Vblock as well
(5) S t EMC I i U ifi d I f t t M i l i t t ll Vbl k
V
Con
tent
and
Des
ign
© 2
P. 22
(5) System management
EMC Ionix Unified Infrastructure Manager as a single point to manage all Vblock components
Hardware/Software Ongoing Costs
SAP TCO model VMS Vblock triggered savingsIssue
Level 1 Level 2 Level 3 Details Global player Local player SMEHardware/Software Ongoing Cost
Technical Infrastructure
Computing Hardware Application Server 45% 40% 33% 1,2,3,4,5
May
20
10
Ongoing CostDatabase Server 32% 30% 27% 1,2,3,4,5Storage 10% 5% - 2Backup Hardware 50% 54% 47% 1, 2Print Hardware - - -y
on V
blo
ck -
Archiving Hardware - - -Network - - -End-User Environment - - -
System Software Computing SW Operating System - - - g Cos
t
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
y p g p g yDatabase - - -Tools - - -Backup Software - - -Print Software - - -
h f re/S
oftw
are
Ong
oingV
Con
tent
and
Des
ign
© 2
P. 23
Archiving Software - - -End-User Environment - - -
Application Software
Maintenance Fees - - -
Tabl
e 11
: H
ardw
ar
Hardware/Software Ongoing CostsPotential Cost Reduction: up to 5%
Issue # Issue Area Effect
(1) Volume reduction
Lower hardware and software maintenance efforts as result of significant reduced number of hardware system piecesM
ay 2
01
0
(2) Subsequentinvestments
The flexibility of Vblock in providing compute resources prevents immediate additional investments due to typical slighter changes in hardware needs by individual systems
y on
Vb
lock
-
(3) Homogeneous extension path
The ability to expand the capacity of Vblock infrastructure without re-arranging existing landscape elements. Vblocks and Vblock components can be combined
(4) Investment protection
Changes in the SAP system layout are covered by changes on the virtualized OS level without the need to exchange hardware Additional resource demands are met by V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
protection without the need to exchange hardware. Additional resource demands are met by additional Vblock elements
(5) Green IT Lower energy consumption and reduced need for data center space
V
Con
tent
and
Des
ign
© 2
P. 24
Operations
SAP TCO model VMS Vblock triggered savingsIssue
Level 1 Level 2 Level 3 Details Globalplayer
Local player SME
Operations System Operations System Monitoring Storage, Server, OS 66% 52% 30% 1,2,4,6,7
May
20
10
Database - - -SAP Basis - - -
System Administration Storage, Server, OS 78% 63% 54% 1 – 7Database 73% 69% 68% 1,2,3,7SAP Basis 0% 0% 5%y
on V
blo
ck -
Backup - - -Archive - - -User Administration - - -
System Problem Management Storage, Server, OS 69% 52% 40% 1 – 7
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
ManagementDatabase 18% 21% 23% 1,2,3,7SAP Basis, Early Watch 0% 0% 2% 6
Software Change Management - - -
atio
ns
V
Con
tent
and
Des
ign
© 2
P. 25
System Service Desk & Incident Mgt. - - -
General/Administrative Costs - - -
Operations Application Operation All level 3 elements - - -
Tabl
e 12
: O
pera
OperationsPotential Cost Reduction: up to 4%
Issue # Issue Area Effect
(1) Flexibility on resource level
Adding/removing compute resources or storage to virtual machines based on demand
(2) Flexible Adding/removing virtual machines and SAP systems with them based on demandMay
20
10
(2) Flexibleprovisioning of systems
Adding/removing virtual machines and SAP systems with them based on demand
(3) Reduction of planned downtime
Due to virtualization, e.g. live migration without downtime from one physical host to another – VMware VMotion
y on
Vb
lock
-
(4) Cost of overtime
Infrastructure maintenance activities can be delivered to a large extend during regular working hours
(5) Complexityreduction
No H/A cluster tests are required(which is typically very time consuming and error-prone)
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
(6) Systemmanagement
Reduced system management efforts through central admin tool EMC Ionix UIM. UIM manages the configuration, provisioning and compliance of a Vblock and multiple mixed Vblocks
(7) Complexityreduction
A pre-configured and standardized Vblock configuration when combined with unified support and end-to-end vendor accountability reduces the efforts for problem management as the variety of interactions to solve problems is smaller
V
Con
tent
and
Des
ign
© 2
P. 26
management as the variety of interactions to solve problems is smaller. There is no ‘ping-pong’ between infrastructure suppliers for root cause analysis and problem resolution
Continuous Improvement Projects
SAP TCO model VMS Vblock triggered savingsIssue
Level 1 Level 2 Level 3 Details Globalplayer
Local player SME
Continuous Continuous May
20
10
Improvement Projects
Business Improvement
Process Design - - -
Organizational Changes - - -
Technical 90% 85% 80% 1 2y on
Vb
lock
-
Setup 90% 85% 80% 1, 2
Business Setup - - -
Interfaces - - -
Project M t - - - vem
ent
Proj
ects
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
Management
Testing35% 30% 23% 3
Training
Continuous Technical
Continuous Technical 50% 50% 50% 1, 2, 4, 5 C
ontin
uous
Im
provV
Con
tent
and
Des
ign
© 2
P. 27
Technical Improvement
Technical Improvement
50% 50% 50% 1, 2, 4, 5
Rollouts Rollouts 22% 18% 10% 2, 4, 5 Tabl
e 13
:
Continuous Improvement ProjectsPotential Cost Reduction: 18% - 25%
Issue # Issue Area Effect
(1) Planning Reduced efforts for planning, blueprint and conceptual design of the SAP infrastructure as Vblock is already pre-configured regarding compute, storage and networkM
ay 2
01
0
network
(2) Flexibility Adding/Removing compute resources or storage to virtual machines based on demand
Adding/Removing virtual machines based on demand
y on
Vb
lock
-
Quick and easy installation of SAP Systems due to the usage of pre-configured templates
(3) IT processstandardization
Creation of (individual) templates to provide test- and training systems
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G(4) Homogeneouslandscape while expanding
Surrounding systems of a SAP landscape (e.g. FTP Server, Print Server, …) can be hosted and operated on Vblock as well
(5) System Reduced system management efforts through central admin Tool EMC Ionix UIM.
V
Con
tent
and
Des
ign
© 2
P. 28
( ) ymanagement
y g gUIM manages the configuration, provisioning and compliance of a Vblock and multiple mixed Vblocks
Upgrade Projects
SAP TCO model VMS Vblock triggered savings
IssueLevel 1 Level 2 Level 3 Details Global
playerLocal player SME
May
20
10
Upgrade Projects
Application Upgrade Process Design - - -
Organizational Changes - - -
T h i l y on
Vb
lock
-
Technical Setup 90% 82% 76% 1, 4, 5
Business Setup - - - 3, 4
Interfaces 15% 15% 15% 3, 4
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
Project Management - - -
Testing35% 30% 23% 2
Training
Upg
rade
Pro
ject
s
V
Con
tent
and
Des
ign
© 2
P. 29
System Upgrade
System Upgrade 81% 75% 64% 3, 4, 5, 6
Tabl
e 14
:
Upgrade ProjectsPotential Cost Reduction: 24% - 36%
Issue # Issue Area Effect
(1) Planning Reduced efforts for planning, blueprint and conceptual design of the SAP infrastructure as Vblock is already pre-configured regarding compute, storage and networkM
ay 2
01
0
network
(2) Flexibility Quick and easy provisioning of test- and training systems on demand
(3) Speed Reduction of upgrade runtimes due to options for adding temporary additional y on
Vb
lock
-
( ) p pg p g p yapplication servers or compute resources
(4) Options to react
Fallback scenarios (return to original state in case of failure) available right out of the box
f fVM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
(5) IT processstandardization
Simple expansion and scaling of SAP instances in case of higher demand due to increasing number of users or new functions based on the ability to expand the capacity of Vblock infrastructures as the architecture is very flexible and extensible
(6) Investment protection
Vblocks and Vblock components can be combined in extensions. That protects any Vblock investment in case of changing demands which require real additional
V
Con
tent
and
Des
ign
© 2
P. 30
protection Vblock investment in case of changing demands which require real additional hardware resources
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
Current Limitations & CaveatsVirtualization becomes broadly adopted
• The acceptance of virtualization in the marketplace is overwhelmingly positive. Rarely have we seen a new technology which was adopted faster by their consumers than by the vendors.
• When running SAP in a virtualized environment, we see as of today two areas May
20
10
which we have to keep in mind:
• Application server virtualization does not fully benefit from dynamic assignment of memory. While adding CPU power boosts a server and reduction of CPU works as well, memory is (with small exceptions) assigned statically between 2 boot cycles. This limitation is expected to be removed within 2 years On the scale of hours or days (see table y
on V
blo
ck -
be removed within 2 years. On the scale of hours or days (see table Dynamics of SAP), memory virtualization works very well.
• Regarding DB Server virtualization, users must take support regulations into account. SAP and their database partners support in general productive use in virtualized environments. Details can vary however by product used. E.g. IBM supports DB2/LUW for VMware environments
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
G
essentially in the same way as they do for physical environments. Oracle’s support has some qualifiers and limitations. Customers certainly need to consult the appropriate SAP support notes to find out the support details for their configurations.(This remark is subject to frequent changes in the support policy of the vendors. Check SAP Notes for details)
V
Con
tent
and
Des
ign
© 2
P. 32
• Vblock combines the effort of different vendors (Cisco, EMC, VMware) to offer a homogenous solution. Single source for provisioning and support is essential.
• The TCO consideration for this study is based on the currently (April 2010) available technology and support matrix for SAP products.
► Summary
May
20
10
► VMS Study MethodologyThe SAP TCO ModelCustomer Profiles
► Vblock SavingsL l 1 A iy
on V
blo
ck -
Level 1 AggregationLevel 2 Aggregation
► Vblock Savings in DetailHardware/Software InvestmentI l t tiV
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
ImplementationHardware/Software Ongoing CostOperationsContinuous Improvement ProjectsUpgrade Projects
V
Con
tent
and
Des
ign
© 2Upgrade Projects
► Conclusion► About VMS
About VMSWho we are
2002• VM Solutions GmbH, Heidelberg• VMS = Value Management Solutions = IT creates value• Creation of a new methodology:
DNA level benchmark to measure and compare complex systems May
20
10
2006DNA-level benchmark to measure and compare complex systems
• Germany’s most active benchmarking company• > 1,000 SAP systems optimized• > 50 international customers
New service: Optimizing SAP licensesy on
Vb
lock
-
2007
2008
• New service: Optimizing SAP licenses
• Advisory Service: SAP know how - best practice processes• > 1,600 years of SAP data collected• VMS Benchmarkbase is the largest repository of SAP usage worldwide • CAGR 40%V
MS
TC
O S
tud
y
2010
ff.
by
VM
S A
G
2008
2009
• CAGR 40%
> 100 international customers Conversion to VMS AG
V
Con
tent
and
Des
ign
© 2
P. 34
• > 2,000 measured SAP systems• Launch of VMS Process Dashboard
Who are VMS Customers?Coverage of various industries and business models
CPG
Process manufacturingM
ay 2
01
0
manufacturing
Pharmaceuticals
Energy / Infrastructurey
on V
blo
ck -
Manufacturing
Automotive / Aerospace
VM
S T
CO
Stu
dy
2010
ff.
by
VM
S A
GRetail
Finance
V
Con
tent
and
Des
ign
© 2
P. 35
Services
IT / IT services
VMS AGBurgstraße 6169121 Heidelberg
Copyright © 2002-2010 VMS AG www.vms.net
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.
Germany
www.vms.net
Phone: +49 62 21 4 38 52-0VMS 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.
Photo Credits: Birkenzweig, eliteglobalbusiness, harry_nl, Nick Saltmarsh, pcshow98, twentyeight on www.flickr.com - Download April 2009 - Royalty-free images of iStockphoto®
Facsimile: +49 62 21 4 38 52-22 E-Mail: [email protected]