How to Understand the Pricing of S/4HANA and HANA

Executive Summary

  • Despite making the code of S/4HANA 93% identical to ECC, SAP attorneys have deemed S/4 the “logical successor” to ECC instead of the “legal successor.” This means SAP ECC customers paying for support contracts with free software updates are unable to upgrade from ECC to S/4 without purchasing the software.
  • Find out about the issues with HANA and S/4HANA pricing before you negotiate with SAP.

Introduction

In this article, we will review the implications for HANA pricing and S/4HANA pricing. If you are negotiating with SAP, neither SAP nor the SAP consulting firms will want you to read this article. They will say the information is not approved by SAP, that Brightwork is not an approved SAP analyst, that information must come from an SAP partner, anything to get you to not use the information in this article. However, one of the worst thing any customer can do is only rely upon information from SAP and a consulting partner when making a decision.

Even listening to Gartner does little to improve accuracy as SAP pays Gartner what we estimate as around $150 million per year as we cover in the article How Gartner Makes its Money.

*This article was written originally in March of 2017, however it was updated and is current as of September 2019. 

What is SAP’s Integrated Strategy for HANA and S/4HANA and How it Purges Oracle?

Because of SAP’s confusing naming, it is still necessary to differentiate between S/4HANA and HANA.

  • HANA is SAP’s first serious foray into databases.
  • S/4HANA, on the other hand, is the ERP system. S/4HANA only works with HANA, breaking with the previous tradition of SAP applications being open to different database vendors.
  • HANA is not obligatory of any other SAP application other than S/4HANA, although SAP strongly leans on its customers, mostly through providing inaccurate information, to move to HANA for many other SAP applications.

SAP has had a few other databases that they owned through the years, like Max DB, but these were very lightly sold. SAP purchased Sybase several years ago. However it has not been able to sell many Sybase databases, and the Sybase acquisition has been a washout, with the Sybase product seen as quite dated. SAP doing very little to keep the Sybase database line up to date, and by trying to force HANA into historically Sybase accounts they damaged their relationships in the core Sybase financial sector and may of that customer switched to Microsoft SQL Server, which is based on Sybase. It is a feature of the controlled IT media, that the horrible outcome the Sybase acquisition has not essentially uncovered. We covered this topic in the article How Accurate is SAP on the Sybase Acquisition.

A Major Change in Strategy

It is difficult to overemphasize what a change in strategy HANA is for SAP. SAP used to be based around a system that, as with most applications vendors is open to a variety of different commercial databases (although not open source databases).

SAP has very strongly based its strategy around HANA. The pricing for HANA is quite unusual and is important to understanding how to best purchase HANA.

The HANA Based Strategy to Remove Oracle from Accounts

SAP has an integrated strategy regarding HANA and S/4 HANA which is related to removing the Oracle database from accounts. Brightwork Research & Analysis receives no income from any vendor outside of competitive intelligence work. And we have no conflicts regarding Oracle or SAP and do not care if either win or lose business (see the explanation at the end of the article). But on its merits, SAP has put forward no reasonable technology reason for any of the other major database vendors to be excluded from supporting S/4HANA. That is, it is not that they have not put forward reasons, but upon inspection, none of these reasons check out. 

SAP’s Refusal to Certify Any DB but HANA

SAP has simply refused to certify any other database for use with S/4. SAP has made many statements regarding HANA’s “unique” performance characteristics, I have carefully evaluated each of these statements and found them to be without merit. And Brightwork’s research into HANA in depth goes back to 2016. 

Secondly, SAP refuses to release transaction processing benchmarks (that due to HANA’s 100% column-oriented design, likely are not very good) as we cover in the article The Hidden Issues with SD HANA Benchmarks and they needed to create an entirely new benchmark under the false premise that the old benchmark did not reflect how companies “use” S/4HANA as we cover in the article John Appleby on SAP BW EML Benchmark. Meanwhile, SAP is losing in benchmarking tests to other database vendors and in reports from many accounts globally. In fact, there is a question as to whether HANA can outperform the far less expensive SQL Server as we cover in the article Why it is Likely That HANA Underperforms SQL Server.

However, through both its own and its many partners, SAP has a very effective sales force and the willing army of compliant consulting partners. These partners effectively to prevent this information from being widely known or repeated.

The first thing to know, before understanding the technical details of HANA or its pricing is that the information provided by SAP and consulting companies is unreliable. The only thing the SAP sales rep and various consulting resources are measured on is sales of either software or consulting hours. Consulting companies are not independent checks on SAP, they repeat whatever SAP says. It is accepted that any lie that is necessary to gain that sales is appropriate. When we support companies in negotiations, we see the same lies told again and again. One of our previous clients even were lied to about why there was a price decrease. 

Understanding SAP’s Strategy with S/4HANA and HANA Pricing

Understanding SAP’s strategy with S/4 and HANA is critical to understanding how SAP prices these products.

SAP’s strategy is to use its dominant ERP system to dictate the database that is used to run this ERP system.

Customer Input Not Required

SAP never asked its customers if they were interested in the very large trade-off of losing database portability by placing stored procedures. Furthermore, there is also nothing to stop SAP from removing those stored procedures and putting them back into the application layer, which is something we predict SAP will do in the future. That is after all the development approach they followed to good effect since SAP began as a company. 

What SAP is doing, although it does not seem to realize it fully, is sacrificing S/4 adoption to build its database business. This strategy has been unsuccessful in moving many companies to S/4. 

Getting Real with the S/4HANA Implementation Numbers

Currently, we estimate far fewer than the claimed number of S/4 implementations live, and almost all of these are for a single module – S/4 Finance. We monitor and analyze the S/4HANA case studies as we cover in The Brightwork Study on S/4HANA Implementations. (This article is the introduction. The actual research is paywalled) 

SAP will not continue, as they have, to sacrifice S/4 adoption forever. Something else SAP has been doing is sacrificing revenues on S/4 to sell HANA. This topic gets a bit convoluted because there is a strong argument that S/4 should be free to current customers who are current on their support. Many customers are paying 22% or more on support contracts and were supposed to receive free updates for all the applications they have purchased. This certainly includes ECC.

How SAP Changed the Rules and Put Itself in the Position to Charge Existing Customers for an Upgrade

