An S/4HANA conversion, trimmed by $9.2M.

The client brief

The utility operated an ECC 6.07 estate licensed for 6,200 Named Users alongside SAP IS-U for industry-specific billing and metering, a full FI/CO engine block, BW for regulatory reporting, and Solution Manager. The S/4HANA on-premise conversion programme was board-approved with a target go-live eighteen months out.

SAP's account team had quoted the conversion at $28.4M of incremental licence value across the next 36 months, principally driven by IS-U engine uplift, an HANA database extension, and a Named User band reset that pushed the entire Professional User population from the prior contract tier to the S/4HANA standard tier.

The IT Director engaged us with a brief that was characteristic of regulated utilities — the conversion had to clear an internal capital-allocation review, and the cost case had to survive an external rate-case audit. The figures had to be defensible to a public utility commission, not just to internal procurement.

SAP's opening position

SAP's opening position rested on three engine lines. IS-U was quoted at $14.6M based on metering-point counts of approximately 3.2 million, the utility's regulated meter population including retired endpoints. The HANA database extension was quoted at $5.2M on a database size projection from the prior conversion estimate, not from the current production footprint. The Named User band reset added approximately $4.8M across the 6,200-user population. The remaining $3.8M was distributed across smaller line items including a new BW/4HANA migration uplift and an analytics module add-on.

The metering-point count for IS-U was particularly contentious. The contractual definition counted active billable meters; the SAP measurement counted all meters in the IS-U master data including retired and disconnected endpoints. The variance was approximately 480,000 meters — about fifteen per cent of the reported population.

The Named User reset was framed as a contractual reconciliation. The S/4HANA standard tier carried a higher per-user price than the legacy ECC tier on the prior agreement. SAP's position was that the conversion triggered re-tiering across the entire chargeable population.

The defence tactics

Four reconstructions carried most of the reduction; a fifth — the contractual rebuttal on the Named User reset — closed the remaining gap.

Metering-point reconciliation

We pulled the IS-U master data and reconciled active billable meters against retired and disconnected endpoints. The active billable population was 2.72 million against the reported 3.2 million. The reconciliation was documented in a one-page analyst note presented to SAP's account team. The IS-U baseline reduced by approximately fifteen per cent against the opening figure.

HANA database footprint rebuild

The HANA database extension was carried on a projected database size from a prior conversion estimate. We measured the current production database footprint and rebuilt the projection against the conversion architecture. The revised projection reduced the database extension cost by approximately forty-one per cent.

Named User band documentation

We documented twelve months of transaction evidence for the entire Named User population. Approximately 1,400 of the 6,200 users had activity supporting a downgrade from Professional to Limited Professional. Another 600 had ESS-only activity supporting a further downgrade. The reclassified population removed approximately $1.7M from the band-reset line.

BW/4HANA migration uplift removal

The BW/4HANA migration uplift was quoted as a separate licence line. We presented the contractual analysis that the BW migration was included in the master agreement's database conversion right. SAP retracted the line item after one round of correspondence.

The settled position

The S/4HANA conversion closed at $19.2M of incremental licence value against the opening $28.4M, a thirty-two per cent reduction. The conversion contract was structured with the engine measurements documented as contractual baselines, with annual reconciliation rights against the utility's evidence.

Contractually, we secured a metering-point definition tied to active billable endpoints with quarterly reconciliation rights, an HANA database extension priced on actual database size with annual measurement, and a Named User band reassessment right with thirty days of advance documentation.

The utility's regulatory affairs team adopted the engine-reconciliation evidence as part of the standing rate-case file. The documentation now serves a dual purpose: SAP licence defence and public utility commission audit defence.

Five takeaways

1. Engine measurements in utility estates are particularly susceptible to inflation through master-data drift. The retired-endpoint cleanup typically removes ten to twenty per cent of metering-point counts.
2. HANA database extensions are routinely quoted on projected footprints. The current-measurement rebuild typically reduces the extension cost by thirty to fifty per cent.
3. Named User band resets at S/4HANA conversion are negotiable through transaction evidence. The reclassification work is the same as USMM remediation.
4. BW/4HANA migration uplifts are sometimes already included in the master agreement's database conversion right. Check the contract before accepting the line.
5. Regulated utilities have a second audience for licence evidence — the public utility commission. The same documentation serves both.