TM-1865 AVEVA Everything3D (2.1) Supports Administration

Training Title of manual (version)
Guide
AVEVA Everything3D™ (2.1)
Supports Administration TM-1865
© Copyright 2015. 2 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
Revision Log
Date Revision Description Author Reviewed Approved
21/09/2015 0.1 Issued for Review BT

17/11/2015 0.2 Reviewed BT ST
26/11/2015 1.0 Approved for Training AVEVA E3D™ (2.1) BT ST KB
05/05/2016 1.1 Revised BT
16/05/2016 1.2 Reviewed BT ST
17/05/2016 2.0 Approved for Training AVEVA E3D™ (2.1) BT ST KB
21/09/2016 2.1 Revised ST
09/01/2017 2.2 Reviewed ST BT
23/06/2017 2.3 Trunnion Notes 7.2.13 updated ST
06/09/2017 2.4 3rd Party Interface Support Added BT
06/10/2017 2.5 Isodraft SKey notes added BT
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.
Visit our website at http://www.aveva.com
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.
@AVEVA Solutions Limited 2015
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.

CONTENTS
1 Introduction .......................................................................................................................... 11
1.1 About this Guide ............................................................................................................................. 11
1.2 Overview of the AVEVA E3D™ Supports Application ................................................................ 11
1.3 Administrator’s Role....................................................................................................................... 13
1.4 Support Catalogues and Specifications ....................................................................................... 13
1.5 Aim ................................................................................................................................................... 13
1.6 Objectives ........................................................................................................................................ 13
1.7 Prerequisites ................................................................................................................................... 14
1.8 Course Structure ............................................................................................................................. 14
1.9 Using this guide .............................................................................................................................. 14
2 AVEVA E3D™ Supports Projects and Databases .............................................................. 15
2.1 Supplied Projects ............................................................................................................................ 15
2.2 Creating a Project ........................................................................................................................... 16
2.3 AVEVA E3D™ Supports Default files ............................................................................................ 18
2.4 Typical Project Configuration ........................................................................................................ 18
2.5 Database Requirements ................................................................................................................. 19
2.6 Including Foreign Databases (Reference Only) ........................................................................... 20
2.7 Including Foreign Databases (Reference Only) ........................................................................... 20
2.8 Copying Foreign Databases (Reference Only) ............................................................................ 21
2.9 Add database to MDB (Reference Only) ....................................................................................... 23
2.10 Testing AVEVA E3D™ Supports in Model ................................................................................ 24
Exercise 1 – Project Setup ......................................................................................................... 25
3 Configuration Checklist ....................................................................................................... 27
3.1 Project Configuration ..................................................................................................................... 27
4 AVEVA E3D™ Supports Administration Forms and Menus .............................................. 29
4.1 Enter AVEVA Catalogue Module ................................................................................................... 29
Exercise 2 – AVEVA E3D™ Supports Administration Forms and Menus ............................... 30
5 Checking the Supports Application Defaults ..................................................................... 31
Exercise 3 - Check Supports Application Defaults .................................................................. 32
6 AVEVA E3D™ Supports Active Control Form .................................................................... 33
6.1 Displaying the AVEVA E3D™ Supports Active Standards Form ............................................... 33
6.2 Support Types ................................................................................................................................. 33
6.3 Activating and Deactivating Support Types ................................................................................ 34
6.4 Activate and Deactivate individual Bores .................................................................................... 36
6.5 Full or Brief Configuration Mode ................................................................................................... 36
Exercise 4 – AVEVA E3D™ Supports Active Control ............................................................... 38
7 AVEVA E3D™ Supports Application Defaults.................................................................... 40
7.1 Supports Admin Data Options (1) Tab.......................................................................................... 40
7.1.1 Max. Pipe Slope (MDSSUPPMS) .............................................................................................. 41
7.1.2 Steelwork Overlap (MDSSUPPOV) ........................................................................................... 41
7.1.3 Max. Packing Dist (MDSPACKDI) ............................................................................................. 42
7.1.4 Max. Packing Overlap (MDSPACKMO) .................................................................................... 42
7.1.5 Max Trunnion Length ................................................................................................................. 42
7.1.6 Pipe Clearance (MDSSUPPCL) ................................................................................................ 42
7.1.7 Max. Horizontal Angle (MDSMAXHANG) .................................................................................. 43
7.1.8 Min. Rod Length (MDSMINHANG) ............................................................................................ 44
7.1.9 Max. Pivot Angle (MDSMAXPIVA) ............................................................................................ 44
7.1.10 Project Hanger Interfaces (MDSHANGIF) ................................................................................. 44
7.1.11 User Warning Angle (MDSPIVWARN) ...................................................................................... 44
7.1.12 Joint Offset (MDSOFFSET) ....................................................................................................... 45
7.1.13 Automatic Pads.......................................................................................................................... 45

7.2 Supports Admin Data Options (2) Tab.......................................................................................... 46

7.2.1 Flange Gapping Value (MDSFLAGAP) ..................................................................................... 46
7.2.2 Alternate Representation Level (MDSLEVCHANGE) ............................................................... 46
7.2.3 Transport Prefix (MDSTRANPREF) and Transport Text (MDSTRANISO) ............................... 46
7.2.4 Number of Characters in Trunnion Support Codes Standard (MDSTRUNCODE) ................... 47
7.2.5 Unit of Weight on Drawings (MDSWEITAG) ............................................................................. 47
7.2.6 Special Support Number ........................................................................................................... 47
7.2.7 Weight Unit (MDSWEIUNIT) ..................................................................................................... 47
7.2.8 Dataset Code Conversion Factor (MPU) ................................................................................... 48
7.2.9 Unique Support Names ............................................................................................................. 48
7.2.10 Special Support Number Unique ............................................................................................... 48
7.2.11 Special Support Number Checker ............................................................................................. 48
7.2.12 Display Orientation in Support Tag on Isometric (MDSORINOT) ............................................. 48
7.2.13 Notes Appear on Isometric Drawings (MDSTRUNNOTES) ...................................................... 49
7.2.14 Display Bracing Members in Isometric MTO (MDSFRAMEBRACING) .................................... 49
7.3 Admin Data Miscellaneous Tab ..................................................................................................... 49
7.4 Zone ID ............................................................................................................................................. 49
7.5 Support Application Defaults ........................................................................................................ 50
Exercise 5 – Changing the AVEVA E3D™ Supports Defaults ................................................. 52
8 AVEVA E3D™ Supports Ancillary Data Form .................................................................... 54
8.1 Standard Tab .................................................................................................................................... 55
8.1.1 Support Standard....................................................................................................................... 55
8.1.2 Standard Replacement Name ................................................................................................... 55
8.1.3 Description ................................................................................................................................. 55
8.1.4 Support Class ............................................................................................................................ 56
8.1.5 Active ......................................................................................................................................... 56
8.1.6 Vendor Reference...................................................................................................................... 57
8.1.7 Pipe Specification Material Code ............................................................................................... 57
8.1.8 PROPCON - MDS Ancillary Material ......................................................................................... 57
8.1.9 SKey .......................................................................................................................................... 57
8.1.10 Skey Override ............................................................................................................................ 57
8.1.11 Isometric MTOC Flag ................................................................................................................ 57
8.1.12 Bore ........................................................................................................................................... 58
8.1.13 Pipe Specification Material Code ............................................................................................... 58
8.1.14 PROPCON - MDS Ancillary Material ......................................................................................... 58
8.1.15 Framework Clearance Option, Closed End Clearance, Open End Clearance ......................... 58
8.2 Active/Shop Flag Tab ..................................................................................................................... 60
8.2.1 Active ......................................................................................................................................... 61
8.2.2 Shop Flag .................................................................................................................................. 61
8.3 Parameters Tab ............................................................................................................................... 61
8.4 Size Tab ........................................................................................................................................... 62
8.5 Parameter Tab ................................................................................................................................. 63
8.6 Alt Expression Tab ......................................................................................................................... 64
8.7 User Des Pars Tab .......................................................................................................................... 64
8.7.1 Adding User-editable Design Parameters ................................................................................. 65
8.7.2 Deleting User-editable Design Parameters ............................................................................... 66
8.8 Support Compatibility .................................................................................................................... 66
8.9 Selection Configuration ................................................................................................................. 67
8.9.1 Primary Component ................................................................................................................... 67
8.9.2 Available on Framework ............................................................................................................ 67
8.9.3 Only Available on Framework .................................................................................................... 68
8.9.4 Minimum Elevation .................................................................................................................... 68
8.9.5 Pipe Direction ............................................................................................................................ 68
8.9.6 Component Type ....................................................................................................................... 68
8.9.7 Head Components Allowed ....................................................................................................... 68
8.9.8 Trunnion Types Allowed On ...................................................................................................... 68
Exercise 6 – AVEVA E3D™ Supports Ancillary Defaults ......................................................... 69
9 AVEVA E3D™ Supports Hanger Data Form ....................................................................... 70

9.1 9.1 Standard Tab ......................................................................................................................... 71

9.1.3 Description ................................................................................................................................. 72
9.1.4 Hanger Configuration ................................................................................................................ 72
9.1.5 Active ......................................................................................................................................... 73
9.1.6 SKey .......................................................................................................................................... 73
9.1.7 SKey Override ........................................................................................................................... 73
9.1.8 Support Function ....................................................................................................................... 73
9.2 Soft Types ........................................................................................................................................ 74
9.3 Bottom Associated Support Standards Tab ................................................................................ 75
9.4 Allowable Rod Sizes ....................................................................................................................... 76
10 Hangers Design Templates .............................................................................................. 78
10.1 Data sheets .................................................................................................................................. 78
10.2 Configuration of the Hanger’s Design Templates ................................................................... 78
11 AVEVA E3D™ Supports- Lighting Support Defaults ...................................................... 80
11.1 Lighting Form .............................................................................................................................. 80
11.1.1 Support: Type ............................................................................................................................ 80
11.1.2 Support: Code............................................................................................................................ 81
11.1.3 Supports: Origin ......................................................................................................................... 81
11.1.4 Support: Replacement Type ...................................................................................................... 81
11.1.5 Support: Max. Height ................................................................................................................. 81
11.1.6 Support: Min. Height .................................................................................................................. 81
11.1.7 Support: Bracket Limit ............................................................................................................... 81
11.1.8 Lighting: Type ............................................................................................................................ 81
11.1.9 Lighting: Filter ............................................................................................................................ 81
11.1.10 Lighting: Origin ....................................................................................................................... 81
11.1.11 Lighting: Y Direction ............................................................................................................... 81
12 AVEVA E3D™ Supports Structure Data Form ................................................................ 82
12.1 Standard Tab ............................................................................................................................... 83
12.1.3 Description ................................................................................................................................. 83
12.1.4 Active ......................................................................................................................................... 83
12.1.5 Framework MTOC Flag ............................................................................................................. 84
12.1.6 SKey .......................................................................................................................................... 84
12.1.7 SKey Override ........................................................................................................................... 84
12.2 Framework Selections/Restrictions Tab ................................................................................... 84
12.3 Framework Codes ....................................................................................................................... 85
12.3.1 Edit Selected Row ..................................................................................................................... 86
12.3.2 Edit Column ............................................................................................................................... 86
Exercise 7 – Supports Structure Data ....................................................................................... 87
13 Framework Template Administration .............................................................................. 88
13.1 Template Modification Rules ..................................................................................................... 89
13.2 Framework Setup ........................................................................................................................ 90
13.2.1 Replacing the Default Steelwork GENSEC Size ....................................................................... 90
13.2.2 Modifying the Design Template’s Minimum/Maximum Lengths ................................................ 96
13.2.3 Creating Template Internal Joints.............................................................................................. 96
13.2.4 Modifying the Appearance of Joints and Fittings on the Supports ADP Drawing ..................... 97
13.3 Framework Naming Conventions .............................................................................................. 97
13.4 Available Templates .................................................................................................................... 98
13.4.1 Extending the Number of Steelwork Framework Types Available ............................................ 98
13.5 Template Options ........................................................................................................................ 98
13.5.1 Availability of Cross Bars ........................................................................................................... 98
13.5.2 Creation of Standard in the Horizontal or Vertical Plane ........................................................... 98
13.5.3 Maximum Gensec Lengths ........................................................................................................ 98
13.5.4 Cross Bar Overlap Override ...................................................................................................... 98
13.5.5 Vertical Section Overlap ............................................................................................................ 99

13.5.6 Maximum Allowable Bore Sizes ................................................................................................ 99

13.6 Automatic Steelwork Orientation ............................................................................................ 100
13.7 Project Special Templates ........................................................................................................ 100
13.7.1 Storage Areas .......................................................................................................................... 101
13.7.2 Filter Settings at a Piping or Tray Project Special Template ................................................... 101
13.7.3 Filter and Build Settings at an HVAC Project Special Template ............................................. 101
Exercise 8 – Steelwork Section Size ....................................................................................... 106
14 AVEVA E3D™ Supports Trunnion Defaults Form......................................................... 107
14.1 Standard Tab ............................................................................................................................. 108
14.1.1 Support Standard..................................................................................................................... 108
14.1.2 Standard Replacement Name ................................................................................................. 108
14.1.3 Description ............................................................................................................................... 108
14.1.4 Active ....................................................................................................................................... 108
14.1.5 Vendor Reference.................................................................................................................... 108
14.1.6 Elevation Restriction ................................................................................................................ 109
14.1.7 Pipe Specification Material Code ............................................................................................. 109
14.1.8 SKey ........................................................................................................................................ 109
14.1.9 SKey Override ......................................................................................................................... 109
14.1.10 Support function ................................................................................................................... 109
14.1.11 Isometric MTOC Flag ........................................................................................................... 109
14.2 Active/Shop Flag Tab ................................................................................................................ 110
14.2.1 Active ....................................................................................................................................... 110
14.2.2 Shop Flag ................................................................................................................................ 110
14.3 User Des Pars Tab .................................................................................................................... 110
14.4 Component Selection Tab ........................................................................................................ 111
14.4.1 Trunnion Sizes and Bore ......................................................................................................... 111
14.4.2 Trunnion Base Plate ................................................................................................................ 112
14.4.3 Trunnion Sizes ......................................................................................................................... 112
Exercise 9 - Trunnions ............................................................................................................. 113
15 Location Plan, ABA Grid Data ........................................................................................ 115
15.1 Gridline Tag Patterns ................................................................................................................ 116
15.2 Support Datum Origin Coordinates......................................................................................... 116
15.3 List of Valid Grids...................................................................................................................... 116
16 Ancillary Selection Criteria............................................................................................. 117
16.1 Temperature Check ................................................................................................................... 118
16.1.1 User Defined Criteria ............................................................................................................... 118
16.1.2 User Defined Functions ........................................................................................................... 119
16.1.3 User Defined Check Function - Creation and Usage Rules .................................................... 119
16.1.4 User Defined Check Function - Example Listing ..................................................................... 119
Exercise 10 - Ancillary Selection ............................................................................................. 121
17 Compensation Plates...................................................................................................... 123
17.1 Compensation Options ............................................................................................................. 123
17.1.1 Gap .......................................................................................................................................... 124
17.1.2 Plate Thickness ....................................................................................................................... 124
17.1.3 Rounding ................................................................................................................................. 124
17.2 Compensation Sizes ................................................................................................................. 125
17.3 Compensation Plate Material ................................................................................................... 126
18 User Defined Ancillary .................................................................................................... 129
18.1 Geometry Sets ........................................................................................................................... 130
18.1.1 AT500 to AT700, BT500 to BT700, LT500 to LT700............................................................... 130
18.1.2 AN500 to AN569 Anchor for Shoes ......................................................................................... 131
18.1.3 AN570 to AN639 Anchor for Pipes .......................................................................................... 133
18.1.4 GT500 to GT569 Guide for Shoes........................................................................................... 134
18.1.5 GT570 to GT639 Guide for Pipes ............................................................................................ 135
18.1.6 ST500 to ST569 Stop for Shoes.............................................................................................. 136
18.1.7 ST570 to ST639 Stop for Pipes ............................................................................................... 137

18.1.8 AN640 to AN700 Anchor for Trunnions ................................................................................... 138

18.1.9 ST640 to ST700 Stop for Trunnions ........................................................................................ 139
18.1.10 GT640 to GT700 Guide for Trunnions ................................................................................. 140
18.2 Point Sets ................................................................................................................................... 141
18.3 Data Sets .................................................................................................................................... 142
18.4 Project Catalogue for User Defined Ancillaries ..................................................................... 142
18.5 Modifying the User Defined Ancillary Standard ..................................................................... 144
18.6 Example User Defined High Pressure Support. ..................................................................... 144
18.6.1 Modifying the support geometry .............................................................................................. 144
18.6.2 User Define Support Activation ............................................................................................... 151
18.6.3 Support Compatibility .............................................................................................................. 152
18.6.4 Selection Configuration ........................................................................................................... 153
18.6.5 User interface Configuration .................................................................................................... 154
18.6.6 Support Configuration xml file ................................................................................................. 154
18.6.7 Support Graphics ..................................................................................................................... 155
18.6.8 Dimension Control Designer .................................................................................................... 156
18.6.9 Testing the User Defined Support in Design ........................................................................... 158
18.7 Creating Secondary User Defined Supports .......................................................................... 159
18.7.1 Modify AT502 Geometry.......................................................................................................... 159
18.7.2 User Define Support Activation (AT502) ................................................................................. 160
18.7.3 User Define Design Parameters (AT502) ................................................................................ 162
18.7.4 Support Compatibility .............................................................................................................. 164
18.7.5 Selection Configuration ........................................................................................................... 164
18.7.6 Adding Support Compatabilty to AT501 .................................................................................. 165
18.7.7 Support Graphics ..................................................................................................................... 166
18.7.8 Dimension Control Designer .................................................................................................... 166
18.8 Configuring the controls on the Support Editor Form .......................................................... 169
18.9 Testing the User Defined Support in Design .......................................................................... 170
Exercise 11 – User Defined Support Ancillaries ..................................................................... 172
19 Supports- Auto Naming .................................................................................................. 173
19.1 Usage and Auto Naming File Selection .................................................................................. 173
19.2 Creating a new Naming File ..................................................................................................... 174
19.3 Testing the Auto Naming file. .................................................................................................. 174
19.3.1 Creating a new support Zone .................................................................................................. 174
19.3.2 Setting Default Creation Zone ................................................................................................. 175
19.3.3 Setting Auto Naming File to a Zone......................................................................................... 176
Exercise 12 –Supports Autonaming ........................................................................................ 177
20 Support Plot Files ........................................................................................................... 179
21 Supports Drawing Production ....................................................................................... 181
21.1 DRA-MDS-ABADEFAULTS ....................................................................................................... 181
21.1.1 Specifying the ABA Defaults File ............................................................................................. 181
21.1.2 Create a Support Drawing ....................................................................................................... 183
21.1.3 ABA Defaults File..................................................................................................................... 185
21.2 AVEVA E3D™ Supports Specific Sheet Template Libraries ................................................ 187
21.2.1 View Element ........................................................................................................................... 187
21.3 MDS Specific Tasks .................................................................................................................. 187
21.3.1 Sheet Tasks ............................................................................................................................. 188
21.3.2 View tasks................................................................................................................................ 189
21.4 Creating a Function – Worked Example ................................................................................. 192
21.4.1 Simple Macro ........................................................................................................................... 192
21.4.2 Handling Units in Macros ......................................................................................................... 193
21.5 Creating a Function................................................................................................................... 194
21.5.1 PML Library ............................................................................................................................. 194
21.5.2 Testing a Function ................................................................................................................... 195
21.6 Creating a Task.......................................................................................................................... 195
21.7 Adding a Task to a Drawing Sheet. ......................................................................................... 196
Exercise 13 AVEVA E3D™ Supports Drawing Production .................................................... 198

22 3rd Party Supports Applications ..................................................................................... 199

22.1 Witch Hanger Interface ............................................................................................................. 199
22.2 Lisega Licad Interface .............................................................................................................. 199
22.3 3rd Party Interface Configuration Files .................................................................................... 199
22.3.1 HangerInterfaceConfiguration.xml ........................................................................................... 199
22.3.2 3rd Party Interface Communication Folder ............................................................................... 199
22.4 3rd Party Interface Settings ....................................................................................................... 200
22.5 3rd Party Databases ................................................................................................................... 201
22.6 3rd Party Interface Load Errors ................................................................................................. 201
22.6.1 Typical Witch Hanger Error ..................................................................................................... 201
22.6.2 Typical Licad Error ................................................................................................................... 201

CHAPTER 1
1 Introduction
About this Guide
This manual is designed to give the Support Administrator guidance on project setup and setting up and
configuring the framework templates for the AVEVA Everything3D™ (AVEVA E3D™) Supports application.
Guidance is also provided on how to produce drawings from the model using the Area Based Automatic
Drawing Production (ADP) application.
Overview of the AVEVA E3D™ Supports Application
The AVEVA E3D™ Support application allows the user to create standard supports for the pipe work, cable
racks, and HVAC model objects. The application is highly interactive, enabling the user to design supports
with the minimum of effort. The Support application is also highly configurable allowing the administrator to
define project related defaults, to control the design of supports, and to determine the range and types of
ancillary support components that can be used on the project.
The standard supports in this application are designed using structural GENSECs and are template driven,
so in essence the template reflects the Standard. A default set of structural templates based on British,
AISC and DIN Standard Steelwork GENSECs is supplied with the application. All of the supplied templates
may be configured by the company or project to adopt any relevant national or regional standard for
steelwork GENSECs.
Ancillaries are the element that are normally attached to the supported object such as a U-bolt, Bolt-on
Shoe, Anchor, and Slip-unit. The ancillaries associated with the template reflect those available with, or,
suitable for, the Standard. If the available templates do not reflect the requirement, a request may be made
via the administrator to work with AVEVA Solutions plc to get the requirement designated as a new Standard
(and hence a new template) or a Special or Project Special could be created by the Designer.
Ancillaries for cable tray and HVAC, sometimes referred to as fixings, are deemed to be the responsibility
of the relevant contractor and are not dealt with in this application.
The AVEVA E3D™ Support development has been completed after consultation with various customers to
allow for the various workflows for support design common across the industries we serve inclusive of multi-
location working under AVEVA Global.
AVEVA E3D™ Supports have been the subject of several studies to address usability and performance of
the application particularly at start-up and ancillary selection and to give the Designers greater flexibility for
configuration of support standards.

