A Study into SAP HANA’s TCO (Intro) (2017)

What This Article Covers

  • Introduction
  • Executive Summary
  • Paid Research Explanation
  • Navigating the Framework and Verbiage of HANA
  • Who is Brightwork Research & Analysis?
  • The Background on HANA
  • The Intent of the Study
  • Research Instructions
  • Research Licenses
  • Getting Clear on the Terminology
  • The State of TCO Studies Generally
  • The Research Method
  • The Manipulation of TCO
  • Forrester’s TCO Study
  • Problems with HANA TCO Context HANA is being pitched to replace Oracle and IBM (primarily)
  • The Brightwork TCO Method
  • The Base and Component Approach
  • The TCO Cost Categories
  • License Costs
  • Hardware Costs
  • Implementation Costs Direct Estimation of Implementation Costs
  • External Implementation Costs
  • Module Implementation Consultant
  • Senior DB Consultant
  • Internal Implementation Costs
  • Total Client Resource Costs for the Implementation
  • Percent of Total Costs (Implementation Costs)
  • Implementation Duration
  • Maintenance Costs
  • Our TCO Estimate
  • Specific Cost Categories and Multiples Explained
  • The HANA TCO Multiple
  • Updates and Reaching Out to Brightwork
  • References

Introduction

This is the first study of its kind. It is the first study into the reality of HANA’s TCO.

SAP has made many statements about HANA lower TCO. SAP has proposed lower TCO for both HANA (the database) and S/4HANA (the ERP system). yet, every single statement about HANA TCO by SAP is supported by a single study into the topic, a study paid for by SAP and produced by Forrester. In this article, we will evaluate the support for SAP’s claims regarding HANA TCO as well as provide our own TCO calculation.

Hasso has routinely argued that SAP HANA is not expensive. Typically Hasso will use the example of compression that is available in column-based databases to reduce the footprint. However discussing the topic with people a little closer to the ground will provide a very different impression. If you talk to SAP account executives or to account executives in SAP partners, they will routinely tell you that SAP HANA is expensive. They will also inform you that HANA is very hard to position, for this reason, once the price tag comes back, the customer often balks.

It is a simple thing for Hasso to propose in interviews how SAP HANA could in some hypothetical sense be not too expensive. But all other sources point to HANA being quite expensive. And you will not be buying HANA from Hasso but an SAP account executive. Hasso’s accuracy lately has been off, and I don’t see analysts or the traditional IT media outlets recording this inaccuracy or commenting upon it. I have performed a detailed analysis of Hasso’s statements on HANA.

However, up until now, there has been no published study on TCO that has been free from SAP’s influence. And only one study published (under SAP’s influence) which is the Forrester TCO study.

Executive Summary

SAP HANA’s TCO is much different than proposed by SAP (and repeated by SAP surrogates). It is not lower than competing alternatives and there are rather obvious reasons as to why. These reasons can be expressed in a general sense, but it is important to perform a mathematical estimated with a full explanation of each of the line items of HANA’s TCO as well as a full explanation of these assumptions.

Most of the assumptions explained in this study are not explained anywhere else that we could find when we performed a literature review prior to performing this study. While there has been an avalanche of claims about HANA, there has been extremely little actual research performed on HANA, and none of it would be able to meet what we consider to be of sufficient quality to be used in decision making regarding HANA.

Paid Research Explanation

This article you are reading will provide some of the details about the research, however, the bulk of the article is paid research. Researching HANA, validating SAP’s claims, checking with many sources in many parts of the world is time-consuming and requires funding. While there exists a great interest in selling HANA and HANA consulting services, there has been close to no interest in determining the accuracy of SAP’s statements regarding HANA. This is a problem. The funding in research very strong tends to flow in one direction — towards promotion.

It is recommended to purchase this document to get the only credible information available in the market the TCO status of HANA. Being a new product still being developed, it is of the highest importance to become aware of the experience of early adopters. Given that SAP research and development has run into various limitations in developing new products going back to after R/3 was released in 1992, HANA has a high probability being less than projected by financially biased promoters of HANA.

Navigating the Framework and Verbiage of HANA

HANA has unfortunately been confusingly explained to customers. Often HANA is referred to as a platform when it is, in fact, a database. There have been a number of products that have HANA in the name (which are sometimes changed to have HANA removed) but these are not HANA. Along with the similarly named S/4HANA, this can make it confusing what is actually being discussed.

The following marketing graphic is a good example of this.

One could spend quite a lot of time critiquing this and other HANA graphics. For example –

  • Pretty much any data stream can be made to be real-time or batch, so the description of these items is odd. HANA has been heavily marketed as being entirely real time. Hasso Plattner has stated that HANA eliminates all batch processing.
  • HANA is almost never connected to Hadoop.
  • Hadoop is open source and has its own open source analytics engine.
  • HANA is not particularly related to “network devices.” So this is a rather strange item to have on this type of graphic.
  • What database cannot accept information from cloud sources?

Overall due to the heavy marketing focus on HANA material, virtually every contention about HANA must be validated with sources outside of SAP. To keep this research article from being to lengthy and meandering, we describe areas that are necessary and pertinent to TCO.

Who is Brightwork Reseach & Analysis?

