P&ID Reports Configuration Category

The P&ID Reports Configuration Category is configured using the main P&ID Reports Configuration Category pane and the Settings sub-category:

P&ID Reports Configuration Category Pane

A P&ID Reports database is supplied with the product (PidReports). By default, AVEVA P&ID will be set to export data to this database. To create a new, blank P&ID Reports database, press Create. A new database will then be created.

The filename of the new database will be "PidReports_<project name>_<incremented number>".

The P&ID Reports Server Name field displays the name of the SQL server, as specified in the Project Database Configuration Category.

The P&ID Reports Database field displays the name of the current P&ID Reports database. Select a different database from the list available from this field if required. The list consists of all P&ID Reports databases created for the project.

Settings Sub-Category

The application pane is divided into the following sections:

P&ID Reports Settings Section

These settings are applicable to both the current and legacy versions of the utility used to export data to a P&ID Reports databases:

• If the Consolidate Reference Object with Parent Object checkbox controls the default setting of the Consolidate checkbox on the Synchronizing dialog. This setting is applicable to both the current and legacy versions of the export utility.

• Check the ISO Export on Synchronization checkbox if the ISO Export checkbox on the Synchronizing dialog is to be checked by default.

• Check the Synchronise Drawing Changes Automatically checkbox to automatically save drawing changes to the PIDREPORTS database. If the checkbox is not checked, drawing changes are saved to the PIDREPORTS database after synchronise and consolidation.

• Check the ISO Export on Silent Synchronization checkbox if exports to ISO 15936 format XML files are to take place during the "silent" (background) synchronization processes.

These settings are only applicable to the "legacy" version of the export utility. In the current version, these settings are hard coded (or are not relevant):

• UDA values are displayed in AVEVA P&ID Reports on the UDA tab. If UDA values are also to be displayed on the same tabs as the items they are associated with (assuming there are fields available for them to be displayed in), check the Merge UDA Values checkbox.

• The Update P&ID Reports after Synchronize checkbox controls the default setting of the Export to P&ID Reports checkbox on the Synchronise dialog. If the Update P&ID Reports after Synchronize checkbox is checked, then the default setting of the Export to P&ID Reports checkbox is checked, and vice versa.

• Check the Update and Consolidate P&ID Reports Database after Synchronize checkbox if this is required.

• If the Add P&ID Drawing Details to Database checkbox is checked:

  • drawing records may be added to the AVEVA P&ID Document Manager, depending on the settings of the Document Manager Configuration Category.

  • the comments regarding an export that may be entered in the Description dialog during the export process are added to the P&ID Reports database.

Line Consolidation Section

Note: These settings are applicable to both the current and the "legacy" versions of the utility used to export data to a P&ID Reports databases.

This section is used to select which line properties are to be compared when attempting to consolidate lines which are present on multiple P&IDs when they are transferred into P&ID Reports.

As required, check the checkboxes in the First / Last Component List and/or Line Fields sections.

Note: The unique pipe validation fields specified in the P&ID project settings are compared regardless of these settings.

When the fields of two lines with unique pipe validation tag do not match, the lines are not consolidated and warning message is displayed in log tab of P&ID Reports.

Unlock the Consolidation Process

The consolidation process updates the entire project data when it is executed, resulting in a a large number of concurrent database transactions. Occasionally, if the process is executed by multiple customers at once, or in other unspecified circumstances, the database could be locked down by unfinished transactions, leaving it in a state in which it cannot be updated until the situation is resolved.

To resolve this situation, select Unlock Consolidation Process. This will force the completion of unfinished database transactions, returning the database to an operational state once again.