An Operations and Maintenance Information Open System Alliance

OIIE Scenario 4 - Publish As-Built Engineering Asset data from ENG, CONSTRUCT to REG-ASSET

This scenario details the batch handover of asset and installation information at the Approved for Commissioning & Closeout gate. The information originates from the Construction Management System or Commissioning Management System depending on availability and ease of extraction of asset data and is sent to the O&M Asset Registry.

Actors

Construction or Commissioning Management System Send constructed asset and installation data
Asset Registry Receive and register O&M-related serialized equipment asset data

Triggers

The list of serialized assets and their corresponding installation information are typically exchanged at the Approved for Commissioning & Closeout gate, after the completion of the construction phase. In some instances, this information may be handed over incrementally throughout the construction phase.

Data Content

The physical, serialized assets that are installed in the plant are obtained from an engineering or construction system. The asset has identification properties (ID, tag, name), categorical properties, data sheet properties that describe the capabilities of the equipment, and associated metadata. A relationship between an asset and its product model can be established at this point in time, however the associated product model data (including data sheet and bill of material) is exchanged in Use Case 4. As-Built asset information also includes installation information, that is, an association between an asset and the segment that it is installed on. An asset can be installed and removed from various segments so that lifecycle asset information tracking is established for subsequent Use Cases.

Data Formats

The data published from and sent by the Construction or Commissioning Management System must comply with ISO 15926 standardized templates and reference data.

The data published to and received by the Structural Registry 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
  • DataSheetType
  • EventType
  • SegmentType
  • UnitType

MIMOSA CCOM Business Object Documents

The following MIMOSA CCOM BODs should be supported:

  • SyncAssets
  • SyncAssetSegmentEvents

Infrastructural Components

Transform Engine

Data transformation is required for this scenario and the OpenO&M-ISO 15926 Transform Engine converts the necessary data from an ISO 15926 format in the Reference Environment to the MIMOSA OSA-EAI CCOM in the Execution Environment. A one-way mapping from ISO 15926 to MIMOSA CCOM is required. Identifier transformation is only required for updates to data already sent from the Reference Environment to the Execution Environment.

ISBM

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 the Asset Register incrementally. The ISBM may also provide alternative transfer mechanisms for performance and scalability purposes.

Implementation Requirements

The Construction or Commissioning Management System must implement a client for the ISBM Provider Publication and Channel Management (only the GetChannel operation) Services.

The Asset Registry must implement a client for the ISBM Consumer Publication and Channel Management (only the GetChannel operation) Services. The Structural Registry may implement the ISBM Notify Listener Service for message notification.

The Transform Engine must implement a client for the ISBM Provider Publication, Consumer Publication and Channel Management (only the GetChannel operation) Services. The Transform Engine may implement the ISBM Notify Listener Services for message notification.

Suggested Channel/Topic Configuration

A channel should be created for the handover of asset definition and as-constructed asset 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:

OIIE:S4:V1.0/StandardXMLSchemaName{:Version}

For example:

OIIE:S4:V1.0/CCOM:SyncAssets:V1.0
OIIE:S4:V1.0/CCOM:SyncAssetSegmentEvents:V1.0