Equipment
Equipment : Model Equipment : Database Hierarchy
Database Hierarchy
All database elements are owned by other elements, therefore elements must be created in a strict order, see figure below.
The following database elements are common to multiple AVEVA E3D™ design disciplines:
•
World
•
Site
•
Zone
Equipment Specific Hierarchy
Below the zone level in the EQUIPMENT discipline, the specific elements are:
Equipment
•
The Equipment (EQUI) element(s) are administrative and can own a number of Sub-equipment elements or Primitive and Nozzle elements. Refer Equipment Element to for further information.
Sub-equipment
•
The Sub-equipment (SUBE) element(s) are owned by Equipment elements. Sub-equipment elements can own a number of Primitive and Nozzle elements. Refer to Sub-Equipment for further information.
Primitive
•
The Primitive (for example, BOX or CYLI) element(s) are owned by Equipment or Sub-equipment elements. These elements dictate the shape and geometry of the equipment item. Refer to Primitives for further information.
Nozzle
•
The Nozzle (NOZZ) element(s) are owned by Equipment or Sub-equipment elements. These elements are used to connect an equipment item to pipework. Refer to Nozzle for further information.
Electrical Component
•
The Electrical Component (ELCONN) element(s) are owned by Equipment or Sub-equipment elements. These elements are used to connect an equipment item to an electrical cable. Refer to Electrical Component for further information.
 
Depending on the selections made from the EQUIPMENT tab, further windows are presented prompting for input and options allowing for the workflow to continue.
Functionality from the EQUIPMENT tab will be unavailable if the correct database hierarchy has not been configured beforehand. For example certain equipment elements must reside below other elements in the database hierarchy.
If a particular equipment element cannot be created at the current position in the database hierarchy the user receives an error message summarising the problem.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo