ISO 20815:2026 Expanded to Hydrogen, Wind, and CCS. Now Try Applying It to a Mixed-Asset Energy Portfolio.

When ISO 20815 was last revised in 2018, it governed reliability and production assurance for petroleum, petrochemical, and natural gas operations. The 2026 edition arrives with a new title — Oil and Gas Industries Including Lower Carbon Energy — Production Assurance and Reliability Management — and a substantially broader scope. It now explicitly covers carbon capture and storage, hydrogen and ammonia production, and wind energy.

That scope change is not administrative tidying. ISO's own summary notes it reflects "operators' growing need to manage mixed hydrocarbon and lower-carbon portfolios." Energy companies are no longer choosing between conventional and clean infrastructure — they are running both, often on the same balance sheet, serving the same grid. ISO 20815:2026 formalises what was already operationally true: the same reliability rigour that applied to gas platforms now applies to electrolysers and wind farms.

What the standard does not resolve is an architecture problem that has been building quietly in enterprise asset management for years.

Two Topologies, One Standard

Consider what ISO 20815:2026 now has to govern for a typical hydrogen-value-chain operator.

At the production end, electrolysers are discrete assets: modular equipment arranged in hierarchies, with pressure vessels, membrane stacks, rectifiers, and cooling systems each carrying their own failure modes, maintenance rhythms, and OEE-grade telemetry. Reliability analysis here follows ISO 14224 taxonomy — parent-child failure structures, equipment class hierarchies, planned shutdown intervals. These are the same data models used to manage a manufacturing plant or a gas processing facility.

At the distribution end, hydrogen pipelines and blending networks are linear assets: graph-topology infrastructure where a segment's condition is inseparable from its position in the network. Risk does not propagate through a hierarchy here — it propagates through upstream and downstream dependencies along the line. GIS-native inspection routing, segment-by-segment integrity scoring, and cascade consequence modelling are the tools that matter. These are the same data models used to manage water mains, power transmission lines, or natural gas distribution.

ISO 20815:2026 asks both sides for the same outputs: a Production Assurance Programme, a Reliability Management Programme, consistent failure categorisation, and auditable performance monitoring across the full scope of covered assets. The standard does not distinguish between the two topologies. But the underlying data structures are fundamentally different, and no amount of process alignment changes that.

The same structural split appears in offshore wind. Cable arrays and export infrastructure are linear assets — networks with topology and cascade interdependencies. Turbine assemblies are discrete assets — equipment hierarchies with component-level failure modes. Operators managing offshore wind have experienced this tension acutely: industry reporting points to significant O&M cost increases driven partly by the difficulty of applying consistent reliability frameworks across both asset classes within a single system.

The EAM Architecture Problem This Creates

Most enterprise asset management platforms were built to serve one industry model. Process and discrete manufacturing platforms reason about equipment in hierarchies. Utility and pipeline platforms reason about infrastructure as networks. Over the past decade, vendors have extended these platforms outward — adding integrations, modules, and connectors — but the underlying reasoning engine remains oriented toward one topology.

For ISO 20815:2026 compliance, that orientation creates a practical problem. You can have a Reliability Management Programme that works well for your electrolysers or one that works well for your pipelines. To have both, you are either running two separate EAM environments — which the standard does not contemplate — or you are forcing one topology's data model onto assets it was not designed to represent. Failure modes get shoehorned. Integrity assessments lose their physical meaning. The audit trail the standard requires becomes inconsistent at the seam between asset classes.

This is not a data integration challenge solvable by a better middleware layer. The core question — what is a failure, how does it propagate, and what is the correct maintenance response — has different answers depending on whether the asset is a network node or a hierarchy item. Connecting two systems does not give you a unified Production Assurance Programme. It gives you two programmes with a data pipe between them.

What the Standard Actually Requires of Your Platform

For operators who want genuine ISO 20815:2026 compliance across a mixed-energy portfolio, the requirement is a platform that natively understands both topologies and can apply a single reliability framework across them — without degrading either.

UniEAM's linear asset management capability is built on GIS-native infrastructure, with network graph models and cascade failure propagation embedded in its core data model. Pipeline segments, cable runs, and distribution networks are first-class objects with the topology attributes that integrity management requires.

UniEAM's discrete asset management capability applies OEE-grade telemetry and ISO 14224 failure taxonomy natively. Electrolyser stacks, turbine assemblies, and facility equipment are managed in the parent-child hierarchies that reliability-centred maintenance demands.

Both sit on the same agentic platform, which means every reliability prediction and maintenance recommendation carries a decision log — the audit-trail requirement that ISO 20815:2026 shares with a growing list of asset integrity standards. A recommendation about pipeline segment recoating and a recommendation about membrane stack replacement are both traceable to the data and reasoning that generated them, in the same environment.

For linear asset management specifics — inspection routing, network dependency modelling, and integrity scoring — the linear asset management knowledge base covers the operational detail.

Timing and Practical Priority

ISO 20815:2026 is in effect now. For operators who have already embedded it into their maintenance management frameworks, the compliance gap may be visible in the seams: reliability metrics that cannot aggregate cleanly across asset classes, audit findings that require manual reconciliation, or production assurance reports that treat pipeline and facility assets as separate documents. For operators still implementing the standard, the architecture decision made now will determine how much remediation is needed later.

The energy transition is producing more mixed-portfolio operators each year — utilities adding generation assets, midstream companies adding hydrogen production, industrials adding distributed energy. For all of them, ISO 20815:2026 is a prompt to ask whether their EAM architecture was built for the portfolio they manage today, or the one they managed a decade ago.

Curious how UniEAM handles both? Request a demo.