Pathnovo Logo
Standards/ISO 15926

ISO 15926 Process Plant Lifecycle Semantic Model

ISO 15926 is the international standard for process plant lifecycle data integration. Semantic data model + Reference Data Library (RDL) + integration patterns. The semantic foundation that CFIHOS 2.0, DEXPI, AVEVA AIM, Cognite Data Fusion, Bentley iTwin, Hexagon HxGN SDx2 build on. Pathnovo's extraction output is ISO 15926-native.

ISO 15926 is structured into multiple parts, each handling a specific aspect of process plant data integration. Most relevant parts for engineering AI implementation:

Part 1

Overview and fundamental principles

Introduces the ISO 15926 standard's purpose: process plant lifecycle data integration across phases (FEED → detailed engineering → procurement → construction → commissioning → operations → decommissioning) and across systems (EDMS, AIM, CMMS, ERP, digital twin). Establishes terminology + scope.

Part 2

Data model

The semantic data model: classes, relations, and instances. Foundation of every later part. Defined as an OWL (Web Ontology Language) ontology so machines can reason over relationships, not just store flat records.

Part 3

Reference data for geometry and topology

Geometric and topological reference classes: how to represent pipe routing, equipment placement, instrument loop topology, and connection relationships in machine-readable form.

Part 4

Initial Reference Data Library (RDL)

The actual vocabulary: thousands of pre-defined object classes (PUMP, VESSEL, INSTRUMENT, FLANGE, VALVE, etc.) with standard attributes and units. CFIHOS 2.0 extends Part 4 RDL for capital facilities handover scope.

Part 6

Methodology for the development and validation of reference data

How new RDL classes are proposed, reviewed, and added. Governance for vocabulary evolution. Critical for buyers needing extensions for industry-specific scope (e.g. LNG-specific equipment classes, hydrogen-specific safety devices).

Part 7

Implementation methods for the integration of distributed systems

How systems on different platforms (AVEVA + Hexagon + Bentley + SAP + Maximo + Cognite) exchange ISO 15926-aligned data. Defines integration patterns and conformance levels.

Part 8

Implementation methods using OWL

Specifically how ISO 15926 maps to OWL and RDF triple stores. Foundation for graph-database-backed asset registers (e.g. Cognite Data Fusion, PNID.IO, AVEVA AIM ontology layers).

Part 9

Implementation methods for facade

How a system that does not natively understand ISO 15926 can present a 'facade' interface that responds in ISO 15926 form. Useful for legacy system integration without forklift replacement.

Part 11-13

Methodology and reference data for templates and adapters

Industry-specific template extensions (oil & gas, chemicals, pharmaceutical, power) and adapter patterns for connecting non-native systems. Ongoing development through ISO TC 184/SC 4 WG 3.

ISO 15926 is the underlying semantic foundation; other engineering standards build on or coexist with it:

ISO 15926 → CFIHOS 2.0

CFIHOS 2.0 sits on top of ISO 15926 Part 4 RDL. CFIHOS extends the RDL with capital-facilities-specific classes and tightens conformance for EPC-to-operations handover. CFIHOS-compliant data is automatically ISO 15926-compliant; the reverse is not true.

ISO 15926 → DEXPI

DEXPI's RDL references ISO 15926 reference classes. DEXPI's XML schema implements a subset of ISO 15926's semantic model specifically for P&ID data exchange. DEXPI is more practical for P&ID exchange because it has a defined XML schema; ISO 15926 alone is a semantic model that requires further specification.

ISO 15926 → ISA 5.1

Different scopes. ISA 5.1 is instrumentation tagging and symbology (e.g. PT-101 means pressure transmitter, loop 101). ISO 15926 is the broader plant lifecycle data semantic model that includes instrumentation as one class category among many. ISO 15926 references ISA 5.1 conventions for instrument-specific data; ISA 5.1 alone does not provide the broader plant model.

ISO 15926 → IEC 61346 / ISO 14224 / ISA 88

ISO 15926 coexists with other engineering data standards: IEC 61346 (industrial systems reference designation), ISO 14224 (equipment reliability data), ISA 88 (batch process control). Each handles a different scope; ISO 15926 provides the cross-disciplinary semantic foundation that lets these specialised standards interoperate.

Pathnovo's extraction output is mapped to ISO 15926 Part 4 RDL classes natively. Tag references resolve to RDL class instances; attributes carry RDL property names; units are RDL-standardised.

RDF / OWL output supported alongside CFIHOS 2.0 native and DEXPI XML. Same underlying extraction; different serialisation formats per downstream platform.

Cross-platform handover: ISO 15926 output ingests cleanly into AVEVA AIM, Hexagon HxGN SDx2, Bentley iTwin, Cognite Data Fusion, SAP PM (via SAP Asset Intelligence Network adapter), IBM Maximo (via ISO 15926 connector).

ISO 15926 facade pattern (Part 9) supported for legacy-system integration: Pathnovo wraps non-ISO-aware systems with ISO 15926-compliant API responses.

RDL extensions: for industry-specific scope (LNG-specific equipment, hydrogen-specific safety devices, pharmaceutical-specific GMP equipment), Pathnovo proposes extensions via the ISO 15926 working-group methodology (Part 6).

