Home  ›  Blog  ›  Energy & Utilities Software Licensing & Compliance
Industry · Energy & Utilities · Compliance

Energy & utilities — SAP IS-U, Oracle WAM, and the NERC CIP overlay.

Energy and utilities organisations run software estates anchored by SAP IS-U, Oracle WAM and Primavera, with a 15- to 25-year asset lifecycle pulling licensing into compatibility conversations no other industry faces. The audit appetite is high, the NERC CIP overlay is real, and the OEM-embedded licensing creates a parallel publisher relationship buyers rarely surface.

Updated: June 2026 Reading time: 12 min Audience: CIO, Head of OT, VP Asset Management, Procurement Director
Energy infrastructure
An industry-specific compliance pattern

Why energy & utilities face a long-cycle licensing problem.

Energy and utilities organisations — upstream and integrated oil & gas, midstream operators, regulated utilities, renewables developers and grid operators — carry a software compliance profile shaped by three forces: a deep SAP, Oracle and IBM estate behind the asset-management, plant-maintenance, work-management and customer-information systems that anchor operations; a 15- to 25-year asset lifecycle that pulls software into compatibility conversations no other industry faces; and a regulatory environment (FERC, NERC CIP, REMIT, Ofgem) that constrains licensing decisions in ways the major publisher account teams rarely understand. In our work with integrated majors, regulated utilities and renewables developers across 2024 and 2025, the recurring compliance patterns are predictable — provided the work happens before the next asset-management modernisation milestone.

The largest single recurring exposure is the SAP IS-U and SAP S/4HANA Utilities footprint. SAP's industry solution for utilities anchors customer information, billing, work management and asset management at most regulated utilities globally; underneath that suite sits an Oracle Database estate that frequently runs in dense Real Application Clusters with multiple options enabled. The audit posture is that the entitlement documentation rarely matches the operational reality at a utility — work-order volume scales with weather events, billing volume scales with customer expansion, and the licensing baseline assumed at the original deal no longer matches the consumption pattern five years in. A structured software license audit defense reconciles that drift on the buyer's terms, before the publisher's LMS team frames it as a shortfall.

The Oracle WAM / Primavera pattern

Oracle's utilities portfolio — Oracle Work and Asset Management (WAM), Oracle Utilities Customer Care & Billing, Primavera P6 for capital-projects scheduling, Hyperion / EPM for financial planning — sits at the second-largest Oracle relationship at most regulated utilities. The compliance pattern is that the named-user metrics drift upward as the operational footprint expands (more field crews, more contractors, more inspectors) and Primavera concurrent-user metrics drift as capital-projects programmes ramp. The defensive posture is to reconcile, annually, the named-user and concurrent-user position against the operational reality.

Utility renewal or audit coming up?

The SAP IS-U pattern, the Oracle WAM / Primavera footprint and the NERC CIP overlay shape the negotiation more than buyers usually credit.

Contact Us →

The NERC CIP / OT licensing overlay

NERC CIP for North American bulk-electric-system operators (and the comparable security overlays in other jurisdictions) constrains the operational-technology licensing decisions in two specific ways. First, the OT environment requires segmented network access and vendor-managed cloud connectivity that some major publishers either do not support or charge a premium for. Second, the OT-system retention and audit-evidence requirements pull licensing decisions toward higher-tier SKUs that include the required retention features. The defensive posture is to scope the OT-system population separately from the IT-system population and to benchmark the OT-tier premium against the commercial baseline.

The renewables / new-development pattern

Renewables developers and new-development teams carry a different licensing pattern from regulated utility incumbents. The estate is younger, the data footprint is cloud-native (AWS, Azure, GCP), the OT stack is supplied by the original-equipment manufacturer (GE, Siemens, Vestas, Nordex) with embedded software that the buyer is licensing through the OEM rather than direct from the publisher. The compliance exposure is that the OEM-embedded licensing creates a parallel publisher relationship that the buyer does not see until the OEM renegotiates with the publisher upstream. The defensive posture is to surface the OEM-embedded licensing into the buyer's entitlement register.

The annual energy & utilities review

The review that pays in energy.

The compliance review that consistently pays in energy & utilities is the annual asset-and-customer-system entitlement review. It reconciles, for each of the top eight publishers, the entitlement against the operational baseline, the IT / OT segmentation against the NERC CIP overlay, and the OEM-embedded licensing against the buyer's entitlement register. Energy & utilities organisations that run this review annually report a 50–75% reduction in renewal-cycle surprises versus those that respond to vendor audits ad hoc.

Download the Software Price Benchmarking Report.

Industry-specific benchmarks across the major publishers — with energy & utilities pricing patterns.

Get the playbook →
FAQ

Common questions.

Why is SAP IS-U the dominant utilities exposure?
SAP's industry solution anchors customer information, billing, work management and asset management at most regulated utilities. Underneath it sits an Oracle Database estate that drifts away from the licensing baseline as work-order and billing volume scales with operational reality.
What is the Oracle WAM / Primavera pattern?
Named-user metrics on Oracle WAM and Utilities Customer Care & Billing drift upward with the operational footprint (more field crews, more contractors). Primavera concurrent-user metrics drift as capital-projects programmes ramp. Annual reconciliation against operational reality recovers cost.
How does NERC CIP affect licensing?
NERC CIP requires segmented OT network access and pulls licensing toward higher-tier SKUs with required retention features. Scope OT separately from IT and benchmark the OT-tier premium against the commercial baseline.
What is the OEM-embedded licensing problem?
Renewables developers and OT-heavy operators license publisher software through OEMs (GE, Siemens, Vestas, Nordex) with embedded software inside the equipment. The buyer does not see the publisher relationship until the OEM renegotiates upstream. Surface OEM-embedded licensing into the entitlement register.
How does the 15–25 year asset lifecycle change licensing?
Long-lifecycle assets force the buyer into compatibility conversations the publisher uses as leverage. Older versions of the software stay licensed for decades; publishers price the support uplift accordingly. Multi-year fixed-escalator commitments break the dependency.
What is the annual energy & utilities review?
A reconciliation across the top eight publishers of entitlement against operational baseline, IT / OT segmentation against the NERC CIP overlay, and OEM-embedded licensing against the entitlement register. Operators running it annually report 50–75% fewer renewal surprises.

Energy & utilities renewal
coming up?

Our energy & utilities practice covers SAP IS-U, Oracle WAM and Primavera, IBM, and the OT-stack OEM-embedded licensing. Buyer-side only.

The Compliance Brief

Weekly compliance intelligence for IT leaders.