Piping and Instrumentation Diagrams (P&ID)

Since the AVEVA Unified Engineering and Next Generation P&ID journey started, migration has been a very important topic on the strategy table of discussion. The goal is to facilitate rapid adoption, and to achieve this, the use of existing proven technologies has been identified as the safest and the most appropriate approach. Therefore, we have combined the use of international standard DEXPI to migrate graphics and connectivity information plus Compare & Update for the data. The intention is to have only one gateway to migrate AVEVA legacy customers and data from 3rd party tools, including scanned drawings. This will reduce development effort, and more importantly, minimize the need for extra configurations.

In summary:

Standardization is key for success

Legacy migration strategy based on proven technologies:

• AVEVA Compare / Update - 100% data migration.

• DEXPI standard schema. - 100% connectivity migration.

Using standards technologies also:

• Reduces development and support effort.

• Reduces customer configuration

• Simplifies customer process and the user interface.

• Allows migration from various sources.

The migration from AVEVA legacy tools to the new AVEVA Unified Engineering environment from a P&ID standpoint is shown in the following image.

The overall migration process can be summarized as following:

• Export from AVEVA legacy or 3rd party tools

• Configuration

• Import

• Consolidation

• Additional possibility– AI/ML Legacy P&ID Recognition

Export from AVEVA Legacy or 3rd Party Tools

• AVEVA P&ID and AVEVA Diagrams have Symbols and Instance Export facilities supporting multiple DEXPI schema (3.3.3 & 4.0.1).

• AI/ML P&ID recognition and 3rd party tools may support different DEXPI versions, please refer to their product documentation.

AVEVA legacy products have been enhanced to support multiple schema versions and more comprehensive mapping (such as pseudo attributes and line styles) within AVEVA’s Default Configuration. The application will vectorize objects and connectivity into a standard schema. This is used to recreate intelligent P&ID in the new environment.

An example of an XML mapping file is shown in the following image.

Configuration

Some setup is required to ensure a smooth import into AVEVA Unified Engineering.

• Tag Format and attributes used on the tag need to be defined and mapped into Name Allocation Manager (NAM) Service and into the Project to allow the dedicated element type (ENGI ITEM) creation during the P&ID Instance import step. See Create Naming rules and Scope in Name allocation manager for more information.

  

• Configuration functionalities

  • AVEVA Unified Engineering has been enhanced to allow Class and Attribute mapping within the configuration module, aimed to facilitate data migration.

  • Symbols are assigned to classes within the AVEVA Unified Engineering Conceptual model. This means that mapping a DEXPI class with the Conceptual Model Class will result in a mapped symbol.

Import

New importing features have been implemented into AVEVA Unified Engineering to facilitate the import process.

• Symbol Import Facility: The AVEVA Unified Engineering P&ID Discipline includes a Default Configuration import facility for symbol import into the AVEVA Unified Engineering Configuration module. This is optional for the migration process. It is designed to help when only symbols are required for migration, not instances.

  

• P&ID Instance Import Facilities have been improved:

  • A P&ID instance can be imported into an AVEVA Unified Engineering module.

  • DEXPI Schema 3.3.3, 4.0.1 and 4.1.1 are supported.

  • Single or bulk import, and import for creation and/or upgrade (import to replace existing drawing), can be managed.

    

Consolidation

Due to DEXPI schema limitations and technology changes (legacy vs next generation), some graphical alignment and consolidation may be required.

AI/ML Legacy P&ID Recognition

The P&ID migration strategy is to be as open as possible, we have enabled migration for 3rd party tools and adopted new technologies such as Artificial Intelligence (AI) and Machine Learning (ML). The decision has been to leverage strategic partnership instead of developing something from scratch. The default approach would be to have partners producing DEXPI file as output from their AI/ML tools.