Theory
Forty years of plant data, one shared model
ISO 15926 tackles a brutal problem: a process plant (refinery, chemical works, platform) is designed by one set of companies, built by others, and operated by yet another for decades — and every handover loses engineering data. ISO 15926 is a standard for data integration across the whole asset lifecycle. The ISO documents are paywalled.
- A generic 4D model — Part 2 defines a foundational, 4-dimensional data model: things are modelled with their temporal parts, so you can represent how a pump, its specification and its state change over time. It's an upper-ontology-like core, famous for being powerful but hard (the perdurantist, 4D style is a steep mental shift).
- Reference Data Library (RDL) — Part 4 is a huge library of standard classes (pump, valve, flange, fluid…) so two companies use the same term for the same equipment type.
- Semantic-web alignment — later parts express ISO 15926 in RDF/OWL, and Part 14 gives it a modern OWL formulation; the related Industrial Data Ontology (IDO) anchors this work to BFO, bringing it into the mainstream ontology world.
- The job it does — a clean data handover from the engineering/procurement/construction (EPC) contractor to the owner-operator, who then runs and maintains the asset on shared semantics.
Use Case Example: An EPC contractor finishes a plant and hands over a 15926-based data set. Twenty years later the operator plans a revamp; because every valve and line was described with shared RDL classes and 4D history, engineers can query what was installed, when it changed, and to what spec — instead of excavating PDFs.