Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
  • Welcome
  • Products
  • Support
  • About
  • More
  • Cancel
AssetWise Enterprise Interoperability
  • Product Communities
  • AssetWise
  • AssetWise Enterprise Interoperability
  • Cancel
AssetWise Enterprise Interoperability
AssetWise Enterprise Interoperability Wiki Sync - flow for publishing master data
    • Sign In
    • -Interop Overview (AssetWise Home)
      • -AssetWise and CMMS integrations - overview
        • +Interop terminology
        • Process-Acknowledge - requesting changes to master data
        • Sync - flow for publishing master data
      • +AssetWise Products and Adapters
      • +Service bus - enterprise message delivery
    • Asset Reliability features with Interop
    • +Troubleshooting Interop with AssetWise
    • +Release Documentation

     
     Questions about this article, topic, or product? Click here. 

    Sync - flow for publishing master data

    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.

    • sync
    • asset
    • BOD
    • work order
    • Segment
    • work request
    • interop
    • overview
    • Share
    • History
    • More
    • Cancel
    • Sandy Milne Created by Bentley Colleague Sandy Milne
    • When: Wed, Sep 4 2019 2:15 PM
    • Sandy Milne Last revision by Bentley Colleague Sandy Milne
    • When: Tue, Mar 17 2020 3:03 PM
    • Revisions: 7
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies