Upload
donna-schmidt
View
212
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Sap hs
Citation preview
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 2
The report and any findings and conclusions provided by SAP as part of this report(hereinafter collectively referred to as the “Report”) is provided for informational purposesonly to give addressees an impression of other customer upgrade projects and certainbenchmarking data related to such projects. With this publication, SAP AG does not give anykind of guidance or instruction, including but not limited to, guidance or instructions related tohow a customer may organize and execute an upgrade project, define infrastructure sizing,the duration and downtimes during the execution of such project, etc.
The Report is based upon the data provided by customers of SAP by using a standardizedquestionnaire and might be updated from time to time. SAP AG did not verify or revise norchange or modify this data. SAP AG does not take any responsibility or liability for theusability, accuracy, and correctness of the data upon which the benchmark is based andwhich is provided herein, excluding damages caused by SAP’s gross negligence or willfulmisconduct.
Disclaimer
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 3
Introduction to the SAP Upgrade Experience Database
Results: Upgrades to SAP ECC 6.0
Upgrade Experiences in Upgrade Projects toSAP ECC 6.0
1
2
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 4
A frequent request from SAP customers to SAP:
“We would like to see benchmarking data from other completed customerupgrade projects”
Strong Customer Demand for Upgrade ExperiencesGathered in Completed Upgrade Projects
SAP Upgrade Experience Databaseprovides orientation on
Project durationBusiness downtimeSatisfaction with the upgradeEtc.
The anonymous results are available in SAP Service Marketplace.
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 5
The online questionnaire can be accessed here.
Questionnaire Used for the SAP UpgradeExperience Database
Only upgrades of production systems are measured
A standardized questionnaire (online) is used for data collection (available in English andGerman versions)
The questionnaire is tailored to tracking upgrade experiences
Many questions can be answered by simple mouse clicks
At present, the database holds data for upgrades to SAP ECC 6.0 and for upgrades to SAPECC 5.0
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 6
Introduction to the SAP Upgrade Experience Database
Results: Upgrades to SAP ECC 6.0
Upgrade Experiences in Upgrade Projects toSAP ECC 6.0
1
2
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 7
Upgrades to SAP ECC 6.0: Number of Datasetsin Database by Source Release
168
30 32
103Total: 333 upgrades
SAP ECC 5.0
SAP R/3Enterprise
SAP R/3 4.6C
SAP R/3 <4.6CThe following slides provide the resultsfor the source releasesSAP R/3 Enterprise andSAP R/3 4.6C.
Results for the other source releaseswill be provided as the number ofdatasets in the SAP UpgradeExperience Database increases.
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 8
Upgrades to SAP ECC 6.0: Approach inUpgrades by Source Release
Approach in upgrade project
20%
4%
12%
64%Technicalupgrade only
Total: 103 upgrades
Functional upgrade
Strategic upgrade
Technical upgrade + subs.functional enhancements
Annotation:Technical upgrade + subs. functional enhancements =technical upgrade with subsequent implementation ofadditional functional or strategic enhancements
Functional upgrade = technical upgrade with additionalfunctional enhancements
Strategic upgrade = technical upgrade with strategicenhancements
Findings:
Most upgrade projects to SAP ECC 6.0 wereperformed using the upgrade approach “Technicalupgrade only.”
On the other hand, the diagrams on the next pageindicate that the new functionality provided withSAP ECC 6.0 is one of the main reasons toupgrade. This is in accordance with the experiencesof other SAP upgrade projects.
Approach in upgrade project
14%79%
5%2%
Technicalupgrade only
Total: 167 upgradesFunctional upgrade
Strategic upgrade
Technical upgrade + subs.functional enhancements
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 9
Upgrades to SAP ECC 6.0: Reasons forUpgrades by Source Release
Reasons for upgrade
0% 25% 50% 75% 100%
Replacement / elimination of modifications and / orcustomer specific development by SAP standard
System landscape consolidation / Integration ofindustry solutions
Business Innovation
Leverage latest technology
Legal compliance
End of mainstream or extended maintenance
Improve usability of existing solution
Functional requirements
based on 103 upgrades
How to read the charts:More than one reason per upgrade could be selected.The results for each reason category are standardizedto the number of upgrades of the given sample.Reasons for upgrade
0% 25% 50% 75% 100%
Replacement / elimination of modifications and / orcustomer specific development by SAP standard
System landscape consolidation / Integration ofindustry solutions
Business Innovation
Leverage latest technology
Legal compliance
End of mainstream or extended maintenance
Improve usability of existing solution
Functional requirements
based on 168 upgrades
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 10
Upgrade strategy
23% 77%Total: 166 upgrades
Downtimeminimized
Resourceminimized
Upgrade strategy
81%19% Total: 102 upgrades
Downtimeminimized
Resourceminimized
Upgrades to SAP ECC 6.0: Upgrade Strategyby Source Release (System Switch Upgrade)
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 11
Upgrades to SAP ECC 6.0: Overall Satisfactionwith Upgrade Approach by Source Release
Overall satisfaction with upgrade
33%
46%
15%6%
Total: 102upgrades
Very satisfied
More than satisfied
Satisfied
Less than satisfied
Overall satisfaction with upgrade
4%
18%
41%
36%
1%
Total: 165upgrades
Very satisfied
More than satisfied
Satisfied
Less than satisfied Not satisfied at all
Annotation:
The following satisfaction levels could beselected:
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
= Very satisfied
= More than satisfied
= Satisfied
= Less than satisfied
= Not satisfied at all
++
+
o
-
--
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 12
Upgrades to SAP ECC 6.0: Customers’Perceived Challenges by Source Release
Customers' perceived challenges
0% 25% 50% 75% 100%
End-user training
Minimize downtime
Efficient testing
Modification adjustment
IT infrastructure / sizing
Project Management
Justify budget for project / value proposition
Cost / effort estimation
based on 88 upgrades
Planning phase
Building Phase
How to read the charts:More than one category per upgrade could beselected.
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
Customers' perceived challenges
0% 25% 50% 75% 100%
End-user training
Minimize downtime
Efficient testing
Modification adjustment
IT infrastructure / sizing
Project Management
Justify budget for project / value proposition
Cost / effort estimation
based on 144 upgrades
Planning phase
Building Phase
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 13
Upgrades to SAP ECC 6.0: Selected CustomerQuotes
“We succeeded in making the upgrade a nonevent in the lives of the business users . . .”
“The upgrade to SAP ERP 6.0 provides us with the flexibility we need to master futurechallenges in the gas industry. . .”
“. . . The new architecture of SAP ERP allows us to collaborate more effectively andoperate more flexibly at a lower overall cost.”
“My IT operators are telling me already that the software is exceptionally easy to workwith.”
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 14
How to read the charts:Distribution of values: shows the frequency distribution of allmeasured values (in weeks, without cutting at the edges).Range of values: by cutting 10% of the number of values ateach end of the frequency distribution outlier values areexcluded. The length of each bar indicates the variance of themeasured values.
Median:
Upgrades to SAP ECC 6.0: Project Duration inWeeks by Source Release
Project duration in weeks
0 4 8 12 16 20 24 28 32 36 40 44 48 52Weeks
Max: 36,6
Median: 21,0
Min: 12,0
based on 168 upgrades
Range of values(w/o outlier values)
Project duration in weeks
0 4 8 12 16 20 24 28 32 36 40 44 48 52Weeks
Max: 31,9
Median: 18,0
Min: 8,1
based on 102 upgrades
Range of values(w/o outlier values)
Distribution of values
Question asked:“Please specify the duration of your upgrade project up to theinitial go-live (in weeks).”
Distribution of values
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 15
Upgrades to SAP ECC 6.0: Duration of ProjectPhases in Weeks by Source Release
Duration of single project phases in weeks
2,0
3,0
6,0
2,0
2,0
18,0
0 5 10 15 20 25
Production cutover & support phase
Final preparation for cutover phase
Upgrade realization phase
Upgrade blueprint phase
Project preparation phase
Weeks
Project duration (total)
How to read the charts:For each project phase, the median value of all answers isshown. In a project, overlaps or gaps between the projectphases are possible.Median:
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
Question asked:“Duration of project phases according to the SAP UpgradeRoadmap (in weeks).”
Duration of single project phases in weeks
2,0
3,0
8,0
3,0
3,0
21
0 5 10 15 20 25
Production cutover & support phase
Final preparation for cutover phase
Upgrade realization phase
Upgrade blueprint phase
Project preparation phase
Weeks
Project duration (total)
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 16
Business Downtime* in Hours by Source Release,without Unicode Conversion
Business downtime* in hours
0 12 24 36 48 60 72 84 96 108Hours
Max: 65,0
based on 91 upgrades
Median: 34,0Range of values
Min: 15,0
Distribution of values
Business downtime* in hours
0 12 24 36 48 60 72 84 96 108Hours
Max: 86,2Min: 22,9
Median: 48,0 Range of values
based on 140 upgrades
* Annotation:Business downtime = total time (planned and unplanned) that the system / solution is notavailable for end users. This includes the technical downtime plus the time necessary forthe data backup, final tests, etc., before the productive environment is released for endusers.
Question asked:“Assuming a 24x7 hours operation of the production system, howmany hours was the production system unavailable for the endusers?”
Findings:The business downtime was <= 48 hours (2 days)SAP R/3 Enterprise: for 74% of all measured upgrade projects
(for 88% <= 60 hours)SAP R/3 4.6C: for 53% of all measured upgrade projects
(for 65% <= 60 hours)
How to read the charts:Distribution of values: shows the frequency distribution of allmeasured values (in hours, without cutting at the edges).Range of values: by cutting 10% of the number of values ateach end of the frequency distribution outlier values are excluded.The length of each bar indicates the variance of the measuredvalues.
Median:
Only upgrades that followed the “Downtime minimized“ upgradestrategy were taken into account. No Unicode conversion wasperformed.
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C Distribution of values
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 17
Upgrades to SAP ECC 6.0: “Modules*” (BusinessScope) Used in the upgraded ERP System
Modules* used in ERP component
0%
25%
50%
75%
100%
CO FI HR LE MM PM PP PS QM SD
based on 102 upgrades
* Annotation:Despite the fact that SAP R/3 modules are no longer applicable in SAP ECC6.0, customers were asked to describe the business functionality of theupgraded SAP software in terms of the classic SAP R/3 modules (e.g., “FI”) inorder to provide a comparison with the business scope of the upgraded SAPsoftware.
Modules* used in ERP component
0%
25%
50%
75%
100%
CO FI HR LE MM PM PP PS QM SD
based on 167 upgrades
Conclusion / findings:A broad coverage of components, and therefore a widescope of business functionality, can be observed in theupgraded systems.
How to read the charts:More than one SAP R/3 module could be selected:the results for each module are standardized to the number ofupgrades of the given sample.
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 18
Upgrades to SAP ECC 6.0: Database Size in GBby Source Release
Database size in GB
0 1000 2000 3000 4000 5000 6000GB
Max: 1870Min: 122
Median: 375
based on 102 upgrades
Range of values(w/o outlier values)
Database size in GB
0 1000 2000 3000 4000 5000 6000GB
Max: 1340Min: 78
Median: 340 Range of values(w/o outlier values)
based on 163 upgrades
Distribution of valuesQuestions asked:“What was the used database size in your productive environment(in GB)?
How to read the charts:Distribution of values: shows the frequency distribution of allmeasured values (in GB, without cutting at the edges).Range of values: by cutting 10% of the number of values at eachend of the frequency distribution outlier values are excluded. Thelength of each bar indicates the variance of the measured values.
Median:
Findings:SAP R/3 Enterprise: 80% of the upgrades DB size <1000 GB
56% of the upgrades DB size < 500 GBSAP R/3 4.6C: 86% of the upgrades DB size <1000 GB
62% of the upgrades DB size < 500 GB
Distribution of values
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 19
Upgrades to SAP ECC 6.0: Number of Projectsby Number of Users AND Source Release
Number of users
9%
17%
17%31%
15%5%5%
1%
Total: 99upgrades
1 - 99
100 - 249
250 - 499
500 - 999
1000 - 1999
2000 - 4999
5000 - 999910000
Number of users
3%1%
15%
18%
19%20%
16%
9%
Total: 166upgrades
1- 99
100 - 249
250 - 499
500 - 999
1000 - 1999
2000 - 49995000 - 9999 10000
SAP
R/3
Ent
erpr
ise
SAP
R/3
4.6
C
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 20
Online Feedback Survey
Your opinion is important to us!
With your feedback we want to ensure that we meet your expectations with thecontent and structure of this report. Your feedback would be very helpful andvaluable for us.
The completion of this short online feedback survey should take no more than afew minutes of your time.
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 22
higher half of the sample (50%)lower half of the sample (50%)
Median
1 2 3 4 5 6 7 8 9 10 11
MedianExample:
Median = the number separating the higher half of a sample from the lower half. The medianof a list of values can be found by arranging all values from lowest value to highest value andpicking the middle one. The median is less sensitive regarding outlier values than thearithmetic mean.
Bar chart as used in this report: the lowest / highest values are cut off (~10% at each endof the sample).
1 2 3 4 5 6 7 8 9 10 11
Min: 2
Median: 6
Max: 10cut offcut off
(back)
SAP AG 2009, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 23
Copyright 2009 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 changedwithout 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 theirrespective 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 andassociated 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials 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 durchSAP 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 Servicessowie 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ähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. 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 anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie 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 Verwendungdieser 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 Hotlinkszugreifen, 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 überInternetseiten Dritter ab.Alle Rechte vorbehalten.