This scenario details an intelligent device network system sensing an asset removal/installation at a functional location and subsequent notification to a maintenance management system.

Actors

I&C Device Monitoring System Notify Maintenance Management System of changes in asset configuration
Maintenance Management System Receive notifications from I&C Device Monitoring System of changes in asset configuration
Associate asset removal/installation with work order

Data Content

The data sent from the I&C Device Monitoring System to the Maintenance Management System is, at a minimum, composed of:

  • The functional location
  • The serialized asset
  • The timestamp of when the installation or removal occurred

In addition, the following data can be sent for context:

  • The agent who performed the installation or removal
  • The calendared maintenance work order associated with the installation or removal

Data Formats

The data published by the I&C Device Monitoring System and received by the Maintenance Management System 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:

  • EventType
    • ecc99353-412b-4995-bd71-1cbc6fc16c7c: Installation of Asset on Segment
    • 3a45e126-b234-42a0-b3b1-07c29522d02d: Removal of Asset on Segment

MIMOSA CCOM Business Object Documents

The following MIMOSA CCOM BODs should be supported:

  • SyncAssetSegmentEvents

Infrastructural Components

ISBM

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

Implementation Requirements

The I&C Device Monitoring System must implement a client for the ISBM Provider Publication and Channel Management Services.

The Maintenance Management System must implement a client for the ISBM Consumer Publication and Channel Management Services. The Maintenance Management System may implement the ISBM Notify Listener Service for message notification.

Suggested Channel/Topic Configuration

A channel should be created for install requests and should conform to the following format:

/Enterprise/Enterprise Subdivision/.../ISO18435:D1.3

For example:

/Enterprise/Refinery A/Area A/Light Ends Area/ISO18435:D1.3

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

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

For example:

OIIE:S10:V1.0/CCOM:SyncAssetSegmentEvents:V1.0