RISE for utilities. Thirty year assets, seven year subscriptions.

Utility operators in electricity, gas, water, and district heating operate against asset lifecycles measured in decades. A transmission line is depreciated across forty years. A power station carries a thirty year operating horizon. A regulatory price control runs for five to eight years and locks revenue trajectories that the business must hit. The SAP landscape that supports the utility, from ISU billing through plant maintenance through the regulated cost accounting, operates inside this lifecycle and must therefore plan against it. A seven year RISE with SAP subscription, signed against a thirty year asset and a five year regulatory window, requires negotiation positions that other industries can safely ignore. This article walks through the specific structural issues utilities face inside RISE and the positions the buyer team should hold at the negotiation table.

The asset lifecycle mismatch.

The first structural issue is the mismatch between the asset lifecycle and the subscription term. A utility plans capital expenditure across decades and must demonstrate that operating systems will remain available and supportable across the same horizon. A seven year RISE term covers a small fraction of the asset life and introduces a renewal cycle that creates renegotiation risk every seven years. The risk compounds over the asset horizon. Across a thirty year asset, the utility faces four to five renewal cycles with the same vendor, each of which is an opportunity for pricing leverage to shift toward SAP. The buyer position must therefore engage the lifecycle question explicitly, with renewal protections drafted into the first contract that anchor pricing trajectories across multiple cycles rather than across the first term alone.

The specific protections include a renewal cap on the bundled price uplift, a defined methodology for the unit price benchmarking at each renewal, and an extension right that allows the utility to extend the existing term at the existing economics rather than entering a fresh renewal negotiation under different conditions. The protections are unusual in the SAP standard playbook and must be negotiated as bespoke language. They are also significantly more valuable to a utility than to a buyer in a faster moving industry, because the asset horizon makes the renewal exposure structurally larger.

The regulatory price control window.

A regulated utility operates inside a regulatory price control that defines allowable costs, revenue trajectories, and the rate at which operating expenditure can be recovered from customers. The price control window typically runs five to eight years, with mid period reviews that may adjust the allowance. Any change in the SAP operating cost during the control window flows directly to the utility margin unless the regulator approves a corresponding allowance adjustment. The implication for a RISE negotiation is that the bundled price needs to be predictable across the control window, with indexation, expansion, and overage exposures all bounded to the magnitudes that the regulatory submission anticipates.

The buyer position should therefore include a hard cap on the year over year subscription increase, drafted to align with the regulator allowance trajectory, and a defined methodology for any expansion that the business undertakes during the control window. The position should also include a contractual confirmation that the SAP team will support any data extraction the regulator requires for the cost review, at no additional cost, within a defined service window. The regulator may demand operating cost evidence in formats the SAP team has not previously delivered. A contractual obligation to support the requirement, drafted into the order form, removes a category of friction that emerges otherwise at the worst possible moment.

Seasonality and demand peaks.

Utility billing systems run heavy at month end, quarter end, and during seasonal demand peaks. Winter heating peaks, summer cooling peaks, and meter reading cycles produce computational load patterns that differ materially from steady state operations. The RISE infrastructure layer must be sized against the peaks rather than against the average, otherwise the seasonal performance degrades and customer impact becomes visible in the contact centre. The buyer position should therefore include explicit capacity provisioning against documented peak profiles, with performance commitments tied to the peak load rather than the steady state.

The position also extends to the hyperscaler reservation strategy. SAP commitments are typically structured against the steady state, with peak capacity drawn from on demand allocation. The on demand allocation carries a price premium that compounds during peak periods. The utility position should be that the reservation covers a defined percentage of the documented peak, not the steady state, and that the peak capacity is dedicated rather than burstable from a shared pool. The reservation strategy has direct cost implications that the SAP infrastructure team must price into the bundled rate.

A utility plans capital expenditure across decades. The SAP landscape that supports it operates inside this lifecycle and must plan against it.

ISU and the legacy of utility specific extensions.

The utility SAP landscape typically includes ISU, the Industry Solution Utilities billing module, alongside the core S/4HANA application. ISU carries deep customisation in most utility operations, with extensions for tariff calculation, meter integration, and revenue assurance that have been built and refined over decades. The migration to S/4HANA Cloud Private Edition under RISE inherits the extensions and must continue to support them. The buyer position should require explicit confirmation that the existing ISU extensions will operate under RISE, with a defined remediation programme for any extension that cannot be carried forward.

The position should also engage the future trajectory of the utility specific functionality. SAP is investing in S/4HANA Utilities for Customer Engagement and related cloud native components. The utility should require visibility into the roadmap, with commitments around feature parity for the existing ISU footprint, before agreeing to a multi year RISE term that locks the utility into a trajectory that the SAP product team may subsequently change.

Compliance and audit obligations.

Utilities face audit obligations from the regulator, from environmental authorities, from financial regulators, and from grid operators. The audits require evidence on operating cost, on system availability, on data integrity, and on cybersecurity controls. The RISE subscription environment must support the audit obligations, with audit rights drafted into the contract that permit access to logs, configurations, and operational records that the regulator may require. The buyer position should require explicit audit access provisions, drafted to align with the specific regulatory obligations the utility carries in each jurisdiction.

The position is more comprehensive for a utility than for a typical commercial buyer because the audit obligations are statutory rather than contractual. A regulator demanding evidence cannot be told that the data is unavailable due to a vendor restriction. The buyer must be able to produce the evidence, and the contract must guarantee the access that produces it.

Long term partnership versus contractual protection.

The SAP commercial team often frames the utility relationship as a long term partnership, with the implication that the contractual detail is less important than the trust between the organisations. The framing is comfortable for the SAP team and dangerous for the utility. The trust may persist across leadership changes on both sides. The contract certainly will. The utility position should be that the partnership is welcome and the contractual protection is essential, with the protection drafted to operate in the absence of the trust as well as in its presence.

Conclusion.

Utilities face structural issues inside a RISE negotiation that other industries can pass over. The asset lifecycle mismatch, the regulatory price control window, the seasonal demand peaks, the ISU legacy, and the audit obligations together demand a negotiation position with components that the SAP standard playbook does not include. The position takes longer to assemble. The protections take longer to negotiate. The reward is a subscription environment that supports the utility across decades rather than across a single seven year term, with pricing trajectories that the regulator can accept and audit obligations that the contract can satisfy. Utilities that take the additional time to engage the position systematically routinely produce seven year outcomes that are twenty to thirty percent below the initial SAP proposal, with renewal trajectories that protect them across the asset horizon. The investment is significant. The return on the investment, measured across the asset life rather than the contract term, is significantly larger.