The AVEVA E3D™ Supports application uses a workflow that will NOT require write access to the Piping,
Cable Tray, HVAC or main Steelwork elements. The following illustration shows how a Support Ancillary
points at a Branch or piping component and a Pseudo attribute is used on the piping component or branch
to point to the Support, thus requiring no write access on the piping hierarchy.
Databases Design Consequences
• The SUPPO element does not appear in the member list for the branch, a Support Explorer is
included to help the Designer to Navigate, Browse, Run the Health check, Modify, Delete and
Display Supports.
• Isodraft has been enhanced to take into account the SUPP elements.
• Moving pipe (By, Drag etc.) will not move supports.
• Data Consistency Check has been enhanced to

check SUPP elements in the same way that ATTAs
are checked.
For example, if the SUPP element is not aligned with

the pipe, the Data Consistency Check displays an
error message

Advantage of Design
• No write access to branch or components required
• Support is contained under one SUPPO element
• New engineering related Elements created. For example, Trunnion, Ancillary etc…
• Better for deleting, adding to drawlist (model and draw), reporting, flushing/issuing etc.
• SUPPO is the primary element. (i.e. fewer elements claimed).
• All additive to DB, no upgrade required
Administrator’s Role
The administrator is responsible for initial setup of the defaults associated with the Support and setup of
the structural steel sizes associated with the frame maker templates. The Support application is supplied
with a set of framework templates, which the administrator must modify to suit the specific requirements of
the project.
Support Catalogues and Specifications
The Support application is supplied with a catalogue and specification. The range of bore and components
in the catalogue are fixed and should be adequate for all projects. The catalogue supplied and associated
specification must not be modified by the administrator or any other user.
Aim
At the end of this Training Course the Support Administrator will have enough knowledge and understanding
to be able to implement AVEVA E3D™ Supports on an AVEVA E3D™ Project.
Objectives
• Configure an AVEVA E3D™ project for use with AVEVA E3D™ Supports.
• Understand the Project Catalogue requirements for AVEVA E3D™ Supports.
• Understand AVEVA E3D™ Supports System Defaults.
• Understand AVEVA E3D™ Supports Autonaming.
• Understand Ancillary Defaults.
• Understand Hanger Data.
• Understand Trunnion Defaults.
• Understand Structural Defaults.
• Understand Framework Template Administration.
• Understand User Defined Ancillaries.
• Understand how to customise AVEVA E3D™ Supports Automatic Drawing Production.

Prerequisites
All Trainees should have a good working knowledge of AVEVA E3D™ and must have attended the AVEVA
E3D™ Supports User Training course.
Course Structure
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.
Using this guide
Certain text styles are used to indicate special situations throughout this document summarised below.
Menu pull downs and button press actions are indicated by bold dark turquoise text.
Information the user has to key-in will be in bold red text.
Where additional information is presented, or reference is made to other documentation the following
annotation will be used:
 Additional information
 Refer to other documentation
System prompts will be bold, italicised, and presented in inverted commas i.e. 'Choose function'.
Example files or inputs will be in the courier new font.

CHAPTER 2
2 AVEVA E3D™ Supports Projects and Databases
The AVEVA E3D™ training material uses the Training project (TRA) which has been preconfigured for
AVEVA E3D™ Supports.
This chapter describes how the AVEVA E3D™ Supports supplied databases can be included or copied into
the current project so that they can be customised. This will also help when adding AVEVA E3D™ Supports
to other projects.
Supplied Projects
The AVEVA E3D™ Supports application is supplied to all users of AVEVA E3D™ Supports with several
projects, along with any client-specific project.
AVEVA supplied Catalogue (ACP) and Sample (APS) projects include all
Projects ACP & APS: the databases required for standard AVEVA E3D™ Supports. Typically,
the AVEVA E3D™ Supports Catalogue, Specification, Steelwork
Templates and user defined ancillaries. These projects are supplied as part
of the main AVEVA Plant software.
Project CCA: Client Catalogue A (only supplied where clients have additional
development completed by AVEVA)
Projects
CPL Carpenter and Patterson If a manufacturer’s interface is used for hanger design, then the
PSL Pipe Support Ltd /MDS/HANGERS database is not used, and one of these
LIS Lisega manufacturer’s projects can be selected instead.
The Training Project has been created using the

Training Setup which can be accessed in
AVEVA Administration via Utilities > Training
Setup.. and selecting the AVEVA E3D™
Supports Tab.
In the Training project no third party interfaces

are selected.
 The use of third party Interfaced is not

covered on the Course.
 The AVEVA E3D™ Supports Customisation Guide accessed via the Help pull-down gives full details of
all Projects and databases.

Creating a Project
 It is assumed that the Training Project has been setup prior to the Training Course by the Trainer.
The Training Project is created using the Project Creation Wizard which can be found in AVEVA
Administration.
Select Start > All Programs > AVEVA > Manage > AVEVA Administration
Select New Project
Project Training
Code TRA
Select Create
 The project is being created in the Default project location this can be changed using the Brow… button.
Select OK and Close the Project Creation Wizard

Project: Training (TRA)
Username: SYSTEM
Password: XXXXXX
MDB: left unset
Click the Admin tile.
Select Utilities > Training Setup…
Number of Designers 1
Pick Create Project Data
Pick OK and Close the Training Setup Form

AVEVA E3D™ Supports Default files
The TRADFLTS directory must contain the following AVEVA E3D™ Supports files.
DES-SUPP-NAMES - Typical AVEVA E3D™ Supports Autonaming File
DRA-MDS-ABA-DEFAULTS - AB ADP Defaults File
MdsUserData.pmldat - MDS User Customisation Macro
These default files need to be present in the ACPDFLTS directory that was installed with AVEVA E3D™
Supports as shown below: -
Running the training set up with the checked

Copy Supports Default files to Current
Project check box should have already copied
these files to the correct location
%TRADFLTS%.
Typical Project Configuration
Supports is supplied with several ancillary standards typically Pipe Support Ltd and Grinnell and is also
capable of being linked to third party vendors like Carpenter and Paterson Ltd and Lisega.
It is supplied with three steelwork standards (BS, DIN and AISC) for building frameworks.

For the purposes of the Training the Training Project (TRA) was configured to use AVEVA E3D™ Supports
with British Steel (BS) and Hangers from Pipe Support Ltd. (PSL).
Database Requirements
The databases used by the Supports application are split into two classes:
• AVEVA controlled reference libraries. These databases are maintained by AVEVA and generally
regarded as being non-user definable. These databases should be included in customer projects as
• foreign imports from the AVEVA ACP project.
• User definable template and configuration databases. These databases contain client/project specific
customised supports data. Basic versions of these databases should initially be copied into a client
project from the AVEVA APS project and then modified to suit. User is then free to include the
• customised versions of these databases either in a local project or by foreign project reference
Databases to be included from ACP project:
MDS/CATA Catalogues and specifications
MDS/PROP Properties database
MASTER/MDSDICT MDS LEXICON database
Databases to be copied from APS project:

MDS/MDSAPPDEFAULTS Application Defaults database
MDS/WELDS Weld templates DATASETS database
MDS/DRAFT Draw Templates
Framework Templates:
MDS/DESITMPL-BS Framework templates for BS steel
MDS/DESITMPL-BS-ORI Orientated Framework templates for BS Steel
Hanger Templates:
MDS/DESITMPL-PSL Hanger templates for Pipe Support Ltd
Special Templates

MDS/DESI-SPECIAL-TMPL-BS Project special framework templates for BS Steel
User Defined Ancillary Database
MDU/CATA MDS Catalogue for user defined Ancillaries
Including Foreign Databases (Reference Only)

The following section was completed automatically by the AVEVA E3D™ Supports Training Setup form but
is included here for reference purposes should the need arise for this to be done manually.
Select Start > All Programs > AVEVA > Manage > AVEVA Administration
Username: SYSTEM
Password: XXXXXX
MDB: left unset
Click the Admin tile.
Including Foreign Databases (Reference Only)
Using the Admin Elements

form
Select Databases and

Extracts
Ensure the following

databases are included:
MDS/CATA
Click the Include button.

Select ProjACP from the Foreign Projects

section.
Username SYSTEM
Password XXXXXX
Name Filter MDS
Select MDS/CATA
Click the Apply button.
The user may be prompted to create the relevant

team, click the Yes button.
Repeat the above process to include the following databases from the ProjACP.
• MDS/PROP
• MASTER/MDSDICT
Copying Foreign Databases (Reference Only)
The following section was completed automatically by the AVEVA E3D™ Supports Training Setup form but
is included here for reference purposes should the need arise for this to be done manually.
Using the Admin Elements

form
Select Databases &

Extracts
Click the Copy Foreign

button.

Select ProjAPS from the Foreign Project

section.
Username SYSTEM
Password XXXXXX
Name Filter MDS
Select MDS/MDSAPPDEFAULTS
Team MDS
Database Name MDSAPPDEFAULTS
Repeat the process for the following

databases:
• MDS/WELDS
• MDS/DESITMPL-PSL
• MDS/DESI-SPECIAL-TMPL-BS
• MDS/DESITMPL-BS
• MDS/DESITMPL-BS-ORI
• MDS/DRAFT
• MDU/CATA
 To be able to copy MDU/CATA database,

team MDU needs to be created.

Add database to MDB (Reference Only)
The new database will need to be added to all the MDBs, in this case A-SUPPORTS
Select MDBs from the Admin

Elements form
Select A-SUPPORTS
Click the Modify button.
Move the following AVEVA E3D™ Supports databases into the current MDB A-SUPPORTS using the down
arrow.
MDS/PROP
MASTER/MDSDICT
MDS/MDSAPPDEFAULTS
MDS/WELDS
MDS/DESITMPL-PSL
MDS/DESI-SPECIAL-TMPL-
BS
MDS/DESITMPL-BS
MDS/DESITMPL-BS-ORI
MDS/DRAFT
MDU/CATA
Select Admin > Exit.

Testing AVEVA E3D™ Supports in Model
Enter AVEVA E3D as a Support Designer using the details below, for example:
Start > All Programs > AVEVA > Design > AVEVA Everything3D
Username: A.SUPPORTMAN
Password: A
MDB: A-SUPPORTS
Click the Model Tile.
Load the Support toolbar by selecting SUPPORTS from the drop

down menu.
By default a Support zone with a Purp set to SUPP must exist in

the database. If a suitable zone cannot be found an error message
is displayed and AVEVA E3D Supports loading is aborted.
 This Zone must not contain any of the old style MDS type
Supports.

Exercise 1 – Project Setup
1. Using the above example create a new project called Training (TRA), use the Training Setup in
Admin to create the Training Teams, Users, Databases and MDBs, add the AVEVA E3D™ Supports
databases to the Project.
2. Test that the AVEVA E3D™ Supports application can be accessed in Model.
 If this exercise is being used prior to AVEVA E3D™ Supports User Training the project should be
turned into Brief Mode as described in Chapter 6.
1.

This page is intentionally left blank.

CHAPTER 3
3 Configuration Checklist
Project Configuration
The table below contains all the steps an administrator needs to cover when attempting to configure the
AVEVA E3D™ Supports application for a project’s requirements. Each section is covered in more detail as
the training progresses.
1 From within the Paragon application, select Application Defaults button, from the Configuration
group to display the Supports Admin Data form.
Modify the Model application defaults e.g. Clearance, Overlap, Pipe slope etc from the Application
Tolerances section.
Modify the support zone identification settings from the Zone ID section of the Miscellaneous tab.
2 From within the Paragon application, select Active Standards button, from the Configuration
group to display the Supports Active Standards form:
Deactivate configurations that are not used on the Project (optional), i.e. Support Type e.g. FT03
not needed by project.
3 From within the Paragon application, select Ancillary button, from the Standard Defaults group to
display the Supports Ancillary Data form.
Standard Replacement Name and Description for each support is displayed on the top of the form
Complete all Ancillary specific setting, i.e. dimensions (design parameters), material, minimum and
maximum values required by the project.
4 Modify the project specification to match settings used in step 3. For example the pipe class ‘CS’ for
carbon steel to match the :MDSPipeMat UDA at specification level in the project.
5 From within the Paragon application, select Hanger Template button from the Standard Defaults
group of the SUPPORTS Tab to display the AVEVA E3D™ Supports Hanger Data form:
Perform similar actions to step 3 and complete all Hanger specific settings.
6 Hanger Design Templates - Check that the Template represents the configurations defined in the
Supports Admin Data and Supports Hanger Data forms. Not required if using a AVEVA E3D™
Supports Hanger Manufacturer Interface.
8 From within the Paragon application, select the Structure button to display the Supports Structure
Data form:
Perform similar actions to step 3 and complete all Structure specific settings.
9 Structural Design Templates – Configure the templates to suit the project or company standards.
10 From within the Paragon application, select Trunnion button to display the Supports Trunnion
Data form:
Perform similar actions to step 3 and complete all Trunnion specific settings.
11 User Defined Ancillary - Modify the Category for the types required.
12 Create/Modify DES-SUPP-NAMES* in the project default directory for Auto naming files.

13 Drawing Backing Sheets - To be modified / created to suit project requirements.
14 Configure AVEVA E3D™ Supports Drawings.

CHAPTER 4
4 AVEVA E3D™ Supports Administration Forms and Menus
Supports Administration Forms are accessed via AVEVA Catalogue
Enter AVEVA Catalogue Module
Login to AVEVA Catalogue as a Support Designer using the details provided by the Trainer, for example:
Start > All Programs > AVEVA > Manage > AVEVA Catalogue
Username: A.SUPPORTADMIN
Password: A
MDB: A-SUPPORTS
Module: Paragon
Click the Paragon Tile.
 A.SUPPORTADMIN is a free user,

the user name will need to be
typed in full into the login form.
Start the Support application by selecting Supports from the drop down menu

Exercise 2 – AVEVA E3D™ Supports Administration Forms and Menus
Using the above example access the AVEVA E3D™ Supports Admin forms and menus in AVEVA
Catalogue.

CHAPTER 5
5 Checking the Supports Application Defaults
The “Check Support Application Defaults” tool is available in the AVEVA Catalogue from the Tools Group
of the SUPPORTS Tab. It should be used prior to doing any customisation and following any software updated.
It is used to validate the current version of AVEVA E3D Supports and also to add any new features or attributes
and can also be used to upgrade a project to Supports from an old style MDS project.
With this form the user is able to check their AVEVA E3D™
Supports application defaults database against the current AVEVA
E3D™ Supports reference project values.
Select the Check Defaults button.
An example of this is shown below.
 This may take some time; a progress bar is displayed on the bottom right of the screen.
The check application defaults scan has identified that an
update is required to the shop flags
Select Update Defaults.
From time to time it may be necessary to update existing standards to either fix problems or provide new
functionality. Such updates will be delivered by this mechanism.

Exercise 3 - Check Supports Application Defaults
Check the Supports Application Defaults as described above

CHAPTER 6
6 AVEVA E3D™ Supports Active Control Form
AVEVA E3D™ Supports is supplied with a comprehensive set of Pipe Supports, however this extensive range
may not be required on all projects. The AVEVA E3D™ Supports Active Control form can be used to select
the support types that will be available on the project.
 This form enhances the existing functionality that is also available from some of the other forms. The
changes that are carried out on this form are reflected on the alternative forms available.
Displaying the AVEVA E3D™ Supports Active Standards Form
From the Configuration Group on the SUPPORTS Tab, select Active Standards
The supports shown in Green will be available on the Project whilst those shown in Red will be
unavailable.
Support Types
Each of the tabs on the top of the Supports Active Standards represents the various Support Types.

Select the Key to Support Types link label as shown.
The resulting key will facilitate navigation of the AVEVA E3D™ Supports
Active Control form.
Activating and Deactivating Support Types
Select the Supports to be activated or deactivated.

Click the Button Activate or Deactivate button the followed by Apply button.

Activate and Deactivate individual Bores
Similarly individual bores of a support can be activated or deactivated. The Apply button is used to confirm
any changes made.
Full or Brief Configuration Mode

Full mode will activate all the Pipe Supports available in the project whilst Brief will create a minimal set
of supports suitable for Training and Demonstration. Currently this demonstration set is not configurable.
Select Brief
Click the Yes button.
The Pipe Supports available are reduced typically as shown on the BT (U-bolt) tab:


Exercise 4 – AVEVA E3D™ Supports Active Control
1. Change the Training Project into Brief mode as described above and investigate activating some
supports.
2. Activate Trunnion XTT17 as it is required for Vessel Supports.
3. Activate AT29A and AT29B which are the reinforcing Pads on Trunnions.
4. Activate BR04 as it is required for Branch reinforcement.


CHAPTER 7
7 AVEVA E3D™ Supports Application Defaults
The AVEVA E3D™ Supports, Supports Admin Data form is the main control form for the AVEVA E3D™
Supports application. It allows the administrator to control some of the design limits within which supports
can be created. The form also allows the administrator to set the criteria that AVEVA E3D™ Supports uses
to locate support zones etc.
The default values/settings shown on the forms are those that exist when the AVEVA E3D™ Supports
application is first installed.
 Some of the defaults on the Options(1) tab can be modified by the designer using the AVEVA E3D™
Supports Application Defaults form, the Designer must be a member of the DESADMIN Team.
The AVEVA E3D™ Supports, Supports Admin Data form modifies values in /MDS/OPTION/DEFAULTS,
which are the defaults that are set for the AVEVA E3D™ Supports Application Defaults form in AVEVA
E3D™ Supports design.
From the Configuration Group on the SUPPORTS Tab, click the Application Defaults button.
Supports Admin Data Options (1) Tab
The defaults on the Options (1) tab are grouped into

three sections: Application Tolerances, Hangers and
Framework Connection Details.

Max. Pipe Slope (MDSSUPPMS)
This is the slope value above which AVEVA E3D™ Supports creates a framework type support perpendicular
to the pipe. Below this slope value, AVEVA E3D™ Supports allows the pipe to sit at an angle relative to the
vertical framework.
Default Session/default
Description
Value catalogue modifiable
1/10 Session Maximum allowable pipe slope for horizontal supports.
:MDSSUPPMS slope > 1/10
:MDSSUPPMS slope < 1/10
Steelwork Overlap (MDSSUPPOV)

This value determines the overlap distance for steelwork overlap type joints on the support frameworks
MDSSUPPOV.
Description
Value (mm) catalogue modifiable
10 Session Steelwork overlap

Max. Packing Dist (MDSPACKDI)
When a pipe is placed on a support, this value is used to check that the distance between the steelwork and
the bottom of ancillary is not exceeded.
Description
50 Session Maximum allowable packing distance
Max. Packing Overlap (MDSPACKMO)
This is the maximum allowable overlap that can occur between a support ancillary and its associated
supporting steelwork.
Description
5 Session Maximum allowable packing overlap
Max Trunnion Length
 This setting is now no longer used and will be removed in future releases.
Pipe Clearance (MDSSUPPCL)
This value is overridden by the new AVEVA E3D™ Supports ancillary default values declared in the AVEVA
E3D™ Supports PARAGON module defaults catalogue, i.e. in the DATA members found in a typical AVEVA
E3D™ Supports ancillary default DTSE element.
For example, DTSE /MDS/ATTA/DEFAULTS/AT01/100/FRMW

Description
100 Session Steelwork clearance from support attachments
 Refer to 8.1.13 Framework Clearance Option, Closed End Clearance and Open End Clearance.
When a designer chooses to build a support using the Clearance option, this value is used to determine
the clearance on both sides of the support attachment. For example, if the AVEVA E3D™ Supports
ancillary default values are not found.
Max. Horizontal Angle (MDSMAXHANG)
This default determines the maximum allowable angle in the horizontal plane with respect to the datum pipe
centreline that a pipe can have in order to be added to a framework.
Description
Value (Degrees) catalogue modifiable
30 Default catalogue Maximum allowable horizontal angle for pipe

Min. Rod Length (MDSMINHANG)
Description
150 Default catalogue Minimum hanger rod length for AVEVA E3D™ Supports
Max. Pivot Angle (MDSMAXPIVA)

This default determines the maximum allowable slope for a horizontal pipe that can be supported by a hanger.
If the user attempts to support a section of pipe which has a slope is greater than the MDSMAXPIVA angle an
error is displayed.
Default
Session/default
Value Description
catalogue modifiable
(Degrees)
30 Default catalogue Maximum pivot angle for pipe hangers
Project Hanger Interfaces (MDSHANGIF)

This shows the available hanger interfaces:
Licad - Lisega
CPL - Witch Hanger from Carpenter & Paterson Ltd
Standard MDS - Standard AVEVA E3D™ Supports hanger application Default value.
PSL - PS Designer from Pipe Supports Ltd
It is possible to define the hanger Interfaces that are available for use in Model.
The default and active hanger interfaces are specified from right click menu here and loaded automatically
when the user enters Model. Only active default hanger interfaces would be available from the drop-down list.
User Warning Angle (MDSPIVWARN)
Session/default
Default
catalogue Description
Value (Degrees)
modifiable
5 Default catalogue Warning pivot angle for pipe hangers

This default is also associated with hangers and determines the angle above which a warning is displayed
to the user. If the user attempts to support a section of pipe whose slope is greater than or equal to the
MDSPIVWARN angle, an error is displayed but the user is allowed to continue with the design process.
 It is essential that the value of MDSPIVWARN is always less than the value of MDSMAXPIVA.
In the example given in MDSMAXPIVA and MDSPIVWARN, the designer would have received a warning
alert, as the slope of the pipe is greater than the MDSPIVWARN angle but less than the MDSMAXPIVA
angle.
 The AVEVA E3D™ Supports manufacturers hanger interfaces (LICAD, PSDesigner and Witch
Hanger) will override these default settings.
Joint Offset (MDSOFFSET)
Session/default
Default
catalogue Description
Value (mm)
modifiable
The value used by the AVEVA E3D™ Supports Integrity
150 Default catalogue
Checker for joint eccentricity.
Automatic Pads
Description
value catalogue modifiable
Sets the Automatic Pad default value:
ON Default catalogue 1. ON
2. OFF
 This option determines whether pads should be added when the support is welded to a floor Plate
