PARAGON - Paragon Reference Manual V11.6SP1 (EN)
PARAGON - Paragon Reference Manual V11.6SP1 (EN)
Reference Manual
Version 11.6SP1
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.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
Revision History
1 Introducing PARAGON..................................................................................1-1
1.1 What Does PARAGON Do? ........................................................................................ 1-1
1.2 About this Manual ........................................................................................................ 1-1
1.2.1 Manual Structure ........................................................................................... 1-2
2 Communicating with PARAGON ..................................................................2-1
2.1 Commands .................................................................................................................. 2-1
2.1.1 Command Description Format....................................................................... 2-1
2.1.2 Syntax Diagrams ........................................................................................... 2-1
2.1.3 Standard Command Tools............................................................................. 2-3
3 General PDMS Commands ...........................................................................3-1
3.1 Entering PARAGON .................................................................................................... 3-1
3.2 Leaving PARAGON ..................................................................................................... 3-1
3.3 Saving and Restoring the Current Display Status ....................................................... 3-1
3.4 Saving Work and Updating Databases........................................................................ 3-2
3.5 Exit from PARAGON without Saving Changes............................................................ 3-2
3.6 Saving the Alpha Readout to File ................................................................................ 3-3
3.7 Audible Error Trace...................................................................................................... 3-4
3.8 Switching Text Output Off............................................................................................ 3-4
3.9 Defining Colours .......................................................................................................... 3-5
4 The Catalogue Database ...............................................................................4-1
4.1 What is the Catalogue For? ......................................................................................... 4-1
4.2 Principal Features of the Catalogue Database ............................................................ 4-1
4.3 Structure of the Catalogue Database .......................................................................... 4-2
4.4 Catalogue (CATA) ....................................................................................................... 4-4
4.5 Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA)............ 4-4
4.5.1 Elements Used in Both Types of Catalogue Section/Category ..................... 4-6
4.5.2 Elements Used in Piping Sections/Categories .............................................. 4-6
4.5.3 Elements Used in Structural Sections/Categories ......................................... 4-6
4.6 Text (TEXT) ................................................................................................................. 4-7
4.7 Parameters .................................................................................................................. 4-8
4.7.1 Component Parameters................................................................................. 4-8
4.7.2 Insulation Parameters.................................................................................... 4-8
4.7.3 Structural Parameters.................................................................................... 4-9
4.7.4 Design DB Parameters ................................................................................ 4-10
4.8 Catalogue Components ............................................................................................. 4-11
4.8.1 Piping Component (COMP; SCOM) ............................................................ 4-12
4.8.2 Profile (PROF; SPRF).................................................................................. 4-13
4.8.3 Joint (JOIN; SJOI)........................................................................................ 4-13
4.8.4 Fitting (FITT; SFIT) ...................................................................................... 4-14
PARAGON enables you to generate or modify a PDMS Catalogue, with facilities for
constructing Catalogue Components under fully interactive visual control, including 3D
colour-shaded representations of the items being designed.
PARAGON combines aspects of both catalogue creation and model design functionality
within a single module. This means that a catalogue designer not only has write access
to a project’s Catalogue databases, but may also read data from the Design databases. If
given write access, the catalogue designer could also experiment with new catalogue
component configurations in a trial design database. This approach simplifies catalogue
maintenance and design. Similarly, it is often useful for a plant design engineer to have
access to the Catalogue to query details of specific components.
PARAGON has a Graphical User Interface consisting of forms and menus. The interface
provides access to the most commonly used facilities. To enter direct command syntax,
use the Display>Command Line menu option to open a special window which accepts
command inputs and displays system outputs. Full details of using PARAGON’s menus
and forms are given in the on-line help, and how to design your own graphical user
interface is explained in the Plant Design Software Customisation Guide.
2.1 Commands
This section describes the conventions used in this manual to describe commands to be
typed in from the keyboard. The description of each command follows a standard format
which is designed to allow the basic attributes of a command to be interpreted easily. To
get the best out of this manual, you are strongly urged to read this section thoroughly.
• Keywords This is a list of those PARAGON command words which are the prime
constituents of the command syntax which carries out the given function.
• Example(s) These are examples of typical command lines that show the effect of
the principal options. Special notes on the behaviour of the command in specific
conditions are given here.
• Command Syntax This shows the actual command with its possible options. The
notation used for commands is described below (Section 2.1.2).
used for cross-referencing purposes in the text and within other syntax diagrams,
are supplemented by fuller descriptions where they are not self-explanatory.
NOTE: This convention does not mean that the second part of the command must be
typed in lowercase letters; commands may be entered in any combination of
uppercase and lowercase letters.
For example, the command
DEFault
may be input in any of the following forms:
DEF
DEFA
DEFAU
DEFAUL
DEFAULT
Commands shown wholly in uppercase letters cannot be abbreviated.
• Syntax diagrams are generally read from top left to bottom right.
• Points marked with a plus sign (+) are option junctions which allow you to input
any one of the commands to the right of the junction. Thus
.------<------.
/ |
>---*--- option1 ---|
| |
|--- option2 ---|
| |
‘--- option3 ---+--->
permits any combination of option1 and/or option2 and/or option3 (each separated by
at least one space) to be used. The ‘options’ may define commands, other syntax
.----<-----.
/ |
>---*--- name ---+--->
means that you may type in a list of PDMS names, separated by at least one space.
• External Macro Facilities - which can be used in a stored macro file and which
control the behaviour of the macro when it is executed
• Standard Concepts - which apply globally within PARAGON
Some of the main command tools (or the PARAGON variations of them) summarised for
convenience:
¾ Command Arguments
Command arguments are also called atoms because they cannot be broken down any
further. They are individual units which PARAGON can recognise as constituents of a
complete command. They usually need to be separated by spaces so that they are
individually distinguishable. Command arguments are distinguished from the other
command parts by being written in lower case italics. The principal command
arguments are:
integer a positive or negative whole number, e.g. 2 -5 25
value a signed number with or without a decimal point, e.g. 2.5 5 -3.8
space the space bar (not usually specified unless of special significance)
varid an identifier (for use with the VARIABLE command within macros) of the
format !name, where ‘name’ is a text string. For example: !COUNTER
!height
¾ Command Parts
Command parts are subsets of the general command syntax which are used frequently
within other command sequences. The following command parts are summarised here:
Expressions
Any mathematical, logical or alphabetical expression whose result replaces it in the
command syntax.
Dimensions
A physical dimension entered using default or explicit units.
Catalogue Element Types
A word used to represent a specific type of element in the Catalogue database hierarchy.
Element Identifiers
Methods for specifying which database element you want your next commend to act
upon.
Cursor-picking Identifier (<sgid>)
This command part defines the most general method of identifying an Element. The
command is completed by picking an element using the cursor in a graphical view.
¾ Expressions (<eval>)
If a value given within a command needs to be calculated from other known values, you
can enter an expression from which the required result is to be evaluated by PARAGON
as it executes the command. Such an expression must be enclosed between parentheses
(...) to identify where it begins and ends.
Full details of the expression syntax are given in the Plant Design Software
Customisation Guide and Plant Design Software Customisation Reference Manual, and
are also available as on–line help.
¾ Dimensions (<uval>)
Once the working units have been specified, all dimensions input subsequently will be
assumed to be in those units unless you override them. (Note that these are simply
specific examples of the use of ‘real’ expressions. You can include explicit units of
measurement when entering a value in any expression.)
Examples
5 5 in current working units
5.5 EX 3 5500 in current working units
5.3/4 5.75 in current working units
5’ 5 feet (only use when working units are FINCH)
5’6 5 feet 6 inches (only use when working units are FINCH)
5’6.3/4 5 feet 6.75 inches (only use when working units are FINCH)
5 INCHES 5 inches (regardless of current working units)
5 M 5 metres (regardless of current working units)
5’6.3/4 IN 5 feet 6.75 inches (regardless of current working units)
NOTE: On output, values are rounded by default as follows:
• millimetres to the nearest millimetre
• inches to the nearest 1/32 or 0.1 inch.
However, rounding on output may be controlled by using the PRECISION
command. Within PARAGON, values are stored as accurately as the host
computer will allow.
Profile Components:
SPRFile PROFile number
Joint Components:
SJOInt JOINt number
Fitting Components:
SFITting
(NOTE: FITTing number is not a valid option)
3D Geomset elements:
GMSEt SBOX SDIsc SDIsk
SCOne LSNout SDSH BOXIng
SSLCylinder SSPHere LCYLinder SCYLinder
LINes SCTorus SREVolution SRTorus
TUBe LPYRamid SEXTrusion SLOOp
SVERtex
Negative 3D Geomset elements:
NGMSet NSBOx NSCOne NLSNout
NSDSh NSSLcylinder NSSPhere NLCYlinder
NSCYlinder NSCTorus NSREvolution NSRTorus
NLPYramid NSEXtrusion SLOOp SVERtex
Structural Geomset elements:
GMSSet SRECtangle SANNulus SPROfile
SPVErtex
3D Pointset elements:
PTSEt PTAXi PTCAr PTMIx
Structural Pointset elements:
PTSSet PLINe
Dataset elements:
DTSEt DATA
Detailing Text elements:
SDTExt DTEXt number
Material Text elements:
SMTExt MTEXt number
Bolt Table elements:
BLTAble BLISt SBOLt LTABle
MBOLt MBLIst DTABle
Connection Table elements:
CCTAble COCO
Units elements:
UNIT MSET MTYPe ATLIst
USECtion UDEFinition
This command part identifies a specific element either explicitly or by reference to its
relative position in the database hierarchy.
Examples
/VALVE10 Named catalogue element
SAME Previous element accessed
OWN Owner of Current Element
NEXT 2 2nd element in member list order at same level
4 4th member of Current Element
LAST 3 MEM 3rd last member of Current Element
END Next element up in hierarchy
SECT Section above Current Element
CATE 3 3rd Category
This command part defines the most general method of identifying an Element. The
command is completed by picking an element using the cursor in a graphical view.
Examples
ID @ Lowest level element hit by cursor
ID SBOX @ Box primitive hit by cursor
ID SCOM @ Piping Component hit by cursor
Keyword: PARAGON
At any point during a PARAGON session, you can elect to leave PARAGON and enter
another module of PDMS. This is simply a matter of inputting the name of the module
to be accessed. At this point, PARAGON will automatically save the results of the
working session and change to the new module. However, all graphical displays, forms
and menus will need to be redefined at the beginning of the next session. In order to
avoid having to redefine a view and screen layout, it is possible to save the current
status of a working session by use of the RECREATE command.
Description: If the intention is to leave PARAGON for a short period only this
facility allows the display definition and status (including the full forms
and menus set) to be saved, for restoration later.
NOTE: Forms resized or moved using the cursor will be INSTALLed to their original
size.
Examples:
RECREATE /PARA1 - saves the display status in file /PARA1
RECREATE /PARA1 OVER - as above, but an existing file /PARA1 is overwritten
RECRE DISPLAY /PARA1 - saves nodal settings, e.g. units, representation etc.
Read back in using $M/name
INSTALL SETUP /PARA1 - restores the display definition stored in file /PARA1
Command Syntax:
Description: These two commands are complementary. SAVEWORK lets you update
the databases to incorporate any changes you have made during your
current PARAGON session (since your last SAVEWORK). GETWORK lets
you refresh your view of all READ or Multiwrite databases to pick up
any changes that others may have made since you first opened them.
Description: This command exits from PARAGON without saving any changes or
the display setup. QUIT has the effect of deleting any changes made
since the last SAVEWORK, module change or MDB change.
Examples:
QUIT Exit from PARAGON (to MONITOR module)
QUIT DESIGN Exit from PARAGON to DESIGN module
QUIT FINISH Exit from PARAGON and from PDMS (returns to operating
system)
Command Syntax:
Description: This facility lets you save the alpha display information to a text file in
the computer operating system. Two types of output are available,
depending on the command used.
The ALPHA LOG/ ALPHA FILE facilities may be used to save data or
as a general output facility.
NOTE: After an ALPHA file has been opened, subsequent output will be directed to both
the file and the screen until the file is closed, or until you change to another
PDMS module.
Examples:
ALP LOG - log information displayed in the COMMANDS
/LF1 COMMANDS
region in file /LF1
ALP LOG /LF1 OVER COMM - as above, but overwrite existing file /LF1
ALP LOG /LF2 - log information displayed in both alpha regions
in file /LF2
ALP FILE /LF2 - log information displayed in REQUESTS region
only
ALP LOG END - finish logging information
ALP FILE END
Command Syntax:
Keywords: ALARM
Keywords: TRACE
Description: This command, applicable in TTY mode only, controls the automatic
output of the Current Element name and attributes. With Trace set to
• The CE colour is used for the element currently being accessed (i.e. the element
highlighted in the Members list). This may be either a primitive or a significant
element.
• The Visible colour is used for any element in the display other than those to which
the active or CE colours apply.
• The Active and Visible elements together constitute the Draw List.
The predefined colour mixes which you may specify by name are as follows:
Examples:
COL 5 DARKGREEN Colour 5 will be changed to dark
green
COL 3 MIX RED 50 GRE 50 BLU 5 Colour 3 will change to the specified
mix of red, green and blue
COL VISIBLE BRIGHTRED Sets the colour for displaying
components to bright red
NOTE: When colours are mixed in their Red, Green and Blue constituents, the
command line must contain values for all three constituents in the correct
order. The numbers entered for the relative proportions of the basic colours
must each be in the range 0-100, but they are not percentages of the overall
colour and so do not need to add up to 100.
Command Syntax:
WORLD
(Connections) (Bolts) (Units) (Specifications) (Groups)
SELEC
SBOL DTAB MBOL MTYP UDEF
SPCO
ATLI
(Piping Catalogue) (Steelwork Catalogue)
SECT STSE
CATE STCA
GMSE GMSE MTEX SPRF SFIT GMSS PTSS GMSE NGMS PTSE SMTE
SCOM PTSE DTEX DTSE SJOI SDTE DTSE
SBOX BLTP SREC PLIN SBOX NSBO PTCA
BOXI DATA SANN BOXI PTAX DATA
PTCA
LSNO SPRO LSNO NLSN PTMI
PTAX
SCON SCON NSCO
PTMI SPVE
SSPH SSPH NSSP
LCYL LCYL NLCY
SCYL SCYL NSCY
SSLC SSLC NSSL
SCTO SCTO NSCT
SRTO SRTO NSRT
TUBE TUBE
LPYR LPYR NLPY
SDIS SDIS
SDSH SDSH NSDS
LINE LINE
SEXT SEXT NSEX
SREV SREV NSRE
SLOO SLOO SLOO
NOTES:
For ease of interpretation in text:
SCOM = COMP
SPRF = PROF CATE/STCA (Category) elements
SJOI = JOIN are optional. Their members can be
SFIT = FITT owned directly by a SECT/STSE.
SDTE = DTEX
SMTE = MTEX TEXT elements, which can
appear at several positions in the
Any negative 3D primitive (as shown below NGMS) hierarchy, have been omitted for
can also be owned by any positive 3D primitive. clarity.
CATA is the highest level element of the Catalogue hierarchy. Its attributes include:
• DESC - a text description of the catalogue.
• PURP - a PDMS word showing the specific purpose for which that catalogue is
intended. This should be set to the same word as the Specification with which it is to
be used; e.g. PIPE, FITT.
A CATA can contain a number of Catalogue Sections. These are of two types: Piping
Sections (SECT) and Structural Sections (STSEC). They are the principal
administrative elements by which the Catalogue is divided and arranged. The Catalogue
can also contain Text elements (TEXT) - see Section 9.6.
All elements referred to in a Specification (see the SPECON Reference Guide) must
exist within a CATA hierarchy, although elements may exist within a CATA which are
not referred to by a Specification.
Note that the following elements may also exist within the Catalogue database at the
same level as CATA:
• Units World (UNITS)
• Connection Tables (CCTAB)
• Bolt Tables (BLTAB)
• Specification World (SPWL)
• Group World (GPWL)
Units, Connection Tables and Bolt Tables are described in Chapter 9 of this manual, the
latter element type being described in more detail in the ISODRAFT Reference Manual.
Specification World elements are detailed in the SPECON Reference Manual.
Sections and Categories are administrative elements which let you segregate particular
types of catalogue data into logical parts of the hierarchy. Sections, which subdivide an
overall CATA, are obligatory; Categories, which subdivide Sections, are optional
(although their use is recommended).
There are two types of Catalogue Section: Piping Sections (SECT) and Structural
Sections (STSEC). Both have the following attributes:
• PURP - a PDMS word showing the specific purpose for which that section is
intended.
• GTYP - a PDMS word showing the generic type for elements contained in the
section. This should be the same word as that used to identify the elements in
DESIGN; e.g. VALV, BEAM.
Similarly, there are two types of Category: Piping Category (CATE) and Structural
Category (STCA). Both have the following principal attributes:
• DESC - a textual description of the category.
• PURP - a PDMS word showing the specific purpose for which that category is
intended. This should be set to the same STYPE as in the Specification with which
it is to be used; e.g. GLOB, GATE etc. for a VALV.
• GTYP - a PDMS word showing the generic type for elements contained in the
section.
• SKEY - a textual symbol key showing how the item is represented in isometric
drawings (see the ISODRAFT Reference Manual).
Both types of Catalogue Section or Category contain the elements 3D P-point Set, 3D
Geometry Set, Data Set, Detailing Text and Material Text, as described in Section
4.5.1. Piping Sections/Categories may also contain Piping Components, as described
in Section 4.5.2. Structural Sections/Categories may also contain Structural
Components (Profiles, Joints and Fittings), Structural Pointsets, Negative 3D
Geometry Sets and Structural Geometry Sets, as described in Section 4.5.3.
• Material Text (MTEX) - elements containing text describing the material(s) from
which the physical Component is constructed. Referred to from SPCOM elements in
the Specification. For further details see Section 9.2.
The Catalogue structure as described so far may be used in various ways, but the
recommended method of use is to place only one type of element in each Catalogue
Section, and to place different kinds of Components in different Catalogue Categories.
For example, you might place all 3D Pointsets for Piping Components in one Piping
Section and all 3D Geomsets for Piping Components in another, with separate Piping
Sections for equal tees and reducing tees. When defining Profiles, you might place
Profiles for Universal Beams in one Structural Section, Profiles for Unequal Angles in
another, and so on.
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 MTEX and DTEX elements described in
Section 4.5.1. See Section 9.6 for further details.
4.7 Parameters
Parameters define the size, geometry and other characteristics of Components. They are
used in setting the attributes of the Pointsets, Geomsets and Datasets to which
Component elements refer.
All classes of Component can use component parameters, design parameters and
insulation parameters. Structural Components can also use attached and owning
design parameters. Component parameters are defined in the Catalogue; the other
classes of parameters allow characteristics to be set during the design process.
The types of structural parameter that a Component can use depends on whether it is a
Piping Component, Profile, Joint or Fitting. In the case of a Joint, it also depends on
how the Component is used in the Design DB.
Joints are of two types: primary and secondary. A primary Joint has an attached
Section in the Design DB; a secondary Joint has an attached Section and an owning
Section. (See the DESIGN Reference Manual for details of primary and secondary
Joints.) Note that primary and secondary Joints are represented by the same class of
Catalogue Component, but the settings of their attributes and the attributes of their
Pointsets and Geomsets are different.
A Fitting Component has an owning Section in the Design DB.
Components which have an attached Section (i.e. primary and secondary Joints) can use
attached parameters to define the attributes of their Pointsets and Geomsets. Attached
parameters correspond to the component parameters of the attached Section. For
example, when a Joint component uses APARAM 2, it picks up the value of the PARAM
2 of the Joint’s attached Section.
Similarly, Components which have an owning Section (i.e. secondary Joints and
Fittings) can use owning parameters in defining the attributes of their Pointsets and
Geomsets. Owning parameters correspond to the component parameters of the owning
Section. For example, when a Joint or Fitting component uses OPARAM 5, it picks up
the value of the PARAM 5 of the component’s owning Section.
You can define specimen values for structural parameters in the same way as for
insulation parameters. For example,
Design parameters allow any component with an SPREF to use values from the
design element which refers to it (via the SPREF). For example, the DES PARAM 4 of a
Component is the fourth value in the Design Parameter Array of the design element.
Design parameters can be used anywhere that component parameters can be used.
Design attached parameters and design owning parameters allow a Joint or
Fitting Component to use values from the design elements which represent its attached
and owning Sections. (Attached and owning sections are explained in Section 4.7.3.) For
example, the DES OPARAM 1 of a Component is the first value in the Design
Parameter Array of the design element of its owning Section. Design attached
parameters can be used anywhere that attached parameters can be used. Similarly,
design owning parameters in place of owning parameters.
You can define specimen values for Design DB parameters in the same way as for
insulation parameters. For example,
MODEL SETTINGS DES PARAM 7 9.5
defines a specimen value of 9.5 for design parameter number 7. See Section 6.4.1 for the
full syntax of how to set values for Design DB parameters.
Figure 4-3 summarises how the various types of parameters may be used with the
different classes of Component.
Their attributes are described in the following sections. These attributes (other than the
component parameters) must be set to actual values (words or references to other
elements). They cannot be defined using parameters.
A reference to an element is usually set to the name of the element, for example /PTSR3,
but it can also be set as a general identifier, for example:
PTSE 4 OF SECT 2 OF CATA /ASA-CATA
The attributes of Pointsets and Geomsets may be defined using component
parameters, design parameters and insulation parameters. Where appropriate,
attributes for structural items may also be defined using design owning parameters and
design attached parameters.
A component parameter may be a numeric value, an expression or a word. (The full
syntax for expressions is defined in the Plant Design Software Customisation Guide.) An
insulation parameter, a structural parameter or a Design DB parameter may only be a
numeric value or an expression. The values assigned to parameters and the use to which
they are put, and the number of parameters used, are arbitrary, depending only on the
skill and experience of the user. Chapter 8 contains examples of the parameterisation of
typical Components.
Catalogue Components do not have member elements.
• PARAM - the component parameters, a list of values used in the 3D Pointset and 3D
Geomset to define the Component.
• GTYPE - a word attribute indicating the generic type of the Piping Component,
selected from the following:
ATTA - attachment
BEND - pipe bend
CAP - end cap
CLOS - closure
COUP - coupling
CROS - cross piece
DUCT - ducting
ELBO - fitting elbow
FBLI - blind flange
FILT - filter
FLAN or FLG - flange
FTUB - fixed length tube
GASK - gasket
HELE - hanger element
INST - instrument
INSU - insulation
LJSE - lap joint stub end
NOZZ - nozzle
OLET - weldolets
PCOM - pipe component
REDU - reducer
SHU - standard hook-up
TEE - fitting tee
TRAC - tracing
TRAP - steam trap
TUBE - implied tube
UNIO - union
VALV - valve
VENT - open-ended pipe or vent
VFWA - four-way valve
VTWA - three-way valve
WELD - weld
The GTYPE must be set as one of the above, otherwise a data consistency check
on a Branch containing the Component (see the DESIGN Reference Manual)
will not work correctly.
• PARAM - the component parameters, a list of values used in the Structural Pointset
and Structural Geomset to define the Component.
• GTYPE - a word attribute indicating the generic type of the Profile. Any word value
may be used. The following are suggested:
BEAM - beam
BRAC - brace
COLU - column
GANT - gantry
GIRD - girder
JOIS - joist
PILE - pile
PROF - profile
PURL - purlin
RIDG - ridge
SDRA - side rail
• GTYPE - a word attribute indicating the generic type of the Joint. Any word value
may be used. The following are suggested:
BASE - base
JOIN - joint
KNEE - knee
• CTYA - a word attribute indicating how the Joint is fixed to the attached Section
(the Joint’s connection type for the attached Section). Any word value may be
used. If the connection type attribute of the attached Section (CTYS or CTYE) has
not been set when the Joint is selected in the design process, the attribute will
automatically be set to the value of CTYA. The PDMS data consistency checks (see
the DESIGN Reference Manual) check whether the connection type attributes of the
Joint and attached Section match.
• CTYO - similar to CTYA, but for the Joint’s owning Section (secondary Joints only).
• GTYPE - a word attribute indicating the generic type of the Fitting. Any word value
may be used, but the word FITT is suggested.
• CTYA - a word attribute used only if the Fitting is attached to a pipe hanger in the
Design DB. Any word value may be used. If the connection type attribute of the pipe
hanger (HCON or TCON) has not been set when the Fitting is selected in the design
process, the attribute will automatically be set to the value of CTYA. The PDMS
data consistency checks (see the DESIGN Reference Manual) check whether the
connection type attributes of the Fitting and pipe hanger match.
NOTE: For details of the MODEL SETTINGS command syntax used to set default values
for component parameters, and specimen values for other classes of parameter,
see Section 6.4.1.
There are many ways in which you can explore the contents of the Catalogue database,
but they fall into three broad categories:
• Accessing a Catalogue element whose identity or hierarchical position is known
• Accessing a Catalogue element whose position in the hierarchy relative to the
current position is known
• Accessing a Catalogue element by picking it from the screen
It is important to appreciate that these navigation facilities provide you with access to
the complete Catalogue and not just those items shown on the graphical display.
In graphical form, you can jump straight to an element which is shown in the screen
display by positioning the cursor over the element and pressing the left-hand mouse
button. This identifies the item under the cursor and makes it the current element.
Alternatively, the cursor can be used in the Members menu (or the command window) to
pick a name from the text display.
You can jump straight to a known element simply by typing its name. You would
usually name an element when you create it.
All elements are automatically given a reference number when created. By stating this
reference it is possible to access an unnamed element. Reference numbers are not
normally shown in PARAGON, but may be obtained by the using the Q REF command.
Keywords: SAME CE
Description: SAME takes you to the element you were at before you accessed the
current element. Repeating the SAME command has the effect of
moving repeatedly between two items - it does not move back along the
list of items accessed.
CE takes you to the current element itself. (This facility may seem
rather pointless in this situation; however the CE keyword is used in
many commands as a means of identifying an element to be the object
of that command.)
Example:
ADD CE - Add the current element to the display.
Command Syntax:
>-- CE -->
>-- SAMe -->
Keywords: GOTO
Description: Most of the above commands can be linked together with the OF
keyword to produce general navigation commands.
Examples:
FIRST SECT OF CATA /PIPECATA
LAST PTSE OF PREVIOUS 3 SECT
FIRST SCOM OF /CATE 5
Command Syntax:
This chapter introduces the methods of Component design and graphical representation
in PARAGON; in particular the MODEL, MODEL SETTINGS and REPRESENTATION
commands are detailed.
Assuming that you have opened a suitable 3D view, the interactive graphical
Component design process in PARAGON is initiated using the MODEL command.
If a new Component is to be designed, then a new catalogue element must first be
specified by a command such as
NEW SCOM /CR2-1 (at SECT or CATE level)
or
NEW SPRF /UB4-A (at STSEC or STCAT level)
The command
MODEL CE
(for ‘Model Current Element’) will add the new component to the 3D view.
Note that the MODEL CE command is valid only for SCOM, SPRF, JOIN, and SFIT
elements.
Only complete Components may be displayed in this way - individual Pointsets and
Geomsets may not be, although these items will easily be distinguishable. (Geomset
and/or Pointset elements can be removed from the display with the aid of the
REPRESENTATION command - see next section).
The MODEL SETTINGS command can be used to specify the Component Design Data
attributes. For example,
MODEL SETTINGS DDRADIUS 75 DDHEIGHT 200
gives the Design Data attributes DDRADIUS and DDHEIGHT values of 75mm and
200mm respectively. The DDRADIUS, DDHEIGHT and DDANGLE attributes are the
Design parameters used in the selection process for variable Components. In PARAGON
it is possible to use these attributes as part of the Component design. For example,
whereas an attribute such as PHEIGHT would normally be defined in terms of
parameters, a command such as
PHEI DDHEIGHT
(assuming a suitable current element) would set PHEIGHT to the Design height. (In
such a case, a MODEL SETTINGS command would need to be followed by a MODEL CE
command before any change in the display would be observed.)
To produce a display of a Component with insulation, the bore, temperature and
working pressure of the Component must be known. To this end the MODEL SETTINGS
command can be used to set the BORE, TEMP and PRESSURE. This must be done
before the Insulation Specification, INSPEC, can be specified. For example,
MODEL SETTINGS TEMP 300 BORE 80
would set the temperature and bore Design Data attributes (the pressure would stay at
its default value, see below). The Insulation Spec may then be specified by a command
such as
MODEL SETTINGS INSPEC /INSUL1
Assuming the drawing REPRESENTATION (see Section 6.4) is correctly set, the
Component will then be displayed with insulation shown.
All Design settings can be restored to their defaults by
MODEL SETTINGS DEFAULT
NOTE: This command also deletes all default and specimen values of parameters. It
unsets the Insulation Specification.
The default values of the Design Data attributes, and the full syntax of how to set them,
are given in Section 6.4.
QUERY MODEL SETTINGS will output the Design settings currently in use. The Design
process is turned off by
MODEL END
which also has the effect of clearing the display.
6.2.1 P-points
P-points may be displayed in PARAGON in one of two ways. The form of display is
controlled by the REPRESENTATION PPOINTS command as illustrated in Figure 6-1.
The size of the arrow may also be controlled by the REPRESENTATION PPOINTS
command, as illustrated in Figure 6-2. The overall length of the arrow is specified in
millimetres. The default length is 50mm. Specifying a length of zero causes the P-point
to appear as a dot.
The P-point numbers may be omitted, or they may be displayed any size, the size being
specified in millimetres. The default size is 5 mm. The size of the numbers is controlled
by the REPRESENTATION PPOINTS command, as illustrated in Figure 6-3.
Both LENGTH and NUMBERS may be set in the same command, for example:
REPRESENTATION PPOINTS ON LENGTH 25 NUMBERS ON SIZE 7
NOTE: P-points are always displayed in some form. They cannot be omitted from the
display completely.
See the Reference Section at the end of this chapter for the full syntax of the
REPRESENTATION PPOINTS command.
6.2.2 P-lines
P-lines may be displayed in PARAGON in one of two ways. The form of display is
controlled by the REPRESENTATION PLINES command as illustrated in Figure 6-4.
The P-line identifier keys may be omitted or displayed. This is also controlled by the
REPRESENTATION PLINES command, as illustrated in Figure 6-5.
P-line length (default 50mm) and size (default 5mm) can also be controlled. See the
Reference Section at the end of this chapter for the full syntax of the REPRESENTATION
PLINES command.
Unlike P-points, P-lines can be omitted from the display completely. Whether a P-line is
drawn or not depends on the settings of three of its attributes:
Whether a Geomset primitive is displayed or not depends on the settings of its LEVEL,
CLFLA and TUFLA attributes (as for a P-line) and also on its OBST attribute. (The
OBST attribute is a number which defines the degree of obstruction for clash checking.)
If the PARAGON LEVEL setting is within the LEVEL range specified for the primitive
(as its LEVEL attribute), then the primitive will be considered for drawing, otherwise it
will not be. If the level condition is satisfied then, the primitive will be displayed if it has
an OBST value of 1 or 2 and the REPRESENTATION setting is
REPRESENTATION OBSTRUCTIONS ON
The primitive will be drawn in solid lines if OBST = 2 (hard obstruction), dashed lines if
OBST = 1 (soft obstruction0.
The control mechanisms of tube, centreline and obstruction are quite independent of
each other. So, for example, if a primitive has an OBST value of 2 and the
REPRESENTATION setting is OBSTRUCTIONS ON, the primitive will be drawn
whatever the values of its CLFLA and TUFLA attributes and the REPRESENTATION
TUBE and CL settings (provided that the PARAGON LEVEL setting is within the
LEVEL range of the primitive).
NOTE: Whenever you use a REPRESENTATION command, the current design
Component is redrawn. If you want to change several REPRESENTATION
settings, put them all in the same line so that the Component is only redrawn
once. For example,
For this example, the settings of the attributes of interest are considered to be:
Here the OBST ON setting matches the OBST 2 attribute value of the obstruction
cylinders and so they become visible, even though they have CLFL and TUFL both
FALSE.
Here TUBE and CENTRELINE are both OFF but OBST is ON, and so only the
obstruction volume primitives are visible.
Compared with Figure 6-9, those primitives with TUFL TRUE now become visible
because TUBE is now ON. The obstruction primitives remain visible because OBST is
still ON.
OBST is now OFF and so the obstruction cylinders disappear. (The obstruction dish
remains because it has TUFL TRUE.)
Here, all those primitives which have one or both of CLFL, TUFL TRUE are visible.
In Figure 6-13, all the REPRESENTATION settings are ON and so all the Geomset
primitives are visible.
Here, all the REPRESENTATION settings are OFF and so no primitives are visible. The
Component P-points are still visible since the REPRESENTATION PPOINTS setting in
the example is ON.
The full default REPRESENTATION is:
CL ON
TUBE OFF
OBSTRUCTIONS OFF
LEVEL 0
PPOINTS ON LENGTH 50 NUMBERS OFF
PLINES ON PKEYS OFF
which is regained by
REPRESENTATION DEFAULT
Note that the TVISIBLE and BVISIBLE end visibility flags have no effect in
PARAGON.
This section gives the syntax of the MODEL SETTINGS command and the
REPRESENTATION command, as described in this chapter and in Chapter 4 (the latter
for setting component parameter defaults etc.).
The description of the syntax for the REPRESENTATION command is spread over a
number of separate sections, each showing how the command is applied to a particular
type of element. The final section summarises the complete REPRESENTATION syntax in
a single diagram.
Querying information is given, as are further examples, where appropriate.
MODEL SET IPAR 1 3.5 IPAR 2 4.5 Sets insulation parameter 1 to 3.5
and insulation parameter 2 to 4.5
MODEL SET APAR 3 5.1 OPAR 2 19.75 Sets attached parameter 3 to 5.1
and owning parameter 2 to 19.75
MODEL SET DES PAR 2 (ATAN(4 / 3)) Sets design parameter 2 to tan-1 4/3
MODEL SET DDANG (ASIN(6 / 7)) Set Design Angle to arcsin (6/7)
Command Syntax:
.---------------------<------------------.
/ |
>- MODEL - SETtings --+--*- CATalogue* -. |
| |- DESign -----| |
| |--------------+- PARam --. |
| | |- APARam -| |
| | ‘- OPARam -+ |
| | | |
| |- IPARam ----------------+------. |
| | .-------------’ |
| | ‘- number -+- value ----|
| | ‘- <expres> -|
| | |
| |-- INSpec --- name -----------------------|
| | |
| |-- TEMp --- value ------------------------|
| | |
| |-- BORe --- value ------------------------|
| | |
| |-- PREssure --- value -------------------|
| | |
| |-- DDHEIght --- value --------------------|
| | |
| |-- DDRADius --- value --------------------|
| | |
| ‘-- DDANGle ---+--- value ----------------|
| ‘--- <expres> --------------|
| |
‘--- DEFault --------------------------------+-->
Querying Syntax:
.---------------------<-----------------.
/ |
>-- REPResentation --*-- CL -------------------------. |
| | |
|-- CENTreline -----------------| |
| | |
‘-- TUBE -----------------------+-- ON ---|
| |
‘-- OFF --+-->
Querying:
Q REPR TUBE
Q REPR CL
Q REPR - queries all Representation options.
.-----------------<--------------------.
/ |
>-- REPResentation --*-- PROFile --+-- CL ----------. |
| | |
|-- CENTreline --| |
| | |
‘----------------+-- ON ---|
| |
‘-- OFF --+-->
Querying:
Q REPR PROF
Q REPR - queries all Representation options.
Description: This command enables individual drawing levels to be specified for the
display of catalogue elements. Every basic primitive shape has an
associated drawing level range attribute stored in the Catalogue. If the
specified drawing level coincides with this range, the 3D object will be
drawn when it is added to the Draw List.
.-------------------<-------------------.
/ |
>-- REPResentation --*-- LEVel --+-- PIPE -------. |
| | |
|-- NOZZle -----| |
| | |
|-- STRUcture --| |
| | |
‘---------------+-- integer --+-->
Querying:
Q REPR - lists all REPRE options
Q REPR LEVEL - lists levels at which other Components are drawn
Q DISPLAY - gives units and tolerance settings, as well as
representation levels
.--------------<------------.
/ |
>-- REPResentation --*-- OBSTruction --. |
| | |
|-- INSUlation ---+-----------|
| |
‘-- PROFile --+- OBSTruction -|
| |
‘- INSUlation --+- ON --.
| |
‘- OFF -+-->
Querying:
Q REPR Lists all Representation settings
Q REPR INSU Queries if INSU is ON or OFF
Q REPR OBST Queries if OBST is ON or OFF
When p-points are on, they are drawn as small arrows with a cross at
the p-point position and with the arrow indicating the p-point direction.
The size of the arrow is controlled by the LENGTH option. P-point
numbers may also be displayed, as controlled by the NUMBERS option.
When p-lines are on, the size of the arrow showing their direction is
controlled by the LENGTH option. P-line identifiers, in the form of the
settings of their PKEY attributes (TOS, BOS, NA, etc.) may also be
displayed, as controlled by the PKEY option.
.---------------------<---------------.
/ |
>-- REPResentation --*-- PLINes -+- ON --. |
| | | |
| |- OFF -| |
| | | |
| ‘-------+- LENgth - <uval> -|
| | |
| ‘-------------------|
| |
‘-- PKEYs --+- ON --. |
| | |
‘- OFF -+-------------------+-->
Querying:
Q REPR PLINES
Q REPR PKEYS
Continued Continued
| |-- HOLes - <onoff> -------------------------|
| | |
| |-- MASSproperties - <int> ------------------|
| | |
| |-- DARCtolerance - <uval> ------------------|
| | |
| \-- UPDATE ----------------------------------|
| |
‘-- DEFault ------------------------------------+-->
<ppsiz> is
>--+- LENgth - <uval> -.
| |
‘-------------------+- NUMbers - <onoff> -.
| |
‘---------------------+-->
<colno> is
>--+-- integer ----------------------------------------.
| |
|-- ACTive -----------------------------------------|
| |
|-- VISIble ----------------------------------------|
| |
|-- CE ---------------------------------------------|
| |
|-- CLASH ------------------------------------------|
| |
|-- OBST -------------------------------------------|
| |
|-- COMPAre --+-- MATCHed -----------------------. |
| | | |
| |-- MISMatched --------------------| |
| | | |
| |-- UNMAtched --+-- CONNector --. | |
| | | | | |
| | ‘---------------+--| |
| | | |
| ‘-- TEXT --------------------------+--|
| |
‘-- AIDS -------------------------------------------+-->
A PTSET is a collection of P-point elements. P-points are used in the design process to
position and orientate Piping Components, and to define their connectivity to each
other. P-points may also be used in PARAGON to define the position and orientation of
the 3D Geomset primitives which make up Piping Components, Joints and Fittings.
(Profiles do not use P-points.)
A P-point has a 3D position and a direction, and is identified by a number. Each
PTSET includes a special P-point, P-point zero (P0), whose position is the component
origin and whose direction is the Z axis direction of the Component. It has no other
attributes. P0 is created automatically by PARAGON; you cannot change it in any way.
The numbering of the P-points of Piping Components must follow certain conventions -
see Appendix A for a summary of these, and the ISODRAFT Reference Manual for fuller
details. There are no special conventions for numbering the P-points of Joints and
Fittings.
A P-point has a connection type attribute, which is used only when the P-point
belongs to a Piping Component. The connection type attribute can be used to specify how
a Piping Component is connected to another at the position of the P-point, for example
by a butt weld or socket weld.
A P-point has a bore attribute, which is used only when the P-point belongs to a Piping
Component. It can be used to specify the bore of the pipe at that point.
PDMS’s data consistency checks (see the DESIGN Reference Manual) can be used to
check that the connection type attributes of Piping Components are compatible with the
corresponding attributes of the Components to which they are connected. The
compatibility of connection types is defined in a Connection Compatibility Table
(CCTAB) - see Section 9.3 for details.
Use of the REPRESENTATION command affects how P-points are drawn by PARAGON;
see Section 6.2 for details.
A PTSET has the following attributes:
• DESC - a textual description of the Pointset
• GTYP - the generic type of the item for which the Pointset is
used
• SKEY - the Symbol Key to which the Pointset relates (see the
ISODRAFT Reference Manual)
• PURP - the purpose of the Pointset
A PTSET may contain one or more of the three types of P-point element:
• Axial P-point - PTAXI
• Cartesian P-point - PTCAR
• Mixed P-point - PTMIX
A PTSSET is a collection of P-line elements (PLINE). P-lines are used in the Catalogue
by Profiles and Joints. P-lines are used in the design process to position and orientate
Sections (derived from Profiles) and Joints.
Direction Position
of P-line of P-line
PROFILE X
(viewing in
-Z direction)
Position
Direction
of P-line
of P-line
X
SECTION Z
A P-line is the structural counterpart of a P-point. It is a line which runs the full length
of a Component parallel to its Z axis. Viewed in the XY plane, it appears as a point. This
point is its position. A P-line also has a direction. This is not the direction of the line
itself (which is always parallel to the Z axis of the Component), but a direction from the
line in the XY plane. The position and direction are defined in XY coordinates only.
Figure 7-1 shows a two-dimensional view and a three-dimensional view of a P-line on
the top of a Section.
P-lines may be used in PARAGON to define the position and orientation of the 2D
primitives in a Structural Geomset which make up a Profile. They cannot be used to
position and orientate the 3D primitives which make up a Joint.
One of the P-lines in a Structural Pointset must be designated as the neutral axis p-
line. This is used in DESIGN for positioning and orientating the Component. (The
neutral axis is the line where there is no stress in bending, and about which the
Component bends.) A P-line is designated as the neutral axis by setting the neutral
axis reference attribute (NAREF) of the Structural Pointset to the name of the P-line.
A PLINE has no member elements and has the following attributes:
• PKEY - the P-line identifier key
• PX,PY - the X, Y coordinates of the P-line
• PLAXI - the axis of the P-line, defining its direction
• LEVEL - the drawing level range attribute
• CLFLA - the centreline drawing flag attribute
• TUFLA - the tube drawing flag attribute
• DESC - a textual description of the Pline
• PURP - the purpose of the Pline
PKEY is a word attribute which identifies the P-line. It is equivalent to the NUMB
attribute of a P-point. PLAXI is a direction, equivalent to the PAXI attribute of a P-
point.
PKEY must be set as a word. PLAXI must be set as a direction - see Section 8.6.3 for
details. PX and PY may be set as values or in terms of parameters. The classes of
parameter which may be used depend on whether the P-line is used by a Profile or by a
Joint - see Section 4.7 for details. Chapter 8 gives examples of setting these attributes.
The settings of LEVEL, CLFLA and TUFLA and the use of the REPRESENTATION
command affect whether or not the P-line is drawn by PARAGON. LEVEL is a pair of
numbers specifying a range and CLFLA and TUFLA are set to TRUE or FALSE
(corresponding to ‘on’ or ‘off’ respectively). The way in which LEVEL, TUFLA and
CLFLA and the REPRESENTATION settings interact is discussed in Section 6.2. (The
settings of LEVEL, CLFLA and TUFLA also affect whether or not the P-line is drawn in
DESIGN.)
The primitives in the Geomsets also have LEVEL, CLFLA and TUFLA attributes, which
affect whether or not they are drawn in PARAGON and DESIGN.
NOTE: A P-line has its own set of axes, which are used in the design process (not in
PARAGON). See the DESIGN Reference Manual for details.
The settings of LEVEL, CLFLA and TUFLA affect whether the primitive is drawn or not
by PARAGON (or DESIGN), as they do for P-lines. See Section 7.2 for details.
OBST is a number which defines the obstruction level of the primitive for use by
DESIGN’s clash checking facility:
• OBST = 0: No obstruction. The primitive will not clash with anything (used for
symbols and negative volumes).
• OBST = 2: ‘Hard’ obstruction. DESIGN’s clash checking facility will report hard
interference with any item having OBST 1 or 2.
The LEVEL, OBST, CLFLA and TUFLA attributes are common to all primitives. Each
primitive also has additional attributes depending on its shape; these are described in
the next section.
The following primitive elements are used by 3D Geomsets. They all have the standard
attributes and the common attributes LEVEL, CLFLA, TUFLA and OBST.
When implied tube is drawn using BOXI elements, the Y axis of the implied BOXI is set
to the PLeave direction of the preceding component. The X axis of the BOXI is set to be
mutually orthogonal to the PLeave and the Z axis of the preceding component (which
usually corresponds to the X axis of the component). The Z axis of the BOXI is then
derived from its X and Y axes (and usually corresponds to the Z axis of the component).
A 3D Geomset may contain more than one BOXI element and corresponding P-points
may be offset in the X or Z directions.
Note for Pipework Designers: If there is no preceding component (that is, if the
implied BOXI forms the Head of a Branch), the Y axis will be set to the Parrive of the
following component (that is, the first component in the Branch). If there are no
components, the BOXI will be set to the orientation of the Zone. (Since Pipe and Branch
elements have no coordinate system, this is the lowest level in the design hierarchy from
which an orientation can be derived.)
PAXI
PHEI
PYBS (-n)
PDIS PDIA
X
ORIG PDIA
PAXI
PDIS PHEI
The values held in PTS are set by the SETPoints command, followed by point
specifications in which each p–point identifier is preceded by ‘P’ or ‘T’, e.g. P1 P2 T3 P4.
When the P-point is preceded by P it is treated in the same way as a point element
(POINT) in the Design Data; when preceded by a T it is treated in the same way as a
tangent point element (TANP) in the Design Data. (See DESIGN Reference Manual for
further details).
The sizes of the top and bottom surfaces of the snout may be defined in terms of their
radii instead of their diameters.
• PTRA, PBRA - radius of top, bottom surfaces of snout
(PX,PY)
of
SVER
PAAX of SEXT
SLOO = SVER
Origin
(PX,PY,PZ)
PANGLE
Z
X (PAAX)
NOTE: For correct clash detection, the maximum number of primitives with OBST set
to 1 or 2 in any GMSSET is 20; the order of these in the members list is not
important. See the DESIGN Reference Manual for details of the best way of
setting up Component data so as to minimise processing time for clash
detection.
The primitives have additional attributes as described in the next section.
The following primitive elements are used by Structural Geomsets. They all have the
standard attributes and the common attributes LEVEL, CLFLA, TUFLA and OBST.
The additional particular attributes of each element are as described below.
Note that each 2D primitive has effectively two types of positional attributes which
allow its geometry to be changed progressively as it is extruded in space to create a 3D
design element (such as a structural SCTN or GENSEC element). The P... attributes
define the geometry at the Start of an extruded section, while the D... attributes define
the change in that geometry between the Start and End of the extruded section.
PXLEN
PLAXIS
PYLEN
PY
X
PX
PANGLE
PRADIUS
PLAXIS
PWIDTH
PY
PX X
SPVE SPVE
PLAXIS
SPRO
X
PX
This chapter describes how to create and manipulate the member elements of the PDMS
Catalogue database.
Querying:
OLD
END
SAME
CE
OWNER
GOTO e.g. GOTO PTREF
NAME
UNNAME
LOCK
UNLOCK
These commands are those which are common to all ‘constructor’ modules of PDMS and
some are used in this chapter without further explanation. However, the element types
which the above commands operate on relate to the Catalogue database rather than the
Design database (so, for example, NEXT SITE is meaningless in PARAGON).
Catalogues and Sections are created using the NEW command. You would normally also
specify names by which you can recognise and refer to the elements created. For
example:
NEW CATA /ANSI-CATALOGUE
will create a Catalogue with the name /ANSI-CATALOGUE in the Catalogue database.
NEW SECT /FLANGES
NEW STSEC /PROFILES
will create a Piping Section with the name /FLANGES and a Structural Section with the
name /PROFILES. Similarly,
NEW CATEG /ANSI-B16.5-CLASS-300-BLIND-FLANGES
NEW STCAT /UNIVERSAL-BEAM
will create a Piping Category and a Structural Category with the names given.
A Catalogue Component is represented by one of the Component elements SCOM,
SPRF, SJOI, SFIT (see Section 4.8).
NEW SCOM
will create a Piping Component with unspecified component parameters, the values of
which may be set later.
If the Component is to be named, this can be done at the same time; for example,
NEW SFIT /EKAA2VEE
The attributes of the Component (see Section 4.8) are set simply by following the
attribute with the word, name or value(s) to be assigned to it. For example:
NEW SCOM
GTYPE ELBO
PTREF /PSE1
GMREF /GSE1
PARAM 20 19.1 12.7 37.1 BWD
The above commands create a Piping Component, of generic type ELBO, which is
defined by 3D Pointset /PSE1 and 3D Geomset /GSE1, and which has the five
component parameters shown. The Pointset and Geomset which are referred to by name
must already exist; they would have been created by the commands
NEW PTSET /PSE1
NEW GMSET /GSE1
All five component parameters have been given values using a single command line, but
they can be given values individually by using commands such as
PARAM[1] 20
PARAM{2] 19
...
etc.
NOTE: You can only use the PARAM[number] syntax to change the value of a parameter
which has already been set.
This facility allows component parameter definitions to be ‘edited’. (Caution: If you
delete a COMP which is referred to by a SPCO - via the CATREF attribute of a design
component - this reference will be lost.). The use of component parameters and the other
classes of parameter is discussed and illustrated in the next section.
NOTE: If you give a PARAM command with, say, four values as a single command line,
PARAGON sets the values of the first four component parameters and deletes
all the rest.
You may define default values which PARAGON will use if you are working with a
Component whose component parameters have not been set up. See Section 4.7 for
details.
The attributes of a Component may be queried by a
QUERY ATTRIBUTES
command, or may be queried individually by name. Component parameters can be
queried as a set by using the command
QUERY PARAMETERS
or singly by using commands such as
QUERY PARAMETER[1]
QUERY PARAMETER[2]
etc.
8.3.1 Introduction
Piping Components, Profiles and Fittings each use one type of Pointset and one type of
Geomset. Joints use both types of Pointset and one type of Geomset. The attributes of
Pointsets and Geomsets may be defined in terms of parameters, set either explicitly or
as real expressions (which may themselves incorporate the current settings of other
parameters). (The classes of parameter which may be used depend on the class of
Component - see Section 4.7 for details.)
For example, the bore of a P-point could be defined by entering
PBORE (PARAM[1])
This means that the value assigned to the bore of the P-point is the value of the first
component parameter.
The Y dimension of a box in a 3D Geomset used by a Joint could be defined as the
expression
PYLEN (APARAM[2] + 3)
This means that the Y dimension of the box is to be given a value in the design process,
taken from the Section to which the Joint is attached. The value of the Y dimension of
the box is the value of the second component parameter of the attached Profile plus 3
mm.
The use of parameters makes it possible to use the same Pointsets and Geomsets for
large numbers of catalogue items. For example, there may be families of tees, valves, I-
beam profiles etc., each family containing items which are geometrically similar. In this
way, the Catalogue size and the effort needed to prepare input data are minimised.
Examples of the parameterisation of typical Components are given later in this chapter.
The values assigned to parameters, the uses to which they are put, and the number of
parameters used, are arbitrary, depending only on the skill and experience of the user,
except in the special case of a Piping Component which represents implied tubing
(GTYPE attribute set to TUBE) and which has no Geomset. In this case, component
parameter 2 must be the outside diameter. If the tube is to be insulated, insulation
parameter 1 must be twice the thickness of the insulation.
Note on the use of Insulation Parameters: Insulation parameters may be used in
two ways. They may be used in an additive manner to increase the diameter or length of
a primitive or, if there is a significant change in the geometry from the uninsulated to
the insulated form, they may be used to define a new primitive. Where there is no
insulation, the insulation parameters will be zero, yielding a primitive of zero diameter
(but probably non-zero length).
An Angle Joint might be parameterised using three component parameters and two
attached parameters, as shown in Figure 8-4.
• PARAM 1 - Overall height of angle leg
• PARAM 2 - Overall length of angle foot
• PARAM 3 - Thickness of leg and foot
PTAXI
If the Pointset is used by a Piping Component, you may optionally define the attributes:
• Connection type (PCON)
• Bore (PBOR)
• P-point symbol key (PSKEY) (see Section 8.5.8)
PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
PTCAR
If the Pointset is used by a Piping Component, you may optionally define the attributes:
• Connection type (PCON)
• Bore (PBOR)
• P-point symbol key (PSKEY) (see Section 8.5.8)
PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
PTMIX
If the Pointset is used by a Piping Component, you may optionally define the attributes:
• Connection type (PCON)
• Bore (PBOR)
• P-point symbol key (PSKEY) (see Section 8.5.8)
PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
The classes of parameter which you can use depend on the class of the Component which
uses the P-point - see Section 4.7 for details.
If you do not define the axis, PAXI Y is assumed.
DESIGN will use as the neutral axis the first P-line in the Structural Pointset which
has a PKEY value of NA, if any. Failing that, it will choose the first P-line with a PKEY
value of NAXI, and failing that, it will choose the first P-line with a PKEY value of
ZAXI. If there are no P-lines with a PKEY value of NA or NAXI or ZAXI, DESIGN will
assume that the neutral axis of the Component lies at the component origin and has a
direction along the positive Y axis.
The classes of parameter which you can use depend on the class of the Component
which uses the P point - see Section 4.7 for details.
NOTE: Only the first 20 primitives in a Geomset with OBST values of 1 or 2 are
considered by DESIGN’s clash checking facility.
By using the TUFLA and CLFLA flags, you can create two different drawings of a
Component, a double-line representation (tube) and a single-line ‘stick’ representation
(centreline).
To define the tube representation for the tee shown in Figure 8-2 (with clash geometry)
the commands shown below could be used. (The P-points in the following examples
relate to the Pointset defined in section 8.5.1.)
NEW GMSET /RTGMSE Create new 3D Geomset
NEW SCYL Create cylinder primitive
PAXI -Y Direction of axis on which SCYL origin lies
PDIS (PARA[5]) Distance of SCYL origin from tee origin = half
overall length
PDIA (PARA[2]) Outside diameter of main run
PHEI (-2 * PARA[5]) Height of SCYL
OBST 2 Set obstruction value as ‘hard’
TUFL TRUE CLFL FALSE Set drawing flags
NEW SCYL
PAXI X
PDIS 0
PHEI (PARA[6])
PDIA (PARA[4])
OBST 2
TUFL TRUE CLFL FALSE
To define the centreline representation for the tee (with welded joints), the following
commands could be used. Figure 8-10 shows the symbol produced. The illustration is
drawn with REPRESENTATION PPOINTS ON LENGTH 0 NUMBERS ON. The P-points
are thus displayed as dots, but they cannot be seen because they lie on the displayed
LINEs.
To put the flanges on the tee the first two representations (as given above) would remain
the same but the centreline representation would not need the SSPH elements (which
represent the welds). The latter are replaced by using the following commands to
represent the flanged connections:
NEW SCYL PAXI P1 PHEI (-PARA[10]) PDIA (PARA[9])
PDIS 0 OBST 2 CLFL TRUE TUFL TRUE
NEW SCYL COPY PREV PAXI P2
NEW LCYL PAXI P3 PTDI 0 PBDI (-PAR[12]) PDIA (PAR[11])
OBST 2 CLFL TRUE TUFL TRUE
PLAXI Y
TUFL FALSE CLFL FALSE Set both drawing flags ‘off’
OBST 2 Set obstruction value as ‘hard’
A P-line may be used to define an axis direction and position for a primitive. The
example below shows how the upper flange could be positioned and orientated using a P-
line. See the Reference Section at the end of this chapter for details.
PLAXI TOS Set axis direction and origin in terms of
P-line TOS
PY (-0.5 * PARA[4]) Position of rectangle origin relative to
position of P-line
Examples:
PAAX -P2 sets PAAX to be opposite the direction of P-point 2 with
its origin at the position of the P-point
PBAX X34-Y sets PBAX to the given direction from the component
origin
PCAX X45Y30Z sets PCAX to the given direction from the component
origin
PAXI X DDANG Z takes the Design DDANGLE and calculates the
direction accordingly
Syntax:
>--+-- X --.
| |
|-- Y --|
| |
‘-- Z --+-->
If the axial attribute of a 2D primitive is specified as a P-line, the direction of the axis is
taken to be the direction of the P-line, and the origin of the axis to be the position of the
P-line. If the axial attribute is specified as a direction or direction expression, the origin
of the axis is taken to be the component origin.
Examples:
PLAX PLIN NAXI sets PLAX to be the direction of the P-line whose PKEY
attribute is NAXI; the origin of the axis is at the
position of the P-line
PLAX X60-Y sets PLAX to the given direction from the component
origin
Syntax:
>--+-- X --.
| |
‘-- Y --+-->
and <plkey> is the PKEY attribute of the P-line.
Detailing Text (SDTE) elements contain descriptive text relating to a Component, which
is used during the construction of drawings, reports, take-off sheets etc. An SDTE
element exists at the same level in the Catalogue database hierarchy as a Component
element (i.e. it is a member of a Section or Category) and is referred to from SPCOM
elements in the Specification.
An SDTE element (which will usually be named) is created simply by typing, for
example:
NEW SDTE /C/T1
The text itself exists as an attribute of the SDTE element; namely one of the attributes
RTEX, STEX or TTEX. The text is input simply by typing the attribute name followed
by the text itself in quotes; for example:
STEX ’21DD-JJOOA2 12.31’
The choice of attribute name depends on the PDMS module which is to use the related
text. STEX and TTEX are used primarily by the detailing interface modules, and the
attribute to be used will be specified from that module. The format of the text depends
on the detailing module in use - see the appropriate Reference Guide for details.
RTEX is used by ISODRAFT, which also uses another SDTE attribute, SKEY. SKEY is
a four-character code which represents a geometric description of the associated
Component type. RTEX and SKEY must be set in order for ISODRAFT to work
correctly. A typical pair of commands would be:
RTEX ’COUPLING - SOCKET WELD 3000LB’
SKEY ’COSW’
(The SKEY codes are fixed for a given element type - see the ISODRAFT Reference
Guide for a list.)
Material Text (SMTE) elements contain descriptive text describing the material(s) from
which the physical component is constructed, and is used during the construction of
drawings, reports, take-off sheets etc. An SMTE element exists at the same level in the
Catalogue database hierarchy as a Component element (i.e. it is a member of a Section
or Category) and is referred to from SPCOM elements in the Specification.
An SMTE element (which will usually be named) is created simply by typing, for
example:
NEW SMTE /5L-S-80
The text itself exists as an attribute of the SMTE element; namely one of the attributes
XTEX, YTEX or ZTEX. The text is input simply by typing the attribute name followed
by the text itself in quotes, for example:
XTEX ’SCM.80 API 5L GR.B SMLC’
The choice of attribute name depends on the PDMS module which is to use the related
text, the attribute to be used being specified from that module. XTEX is used by
ISODRAFT.
The Connection Compatibility Table (element name CCTA) holds a list of all the
compatible connection types for Piping Components in a set project. A CCTA is an
administrative element which exists at the same level as CATA in the hierarchy. A
CCTA has Connection Compatibility (COCO) elements as its members, each of which
has a pair of coded connection types stored as its CTYPE attribute. These connection
types are those referred to in the PCON attribute of a Piping Component’s P-points.
The commands below give an example of the setting up of a typical connection table.
NEW CCTA
NEW COCO /WELDWELD CTYPE WELD WELD (weld to weld)
NEW COCO /SCRDSCRD CTYPE SCRD SCRD (screwed to screwed)
NEW COCO /WELDBW CTYPE WELD BW (weld to butt weld)
Note that ISODRAFT uses the connection codes to derive bolting requirements, and so
the connection codes used must conform to certain standards - see Appendix B and the
ISODRAFT Reference Guide for details. Setting up the Connection Compatibility Table
should be one of the first tasks to be carried out when commencing a design project
using PDMS.
The Bolt Table hierarchy contains information describing the nature of the bolted
connections of Piping Components in a project. Although the Bolt Table is part of the
Catalogue database, and so must be set up using PARAGON, 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. Element creation and attribute setting is done
in the usual way.
The Bolt Table hierarchy is illustrated below:
WORLD
SECT
BLIST LTAB
BTSE
SBOLT DTAB
BLTP
• BLTP - the Bolt P-point stores the bolting information for an individual bolt for a
particular type of flange. It has the following attributes:
• BLIS - the Bolt List is an administrative element which groups together Standard
Bolt (SBOL) elements.
• DTAB - the Diameter Table stores information on standard bolt lengths, held as a
string of values in its BLEN attribute. DTAB is accessed from the NSTD attribute of
the SBOL element.
PARAGON enables unit types to be set up which will then be linked to relevant
attributes of the various elements which appear throughout the PDMS databases. The
most common units (the default units) are millimetres, inches or feet and inches, which
are usually assigned to bore and distance attributes. These units currently apply to all
PDMS modules except PROPCON.
You may also define other units with conversion factors to relate one set of units to
another; unit definitions can be collected together into sets to be used for different
purposes.
Information controlling units is held in a UNIT element of the Catalogue Database. The
UNITS hierarchy is shown below:
WORLD
MSET USEC
MTYP UDEF
ATLI
• MTYP - Measurement Type. This element forms the link between a collection of
attributes and the Units Definition (UDEF) to be used for them. The attributes are
accessed via the ATLI (Attribute List) elements owned by the MTYP and the Units
Definition via its UREF attribute. The latter simply contains the name of the UDEF
element which is to be used for the attributes named in the member ATLI elements.
• ATLI - Attribute List. Each ATLI element contains (as its ATNA attribute) the
name of the attribute for which the UREF (see above) applies.
• UDEF - Units Definition. One UDEF is required for each non-PDMS unit that you
wish to implement. UDEF has the following special attributes:
• SIGF and DECP - Significant Figures and Decimal Places. These relate to the
output of units.
To summarise, the unit is defined as:
(input_value * MULT ) + ADEN
and is output to SIG significant figures with DEC decimal places and suffixed by the
notation ABREV ( e.g. ‘psi’).
UREF /INCH set the Reference Units that the MTYP refers to
NEW ATLI create an Attribute List for the MTYP
ATNA ACBO set the Attribute Name that is required to be
output/input in inches
If ACBO is referred to in PROPCON, the attribute name (ATNA) is searched for in the
UNIT hierarchy. The search then moves up the hierarchy to find the MTYP attribute
UREF. The MULT attribute of the UDEF (found from the UREF) is then applied to the
stored ACBO attribute and the ABREV is output with the resulting value.
As a further example, to define and use a unit system called /IMPERIAL, for which
temperatures (TEMP, PTEM and RTEM) will be in Fahrenheit and pressures (PRES,
RPRE and IPRE) will be in PSI, the instruction sequence would be:
For users who required bores, bolt diameters and lengths, and rod diameters that are
not included in the standard nominal values stored in core, a facility exists for the
creation of tables that hold the required values in the catalogue database.
When being switched from module to module, the catalogue database is scanned for a
NBRWLD element with the PURP attribute set to BORE indicating that user-defined
nominal bores etc are to be used. If so, the nominal bore-checking routine is switched to
the user-defined nominal bores.
Bores
For most users, the requirement is adding or removing a few bores. For this purpose, a
macro of standard PDMS bores is provided (nominal_bore.mac), which enables a user to
edit the values concerned and then input the User-defined Nominal Bore table into the
catalogue.
Bolts
When there is a need to use a bolting catalogue with both Imperial and Metric projects,
there is not always a direct conversion from one system to the other. For example, a ½
inch bolt may convert to a 12mm rather than a 13mm one.
To overcome the problem, User-defined Nominal Bolting tables for diameter and length
can be set up, as for the User-defined Nominal Bore table. The PURP attribute is set to
BDIA for bolt diameters and BLEN for bolt lengths.
Rods
When rods for hangers and supports are specified, the rod diameter is related to the
bore diameter. It is, therefore, necessary to have User-defined Nominal Rod Diameter
tables, if User-defined Nominal bores are being used.
If a hanger connects to a branch with different bores, the rod diameter is selected to
match the branch with the User-defined Nominal bore or, if this applies to neither
branch, the standard piping bore. The PURP attribute is set to ROD.
Database
The following addition is made to the catalogue database:
World element NBRWLD, with:
Attribute PURP.
Owns:
NOMINB elements, with:
Real attribute INCBOR Inch Nominal Value
Real attribute MMBOR MM Nominal Value.
A Dataset (DTSE) is a collection of DATA elements. These can be used to store any
items of catalogue data which need to be queried directly from within the DESIGN or
DRAFT modules and which are not accessible by other means.
The PPRO attribute can also be set to a parameterised expression which will be used in
the definition of Pointsets and Geomsets. See Section 11.3.
Consider the following examples, which allow you to query two properties of this
parameterised I-beam in DESIGN:
P3
P4 P1
P2
The command Q PROP DEPT in DESIGN or DRAFT will return the depth of the
current beam (or the default of 600 if the true value cannot be evaluated).
Example 2: The cross-sectional area of the beam
Datakey: XSEC
Dtitle: ’Cross–section of beam’
Pproperty: (((P [1] - (2 * P[3])) * P[4]) + (2 * (P[2] * P[3]))
NOTE: PARAM has been shortened to P here to show the format of the
expression more clearly. The full version must be used when setting
the attribute.
Purpose: DATA
Number: not relevant here, so leave unset
The command Q PROP XSEC in DESIGN or DRAFT will return the calculated cross-
sectional area of the current beam.
Similarly, you could query the following attributes of this DATA element:
Q PRTI XSEC Data title
10.3.2 Querying
The value of RPROP can be queried using the command:
Q RPROP datakey
This command will return the result ‘RPROP unset’ if the corresponding PPRO attribute
contains a text string rather than a real value.
The default value of a text or real property value may be queried from a Design
component using the command:
Q PRDE datakey
A list of the datakeys available at a Design item can be obtained using the command:
Q PRLS
To avoid having to transfer component design or specification errors from the Catalogue
database to the Design database before data inconsistencies can be detected, a facility is
provided for checking the main settings of a piping catalogue as you build it in
PARAGON. (This facility is not yet available for checking a structural catalogue.)
The basic command to initiate a database consistency check, using default settings, is
CHECK <gid>
where <gid>, the element below which checks are to be carried out, may be any SPEC,
SELE, SPCO or COMP.
If you start the check from within a specification (SPEC, SELE or SPCO) all components
referenced via the starting element will be checked. If you start the check at component
level (COMP), only that component and elements below it will be checked.
(See Section 13.3 for details of the ways in which you can modify the default checking
procedures.)
At SPCO level:
• Check that all of the following reference attributes are set: CATREF, DETAIL,
MATX, CMPR, BLTREF. (The BLTREF need be set only if the connection type
begins with F or L.)
You can modify the effect of the CHECK command by using additional syntax so that
you can check different types of catalogue without generating unnecessary errors.
The command options are as follows:
TOLerance CATAlogue CMPRef ON/OFF
switches Component Reference checking on or off for all component types in a SPCO.
TOLerance CATAlogue CMPRef word ON/OFF
switches Component Reference checking on or off for the specified component type in a
SPCO.
TOLerance CATAlogue GMREf ON/OFF
switches Geomset Reference checking on or off for all component types.
TOLerance CATAlogue GMREf word ON/OFF
switches Geomset Reference checking on or off for the specified component type.
TOLerance CATAlogue BORE ON/OFF
switches bore checking on or off for Pointsets.
TOLerance CATAlogue BORE value value
sets range of permissible bores to be checked for Pointsets.
TOLerance CATAlogue ISOMetric ON/OFF
checks for SKEY and similar ISODRAFT–related settings.
TOLerance CATAlogue DEFault
resets all checking options to their default settings.
To query any of the current data consistency checking settings, use the corresponding
command format
Q TOLerance CATAlogue ...
Error messages which can result from diagnosed data inconsistencies are as follows:
C10 Spec error: Question word asked more than once
C20 Spec error: Question TYPE never asked
C30 Spco error: DETA not set
C40 Spco error: Unknown ref for DETA
C50 Spco error: MATX not set
C60 Spco error: Unknown ref for MATX
C70 Spco error: CMPR not set
C80 Spco error: Unknown ref for CMPR
C90 Spco error: BLTR not set
C100 Spco error: Unknown ref for BLTR
C110 Spco error: CATR not set
C120 Spco error: Unknown ref for CATR
C130 Comp error: PTRE not set
C140 Comp error: Unknown ref for PTRE
C150 Comp error: GMRE not set
C160 Comp error: Unknown ref for GMRE
C170 Ptset error: Duplicate ppoint number integer
C180 Ptset error: No ppoints set
C190 Ptset error: Unknown connection type word for ppoint
C200 Comp error: GTYPE word different from spec TYPE
word
C210 Ptset error: Non standard bore value for ppoint
You must use the following conventions for numbering the P-points of Piping
Components so that ISODRAFT can recognise them:
• For tube components, there must only be one P-point, P1, which defines the bore
and connection type of both ends of the piece of tube.
• For nozzles, the connection P-point (i.e. the P-point for connection to the head or tail
branch) must be P1.
• For two-way components, the arrive and leave P-points must be numbered P1 and
P2 (in either order). For two-way valves, the spindle direction must be indicated by
P3.
• For three-way components, the offline leg must be indicated by P3. The spindle
direction for three-way valves must be specified by using a P-point greater than
P3, which must have its bore unset.
• For four-way components, the two straight-through flows must have P-points
P1/P2 and P3/P4. The spindle direction for four-way valves must be specified by
using a P-point greater than P4, which must have its bore unset.
• For eccentric reducers without a connection point, the flat side must be
indicated by P3. Eccentric reducers with a connection point must use P3, with
a valid bore set, to indicate the connection point and must use P9, with bore unset,
for orientation of the flat side.
P4 P3 P5
P1 P2
It is important that certain items in the Catalogue database are named as they are
referenced from other databases as well as internally. It would be impracticable to allow
system-generated database reference numbers to be referenced as this would lead to
meaningless output from reports and isometrics.
Figure B-1 shows the relationship between the Design, Specification, and Catalogue
databases. Consistency when naming items is important, making cross-database
connections as easily identifiable as possible.
In ISODRAFT, bolt lengths for Piping Components are derived by referring to the SBOL
name. Item detail is picked up from the RTEX attribute of the DTEX and the material is
picked up from the XTEX attribute of the MTEX.
Note that the item code name on an isometric is obtained from the second part of the
SPREF attribute of a Component, i.e. its name in the Specification. In the example in
Figure B-1, the name would be output as FLANWN300100. See the ISODRAFT
Reference Manual for further details.
The list below is not exhaustive and only shows example codes - it is not mandatory.
Item and/or Connection Type Code
300lb Raised-Face Flange FGD
300lb Gasket GGD
Pipe Bevelled End TUB
Butt Weld BWD
Socket Weld SWF
300lb Wafer Fitting WGD
Screwed Male SCM
Screwed Female SCF
The table in the previous section can be used to construct a PDMS Connection
Compatibility Table (CCTA) which sets out all the permissible connection pairs.
If an attempt is made to connect two pipework components in DESIGN, then a check is
made to see if the p-leave PCON attribute of the first component and the p-arrive PCON
attribute of the second component appear as a matching pair in the connection table. If
there is such a matching pair then the components are connected, otherwise a similar
check is made on the p-leave PCON attributes of each component. If a matching pair is
now found, the second component is ‘flipped’ and connected to the first. If no matching
pair is found then an ‘incompatible connection type’ error message is output and
the second component is left in its original position and orientation.
The following sample connection table uses the connection list given in the previous
section:
NEW CCTAB
NEW COCO /FGDGGD
CTYPE FGD GGD
NEW COCO /TUBBWD
CTYPE TUB BWD
NEW COCO /GGDWGD
CTYPE GGD WGD
NEW COCO /TUBSWF
CTYPE TUB SWF
NEW COCO /SCMSWF
CTYPE SCM SWF
NEW COCO /SCFTUB
CTYPE SCF TUB
The COCO (Connection Compatibility) elements are named so that the allowable
connections are easily queried.
The above table 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, e.g. flat
face and raised face: however, there are some exceptions. On some jobs a flat-faced
flange on a piece of equipment may be butted up to a raised-face flange. If this is a
common occurrence, it may be worth inputting a new COCO to allow the connection.
This Appendix gives sample macros for the construction of typical Catalogue Piping
Components using PARAGON.
Each macro starts at CATEGORY level. The view parameters used to produce the
drawings shown vary between each example, and so are not given here. Each drawing
has REPRESENTATION settings of TUBE ON CENTRELINE ON PPOINTS ON
NUMBERS ON. Some of the Components are too large to fit onto a typical view area
when drawn at the default SCALE value of 1. Values of 0.5 are suggested for examples 1
and 3, and 0.05 for example 6.
The definition for each Component includes the possibility of insulation being present,
although this is not drawn. Note how the clash geometry and component geometry have
been combined.
NEW PTAX
PCON (PARAM[7]) NUMB 2 PBOR (PARAM[1]) PAXI Y
PDIS (PARAM[4] + PARAM[5])
/MWWNFLAN
GOTO GMRE
NEW SCYL
CLFL TRUE TUFL TRUE PDIS 0 PHEI (PARAM[4])
PDIA (PARAM[3] + IPARAM[1]) PAXI Y
NEW LINE
OBST 0 CLFL TRUE P1 P2
NEW SSPH
OBST 0 CLFL TRUE PDIS 0 PAXI P2 PDIA (PARAM[9])
NEW LSNO
TUFL TRUE PTDI (PARAM[5] + PARAM[4])
PBDI (PARAM[4]) PBDM (PARAM[6] + IPARAM[1])
PTDM (PARAM[2] + IPARAM[1]) PAAX Y PBAX X POFF 0
END
$.
GOTO GMRE
NEW LINE
OBST 0 CLFL TRUE P1 P2
NEW SSPH OBST 0 CLFL TRUE PDIS 0 PAXI P1 PDIA (PARAM[8])
NEW SSPH OBST 0 CLFL TRUE PDIS 0 PAXI P2 PDIA (0.65 * PARAM[9])
NEW LSNO
TUFL TRUE PTDI (PARAM[5])
PBDI 0 PTDM (PARAM[4] + IPARAM[1])
PBDM (PARAM[3] + IPARAM[1])
PAAX Y PBAX -Z POFF (PARAM[6])
END
$.
NEW LSNO
OBST 0 CLFL TRUE PTDI (PARAM[5]) PBDI 0.00 PTDM (PARAM[4] +
IPARAM[1])
PBDM (PARAM[4] + IPARAM[1]) PAAX P1 PBAX Z TVIS FALSE
NEW LSNO COPY PREV PAAX P2
NEW SCYL OBST 0
TUFL TRUE PHEI (PARAM[5])
PDIA (PARAM[4] + IPARAM[1]) PAXI P1
NEW SCYL COPY PREV PAXI P2
END
$.
PAXI -Y
NEW PTAX
PCON (PARAM[8]) NUMB 2 PBOR (PARAM[1]) PDIS (PARAM[2])
PAXI X
NEW PTCA
NUMB 3 PX (-PARAM[6]) PY (PARAM[5]) PZ 0
PTCDIR -X 24 -Y
NEW PTCA
NUMB 4 PX (-PARAM[7]) PY (PARAM[7]) PZ 0
PTCDIR -X 45 -Y
NEW PTCA
NUMB 5 PX (-PARAM[5]) PY (PARAM[6]) PZ 0
PTCDIR -Y 24 -X
/MWLOBST-51
GOTO GMRE
NEW SRTO
PAAX P1 PBAX P2
PDIA (-1.2 * PARAM[4])
PHEI (PARAM[3])
NEW SSLC OBST 0
CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-PARAM[3]) PDIS 0
PAXI P1 PXTS -11.5
NEW SSLC OBST 0
CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-PARAM[3]) PDIS 0
PAXI P2 PXTS 11.5
NEW SSLC OBST 0
CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-2 * PARAM[3])
PDIS (PARAM[3]) PAXI P3 PXTS -11.5 PXBS 11.5
NEW SSLC COPY PREV PAXI P4
NEW SSLC COPY PREV PAXI P5
END
$.
PARAGON Syntax:
NEW PTSE /PBOXI2
NEW PTAX
PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 0 PAXI -Y
END OF END
NEW GMSE /GBOXI2
NEW BOXI
PAXI P1 PXLE (PARAM[3]) PZLE (PARAM[2]) CLFL TRUE TUFL TRUE
END OF END
NEW PTSE /PELBO
NEW PTAX
PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 250
PAXI -Y
END
NEW PTAX
PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 250
PAXI X
END OF END
NEW GMSE /GELBO
NEW SRTO
CLFL TRUE TUFL TRUE PAAX P1 PBAX P2 PDIA (PARAM[2])
PHEI (PARAM[3])
END OF END
NEW PTSE /PVELBO
NEW PTAX
PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 250
PAXI -Y
END
NEW PTAX
HEADING
TYPE NAME PBOR0 STYP CATREF DETAIL MATXT CMPRE
BLTREF
ELBO */HB300X100 300100.0 H /HELBO101 =0 =0 =0
=0
ELBO */VB300X100 300100.0 V /VELBO101 =0 =0 =0
=0
HEADING
TYPE NAME PBOR0 CATREF DETAIL MATXT CMPREF
BLTREF
WELD */W300X100 300100.0 /BWELD101 =0 =0 =0
=0
$.
DESIGN Syntax:
NEW PIPE
SPEC BOXI.SPEC
NEW BRAN /BOXIBRAN
HPOS E0 HBOR 300100 HDIR N HCON BWD
TPOS E2500 N7000 U1000 TDIR S TBOR 300100 TCON BWD
NEW WELD SEL CONN TO PH AND P0 IS U
SPRE /BOXI.SPEC/W300X100 LSTU /BOXI.SPEC/D300X100 ORIF TRUE POSF
TRUE
NEW ELBO SEL WI STYP V
THRO N5000 DIR U
NEW ELBO SEL WI STYP H
THRO U1000 DIR E
NEW ELBO SEL WI STYP V
THRO PT DIR N
NEW WELD SEL CONN TO PT AND P0 IS E
END
Note that it is assumed that a COCO element allowing BWD to BWD connections
already exists in your database.
This appendix contains a glossary of the element types which you can use in PARAGON,
and a list of them grouped according to their function. Some element types can be
created and deleted in PARAGON, and have their standard attributes of NAME and
LOCK changed, but must have their particular attributes set by other PDMS modules.
These are indicated by references to the appropriate manuals.
The list of element types is the list of ‘special nouns’ for PARAGON (its <snoun> syntax
diagram).
D.1 Glossary
3D Pointset elements:
PTSEt PTAXi PTCAr PTMIx
3D Geomset elements:
GMSEt SBOX SDISc SDISk SCONe
LSNOut SDSH BOXIng SSLCylinder SSPHere
LCYLinder SCYLinder LINEs SCTOrus SRTOrus
TUBE LPYRamid SEXTrusion SREVolution SLOOp
SVERtex
Dataset elements:
DTSEt DATA
Piping Components:
SCOMponent COMPonent number
Profile Components:
SPRFile PROFile number
Joint Components:
SJOInt JOINt number
Fitting Components:
SFITting (NOT FITTing number)
Units elements:
UNIT MSET MTYP ATLIst USECtion
UDEFinition