- The lies in an NTT Data article about HANA are so extreme that we created a new award called the Propaganda Award.
- Review one of the worst articles ever written about HANA.
The Brightwork Research & Analysis Propaganda in It Award is awarded to articles that contain excessive degrees of false information about IT topics. In this award, we include parts of the awarded article, along with our critique.
The award winner can display the image above on their website. We recommend right below the article for which they won the award. This article is titled 2015: The Year of S/4 HANA.
2015: The Year of S/4 HANA
Posted 01/31/2015 by Alison Bessho
“First announced in 2010, it quickly became clear that SAP HANA would be the foundation for everything at SAP. With columnar storage, advanced in-memory compressions, and unmatched processing power, SAP on HANA is fast, empowering businesses to run in real time, crunching Big Data – transactional, operational, structured, & unstructured – to transact, analyze and predict instantly on a single platform at the moment of opportunity.”
It is untrue that HANA has “unmatched processing power.” In fact, SAP has provided no benchmarks that support any of SAP’s marketing proposals regarding HANA. This is covered in the article Which is Faster HANA or Oracle 12C? While comparing benchmarks requires interpretation, there is no basis for SAP to state that HANA is faster or has better performance than comparable databases on the market.
“While HANA’s accolades for speed are well earned, HANA’s ability to dramatically simplify enterprise architecture, reinforce stability, scale limitlessly, and generate big savings in the process are equally impressive.”
This is an unproven claim, but a claim often made by SAP. SAP has proposed that HANA greatly simplifies enterprise architecture. That statement makes no sense. HANA is not an “enterprise architecture.” HANA is a database. SAP has stated that HANA has a simplified data model, but this article, Does SAP S/4HANA Actual Have a Simplified Date Mode?, explains why this is untrue. This article Is SAP S/4HANA a New Application Architecture?, explains that Hasso Plattner and SAP’s proposals regarding SAP S/4HANA is an application architecture is unsupported.
According to Forrester, enterprises opting to implement SAP HANA can expect to see their software costs fall by more than 70%, their hardware costs by 15%, and their administration and development costs by 20%.
This study was funded by SAP. And it is both a completely flawed study that is entirely based upon information provided by SAP. Forrester’s statements are entirely based upon projections. Brightwork estimates that HANA is the most expensive database that can be purchased. There are multiple reasons for this that range from the cost of the software, the cost of the hardware, the transition from Oracle or another database to HANA, the cost of HANA resources, etc..
There are multiple reasons for this that range from the cost of the software, the cost of the hardware, the transition from Oracle or another database to HANA, the cost of HANA resources, etc..
It is no surprise that today, according to SAP, HANA has more than 5,800 customers and more than 1,850 customers running Business Suite on HANA, making it the fastest-growing product in SAP history.
S/4 HANA is sure to further accelerate this torrid pace of HANA adoption.
HANA does not have 5,800 customers using the database. The definition of a customer is that the SAP customer has a HANA license. This license will include a run time license, which requires very little investment from a company. Because SAP has exaggerated these number to make an impression on Wall Street and customers, the statement about being the fastest growing product in SAP history is very unlikely to be true. HANA has been a modestly selling database and still has a modest market share.
HANA has been a modestly selling database and still has a modest market share.
“Many core enterprise systems today — think of the ERP boom in the ’90 — are flirting with overdue replacement cycles and/or upgrades, extensive and expensive customizations, rising maintenance costs and, most critically, a lack of flexibility needed to meet today’s changing business demands.”
All of this may be true in parts. However, the overall sentence is highly misleading.
- The extensive customizations were necessary because SAP’s functionality was not sufficient to meet the requirements of the ECC customers.
- The customizations will have to be greatly adjusted due to S/4HANA using the HANA database.
- There is no evidence that S/4HANA will reduce maintenance costs. In fact, if one uses S/4HANA it lowers the ability of a company use outsourced support. Companies usually save 1/2 of their support spend when they move to a third party support entity. However, NTT Data, as with all the SAP partners, will not tell their customers this fact.
- There is no evidence that S/4HANA has any more flexibility to meet today’s changing business demands. This continues the overall article’s pattern of presenting proposals without any evidence, or where the evidence goes the other way.
“In a nutshell, S/4 HANA is a collection of integrated, modernized ERP (and other) apps with a simplified code and data model (no material aggregates to be maintained) capable of running OLTP and OLAP on the same system.”
Untrue. HANA does have aggregates, but they are not called aggregates by SAP. And the problem with current ERP implementations is not that ECC uses “aggregates.” Secondly, the code may be simplified. However, it is not true that the data model is simplified. This is covered in our article Does SAP S/4HANA Actual Have a Simplified Date Mode?
“In addition to ease of implementation without disruption, S/4 HANA benefits include compression, real time analytics, landscape simplification, and ease of configuration, delivered through a simplified and enhanced end-user interface based on SAP Fiori. S/4 HANA, not incidentally, is also optimized for cloud deployment.”
S/4HANA has compression, but again the problems at SAP ECC accounts having nothing to do with compression. There is no landscape simplification with S/4AHANA. There is no ease of configuration. There discussion of preconfigured capabilities in S/4HANA, but SAP has claimed this so many times in SAP’s history, and configuration is still done the way it always has been. S/4HANA has nothing to do with the cloud, although SAP has tried to comingle S/4HANA with the cloud since S/4HANA was first developed.
But the truth is most S/4HANA implementations are on premises. Something which confuses companies is the HANA Cloud Platform. This is covered in the article Is the SAP HANA Cloud Platform Designed for Cloud Washing?
As the cloud-computing paradigm shift plays out and more mission-critical functions ascend to the cloud, and as reported by Computerworld, 53% of IT leaders cite cost containment as their number one business priority, S/4 HANA will play a pivotal role in 2015, simplifying and reducing hardware costs, driving deeper cost savings from cloud services; increasing the cloud’s analytic and BI capabilities by orders of magnitude; wringing latency from cloud-based services; and infusing cloud services with unprecedented reach and flexibility.
There is zero evidence for any of this, except for the quote from Computerworld. 2015 came and went, and S/4HANA did not play a “pivotal roll.” In fact, it was barely implemented at all in 2015.
It is confusing as to why S/4HANA would reduce hardware costs. S/4HANA requires HANA and HANA use the most expensive hardware as it is a combination of memory and SSD. S/4HANA is still barely implemented in the cloud. Therefore it has not reduced savings in cloud-based services.
S/4HANA (or short: S/4) is the next-generation Business Suite — a new product and not a legal successor of the SAP Business Suite 7 — based on the following three attributes:
- SAP HANA as the underlying platform with increased speed, merge of analytical and transactional data (OLTP & OLAP merge) and in-memory compression to reduce data footprint. S4 is only built on SAP HANA.
- Real-Time & Simplified: SAP HANA allows us to simplify our applications and the underlying data model (no aggregates, no indices anymore) leading to higher flexibility & throughput and data footprint reduction
- SAP Fiori as the holistic user experience (UX) paradigm delivering cross application user experience: web-based, all devices, role-based and decisive
There is an important reason why S/4HANA is classified as a legal successor, but not a logical successor to ECC. This is so SAP can charge companies that are already paying 23% in yearly support now have to pay for S/4HANA as if it was a new product. Brightwork has already proposed that S/4HANA should be free to the customer.
This is covered in the article Why SAP S/4HANA Should be Free. NTT Data will never side with customers on this topic, even though the logic for it is irrefutable, because NTT Data is a SAP Partner, and SAP partners must tow the line on anything that SAP says.
The S/4 product family – new products that will be delivered within 2015, starting Q1 – consist of the following three products (deployment options):
- 1S/4HANA Public Cloud – simplified, HANA-based end2end solutions for lines of businesses (LOB) operated in the SAP public cloud with full SaaS qualities (e.g. end2end ERP processes for the Professional Services industries; end2end Marketing Campaign Management; Operational Procurement; …)
- 2S/4HANA Private Managed Cloud – a full ERP-only version, partly simplified, fully HANA-based, ~30% Fiori-based UI (rest classical SAP GUI), operated and managed in the new Innovation-HEC along SaaS operation practices
- 3S/4HANA on-Premise – full on-Premise ERP version (equal to Suite on HANA) with Simplification Exchange Innovation add-ons for finance (sFIN Q1) and logistics (sLOG Q4)
This is misleading as the vast majority of S/4HANA implementations are on-premises. Option 1 and option 2 above are barely used.
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 Other Who Was Right and Wrong on HANA Content
The Real Story on ERP Book
How This Book is Structured
This book combines a meta-analysis of all of the academic research on the benefits of ERP, coupled with on project experience.
ERP has had a remarkable impact on most companies that implemented it. Unplanned expenses for customization, failed implementations, integration, and applications to meet the business requirements that ERP could not–have added up to a higher Total Cost of Ownership for ERP were all unexpected, and account control, on the part of ERP vendors — is now a significant issue affecting IT performance.
Break the Bank for ERP?
Many companies that have broken the bank to implement ERP projects have seen their KPIs go down— but the question is why this is the case. Major consulting companies are some of the largest promoters of ERP systems, but given the massive profits they make on ERP implementations — can they be trusted to provide the real story on ERP? Probably not, however, written by the Managing Editor of SCM Focus, Shaun Snapp — an author with many years of experience with ERP system. A supply chain software expert and well known for providing authentic information on the topics he covers, you can trust this book to provide all the detail that no consulting firm will.
By reading this book you will:
- Examine the high failure rates of ERP implementations.
- Demystify the convincing arguments ERP vendors use to sell ERP.
- See how ERP vendors take control of client accounts with ERP.
- Understand why single-instance ERP is not typically feasible.
- Calculate the total cost of ownership and return on investment for your ERP implementation.
- Understand the alternatives to ERP.
- Chapter 1: Introduction to ERP Software
- Chapter 2: The History of ERP
- Chapter 3: Logical Fallacies and the Logics Used to Sell ERP
- Chapter 4: The Best Practice Logic for ERP
- Chapter 5: The Integration Benefits Logic for ERP
- Chapter 6: Analyzing The Logic Used to Sell ERP
- Chapter 7: The High TCO and Low ROI of ERP
- Chapter 8: ERP and the Problem with Institutional Decision Making
- Chapter 9: How ERP Creates Redundant Systems
- Chapter 10: How ERP Distracts Companies from Implementing Better Functionality
- Chapter 11: Alternatives to ERP or Adjusting the Current ERP System
- Chapter 12: Conclusion