for example PANE or HPLATE in Marine projects.

Supports Admin Data Options (2) Tab
Flange Gapping Value (MDSFLAGAP)
Description
0 Default catalogue Flange gapping value.
This is the value used for flange gap control when the flange gap toggle is true on the AVEVA E3D™
Supports Application Defaults form.
Alternate Representation Level (MDSLEVCHANGE)
Description
The value that can be set to allow alternative graphical
7 Default catalogue
representation.
Transport Prefix (MDSTRANPREF) and Transport Text (MDSTRANISO)

The default MDSTRANPREF contains the prefix string that identifies a transportation support. If the support
name starts with the transport prefix, the STEX of all support attachments associated with the support will
have the transportation#/support text string, contained in the default MDSTRANISO. This is appended to the
support name in the Attachment Stext attribute and will appear on the relevant Piping Isometric.

Description
T Default catalogue MDSTRANPREF: transportation support prefix.
TRANSPORTATION# MDSTRANISO: transportation support text as seen

Default catalogue
/SUPPORT on the Piping Isometric.
Number of Characters in Trunnion Support Codes Standard (MDSTRUNCODE)
Description
Number of characters to be displayed in trunnion
5 Default catalogue
support codes standard.
Unit of Weight on Drawings (MDSWEITAG)
Description
Kgs Default catalogue Defines the unit of weight on drawings.
Special Support Number
This section deals with Special Support Number Prefix (MDSSPECPRE), Special Support Number Unique
(MDSSPECFLA) and Special Support Number Checker (MDSSPECON).
Description
SPS Default catalogue MDSSPECPRE: special support number prefix
false Default catalogue MDSSPECFLA: special support number unique flag
false Default catalogue MDSSPECON: special support number checker
The MDSSPECPRE default is the special support number prefix and is used when special supports are
created. The prefix is used in combination with the standard support name. It can be made to be unique
within the current MDB by setting the MDSSPECFLA default to true. Setting the default value to false
allows the special support number to exist at more than one support. Setting MDSSPECON to true
prevents the user from proceeding until a special support number is entered.
Weight Unit (MDSWEIUNIT)
Description
This value is a conversion factor that allows output of
1 Default catalogue
weights in units other than kg.
All catalogue weights are stored in the database in kg. This setting is used in weight calculations and
enables output in lbs, or any other desired units. The options are:
1 (kg) = output in kg
2.2046 (lbs) = output in lbs
Other = Any other weight units. Enter the appropriate conversion factor in the numeric entry box.

Dataset Code Conversion Factor (MPU)
Description
Dataset code conversion factor (two options):
1. Metric project = Dimensions in mm.
Metric project Default catalogue
2. Imperial project = Dimensions in inches Divided by
25.4 to give output in inches.
Unique Support Names

When the check box is selected, each ancillary on the support frame receives a unique number and
functionality is made available for the user to create reference supports.
When the check box is deselected, functionality for the user to create reference supports is disabled.
The main purpose of the reference support functionality is to allow the user to add reference an existing
support ancillary.
For example, if when creating a new framework support there is an ancillary created on another pipe that the
user wishes to reference to the support, the user can select the ancillary and it becomes part of the support.
Special Support Number Unique

Please see 7.2.6 Special Support Number.
Special Support Number Checker

Please see 7.2.6 Special Support Number.
Display Orientation in Support Tag on Isometric (MDSORINOT)
Description
Sets what the support tag displays on the Isometric.
true = PS100
true Default catalogue
ORI = N
false = PS100

Notes Appear on Isometric Drawings (MDSTRUNNOTES)
Description
Determines whether the following notes are created and will
therefore appear on isometric drawings:
DO NOT CUT HOLE IN PIPE

true Default catalogue 6mm WEEP HOLE
FREE TO SLIDE
 This setting has no effect in existing Supports.
Display Bracing Members in Isometric MTO (MDSFRAMEBRACING)
Description
Determines whether the Bracing Members appear on isometric
False Default catalogue
drawings MTO:
Admin Data Miscellaneous Tab
The defaults on the Miscellaneous tab currently

only used to specify Zone ID.
Zone ID
The settings within the Zone ID section represent the criteria that the AVEVA E3D™ Supports application
uses to select suitable zones for creation of support frameworks.

Support Application Defaults
The AVEVA E3D™ Supports designer can modify some of the defaults using the AVEVA E3D™ Supports
Application Defaults form.
To access the Supports Application Defaults form select Defaults form the
Settings group on the SUPPORTS tab in AVEVA E3D Model.
All values entered into this form are always displayed in the current format for distance units set inside
AVEVA E3D.
 Any changes made here are temporary, i.e. they apply only to the current session. To make the
changes to the defaults permanent, use the applicable administration forms.
The items on this form are self-explanatory except for Flange

Gaps. This function only works in ‘creation by cursor’ mode. The
setting for this functionality is available by pressing the Flange
Gaps button. This will display the Supports Flange Gaps form:
Note: ID1 is the first member identified and ID2 is the second member identified (if applicable). This can
make a significant difference to the structure as shown in the examples below. The positioning of the
framework legs can be used with either the identified GENSECs geometry or GENSECs origin.

The following examples show the effect of selecting the members in different orders.
ID1 = off, ID2 = off both flange gaps are set to off Left first, ID1 = Inside, ID2 = Outside
Right first, ID1 = Inside, ID2 = Outside Left first, ID1 = Inside, ID2 = Off
Right first, ID1 = Inside, ID2 =

Off

Exercise 5 – Changing the AVEVA E3D™ Supports Defaults
1. Change the Steelwork Overlap from 10mm to 20 mm and the Pipe Clearance from 100mm to
150mm.
2. Enter AVEVA E3D Model and check that the values have changed on the Supports Application
Defaults Form.


CHAPTER 8
8 AVEVA E3D™ Supports Ancillary Data Form
The Supports Ancillary Data form contains the design parameter definitions for all the ancillary support
components that can be modelled using design parameters in the AVEVA E3D™ Supports catalogue. It
allows the administrator to define the physical dimensions of all the ancillaries to match a given vendor. The
supplied parameters are generally based on, but not exclusively:
• Carpenter & Patterson Ltd
• Pipe Suspension Equipment Catalogue No 7/94.
References to the supplier figure numbers are provided on the relevant section of the form. The form also
provides material descriptions. The forms allow the administrator to set minimum and maximum design
values associated with certain attributes of the ancillary, and contains information used during Material Take
Off (MTO) extraction by the AVEVA E3D™ Supports Automatic Drawing Production application.
The component descriptions can also contain rules that modify the geometry of the component in certain
situations, e.g. by adding stiffening webs for pipe shoes where the height of the shoe exceeds a given value.
Changes made are only applied to the database when the Apply button is pressed. The Cancel button
closes the form.
Select Ancillary button located in the Standard Defaults group from the main menu to display the
Supports Ancillary Data form.
 There are similar data forms available for Hanger Supports, Structural Frameworks and Trunnions.
These will be covered in the forthcoming chapters.

8.1 Standard Tab
The left hand side of the form lists the available AVEVA E3D™ Supports ancillary support standards.
The buttons below the list provide filtering on specific support types.
When a support type is highlighted, the Support Standard name, its Standard Replacement Name,
Description and the Support Class are updated at the top of the form (described below). This information
is outside of the tabbed areas and is displayed on all tabs.
The plotfile for the selected standard is displayed on the right of the form. To zoom in on an area of the
plotfile, click and drag with the middle mouse button. To restore the original size, use the right-click menu
and select Reset Limits.
The information on the form is grouped into two sections:
• Standard - details apply to all sizes of the component.
• Bore Specific – details are only associated with the specified size (bore) of component.
The Apply button should be used before selecting another standard; otherwise any changes will be lost.
Support Standard
The support type selected in the list is copied here, and cannot be changed. The Support Standard is the
code used internally within the software by the AVEVA E3D™ Supports application.
Standard Replacement Name
This is the client’s replacement support name used on all forms in the AVEVA E3D™ Supports application
when referring to the support type defined by the Support Standard. It is also output in place of the Support
Standard name on AVEVA E3D™ Supports Automatic Drawing Production drawings. The name can be
modified by editing the text in this field. All characters in the replacement name MUST be alpha/numeric
only.
For Training Purposes the replacement Name of AT01 has been changed to XXXAT01. Click the Apply
button on the form and Save Work.
Description
The text in this field is configurable to suit each design project; it is displayed to the user in the Design
module and changes the associated Material Take Off (MTO) details on Isometrics and on AVEVA E3D™
Supports Automatic Drawing Production system.

For Training purposes change the Description of AT01 to Welded Pipe shoe for ¾” N.B. to 20” N.B., as
shown above. Click the Apply button on the form and Save Work.
Support Class
Support Class is used by the AVEVA E3D™ Supports application to detect how the support should be
created.
In the example above AT01 the Welded Pipe shoe for 3/4" N.B. to 20" N.B. has a Support Class of Welded
Shoe.
The following defaults are located in the Standard section of the form:
Active
This option enables the administrator to specify which of the available ancillaries will be available for use
on the project by the AVEVA E3D™ Supports designer, as follows:
True - ancillary included in selection lists
False - ancillary excluded from selection lists
This Active setting overrides any subsequent setting shown on the Active/Shop Flag.
 This function is the same as that performed on the AVEVA E3D™ Supports Active Control form as
detailed in Chapter 7. Both forms complement each other.

Vendor Reference
Details the vendor figure number associated with the component build parameters that are detailed on the
Supports Structure Data window.
Pipe Specification Material Code

The pipe material is specified here, as follows:
• CS Carbon Steel
• SS Stainless Steel
• FG Fibre Glass
• GV Galvanised
• PL Plastic
• CN Cupro Nickel.
ALL represents ANY material, i.e. valid for all pipe specifications.
This text value, e.g. CS, represents the setting stored at a valid PIPE specification, at the UDA
:MDSPipeMat, for use by the AVEVA E3D™ Supports application. These settings are totally configurable
and NOT restricted to the example values shown here.
PROPCON - MDS Ancillary Material
The ancillary component material is selected from the materials contained in the PROPCON (properties)
database.
SKey
The SKey is the defaults symbol that is used to represent the support on the Isodraft Isometric.
Skey Override
The user can specify a symbol to represent the support on the Isodraft Isometric. This can be one of the
existing Isodraft symbols or a user defined symbol based on the default SKey.
 TM-1873 AVEVA Everything3D™ (2.1) Isodraft Administration Rev 2.0
Isometric MTOC Flag
This setting determines whether the material for a AVEVA E3D™ Supports ancillary appears in the
material list on the piping isometric:-
Ancillary material appears in the isometric material

True -
list.
Fals Ancillary material does not appear in the isometric

-
e material list.
The Isometric MTOC Flag overrides any subsequent Shop Flag settings shown on the Active/Shop Flag
Tab.
The following defaults are located in the Bore Specific section of the form.

Bore
The size (bore) of the pipe (in mm) is specified by clicking on the up/down arrows. The following pipe defaults
apply to the size of the pipe selected.
Provides the same information as Pipe Specification Material Code above, but overrides the Standard
setting for the selected bore.
PROPCON - MDS Ancillary Material
Provides the same information as PROPCON - MDS Ancillary Material above, but overrides the Standard
setting for the selected bore.
Framework Clearance Option, Closed End Clearance, Open End Clearance
MDS allows an overlap (clearance) value to be used when an ancillary is placed on a framework type
support.
This functionality will always override the pipe clearance value declared in the AVEVA E3D™ Supports,
Supports Admin Data form Options (1) tab explained in Pipe Clearance (MDSSUPPCL), and the AVEVA
E3D™ Supports, Supports Application Defaults form in User Modified Defaults.
An additional parameter for the ancillaries is used to instruct AVEVA E3D™ Supports how the overlap
(clearance) is applied, whether from the centreline or the geometry of the pipe and the AVEVA E3D™
Supports ancillary (e.g. the outside of the pipe). See the example below:
Framework Clearance Option
Additional overlap (clearance) values are stored within the catalogue held dimensional parameters of the
ancillary. The two values cater for different clearances, dependent on the type of standard framework being
created, designated as the Open End and Closed End clearances, as shown below:

Open End and Closed End Clearances
There is also a build style parameter which is held as a user defined attribute (UDA) that specifies the way
the support frame dimensions are applied when the frame is built up, i.e. whether the inside or outside of
the steelwork at the closed end is used. This UDA is copied from the support frame template.
Using Inside or Outside Style
The Build Style of the AVEVA E3D™ Supports framework is controlled via the UDA :MDSBuildStyl at the
STRUCTURE element of a AVEVA E3D™ Supports framework template. There are two options, i.e. INSIDE
(default) or OUTSIDE, which currently may only be set via the command line in the AVEVA E3D™ Supports
framework template Design databases.
 Changing this UDA manually at design instance of the template will have no effect as it is always
copied form the template each time the support frame is modified by the application.
8.1.15.1 Limitations
The overlap (clearance) functionality described above has only been added to the following support frame
types:
FT03 to FT15 inclusive FT21 FT32 FT36 FT40 FT56

FT17 FT25 FT33 FT37 FT42
FT18 FT29 FT34A, B, C FT38 FT43
FT19 FT31 FT35 FT39 FT51

Active/Shop Flag Tab

Active
The setting of these check boxes determines the pipe bore sizes that the selected ancillary can be attached
to.
When Active is true on the Standard tab, all check boxes are ticked (true) by default, but the administrator
can un-tick boxes as required for the project.
When Active is false on the Standard tab, this setting overrides all the check box settings, and are treated
as false, even if they are ticked (true).
Shop Flag
The setting of these check boxes determines whether the material for a AVEVA E3D™ Supports ancillary
appears in the piping isometric material list under the FABRICATION MATERIALS (SHOP TRUE) or
ERECTION MATERIALS (SHOP FALSE) heading of the MTO.
When the Isometric MTOC Flag is true on the Standard tab, all check boxes are ticked (true) by default,
but the Administrator can un-tick boxes as required for the project.
When the Isometric MTOC Flag is false on the Standard tab, this setting overrides all the check box
settings shown on this tab, and are treated as false, even if they are ticked (true).
Parameters Tab
The Parameters tab displays a table of the design parameters for the selected AVEVA E3D™ Supports
ancillary for each bore size. The bore sizes that appear in this table are NOT dependent on the Active
check box settings of the previous tab. The parameters listed here are for display purposes only (not
editable). Parameters are changed in the Size tab.
The width of the columns can be altered by clicking and dragging the vertical column separator lines.
Selecting a row (by left-clicking) selects that bore size in the Size, Alt Expression and User Des Pars tabs.
For example, when switching to the Size tab, that bore will already be selected, but can be changed using
the Bore selection control.

Size Tab
The Size tab allows all the design parameters for a specific bore size to be edited. The design parameters
listed here correspond to the applicable row of the table in the Parameters tab.
The description of the design parameters shown in the Size (and Parameter) tabs are taken from the
DTREF of the SCOM of the CATE in the CATA in the AVEVA E3D™ Supports-Standards-Supports (e.g.
for an AT01, all the SCOM are collected for /ATTA-AT01). Where the CATE cannot be found, the
descriptions are shown as unset, and the message ‘Cannot collect SCOM DBREFS and get descriptions’
is displayed on the status bar. If the CATE is found, but one or more design parameter descriptions are
unset, it is displayed as unset.
When the Apply button is clicked, the changes for the selected bore size will be reflected in the applicable
row of the Parameters tab.
On returning to the Parameters tab, all the changes made can be viewed together. If these are satisfactory,
all the changes can be applied at once to the database by clicking on the Apply button.

Parameter Tab
The Parameter tab allows a selected design parameter to be changed for a specific bore size, or range of
bore sizes. This corresponds to editing a column of the table in the Parameters tab.
The design parameter to be edited is selected from the Column drop-down list and the new value is entered
into the Value box. The range of bore sizes that the value is applicable to is specified using the From Bore
and To Bore drop-down lists.
When the Apply button is clicked, the list at the left of the form is updated with the new value. The changes
will also be reflected in the relevant columns of the table in the Parameters tab. On returning to the
Parameters tab, the changes made can be viewed together. If these are satisfactory, all the changes can be
applied at once to the database by clicking on the Apply button.
Change the Support Height of AT01

from 100mm to 150mm
Column 5. Support Height
From Bore 20
To Bore 500
Value 150

Alt Expression Tab
The Alt Expression tab provides for alternative expressions and alternative design parameters for a particular
bore. This feature is used to change the geometry of a component in certain situations.
The AVEVA E3D™ Supports application checks the alternative expression each time the component is
modified. If the expression is true, the alternative design parameters to the right of the expression are used.
In the example screenshot above, when design parameter 5 is greater than 100mm, design parameter 7 is
set to 6mm and design parameter 9 is set to 25mm.
This creates stiffeners on the AT01 pipe shoe 6mm thick and located 25mm from each end of the shoe.
 It is not possible to create new expressions, only to alter those that are present
User Des Pars Tab

This tab lists the design parameters that the AVEVA E3D™ Supports designer can modify during the
creation or subsequent modification of a support. The example screenshot shows component AT01, bore
size 20mm. The designer would only be allowed to modify two of the design parameters for AT01:
Design Parameter 2 - support length, which has minimum and maximum values of 100mm and 350mm
Design Parameter 5 - support height, which has minimum and maximum values of 50mm and 180mm
When the designer modifies these values using the AVEVA E3D™ Supports application, the minimum and
maximum values are checked and a warning message is displayed if any values are outside their allowable
ranges. The administrator must ensure suitable minimum and maximum values are entered for the design
parameters.
In some situations it may be necessary to restrict a user-editable parameter to a single value. For example,
for AT01 with 20mm bore, the shoe height may need to be fixed at 100mm to match the component available
in a given supplier catalogue. In this case the minimum and maximum values are both set to 100.
Adding User-editable Design Parameters
To create a new user-editable design parameter:
1. Select the Standard tab and select the relevant ancillary.

2. Select the User Des Pars tab and select the Bore using the up/down arrows.
3. Click on the New User Editable Design Parameter button. An Input form is displayed requesting the
number of the new design parameter.
4. Enter the design parameter number (e.g. 1 for

Flange Width) and click the OK button to create the
new user design parameter. The new design
parameter appears on the form, with default minimum
and maximum values of 0.
Important: This new design parameter will appear on the form for ALL BORE SIZES in the standard. Ensure
the values required are entered at each bore size.
5- Enter suitable minimum and maximum allowable values for the design parameter as shown below,
(Min = 80 and Max = 100).
6. Click the Apply button to commit the changes to the database.

Deleting User-editable Design Parameters
To delete an existing user-editable design parameter:
1. Click on the Remove User Editable Design Parameter button. An Input form is displayed requesting the
number of the user design parameter to be deleted.
2. Enter the design parameter number (e.g. 1 for Flange Width) and click the OK button to delete the selected
user design parameter.
The Confirm form is displayed as shown below. Click

the Yes button to delete the selected user design
parameter.
3. The selected user design parameter is now deleted from all bores of the AVEVA E3D™ Supports Ancillary
standard, as shown.
4. Click the Apply button to commit the changes to the database.
Support Compatibility
The Support Compatibility tab defines which associated ancillaries are available to the user for each
particular ancillary type.
The fields at the top of the window display details for the currently selected ancillary. Refer to Standard Tab
for further information.
Each ancillary type is associated with a particular support class. For example, an AT01 is associated with a
welded shoe support class. The support class of the selected ancillary displays at the top right of the Supports
Ancillary Data window.

The list of Available Support Classes contains all available support classes.
The list of Compatible Support Classes contains all available support classes that are compatible with the
currently selected ancillary.
To make a support class available, select an item in the list of available support classes and click the right
arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow to reverse the action.
The list of Compatible Ancillaries contains all compatible ancillaries (populated from the selections made in
the list of compatible support classes).
The list of Restricted Ancillaries allows you to specify the ancillaries that are excluded during support
creation.
To exclude an ancillary from support creation, select an item in the list of compatible ancillaries and click the
right arrow at the side of the list. The item is transferred to the Restricted Ancillaries list. Click the left arrow
to reverse the action.
The combination of the lists defines the ancillary types that the user can select from.
Selection Configuration
The Selection Configuration tab contains checks for the restrictions for each ancillary.
The Common part of the Selection Configuration tab applies to all ancillaries. The Trunnion Ancillary part of
the tab applies only to Trunnion ancillaries and becomes active if the support class of the selected ancillary
contains the word TRUNNION.
Primary Component
Select the check box to define that the ancillary can be created as a standalone ancillary, not just as an
associated ancillary.
If the support class of the currently selected ancillary starts with the word FOR, the check box is deactivated.
Available on Framework
Select the check box to define that the ancillary can be created on a framework.

Only Available on Framework
Select the check box to define that the ancillary is only available on a framework structure.
Minimum Elevation
Specifies the elevation (height) at which an ancillary can be created at and above. For example, setting a
value of 5000 means the ancillary can be created at any elevation at 5000mm and above, but not below
5000mm. If a value of -1000 is input, the support can be created at any elevation below 1000mm.
The default setting is *, indicating that there is no restriction on the elevation at which the ancillary can be
created.
Pipe Direction
Select the Vertical check box to define that the ancillary can be created on a vertical pipe.
Select the Horizontal check box to define that the ancillary can be created on a horizontal pipe. If the ancillary
is allowed on a horizontal pipe, it must pass the maximum slope check.
Component Type
By default, the Supports application positions the Trunnion ancillary on the head or the base of the Trunnion.
The Head option button indicates that the Trunnion ancillary is positioned on the head of the Trunnion.
The Base option button indicates that the Trunnion ancillary is positioned on the base of the Trunnion.
If the Trunnion ancillary is in the support class FOR TRUNNION BASE or PIPE REST INLINE, it is defined as
a base component. If the Trunnion ancillary support class contains the word BASE or BEARING, it is defined
as a base component. All other Trunnion ancillaries are defined as head components.
Head Components Allowed

