Data Integration - How is it done in ISO 15926?

latest update: 2018-12-10


The title of ISO 15926 is:

Industrial automation systems and integration Integration of life-cycle data for process plants including oil and gas production facilities

This topic explains a way to achieve that integration.


When looking at the Plant Life-cycle Model we can see three domains: Class (blue), Design World (green) and Real World (yellow). Please make sure you read Possible Worlds.

Of course this is not the entire model of a plant, it is a skeleton for one plant item (not really, see later) during its entire cradle-to-grave existence.

Process Design

So  let's begin at the begin: Process Design at the far left of the above diagram.

It is an Activity model at Class level. In this example around a specialization of an instance of ClassOfActivity, called PUMPING WASTE WATER TO V-101 or the like.

Two things are participating to that ClassOfActivity:

  • an instance of ClassOfFunctionalObject with a Process tag P14 that participates in the Role of PERFORMER and is represented on a Process Flow Diagram;
  • an instance of ClassOfStream with a Process tag S12 that participates in the Role of SUBJECT and is represented on a Block Flow Diagram and the Heat & Material Balance

The Stream data in the Heat & Material Balance are used by the Process Engineer for his Process Data Sheet for P-101 (see Plant Design below).

For the declaration use TIP_EC001 "Declaration of a Class", for the participation the TIP_C0011 "Class Of Participation in a ClassOfActivity".

Plant Design

The design world, so the green part, is shown in the diagram below 

A PhysicalObject, like PUMP SYSTEM P-101 is represented on a P&ID, which means that the pumping service at the topological location defined by that P&ID shall be fulfilled by a to-be-designed PhysicalObject that we call P-101.

P-101 has two aspects:

  1. Functional aspects, attributed to a temporal part of P-101 called P-101-FPO, where FPO stands for FunctionalPhysicalObject;
  2. Physical aspects, attributed to a temporal part of P-101 called P-101-MPO, where MPO stands for MaterializedPhysicalObject.

P-101-FPO is typed with an instance of ClassOfFunctionalObject called CO-P-101-FRC (ClassOf P-101 FunctionalRequirementsClass) and P-101-MPO is typed with an instance of MaterializedPhysicalObject called CO-P-101-RC (ClassOf P-101 RequirementsClass).  Here, by exception, a Classification template is not used, because this link shall be immutable and changing rdf:type is more difficult that deprecating a template. It would be better to do the same with TemporalWholePart but RDF nor any of the known ontologies has a standard property for that.

These five objects (17, 15, 14, 22, and 21 in above diagram) shall be declared simultaneously with TIP_EP002 "Declaration of an instance of dm:PhysicalObject". And whenever terminated they shall get the same valDeprecationDate as well.

P-101-FPO is represented on a particular version of the applicable P&ID, whereas P-101-MPO is represented in a particular version of the 3D Plant Model.

Resuming: These five objects shall be declared for each plant item, stream, spatial location, and for any parts thereof in case there is information to be attributed to those parts. This can, and will in most cases, be done at a later date. This cluster is the immutable core of the design, all information shall be attributed to temporal parts of -FPO or -MPO, or to class-of-temporal-parts of CO- xxx-FRC or CO-xxx-RC. For this attribution some 170 standard templates are available (for free, like everything else on this website).


All FPOs shown in a P&ID are to be declared as discussed above and subsequently interconnected following the topology of that P&ID, using TIP_P0011 "Interconnecting two instances of PhysicalObject", where MPOs shown in a 3D Plant Model are to be declared and interconnected following the topology of that 3D Model.

Other than this topological information and some composition and containment (of Streams) information (P-101 is a part of Plant 12345, Stream P-101-S is contained in P-101) no other information shall be attributed to the FPO or MPO, but rather to the classes CO- xxx-FRC or CO-xxx-RC . This is discussed below.

Process Engineering & Detailed Engineering (at Class level)

Based on the Heat & Material Balance data the Process Engineer provides the information about the process conditions that must be handled by P-101 (or other equipment, piping, instrumentation). The related document or data set represents (and defines) a version of the FunctionalRequirementsClass CO-P-101-FRC. Any revision of that document/data set must result in a new class-of-temporal-part of CO-P-202-FRC.

The RequirementsClass CO-P-101-RC is made a subclass of the FunctionalRequirementsClass,  thus adding the Process Conditions section to the Technical Specification, that represents/defines a version of the RequirementsClass CO-P-101-RC . Any revision of that document must result in a new class-of-temporal-part of CO-P-202-RC.


There are three steps to be taken:

  1. Determine the objects, Classes or Individuals, that are shown or implied on functional diagrams, such as a PFD, P&ID, Control Diagram, One-line Diagram, etc. and declare those objects;
  2. Determine the interrelationships between these objects and represent those with templates;
  3. Attribute information, that is exclusively about an such object, to that object using the applicable templates; this is preferrably based on an agreed-upon Product Model.

(soon to be continued for the Actual World)