Pricing

Sign in
Request a Demo
ISO 15926

What Is ISO 15926? Data Model, RDL & Asset Data Integration

ISO 15926 is a standard for integrating lifecycle data across process plants. Learn how its data model, reference data and CFIHOS support interoperability.

ISO 15926 is an international standard for integrating, sharing, exchanging, and handing over lifecycle information about process plants and industrial assets. It provides a common semantic framework for representing technical information so that data created in different systems and by different organizations can retain the same meaning throughout the asset lifecycle.

The standard addresses a fundamental problem in asset-intensive industries: engineering and asset information created during design, procurement, construction, and commissioning often needs to move between different organizations and software systems before eventually being used in operations and maintenance. Without common definitions and structures, this information requires extensive mapping and interpretation every time it moves between systems.

ISO 15926 provides a common foundation for that exchange. Rather than requiring every application to use identical internal databases, the standard provides a shared way of representing assets, properties, classifications, relationships, and lifecycle information.

This makes ISO 15926 particularly relevant to data interoperability, Asset Information Management (AIM), engineering data exchange, project handover, and the development of reliable digital asset information.

What Is ISO 15926 and What Is It Used For?

ISO 15926 is formally titled Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities.

At its core, the standard is intended to make technical information understandable across systems and throughout the lifecycle of a facility.

Consider a centrifugal pump specified by an engineering contractor. Information about that pump may originate in an engineering application, pass through procurement and supplier systems, enter an asset information platform during project execution, and eventually be transferred into an ERP, CMMS, or other operations system.

Each system may structure and name the information differently.

ISO 15926 provides a semantic foundation that can help systems identify that they are describing the same type of asset, properties, and relationships even when their internal data structures differ.

This supports a central goal of asset data management: preserving the meaning, structure, and context of asset information as it moves between organizations, systems, and lifecycle phases.

ISO 15926 Data Model: How Does It Work?

The ISO 15926 data model is defined principally in ISO 15926-2. It provides a conceptual data model for the computer representation of technical information about process plants.

Rather than defining only a fixed database schema, the model provides a semantic structure for representing physical objects, activities, properties, classifications, relationships, and changes over time.

This is important because industrial asset information is not static.

An equipment item may be designed, specified, purchased, installed, commissioned, maintained, modified, and eventually replaced. Information about that asset can therefore originate from multiple organizations and systems over decades.

ISO 15926 provides a common conceptual model through which those systems can represent the meaning and relationships of that information.

In practical asset information management, this can help reduce dependency on bespoke point-to-point mappings between engineering, procurement, asset information, ERP, CMMS, and other enterprise systems.

What Is the ISO 15926 Reference Data Library (RDL)?

A data model defines how information can be represented. Reference data defines what the concepts used within that information mean.

The ISO 15926 approach therefore combines its data model with standardized reference data. ISO/TS 15926-4:2024 defines core reference data that can be used to record information about process plants, including core classes and information describing individual reference data items.

In practice, reference data provides common concepts that different organizations and systems can use when describing industrial information.

The distinction can be summarized as:

  • Data model — defines the conceptual structure used to represent information
  • Reference data — provides standardized concepts used within that structure
  • Templates — provide reusable patterns for representing information consistently
  • Implementation methods — provide methods for implementing these structures for information exchange

Together, these components allow information to be exchanged based on shared meaning rather than relying only on matching column names, database structures, or application-specific identifiers.

This is particularly relevant when information from multiple engineering contractors and suppliers must ultimately contribute to a consistent Master Tag Register (MTR) and operational asset information environment.

ISO 15926 Parts: Which Parts Matter for Asset Data?

ISO 15926 is a series rather than a single specification. Different parts address different elements of lifecycle information integration.

Some of the most relevant include:

  • ISO 15926-2 — Data model: defines the conceptual data model for representing technical information about process plants.
  • ISO/TS 15926-4 — Core reference data: defines core reference data items used to record information about process plants. The current published edition is ISO/TS 15926-4:2024.
  • ISO/TS 15926-7 — Template methodology: provides a methodology for lifecycle information integration using templates based on the Part 2 data model.
  • ISO/TS 15926-8 — OWL implementation: provides implementation methods using Resource Description Framework (RDF) and Web Ontology Language (OWL).
  • ISO 15926-100 — Vocabulary: defines terminology used across the ISO 15926 series. ISO 15926-100:2026 was published in June 2026.