The Head Components Allowed part of the tab applies only to Trunnion ancillaries and becomes active if
the selected ancillary is a Trunnion head component.
Select the Tube check box to define that the head component of the Trunnion ancillary can be positioned on
a pipe tube.
Select the Elbow check box to define that the head component of the Trunnion ancillary can be positioned on
a pipe elbow.
Select the Reducer check box to define that the head component of the Trunnion ancillary can be positioned
on a pipe reducer.
Select the Tee check box to define that the head component of the Trunnion ancillary can be positioned on a
pipe tee.
Trunnion Types Allowed On
The list of allowed Trunnions contains all Trunnions that the currently selected Trunnion ancillary can be
created on. The list of restricted Trunnions allows you to specify the Trunnion types that the ancillary cannot
be created on.
To restrict an ancillary from being created on a Trunnion type, select an item in the list of allowed Trunnions
and click the right arrow at the side of the list. The item is transferred to the adjacent list. Click the left arrow
to reverse the action.

Exercise 6 – AVEVA E3D™ Supports Ancillary Defaults
Using the above example, change the Replacement Name and the Description of AT01.
Change the shoe height of all AT01 shoes from 100mm to 150mm. Test the new default shoe height in
Design.
On the Ancillary Selection Form the Standard Name and Description should be as follows:
The Shoe height should be displayed as 150mm.
Navigate to the Ancillary (ANCI) in the Model explorer, then from the Properties Grid, select Specification >
Parameters and note the Support Height.

CHAPTER 9
9 AVEVA E3D™ Supports Hanger Data Form
 Important: The AVEVA E3D™ Supports hanger template configurations displayed in the AVEVA
E3D™ Supports Hanger Data form - Standard tab shown below MUST represent the same hanger
components included in the actual hanger templates defined in the SITE called /MDS/HANGERS. This
holds the modelled hanger templates for each hanger component manufacturer/supplier in their
respective databases.
The AVEVA E3D™ Supports Hanger Data form is used to define the configuration of the AVEVA E3D™
Supports hanger templates. Each hanger’s configuration can have a replacement name more meaningful
to the AVEVA E3D™ Supports designer, and a description to suit a particular design project.
These AVEVA E3D™ Supports Hanger templates only apply to the AVEVA E3D™ Supports application
when the Project Hanger Interface (MDSHANGIF) default value is set to Standard MDS.
The Project hanger interface is set on the AVEVA

E3D™ Supports Admin Data form which can be
displayed in Paragon by selecting Application
Defaults from the Configuration Group of the
SUPPORTS Tab.
Four sets of AVEVA E3D™ Supports hanger

templates are supplied with the application, one
for each of the hanger components
manufacturer/supplier, i.e. Licad, PSDesiger,
Witchhanger and Standard MDS.
For the purposes of the training the Standard MDS

will be used.
Changes made are only applied to the database

when the Apply button is clicked.
The Cancel button cancel the form. If changes

have been made, but not applied, a Question alert
form is displayed asking if the changes are to be
applied before exiting.
Select Hanger Template from the Standard Defaults group of the SUPPORTS Tab.

9.1 Standard Tab
The left hand side of the forms lists the available AVEVA E3D™ Supports hanger template types; each type
represents a hanger configuration. There are two basic hanger types: Fixed hangers (FH) and Variable
Hangers (VH).
When a hanger configuration is highlighted, the AVEVA E3D™ Supports standard, its replacement name
and description appear at the top of the form (described below). This information is outside of the tabbed
areas and is displayed on all four tabs.
The plotfiles for all of the selected hanger configurations are displayed on the right of the form. To zoom in
on an area of the plotfile, click and drag with the middle mouse button. To restore the original size, use the
right-click menu and select Reset Limits.
The Apply button should be clicked before selecting another standard; otherwise any changes will be lost.
Support Standard
The AVEVA E3D™ Supports hanger template configuration selected in the list is copied here, and cannot
be changed.

when referring to the hanger configuration defined by the Support Standard. It is also output in place of the
Support standard name on AVEVA E3D™ Supports Automatic Drawing Production drawings.
The replacement name is based on the hanger configuration, see Hanger Template Configuration.
Description
Hanger Configuration
Each hanger template configuration has its own specific design characteristics, based on the following
considerations:
• Is it a single or double configuration?

• Should the hanger be connected to a vertical or to a horizontal pipe?
• Should the pipe be insulated?
• Should the steelwork connection be a double-channel connection?
• What type of beams can be used for the steelwork connection?
• If it is a variable spring hanger, where is the spring located? Is it below the pipe? Is it located above
the pipe but below the steelwork? Is it located on top of the steelwork?
• Is the hanger connected to the pipe using a pipe clamp or to a welded lug?
The hanger template configuration is defined as a combination of three basic components, the top (T),
middle (M) and bottom (B) component. For example, a T1 M2 B5 hanger means that the hanger has a T1
type top connection, M2 type middle connection and a B5 type pipe connection. These three basic
components can be viewed on the plot files shown on the right of the form.
Based on this combination and on other attributes of the hanger templates and of the catalogue
components, the AVEVA E3D™ Supports application can determine how to incorporate the hanger
template into the design.
Use the drop-down lists to select the T, M and B components that represent the selected hanger
configuration, and then click the Apply button.

Active
This option enables the administrator to specify which of the available AVEVA E3D™ Supports hanger
template configurations will be available for use on the project by the AVEVA E3D™ Supports designer,
as follows:
True = hanger template configuration included in selection

lists
False = hanger template configuration excluded from selection

lists
 This function is the same as that performed on the AVEVA E3D™ Supports Active Control form as
detailed in Chapter 7.
SKey
The symbol key that is stored against the SDTE of the specification is displayed here. A symbol key specifies
a symbol representation for a support type on an isometric drawing.
SKey Override
You can override the symbol key that is stored against the SDTE of the specification. Input an alternative
symbol key value in the field to modify the symbol representation for a support type on an isometric drawing.
Support Function
The hanger support function is specified here. For example, FH for a Fixed Hanger.
By default, ancillary, hanger and trunnion standards are assigned a default support function corresponding
to their standard code. For example, AT, AN, FH, VH, TT, these are fully configurable.
To specify a support function for an ancillary, refer to Ancillary Data for further information.
To specify a support function for a trunnion, refer to Trunnion Data for further information.

Soft Types
This tab is used for viewing hanger template configuration soft types. These configurations use the same
template as the hanger configuration defined in the Soft type column, but are handled differently by the
AVEVA E3D™ Supports application.
 The hanger template configuration in the Soft Type column is the master template used by the AVEVA
E3D™ Supports hanger standard shown in the Standard column.

Bottom Associated Support Standards Tab

If a hanger supports a pipe through a lug, ancillary or trunnion, this tab allows you to view the standard
supports that can be used for the support.
Selecting a component in the Bottom Hanger Type column will display the standard types that can be
associated with it in the Supports Standards column. The associations can only be modified using the
command line interface.

Allowable Rod Sizes
This tab enables the administrator to view the range of available rod sizes for a given hanger configuration.
Click on an entry in the Nominal Pipe Size column. The available rod sizes for the selected bore and hanger
configuration are listed in the Rod Sizes column.
Additional rod sizes can be added to the Catalogue by editing the Pproperty attribute of the DATA elements
held for each rod below the SECT MDS/HANGER/DEFAULTS/ROD-SIZE under the CATA
MDS/HANGER/DEFAULTS.
 The Hanger Data Form will need to be closed and reopened to display these changes.


CHAPTER 10
10 Hangers Design Templates
Hangers design using supplier-specific hanger components are template driven. A default set of templates,
in a APPLDW called /SUPPORT/HANGERS/PSL, is supplied with the application. Each hanger’s
configuration template has its own ZONE. Each size of a given hanger’s configuration is represented by a
SUPPO component. Two sets of hanger templates are supplied with the application, one for each hanger
components supplier.
Data sheets
Each hanger’s configuration, whether fixed, variable, single or double, has an associated application
standard data sheet. For some companies it might be a data sheet for the available hanger’s components;
in other companies it might be a data sheet for the specific hanger’s configuration.
All of the application standard data sheets are accessible to the designer, either via the AVEVA E3D™
Supports - User Guide or from within the Model module via the View Standard button on the Additional
Tools drop-down menu in the Tools group.
To configure templates, the Administrator requires read/write access to the hangers design templates
database. For example PSI hangers are stored in AVEVA E3D™ Supports Db /MDS/DESITMPL-PSL
which is in the APS project and would need to be copied into the Design project.
Configuration of the Hanger’s Design Templates
When the AVEVA E3D™ Supports application creates a hanger of a given configuration, it copies the required
hanger template. In order for the application to know which template it should copy, a specific naming
convention is used. Each hanger configuration has a name (e.g. FH01, VH01). As explained earlier, each
zone represents a single hanger configuration.

The names of the zones have the following formats:
• MDS/FH** This is used for fixed hangers (e.g. /MDS/FH01).
• MDS/VH** This is used for variable hangers (e.g. /MDS/VH01).
(** denotes a two digits sequence number)
Each zone owns several SUPPO elements. Each SUPPO

represents a hanger size for that configuration. The name of the
SUPPO templates has the following format:
MDS/FH**/pipe_size_in_mm
For example, a SUPPO having the name /MDS/FH01/100

represents a template for a hanger with a FH01 configuration,
used for a 100mm pipe.
In some cases, the hanger designer may need different hanger

sizes for the same pipe size. A good example of this is when a
hanger is attached to a welded elbow lug. The lug may have a
range of hole sizes. So, although the hanger configuration type
is the same and the pipe size is the same, a lug with a larger
hole will require a larger pin and a hanger with larger rods. This
is handled by adding a one letter suffix to the name of the
SUPPO and is compatible with AVEVA’s standard naming
convention used in the hanger’s catalogue for rod sizes.
For example, suffix A is used for an M6 rod size, B for an M8

rod size etc. A typical template name for such a hanger may be:
/MDS/FH01/100/A. This template is for hangers with the FH01
configuration, connected to a 100mm pipe and having M6 rod
size.
The range of sizes available for a given hanger configuration, as well as other specific configuration data, is
set when the hangers feature of the AVEVA E3D™ Supports application is used for the first time in a session.
The application then scans the AVEVA E3D™ Supports hanger’s APPLDW typically
/SUPPORT/HANGERS/PSL, reads the zones attributes, and saves it in memory for later use. The range of
available hanger sizes for each configuration is determined from the restraints elements below the zone.
Each hanger has its own specific design characteristics, as defined in the AVEVA E3D™ Supports Hangers
Data form.

CHAPTER 11
11 AVEVA E3D™ Supports- Lighting Support Defaults
 Lighting Support is not supported for this release. It will be included for the future releases.
The AVEVA E3D™ Supports Lighting Support Defaults form allows the administrator to set up the
defaults required by the Lighting Support function.
Changes are only applied to the database when the Apply button is clicked. The Cancel button closes the
form. If any changes have been made but not applied, a window is displayed asking if the changes are to
be applied before exiting. The Reset button cancels any changes that have been made to the form, but
leaves the form displayed for further use.
Lighting Form
Select Lighting Support from the Standard Defaults group on the SUPPORTS Tab.
Support: Type
The text in this field is used to identify a lighting type support.

Support: Code
PML (programmable macro language) string expression giving the support code to the Lighting Support,
which is used for output in Draw or Report.
Supports: Origin
Defines the origin of the support that will be used when positioning the support. Any positional attribute or
p-point reference may be specified.
Support: Replacement Type
This is the alternative support type to be output in Draw or Report.
Support: Max. Height

The maximum height (in mm) at which the support can be created. It can also be set locally within the
support template to provide different maximum values under different conditions (different zone, elevation,
etc.)
Support: Min. Height
The minimum height (in mm) at which the support can be created. It can also be set locally within the support
template to provide different minimum values under different conditions (different zone, elevation, etc.).
Support: Bracket Limit
If the support height (in mm) is less/greater than this value, then bracket(s) will be removed from or added
to the support. The Bracket Limit may also be specified locally within the support template.
Lighting: Type
Specifies the item within the design database that represents the lighting equipment that is to be supported.
Lighting: Filter
This is a PML expression specifying the lighting more precisely.
Lighting: Origin
Specifies the origin of the lighting. When the support is created, its origin will be placed at the lighting origin.
Any positional attributes or p-point reference (e.g. DP1, P2) may be specified. It should be in the middle of
the lighting when viewing from the Z (vertical) direction.
Lighting: Y Direction
This setting is used during lighting support creation to orient the support so that its Y axis is aligned with the
Y direction of the lighting specified on this form. Any positional attribute, local axis of lighting (e.g. Y45N) or
p-point reference (e.g. DP1 or P1) of the lighting may be used. Lighting is assured to be in the horizontal
plane.

CHAPTER 12
12 AVEVA E3D™ Supports Structure Data Form
The AVEVA E3D™ Supports, Supports Structure Data form defines which of the available support
standards can be used in a project, and client’s replacement support names and descriptions can be
specified.
Framework types prefixed CT, DT, FT etc. can be organised into groups, which makes selection of a
framework easier for the AVEVA E3D™ Supports administrator.
The form also defines which ancillaries will be available to the designer for a particular framework support.
Alternative codes can be defined to replace the AVEVA E3D™ Supports application default codes to suit
the client’s standard.
Changes are only applied to the database when the Apply button is clicked. The Cancel button removes
the form. If changes have been made, but not applied, a window is displayed asking if the changes are to
be applied before exiting.
 Only the first three tabs are used in the majority of cases.
Click the Structure button from the Standard Defaults group on the SUPPORTS Tab to display the
Supports Structure Data form.

Standard Tab
The left hand side of the form lists the available framework support types. The buttons below the list provide
filtering on specific support types.
When a support type is highlighted, the support standard name, its replacement name and description
appear at the top of the form (described below). This information is outside of the tabbed areas and is
displayed on all tabs.
The plot file for the selected standard is displayed on the right of the form. To zoom in on an area of the plot
file, click and drag with the middle mouse button. To restore the original size, use the right-click menu and
select Restore Limits.
The Apply button should be clicked before selecting another standard; otherwise any changes will be lost.
Support Standard
The support type selected in the list is copied here, and cannot be changed.
modified by editing the text in this field.
Description
Active
This option enables the administrator to specify which of the available support standards will be available
for use on the project by the AVEVA E3D™ Supports designer, as follows:
True = Support included in selection lists.
False = Support excluded from selection lists.

Framework MTOC Flag
This setting is applied to the MTOC attribute of the selected component as follows:
True = Material appears in the isometric material list.
False = Material does not appear in the isometric material list.
 The settings detailed in Vendor Reference, Elevation Restriction, Pipe Specification Material Code,
PROPCON - MDS Ancillary Material and Isometric MTOC Flag are not normally used on frameworks.
SKey
SKey Override
Framework Selections/Restrictions Tab
This tab is used to specify what ancillaries are available to the AVEVA E3D™ Supports designer during
framework support creation. The fields at the top of the form show which framework is currently selected
(see Standard tab).
The left hand Selections (Allowed Ancillaries) list contains all available AVEVA E3D™ Supports
ancillaries. The buttons below the list provide filtering on specific ancillary types. To make an ancillary
available, click on the item in the list then click on the right arrow icon at the side of the list. This transfers

the item to the adjacent list. Clicking on the left arrow icon reverses this action. The * character represents
all AVEVA E3D™ Supports ancillary types.
The Restrictions (Ancillaries Not Allowed) list is used in a similar way, but is for AVEVA E3D™ Supports
ancillaries that are to be excluded.
The combination of both of these lists defines the list of AVEVA E3D™ Supports ancillary types the designer
can select from. In the example screenshot above, the * in the Selections list means that all ancillary types
are to be made available, but the Restrictions list shows that AN04, AN05*, AN61 and all LT types are to
be excluded from use by the AVEVA E3D™ Supports application for this support type.
Framework Codes
The Framework Codes tab contains alternative codes for the support codes used by the AVEVA E3D™
Supports application. For example, the framework support FT09 is made up of several sizes and numbers
of cross bars.
AVEVA E3D™ Supports can support up to 6 cross bars and up to 50 frame steelwork configurations.
FT09-3-1 in the following example represents a FT09 framework support with 3 cross members and the first
steelwork size. So a Piping General Arrangement drawing may be marked up as follows:

These codes depend on the steelwork size used and the numbers of cross bars. In some circumstances
the client’s standard may have a different standard code for different steelwork sizes but the same
configuration.
The settings defined here may be used to print the correct code in the AVEVA E3D™ Supports Design
module, on the ADP drawing, in the material list of the piping isometric and output in an AVEVA E3D™
Report if required.
For example, if an alternative code of M10A1 is specified for FT09-1-1, the Design, ADP and isometric
applications will replace the FT09-1-1 code with M10A1.
Edit Selected Row
The list at the left of the form shows the possible support codes for the selected framework (FT09 in the
example screenshot) and the alternative code, if defined. The * character means that applications will use
the Fixed code, which is the default setting.
If an alternative code is required for an individual support code, it is entered into the Alternative Code text
box, to replace the * character.
Edit Column
An alternative code can be specified for a range of fixed codes, by making appropriate selections in the
From and To drop-down lists. Enter an Alternative Code into the text box to replace current values stored
in the From and To list gadgets.

Exercise 7 – Supports Structure Data
1. Change the Standard Replacement Name of the FT09 to XXXFT09 and the Description to
Training Support Frame.

CHAPTER 13
13 Framework Template Administration

Template Modification Rules
Clients may configure the AVEVA E3D™ Supports application Structural Design Templates to an alternative
National Standard for Steelwork Gensecs as opposed to the British Standard supplied as default. This may
be a different size from the same steelwork standard or a different size from a different standard.
Apply the following rules when replacing the default size to ensure the AVEVA E3D™ Supports application
functions correctly:
• The origin of each template must remain in the same position when the steelwork size is modified.
The example shown in this section has the origin on the back mark of the cross bar. Move the origin
to align with the back when the size is changed. This ensures that the origin is placed in the correct
position in relationship to the Support datum ancillary (ANCI) when the framework is generated.
• DO NOT modify the position of the Gensecs starts and ends in relationship to the structure
orientation
• Use the naming convention described in Framework Naming Conventions.
• There is a limit of fifty structural templates per support type. This limit is governed by the Pipe
Support Specification ‘/MDS’.
• All structural members defined as GENSEC elements in the default templates will have a numerical
value set against their design parameter attribute.
For example, the default value for design parameter number 1 of GENSEC
SUPPORT/FRAMES/BS/FT09/1-BAR-1 (below the APPLDA SUPPORT/FRAMES/BS/DATA/FT)
is set to 1140. This value is the maximum allowable length for this particular GENSEC. The value
is checked against the actual length of a GENSEC element, named <structurename>-BAR-1, and
is created automatically during the creation of a Pipe Support by the Supports application. Clients
may modify this attribute in their template database as part of their configuration.
• Where a template contains internal joints, it may be necessary to modify the specification reference
to a handed joint when a mirror operation is performed. To do this, set the UDA :MdsMirror to the
spref required for a mirrored joint, when the joint is created in the template.
When a framework is created, the template is copied to the datum support (the first pipe identified will be
the datum support) and then the framework is stretched and re-sized, depending on the method of creation
used, i.e. Cursor, Dimensions or Clearance. Therefore, the initial positioning and orientation of the
GENSECs within the structure are critical.
An example of replacing the default steelwork size is shown in the next section, Framework Setup.

Framework Setup
Replacing the Default Steelwork GENSEC Size
The Supports application is supplied with a default set of frameworks based on British Steelwork standards.
The project can modify the steelwork sizes and the following example explains how the administrator makes
the alternatives available. In the example, support types FT09 option 1, which uses 60x60x8 angle Internally
Welded British Steel Standard, is changed to 2x2x3/8 AISC Standard.
Enter the AVEVA E3D in the Training

Project and Select STRUCTURES from the
Discipline drop down menu.
Navigate to the FT09 template structure

SUPPORT/FRAMES/BS/FT09/1. This is the first
available size for the FT09.
Add the structure to the 3D View.

Navigate to the STRU and select Current Element from the Local Coordinate System of the VIEW Tab
Navigate to the STRU and select Current Element button from

the Coordinate System on the VIEW Tab.
Select all three GENSECs with a Cursor Window.
Using the Properties Form
Select Specification then Reference
Spec American Standard Profiles
Type Angle
Profile L2x2x3/8

After this has been completed the image to the left

should be displayed on the screen.
 The Gensecs now have gaps between each

other and the back mark of the cross member
SUPPORT/FRAMES/BS/FT09/1-BAR-1 has
moved off the origin of the structure.
Select the cross bar SUPPORT/FRAMES/BS/FT09/1-BAR-1.
Using the Right Hand Mouse Button, from the AVEVA Power
Wheel select Context > Move
Specify the Base Point as the Centre of a P-Line.
Hold the Shift Button and using a Right Hand Click Select P-Line
Midpoint from the AVEVA Power Wheel.

Identify the P-Line LTOP.
Specify the secont point as
U 0
V -8
W 1.6
Use Tab to Move between the fields.
After completing these steps, the following view should be displayed on the screen.

The two vertical gensecs should be moved flush with the cross member.
Navigate to SUPPORT/FRAMES/BS/FT09/1-V2 and select Move from the AVEVA Power Wheel.
Use P-Line Midpoint. Select LBOT on the vertical GENSEC

to set the base point.
Set U and W to 0 and Lock using the Tab Key
Pick LBOT on the Cross Member to specify the

Cross Member.
The process should be repeated to the vertical

gensec SUPPORT/FRAMES/BS/FT09/1-V1.

Make the two vertical members flush with each other and at the intersection point the origin of the structure.
This could be done in a similar way as before using P-Line Midpoint and Locking the appropriate values.
On completed, the following view should be displayed on the screen.
Look east to make sure the cross bar has not moved in the vertical direction. The face of the gensec must
be flush with the origin of the structure, as shown below.

The final action is to modify the Description attribute at the

structural level this can be done using the Properties Grid.
Make the STRU the Current Element and set the Description to
L2x2x3/8thk Angle Welded this description is used on the
framework selection form.
Modifying the Design Template’s Minimum/Maximum Lengths

All structural GENSECs defined in the Design Template Database have their design parameter set to the
maximum usable length. The Supports application issues a warning to the user when the Support Integrity
Checker is actioned at the end of each creation or modification process. This check is only a warning and
the user is allowed to complete the support. The warning indicates to the user that either the support is
stressed or the steelwork size needs increasing.
It is also possible to define a minimum length by setting design parameter 2. For example, if the design
parameters of a GENSEC are set to 1000 100, the maximum length is 1000 and the minimum length is 100.
In the example shown the max length of the cross bar on FT09/1 is set to 1070.
From the Model Explorer, make the GENSEC

