An Operations and Maintenance Information Open System Alliance

OIIE Scenario 2 - Publish As-Designed / As-Built Engineering Network / Segment / Tag data from REG-LOCATION to O&M

This scenario details the batch exchange of structural design information that forms part of the registry master data required by most O&M systems. This information originates from the Structural Registry (which stores Plant Breakdown Structures, Logical P&IDs and PFDs) and is sent to all applicable O&M systems.


Structural Registry Send O&M-related engineering network, segment and tag data
O&M Systems Receive and Register O&M-related engineering network, segment and tag data


The information flows can occur after the following events have occurred:

  • Use Case 1 or Use Case 2 have resulted in the Structural Registry being populated with new data to publish to O&M systems
  • Data enrichment has occurred within the Register
  • A data quality analysis has taken place and has been signed-off
  • The publication of data has been signed-off

Data Content

The information exchanged are those necessary to properly bootstrap O&M systems. Master data includes several functional sub-categories. The logical structural arrangement of the plant (hereafter referred to as a topology) is derived from P&ID and PFD information and forms the basis for the asset registry of many O&M. For the components in the structure, it should contain the identification properties (ID, tag, name), categorical properties (in relation to the reference data described above), interconnections, flow and intended physical sequence of equipment, data sheet properties that represent the requirements of installed equipment, controls and instrumentation, and associated metadata. Where topologies show interconnections between functional segments, breakdown structures show decomposition of segments. Breakdown structures are a hierarchical view of a system to show the composition of the functional segment.

To provide a level of traceability and diagrammatic arrangement for systems that require it (typically HMI applications), the relationship between the logical structural elements and their originating diagram as well as associated data (e.g. positioning and scale) are also exchanged. Document data is also included, such as the information in the title block, canvas size and origin position, to provide context.

Data Formats

The data published by the Structural Registry and received by O&M Systems must conform to MIMOSA CCOM BODs.

MIMOSA CCOM Reference Types

For the purposes of reference data management, the following MIMOSA CCOM types may be referenced:

  • AssetType
  • AttributeType
  • BreakdownStructureType
  • DataSheetType
  • MeasurementLocationType
  • MeshType
  • NetworkConnectionType
  • SegmentType
  • UnitType

MIMOSA CCOM Business Object Documents

The following MIMOSA CCOM BODs should be supported:

  • SyncEngineeringDiagram
  • SyncSegments
  • SyncBreakdownStructures

Infrastructural Components


The communication between all systems occurs via the ISBM using publish-subscribe services.

Due to the large volume of data output from these source systems, data may be sent to O&M Systems incrementally. The ISBM may also provide alternative transfer mechanisms for performance and scalability purposes.

Implementation Requirements

The Structural Registry must implement a client for the ISBM Provider Publication and Channel Management (only the GetChannel operation) Services.

O&M Systems must implement a client for the ISBM Consumer Publication and Channel Management (only the GetChannel operation) Services. O&M Systems may implement the ISBM Notify Listener Service for message notification.

Suggested Channel/Topic Configuration

A channel should be created for the provisioning of engineering data and should conform to the following format:

/Enterprise/Enterprise Subdivision/.../ISO18435:D0.2

For example:

/Enterprise/Refinery A/Area A/Light Ends Area/ISO18435:D0.2

As outlined in the document ISBM Guidelines, topics should match the message content. Correspondingly, the following topic format should be used:


For example: