If SAP Rapid Deployment Solutions are by nature, packaged solutions, you might be wondering how can this help deliver differentiation within my enterprise system?
Well first off, while rapid-deployment solutions are indeed preconfigured, adjustments can be made to fit your unique business needs and processes. Those customers taking on a higher percentage of pre-configuration will of course gain the most in project industrialization, lower costs and faster roll-out, but with rapid-deployment solutions, there is always room (in fact this is the most common case) for a delta of 20-30% where specific configuration addresses uniqueness and additional extensions and custom development services can deliver competitive differentiation.
So how does this all come together?
There are now more than 150 rapid-deployment solutions, cutting across the full SAP portfolio, including innovations, such as SAP 360 Customer and SAP Business Suite on HANA. Today, approximately 1/3 of our more than 2,400 customers are purchasing multiple rapid-deployment solutions, leveraging our solutions as a building blocks to address their broad business needs. While a portion of our customers take a phased approach (implementing one solution at a time in sequence), increasingly they are implementing multiple rapid-deployment solutions in parallel, in what we call assemble-to-order.
As you can see from the image above, this approach helps to solve end-to-end business needs for customers, more efficiently, by combining multiple rapid-deployment solutions, along with engineered services, rapid data migrations and solution extensions. The end result for assemble-to-order is to successfully deliver across a customers needs in a highly productized way, lowering overall project costs, freeing more resources towards innovation and solution differentiation.
Stay tuned on SCN for the remaining 4 blogs in this series, ‘Top Reasons Customers Choose SAP Rapid Deployment Solutions’ The next blog is about ‘Innovation’…
Follow SAP Rapid Deployment Solutions on Twitter: @SAPRDS