① Guide · Industry estate patterns
Electric, gas, and water utilities run billing and customer systems on the mainframe under a constraint other sectors do not share: every dollar of software cost is eventually scrutinized by a regulator and recovered from rate payers. That changes how a utility should negotiate. Here are the estate patterns, the seasonal peak that sets the bill, and the merger traps that decide cost.
A utility does not just pay for its software. It has to justify the cost to a commission.
The mainframe in a large utility sits under the most regulated workloads the business runs. Customer information systems, billing engines, meter data management, and work and asset management at electric, gas, and water utilities commonly run on z/OS because they are high volume, transactional, and intolerant of error. A billing mistake at utility scale is a regulatory event, not a help desk ticket, so these systems stay on the platform that has proven it can run them, and the IBM, Broadcom (CA), BMC, and Compuware (BMC) software that supports them stays on long renewal cycles alongside them.
What makes utility licensing distinct is not the technology. It is the accountability. Software spend in a regulated utility flows into rate cases, where the prudence of every recovered cost can be questioned. That gives a utility a reason to negotiate hard that other buyers lack, and it gives the licensing team a defensible story to tell when it does. This guide covers the three patterns that decide utility software cost: the regulated cost recovery frame, the seasonal billing peak, and the merger driven estate change that consolidation keeps producing. For the underlying disciplines see cost optimization and renewal advisory.
Software spend recovered through rates is spend a regulator can call imprudent. That cuts both ways. It pressures the utility to hold costs down, and it gives the negotiation a purpose the vendor cannot dismiss. A renewal uplift that cannot be justified to a commission is one the utility has a documented reason to refuse.
Billing volume rises and falls with the weather. Summer cooling and winter heating drive consumption, estimation reruns, and high bill complaint cycles that lift the rolling four hour average in predictable months. Sub-capacity charges follow that peak, so a utility pays all year for a peak a few seasons create unless it manages the window.
Utility consolidation is constant, and every merger reopens the license position. Vendors often treat a combination as a trigger to revalue, and a merged entity running two estates on one set of agreements can find itself double counted. The combined position should be modeled before close, not discovered in the first post merger audit.
| Workload | Typical platform role | The buyer lever |
|---|---|---|
| Customer information and billing | Core z/OS, high transaction volume, regulated for accuracy | Seasonal R4HA management; the largest single consumer |
| Meter and usage data | Batch heavy, growing with smart meter rollout | Reschedule reads off the online peak; watch data growth creep |
| Work and asset management | Transactional, field and outage driven | Storm and outage spikes lift the peak; size for them deliberately |
| Db2 for z/OS data layer | System of record under billing and CIS | IPLA tools licensed on capacity; cut the MSU they price on |
| Tools estate (Broadcom, BMC, Compuware) | Scheduling, output, performance, change management | Portfolio consolidation and competitive displacement as leverage |
Estate composition varies widely by utility size, regulatory jurisdiction, and modernization stage. The workloads above are common patterns, not a fixed standard.
Customer information, billing, meter data, and work and asset management at large utilities commonly run on z/OS because the workloads are high volume, transactional, and regulated for reliability. A billing error at scale is a regulatory event, so these systems stay on the proven platform, and the software that supports them stays on long renewal cycles.
Billing volume swings with the weather. Summer cooling and winter heating drive consumption and high bill complaint cycles that lift the rolling four hour average in predictable seasons. Because sub-capacity charges follow that peak, a utility that does not manage its seasonal R4HA pays year round for a peak a few months create.
Consolidation is common, and each merger reopens the question of whose contracts survive and whether the combined estate is licensed for the combined load. Vendors often treat a merger as a trigger to revalue. Model the combined position before the deal closes, not in the first post merger audit.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Facing a rate case or a merger that touches the estate? We model the license position before it is questioned.
The regulator is a reason to negotiate, not an excuse to overpay.
Related industry guides: banking, where the regulators add a layer, insurance estate patterns, and telecom. Practice: license transfer in mergers and acquisitions and capacity planning with software cost. Commercial: mainframe cost optimization.