SUPPORT/FRAMES/BS/FT09/1-BAR-1 the CE and
select Attributes from the Display group on the
HOME Tab.
Enter 1070 for the Desparam attribute.
Creating Template Internal Joints
Create template internal joints using standard structural connections. If a joint needs to be ‘handed’ for
mirrored frameworks, use the UDA :MdsMirror at the catalogue join element to store the joint reference.

Modifying the Appearance of Joints and Fittings on the Supports ADP Drawing
If the appearance of a template joint or fitting on the Supports ADP drawing is not desirable, set the FIXING
function attribute to DUMMY. Joints and fixings are then ignored on the drawing material list and are not
tagged in the graphical views. Use this attribute when a joint, which has no physical properties, is used to cut-
out a GENSEC.
Framework Naming Conventions
Ensure each framework conforms to the following naming conventions. This enables the Supports application
to navigate to the appropriate element and customise the application for both the Design and Draw stages of
support production. Failure to apply these naming conventions may cause the applications to fail to produce
supports.
Type Name format Example
APPLDW SUPPORT/FRAMES/{Template type} SUPPORT/FRAMES/BS
SUPPORT/FRAMES/{Template
APPLDAR SUPPORT/FRAMES/BS/AREA
type}/AREA
SUPPORT/FRAMES/{Template type}/
APPLDA SUPPORT/FRAMES/BS/DATA/FT
DATA/{Framework type}
ZONE SUPPORT/FRAMES/BS/FT09
type}/{Framework type}
STRU SUPPORT/FRAMES/BS/FT09/1
type}/{Framework type}/{option}
SUPPORT/FRAMES/{Template SUPPORT/FRAMES/BS/FT09/1-
FRMW
type}/{Framework type}/{option}-FRMW1 FRMW1
CROSSBAR SUPPORT/FRAMES/{Template
SUPPORT/FRAMES/BS/FT09/1-BAR-1
GENSEC type}/{Framework type}/{option} -BAR-1
VERTICAL
MEMBERS (if SUPPORT/FRAMES/{Template SUPPORT/FRAMES/BS/FT09/1-V1
needed) type}/{Framework type}/{option}-V1 or V2 SUPPORT/FRAMES/BS/FT09/1-V2
GENSEC
SUBS
type}/{Framework type}/{option}-SUBS1 SUBS1
JLDATU
type}/{Framework type}/{option}-VI/S1 V1/S1
SUPPORT/FRAMES/BS/FT09/10-
PLDATU type}/{Framework
V1/S1/PLDAT
type}/{option}/V1/S1/PLDAT
SUPPORT/FRAMES/BS/FT09/10-
FIXING type}/{Framework type}/{option}-
V1/S1/IJOINT1
VI/S1/IJOINT1
There are two zones for each of these framework types: FT03, FT04, FT14, FT15, FT18, and FT19. Each one
is supplied with the suffix -H or -V e.g. SUPPORT/FRAMES/BS/FT04H.
The suffix allows the orientation of members within the structure to be different when used with vertical or
horizontal lines.

Available Templates
Extending the Number of Steelwork Framework Types Available
The supplied sets of templates contain, typically, four options for each framework. To extend this number,
create extra structures using the naming convention in Framework Naming Conventions. To reduce the
number of framework types, delete unwanted structures from the design template database.
Template Options
Availability of Cross Bars
Each standard has the ability to add up to a maximum of six cross bars. In some circumstances the office or
project standard may not want a particular standard to allow cross bar creation. Control this by setting the
:Mdsbars attribute at the template zone level. Use a ‘true’ setting to allow cross bar creation and ‘false’ to
prevent it.
Creation of Standard in the Horizontal or Vertical Plane
Some standards allow the creation of a support in the horizontal or vertical plane. In some circumstances the
office or project standard may not allow both. Control this by setting the :MdsHV attribute at the template zone
level.
:MdsHV Description
BOTH Allows creations in the horizontal and vertical plane.
HORI Allows creation in the horizontal plane only.
VERT Allows creation on the vertical plane only.
Maximum Gensec Lengths
At each GENSEC within the template, design parameter 1 is set to the maximum length allowed. The Support
Integrity Checker monitors this value against the actual length and issues a message to the user when the
support has been completed. If the :MdsCheck attribute is set to true, the user is not allowed to complete the
support without making the GENSEC length less than the maximum allowed. If the :MdsCheck attribute is set
to false, a warning is issued and the support is completed.
Cross Bar Overlap Override
When a support is created, it uses the application overlap default,

obtained from the application default form, to overlap the steelwork
for welding. This can be overridden on each individual cross bar by
setting the :MdsOlap attribute at the GENSEC element. If the UDA
:MdsOlap is set to OVERLAP, the application uses the setting in the
UDA :MdsOnum as the overlap value required.

Vertical Section Overlap
The vertical GENSEC is extended past the cross bar by the

application overlap value, in order to weld the GENSECs
together. In some circumstances the vertical member may
need to be flush with the top of the cross bar. To achieve this,
set the UDA :MdsOlap value at the vertical GENSEC to
OVERLAP and the UDA :MdsOnum value to -100 (if the
cross bar depth is 100).
The example on the left is the standard/default configuration

with the :MdsOlap unset <default>.
The example below assumes a common template GENSEC size of

100x100x8 angle. The vertical GENSEC UDA :MdsOlap value is set
to OVERLAP and the :MdsOnum value is set to - 100, (the depth of
the cross bar being 100).
Maximum Allowable Bore Sizes
Each support framework has the functionality to control the minimum and maximum pipe bore allowed for the
template. This is achieved by setting the :MdsMaxBore and :MdsMinBore UDA. For example, if the first
template for FT09 is 60x06x8 angle and you set the :MdsMaxBore to 100 and the :MdsMinBore to 50, the user
will not be allowed to add a pipe to the support which is less than 50 or greater than 100.
Navigate to SUPPORT/FRAMES/BS/FT09/1
q :MDSMaxBore :MDSMinBore
:MDSMaxBore 1200
:MDSMinBore 0
The support framework can also be configured to set the minimum and maximum pipe bores using the
dimensional values. This is achieved by setting the :MdsRange UDA.
For example, if the UDA is set to ‘1,0,610,80’, it means that dimension 1 can be between 0 and 610 with a
maximum bore of 80.
If it is set to ‘(1/2/3),0,610,80\(1/2),0,305,80\3,0,305,80’, it means that dimension 1, 2, and 3 has a maximum

length of 610 up to 80 bore, dimension 1 and 2 has a maximum length of 305 up to 80 bore, and dimension 3
has a maximum length of 305 up to 80 bore. The largest bore will be used in the check when more than one
bore exists on a framework.
Q :MDSRange
:MDSRange unset.

Automatic Steelwork Orientation
The Supports application can automatically orientate the support structure steel members of a framework type
support, dependant on the orientation of identified stiffeners. The correct orientation is achieved by utilising
appropriate templates. Each standard template has four alternatives as depicted in the example below for a
FT08 support frame.
The alternative templates are named in the form.
/{standard_template_name}/{suffix}
where suffix, is a configuration code based on the orientation of the stiffeners e.g.
SUPPORT/FRAMES/BS/FT08/1/1, SUPPORT/FRAMES/BS/FT08/1/2.
Only the templates that are built up from angle profiles have oriented alternatives.
The user-defined attribute (UDA) :MdsTmplOri is included in the Supports project MASTER/MDSDICT, which
is used to store the orientation of stiffeners as an integer. This UDA is available at STRU level and the default
value is “0”.
Project Special Templates
Project special templates allow users to create a special support with some GENSEC members, very quickly,
and if necessary to complete the design of the standard support in the standard Supports Beams & Columns
application.
Users who have write access to the project special discipline zones owned by the APPLDW
SUPPORT/FRAMES/SPECIALS/BS can create their own Project Special structural templates.
The origin of a support structure is always at the P9 of the DATUM ancillary of the current support being
created. The copied members of a project special template are positioned relative to the support structure
origin position.

Storage Areas
It is recommended that Supports project special template zones are stored in an APPLDW (Application
Data World) named SUPPORT/FRAMES/SPECIALS/BS.
Four zones are required to store the project special structure templates. Name them as follows to enable
the Supports application to recognise the appropriate discipline templates:
• SUPPORT/SPECIALS/BS/PIPE, the PIPING

template zone.
• SUPPORT/SPECIALS/BS/HVAC, the HVAC
template zone.
• SUPPORT/SPECIALS/BS/TRAY, the Cable Tray
template zone.
• SUPPORT/SPECIALS/BS/LIGHTING, the Lighting
template zone.
In the Supports Design application, if a discipline zone

exists, e.g. SUPPORT/SPECIALS/BS/PIPE, the STRU
elements are displayed in the Select Project Special
form. Otherwise the user is informed that the zone
SUPPORT/SPECIALS/BS/PIPE does not exist, and the
Copy Project Special operation is aborted. If the zone
exists but there are no STRU elements, an error
message such as the one on the right is displayed.
Filter Settings at a Piping or Tray Project Special Template

The UDA :MdsHv setting at the STRU element of the project special template is the only filtering mechanism
available. It can be set to HORI, VERT, or BOTH. The settings are self-explanatory and are relative to the
orientation of the current pipe or tray being supported by the special support.
The list of piping and cable tray project special templates displayed, and available to the user, is the same
list as the STRU members that currently exist in the appropriate discipline template zone. It is filtered
according to the settings of the UDA :MdsHv at the structural template, and the orientation of the pipe or
tray being supported.
The selected structural template is copied into the AVEVA E3D™ Supports special support being created
without any modifications to the design of its members. None of the attributes at the project special STRU
template or any of its members are used by the Supports application for either of these disciplines. They
are not required and should not be set.
The project special templates members in the piping and cable tray disciplines are copied exactly into the
Supports special support and positioned relative to the Supports special support origin currently being
created. There is no automatic modification of the positions and length of the template members when they
are copied into the AVEVA E3D™ Supports support.
Filter and Build Settings at an HVAC Project Special Template
13.7.3.1 HVAC Structure Template

The list of HVAC templates, for the HVAC STRT element to be supported, is filtered on the settings of two
UDA’s. They are :MdsHv (described in Filter Settings at a Piping or Tray Project Special Template) and
:MdsRange and are both attributes of the STRU template.
The second filter control, :MdsRange, is implemented for HVAC templates only. It controls whether
insulation exists on the HVAC STRT element being supported. The settings are shown in the table below:

Setting Action
Restrict the STRU template to support only HVAC STRT elements that are
0
un insulated.
Restrict the STRU template to support only HVAC STRT elements that are
1
insulated.
Allow the STRU template to support HVAC STRT elements that are either
2, any other value, or left unset
un insulated or insulated.
Having set the UDA’s at the STRU templates, consider also :MdsCheck. Set this UDA at the time the template
is selected and/or built from the list displayed in the Select Project Special Template form. The options are
shown in the table below:
Setting Action
Include the insulation thickness of the HVAC STRT element in the design and build
true calculations of the STRU template members copied to the current Supports HVAC
Special Support.
Exclude the insulation thickness of the HVAC STRT element in the design and build
false
calculations of the STRU template members copied to the current Supports HVAC
(default setting)
Special Support.
13.7.3.2 HVAC Structure Template Members

The positions and lengths of HVAC STRU template members are automatically modified by the settings of
two UDA’s, :MdsConfigA and :MdsConfigB, i.e. the types GENSEC, SUBS, EXTR and VERT.
Each of the HVAC Project Special Support templates are built on a base HVAC STRT duct size of 500mm
wide x 500mm high and is modified by the UDA’s mentioned above. The build action takes place when the
template is selected.
There are several predefined Project Special HVAC templates supplied at this release to complement the
existing standard AVEVA E3D™ Supports HVAC templates available.
Clicking the Copy project Special button when a HVAC Special support is being created will invoke a form,
shown below, displaying the list of available HVAC project special supports. The generated list is dependent
on whether the HVAC STRT component to be supported is insulated or not, and the setting at the UDA
:MDSRange of the STRU element at each of the AVEVA E3D™ Supports HVAC project special templates.

The HVAC project special templates STRU elements displayed in the form shown are considered suitable for
supporting HVAC STRT elements which are UNINSULATED.
The display list of template STRU elements suitable for the identified HVAC STRT element to be supported
is controlled by the STRU template UDA’s :MDSRange and :MDSHV.
The controlling attribute which determines whether the HVAC project special is allowed to support
INSULATED and/or UNINSULATED HVAC STRT elements is the UDA :MDSRange stored at the STRU
elements (MDS Project Special Supports) in the HVAC zone named SUPPORT/SPECIALS/BS/HVAC.
• If the :MDSRange UDA at the STRU element is set to ‘1’, then the AVEVA E3D™ Supports Project
Special template will only be allowed on INSULATED HVAC STRT elements.
• If the :MDSRange UDA at the STRU element is set to ‘0’, then the AVEVA E3D™ Supports Project
Special template will only be allowed on UNINSULATED HVAC STRT elements.
• If the :MDSRange UDA at the STRU element is set to ‘2’ or <’any other value’, except ‘0’ or ‘1’> or
left at the default off <unset>, then the AVEVA E3D™ Supports Project Special template will be
allowed on both INSULATED and UNINSULATED HVAC STRT elements.
• The UDA :MDSHV controls whether the HVAC project special is allowed to support HVAC STRT
elements which are ‘HORIZONTAL, ‘VERTICAL’ and ‘HORIZONTAL or VERTICAL’.
• If the :MDSHV UDA at the STRU element is set to ‘HORI’, then the AVEVA E3D™ Supports Project
Special template will only be allowed on HORIZONTAL HVAC STRT elements.
• If the :MDSHV UDA at the STRU element is set to ‘VERT’, then the AVEVA E3D™ Supports Project
Special template will only be allowed on VERTICAL HVAC STRT elements.
• If the :MDSHV UDA at the STRU element is set to ‘BOTH’, then the AVEVA E3D™ Supports Project
Special template will be allowed on both HORIZONTAL and VERTICAL HVAC STRT elements.
• The controlling attribute which determines whether the INSULATION thickness, on the HVAC STRT
being supported, is considered in the build calculations in the design of the AVEVA E3D™ Supports
support is the UDA :MDSCheck. This UDA is also stored at the STRU elements (Supports Project
Special Supports) in the HVAC zone named SUPPORT/SPECIALS/BS/HVAC.
• If the :MDSCheck UDA is set to TRUE, the INSULATION thickness, if any exists on the HVAC STRT
element being supported will be INCLUDED, i.e. taken into account, in the support build calculations
of the AVEVA E3D™ Supports support.
• If the :MDSCheck UDA is set to FALSE, the INSULATION thickness, if any exists on the HVAC STRT
element being supported will be EXCLUDED, i.e. ignored and NOT taken into account, in the support
build calculations of the AVEVA E3D™ Supports support.
All of the Supports HVAC Project Special Support templates MUST be built based on an HVAC STRT duct
size of 500mm wide x 500mm high. The reason for this is so that the GENSEC (SUBS, EXTR or VERT)
members of the project special structure are moved and positioned automatically in a one time ONLY
operation when the template is selected, to suit the size of HVAC STRT being supported.
The way the GENSEC lengths and/or positions are controlled is by the values of two UDAs defined at the
relevant GENSEC elements in the Project Special template structure.
The two UDA’s used at GENSEC, SUBS, EXTR and VERT elements are :MDSConfigA and MDSConfigB.
For example the STRU SUPPORT/SPECIALS/BS/HVAC/1 contains a FRMW with 7<seven> GENSEC
members. Shown below are the UDA settings for GENSEC 1 and 6 only:

GENSEC 1 = SUPPORT/SPECIALS/BS/HVAC/1-BAR-1
:MDSConfigA false,,,\true,0.5\true,0.5
:MDSConfigB unset
GENSEC 6 = SUPPORT/SPECIALS/BS/HVAC/1-V1
:MDSConfigA true,W,0.5,WIDTH\,\true,1
:MDSConfigB unset
MDS Project Special Structural Template MDS Project Special Support copied from the template
SUPPORT/SPECIALS/BS/HVAC/1 configured to SUPPORT/SPECIALS/BS/HVAC/1 and automatically
suit the DEFAULT 500mm wide x 500mm high adjusted to suit the ACTUAL 500mm wide x 300mm
HVAC ducting size. high.
Consider the UDA settings for GENSEC 1 = SUPPORT/SPECIALS/BS/HVAC/1-BAR-1 and interpret what
they mean.
:MDSConfigA false,,,\true,0.5\true,0.5
<see below> 1 2 3
The values in this attribute are delimited into 3 values by the backslash ‘\’ character and further delimited by
the comma ‘,’ character, e.g.
1 false,,, [a,b,c]
false = Element will NOT be repositioned
a) <blank> = a) above is ‘false’, so not applicable
b) <blank> = a) above is ‘false’, so not applicable
c) <blank> = a) above is ‘false’, so not applicable
2 true,0.5
true = Element POSS (GENSEC start position) needs to be repositioned
0.5 = ½(half) the difference between the default size of the HVAC duct (500mm) and the
actual size of the HVAC duct (500mm)

true,0.5
3
true = Element POSE (GENSEC end position) needs to be repositioned
0.5 = ½(half) the difference between the default size of the HVAC duct (500mm) and the
actual size of the HVAC duct (300mm)
:MDSConfigB unset
No action will be taken as the UDA value is unset.
This value will only be set with values of a similar type to those attributed to :MDSConfigA when the element
needs to be moved in more than one direction.
Now, consider the UDA settings for GENSEC 6 = SUPPORT/SPECIALS/BS/HVAC/1-V1 and interpret what
they mean.
:MDSConfigA true,W,0.5,WIDTH\,\true,1
<see below> 4 5 6
The values in this attribute are delimited into 3 values by the backslash ‘\’ character and further delimited by
the comma ‘,’ character, e.g.
4 true,W,0.5,WIDTH [a,b,c,d]
a) true = Element will be repositioned
b) W = The direction in which the element will be moved
c) 0.5 =Move the element 0.5 x WIDTH <value in d) below>

difference between the ACTUAL width and the DEFAULT width of the
HVAC STRT
d) WIDTH = WIDTH or HEIGHT of HVAC STRT element to be considered in c)

above
5 a), b)
a) <blank> = not applicable
b) <blank> = not applicable
6 true,1 [a,b]
a) true = Element POSE (GENSEC end position) needs to be repositioned
b) 1 = 1 x difference between the default size of the HVAC duct (500mm) and
the actual size of the HVAC duct (300mm)
:MDSConfigB unset
No action will be taken as the UDA value is unset.
This value will only be set with values of a similar type to those attributed to :MDSConfigA when the element
needs to be moved in more than one direction.
 At this release the UDAs :MDSConfigA and :MDSConfigB are ONLY considered when copying an
AVEVA E3D™ Supports HVAC Project Special Template.

Exercise 8 – Steelwork Section Size
1. Using the example above change the Steelwork size of an FT09 type support.
2. Create a new FT09 made of 50mm Box Section.

CHAPTER 14
14 AVEVA E3D™ Supports Trunnion Defaults Form
The AVEVA E3D™ Supports Trunnion Data form defines which of the available Trunnion types can be
used on a project, and which Trunnion bore sizes can be used with each pipe bore.
The form also enables the administrator to specify the pipe sizes that the selected Trunnion can be attached
to, and whether the Trunnion material type appears on the piping isometric.
The administrator can also select which Trunnion base plate standards will be available to the designer.
Changes are only applied to the database when the Apply button is clicked. The Cancel button closes the
form. If changes have been made but not applied, a window is displayed asking if the changes are to be
applied before exiting.
Click the Trunnion button from the Standard Defaults group on the SUPPORTS Tab to display the
Supports Trunnion Data form.

Standard Tab
The left hand side of the form lists the available trunnion support types (TT series). When a trunnion name is
highlighted, its support standard name, replacement name and description appear at the top of the form
(described below). This information is outside of the tabbed areas and is displayed on all tabs.
The plot file for the selected standard is displayed on the right of the form. To zoom in on an area of the plot
file, click and drag with the middle mouse button. To restore the original size, use the right click menu and
select Reset Limits.
The Apply button should be clicked before selecting another Trunnion type, otherwise any changes will be
lost.
Support Standard
The Trunnion name selected in the list is copied here and cannot be changed.
modified by editing the text in this field.
Description
The text in this field is configurable to suit each design project; it is displayed to the user in the Model module
and changes the associated Material Take Off (MTO) details on Isometrics and on AVEVA E3D™ Supports
Automatic Drawing Production system.
Active
This option enables the administrator to specify which of the available Trunnion types will be available for
use on the project by the AVEVA E3D™ Supports designer, as follows:
True = trunnion type included in selection lists.
False = trunnion type excluded from selection lists.
This Active setting overrides any subsequent Active setting shown on the Active/Shop Flag tab.
Vendor Reference
Not applicable.

Elevation Restriction
Specifies the elevation (height) at which a trunnion can be created at. For example, setting a value of 5000
means the trunnion can be created at any elevation up to and including 5000mm. If a value of -1000 is entered,
the trunnion can be created at any elevation below 1000mm.
The default setting is *, meaning there is no restriction on the elevation at which the trunnion can be created.
The pipe material is specified here, as follows:
• CS Carbon Steel
• SS Stainless Steel
• FG Fibre Glass
• GV Galvanised
• PL Plastic
• CN Cupro Nickel
• ALL represents ANY material, i.e. valid for all pipe specifications.
This text value, e.g. CS, represents the setting stored at a valid PIPE specification, at the UDA :MDSPipeMat,
for use by the Supports application. These settings are totally configurable and NOT restricted to the example
values shown here.
SKey
SKey Override
Support function
The trunnion support function is specified here. For example, TT for a Trunnion.
By default, ancillary, hanger and trunnion standards are assigned a default support function corresponding
to their standard code. For example, AT, AN, FH, VH, TT, these are fully configurable.
Isometric MTOC Flag
This setting determines whether the material for the AVEVA E3D™ Supports trunnion appears in the material
list of the piping isometric, as follows:
True = trunnion material appears in the isometric material list.
trunnion material does not appear in the isometric material

