Overview of Transfer Process_ABoM

This transfer of data is based on a diagram in AVEVA Diagrams, and exports all data for a particular diagram.

The data is published either using the ABOM_Published DB view or the ABOM PML function, which is made available through Integration Service. AVEVA ERM connects to AVEVA Integration Service and transfers the available data into screen s21002.

Data is available to AVEVA ERM only when Abom_publishingstatus of the diagram elements in AVEVA Diagrams reaches the status Published. When an ABOM is in status ‘Retired’, no updates are allowed.

After the data is consumed in AVEVA ERM, the publishing status in AVEVA Diagrams is changed to “Consumed”. This ensures that the data is not imported again into AVEVA ERM until it is changed and published again.

On the ABOM transfer from AVEVA Diagrams, an appropriate configuration is created so that the information needed to create/update both items and header records are available. The following changes take place in AVEVA ERM after the ABOM data is transferred:

• ABOM header records corresponding to the information sent are also created.

• Design Ref – Dabacon ID information is mapped to External Reference (on ABoM Item).

• Diagram Id is mapped to External Group Reference (on ABoM Item).

• TAG Id is mapped to External TAG Id (on ABoM Item).