Sync - flow for publishing master data

Sandy Milne — Tue, 17 Mar 2020 19:03:35 GMT

Current Revision posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 3/17/2020 7:03:35 PM

In the standardized integration between a CMMS product and an AssetWise product, the CMMS is the system of record. Therefore the CMMS publishes several types of information using the Sync pattern.

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

When any of these objects are created or modified, a message called a BOD describing the new values should be published by the CMMS adapter to the service bus.

There are also supplemental BODs defined for the supporting objects of a system, such as Value Lists, Employees, etc. Please refer to the AWEIS Setup Guide 1.2 for further details regarding these BODs.

SyncAgents
SyncTypes
SyncLogisticResources

Synchronization Pattern

(The following content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

In a typical integration between systems, the best practice is to define a single master - the system of record - for any given piece of data. The system retains ownership of the data and is the “single source of truth”. Changes are only allowed in the master, and the object synchronization pattern replicates the changes to other systems that require that data.

MIMOSA/OAGIS uses the “Sync” verb on these types of documents. The master system publishes a Sync BOD to the topic on the service bus whenever an object is created, modified or deleted, and each system receives a copy of the message to replicate the change in their databases.

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

Tags: sync, asset, BOD, work order, Segment, work request, interop, overview

Sync - flow for publishing master data

Sandy Milne — Thu, 31 Oct 2019 14:08:02 GMT

Revision 6 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 10/31/2019 2:08:02 PM

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

When any of these objects are created or modified, a message called a BOD describing the new values should be published by the CMMS adapter to the service bus.

Synchronization Pattern

(The following content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

Tags: sync, asset, BOD, work order, Segment, work request, interop, AssetWise Interoperability, overview

Sync - flow for publishing master data

Sandy Milne — Wed, 02 Oct 2019 17:41:51 GMT

Revision 5 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 10/2/2019 5:41:51 PM

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

When any of these objects are created or modified, a message describing the new values should be published by the CMMS adapter to the service bus.

Synchronization Pattern

(The following content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

Tags: sync, asset, work order, Segment, work request, interop, AssetWise Interoperability, overview

Sync - flow for publishing master data

Sandy Milne — Fri, 06 Sep 2019 18:57:56 GMT

Revision 4 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 9/6/2019 6:57:56 PM

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

When any of these objects are created or modified, a message describing the new values should be published by the CMMS adapter to the service bus.

Synchronization Pattern

(The following content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

Tags: sync, interop, AssetWise Interoperability, overview

Sync - flow for publishing master data

Sandy Milne — Wed, 04 Sep 2019 18:44:33 GMT

Revision 3 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 9/4/2019 6:44:33 PM

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

The CMMS acknowledges these requests with either an acceptance and a Work order or Work request; or a rejection with reason code.

Synchronization Pattern

(The following content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

Tags: sync, interop, AssetWise Interoperability, overview

Sync - flow for publishing master data

Sandy Milne — Wed, 04 Sep 2019 18:43:38 GMT

Revision 2 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 9/4/2019 6:43:38 PM

In the standard integration, the CMMS is the source of:

Asset
Segment
Work order
Work request
Solution package

The CMMS acknowledges these requests with either an acceptance and a Work order or Work request; or a rejection with reason code.

Synchronization Pattern

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

(This content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

Tags: sync, interop, AssetWise Interoperability, overview

Sync - flow for publishing master data

Sandy Milne — Wed, 04 Sep 2019 18:15:48 GMT

Revision 1 posted to AssetWise Enterprise Interoperability Wiki by Sandy Milne on 9/4/2019 6:15:48 PM

Synchronization Pattern

In this pattern, there is generally only one publisher (master system) with one or more subscribers.

(This content has been repurposed from the AssetWise Interoperability Overview document. The full document is available in per-release folders here)

Tags: sync, interop, AssetWise Interoperability, overview