AVEVA AIM Configuration Category

The AVEVA AIM Configuration Category is divided into four sub-categories:

Configurations Sub-Category

The Settings sub-category is used to specify general settings for the AVEVA Asset Information Management (AVEVA AIM) interface, relating to the format of the files generated by the export from AVEVA P&ID.

For detailed information, refer to the AVEVA AIM Schematic Gateway Configuration Guide.

Mappings Sub-Category

The mappings between AVEVA P&ID format data and AVEVA AIM Portal format data are stored in sets of three XML files, one for each of the following types of mapping:

• Presentation Mapping

• Attribute Mapping

• Class Mapping

• Pattern Mapping

This sub-category is used to select the mapping files to be used.

To select a mapping file, select the appropriate button and browse for the required file using the Open dialog.

To open a mapping file for editing, select the appropriate button. The file is then opened in a text editor.

Interfaces used to "manually" set up attribute and class mappings are accessed from the appropriate button.

Attribute Mappings Interface

An interface to "manually" set up attribute mappings is accessed from the appropriate button.

The Attribute Mapping dialog is then displayed:

Click to populate the dialog with all the mappings already set up in the attribute mapping XML file:

To add a mapping, click: . A new row is then added to the grid. Enter the details of the mapping as required.

To delete mappings, check their Select checkboxes and then click . Check the Select All checkbox to check all the Select checkboxes.

Click Save to save changes made to the mappings and Close the exit the dialog.

Class Mappings Interface

Note: To set all P&ID component classes to ‘UNKNOWN’ set the class mappings as follows:

An interface to "manually" set up class mappings is accessed from the appropriate button. The Class Mapping dialog is then displayed:

To populate the dialog with all the mappings already set up in the class mapping XML file, click .

The Configure Integration Service Location dialog is then displayed:

Enter the details of the integration service set up for the interface between AVEVA P&ID and AVEVA AIM and click Test Service. The Class Mapping dialog is then populated with the content of the XML mapping file:

Note: For information on setting up integration services in general and the AVEVA AIM source type in particular, refer to the Middle Tier Settings Appendix in the AVEVA P&ID Reports User Guide.

To add a mapping, click . A new row is then added to the grid. Select the details of the mapping as required. The lists of classes available for selection is derived from the selected integration service.

To delete mappings, check their Select checkboxes and then click . Check the Select All checkbox to check all the Select checkboxes.

Click Save to save changes made to the mappings and Close the exit the dialog.

Settings Sub-Category

The Settings sub-category is used to specify general settings for the AVEVA AIM interface, relating to the format of the files generated by the export from AVEVA P&ID.

Background Settings

To select the background colour of the SVG files generated by the project, either select the required colour from the Colour field list, or enter the RGB values of the colour in the fields provided, or click Pick Colour and select the required colour from the standard colour selection dialog.

Line Thickness Setting

In the Scale Factor field, enter a value to scale the stroke-width of lines in output drawings. The value is valid only in a range of > '0.0' to <= '100.0'.

If the value set to '1', this means that lines are not scaled, and are exported at their original thickness. An entered stroke width value of less than 1 will reduce the original stroke width, e.g. with an original stroke width value of 4 entering a stroke width value of '0.1' will reduce the stroke width to 0.4. An entered value of greater than '1' will increase the original stroke width, e.g. with an original stroke width value of '4' entering a line thickness scale value of '5' will increase the stroke width to '20'. The default value is '1'.

Delimiters Setting

In the SVG and EIWM XML output files, nozzles which are the "children" of parent equipment are identified with a tag which is the concatenation of the equipment tag and the nozzle tag. In the Equipment / Nozzle Delimiter field, enter the delimiter that is to be used to separate the equipment component of such tags from the tag component.

For example, if the parent equipment tag is "E101", the nozzle tag is "N1", and the delimiter is "/", then the resultant tag assigned to the nozzle in the SVG and EIWM output files will be "E101/N1".

Other Settings

• Fast Graphics Model: If the Fast Graphics Model checkbox is checked drawing entities such as meshes that are not required for the output are not exported, speeding up the process. The checkbox is unchecked by default.

• Create CSV Tag File: If during output procedures, a CSV file containing a list of all the tagged objects and classifications is to be written to the output folder then check the Create CSV Tag File checkbox. In the Columns field, add the additional comma separated columns to export the objects attributes in the CSV export.

