Introduction

The AVEVA Unified Engineering Default Configuration provides significant benefits over traditional approaches, which includes schedule, cost, safety, and sustainability, and it is a result of an extensive effort that AVEVA has invested in. Historically, companies have spent months or years attempting to optimally configure their data-centric engineering, design, and capital project execution systems with varying degrees of success.

We have gathered the lessons learned from hundreds of these implementations and identified the patterns that have informed a set of configurations for AVEVA Unified Engineering and Capital Project Execution solutions, which now ship as AVEVA’s Default Configuration. It includes the following:

• A rich data model that is capable of representing thousands of equipment types, components, and their relationships to each other.

• Discipline-specific views to the data model that allow engineers and designers to efficiently populate and manage technical data.

• Configurations that are optimally aligned across products.

• Templates for traditional engineering deliverables, such as lists and datasheet templates informed by industry standards.

• Symbol libraries and Catalogues that are mapped to the rich data model.

• Data Views that fulfil industry formats, such as the following:

  • International Organization for Standardization (ISO) 15926

  • Data Exchange in the Process Industry (DEXPI)

  • Capital Facilities Information Handover Specification (CFIHOS)

The AVEVA Unified Engineering Default Configuration is designed to support the implementation of Process, Mechanical, Electrical, and Instrumentation deliverables. The configuration provides examples of best practices in the implementation of the AVEVA Unified Engineering.

The AVEVA Unified Engineering Default Configuration should be used as a “Corporate Template Setup”. Once a customer has adopted it, this project becomes their own and AVEVA cannot be held liable for any errors that occur as part of this project’s ongoing configuration and modification. AVEVA supplies the “AVEVA Default Configuration Governance Content" as part of this collateral documentation, this contains a set of best practices and recommendations to consider and follow on how to modify the Default Configuration to ensure compliance with the practices and standards AVEVA uses to develop and expand its content.

Default Configurations Summary Table

Assumptions

This document has been written for users familiar with Engineering Administration, with prior knowledge of the AVEVA Unified Engineering application.

It is assumed that:

• Users have a valid license, and the software has been installed.

• Users know how to launch the application.