This scenario is similar to the previous, but details the exchange of asset and installation information. This information originates from the Asset Registry and is sent to all applicable O&M systems.
Actors
| Asset Registry | Send O&M-related serialized equipment asset data including asset installation |
|---|---|
| O&M Systems | Receive and register O&M-related serialized equipment asset data |
Triggers
The information flows can occur after the following events have occurred:
- Use Case 1 or Use Case 2 have resulted in the Asset 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 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 by the Asset 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
- DataSheetType
- EventType
ecc99353-412b-4995-bd71-1cbc6fc16c7c: Installation of Asset on Segment
- SegmentType
- UnitType
MIMOSA CCOM Business Object Documents
The following MIMOSA CCOM BODs should be supported:
- SyncAssets
- SyncAssetSegmentEvents
Infrastructural Components
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 O&M Systems incrementally. The ISBM may also provide alternative transfer mechanisms for performance and scalability purposes.
Implementation Requirements
The Asset 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:
OIIE:SC5:V1.0/StandardXMLSchemaName{:Version}
For example:
OIIE:S5:V1.0/CCOM:SyncAssets:V1.0 OIIE:S5:V1.0/CCOM:SyncAssetSegmentEvents:V1.0
