An asset's Asset Key is the information required by V-Suite CORE Synchronization to find the asset in the asset database and synchronize that asset with updated information. The asset key should preferably be unique and non-volatile, meaning it is unlikely to change.

V-Suite CORE's ability to incrementally synchronize the asset database from a CAD Source depends on the ability of the CAD provider adapter to provide unique non-volatile asset keys. The following default synchronization behavior applies:

 

V-Suite CORE Synchronization Behavior

Asset Key

Example

Synchronization Behavior

No asset key:
Synchronization cannot assign an asset key to the asset it is provided with.

The asset does not have any attributes or geometry which uniquely identify the asset.

The asset will be added to the asset d Database. It will always be removed from the asset database during the next synchronization.

Non-unique asset key:
Synchronization can assign an asset key to the asset, but the asset key is not always unique.

The asset key is based on a tag attribute but the value might not always be unique.

The asset will be added to the asset d atabase. If the asset database contains other assets with the same asset key, it will be removed from the asset database during the next synchronization.

Volatile asset key:
Synchronization can assign a unique asset key to the asset, but the Asset Key is volatile (may change).

The asset key is based on the asset's geometry which uniquely identifies the asset but the a Asset can be moved, changed in size or re-oriented which would change the asset key.

The asset will be added to the asset database. If the asset key changes, it will be removed from the asset data during the next synchronization. If the asset key does not change, synchronization will update the asset's:


  • Attribute values (as long as these attributes are not part of the asset key)
  • Geometry - its dimensions, position and orientation (as long as geometry is not part of the asset key)
  • Appearance (color)
  • Hierarchy (as long as the asset's parent is not part of the asset key)

Non-volatile, unique asset key:
Synchronization can assign a unique, non-volatile asset key to the asset .

The asset key is based on the asset unique ID assigned by the CAD source, for example the system_occurence_number of a Valve provided from a PDS Intergraph source. 

The asset will be added to asset database. It will remain in the asset d atabase unless and until it is removed from the CAD source. If the asset changes in the CAD source, synchronization will update tje asset's:

  • Attribute values
  • Geometry (its dimensions, position and orientation)
  • Appearance (color)
  • Hierarchy