SAP changed the game, and declared that S/4 was a “logical successor” to ECC, but not a “legal successor.” 

SAP’s attorneys had to twist themselves into a pretzel to come up with the phrase that S/4HANA is the “logical successor” but not the “legal successor” to ECC. SAP covered up the deception by stating that S/4HANA was so different from ECC that it was a new product.

But an analysis by Paul Coetser or through a related party found that S/4HANA was somewhere around 93% code identical to ECC.

Why is S/4HANA (According to SAP) Not the Legal Successor to ECC?

The real reason S/4HANA is not the legal successor to ECC?

SAP wanted to charge for S/4HANA, hence giving them the ability to double-bill its customers. We covered this in the article Why SAP S/4HANA Should be Free.

This is just another change in the rules which violated the support agreement that states if the customer keeps up with their maintenance, they are owed all upgrades for the products you purchased.

This phrasing meant that ECC was from a support perspective sunsetted. With support extending to 2025 and S/4 was positioned as entirely new applications that existing customers would have to pay for.

All of this translates into the price for SAP increasing for customers. However, will your friendly neighborhood SAP consulting company explain this to their clients?

Of course not. If you ask a nice SAP consulting firm about whether these are in fact price increases they will dance around the topic. 

Is S/4HANA a Good Value for Existing ECC Customers They Get it For Free?

How many companies that purchased ECC five years ago thought that after five years of paying more than 22% in annual support that they would also have to repurchase their ERP license, or stay on the last version of ECC?

  • Given this background, the idea that SAP is offering, as it has, promotions on S/4 for “free” is misleading because it makes little sense for current support customers to pay anything for S/4.
  • After all, customers did not ask SAP to introduce S/4. SAP made this decision based on their internal incentives which branch into an overall strategy to remove Oracle from their customers.

Nevertheless, SAP has repeatedly offered S/4 for “free.” but has refused to discount HANA (except for the runtime license, which is not a real license). Therefore, SAP can “recoup” the costs of “free” S/4, by getting customers to pay for and get onto HANA.

Getting customers on HANA is a huge win for SAP because as will be described in this paper very few companies will be able to run for very long on the amount of HANA license that they initially purchase. And this leads directly into the question of database sizing and its importance in HANA pricing, which we will get into now. 

The Importance of Database Sizing in HANA Pricing

Of primary importance in HANA pricing is that before any pricing numbers begin to be applied, database sizing must be performed. This is because HANA is sold per GB. This is quite an unusual pricing for a database.

What this means is the HANA pricing is based on the size or footprint of the SAP database. And SAP has released information that will cause customers to substantially undersize the footprint so that SAP can get their foot in the door with HANA. Customers routinely have to go back to SAP and request more GB, which blows their budget.

Without an accurate footprint estimate, HANA cannot be priced correctly. However, all the sources of information on sizing the footprint either come from SAP or come from a SAP partner. Companies that are partners with SAP lose control over the information that they provide to customers. They must not provide information that contradicts the SAP information (read our analysis of the SAP partnership agreement). This, of course, includes companies that are the largest advisors in the space (your Deloittes, Accenture, etc..) to the smallest.

How do we know this?

SAP partners contact me and tell me stories of how SAP threatens to take their partnership away if they don’t follow the SAP rules. No SAP partner can provide accurate information on SAP pricing, SAP HANA pricing or any other SAP pricing for that matter.

Therefore, companies are boxed out of accessing accurate information on this topic. Brightwork Research and Analysis is one of the few entities which will publish or provide consulting on this topic. Unsurprisingly, we have no partnership with SAP, and unlike someone like Gartner or Forrester, we take no money from SAP (or any other vendor for anything else than competitive intelligence).

Getting into the Customer’s Business Regarding Archiving

In most cases when a database is sold, the database vendor sees the sizing as more of a customer determined item. Yet this is not the case with HANA. 

Companies have database administration groups that have their own views as to how frequently and how extensively they want to perform archiving. How much they want to rely upon compression, etc.. However, because of SAP’s pricing of HANA, SAP is now front and center on the topic of the database size, and has become quite prescriptive of how they think database administration departments should be managing their databases.

After HANA is Sold: SAP’s Next Steps for Follow on Sales

Furthermore, it is now clear that HANA is just a first step for SAP sales in penetrating the database layer. The first salvo was to lead with HANA. The argument being that no other database can keep up with the performance provided by HANA. SAP not only intends to get the application database business from its customers which its applications reside upon but also is positioning other database products, such as those it acquired from Sybase in its accounts as well. Sybase has been unsuccessful against Oracle, but this time Sybase’s products are commingled with SAP’s sales force and positioning.

All SAP Applications Work Better with HANA?

SAP’s marketing positioning is that these databases work much better with HANA than with any other database. So it is a two-step process.

  1. The first step is convincing clients to use HANA. SAP is doing this with a combination of selling the purported performance benefits of HANA, along with blocking all other vendors from applications like S/4 so that they are the monopoly database provider for their ERP system.
  2. The second step is marketing the compatibility aspects of HANA with all other database products. That is HANA is simply the nose of the camel into the tent. There is an ancient Arabic proverb about what happens after you let the nose of a camel into the tent. At first, it may seem innocuous, but bad things follow if you don’t put a stop to it. Bedouin know you do not allow the camel’s head into the tent. If you let it in, pretty soon your tent is lying on its side, and your belongings are strewn across the desert. 

SAP sales reps are excellent at getting the nose into the tent. The nose is brought in normally through false statements. Curiously, very few SAP customers hold SAP accountable for things they said that turned out to be false and that the contracts are based upon these false pretenses. I am repeatedly told by procurement departments that they have no choice because SAP has them “over a barrel.” 

SAP consulting companies are also intent on telling the customer to never hold SAP accountable, and that lying is not lying. Of course, the SAP consulting companies have far more allegiance to SAP than to their “clients.”

Archiving “Down” HANA’s Footprint?