Validation: ISO 15926 output validated automatically against published RDL before delivery; conformance report provided per delivery.

What is ISO 15926?

ISO 15926 is the international standard for process plant lifecycle data integration. It defines a semantic data model (Part 2), a reference data library / RDL (Part 4), and integration patterns (Parts 7-9) that let process plant engineering, procurement, construction, and operations systems exchange data over the full lifecycle. Defined as an OWL (Web Ontology Language) ontology so machines can reason over relationships. Maintained by ISO Technical Committee 184, Subcommittee 4, Working Group 3.

What is the difference between ISO 15926 and CFIHOS?

ISO 15926 is the broad semantic data model for the full process plant lifecycle. CFIHOS 2.0 sits on top of ISO 15926 and tightens the specification for the specific use case of EPC-to-operations handover. CFIHOS extends the ISO 15926 Part 4 RDL with capital-facilities-specific classes (asset handover register schema, equipment lifecycle attributes, operations-readiness fields) and prescribes which classes / attributes are mandatory at handover. CFIHOS-compliant data is automatically ISO 15926-compliant. ISO 15926 covers the broader scope; CFIHOS handles the handover-specific subset. Most asset owners use both: ISO 15926 as the underlying semantic foundation, CFIHOS for the handover-specific deliverable specification.

Is ISO 15926 mandatory?

Not directly. ISO 15926 is voluntary; adoption depends on owner-operator and EPC contractor specification. However, increasingly major owner-operators (Aramco, ADNOC, BP, Shell, Equinor, Petrobras) specify ISO 15926-compliant handover as a project requirement. Indian PSU operators (IOCL, BPCL, HPCL, ONGC, GAIL) increasingly reference ISO 15926 in their asset information management standards. EPC contractors that cannot deliver ISO 15926-aligned data progressively lose competitive position on tier-1 owner-operator projects.

How do you use ISO 15926?

Three layers of adoption. (1) Reference: cite ISO 15926 Part 4 RDL class names in your asset register so different systems use the same vocabulary. (2) Conformance: emit asset register data as ISO 15926-compliant RDF / OWL serialisation that ISO 15926-aware platforms (AVEVA AIM, Cognite Data Fusion, Bentley iTwin) ingest natively. (3) Integration: use ISO 15926 Part 7 / 9 integration patterns to connect distributed systems via ISO 15926 facade APIs. Pathnovo supports all three layers: extraction output is RDL-mapped (layer 1), serialisable as RDF / OWL (layer 2), and accessible via ISO 15926 facade API (layer 3).

What is the ISO 15926 RDL?

RDL = Reference Data Library. Defined in ISO 15926 Part 4. Contains thousands of pre-defined object classes (PUMP, VESSEL, INSTRUMENT, FLANGE, VALVE, COMPRESSOR, COLUMN, EXCHANGER, etc.) with standard attributes (e.g. PUMP has design_pressure, design_temperature, materials, capacity, head, NPSH) and units (e.g. design_pressure is in barg or psig per RDL convention). Cross-vendor consistency: when AVEVA emits 'pump' and Hexagon emits 'pump', both reference the same RDL class so downstream systems treat them identically. RDL is publicly available and updated through the ISO 15926 working group methodology.

How does Pathnovo use ISO 15926?

Pathnovo's extraction output is mapped to ISO 15926 Part 4 RDL classes natively. Each extracted tag, equipment, line, instrument, valve, weld joint, mill cert heat number, HAZOP node resolves to an RDL class instance with RDL-standardised property names and units. Output serialised as RDF / OWL (ISO 15926 native), CFIHOS 2.0 XML (CFIHOS native, also ISO 15926-compliant by extension), or DEXPI XML (P&ID exchange specifically). Same underlying extraction; different serialisation formats per downstream platform requirements.

Which platforms support ISO 15926?

Strong support: AVEVA AIM (native ISO 15926 ingestion), Cognite Data Fusion (RDF graph backend natively ISO 15926-aligned), Bentley iTwin (ISO 15926 + CFIHOS 2.0 native), Hexagon HxGN SDx2 (ISO 15926 + DEXPI ingestion), Siemens COMOS (ISO 15926 export). Partial support: SAP Asset Intelligence Network (ISO 15926 connector available), IBM Maximo (ISO 15926 adapter via partner ecosystem). For platforms with only partial support, Pathnovo's ISO 15926 facade (Part 9 pattern) can wrap them with ISO 15926-compliant API responses.

Can I extend ISO 15926 RDL for my industry?

Yes, via the ISO 15926 working group methodology defined in Part 6. New classes (e.g. for LNG-specific equipment, hydrogen-specific safety devices, pharmaceutical GMP-specific equipment) are proposed to ISO TC 184/SC 4 WG 3 with technical justification, reviewed, and added to subsequent RDL releases. Pathnovo participates in industry-specific extension proposals when client engagements require RDL classes not yet in the published library.

See what your documents actually contain.

Send us 10 documents from your current project. We extract, reconcile, and show you exactly what we find in 48 hours, before any contract.

If the accuracy isn't what we promised, you owe us nothing.