TM-1840 AVEVA Catalogue (1.1) Piping Catalogues and Specifications Rev 4.0 PDF
TM-1840 AVEVA Catalogue (1.1) Piping Catalogues and Specifications Rev 4.0 PDF
Revision Log
Updates
Change highlighting will be employed for all revisions. Where new or changed information is presented
section headings will be highlighted in Yellow.
Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers please report it to AVEVA
Training & Product Support at [email protected]
This manual provides documentation relating to products to which you may not have access or which may
not be licensed to you. For further information on which products are licensed to you please refer to your
licence conditions.
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free
from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar
losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of
data or information; any special, indirect, consequential or pure economic loss, costs, damages,
charges or expenses which may be suffered by the user, including any loss suffered by the user
resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of
whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence)
or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with
the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year
in which the user's claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software
licence under which the AVEVA software was purchased, the clauses in the software licence shall
take precedence.
Copyright
All intellectual property rights, including but not limited to, copyright in this manual and the associated
software, (including source code, object code, and any data) belongs to or is validly licensed by AVEVA
Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this
document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or
transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is
granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the
beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product, machine, or
system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such
unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with the
terms and conditions of the respective licence agreements, and in accordance with the relevant User
Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
Copyright 2012 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA
shall not be liable for any breach or infringement of a third party's intellectual property rights where such
breach results from a user's modification of the AVEVA software or associated documentation.
The AVEVA Everything3D™ user interface is based on the Microsoft® Office Fluent™ user interface.
Trademark
AVEVA™, AVEVA Everything3D™, and AVEVA CATALOGUE™ are registered trademarks of AVEVA
Group plc or its subsidiaries. AVEVA product names are trademarks or registered trademarks of AVEVA
Solutions Limited or its subsidiaries. Unauthorised use of trademarks belonging to AVEVA Group plc or its
subsidiaries is strictly forbidden.
Fluent is a trademark of Microsoft Corporation and the Fluent user interface is licensed from Microsoft
Corporation.
The Microsoft Office User Interface is subject to protection under U.S. and international intellectual property
laws and is used by AVEVA Solutions Limited under license from Microsoft.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its
name or logo belongs to its respective owner.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
1 Introduction ..........................................................................................................................11
1.1 Aim ................................................................................................................................................... 11
1.2 Objectives........................................................................................................................................ 11
1.3 Prerequisites ................................................................................................................................... 11
1.4 Course Structure............................................................................................................................. 11
1.5 Using this guide .............................................................................................................................. 11
1.6 Setting up the Training Course ..................................................................................................... 12
2 AVEVA Catalogue Paragon Module – Overview ................................................................13
2.1 Objectives........................................................................................................................................ 14
2.2 The Catalogue Database Structure ............................................................................................... 14
2.3 Part World (PRTWLD) ..................................................................................................................... 14
2.4 Table World (TABWLD) .................................................................................................................. 15
2.5 Specification World (SPWL) .......................................................................................................... 15
2.6 Connection Tables (COCO Tables) (CCTA) ................................................................................. 16
2.7 Catalogue (CATA) ........................................................................................................................... 17
2.8 Bolt Tables (BLTA).......................................................................................................................... 18
2.9 Units ................................................................................................................................................. 18
2.9.1 Current Session Units................................................................................................................ 19
2.10 Forward Planning ........................................................................................................................ 20
2.11 Paragon – General Application Menu Bar ................................................................................ 20
2.12 The Catalogue Explorer .............................................................................................................. 21
Exercise 1 - Entering a Paragon Session..................................................................................22
3 Coding Systems ...................................................................................................................23
3.1 Why Have a Coding System? ........................................................................................................ 23
3.2 Standard Coding Systems ............................................................................................................. 23
3.3 Are Element Names Significant? .................................................................................................. 24
3.4 What System? ................................................................................................................................. 24
Exercise 2 - Coding System.......................................................................................................30
4 Component Creation............................................................................................................31
4.1 Enter Paragon in the Training Project – A Worked Example ..................................................... 31
4.2 Creating the Catalogue Hierarchy – A Worked Example ............................................................ 32
4.3 Automatic Naming – A Worked Example ..................................................................................... 32
4.4 Creating a Component Category (CATE) Element – A Worked Example ................................. 32
4.4.1 Parameter Definitions ................................................................................................................ 34
4.4.2 Modifying the Component (SCOM) element ............................................................................. 35
4.4.3 Creating a Component Copy ..................................................................................................... 36
4.4.4 Parameter Values ...................................................................................................................... 37
4.5 Constructing Point Sets (PTSE) – A Worked Example ............................................................... 37
4.5.1 PTAXI ........................................................................................................................................ 38
4.5.2 PTCAR....................................................................................................................................... 41
4.5.3 PTMIX........................................................................................................................................ 42
4.5.4 PTPOS....................................................................................................................................... 42
4.5.5 PSKEY....................................................................................................................................... 43
4.5.6 P-Point Visibility (PVIF) ............................................................................................................. 43
4.5.7 Point Set for TUBE .................................................................................................................... 43
4.5.8 Functions ................................................................................................................................... 44
4.5.9 P-point Conventions .................................................................................................................. 44
4.6 Geometry Sets (GMSE)................................................................................................................... 44
4.6.1 Creating a Geometry Set – A Worked Example........................................................................ 45
4.7 Example Valve showing Point and Geometry Sets ..................................................................... 50
Exercise 3 - Component Creation..............................................................................................53
23 Administration.................................................................................................................229
23.1 Naming Rules ............................................................................................................................ 229
23.2 Representation Rules ............................................................................................................... 230
Appendix A - Pipe Catalogue Coding Conventions ...............................................................231
A1.1 Component Naming .................................................................................................................. 231
A1.2 Bolting ........................................................................................................................................ 232
A1.3 COCO Table Coding.................................................................................................................. 234
A1.4 Component NAME codes ......................................................................................................... 236
A1.5 Component Type ....................................................................................................................... 237
A1.6 Control Valves Specials etc... .................................................................................................. 237
A1.7 Regulating valves...................................................................................................................... 239
A1.8 Regulating valves -actuator operated ..................................................................................... 240
A1.9 Bend: Standards........................................................................................................................ 241
A1.10 Bend: Type................................................................................................................................. 242
A1.11 Coupling: Standards ................................................................................................................. 243
A1.12 Coupling: Type .......................................................................................................................... 244
A1.13 Elbows: Standards .................................................................................................................... 245
A1.14 Elbow: Type ............................................................................................................................... 246
A1.15 Flanges: Standards ................................................................................................................... 247
A1.16 Flange: Type ............................................................................................................................. 248
A1.17 Orifice Flanges .......................................................................................................................... 249
A1.18 Reducing Flanges ..................................................................................................................... 250
A1.19 Gaskets: Standards .................................................................................................................. 251
A1.20 Gasket: Type.............................................................................................................................. 253
A1.21 Gasket: Thickness .................................................................................................................... 254
A1.22 Closures: Standards ................................................................................................................. 255
A1.23 Closures: Type .......................................................................................................................... 256
A1.24 Miscellaneous Items ................................................................................................................. 257
A1.25 Miscellaneous Items: Types..................................................................................................... 259
A1.26 Nipple: Standards...................................................................................................................... 260
A1.27 Nipple: Type............................................................................................................................... 261
A1.28 Nipple: End Connection ........................................................................................................... 262
A1.29 Nipple: Length ........................................................................................................................... 263
A1.30 Pipe: Standard ........................................................................................................................... 264
A1.31 Pipe: Type .................................................................................................................................. 265
A1.32 Reducer: Standard .................................................................................................................... 266
A1.33 Reducer: Type ........................................................................................................................... 267
A1.34 Stub-End: Standard................................................................................................................... 268
A1.35 Stub-End: Type.......................................................................................................................... 269
A1.36 TEE: Standard............................................................................................................................ 270
A1.37 TEE: Type................................................................................................................................... 271
A1.38 Valves: Standards and Manufacturer...................................................................................... 272
A1.39 Valves: Type .............................................................................................................................. 275
A1.40 Valves: Actuators ...................................................................................................................... 276
A1.41 Orifice plate hole sizes ............................................................................................................. 277
A1.42 Valves: Manufacturer - Saunders Valves................................................................................ 278
A1.43 Valves: Manufacturer - Worcester Valves .............................................................................. 279
A1.44 Welds.......................................................................................................................................... 280
A1.45 Attachments............................................................................................................................... 281
A1.46 Nozzle: Standards ..................................................................................................................... 282
A1.47 Nozzle: Type .............................................................................................................................. 283
A1.48 Flange Facings Table E1 .......................................................................................................... 284
A1.49 End connections for non flanged connections Table E2...................................................... 285
A1.50 End connections for flange faces Table E3............................................................................ 286
A1.51 Pressure ratings Table D1........................................................................................................ 287
A1.52 Wall Thickness (Schedules) Table D2..................................................................................... 288
A1.53 Nominal Sizes Table N1............................................................................................................ 289
A1.54 Material Codes........................................................................................................................... 290
A1.55 Schedule Thickness Codes...................................................................................................... 291
Appendix 2 - Catalogue Primitives ..........................................................................................292
© Copyright 2012 to current year. 9 www.aveva.com
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Everything3D (1.1)
Piping Catalogues and Specifications TM-1840
1 Introduction
This training course is aimed at Piping Designers/Engineers with AVEVA Plant Pipework Modelling
experience and aims to introduce the concepts of building catalogue components and piping specifications
using the AVEVA Catalogue Paragon module.
1.1 Aim
To be able to create and maintain AVEVA Plant Catalogue databases by creating piping components and
specifications.
1.2 Objectives
At the end of this training course the User will be able to:
Use the Catalogue Explorer to access the Catalogue, Properties, Model and Draw Databases.
Set GPART reference attributes to 3D Model, 3D Templates, Draw Symbol Sets, etc.
1.3 Prerequisites
Participants should have a good working knowledge of modelling pipework using AVEVA Plant products and
have completed both the AVEVA Everything3D™ Foundations and AVEVA Everything3D™ Pipework
Modelling training.
Training will consist of oral and visual presentations, demonstrations and set exercises. Each workstation
will have a training project, populated with model objects. This will be used by the trainees to practice their
methods, and complete the set exercises.
Certain text styles are used to indicate special situations throughout this document, here is a summary:
Menu pull downs and button press actions are indicated by bold dark turquoise text.
Additional information
System prompts should be bold and italic in inverted commas i.e. 'Choose function'
Example files or inputs will be in the courier new font, colours and styles used as before.
Select Start > All Programs > AVEVA > Manage > AVEVA Catalogue
Login to Paragon using the details provided by the Trainer. They will typically be as shown below:
Project Training
Username A.PIPER
Password A
MDB A-PIPING
Click Paragon
Select Utilities > Training Setup… from the main menu to display the Training Setup form. Navigate to the
Piping tab.
Check the Setup Training Course checkbox, click the Apply button and Close the form.
Completed Exercises are available via the Training Setup form and may be accessed by the Trainer, if
required.
This chapter gives an overview of Paragon functionality, describes the hierarchy of the Catalogue DB and
the main component members, and introduces the user interface. The chapter will also highlight and stress
the importance of having clear conceptual component designs before the design process begins.
Paragon enables the catalogue designer to build new Project databases and maintain the supplied AVEVA
Catalogue. This process involves the creation and modification of Piping Components and Steelwork
Components (Profiles, Joints and Fittings), and updating the associated specifications using the
standardised graphical user interface (GUI). This training guide will cover items pertaining to Piping
Components only.
As with other AVEVA modules and databases, only authorised Users have write access; catalogue
databases being created with Update or Multi-write access. The User Interface for Multi-write Claiming and
Querying is identical to that of the Model module.
The User can define catalogue components by utilising a series of forms that constitute Paragon’s GUI and
by entering the following types of data:
Datasets.
Connection Tables.
The GUI allows the User to build and modify Piping Specifications by creating the following data structures:
Bolt Tables.
Part Families.
Properties Data.
2.1 Objectives
When using Paragon, assuming that the appropriate access rights exist, the User is automatically directed to
the first catalogue database available within the particular MDB. It is highly likely that there will, in fact, be
more than one catalogue database in an MDB.
On entry to Paragon, there are four visible Worlds: Catalogue, Design (or Model), Draft and Property which,
can all be modified from within the appropriate application.
The diagram below shows the top level of the hierarchy within the Catalogue World.
CATALOGUE WORLD
The significance of the eight levels shown is explained in detail as appropriate and, together with their
successive hierarchies, introduced by the following sections.
The Part World (PRTWLD) can own any number of Part Families (PRTELE). Part Families consist of a
number of Parts (GPART) which, have reference attributes pointing to the 3D Model, material, Isodraft
description, etc. Parts are used in the catalogue to fully describe the components without the need for a
piping specification.
PRTWLD
PRTELE
Size Range tables (NOMTAB) define the nominal bore sizes and wall thicknesses that are allowed in
any specification that references the table.
Branch tables (BRTAB with PURPOSE attribute set to BRAN) define the branch and header size
combinations allowed for branch items, such as a TEE, within any specification that references the
table.
Reducer tables (BRTAB with PURPOSE attribute set to REDU) define the large end and small end size
combinations allowed for reducing items in a specification that references the table.
Wall Thickness tables (WTHTAB with PURPOSE set to REF) define the pipe Wall thickness for a
particular schedule and nominal bore size.
Pipe Data tables (PDAELE) reference the Wall Thickness tables; defining a Corrosion Allowance and
Flared Flanged Allowance for a particular nominal bore size.
TABWLD
The separate module SPECON (Specification Constructor) can also be used to build and maintain piping
specifications, although the module accepts tabular input only. In AVEVA Plant (12.1) SPECON can be
accessed from within PARAGON via SPECONMODE; this is discussed later in the guide.
The following hierarchy applies, regardless of the method used to create the specification:
SPWL
SPEC SPEC
SELE SELE
The Specification World (SPWL) can own any number of specifications and each corresponds precisely to a
specification used in a manual design situation. Each specification is a collection of (piping) Specification
Components (SPCO) whose selection is controlled by a varying number of Selectors (SELE).
The purpose of specifications is almost identical to that in a manual design situation but with one subtle
advantage; the User is not able to ‘cheat’ the system by using an out of specification component. Every
component used in an AVEVA Model must belong to one of the project specifications
The purpose of a SPCO is to act as an intermediate reference between Model data and catalogue data. In
this way, the amount of geometric and connectivity data actually stored is dramatically reduced.
To illustrate the above advantage, consider a project containing a large number of 50mm butt weld elbows
to BS1640. The elbows are of identical dimension and specification but with differing locations on the
project. Each elbow is ‘created’ in an AVEVA CATALOGUE™ Model and its unique attributes are defined,
i.e. position, orientation and ownership. In addition, a specification reference is assigned; this corresponds to
the name of a particular Specification Component.
Several specifications may allow the use of a particular component, and so each must contain a SPCO to
acknowledge the fact. The SPCO contains reference information to the catalogue including the specific
catalogue component. This thereby references the component’s physical shape, size and connectivity data;
plus detail text descriptions, material and specification. This information is used when producing isometric
drawing and material take offs (MTO), or employed in interfaces to other systems.
It can be seen then that by having this system of references, the bulk of data concerned with our BS1640
elbows is stored only once.
Each SPCO has the additional attribute Part Reference (PRTREF) which points to a General Part Element
(GPART).
GPARTs enable components to be fully defined via reference attributes to the 3D model, Draw Symbol Set,
Material, etc... GPARTs and GPART families are further discussed later in the training manual.
The coding system used for defining connection pairings is defined by the User. This is achieved by the use
of connection compatibility tables; the hierarchy of these tables is illustrated by the below diagram.
CCTA
The CCTA is the owner of a number of Connection Compatibility (COCO) tables and Connection
Compatibility Description Elements (COCDES). A COCO is merely a statement of two allowable connection
types. The COCDES is referenced by the COCO element and stores a full description of the connection
type.
When the command ‘CONNECT’ is used in Model, the system will check whether the two components being
connected are compatible. This check is also made when Data Consistency tests are performed by the
designer. In both cases the point of reference is the COCO TABLE.
In real terms, the COCO table will reflect the requirements of the project specifications. A COCO has an
attribute, CTYPE, which is set to the possible connection types, i.e. WELD WELD or BW BW.
CATA
SECT
SCOMP
SCONE PTMIX
LSNOUT
SSPHERE
LCYLINDER
SCYLINDER
LINE
As illustrated by the above hierarchical diagram, the members of a Catalogue (CATA) are Sections (SECT).
These Sections are for the convenience of users and it is generally accepted that the different generic types
are contained in separate Sections, i.e. flanges, valves, tees etc...
The Sections own Categories (CATE), which would in turn own specific types within the same generic field
to various standards i.e. weld neck flanges, slip-on flanges etc....
Although variable, the category usually own four distinct ‘types’ of element:
SCOMP (Catalogue Component): contains the parameters of the specific component and references
the 3D geometry (GMSE), the axial configuration (PTSE), the Dataset (DTSE) and the Bolt set (BTSE).
PTSE (Pointset): defines the axis system and associated P-points. Components can share a PTSE
which leads to further economy in data storage.
GMSE (Geomset): contains a number of primitives which together describe the physical appearance of
a component, and are related to a PTSE. Many components use the same GMSE.
SDTEXT: contains the component detail text string and its isometric symbol reference (SKEY).
DTSE (Dataset): contains a number of DATA elements describing the component parameters and can
be used in Model, e.g. to modify component properties.
BTSE (Boltset) defines the bolting requirements of a flanged component and is further described
below.
The Bolt Table hierarchy contains information describing the nature of the bolted connection of Piping
Components in a project. Although the Bolt Table is part of the Catalogue Database, it has been designed
for use by Isodraft and is therefore described in detail by the Isodraft Reference Guide.
CATALOGUE WORLD
SECT
Flanged components can have a Boltset (BTSE) which defines the bolting requirements across a flanged
joint. This can include items such as nuts, washers, etc... The Bolt Table section of the Catalogue contains
specific bolt information such as lengths, number of, diameters, etc...
Element types and attributes are further described in the Bolting Chapter.
2.9 Units
CATALOGUE WORLD
UNITS
The Units primary element in the first catalogue database can be used to set the default unit for Bore and
distance for the project.
There are two main attributes Bore units (Bunits) and Distance units (Dunits)
Prior to PDMS 12.1 it was only possible to set the units for Bore and Distance.
When the User enters dimensional data in any window, the units applied are taken from default settings. The
default units are specified independently for each unit type.
To change the default units, select Settings > Units to display the Current Session Units window.
A system default file is supplied for both metric and imperial units:
%AVEVA_DESIGN_DFLTS%/system-current-units-Met.pmldat
%AVEVA_DESIGN_DFLTS%/system-current-units-Imp.pmldat
To set the default units for a specific project the Administrator must select the required units using the
Current Session Units window and click Save. A file, %AVEVA_DESIGN_USER%/xxx-save-current-units-
Met.pmldat or %AVEVA_DESIGN_USER%/xxx-save-current-units-Imp.pmldat is then created.
The created file must be copied to the project defaults folder and renamed to %xxxdflts%/project-current-
units-Met.pmldat or %xxxdflts%/project-current-units-Imp.pmldat. The User is then permitted to use the
Project Defaults or use a saved file previously created.
On Global projects, it is necessary to propagate the units settings file to all project satellites. If the "Other
Data Transfer" mechanism has been implemented, (refer to Transfer of Other Data in Running Global
Projects guide), project unit settings files could be propagated. Otherwise, the most practical method of
propagating a project units file is simply to e-mail the file to all satellites and have the file copied to the
appropriate project folder. In practice, project units files will be configured at the beginning of a project, and
are unlikely to be changed frequently during the life of a project.
The User Settings, Save and Restore buttons can be disabled by the Administrator which forces the User
to use the project default settings. To disable the buttons, the Administrator must open the file saved in the
project defaults folder and change the following line:
!!comFormats.allowUserSaveFile = true
to
!!comFormats.allowUserSaveFile = false
Although the User cannot save their user settings, they are still able to change the unit format for the current
working session. When the User ends the current sessions the unit format reverts back to the project
defaults.
Paragon ensures it is very easy for the User to define catalogue database items in terms of their connectivity
(point sets), physical shape (geometry sets), dimensions (typically defined in terms of design parameters),
and other relevant attributes. Despite this assistance, it is advised for the User to have a clear idea of
exactly what each component is to look like and how its dimensions are to be defined before the design
process begins.
Paragon automates the component design process as far as possible, but there is no substitute for a
pencilled sketch for any new type of component, with the required design parameters marked on it.
Considering the User task to be completed, the initial route on entering Paragon is via the Paragon menu
and the selection of an appropriate application.
This course covers the Pipework and Equipment applications which display the relevant forms for
component data entry, modification, etc.
The pull-down menu options for Display, Query, Delete, Window and Help behave in a similar manner to
other AVEVA CATALOGUE modules.
Options for Settings, Utilities and Create are module specific and will be discussed in detail throughout the
remainder of the training manual.
………………………………………………………………………………………………………………………...
Consider the allowable element types that may exist beneath MASTER/PIPECATA. What element
types, if any, are missing from the members list?
………………………………………………………………………………………………………………………...
Access the bolting tables. At what level is the diameter of the bolts stored (BDIA)?
………………………………………………………………………………………………………………………...
What are the specifications stored within MASTER/PIPECATA? Name them for this DB.
………………………………………………………………………………………………………………………...
Navigate to specification /A150. What are the elements that form this specification?
………………………………………………………………………………………………………………………...
Does anything exist below these elements in the hierarchy and what is the lowest Element?
………………………………………………………………………………………………………………………...
Go to section /TEE within the catalogue. Note there are several categories holding information relating
to different types of tees. Access category /LDTB530.
3 Coding Systems
This chapter discusses the need for a coding system in the piping catalogue and the format of the AVEVA
coding system.
AVEVA Plant products require an element, such as a catalogue component, to have a unique name. With so
many elements being ‘structured’, AVEVA Catalogue adheres itself to a coding system in a number of areas.
Some examples are:
PTSET Names.
Standard AVEVA Catalogue has a catalogue containing approximately 50,000 components and has a
developed coding system which allows the definition of unique names for the supplied and future
components. Indeed, the coding system could generate in excess of 60 billion different names.
There are real advantages to having a standard coding system for catalogue component names and
connection types. Adopting a standard naming structure allows the following:
Queries relating to a component or range of components can be referred to precisely by name and
without encountering conventions unique to a company.
The retrieval of components, at any stage, beyond those being used from a given range and required
for a particular application.
To AVEVA CATALOGUE, element names are inconsequential but to the User, as already suggested, a
standard code would ease identification/ relocation.
Conventions will vary from company to company but some conventions that are possibly not company
orientated are:
Specification component names i.e. A3B/100EL - a 100 N.B. elbow within the specification /A3B.
Detailing text names - the name usually includes the short-code required by the detailing interface.
Branch numbers are usually prefixed by the pipe name, as nozzles are by equipment name.
The type of coding system very much depends on what is being coded, but at the outset two very basic
questions require answering:
The answer to the first question is often yes for the reasons already given. The answer to the second
question is a little more involved and is best explained by an example.
Manufacturer/standard
Specific standard
Type
Specific Type
End connection
Rating
Material
The material need not be included in the basic coding system because there is sufficient scope within other
fields for reference. A User may add a material code, potentially company orientated, by simply editing the
catalogue macros.
The following sheets are an extract from the Standard Component Coding System (see Appendix 1 for
further information). Using this system, the name derived for a 150mm long radius, butt weld elbow to ANSI
B16.9 is /AAEA200RR:
Coding System Example Component
A A A A E
B ANSI B16.11 B
D ANSI B16.5 D
G G GASKETS
H H
J J
K K CLOSURES
L L
M M MISCELLANEOUS
N N NIPPLES
P P PIPE
Q Q
R R REDUCERS
S S STUB-ENDS
T T TEES
U U
V V VALVES
W W
X X
Y Y
Z Z NOZZLES
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
0 0
A A E A A A E A 2
C 45 DEGREE C
H REDUCING ELBOW H
J STREET ELBOW J
K CLOSE RADIUS K
L MEDIUM RADIUS L
M OPEN RADIUS M
P 45 DEGREE SPRING P
T 4D PULLED BEND T
U 5D PULLED BEND U
W MITRE BEND W
Z Z COMPRESSION
1 1 PLAIN
3 3 SOCKET WELD
9 9
0 0
A A E A 2 0 0 A A E A 2 0 0 R R
F CLASS 600 F 1 25
J CLASS 2500 J 2 50
K K 2.1/2 65
L L 3 80
M M 3.1/2 90
N N 4 100
P P5 125
Q Q
R R 6 150
S S
T T 8 200
U U
V V 10 250
W W 12 300
X X 14 350
Y Y 16 400
Z Z 18 450
1 1 20 500
4 4 26 650
5 5 28 700
7 7 32 800
8 8 34 850
0 0 ZERO
Refer to Appendix 1 for a full description of the Standard Component Coding System and some examples
of Material and Schedule Thickness Short Codes.
For the purposes of the training, the coding system has been modified slightly because the components
might exist in the AVEVA Catalogue. Typically AAEA2BG-100 is the code used for a 100NB 90 Degree
Butt Weld Elbow.
1. Using the example above and Appendix 1 code the following components:
4 Component Creation
Paragon automates the component design process as far as possible, but there is no substitute for a
precursory sketch of any new type of component; complete with the required design parameters marked. It
is beneficial to mark the required P-points along with their number on the sketch; this is useful when creating
Point Sets.
Diagrams of P-point layouts, as used by AVEVA CATALOGUE, can be found in the Isodraft Reference
Manual.
Select Paragon > Pipework… from the main menu bar to access the additional
menu options that relate exclusively to this application.
To create a new Catalogue (CATA) element, select: Create > Catalogue... from the main window pull down.
In order that all subordinate members of the hierarchy are given a meaningful name, Automatic Naming
should be turned on at this point.
Select Settings > Naming… from the main menu pull down.
Select Create > Category... from the main menu (the High and Low level storage areas will be set
automatically).
In the example below and as described previously, a Category name of AAEA2BG has been used as a short
code for an ANSI Standard, 90 degree, Butt Weld, LR Elbow.
Parameter No 1 is always Nominal Bore and is created automatically with the Category.
At this stage, the hierarchy has been created for the Elbow Category /AAEA2BG:
Before continuing, it is necessary to consider the parameters required to define the elbow, the p-point layout
of the component, and the 3D geometry. For the example elbow, five parameters are required and the
following information can be allocated:
Parameter 4 Radius
ANSI BW 90 L.R.W.E
Click Apply
Rename the elbow to reflect the bore size and set the generic type to be ELBO:
Change the Name to /AAEA2BG-100, the Description to Elbow and the Generic Type to ELBO.
Click Apply.
Create a further two components in this category for bore sizes 150mm and 200mm.
On the bottom of the form select the row /AAEA2BG-100 using the Arrow
Select Copy
Select the new component and repeat the Copy operation to create a third component. Name the new
components as described earlier using Components on the Model Operations pane.
A Point Set is a definition of the axis system and associated P-points for a piping component (including
nozzles).
Consider the construction of equipment in Model; the User defines the axis system of the equipment and
primitive elements. A similar task is required in catalogue creation but whereas P-points are defined in a
fixed relationship to the equipment geometry, in the instance of piping components the primitives are
effectively draped about the P-points. P-points must be defined before the component geometry is created.
The Point Set provides information to several modules. Each P-point contains details of bore, connection
type, relative positions and direction for all the components that use it. The Point Sets underpin a number of
fundamental operations used in Model and Draw and their configuration is of great importance when
producing isometrics from IsoDraft.
One Point Set can be used for many similar components with varying bore sizes. Consequently, the point
sets are parameterised so that the dimensions can vary for each component size.
Z
P2 - Default Componen t
Leave Point
-X Y
PO - (Component Origin)
-Y X
P3 - (Branch P- point)
P1 - Default. Component
Arrive Point
-Z
PTPOS P-point defined by specifying a position expression PTCPOS and using PTCD to specify a
direction expression.
The type used depends on the position and orientation of the point relative to the component origin.
4.5.1 PTAXI
The most commonly used Point Set is the PTAXI. This is an axial P-point; allowing the P-point to be defined
in terms of an axis and a distance along that axis.
To display the component Axes system, tick the Axes check box at the top of the Model View form as
shown below.
Select Point Set on the Model References pane. The bottom part of the form will change to Point Set
References.
Select Axial P-point… from the pull-down menu. Enter data for the first P-point as follows:
P-point number 1
Purp The P-point Purpose attribute can be left blank.
Pskey NULL
Bore PARA 1
Axis Direction Y The Axis Direction for the P-point can be positive or negative,
i.e. Y or -Y or any axis chosen for P1.
This has defined P1 of the elbow and has used three parameters to supply the data that varies with bore
size. P2 may be defined in the same way - the choice of axis and number differs; all other parameters
remain the same.
Using the same method as previously shown, enter data for the second P-point as follows:
P-point number 2
Purp The P-point Purpose attribute can be left blank.
Pskey NULL
Bore PARA 1
Axis Direction X The Axis Direction for the P-point can be positive or negative,
i.e. X or –X or any axis chosen for P2.
The diagram below illustrates the PTSE required for a component such as an elbow.
Two new PTAX elements have been created under the PTSE administrative level. Note the attributes for
PTAX 1.
Navigate to PTAX 2 and use Query > Attributes to display the attributes of the second P-point.
4.5.2 PTCAR
The second method is a Cartesian P-point, and is referred to as PTCAR. This allows a P-point to be defined
by specifying the position and direction explicitly.
4.5.3 PTMIX
The third method is a mixture of the two previous methods, hence the title PTMIX. This method allows the
position to be specified explicitly (as in PTCAR) and the direction using PAXI (as in PTAXI). The axis
direction may be parallel to X, Y, Z, or in the XY, YZ, ZX plane.
On selection of Mixed Type P-Point from the pull-down menu, the Point Set References form is updated
as above and requires similar information as defined for PTCAR with the exception that an Axis Direction
(PAXI) is required instead of a Direction.
The diagram below illustrates a further hypothetical PTSE in which it would be appropriate to use PTMIX.
This example could have used PTCAR - it is a matter of personal choice, influenced by the information
present.
A PTSE may contain any combination of PTAX, PTCAR or PTMIX members. Bore and connection
details are optional. These must be given whenever a connection is to be made to a particular P-point.
There are cases where it is better to omit them, e.g. P3 on a valve or an eccentric reducer.
4.5.4 PTPOS
A PTPOS allows a P-point to be defined by specifying a position expression PTCPOS and using PTCD to
specify the direction expression.
4.5.5 PSKEY
The Pskey is used to override the default Skey when a component requires a different end connection. This
is commonly used for user-defined symbols within ISODRAFT. The default setting is NULL.
The PTSE required for TUBE is unique. The length of tube is variable. Only one P-point needs to be
described in order to set the bore size and connection type.
A single Axial P-point (PTAX) is required for TUBE, with the following settings:
P-point number = 1
PBOR = PARA 1
PDIS = 0
PCON = PARA 3
For implied TUBE, PARA 2 is reserved for O.D. by convention. No geometry set is required.
4.5.8 Functions
Contrary to the User having to define every dimension as a parameter, there is a facility for describing one
dimension as a function of another.
These are some examples of the use of functions taken from the standard catalogue. The input is in the
form of Standard Algebraic Notation.
(PARA[3] – PARA[4])
(PARA[3] + PARA[5])
A Geometry Set (GMSE) is a key part of the catalogue, being visible to everyone connected by a project.
There are also two additional ‘flags’ associated with Catalogue primitives; one for tube representation
(TUFLA) and one for centre line representation (CLFLA).
It is normal practice to model three representations of catalogue components: Centre Line, Detail and
Obstruction.
Centre Line Visible to Designer when selecting the Centre Line representation in Model and Draw.
This representation is often used on Draw Drawings for clarity and may include weld
blobs.
Obstruction Used by Clasher and should include both hard and operational soft volumes. In the
majority of cases the Obstruction volume can be the same as the detail volume.
When creating equipment it is necessary to have a mental image of the equipment origin and its axis
system. For Catalogue components, this information is provided in the form of a PTSE. Geometry Sets use
parameters in the same way as Point Sets.
In order to begin creation of the GMSE, it is necessary to be armed with the details of the relevant PTSE.
Methods of documenting such information are dealt with elsewhere, but at this stage a pictorial method,
such as the diagram below, will be instructive.
Before creating the GMSE, it is useful to define the level of representation required.
The reference section at the bottom of the Model View is updated for Geometry References as follows:
To represent the Elbow, select a Positive SCTOR (Circular Torus) primitive from the pull down menu and
check the Show Geometry Plot checkbox.
The primitive SCTO is shown in the graphical display area of the Model View form.
The Geometry Plot assists the User to set the required attributes for each particular primitive. In this case
PAAX, PBAX and PDIA for an SCTO.
A Axis to P1 (p-point 1)
B Axis to P2
Drawing Level 0 to 10
Obstruction to Hard (necessary as this primitive will also be used for the Obstruction representation)
Click Apply
Uncheck the Show Geometry Plot tick box and, select Piping Detail from the top Repr Pull Down.
Drawing Level: Each primitive used to define a catalogue component has an associated drawing level.
The primitive will be shown in a graphical view only if the drawing level range for the view
representation includes the drawing level specified for the primitive.
To create the Centre Line ON representation, select a Line primitive from the pull-down menu and set the
Representation to Piping Centre Line. This will automatically set Centre Line Flag ON and Tube Flag OFF.
Set the Direction (PTS) of the line to P1 T0 P2 and the Diameter (DIAM) to 2.
Select Apply
Set the Representation to Piping Centre Line. This will automatically set Centre Line Flag ON / Tube Flag
OFF.
Set:
Direction (PAXI) to P1
All primitives used only on CL representation should have Obstruction None (some may be used on
TUBE and CL representation)
Any point defined in the PTSE, including the Origin P0, can be used to create lines. They may become
tangent points by the substitution of the prefix T instead of P.
PAXI may be defined as one of the P-points in the PTSE. In this case, the primitive would be positioned
at that P-point and thus PDIST would apply from that P-point rather than from P0.
The following example illustrates the above concepts in relation to a more complex situation. The valve
below is shown by three representations.
In addition to the Points 1, 2 and 3 that are required by Isodraft, extra points 30, 31, 32 and 33 have been
added to help with hand wheel construction.
Using the previous example, create the hierarchy required to store the 90 degree, Butt Weld, LR
Elbows i.e. CATA, SECTion, Component CATEgory, etc...
CATA
SECT
Create the first component SCOM: 100mm NB Butt Weld ELBO as described previously. Remember
to rename the component and set the GTYPE and description.
Create two further components for bore sizes 150mm and 200mm using the Copy facility.
Pointset Creation
Create a Pointset for the elbow category as described above use two PTAX elements.
Create a Geomset for the ELBO as described previously. Remember to consider the centreline, piping
detail and obstruction representations.
Check each Representation Level: Centreline Piping, Detail and Piping Obstruction in the Graphical
Display
Refer to Appendix 2 for details of Catalogue primitives available to be used in this exercise.
Nominal Bore 1
Parameter 1
Nominal Bore 2
Parameter 2
(or Connection Type 2)
Connection Type
Parameter 3
Connection Type 2
Parameter 4
Flange Thickness
Parameter 5
and/or Bolt Length
B
P-Point Configuration
C
Connection BWD
PA 1 PA 2 PA 3 PA 4 PA 5 PA 6 PA 7
P-Point Configuration
C
B
Connection BWD
A A
PA 1 PA 2 PA 3 PA 4 PA 5 PA 6 PA 7 PA 8
P-Point Configuration
B
Connection FBD and BWD
D
C
Flange Hub
Tube Dia. Flange
Nominal Connection Connection Dia. Length
(Value Thickness Weld Dia.
Size 1 Type 1 Type 2 (Value (Value
‘B’) (Value ‘C’)
‘A’) ‘D’)
PA 1 PA 2 PA 3 PA 4 PA 5 PA 6 PA 7 PA 8
P-Point Configuration
B
C
Connection BWD
This reducer can be modeled similar to the previous reducer, and as there is no connection required on
P3; P0, P1 and P3 can be at the same point with P3 pointing towards the Flat.
OD 1
Nominal Nominal Connection OD 2 Length Offset
(Value Weld Dia.
Size 1 Size 2 Type (Value ‘B’) (Value ‘C’) (Value ‘D’)
‘A’)
PA 1 PA 2 PA 3 PA 4 PA 5 PA 6 PA 7 PA 8
Reducers have a connection reference to facilitate connections e.g. a boss for a drain. If the connection
facility is not being used, then an eccentric reducer will have a p-arrive, a p-leave and a P3 to orientate
the flat side. If the connection facility is to be used, P3 will be the connection p-point and as such must
have a valid bore and orientation. As the flat side can be either in the same direction as the connection
or directly opposite, a P9 p-point must be used to determine the orientation of the flat side.
G
L
P-Point Configuration
Connection FBD
B
C
A
The Globe valve should be created similar to the example described previously with representations for
Centre Line, Detail and Obstruction.
Extra P-point numbers 30, 31, 32 and 33 should be created to help with the Hand Wheel construction.
Distance to Bottom
Hand Wheel Height
Flange Thickness
Body Height
Hand Wheel
Connection
Flange Dia.
(Value ‘G’)
Thickness
(Value ‘A’)
(Value ‘B’)
(Value ‘D’)
(Value ‘H’)
(Value ‘E’)
(Value ‘F’)
(Value ‘L’)
(Value ‘c’)
Length
Type
PA 1 PA 2 PA 3 PA 4 PA 5 PA 6 PA 7 PA 8 PA 9 PA 10 PA 11
This chapter describes the creation of Detail Text, Material Text and General Text elements and their
attribute settings.
5.1 Objectives
Material Text (SMTEX) elements contain descriptive text describing the material(s) from which the physical
component is constructed. SMTEX elements are used during the construction of drawings, reports, take–off
sheets etc...
An SMTEX element exists at the same level in the Catalogue Database hierarchy as a Component element
and is referred to from GPART and SPCOM elements in the Specification.
As Material Texts are common across component types, it is normal to create them in a separate section.
Alternatively the Name could be a Material Short Code for example /AAA
Each SMTEX element has the common attributes TYPE, NAME, LOCK and OWNER and in addition XTEX,
YTEX and ZTEX shown on the form as Material (Isodraft), (Interface B) and (Interface C).
By default XTEX is used by ISODRAFT but this can be modified to use YTEX or ZTEX if required. These
additional attributes could be used to store the material description in a different language.
Each GPART element and specification component (SPCOM) has a reference indicator - DETREF. This is a
reference to the name of a Detail Text element (SDTEX). The purpose of a SDTEX is to carry textual
information defining the various piping components. This information is used when selecting component
types in Model, in material take-off reports and as an output on the ISODRAFT isometric material list.
Name: AAEA2BG-SG
Repeat the above operation and create a further detail text for AAEA2BG-SE (Sch. 30).
The Generic Type field displays all the standard types known to AVEVA CATALOGUE as defined in the
IsoDraft manual. Once a Generic Type has been selected, the descriptions for that type will be displayed.
Next select the required description. The act of selecting a Generic Type plus the Description will
automatically set the SKEY field.
Each SDTEX element has the common attributes TYPE, NAME, LOCK and OWNER and in addition, SKEY,
RTEX, STEX, TTEX, MtoLength, and MtoQuantity.
RTEX, STEX and TTEX are the actual text strings carried by the DTEX element.
Detail (Isodraft) is the field for the RTEX. This identifies the default used by Isodraft.
Interface B is for STEX creation and Interface C for TTEX. Either can be used in place of RTEX.
By default, ISODRAFT uses RTEX to generate component descriptions, but it is also possible to use
STEX or TTEX for the same purpose. This allows three different descriptions to be used for
components. In some European companies, this has been used to provide different language output
formats.
The fields Length and Quantity relate to the use of additional material take-off data in IsoDraft. The
value, to which these attributes (MtoLength & MtoQuantity) have been set, will be output on the ISOs
only if the MTOR attribute has been set in Model for that component. The MTOR must be set to a
relevant GPART reference or SPREF, which selects the DTEX and MTEX information plus any length
(MtoLength) or (MtoQuantity) which is set.
If both are set then only the Length will be shown. If the Quantity is required then the Length must be
unset to allow this as only one attribute may be displayed.
Text on attributes RTEX, STEX, TTEX, XTEX, YTEX, and ZTEX can be parameterised. Expressions may be
entered when defining these attributes and evaluated when queried in Model and Isodraft, for example:
QUERY RTEXT displays the evaluated text, which in the above example for a gasket with PARAM[1] of 100
is ‘GASKET 100mm NB’. Isometrics featuring this gasket will also show the evaluated RTEXT in the material
list.
The Text is a general element that can occupy many positions in the hierarchy. It can be used to store
additional information about an owning or adjacent element. The TEXT element should not be confused with
the SMTEX and SDTEX elements described above. The text itself exists as the STEX attribute of the TEXT.
The STEX attribute is completely independent of the STEX attribute of the detailing text (SDTEX)
elements described earlier in this chapter.
When creating a new specification, a TEXT element is created as the first item. This TEXT element is
required by the Model Application. If the TEXT element is not present, is not the first item, or does not have
a STEX set correctly, the specification will not be displayed on the Specification Selection form.
The STEX should be set to one of the following depending on what the specification is to be used for:
On cable tray Specifications an additional TEXT element is required. The element should be the last
member, after all the Selectors, and should have its STEX set:
If these rules are not followed, the result will be that the use of the spec is by entry on the Command
Window only and not by the Graphical User Interface.
Create a Detail Text and Material Text for each of the components previously created, select the correct
Symbol Key.
Create a Detail Text and Material Text for the Valve – the material can be assumed to be Bronze.
All Piping Material can be created in a section named PIPE-MATERIALS as they are common to all Piping
components.
GPART Families and elements are used in the catalogue to fully define a component without the need for a
piping specification. The structure of the hierarchy is as follows:
PRTWLD
PRTELE
Each PRTELE element represents a GPART family corresponding to a specific GTYPE, e.g. ELBO, INST,
REDU, etc...
PRTELEs contain a number of GPART elements, each of which fully defines an individual component.
GPART elements have attributes as follows:
Using ‘The AVEVA Material Coding System’, the Code for the Pipe Material ASTM A53 GR.A has a short
code of AAA. The created Part Family will hold Elbows made from ASTM A53 GR.A.
Construct a part family from the previously created Elbow Category AAEA2BG. To aid this task, a Part
Family Creation form is displayed.
The Part Family form is populated with the three Elbow parts.
The Part Family form is updated to include a Tasks > General Attributes pane. Set the following:
Type: ELBO
Subtype: BW
A Part Family has now been created from category AAEA2BG consisting of three components.
Each part name should fully describe the component. Both material and schedule thickness need to be
included within the AVEVA Catalogue name.
For the elbow category, the material is Carbon Steel ASTM A53 GR A (Short Code AAA).
Bore sizes 100 and 150mm are Schedule 40 (Short Code SG) and the 200 NB Elbow is Schedule 30 (Short
Code SE).
Using the Tasks > General Attributes pane, set the Gpart names and descriptions to the values shown
below:
This is the Detail Ref (Detref) and will reference an SDTE element.
The Skey and Rtext attributes can be modified by selecting Edit Iso Description.
Repeat the process to set Iso Descriptions for the 150 and 200NB Elbows.
The Material Text should be set in a similar way to the Detail Text.
Using the AVEVA coding system for weight, the weight elements for 90 Degree Butt Weld Elbows are
named as follows:
Navigate to each weight element and set the component weight reference (Cmpref) for the elbow parts in a
similar way as for Detref and Matxt.
Weight data is stored in the CWEI attribute of the CMPD element and can be modified by selecting Edit
Weight… on the Part Family form.
Create the Part World Part Elements and Gparts for the three elbows as described previously.
Create Gparts and set the appropriate references for all components created in the Component Building
Exercise (Chapter 4). Example names are shown below:
Isometric
Name Description Material Weight
Description
BW CONCENTRIC
AAASGAARC2BG-150x100 REDUCER SCH 40 AARC2BG-SG ASTM-A53-GRA RD-40-150
ASTM A53 GR.A
BW CONCENTRIC
AAASGAARC2BG-200x100 REDUCER SCH 40 AARC2BG-SG ASTM-A53-GRA RD-40-200
ASTM A53 GR.A
BW CONCENTRIC
AAASEAARC2BG-200x150 REDUCER SCH 30 AARC2BG-SE ASTM-A53-GRA RD-30-200
ASTM A53 GR.A
Isometric
Name Description Material Weight
Description
BW TEE SCH 40
AAASGAATA2BG-100x100 AATA2BG-SG ASTM-A53-GRA T-40-100
ASTM A53 GR.A
BW TEE SCH 40
AAASGAATA2BG-150x100 AATA2BG-SG ASTM-A53-GRA T-40-150
ASTM A53 GR.A
BW TEE SCH 40
AAASGAATA2BG-200x100 AATA2BG-SG ASTM-A53-GRA T-40-200
ASTM A53 GR.A
BW TEE SCH 30
AAASEAATA2BG-200x150 AATA2BG-SE ASTM-A53-GRA T-30-200
ASTM A53 GR.A
Isometric
Name Description Material Weight
Description
300# WELD NECK
ASTM-A53-
AAASGAAFW2BG-100 FLANGE R.F. SCH 40 AAFW2BG-SG FW-D-100
GRA
ASTM A53 GR.A
300# WELD NECK
ASTM-A53- FW-D -
AAASGAAFW2BG-150 FLANGE R.F. SCH 40 AAFW2BG-SG
GRA 150
ASTM A53 GR.A
300# WELD NECK
ASTM-A53- FW-D -
AAASEAAFW2BG-200 FLANGE R.F. SCH 30 AAFW2BG-SE
GRA 200
ASTM A53 GR.A
Isometric
Name Description Material Weight
Description
BW ECCENTRIC
AAASGAARE2BG-150x100 REDUCER SCH 40 AARE2BG-SG ASTM-A53-GRA RD-40-150
ASTM A53 GR.A
BW ECCENTRIC
AAASGAARE2BG-200x100 REDUCER SCH 40 AARE2BG-SG ASTM-A53-GRA RD-40-200
ASTM A53 GR.A
BW ECCENTRIC
AAASEAARE2BG-200x150 REDUCER SCH 30 AARE2BG-SE ASTM-A53-GRA RD-30-200
ASTM A53 GR.A
Isometric
Name Description Material Weight
Description
300# FLANGED
YNKAAVHAB0-100 GLOBE VALVE ANSI AAVHAB0-D BRONZE -
BRONZE
300# FLANGED
YNKAAVHAB0-150 GLOBE VALVE ANSI AAVHAB0-D BRONZE -
BRONZE
300# FLANGED
YNKAAVHAB0-200 GLOBE VALVE ANSI AAVHAB0-D BRONZE -
BRONZE
The Weight for the Globe valve will be created later in this Training Course.
This chapter covers the construction and use of Connection Compatibility Tables, Connection Compatibility
elements and use of CKEYs for Spooler.
The Connection Table (element type CCTA) holds a list of all the compatible connection types for Piping
Components in a project.
CCTA
A CCTA is an administrative element which, exists at the same level as CATA in the hierarchy. A CCTA has
two types of member elements:
Connection Compatibility (COCO) element: has a pair of coded connection types stored as a CTYPE
attribute.
These connection types are those referred to in the PCON attribute of a Piping Component’s P–points.
Connection Compatibility Description (COCDES) element: store a full description of the connection
types.
These elements are referenced by the COCO elements via a two element array attribute;
COCOREference.
Connection compatibility codes can be configured using the external file: %PMLUI%/cat/dflts/coco-table.
The following is an extract from the top of the file which explains how the COCO should be defined:
# Use this file to configure the CCTA element types (Coco table connection types)
#
# After the comment (#) lines, include the required connection types as strings, one per line with each
# string containing a maximum of 4 characters. If there are no valid entries, the coco table connection
# type list is filled from the types in the database
#
# eg.
# OPEN
# GGD
# ATT
# TUB
# BW
# FG
# FBB
#
The Connection Compatibility Table form is automatically presented to the User on COCO Table creation.
Refer to Appendix 1 for a full description of the Available Connection Type short codes.
To add a new connection, select the required short codes from the Available Connection Types scrollable
list (use the CTRL key for multiple selections).
Once the required connection types are selected, use Add to include them in the Ctype list.
Select a matching short code from the pull down list under heading Coco 1. Repeat as necessary for all
allowable connections by using the columns Coco 2, Coco 3, etc...
Right click on the grid headings to add more columns for further connections.
ISODRAFT uses the connection codes to derive bolting requirements, and so the connection codes
used must conform to certain standards; see the ISODRAFT Reference Guide for details. Setting up
the Connection Table should be one of the first tasks to be carried out when commencing a design
project using AVEVA Catalogue.
Naming of the P-point PCON attribute of a Piping Component requires early consideration. The PCON name
is for use mainly in data consistency checking, but also by IsoDraft for ascertaining bolting details. The rules
for IsoDraft are:
The first letter of the PCON attribute of a flange must be ‘F’ or ‘L’ (the latter for lap joints)
The Following table is not exhaustive and only shows example codes.
The COCO (connection compatibility) elements are named so that the allowable connections can be easily
queried. The following Connection Table, which uses the connection list above, shows, for example, that
tube can be connected to a screwed female connection but not to a screwed male connection.
Different ratings of flanges and gaskets should have different connection attributes to ensure that different
pressure fittings cannot be connected without a warning message being issued. This principle also applies
to different flange face characteristics, i.e. flat face and raised face. However, there are some exceptions; a
flat–faced flange on a piece of equipment may be butted up to a raised–face flange. If this is a common
occurrence, a new COCO could be formed to allow the connection.
If an attempt is made to connect two pipework components in AVEVA E3D Model, the following process
occurs:
YES NO
YES NO
To set a long description for the connection short codes, use Create/Modify Coco Descriptions from the
Connection Compatibility Table Form.
Q PCONDESC <N>
For example
Q PCONDESC 1 or Q PCONDESC 2
The SPOOLER module requires being aware of the basic connection or joint but not the rating, face types,
thread etc... The type of connection is identified by the attribute Ckey of the COCO.
The Ckey attribute can be set to any of the following standard Isodraft end connection types.
BW Butt Weld
SW Socket Weld
SC Screwed Connection
CP Compression
FL Flanged
PL Plain
Ckeys can be set to one of the values above using the Connection Compatibility Table form.
Alternatively selecting Utilities > Modify Ckeys… from the main menu allows modification or addition of the
standard Ckeys to existing or new COCOs.
The Edit Ckeys form is presented as illustrated below. A CCTA can be selected in the members list form
and using the CE button, populated with the required information from each COCO.
The following is a list of the catalogue components with their connection types.
Tube TUB
TUB
See Appendix 1 Pipe Catalogue Coding Conventions for a full description of the Coco Table Coding
8 Piping Specifications
The purpose of specifications in AVEVA Catalogue is similar to that in a manual design situation; it limits and
controls the designers’ choice of components for a given application. One subtle difference in AVEVA
Catalogue is that the designer cannot ‘cheat’ by including a non-specific component. All components must
be included in one AVEVA Catalogue specification before the system will allow access to catalogue data.
Specification Tables are used to assist with the creation of Piping Specifications. There are several types of
table, including Nominal Bore, Branch, Reducer, Wall Thickness and Pipe Data Tables.
Size Range tables (NOMTAB) define the nominal bore sizes and wall thicknesses that are allowed in
any specification that references the table.
Branch tables (BRTAB with PURPOSE attribute set to BRAN) define branch and header size
combinations allowed for branch items such as a TEEs or OLET in any specification that references the
table.
Reducer tables (BRTAB with PURPOSE attribute set to REDU) define the large end and small end
size combinations allowed for reducing items in any specification that references the table.
Wall Thickness tables (WTHTAB with PURPOSE set to REF) define the pipe Wall thickness for a
particular schedule and nominal bore size.
Pipe Data tables (PDAELE) define a corrosion allowance and flared flanged allowance for a particular
nominal bore size.
Before the tables can be created, it is necessary to create a Spec Table World with a Purpose of PIPE.
Select Create > Spec Table > World… from the main menu to display the Create Table World form.
To create a nominal bore range table, define the bore sizes required for the specification. For this example,
choose a range of 15-200mm
Choose a range of 15-200 mm Omit bores 65, 90 and 125 mm by using the Shift and Ctrl keys.
Add a Description:
Size Range 15NB-
200NB
Underneath NOMTAB are a number of SNOTAB elements; one for each bore size, with attributes as follows:
Once created, the NOMTAB defines a range of bore sizes and associated schedules. The table will be
referenced later in this example to assist with the build of a piping specification. Firstly, two other tables must
be created, one for branch connections and one for reducers.
To create a Branch table select Create > Spec Table > Branch Table… to display the Create Branch
Table form.
Add the bore sizes 15-200, omitting 65, 90 and 125 in exactly the same way as completed for the Size
Range Table. These sizes represent the main branch size.
Use the grid to define the fitting types at specific branch/header sizes; a list of short codes appears at the left
hand side of the form. For example:
TOL Threadolet
TR Tee - Reducing
ST Tee - Straight
STUB Stub End
PAD Reinforcing Padd
WOL Weldolet
BW Butt Weld
SW Socket Weld
SOL Sockolet
The short codes are under user control and are stored in the file:
%AVEVA_DESIGN_DFLTS%\cat-pipetablecodes.pmldat.
To specify a particular fitting, firstly select a Short Code from the list, e.g. SOL. Set the Cell Click Action to
Add and use the left hand mouse button to identify the branch/header sizes that are applicable to the fitting.
Complete the Branch Table using cell click actions as shown below:
To create a Reducer Table, select Create > Spec Table > Reducer Table… from the main menu.
Add the bore sizes 15-200, omitting 65, 90 and 125 in exactly the same way as for the Size Range Table
and the Branch Table. These sizes represent the main bores. Across the top of the form is a list of reducing
bore sizes.
Use the grid to define the fitting types at specific small/large end sizes. The reducer short codes for this
example are:
ECC Eccentric
CONC Concentric
In regards to the branch tables, select a short code and cell click action to specify a particular reducer type.
To create a Wall Thickness Table, select Create > Spec Table > Wall Thickness Table… from the main
menu.
Add bore sizes 200-900 mm in the same way as before and then enter the following wall thickness values:
To create a Pipe Data Table, select Create > Spec Table > Pipe Data Table from the main menu.
Add bore sizes 15-200mm in the same way as before omitting bore sizes 65, 90 and 125mm.
15-40mm: SCH80
50-150mm: SCH40
200mm: SCH30
The flange allowance parameter is included in the pipe data tables for use with flared flanges and
accounts for the extra length of tube required. Flared flanges will be dealt with later in the training
guide.
Before a piping specification can be created, it is necessary to create a Pipe Specification World, an
administrative top level element of the hierarchy.
To create the Piping Specification, select Create > Specification> Specification… from the main menu.
Set the Description to 300# Carbon Steel and from the pull down menu set the Spec Type to Piping.
There are three other possible types of Specification: Insulation, Tracing and Bolting.
Click the Back button and then select Edit CAD Atts.
Using the tables created earlier, navigate to each one and select CE to set references to the Nominal Bore,
Branch, Reducer and Pipe Data Table Ref. Tables.
Apply the changes and select Back to return to the Specification form.
Headings are used to wholly define each component of the piping specification. Headings vary according to
GType, for example:
PBORE (or PBOR0) is the nominal bore of the component. For multi-way components, such as Tees,
or Valves, PBORE3 is required to specify the bore size of the offline leg. For Reducers, PBORE2 is
used for the secondary bore size.
STYPE is used to further distinguish the type of component, e.g. Valves may have an STYP of BALL,
GATE, GLOBE, and CHECK. Reducers could have an STYP of ECCentric or CONCentric.
Components with the same type and bore combination must have different STYPEs.
SHOP is set to either TRUE or FALSE according to whether the item is fabricated in-shop or on site.
It is possible to set default answers in the specification. For example, for a Flange, that may have questions:
TYPE, PBORE and STYPE, the STYPE could be set to a default value of ‘WN’ to denote Weld Neck.
It is not permissible to set a default value for TYPE and generally it is inappropriate to set a default for
PBOR0. The method of indicating ‘no default’ is a ‘-’ sign. Defaults can alternatively be set to ‘=’ which
means select the first available component in the spec for a specified type and bore size.
TUBE is generally the first item to be added to a piping spec. For TUBE, the headings will be TYPE,
PBORE, STYPE and SHOP.
STYP and SHOP have a default value of ‘=’ set by using the Default text gadget
The questions can be defined individually as shown above using the Add Question button and the
Question pull down menu.
Click the Use Standard Heading Sets button to display the following task window:
Highlight the second TUBE in the Standard Headings list to display pre-defined Questions and Defaults.
Press Use Selected Headings to return to the original Tasks > Headings window.
Use Set Headings and Back to return to the Create Specification form.
The next stage is to add a TUBE category to the spec. An existing AVEVA category ‘ANSI B36 10 PE SMLS
PIPE’ will be used for this example.
Size Range
From: 15
To: 200
Stype: TUB
Select Find.
This will search all elements of type CATE in the Catalogue database.
The search is further refined to those CATE elements with a CSTA (Catalogue Standard) attribute set to
ANSI. The result of the above search lists all ANSI items in the catalogue.
From: 15
To: 200
The TUBE items are added to the Carbon Steel spec and given a unique name - the Specification
Reference (SPCOM).
The answers for selectors TYPE, PBOR0 and the Catalogue Ref are populated in the spec table and linked
to existing catalogue data held in TUBE CATEgory; AAPA100
Select Back.
To set answers for the SHOP flag, select all TUBE items in the table:
Select Back.
References are links to other parts of the database. When adding components from an existing category as
in the previous example, the Catalogue Reference is added to the specification table automatically.
Detail Reference – a description of the component, e.g. ANSI B36 10 PE SMLS PIPE SCH80.
Template Reference.
Set the detail references for the TUBE items already added to the spec CS-PIPE-SPEC
In AVEVA Catalogue(1.1) a database text string limitation causes a crash if the database
MASTER/HVACCATA is included in the MDB. Using the Command Window this database should be
excluded as follows:
mdb up
defer MASTER/HVACCATA
exit
The Detail Text can be filtered on the NAME Column as explained earlier
For TUBE 50NB – 150NB, in the name Column type /AAPA100 and Select /AAPA100-SG referring to ANSI
B36 10 PE SMLS PIPE SCH40.
For TUBE 200NB; in the name Column type /AAPA100 and Select /AAPA100-SE, referring to ANSI B36 10
PE SMLS PIPE SCH30.
The name of the component is the name that will appear on the Isometric drawing and should be changed to
reflect the Component Material, Schedule and type. The following are typical component codes for pipe.
Typically the code on the material list of the Isometric will be AAASKAAPA100, information on Isomeric
Material Codes is described later.
Enter Replace: TUBE- and With AAASKAAPA100: and click the Apply button.
Using a similar process rename all the Component (SPCO) Codes as shown below.
In this section, the Elbow Part Family created earlier will be added to the pipe specification.
Add the headings for the elbow part family as shown above by selecting a standard heading for ELBO.
Select the Set Headings and Back buttons.
Set the Size Range 15 – 200mm, Stype BW, Heading Type ELBO and Add From to Part Family List….
The Parts are fully defined (with the exception of SHOP) due to the references being set earlier on Part
Family creation.
The current part family only contains three elbows. To fully complete the Elbow section of the specification it
is necessary to search the database for additional bore sizes:
Elbows 15NB – 40NB Socket Weld Carbon Steel 3000# (/ABEB330, /ABEB330-D, ASTM-A53-GRA)
with Stype: SW
Using the TUBE example previously completed, add these elbows to the Carbon Steel spec and change
Shop to TRUE.
In this section, use the Branch Table BRAN-15-200, to add the required tees to the piping specification.
Create headings for TYPE, PBOR0, PBOR3, STYP and SHOP using Add Heading … in the same way as
completed for previous examples.
Set the defaults for SHOP and STYPE to =. Select the Back button.
Initially, the Tees created earlier in the Training are added to the Spec.
Set:
Stype: TEE
Name: AAA-AATA2BG
As the Branch code “TEE” covered all the Tees created during the Training Course, all Tees are added to
the spec. Set Shop to TRUE.
Set:
Stype: BW
Name: AATA200
AATA200 is the name of an existing TEE category containing a range of ANSI B16.9 BW Tees
Note that only Tee sizes with a Branch Code of BW have been added to the spec.
Set Shop to TRUE, the Detail Text should be changed to AATA200-D and the material text to ASTM-A53-
GRA.
Repeat the process for the Socket Weld Tees and the Half Couplings:
The Socket Weld Tees (SW) can be found in ABTA330, Detail Text ABTA330-D and Material Text ASTM-
A53-GRA.
The Half Couplings (SOL) can be found in ABTH330, Detail Text ABTH330-D and Material Text ASTM-A53-
GRA.
Create headings for TYPE, PBOR1, PBOR2, STYP and SHOP using Add Heading … in the same way as
for previous examples.
Set:
Stype: TCON.
Name: AAA-AARC2BG.
Repeat the process and add the Eccentric Reducers, setting Stype to TECC, Heading to REDU and Name
to AAA-AARE2BG.
Use the Reducer Table created earlier, REDU-15-200, to add reducers to the piping specification. This is
done in a similar way to tees.
Adding Reducers to the current specification will add duplicate reducers that will be deleted in the next
section.
In the Tasks pane, select By Reducer Code and ECC from the Reducer Code table.
Set:
Stype: ECC.
Heading: REDU.
Name: AARE200.
In addition SHOP should be set to TRUE, the Detail Text should be changed to AARE200-D and the
Material Text to ASTM-A53-GRA.
In a similar way Concentric Reducers CONC are created using the Category AARC200, Detail Text
AARC200-D and Material Text ASTM-A53-GRA.
SWGE items are created using Category 00NEB0S, Detail Text 00NEB0S-D and Material Text ASTM-A53-
GRA.
AVEVA Catalogue does not allow a SPREF to exist more than once; items in a specification that are
identical but are required to be distinguished may be allocated a suffix. Isodraft can be made to ignore such
a suffix by recognising the delimiting character which separates the suffix from the rest of the SPREF.
For example, if the delimiting character is defined as a colon (:) i.e. the default scenario, IsoDraft will identify
two components with the SPREFs /CS-PIPE-SPEC/AAASKAAPA100:15 and /CS-PIPE-
SPEC/AAASKAAPA100:20 as having the same item code AAASKAAPA100.
Note that the code displayed on the Isometric by default does not display the Piping Specification.
Refer to the IsoDraft Reference Manual for further details, including the way in which the User may
specify which character is to be recognised as the delimiter.
The following extracts show typical component codes (SPCO) for Elbows and Reducers:
The component code is based on the part number with the dash replaced by a semi-colon. Components
without parts have their names set based on Material, schedule, category and bore.
The names have been set using an “Autonaming” function which is supplied with Training Setup.
Note: the Designer must be a member of the CATADMIN Team to Define Naming Rules
Select Copy.
From the Naming Settings form, Pick Save and OK the form.
return 'error'
endfunction
Where the headings of a specification include PBOR1 and PBOR2, the specification form assumes that the
PBOR1 and PBOR2 of the items to be added must be different. This is true when the items to be added are
reducers or swages. However, there are many instances where other item types, such as flanges and
valves, are a mixture of reducing items and equal items within the same heading.
When a heading is used which has PBOR2 in the headings and the type is not a REDU, then a new toggle
is made visible on the form.
This toggle can be switched off to allow items to be added to the list where the PBOR1 does not differ from
the PBOR2. If only items of differing bores are to be searched for, then the toggle should be switched on.
As with any other aspect of AVEVA Catalogue, the task of modifying existing data is relatively simple.
Modification of a recently created specification, which has not been used, can be done with impunity. If,
however, pipes have already been designed using the specification, it is necessary to consider the
consequences of any modification.
When a pipe component has been created and selected in Model, it has a specification reference (SPRE),
which in turn carries references to the catalogue.
If an item in the specification is deleted when there are elements in the Model referencing that item, the
references to the catalogue are lost. This would mean that it would not be possible to produce drawings,
isometrics or carry out a clash check since references provide the geometry and orientation of each
component.
The method of avoiding this situation is to REMOVE specifications or specification components. When
REMOVING items, the SPCOMS are transferred to a system generated specification named LIMBOSPEC.
This means that the SPCOM is still in existence, but further use is prevented since it is no longer part of the
existing specification.
To Delete SPCOMS, use Modify > Specification, select the items required and perform: Delete
Permanently from the Tasks panel.
There are duplicate Reducers in the used specification and, as they have not been used, they can be
deleted.
To maintain upwards compatibility, SPECON still exists as a separate module and the old method of spec
generation using the Command Window and macro input remains the same.
In addition, SPECON can be accessed from the Paragon GUI by issuing the command SPECONMODE.
This mode accepts Command Window and macro input in exactly the same way as SPECON but saves the
User from performing a module switch.
Once in SPECONMODE, enter the command EXIT to return to the Paragon GUI.
A utility is provided to convert old style (pre PDMS 12.0) piping specifications to the new 12 series format
specs including Parts. Select Utilities > Convert Spec… to prompt the Convert Spec form.
The converted spec SP/A1A has an extra Part Ref reference column which points to the newly created
GPART associated with the piping component.
Create the associated Nominal Bore, Branch, Reducer, Wall Thickness and Pipe Data Tables.
Add the Flanges and the Valve from the Parts created in the earlier Component Building Exercise.
Create Headings for the addition of a Gasket category and search the catalogue for a suitable 300#
gasket to include.
Remember to Savework
The following chapter outlines the creation of a simple pipe in Model using components created in previous
chapters from the new piping specification.
Start > All Programs > AVEVA Plant > Design > AVEVA Everything3D
Login to Model using the details provided by the Trainer. They will typically be as shown below:
Project Training
Username A.PIPER
Password A
MDB A-PIPING
Click Model
In a similar way Pick Zone and create a new zone in this newly created site.
Enter the following into the Pipe Editor: Create Pipe form:
Bore: 100mm.
Direction: E.
Bore: 100mm.
Connection: OPEN.
Direction: W.
East: 2000.00.
Pick Zoom to Drawlist and Isometric > ISO 3, using the R.H. Mouse button to display the pipe.
Create a simple pipe using the spec and components created earlier.
Try to use and many components as you can using different sizes.
This chapter covers the construction and use of Insulation catalogue data, together with its use in the
AVEVA E3D Model.
Insulation in non-AVEVA Catalogue terms is the application of material to piping to either keep it hot or cold,
depending on the service required. As far as AVEVA E3D is concerned, it has the effect of ‘thickening’ up
the ‘pictorial’ appearance and clash geometry. The relevant considerations are as follows:
Spacing/positioning of pipes
This is a practical consideration and obviously dependent on the type and configuration of the
insulation. In the AVEVA E3D Model, positioning operations such as BOP (Bottom of Pipe),
CLEARANCE, BEF, BEHIND etc… will take insulation into account if it is selected.
Pictorial Representation
The pictorial representation is, as with any element in AVEVA E3D, user definable. Primitives can be
displayed with or without an insulation thickness.
Temperature
Piping can be insulated to the same specification but require a different thickness depending on the
temperature of service. The insulation specification can be set up such that it is selective in the
application of insulation due to temperature.
The application of the above will become more obvious and explained more fully by the following sections.
Insulation can be applied to a component shape by adding an IPARA to the Geomset definition of the
cylinder that depicts, say, the main body of a TEE. Alternatively, a new shape can be added to the Geomset
that ’wraps around’ the basic shape and has an Obstruction value of Soft.
The insulation value, IPARA, is made to operate by the temperature set in the Model against the pipe.
Normally there will be an insulation specification that establishes the differing thickness of insulation for
varying requirements.
Display the elbow category AAEA2BG created earlier. Select Geometry in the Model References pane and
navigate to the SCTO type that represents the Elbow Shape.
Test the Insulation is being displayed correctly by changing the Component Representation.
When a Catalogue Component is defined using insulation parameters, its dimensions are not completely
specified in the Catalogue. So that Paragon can give some idea of what the Component will look like when
used in a Model, it is possible to define specimen values for the insulation parameters. These specimen
values apply to all Components, unlike the component parameters which are attributes of a particular
Component.
Insulation values can be set in one of two ways; if the Insulation Specification already exists it may be
selected by using the Insu Gadget on the Model Parameters form. Adjusting the temperature will vary the
thickness.
Alternatively, using the same form, a value may be entered by selecting Insul. Parameters under the
Parameter Settings gadget, and entering a No. and Value. This is followed by selecting Insert in the
gadget window.
The values are set using Settings > Model Parameters… to display the following form:
The INSULation component is created in the catalogue and exists only as a NAME, GTYPE and PARA.
There is no requirement for a Point Set or Geometry Set.
At CATA level, create a new Section named Insulation and a new Category named E3D-INSULATION.
Navigate to the Component as shown on the Model View form and enter:
Name: I-25.
Desc: Insulation 25. Generic
Type as INSU.
Parameter 50.
Navigate to the Category and use Copy to create four further insulation components. Rename the new
components and set the value of the first parameter as below:
I-30 PARA 60
I-40 PARA 80
I-50 PARA 100
I-65 PARA 130
The PARA value is set to twice the thickness required. The thickness is applied to all sides of the
primitive. A second parameter IPARA 2 may also be added for use with insulation on one side of a
component. Also Insulation may also be calculated using an expression
This insulation specification is created from the engineering spec in the same manner as the piping
specification. AVEVA Catalogue allows ranges of Temperatures and Bores to be entered into the insulation
spec. If the Engineering requirement is as follows, the AVEVA Catalogue Specification macro would follow
the manner shown on the following page.
Nominal Size Temp Insulation Thickness
120-200 25
40-150 201-300 50
301-400 65
120-200 30
200-300
201-300 65
The macro can be run in SPECON or SPECONMODE. Alternatively, the UI can be used to generate the
insulation spec as described below.
TEXT 'INSU'
HEADING
If you can use the Standard Heading Set INSU make sure the order is as shown.
Click on CE.
The bores and temperature ranges will need to be updated manually as shown below:
Select Edit Answers and ensure the following fields are complete:
Remember to Savework
In Model, if the Insulation Specification (ISPEC) is set to WW and the temperature (TEMP) is set to one of
the ranges specified, the soft volumes will be visible for Clash Detection.
ISPEC and TEMP are cascading attributes, i.e. if set at Pipe level, the same values will automatically be set
at Branch level. However, only ISPEC is cascaded down to individual components.
It is possible that branches owned by the same pipe will have different insulation, or that a branch may only
be partly insulated. These conditions can be satisfied by setting / un-setting the ISPEC attribute.
From the Modify section on the Piping Tab Pick Spec / Bore
Right Click on the Selected Items and select Modify Insulation Spec
Note how the design representation alters to reflect the insulation applied.
Add Insulation (IPARA[1]) to the Geometry of all the components created earlier.
Create the required Catalogue hierarchy to store Insulation Components I-25, I-30, I-40, I-50 and I-65
as described above.
11 Nozzle Specifications
This chapter covers the Specification Generator Application which is used to build a structured nozzle
specification from an existing set of catalogue items. Items added to a nozzle specification may be selected
in the AVEVA E3D Model.
In Paragon, from the main menu, select Paragon > Spec Generator… to enter the Spec Generator
Application.
To create a new Specification World (SPWL) element, navigate to PIPING/CATA-A and select:
Setting the Generic Type, sets the Purpose (PURP) attribute at SPWL level
To create a new Specification (SPEC) element, select Create > Specification… from the main menu.
In the Build Specification form, create a new nozzle by selecting Gtype > Add….
Select (Para 1) Name from the pull-down Name field. This will display Parameter 1 (Bore) of each nozzle on
the Category being loaded into the form by pressing the Load button. Selecting the sizes shown and
pressing the Add button will place these items into the Spec. Any sizes added by mistake may be
removed by being highlighted in the Entries column and using Remove.
From the pull down bar menu on the Nozzle Specification form select Gtype > Add…
The description that is entered here will be displayed against the Nozzle Type and Generic Type on the
Create Nozzle and Nozzle Specification forms in Model.
Use the Add Button to select the range of sizes required. Select Control > Build from the menu bar on the
Build Specification form, and then select Control > Close to dismiss the form.
A full list of specifications can be viewed using Display > Specifications… from the application main menu .
Selecting the Spec World Type as Equipment will filter out the available nozzle specs.
To modify an existing Nozzle Specification navigate to that SPEC and select: Modify > Specification from
the application menu bar. The Modify - Nozzles Specification form appears:
The form is the same as for building nozzle specifications and many of the actions to modify an existing
specification are the same as building a new spec.
The Generic Types list shows the current description of the nozzles contained in the spec. To edit the
entries in this list highlight the entry, and select the Gtype > Description… option from the form’s menu bar,
and amend the generic type description as required.
Selecting Gtype > Remove will cause all selectors and Spcoms to be deleted.
The Entries list shows all catalogue components currently accessible via the Specification for the
highlighted Generic Type. This list may be edited as follows:
To Add one or more components navigate to the CATE in the Explorer, which contains the required items,
and press the Load button. All available components will be listed by name in the Category list.
Navigate to AAZFBD0
Highlight those items to be added to the SPEC and press the Add button to copy them into the Entries list.
To Remove one or more components from the SPEC, highlight the items in the Entries List and press the
Remove button.
The Entries list shows only those components, which are to be included in the current SPEC. Select
Control > Build from the Build Specification form to rebuild the modified Specification.
Build a Nozzle Specification for 150# (AAZFBB0), 300# (AAZFBD0) and 600# (AAZFBF0) ANSI Nozzles
increase the range to cover 15 – 600 NB.
Create a new Nozzle and modify an existing Nozzle using the Nozzle Icon from the appropriate part of the
EQUIPMENT Tab in the AVEVA E3D Model
12 Bolting
This chapter describes the bolting facilities in AVEVA Catalogue. It covers MIXED Bolt Sets and how to
include additional items such as NUTs, WASHERS etc. on the MTO in IsoDraft.
The Bolt Table hierarchy contains information describing the nature of the bolted connection of Piping
Components in a project. Although the Bolt Table is part of the Catalogue Database, it has been designed
for the exclusive use of Isodraft and so is described in detail in the Isodraft Reference Guide; only a
summary is presented here.
CATALOGUE WORLD
SECT
BTSE
The BOLT SET is the administrative element for ‘NEW’ bolting information. It owns Bolt point (BLTP)
elements. BOLT SETS are not required for ‘OLD’ bolting.
BLTP
The bolt point stores the bolting information for each bolt hole on the flange, and has the following
attributes:
This information is relevant to a particular Piping Component, e.g. BTHK is the bolt length necessary for that
Component only and will be matched with a BTHK from the BLTP of the Component to which it is bolted in
the Model. There must be a BLTP for each bolt hole within a Component unless all bolts are identical.
BLTA
The BOLT TABLE is an administrative element.
BLIS
The BOLT LIST is an administrative element, which groups together Standard Bolt (SBOL) elements.
SBOL
The STANDARD BOLT element which has the attributes:
Any associated nuts, washers and other bolting items can be included using BITEM to store their type,
and BITL to store the length of the additional items.
LTAB
The LENGTH TABLE holds a number of DIAMETER TABLES.
DTAB
The DIAMETER TABLE, one for each size of bolt, has information on standard bolt lengths, held as a
string of values in its BLEN attribute. DTAB is accessed from the NSTD attribute of the SBOLT element.
The AVEVA Catalogue bolting facilities allow Isodraft to calculate correctly the lengths and numbers of bolts,
provided that all bolts within a given connection are of equal length.
The method used for calculating bolting requirements is determined by the connection compatibility (COCO)
codes for the fitting in question.
Any reference to component connection types (PCON attributes) beginning with one of the letters F or L will
cause Isodraft to attempt to calculate bolting requirements. In order for the requirements to be calculated
correctly, the following conventions must be adhered to.
For flanges and flanged fittings, the PCON for the flanged face must begin with either F or L (lap
joint). There are no restrictions on the other letters of the PCON attribute name, up to a maximum of
four letters.
For gaskets, both faces must have a PCON beginning with G. There are no restrictions on the other
letters of the PCON attribute name, up to a maximum of four letters.
For wafer fittings, both faces must have a PCON beginning with W. There are no restrictions on the
other letters of the PCON attribute name, up to a maximum of four letters.
For lap joints, the side of the flanged component away from the gasket must have a PCON which does
not begin with F, L, G or W.
FLAN
LJSE
GASK
© Copyright 2012 to current year. 150 www.aveva.com
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Everything3D (1.1)
Piping Catalogues and Specifications TM-1840
LJSE
FLAN GASK
For fittings that do not require bolts to be calculated, the PCON can be any combination of letters
provided that the first letter is not F, L, G or W.
The piping specification has an attribute BLTM (Bolting Method) which must be set to ‘NEW’ and a
BSPEC reference attribute which should be set to the bolting specification name.
Piping Component SPCOMs within a spec are no longer required to have the BLTREF attribute set.
Bolting details etc. are accessed via the BLRF attribute of the catalogue component which will point to a
BTSE (Bolt Set).
At the first component find the BTSE via the CATREF and store the appropriate P-point of the component.
If the second component connection type starts with G (a gasket) get its P1 – P2 distance, and go to the
next component. If its connection type starts with F or L, go to the BTSE via the CATREF and store the
appropriate P-point of the component.
Select the bolt from the Bolt Specification and obtain its standard (rounded up) length.
The calculation of bolts through wafer components is the same as the standard flange – gasket – flange
calculation, with the following differentiation:
If within the joint, a component’s connection type starts with W (wafer), get its P1 – P2 distance, and go
to the next component.
The joint may contain any number of wafer components, and any number of gaskets.
The calculation of bolts through components with mixed bolt needs is the same as the general wafer
calculation. However, the calculation allows for different bolts in the set to stop at different places within the
joint.
If the BTYP of the bolt is JACK, TAP or CAP, this will complete that particular bolt calculation. A subsequent
BTYP of JACK, TAP or CAP for the same bolt NUMBER further on in the joint triggers a new bolt.
Nozzle flanges are handled exactly as other flanges via a BLRF of CATREF.
Once the accumulated flange and wafer thickness has been calculated, the lengths of elements such as
nuts and washers are added. The Bolt SPCOM SBOLT, has an attribute BITL, which stores the thickness of
washers and nuts, whilst the attribute XTRA can store a value for extra thread lengths.
Bolt Sets and Bolt Points can be created or modified using the Bolting References pane accessed by
selecting Bolt Set from the Model References section of the Model View form:
There is one Bolt Point (BLTP) for each bolt hole in the component.
If all the bolts are the same by selecting “No of identical Bolts (BTSE)” the Number, Diameter, Bolt Type and
Thickness can be set at The Bolt Set Level in individual bolt points are not required.
Bolt BDIA -
Diameter
This can be a property, fixed numerical value,
Bolt BTHK component parameter or a mathematical
Thickness expression. e.g. (RPRO FLTH)
BTHK, BDIA & BTYPE attributes can all be set to actual values or Design parameters.
Components with blind holes have the tapping depth assigned to their BTHK.
Jacking bolts have their BTHK set to the sum of the flange/facing thickness and the required opening
gap.
Wafer components with special bolting needs require the BTHK values set for the specific Bolt Points
affected.
GASKET
2No. WELD NECK FLANGE
COCO GBD
PREF /T300CS/TAFWD0:150
Distance P1 to P2 is 3mm
COCO FBD
BSPEC /T300CS-BOLTS
BLTM ‘NEW’ Isodraft will look for a Bolt Set when
No setting required
BLTM is set to NEW
TEXT ‘PIPING’
TYPE NAME PBOR0 SHOP STYP CATREF DETAIL MATXT CMPREF BLTREF
DEFAULTS
- - 0.00 = =
FLAN */TFAWBD0:150 150.00 TRUE WN /TAFWBD0-150 /TAFWBD0-D /CS =0 =0
TYPE NAME BDIA BTYP BSEL CATREF DETAIL MATXT CMPREF BLTREF
DEFAULTS
- - - STUD A /BOLT
BOLT */STUD:20 20.00 STUD A /BOLT /STUD-D /BOLT-M =0 /BOLT20
=0
BOLT */CAP:20 20.00 CAP A /BOLT /CAP-D /BOLT-M /CAP20
BOLT */WASH:20 20.00 WASH A //WASH-20 /WASH-D /BOLT-M =0 =0
BOLT */NUT:20 20.00 NUT A / NUT-20 /BOLT-D /BOLT-M =0 =0
WORLD /*
SECT SECT
/METRIC-BOLT-SETS /FLANGES
BLIS LTAB
/BLIST-TRAINING /LTAB-TRAINING
CATE
BTSE /TAFWBD0 SBOL
/TAFWBD0-MB-150
/BOLT20
SCOM
/TAFWBD0-150 XTRA 3 DTAB
BLTP BITL 20 2 2 20BITEM
NUT WASH WASH NUT
BLTR
NSTD /D20
Num 1 /TAFWBD0-MB-150 BLEN (50 60 70 80)
BDIA 20
BTHK PARA 5 BOLT Length
BTYPE BOLT Default
PARA5 30
Selection
In conjunction with the diagram shown in Section 12.4, the following points detail Bolt selection. In the first
instance Bolt Selection is triggered by:
Isodraft looks at the Pipe Spec and if the Bolt Method (BLTM) is ‘NEW’, Bolts are selected as follows:
2. The Flange Specification Reference (SPREF) points at a Specification Component (SPCO) in the
Piping Spec.
3. The Specification Component (SPCO) has a Catalogue Reference (CATREF) which points at a
Component (SCOM)
4. The Component (SCOM) has a Bolt Reference Table (BLTR) which points at a Bolt Set (BTSE).
The Bolt Set (BTSE) can define a number of Bolts with a Bolt diameter, Thickness and Type, or a series of
Bolt Points (BLTP); one for each bolt. Bolt selection is the same in all the cases.
In the example of Section 12.5, Bolt Number 1 is selected using the following information: Bolt Diameter
(BDIA) 20; Bolt Type (BTYP) BOLT and Bolt Thickness (BTHK) PARA 5 of the Flange.
1. Isodraft checks the Pipe Spec for the Bolt Spec (BSPEC) to use.
2. The Bolt Type (BTYP) of the flange is BOLT but the default in the Bolt Spec (BSPEC) is STUD – this
default has a greater importance compared to BOLT and is therefore used.
3. Isodraft searches the bolt spec for a 20 Dia. STUD and finds a Bolt Reference (BLTREF) of BOLT20
this will be used for the bolt length calculation.
4. The Bolting Code, Detail and Material information is also selected for use on the Isometric; the bolt
length once calculated can also be added to the CODE.
5. The BOLT20 Bolt Length Calculation is performed as follows using the Bit Items (BITEM) and Bit
Length (BITL):
½ XTRA 1.5
Nut 20
Washer 2
Gasket 3
Washer 2
Nut 20
½ XTRA 1.5
Total 124mm
6. Once the Bolt Length has been calculated a reference is made to a Standard Length Table (DTAB) to
find the next allowable size; in the example case, this is 130mm.
7. Isodraft selects each one of the Bit Items from the Specification: 20mm Nut, 20mm Washer, 20mm
Washer and a 20mm Nut. In each case the Code, Detail and Material information is selected for use on
the Isometric
The selection is repeated to for the next bolt and the bolts are accumulated.
Use the following worked example to create a Boltset (BTSE) and Bolt Points for the Flange and Valve
created in the training catalogue. Use STUD bolts, and create NUTS and WASHERS.
Create a new Bolt Specification and set this as the Bolt Spec for the Piping Specification /CS-PIPE-SPEC.
The bolt requirements for the ANSI 300# Flanges already created are:
150mm 12 M20
200mm 12 M24
Create a bolt table and bolt specification for an extended size range as follows:
ANSI 300#WN
No of Bolt Holes Bolt Diameter
Flange Bore Size
50mm 8 M16
100mm 8 M20
150mm 12 M20
200mm 12 M24
250mm 16 M27
300mm 16 M30
400mm 20 M33
Bolt Tables are used to hold Bolt Length Tables (LTAB) which store Standard Bolt Lengths for specific
diameters (DTAB). Bolt Lists are used to group together standard bolt elements (SBOL).
From the main menu bar, use: Create > Bolt Table Utilities…
A new BLTAB element is created and the Bolt Table Utilities form is displayed:
Create a new Length Table element (LTAB) by clicking Add Length Table.
Create a new Diameter Table element (DTAB) by clicking Add Diameter Table.
Name the table D16 and set the standard bolt lengths for this table as shown below.
Set the start length to 50, interval 10 and the end length to 200, Start Weight 0.079, Weight Interval 0.014
any lengths not required can be deleted using the Delete Length button. Click the Apply button. The bolt
lengths and Weights are created
Create the following standard length tables for bolt diameters in increments of 10mm:
Name Start Length Length Interval End Length Start Weight Weight Interval
D12 50 10 150 0.045 0.007
D16 50 10 200 0.079 0.014
D20 80 10 200 0.207 0.02
D24 100 10 220 0.424 0.03
D27 120 10 220 0.467 0.04
D30 120 10 260 0.69 0.05
D33 150 10 300 1.15 0.06
On calculation of the bolt length these tables will be used to round the bolt length up to the nearest standard
length.
12.5.4 Creating a Standard Bolt List (BLIS) / Bolt List Elements (SBOL)
Select the Single Bolting tab from the Bolt Table Utilities form.
Click Add Single Bolt List to create the administrative level of the hierarchy (BLIS).
Create a Stud Bolt using Add Bolt from the Single Bolt Elements pane to create the SBOL element and
set the attributes values as follows:
Extra Length: 3
Bolt Items:
NUT WASH WASH NUT
The Bolt Items allow additional requirements such as washers, nuts, etc... to be stored in the database.
Once the Bolt has been selected, additional items can be selected from the bolt spec using the BTYP
selector.
Extra Length is used to add any additional Bolt length required, this for example, may be used to cater for
extra threads beyond the end of the Nuts.
Non Std Bolt Length is a pointer to the Bolt Non. Standard Length Table i.e. /D16
It is not necessary to set Diameter, Lengths or Number of Bolts. These attributes were used by earlier
versions and are not now required.
A further CAP Bolt is required to select set screws on a Wafer Valve. Create a new SBOL element as above
and shown below:
Create further STUD/CAP bolts; S-BOLT20, CAP20, S-BOLT24, CAP24, S-BOLT27, CAP27, S-BOLT30,
CAP30, S-BOLT33, and CAP33.
Create a new section to hold the bolting Material Text elements. Name the section BOLT-MATERIAL-TEXT.
Create a new Section and a new Category to contain dummy components for the Stud Bolts, Cap Bolts,
Nuts and Washers in order that the CATREF attributes in the bolting spec can be set.
Set the Section name to /BOLT-CATA.SECT and the CATE name to DUMMY-BOLTS.
There is no requirement for either a point set or a geometry set. Set GTYPE to BOLT. The first parameter
should be set to the bolt diameter as follows.
12.5.8 Washers
Create a Category to hold Washers in a similar way to the Bolts navigate to the Section name to /BOLT-
CATA.SECT and create a new CATE named WASH.
There is no requirement for either a point set or a geometry set. Set GTYPE to BOLT. The first parameter
should be set to the bolt diameter as follows.
12.5.9 Nuts
This should be repeated for Nuts navigate to the Section name to /BOLT-CATA.SECT and create a new
CATE named NUTS.
There is no requirement for either a point set or a geometry set. Set GTYPE to BOLT. The first parameter
should be set to the bolt diameter as follows.
Create a new Detail Text element to hold the description of the STUD bolt.
Create three further Detail Text elements for washers, nuts and caps as follows:
Type – BOLT
SubType – STUD
Each Bolt Part must have the Bolt Reference set to its appropriate SBOL for example. S-BOLT16, S-BOLT20,
S-BOLT24, S-BOLT27, S-BOLT30, or S-BOLT33.
Rename the Parts HDGSTUD-16, HDGSTUD-20, HDGSTUD-24, HDGSTUD-27, HDGSTUD-30 and HDGSTUD-
33.
TRAINING.PARTS.BOLTS-CAP
Set the Bolt Reference to the appropriate SBOL for example. CAP16, CAP20, CAP24, CAP27, CAP30 or
CAP33.
TRAINING.PARTS.BOLTS-WASH
TRAINING.PARTS.BOLTS-NUTS
Use Modify > Name… to change the Bolt set name to /AAFWABG/BTSE_100, for use with the 100NB
Flange.
Select Create > Copy… from the main menu and make a copy of the Bolt set for the 150NB and 200NB
Flanges.
Copy AAFWABG/BTSE_100 to
AAFWABG/BTSE_150.
Copy AAFWABG/BTSE_150 to
AAFWABG/BTSE_200.
Use Modify > Category… from the main menu bar. Highlight the Component in the Model References
panel.
Check the Bolt Set: for a 100NB Flange it should be set to /AAFWABG/BTSE_100.
Repeat the process for 150NB and 200NB Flanges, changing the Bolt Set as appropriate.
Select component /AAFWABG-100 and Bolt Set /AAFWABG/BTSE_100. The panel at the bottom of the
form can now be used to create the Bolt Points required for the Flange.
Create a metric bolt set for the Flange: 8 NOFF, M20 Bolts.
There are 8 identical bolts; select No of Identical Bolts (BTSE) from the toggle buttons.
Number Off: 8
Bolt Diameter: 20
Bolt Thickness: PARA 6
Bolt Type: BOLT
There are 12 identical bolts, select No of Identical Bolts (BTSE) from the toggle buttons.
Number Off 12, Bolt Diameter 20, Bolt Thickness PARA 6, Bolt Type BOLT.
There are 12 identical bolts, select No of Identical Bolts (BTSE) from the toggle buttons.
Number Off 12, Bolt Diameter 24, Bolt Thickness PARA 6, Bolt Type BOLT.
If the BTYP for both sides of a joint is set to BOLT, the default bolt of the given diameter is used.
If the BTYP for one side of the joint is set to BOLT and the other side is set to anything other than
BOLT, the BTYP of bolt specified by the other side will be used.
For example, a bolted through flange may have its BTYP set to BOLT, and the mating flange may
require cap screws and have its BTYP set to CAP. In this case, the cap screw overrides the default
type, and the selected BTYP will be CAP. A BTYP of Cap is also used to trigger a new bolt.
If both BTYPs are the same and are not set to BOLT, the bolt with that BTYP is selected. If the BTYPs
are not equal and are also not set to BOLT, the BTYP from the start of the bolt is selected.
Create a new spec named T300CS-BOLTS. Set the description to Example Metric Bolting Spec and the
Spec Type to Bolting from the pull-down menu.
Define the headings TYPE, BDIA, BTYP and BSEL for the bolt specification as shown below:
Select the button Set Headings and Back to return to the Create Specification form. Navigate to the
Category /DUMMY-BOLTS.
Apply the changes to add the Dummy Bolts to the spec and select Back.
Using the same methodology, add the Cap Screws, Washers and Nuts to the bolting specification.
For each type, use as appropriate part Family and a BTYP of CAP, WASH or NUT.
Once the bolting specification is complete, edit the piping specification CS-PIPE-SPEC to reference the bolt
spec:
Verify the described worked example to ensure all components of the Bolt Table, Catalogue and
Specification have been created and are usable.
Using the knowledge gained from this chapter, create a Wafer Valve as shown below:
2 56 Total Length
11 19 Tapping Depth
Create a Wafer Valve as shown in the illustration; make sure that the Connection type is set to WFBD.
A COCO that starts with W indicates to AVEVA Catalogue that the valve is a Wafer fitting and would fit
between flanges. PARA 11 will be also used for the length of the CAP Screws. Remember to create a
CATE to hold the components. Use AAVWBD for the CATE name
Create a Detail Text named AAVWBD-D Detail “300# Butterfly Valve” select Genetic Type VALVE
and Description Butterfly Valve (FL) this will give an SKEY of VYFL.
Create a new Bolt Set for the VALVE, use Individual Bolts (BLTP). 8 through bolts and 4 Cap Screws
are required. Remember if the Bolt Type is set to BOLT the default bolt in the bolt spec is selected.
Test in Model and produce an Isometric of the pipe. The bolting appears as follows:
8 - 20mm Diameter Cap Screws 70mm Long (two for each cap hole) .
24 - 20mm Diameter Washers (two for each Stud Bolt and one for each Cap Screw).
This chapter covers the use of Design Variables DDHEIGHT, DDRADIUS and DDANGLE Design
Parameters (DESPARAM) and Datasets.
13.1 Objectives
During the creation of Catalogue components, the use of parameters reduces the number of geometry and
pointsets that are required. Design Parameters (DES PARAM) can also be used in a similar way to
Catalogue Parameters.
There are occasions when certain parameters need to be variable. Users will be accustomed to stating the
HEIGHT of nozzles (which are catalogue components) and perhaps, the angle on a pulled bend by defining
a non-orthogonal direction. To achieve this end, the following Design Parameters are used:
These parameters are used in element pointsets and geomsets, where an element has attributes of height,
angle or radius.
When creating a bend in Model, the syntax ANG 60 for example, is used to specify the design data angle.
In order to cater for the setting of angles in a pointset, the direction of the points need to be defined
differently. For a PTAX element, the PAXI attribute is set between two axes; for example, PAXI Y DDANG Z
where DDANG refers to the angle attribute from the Model database.
The Settings > Model Parameters form, described in Chapter 10.3 above, can be used to specify values
for the Component Design Data attributes. The Default values are shown when the form is first selected and
these are Design Radius 225, Design Height 100 and Design Angle 90.
Design parameters allow components to take dimensions from the Design Parameter Array in the Design
Database. Each Design element has a design parameter array which allows any component with a SPREF
to use the values stored in Design to complete that component’s definition. For example, DESPARAM 4
would refer to the fourth value of the design parameter array of the design element. Design Parameters can
be used anywhere that component parameters are used.
For example, the distance of a P-point could be defined by entering: PY (PARAM[1 ]).
This means that the value assigned to the distance along the Y axis is value of parameter 1 from the
catalogue component.
Alternatively using Design DB Parameters, the distance could also be expressed as: PY (DESPAR[4 ] ).
This statement uses value 4 from the Despara array attribute in the Model DB.
A Dataset (DTSE) is an administrative level of the hierarchy that contains a number of DATA elements; one
for each component parameter. If a Dataset is created for a catalogue category, it can be queried directly
from within Model or Draw.
The DTSE and DATA elements are created automatically when the Create > Category form is used to
create a new component category.
A Dataset can be modified by selecting Modify > Data Set... from the main menu. For the WAFER VALVE
AAVWBD created earlier, the Dataset is as shown:
The Key setting is the trigger that allows a specific DATA element to be referenced from within DESIGN or
Draw.
For the butterfly valve, the height to the top of the hand level is set to PARA 4, and consequently the valve
P-point P3 has PZ = PARA 4. Using Data Sets, this could be expressed as a Design Parameter thereby
allowing the hand lever height to become a Design variable.
Modify the Valve Pointset. Set P-point P3 to have PZ = (RPROP HLHT) and press the Apply button.
Modify the Valve Geometry Set. Alter the primitive SBOX. Set PZ = (RPROP HLHT) and click the Apply
button.
Alter the primitive SCYL. Set PHEI = (RPROP HLHT) and click the Apply button.
To test the Component use Settings > Model Parameters… from the main menu bar.
Select Design Parameters… from the Parameter Settings pull down menu.
In the prompted Model Settings form, set No to 1, allocate a Value of 500 and select Insert.
The pictorial representation of the Valve changes to reflect the new Hand Lever Height:
Modify the Dataset on the WAFER VALVE to make the Handwheel Lever Height a Design Parameter.
14 Flange Offset
(PWALLTH(1) + 2mm)
The following example illustrates the creation of a 300# Slip-on Flange using a Flange Offset based on Wall
Thickness.
Parameters:
1. Nominal Size.
2. Lay Length.
3. Face Connection.
4. Tube Connection.
5. Flange Diameter.
6. Overall Thickness.
7. Flange Thickness.
Name GTYPE 1 2 3 4 5 6 7
AAFHBD3-100 FLAN 100 0 FBD SWF 254 42 32
Name: AAFHBD3-D
Generic Type: Flange.
Description: Slip-on Flange (Symbol Key FLSO)
Detail (Isodraft): 300# SLIP-ON FLANGE R.F. (Inc. Wall Thickness).
Verify the described worked example to ensure all components of the Slip-on Flange have been created and
are usable.
The Flange allowance parameter is used to set the ALLOW and LOOS
attributes on the Flange
PDTAB Expression
Pflallowance ( 10 * ATTRIB PWALLT(1) )
The following example illustrates the creation of a Loose Flange with extra tube being supplied for the
creation of a flared end. The example is based on using Pipe Wall thickness to calculate the extra tube.
( 10 * ATTRIB
PWALLT(1)).
1 Nominal Size.
3 Face Connection.
4 Tube Connection.
5 Flange Diameter.
6 Flange Thickness.
Name GTYPE 1 2 3 4 5 6
AAFHBD3-100 FLAN 100 0 FBB TUB 229 24
P-point 1 and P-point 2 are both on the Flange face as Parameter 2 (Lay Length) is set to 0:
The Backing Flange is set back from the flange face by the Pipe Wall Thickness (PWALLT(1) )
The Bolts required for the Flange need to be longer to take into account the Flange Thickness and the Wall
Thickness, typically ( RPRO FLTH + PWALLT(1) ).
Create a Detail Text for the Flange and set the attributes as follows:
Navigate to each SCOM and set the CompType to ALLO using the Attributes Form which can be displayed
using the R.H. Mouse button on the Catalogue Explorer.
Using Chapter 15 as a guide, create three Loose Flange parts with a Flange Allowance; ensure that the
CompType is set to ALLO.
Add the GPARTS for the Slip-On and Loose Flange to the Piping Specification /CS-PIPE-SPEC created
earlier.
The loose Flange is rated 150#, therefore a 150# Gasket will be required. Select the Gasket CATE
/ACGCBBG and set the Material reference to /GAM (Asbestos Free).
Create a new Pipe in Model; selecting both a Loose Flange and a Slip-On Flange.
In Model create a Pipe as shown below containing a Slip-on Flange and a Loose Flange. Navigate to the
LOOSE Flange and query the wall thickness and Flange Allowance.
Q PWALLTH(1).
PWallthickness: 6mm.
Q FLALLOWANCE.
Flallowance: 60mm.
In this example the distance between P1 and P2 is 8mm a Wall thickness of 6mm + 2mm.
If a Flange has a CompType of ALLO, AVEVA Catalogue will automatically set the Flange Attributes
Loose and Allowance on selection. These attributes can also be manually overwritten if required.
Q LOOSE
Loose false
Q ALLOWANCE
Allowance 60mm
The ATTA element was initially introduced as a piping component to mark the position within a branch
where a support or some other attachment was to be positioned. The use of the ATTA element has been
expanded and used for many other purposes, but they are used mainly by Isodraft. Listed below are the
most common uses of ATTAs in Isodraft:
Support.
Comment.
Flow.
Splitting.
Insulation Change.
Penetration.
An ATTA element has an attribute ATTY (Attachment Type) which is set according to use. The following is a
selection of ATTY Types.
ATTY Use
Unset, HANG,WELD Support
Attachment Points are similar to TUBI elements in that they have NO Geomset, only a point set. Two PTAX
elements are required, as follows:
1 2
P-point number
NULL NULL
Pskey
PARA 3 PARA 3
ConnectionType
PARA 1 PARA 1
Bore
ALL ALL
Pvisibility
-X X
Axis Direction
unset unset
PZ Axis
0 0
Distance
Currently only ATTAs added into a piping specification for use as Penetrations require an SKEY setting of
(FLOR), all other ATTA use is interpreted directly by Isodraft from the ATTY setting stated in Model.
Exercise 17 - ATTAs
All Specifications require Attachment Points to be included. Define the headings TYPE, PBOR0, and STYP.
Set the default STYP to AT.
Navigate to the Category ATTAS and add ATTA 15 – 200 to the spec /CS-PIPE-SPEC; created earlier with
an STYP of AT.
Test the use of ATTAs in Model for indicating Support Positions and for the addition of a comment. In both
cases set the Stext to an appropriate string to be displayed on the Isometric, for example “PS-0001” or “Do
Drill Through”.
17 Bends
Bends can be represented in two ways within AVEVA E3D Model: Pulled or Mitred. Bends can be of fixed or
variable radius and angle. Bends can also be used to correct tolerances on sloping Pipes.
A Bend with no geometry is assumed to be a Mitred Bend. Mitred bends can be built with a fixed number of
segments or cuts. The User can also specify the number of segments when building the design.
As the example below shows, Mitred Bends do not have a Geometry Set.
If Para 4, Number of Cuts, is set to -1, the number of cuts must be set by the User in Model using the
NCUTS attribute of the Bend.
17.1.2 P-Points
Mitred Bends in the AVEVA Catalogue are Variable Angle and Variable Radius.
The calculation used for the distance on the P-Points in the AVEVA Catalogue is specified in reverse polish
notation due to the age of the Catalogue. A more modern way of expressing this would be (radius * (tan
angle) / 2).
Pulled bends are used as real bends by setting the Radius. They are also used to correct discrepancies in a
route, particularly with falling pipes. In this instance, the bend radius is normally set to 0.
The bend radius can be set from the Pipe Spec, a Pipe Fabrication Machine or, alternatively, can be set
manually.
An attribute called BENDMACREF is available and set at the Zone level. Providing that the CompType on
the BEND’s SCOM is set to VAR, it is possible to automatically select the bend radius from a Pipe
Fabrication Machine.
AVEVA E3D will first attempt to set the radius via the specification selectors, followed by a check on the
zone for a Fabrication Machine World to validate the bend against. The Radius must be set manually if no
radius is set.
This method is traditionally the way to set the bend radius. Having a RADIUS heading in the specification
will set the Radius within Model.
The following is an example of a piping spec with the Bend Radius selector RADIUS used. Note that the
radius is based on the OD of the pipe multiplied by the Radius; for example the OD of a 100NB Pipe is
114.3mm, therefore the bend radius is calculated as 342.9mm. In practice any bend radius could be used.
OLD SPECIFICATION /EX-SPEC
TEXT 'PIPING'
HEADING
NAME TYPE PBOR0 STYP SHOP RADIUS CATREF DETAIL MATXT CMPREF BLTREF TMPREF PRTREF
DEFAULTS
- - - EV TRUE =
*/EV15 BEND 15.00 EV TRUE 64.02 /00EV000DD /00EV000-D /ABB /00EV000DD-CW =0 =0 =0
*/EV20 BEND 20.00 EV TRUE 80.01 /00EV000EE /00EV000-D /ABB /00EV000EE-CW =0 =0 =0
*/EV25 BEND 25.00 EV TRUE 100.2 /00EV000FF /00EV000-D /ABB /00EV000FF-CW =0 =0 =0
*/EV40 BEND 40.00 EV TRUE 144.78 /00EV000HH /00EV000-D /ABB /00EV000HH-CW =0 =0 =0
*/EV50 BEND 50.00 EV TRUE 180.96 /00EV000JJ /00EV000-D /ABB /00EV000JJ-CW =0 =0 =0
*/EV65 BEND 65.00 EV TRUE 219.09 /00EV000KK /00EV000-D /ALB /00EV000KK-CW =0 =0 =0
*/MBEND:50 BEND 50.00 MIT TRUE 301.6 /00BX204JJ /00BX204-D /AAB /00BX204JJ-CW =0 =0 =0
*/EV80 BEND 80.00 EV TRUE 266.7 /00EV000LL /00EV000-D /ALB /00EV000LL-CW =0 =0 =0
*/MBEND:80 BEND 80.00 MIT TRUE 444.5 /00BX204LL /00BX204-D /AAB /00BX204LL-CW =0 =0 =0
*/EV100 BEND 100.00 EV TRUE 342.9 /00EV000NN /00EV000-D /ALB /00EV000NN-CW =0 =0 =0
*/ZO100 BEND 100.00 ZO TRUE 0 /0VBMM /VAR-D =0 =0 =0 =0 =0
*/MBEND:100 BEND 100.00 MIT TRUE 571.5 /00BX204NN /00BX204-D /AAB /00BX204NN-CW =0 =0 =0
*/EV150 BEND 150.00 EV TRUE 504.9 /00EV000RR /00EV000-D /ALB /00EV000RR-CW =0 =0 =0
*/MBEND:150 BEND 150.00 MIT TRUE 841.5 /00BX204RR /00BX204-D /AAB /00BX204RR-CW =0 =0 =0
Also illustrated are Zero radius bends for use with Sloping Pipes and a Mitred Bend.
For a Bend Radius to be set via a Pipe Fabrication Machine the CompType on the Bend SCOM must be set
to VAR and the Radius in the Spec must NOT be set.
The following is an example of a macro setting the CompType of the Bends that are used in the Training
Piping Spec.
/00EV000AA CompType VAR
/00EV000BB CompType VAR
/00EV000CC CompType VAR
/00EV000DD CompType VAR
/00EV000EE CompType VAR
/00EV000FF CompType VAR
/00EV000GG CompType VAR
/00EV000HH CompType VAR
/00EV000JJ CompType VAR
/00EV000KK CompType VAR
/00EV000LL CompType VAR
/00EV000MM CompType VAR
/00EV000NN CompType VAR
/00EV000PP CompType VAR
/00EV000RR CompType VAR
/00EV000TT CompType VAR
/00EV000VV CompType VAR
/00EV000WW CompType VAR
/00EV000XX CompType VAR
/00EV000YY CompType VAR
/00EV000ZZ CompType VAR
/00EV00011 CompType VAR
/00EV00022 CompType VAR
/00EV00033 CompType VAR
/00EV00044 CompType VAR
/00EV00055 CompType VAR
/00EV00066 CompType VAR
/00EV00077 CompType VAR
/00EV00088 CompType VAR
/00EV00099 CompType VAR
17.2.4 Tube OD
The tube must match exactly the Tube OD in the Pipe Fabrication Machine, for example the OD of a 150NB
Tube is 168.3mm.
Exercise 18 - Bends
Add the Mitred Bend Categories /00BV0W3 for a 3 Cut Mitred Bend and /00BV0WN for a variable Cut
Mitred Bend to the Pipe Spec /CS-PIPE-SPEC.
Use the associated detail text /00BV0W3-D and /00BV0WN-D and the Material /ASTM-A53-GRA.
Test the Mitred Bends in Model. Remember to set the Band Radius and, in regards to the Variable Cut
Mitred Bend, the attribute NCUTS must be set e.g. NCUTS 6.
Create a new Section called /DetailText in the Training Catalogue /TRAINING.CATA and a new Detail Text
named /00EV003-D.
Add Category /00EV000 to the Pipe Spec /CS-PIPE-SPEC created earlier; do not set a radius as the bend
will be selected via a Fabrication Machine in Model.
Enter the AVEVA E3D Model and navigate to the Piping Zone. Update the zone to point at the Fabrication
Group (FMGRP):
This can be done by selecting the Zone with the R.H. Mouse
Button and selecting Attributes.
BendMacReference /Bending_3D.
18 Sloping Pipes
On a typical project, pipes are routed horizontally and vertically, but it may be necessary for designers to
include pipes which slope at angles between components (falling pipes).
AVEVA E3D allows the user to set the leave direction of a component to achieve a given slope in the pipe
connecting it to the next component, which is valid only for a branch element and a component whose
geometry involves a change of direction and have a variable angle, such as an Elbow, variable directional P-
points can be added to Tees and Flanges.
The Pipe slopes are controlled using an Slope Reference (SLOREF) attribute on the Pipe or Branch to
define a design slope and can also be used by the Datacon utility to check Pipe Slopes.
The availability and name of Slope Ref is determined via the Paragon module within AVEVA Catalogue.
Each Slope Ref is determined by the Slope Element (SLOELE).
Example of SLOREF use in AVEVA E3D Model via the Create Pipe
form.
The following illustration shows how the correction can be applied to reduce the offset. The P1 and P2 of the
tee are aligned with the main branch. The P3 of the tee can be a variable angle P-Point.
As stated above, it is possible to define the slope on the offline leg (P3) of a Tee and one of the P-Points of
a Flange - normally the Leave (PL) or P2. This is done in the catalogue by setting the OffTolerance attribute
of the Flange or Tee P-Point to the allowable offset angle.
This allowable angle is further qualified in Model with the use of a Nominal Direction (NOMDIR) for the P-
Point i.e. Variable Angle P-Points. The NOMDIR gives the exact direction.
Similarly on a Tee, the offline leg of a Tee can be directed and the offset orientated.
Select Slope Component from the Modify part of the PIPING Tab
The Slope form in Model indicates the current direction of the Tee. The lower section of the form indicates
how the slope is determined, either using the form values which allow the user to key in a Fall or via the
slope set on the branch. The slope is specified as both a ratio and angle, and the User can specify whether
the direction will slope Up or Down, in this case the slope is Down.
The Slope Table contains Slope Elements (SLOELEs) which define the individual slopes.
Default Slope - this is the optimum angle for the slope, i.e. 1 in 5 for the above
Minimum Slope - the minimum slope below which the fluid will not drain
Maximum Slope - the maximum slope above which the fluids drains too quickly, leaving the solids in
the pipe.
Minimum Vertical Slope – the minimum vertical slope beyond which both fluids and solids will drain.
If the Slope Ref is set against a pipe it will be checked during Data consistency Checks and prior to
Production Checks.
In the Piping Application in Paragon Select Create or Modify > Slope Element…
SLOELE Attributes:
Name /1in5
Type SLOELE
Owner /PIPE-SLOPES-SLOTAB
MinSlope 10.7444deg
MaxSlope 11.8754deg
DefSlope 11.3099deg
MinVertical 20.0000deg
Apply
Apply
Set OffTolerance: 12
Using the described examples in Chapter 18, make the 90deg Butt Weld Elbow created earlier variable
angle. Update the OffTolerance on the Flange and Butt Weld Tee to allow them to be used with Sloping
Pipes.
Test that Sloping Pipes can be routed in Model, your Trainer will help you with this as required.
19 Properties
Properties data was initially used to hold those properties of components and materials which may be
needed for stress analysis or safety auditing of all or part of a design; typically weight. In AVEVA
CATALOGUE the Properties database has been extended to include data such as the material densities
required by the Model structural application for calculating weights and centres of gravity of steelwork items.
CMPW
CMPT
CMPD TUBD
Attributes: Attributes:
OUTD OUTD
The Component Property data in the properties database is referenced from the specification component
(SPCO) and Gpart via the component reference (Cmpref). The Properties database contains the following
element types:
The TUBD and CMPD elements store the physical data, and it is these elements which are referenced by
the component reference (Cmpref). Attributes for Outside Diameter (OUTD) and Actual Bore (ACBO) are
common to both, whilst component weight (CWEI) is used on CMPD and unit weight (UWEI) on TUBD.
In the case of implied tube there must always be a TUBD data element in the properties database. The
SPCO for implied tube is referenced by the Branch head tube specification (HSTU) and the component
leave tube specification (LSTU).
In the following example a weight property will be added to a Flange and implied Tube
Use Create > Properties… from the main menu in the Piping Application to create a new CMPW.
In a similar way, create a CMTP called TUBE and a TUBD element for TUBE. Set the Name to PIPE-30-200
and Uweight to 0.03.
The CMPD and TUBD would then be referenced as the CMPREF of the SPCO in the piping specification.
For the TUBE, set a Component Ref which points to a TUBD element in the properties database. Navigate
to the required element P-30-200 and then click the CE button on the right hand side of the text gadget.
Create the properties hierarchy described above for TUBD and CMPD.
Set the Component References for all TUBE items in the spec CS-PIPE-SPEC
AAVHAB0-150-CW – 30
AAVHAB0-200-CW – 40
20 Spooling
This chapter covers the creation of a weld catalogue and specification data to make use of new facilities
involving automatic weld numbering in the AVEVA E3D Spooler module.
To make use of automatic weld numbering facilities in the Spooler module it is necessary to create a weld
catalogue and specification data.
AVEVA provide a macro, which will create the weld specification and is linked to the /AVEVAPIPE.CATA
catalogue where a MODELLED.WELDS.CADC section exists. Alternatively, the user can create a new
specification or modify those already existing.
Enter EXIT.
This macro should be run for each pipe specification likely to be used for piping design where the automatic
weld numbering facilities are required.
The macro defines welds in the range of nominal sizes from 10mm to 900mm (36 inch). They define
pipe ODs based on API standard schedule pipe. Users should take them as examples, and modify
them to suit local requirements. Care should be taken to maintain the system of selectors defined for
the specifications.
To view the welds created, select Modify > Specification… and set the Headings pull down to WELD.
If welds are already present in the selected specification, it is necessary to add the required selectors to the
existing weld SPCOMs together with a default setting so that the existing selection is unaffected
Add four new headings for STYP, EDGE, ALLO and SHOP.
Use Edit Answers… to add an identical set of answers to all existing weld SPCOMs, and set the Default
values of these answers to match. For example:
Assuming a spec name of XXX, edit the answers for each existing WELD as follows:
Welded components are assumed to incorporate a half root gap at each connecting P-point, therefore
allowing components to be connected together whilst still allowing for the weld root gap. In this case, an
inserted weld must be of zero length.
Further, to achieve correct dimensions and cut lengths, the following must be inserted:
The selector of question EDGE is used to differentiate between the three welds required for each given
bore. The following may also be permissible answers:
The example macro uses a full weld length of 4mm and half weld length of 2mm. This length is set as a
parameter for each component SCOM in the MODELLED.WELDS.CADC section of the
AVEVAPIPE.CATA. This should be changed in the master catalogue if necessary to suit the particular
weld details.
The ALLO selector is used to denote a field fitting allowance. It may be TRUE or FALS.
The SHOP selector is used to denote a shop or field weld, and also may be TRUE or FALS.
The STYP selector is not actually used to select a weld. Its answer is extracted after weld selection to form
the prefix part of a weld number.
This chapter describes the methods of obtaining different item codes within the same specification, UDA’s
and delimiters.
A Component’s ItemCode, as shown in the material list on a Piping Isometric, is derived from the name of
the SPCOM minus the Specification name and leading /. Thus, components whose SPREF points to the
SPCOM /A150/FW100 (in Spec /A150) will have the item code FW100.
AVEVA Catalogue does not allow any name or specification reference (SPREF) to exist more than once
within a specification. Identical components can be distinguished by having a suffix added to their SPREF.
Consider an ELBO with a Spref name /A150/ELBO25 and whose Catref is a standard elbow. The
specification also requires an elbow capable of having an elbolet connected to it. The second elbow cannot
have the same SPREF as the first and therefore a suffix must be added e.g. /A150/ELBO25:X.
The DELIMITER that separates the common part of the SPREF from the suffix is a colon (:), this is the
default delimiter, although any of the following may be used:
AT Specifies @ Symbol
For a full explanation of the use of DELIMITER’s see the Isodraft Reference Manual.
It is normal practice for the ItemCode shown on the Isometric to carry the full description of the component -
this would normally include material and wall thickness.
If different ItemCodes are required for different clients within the same common piping specification, these
can be set in the Catalogue database as User Defined Attributes (UDA’s) of the spcom.
The following example shows part of a specification. The SPCOM has two UDAs :clienta and :clientb.
:clienta = ‘F100L’
:clientb = ‘FLAN100’
Note that any text after the delimiter character in a UDA will be stripped off (for example FLAN100:ZZ
becomes FLAN100).
Alternative ItemCodes for bolts are taken from UDAs set on DTAB elements, not on the SPCOM as found
with ItemCodes.
The SBOLT elements must have the attribute NSTD pointing to the DTAB element.
The name of the UDA on the DTAB element must be related to the UDA set for the SPCOM. Using the
previous example above for ItemCodes, the corresponding DTAB UDA would be named :clienta1,
:clienta2 etc… In addition, another set could be named :clientb1, :clientb2 etc…
ItemCodes are stored in a DTAB UDA as text separated by spaces. As text UDAs have an upper limit
of 120 characters, the list of ItemCodes continues across the set of UDAs. For example, if each
ItemCode was 10 characters long, 11 ItemCodes could be stored in each UDA of the set.
The number of ItemCodes stored in each UDA set should correspond to the number of elements in the
BLEN attribute of the DTAB.
SBOLT /BL100
NSTD /M16
DTAB /M16
This chapter describes the Catalogue checking facility and briefly describes the main settings. All settings
described refer to a Piping catalogue.
There is currently no User Interface for the Database Consistency Checker. In the Command Window,
type...
CHECK name
Name is the element at which checks are to commence, this can any SPEC, SELE, SPCO, or
SCOMP.
If the check is started from within a specification (SPEC, SELE or SPCOM), all components referenced via
the starting element will be checked. If the check is started at component level (SCOMP), only that
component and elements below will be checked.
At SPEC Level:
From the TYPE reference, check that the GTYPE of the COMP has the same setting.
From the TYPE reference, check that the SKEY setting of SDTEX is correct.
From the TYPE reference, check that the point set has the correct geometry, as required by Isodraft.
At SPCO Level:
Check that all of the following reference attributes are set: CATREF, DETAIL, MATX, CMPR.
At SCOMP Level:
At a PTSE, check that P-points are set and that there are no duplicate numbers.
At a GMSE, check that there are primitives set and that they are not degenerate. Check also that no
invalid P-point numbers or parameters are used. Note that this test uses catalogue parameters, so that
if a primitive is constructed only from Design and Insulation parameters, a spurious warning will be
generated.
Check that each P-point connection type exists in the COCO tables. P-points used for construction
purposes can have a connection of 0.0, NUL or NULL.
Check that a P-point bore is valid for a recognised set of nominal bore p-points used for construction
purposes. A P-point with connection type CLOS, can have a zero bore.
The following is an extract from a data consistency check performed at SPEC level:
SPCOMPONENT 1 /CS-PIPE-SPEC/REDU-16
SPCOMPONENT 1 /CS-PIPE-SPEC/GASK-1
SPCOMPONENT 1 /CS-PIPE-SPEC/GASK-2
END
The error: ‘C150 Comp error: GMRE not set’ could be reported for any Gasket or Attachment element. As
ATTAs and some GASKets do not necessarily require a geometry set, this may not be a catalogue problem.
The error ‘C820 SKEY not set’ for the REDUCER would require further investigation.
The effect of the CHECK may be modified, by using additional syntax, so that different types of the
catalogue can be checked without generating unnecessary errors.
Refer to the Paragon Reference Manual for a full description of the settings and associated error
messages.
How many different error messages are there and what does each one mean?
23 Administration
This session is intended specifically for users responsible for setting up the AVEVA Catalogue Paragon
applications to suit individual company requirements.
Special access rights are required to use the Administration options from Paragon’s menus. Without the
appropriate access rights, these menu options will be hidden. Access rights are assigned by the project
administrator.
On installation a number of piping component representation rules are set up as standard. These reside in a
defaults file: UI-DREP in the %AVEVA_DESIGN_DFLTS% directory. Representation rules may be modified
or created as required. To set or change these rules select Settings > Representation Rules…. The
following form will be displayed.
min drawing level \ max drawing level \ obstruction level \ centreline flag \ tube flag
Obstruction Soft
Tube representation On
Size
Facing
Rating
Component Type
Standard number
International Standard
I ISO
M Manufacturers Standardisation
Society (MSS)
J Japanese Standard
Type
E3D GTYP ATTA, TEE, BEND, ELBO, REDU, FLAN, OLET, NOZZ CROSS, VALVE, etc
Rating
ANSI, BS, API, MSS 125#, 150#, 300#, 600#, 900#, 1500#, 2500#, 3000#, 6000#, 9000# (#=lb/sq. in.)
DIN (ND=Nenndruck) 10, 16, 25, 63, 100, 160, 250, 320, 400
Facing:
ANSI, BS, API, MSS, DIN ANSI, BS, API, MSS DIN
Size:
A1.2 Bolting
Normally unused
Rating
Facing
ISOGEN TYPE
Each COCO is restricted to a maximum of 4 characters to define the connection. The following types are
treated as standard connections and their meanings are described below:
ALL Compatible with all items SCF Screwed Female
ATT Attachment SCM Screwed Male
BWD Butt weld CLOS Closed end
SWF Female Socket welding SWM Male Socket welding
TUB Pipe or Tubing OPEN Open end
VENT Open to vent DRAN Drain connection
NULL No Connection
The following codes are used to set the connection types of flanged items. Each character defines a
different attribute of the appropriate connection type.
E3D Type (char 1) Facing (char 2) Rating (char 3)
F Flange facing (for A FF A PN 125#
Flanges, Valves etc.)
G Gasket facing (To connect B RF B PN 150#
to flanges)
W Wafer type component C FE DIN2512 C PN 250#
(Char 1 followed by
normal flange COCO)
D NU DIN2512 D PN 300#
E E PN 400#
F F PN 600#
G G PN 900#
H H PN 1500#
J J PN 2500#
K K PN 5000#
L L PN 2.5
M M PN 6
N N PN 10
P V13 DIN2513 P PN 16
Q R13 DIN2513 Q PN 25
R R PN 40
S PN 63
T PN 100
Each character of the component name can be selected from the appropriate tables. Character 3 defines the
component type. Character 1 is derived from the international standard columns.
All other characters are derived from the component specific page as either direct information or reference
to the tables.
The character table reference for elbows is to be used to get the rest of the characters.
Finally the bore sizes are selected from table N1. There are characters for both bore sizes so the final two
characters are NN. This gives us a catalogue name of AAEA200NN
Typ A
Typ=M Typ=N Typ=S Typ=W
A A A A Worcester
B B B B
C C C C
D D D D
E E E E
F F Fisher F F
G G G G
H H H H
J J J J
K K K K
L L L L
M M M M
N N N N
P P P P
R R R R
S Masoleian S S Severn S
T T T T
U U U U
V V Northvale V V
W W W W
X X X X
Y Y Y Y
Z Z Z Z
A
A Angle, Direct Acting Globe T
B Ball U
C V
D Direct Acting Globe W
E X
F Butterfly Y
G Z
H 1
J 2
K 3 Three Way
L 4
M 5
N 6
P Plug 7
Q 8
R Reverse acting globe 9
S 0
A
A U
B V
C W
D Diaphragm X
E Electric Motor Y
F Z
G 1
H 2
J 3
K 4
L 5
M 6
N 7
P Piston - Linear 8
Q 9
R Piston - Rotary 0
S
T
Std. B
A S
B T
C U
D V
E W
F X
G Y
H Z
J 1
K 2
L 3
M 4
N 5
P 6
Q 7
R 8
9
0 Not Specified
B 0
Std. C
American Std.= A British Std.= B DIN Std.=D MSS Std.= M Manu Std. =V
A ANSI B16.9 A BS 1640 A A MSS-SP83 A
B ANSI B16.11 B BS 3799 B B B
C ANSI B16.3 C BS 1387 C C C
D ANSI B16.4 D BS 143 D D D
E ANSI B16.18 E E E E
F ANSI B16.22 F F F F
G G G G G
H H H H H
J J J J J
K K K K K
L L L L L
M M M M M
N N N N N
P
Q
R
S
T Victaulic
Example:
C
A U Union
B V Victaulic
C W
D Dow Radial Clamp X
E Y
F Full Coupling Z
G 1
H Half Coupling 2
J 3
K 4
L 5
M 6
N 7
P 8
Q 9
R Flange Adapter, Radial Lock 0
S
T
C 0
Std. E
American Std.= A British Std.= B DIN Std.=D Manuf. Std.= P Manuf. Std.= V
A ANSI B16.9 A BS 1640 A DIN 2605 A A
B ANSI B16.11 B BS 3799 B B B
C ANSI B16.28 C BS 1740 C C C
D ANSI B16.5 D BS 1965 D D Peabody Dore D
E ANSI B16.3 E BS 1387 E E E
F ANSI B16.4 F BS 143 F F F
G ANSI B16.22 G G G G
H ANSI B16.18 H H H H
J ANSI B16.24 J J J J
K K K K K
L L L L L
M M M M
N N N N
P
Q
R
S
T Victaulic
Example:
E
A Long Radius (R=1.5 NB) U 5D Pulled Bend
B Short Radius (R= 1 NB) V Variable Radius Bend
C 45 Deg Elbow W
D Single Tangent (LR) X Mitre Bend
E Double Tangent (LR) Y Side Outlet Elbow
F Long Radius Return (3NB) Z 45 Deg Bend
G Short Radius Return(2NB) 1 45 Deg Elbow R=1NB
H Reducing 2 90 Deg Elbow R=2.5NB
J Street Elbow 3 45 Deg Elbow R=2.5NB
K Close Radius 4 45 Deg Elbow R=5NB
L Medium Radius 5
M Open Radius 6 60 Deg Elbow
N 67.5 Deg Spring 7
P 45 Deg Spring 8
Q 22.5 Deg Spring 9
R 90 Deg Bend 0
S 3D Pulled Bend
T 4D Pulled Bend
Std. F
American Std.= A British Std.= B DIN Std.=D MSS Std.= M Manuf. Std.= V
A ANSI B16.9 A BS 1770 A DIN 2632 A MSS SP-44 A
B API 600 B BS 1560 B DIN 2633 B MSS SP-51 B
C API 605 C BS 3293 C DIN 2635 C C
D ANSI B16.36 D BS 4504 D DIN 2527 D D
E ANSI B16.24 E BS 10 E DIN 2631 E E
F F BS 2035 F DIN 2634 F F
G G G DIN 2636 G G
H H BS 4622 H DIN 2630 H
J J BS 4772 J DIN 2637 J
K K K DIN 2638 K K
L L L DIN 2641 L L
M M M M M
N N N DIN 2512 N N
P P P P
Q Q Q Q
R R R DIN 2628 R R
S S S DIN 2629 S S
T Victaulic
Example:
F
A U
B Blind V Victaulic
C Screwed Boss W Weld Neck
D X Spacer
E Y
F Z
G 1
H Hub Slip on 2
J 3
K 4
L Lap 5
M 6
N 7
P Plate Slip on 8
Q Orifice 9
R Reducing 0
S Socket Weld
T Threaded
F Q
A BSP Weld Neck :BSP R
B NPT Weld Neck :NPT S
C SW Weld Neck :SW T
D Socket Weld : BSP U
E Socket Weld : NPT V
F Socket Weld : SW W
G Screwed BSP : BSP X
H BSP : NPT Screwed BSP : NPT Y
J BSP : SW Screwed BSP : SW Z
K NPT : BSP Screwed NPT : BSP 1
L NPT : NPT Screwed NPT : NPT 2
M NPT : SW Screwed NPT : SW 3
N BSP Slip on : BSP 4
P NPT Slip on : NPT 5
Q SW Slip on : SW 6
7
8
9
0
F R
A Weld Neck concentric U
B Weld Neck eccentric V
C Socket Weld concentric W
D Socket Weld eccentric X
E Screwed BSP concentric Y
F Screwed BSP eccentric Z
G Screwed NPT concentric 1
H Screwed NPT eccentric 2
J Slip On concentric 3
K Slip On eccentric 4
L Filler Flange 5
M 6
N 7
P 8
Q 9
R 0 Not Used
S
T
Std. G
American Std.= A British Std.= B DIN Std.=D
A ANSI B16.20 A BS 3063 (BS10/1770/2035) A DIN 2690 (for DIN2501)
B ANSI B16.21 B BS 3381 (BS1560) B DIN 2691 (for DIN2512)
C ANSI B16.5 C BS 4865 (BS4504/4622/4772) C DIN 2692 (for DIN2513)
D API 605 D BS 1560 (BS1560) D
E E BS 3293 (BS3293) E
F F F
G G G
H H H DIN 2697
J J J DIN 2698
K K K
L L L
M M M
Manufacturers std= G or = V
A A
B B
C C
D D
E E
F F
G G
H H
J J
K K
L L
M M
N N
P P
Q Q
R Graylock R
S S
T T Victaulic
Example:
G
A Full Face U
B Inside Bolt Circle V Victaulic Clamp
C Raised Face with Centring Ring W
D Large Tongue & Groove X
E Small Tongue & Groove Y
F Ring Type Joint Z
G Graylock Sealing Ring & Clamp 1
H Large Male / Female 2
J Small Male / Female 3
K 4
L 5
M 6
N 7
P 8
Q 9
R 0
S
T
G
A 1 mm U 3/32"
B 2 mm V 1/8"
C 3 mm W 5/32"
D 4 mm X 3/16"
E 5 mm Y 7/32"
F 6 mm Z 1/4"
G 1.5 mm 1
H 2
J 3
K 4
L 5
M 6
N 7
P 8
Q 9
R 1/64" 0 Not specified
S 1/32"
T 1/16"
Std. K
American Std.= A British Std.= B DIN Std.=D Manuf. Std.= G Manuf. Std.= V
K
A
B U
C Long Cap V Victaulic Clamp
D Short Cap W
E X
F Flat Closure Y
G Graylock Blind Hub Z
H 1
J 2
K 3
L Countersunk Plug 4
M Square Head Plug 5
N Hexagonal Head Plug 6
P Round Head Plug 7
Q Plain Bull Plug 8
R Tapped Bull Plug 9
S Slotted Head Plug 0
T
Std. M
American Std.= A British Std.= B DIN Std.= D Manufacturer Std.= G
A American Std. A British Std. A DIN Std. A
B B B B
C C C C
D D D D
E E E E
F F F F
G G G G Gestra
H H H H
J J J J
K K K K
L L L L
M M M M
N N N N
P P P P
Q Q Q Q
R R R R
S S S S
Manufacturer Std.= K Manufacturer Std.=N Manufacturer Std.= P Manufacturer Std.= R
A A A A
B B B B
C C C C
D D D D
E E E E
F F F F
G G G G
H H H H
J J J J
K Krupp Köppers K K K
L L L L
M M M M
M
A Flame Arrester U
B Single Bellows Unit V
C Bursting Disc Assembly W Weld
D Air Dryer X Basket Type Strainer
E Double Bellows Y Y Type Strainer
F Flow Indicator Z T Type Strainer
G Filter 1
H Sight Glass 2
J Spacer for tongue and groove flanges 3
K Ball Float Trap 4
L Line blind 5
M 6
N 7
P Pot Type Strainer 8
Q Orifice Plate 9
R 0
S Spectacle Blind
T
Std. N
American Std.= A British Std.= B DIN Std.=D Manufacturer Std.= V
A ASTM A120 A BS 534 A A
B ASTM A53 B BS 806 B B
C ANSI B36.10 C BS 1306 C C
D D BS 1387 D D
E E BS 1600 E E
F F F F
G G G G
H H H H
J J J J
K K K K
L L L L
M M M M
N N N N
P P P P
Q Q BS 3799 Q Q
R R BS 1740 R R
S S BS 143 S S
T T T T
U U U U
V V V V Victaulic
W W W W
X X X X
Y Y Y Y
Z Z Z Z
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
8 8 8 8
9 9 9 9
0 Not specified 0 Not specified 0 Not specified 0 Not Specified
Example:
Nipple ASTM A120 = AAN
Victaulic nipple = VTN
N
A U
B Barrel Nipple V
C W
D X
E Eccentric Swage Y
F Z
G 1
H Hexagonal 2
J 3
K Close Taper 4
L 5
M 6
N 7
P Pipe Nipple 8
Q 9
R 0
S Concentric Swage
T Tank Nipple
N
A Plain x Bevel U
B Plain x Plain V Bevel x Victaulic Groove
C Plain x Threaded NPT W Threaded x Victaulic Groove
D Plain x Threaded BSP X Victaulic Groove To Groove
E Threaded Both Ends NPT Y
F Threaded Both Ends BSP Z
G Bevel x Threaded NPT 1
H Bevel x Threaded BSP 2
J Threaded NPT x Bevel 3
K Threaded BSP x Bevel 4
L Threaded NPT x Plain 5
M Threaded BSP x Plain 6
N Bevel x Plain 7
P Bevel x Bevel 8
Q 9
R Radial Lock Both Ends 0
S Soldered, Brazed
T Radial Lock x Flanged
N
A 50 mm U 9"
B 65 mm V
C 75 mm W
D 100 mm X
E 125 mm Y
F 150 mm Z
G 175 mm 1
H 200 mm 2
J 2" 3
K 250 mm 4
L 3" 5
M 400 mm 6
N 4" 7
P 5" 8
Q 9
R 6" 0 Not Specified
S As Per Standard
T
Std. P
American Std.= A British Std.= B DIN Std.=D
A ANSI B36.10 A BS 534 A DIN 2448
B ASTM A-106 B BS 806 B DIN 2458
C API 5L C BS 1306 C DIN 2462
D ASTM A-53 D BS 1387 D DIN 2463
E ANSI B36.3 E BS 1600 E DIN 2916
F ANSI B36.19 F BS 2598 F DIN 4376
G ASTM B42/B43 G BS 3351 G
H H BS 3600 H
J J BS 3601 J
K K BS 3602 K
L L BS 3603 L
M M BS 3604 M
N N BS 3605 N
P P BS 3606 P
Q Q BS 2035 Q
R R BS 2871 R
S S S
T T T
U U U
V V V
W W W
X X X
Y Y Y
Z Z Z
1 1 1
2 2 2
3 3 3
4 4 4
5 5 5
6 6 6
7 7 7
8 8 8
9 9 9
0 Not Specified 0 Not Specified 0 Not Specified
Example:
P
A Seamless Steel Pipe U
B V
C Centrifugally Cast W
D X
E Electric Fusion Welded Y
F Z
G Glass Pipe 1
H 2
J 3
K 4
L Lined Flanged Pipe 5
M 6
N 7
P 8
Q 9
R Resistance Welded 0 Not Specified
S
T
Std. R
American Std.= A British Std.= B DIN Std.=D Manufacturer Std.= P
A ANSI B16.9 A BS 1640 A A
B ANSI B16.11 B BS 3799 B B
C ANSI B16.14 C BS 1740 C C
D ANSI B16.5 D BS 1965 D D Peabody Dore
E E BS 143 E E
F ANSI B16.18 F F F
G ANSI B16.22 G G G
H H H H
J ANSI B16.24 J J J
K K K K
L L L L
M M M M
N N N N
P P P P
Q Q Q Q
R R R R
S S S S
T T T T
U U U U
V V V V
W W W W
X X X X
Y Y Y Y
Z Z Z Z
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
8 8 8 8
9 9 9 9
0 Not Specified 0 Not Specified 0 Not Specified 0 Not Specified
Example:
R
A T
B U
C Concentric V
D W
E Eccentric X
F Y
G Z
H Hexagonal Bush 1
J 2
K 3
L 4
M 5
N Hexagonal Nipple 6
P 7
Q 8
R Reducing Insert 9
S 0 Not Specified
Std. S
American Std.= A British Std.= B
A ANSI B16.9 A BS 1640 PT1
B B BS 1640 PT2
C C
D D
E E
F F
G G
H H
J J
K K
L L
M M
N N
P P
Q Q
R R
S S
T T
U U
V V
W W
X X
Y Y
Z Z
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
0 Not Specified 0 Not Specified
Example:
S
A U
B V
C W
D X
E As Per Standard Y
F Z
G Graylock Weld Hub 1
H 2
J 3
K 4
L 5
M 6
N 7
P 8
Q 9
R 0 Not Specified
S
T
Std. T
American Std.= A British Std.= B DIN Std..= D Manufacturer Std.= L
A ANSI B16.9 A BS 1640 A DIN 2615 A
B ANSI B16.11 B BS 3799 B B
C ANSI B16.3 C BS 1740 C C
D ANSI B16.4 D BS 1965 D D Ladish
E ANSI B16.5 E BS 143 E E
F ANSI B16..18 F F F
G ANSI B16..22 G G G
H H H H
J ANSI B16.24 J J J
K K K K
L L L L
M M M M
N N N N
P P P P
Q Q Q Q
R R R R
S S S S
Example:
T
A 90 Deg. Fitting U Set On Branch With Saddle
B 45 Deg. fitting V Set On Branch, Var Angle
C Cross W Weldolet
D Y- Piece X Sockolet
E Elbolet Y Thredolet
F TEE By Full Coupling Z Sweepolet
G Street TEE 1 Instrument TEE
H TEE By Half Coupling 2
J Sweep TEE 3
K Double Sweep TEE 4
L Latrolet 5
M Side Outlet TEE 6
N Nipolet 7
P Side Outlet Elbow 8
Q 9
R 0 Not specified
S Set On Branch (90Deg)
T Reinforced Set On Branch
T 0
Std. V
American Std.= A British Std.= B DIN Std..= D Manuf. Std.= C
A ANSI B16.10. A BS 1414. A DIN 3202. A
B B BS 16 B B
C C BS 1868 C C Crosby
D BS 1873 D D
E E E Delta E
F F BS 5352 F F
G G G G
H H H H
J J J J
K K K K
L L L L
M M M M
N N N N
P P P P
Q Q Q Q
R R BS 4460 R R Crane
Manuf. Std.= F Manuf. Std..= G Manuf. Std.= H Manuf. Std.= K
A A A A
B B B B
C C C C
D D D D
E E Gestra E E
F F F F
G G G G
Manuf. Std.= F Manuf. Std..= G Manuf. Std.= H Manuf. Std.= K
H H H Hattersley H
J J J J
K K K K
L L L L
M M M M
N N N
P P P P
Q Q Q Q
R Farris R Graylock R R
S S S S
T T T T
Y Keystone
V
A Angle Globe U Angle Stop Check
B Ball V Straight Stop Check
C Ball Type Check W Wafer Check
D Diaphragm X
E Piston Check Y Y Type Globe
F Butterfly Z
G Gate 1
H Globe 2
J Swing Check 3 Three Way
K Tilting Disc 4
L Full Bore Diaphragm 5
M Flap Check 6
N Needle 7
P Plug 8
Q Poppet 9
R Relief 0 Not Specified
S Short Ball
T Tank Dump Valve
V
A Manual 90 Deg Turn U
B Diaphragm Fail Open V
C Diaphragm Fail Close W
D Pneumatic Piston X
E Electric Motor Actuator Y
F Z
G Gear Driven Handwheel 1
H Hydraulic 2
J 3
K Pressure Seal 4
L 5
M 6
N Non Rising Stem Handwheel 7
P Piston Fail Open 8
Q Piston Fail Closed 9
R Rising Stem Handwheel 0 Not Specified
S Soenoid
T
V R
A U
B V
C W
D 0.110 SQ INS X
E 0.196 SQ INS Y
F 0.307 SQ INS Z
G 0.503 SQ INS 1
H 0.785 SQ INS 2
J 1.287 SQ INS 3
K 1.838 SQ INS 4
L 2.853 SQ INS 5
M 3.600 SQ INS 6
N 4.340 SQ INS 7
P 6.379 SQ INS 8
Q 11.050 SQ INS 9
R 16.000 SQ INS 0 Not Specified
S
T 26.000 SQ INS
S A V D
A Manual Lever 90 Deg Turn U Diaphragm Operated Spring Close
B Saunair ES60 V
C Saunair ES61 W
D Saunair ES62 X
E Saunair ES63 Y
F Saunair ES64 Z
G Saunair ES65 1
H Saunair ES66 2
J Saunair ES67 3
K Saunair ES68 4
L Saunair ES69 5
M Saunair ES70 6
N Saunair ES71 7
P Saunair ES72 8
Q Saunair ES73 9
R Lever, Vertical Arc 0 Not Specified
S Non Rising Stem Handwheel
T Diaphragm Operated Spring Open
W A V
A Wrench or Tee Bar U
B Norbro 10-40 V
C Norbro 20-40 W
D Norbro 25-40 X
E Norbro 30-40 Y
F Z
G 1
H 2
J 3
K 4
L 5
M 6
N 7
P 8
Q 9
R 0 Not Specified
S
T
V 0
A1.44 Welds
0 0 Z
A T TEE
B Branch U
C V
D W
E X
F Fillet (SW) Y
G Z
H 1
J 2
K 3
L 4
M 5
N 6
P 7
Q 8
R 9
S SQ Flange Fillet 0 Not Specified
A1.45 Attachments
0 0 X
A U
B V
C W
D X
E Y
F Z
G 1
H 2
J 3
K 4
L 5
M 6
N 7
P 8
Q 9
R 0 Not Specified
S Pipe Support Atta
T
X 0
Std. Z
American Std.= A British Std.= B DIN Std. = D
A ANSI B16.5 A A
B ANSI B2.1 B BS 1560 B DIN 2632
C ANSI B36.10 C BS 4504 C DIN 2633
D D BS 3799 D
E E BS 10 E DIN 2635
F F F
G G G
H H H
J J J
K K K
L L L
M M M
N N N
P P P
Q Q Q
R R R
S S S
T T T
U U U
V V V
W W W
X X X
Y Y Y
Z Z Z
1 1 1
2 2 2
3 3 3
4 4 4
5 5 5
6 6 6
7 7 7
8 8 8
9 9 9
0 Not Specified 0 Not Specified 0 Not Specified
Example:
Z
A T Threaded
B Boss U
C Integral V
D W Welded
E X
F Flanged Y
G Graylock Z
H Half Coupling 1
J 2
K 3
L 4
M 5
N 6
P 7
Q 8
R 9
S 0 Not Specified
Z 0
A Flat Face U
B Raised Face V Victaulic
C Large Tongue W
D Large Groove X
E Small Tongue Y
F Small Groove Z Compression
G 1 Plain
H Large Male Smooth 2 Buttweld (Bevel)
J Large Male Serrated 3 Socket Weld
K Large Female 4 Threaded Male & Female
L Radial Lock 5 Threaded NPT Female
M Small Female 6 Threaded NPT Male
N Small Male 7 Threaded BSP Female
P Projection V13 (DIN ) 8 Threaded BSP Male
Q Recess R13 (DIN ) 9
R Ring Type Joint 0 Not Specified
S Soldered, Brazed
T
A U
B V Victaulic
C W BSP Para Male X SW
D X BSP Taper Male X SW
E Y
F Z
G 1 Plain
H 2 Bevel
J 3 Socket Weld
K 4 Threaded Male & Female
L Radial Lock 5 Threaded NPT Female
M 6 Threaded NPT Male
N 7 Threaded BSP Female
P 8 Threaded BSP Male
Q 9
R 0
S Soldered, Brazed
T
A Flat Face U
B Raised Face V
C W
D Dow Radial Lock X
E Y Plain / Threaded
F Z Plain/SW
G Graylock 1
H 2 Buttweld (Bevel)
J 3 Socket Weld
K 4 Threaded Male & Female
L Integral gasket 5 Threaded NPT Female
M 6 Threaded NPT Male
N 7 Threaded BSP Female
P 8 Threaded BSP Male
Q 9 Socket Weld / Threaded
R Ring Type Joint 0
S Soldered, Brazed
T
A PN 125# U PN 160
B PN 150# V PN 250
C PN 250# W PN 320
D PN 300# X PN 400
E PN 400# Y PN 75#
F PN 600# Z PN 10000#
G PN 900# 1
H PN 1500# 2 PN 2000#
J PN 2500# 3 PN 3000#
K PN 5000# 4
L PN 2.5 5
M PN 6 6 PN 6000#
N PN 10 7
P PN 16 8
Q PN 25 9 PN 9000#
R PN 40 0 Not Specified
S PN 63
T PN 100
A SCH 5S U Medium
B SCH 10S V Heavy
C SCH 10 W
D SCH 20 X
E SCH 30 Y
F SCH 40S Z
G SCH 40 1
H SCH 60 2 Class 2000#
J SCH 80S 3 Class 3000#
K SCH 80 4
L SCH 100 5
M SCH 120 6 Class 6000#
N SCH 140 7
P SCH 160 8
Q STD 9
R XS 0 Not Specified
S XXS
T Light
The Material Codes Used in the AVEVA Catalogue have Short Codes as detailed in the table below. When
allocating Material Codes, it is advisable to use the AVEVA Catalogue Search utility.
The following are example Schedule Thickness Short Codes some of which have been used in this Guide.
The following three-dimensional primitive elements are all used by geometry sets (GMSET). They all have
common attributes LEVEL, CLFLA, TUFLA and OBSTR. The particular attributes of each element are
described on the following pages.
PX
PZ
PXLEN
PYLEN
With this type of cylinder, primitive, the size and location is defined by the distance to the bottom face from
the origin and the height. SCYL has particular attributes as follows:
The height of the LCYL is defined as the distances from the origin to the two end faces. LCYL has particular
attributes as follows:
This is similar to the DISH available in the Design Data. It allows symbolic modelling of control valves and
closer modelling of other Components. SDSH has the following particular attributes.
The Snout primitive is a cylindrical element of varying diameter along its length. It may be eccentric or
concentric. LSNO has particular attributes as follows:
The circular torus is only part of a torus. It is not permitted to subtend more than 180 degrees. It is circular in
cross–section. SCTO has particular attributes as follows:
The rectangular torus is similar to the circular torus except that it is rectangular in cross–section. SRTO has
particular attributes as follows:
In addition to the three–dimensional primitive elements, 3D Geomsets may contain Line (LINE). A LINE has
one particular attribute:
PTS: a set of numbers (up to six) representing P–point numbers of the P–points of the associated
Pointset, determine the course of the line.
The values held in PTS are set by preceding the P–point number by ‘P’ or ‘T’, e.g. P1 P2 T3
P4.
When prefixed with T it becomes a tangent point and thus a curve is drawn.
Used only in the representation of implied tube. Has the single particular attribute:
If PDIA is 0 then a line is produced. Depending on the scale to which a drawing is to be produced, a
small positive value would effectively give a thicker line.
Slope Bottomed Cylinder (SSLC) Catalogue Primitive PDIS distance from origin
The main use of this element is in the creation of rectangular reducers for ducting etc. LPYR has the
particular attributes as follows:
Components whose GTYPE attribute is TUBE can use BOXI elements to give, for example, implied tube of
rectangular cross-section. BOXI elements can be used for modelling ducting, trunking and cable tray. BOXI
has the particular attributes as follows:
This primitive is generated by extruding a user-defined 2D shape, known as a Loop (SLOO), whose outline
is defined by a set of member elements; Vertices (SVER). The lines joining adjacent SVERs form the edges
of the SLOO. The extrusion distance is defined by the height of the SEXT to give the final 3D volume.
In addition to the attributes defining its position, each SVER can have a radius, which applies a convex or
concave fillet to the loop at that point.
PAAX,PBAX Direction of axes of SLOO. (These will define co-oridinate system for SVERs).
Below is a DATAL output of a catalogue representation for a M12 Hexagon Head Bolt:
NEW SCOMPONENT /boltm12
GMRE /gm-01
GTYP BOLT
PARA 80 12 95 5 35 12 68 86 22 10 $
NEW LCYLINDER
TUFL true
PTDI ( 0.5 * ATTRIB PARA[6 ] + ATTRIB PARA[4 ] + 2 * ATTRIB PARA[10 ] )
PBDI ( -0.5 * ATTRIB PARA[6 ] - ATTRIB PARA[4 ] - ATTRIB PARA[10 ] )
PDIA ( ATTRIB PARA[2 ] )
NEW SEXTRUSION
TUFL true
PX 0
PY 0
PZ ( 0.5 * ATTRIB PARA[6 ] + ATTRIB PARA[4 ] + 2 * ATTRIB PARA[10 ] )
PAAX -X
PHEI ( ATTRIB PARA[10 ] )
NEW SLOOP
NEW SVERTEX
PX ( 0.5 * ATTRIB PARA[9 ] )
PY 0
PRAD 0
NEW SVERTEX
PX ( 0.5 * COS ( 60 ) * ATTRIB PARA[9 ] )