The chart that SAP likes to show is with almost all data archived on to a separate database. SAP is pushing customers to use Sybase IQ to archive old data from ERP. Sybase IQ, a column-based database like HANA which SAP picked up from its Sybase acquisition, which they have had a tough time leveraging (interestingly, HANA, while being column-oriented like Sybase IQ is not based upon Sybase IQ, but has a different design heritage.

However, the problem with this is that this is now different databases with different skill sets that SAP is proposing that its customers acquire.

The undersizing of HANA is both obvious from the logic that SAP presents on HANA and from the real world feedback where multiple SAP customers that bought into SAP’s undersized model are now coming back to purchase more HANA license so that they can cover the database size. The degree to which HANA is undersized at the point of initial purchase is becoming obvious as come customers come back to SAP within six months to acquire more HANA GB. As I have written previously, HANA is very expensive per GB.

The Deliberate Undersizing by SAP and SAP Consulting Firms

As a synopsis, there are four distinct areas where SAP relies upon to drive footprint reduction, and of these four areas, two are very significantly overestimated by SAP. To see how these areas are overestimated, please see the paper that has been referenced. 

Of all the areas where the footprint can be reduced, it is the indexes where most the space-saving occur. This is normally between 33% and 25% of the database. Archival can reduce the size of a footprint also, but SAP makes it sound like customers aren’t already archiving, and there is nothing in HANA that makes archival more effective than in any other database. 

Secondly, the archival is not free. 

What Archival Entails

Archival means increased costs in labor to perform the archiving. Therefore what SAP is saying is that while HANA will do nothing for archival, if the company desires, they can spend more resources on archival. This will suit SAP, as SAP can make the initial purchase price lower, increasing the potential demand for HANA. Therefore, according to SAP, customers should perform more archival so that SAP can sell more HANA. However, what happens if the customer is not able to follow through on the level of archival that they initially commit to?

Well, then the database will grow, and SAP will have its hand out for more HANA license(s). And the problem with this is that while SAP is making greatly exaggerated proposals regarding footprint reduction, if they are wrong, there is nothing that the customer can do about it, except buy more HANA license. 

After the initial HANA purchase is made, and once the system begins being used for production (at which point the database will grow), then the company has narrowed its options. And of course, software vendors love narrowing the options of their customers.

That is called lock-in.

You put the customer in a position where they have to buy more from you, or they can’t operate properly.

SAP’s Un-natural Focus on Footprint Reduction

Getting back to the point about total realistic footprint reduction. In our estimate, roughly another 20% reduction from all other sources is attainable, although not without cost.

This enormous focus on footprint reduction is so important because unlike most other database vendors, SAP prices HANA per GB. No other vendor has such a focus on database size, because no other vendor that competes in this space prices their database per GB. Therefore, the maximum ordinarily attainable footprint reduction should be roughly 50%. This is the number that we have applied to our cost calculations in this paper. Some customers will reduce their footprint a bit more, some a bit less, but we believe 50% is a reasonable assumption to use for footprint compression.

HANA Pricing with Realistic Assumptions

A mid-size ERP instance is about 2-4TB depending on modules implemented, years of operations, archiving, and self-developed tables. If we assume a 50% reduction in the database footprint due to the use of HANA, this becomes about 1-2 TB. As we stated earlier, HANA is priced per GB. 1 TB is 1000 GB. So a typical mid-sized ERP instance on HANA would be between 1000 GB to 2000 GB. SAP also has a well known non-discount policy on HANA, and this makes the pricing easier.

  • The range of pricing for a 1000 to 2000 GB instance of HANA would be a one time cost of roughly $6.2 million. At 20% per year, this will add a support charge of $1.24 million.
  • Then hiring HANA skills into the database administration function will have to be added to that figure. And HANA skills are still very difficult to find.

Important Facts Related to HANA Pricing

  • HANA is quite expensive for a database and SAP knows this. HANA also has a high implementation and maintenance cost. 
  • However, SAP is doing everything it can to make the initial purchase price of HANA low to obscure its actual cost. Interestingly, in the only well known published study on the TCO of HANA that has been published by Forrester, the runtime license was used to price HANA. HANA’s runtime license is deceiving and interferes with the correct pricing of HANA. The runtime license is designed to get customers to be able to test HANA at a very reduced price of 8% of the cost of “full” HANA.
  • We created our own proportional TCO calculation of HANA which you can read at A Study into SAP HANA’s TCO

Customer sometimes think that this is the actual price of HANA. SAP knows how to time software audits so that they can extract the most revenue from accounts.

  • The HANA runtime license is a bear trap designed to lull companies into thinking the price of HANA is far lower than it is.
  • And unsurprisingly, as SAP paid for the Forrester study on HANA TCO, Forrester used the runtime license to reduce the TCO of HANA. Forrester does note that it used the runtime license, but somehow turned it around so that the use of what is obviously a temporary license was considered more, not less accurate than using the standard HANA pricing.

S/4HANA Pricing

Once HANA has been priced, the next step is to price S/4.

S/4 is more straightforward to price in one respect as it is not based on a database sizing effort. The confusing aspect of S/4 is that it has routinely been offered for free, and the vast majority of S/4 “customers” did not pay anything for S/4. S/4 is a gateway application to HANA, which is the real motivation for SAP. SAP wants, as we have described in detail already, to get into the database layer. This is not only because HANA is so expensive, but also because SAP sees HANA as a Trojan Horse to eventually take over the database layer and kick the current database vendor, or database vendors out of their customers.

  • Therefore the pricing of S/4 could be nothing or can be something depending on the promotion that is run at the time of purchase.
    Secondly, there is no policy against discounting S/4, and we have observed S/4 being quite heavily discounted.
  • SAP has been offering S/4 at a very low price to consulting companies so they can install S/4. These consulting companies don’t care about using S/4 for their internal operations, but they want to gain the consulting experience to S/4 so they can advertise this fact and get S/4 business. This is precisely what Infosys did, and it is quite unlikely that Infosys paid very much at all for S/4. When Infosys communicates to the outside world, they tell companies they made a strategic decision to use S/4, however, in actual fact, they have no need for S/4. 

How SAP HANA is Now Being Discounted

One of the constants with SAP’s policies is change. In this article, we will cover SAP’s change in pricing policy regarding HANA pricing.

At One Time the Only Non-Discounted Product on SAP’s Price List

For years after HANA was first introduced it was the only product SAP offered that was not to be discounted by any account executive. However, several years ago this policy was changed so that HANA could be discounted. And the discounts seem actually to be high. As high as 65% of the list price. Interestingly this was predicted by UpperEdge in an article in January 2014.

“SAP has been very aggressive in pushing and hyping the growth attributed to HANA on all of its prior earnings calls.  UpperEdge has consistently observed interest from our client base in HANA but such interest has been limited to specific use cases and pilots as opposed to broad, wide spread adoption.  In addition, now that HANA has had enough soak time in various customers for various use cases, feedback is now available regarding the benefits achieved relative to the cost.  From what we are hearing, customers like the technology but have concerns regarding the cost.  This type of feedback will likely spread within the user groups prompting SAP customers to seriously consider comparable, lower cost solutions.  Could this be enough to finally drive SAP to discount HANA? We believe it is something SAP is seriously considering.”

However, the discounting that is now occurring with HANA is not the end of the issue. HANA has more indirect access liability than any other database, because SAP brings indirect access claims against its customers, while no other software vendor (outside of an attempt by Software AG to copy SAP) does. We covered this in the article HANA Police Indirect Access Charges.

Therefore, the price on HANA can be discounted until the customer is found to be out of compliance. And SAP can use indirect access to charge more for HANA after it is installed, and after the company can do anything about it.

Therefore, what is the actual value of the HANA discount?

Understanding the Logic for of Trading in Unused Licenses for S/4HANA

SAP often offers customers the ability to trade in unused licenses for a credit towards a HANA or S/4HANA purchase. The motivation by the sales rep is clear, as they are incentivized by SAP to push both of these products. And in fact, some entities that provide SAP licensing advice, advise their clients to do just this.

The logic for Snow Software’s proposal for trading in licenses for S/4HANA is laid out in their article Use S/4HANA to Get Rid of your SAP Shelfware?

In that article they layout the following logic for purchasing S/4HANA.

Let us get into their quotations.

“SAP Business Suite 4 SAP HANA. S/4HANA, for short, is SAP’s latest technology. But it’s also much more than that. S/4HANA represents a fundamental shift in how the mega vendor will generate long-term revenue streams. What is often less-discussed is what S/4HANA means for you, the customer. Not only in terms of technology; but in terms of an opportunity to reshape your relationship with SAP. Without over-dramatizing things, it’s a once-in-a-lifetime opportunity. Why? Because SAP needs S/4HANA to be a success. It needs to demonstrate to investors that it has a business model that is not stuck in the era of on-premise perpetual software licensing. And because it needs to sell S/4HANA licenses, it is offering excellent deals to existing SAP customers to move fast.”

So, what can be seen as left out is that S/4HANA has not been a success and it has had plenty of time to become one. It has a massive installed base (with ECC/Business All in One) on which to sell into, and out research into S/4HANA demonstrates that S/4HANA even in 2019 has little uptake. The details are covered in our research The S/4HANA Implementation Buyer Intelligence Highlights.

Now, while it is true that SAP has a strong desire to show that it’s business model is not suck in an on-premises state, SAP really has Wall Street fooled already on this topic. SAP has successfully adopted cloud speak, and is constantly cloud washing their products. The more you cloud wash, the more Wall Street rewards you. So we have yet another example of an industry that is driven by the opinions of people who don’t have any expertise in the area.

S/4HANA to be Delivered as SaaS?

Secondly, (and don’t tell Wall Street or they will be very very sad) S/4HANA is unlikely to be delivered by SaaS. In our research, it turns out that very few of the implementations have been in the cloud. And in the few that I can find that are stated to be in the cloud or SaaS, they are not cloud or SaaS at all. Instead, they are non-multi-tenant or simply hosted solutions. Customers can expect none of the traditional benefits of SaaS from S/4HANA when delivered this way.

Finally, S/4HANA has nothing to do with the cloud or SaaS.

The quoted paragraph from Snow Software continues:

“And therein lies a huge opportunity for those existing SAP customers, who have typically seen their investments in SAP license increase year-on-year over quite significant periods of time. This is an opportunity to reverse that trend and focus in driving deals with hungry SAP account managers on the licenses and technologies you really need, not the ones you’ve been force-fed over recent years. To understand the scale and opportunity of this shift, we must first look to the past.”

Customers Need S/4HANA?

It is very difficult to argue that anyone “needs” S/4HANA at this point. S4HANA comes with all types of implementation costs and maintenance costs. These costs are far higher than any potential license cost benefit from moving to S/4HANA. In fact, the majority of costs associated with SAP come in maintaining SAP systems, not purchasing SAP systems. I cover this topic in detail in my book on TCO, Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making.

The quoted paragraph from Snow Software continues:

“The fundamental change is that the open architecture of R/3, with the ability to employ third-party databases within the system, is giving way to a more specific database that you’ll require as part of the platform – SAP’s HANA. This is all being done with the promise of improved performance and scalability through in-memory databases.”

Well, the promise of the performance improvement is not analyzed by Snow Software’s article. But as HANA is an analytics database primarily, there is no evidence that an ERP system will run much faster on HANA due to software. Here it is important to draw a distinction between the software side and the hardware side of HANA.

Hardware Improvement?

HANA combines a changed database with SSD memory (instead of a spinning disk) so the performance will automatically increase because of the hardware change (SSD), but not necessarily due to the software.

The quoted paragraph from Snow Software continues:

“The faster it migrates everyone, the quicker it can stop focusing its investment in resourcing and maintaining R/3. So, in a perfect world, SAP would spend nothing on R/2 today and, 10 years from now, it won’t spend any money on R/3.

Moreover, S/4HANA revenue is heavily scrutinized by investors in SAP. The faster they see adoption of this new platform, the quicker that is reflected in the share price for SAP. SAP as a stock needs a growth leg to the story despite its strong position and cash flow.

The transition to S/4HANA requires the replacement of third-party database systems with HANA and there is a monetary uplift from doing this.”

Ok, so this is a strange way of saying that the cost will be higher. The cost of HANA is quite high, and the expensive software is just the beginning. The following quotation will focus on support costs, but the support costs are based upon the license cost. Let us continue with the quotation to see how this is a problem.

Lower Cost for HANA?

The quoted paragraph from Snow Software continues:

“SAP Enterprise support customers currently pay (by default) 22% of license costs in annual maintenance for the use of third-party databases within the architecture of their systems. SAP has steadily over the past few years increased this amount from the 15% level in advance of its migration mandate. In lieu of paying an annual 22% of license costs for your database (typically Oracle), you will pay 15% of license costs for HANA*. Additionally, as an incentive to move to S/4HANA, SAP’s extension policies may enable you to apply unused SAP licenses against a credit for the new purchase. A reduction in the software application value means reduction in overall maintenance to be paid on HANA. *Note that individual circumstances may vary.”

The problem is that Snow Software is making a case for the lower cost of the annual license cost for HANA. However, HANA is the most expensive database on the market. So if you decline from 22% to 15% maintenance, the maintenance is lower, but the base is much higher than the database that HANA replaces.

Secondly, HANA comes with other liabilities, such as indirect access liability, that impact the costs of other software, which are a whole other can of worms and which I have covered in part in other articles.

All of this leads back to a central problem with SAP procurement, it is too often focused on the price of the item, or getting a good deal on the item, and making decisions that seem to make sense in an initial cost of acquisition perspective, without working in enough product knowledge into the equation.

Hiding Pricing Information

The problem with hiding pricing information is that it is used as a control technique by software vendors in order to pry information from the buyers. It also greatly lengthens the process of finding out the pricing information and reduces the comparability of applications. In order to function efficiently, markets require published price information. There are some laws in the US on this topic for consumer products, but not for products purchased by corporations. On several occasions, vendors have sent me non-disclosure agreements (NDA) that covered pricing information. However, this is a misuse of the NDA legal concept, as NDAs are designed to protect proprietary information—technical information, software intellectual property—and not pricing information. The legal phraseology implied that I could be sued for sharing pricing information with a third party if it damaged the company’s business. However, wouldn’t any sharing of pricing information, unless the software vendors were the low-cost provider “damage their business?” Pricing information is part of what makes markets work and should be published. There is a very interesting story about the lack of quantification of fees in the mutual fund industry, which has important connections to TCO but in a different realm.

Hiding Price Information as a Control Technique

The problem with hiding pricing information is that it is used as a control technique by software vendors in order to pry information from the buyers. It also greatly lengthens the process of finding out the pricing information and reduces the comparability of applications. In order to function efficiently, markets require published price information. There are some laws in the US on this topic for consumer products, but not for products purchased by corporations. On several occasions, vendors have sent me non-disclosure agreements (NDA) that covered pricing information. However, this is a misuse of the NDA legal concept, as NDAs are designed to protect proprietary information technical information, software intellectual property and not pricing information. The legal phraseology implied that I could be sued for sharing pricing information with a third party if it damaged the company’s business. However, wouldn’t any sharing of pricing information, unless the software vendors were the low-cost provider damage their business? Pricing information is part of what makes markets work and should be published.

Advice on Enjoying the S/4HANA Quiz

To see the full screen just select the lower right-hand corner and expand. Trust us, expanding makes the experience a whole lot more fun.

 

Conclusion

The pricing templates provided on HANA are not reliable and will not result in a correct SAP HANA cost or SAP HANA price. They will result in the database being undersized. The customer will then need to go back to SAP to purchase more HANA GB licenses. However, if the customer had known the actual cost when they purchase the initial HANA licenses, it very may well have changed their initial purchase decision.

Secondly, the price per GB declines as the size of the database increases. We do not have the information on whether SAP charges an incremental cost for the new HANA licenses or if the customer starts off buying the new HANA GB at “zero.”

However, once data has been migrated and the HANA database has been brought up, there is little in the way of options to move away at that point. The logical decision will be to purchase more incremental GB licenses of HANA. This is only one of the compound features around HANA that most customers have no idea about when the sign the contract.

In our estimate, many IT directors will be hiding the actual results of HANA purchases for years to come.

Who Sanctioned Deliberate Undersizing?

It should also be recognized that this is sanctioned from the very top of SAP. One of the primary proponents of the faulty and undersized footprint estimation of the SAP database has been none other than Hasso Plattner.

  • HANA and S/4 (HANA) are tricky items to price. S/4 HANA has frequently been offered on promotion for free.
  • However, S/4 HANA is not actually fully released as a suite. SAP is adding functionality on what is called a “birthing schedule, ” but by the normal standard applied to applications, S/4 HANA Enterprise Management (EM) (that is the entire suite) is simply not released. SAP was more honest about this in the past, but it has now changed its messaging to pretend that S/4 HANA EM is released. SAP has an on-premises version called 1151 and a cloud version called 1603. 

Furthermore, notice the unusual numbering conventions that are not typical of SAP products.

HANA Pricing and Discounting and S/4HANA EM

Customers should consider HANA discounting to continue into the future. HANA was significantly overpriced, to begin with, and the reality of HANA is nowhere close to the marketing hype. However, HANA also comes with indirect access issues, and due to the lower price, is now being pitched to do things by SAP that it is not the right database type to do.

Therefore, even at a reduced price, there is still an open question regarding value and appropriateness of applications of HANA.

We have been in these systems, and they are not complete. After declaring that S/4 HANA EM is complete, in the next breath that state that every three months S/4 HANA EM will be “more complete,” which is a bit of misdirection on the topic. S/4 HANA EM is not complete, and this truth should be used by customers to argue for either a steep discount on S/4 HANA EM or for the customer to simply wait until the promotion resurfaces. There is very little reason to implement S/4 HANA currently, and it does, in fact, make the most sense to simply wait.

The effect of having an SAP consulting firm into your company is like bringing in a fire hydrant that distributes lies instead of water. As soon as the consulting firm begins advising, it is like a jet stream of falsehoods.

The Problem: How Consulting Firms Coordinate with SAP to Mislead Clients

SAP consulting partners have been hiding everything covered in this article from their clients. Their objective is to cooperate with SAP to extract as much out of the account as possible. It is bizarre that SAP customers look for advice from companies like Deloitte or Infosys that is entirely driven by aggressive sales quotas. Any S/4HANA or HANA purchase and implementation will result in significant amounts of income for the consulting firms. The long-term relationship between SAP and its consulting ecosystem is that SAP proposes what is often false information, and the consulting companies go about agreeing with SAP. We analyze presentations from many SAP, and the consulting firm sent to us from clients from around the world as part of our fact-checking services. The information presented by SAP consulting firms to their clients is primarily of low quality, and we think known to be false (at least to some degree) by the consulting firms submitting this to their clients.

Being Part of the Solution: What to Do About HANA

SAP and the consulting firms rely on providing information without any fact-checking entity to contradict the information they provide. This is how companies end up paying for a database that is exorbitantly priced, exorbitantly expensive to implement and exorbitantly expensive to maintain.

The Necessity of Fact Checking

We ask a question that anyone working in enterprise software should ask.

Should decisions be made based on sales information from 100% financially biased parties like consulting firms, IT analysts, and vendors to companies that do not specialize in fact-checking?

If the answer is “No,” then perhaps there should be a change to the present approach to IT decision making.

In a market where inaccurate information is commonplace, our conclusion from our research is that software project problems and failures correlate to a lack of fact checking of the claims made by vendors and consulting firms. If you are worried that you don’t have the real story from your current sources, we offer the solution.

Financial Disclosure

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 HANA and S/4HANA Pricing and Costs Content

References

I cover how to interpret risk for IT projects in the following book.

https://www.sap.com/products/hana.html

*https://upperedge.com/sap/sap-announces-4q-revenue-shortfall-is-it-time-to-discount-hana/

https://www.snowsoftware.com/int/blog/2016/09/20/use-s4hana-get-rid-sap-shelfware-pt-1#.WBzBfY_XJ-Y

The Risk Estimation Book

Rethinking Enterprise Software Risk: Controlling the Main Risk Factors on IT Projects

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.

Chapters

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

Risk Estimation and Calculation

Risk Estimation and Calculation

See our free project risk estimators that are available per application. The provide a method of risk analysis that is not available from other sources.

project_software_risk

The Secret to Not Talking About The Cost of SAP HANA

Executive Summary

  • SAP HANA costs are extremely high, but there is a blackout on this topic as so many entities are aligned with SAP.
  • We honestly cover the total cost implications of HANA.

Introduction to SAP HANA Costs

I was recently interacting with a person on LinkedIn, and I brought up the topic of SAP HANA’s costs. This person responded that they did not know why I was bringing up costs!

Wow, what a comment.

A Consistent Theme to Treat SAP HANA Costs as a Verboten Topic

This has been a consistent theme that I have noticed with regards to HANA, where lots of ink is given to discussing the benefits of HANA but so little time is spent discussing its costs. It is almost as if it is a taboo subject. On the other hand, HANA is often presented as reducing TCO. So if that is true, then obviously the first place to start is to figure out what it costs to buy and operate.

SAP HANA Costs

Here is the truth.

HANA is quite expensive. It is expensive in hardware, software as well as resources which bill at the top of the market and which are difficult to find. I have heard of big consulting companies charging roughly $350 per hour for them, and that adds up fast.

HANA hardware alone is typically going to come to $1 million.

SAP has provided some insight into these costs which are not part of the SAP price list (that is not kept private). They have provided total cost of ownership numbers, or TCOs for SaaS. However, these come to:

  • $2.7 million for 1TB for HANA Cloud Platform
  • $5.9 million for HANA Enterprise four years (these are 2014 numbers).

Now Amazon Web Services (AWS) which provides transparency regarding costs. They offer up to 2 TB of RAM per instance. This means that HANA on AWS can be priced, although the data volumes are necessary to have (AWS has Business All in One, Business One, Business Objects, among others).

SAP HANA’s Misleading Pricing

Now if we move to the applications that use HANA, a Finance purchase and implementation is going to be much more than an FI/CO implementation. I have found this myself, but this is the story I have repeatedly heard from sales reps that sell HANA.

Why SAP HANA’s Pricing is So Misleading

HANA’s price is at first blush straightforward. It is priced per GB and quite expensive. But the problem is SAP proposes ridiculous reductions in the database footprint that will not turn out to be correct (around a 98.5% reduction). Thus almost every HANA purchase is based upon false assumptions. Second, the associated costs make it tough to price entirely. This is particularly the case because it is so difficult for find use cases that can cover HANA’s high costs.

The expense of HANA is a primary reason why HANA has been so limited in its market acceptance.

Details of the Costs Associated with Moving to SAP HANA

SAP often presents HANA as sort of a “slam dunk” purchase.

According to SAP, HANA has a lower TCO than any other competition database.

  • It implements faster than any other competing database (even when a database is already installed).
  • It has more innovation than any different competing database.
  • It has better performance than any other database.
  • It has better performance in every dimension than any other competing database.

Is any of this true? 

While at Brightwork we hate bursting people’s bubbles, but the truth is quite a bit more complicated than what is commonly presented by SAP and SAP’s surrogates on HANA.

In this article, we will cover the complications of using HANA from the licensing and database administration.

How SAP HANA is Problematic from the Administration Side

SAP’s “new” ERP system called S/4HANA and which is not new, only runs on HANA. However, many large corporations have set Oracle or IBM DB as corporate DB standards, and this restriction of S/4 makes it difficult for companies to streamline administrations.

This is something that is entirely left of SAP’s marketing on HANA.

How SAP HANA is Problematic from the Licensing Side

And many companies have what we called unlimited Oracle license which allows them to use any number of Oracle DB for a predetermined price. Adding HANA will not reduce their DB cost but will, in fact, increases the overall DB costs. That is HANA becomes a “net increase” in license and therefore support cost.

Brightwork Research & Analysis recently performed the first independent study into HANA’s TCO. And this issue complicates the licensing estimations of HANA versus competitive databases.

And for those that purchased Oracle DB from SAP, they will have to continue to pay the same maintenance for Oracle DB throughout even if they want to move to HANA as long as there are any SAP systems still running on Oracle DB.

This translates into double the database maintenance fees during the period of migration which can take years if there are many large SAP systems running currently. However, the average we use is 1.25 years. That is we assume that HANA can be taken live in 1.25 years from when the HANA implementation begins.

The Overall Cost Implications

Long story short, this greatly increases the costs of moving to HANA. This also explains the multiple areas of costs and how HANA uniquely uses, which must be considered to come up with a representative TCO.

The Oracle database or IBM database that the customer is using today is considered sunk cost. Therefore if the customer is to move to HANA, they are the sunk costs that they have incurred previously and rebuying a new database all over again. Something that they could simply save just staying with the Oracle and IBM databases that they already have.

SAP HANA is the Highest Overhead Database

We won’t go into this much in this article, because we cover it in detail in our research A Study into SAP HANA’s TCO, but the amount of complexity that HANA exposes customers to is substantial. The reason for that overhead is predominantly the instability of HANA. This combines with a very high cost of resources as HANA resources charge at the top of the market. This is covered in part by the quotation from SAP Nation 2.0.

“Liz Herbert, an analyst at Forrester wrote about the diversity around the HANA product alone: “clients struggle to keep up with the rapidly evolving landscape of HANA — an ever growing list of solutions that includes HANA, HANA Cloud, HANA Enterprise Cloud, S/4HANA, Simple Finance and others.””

The TCO of SAP HANA

One could see something like the following representing the cost magnitude per cost area of using HANA:

  1. Costs of Hana DB ($$$$) $0 if staying put on existing anyDB.
  2. Costs of new hardware Infrastructure ($$$)
  3. Costs of reimplementation ($$$$$)
  4. Costs of retraining ($$$)
  5. Costs of higher downtime ($$$$$$)

We have estimated the TCO of HANA vis-a-vis competing databases in the article A Study into HANA’s TCO.

The Question of Why HANA is Selected?

Why is HANA being selected in these cases where it is not only the highest price option but the highest price option by a factor of quite a few multiples?

So why would this be the case?

Well, one reason can be the incentives of the IT decision makers. In the article To Whom Does Your IT Department Owe Its Allegiance, I question SAP shops that seem to select SAP no matter the actual outcomes. The reasons for this are often that the people in these IT shops see SAP as their primary skill, which includes managing SAP implementations. This means that these IT decision makers need to continue to oversee SAP projects in order to continue to develop their career.

Why Choose HANA?

After having analyzed HANA from many dimensions, it is extremely difficult to see the value of HANA. HANA’s design is extremely limited to analytical applications, although in the article Which is Faster HANA or Oracle 12c, it is explained that HANA does not, as proposed by SAP perform well in transaction processing. Secondly, HANA would have to have a very high TCO. This is true because HANA is so much less mature than the databases that it competes against, and even now it is difficult to find very experienced HANA skills.

This is why the two most likely reasons why HANA would be selected is that:

  • The buyer believes the exaggerations of HANA which are covered in the article When Articles Exaggerate the Benefits of HANA.
  • The IT decision maker has the incentive to continue to have SAP on their resume, versus other vendors.

There is not a single reason to change from Oracle or whatever else the client is using to jump to HANA. Furthermore, HANA has indirect access concerns and data lock-in that other databases do not have. HANA is exorbitant in both license cost and implementation cost. Companies that primarily put in HANA have IT departments that are remotely controlled by SAP or were tricked into purchasing the database by performance promises that it is now clear never had any basis in fact.

I cover this in the following article What is the Actual Performance of HANA?.

Some SAP Shops Prefer HANA

IT departments that are essentially self-reinforcing with HANA. I do not believe there are studies of the effect of HANA in companies because the IT department wants merely the implementation to be considered a success. So they can always say that this or that processed faster. If I were to audit HANA implementations and were to come up with non-complimentary information, the IT department would bar me from using either their client name and if they could, any information about my findings. For each HANA implementation, the only right answer according to IT is that the HANA implementation was a success. And of course, all the decision makers in IT deserve new titles.

Something significant to consider is that IT departments get positive reinforcement from SAP for buying and implementing HANA, whether HANA benefits the business, or benefits it close to what an alternative investment would benefit the business.

HANA’s value proposition is not competitive with other investments a company could make. I question any IT department that has purchased HANA and do not believe it is possible to justify on its merits. And this leads to a different point.

Wasting The IT Budget on HANA

I meet with so many companies that don’t have the budget for really logical simple things. I could provide a list of things ranging from the bill of material management software to forecasting software that would have a much higher payback than a HANA purchase and implementation. In fact, at one of my client’s, they could not put in very basic improvements that I recommended and were hoping for free stuff from me because they were so budget constrained. The things they could not afford was lengthy. They could not hire or pay their planners well enough. They could not maintain their current systems. Could not provide a forecasting system, could not maintain their master data parameters for MRP.

However, for some reason, they had the money for a HANA upgrade. After all the things I listed as shortcomings, how could HANA, a luxury expenditure with such a limited upside and so uncompetitive versus the alternatives be approved for purchase and implementation?

It is a very dysfunctional system to have a company like SAP continually pulling resources out of companies that could be used for far better purposes. SAP is significantly to blame. But so are IT departments. Every year that I get older, I esteem the decision-making ability of IT departments a little bit less. These problems stem from a very poor ability to discern between biased and unbiased information sources.

Advice on Enjoying the Quiz

To see the full screen just select the lower right-hand corner and expand. Trust us, expanding makes the experience a whole lot more fun.

 

Conclusion

There is no point in putting off cost considerations and not discussing HANA costs. Yet, so many authors do this. They list the benefits of HANA without listing the costs.

For those interested in specifically HANA’s pricing (along with S/4HANA’s pricing) see the article How to Understand Pricing for S/4HANA and HANA.

SAP’s Inaccurate Messaging on HANA as Communicated in SAP Videos

Fact-Checking SAP’s HANA Information

This video is filled with extensive falsehoods. We will address them in the sequence they are stated in this video.

SAP Video Accuracy Measurement

SAP's Statement
Accuracy
Brightwork Fact Check
Link to Analysis Article
HANA is a Platform
0%
HANA is not a platform, it is a database.How to Deflect You Were Wrong About HANA
HANA runs more "in-memory" than other databases.
10%
HANA uses a lot of memory, but the entire database is not loaded into memory.How to Understand the In-Memory Myth
S/4HANA Simplifies the Data Model
0%
HANA does not simplify the data model from ECC. There are significant questions as to the benefit of the S/4HANA data model over ECC.Does HANA Have a Simplified Data Model?
Databases that are not HANA are legacy.
0%
There is zero basis for SAP to call all databases that are not HANA legacy.SAP Calling All Non-HANA DBs Legacy.
Aggregates should be removed and replaced with real time recalculation.
0%
Aggregates are very valuable, and all RDBMS have them (including HANA) and they should not be removed or minimized in importance.Is Hasso Plattner Correct on Database Aggregates?
Reducing the number of tables reduces database complexity.
0%
Reducing the number of tables does not necessarily decrease the complexity of a database. The fewer tables in HANA are more complicated than the larger number of tables pre-HANA.Why Pressure SAP to Port S/4HANA to AnyDB?
HANA is 100% columnar tables.
0%
HANA does not run entirely with columnar tables. HANA has many row-oriented tables, as much as 1/3 of the database.Why Pressure SAP to Port S/4HANA to AnyDB?
S/4HANA eliminates reconciliation.
0%
S/4HANA does not eliminate reconciliation or reduce the time to perform reconciliation to any significant degree.Does HANA Have a Simplified Data Model and Faster Reconciliation?
HANA outperforms all other databases.
0%
Our research shows that not only can competing databases do more than HANA, but they are also a better fit for ERP systems.How to Understand the Mismatch Between HANA and S/4HANA and ECC.

The Problem: A Lack of Fact-Checking of HANA

There are two fundamental problems around HANA. The first is the exaggeration of HANA, which means that companies that purchased HANA end up getting far less than they were promised. The second is that the SAP consulting companies simply repeat whatever SAP says. This means that on virtually all accounts there is no independent entity that can contradict statements by SAP.

The Necessity of Fact Checking

We ask a question that anyone working in enterprise software should ask.

Should decisions be made based on sales information from 100% financially biased parties like consulting firms, IT analysts, and vendors to companies that do not specialize in fact-checking?

If the answer is “No,” then perhaps there should be a change to the present approach to IT decision making.

In a market where inaccurate information is commonplace, our conclusion from our research is that software project problems and failures correlate to a lack of fact checking of the claims made by vendors and consulting firms. If you are worried that you don’t have the real story from your current sources, we offer the solution.

Inaccurate Messaging on HANA as Communicated in SAP Consulting Firm Videos

For those interested in the accuracy level of information communicated by consulting firms on HANA, see our analysis of the following video by IBM. SAP consulting firms are unreliable sources of information about SAP and primarily serve to simply repeat what SAP says, without any concern for accuracy. The lying in this video is brazen and shows that as a matter of normal course, the consulting firms are happy to provide false information around SAP.

SAP Video Accuracy Measurement

SAP's Statement
Accuracy
Brightwork Fact Check
Link to Analysis Article
HANA runs more "in-memory" than other databases.
10%
HANA uses a lot of memory, but the entire database is not loaded into memory.How to Understand the In-Memory Myth
HANA is orders of magnitude faster than other databases.
0%
Our research shows that not only can competing databases do more than HANA, but they are also a better fit for ERP systems.How to Understand the Mismatch Between HANA and S/4HANA and ECC.
HANA runs faster because it does not use disks like other databases.
0%
Other databases also use SSDs in addition to disk.Why Did SAP Pivot the Explanation of HANA In Memory?
HANA holds "business data" and "UX data" and "mobile data" and "machine learning data" and "IoT data."
0%
HANA is not a unifying database. HANA is only a database that supports a particular application, it is not for supporting data lakes.
SRM and CRM are part of S/4HANA.
0%
SRM and CRM are not part of S/4HANA. They are separate and separately sold applications. SAP C/4HANA is not yet ready for sale. How Accurate Was Bluefin Solutions on C-4HANA?
Netweaver is critical as a platform and is related to HANA.
0%
Netweaver is not relevant for this discussion. Secondly Netweaver is not an efficient environment from which to develop.
HANA works with Business Objects
10%
It is very rare to even hear about HANA and Business Objects. There are few Buisness Objects implementations that use HANA.SAP Business Objects Rating
Leonardo is an important application on SAP accounts.
0%
Leonardo is dead, therefore its discussion here is both misleading and irrelevant.Our 2019 Observation: SAP Leonardo is Dead
IBM Watson is an important application on SAP accounts.
0%
Watson is dead, therefore its discussion here is both misleading and irrelevant.How IBM is Distracting from the Watson Failure to Sell More AI and Machine Learning
Digital Boardroom is an important application on SAP accounts.
0%
SAP Digital Boardroom is another SAP item that has never been implemented many places.

Financial Disclosure

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 HANA and S/4HANA Pricing and Costs Content

References

https://www.oracle.com/us/corporate/license-management-services/unlimited-license-agreement-2613729.pdf

*https://www.amazon.com/SAP-Nation-2-0-empire-disarray-ebook/dp/B013F5BKJQ

Costs are of course quite important to IT decision making. I cover TCO in depth in the following book.

TCO Book

 

TCO3

Enterprise Software TCO: Calculating and Using Total Cost of Ownership for Decision Making

Getting to the Detail of TCO

One aspect of making a software purchasing decision is to compare the Total Cost of Ownership, or TCO, of the applications under consideration: what will the software cost you over its lifespan? But most companies don’t understand what dollar amounts to include in the TCO analysis or where to source these figures, or, if using TCO studies produced by consulting and IT analyst firms, how the TCO amounts were calculated and how to compare TCO across applications.

The Mechanics of TCO

Not only will this book help you appreciate the mechanics of TCO, but you will also gain insight as to the importance of TCO and understand how to strip away the biases and outside influences to make a real TCO comparison between applications.
By reading this book you will:
  • Understand why you need to look at TCO and not just ROI when making your purchasing decision.
  • Discover how an application, which at first glance may seem inexpensive when compared to its competition, could end up being more costly in the long run.
  • Gain an in-depth understanding of the cost, categories to include in an accurate and complete TCO analysis.
  • Learn why ERP systems are not a significant investment, based on their TCO.
  • Find out how to recognize and avoid superficial, incomplete or incorrect TCO analyses that could negatively impact your software purchase decision.
  • Appreciate the importance and cost-effectiveness of a TCO audit.
  • Learn how SCM Focus can provide you with unbiased and well-researched TCO analyses to assist you in your software selection.
Chapters
  • Chapter 1:  Introduction
  • Chapter 2:  The Basics of TCO
  • Chapter 3:  The State of Enterprise TCO
  • Chapter 4:  ERP: The Multi-Billion Dollar TCO Analysis Failure
  • Chapter 5:  The TCO Method Used by Software Decisions
  • Chapter 6:  Using TCO for Better Decision Making

TCO Calculator

TCO Calculator

Brightwork Research & Analysis offers the following free TCO calculators. See by clicking the image below:

calculate_tco