Synchronisation

The purpose of synchronisation is to inherit confirmed changes for an item in the asset tree from the corresponding item in the asset type tree and to decide whether to accept or reject the changes for the selected item, its child items and asset model items in each instance of the asset type.

Synchronisation is the act of pulling through the configuration and structure from the asset type tree to the asset tree.

Synchronisation is initiated from:

  • the asset type tree for a changed item, or
  • from the asset tree for an unsynchronised item.

Synchronisation only affects items in the asset tree. The effect in the asset tree depends on which tree synchronisation was initiated from, the selected item and the results of the rules evaluation for the item.

Asset tree entities can be unsubscribed from synchronisation to enable asset modifications without an asset type change overwriting asset changes during synchronisation. This enhances user control over data synchronisation and provides flexibility in managing asset-related information. Refer to Unsubscribe from and Resubscribe to Synchronisation.

In the asset tree

Confirmed changes in the asset type tree can be retrieved or "pulled down" for the following inherited items in the asset tree:

  • in-place assets, placeholder assets, placeholder assets - linked and their linked detail records
  • regular asset components, placeholder asset components, placeholder asset components - linked and their linked detail records
  • tasks and their linked detail records.

Synchronising from the asset tree allows for more control, as one-to-one syncing occurs. So, the configuration on the corresponding asset type is only rolled out to the asset that is being synchronised.

Synchronisation process

  1. Select the relevant item and click Synchronise.
  2. Set the required synchronise options and click Accept.
  3. Accept or reject development changes for the synchronised items in the asset tree.

Best practice

  • Synchronise an item in an asset model to get all the confirmed changes from the asset type model on which it is based and then accept or reject the changed items with development status NAC, MAC or DAC.
  • Compare changes before accepting development of each inherited change.