Brightwork Research & Analysis is an independent research entity. We specialize in researching SAP. We have first-hand experience implementing SAP, something which differentiates us from most other research entities that cover SAP.

SAP leadership perceptions are the result of a global orchestrated powerful ecosystem all with vested interests. System integrators, CIOs/CFOs, analysts and IT media defend the perception of SAP leadership to preserve their interests, which have been valued in trillions of dollars. (See the book SAP Nation and SAP Nation 2.0 by Vinnie Mirchandani for a fuller explanation of the financial implications of SAP’s ecosystem.) According to Gartner, Accenture has 46,000 SAP consultants, IBM has 36,000, can you count on their neutrality to give you advice on SAP? They clone what SAP says with no research or verification, what SAP says they repeat. This leads to zero objectivity and what should, logically at least, amount to zero credibility as to the viability of HANA.

Obviously, SAP is pro-HANA, but many SAP consulting companies are also pro-HANA. And their evidence? That can be found in billing hours. Getting behind SAP HANA maintains their income streams. The more money customers invest in SAP, the better these consulting companies do. Most media entities, who take money from SAP, are also pro-HANA and SAP has distributed large amounts of information that is directly from SAP marketing and is unfiltered by the media outlet since HANA and S/4HANA’s introduction. SAP has distributed large amounts of money to media entities for what is called “paid placements.” These are undeclared advertisements, usually written by SAP, and can be found in Fortune, Forbes, ComputerWorld (owned by IDC) and many other IT media outlets. All of this has led to a general misimpression as to what has actually been happening on HANA implementations.

Our lack of financial relationship with SAP has allowed us to publish this study without external influence.

The Background on HANA

Before getting into the case studies of HANA, it is important to have a full frame of reference as to what HANA is. Along with S/4HANA, HANA is one of the largest initiatives on the part of SAP ever undertaken. It is one of the largest current development projects at SAP and has been for several years. SAP went public in 2011 with the announcement of HANA. HANA maintains a natural connection with the S/4HANA database, as currently S/4HANA, the ERP system can only run on the HANA database. The two products have the same term “HANA” in their title. This is quite unusual as it is either extremely rare or completely unique to include the database in the name of the application. SAP’s reason for doing this is primarily for marketing related.

S/4HANA maintains an artificially exclusive restriction with the HANA database. SAP S/4HANA runs only on HANA. Customers are being forced to replace Oracle and IBM and Microsoft databases with HANA. And that is really just the tip of the iceberg as at a wide variety of accounts SAP is pushing HANA into various applications using usually some type of compatibility argument. That is only HANA support x, y or z in the application, and therefore, HANA should be purchased.

HANA can be evaluated from many dimensions, and the overall topic is complex. These dimensions all have impacts on the TCO of HANA. We address these issues as necessary to explain our TCO estimates for HANA.

Intent of the Study

  • This study was intended to determine the TCO of HANA.
  • This study was not undertaken to determine the implementation status of HANA. That would mean using a case study approach, which is not what we did in this study.
  • Some TCO estimates are created to arrive at a total dollar figure. All of our TCO calculations up to this study have been exactly that. However, this study was designed to validate the proposal by SAP that the TCO of HANA is lower than that of the databases that it aims to replace. For that question, developing a fraction or multiple is the obvious approach. If HANA’s TCO is less than one compared to competing databases then SAP’s claims would seem to be more valid. Conversely, if HANA’s TCO is greater than one compared to competing databases then SAP’s claim would seem to be invalid.

S/4HANA is the next version of SAP’s widely implemented ERP system. SAP has put an enormous effort into marketing S/4HANA. Yet many of the aspects of S/4HANA are not well covered by SAP. For example, important implications for a S/4HANA implementation are left out, particularly if those implications are not positive.

For all of the effort expended by SAP on socializing and popularizing S/4HANA, it can be said without a doubt that S/4HANA is generally poorly understood. But beyond misunderstanding the components that make up the solution, there is an even greater misunderstanding regarding the implications of S/4HANA.

Research Instructions

To Purchase This Research — See the Following Link

This page will stay open. After making the purchase, select the following link to get to the research article.

___________________________

If you run into any problems or have any questions, please email us at info@brightworkr.com.

Research Licenses

All sales are for a single email. If analytics show sharing of email logins, the account will be shut down.

For companies that have purchased a block of user access licenses (and that use a coupon code) our paywall records how many times the coupon code is used. And the coupon code can only be used as many times as was purchased by your company, and our paywall records the number of times a coupon code is used by a single user.

If you are reading this research on anything but the Brightwork website then you are not using the research in accordance with the license. The license is not for copying the research, (and we have anti-copying software on the site). It is for reading the research as many times as one wants for the term of the license. This applies for sharing the research with SAP. SAP is takes in over $20 billion a year in revenue, if they want to read research about their products, they can afford to pay.

Secondly, this research is updated as time passes and as new information comes to light.

Research Updates

Most research is static. However, the plan is for this and for other Brightwork Research & Analysis research to be updated. As new case studies come forward, they will be added to this research. As things changes with respect to HANA, we will update this research. Companies have the option of having the research renewed every 6 months (at a reduced rate) so that they can be kept up to date on recent changes.