ISO 15926, process-plant lifecycle data.
ISO 15926 is the international standard for representing and integrating process-plant lifecycle information. It provides a common data model and a library of reference data so that engineering, procurement, construction, and operations systems can exchange asset data without losing meaning.
What ISO 15926, process-plant lifecycle data means.
A process facility is described by dozens of systems over its life, from the FEED tools through the EPC design and procurement systems to the operations and maintenance databases, and each handoff between them risks dropping or distorting the meaning of the data. ISO 15926 exists to carry that meaning across the whole lifecycle. It defines a common data model for plant information together with a library of standard reference classes, so a pump, a transmitter, or a line means the same thing to the receiving system as it did to the sending one, regardless of the application. It is published as a multi-part standard covering the core model, the reference-data library, and methods for implementing the model in practice. In a handover it works alongside CFIHOS. CFIHOS sets out, in practical terms, what information has to be handed over and in what form, while ISO 15926 provides the underlying data structure those requirements align to. For an instrumentation team the consequence is concrete. The instrument index, equipment list, and line list are the asset data that has to map cleanly onto the handover schema.
What ISO 15926 standardizes
It defines a common data model for process-plant information and a library of standard reference classes, so asset data keeps its meaning as it moves between systems. The goal is integration across the facility lifecycle rather than a single file format.
ISO 15926 and CFIHOS
The two are complementary. CFIHOS is a practical specification for what information must be handed over and how it is structured for a project. ISO 15926 is the underlying data-integration standard those requirements align to. A handover often references both.
Why lifecycle data integration matters
A plant's information passes through many tools from design to operations, and meaning is easily lost at each handoff. A shared data model lets the receiving system interpret an instrument, a line, or a piece of equipment the same way the sending system meant it, which is the difference between a usable handover and a pile of mismatched files.
From P&ID to a conformant register
The instrument index, equipment list, and line list taken from the P&IDs are the asset data that has to map onto the handover schema. Getting those registers complete and consistent first is what makes alignment to an ISO 15926 or CFIHOS structure achievable rather than aspirational.
Common questions
What is ISO 15926 used for.
What is the difference between ISO 15926 and CFIHOS.
Is ISO 15926 a file format.
How does ISO 15926 relate to data handover.
Run it on your drawings.
Upload a drawing set, get every document populated and classified, export to the format your team uses.