• Use Pipeline Annotation: If the pipe annotation placed on the drawing is to be hot-spotted and exported to EIWM XML file then check the Use Pipeline Annotation checkbox. By default the checkbox will be checked.

  If the checkbox is checked then Pipe (start node type PSN) labels placed on drawings will be hot-spotted/exported in AVEVA AIM with the following priorities:

  • First Priority: Reporting Label.

  • Second Priority: Main Segment Annotation (If there is no reporting label).

  • Third Priority: First Annotation with the maximum pipe properties (If there is no reporting label or Main segment annotation).

  If there is no annotation on the pipe then:

  • Main Segment properties with 'Default' tag format.

  • Start node properties with 'Default' Tag format.

  If the checkbox is unchecked then Pipes (Start node type PSN) label placed on drawings will be hot-spotted/exported in AVEVA AIM with the following priorities:

  • Reporting Label (first priority).

  • Main Segment properties with Default tag format (if there is no reporting label).

  • Start node properties with Default Tag format (if there is no reporting label and main segment in pipe).

  Note: Branch pipes with start node type BSN are not hot-spotted in SVG file or exported to the EIWM XML file.

• Use Equipment Tag Display: If the equipment annotation placed on the drawing is to be hot-spotted then check the Use Equipment Tag Display checkbox. By default the check box will be unchecked.

  If the checkbox is checked then the equipment tag will be hot-spotted with the following priorities:

  • First priority: Equipment label with XEQ type

  Note: If there are multiple equipment labels (XEQ) then the label with the maximum equipment properties will be hot-spotted.

  • Second priority: Equipment header label with XEH type (if XEQ is not present)

  Note: If there are multiple equipment header labels (XEH) then the header label with the maximum equipment properties will be hot-spotted.

• Create Pipeline Model: If all piping segments which are part of common pipelines are to be combined and tagged as single pipelines in the SVG and EIWM XML output files, check the Create Pipeline Model checkbox. The checkbox is unchecked by default.

• Export Instrument Alarms: If instrument alarms are to be included in the output, check the Export Instrument Alarms checkbox. The checkbox is unchecked by default.

• Add Pipe Connector As Part Of: If "As Part Of" associations are to be included in EIWM XML output files for pipe connectors, check the Add Pipe Connector As Part Of checkbox. The checkbox is unchecked by default.

Advanced Options Sub-Category

The Advanced sub-category is used is to export data to a remote location, and to export data from multiple project drawings.

AVEVA AIM Service Section

Drawing data already generated by an AVEVA AIM export may be transferred to a remote location, for example, a shared network folder, using an AVEVA AIM server service.

If this facility is to be used, check the Transfer files to Remote AVEVA AIM Server checkbox.

In the AVEVA AIM Service Path field, enter the location of the AVEVA AIM server service. Click Test to test that the location of a functional service has been entered. If so, message is displayed to confirm this:

In the Remote Server Publishing Location field, enter the remote folder into which output files are to be copied.

Click Transfer to copy all the files currently in the local staging area (as specified in the Configurations sub-category) to the remote location. A message is displayed once the transfer is complete.

Batch Publish option to AVEVA AIM Section

The Project drawings available list displays all those project drawings from which data can exported.

To select a drawing to export data from, select it and select >.

To select multiple drawings to export data from, select them and select >>.

To select all available drawings to export data from, select the button with the green arrow on it.

Selected drawings are moved from the Project drawings available list to the Drawings selected for publish list.

Use < and << to de-select single or multiple drawings and move them back to the Project drawings available list.

Select the button with the red cross button on it to de-select all selected drawings.

When all required drawings have been selected, click Apply.

Carry out the export using facilities available in the Log Options section.

Log Options Section

To generate export files from the drawings selected in the Batch publish options to AVEVA AIM section, click Start.

The export then takes place. The progress of the export is indicated by a progress bar.

Details of the export or displayed in the log window below it.

To stop the export, click Stop.

To clear the log window, click Clear.

To view the log in the log file generated as part of the export,click View Log. For the log to be available, the Log Enabled checkbox in the Configurations sub-category must be checked, and the file name and location of the log file entered in the Log File field.