Data migration

This section focuses on the Migration Strategy providing Best Practice advice to ensure a smooth transition of legacy data (for example, AVEVA Diagrams, AVEVA P&ID, AVEVA Electricall, AVEVA Instrumentation, 3rd party tools) to the AVEVA Unified Engineering solution.

It is important to keep in mind that AVEVA Unified Engineering alongside its Default Configuration is a multi-discipline environment, in which any object created within this environment will inherently include data from Process, Mechanical, Electrical, and Instrumentation disciplines. This is a concept that is crucial when focusing on the Data Migration aspect. Objects should be migrated only once and then Discipline data should follow accordingly. Furthermore, while the solution takes care of all the main Engineering Disciplines, interactions with other tools and services (for example, Process Simulation, ETAP Calculations, E3 Panel, 3D Models, ALM solution, Name Allocation Manager, AVEVA Asset Information Management) should be considered. A good representation of the AVEVA Unified Engineering ecosystem that might impact the Data Migration Strategy is shown in the following image.

Within the AVEVA Unified Engineering Data Migration scope, P&ID and E&I should be considered as two independent processes, each with its own methodology. Those will be treated separately in the following sections:

• Piping and Instrumentation Diagrams (P&ID) migration process.

  • Using DEXPI and Compare/Update function included in AVEVA's Default Configuration into both Legacy Products and AVEVA Unified Engineering.

• Electrical & Instrumentation (E&I) migration process.

  • Using AI/AE SQL Migration Tool, a custom solution developed specifically by AVEVA R&D for this purpose.

Migration workflow is dependent on content, and should be analyzed case by case based on customer requirements:

• Depending on customer request to migrate both data and graphics, or just data.

• Depending on customer current usage of AVEVA Engineering.

As a generic rule, AVEVA recommends to migrate first P&ID and then E&I data.