External Reference Id

ExternalReferenceId information represents the dabaconid value as known in AVEVA Marine for an element. This information is transferred and stored in AVEVA ERM and is used for identification of the element.

The following concepts support this feature: Standard material, project component, raw plate, raw profile, drawing, design specification, fabricate and hull unit.

Example 1: Standard Material created and published from AVEVA ERM and imported in AVEVA Marine

1. Create and publish a new standard material in AVEVA ERM. An ‘Update’ notification is generated from AVEVA ERM to AVEVA Marine with the number of components available.

   

2. AVEVA Marine processes the ‘Update’ notification, queries the data from AVEVA ERM and imports data into AVEVA Marine.

3. AVEVA Marine generates an ‘Acknowledgement’ or ‘Error’ notification. Both types of notifications include a value in ExternalReferenceId corresponding to the dabaconid of the components.

   

4. AVEVA ERM automatically processes the ‘Acknowledgement’ or ‘Error’ notification and updates the value of External Reference for the element.

For all the concepts supporting this feature, the External Reference information can be verified in AVEVA ERM in the Integration tab in the External Reference field.

Example 2: Standard material created and published from AVEVA Marine

When standard materials are published from AVEVA Marine, External Reference is part of the information exported, and mapped into the import run in AVEVA ERM and this way, the elements are created with External Reference information.

External Reference feature is applicable to AVEVA ERM 13.0 and later and AVEVA Marine SP5 Fix1 and later. If you are using a version prior to these, you need to synchronize the data manually.

For this purpose, a manual import needs to be run in AVEVA ERM. For more information on how to run a manual import, see Manually.

After running this synchronization, AVEVA ERM will be updated with all the missing External References for the concepts that were already transferred. This will allow a proper identification of data already transferred when present in any further updates.

This synchronization should be run only once, and no notification was implemented for the transfer. Details about the updates applied can be seen in the s22050 Data Import screen in the Audit Summary and Audit Detail sections.