SAP S/4HANA TCO: the data-volume line item that most calculators leave out

The TCO calculator on the partner's screen is well-engineered. Migration phase: discrete cost, time-bounded. License: per-user, per-module, fixed. Hosting: per-node, fixed. Productivity uplift: modeled as recurring benefit. The output is a clean five-year curve and a defensible NPV.

The architecture lead asks a quieter question: where in this model is data volume? The partner explains that data volume informs node count, which is captured in hosting. The architecture lead presses: but is data volume modeled as growing? A pause. The answer is: no, it is treated as a fixed input.

The output curve is clean because the model treats the cost driver that actually shapes the curve as a constant. The model is wrong in a specific and consequential way.

This is the structural blind spot in most S/4HANA TCO calculators in circulation, and it is the reason the post-cutover variance against the business case is usually negative on the recurring line.

Step One — The Wrong Assumption

TCO is licenses, infra, and integration.

"We modeled licenses, infrastructure, and integration. That's TCO."

— Standard pre-board TCO framing

The assumption defines TCO by what is easy to budget — licenses, infrastructure, integration — and treats data volume as an input to those buckets rather than a recurring driver in its own right. The omission becomes load-bearing the moment data volume changes faster than the buckets it feeds. In practice, data volume grows with operational time at a rate that the bucketed model does not represent, so the model's projection diverges from reality starting at cutover and the divergence compounds.

Step Two — The Partial Signal

Year-one actuals come in, and the recurring line is the variance.

The partial signal is the post-year-one variance. License is on-model, integration is on-model, hosting has a recurring overshoot, and the recurring overshoot traces back to nodes that were provisioned to absorb data growth that was not in the model. The partner explains the overshoot in operational terms (the data grew faster than projected); the honest read is that the model did not have a way to project it accurately.

Step Three — The Failed Fix

Adjusting the growth assumption rather than the model structure.

The failed fix is parameter tuning. The team revises the growth assumption upward and reruns the calculator. The new projection is closer to actuals; the structural problem is unchanged. The fix is failed because the data-volume growth rate is itself a function of operational time and retention discipline — both variables the model still treats as inputs. Twelve months later, the actuals are again above projection, because the projection still does not include retention as a managed lever.

Fig. 1 — The line item the calculator leaves out is the one that drives the recurring number. Adding it changes the case the program runs against.

Step Four — The Real Failure

The actual failure is treating data volume as a fixed input.

The real failure is structural to the calculator. Data volume in a real SAP estate is not a fixed input; it is a variable shaped by retention discipline, archive-object scope, ILM policy, and the operational growth rate of the business itself. A TCO model that treats data volume as a single number — rather than as a managed lever — is omitting the lever that determines whether the recurring cost line goes up, stays flat, or comes down.

Calculators built with the line item included make a different recommendation. They show the present value of the retention discipline. They show the cost of the un-retention option. They show the difference, year over year, between a program that runs retention as a discipline and one that does not. The difference is large, durable, and recurring.

Step Five — The Definition

Now the definition lands.

Data-volume-aware S/4HANA TCO is a TCO discipline that models data volume as a managed line item — with the retention regime as a recurring cost lever — rather than as a fixed input feeding the hardware bucket.

The framing matters because it changes what the board approves. A board that has seen the data-volume line is approving a different commitment than a board that has not. The commitment includes the retention discipline that the recurring number depends on.

What Solix Enforces

Data volume as a managed line item, retention as a recurring discipline.

What Solix runs in this category is the recurring discipline behind the line item: ILM-governed retention, certified archiving execution, NLS for the cold tier, and the operational practice of treating data volume as a number the program can move rather than a number the program discovers. The board case becomes a commitment the program can hold against, year over year.

Three things to do this week

• Rebuild your S/4HANA TCO model with a data-volume line item. Add a line that explicitly models data volume — current, projected, and managed-with-retention — feeding the node count, license tier, backup, and DR lines. The output curve will be different. Show the board the difference.
• Add a managed-retention scenario to the case. Model three scenarios: no retention discipline (data grows at organic rate), one-time reduction (archiving project pre-migration, no ongoing discipline), and recurring retention (ILM and NLS run as ongoing). The recurring scenario is almost always the lowest-NPV path.
• Make the data-volume line a board-visible KPI. Once approved, report data volume against the modeled curve quarterly. The discipline of reporting against the line item is what keeps the retention regime from regressing to the unmanaged default.

References

• SAP Help Portal — Nearline Storage for SAP BW and SAP BW/4HANA. Nearline storage is the mechanism that makes the data-volume line item moveable.
• SAP Help Portal — SAP Information Lifecycle Management (ILM) — Overview. ILM is the policy layer that operationalizes retention as a recurring discipline.
• Gartner press — Gartner Forecasts Worldwide Data Management Software Spending. Gartner's data-management forecast tracks the broader pattern of retention-tier spend as a separate line item.
• Forrester — Forrester Wave: Data Management for Analytics. Forrester's research on data-platform TCO underlines the structural impact of unmanaged data growth.
• IDC press — IDC Worldwide Global DataSphere Forecast. IDC's global datasphere forecast establishes the growth assumption a credible TCO model has to start from.