Comprehensive Software Reviews to make better IT decisions
SAP S/4HANA and HANA Licensing Series – Part III: Migrating to S/4HANA Will Cost More
Beware promises of cost savings and license optimization by acquiescing to SAP’s need for you to migrate from ECC to S/4HANA. Efficiencies in the areas of license optimization are usually offset by additional costs. Use a total cost of ownership (TCO) approach to evaluate the deal.
As we have previously discussed here, migrating to S4 or C4/HANA may present some organizations with the rare opportunity to re-negotiate their ERP agreements with SAP, in essence hitting the "reset" button. Upon review of multiple S4/HANA contracts, however, it would appear that few organizations have taken a long-term approach towards this unique opportunity.
The SaaS Dilemma
The promise to customers is that S/4HANA will provide a new SaaS-based model for both the business model and the software delivery components for the ERP software. Additional benefits such as performance gains and lower database costs must be scrutinized and decomposed to separate myth from reality.
As of early 2018, SAP had 7,900 customers (updated to 10,900) that had purchased SAP S/4HANA license entitlements, of which approximately 1,500 have gone live on the system. Now keep in mind a couple of crucial points.
- With over 437,000 customers, the reported 7,900 deals for S/4HANA represents 1.8% of SAP’s customer base.
- Furthermore, at 1,500 “live” systems, this represents only ~20% of signed contracts for S/4 HANA.
The primary takeaway from these numbers is that S/4HANA growth is occurring, yet it is still nascent compared to the legacy SAP install base. Furthermore, it appears that customers are engaging with SAP in piecemeal deals where S/4HANA is coupled with other product purchases rather than taking the opportunity to re-shape their complete ERP contracts.
What about the promises around improved cost structures and efficiencies from the SaaS deployment model? Well, very few agreements that we have reviewed include S/4HANA being deployed via the public cloud under a SaaS model. Implementations tend to be in a hosted, private cloud environment (i.e. colocation) or on premises. In many cases, enterprises are taking a hybrid approach of keeping core systems of record on premises while deploying a branch or line of business (LOB) functionality in a cloud environment, further increasing the implementation complexity. When implemented in this manner, the benefits of public cloud are non-existent. This serves to shift the business model to a subscription and/or transaction-based model that is more profitable for SAP and reflects well to its Wall Street analysts, but yields little in terms of benefits for the customer.
…And the Costs Mount Up
Take into consideration the requisite hardware costs and changes to the database requirements and layer this on top of poor adoption of S/4 HANA overall, and the cost-benefit analysis becomes more prohibitive as one moves away from the public cloud model.
For example, hardware improvements are a function, to some extent, of the specialized SSD memory required to run a HANA appliance. So is it the software or the hardware upgrade that is driving performance improvements, where they exist? To what extent for each factor? And, in case it needs to be mentioned, SAP customers will be footing the bill for this super-charged hardware, either directly when purchasing appliances or via inflated subscription pricing.
A final consideration is a requirement that S/4HANA is run on the HANA database. To incent customers to view this as a net positive, SAP has recently raised the prices on third-party run-time databases from suppliers such as Oracle, Microsoft, and IBM. SAP then compares the 22% of net license costs for third-party databases with the seemingly lower price of 15% for the HANA database. To be fair, SAP will often allow the value of shelfware licenses to be applied against the HANA database cost, which does bring the dual benefit of a one-time discount/credit and a lower Software Asset Value (SAV) upon which HANA charges are based.
One drawback is that HANA is the most expensive database product in the marketplace, coupled with a firm "no discount" policy from SAP. So it is a possibility that with a lower 15% license fee for HANA, the underlying base may be much higher than the legacy database solution, driving support costs higher. Additionally, enterprises must deal with the indirect (digital) access license issues plaguing them along the way, adding or modifying license terms and fees.
Take a holistic approach to calculate the costs of an S/4HANA migration; don't get hyper-focused on the licensing. Clearly documenting the costs of implementation (both soft and hard costs), the additional hardware requirements, and licensing will yield a more complete picture of costs against which the business case can be made. Note that most S/4HANA projects that have gone live are in their early days. Consider taking a long-term approach to this migration and build a bigger value bucket in the process.
Source: SoftwareReviews, Accessed July 19, 2019
Want to Know More?
VMware challenges IT to be more than it may be comfortable with: technologists as members of an elite caste charged with the moral use of technology and guarding the uninitiated against negative consequences.
Analysts make their bones on prognostication and prediction, and the imminent demise of any given technology is a mainstay of their subject matter. San Francisco-based VMware has made its sacrificial offerings but for two different auguries. First the place and dominance of public cloud as the center of the enterprise IT activity and work. Secondly, and more importantly, the enduring importance of self-service, elasticity, measure service, broad network access, and pooled resources.
ALM Works Structure for Jira enables Atlassian customers to track and manage projects at scale.
Many contract reviewers and negotiators often assume that terms and conditions applicable to both parties must be identical or mirror each other. Nothing could be further from reality.
Jenkins from CloudBees has been a stalwart of the open-source continuous integration (CI) / continuous delivery (CD) movement for well over a decade. The recent introduction of Jenkins X promises to make CI/CD pipelines with Kubernetes easier to set up and maintain.
Atlassian embraces the reality that roadmaps and plans are living, breathing, and continually changing.
Microsoft has just announced that effective July 1, 2020, Microsoft Partners will lose their Internal Use Rights (IUR) to use Microsoft products at no charge. The IUR benefit is easily the most valuable partner benefit and is currently received as a component of the Microsoft Action Pack.
Software QA requires complete end-to-end visibility of your delivery process and your team’s ability to meet defined quality standards and benchmarks. QACube provides the reporting and analytics capabilities organizations need to evaluate the quality and value of product deliverables as they progress in your pipeline.
Oracle just reported slightly better than expected Q4 FY19 results with revenues of $11.1B for the quarter and $39.5B for the year, up 3% in constant currency. A closer look at Oracle's change in the reporting of cloud revenues offers some clues about its longer-term cloud transition strategy.