Basic Configuration

Configuration is required in the Lexicon and Tags modules of Engineering in order to set up the interface between AVEVA P&ID and AVEVA Engineering, refer to Compare and Update Drawing Data with Data from External Sources.

Note: This is in addition to the configuration required in the AVEVA P&ID Administration program, refer to Plant and Marine Integration Configuration Category, and the AVEVA Reports Service (see Set up AVEVA P&ID to Connect with AVEVA Engineering).

Lexicon Module Configuration

In order for the interface between Engineering and P&ID to function, the following element must be present in Lexicon, with attributes:

The selected Element types attribute must be set:

See also Points to Note.

Tags Module

1. In the Tags module, access the Compare/Update facility from the Data Management tab and select AVEVA P&ID from the upper list in the Source Selection group of the Actions tab that is then displayed:

   

2. Select Options from the Configuration group to display the following Options dialog:

   

3. Click Configure P&ID. In the dialog that is then displayed, enter the address of the appropriate AVEVA Reports Service:

   

   Click Test Connection to test that a valid address has been entered. Press OK to close the dialog.

4. Different configurations may be set up for the interface. For example, one for importing lines, one for importing instrument, and so on. Each configuration may include its own mapping between AVEVA P&ID and Engineering attributes, its own filters etc.

   To set up a configuration, click Manage Configuration. The Compare/Update Configuration wizard is then displayed:

   

5. To create a new configuration, select the Create new configuration option and click Next to continue.

   To view or edit and existing configuration, select the Edit existing configuration option, and select it from the list that is then displayed. Click Next to continue.

6. Enter the name of the configuration in the Display Name field and select the element type that the configuration is concerned with from the Element Type list.

   

   From the Name Attribute list, select the attribute of the selected element type which is to serve as the name attribute of imported items in Engineering.

   From the Unique Attribute list, select the attribute which is to serve as the unique key attribute of imported items.

   For lines, this must be Branch Id. For other types of element it must be handle.

   Click Next to continue.

7. In the next step, select the Engineering element type to which the AVEVA P&ID element type is to be mapped:

   

   Click Next to continue.

8. In the next step, set up any required filters for the export.

   

   Refer to Compare and Update for details of this procedure. Click Next to continue.

9. Finally, set up the mappings between AVEVA P&ID attributes and Engineering attributes.

   

   Refer to Compare and Update for details of this procedure.

   Click Finish to save the configuration and exit the wizard.

Points to Note

• The PMGEngiPID attribute is used to uniquely identify imported AVEVA P&ID elements during the import process. It must therefore be unique for each imported element, or else an error will occur.

  The attribute is formed from a concatenation of the Project Id, unique attribute (as set in the Configuration Wizard) and the drawing number + sheet number of each element.

  It must not be edited in Engineering.

• Name attributes in Engineering must be unique and must not contain spaces. Therefore the values of AVEVA P&ID attributes mapped to the Engineering Name attribute must also be unique and must not contain spaces.

• If branches are imported they are likely to be assigned the same Name attributes (derived from their line numbers) as their main pipes. Branches should therefore be excluded from imports by means of a filter set up in the Configuration Wizard, or using the Filters facility accessed from the Actions tab.

• If the AVEVA P&ID Line Size attribute is mapped to the Engineering UDA Line Size attribute, the UDA Type of the Engineering UDA Line Size attribute must be set to Text instead of Real.