AVEVA Unified Engineering Vocabularies
- Last UpdatedJun 27, 2025
- 3 minute read
AVEVA Unified Engineering contains seven Vocabularies (as part of the standard release). As the product evolves, enhancements or new features may lead to updates in existing vocabularies or the introduction of entirely new ones.
Each vocabulary is named and versioned in the following way:
-
Base vocabulary – Version 2.0
-
Engineering vocabulary – Version 2.1
-
E&I vocabulary – Version 4.3
-
ETAP vocabulary – Version 1.6
-
Simulation vocabulary – Version 1.4
-
PID vocabulary – Version 7.0
-
SEE vocabulary – Version 1.0
Vocabularies are not entirely independent; they follow a form of hierarchical inheritance known as dependencies. For example, the Engineering vocabulary is dependent on the Base vocabulary. In this structure, a parent vocabulary must be successfully validated before any of its dependent (child) vocabularies can be considered valid. This layered validation process ensures consistency and maintains the integrity of related vocabularies across the system.
All vocabulary items are defined by URIs and can be accessed via the Data Model API, along with their corresponding database definitions (if applicable).
Base Vocabulary
The Base Vocabulary is a foundational vocabulary that contains some basic modelling terms common across all Engineering vocabularies and functionalities. It is an integral part of the product, any Conceptual Model that contains Base Definitions also has these items included.
The Base Vocabulary (V2.0) consists of three Base Association types and their inverse Association types. The system behavior defined for handling the deletion of an Association and its resulting impact on the associated Part is shown in the table below.
|
Direct Association Type |
Inverse Association Type |
Part Creation/Deletion |
|---|---|---|
|
Has Part |
Is Part Of |
Part is created and deleted. |
|
Can Have Part |
Can Be Part Of |
Part is not created but deleted. |
|
References |
Has References |
Part is neither created or deleted. |
|
Realized By |
Specified By |
Part is neither created or deleted. |
For example, if a Class Association between a Pump and a Motor has an Association Type of HasPart, when a Pump is created, the system automatically generates and associates a Motor using the class association. Through this association, the motor can inherit the name of the Pump in accordance with the project naming conventions.
Additionally, both components, the Pump and the Motor, may be expected to appear together in compound symbols within engineering drawings or be included in a shared datasheet, reflecting their functional relationship. This type of automated behavior is enabled by the Vocabulary-driven configuration applied during the build process.
Engineering Vocabulary
The Engineering vocabulary serves as another foundational vocabulary, containing items that AVEVA identifies as common across all engineering disciplines, for example, Instrument. It enables the definition of a shared set of core items, which can then be extended and specialized within more specific domain vocabularies.
This vocabulary is dependent on the Base Vocabulary, which must be enabled in the Configuration module.
E&I Vocabulary
The E&I Vocabulary is designed to support electrical and instrumentation business workflows for basic and detailed engineering design. It is dependent on the Engineering Vocabulary, and by extension, the Base Vocabulary.
ETAP Vocabulary
The ETAP Vocabulary is developed to support integration with the ETAP application, allowing validation of electrical design. The main power distribution system can be modelled in ETAP and imported into AVEVA Unified Engineering. This vocabulary requires the E&I Vocabulary, and by extension, the Engineering and Base Vocabularies to be enabled within the Configuration module.
Simulation Vocabulary
The Simulation Vocabulary supports integration with simulation applications, allowing validation of process design. It requires both the Base and Engineering vocabularies to be enabled within the Configuration module.
P&ID Vocabulary
The P&ID Vocabulary is designed to support process and piping workflows for both basic and detailed engineering design. It requires both the Base and Engineering vocabularies to be enabled within the Configuration module.
SEE Vocabulary
The SEE Vocabulary enables seamless integration with etap/SEE Electrical applications for detailed electrical engineering design. Currently, SEE Electrical 3D Panel+ is the only product integrated with AVEVA Unified Engineering. This vocabulary requires the E&I Vocabulary, and by extension, Engineering and Base Vocabularies to be enabled within the Configuration module.
Note:
Further detailed Vocabulary information can be requested and will be provided by AVEVA,
subject to dedicated approvals. The AVEVA Unified Engineering online help contains
guidance for specific workflows. See Welcome to AVEVA Engineering for more information.