False =
list.
The Isometric MTOC Flag overrides any subsequent SHOP Flag settings shown on the Active/Shop Flag
tab.

Active/Shop Flag Tab
Active
The setting of these check boxes determines the pipe bore sizes that the selected trunnion type can be
attached to.
When Active is True on the Standard tab, all check boxes are ticked (true) by default, but the administrator
can untick boxes as required for the project.
When Active is False on the Standard tab, this setting overrides all the check box settings, and are treated
as False, even if they are ticked (true).
Shop Flag
The setting of these check boxes determines whether the material for a AVEVA E3D™ Supports Trunnion
appears in the piping isometric material list under the FABRICATION MATERIALS (SHOP TRUE) or
ERECTION MATERIALS (SHOP FALSE) headings of the MTO.
When the Isometric MTOC Flag is True on the Standard tab, all check boxes are ticked (true) by default, but
the administrator can untick boxes as required for the project.
When the Isometric MTOC Flag is False on the Standard tab, this setting overrides all the check box settings
shown on this tab, and are treated as False, even if they are ticked.
User Des Pars Tab
Not used.

Component Selection Tab
Trunnion Sizes and Bore

The size of the pipe (in mm) is specified by clicking the Bore up/down arrows. The available Trunnion bores
for the selected Trunnion type and pipe bore are shown in the Active list.
To make a particular Trunnion bore size available to the Supports designer, click on the item in the Inactive.
list then click on the right arrow icon on the side of the list. This transfers the item to the adjacent Active list.
Clicking on the Left arrow reverses the action.
Each bore for any of the Supports Trunnion types may have one or more Trunnion bores set as the supplied
Supports defaults. The maximum Trunnion bore size is normally one pipe bore size less than the main pipe
bore size.
Trunnion sizes are used to set the Default, Minimum and Maximum sizes for the Trunnion and are described
below.
Select Bore 150
You can see that for a bore of 150mm the Trunnion

size is 100mm.

Make Size 80 active using the Arrow.
Trunnion Base Plate
The available standards for the Trunnion base plate for the selected Trunnion type/Bore are shown in the
Inactive list.
To make a particular standard available to the Supports designer, click on the item in the Inactive list then
click on the right arrow icon on the side of the list. This transfers the item to the adjacent Active list.
Clicking on the right arrow reverses this action.
The Supports Trunnion type will determine if one or more Trunnion base plates are required as the default.
The supplied Supports defaults will take account of this.
Trunnion Sizes
The Trunnion Size is the length of the Trunnion from the bottom of the Trunnion baseplate, (not the bearing
plate) to the centre of the pipe to which it is welded/clamped.
The minimum and maximum trunnion size for the selected Trunnion type and pipe bore can be set here, as
well as the default Trunnion size (length).
Change the Trunnion sizes of the 150NB Pipe Size as shown
Default 300
Minimum 184
Maximum 1000

Exercise 9 - Trunnions
1. Using the example above change the available Trunnion sizes for a 150NB Pipe to include an 80NB
Trunnion.
2. Change the Trunnion Default, Minimum and Maximum sizes.


CHAPTER 15
15 Location Plan, ABA Grid Data
The Supports application contains functionality to include GRIDSY grids (available in MODEL) in the ABA
location plan. The use of SCTN based grid definitions is maintained. The functionality enables the use of
multiple grid systems across the 3D model. Suitable grid systems are automatically selected in the ABA
location plan during drawing generation.
In order to include a GRIDSY grid in AVEVA Catalogue™, it is first necessary to set up a grid in MODEL.
You can define the list of available grids, the pattern for tagging of gridlines (PML expression) and origin of
support coordinates that display on the drawing.
The administration data is stored in the MDSAPPDEFAULTS database below CATA

MDS/ABAGRIDDATA/DEFAULTS.
The default values/settings indicated on the window are those that exist when the Supports application is first
installed.
Click the Location Plan button from the Configuration group on the SUPPORTS Tab to display the Supports
ABA Grid Data form.
Changes made are only applied to the database when Apply is clicked. To keep the changes the Save Work
operation must to be performed.
Click Dismiss to close the window. If changes have been made, but not applied, a window displays asking if
the changes are to be applied before exiting.

Gridline Tag Patterns
The gridline tag patterns allow you to customise the way in which grid data is tagged within the ABA location
plan which is created in the DRAW application. PML expressions can be input into the GRDLN Tag and SCTN
Tag fields which are evaluated against the selected gridlines.
Expressions are evaluated against the X and Y gridlines that are automatically selected when generating the
support, such expressions can therefore comprise of any of the gridline attributes or any attribute from the
hierarchy above (provided that STRING output is maintained).
When the ABA location plan is created, the result is written into the ATEXT attribute of a SLAB. It can contain
explicit sequences that have special meanings in DRAW, for example '/#' which is interpreted as a newline
character and splits the resulting text into two lines.
Support Datum Origin Coordinates
The support datum origin coordinates settings allow you to define the calculation process for the support datum
dimensions used in the ABA location plan in the DRAW application.
The Support Coordinates Origin drop-down list contains the following types of support datum calculation:
• Matching Grid - The origin of the selected grid is used.
• Zone, Site, World - The origin of the specified element in the hierarchy above the support is used.
• Named Item - The origin of the specified named item in the design database is used.
List of Valid Grids
You can define the available grid systems for use with the ABA location plan.
To add a grid to the list of valid grids, select the grid (GRIDSY, STRU or FRMW grid element) to be added on
the Catalogue Explorer and click ADD CE.
Click Remove Selected to delete the currently selected grid from the list of valid grids.

CHAPTER 16
16 Ancillary Selection Criteria
Sets user defined ancillary selection criteria for the generation of supports. These criteria are used in addition
to the standard checks that are performed on ancillaries when they are created. For example, bore,
temperature and material checks.
The administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/SELECTION-
CRITERIA.
The default values/settings that display on the windows are those are those that exist when the Supports
Click Reset to revert the User Defined Ancillary Selection Criteria window to the default values/settings.
Click the Ancillary Selection Criteria button from the Configuration group on the SUPPORTS Tab to display
the User Defined Ancillary Selection Criteria form.
operation must be performed.
Click Dismiss to close the window. If changes are made, but not applied, a window displays asking if the
changes are to be applied before exiting.

Temperature Check
You can override the default temperature check that is performed at branch level.
For example, the temperature check can be modified to be carried out at pipe level by changing the expression
field to temp of PIPE.
The validity of the PML expression is checked by AVEVA Catalogue™, if an error is detected an error message
displays and the Expression field is highlighted.
User Defined Criteria
You can input customised ancillary checking expressions in the Criteria 1 to 5 fields.
For example, the paint code of a branch can be specified, the user is then only able to create the ancillary if
the paint code matches that defined in the PML expression.
Input an ancillary selection criteria description in the Description field.
Input a valid PML expression in the Expression field.
Tick the Active check box to activate the ancillary selection criteria.

The supports hierarchy is separate from the branch and pipe. The initial element expected in the criteria
expression is the SUPPO element. The previous component on the selected branch, nearest to the SUPPO
element is represented by the compref attribute on the SUPPO.
User Defined Functions
In addition to the standard expression functionality, it is also possible to create a user defined function to
perform more advanced checking.
You can assign a user defined check function to the Criteria fields. The value in the expression field is the full
function call to the user defined function. For example, the expression can be called !!checkCriteria1().
User Defined Check Function - Creation and Usage Rules
The following rules must be observed when assigning a function:
• The function entered in the expression field must be in the correct format. For example,
!!functionName()
• The user defined function file must have a BOOLEAN return type. For example, the function file
definition must in the following format:
Define function !!functionName() is BOOLEAN
• The function cannot be called with any arguments. For example, the function brackets must be empty.
• When the user defined check function is run, the current element is the datum support of the pipe so
all processing must be done on this basis. For example, to interrogate the branch the following
commands can be used.
If !!ce.compref.type.eq(‘BRAN’) then
!bran = !!ce.compref (if the compref is the branch itself)
else
!bran = !!ce.compref.owner (if the compref is a branch component)
Endif
User Defined Check Function - Example Listing

The example user defined check function enables the user to create a support only when the paint spec of the
branch is either '12345-STD-PIP-001-RAL1069' or '12345-STD-PIP-001-RAL1070'.
define function !!checkCriteria1() is BOOLEAN

--get the paint spec of the pipe branch
var !paintSpec ptsp of bran of compref
--make sure that the paint spec of the of the pipe is one of the types specified below
if !paintSpec.neq('12345-STD-PIP-001-RAL1069') and
!paintSpec.neq('12345-STD-PIP-001-RAL1070') then
return FALSE
else
return TRUE
endif
endfunction

The user defined check function must be created in a standard text file. As the function name is checkCriteria1
the file should be saved as checkcriteria1.pmlfnc
It is recommended that check functions are saved in a separate folder to AVEVA E3D™ and that the pmllib
environment variable in AVEVA E3D™ startup is modified to point to it.
For example:
Create a folder called pmllib in c:\userpml\
Save checkcriteria1.pmlfnc to c:\userpml\pmllib\
Modify the environment variable for pmllib to add this new search path. For example:
set pmllib= c:\userpml\pmllib;%PMLLIB%
Enter MODEL, type PML REHASH ALL into the command line and press Enter. The pml index is updated
allowing the user defined file to be used.
Refer to the Using PML in AVEVA Products for further information regarding PML customisation.

Exercise 10 - Ancillary Selection
Restrict the selection of Ancillaries to Pipes where the Pipe Bore is Greater than 40mm, this would be useful
if the small bore pipes are to be site supported.
Hint ( ATTRIB BORE OF PIPE OF COMPRE GT 40 )
 When the check is done the Designer will be at an Ancillary.
In Model check that Supports can only be added to Pipes with a bore greater that 40mm


CHAPTER 17
17 Compensation Plates
The Supports application contains functionality to enable the creation and modification of compensating plates
in order to fill any gaps between frameworks and ancillaries. In order to create compensating plates within
MODEL, it is first necessary to set up a number of administrative options.
The administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/COMPENSATING-
PLATES/DEFAULTS.
Compensation Options
Click the Options button from the Compensating Plates group on the SUPPORTS Tab to display the
Supports Compensation Options form.
Setting of the minimum and maximum gap sizes and the calculation process for plate thicknesses and
rounding distances can be done through this form.
installed.
Clicking the Reset button reverts the Supports Compensation Options window to the default
values/settings.
Clicking Dismiss button closes the window. If changes have been made, but not applied, a window displays
asking if the changes are to be applied before exiting.

Gap
The gap settings allow you to define when a compensation can be used and which type of compensation to
use in a particular situation.
It is also possible to define the maximum gap for a plate to be used. If the gap is between the maximum for a
plate and the maximum for a profile, then a compensating profile (FIXING) is created.
The dimensional value of the Minimum field defines the minimum space required for the user to create a
compensating plate. If the gap is less than this value then it is not regarded as a gap and no compensation is
created.
The dimensional value of the Maximum for Plates field defines the maximum space required for the user to
create a compensating plate. If the gap is equal or less than this value (and not less than the Minimum) then
plates (PANE) are created to fill the gap.
The dimensional value of the Maximum for Profile field defines the maximum space required for the user to
create a compensating profile. If the gap is equal or less than this value but greater than the maximum value
for plates, then a profile (FIXING) is placed to fill the gap.
Plate Thickness
The plate thickness settings allow you to define the calculation process for the thickness of the compensating
plate.
The Calculation Method drop-down list contains the following types of plate thickness calculation:
• Greater or equal to the gap - The overall thickness of all plates must either fit the gap or overlap it.
There must be no remaining gap.
• Less or equal to the gap - The overall thickness of all plates must never overlap the gap. Plates either
fit the gap or some gap remains.
• Closest to the Gap - There can be either an overlap or a gap remaining, Plates of thicknesses are
selected so the overall thickness is as close to the gap size as possible.
The Visually Accommodate option can be set to either On or Off using the drop-down list. If there is a gap or
overlap, the actual thickness of the top plate can be accommodated so that it fits the gap. Adding an extra
design parameter to the plate alters the height.
Rounding
The rounding settings allow you to define the calculation process for the rounding of the compensating plate.
The X and Y values for the compensating plate are the length and width values. In order to obtain these sizes
a calculation can be performed, refer to Compensation Sizes for further information.
After the X or Y size of the compensating plate is calculated, it is rounded according to the specified
parameters.
The Calculation Method drop-down list contains the following types of rounding calculation:
• Always Up - The resulting value from the calculation is always rounded upwards. For example, if the
resulting X size is 33mm and the rounding X value is set to 10mm then it is rounded up to 40mm
• Always Down - The resulting value from the calculation is always rounded downwards. For example,
if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded down to
30mm.
• To Closest Value - The resulting value from the calculation is rounded to the nearest number. For
example, if the resulting X size is 38mm and the rounding X value is set to 10mm then it is rounded
up to 40mm.

The X-size value and Y-size value fields allow you to define the nearest value to round to.
For example, an X-size value of 10mm rounds the result to the nearest 10mm.
To disable rounding, set the X and Y size values to 0mm.
Compensation Sizes
Click the Sizes button from the Compensating Plates group on the SUPPORTS Tab to display the Supports
Compensation Sizes form.
Setting the rules that are used to calculate both the X and Y sizes of the compensating plate can be done
through this form.
installed.
Clicking the Reset reverts the Supports Compensation Sizes window to the default values/settings.
Clicking the Dismiss button closes the window. If changes have been made, but not applied, a window
displays asking if the changes are to be applied before exiting.
The Supports Compensation Sizes window contains two tabs for specifying separate rules to calculate the
X and Y sizes of the compensating plate.
The General Rule is used when a rule for a given support type is not defined.
The Default Value field defines the default X and Y sizes of the compensating plate.

Rules can be created for specific support types, input the support codes into the support code field, separated
by a space. An asterisk can be used to identify all support types. If two rules are defined for the same support
type, the first rule in the list for that support type is used and the second is ignored.
A rule must always be a PML expression that returns a REAL value upon evaluation. If the expression contains
references to attributes or properties, the expression is evaluated against the ANCI of the support. Therefore
it can contain any attribute or property which is available on the ANCI element.
To access the width of the GENSEC supporting the ANCI, the syntax 'VVAL( !WIDTH)' can be included into
the expression. The profile width in this context is the width of the GENSEC face below the ANCI depending
on the profile rotation and may not necessarily correspond to the catalogue property WIDT.
If the evaluation of the rule expression fails, then the explicitly set default value is used instead.
To add a new rule to the list of available rules, click Add Entry button to display the Add Entry window.
You can populate the Support Codes and X-Size Rule or Y-Size Rule fields with the relevant rule values.
Click OK to add the rule to the list of available rules or Cancel to discard any changes and close the Add
Entry window.
Click Remove Entry button to delete the currently selected rule.
Compensation Plate Material
Click the Materials button from the Compensating Plates group on the SUPPORTS Tab to display the Set
Compensation plate Materials form.

Setting of the available materials for a compensating plate can be done through this form.
The default values/settings indicated on the window are those that exist when the supports application is first
installed.
Clicking the Dismiss button closes the window. If changes have been made, but not applied, a window
displays asking if the changes are to be applied before exiting.
The Set Compensation plate Materials window contains two lists, the first lists the different possible choices
of materials and the second lists the available materials.
To set a material choice, select the appropriate choice from the list of available choices and then select the
material for that choice from the list of available materials.
Duplicate choices are omitted from the material selection drop-down list in MODEL.
The default choice is the material that is initially set when a compensation is created. It is not possible to
remove the default choice.
The available materials that can be assigned to a choice are populated from the MDS/PROP database and
only solid materials are available for selection.


CHAPTER 18
18 User Defined Ancillary
The Supports application allows the Supports administrator to create a set of ancillary standards with their
own geometry. Configuration of standards dimensionally is covered in Supports Ancillary Defaults form
which can be accessed via the Ancillary button located in the Standard Defaults group.
The term ‘user’ in this section is the term used to represent ‘client/customer’.
To create user defined component for use with the AVEVA E3D2.1 Supports application, two specific areas
must be addressed.
1. Catalogue Selection activation / settings
This is an Administrative task with the Paragon module requiring write access to:
a. Application support defaults database containing the activation and size range settings
b. The User defined component database containing the geometry of the user defined
component
2. User interface configuration
This section addresses the configuration of the user defined images / diagrams and dimensions displayed
within the AVEVA E3D2.1 Supports application.
This is managed via the Dimension Control Designer and using the SupportConfiguration.xml
configuration where User Defined .png files can be used to display the company specific defined standards.
The user defined ancillary standards comprise a number of support types. The following table shows the user
defined ancillary types that have been created and which can be configured geometrically:
Standard Description Range From To Total

AT Ancillary AT500 AT700 201
LT Lug LT500 LT700 201
BT U-Bolt BT500 BT700 201
AN Anchor for shoes AN500 AN569 70
AN Anchor for pipes AN570 AN639 70
AN Anchor for Trunnions AN640 GT700 61
GT Guide for shoes GT500 GT569 70
GT Guide for pipes GT570 GR639 70
GT Guide for trunnions GT640 GT700 61
ST Stops for shoes ST500 ST569 70
ST Stops for pipes ST570 ST639 70
ST Stops for trunnions ST640 ST700 61

The ability to create these user defined ancillary types is achieved by AVEVA E3D™ Supports being
configured to use a blank set of ancillaries of the above types, so that users can complete their own geometry.
The MDU/CATA database has been copied from AVEVA Sample Project (APS) into the current
Training Project to allow modification. A hierarchy /MDU prefix is used instead of the /MDS prefix
where applicable.
The MDU/CATA database has the geometry and point sets pre-created and linked into the AVEVA E3D™
Supports catalogue and specification. The geometry sets are empty and the point sets have the minimum p-
point requirements for AVEVA E3D™ Supports. The geometry can then be created within the MDU/CATA
database and any design parameters required for the component can be set up. The MDU/CATA database
only stores geometry, point and data sets for the types and ranges detailed below.
Geometry Sets
The geometry sets have been created in database MDU/CATA. The following section shows what has been
added and detail any properties that are being used. The AVEVA E3D™ Supports administrator can add
geometry using these properties if needed and add additional properties as necessary.
AT500 to AT700, BT500 to BT700, LT500 to LT700
Simple Box Representation.
This is set to a length of 10, and uses the pipe outside

diameter (OD) as the x and y length.
The three standard catalogue parameters have been

added, nominal bore (NB), outside diameter (OD) and
connection type (CONN) and 25 design parameters
have been created.

The following are the parameters that have been pre-set, i.e. to -1. All other design parameters are set to 0
(zero), as shown in the form displayed above.
Number Description Dkey
22 Minimum Insulation MNIN
23 Maximum Insulation MXIN
24 Minimum Temperature MINT
25 Maximum Temperature MAXT
No user editable design parameters have been defined.
AN500 to AN569 Anchor for Shoes

Simple Anchor Representation.
These user standards are created using Add

Associated Ancillary on the Support Editor form.
The shoe parameters HEI (shoe height) and WID

(flange width) are used in order to size the anchor.
It will then ask for a section or box to be identified
to read the anchor width across the section of box.

The three standard catalogue parameters have been added, nominal bore (NB), outside diameter (OD) and
connection type (CONN) and 25 design parameters have been created.
The following lists the parameters that have been preset, i.e. to -1, 100, 102 and 165. All other design
parameters are set to 0 (zero), as shown in the Properties form.
1 Associated Shoe Height HEI
2 Associated Shoe Flange Width WID
3 Support Beam Flange Width SBFW
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000)
and default values have been added as shown.

AN570 to AN639 Anchor for Pipes
Simple Box Representation.

have been created.
The following lists the parameters that have been pre-set i.e. to -1. All other design parameters are set to 0
(zero), as shown in the Properties form.
No user editable design parameters have been defined.

GT500 to GT569 Guide for Shoes
Simple Guide Representation.
These user standards are created using
Add Associated Ancillary on the Support Editor

Form.

(flange width) are used in order to size the guide.
The following lists the parameters that have been preset, i.e. to -1, 100 and 102. All other design parameters
are set to 0 (zero), as shown in the Properties form.
3 Clearance CLR
4 Length LEN
Design parameters 1, 2, 3 and 4 have been declared as user editable (with an allowable range of 0 to 1000)

GT570 to GT639 Guide for Pipes

have been created.
The following lists the parameters that have been preset, i.e. to -1 and 0. All other design parameters are set
to 0 (zero), as shown in the Properties form.
1 Height HEI
2 Width WID
3 Clearance CLR
4 Length LEN
Design parameters 1, 2, 3 and 4 have been declared as user editable (with an allowable range of 0 to 1000)

ST500 to ST569 Stop for Shoes
Simple Stop Representation
These user standards are created using Add

Associated Ancillary on the Support Editor Form.

(flange width) are used in order to size the anchor. It
will then ask for a section or box to be identified to
read the anchor width across the section of box.

have been created.
The following lists the parameters that have been preset, i.e. to -1, 100 102 and 165. All other design
parameters are set to 0 (zero), as shown in the Properties form.
3 Support Beam Flange Width SBFW

ST570 to ST639 Stop for Pipes
Simple Box Representation

have been created.
The following lists the parameters that have been preset, i.e. to -1. All other design parameters are set to 0
(zero) as shown in the Properties form.

AN640 to AN700 Anchor for Trunnions
Simple Anchor Representation.
These user standards are created using Create Base

Component on the Support Editor form.
The following lists the parameters that have been pre-set. The plate length (PLEN), plate width (PWID) and
plate thickness (PTHK) will be obtained from the identified base plate, i.e. to -1. All other design parameters
are set to 0 (zero) as shown in the form displayed above.
1 Plate Length PLEN
2 Plate Width PWID
3 Plate Thickness PTHK
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and
default values have been added as shown.

ST640 to ST700 Stop for Trunnions
Simple Stop Representation.


have been created.
The following lists the parameters that have been preset. The plate length (PLEN), plate width (PWID) and
plate thickness (PTHK) will be obtained from the identified base plate. All other design parameters are set to
0 (zero) as shown in the form displayed above.
1 Plate Length PLEN
2 Plate Width PWID

