- SAP introduced a Rapid Deployment Solution, which does nothing to speed project implementations.
- Why the RDS is specifically designed to deceive customers.
Introduction to the SAP RDS
In this article, we will cover the SAP RDS or the Rapid Deployment Solution. SAP proposes that using the RDS speeds implementation, however in this article we will review if this is true.
What Are the SAP RDSs?
There currently roughly 120 RDSs, but this number is misleading as many of the RDSs are still being developed, although it is difficult to be sure if all the RDSs will continue to be developed.
RDSs overlap with SAP Best Practices, but are really a combination of a number of different things. They are often confused with wizard-driven configuration assistants, but they are not this.
RDSs significantly differ from one another, therefore it cannot be said what is in any one particular RDS package, as it depends upon which RDS is being discussed. Therefore, it can only be said what RDS are generally.
As many RDSs are still being developed – but have been “released,” the quantity of what is in an RDS greatly varies from RDS to RDS.
A Generalized Description of RDSs
The best-generalized description of RDSs would be the following:
- SAP Basis notes
- Process flow documentation
- Configuration guides (the same as those that are referred to in SAP Best Practices)
- Basic Demos (assumed to be data and accompanying documentation) (in only some cases, but not all RDSs have them)
- An implementation approach which assumes a small and simple solution, with very little requirement gathering as the standard – simple configuration is accepted in all areas. (although this point is not generally emphasized)
RDSs are a standard package. For example, the RDS Foundation Starter RDS includes material for the following areas:
However at a previous prospect while the RDS Foundation Starter was included in scope, only one or two areas above were in scope.
The larger RDSs have enough content to organize the documentation per area of SAP. We will go into Accounts Receivable to see the detailed view.
Within one area, some explanation is of the area is combined with document links.
ASAP for RDS
There is also ASAP for RDS. A check was performed comparing what is available from ASAP 8 to ASAP 8 for RDS under one of the steps of ASAP. The following was found:
- Under Project and Budgeting, ASAP for RDS has two more documents.
- Under Project and Operational Standards ASAP has a number of ALM documents that are not part of ASAP for RDS.
- Under Execution, Monitoring, and Controlling of Results, ASAP for RDS has an Agile Project and Sprint Backlog document
- Under Project Team Training ASAP for RDS there are more documents than under ASAP
- Under Business Process Map, ASAP for RDS has an extra Agile Lean Blueprint document.
- Under Data Migration Approach and Strategy, ASAP has several more Data Migration documents
- ASAP for RDS has a subheading and two documents under Demo Environment that ASAP does not have.
- Under Phase Closure and Sign Off phase Deliverables, ASAP has a number of documents that ASAP for RDS does not have.
Overall, there is slighting different documentation offered between ASAP and ASAP for RDS. However, the differences between ASAP (standard) and ASAP for RDS appear to be minor.
How SAP Pretended RDSs Sped and Simplified Implementations to the Investment Community
RDSs were used to excite the investment community on how much they would improve implementations and increase license revenue.
Snabe’s explanation is that SAP has spent a good amount of time optimising implementations and cited RDS as one of the key planks in that strategy. As I said, we could have a good conversation on that topic alone. What I am hearing is that yes, RDS does simplify implementations, but only where you’re prepared to implement SAP’s version of best practices. We have yet to see substantial evidence from customers as to how that’s working out. – ZDNet
Many of the people that talk about RDSs have never researched them and don’t know what is in them. RDSs follow a long line of things that SAP has introduced, which includes ASAP Methodology and Solution Manager along with other items that have been predicted to speed the implementation time of SAP applications, but which never have had the intended effect.
Financial Bias Disclosure
Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.
Search Our SAP Project Management Content
Enterprise Software Risk Book
Better Managing Software Risk
The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.
Finding What Works and What Doesn’t
In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.
Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model