Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Revision Log
Updates
Change highlighting will be employed for all revisions. Where new or changed information is presented
section headings will be highlighted in Yellow.
Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers please report it to AVEVA
Training & Product Support at tps@aveva.com
This manual provides documentation relating to products to which you may not have access or which may
not be licensed to you. For further information on which products are licensed to you please refer to your
licence conditions.
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free
from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar
losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of
data or information; any special, indirect, consequential or pure economic loss, costs, damages,
charges or expenses which may be suffered by the user, including any loss suffered by the user
resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of
whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence)
or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with
the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year
in which the user's claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software
licence under which the AVEVA software was purchased, the clauses in the software licence shall
take precedence.
Copyright Notice
All intellectual property rights, including but not limited to, copyright in this Training Guide and the associated
documentation belongs to or is licensed to AVEVA Solutions Limited or its affiliates.
All rights are reserved to AVEVA Solutions Limited and its affiliates companies. The information contained in
this Training Guide and associated documentation is commercially sensitive, and shall not be adapted,
copied, reproduced, stored in a retrieval system, or transmitted in any form or medium by any means
(including photocopying or electronic means) without the prior written permission of AVEVA Solutions
Limited. Where such permission is granted, AVEVA Solutions Limited expressly requires that the Disclaimer
included in this Training Guide and this Copyright notice is prominently displayed at the beginning of every
copy that is made.
Licenses issued by the Copyright Licensing Agency or any other reproduction rights organisation do not
apply. If any unauthorised acts are carried out in relation to this copyright work, a civil claim for damages
may be made and or criminal prosecution may result.
AVEVA Solutions Limited and its affiliate companies shall not be liable for any breach or infringement of a
third party's intellectual property rights arising from the use of this Training Guide and associated
documentation.
Trademark Notice
AVEVA™, AVEVA Everything3D™, AVEVA E3D™, [AVEVA Tags], Tribon and all AVEVA product and
service names are trademarks of AVEVA Group plc or its subsidiaries
Use of these trademarks, product and service names belonging to AVEVA Group plc or its subsidiaries is
strictly forbidden, without the prior written permission of AVEVA Group plc or AVEVA Solutions Limited. Any
unauthorised use may result in a legal claim being made against you.
Fluent is a trade mark of Microsoft Corporation. The Fluent user interface is licensed from Microsoft
Corporation by AVEVA and use of the Fluent trademark is strictly forbidden.
All other trademarks belong to their respective owners and cannot be used without the permission of the
owner.
AVEVA Everything3D™ (AVEVA E3D™) enables designers to create a 3D model of a Plant design in a
multi-discipline environment. One of these disciplines is Equipment modelling and AVEVA E3D enables
designers to create 3D representations of plant equipment of all types for use within the wider context of the
model.
1.1 Aim
The aim of this training module is to provide basic knowledge of Equipment Modelling within AVEVA E3D.
1.2 Objectives
1.3 Prerequisites
It is expected that trainees will have completed the TM–1801 AVEVA Everything3D™ Foundations training
course.
Training will consist of oral and visual presentations, demonstrations and set exercises. Each workstation
will have a training project, populated with model objects. This will be used by the trainees to practice their
methods, and complete the set exercises.
Certain text styles are used to indicate special situations throughout this document.
Menu pull downs and button press actions are indicated by bold dark turquoise text.
Additional information notes and references to other documentation will be indicated in the styles below.
Additional information
System prompts will be bold and italic in inverted commas i.e. 'Choose function'.
Example files or inputs will be in the courier new font. If users are required to enter information as part of
an example, appropriate fonts and styles previously outlined will be used.
Login to AVEVA E3D using the details provided by the Trainer. They will typically be as shown below:
Username: A.EQUIPMAN
Password: A
MDB: A-EQUIPMENT
Module: Model
On the TOOLS tab, in the Training group, click the Setup button to display the Training Setup form.
Navigate to the Equipment tab.
Select the Equipment radio button, if not already selected, check the Setup Training Course checkbox,
click the Apply button and close the form.
This chapter provides an overview of general features for Equipment Modelling in AVEVA E3D.
Equipment (EQUI) elements may represent any type of equipment in a Plant. It is important is that the
modelled equipment is a reasonable representation of the actual equipment. Specifically, that it is
volumetrically and spatially correct and that any nozzles, are correctly positioned, orientated and
specified.
The level of detail of the equipment model depends on the project requirements. While adding greater
detail provides a more realistic representation, it also takes more time and as such will cost more.
Different modelling methods are available to designers. Which method is appropriate often relates to the
degree of information available, the significance of the modelled item, and the frequency with which the
item will be created in the model.
EQUI elements may own one or more optional Sub-equipment (SUBE) elements. The
SUBE elements are used to break down equipment into sub-parts, e.g. main equipment
and supports.
Both the EQUI and the SUBE elements can own Primitives.
Primitives are the elements that are displayed in the 3D View to represent the
equipment and act as the building blocks for equipment modelling within AVEVA E3D.
Basic principles using primitives – this method is generally used for one-off equipment items or
where the size of the equipment doesn’t change. Repeat copies of equipment can be used in the
model by using the Standard Model Library.
Refer to TM-1802 AVEVA Everything3D™ (2.1) Model Utilities for information on Standard Model
Library.
Design templates – this method uses primitives and other elements in a design template. The
templates are generally parametrised such that the equipment may be re-sized for each instance of
the template in the design.
Creating Equipment Design Templates is outside the scope of this training guide. Refer to TM-1852
AVEVA Everything3D™ Equipment Design Templates (2.1), however, creating equipment elements
using design templates is described.
Importing models – equipment models may be imported using the Mechanical Equipment Interface
or from different file formats.
Using each of these methods is described fully later in the training guide.
Editor mode can be used to modify equipment primitives, however, it should not be used on equipment
elements modelled from design templates.
To enter Editor Mode, select the Editor button located in the Modify section of the HOME tab.
AVEVA E3D provides a utility to import equipment data from an Excel (.xls) or Comma Separated
Variable (.csv) file to create the top level EQUI element.
The import data may set any of the standard attributes or UDAs of an EQUI element but will not create
any primitives.
AVEVA E3D also provides a utility to produce equipment reports, which is separate to other reporting
methods.
Equipment elements may be ‘associated’ with each other or any other element in the model via
predefined constraints or restrictions. The restrictions provide logic that can be evaluated to describe how
the objects relate to each other.
Geometric restrictions, e.g. the origin points of two elements must be co-incident.
Checking the existence of elements, e.g. a hole exists for access to a piece of equipment.
Attribute comparison, e.g. the material of the associated elements are the same.
Associations are ‘passive’, i.e. they must be queried to see if the constraints are complied with.
It may be necessary on a project for designers to create holes in panel elements, i.e. deck plates,
grating, walls, floors, etc., for access to equipment.
AVEVA E3D provides functionality to control and manage hole creation to ensure design integrity.
Volume Models are similar to equipment elements. They may be used for modelling any item in AVEVA
E3D that is constructed from primitives but is not required to be displayed in Model Explorer as an EQUI
element.
A typical use of volume models may include plant Civils items (e.g. concrete slabs, concrete plinths, site
roads) or the modelling of escape routes/access obstruction volumes. Volume models can also be used
as a method of reserving space within the plant layout for equipment items not yet ready for modelling.
This chapter explores a number of issues that designers should consider prior to commencing any
equipment modelling and describes how equipment elements can be created with basic modelling
methods using primitives.
Conventionally, equipment items are named using the tag number, e.g. /E1101, /P1001-A, /D2016, etc.
However, any name or naming convention may be used. It is not usual to name primitives, except
nozzles, unless they need to be identified for some purpose.
Nozzles are named and generally prefixed by the equipment name to make them unique, e.g. /E1101-
N1, /P1001-A/N1, /D2016/1. Naming the nozzles also helps in identification when connecting pipework to
them. Nozzle names will also be referenced on Piping Isometrics.
Whatever names are given, the naming convention is usually defined by the project specification. It is
possible that the project may have Autonaming rules set up for items such as nozzles so that the project
conventions are followed in every detail.
The position of the equipment origin is a key consideration prior to commencing modelling. The point
selected for an equipment origin is often dictated by other project information, such as known co-
ordinates or adjoining structures and pipe elements. Understanding the position of the origin of
equipment, sub-equipment and primitive elements will help designers model more effectively.
Equipment elements, Sub-equipment elements and Primitive elements each have an origin. The origin
position is held within each elements Position attribute.
The EQUI element’s Position attribute holds the equipment origin position. By default, the position is
expressed in world co-ordinates, however the user can change this to other design elements if required.
If SUBE elements are used, the Position attribute defines the SUBE origin position with respect to the
equipment origin (default).
A solid primitive’s Position attribute defines the position of the primitive’s origin with respect to its
owner, i.e. the EQUI origin or the SUBE origin.
For all negative primitives, the Position attributes define the position of the negative primitive’s origin
with respect to its owning solid primitive’s origin.
3.3 Primitives
The following primitives are available for equipment modelling in AVEVA E3D.
3.3.1 P-points
Each primitive has a set of P-points at fixed locations. A P-point is a point that has a position and
direction attribute as well as other attributes that are used by other modules and applications.
P-points are numbered, with P0 always being at the origin of the primitive. For example, a BOX has
7 P-points:
P1 is in the centre of the top face of the box and points away from the face in a +ve Z direction.
P2, P3, P4 and P5 are located on the four vertical faces. Each located at the centre of and pointing
away from its face.
P6 is located in the centre of the bottom face of the box pointing away from the face in a -ve Z
direction.
For equipment modelling, P-points are used for locating and aligning primitives.
To obtain a desired shape or effect in the model, negative primitives may be used to ‘cut’ a solid
primitive.
This worked example builds a piece of process equipment, a Reboiler, tagged E1301, from the AVEVA
Plant training project.
The equipment locations for the project are shown on the following Equipment Location drawing below.
The dimensions for Reboiler E1301 are shown on the Equipment Arrangement drawing below.
Before starting to model E1301, or any equipment item, key decisions need to be made:
The equipment origin can be placed anywhere. It could be placed on the bottom of one of the
saddles so that it may be located on a foundation, however, looking at the location information on
the Equipment Location drawing, it would be easier to place the origin on the centreline of the
equipment in line with nozzles NS1 and NS2.
There is little point in modelling the equipment in one orientation and then re-orientating it when
complete. From the Equipment Location end to the North, so this is the orientation that will be
used for the primitives. The equipment will use the default orientation of Y is N and Z is Up.
Looking at the Equipment Arrangement drawing for E1301 it may be broken down to the following
primitives:
6 x Cylinders
2 x Boxes
5 x Nozzles
1 x Dish
Total 14 Primitives
Although it is not important in which order the primitives are built, it makes sense to model the main
‘body’ of the Reboiler first, i.e. the longest cylinder (Cylinder 1). From this base most of the other
primitives can be positioned.
Before beginning to model the primitives for this equipment, it is important to consider your working
plane. The cylinders modelled here will have their Z-axes’ as the North/South axis, thus we will use the
UW plane. This may be selected from VIEW > Local Coordinate System > UW or by selecting the plane
from the PowerCompassTM. We will remain in this plane for the entire worked example.
This will activate the Contextual Editor, which will guide the user though the creation stages.
The southern end of the cylinder is 290 – 60 = 230mm South of the equipment origin. We will use this
as its base centre.
Enter E 0 N -230 U 0 in to the co-ordinates boxes. After typing each co-ordinate press the Tab key to
lock it and advance to the next co-ordinate. Once complete press the Return key to advance.
From the Equipment Arrangement drawing, the length of this cylinder can be derived as 6590 – 60 –
60 = 6470mm and has a diameter of 835mm.
This will complete the cylinder creation. Right click and drag to 11 O’clock on the PowerWheelTM to set
Limits Extents.
The next primitive to be created is the flange on the southern end of the equipment (Cylinder 2). On the
Create Primitive form click Cylinder again to display the contextual editor.
From the Equipment Arrangement drawing, the thickness of the flange is 60mm and the diameter is
960mm.
With equipment E1301 as the CE, type CYLI into the 3D View.
Position the base centre of the new cylinder at P1 of the first cylinder. P-point snaps may be turned on by
holding <Shift>, right clicking and dragging to 12 O’clock on the snaps PowerWheelTM.
Enter 60 in the Height input box and 960 in the Diameter input box.
Enter 910 for the diameter. When prompted for the dish
height, press the down arrow and select Knuckle Radius,
then input 75. Then input -200 for the height.
See page 101 for more details regarding dish definition and knuckle radii.
A Nozzle (NOZZ) primitive has its origin, P-point P0, at the face of the nozzle
flange and is co-incident with P-point P1.
P-point P2 is at the bottom of the ‘stem’ of the nozzle and the Height attribute is
the distance between P1 and P2.
When a nozzle is positioned it is the origin position (P0) that is specified. A nozzle
orientation may be specified by setting the direction of P1 or the origin may be
rotated around another axis.
It is customary to model the nozzle ‘stem’ back to the centreline of the vessel.
The first nozzle to be created is NS2, a 100mm Nominal Bore, 150lb ANSI flange nozzle.
The Equipment Arrangement drawings shows that the nozzle is located at the equipment origin in both
the North/South direction and the East/West direction The face of the nozzle’s flange is 635mm above
the equipment centreline.
Make the EQUI element E1301 the CE and set the viewing
direction to Iso .
Enter 635 in the Height textbox to model the stem back to the
centreline.
The entries in the Specification, Generic Type and Bore options list depend on the nozzle
specifications in the catalogue.
In the Position fold-up panel of the Modify Nozzle form, enter 635 in the Up
textbox.
With the Origin as the datum, rotate the nozzle 90° around the Y Axis using
the Rotate fold-up panel.
Click the Next button on the Modify Nozzle form to display the Create
Primitive form.
With nozzle NS2 as the Current selection, type RO into the 3D View.
Press the down arrow and select Copy.
The nozzle is given a system name, NOZZ Copy-of-NS2, as the Rotate + Copy mode did not offer an
option to rename the copy elements.
Right click on NOZZ Copy-of-NS2 in Model Explorer and select Rename from the Model Explorer pop-
up menu to display the Name form. Enter E1301/NS1 in the Name textbox on the form, click the Apply
button to rename the nozzle and then close the form.
From the Equipment Arrangement drawing, nozzle N2 is a 200 NB 300lb Ansi Flange nozzle
positioned 350 + 460 = 810mm North of nozzle NS2.
From the Equipment Arrangement drawing, nozzle N1 is 2440mm North of nozzle N2, rotated by 180º
and has the same specification and nominal bore.
From the Equipment Arrangement drawing, the final nozzle, N3, is 2440 + 2440 = 4880mm North of
nozzle N2 and is the same specification and nominal bore. Move with Copy the Nozzle N2 4880 North.
With the EQUI element E1301 as the CE, in the Create group, select
Sub-Equipment from the Create Equipment button options list to
display the Sub-Equipment form.
For the supports there is no reason to make the SUBE element origin
different from the owning EQUI element origin.
Leave the position as the default, i.e. the same as the owing element,
and click the OK button and then close the form.
The two supports are modelled as BOX primitives. From the Equipment Arrangement drawing, the
supports are 200mm wide x 460mm long and the bottoms of the supports are 630mm below the
centreline of the equipment.
The box primitive can now be copied to create the second support. From the Equipment Arrangement
drawing, the second support is 3660mm North of the first support.
With Box 1 as the current selection, type CO into the 3D View, then select a point on the box for the
base point, here P5 has been used.
This kind of volume may be represented by a primitive, but is usually only required for clash detection
purposes and would not normally be displayed during modelling activities.
These kinds of primitives are called Obstruction Volumes and are placed on the obstruction display
levels, 9 10 by default. This type of volume may be used for such things as escape routes, walkways,
valve access, maintenance access, lifting access, etc.
From the Equipment Location drawing, the tube-pull volume must be 6500 long. Although no diameter
is given, making it the OD of the main vessel, i.e. 835, will adequately cover the tube bundle.
Although equipment primitives are not usually named, this cylinder has a particular function so re-name it
to E1301/TUBE_PULL.
On the Graphics Settings form, on the Representation tab, enter 6 in the Others textbox in the Level
frame. Note that the tube pull obstruction volume is no longer displayed.
Select 50% from the Obstruction Visibility/Translucency options list and click the Apply button. The
tube pull obstruction volume is now displayed at 50% translucency.
On the Graphics Settings form, select Off from the Obstruction Visibility/Translucency options list,
click the Apply button and close the form.
On the PROJECT tab, select Save Work and click the Yes button in the confirmation message.
Iso View
VIEW A-A
SECTION B-B
SECTION C-C
Additional Information
Create one sub-equipment named /SKIRT and one sub-equipment named /COLUMN. The origins of
both sub-equipments should be the same as for the EQUI element as all dimensions are relative to
the underside of the baseplate.
The skirt is constructed of a 1473 OD x 30WT tube and has a 600 OD x 20WT access sleeve on the
southern axis.
This exercise creates the Reflux Drum, tagged D1201. The Equipment Arrangement drawing for
D1201, together with the Nozzle Schedule, are shown below.
Nozzle Schedule
The previous chapter described how equipment items can be created using primitives arranged in 3D space
but with no relationship between them. AVEVA E3D enables equipment templates to be created and
instances of the template placed in the model.
An equipment template is a collection of primitives that make up the equipment shape grouped together
under a Template (TMPL) element. The template definitions are held in a Design database which is
referenced when an instance of the template is created. Templates can be of two types:
Parameterised templates – contain rules that allow the primitives of the equipment to be re-sized and
re-positioned or supports, if any, to be added or modified.
The creation of equipment templates id outside the scope of this training guide.
On the EQUIPMENT tab, in the Create group, selecting Standard from the Create Equipment button
options list displays the Create Equipment form. The form enables an equipment item to be created by
making a series of selections based on the styles of various equipment templates.
There are two methods are used to select the appropriate template, a Selection Table or a Specification.
The middle part of the form contains two lists. The upper
one is the Current Selection which is empty at the start of
the process, and the lower one is the Selection list from
which selections are made. The options in the Selection
list depend on the Specification selected.
The process continues until all choices have been made and a template has been selected. A model of the
selected template is displayed in the 3D View at the bottom of the form.
If a Plotfile has been created for the equipment item it can be displayed by
clicking the Plotfile… button.
The Plotfile usually contains information relating to key dimensions and the
equipment origin.
Clicking the Apply button displays the Positioning Control form and the prompt ‘Position Equipment Origin
Snap (Snap):’
The equipment may be positioned in the model using appropriate settings on the Positioning Control form.
Equipment items can be created with more meaningful element types, other than EQUI, that better describe
their function. For example, model elements may be called :PUMP, :REBOILER, :TANK, or :FILTER. This
is achieved through the use of User Defined Element Types (UDETs).
UDETs are created based on a standard AVEVA E3D element type, in this case equipment (EQUI) items.
UDETs are defined in AVEVA Administration™ Lexicon module and generally have the same attributes
as the base type, although some of the attributes may be hidden at the time of creating the UDET.
UDETs are distinguished from standard element types by the prefix of a colon, similar to User Defined
Attributes (UDAs). They also have an ActType (active type) attribute which is set to the UDET type, e.g.
:PUMP. The standard Type attribute is set to the base type, e.g. EQUI.
In most respects UDETs may be used in exactly the same way as EQUI elements. However, in the current
User Interface there are no forms to create the UDET elements, other than where an equipment template is
used. UDETs can be created using the Command Window by entering the syntax NEW <UDET>, e.g. NEW
:PUMP.
Once a UDET has been created its ActType attribute may be changed by using the Command line syntax
CHANGETYPE TO <UDET>, where <UDET> is another valid UDET for the Type defined in Lexicon. An
EQUI may also be changed to a UDET using the same syntax.
This worked example creates two stacked Heat Exchangers, tagged E1302A and E1302B, using pre-
defined equipment templates. The equipment will be created using a User Defined Element Type (UDET)
of :HEATEX.
4.4.1 Information
The Equipment Arrangement drawing for the two heat exchangers, together with Nozzle Schedules and
stacking arrangement, is shown below.
E1302A
Nozzle Schedule
Stacking Arrangement
E1302B will be created first as it is the top exchanger and only has one set of supports.
From the User Defined Type options list select HEATEX. This
will create the equipment as a UDET :HEATEX
Select the Selection Table radio button and from the Selection
Table options list select /AVEVA_STD_EQUIP.
Each property of the template has an assigned letter, a description and a default value. The drawing in the
graphics view may be zoomed, using the mouse scroll wheel, or zoomed in using a window by clicking and
holding down the left mouse button whilst dragging a rectangle on the view. When zoomed in, clicking the
middle mouse button will progressively zoom out.
Using the Equipment Arrangement drawing for E1302B, enter the following values for the dimensional
properties on the form:
The drawing on the form shows the exchanger with no supports and the
Exchange Support property is set to a default of No Supports.
Click the small down arrow adjacent to the textbox to display the
Exchanger Support form.
E = Distance to CL 450.
On the Modify Properties form for the Exchanger click the OK button to enter the values and close the
form.
Click the Explicit Position button on the Positioning Control form to display the Explicit Position form.
From the Equipment Location drawing, the following values can be derived
for the origin of E1302B:
N 294460
Up 109757
Enter the values in the Explicit Position form and click the Apply button and close the form.
The origin of the Heat Exchanger is in the correct position, however, from the Equipment Location drawing
it can be seen that the flanged end must be at the southern end of the equipment, i.e. the equipment needs
to be rotated 180º about the Z axis of the origin.
Double click E1302B to enter Editor mode and display the equipment grips at the origin of E1302B. Rotate
the equipment around the Z axis by 180°. Press <Escape> to exit Editor mode.
Select Rename from the pop-up menu to display the Name form.
Enter E1302B/NS1 in the Name textbox and click the Apply
button. Close the form.
Repeat the operation for the remaining three nozzles, entering the following data:
NOZZ2 – Name: E1302B/NS2, Specification: 150lb Ansi Flange, Nominal Bore: 100mm
NOZZ3 – Name: E1302B/N2, Specification: 150lb Ansi Flange, Nominal Bore: 150mm
NOZZ3 – Name: E1302B/N1, Specification: 150lb Ansi Flange, Nominal Bore: 150mm
From the Equipment Arrangement drawing it can be seen that E1302A is a mirror of E1302B with some
nozzle specification differences and additional ‘feet’ to support E1302B.
Rather than go through the creation process again, it is easier to copy and mirror E1302B and make the
required changes and additions afterwards.
With E1302B as the CE, select HOME > Create > Copy
Mirror display the Mirror form.
Select Rel. from the To options list to place the copy in the
same place in the hierarchy as the original.
The plane must, therefore, be moved to an elevation of 109757 – (922 / 2) = 109296, i.e. in the middle of the
two centreline elevations.
Enter the value in the Up textbox and click the Apply button to create the new heat exchanger. Click the
Yes button on the confirmation message to retain the copy and close the Mirror form.
Right click on E1302A in Model Explorer and select Rename from the pop-up menu to display the Name
form. Enter E1302A in the Name textbox and click the Apply button. Do not close the form.
The nozzles also need to be renamed in accordance with the Equipment Arrangement drawing for
E1302A.
Navigate to NOZZ 1 of E1302A in Model Explorer. Click the CE button on the name form and enter
E1302A/NS2 in the Name textbox, press the Return key and click the Apply button to rename the nozzle.
Repeat the process, entering the following values for the remaining three nozzles:
The nozzle specification for Nozzle N2 on E1302A is different from that of Nozzle N1 on E1302B and must
be re-specified as an 80 NB 300lb Ansi Flange nozzle.
Navigate to the nozzle in Model Explorer and On the EQUIPMENT tab, in the Modify group, click the
Nozzle button to display the Modify Nozzle form. Verify that the Specification is already set at ANSI-
NOZZLES and the Generic Type set to 300lb Ansi Flanges. Select 80mm from the Nominal Bore options
list, click the Next button and close the form.
E1302A requires two additional feet to support E1302B. The new feet will be created by copying and
rotating the existing feet.
Before beginning make sure working plane is set to the UW plane. This may be set by selecting the green
plane from the PowerCompassTM.
Double click E1302A to enter Editor mode for the equipment, then double click one of the Box supports of
E1302A to enter the editor for the SUBE. The SUBE should now be the current selection.
Type RO into the 3D View then press <Enter>. Press the down arrow key and choose the Copy option.
Pick a point on the centreline of E1302A for the base point, here P0 of Cylinder 6 has been used.
Then enter 180 in the angle input box, a preview may be seen. Pressing <Enter> will complete the
command and create the rotated copy of the supports.
This exercise creates the four pumps found on the Equipment Location drawing:
The duty and standby Reflux Pumps, tagged P1501A and P1501B.
The duty and standby Overhead Product Pumps, tagged P1502A and P1502B.
The Equipment GA for each set of pumps, together with the Nozzle Schedules, are shown below.
P1501A & B
Nozzle Schedule
The pumps are Centrifugal, Centreline Mounted, Tangential Outlet Pumps (AVEVA Standard,
template PUMP005).
To use the template, the origin position of the pump must be derived from the positional information
given on the Equipment Location drawing.
Create the first pump as a UDET :PUMP and Move with copy this pump to create the second pump.
P1502A & B
Nozzle Schedule
The pumps are Centrifugal, Centreline Mounted, Vertical Offset Nozzle Pumps (AVEVA Standard,
template PUMP006).
To use the template, the origin position of the pump must be derived from the positional information
given on the Equipment Location drawing.
Create the first pump as a UDET :PUMP and move with copy this pump to create the second pump.
An Electrical Component (ELCONN) in equipment terms is a connection point between equipment and
cables and can represent anything from an individual cable gland to a piece of electrical equipment, such as
a generator. Electrical components are catalogue items and are selected from the catalogue via a selection
table and are positioned and orientated within equipment in the same way as nozzles and primitives.
If the project has been configured with User Defined Element Types based on electrical component
(ELCONN) element type, they will appear in the User Defined Type list. When the electrical
component element is created, it will be created as the User Defined Type selected from this list.
Selecting a User Defined Element Type may change the content of the Selection Table if the table has
been configured to filter on element type.
Clear the Drawlist and add back pump P1501B. Use the PowerWheelTM to Limit Extents and set the view
direction to Iso .
Save Work.
The Equipment discipline provides utilities that can aid productivity for equipment modelling and reporting,
including the Mechanical Equipment Interface, the Import Equipment Data utility and the Equipment
Report utility.
The Mechanical Equipment Interface (MEI) enables STEP (.stp) files generated by mechanical modeling
software to be imported into AVEVA E3D. Whilst the resultant equipment items are not ‘intelligent’, nozzles
may be created to overlay the imported model so that pipework may be connected to the equipment.
The model may be imported as an Equipment (EQUI) element or a Volume Model (VOLM) element,
selected from the Import Model As options list. Leave the setting as Equipment, the default.
Empty the 3D View and click the Import button to start the model import.
The import will take time depending on the size of the file to be imported.
Click in the Value cell of the Orientation WRT Owner attribute and edit
the attribute from Y is N and Z is U to Y is U and Z is E.
Select 300lb Ansi Flanges from the Generic Type options list.
With the pump as the CE zoom in to the vertical nozzle on the body of the
pump. Click the Position Nozzle link label to display additional information
on positioning at the bottom of the form:
Click and hold the left mouse button and select two opposing points on the
circumference of the nozzle, releasing the mouse button after each pick
The new nozzle is located in the centre of the model nozzle but is incorrectly
orientated.
Click the Flip Direction link label to orientate the nozzle correctly, as indicated by
the aid arrow.
Click the Create Nozzle link label to create the new ‘intelligent’ nozzle.
Close the MEI Create Nozzle and the MEI Import forms.
Equipment (EQUI) or Volume Model (VOLM) elements in AVEVA E3D may be exported to a STEP (.stp) file
and imported by other 3rd Party packages.
Clicking the OK button creates the STEP file in the specified location.
The Import Equipment Data utility enables EQUI elements to be created in the database by importing data
from an Excel (.xls) or comma separated value (.csv) file. The import data may set any of the standard
attributes or UDAs of an EQUI element but will not create any primitives.
The Type column displays the element type, including UDETs, and each entry is prefixed by an icon which
represent the status of the data, as described in the following table:
This icon indicates that no equipment with the name exists in the database. If the data is loaded, an
element of this name will be created.
This icon indicates that equipment with the name already exists in the database. If the Load All Data
function is used, then attributes of the existing equipment will be modified. No action will be
taken on rows with this icon if the Load New Data button is used.
This icon indicates that the system has identified a problem with this row of data. No action will be
taken on rows with this icon when the Load All Data or Load New Data buttons are used.
Clicking the Load All Data button will process all of the rows that create a new element or modify an
existing element. Clicking the Load New Data button will only process the rows that create new elements.
New data is created at the current location in the database if an owning element field is not included in
the imported file. The owning element is considered to be the current element when the file was loaded
and the rows of data analysed, not the current element when a Load button is pressed. If an owning
element field is provided in the import file, the system will attempt to create elements under the
specified owner.
Once imported, the icons on the left of the form change to indicate the status of the loaded data.
This icon indicates that the creation or modification operation was successful, i.e. an element has
been created or modified in the database.
This icon indicates that the operation has not completed successfully because of an error found while
the system was trying to create or modify an element. If an attribute value is incorrect then the
element has been created, but not all of its attribute data has been loaded.
The Undo function may be used to remove all of the changes made by the load operation and revert
the database back to its state before the load, or the errors on the erroneous elements dealt with
individually.
Selecting a row in the table with this icon will display a message in the Messages area of the form to
indicate the error.
Another import file can be loaded by clicking the Open File button or by typing a name directly into the
filename textbox on the form.
The Reload File button reloads the file shown in the filename textbox. This may be necessary if the current
element was incorrect or an owner element was missing when the file was first loaded.
It is possible to load element types other than Equipment using this utility. If the imported file is carefully
constructed, following the rules listed below, it would be possible to import other element types provided that
fields in the file contain all of the required data. For example, a nozzle list could be loaded provided that the
owning equipment name is provided in an Owner field for each nozzle element, and the Type field identifies
the element as a nozzle.
5.2.1 Rules for the Content of Import XLS and CSV Files
The first row of the file contains a list of headings. Each heading represents a column in the file
containing an attribute of the elements being loaded.
There must be a NAME column; otherwise the file will not be loaded. The NAME column may contain
the name of a new element, or the name of an existing element. If an existing element name is used,
then this row is an update row for that element. The name used must obey the normal rules for element
naming in AVEVA E3D.
There must be a TYPE column. This column contains the database element type of the element being
loaded, e.g. EQUI. If this column is absent, the file will not be loaded. If the Project has been configured
with User Defined Element Types, then this column could contain a valid UDET name (e.g. :PUMP). If
the named element already exists, but its element type does not match the TYPE in the file, then this
row will be ignored and an error raised.
An OWNER column may be included. If this column is present, it must contain the name of an existing
element that will own each imported item when it is created. This owner name will be ignored if the
Copyright © 2013. 53 www.aveva.com
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Everything3D™ (2.1)
Equipment Modelling TM-1811
imported item already exists, i.e. it is not possible to change the owner of existing Equipment by using
the OWNER column. If the OWNER column does not exist in the file, then the owner is the current
location in the Design db hierarchy at the time that the file is loaded and analysed. In this case, the
current database element at the time that the file is loaded must be able to contain imported elements.
The remaining headings in the file must be valid attribute names for the element type being loaded. The
attribute names may include User Defined Attribute (UDA) names.
Columns cannot be added for array type attributes unless those attributes can be set using a list of
values in a single field in the file. For example, the string "10 20 30" in a DESP field would set design
parameter 1 to 10, 2 to 20 and 3 to 30.
Every row following the heading row must contain the correct number of fields (columns) as defined by
the heading row.
Every row must contain valid values, or no values, for each field.
If a new element is being created, an attribute will be set to its default value if a field in the file is empty.
Two adjacent separators denote an empty field. The NAME and TYPE fields cannot be empty.
If an existing element is being modified, an attribute value will remain unchanged if a field in the file is
empty.
It is not possible to unset an attribute value from a file, other than by providing the default value. For
example "X0Y0Z0" for a position.
Each field in the file must be a text field. Care must be taken with fields containing values that are
considered by Microsoft Excel to be a formula. For example a database reference number in the form
"=123/456" would be considered to be a formula because of the = character. This can be overcome by
proceeding the = character with a single quote character that forces the field to be treated as a text
string. If the file will not load successfully into Microsoft Excel, it will not load successfully using this
import utility.
Any import of new or modified element data will be subject to the data access control configuration
implemented for the current User and Project.
This utility will not attempt to claim data automatically in an Explicit Claim database. If the data is imported
into an Implicit Claim database, then the appropriate elements will be claimed, if not already claimed by
another user.
The Equipment Report utility is specifically designed to quickly generate configurable equipment reports
using the equipment elements and their attributes stored in the Design databases. The reports may be
exported to Excel for printing or additional enhancement.
On the EQUIPMENT tab, in the Report group, clicking the Equipment Report button displays the
Equipment Report form. The form has two tabs, Columns and Output.
The Columns tab allows the definition of the report including the elements and their attributes to be
reported.
The Report Type options list sets the type of element to be reported. Reports can be generated for
Equipment items, Nozzles or Electrical Components.
The scope of the report is selected using the Scope options list and can be set to All, where the entire MDB
is used or the Current Element where the CE will be used.
The tab has two lists, the left showing Available Attributes and the right showing Chosen Attributes
which, by default, is empty.
The Available Attributes list shows the standard attributes and UDAs available for the selected report
element type, in alpha-numeric order, together with their Description, Data Type and Report Header, i.e.
the text that will appear at the top of the column if the attribute is selected to appear in the report.
The Pseudo Attributes checkbox, which is by default unchecked, may be used to include the pseudo
attributes of an element in the Available Attributes list, thereby making them available for inclusion in the
report.
Once the attribute selection process has commenced the checkbox is greyed out, therefore, the choice
whether to include them in the report must be made before attribute selection starts.
Emptying the Chosen Attributes list re-activates the Pseudo Attributes checkbox.
Between the two lists are four buttons that facilitate transfer of the attributes from one pane to another.
Left clicking on an attribute in either list highlights the selection. Multiple attributes may be selected in either
list using the standard Windows selection methods. Attributes may only appear in one of the lists; therefore,
attributes added to the Chosen Attributes list no longer appear in the Available Attributes list.
The attributes will populate the Chosen Attributes list in the order they are selected. Multiple, non-
contiguous selections will appear in alpha-numeric order when added to the Chosen Attributes list. The
four buttons on the right hand side of the Chosen Attributes list may be used to modify the list order.
Having selected the Element Type, Scope and Attributes, clicking the Output tab presents the data in a
grid where the columns are in the order specified in the Chosen Attributes list and the column headings are
the Report Header texts.
The data in the Output tab grid may be grouped, filtered, sorted and summarised as per standard
AVEVA E3D grid functionality.
Grouped and filter operations on the Output tab are reflected in the resulting Excel file.
This exercise imports a csv file to create a number of equipment elements and generates various equipment
reports.
Import file TM-1104_Ex4_EquipImport.csv, located in the AVEVA E3D user folder typically
C:\AVEVA\Plant \PlantTraining2.1\Training\userdata, to the new Zone.
The equipment reports should show the following attributes in the order given:
b) Owner.
c) ActType.
d) Description.
e) Position.
f) Orientation.
This chapter gives an overview of associations and describes the use of the Equipment Association utility
within AVEVA E3D.
Associations are user defined constraints (restrictions) between two or more objects in the Model database.
The restrictions provide logic that can be evaluated to describe how the objects relate to each other.
Geometric restrictions, e.g. the origin points of two elements must be co-incident.
Checking the existence of elements, e.g. a hole exists for a pipe to pass through.
Attribute comparison, e.g. the material of the associated elements are the same.
AVEVA provides a set of core association definitions that are used in the AVEVA E3D utilities and
applications that use associations, i.e. Equipment Associations, Hole Management and MDS. The User is
also able to create alternative association definitions for user defined utilities and applications.
Associations are passive, i.e. they must be queried to see if they pass or fail their defined restrictions. An
association cannot resolve itself if it is broken. It must be clearly understood that association utilities and
applications are NOT geometric constraint solvers.
For dynamic geometric constraints attribute rules should be used. Information on these can be found in
the AVEVA E3D help files and reference guides. Attribute rules are not discussed in this Training
Guide.
Association Definitions are stored in read only Design (DESI) database with the following hierarchy
elements.
Associations are stored in a Design database with the following hierarchy elements.
When an Equipment Association is created, an instance of the selected Association Definition is created
in the first Association Group (ASSOGP) element with the Purpose attribute set to ASEQ and the
references set for the objects involved in the association. The restriction(s) of the association are tested and
if the results are valid the association is passed and if invalid, the association is failed.
The Equipment Associations utility provides pre-defined associations for equipment based on the AVEVA
supplied core associations. The types of equipment associations are:
Parallel Offset Two lines are parallel and separated by a given distance.
Horizontal One point is vertically above the other point, or separated in the
Distance horizontal plane by a given distance.
Point Above
A point is vertically above or below a line within a given tolerance.
Line
The equipment associations outlined above require association reference planes to be established between
Model elements. The reference planes can be established on the standard P-points for primitives or on
additional design points created uniquely for associations.
Although existing P-points of equipment primitives may be picked for the association reference planes, it can
be quite difficult to pick a particular graphical point in a 3D View where many elements are displayed. To
make it easier to select reference points or lines to be used in an Association, it is recommended that
Design Points are created in Design Templates, and P-points in catalogue items that identify themselves as
connection points for associations.
However, if these points are not available in the templates or catalogue items, Design Points may be added
to EQUI element, or UDETs based on an EQUI, at appropriate locations in the element so that they are
readily available to users when creating associations.
The Association Design Points must have their Purpose attribute set to a four character value where the
first two characters are chosen by the user defining the point, and the last two characters must be 'FA'.
For example, an Equipment may be created with three Association Design Points with Purpose attributes
set to CLFA for centre-line, BOFA for bottom face and TOFA for top face.
Identify the two pumps named /P1501A and /P1501B in the 3D View. A Parallel Offset association will be
created for these two pumps to ensure that their centrelines remain parallel at a minimum distance.
In this example the ZDIR points represent the default reference planes on the items, i.e. the origin of
the pumps.
Select Min. from the Separation options list and enter 1800 in
the adjacent textbox. This means that the two pumps must
have a minimum centreline separation of 1800mm.
Click the Undo button on the Quick Access Toolbar to move P1501A back to its original position. Press
Escape to exit Editor mode.
Re-test the association to ensure that the Test Result is now Passed. Click the Back button on the
Equipment Associations form to return to the previous form display showing the association types.
Select Max from the Separation options list and enter 2200 in
the adjacent textbox.
Test the associations by moving either pump beyond the maximum and minimum constraints before
returning them to their original positions.
For the associations created previously in this worked example the default ZDIR origin plane was used,
however, reference planes may also be selected from existing P-points on elements consisting of primitives
or Plines from structural profile elements.
Clear the Drawlist. Drag and drop pumps :PUMP P1502A and :PUMP P1502B from ZONE-EQUIPMENT-
AREA01 and :SLAB BASE_SLAB from ZONE ZONE-CIVIL-AREA01 into the 3D View and use the
PowerWheelTM to set Limits Extents.
Identify pump P1502B in the 3D View. A Mate association will be created between the pump and its
concrete base using selected reference planes.
Click the Select Association Item… link label at the top of the
Equipment Associations form and select P1502B from the 3D
View.
Left click and hold on the pump baseplate BOX primitive and
select the lowest of the three P-points displayed at the centre
of the primitive, i.e. P6.
Left click and hold on the base BOX primitive and select the
upper of the three P-points displayed at the centre of the
primitive, i.e. P3.
Select Equal from the Separation options list and enter 0 in the adjacent textbox.
Click the Create Association button to create the association and check that the Test Result has passed.
Right click on the newly created association in the list and select
Association Details… from the pop-up menu to display the
Association Detail form.
Note that this association comprises of two restrictions, one that
the directions of the reference planes must be parallel and
opposite and one for the separation, i.e. Distance 1st member
point to 2nd member plane.
Move the pump up using the Editor mode and re-test the
association. Check the association details again and note that
only one of the two restrictions has failed, i.e. the separation.
Return the pump to its original position and exit Editor mode.
Close the Association Detail form and the Equipment
Associations form.
Close the form and return to the Design Points form where
the Design Point is now displayed.
Click the Mate radio button and click the Pick Association
Partner link label.
Select BOFA from the Use reference Plane options list in the
Source Element frame.
Equipment associations may be deleted by highlighting the association in the list and clicking the Delete
Association link label at the bottom of the Equipment Associations form.
Alternatively, the association may be deleted by right clicking the association in the list and selecting Delete
from the pop-up menu.
If an element participating in an association is deleted, the Association test will return the result false to
indicate that the association has failed.
It is possible to find out which element has been deleted by inspecting the Association Member (ASSMBR)
elements for a bad reference in the Amemrf attribute.
The Association Manager enables the user to view all Equipment Associations or a selected subset of the
Equipment Associations in the project.
On the EQUIPMENT tab, in the Associate group, clicking the Manage Associations button displays the
Association Manager form.
Current Element – this option displays all associations which the current element is involved in.
Selected Purpose – this option activates the Purpose options list where ASEQ can be selected to
display only Equipment Associations.
Invalid – this option shows all associations where the settings are incorrectly specified and are
invalid.
Contain Invalid References – this option displays all associations where one or more of the
ASSMBR elements has its Amemrf attribute set to an invalid reference.
The filtered associations are displayed in a grid in the Associations frame, displaying the Association
name of the association, the Description of the association type, the Purpose and the two elements
involved in the association. Clicking the Refresh button refreshes the list.
View Association Elements– this option zooms into the association items in the 3D View.
Navigate To – this option has a sub-menu that enables the user to navigate to the association
(ASSOC) or either of the association items in Model Explorer.
Export to Excel – this option displays the Save Association Data As browser that enables the user to
select a folder and filename to save the entire association grid to an Excel (.xls) file
Print Preview – opens a standard windows print preview dialogue and allows the grid to be printed.
Left clicking on any association in the list highlights it in blue and populates the Restrictions and
Associated Detail frames of the Association Manager form.
The Restrictions frame displays the Restriction Description and Status for the one or more restrictions
that make up the association in a grid.
Right clicking on any entry in the grid displays a pop-up menu with the same
Navigate To functions described previously.
The Association Detail frame displays the Target (reference plane) of each element, the Position of the
target, the Direction and XDistance, YDistsnace and ZDistance of the two reference planes and the
Actual Distance between the points.
Right clicking on any entry in the grid displays a pop-up menu with an option
to Navigate To Target, i.e. the primitive, and the same export and print
functions described previously.
Association Worlds (ASSOWL) and Association Groups (ASSOGP) for the storage of Equipment
Associations (and other associations) may be created, modified, deleted and organised using the Organise
Association Store form.
On the EQUIPMENT tab, in the Associate group, selecting Browser from the Manage Associations
button options list displays the Organise Association Store form.
The form displays all ASSOWL elements in the project in a grid and has link labels to enable Association
World (ASSOWL) elements to be created, modified and deleted.
The Show Association Groups link label replaces the Association World grid with an Association Group
grid and link labels to enable Association Group (ASSOGP) elements to be created, modified and deleted.
Create a Mate association between the bottom face of C1101 skirt and the top face of the :SLAB
BASE_SLAB element. Test the association by moving the slab element.
On a typical AVEVA Plant project it is necessary for designers to create holes in panel elements, i.e. deck
plates, grating, walls, floors, etc. Due to the implications on design integrity and cost, the hole creation
process needs to be controlled and managed.
AVEVA E3D controls and manages holes using the Hole Management utility which facilitates:
Communication of hole data between disciplines including Request and Approval processes.
Ensuring holes are only created by users with appropriate write access permissions.
Performing validation checks on managed holes and providing feedback to users on the hole status.
Generally in AVEVA Plant projects discipline Designers do not have write access to items created by other
disciplines, i.e. a Piping Designer does not have write access to Structural elements and Structural
Designers do not have write access to Piping elements, etc.
With the Hole Management utility, holes are specified and requested by the penetrating discipline, normally
piping, HVAC or Equipment designers. Approval of hole requests is provided by the team that owns the
penetrated element, normally Structural Designers.
The specification of a penetration hole by the relevant discipline in the appropriate Design discipline creates
a ‘virtual hole’ in the panel element, consisting of a FRMW and two FIXING elements. Each FIXING
element has a Specification Reference (Spref) attribute that points to the hole definition in the catalogue.
An Association (ASSOC) element that references all of the hole elements is also created.
Once the ‘virtual hole’ has been created the penetrating discipline enters the Hole Management utility and
requests the hole. The owner of the penetrated element then reviews and approves (or rejects) the hole
request using the mechanism provided by the Hole Management utility.
The act of approving the request creates the ‘actual’ hole as a PFIT owned by the PANE element. The Hole
Management utility checks and validates the hole using the association restrictions and stores data on the
hole history and status. Only valid holes may be approved.
If no ASSOGP element with the Purpose set to HOLE can be found, the
Hole Management utility will create an ASSOGP in the first writeable
ASSOWL element and set the Purpose attribute.
Once the penetration hole has been specified and the ‘virtual’ hole created, the Hole Management utility
provides a series of tasks for the Originator (Penetrating discipline) and Reviewer (Penetrated discipline).
Originator
Reviewer Tasks
Tasks
Request Approve
Redundant Reject
Delete Entry
The main workflow scenarios for the request/approval cycle are detailed in the following sections.
In this workflow the Originator creates the ‘virtual’ hole and then either requests it or deletes the entry.
Once requested, the Originator may cancel the request and delete the entry prior to it being reviewed.
If requested and not cancelled or deleted, the Reviewer checks the hole details and, if acceptable, approves
it, thereby creating the ‘actual’ hole.
If the Reviewer rejects the hole, the Originator may re-request the hole without modification, modify the
‘virtual’ hole and then re-request it, cancel the request or delete the entry.
In this workflow the ‘actual’ hole has been created. The Originator decides that the hole is now redundant
and sets its status to Redundant.
Before the Originator can delete the entry the Reviewer must agree that the hole is redundant.
In this workflow the ‘actual’ hole has been created. The Reviewer, possibly due to changed conditions,
decides to reject the hole. The Originator has the option to:
Modify the hole and re-request it, whereby it will go through the normal review and approval cycle.
Cancel the request, in which case the ‘virtual’ hole details remain
Delete the entry, in which case the entire hole is deleted and the ‘virtual’ hole and association deleted.
The ‘actual’ hole is deleted and the panel restored to its original state.
The Hole Management utility, as with other applications that use associations, is passive, i.e. the user is not
alerted if a hole association is broken or invalidated. The User must enter the Hole Management application
and actively verify if the association is still valid.
The use of the application will vary from company to company. In some it may be down to the individual
designers to request and approve holes, whilst in others it may be the discipline lead designer or a
designated user who performs the tasks.
This worked example creates two penetrations in the plating of the lower level of the Equipment Support
Structure around the supports of the Reflux Drum D1201.
On the TOOLS tab, in the Training group, click the Setup button to display the Training Setup form.
Equipment penetrations require an EXTRUSION (EXTR) primitive to be part of the equipment to act as the
‘cut-out shape’ in the structural panel. The first task, therefore, is to create and identify the extrusion before
the hole is specified and requested.
If, as in this example, an equipment requires more than one penetration, an extrusion for each penetration
must be created in separate SUBE elements.
Remove all elements from the 3D View to clear the Drawlist. Add EQUI D1201 from ZONE-EQUIPMENT-
AREA01.
Set the viewing direction to Iso , use the PowerWheelTM to Limit Extents and set the working plane to
UV.
From the Defaults group in the EQUIPMENT tab, set the Representation Style to Obstruction and set the
Obstruction Level to Soft.
With the SUBE D1201_SUPP_A as the CE, on the EQUIPMENT tab, in the Create group, pick the
Extrusion option from the second row of the Primitives Gallery.
Make D1201_SUPP_B the CE and repeat the process for the second support, naming the extrusion
D1201_B_PENI.
Note that SUBE now includes a Port Set (PORS) element that owns a Port (PORI) element whose Tarflag
attribute has been set to the name of the extrusion, i.e. D1201_A_PENI.
Make SUBE D1201_SUPP_B the CE and repeat the process to set the penetration profile for the second
support.
On the EQUIPMENT tab, in the Penetrate group, click the Holes button to display the Hole Association
Manager form.
This form displays the Hole Associations in the model. The Hole Association Filter frame enables the
User to limit the display by selecting various Disciplines, Status, Claimed Status and Validities from the
option lists. The filtered Hole Management associations are displayed in the Hole Associations grid.
Make sure the Current Element radio button is selected (the default), leave the option lists at their default
settings and click the Apply Filter link label. This displays all the hole associations that include the panel, in
this example there are only two.
The associations are displayed in a grid that gives information about the associations including their status
and validity. The Association column contains the auto-named association identifier.
Right clicking in the grid displays a pop-up menu that has the following options:
Navigate To – this option has a sub-menu enabling the Association, Penetrated Item or Penetrating
item to be selected. The selected item is navigated to in the Model Explorer and becomes the CE.
Validate – this option validates the hole association by checking the four restrictions. Details of the
restrictions are given later in this worked example. If all restrictions are satisfied the Valid column entry
for the association is changed to Passed. If one or more of the restrictions are not satisfied then the
Valid column entry is changed to Failed.
Add to 3D View – this option adds the association elements, i.e. the panel, branch and ‘virtual’ hole
fixings, to the 3D View.
Remove from 3D View – this option removes the association elements from the 3D View.
Focus on Hole – this option ‘zooms’ in to the selected hole. This is very useful in a complex model with
many penetration holes.
Save/Unclaim - this option enables the User to save the data and release the claim(s) to the selected
holes.
Export to Excel… – this option displays the Save Hole Association List As file browser form where a
location and filename for the exported grid may be specified. Clicking the Save button on the browser
creates an .xls file with the specified name.
Print Preview… – this option displays a Print Preview dialogue that enables the association list to be
viewed and printed.
Right click on the first association in the grid and select Focus on Hole from the pop-up menu. Note the 3D
View has zoomed into the penetration hole.
Right click on the first association in the grid again and select Validate from the pop-up menu to ensure the
hole is valid, i.e. the Valid column entry is set to Passed.
Multi select both holes from the grid and click the Manage Selected Holes link label to display the Hole
Management form.
The selected holes are displayed in a grid with different information to that of the Hole Association
Manager form. Note the Status column is blank, indicating that this hole has not previously been managed.
Right clicking in the column headers or any of the fields displays a pop-up menu which has similar options to
the Hole Association Management form pop-up menu described earlier.
The Hole Management form contains fold-up panels for Selected hole data, Hole validation results and
Hole History.
Select the first hole in the list and expand the Selected Hole Data fold-up panel to display the data for the
hole.
Minimise the Selected Hole Data fold-up panel and expand the Hole validation results fold-up panel.
Check existence of all associated elements – this test checks that all of the elements involved in the
association exist. It is possible that the panel, branch or other elements may have been deleted after
the penetration hole was created.
Check all associated elements intersect the Hole Owner – this test checks that the associated
elements actually pass through the owning panel. It is possible that the panel or the branch may have
been moved since the penetration hole was created.
Check all the virtual hole and the Design Point are coincident – this test checks that the virtual hole
and the Design Point, created with the penetration, are coincident.
If one or more of the test fail, then the whole association fails and the hole cannot be requested.
Minimise the Hole validation results fold-up panel and expand the Hole History fold-up panel. Note that
there are no entries in the panel as no tasks have been actioned for the hole. Minimise the Hole History
panel.
The Hole Comment textbox enables a comment to be added to the latest action by entering an appropriate
comment and clicking the Save button. Only the latest action comment is kept as no provision is made to
store them.
Click the Request link label and click the Yes button on the
displayed confirmation message.
Open the Hole History fold-up panel and note that an entry
has been made detailing the change in status of the hole.
Note that the Originator tasks are now inactive. Save Work and then close the Hole Management form.
Open the Training Setup form and on the Setup Tools tab enter login details for the Structural user.
Username: A.STEELMAN
Password: A
Click the Switch User button, click the Yes button on the Save Work confirmation message and close the
Training Setup form.
Select all element in the 3D View by using a selection fence then use the Remove Selection function on the
PowerWheelTM to clear the 3D View. Then add EQUI D1201 to the 3D View.
On the EQUIPMENT tab, in the Penetrate group, select Hole Manager from the Holes button options list to
display the Hole Management form.
Select both holes in the grid, click and drag them into the 3D View. Set Limits Extents using the
PowerWheelTM.
With the graphical view of the penetration hole visible, click the
Approve link label and click the Yes button on the displayed
confirmation message.
Note that the ‘virtual’ hole fixings have disappeared and the ‘actual’ hole has been created in the panel.
The ‘virtual’ hole fixing have not been deleted but removed from the Drawlist. There are retained in
event of the hole being modified.
Expand the Hole History fold-up panel and note the new Status column entry. Click the Return to Hole
Associations link label at the bottom of the Hole Management form to return to the Hole Association
Manager form.
The Reviewer may reject a hole on initial review or after it has been approved. In either case Originator
has the option to modify the hole and re-request, cancel the request or delete the entry.
Select the first penetration hole created) in the grid to make it the current association and click the Manage
Selected Holes link label to display the Hole Management form. This hole has previously been approved
so the only Reviewer task available is Reject.
Click the Reject link label under the Reviewer Tasks and then click the Yes button on the confirmation
message. The hole status has now changed to Rejected.
The Originator now has the option to modify the hole definition, as described above, Cancel Request or
Delete Entry, which have the following affects:
Cancelling the request removes the ‘actual’ hole and resets the Hole History Status to blank, i.e. it
has been reset to its original status after the ‘virtual’ hole was created but before it was requested. The
‘virtual’ hole fixings and hole management associations are retained so that the hole may be modified
and re-requested later.
Deleting the entry deletes the ‘actual’ hole, the ‘virtual’ hole fixings and the hole management
associations, restoring the panel to its original state before the penetration was created.
For this worked example the request will be cancelled and then the entry deleted. Save work then return to
the Hole Association Manager form and dismiss the form.
Open the Training Setup form and on the Setup Tools tab enter login details for the Equipment user.
Username: A.EQUIPMAN
Password: A
Click the Switch User button, click the Yes button on the Save Work confirmation message and close the
Training Setup form.
Navigate to the panel in SBFR /EL(+)104880_TOS_PLATE to make it the CE. On the EQUIPMENT tab, in
the Penetrate group, click the Holes button to display the Hole Association Manager form.
Select the hole that has just been rejected and click the Manage Selected Holes link label to display the
Hole Management form
Click the Cancel Request link label under the Originator Tasks to
display the cancel confirmation message.
Open the Hole History fold-up panel and note that the hole status is blank, i.e. Note also that the ‘virtual’
hole fixings are still present.
Click the Delete Entry link label under the Originator Tasks to
display the remove confirmation message.
Note that all references to the hole have been deleted from the Hole Management form and the ‘virtual’
hole fixings have also been deleted, restoring the panel to its original state at the penetration.
Click the Return to Hole Associations to display the Hole Association Manager form.
Select the second penetration hole created in the grid to make it the current association and click the
Manage Selected Holes link label to display the Hole Management form. This hole has previously been
approved so the only Originator task available is to make it Redundant.
Before the Originator can delete the entry the Reviewer has to agree it is redundant.
Click the Agree Redundant link label under the Originator Tasks
to display the redundant confirmation message.
Open the Hole History fold-up panel and note that the hole status has been set to Withdrawn.
The only Originator task now available is Delete Entry. Click the link label to delete the hole entry.
Create penetrations for E1302A supports in the upper deck panel of the Equipment Support Structure.
The trainee will need to switch users as necessary for the hole approval workflow.
Volume Models are similar to EQUI elements. They may be used for modelling any item in AVEVA E3D that
will be constructed from primitives but is not required to be displayed in the Model Explorer as an EQUI
element.
A typical use of volume models may include plant Civils items (e.g. concrete slabs, concrete plinths, site
roads) or the modelling of escape routes/access obstruction volumes. Volume models can also be used as a
method of reserving space within the plant layout for equipment items not yet ready for modelling.
VOLM elements have some of the attributes of an EQUI and may own primitives
directly, with the exception of Nozzles.
VOLM elements may own one or more optional Sub-Volume Model (SVOLM)
elements which may own any primitive except Nozzles. The SVOLM elements are used
to break down Volume Models into sub-parts and are similar, and have some of the
same attributes, as SUBE elements.
On the GENERAL tab, in the Volumes group, clicking the Volume button
displays the Volume Model form.
The form is similar to the Create Equipment form described earlier in the
training guide, except that there is no Attributes… button as VOLM
elements do not have the attributes that are set by this option.
VOLM elements may be named and positioned, the option lists and
textboxes enable its origin to be set with respect to any element, as for an
EQUI element.
With a VOLM as the CE, on the GENERAL tab, in the Volumes group,
clicking the Sub-Volume button displays the Sub Volume Model form.
SVOLM elements may be named and positioned, the option lists and
textboxes enable its origin to be set with respect to any element, as for a
SUBE element.
All primitives, except NOZZ elements may be owned directly by VOLM or by SVOLM elements. Primitives
are created and modified using the functions on the EQUIPMENT tab.
In the Training project all of the civil works and foundations are modelled using Volume Models and are
created in suitable Civils SITEs. Only members of the Civils team have access to these SITEs. In order to
carry out the worked examples and exercises it is necessary to switch user.
On the TOOLS tab, in the Training group, click the Setup button to display the Training Setup form.
Navigate to the Setup Tools tab and enter the following details for the new user:
Username: A.CIVILMAN
Password: A
In this worked example volume models are added to the Civils works to represent reserved walkway areas
which in reality have no physical geometry but need to be used during clash checking to ensure appropriate
room and access is available for plant personnel and machinery.
On the TOOLS tab, in the Display group, click the Commands button to display the Command Window.
In the Command Window enter NEW :WALKWAY /AREA01-WALKWAYS. This creates a user defined
element with the base type VOLM.
User Defined Element Types can only be created using the Command line.
The User Defined Element Type :WALKWAY has been previously defined in the Lexicon module. Query
the attributes and note that the ActType is :WALKWAY and the Type is VOLM.
In the Modify group, of the HOME tab, from the Move button option
list, click the Position button to display the Explicit Position form.
West 318000
North 302500
Up 100000.
The walkways will be made with a combination of BOX and Extrusion primitives. Extrusions are 2D shapes
that are extruded through a distance. An extrusion is made up of three elements:
EXTR – the extrusion itself. The Position attribute holds the World position of the extrusion origin and
the Height attribute holds the extrusion distance.
LOOP – this is the 2D shape that owns a series of vertices, one at each change in direction of the
shape.
VERT – these are the vertices. Their position is expressed in local co-ordinates, i.e. with respect to the
EXTR origin.
Right click the extrusion in the Model Explorer and click Rename. Using the rename element form, name
the extrusion WW-01_1.
On the VIEW tab, in the Settings group, click the Graphics button to display the Graphics Settings form.
On the Representation tab, select 50% from the Obstruction/Visibility Translucency options list and click
the Apply button to display the walkway.
Enter the box creation function from the button in the primitives
gallery, then press the down arrow and choose the Explicit option.
Xlength 1500mm
Ylength 9600mm
Zlength 2600mm
The Equipment Support structure in /ZONE-STRUCTURAL-AREA01 requires access stairs which will be
added as a separate design process. Using Volume models create a suitable reserved volume for these
stairs which can be also used as an access reservation volume once the stairs are modelled.
Two flights of stairs should be modelled as two extrusions. The top flight is 1130mm wide and the bottom
1260mm wide. The positions, wrt World, for the required vertices are shown below.
Ensure that the extrusions are set as Obstruction Volume and Soft.
Both extrusions should sit under a single VOLM named STWAY-001, each extrusion should be named
STWAY-001_1 and STWAY-001_2.
Save Work.
Please note that some P-points have been removed from selected images to maintain display clarity.
Box (BOX)
Cylinder (CYLI)
Cone (CONE)
Snout (SNOU)
Only an Xoffset is shown in this example, however, both Yoffset and Xoffset may be set.
Pyramid (PYRA)
Only a Yoffset is show in this example, however, both Yoffset and Xoffset may be set.
Dish (DISH)
If the knuckle radius is 0 then the dish is represented as a segment of a sphere. If the knuckle radius is
greater than 0 then the dish is represented as a partial ellipsoid, generally used to represent a
torispherical end to a vessel.
Only an Xtshear and Ybshear are shown in this example, however, Xtshear, Ytshear, Xbshear and
Ybshear may be set in any combination to obtain the required results. The values for these attributes
may be +ve or –ve.
Extrusion (EXTR)
A solid of revolution is a 2D shape, defined by a series of vertices at each change in direction, rotated
through a specified angle around a specified rotation axis. The primitive consists of three element
types, i.e. REVO, LOOP and VERTs.
Nozzle (NOZZ)
Although a nozzle is classed as a primitive, it is unlike the other primitives in that its geometry is determined
in Paragon as part of a catalogue component. Nozzles of different types and geometry may be constructed
in Paragon to suit the requirements of the Piping Specification.
The specific nozzle type is referenced from Paragon using the Spref (Specification Reference) attribute.
Height Height between nozzle face and end, i.e. from P1 to P2.