GT640 to GT700 Guide for Trunnions


have been created.
The following lists the parameters that have been preset. The plate length (PLEN), plate width (PWID) and
plate thickness (PTHK) will be obtained from the identified base plate. All other design parameters are set to
0 (zero) as shown in the form displayed above.
1 Plate Length PLEN
2 Plate Width PWID
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and
default values have been added as shown.

Point Sets
These have been created with the minimum points required by AVEVA E3D™ Supports. These are:
P-Point Description
1 Arrive Point
2 Leave Point
3 Bottom of Pipe (BOP) -5mm, i.e. bottom of the ancillary geometry -5mm
9 BOP (Including geometry if required), i.e. bottom of the ancillary geometry
10 Left of Pipe
11 Right of Pipe
12 BOP
The diagram below shows the position and directions of the p-points, P1 and P2 are arriving and leave points
along the centreline of the pipe.
 The AVEVA E3D™ Supports default p-points provided cannot be deleted or modified, but additional
ppoints can be created if required.

Data Sets
These have been created with the minimum number of elements required by AVEVA E3D™ Supports. These
are:
Data Name Description DataKey DefaultProperty
/Prefix-DESC Support Standard DESC 'AT500'

(BEF (AFT (ATTRIB PPRO of DATA
Standard Replacement
/Prefix-RNAM RNAM /MDS/ATTA/DEFAULTS/AT500/GEN/CCOD , ‘(‘’’)
Name
, ‘’’ )’ ) )
/Prefix-PA1 Nominal Bore NB PARA 1
/Prefix-PA2 Outside Diameter OD PARA 2
/Prefix-PA3 Connection Type CONN PARA 3

( ATTRIB DENS of 1 OF 1 of :MDSMatRef *
/Prefix-WEIG Component Weight WEIG ATTRIB NVOL / 1000 / 1000 / 1000 * VVAL
!!MDSWEIUNIT )
( ATTRIB DESC of :MDSMatRef )
/Prefix-MATR Component Material MATR
( TRIM ( DIST ( NOMBORE ( false, ATTRIB

/Prefix-CODE Support Code CODE CPAR[1 ] ) , false , false , true , 4 , false ) ) + '-' +
ATTRIB PROPRNAM)
(BEF (AFT (ATTRIB PPRO of DATA
MDS Configurable /MDS/ATTA/DEFAULTS/AT500/GEN/DESC , ‘( ‘’’ )
/Prefix-CDES CDES
Description ‘’’ ) ) )
/Prefix-DP1 Design Parameter 1 Unset DESP[1]
Where /Prefix is /Standard-DATA- e.g. /AT500-DATA-DESC and the standard used as an example above is
AT500.
The Supports administrator can add/modify the data set as necessary.
Project Catalogue for User Defined Ancillaries
The catalogue items for the user defined ancillaries have been created in the ranges detailed below within the
MDU/CATA database in AVEVA Sample project (APS). This database contains all the catalogue elements,
i.e. SCOM, GMSE, PTSE, DTSE and SDTE, where the user will modify the GMSE to suit their requirements.
The specification components for ALL the user defined ancillaries are in the /MDS specification in the AVEVA
E3D™ Supports project, which MUST NOT be modified by users.
Current Range AVEVA E3D™ User Range AVEVA E3D™
Standard Description Supports Project Supports Project
From To From To
AT Ancillary AT01 AT115 AT500 AT700
LT Lug LT01 LT16 LT500 LT700
BT U-Bolt BT01 BT11 BT500 BT700
AN Anchor AN01 AN18 AN500 AN700
GT Guide GT01 GT50 GT500 GT700
ST Stop ST01 ST33 ST500 ST700

The MDU/CATA catalogue hierarchy has been created as shown on the previous page for a size range of
8mm (1/4") to 1200mm (48") in the bore sizes shown below:
Metric NB Imperial NB Actual OD OD

8 1/4 13.7 14
15 1/2 21.3 21
20 3/4 26.7 26
25 1 33.4 33
32 1.1/4 42.2 42
40 1.1/2 48.3 48
50 2 60.3 61
65 2.1/2 73 73
80 3 88.9 89
100 4 114.3 115
125 5 141.3 141
150 6 168.3 169
200 8 219.1 220
250 10 273 273
300 12 323.8 324
350 14 355.6 358
400 16 406.4 407
450 18 457 457
500 20 508 508
550 22 559 559
600 24 610 610
650 26 660 660
700 28 711 711
750 30 762 762
800 32 813 813
850 34 864 864
900 36 914 914
950 38 965 965
1000 40 1016 1016
1050 42 1067 1067
1100 44 1118 1118
1150 46 1168 1168
1200 48 1219 1219

Modifying the User Defined Ancillary Standard
The administrator uses the standard PARAGON Pipework Application to modify the required elements within
the MDU catalogue database, i.e. MDU/CATA
Within the MDU/CATA database, the following should not be deleted or modified (including name change):
CATREF (Catalogue Reference)
PTREF (P-Point Set Reference) (see Note below)
GMREF (Geometry Set Reference) (see Note below)
DTREF (Data Set Reference) (see Note below)
 Although the MDU/CATA default p-points provided cannot be deleted or modified, additional p-points
can be created. Also, geometry can be added to the geometry sets, and additional properties included
as necessary.
Example User Defined High Pressure Support.
The following is an example of a simple High Pressure Support.
 Some basic Piping Cats and Specs knowledge is assumed during this example.
Modifying the support geometry

The support designer can create any shape but it should
be kept simple.
Enter the Paragon Module of the Training

Project as a Support Administrator using the
following details.
Username: A.SUPPORTADMIN
Password: A
MDB: A-SUPPORTS
Module: Paragon
Click the Paragon Tile.

From the Catalogue Explorer, navigate to support CATE

ATTA-AT501.
Enter the Piping application Select PIPING for the Application

Pull-down
Select Category from the Modify Group of the CATALOGUE Tab.
The Support can now be modified as required to suit the Project requirements. Navigate to AT501-4.100 from
the bottom section of the Model View window.

It is normal practice in AVEVA E3D™ Supports to use Design Parameters or Real Properties to define the
component.
For example:
RPROP DEPA (Design Para 1) - Width

RPROP DEPB (Design Para 2) - Thickness
RPROP DEPC (Design Para 3) - Height
RPROP DEPD (Design Para 4) - Bolt Diameter and Height
Several dimensions will be assumed based on calculations from the above.
Update the Category Dataset Descriptions by navigating to the Data Set from the Model References window
of the Model View Form.

Select Model Parameters from the Settings Group of the CATALOGUE Tab
Set the Design Parameters as shown using Insert:
Design Para 1 – 300
Design Para 4 - 30
Select Only Update Catalogue Parameters
Open up the Model View window again by selecting Category from the Modify Group of the CATALOGUE
Tab.
Modify Point 3 – Distance to (RPROP DEPC / 2 + 0.5) by navigating to the Point Set from the Model
References window of the Model View Form.
Then update the following distances.
Point 9 – Distance ( RPRO DEPC / 2 )
Point 10 – Distance ( RPRO DEPA / 2 )
Point 11 – Distance ( RPRO DEPA / 2 )
Point 12 – Distance ( RPRO DEPC / 2 )

Create the following Points to position the Bolt.
Point 31 – PTCA
Direction Z
PX (RPRO DEPA / 3)
PZ (RPRO DEPC / 2)
Point 32 – PTCA
Copy Point 31
Direction -X
Point 33 – PTCA
Direction Z
PX (- RPRO DEPA / 3)
PZ (RPRO DEPC / 2)
Point 34 – PTCA
Copy Point 33
Direction -X
Update the following Geometry.

SBOX 1
PXLE (RPRO DEPA)
PYLE (RPRO DEPB)
PZLE (RPRO DEPC)
Create the following geometry for the Bolts
SCYL
PAXI P31
PHEI (RPRO DEPD +

RPRO DEPD / 4)
PDIA (RPRO DEPD)
COPY of prev SCYL
PAXI P33
SEXT
PAAX P32
PBAX P1
PHEI (RPRO DEPD)
Click the Modify Points button to create the vertices of the SLOO as shown

COPY of prev SEXT
PAAX P34

User Define Support Activation
The new User Defined Support requires activation in the Training project.
Select Ancillary button in the Standard Defaults group of the SUPPORTS Tab to display the Supports
Ancillary Data form.
On the Standard tab select support AT501.
Enter a new Description of High Pressure Support.
Select the Support Class ANCHOR.
Select True radio button on the Active section.
On the Active / Shop Flag

tab.
Select the Bores as shown

from 25 to 300.
Excluding Bores 32, 65 and

125.

Use the Size tab to set the four parameters Width, Thickness, Height and Bolt Dia using the values shown
below on the table.
Click the Apply button and then Save Work.
Nom Bore Width Thickness Height Bolt Dia/Hei

25 100 50 50 15
40 140 80 80 20
50 150 100 100 20
80 300 100 160 20
100 300 100 200 30
150 300 100 300 30
200 300 200 400 40
250 300 200 500 40
300 900 300 600 50
Support Compatibility is used to define associated ancillaries. Initially this will be left Blank it will be explained
and used later in this Training

This High Pressure Support needs to be set as a Primary Support which cannot be used on a Framework or
on a Vertical Pipe.
This can be done through the Selection Configuration tab of the form as shown below.
 Notes:
Databases MDS/MDSAPPDEFAULTS and MDU/CATA, it is recommended that these databases are

copied to a customer’s master project or the current project itself. The masters issued in AVEVA project
should not be modified.
Geometry Sets, elements can be created, change or deleted below the existing geometry set.
Point Sets, the default set of point are already created and should not be deleted or modified. Additional
points can be added that may be required to help with geometry creation.
Data Sets, the default set of properties are already created and should not be deleted or modified.
Additional properties can be added as required.

User interface Configuration
The User interface can be customised to include Graphics that

have optional Dimension controls.
The Graphics are drawn using a suitable graphical editor for

example Paint. Dimensions are added using the AVEVA
Dimension Control Designer and the information is stored in an
xml file called supportconfiguration.xml.
Support Configuration xml file

The location of the supportconfiguration.xml is controlled by the environment variable
MDS_SUPPORT_CONFIG_LOCATION, by default this is set to the installation directory in the file evar.init.
For example set MDS_SUPPORT_CONFIG_LOCATION=%aveva_design_installed_dir%
Typically C:\Program Files (x86)\AVEVA/Everything3D2.10
A copy of the SupportConfiguration.xml file should be stored in a suitable project file location with write
access.
Create a new folder C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config
Copy the file SupportConfiguration.xml
From C:\Program Files (x86)\AVEVA\Everything3D2.10
To C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config

Modify the environment variable MDS_SUPPORT_CONFIG_LOCATION to point at this new location. This in
normally done in the custom_evars.bat file which is found in the Projects folder typically
C:\Users\Public\Documents\AVEVA\Projects
Edit the file custom_evars.bat and add towards the bottom of the file the line: -
set MDS_SUPPORT_CONFIG_LOCATION=C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config
Support Graphics
Using a suitable editor for example Paint draw the Support AT501 on a 200x200 canvas, make it simple but
representative.
The graphic should be saved as a png file in the same Folder and the Support Configuration file i.e.
C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config in this case at501.png.

Dimension Control Designer
Open the Dimension Control Designer (DimensionControlDesigner.exe) found in the E3D2.1 program
folder.
Typically, C:\Program Files (x86)\AVEVA/Everything3D2.10
Open the new configuration file SupportConfiguration.xml file using the file menu.
Select File > Open
Navigate to
C:\AVEVA\Plant\PlantTraining2.1\Training\
mds_support_config
Select SupportConfiguration.xml and Open

Enter AT501 in the Mapping name field and click the Create button to add this user defined support to the
Current Mapping list.
To be able to display the picture, the image id on the left side should be changed from <Image
id="at501_dim”/>to <Image id="at501.png" />.
After clicking File > Save Pick OK
The image will be displayed.

There is one Dimension Box with a Dimension ID of distance this is used by the system to position the
supports along the Pipe.
The Position of this Dimension Box in the Graphic can be changed by clicking on the Dimension Box and
using the arrows to change is position.
Save the Support Configuration File and confirm it is to be overwritten.
Testing the User Defined Support in Design
The support ancillary created above can be used on any Carbon Steel pipe.
Enter Model and add Pipe 02200-B-42 belonging to zone ZONE-PIPING-AREA02-WORKSHOP to the 3D
View.
Enter AVEVA E3D™ Supports, select Ancillary button, select the pipe and then select XAT501 from the
Ancillary Selection form and position it on the pipe.

Creating Secondary User Defined Supports
In the following example a SHIM is added to the High Presure Support AT501 created prevously. AT502
Packer for High Presure Support is a secondary support off an AT501.
Modify AT502 Geometry
In Paragon Navigate and Modify
CATE ATTA-AT502
Set the Design Parameters
DESPA1 100
DESPA2 300
DESPA3 100
DESPA4 100
Select Only Update Catalogue

Parameters
Update the Data Set with changing the Description of the following Design Parameters:

DEPA -Distance to Top
DEPB -Width
DEPC -Depth
DEPD -Height
Key -HEI
 HEI will be used later

by the Dimension
Control.
Select Geometry and update the SBOX.
Repr Piping Detail
Obstruction Hard
X Length (RPRO DEPB)
Y Length (RPRO DEPC)
Z Length (RPRO HEI)
Z Co-ordinate ( - ( RPRO DEPA + RPRO HEI / 2 ) )
User Define Support Activation (AT502)
The new User Defined Support requires activation in the Training project.
Select Ancillary from the Standard Defaults of the SUPPORTS Tab of the SUPPORTS discipline.
On the Standard tab select support AT502.

Enter a new Description of High Packer for High Pressure Pipe.
Select the Support Class SHIM
Change Active to True.
On the Active / Shop Flag tab.
Select the Bores as shown from 25 to 300. Excluding Bores 32, 65 and 125.
Use the Size tab to set the four parameters Distance to Top, Width, Depth and Height using the values
shown below on the table.
Click the Apply button and then Save work.

Nom Bore Distance to Top Width Depth Height

25 25 100 50 25
40 40 140 80 40
50 50 150 100 50
80 80 300 100 80
100 100 300 100 100
150 150 300 100 150
200 200 300 200 200
250 250 300 200 250
300 300 900 300 300
User Define Design Parameters (AT502)
Design Parameter 4 is being used to set the Height, the value range for each Bore size must be specified.
Select User Des Pars tab.

Click New User Editable Design Parameter
Enter Design Parameter Number 4 and Click OK
Bore Des par 4 Min Des par 4 Max

Specify the Minimum and Maximun values of Height 25 10 100
(despa4) for each bore. 40 10 100
50 10 150
80 10 150
100 10 200
150 10 200
200 10 200
250 10 300
300 100 300
Click the Apply button and Save Work.

This is a secondary Support for AT501 so will need no associated support classes.
As the form shows this packer is NOT a Primary Support and cannot be used on a Framework or on a Vertical
Pipe.

Adding Support Compatabilty to AT501
In this example AT502 is a secondary support of AT501.
Select AT501 and select the Support Compatibility tab, select Support Class SHIM from the Available
Support Classes and use the arrow to move SHIM to the right into Compatible Support Classes.
Select all the Compatible Ancillaries with exception of AT502 and use the arrow to move them to the
right into Restricted Ancillaries.

Click the Apply button and Save Work.
Support Graphics
Using a suitable editor for example Paint draw the Support AT502 on a 200x200 canvas.
The graphic should be saved as a png file in the same Folder and the Support Configuration file i.e.
C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config in this case at502.png.
Dimension Control Designer
Open the Dimension Control Designer (DimensionControlDesigner.exe) found in the E3D2.1 program
folder.
Typically C:\Program Files (x86)\AVEVA\Everything3D2.10
Open the new configuration file SupportConfiguration.xml file using the file menu.
Select File > Open Navigate to C:\AVEVA\Plant\PlantTraining2.1\Training\mds_support_config
Select SupportConfiguration.xml and Open
Enter AT502 in the Mapping name field and click the Create button to add this user defined support to the
Current Mapping list.

To be able to display the picture, the image id on the left side should be changed from <Image
id="at502_dim”/>to <Image id="at502.png" />.
After clicking File > Save Pick OK
The image will be displayed.

In the Add Dimension Box type hei and click the Add button.
 Dimension hei is added to the xml and a box is shown on the centre of the graphic.
Position the new dimention hei on the graphic as shown below using the Arrows.
Click File > Save.
Pick OK

Configuring the controls on the Support Editor Form
When creating a new ancillary, it is necessary to configure the controls on the Support Editor form. This can
be done by modifying one of the six object files located in the software program directory
\PMLLIB\supports\design\objects.
It is intended to add these setting to the paragon administration forms in a future release of AVEVA E3D™.
The file to edit will depending on what type of support has been added.
mdsSupportEditorCtrlConfig??.pmlobj
Please substitute?? for AN, AT, BT, GT, LT or ST
It is recommended that these pml files are copied to a company/project specific folder, the variable “pmllib”
updated and that the originals are not modified
The following is an example of file mdsSupportEditorCtrlConfigAT.pmlobj showing AT501 and AT502. For the
purposes of the Training the configuration file will remain unchanged.

Testing the User Defined Support in Design
The Support Ancillary created above is used in conjunction with AT501.
Enter Model and add Pipe 02200-B-42 belonging to zone ZONE-PIPING-AREA02-WORKSHOP to the 3D
View. Modify the previously created AT501.
Supports can be added by selecting 3D View > Add

Supports on the Model Explorer.
Using the Support Editor form, select Add Associated

Ancillary.
Select AT502 and click the OK button.

The SHIM Height can be changed from the default of 300mm.

Exercise 11 – User Defined Support Ancillaries
1. Using the above example modify Support AT501, customise the user interface and position it on a pipe
in Model.
2. Activate and customise the interface for AT502, position it in the model using and appropriate AT501.
3. Make Support AT501 available for use on both Carbon Steel and Stainless Steel Pipes; remember to set
both the Pipe Specification Material Code and the Propcon – AVEVA E3D™ Supports Ancillary Material.
4. Activate U-Bolt BT501 and use it on a Carbon Steel Pipe.

CHAPTER 19
19 Supports- Auto Naming
An auto naming facility is available in the project default area (tradflts), which is common to multiple users.
By default, the DES-SUPP-NAMES auto naming file is used, but users can select any other available auto
naming file with the DES-SUPP-NAMES prefix, for example the naming file for Area 32 may be called DES-
SUPP-NAMES-32
Usage and Auto Naming File Selection
To select an auto naming file, select Autoname from the Settings group on the
SUPPORTS tab in AVEVA E3D™ Supports Model to display the Supports
AutoNaming File form.
The Supports AutoNaming File form allows the user to

select a different Auto Naming file for the session or to set
a different Auto Naming file, stored against the Default
Zone.
This is done by clicking the Set AutoNaming File to

Default Zone button. The Auto Naming file is stored in a
UDA named :MDSAutofile at the Zone level.
The Auto Naming file shows several naming files.

The default file uses the concept of a prefix, index, and
suffix value. An example of the contents of the file are
shown below; the Administrator may change these values
or create another file with the DES-SUPP-NAMES prefix.

The default file can also use an index that starts at a value named MinIndex and up to a value called MaxIndex.
This allows the user to have a predefined range of support numbers.
Another value stored in this file is called the IWidth. This allows a predefined format for the support number
i.e. when IWidth is set to 5 the support number contains 5 numbers e.g. PS01234.
Creating a new Naming File
In the following example a new naming file will be created for Area 32.
Navigate to the project default location in our case %tradflts%.
If this is not known, key in Q EVAR TRADFLTS in the Command Window, to return the following value: -
Environment variable TRADFLTS :C:\Users\Public\Documents\AVEVA\Plant\Projects\Training\tradflts
Copy the file DES-SUP-NAMES and rename it to DES-SUP-NAMES-AREA32
Edit the file using a suitable text editor.
Change the prefix to read PS-32-

and the index to 0.
Save the file.
Testing the Auto Naming file.
Creating a new support Zone

Select Zone from the Create group on the GENERAL tab.
Name ZONE-SUPPORTS-AREA32
Purpose SUPP Support
Click the OK button.

Setting Default Creation Zone
This can be set from the Storage group on the SUPPORTS Tab
Or by selecting Defaults from the Settings group on the SUPPORTS tab.
From Creation Zone and Templates section click the Select... button and change the creation zone to
ZONE-SUPPORTS-AREA32.
Click the OK button followed by the OK button from the Supports Application Defaults form.

Setting Auto Naming File to a Zone
Once the creation zone has been selected the naming file created earlier can be associated with the Zone.
Select the Autoname button from the Settings Group

on the SUPPORTS tab.
Select DES-SUPP-NAMES-AREA32
Click the Set Autonaming File to Default Zone button.
Click the Yes button.
Click the OK button on the Supports AutoNaming File

form.

Exercise 12 –Supports Autonaming
Using the above example create a new Supports Autonaming file and associate it with a new zone, test
the results by creating some new supports.


CHAPTER 20
20 Support Plot Files
Users can use their own plot files, including logos and client-specific information instead of the AVEVA
E3D™ Supports Plot Files.
User plots should be stored in a parallel file structure, AVEVA E3D™ Supports can then search in the user
area before the AVEVA area. This search path is set on the %mdsplots% environment variable, which is
set in the evars.bat batch file, customisation is normally done in the file “custom_evars.bat” which is typically
stored in c:\Users\Public\Documents\AVEVA\Projects\E3D2.1 .
The default location of the plot files is “C:\Program Files (x86)\AVEVA\Everything3D2.10\PMLUI\des\mds\plot”
A typical customisation might be: Set MDSPLOTS=D:\PMLUI\des\plot
The plot file names are of the format MDS-Standards-FT09-1.plt


CHAPTER 21
21 Supports Drawing Production
DRA-MDS-ABADEFAULTS
AVEVA E3D™ Supports uses the standard Area Based Automatic Drawing Production (ABA) facilities to
produce its detail drawings in Draw. For the use of ABA certain AVEVA E3D™ Supports specific elements
have been added into the delivered project. In summary these are:
• Supports specific Sheet Templates (SHTMPLs) and their associated Views Layers and Tasks, plus
some referenced Library (LIBY) elements.
• Supports specifics only are documented below. For other details of the administration of ABA, see the
AVEVA E3D™ Supports Customisation Guide.
• One of the principles of ABA is that it works on an area of the database defined by coordinates.
AVEVA E3D™ Supports/ABA does not make use of this part of the functionality initially but calculates
the area required around a support or hanger and then back-fills the requirement into the ABA forms.
Specifying the ABA Defaults File