The series continues to evolve as approaches to industrial information integration develop.

For most owner-operators, EPCs, and suppliers, understanding every technical component of ISO 15926 is less important than understanding the principle behind them: industrial information should be represented using shared structures and meanings so that it can move reliably between systems and lifecycle stages.

ISO 15926 vs CFIHOS: What Is the Difference?

ISO 15926 and CFIHOS address related information interoperability challenges, but they should not be treated as interchangeable standards.

ISO 15926 provides a semantic and data integration framework for process plant lifecycle information.

CFIHOS provides a practical specification for standardized information handover on capital facilities projects.

This difference matters in practice.

An owner-operator preparing a major capital project typically needs to define exactly which information contractors and suppliers must deliver, how that information should be structured, and how it will be validated before handover.

CFIHOS is designed around this practical handover problem.

ISO 15926 addresses the broader challenge of representing and exchanging lifecycle information consistently across systems and organizations.

For an EPC or supplier, CFIHOS requirements may therefore be more visible in project information requirements, while ISO 15926 forms part of the wider standards landscape supporting interoperable industrial information.

How Do ISO 15926, CFIHOS and DEXPI Work Together?

ISO 15926, CFIHOS, and DEXPI address related interoperability problems at different levels.

ISO 15926 provides a framework for representing and integrating lifecycle information about process plants.

CFIHOS focuses on standardizing information requirements and handover for capital facilities projects.

DEXPI focuses more specifically on standardized data exchange for process engineering information, particularly P&ID data.

They should therefore not simply be viewed as competing standards.

A digital project environment can involve multiple standards addressing different information domains and exchange requirements. Their common objective is to reduce ambiguity and manual mapping when engineering information moves between organizations and systems.

For owner-operators, the practical challenge is ensuring that information delivered using these standards ultimately becomes usable operational asset information rather than remaining isolated project data.

How Is ISO 15926 Used in Engineering and Asset Information Management?

The principles behind ISO 15926 become particularly valuable when information crosses organizational or system boundaries.

During a major capital project, information can move through a chain such as:

Engineering system → EPC → equipment supplier → asset information platform → owner-operator → ERP / CMMS

At every transition there is a risk that identifiers, classifications, properties, relationships, or context will be interpreted differently.

Semantic standards and controlled reference data reduce this ambiguity by giving systems and organizations a shared basis for understanding the information being exchanged.

In practice, this can support:

  • consistent asset and equipment classification
  • more reliable engineering data exchange
  • reduced manual mapping between systems
  • structured document handover
  • improved equipment-to-document relationships
  • more reliable asset data migration
  • integration between engineering, ERP, CMMS, and asset information systems
  • stronger information foundations for digital twin implementations

The value is therefore not the standard in isolation. The value comes from maintaining consistent meaning as information moves from engineering and project execution into operations.

How Does ISO 15926 Support Project Handover?

Project handover is one of the points where information interoperability becomes most visible.

Owner-operators may receive asset information from multiple EPCs, package vendors, and equipment suppliers. Each source may use different naming conventions, classifications, attribute structures, and document references.

Without consistent information requirements, significant effort can be required to map and validate this information before it can be loaded into operational systems.

Standards-based information management helps establish a common structure and meaning earlier in the lifecycle.

In practice, this means ensuring that equipment tags, technical attributes, classifications, relationships, documents, and other deliverables can be connected into a coherent document handover package rather than treated as disconnected files and spreadsheets.

This is also where ISO 15926 and CFIHOS become complementary concepts: ISO 15926 addresses semantic interoperability across lifecycle information, while CFIHOS provides practical requirements for structured project information handover.

How Does ISO 15926 Improve Data Interoperability?

The larger business problem addressed by ISO 15926 is interoperability.

Industrial organizations typically operate a heterogeneous application landscape. Engineering tools, procurement systems, supplier databases, document management platforms, ERP systems, CMMS applications, and digital twin platforms may all contain information about the same physical asset.

The challenge is not simply moving data between those systems. It is ensuring that the meaning of the data survives the transfer.