In Draw select Defaults from the Area-Based Auto group of the AREA Tab
Select Default File and browse to the project

defaults folder typically: -
C:\Users\Public\Documents\AVEVA\Projects\E3D2.1\T
raining\tradflts
Select DRA-MDS-ABA-DEFULTS-AREA01
Click Apply.
© Copyright 1974 to current year. 181 www.aveva.com

 Note that Area is Red as /MDS-ABA-

AREA01-Library cannot be found.
Click the Red Button to create the missing Library
Select File > Save Defaults to save the Defaults
Select File > Close to close the form
Select the Draw Explorer from the Explorers group on the TOOLS Tab
From the Draw Explorer, navigate to Department DEPT-

SUPPORTS-AREA01
Select Registry > Create from the Explorers group on the TOOLS Tab

Name REGI-SUPPORTS-AREA01
Click OK and Cancel the Registry Information form.
Create a Support Drawing
Select New Drawing from the Supports Group of the AREA Tab
Select Load Supports > All in MDB
Select a Support and Template
Pick Apply
Use Existing Drawing to display the

Support Drawings


ABA Defaults File
A sample DRA-MDS-ABA-Defaults file is supplied with AVEVA E3D™ Supports default values, as shown
below:
--
-- ========================================
-- General Defaults For Area Based ADP Use.
-- ========================================
--
-- Section 1
!!abadefaults.libr.val = '/Aba/graphical_reports_library'
!!abadefaults.dlib.val = '/MDS-Drawing-Templates'
!!abadefaults.alib.val = '/MDS-ABA-Area-Library'
!!abadefaults.disl.val = '/PROJ/ABA/CLASS'
!!abadefaults.keyp.val = '/Aba/keyplans_library'
!!abadefaults.symb.val = '/Aba/symbols_library'
!!abadefaults.labl.val = '/Aba/tag_rule_library'
!!abadefaults.task.val = '/PROJ/ABA/TASK'
!!abadefaults.logf.val = '%ABALOG%'
!!abadefaults.batf.val = '%ABABATCH%'
!!abadefaults.logpath = '%ABALOG%'
!!abadefaults.batpath = '%ABABATCH%'
!!abadefaults.ustring = 'SYSTEM'
!!abadefaults.string = 'XXXXXX'
!!abadefaults.startbat = '%ABABATCH%\Batch.bat'
-- End Section 1
--
-- =============================================
-- Permitted View Scales
-- =============================================
--
-- Section 2
Metric \MET \1/1 \1 1 \1
Metric \MET \1/2 \1 2 \0.5
Metric \MET \1/3 \1 3
\0.333333,0.3333,0.33
Metric \MET \1/5 \1 5 \0.2
Metric \MET \1/10 \1 10 \0.1
Metric \MET \1/20 \1 20 \0.05
Metric \MET \1/25 \1 25 \0.04
Metric \MET \1/33.1/3 \1 33.1/3
\0.0303,0.03
Metric \MET \1/50 \1 50 \0.02
Metric \MET \1/75 \1 75
\0.013333,0.0133,0.013
Metric \MET \1/100 \1 100 \0.01
Metric \MET \1/150 \1 150
\0.006667,0.0067
Metric \MET \1/200 \1 200 \0.005
Metric \MET \1/250 \1 250 \0.004
Metric \MET \1/500 \1 500 \0.002
Metric \MET \1/1000 \1 1000 \0.001
Metric \MET \1/1250 \1 1250 \0.0008
Metric \MET \1/2500 \1 2500 \0.0004
Architectural \ARC \3" = 1'-0" \3Inch 1' \0.25
Architectural \ARC \1 1/2" = 1'-0" \1.1/2Inch 1' \0.125
Architectural \ARC \1" = 1'-0" \1Inch 1'
\0.083333,0.0833
Architectural \ARC \3/4" = 1'-0" \0.3/4Inch 1' \0.0625
Architectural \ARC \1/2" = 1'-0" \0.1/2Inch 1'
\0.041667,0.0417
Architectural \ARC \3/8" = 1'-0" \0.3/8Inch 1' \0.03125
,0.0313
\0.020833,0.0208
\0.015625,0.0156


\0.010417,0.0104
\0.005208,0.0052
Engineering \ENG \1" = 10'-0" \1Inch 10'
\0.008333,0.0083
\0.004167,0.0042
\0.002778,0.0028
\0.002083,0.002
\0.001667,0.0017
\0.001389,0.0014
\0.001111,0.0011
\0.000833,0.0008
-- End Section 2
--
-- =============================================
-- Symbol Templates
-- =============================================
--
-- Section 3
-- Plan View E/W axis
/Aba/SAM/grids/EW
-- Plan View N/S axis
/Aba/SAM/grids/NS
-- Elevation View EW axis
/Aba/SAM/grids/vert_EW
-- Elevation View NS axis
/Aba/SAM/grids/vert_NS
-- North Arrow
/Aba/north_arrow
-- End Section 3
--
-- =============================================
-- Auto Number Task
-- =============================================
--
-- Section 4
/Aba/AutoNumber
-- End Section 4
--
13:4 12.0
-- =============================================
-- Imperial Paper Sizes
-- =============================================
--
-- Section 5
A \8.5 11
B \17 11
C \22 17
D \34 22
E \44 34
-- End Section 5
--
-- =============================================
-- Metric Paper Sizes
-- =============================================
--
-- Section 6
A0 \1189 841
A1 \841 594
A2 \594 420

A3 \420 297
A4 \297 210
A5 \210 148
-- End Section 6
AVEVA E3D™ Supports Specific Sheet Template Libraries
Enter Draw in the Training project (TRA).
An example hierarchy with relevant elements and key Supports attributes is shown below.
View Element
The standard VIEW element has two user-defined attributes associated with it that are significant to
AVEVA E3D™ Supports. They are:
• :ABAUpdate Set to true or false to control when Update Design is performed on the View. If set
to false, the update is not performed when a Drawing is created but is done as specified in the
owned tasks. This prevents multiple Update Designs and hence optimises drawing processing time.
• :MDSABAOption This controls the Projection angle of the View: 1 = 1st angle projection and
3 = 3rd angle projection. The UDA defaults to 3rd angle projection if unset.
MDS Specific Tasks
Each task is outlined in a separate table below. Tasks are grouped as follows:
• Sheet tasks.
• View tasks.

Sheet Tasks
SheetLayout
Task name: MDS_aba_sheet_task
Function name: Mdsabasheettask.pmlfnc
This task is mandatory for all AVEVA E3D™ Supports Template sheets as
it sets up the sheet environment to be able to run all the other Tasks for a
Description:
particular Template. It defines the Views, sets the scales, switches off the
View Frames, and sets the View Type. It also gets the name of the
required AVEVA E3D™ Supports Support.
RunData
Task name: MDS_aba_rundata
Function name: MdsAbaRunData.pmlfnc
This task adds run time data of the User, with options of login Name or
Description: User at a predefined location, and text size to the AVEVA E3D™ Supports
Detail Sheet.
SheetComment
Task name: MDS_aba_comment
Function name: MDSabacomment.pmlfnc
Description: This task adds any Support Comment set by the designer
during the Support Creation sequence. It is positioned at the bottom of the
MTO Table on the Sheet.
Support type
Task name: MDS_aba_supptype
Function name: MDSabasupptype.pmlfnc
Description:
Support code
Task name: MDS_aba_suppcode
Function name: MDSabasuppcode.pmlfnc
Description:

Places weld detail overlay
Task name: MDS_aba_overlay
Function name: MDSabaoverlay.pmlfnc
Description:
View tasks
MainView
Task name: MDS_aba_view_task
Function name: MDSabaviewtask.pmlfnc
This task is mandatory as it processes other View tasks although the

majority of the main detail VIEWS attributes are modified in this function
(task).
Description:
The View Scales and the update of each detail view is carried out in the
sheet function (task), i.e. !!mdsabasheettask.pmlfnc to avoid updating
these Views more than necessary.
Support location plan view
Task name: MDS_aba_location_plan_task
Function name: MDSabalocplan.pmlfnc
This task performs the following:
• Creates and sizes a Location View to fit the available sheet space
• Creates and positions a Datum symbol
Description: • Gets the nearest Gridline for location and adds to the View
• Adds labels and dimensions to the View
• Places a North Arrow
The View is not necessarily to a standard scale.
Support material take-off of steel
Task name: MDS_aba_mtosteel
Function name: MDSabamtosteel.pmlfnc
This task adds a table of steel member requirements, for the Support, to
the Template Sheet. Description text can be either DTXS (stex of detref) or
Description:
DTXR (rtext of stex) where the stex is a manufacturer’s description and the
rtext is a generic description.

Support material take-off of components
Task name: MDS_aba_mtocomp
Function name: MDSabamtocomp.pmlfnc
This task adds a table of Support Components requirements to the

Description:
Template Sheet.
Support Component tag
Task name: MDS_aba_ancil_tags
Function name: MDSabaanctags.pmlfnc
Description: Adds Support Component (Ancillaries) Labels
Support steelwork tag
Task name: MDS_aba_steel_tags
Function name: MDSabasteeltags.pmlfnc
Description: Adds Support Steelwork Labels.
Support steelwork joint tag
Task name: MDS_aba_ix_joint_tags
Function name: MDSabasteeltags.pmlfnc
This task adds Steelwork (SCTN) internal and external joint labels to the
Description:
Drawing.
Axes for isometric view
Task name: MDS_aba_iso_view_axes
Function name: MDSabaisoview.pmlfnc
Description:
Support data
Task name: MDS_aba_supp_data
Function name: MDSabasuppdata.pmlfnc
Description:

Add weld symbols
Task name: MDS_aba_weld_tags
Function name: MDSabaweldtags.pmlfnc
Description:
Add weld symbols
Task name: MDS_aba_weld_tags
Function name: MDSabaweldtags.pmlfnc
Description:
Label U bolt holes
Task name: MDS_aba_ubolt_hole_tags
Function name: MDSabaubolttags.pmlfnc
Description:

Creating a Function – Worked Example
The following section works through creating a new simple Sheet task to add some text to Supports Drawings.
The sequence of events is:
• Create a simple macro.

• Convert the macro to a function.
• Create a Sheet Task.
Simple Macro
First create a simple macro and test that it works OK on a Supports Draw Sheet.
Create a new folder called c:\mdspmllib.
 When a sheet function runs AVEVA E3D Draw ABA will be at Sheet level.
--Macro to create a simple Note and Text
-- Get Sheet Name

!sheet = !!ce
-- Delete Note if it exists

!notename = !sheet.name & '/TRAINING-NOTE'
$!notename
handle any
elsehandle none
delete note
endhandle
new note $!notename

Cheight 2.5mm
new texp
at x320 y60
btext 'THIS NOTE WAS ADDED DURING THE SUPPORT TRAINING'
Above is a simple macro that will create some text in a new note, it checks if the note exists and deletes it if
required. Save the macro as MDSAbaTraining.pmlmac in the C:\mdspmllib folder.
Display a typical Supports ABA Drawing, navigate to sheet level, run the macro by dragging the macro
MDSAbaTraining.pmlmac onto the Command Window.

The screenshot shows the new text added.
 It may be necessary to create a support and drawing if none exist on the current project.
Handling Units in Macros

The following section shows some additional lines to show how to handle imperial Units in Macros.
--Macro to create a simple Note and Text
-- Save the current Units

-- and Set UNITS to metric for making task
work when in imperial.
prec 2 dp
var !units UNITS
UNITS MM Bore
-- Get Sheet Name

!sheet = !!ce

$!notename
handle any
elsehandle none
delete note
endhandle
new note $!notename

Cheight 2.5mm
new texp
at x320 y60
btext 'THIS NOTE WAS ADDED DURING THE
SUPPORTS TRAINING'
-- Switch Units to whatever they were

!!ce = !sheet
UNITS $!units
prec var def

Creating a Function
The macro can now be turned into a Function.
Copy the macro and change its file extension name from pmlmac to pmlfnc.
Copy MDSAbaTraining.pmlmac to MDSAbaTraining.pmlfnc
define function
!!MDSAbaTraining(!params is array)
-- Save the current Units

-- and Set UNITS to metric for making task
work when in imperial.
prec 2 dp
var !units UNITS
UNITS MM Bore
-- Get Sheet Name

!sheet = !!ce

$!notename
handle any
elsehandle none
delete note
endhandle
new note $!notename

Cheight 2.5mm
new texp
at x320 y60
btext 'THIS NOTE WAS ADDED DURING THE
SUPPORTS TRAINING'
-- Switch Units to whatever they were

!!ce = !sheet
UNITS $!units
prec var def
endfunction
The macro created earlier has been turned into a function by adding
define function !!MDSAbaTraining(!params is array) at the top and endfunction at the bottom.
PML Library
Functions must exist in a PML Library (pmllib) the new directory must exist in the PMLLIB Path.
Edit the evars.bat Batch file and add the following line at the bottom:
set pmllib=c:\mdspmllib;%pmllib%
 In the above the new function is in the directory c:\mdspmllib. If the new function is addition to existing
macros then the index will need rebuilding using PML REHASH ALL.
Enter Draw and check the variable has been set correctly by keying in Q EVAR PMLLIB in the Command
Window.

Environment variable PMLLIB :c:\mdspmllib;C:\AVEVA\Plant\E3DTraining\Training\pmllib;C:\Program Files

(x86)\AVEVA\Plant\E3D1.1.0\PMLLIB
Testing a Function
To test the function navigate to a Support ABA sheet, delete the note if it already exists and run the function
by keying in the following in the Command Window:-
!aa = array()
Call !!MDSAbaTraining(!aa)
The Note should be appeared on the Support Drawing.
Creating a Task
Select Library > Task from the Modify group on the AREA Tab
Select the Drawing radio button.
Name /mds_aba_training
Description Training Task
Function mdsabatraining
Click the Add button.
 The task has no parameters so this is left blank.
Select File > Save Tasks followed by File > Close
Save Work.

Adding a Task to a Drawing Sheet.
Select Template > Sheet from the Modify group on the AREA
Tab
Select /MDS-ABA-3-VIEWS(METRIC)S1
 The drawing templete is also displayed
The Modify ABA Template Sheet form is displayed and the Template is also displayed in the graphics
window.
Locate the Task mds_aba_training in the Available pane.
Move it to the Selected pane using the arrow shown below.
Click the OK button.

The ABA Template View form is displayed. As there

are no View Tasks to add, this form can be dismissed.
Click the Cancel button.
Save Work.
The new task will now be added to the Drawing Sheet.
This new task will now be performed each time the

Drawing Sheet is used.
Test the task by creating a new Supports Drawing.

Exercise 13 AVEVA E3D™ Supports Drawing Production
1. Using the above example create a new task to add some text to a Support Drawing Sheet and
test that is added to the Sheet.

CHAPTER 22
22 3rd Party Supports Applications
In addition to the standard E3D hanger interface, hangers can also be created using 3rd Party Support
applications. In the current release two interfaces are included Carpenter & Paterson Ltd., Witch Hanger and
Lisega, Licad.
It intended that this will be expanded along with a generic 3rd Party Interface.
Witch Hanger Interface
The Witch Hanger interface (Carpenter & Paterson Ltd. hanger design software) works with the relevant
manufacturer hanger component catalogue, which is supplied with the Supports application (CPL, Carpenter
& Paterson databases).
The hanger design software belongs to the hanger manufacturer and can be obtained from the vendor.
Hanger configurations are displayed from the manufacturer’s interface not the Supports application. There are
no pre-defined support standard names available when using a hanger manufacturers interface.
The Database CPLMDS/CPLCATA must be included in the MDB this database can be found in the AVEVA
Supplied CPL project.
Lisega Licad Interface
The Lisega Licad Interface works with the relevant manufacturer hanger component catalogue.
The hanger design software and the associated E3D Project (LIS) belongs to the hanger manufacturer and
can be obtained from the vendor.
Hanger configurations are displayed from the manufacturer’s interface not the Supports application. There are
no pre-defined support standard names available when using a hanger manufacturers interface.
The Databases KATALOG/H&S_DICT and KATALOG/LS_CATA must be included in the MDB these
databases can be found in the Lisega Licad Supplied LIS project.
3rd Party Interface Configuration Files
HangerInterfaceConfiguration.xml
The configuration file for the 3rd Party Interfaces is HangerInterfaceConfiguration.xml which can be found in
the E3D2.1 executables folder typically C:\Program Files (x86)\AVEVA\Everything3D2.10 under normal
circumstances there is no need to modify this file, however it does contain the reference to the location of the
3rd Party executable so may need to be modified if the 3 rd Party software is not installed to the default location.
3rd Party Interface Communication Folder
A new folder “<project>hid” will be automatically created in the project folder typically
c:\Users\Public\Documents\AVEVA\Projects\E3D2.1\Training\trahid.
This folder will contain 3rd party sub folders typically cplData for Witch Hanger and lisegaData file Lisega
Licad.
© Copyright 1974 to current year. 199 www.aveva.com

3rd Party Interface Settings
Login to AVEVA Catalogue as a Support Designer using the details provided by the Trainer, for example:
Start > All Programs > AVEVA > Manage > AVEVA Catalogue Project: Training (TRA), Username:
A.SUPPORTADMIN, Password: A, MDB: A-SUPPORTS and Click the Paragon Tile, Select the SUPPORT
Application.
 A.SUPPORTADMIN is a free user, the user name will need to be typed in full into the login form.
The AVEVA E3D™ Supports, Supports Admin Data form is the main control form for the AVEVA E3D™
Supports application. It allows the administrator to control some of the design limits within which supports can
be created.
The default values/settings shown on the forms are those that exist when the AVEVA E3D™ Supports
 Some of the defaults on the Options(1) tab can be modified by the designer using the AVEVA E3D™
Supports Application Defaults form, the Designer must be a member of the DESADMIN Team.
From the Configuration Group on the SUPPORTS Tab,

click the Application Defaults button.
The Project Hanger Interfaces Section of this form

controls whether the interface is available in the project
and which interface is the default.
Right Click on the Table and make Licad 9 available and

Witchhanger 4 Default and Available.

3rd Party Databases
The following databases should be included in the project and added to the appropriate MDB as described
earlier.
3rd Party Software Project Database Typical MDB
Witchhanger CPL CPLMDS/CPLCATA A-SUPPORTS
Licad LIS KATALOG/H&S_DICT A-SUPPORTS
KATALOG/LS_CATA
3rd Party Interface Load Errors
When the Designer uses the Support application one of the following errors may be displayed indicating that
the 3rd Party software is not loaded or that the catalogue database for that application is missing.
Typical Witch Hanger Error
The following error shows that the Witch Hanger Software is not loaded and the CPL catalogue is not in the
MDB.
Typical Licad Error
The following errors show that the Licad Software is not loaded and the LIS catalogues are not in the MDB.


TM-1865 AVEVA Everything3D (2.1) Supports Administration

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TM-1865 AVEVA Everything3D (2.1) Supports Administration

Hochgeladen von

Copyright:

Verfügbare Formate

Training Title of manual (version)

© Copyright 2015. 2 www.aveva.com

Date Revision Description Author Reviewed Approved

21/09/2015 0.1 Issued for Review BT

Visit our website at http://www.aveva.com

© Copyright 2015. 3 www.aveva.com

@AVEVA Solutions Limited 2015

© Copyright 2015. 4 www.aveva.com

© Copyright 2015. 5 www.aveva.com

7.2 Supports Admin Data Options (2) Tab.......................................................................................... 46

© Copyright 2015. 6 www.aveva.com

9.1 9.1 Standard Tab ......................................................................................................................... 71

© Copyright 2015. 7 www.aveva.com

13.5.6 Maximum Allowable Bore Sizes ................................................................................................ 99

© Copyright 2015. 8 www.aveva.com

18.1.8 AN640 to AN700 Anchor for Trunnions ................................................................................... 138

© Copyright 2015. 9 www.aveva.com

22 3rd Party Supports Applications ..................................................................................... 199

© Copyright 2015. 10 www.aveva.com

About this Guide

Overview of the AVEVA E3D™ Supports Application

© Copyright 2015. 11 www.aveva.com

Databases Design Consequences

• Moving pipe (By, Drag etc.) will not move supports.

• Data Consistency Check has been enhanced to

For example, if the SUPP element is not aligned with

© Copyright 2015. 12 www.aveva.com

• No write access to branch or components required

• Support is contained under one SUPPO element

• SUPPO is the primary element. (i.e. fewer elements claimed).

• All additive to DB, no upgrade required

Support Catalogues and Specifications

• Understand the Project Catalogue requirements for AVEVA E3D™ Supports.

• Understand AVEVA E3D™ Supports System Defaults.

• Understand AVEVA E3D™ Supports Autonaming.

• Understand Ancillary Defaults.

• Understand Hanger Data.

• Understand Trunnion Defaults.

• Understand Structural Defaults.

• Understand Framework Template Administration.

• Understand User Defined Ancillaries.

• Understand how to customise AVEVA E3D™ Supports Automatic Drawing Production.

© Copyright 2015. 13 www.aveva.com

Using this guide

Information the user has to key-in will be in bold red text.

 Refer to other documentation

Example files or inputs will be in the courier new font.

© Copyright 2015. 14 www.aveva.com

The Training Project has been created using the

In the Training project no third party interfaces

 The use of third party Interfaced is not

© Copyright 2015. 15 www.aveva.com

Select New Project

Select OK and Close the Project Creation Wizard

© Copyright 2015. 16 www.aveva.com

Project: Training (TRA)

MDB: left unset

Click the Admin tile.

Select Utilities > Training Setup…

Pick Create Project Data

Pick OK and Close the Training Setup Form

© Copyright 2015. 17 www.aveva.com

AVEVA E3D™ Supports Default files

DES-SUPP-NAMES - Typical AVEVA E3D™ Supports Autonaming File