For example, transferring a value called “design pressure” is useful only when the receiving system understands which equipment item it belongs to, what property is being described, which unit is used, and how that information relates to the rest of the asset hierarchy.

Semantic models, reference data, controlled identifiers, and relationships help preserve this context.

That makes ISO 15926 relevant not only to data interoperability, but also to broader data quality management and information governance across the asset lifecycle.

How Sharecat Supports ISO 15926-Aligned Asset Information

Sharecat helps owner-operators establish structured, consistent asset information as engineering and supplier data moves from projects into operations.

Rather than requiring operations teams to reconcile fragmented spreadsheets, documents, and engineering datasets after handover, Sharecat provides a controlled environment for managing tagged equipment, technical attributes, documentation, and relationships throughout project execution.

This includes:

  • consolidating tagged equipment into a controlled Master Tag Register
  • structuring technical asset information against agreed data requirements
  • validating incoming EPC and supplier information
  • maintaining relationships between equipment, attributes, and engineering documentation
  • supporting structured information handover into operational systems
  • maintaining traceability from source information through validation and final delivery

The result is asset information structured for interoperability rather than simply collected for handover.

Where projects use standards such as ISO 15926 and CFIHOS, this provides a practical foundation for moving standardized information from engineering and suppliers into the systems owner-operators depend on during operations.

Frequently Asked Questions About ISO 15926

What is ISO 15926?

ISO 15926 is an international standard series for integrating lifecycle information about process plants, including oil and gas production facilities. It provides a data model, reference data, templates, and implementation approaches intended to support consistent information exchange between systems and organizations.

What is the ISO 15926 data model?

ISO 15926-2 defines the conceptual data model used for representing technical information about process plants. It provides a system-independent framework for representing assets, properties, activities, relationships, and other lifecycle information.

What is the ISO 15926 Reference Data Library?

Reference data within the ISO 15926 framework provides standardized concepts that can be used when representing process plant information. ISO/TS 15926-4:2024 specifies core reference data items for process plants, including oil and gas production facilities.

Is ISO 15926 the same as CFIHOS?

No. ISO 15926 addresses semantic representation and integration of process plant lifecycle information. CFIHOS focuses more specifically on standardized information requirements and deliverables for capital project handover.

What is ISO 15926 used for?

ISO 15926 supports interoperable lifecycle information exchange in process industries. Relevant applications include engineering data integration, reference data management, information exchange between systems, asset information management, and digital handover.

Does ISO 15926 only apply to oil and gas?

No. Although oil and gas production facilities are explicitly included in its scope and have played an important role in the development and adoption of the series, ISO 15926 addresses lifecycle information for process plants more broadly.

What is the difference between ISO 15926-2 and ISO 15926-4?

ISO 15926-2 defines the conceptual data model, while ISO/TS 15926-4 specifies core reference data used in representing process plant information. They therefore perform different but complementary functions.

How does ISO 15926 relate to digital twins?

Digital twins depend on information from multiple systems being connected to the same physical assets with consistent meaning and context. ISO 15926 provides semantic concepts that can support this interoperability, although implementing a digital twin involves additional technologies, information models, and governance processes.

Related concepts

ISO 15926 provides a semantic foundation for exchanging lifecycle information across systems, while specifications such as CFIHOS translate the wider interoperability challenge into practical information requirements for capital projects. Together with controlled tag registers, structured Bill of Materials data, and validated handover documentation, these concepts help owner-operators preserve usable asset information from engineering through operations.

Related Terms

Advanced Work Packaging (AWP)

What Is Advanced Work Packaging (AWP) and How Does It Work?

As-Built Documentation

What Is As-Built Documentation in Capital Projects?

Asset Administration Shell (AAS)

What is an Asset Administration Shell (AAS)??

Asset Data Migration

What Is Asset Data Migration? Process, Steps & Best Practices

Let's talk!

A member of our team will be in touch soon.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
By clicking “Submit” you agree to our TOS and Privacy Policy.
Looking for technical and product support? Click here.

Let's talk!

A member of our team will be in touch soon.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
By clicking “Submit” you agree to our TOS and Privacy Policy.
Looking for technical and product support? Click here.