catalogues and specifications reference manualcatalogues and specifications reference manual

Catalogues and Specifications

Reference Manual

DisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaimany and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct described in this publication may be incorporated into any third-party software, product,machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective license agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthoriseduse of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solutions Ltd

Catalogues and Specifications Reference Manual

Contents Page


Reference ManualIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1How this Manual is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Command Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Standard Command Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Entering PARAGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Saving Work and Updating Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Exit PARAGON without Saving Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Saving the Alpha Readout to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Switching Text Output Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Defining Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4

Catalogue Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1What is the Catalogue For?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Principal Features of the Catalogue Database . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

12.0i


Structure of the Catalogue Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Catalogue (CATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA) . . 4:4Elements Used in Both Types of Catalogue Section/Category . . . . . . . . . . . . . . . . . . . . . . 4:5Elements Used in Piping Sections/Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5Elements Used in Structural Sections/Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5

Text (TEXT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6Component Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6Insulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7Structural Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7Design DB Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8

Catalogue Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9Piping Component (COMP; SCOM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10Profile (PROF; SPRF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11Joint (JOIN; SJOI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11Fitting (FITT; SFIT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12

Component Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12

Selection Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14

Manipulating the Catalogue Database using PARAGON . . . . . . . . 5:1Basic Element Operation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Creation, Deletion etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Implicit Element Referencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2List Position Changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Standard Attribute Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2

Creating Catalogues, Sections and Catalogue Components. . . . . . . . . . . . . . . 5:3Using Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Expressions Using Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5

Examples of Parameterisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6Constructing 3D Pointsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9PTAXI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9PTCAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10

12.0ii


PTMIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11Example of Defining a 3D Pointset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12Defining an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12Defining a Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13Defining an Explicit Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13Defining a Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:14Defining Connection, Bore and Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:14Controlling the Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:14Specifying Pipe End Conditions for use by ISODRAFT . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:14

Constructing Structural Pointsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15Example of Defining a Structural Pointset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15The Neutral Axis Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16Defining an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16Defining a Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17Defining a Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17Controlling the Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17

Constructing 3D Geomsets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17Constructing Structural Geomsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20Reference Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:21Parameter-Controlled Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:21Axial Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22

Component Design and Representation in PARAGON . . . . . . . . . . 6:1Component Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1P-point and P-line Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2P-points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4

Geomset Primitive Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Reference Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11Model Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11Setting Representation for Piping Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14Setting Profile Representation for Steelwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:15Setting Level Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:16Setting Obstruction and Insulation Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:17Setting P-Point Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:18Setting P-Line Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:19Full REPRESENTATION Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:20

Catalogue Database Elements Setup in PARAGON . . . . . . . . . . . . 7:1

12.0iii


3D Pointsets (PTSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Axial P-point (PTAXI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2Cartesian P-point (PTCAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3Mixed Type P-point (PTMIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3Position Type P-point (PTPOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3

Structural Pointsets (PTSSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:33D Geomsets (GMSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:53D Geomset Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6Box (SBOX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6Boxing (BOXI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Cone (SCON). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7Cylinder (LCYL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8Cylinder (SCYL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9Slope-Bottomed Cylinder (SSLC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9Disc (SDIS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:10Dish (SDSH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Line (LINE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Line (SLINE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11Pyramid (LPYR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12Circular Torus (SCTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12Rectangular Torus (SRTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:13Snout (LSNO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:13Sphere (SSPH). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14Tube (TUBE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14User-defined Extrusion (SEXT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15Solid of Revolution (SREV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15

Negative 3D Geomsets (NGMSET) and Negative Primitives . . . . . . . . . . . . . . 7:16Structural Geomsets (GMSSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18Structural Geomset Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18Structural Rectangle (SREC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:18Structural Annulus (SANN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:19Structural Profile (SPRO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:20

Detailing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:21Material Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:22Connection Compatibility Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:22COCDES Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23

Bolting Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23

12.0iv


Branch Reducer and Nominal Bore Size Tables . . . . . . . . . . . . . . . . . . . . . . . . 7:24Unit Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:25Use of Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26

General Text Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:28User-defined Nominal Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:28

Creating Datasets in PARAGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Attributes of DATA Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Querying Properties in DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2Real Properties of P-points, P-Lines and Geomsets . . . . . . . . . . . . . . . . . . . . . 8:3Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

Checking Catalogue Database Consistency using PARAGON . . . 9:1Initiating a Standard Data Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1What the Checking Facility Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Controlling the Detailed Checking Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3

Piping Components in PARAGON. . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Special Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Implied Tube. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Mitred Bends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2How Number of Cuts (NCUTS) Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3Dynamic PPOINTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:4Implied Geometry sets in PARAGON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:4

Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:4Example Connection Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:5Connection Compatibility Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:6Construction of Typical Piping Components . . . . . . . . . . . . . . . . . . . . . . . . . . 10:7

Specification Constructor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1Content and Format of a Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2How Component Selection Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:4

Manipulating the Catalogue Database using SPECONMODE. . . . 12:1

12.0v


Creating a Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1Accessing an Existing Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:2Entering Tabular Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:3General Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:3Special Characters in SPEC Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:3Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:4Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:5Selector Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:5Subtype Selectors: A Special Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6Including User-defined Attributes in Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6Including Comments in Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6

Editing an Existing Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:7Adding a New SPCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:7Deleting or Removing a SPEC or SPCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:7

Copying a Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:8Outputting a Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9Defining the Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9Outputting Complete Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9Controlling the Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9Outputting Parts of Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9How Bores Are Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:10

Using Macros For SPECON Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:10

Typical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1Selectors and Pointers for Piping Components . . . . . . . . . . . . . . . . . . . . . . . . 13:1Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2P-Point Zero: A Special Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3Reference Pointers and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3Examples From Piping Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:5

Selectors and Pointers for Structural Components . . . . . . . . . . . . . . . . . . . . . 13:6Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:6Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:6Reference Pointers and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:9Examples From Structural Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:9

Selectors and Pointers for Insulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:10Pipework Insulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:10Structural Insulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:12

12.0vi


SPECONMODE Command Syntax Diagrams . . . . . . . . . . . . . . . . . 14:1Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1<speca> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1<table> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:2<heading> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:2<default> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:3<linesp> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:3<id> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:3<copy> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:3

Other PDMS Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:4

SPECONMODE Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:1

Nominal Pipe Size Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1

Properties Constructor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1Setting Up a Properties Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Design Layout Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Material Property Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Case Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Component Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Constraint Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2Run Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2

Material Property Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:3Hierarchy Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:3Material Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:3Pointers from the Design DB and Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:4

Case Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:4Hierarchy Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:4Pointer from the Design DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:5

Component Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:5Hierarchy Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:5Querying Calculated Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:7Pointer from the Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:7

Constraints Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:7Hierarchy Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:7Pointer from the Design DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:8

Run Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:8

12.0vii


Hierarchy Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:8

Use of Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18:1

Exponential Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19:1

PROPCON Command Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . 20:1Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20:1

12.0viii

Catalogues and Specifications Reference ManualIntroduction

1 Introduction

1.1 About this ManualThis document is a Reference Manual for the Catalogues and Specifications. It describesall of the PARAGON, SPECON and PROPCON keyboard-entered commands in detail. Ifyou need information on how to use the Graphical User Interfaces refer to the Catalogueand Specifications User Guide.

It is assumed that you have attended a training course and are familiar with the basicconcepts underlying the use of AVEVA products.

1.2 How this Manual is OrganisedThis manual is divided into chapters, as follows:

Document Conventions describes notation and conventions used whenentering commands.

Common Commands describes how to enter, leave and change the states ofPARAGON.

Catalogue Database Structure gives details of the Catalogue database hierarchy andthe ways in which its constituent elements are defined.

Manipulating the Catalogue Database using PARAGON

explains the procedure for defining the various types ofelement which represent the design components withinthe Catalogue database.

Component Design and Representation in PARAGON

introduces the principles of catalogue componentdesign and their representation in graphical displays.

Catalogue Database Elements Setup in PARAGON

details elements used for the creation of point set,geometry sets, descriptive texts, coco tables, boltingtables and unit of measurements.

Creating Datasets in PARAGON explains the concept of datasets, used to storecatalogue data which needs to be queried fromDESIGN or DRAFT and which is not accessible byother means.

Checking Catalogue Database Consistency using PARAGON

describes how to check the catalogue database forinconsistencies from within PARAGON, so that errorscan be corrected before the data is used in a design.

Piping Components in PARAGON summarises some p-point conventions which should befollowed to enter correct functioning of ISODRAFT.

12.01:1

Catalogues and Specifications Reference ManualIntroduction

1.3 Intended AudienceIn most companies the responsibility for creating Catalogues and Specifications is restrictedto a team of Standards Engineers within the Production Engineering Department or itsequivalent. You might, therefore, be a member of such a team setting up or updating aSpecification. Alternatively, you might be a pipework or structural designer who needs to usea Specification to select a suitable component and who wishes to understand the principlesunderlying the selection process.

1.4 AssumptionsYou are assumed to be familiar with the general principles of using PDMS, although some ofthe most relevant points are repeated in this manual as a reminder.

Specification Constructor introduces the principles of specifications.

Manipulating the Catalogue Database using SPECONMODE

describes SPECONMODE within PARAGON.

Typical Specifications describes typical specifications.

SPECONMODE Command Syntax Diagrams

lists SPECONMODE command syntax diagrams.

SPECONMODE Error Messages a list of common SPECONMODE error messages.

Nominal Pipe Size Tables a list of Nominal Pipe Size Tables.

Properties Constructor introduces the principles of PROPCON.

Use of Groups describes the use of groups in PROPCON.

Exponential Numbers describes Exponential Numbers in PROPCON.

PROPCON Command Syntax Diagrams

a list of PROPCON command syntax diagrams.

12.01:2

Catalogues and Specifications Reference ManualDocument Conventions

2 Document Conventions

This section describes the conventions used in this manual to describe commands to betyped in from the keyboard. The description of each command follows a standard formatwhich is designed to allow the basic attributes of a command to be interpreted easily. To getthe best out of this manual, you are strongly urged to read this section thoroughly.

2.1 Command Description FormatYou will find that commands are described in a standard format. This format is describedbelow.

• Title (e.g. Setting Level Representation)• Keywords This is a list of those PARAGON, SPECON or PROPCON command words

which are the prime constituents of the command syntax which carries out the givenfunction.

• Description This is a brief description of the use of the command.• 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 conditionsare given here.

• Command Syntax This shows the actual command with its possible options. Thenotation used for commands is described below (Syntax Diagrams).

• Querying The relevant querying options are listed.

2.2 Syntax DiagramsThe commands described in this manual have their legal command and interrogationoptions presented in the form of syntax diagrams. These diagrams formalise the precisecommand sequences which may be used and are intended to supplement the explanationsgiven in the appropriate sections of the manual.

The following conventions apply to syntax diagrams:• All diagrams have abbreviated names. Such names are composed of lowercase letters

enclosed in angled brackets, e.g. <expres>. These short names, which are used forcross-referencing purposes in the text and within other syntax diagrams, aresupplemented by fuller descriptions where they are not self-explanatory.

• Commands to be input from the Command Line are shown in a combination ofuppercase and lowercase letters. In general, these commands can be abbreviated; thecapital letters indicate the minimum permissible abbreviation.

Note: This convention does not mean that the second part of the command must be typedin lowercase letters; commands may be entered in any combination of uppercaseand lowercase letters.

12.02:1


For example, the command

DEFault

may be input in any of the following forms:

DEFDEFADEFAUDEFAULDEFAULT

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

means you may type in ABC or PQR or any command allowed by the syntax given indiagram <dia> or just press Enter/Return to get the default option.

• Points marked with an asterisk (*) are loop-back junctions. Command optionsfollowing these may be repeated as required. Thus

permits any combination of option1 and/or option2 and/or option3 (each separated byat least one space) to be used. The ‘options’ may define commands, other syntaxdiagrams, or command arguments). The loop-back construction may form anexception to the rule of reading from top left to bottom right.The simplified format

means that you may type in a list of PDMS names, separated by at least one space.

>---+--- ABC -----.| ||--- PQR -----|| ||--- <dia> ---|| |‘-------------+--->

.------<------./ |

>---*--- option1 ---|| ||--- option2 ---|| |‘--- option3 ---+--->

.----<-----./ |

>---*--- name --+--->

12.02:2


2.3 Standard Command ToolsCommand Tool is a generic term covering command arguments (or atoms) and commandparts. Both classes of command tool fit into ordinary commands and provide different waysof stating a particular requirement. Command tools may be PDMS-wide or module-specific.This section describes the standard Command Tools that may be used in PARAGON,SPECON or PROPCON. They may be one of the following:

• Standard Command Tools - which fit into ordinary commands• 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, SPECON or PROPCON

Some of the main command tools (or the PARAGON, SPECON or PROPCON variations ofthem) summarised for convenience:

Command ArgumentsCommand arguments are also called atoms because they cannot be broken down anyfurther. They are individual units which PARAGON, SPECON or PROPCON can recogniseas constituents of a complete command. They usually need to be separated by spaces sothat they are individually distinguishable. Command arguments are distinguished from theother command parts by being written in lower case italics. The principal commandarguments are:

Note: There must be a space before and after each of these command arguments.

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

letter a single alphabetic character

word a sequence of up to four letters with significance to PDMS

text a string of alphanumeric or symbol characters, which may include spaces,enclosed between single closing quotation marks ’...’ or |...| characters.This is normally used to add descriptive material to an appropriateattribute. For example, DUTY ’Low Pressure’. (Note that paired quotationmarks ‘...’ will not work.)

space the space bar (not usually specified unless of special significance)

name a sequence of characters preceded by a / character and representing aPDMS Element name, e.g. /VALVE1.

filename an external file name of the format /filename

varid an identifier (for use with the VARIABLE command within macros) of theformat !name, where ‘name’ is a text string. For example: !COUNTER!height

comma the , character, which can be used to concatenate PARAGON, SPECON orPROPCON commands; for example: NEW UNIT, BUNI INCH, DUNI FINC

plus minus the +, -, * and / characters, which can be used within

star solid expressions, for example: (1 + 2), (1 - 2), (1 * 2), (1 / 2)

12.02:3


Command PartsCommand parts are subsets of the general command syntax which are used frequentlywithin other command sequences. The following command parts are summarised here:

Expressions

Any mathematical, logical or alphabetical expression whose result replaces it in thecommand 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. Thecommand 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 canenter an expression from which the required result is to be evaluated by PARAGON,SPECON or PROPCON as it executes the command. Such an expression must beenclosed between parentheses (...) to identify where it begins and ends.

Full details of the expression syntax are given in the Plant Design Software CustomisationGuide and Plant Design Software Customisation Reference Manual, and are also availableas on-line help.

Dimensions (<uval>)Once the working units have been specified, all dimensions input subsequently will beassumed to be in those units unless you override them. (Note that these are simply specificexamples of the use of ‘real’ expressions. You can include explicit units of measurementwhen entering a value in any expression.)

12.02:4


Examples

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, SPECON or PROPCON, values are stored as accurately as thehost computer will allow.

Catalogue Element Types (<snoun>)This command part refers to an element type in the Catalogue hierarchy.

Catalogue administrative elements:

Piping Components:

Profile Components:

Joint Components:

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)

WORLd CATAlogue SECTion STSEction

CATEgory STCAtegory TEXT

SCOMponent COMPonent number

SPRFile PROFile number

SJOInt JOINt number

12.02:5


Fitting Components:

Note: FITTing number is not a valid option)

3D Geomset elements:

Negative 3D Geomset elements:

Structural Geomset elements:

3D Pointset elements:

Structural Pointset elements:

Dataset elements:

Detailing Text elements:

SFITting

GMSEt SBOX SDIsc SDIsk

SCOne LSNout SDSH BOXIng

SSLCylinder SSPHere LCYLinder SCYLinder

LINes SCTorus SREVolution SRTorus

TUBe LPYRamid SEXTrusion SLOOp

SVERtex

NGMSet NSBOx NSCOne NLSNout

NSDSh NSSLcylinder NSSPhere NLCYlinder

NSCYlinder NSCTorus NSREvolution NSRTorus

NLPYramid NSEXtrusion SLOOp SVERtex

GMSSet SRECtangle SANNulus SPROfile

SPVErtex

PTSEt PTAXi PTCAr PTMIx

PTSSet PLINe

DTSEt DATA

SDTExt DTEXt number

12.02:6


Material Text elements:

Bolt Table elements:

Connection Table elements:

Units elements:

Group World elements:

Part World elements:

Specification World elements:

Table World elements:

Specific Element Identifier (<gid>)This command part identifies a specific element either explicitly or by reference to its relativeposition in the database hierarchy.

SMTExt MTEXt number

BLTAble BLISt SBOLt LTABle

MBOLt MBLIst DTABle

CCTAble COCO COCDES

UNIT MSET MTYPe ATLIst

USECtion UDEFinition

GPWL GROUp

PRTWLD PRTELE GPART

SPWL SPECi SELEc SPCOm

BRTAB NOMTAB TABWLD

12.02:7


Examples

Cursor-picking Identifier (<sgid>)

This command part defines the most general method of identifying an Element. Thecommand is completed by picking an element using the cursor in a graphical view.

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

ID @ Lowest level element hit by cursor

ID SBOX @ Box primitive hit by cursor

ID SCOM @ Piping Component hit by cursor

12.02:8

Catalogues and Specifications Reference ManualCommon Commands

3 Common Commands

The commands in this section are available throughout PDMS.

3.1 Entering PARAGONThe commands for PARAGON and PROPCON are combined within the PARAGON moduleso that you do not need to switch between modules. SPECON commands are also availablein PARAGON by using the SPECONMODE command.

To enter SPECON commands type SPECONMODE.

To exit SPECONMODE type EXIT.

3.2 Saving Work and Updating Databases

Keyword: PARAGON or SPECONMODE

Description: This command is available throughout PDMS, allowing PARAGON orSPECON to be accessed at any time.

Keyword: SAVEWORK GETWORK

Description: These two commands are complementary. SAVEWORK lets you updatethe databases to incorporate any changes you have made during yourcurrent PARAGON session (since your last SAVEWORK). GETWORKlets you refresh your view of all READ or Multiwrite databases to pick upany changes that others may have made since you first opened them.

Both commands can be restricted to specific databases within the currentMDB by following them with a list of numbers. These numbers representspecific databases in the order they appear in the output of the STATUScommand, which may be given in MONITOR or in the MDB mode of anyGUI module. If no database numbers are given, then the commandsapply to the whole MDB.

It is good practice to use SAVEWORK frequently, to ensure maximumdata security. However, it should only be necessary to use GETWORKwhen there are specific changes that you wish to pick up (in which case itis likely that you will know which databases you will actually want torefresh). GETWORK slows subsequent database access because theinformation has to be re-read from disk, and should be avoided unlessyou really need to use it.

12.03:1


3.3 Exit PARAGON without Saving Changes

Examples:

Command Syntax:>-- QUIT --+-- modulename --.

| ||-- FINish ------|| |‘----------------+-->

3.4 Saving the Alpha Readout to File

Note: After an ALPHA file has been opened, subsequent output will be directed to both thefile and the screen until the file is closed, or until you change to another PDMSmodule.

Keyword: QUIT FINISH

Description: This command exits from PARAGON without saving any changes or thedisplay setup. QUIT has the effect of deleting any changes made sincethe last SAVEWORK, module change or MDB change.

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)

Keywords: ALPHA LOG ALPHA FILE

Description: This facility lets you save the alpha display information to a text file in thecomputer operating system. Two types of output are available, dependingon the command used.

ALPHA LOG enables the contents of either or both of the COMMANDSand REQUESTS alpha regions to be written to a file.

ALPHA FILE enables the contents of the REQUESTS region only to bewritten to file.

The ALPHA LOG/ ALPHA FILE facilities may be used to save data or as ageneral output facility.

12.03:2


Examples:

Command Syntax:>-- ALPha --+-- LOG --+-- name --+-- OVERwrite --.

| | | || | |-- APPend -----|| | | || | ‘---------------+-- COMMands --.| ‘-- END --> | || |-- REQuests --|| | || ‘--------------+->|‘-- FILE --+-- name --+-- OVERwrite --.

| | || |-- APPend -----|| | || ‘---------------+-->

‘-- END -->

3.5 Switching Text Output Off

Examples:

Command Syntax:>-- TRAce --+-- ON ---.

| |‘-- OFF --+-->

ALP LOG /LF1 COMMANDS - log information displayed in the COMMANDS region infile /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

Keywords: TRACE

Description: This command, applicable in TTY mode only, controls the automaticoutput of the Current Element name and attributes. With Trace set to ON,the attributes display is automatically updated for each elementaccessed. With Trace set to OFF, the attribute display is not changed.When macros are being run, TRACE is always set to OFF automatically.

TRACE OFF - Stops the automatic output of attribute data.

TRACE ON - Restarts automatic output of Current Element name and attributes.

12.03:3


3.6 Defining Colours

Definitions:• The Active colour is used for the catalogue component being worked on (the

significant element, e.g. ELBO, VALV). If the current element is a geometric primitive,the active colour is used for all primitives owned by the significant element except thecurrent primitive.

• The CE colour is used for the element currently being accessed (i.e. the elementhighlighted 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 theactive 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:

Keywords: COLOUR ACTIVE CE VISIBLE AIDS

Description: These commands allow colours to be defined so that the status ofdifferent types of item in the display may be distinguished by means ofcolour. The colours used have default settings, but these may beredefined.

The colours may be assigned by using the COLOUR command to definethe Red-Green-Blue mix for a colour number or to assign a predefinedcolour mix by name. PARAGON allows the use of 100 user-definablecolours, plus some specific ones which are assigned to items which needto be readily distinguishable in the display.

Colour Red Green Blue

black 0 0 0

white 100 100 100

whitesmoke 96 96 96

ivory 93 93 88

grey 66 66 66

lightgrey 75 75 75

darkgrey 32 55 55

darkslate 18 31 31

red 80 0 0

brightred 100 0 0

coralred 80 36 27

tomato 100 39 28

plum 55 40 55

deeppink 93 7 54

pink 80 57 62

salmon 98 50 44

12.03:4


orange 93 60 0

brightorange 100 65 0

orangered 100 50 0

maroon 56 14 42

yellow 80 80 0

gold 93 79 20

lightyellow 93 93 82

lightgold 93 91 67

yellowgreen 60 80 20

springgreen 0 100 50

green 0 80 0

forestgreen 14 56 14

darkgreen 18 31 18

cyan 0 93 93

turquoise 0 75 80

aquamarine 46 93 78

blue 0 0 80

royalblue 28 46 100

navyblue 0 0 50

powderblue 69 88 90

midnight 18 18 31

steelblue 28 51 71

indigo 20 0 40

mauve 40 0 60

violet 93 51 93

magenta 87 0 87

beige 96 96 86

wheat 96 87 70

tan 86 58 44

sandybrown 96 65 37

brown 80 17 17

khaki 62 62 37

chocolate 93 46 13

darkbrown 55 27 8

Colour Red Green Blue

12.03:5


The default colour assignments are:

Examples:

Note: When colours are mixed in their Red, Green and Blue constituents, the commandline must contain values for all three constituents in the correct order. The numbersentered 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 upto 100.

Colour No Colour

Current element yellow

Visible elements lightgrey

1 grey

2 red

3 orange

4 yellow

5 green

6 cyan

7 blue

8 violet

9 brown

10 white

11 pink

12 mauve

13 turquoise

14 indigo

15 black

16 magenta

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, greenand blue

COL VISIBLE BRIGHTRED Sets the colour for displaying components to brightred

12.03:6


Command Syntax:>-- COLour -+- integer -.

| ||- ACTIVE --|| ||- CE ------|| |‘- VISIble -+- colour_name -->

|‘- MIX RED integer GREen integer BLUe integer -->

where colour_name is the name of any of the predefined colour mixes listed above.

Querying:>-- Q COLour --+-- integer -----.

| ||-- ACTIVE ------|| ||-- CE ----------|| |‘-- VISIble -----+-->

12.03:7


12.03:8

Catalogues and Specifications Reference ManualCatalogue Database Structure

4 Catalogue Database Structure

This chapter details the structure of the PDMS Catalogue database.

Note: Words of four or five uppercase characters which appear in this chapter (forexample, CATA, BLTA, SPREF) are PDMS element names. When an element’smember list is queried in PDMS, each element type will be displayed as a four-character name. Five or six characters are occasionally used in this chapter wherethis gives a ‘PDMS’ name which is closer to the element’s ‘English’ name, forexample SPREF (instead of SPRE) for Specification Reference.

4.1 What is the Catalogue For?The Catalogue in PDMS serves a purpose similar to a parts catalogue to which a pipeworkdesigner or structure designer would refer when using ‘conventional’ design methods. Itcontains details of all available components (piping and structural), including theirdimensions, geometry and drawing symbols. Whereas the conventional parts catalogue is abook held in the DESIGN Office, the PDMS Catalogue is a database held on the computer.

4.2 Principal Features of the Catalogue DatabaseIf a new Catalogue database (DB) is required, PARAGON can be used to construct it - seeManipulating the Catalogue Database using PARAGON for details of creating andmanipulating a Catalogue DB using PARAGON.

The Catalogue data is held according to a strict hierarchy which is similar in form to that ofthe Design data.

When a Component is selected by the designer using DESIGN, a Specification Reference(SPREF) is identified and held in the DESIGN database. The SPREF points to aSpecification Component (SPCOM) in the Specification. This in turn points to a CatalogueComponent (SCOM, SPRF, SJOI, SFIT, etc.) in the Catalogue (see Figure 4:1.:Interrelationship between Design Data, Catalogue and Specifications).

Whereas the Design data is specific to a particular DESIGN, Catalogues and Specificationsmay be specific to a company but general to a number of projects in that company. Forexample, the same Catalogue Component may be referred to many times in a particulardesign and may also appear in other design projects proceeding at the same time.

Catalogues are usually built up as a library of catalogue macros. A selection of thesemacros can then be used to build up a project-specific Catalogue database containing onlythose Components which might be used on that project.

12.04:1


Figure 4:1. Interrelationship between Design Data, Catalogue and Specifications

4.3 Structure of the Catalogue DatabaseCatalogues are constructed as a hierarchy of elements. Each element has certainattributes and some may contain further member elements. The complete Cataloguehierarchy is shown in Figure 4:2.: The Catalogue Database Hierarchy.

Note that in any discussion of attributes which may appear in the rest of this chapter, the‘standard’ attributes of TYPE, NAME, OWNER and LOCK will not be mentioned, as theseare common to all the elements described below.

In addition, User Defined Attributes (UDAs) and User Defined Element Types (UDETs) maybe used with Catalogue database elements - see the LEXICON Reference Manual fordetails.

12.04:2


Figure 4:2. The Catalogue Database Hierarchy

4.4 Catalogue (CATA)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 beused; e.g. PIPE, FITT.

• CSTA - the Catalogue standard.

12.04:3


A CATA can contain a number of Catalogue Sections. These are of two types: PipingSections (SECT) and Structural Sections (STSEC). They are the principal administrativeelements by which the Catalogue is divided and arranged. The Catalogue can also containText elements (TEXT) - see General Text Elements.

All elements referred to in a Specification (see Specification Constructor) must exist withina CATA hierarchy, although elements may exist within a CATA which are not referred to by aSpecification.

Note that the following elements may also exist within the Catalogue database at the samelevel 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 Catalogue Database ElementsSetup in PARAGON, the latter element type being described in more detail in theISODRAFT Reference Manual. Specification World elements are detailed in SpecificationConstructor.

4.5 Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA)Sections and Categories are administrative elements which let you segregate particulartypes of catalogue data into logical parts of the hierarchy. Sections, which subdivide anoverall CATA, are obligatory; Categories, which subdivide Sections, are optional (althoughtheir use is recommended).

There are two types of Catalogue Section: Piping Sections (SECT) and StructuralSections (STSEC). Both have the following attributes:

• DESC - a textual description of the section. • 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 StructuralCategory (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 isto 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).• PTRE - a reference to a 3D P-point Set (PTSE). • GMRE - a reference to a 3D Geometry Set (GMSE). • DTRE - a reference to a Data Set (DTSE).

12.04:4


• CDET - a reference to Detailing Text (DTEX).

Both types of Catalogue Section or Category contain the elements 3D P-point Set, 3DGeometry Set, Data Set, Detailing Text and Material Text, as described in Elements Usedin Both Types of Catalogue Section/Category. Piping Sections/Categories may also containPiping Components, as described in Elements Used in Piping Sections/Categories.Structural Sections/Categories may also contain Structural Components (Profiles, Jointsand Fittings), Structural Pointsets, Negative 3D Geometry Sets and StructuralGeometry Sets, as described in Elements Used in Structural Sections/Categories.

4.5.1 Elements Used in Both Types of Catalogue Section/CategoryThe following elements may be used in either type of Catalogue Section or Category:

• 3D P-point Set (PTSET) (usually abbreviated to 3D Pointset) - a definition of theposition, direction, connection type and bore of a Component’s P-points, to be used byDESIGN, ISODRAFT, etc.

• 3D Geometry Set (GMSET) (usually abbreviated to 3D Geomset) - a grouping of 3Dprimitive elements, defining the dimensions, orientation and obstruction geometry ofeach primitive. Used by DESIGN and the Drawing modules.

• Data Set (DTSET) (usually abbreviated to Dataset) - a grouping of DATA elements,holding any catalogue data not stored more specifically elsewhere and which isrequired for use in DESIGN or DRAFT; e.g. the cross-sectional area of a structuralsteel member calculated from its parameterised dimensions.

• Detailing Text (DTEX) - elements containing general descriptive text relating to aComponent. Referred to from SPCOM elements in the Specification. For further detailssee Detailing Text.

• Material Text (MTEX) - elements containing text describing the material(s) from whichthe physical Component is constructed. Referred to from SPCOM elements in theSpecification. For further details see Material Text.

4.5.2 Elements Used in Piping Sections/CategoriesA Piping Section or Category may contain all those elements listed in Elements Used inBoth Types of Catalogue Section/Category plus the following:

• Piping Component (COMP) - an element defining a piece of pipework. It consists of alist of values (known as component parameters) and references to a 3D Pointsetelement and a 3D Geomset element. The Pointset and Geomset make use of thecomponent parameter values in defining the size, geometry and connection types ofthe Piping Component.

4.5.3 Elements Used in Structural Sections/CategoriesA Structural Section or Category may contain all those elements listed in Elements Used inBoth Types of Catalogue Section/Category plus the following:

• Structural Pointset (PTSSET) - a definition of the position and direction of aComponent’s P-lines, to be used by DESIGN.

• Negative 3D Geometry Set (NGMSET) (usually abbreviated to Negative 3DGeomset) - a grouping of 3D negative primitive elements (representing holes, endpreparations etc.), defining the dimensions, orientation and obstruction geometry ofeach primitive. Used by DESIGN and the Drawing modules.

12.04:5


• Structural Geometry Set (GMSSET) (usually abbreviated to Structural Geomset) - agrouping of 2D primitive elements, defining the dimensions, orientation and obstructiongeometry of each primitive. Used by DESIGN and the Drawing modules.

• Profile (PROF) - a 2D structural Component defining the cross-section of a beam,column etc. (a Section). It consists of a list of component parameters and references toa Structural Pointset element and a Structural Geomset element. The Pointset andGeomset make use of the component parameter values in defining the size andgeometry of the Component. In the design process, a length is associated with a Profileto produce a Section.

• Joint (JOIN) - a 3D structural Component defining a physical means of attaching oneSection to another. It consists of a list of component parameters and references to aStructural Pointset element, a 3D Pointset element and a 3D Geomset element. Thetwo Pointsets and the Geomset make use of the component parameter values indefining the size and geometry of the Component.

• Fitting (FITT) - a 3D structural Component defining an object which is physicallyattached to a Section but is not part of the structure formed by Sections and Joints. Forexample, a Fitting may be used to attach a pipe hanger to a Section. The elementconsists of a list of component parameters and references to a 3D Pointset elementand a 3D Geomset element. The Pointset and Geomset make use of the componentparameter values in defining the size and geometry of the Component.

The Catalogue structure as described so far may be used in various ways, but therecommended method of use is to place only one type of element in each CatalogueSection, and to place different kinds of Components in different Catalogue Categories. Forexample, you might place all 3D Pointsets for Piping Components in one Piping Section andall 3D Geomsets for Piping Components in another, with separate Piping Sections for equaltees and reducing tees. When defining Profiles, you might place Profiles for UniversalBeams in one Structural Section, Profiles for Unequal Angles in another, and so on.

4.6 Text (TEXT)The Text is a general element that can occupy many positions in the hierarchy. It can beused to store additional information about an owning or adjacent element. The TEXTelement should not be confused with the MTEX and DTEX elements described in ElementsUsed in Both Types of Catalogue Section/Category. See General Text Elements for furtherdetails.

4.7 ParametersParameters define the size, geometry and other characteristics of Components. They areused in setting the attributes of the Pointsets, Geomsets and Datasets to which Componentelements refer.

All classes of Component can use component parameters, design parameters andinsulation parameters. Structural Components can also use attached and owning designparameters. Component parameters are defined in the Catalogue; the other classes ofparameters allow characteristics to be set during the design process.

4.7.1 Component ParametersPiping Components (COMP), Profiles (PROF), Joints (JOIN) and Fittings (FITT) all have aPARAM attribute which lists the component parameters.

12.04:6


Creating Catalogues, Sections and Catalogue Components describes how to set up thecomponent parameters of a Component. You may define default values which PARAGONwill use if you are working with a Component whose component parameters have not beenset up. The values are set using the MODEL SETTINGS command. For example,

MODEL SETTINGS PARAM 1 10

defines a default value of 10 for component parameter number 1. See Model Settings forthe full syntax of how to set default values.

These default values are set up only for the current PARAGON session. They are not storedin the Catalogue DB. You must define the component parameters of a Component beforeyou use it in the DESIGN DB.

4.7.2 Insulation ParametersA design element in the DESIGN DB refers to a main Catalogue Component (indirectly) viaits Specification Reference (SPREF) attribute. The design element may also refer to asecond Catalogue Component which defines the insulation of the first Component, via itsInsulation Specification (ISPEC) attribute. The second Component is the InsulationComponent of the design element.

Insulation parameters (IPARAM) allow the main Component to take dimensions from theInsulation Component. When the main Component uses IPARAM 3, for example, it picks upthe value of the PARAM 3 of the corresponding Insulation Component.

When you define a Catalogue Component using insulation parameters, its dimensions arenot completely specified in the Catalogue. So that PARAGON can give some idea of whatthe Component will look like when used in a design, you can define specimen values for theinsulation parameters. These specimen values apply to all Components, unlike thecomponent parameters which are attributes of a particular Component. The values are setusing the MODEL SETTINGS command. For example,

MODEL SETTINGS IPARAM 3 25

defines a specimen value for insulation parameter number 3. See Setting Obstruction andInsulation Representation for the full syntax of how to set values for insulation parameters.The values are not stored in the Catalogue DB; they are set up only for the currentPARAGON session.

4.7.3 Structural ParametersThese allow Joint and Fitting Components to take dimensions from the Section or Sections(beam, column, etc.) to which they are physically connected. In this way, a basic design ofJoint or Fitting may be adjusted automatically in the Design DB to fit a connected Section ofany size. (Structural parameters are meaningless for Profiles.)

Structural parameters are of four types:• Attached parameters (APARAM)• Owning parameters (OPARAM)• Design attached parameters (DES APARAM)• Design owning parameters (DES OPARAM).

The types of structural parameter that a Component can use depends on whether it is aPiping Component, Profile, Joint or Fitting. In the case of a Joint, it also depends on how theComponent is used in the Design DB.

12.04:7


Joints are of two types: primary and secondary. A primary Joint has an attached Section inthe Design DB; a secondary Joint has an attached Section and an owning Section. (Seethe DESIGN Reference Manual for details of primary and secondary Joints.) Note thatprimary 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 aredifferent.

A Fitting Component has an owning Section in the Design DB.

Components which have an attached Section (i.e. primary and secondary Joints) can useattached parameters to define the attributes of their Pointsets and Geomsets. Attachedparameters 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 theJoint’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. Forexample, when a Joint or Fitting component uses OPARAM 5, it picks up the value of thePARAM 5 of the component’s owning Section.

You can define specimen values for structural parameters in the same way as for insulationparameters. For example,

MODEL SETTINGS APARAM 2 300

defines a specimen value of 300 for attached parameter number 2. See Section 5.9? forthe full syntax of how to set values for structural parameters.

4.7.4 Design DB ParametersThese allow structural Components to take dimensions from Design Parameter Arrays inthe Design DB. Each design element has a Design Parameter Array with ten values. (Seethe DESIGN Reference Manual for further details.)

Design DB parameters are of three types:• Design parameters (DES PARAM) • Design attached parameters (DES APARAM, structural items only)• Design owning parameters (DES OPARAM, structural items only)

Design parameters allow any component with an SPREF to use values from the designelement which refers to it (via the SPREF). For example, the DES PARAM 4 of aComponent is the fourth value in the Design Parameter Array of the design element. Designparameters can be used anywhere that component parameters can be used.

Design attached parameters and design owning parameters allow a Joint or FittingComponent to use values from the design elements which represent its attached andowning Sections. (Attached and owning sections are explained in Structural Parameters.)For example, the DES OPARAM 1 of a Component is the first value in the DesignParameter Array of the design element of its owning Section. Design attached parameterscan be used anywhere that attached parameters can be used. Similarly, design owningparameters in place of owning parameters.

You can define specimen values for Design DB parameters in the same way as forinsulation parameters. For example,

MODEL SETTINGS DES PARAM 7 9.5

12.04:8


defines a specimen value of 9.5 for design parameter number 7. See Model Settings for thefull syntax of how to set values for Design DB parameters.

Figure 4:3.: Table of Parameters and Components summarises how the various types ofparameters may be used with the different classes of Component.

Figure 4:3. Table of Parameters and Components

4.8 Catalogue ComponentsThere are four classes of Catalogue Component:

• Piping Component• Profile• Joint• Fitting

Their attributes are described in the following sections. These attributes (other than thecomponent parameters) must be set to actual values (words or references to otherelements). 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 structuralitems may also be defined using design owning parameters and design attachedparameters.

A component parameter may be a numeric value, an expression or a word. (The full syntaxfor expressions is defined in the Plant Design Software Customisation Guide.) An insulationparameter, a structural parameter or a Design DB parameter may only be a numeric valueor an expression. The values assigned to parameters and the use to which they are put, andthe number of parameters used, are arbitrary, depending only on the skill and experience ofthe user. Manipulating the Catalogue Database using PARAGON contains examples of theparameterisation of typical Components.

Catalogue Components do not have member elements.

PipingComp't

Profile Prim'yJoint

Sec'yJoint

Fitting

Catalogue Component Parameters

Insulation Parameters

Attached Parameters (Structural)

Owning Parameters (Structural)

Design Parameters (Design DB)

Design Attached Parameters

Design Owning Parameters

b b b b b

b b b b b

b b

b b

b b b b b

b b

b b

Parameter:

Applicable to:

(PARAM)

(IPARAM)

(APARAM)

(OPARAM)

(DES PARAM)

(DES APARAM)

(DES OPARAM)

(COMP) (PROF) (PJOI) (SJOI) (FITT)

12.04:9


4.8.1 Piping Component (COMP; SCOM)The attributes of a Piping Component are:

• PTREF - reference to a 3D Pointset element. • GMREF - reference to a 3D Geomset element.• 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 - gasketHELE - hanger elementINST - 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 tubeUNIO - union VALV - valve VENT - open-ended pipe or vent VFWA - four-way valve VTWA - three-way valve WELD - weld

12.04:10


The GTYPE must be set as one of the above, otherwise a data consistency check on aBranch containing the Component (see the DESIGN Reference Manual) will not workcorrectly.

• DTREF - reference to a Dataset element.

4.8.2 Profile (PROF; SPRF)The attributes of a Profile are:

• PSTREF - reference to a Structural Pointset element. • GSTREF - reference to a Structural Geomset element.• 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:


4.8.3 Joint (JOIN; SJOI)The attributes of a Joint are:

• PSTREF - reference to a Structural Pointset element. • PTREF - reference to a 3D Pointset element. • GMREF - reference to a 3D Geomset element.• PARAM - the component parameters, a list of values used in the Structural Pointset,

3D Pointset and 3D Geomset to define the Component.• GTYPE - a word attribute indicating the generic type of the Joint. Any word value may

be used. The following are suggested:

• CTYA - a word attribute indicating how the Joint is fixed to the attached Section (theJoint’s connection type for the attached Section). Any word value may be used. If the

BEAM - beam

BRAC - brace

COLU - column

GANT - gantry

GIRD - girder

JOIS - joist

PILE - pile

PROF - profile

PURL - purlin

RIDG - ridge

SDRA - side rail

BASE - base

JOIN - joint

KNEE - knee

12.04:11


connection type attribute of the attached Section (CTYS or CTYE) has not been setwhen the Joint is selected in the design process, the attribute will automatically be setto the value of CTYA. The PDMS data consistency checks (see the DESIGN ReferenceManual) check whether the connection type attributes of the Joint and attached Sectionmatch.

• CTYO - similar to CTYA, but for the Joint’s owning Section (secondary Joints only).• DTREF - reference to a Dataset element.

4.8.4 Fitting (FITT; SFIT)The attributes of a Fitting are:

• PTREF - reference to a 3D Pointset element. • GMREF - reference to a 3D Geomset element.• PARAM - the component parameters, a list of values used in the Structural Pointset,

3D Pointset and 3D Geomset to define the Component.• 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 pipehanger (HCON or TCON) has not been set when the Fitting is selected in the designprocess, the attribute will automatically be set to the value of CTYA. The PDMS dataconsistency checks (see the DESIGN Reference Manual) check whether theconnection type attributes of the Fitting and pipe hanger match.


Note: For details of the MODEL SETTINGS command syntax used to set default valuesfor component parameters, and specimen values for other classes of parameter, seeModel Settings.

4.9 Component PartsThe GPART element allows catalogue components to be fully defined in one place andwithout the need for specifications, and these can be used by all disciplines.

The GPART element has the same standard attributes as a SPCO, including CATREF,DETREF, MATXT, CMPREF and BLTREF, along with other attributes specific to the Part. Itis also possible to add any number of user defined properties to each individual Part.

Parts can be added to the Selection Tables for selecting Parts in the design module, andthese can be used for all disciplines except piping.

For the piping discipline it is possible to add Parts to Piping Specifications in the same wayas SPCO’s.

It is possible to select Parts in the design model directly from the catalogue, using filteredsearches.

4.9.1 HierarchyParts are defined under a new Part World hierarchy:

12.04:12


The PRTELE’s can be used to define a hierarchy with any number of levels, allowing flexiblegrouping of Parts in the database.

4.10 Selection TablesSelection Tables are used for selecting Component Parts in the design model. They providethe following methods of selection:

1. Selection Criteria can be used to offer you a choice of Parts based on the currentdesign context (e.g. captain or crew cabin, inside or outside hull, etc.)

2. Attributes Filters can be used to allow you to search the selection table for Parts withmatching attributes.

3. A combination of 1 and 2 can be used.

Note: It will also be possible to use attribute filters to select Parts directly from thecatalogue without using selection tables at all, however the use of selection tables isrecommended where only a subset of the whole Part catalogue should be used on aparticular project.

12.04:13


4.10.1 HierarchySelection tables will be stored under a new hierarchy as shown below:

1. The Table Group will contain Selection Tables that are related in some way (at leastone table group for each discipline).

2. The Selection Table will contain one Table Header and numerous Table Items.3. The Table Header defines the selection questions for that table.4. The Table Items have a reference to the corresponding Part, and hold the selection

answers for that Part.

12.04:14

Catalogues and Specifications Reference ManualManipulating the Catalogue Database using PARAGON

5 Manipulating the Catalogue Database using PARAGON

PARAGON has a Graphical User Interface consisting of forms and menus. The interfaceprovides access to the most commonly used facilities. To enter direct command syntax, usethe Display>Command Line menu option to open a special window which acceptscommand inputs and displays system outputs.

This section describes PARAGON keyboard-entered commands in detail. If you needinformation on how to use PARAGON to carry out the principal Catalogue design activitieswith minimal use of the keyboard, by using the Graphical User Interface, refer to theCatalogues and Specifications User Guide.

5.1 Basic Element Operation Commands

5.1.1 Querying

5.1.2 Creation, Deletion etc

QUERY e.g. QUERY ATTRIBUTES

NEW e.g. NEW SECTION

DELETE e.g. DELETE SREC

REORDER e.g. REORDER 5 BEFORE 3

COPY e.g. COPY /VALVES2-1

RENAME e.g. RENAME /UEANGLE80 /UEANGLE100

INCLUDE e.g. INCLUDE SCOM 6 OF /FLAN300 BEFORE 2

12.05:1


5.1.3 Implicit Element Referencing

5.1.4 List Position Changing

5.1.5 Standard Attribute Setting

These commands are those which are common to all ‘constructor’ modules of PDMS andsome are used in this chapter without further explanation. However, the element typeswhich the above commands operate on relate to the Catalogue database rather than theDesign database (so, for example, NEXT SITE is meaningless in PARAGON).

OLD

END

SAME

CE

OWNER

GOTO e.g. GOTO PTREF

FIRST (Can be just command word by itself or followed by element

LAST type, for example FIRST LCYL)

NEXT

PREVIOUS number list position number, e.g. ‘5’

NAME

UNNAME

LOCK

UNLOCK

12.05:2


5.2 Creating Catalogues, Sections and Catalogue ComponentsCatalogues and Sections are created using the NEW command. You would normally alsospecify 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 /FLANGESNEW STSEC /PROFILES

will create a Piping Section with the name /FLANGES and a Structural Section with thename /PROFILES. Similarly,

NEW CATEG /ANSI-B16.5-CLASS-300-BLIND-FLANGESNEW 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 Catalogue Components).

NEW SCOM

will create a Piping Component with unspecified component parameters, the values ofwhich 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 Catalogue Components) are set simply by followingthe attribute with the word, name or value(s) to be assigned to it. For example:

NEW SCOMGTYPE ELBOPTREF /PSE1GMREF /GSE1PARAM 20 19.1 12.7 37.1 BWD

The above commands create a Piping Component, of generic type ELBO, which is definedby 3D Pointset /PSE1 and 3D Geomset /GSE1, and which has the five componentparameters shown. The Pointset and Geomset which are referred to by name must alreadyexist; they would have been created by the commands

NEW PTSET /PSE1NEW GMSET /GSE1

All five component parameters have been given values using a single command line, butthey can be given values individually by using commands such as

PARAM[1] 20PARAM{2] 19...etc.

Note: You can only use the PARAM[number] syntax to change the value of a parameterwhich has already been set.

12.05:3


This facility allows component parameter definitions to be ‘edited’. (Caution: If you delete aCOMP 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 ofparameter 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 therest.

You may define default values which PARAGON will use if you are working with aComponent whose component parameters have not been set up. See Parameters fordetails.

The attributes of a Component may be queried by a

QUERY ATTRIBUTES

command, or may be queried individually by name. Component parameters can be queriedas a set by using the command

QUERY PARAMETERS

or singly by using commands such as

QUERY PARAMETER[1]QUERY PARAMETER[2]etc.

5.3 Using Parameters

5.3.1 IntroductionPiping Components, Profiles and Fittings each use one type of Pointset and one type ofGeomset. Joints use both types of Pointset and one type of Geomset. The attributes ofPointsets and Geomsets may be defined in terms of parameters, set either explicitly or asreal expressions (which may themselves incorporate the current settings of otherparameters). (The classes of parameter which may be used depend on the class ofComponent - see Parameters 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 firstcomponent parameter.

The Y dimension of a box in a 3D Geomset used by a Joint could be defined as theexpression

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 thebox is the value of the second component parameter of the attached Profile plus 3 mm.

12.05:4


The use of parameters makes it possible to use the same Pointsets and Geomsets for largenumbers of catalogue items. For example, there may be families of tees, valves, I-beamprofiles etc., each family containing items which are geometrically similar. In this way, theCatalogue 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 ofparameters 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 (GTYPEattribute set to TUBE) and which has no Geomset. In this case, component parameter 2must be the outside diameter. If the tube is to be insulated, insulation parameter 1 must betwice the thickness of the insulation.

Note: on the use of Insulation Parameters: Insulation parameters may be used in twoways. They may be used in an additive manner to increase the diameter or length ofa primitive or, if there is a significant change in the geometry from the uninsulated tothe insulated form, they may be used to define a new primitive. Where there is noinsulation, the insulation parameters will be zero, yielding a primitive of zero diameter(but probably non-zero length).

5.3.2 Expressions Using ParametersAny expression which includes parameters and which evaluates to a real result may be builtinto definitions of Pointsets and Geomsets. For example:

PDIA (4.5 * PARA[2]) PDIS (-PARA[2]) PBOR (PARA[7] + IPARA[1]) PHEI (PARA[2] + 50) PDIS (APARA[2] - PARA[7]) PDIA (-(PARA[1] - PARA[5])) PX (2 * OPARA[3])PTDIS (PARA[2] * DESP[5])PHEI (PARA[4] / ODESP[1])PZ (5 * (ADESP[3] * PARA[9])PDIS (3.1 * (PARA[1] + HEIG)) PHEI (PARA[1] * TAN (ANGL / 2))

(For the full range of expression syntax available, see the DESIGN Software CustomisationGuide.)

12.05:5


5.4 Examples of ParameterisationExample 1 A Slip-On Flange

Figure 5:1. Example of Parameterisation for a Slip-On Flange

A slip-on flange can be parameterised using five component parameters, as shown inFigure 5:1.: Example of Parameterisation for a Slip-On Flange.

• PARAM 1 - PBORE• PARAM 2 - Outside Diameter• PARAM 3 - Thickness• PARAM 4 - Connection Type at P1• PARAM 5 - Connection Type at P2

12.05:6


Example 2 A Reducing Tee

Figure 5:2. Example of Parameterisation for a Reducing Tee

A reducing tee might be parameterised using 12 component parameters, as shown in Figure5:2.: Example of Parameterisation for a Reducing Tee.

• PARAM 1 - Nominal bore of main run (PBOR1)• PARAM 2 - Outside diameter of main run• PARAM 3 - Nominal bore of branch (PBOR3)• PARAM 4 - Outside diameter of branch• PARAM 5 - Half overall length of main run• PARAM 6 - Standout length of branch run• PARAM 7 - Connection type of main run• PARAM 8 - Connection type of branch run• PARAM 9 - Flange diameter of main run• PARAM 10 - Flange thickness of main run• PARAM 11 - Flange diameter of branch run• PARAM 12 - Flange thickness of branch run

Other families of tees could be defined as follows:• Equal and reducing welded tees using parameters 1-8• Equal and reducing flanged tees using all the parameters

12.05:7


Example 3 A Universal Beam Profile

Figure 5:3. Example of Parameterisation for a Universal Beam Profile

A Universal Beam Profile might be parameterised using four component parameters, asshown in Figure 5:3.: Example of Parameterisation for a Universal Beam Profile.

• PARAM 1 - Overall height of Profile• PARAM 2 - Flange width• PARAM 3 - Web thickness• PARAM 4 - Flange thickness

12.05:8


Example 4 An Angle Joint

Figure 5:4. Example of Parameterisation for an Angle Joint

An Angle Joint might be parameterised using three component parameters and twoattached parameters, as shown in Figure 5:4.: Example of Parameterisation for an AngleJoint.

• PARAM 1 - Overall height of angle leg• PARAM 2 - Overall length of angle foot• PARAM 3 - Thickness of leg and foot• APARA 1 - Height of profile of attached Section• APARA 2 - Width of flange of attached Section

5.5 Constructing 3D PointsetsA 3D Pointset defines the connection information of a Piping Component, Joint or Fitting asexplained in Component Design. For the three types of P-point elements which may becontained in a 3D Pointset, you must define the following attributes:

5.5.1 PTAXI• A P-point number (NUMB)• An axis direction (PAXI) (parallel to X, Y, Z or in the XY, YZ or ZX plane)• A distance along the specified axis (PDIS)

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 Defining a Direction)

12.05:9


PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.

Figure 5:5. Example of three Axial P-Points

5.5.2 PTCAR• A P-point number (NUMB)• An axis direction (PTCDIR) (in any plane)• An explicit position (PX, PY, PZ) (explicit coordinates)

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 Defining a Direction)


12.05:10


Figure 5:6. Example of two Cartesian P-Points

5.5.3 PTMIX• A P-point number (NUMB)• An axis direction (PAXI) (parallel to X, Y, Z or in the XY, YZ or ZX plane)• An explicit position (PX, PY, PZ) (explicit coordinates)

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 Defining a Direction)


Figure 5:7. Example of two Mixed P-Points

12.05:11


5.5.4 Example of Defining a 3D PointsetA suitable 3D Pointset for the reducing tee shown in Figure 5:2.: Example ofParameterisation for a Reducing Tee would be created as follows:

Notice how all the P-point attributes may be defined on one line. The last P-point (P3) couldalternatively be defined as a Cartesian P-point:

Further examples of the construction of typical 3D Pointsets are given in Appendix C.Reference information concerning the setting up of the P-point attributes is given in thefollowing subsections.

5.5.5 Defining an AxisThe PAXI attribute of a P-point can be defined in one of two ways:

• by a direction letter, e.g. PAXI Z• by an angle in the XY plane (see below). You can specify the angle as

• a number• DDANGLE• a parameter• TWICE a parameter

The classes of parameter which you can use depend on the class of the Component whichuses the P-point - see Parameters for details.

If you do not define the axis, PAXI Y is assumed.

NEW PTSET /RTPTSE Create new 3D Pointset

NEW PTAX Create axial P-point element

NUMBER 1 P1

PAXI -Y Direction of P1 along negative Y axis

PDIS (PARA[5]) Distance along axis from P0 = half overall length

PCON (PARA[7]) Connection type at P1

PBOR (PARA[1]) Nominal bore at P1

NEW PTAX

NUM 2 PAXI Y PDIS (PARA[5]) PCON (PARA[7]) PBOR (PARA[1])

NEW PTAX

NUM 3 PAXI X PDIS (PARA[6]) PCON (PARA[8]) PBOR (PARA[3])

NEW PTCAR

NUM 3 PCON (PARA[8]) PBOR (PARA[3])

PX (PARA[6]) PY 0 PZ 0

PTCDIR X

12.05:12


Figure 5:8. P-point Axis Definition

5.5.6 Defining a DistanceDistance in a PTAXI element is defined by the PDISTANCE keyword (minimum abbreviationPDIS) followed by a value or a parameter function. For example:

If you do not define the distance, a value of zero is assumed.

For the reducing tee shown in Figure 5:2.: Example of Parameterisation for a Reducing Tee,the position of P-point 3 could be defined by the commands:

PAXI XPDIS (PARAM[2])

since PARAM 2 is the dimension called ‘height’.

5.5.7 Defining an Explicit PositionPosition in a PTCAR element and a PTMIX element is defined by the PX, PY and PZkeywords, each followed by a value or a parameter function. For example:

If you do not define a coordinate, a value of zero is assumed.

PDIS 100 sets P-point position to 100 units along defined axis

PDIS (PARAM[1] sets P-point position to (value of first component parameter)units along defined axis

PX 100 sets P-point X coordinate to 100

PY (0.5 * APARA[3]) sets Y coordinate to (0.5 times value of third attachedparameter) units

PZ (PARA[2] * SIN (ANGLE / 2)) sets Z coordinate to (second component parametertimes sine of half design angle) units

12.05:13


5.5.8 Defining a DirectionDirection in a PTCAR element is defined by the PTCDIRECTION keyword (minimumabbreviation PTCDIR), followed by the direction specified in terms of the X, Y, Z axes androtations towards those axes. For example:

For other examples, see Figure 5:6.: Example of two Cartesian P-Points. Note that any one,any two, or all three of X, Y, Z may be present in the PTCDIR command line, in any order.The rotation value may be positive, negative or absent altogether (i.e. zero). If you do notdefine the direction, DIR Y is assumed.

5.5.9 Defining Connection, Bore and NumberThese three attributes are common to all three types of P-point elements, and are set by thePBORE, PCONNECTION and NUMBER (minimum abbreviations PBOR, PCON, NUM)commands respectively. PBOR and PCON may be set as parameter functions as well aswords. Examples:

PBORE (0.5 * PARAM[2])PCONN BWDPCONN (PARAM[7])NUMBER 3

If you do not define the bore or the P-point number, a value of zero is assumed.

5.5.10 Controlling the Appearance How a P-point is drawn depends on the REPRESENTATION settings. This is discussed inP-point and P-line Representation.

5.5.11 Specifying Pipe End Conditions for use by ISODRAFTThe symbol used by ISODRAFT to represent a particular piping component on an isometricdrawing is determined by the symbol key (SKEY attribute setting) for that component. (Seethe ISODRAFT Reference Manual for a full explanation of this concept.)

By default, each SKEY has associated with it a standard end condition (showing the pipeconnection type) which applies to each of the component’s connection points. The endcondition for any individual connection point may be modified, if required, by setting thePSKEY attribute of the corresponding P-point to a PDMS word chosen from the following:

PTCDIR X45Y direction is along the X axis, rotated 45 degrees towardsthe Y axis

PTCDIR X(ANGL / 2)Y45U includes an expression for the Y component

BW Butt Weld

CP Compression

FL Flange

SC Screwed

SW Socket Weld

PL Plain

12.05:14


The effect of setting PSKEY to one of these words for a P-point of type PTAXI, PTCAR orPTMIX is that ISODRAFT will then add the symbolic representation of the specified endcondition to the symbol derived from the corresponding SKEY when it plots an isometricdrawing showing the component. The default setting for PSKEY is always NULL, whichmeans that ISODRAFT plots only the standard end conditions for the symbol.

Note that the effect is additive, so that ISODRAFT superimposes any user-specified endcondition (derived from a non-Null PSKEY setting) on top of any end condition which formspart of the standard symbol associated with the SKEY. The use of the PSKEY facility is,therefore, applicable mainly to components which do not have other end conditions alreadydefined, particularly those associated with user-defined symbols (as detailed in theISODRAFT Reference Manual).

5.6 Constructing Structural PointsetsA Structural Pointset defines the connection information of a Profile or Joint as explained inStructural Pointsets (PTSSET). A Structural Pointset has a neutral axis reference attributein addition to the standard attributes, and contains P-lines.

5.6.1 Example of Defining a Structural PointsetA suitable Structural Pointset for the Profile shown in Figure 5:3.: Example ofParameterisation for a Universal Beam Profile would be created as follows:

Notice how all the P-line attributes may be defined on one line. Reference informationconcerning the setting up of the P-line attributes is given in Defining an Axis to Controllingthe Appearance.

NEW PTSSET /UBPTSE Create new Structural Pointset

NEW PLIN /UB-TOS Create P-line element for top of steel

PKEY TOS Define key

PLAXI Y Direction of P-line along positive Y axis

PY (0.5 * PARA[1]) Distance in Y direction from component origin = half overallheight. (There is no need to set PX, because it is zero.)

CLFLA TRUE Display P-line in centreline representation

TUFLA FALSE but not in tube representation

NEW PLIN /UB-BOS Create new P-line element for bottom of steel

PKEY BOS PLAXI -Y PY (-0.5 * PARA[1]) CLFLA TRUE TUFLA FALSE

NEW PLIN /UB-NA - Create new P-line element for neutral axis

PKEY NAXI PLAXI Y CLFLA TRUE TUFLA FALSE

END Make the Structural Pointset the current element

NAREF /UB-NA Define neutral axis reference

12.05:15


5.6.2 The Neutral Axis ReferenceThe neutral axis reference identifies a P-line in the Structural Pointset. It is set by theNAREF command. The attribute is usually set to the name of the P-line, but may be set tothe P-line’s number in the member list of the Pointset. For example:

If you do not set NAREF, DESIGN will make an assumption about where the neutral axis is.You are strongly recommended to set the neutral axis reference in the Catalogue.

DESIGN will use as the neutral axis the first P-line in the Structural Pointset which has aPKEY value of NA, if any. Failing that, it will choose the first P-line with a PKEY value ofNAXI, and failing that, it will choose the first P-line with a PKEY value of ZAXI. If there are noP-lines with a PKEY value of NA or NAXI or ZAXI, DESIGN will assume that the neutral axisof the Component lies at the component origin and has a direction along the positive Y axis.

Figure 5:9. P-line Axis Definition

5.6.3 Defining an AxisThe PLAXI attribute of a P-line can be defined in one of two ways:

• by a direction letter, e.g. PLAXI Y• by an angle in the XY plane (see below). You can specify the angle as

• a numbe• DDANGLE• a parameter• TWICE a parameterThe classes of parameter which you can use depend on the class of the Componentwhich uses the P point - see Parameters for details.

If you do not define the axis, PLAXI Y is assumed.

NAREF /UB-NA Sets neutral axis reference to the P-line called /UB-NA

NAREF 3 Sets neutral axis reference to the third P-line of the Structural Pointset

12.05:16


5.6.4 Defining a PositionPosition in a P-line element is defined by the PX and PY keywords, each followed by a valueor a parameter function. For example:

If you do not define a coordinate, a value of zero is assumed.

5.6.5 Defining a KeyA P-line is identified by its key in the same way as a P-point is identified by its number. Thekey is defined by the PKEY keyword followed by a word. For example:

5.6.6 Controlling the Appearance Whether a P-line is drawn or not depends on the settings of its LEVEL, TUFLA and CLFLAattributes, and the REPRESENTATION settings. How a P-line is drawn also depends on theREPRESENTATION settings. See P-point and P-line Representation for details.

5.7 Constructing 3D GeomsetsA 3D Geomset is a grouping of the primitive elements which make up a Piping Component,Joint or Fitting. It specifies the dimensions, orientation and obstruction geometry of eachprimitive. The Geomset defines what is drawn for a particular Component by PARAGON(and other PDMS modules), and also defines the obstruction geometry of the Componentfor use when clash checking. Each Component is built up from a combination of three-dimensional primitives, as listed in 3D Geomsets (GMSET).

Creating a Geomset consists of creating the relevant member primitives and setting theattributes for each primitive. For each primitive the OBST attribute must be set, whilst for aprimitive that is required to be drawn the LEVEL, TUFLA and CLFLA attributes must also beset. (See Component Design and Representation in PARAGON and the DESIGNReference Manual for details of these attributes.) 3D Geomset elements and their attributesare listed in 3D Geomset Primitives.

Note: Only the first 20 primitives in a Geomset with OBST values of 1 or 2 are consideredby DESIGN’s clash checking facility.

By using the TUFLA and CLFLA flags, you can create two different drawings of aComponent, a double-line representation (tube) and a single-line ‘stick’ representation(centreline).

PX 50 sets P-line X coordinate to 50

PY (0.5 * DESPAR[2]) sets P-line Y coordinate to 0.5 * (value of second designparameter) units

PKEY TOS sets P-line key to TOS

PKEY may be set to any desired word value. Typical values are:

TOS Top of steel, for a P-line at the top of the Profile

BOS Bottom of steel, for a P-line at the bottom of the Profile

NA, NAXI or ZAXI Neutral axis P-line

12.05:17


To define the tube representation for the tee shown in Figure 5:2.: Example ofParameterisation for a Reducing Tee (with clash geometry) the commands shown belowcould be used. (The P-points in the following examples relate to the Pointset defined inPTAXI.)

To define the centreline representation for the tee (with welded joints), the followingcommands could be used. Figure 5:10.: Centreline Representation of a Reducing Teeshows the symbol produced. The illustration is drawn with REPRESENTATION PPOINTSON LENGTH 0 NUMBERS ON. The P-points are thus displayed as dots, but they cannot beseen because they lie on the displayed LINEs.

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

12.05:18


Figure 5:10. Centreline Representation of a Reducing Tee

NEW SSPH Create sphere primitive (to represent weld)

PAXI -Y Direction of axis on which sphere origin lies

PDIS (PARA[5]) Distance of sphere origin from tee origin = halfoverall length

PDIA (0.1 * PARA[1]) Sphere diameter relative to bore size

OBST 0 Clash checking to ignore item

TUFLA FALSE CLFL TRUE Set drawing flags

NEW SSPH

PAXI P2 Set axis direction and origin in terms of P-point 2

PDIS 0 PAXI P2 PDIS 0 is equivalent to PAXI Y PDIS(PARA[5]))

PDIA (0.1 * PARA[1])

OBST 0

CLFL TRUE

NEW SSPH

PAXI P3 PDIS 0 PDIA (0.1 * PARA[3])

OBST 0 CLFL TRUE

NEW LINE P3 P0 Define line elements

OBST 0 CLFL TRUE DIAM 1

12.05:19


Note how a P-point has been used to define an axis direction and origin for a primitive - seeReference Section for details.

To put the flanges on the tee the first two representations (as given above) would remain thesame but the centreline representation would not need the SSPH elements (whichrepresent the welds). The latter are replaced by using the following commands to representthe 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

5.8 Constructing Structural GeomsetsA Structural Geomset is a grouping of the 2D primitive elements which make up a Profile.Like the 3D Geomset, it specifies the dimensions, orientation and obstruction geometry ofeach primitive. It also defines the symbol that is drawn for a particular Component and theobstruction geometry of the Component. The Profile is built up from a combination ofStructural Rectangles (SREC) and Structural Annuli (SANN), as described in StructuralGeomsets (GMSSET). Structural Geomset elements and their attributes are listed inStructural Geomset Primitives.

To define the tube representation for the Profile shown in Figure 5:3.: Example ofParameterisation for a Universal Beam Profile, the commands shown below could be used.A simplified clash geometry for the Profile is specified by defining a bounding box for theProfile with ‘hard’ obstruction and giving the primitives of the Profile itself ’no obstruction’.The P-lines used are those defined in Example of Defining a Structural Pointset.

NEW LINE P1 P2

OBST 0 CLFL TRUE DIAM 1

NEW GMSSET /UBGMSS Create new 2D Geomset

NEW SRECT Create rectangle primitive for web

PXLE (PARA[1]) Web thickness

PYLE (PARA[1] - 2 * PARA[4]) Web length

(PX and PY are zero, so there is no need to set them)

PLAXI Y Direction of axis of rectangle


OBST 0 Set obstruction value as ‘none’

NEW SRECT Create rectangle primitive for upper flange

PXLE (PARA[2]) PYLE (PARA[4]) Flange length and thickness

PY (0.5 * (PARA[1] - PARA[4])) Position of rectangle origin

PLAXI Y Direction of axis of rectangle

12.05:20


A P-line may be used to define an axis direction and position for a primitive. The examplebelow shows how the upper flange could be positioned and orientated using a P-line. SeeReference Section for details.

5.9 Reference Section

5.9.1 Parameter-Controlled AttributesThe following attributes of P-points, P-lines and Geomset primitives may be set equal toparameters or functions of parameters (as well as to constant values):

PDIStance PBDIstance PTDIstance

PBBT PBTP PCBT PCTP

PDIAmeter PBDMeter PTDMeter

PRADius PBRAdius PTRAdius PWIDth PANGle

POFFset PBOFfset PCOFfset

PX PXLEngth PY PYLEngth PZ PZLEngth

PBORe PCONnect PHEIght

PXTShear PYTShear PXBShear PYBShear


OBST 0 Set obstruction value as ‘none’

NEW SRECT Create rectangle primitive for lower flange

PXLE (PARA[2]) PYLE (PARA[4])

PY (-0.5 * (PARA[1] - PARA[4]))

PLAXI Y

TUFL TRUE CLFL FALSE

OBST 0

NEW SRECT Create rectangle which bounds the Profile

PXLE (PARA[2]) PYLE (PARA[1])

PLAXI Y

TUFL FALSE CLFL FALSE Set both drawing flags ‘off’

OBST 2 Set obstruction value as ‘hard’

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

12.05:21


5.9.2 Axial AttributesAxial attributes of both 3D and 2D primitives define a position and a direction. An axialattribute of a 3D primitive may be specified as a direction in one, two or three dimensions oras a P-point. Similarly, the axial attribute of a 2D primitive may be specified as a direction inone or two dimensions or as a P-line.

If an axial attribute of a 3D primitive is specified as a P-point, the direction of the axis istaken to be the direction of the P-point, and the origin of the axis to be the position of the P-point. If the axial attribute is specified as a direction, the origin of the axis is taken to be thecomponent origin, i.e. the position of P-point 0.

Examples:

Syntax:>--+- PAXIs --.

| ||- PAAXis -|| ||- PBAXis -|| |‘- PCAXis -+- sign -.

| |‘--------+- P - number -------------------------------.

| |‘- <axis> -+- value -----. |

| | ||- <expres> --+- sign -. || | | || ‘--------+- <axis> -|| |‘---------------------------------+-->

where <axis> is>--+-- X --.

| ||-- Y --|| |‘-- Z --+-->

If the axial attribute of a 2D primitive is specified as a P-line, the direction of the axis is takento be the direction of the P-line, and the origin of the axis to be the position of the P-line. Ifthe axial attribute is specified as a direction or direction expression, the origin of the axis istaken to be the component origin.

Examples:

PAAX -P2 sets PAAX to be opposite the direction of P-point 2 with its origin atthe 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

PLAX PLIN NAXI sets PLAX to be the direction of the P-line whose PKEY attribute isNAXI; 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

12.05:22


Syntax:>- PLAXis -+- sign -.

| |‘--------+- PLINe - <plkey> --------------------------.

| |‘- <axis> -+- value -----. |

| | ||- <expres> -+- sign -. || | | || ‘--------+- <axis> -|| |‘---------------------------------+-->

where <axis> is>--+-- X --.

| |‘-- Y --+-->

and <plkey> is the PKEY attribute of the P-line.

12.05:23


12.05:24

Catalogues and Specifications Reference ManualComponent Design and Representation in PARAGON

6 Component Design and Representation in PARAGON

This chapter introduces the methods of Component design and graphical representation inPARAGON; in particular the MODEL, MODEL SETTINGS and REPRESENTATIONcommands are detailed.

6.1 Component DesignAssuming that you have opened a suitable 3D view, the interactive graphical Componentdesign 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 specifiedby a command such as

The command

MODEL CE

(for ‘Model Current Element’) will add the new component to the 3D view.

Note: 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 andGeomsets may not be, although these items will easily be distinguishable. (Geomset and/orPointset elements can be removed from the display with the aid of the REPRESENTATIONcommand - see P-point and P-line Representation).

The MODEL SETTINGS command can be used to specify the Component Design Dataattributes. For example,

MODEL SETTINGS DDRADIUS 75 DDHEIGHT 200

gives the Design Data attributes DDRADIUS and DDHEIGHT values of 75mm and 200mmrespectively. The DDRADIUS, DDHEIGHT and DDANGLE attributes are the Designparameters used in the selection process for variable Components. In PARAGON it ispossible to use these attributes as part of the Component design. For example, whereas anattribute such as PHEIGHT would normally be defined in terms of parameters, a commandsuch as:

PHEI DDHEIGHT

NEW SCOM /CR2-1 (at SECT or CATE level)

or

NEW SPRF /UB4-A (at STSEC or STCAT level)

12.06:1


(assuming a suitable current element) would set PHEIGHT to the Design height. (In such acase, a MODEL SETTINGS command would need to be followed by a MODEL CEcommand before any change in the display would be observed.)

To produce a display of a Component with insulation, the bore, temperature and workingpressure of the Component must be known. To this end the MODEL SETTINGS commandcan be used to set the BORE, TEMP and PRESSURE. This must be done before theInsulation 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 itsdefault value, see below). The Insulation Spec may then be specified by a command suchas

MODEL SETTINGS INSPEC /INSUL1

Assuming the drawing REPRESENTATION (see Reference Section) is correctly set, theComponent 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 unsetsthe Insulation Specification.

The default values of the Design Data attributes, and the full syntax of how to set them, aregiven in Reference Section.

QUERY MODEL SETTINGS will output the Design settings currently in use. The Designprocess is turned off by

MODEL END

which also has the effect of clearing the display.

6.2 P-point and P-line Representation

6.2.1 P-pointsP-points may be displayed in PARAGON in one of two ways. The form of display iscontrolled by the REPRESENTATION PPOINTS command as illustrated in Figure 6:1.:Specifying P-points On or Off.

Figure 6:1. Specifying P-points On or Off

12.06:2


The size of the arrow may also be controlled by the REPRESENTATION PPOINTScommand, as illustrated in Figure 6:2.: Specifying P-point Length. The overall length of thearrow is specified in millimetres. The default length is 50mm. Specifying a length of zerocauses the P-point to appear as a dot.

Figure 6:2. Specifying P-point Length

The P-point numbers may be omitted, or they may be displayed any size, the size beingspecified in millimetres. The default size is 5 mm. The size of the numbers is controlled bythe REPRESENTATION PPOINTS command, as illustrated in Figure 6:3.: Specifying P-point Number Representation.

Figure 6:3. Specifying P-point Number Representation

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 displaycompletely.

See Reference Section at the end of this chapter for the full syntax of theREPRESENTATION PPOINTS command.

12.06:3


6.2.2 P-linesP-lines may be displayed in PARAGON in one of two ways. The form of display is controlledby the REPRESENTATION PLINES command as illustrated in Figure 6:4.: Specifying P-lines On or Off.

Figure 6:4. Specifying P-lines On or Off

The P-line identifier keys may be omitted or displayed. This is also controlled by theREPRESENTATION PLINES command, as illustrated in Figure 6:5.: Specifying P-lineIdentifier Key Representation.

Figure 6:5. Specifying P-line Identifier Key Representation

P-line length (default 50mm) and size (default 5mm) can also be controlled. See ReferenceSection at the end of this chapter for the full syntax of the REPRESENTATION PLINEScommand.

Unlike P-points, P-lines can be omitted from the display completely. Whether a P-line isdrawn or not depends on the settings of three of its attributes:

• LEVEL - the drawing level range• CLFLA - the centreline drawing flag attribute• TUFLA - the tube drawing flag attribute

LEVEL is a pair of integers. CLFLA and TUFLA are logical attributes which are set to TRUEor FALSE (corresponding to ‘ON’ or ‘OFF’ respectively). When you first create a P-line,CLFLA and TUFLA are both FALSE.

Control is initially on the setting of LEVEL. If the PARAGON LEVEL setting is within theLEVEL range specified for the P-line (as its LEVEL attribute) then the P-line will beconsidered for drawing, otherwise it will not be. If the level condition is satisfied, thenwhether a P-line is displayed or not in PARAGON depends upon the settings of its CLFLA

12.06:4


and TUFLA attributes and upon the settings of the drawing options specified by theREPRESENTATION command.

The REPRESENTATION command provides a means of effectively overriding the settingsof the P-line’s drawing attributes without changing them. An example REPRESENTATIONcommand is

REPRESENTATION TUBE ON CL OFF

(The word CENTRELINE may be used instead of CL.)

The drawing option settings interact with the drawing attributes of the P-lines thus: if an ‘ON’REPRESENTATION setting matches a corresponding ‘TRUE’ attribute setting (e.g.REPRESENTATION CL ON and CLFL TRUE) then the P-line will be drawn, otherwise it willnot be drawn.

The drawing of Geomset primitives is controlled in a similar way. The next section givesexamples of how the LEVEL, CLFLA and TUFLA attributes interact with theREPRESENTATION settings.

6.3 Geomset Primitive RepresentationWhether 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 OBSTattribute 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 itsLEVEL attribute), then the primitive will be considered for drawing, otherwise it will not be. Ifthe level condition is satisfied then, the primitive will be displayed if it has an OBST value of1 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 ifOBST = 1 (soft obstruction0.

The control mechanisms of tube, centreline and obstruction are quite independent of eachother. So, for example, if a primitive has an OBST value of 2 and the REPRESENTATIONsetting is OBSTRUCTIONS ON, the primitive will be drawn whatever the values of itsCLFLA and TUFLA attributes and the REPRESENTATION TUBE and CL settings (providedthat the PARAGON LEVEL setting is within the LEVEL range of the primitive).

Note: Whenever you use a REPRESENTATION command, the current design Componentis redrawn. If you want to change several REPRESENTATION settings, put them allin the same line so that the Component is only redrawn once. For example,REPRESENTATION TUBE ON CL OFF OBST ON PPOINTS OFF

The following example shows the Catalogue representation of a control valve, and how itmight appear in PARAGON with various combinations of TUBE, CL and OBST settings. Allthe illustrations have PPOINTS ON.

12.06:5


Figure 6:6. Catalogue Control Valve, showing all Primitives

For this example, the settings of the attributes of interest are considered to be:

SCYL 1, SCYL 2 and SDSH 1 are obstruction volume primitives, that is, they representthe obstruction volume of the Component, not its physical geometry and dimensions. Theother primitives represent the actual geometry and dimensions of the Component.

The following illustrations show the appearance of the Component under variousREPRESENTATION settings.

SCYL 1 - OBST 2, CLFL FALSE, TUFL FALSE

SCYL 2 - OBST 2, CLFL FALSE, TUFL FALSE

SSPH 1 - OBST 0, CLFL TRUE, TUFL TRUE

SCON 1 - OBST 0, CLFL TRUE, TUFL TRUE

SDSH 1 - OBST 2, CLFL TRUE, TUFL TRUE

SCYL 3 - OBST 0, CLFL FALSE, TUFL TRUE

SCYL 4 - OBST 0, CLFL FALSE, TUFL TRUE

LSNO 1 - OBST 0, CLFL FALSE, TUFL TRUE

LSNO 2 - OBST 0, CLFL TRUE, TUFL FALSE

LSNO 3 - OBST 0, CLFL FALSE, TUFL TRUE

LSNO 4 - OBST 0, CLFL TRUE, TUFL FALSE

12.06:6


Figure 6:7. REPRESENTATION OBST OFF TUBE OFF CL ON

This is the default REPRESENTATION setting for OBSTRUCTION, TUBE andCENTRELINE. The attribute settings chosen for this example are ‘typical’ for a Catalogue,and so Figure 6:7.: REPRESENTATION OBST OFF TUBE OFF CL ON shows the ‘normal’appearance of the valve. Notice how the OBST OFF setting does not affect the visibility ofthe obstruction dish (handwheel space) since it has CLFL TRUE.

Figure 6:8. REPRESENTATION OBST ON TUBE OFF CL ON

12.06:7


Here the OBST ON setting matches the OBST 2 attribute value of the obstruction cylindersand so they become visible, even though they have CLFL and TUFL both FALSE.

Figure 6:9. REPRESENTATION OBST ON TUBE OFF CL OFF

Here TUBE and CENTRELINE are both OFF but OBST is ON, and so only the obstructionvolume primitives are visible.

Figure 6:10. REPRESENTATION OBST ON TUBE ON CL OFF

Compared with Figure 6:9.: REPRESENTATION OBST ON TUBE OFF CL OFF, thoseprimitives with TUFL TRUE now become visible because TUBE is now ON. The obstructionprimitives remain visible because OBST is still ON.

12.06:8


Figure 6:11. REPRESENTATION OBST OFF TUBE ON CL OFF

OBST is now OFF and so the obstruction cylinders disappear. (The obstruction dishremains because it has TUFL TRUE.)

Figure 6:12. REPRESENTATION OBST OFF TUBE ON CL ON

Here, all those primitives which have one or both of CLFL, TUFL TRUE are visible.

12.06:9


Figure 6:13. REPRESENTATION OBST ON TUBE ON CL ON

In Figure 6:13.: REPRESENTATION OBST ON TUBE ON CL ON, all theREPRESENTATION settings are ON and so all the Geomset primitives are visible.

Figure 6:14. REPRESENTATION OBST OFF TUBE OFF CL OFF

Here, all the REPRESENTATION settings are OFF and so no primitives are visible. TheComponent P-points are still visible since the REPRESENTATION PPOINTS setting in theexample is ON.

12.06:10


The full default REPRESENTATION is:

CL ONTUBE OFFOBSTRUCTIONS OFFLEVEL 0PPOINTS ON LENGTH 50 NUMBERS OFFPLINES ON PKEYS OFF

which is regained by

REPRESENTATION DEFAULT

Note that the TVISIBLE and BVISIBLE end visibility flags have no effect in PARAGON.

6.4 Reference SectionThis section gives the syntax of the MODEL SETTINGS command and theREPRESENTATION command, as described in this chapter and in Catalogue DatabaseStructure (the latter for setting component parameter defaults etc.).

The description of the syntax for the REPRESENTATION command is spread over anumber of separate sections, each showing how the command is applied to a particular typeof element. The final section summarises the complete REPRESENTATION syntax in asingle diagram.

Querying information is given, as are further examples, where appropriate.

6.4.1 Model Settings

Examples of setting default component parameters:

Keywords: MODEL SETTINGS

Function: Sets default component parameters and design data attributes.

Description: Sets default values for component parameters and specimen valuesfor other classes of parameters (see Catalogue Database Structure).Also sets design data attributes; the numeric attributes may be used inplace of parameters for defining Pointsets and Geomsets.

MODEL SET PAR 3 35 Sets default value for component parameter 3 to 35

MODEL SET IPAR 1 3.5 IPAR 2 4.5 Sets insulation parameter 1 to 3.5’ andinsulation parameter 2 to 4.5

MODEL SET APAR 1 250 Sets attached parameter 1 to 250

MODEL SET APAR 3 5.1 OPAR 2 19.75 Sets attached parameter 3 to 5.1 and owningparameter 2 to 19.75

MODEL SET CAT OPAR 3 2.5 Sets owning parameter 3 to 2.5

MODEL SET DES PARA 3 1.2 Sets design parameter 3 to 1.2

12.06:11


The word CAT (short for CATALOGUE) in the fifth example is optional. You can use it whensetting default values for component parameters, and when setting specimen values forstructural parameters. You may find it helpful to use the word for clarity in macros, todistinguish between Design DB parameters and other classes of parameters.

Values for any of these classes of parameters may be set in a single command, forexample:

MODEL SET PAR 2 12 IPAR 1 17 APAR 2 32 DES PAR 3 25 DES OPAR 5 6.3

Examples of setting design data attributes:

Default values:

MODEL SET DES APAR 10 99 Sets design attached parameter 10 to 99

MODEL SET DES PAR 2 (ATAN(4 / 3)) Sets design parameter 2 to tan-1 4/3

MODEL SET DEF Deletes all default and specimen parameters(also sets Design Data attributes to defaultvalues)

MODEL SET INSPEC /IS50 Set Insulation Specification to IS50

MODEL SET BOR 100 TEMP 350PRESS 50

Set Component bore, temperature and pressureto given Design value as

MODEL SET DDHEI 2000 DDRAD 35 Set height and radius to given Design values

MODEL SET DDANG (ASIN(6 / 7)) Set Design Angle to arcsin (6/7)

MODEL SET DEF Set Design Data attributes to default values (alsodeletes all default and specimen parameters andunsets Insulation Spec)

TEMP -100000

BORE 150.0 mm

PRESSURE 0.0

DDANGLE 90 degrees

DDHEIGHT 100.0 mm

DDRADIUS 225 mm

INSPEC Nulref (i.e. unset)

12.06:12


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:

>- Q - MODEL -- SETtings --+-- CATalogue --.|-- DESign -----||---------------+-- PARam ---.| |-- APARam --|| ‘-- OPARam --+| ||-- IPARam ------------------|| ||-- INSpec ------------------|| ||-- TEMp --------------------|| ||-- BORe --------------------|| ||-- PREssure ----------------|| ||-- DDHEIght ----------------|| ||-- DDRADius ----------------|| |‘-- DDANGle -----------------+-->

12.06:13


6.4.2 Setting Representation for Piping Components

Examples:

Command Syntax:.---------------------<-----------------./ |

>-- REPResentation --*-- CL -------------------------. || | ||-- CENTreline -----------------| || | |‘-- TUBE -----------------------+-- ON ---|

| |‘-- OFF --+-->

Querying:

Keywords: REPRESENTATION TUBE CL CENTRELINE

Description: The REPRESENTATION command allows piping components tobe represented by a single centreline (CL) or by a 2D outline(TUBE). In some cases, it helps to switch between the tworepresentations to simplify an otherwise complicated view.

Switching TUBE On switches CL Off automatically, and vice versa.

TUBE and CL representations are not instantly updated on thescreen. To see the effects of a representation change, it isnecessary to replace the affected item in the Draw List byRemoving and Adding it.

REPR TUBE ON Sets tubing representation as double line

REPR CL ON Sets tubing representation as centreline

Q REPR TUBE

Q REPR CL

Q REPR - queries all Representation options.

12.06:14


6.4.3 Setting Profile Representation for Steelwork

Examples:

.-----------------<--------------------./ |

>-- REPResentation --*-- PROFile --+-- CL ----------. || | ||-- CENTreline --| || | |‘----------------+-- ON ---|

| |‘-- OFF --+-->

Querying:

Keywords: REPRESENTATION PROFILE

Description: The REPRESENTATION PROFILE commands allow structuralsteel profiles to be represented by a single centreline or by a 2Doutline. In some cases, it helps to switch between the tworepresentations to simplify an otherwise complicated view.

Changes to the representation are not instantly updated on thescreen. To see the effects of a representation change, it isnecessary to replace the affected item in the Draw List by Removingand Adding it.

REPR PROF ON PROF CL OFF Sets profile representation as 2D outline

REPR PROF CL ON PROF OFF Sets profile representation as centreline

REPR PROF ON PROF CL ON Sets both types of representation on

Q REPR PROF

Q REPR - queries all Representation options.

12.06:15


6.4.4 Setting Level Representation

Examples:

Command Syntax:.-------------------<-------------------./ |

>-- REPResentation --*-- LEVel --+-- PIPE -------. || | ||-- NOZZle -----| || | ||-- STRUcture --| || | |‘---------------+-- integer --+-->

Querying:

Keywords: REPRESENTATION LEVEL

Description: This command enables individual drawing levels to be specified forthe display of catalogue elements. Every basic primitive shape hasan associated drawing level range attribute stored in the Catalogue.If the specified drawing level coincides with this range, the 3Dobject will be drawn when it is added to the Draw List.

The practical effect of this facility is that it allows you to minimisevisible detail when representing catalogue items. For instance, atlevel 3, steelwork may be represented as single line only, whereasat level 1 the full detail may be visible. Level 3 may well beadequate for design purposes.

LEVEL manipulation is not instantly updated on the screen. To seethe effects of a level change, use the REPR UPDATE command.

REPR LEVEL PIPE 5 Sets piping level to 5. All pipes which are added after thiscommand will be drawn at level 5. Those which were already inthe view will remain unchanged.

REPR LEVEL 2 Set level for all other Component types to 2

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

12.06:16


6.4.5 Setting Obstruction and Insulation Representation

Examples: REPR OBST ON INSU OFFREPR INSU ON REPR PROF OBST ON PROF INSU OFF

Command Syntax:.--------------<------------./ |

>-- REPResentation --*-- OBSTruction --. || | ||-- INSUlation ---+-----------|| |‘-- PROFile --+- OBSTruction -|

| |‘- INSUlation --+- ON --.

| |‘- OFF -+-->

Querying:

Keywords: REPRESENTATION OBSTRUCTION INSULATION

Description: Component Obstructions are often given LEVELS or TUBE andCENTRELINE settings which render them invisible. Setting theRepresentation of OBST On forces the system to override normalLEVEL and TUBE settings and show all of the primitives,regardless of the other settings.

Setting the Representation of INSU On or Off determines whetheror not insulation is shown on primitives.

These have the effect of considering all primitives which have anobstruction level greater than zero and all primitives which areaffected by insulation parameters. As with changes to LEVELrepresentation, the graphics display is not updated instantly. Usethe RECR UPDATE command to make any changes visible.

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

12.06:17


6.4.6 Setting P-Point Representation

Examples:

Command Syntax:>-- REPResentation - PPoints --+-- ON ---.

| ||-- OFF --|| |

| |‘--------------------------+--.

|.--------------<---------------------’|+-- NUMbers --+-- ON ---.| | || ‘-- OFF --|| |‘------------------------+-->

Querying:Q REPR PPOINTS

Keywords: REPRESENTATION PPOINTS LENGTH NUMBERS

Description: P-point representation may be set to ON or OFF. The defaultsetting is PPOINTS OFF, although p-points will be shownautomatically as part of an identification operation.

When p-points are on, they are drawn as small arrows with a crossat the p-point position and with the arrow indicating the p-pointdirection. The size of the arrow is controlled by the LENGTH option.P-point numbers may also be displayed, as controlled by theNUMBERS option.

As with changes to other representation settings, the graphicsdisplay is not updated instantly. Items must be removed and re-added to the Draw List before changes to the display of p-pointsbecomes visible.

REPR PPOINTS ON Sets the p-point representation to ON

REPR PPOINTS LENGTH 5 Sets size of p-point arrows

REPR PPOINTS NUMB ON Shows p-point numbers

12.06:18


6.4.7 Setting P-Line Representation

Examples:

Command Syntax:.---------------------<---------------.

/ |>-- REPResentation --*-- PLINes -+- ON --. |

| | | || |- OFF -| || | | || ‘-------+- LENgth - <uval> -|| | || ‘-------------------|| |‘-- PKEYs --+- ON --. |

| | |‘- OFF -+-------------------+-->

Querying:Q REPR PLINESQ REPR PKEYS

Keywords: REPRESENTATION PLINES LENGTH PKEY

Description: P-line representation for structural Profiles may be set to ON orOFF. The default setting is PLINES OFF.

When p-lines are on, the size of the arrow showing their direction iscontrolled by the LENGTH option. P-line identifiers, in the form ofthe settings of their PKEY attributes (TOS, BOS, NA, etc.) may alsobe displayed, as controlled by the PKEY option.

As with changes to other representation settings, the graphicsdisplay is not updated instantly. Use the RECR UPDATE commandto see changes to the display of p-lines.

REPR PLINES ON Sets the p-line representation to ON

REPR PLINES LENGTH 6 Sets size of p-line arrows

REPR PLINES PKEY ON Shows p-line identifiers (settings of PKEY attributes)

12.06:19


6.4.8 Full REPRESENTATION Syntax.----------------------<-------------------./ |

>-- REPResentation --+--*-- TUBE - <onoff> --------------------------|| | || |-- CL ----------. || | | || |-- CENTreline --+- <onoff> -----------------|| | || |-- HOLEs - <onoff> -------------------------|| | || |-- OBSTruction - <onoff> -------------------|| | || |-- INSUlation - <onoff> --------------------|| | || |-- LEVel -+- PIPE ------. || | | | || | |- NOZZle ----| || | | | || | |- STRUcture -| || | | | || | ‘-------------+- integer ---------|| | || |-- PPoints - <onoff> - <ppsiz> -------------|| | || |-- PROFile -+- CL ----------. || | | | || | |- CENTreline --| || | | | || | |- OBSTruction -| || | | | || | |- INSUlation --| || | | | || | ‘---------------+- <onoff> -----|| | || |-- PNODes --. .--------<---------. || | |/ | || |-- SNODes --*- <onoff> ----------| || | | | || | |- COLour - <colno> -| || | | | || | ‘-- SIZe - <uval-----+----------|| | || |-- POINts - <onoff> ------------------------|| | || |-- PKEYs - <onoff> -------------------------|| | || |-- PLINes - <onoff> -+- LENgth - <uval> -. || | | | || | ‘-------------------+--|| | || |-- HOLes - <onoff> -------------------------|| | || |-- MASSproperties - <int> ------------------|| | || |-- DARCtolerance - <uval> ------------------|| | || \-- UPDATE ----------------------------------|| |‘-- DEFault ------------------------------------+-->

<onoff> is either ON or OFF

<ppsiz> is

>--+- LENgth - <uval> -.| |‘-------------------+- NUMbers - <onoff> -.

| |‘---------------------+-->

12.06:20


<colno> is

>--+-- integer ----------------------------------------.| ||-- ACTive -----------------------------------------|| ||-- VISIble ----------------------------------------|| ||-- CE ---------------------------------------------|| ||-- CLASH ------------------------------------------|| ||-- OBST -------------------------------------------|| ||-- COMPAre --+-- MATCHed -----------------------. || | | || |-- MISMatched --------------------| || | | || |-- UNMAtched --+-- CONNector --. | || | | | | || | ‘---------------+--| || | | || ‘-- TEXT --------------------------+--|| |‘-- AIDS -------------------------------------------+-->

12.06:21


12.06:22

Catalogues and Specifications Reference ManualCatalogue Database Elements Setup in PARAGON

7 Catalogue Database Elements Setup in PARAGON

This chapter describes in detail the following Catalogue DB elements:• 3D Pointset (PTSET)• Structural Pointset (PTSSET)• 3D Geomset (GMSET)• Negative 3D Geomset (NGMSET)• Structural Geomset (GMSSET)• Detailing Text and Material Text• Connection Tables and Bolt Tables• Unit Types• General Text• User-defined Nominal Dimensions

Creation and manipulation of the Catalogue elements is described in Manipulating theCatalogue Database using PARAGON.

7.1 3D Pointsets (PTSET)A PTSET is a collection of P-point elements. P-points are used in the design process toposition 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 3DGeomset primitives which make up Piping Components, Joints and Fittings. (Profiles do notuse P-points.)

A P-point has a 3D position and a direction, and is identified by a number. Each PTSETincludes a special P-point, P-point zero (P0), whose position is the component origin andwhose direction is the Z axis direction of the Component. It has no other attributes. P0 iscreated automatically by PARAGON; you cannot change it in any way.

The numbering of the P-points of Piping Components must follow certain conventions - seePiping Components in PARAGON for a summary of these, and the ISODRAFT ReferenceManual for fuller details. There are no special conventions for numbering the P-points ofJoints and Fittings.

A P-point has a connection type attribute, which is used only when the P-point belongs toa Piping Component. The connection type attribute can be used to specify how a PipingComponent is connected to another at the position of the P-point, for example by a butt weldor socket weld.

12.07:1


A P-point has a bore attribute, which is used only when the P-point belongs to a PipingComponent. 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 tocheck that the connection type attributes of Piping Components are compatible with thecorresponding attributes of the Components to which they are connected. The compatibilityof connection types is defined in a Connection Compatibility Table (CCTAB) - seeConnection Compatibility Tables for details.

Use of the REPRESENTATION command affects how P-points are drawn by PARAGON;see P-point and P-line Representation 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

7.1.1 Axial P-point (PTAXI)A PTAXI allows a P-point to be defined in terms of an axis and a distance along that axis. APTAXI has no member elements and has the following attributes:

• NUMB - the P-point number • PCON - the connection type• PBOR - the bore of the P-point • PAXI - the axis of the P-point• PDIS - the distance along the axis of the P-point• PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT• DESC - a textual description of the P-point• PURP - the purpose of the P-point

NUMB must be set as a value. PAXI must be set as a direction - see Defining an Axis fordetails. The other attributes may be set as values or words (as appropriate), or in terms ofparameters (which in turn are values or words). The classes of parameter which may beused depend on the class of Component (Piping Component, Joint or Fitting) which usesthe P-point - see Parameters for details. PCON and PBOR are used for Piping Componentsonly. They have no meaning if the P-point is used by a Joint or Fitting. For details of PSKEYsettings, see Specifying Pipe End Conditions for use by ISODRAFT.

These conventions also apply to the attributes of the PTCAR and PTMIX elementsdescribed below. See Constructing 3D Pointsets for examples of setting these attributes.

12.07:2


7.1.2 Cartesian P-point (PTCAR)A PTCAR allows a P-point to be defined by specifying its position and direction explicitly. APTCAR has no member elements and has the following attributes:

• NUMB - the P-point number• PCON - the connection type• PBOR - the bore of the P-point• PX,PY,PZ - the X, Y, Z coordinates of the P-point• PTCDIR - the direction of the P-point• PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT• DESC - a textual description of the P-point• PURP - the purpose of the P-point

PTCDIR must be set as a direction - see Defining a Direction for details.

7.1.3 Mixed Type P-point (PTMIX)A PTMIX allows a P-point to be defined by specifying the position explicitly but using PAXI tospecify the direction. A PTMIX has no member elements and has the following attributes:

• NUMB - the P-point number• PCON - the connection type• PBOR - the bore of the P-point• PX,PY,PZ - the X, Y, Z coordinates of the P-point• PAXI - the axis of the P-point• PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT• DESC - a textual description of the P-point• PURP - the purpose of the P-point

7.1.4 Position Type P-point (PTPOS)A PTPOS allows a P-point to be defined by specifying a position expression PTCPOS andusing PTCD to specify the direction expression. A PTPOS has no member elements andhas the following attributes:

• NUMB - the P-point number• PCON - the connection type• PBOR - the bore of the P-point• PTCPOS - the position expression• PTCD - the direction expression• PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT• DESC - a textual description of the P-point• PURP - the purpose of the P-point.

7.2 Structural Pointsets (PTSSET)A PTSSET is a collection of P-line elements (PLINE). P-lines are used in the Catalogue byProfiles and Joints. P-lines are used in the design process to position and orientate Sections(derived from Profiles) and Joints.

12.07:3


Figure 7:1. D and 3D Views of a P-line

A P-line is the structural counterpart of a P-point. It is a line which runs the full length of aComponent parallel to its Z axis. Viewed in the XY plane, it appears as a point. This point isits position. A P-line also has a direction. This is not the direction of the line itself (which isalways 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.: D and 3D Viewsof a P-line shows a two-dimensional view and a three-dimensional view of a P-line on thetop of a Section.

P-lines may be used in PARAGON to define the position and orientation of the 2D primitivesin a Structural Geomset which make up a Profile. They cannot be used to position andorientate 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 isthe 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 ofa 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 Defining an Axis fordetails. PX and PY may be set as values or in terms of parameters. The classes ofparameter which may be used depend on whether the P-line is used by a Profile or by a

12.07:4


Joint - see Parameters for details. Manipulating the Catalogue Database using PARAGONgives examples of setting these attributes.

The settings of LEVEL, CLFLA and TUFLA and the use of the REPRESENTATIONcommand affect whether or not the P-line is drawn by PARAGON. LEVEL is a pair ofnumbers 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 CLFLAand the REPRESENTATION settings interact is discussed in P-point and P-lineRepresentation. (The settings of LEVEL, CLFLA and TUFLA also affect whether or not theP-line is drawn in DESIGN.)

The primitives in the Geomsets also have LEVEL, CLFLA and TUFLA attributes, whichaffect 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 inPARAGON). See the DESIGN Reference Manual for details.

7.3 3D Geomsets (GMSET)A GMSET is a grouping of 3D primitive elements which are used to make up PipingComponents, Joints and Fittings. It specifies the dimensions, orientation and obstructiongeometry of each primitive. The Geomset defines the symbol that is drawn for a particularComponent by PARAGON (and DESIGN) and also defines the obstruction geometry of theComponent for use when checking for clashes. Each symbol is built up from a combinationof the following primitives:

• SBOX - rectangular box• BOXI - boxing (used by HVAC and Ducting etc)• SCON - cone• LCYL - cylinder• SCYL - cylinder• SSLC - slope bottomed cylinder• SDIS - disc• SDSH - dish• SLINE - line• LINE - line• LPYR - pyramid• SCTO - circular torus• SRTO - rectangular torus• LSNO - snout• SSPH - sphere• TUBE - tubing• SEXT - user-defined extrusion• SREV - solid of revolution

GMSET has no attributes other than the standard ones. Each member element of a 3DGeomset has the following attributes in addition to the standard ones:

• LEVEL - the drawing level range attribute• CLFLA - the centreline drawing flag attribute• TUFLA - the tube drawing flag attribute

12.07:5


• OBST - the obstruction attribute• DESC - a textual description of the Geomset• GTYP - the generic type of the item for which the Geomset is used• PURP - the purpose of the Geomset

The settings of LEVEL, CLFLA and TUFLA affect whether the primitive is drawn or not byPARAGON (or DESIGN), as they do for P-lines. See Structural Pointsets (PTSSET) fordetails.

OBST is a number which defines the obstruction level of the primitive for use by DESIGN’sclash checking facility:

• OBST = 0:No obstruction. The primitive will not clash with anything (used for symbols andnegative volumes).

• OBST = 1:‘Soft’ obstruction. Used for insulation, access volumes, penalty volumes, etc.

• OBST = 2:‘Hard’ obstruction. DESIGN’s clash checking facility will report hard interference withany item having OBST 1 or 2.

The LEVEL, OBST, CLFLA and TUFLA attributes are common to all primitives. Eachprimitive also has additional attributes depending on its shape; these are described in thenext section.

7.4 3D Geomset PrimitivesThe following primitive elements are used by 3D Geomsets. They all have the standardattributes and the common attributes LEVEL, CLFLA, TUFLA and OBST.

7.4.1 Box (SBOX)SBOX has particular attributes as follows:

• PXLE, PYLE, PZLE - box dimensions in X, Y, Z directions• PX, PY, PZ - box coordinates

Figure 7:2. SBOX Catalogue Primitive

12.07:6


7.4.2 Boxing (BOXI)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 trays.

BOXI has the following particular attributes:• PXLE - cross-section X-direction length• PZLE - cross-section Z-direction length• PAXI - position and orientation of normal to centre of end face• TVISI - visibility of top face• BVISI - visibility of bottom face

Figure 7:3. BOXI Catalogue Primitive

When implied tube is drawn using BOXI elements, the Y axis of the implied BOXI is set tothe PLeave direction of the preceding component. The X axis of the BOXI is set to bemutually orthogonal to the PLeave and the Z axis of the preceding component (whichusually corresponds to the X axis of the component). The Z axis of the BOXI is then derivedfrom 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 maybe offset in the X or Z directions.

Note: for Pipework Designers: If there is no preceding component (that is, if the impliedBOXI forms the Head of a Branch), the Y axis will be set to the Parrive of thefollowing component (that is, the first component in the Branch). If there are nocomponents, the BOXI will be set to the orientation of the Zone. (Since Pipe andBranch elements have no coordinate system, this is the lowest level in the designhierarchy from which an orientation can be derived.)

7.4.3 Cone (SCON)SCON has particular attributes as follows:

• PAXI - direction of axis of cone• PDIS - height of vertex above base• PDIA - diameter of base

12.07:7


Figure 7:4. Cone Catalogue Primitive

7.4.4 Cylinder (LCYL)There are three types of cylinder primitive defined in different ways. LCYL is defined by thedistances from the origin to the two end faces. LCYL has particular attributes as follows:

• PAXI - direction of axis of cylinder• PDIA - diameter of cylinder• PBDI - distance along axis to centre of bottom surface• PTDI - distance along axis to centre of top surface• TVISI - visibility of top face• BVISI - visibility of bottom face

Figure 7:5. Cylinder (LCYL) Catalogue Primitive

12.07:8


7.4.5 Cylinder (SCYL)This type of cylinder primitive is defined by the distance to the bottom face from the originand the height. SCYL has particular attributes as follows:

• PAXI - direction of axis of cylinder• PHEI - height of cylinder• PDIA - diameter of cylinder• PDIS - distance along axis to centre of nearest surface• TVISI - visibility of top face• BVISI - visibility of bottom face

Figure 7:6. Cylinder (SCYL) Catalogue Primitive

7.4.6 Slope-Bottomed Cylinder (SSLC)This is similar to the SLCY available in the Design Data and has its main use in themodelling of mitred bends. SSLC has the following particular attributes:

• PAXI - direction of axis of cylinder• PHEI - height of cylinder• PDIA - diameter of cylinder• PXTS - inclination of top face to X-axis• PYTS - inclination of top face to Y-axis• PXBS - inclination of bottom face to X-axis• PYBS - inclination of bottom face to Y-axis• PDIS - distance from origin• TVISI - visibility of top face• BVISI - visibility of bottom face

12.07:9


Figure 7:7. Slope-Bottomed Cylinder (SSLC) Catalogue Primitive

7.4.7 Disc (SDIS)The Disc primitive is a circular element of zero thickness. SDIS has particular attributes asfollows:

• PAXI - direction of axis of disc• PDIS - distance along axis to centre of disc• PDIA - diameter of disc

Figure 7:8. Disc Catalogue Primitive

12.07:10


7.4.8 Dish (SDSH)This is similar to the DISH available in the Design Data. It allows symbolic modelling ofcontrol valves and closer modelling of other Components. SDSH has the following particularattributes:

• PAXI - direction of axis of dish• PDIS - distance along axis to centre of top surface• PDIA - diameter of dish base• PHEI - maximum height of dished surface above base• PRAD - corner radius

If PRAD=0 a spherical section dish is drawn, if PRAD>0 an ellipsoidal section dish is drawn.

Figure 7:9. Dish Catalogue Primitive

7.4.9 Line (LINE)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 in thecorresponding Pointset, which determine the course of the line.

The values held in PTS are set by the SETPoints command, followed by pointspecifications 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 pointelement (TANP) in the Design Data. (See the DESIGN Reference Manual for furtherdetails).

7.4.10 Line (SLINE)In addition to the three-dimensional primitive elements, an alternative to the LINE element isthe SLINE. This has two particular attributes:

• PTSPOS - Start position expression• PTEPOS - End position expression

12.07:11


7.4.11 Pyramid (LPYR)The main use of this element is in the creation of rectangular reducers for ducting etc. LPYRhas the particular attributes as follows:

• PAAX - direction of axis normal to top face of pyramid (the A axis): this is taken to be in the Z direction

• PBAX, PCAX - the directions of the two axes perpendicular to the A axis and mutuallyperpendicular to define the position of the B and C sides

• PBTP, PCTP - length of top faces in B axis and C axis directions• PBBT, PCBT - length of bottom faces in B axis and C axis directions• PBOF, PCOF - top face offsets in B axis and C axis directions• PTDI - distance from origin to centre of top face along A axis• PBDI - distance from origin to centre of bottom face along A axis• TVISI - visibility of top face• BVISI - visibility of bottom face

Figure 7:10. Pyramid Catalogue Primitive

7.4.12 Circular Torus (SCTO)The circular torus is only part of a torus; it is not permitted to subtend more than 180degrees. It is circular in cross-section. SCTO has particular attributes as follows:

• PAAX, PBAX - direction of axes normal to the end faces of the torus• PDIA - diameter of the cross-section of the torus.• TVISI - visibility of top face• BVISI - visibility of bottom face

12.07:12


Figure 7:11. Circular Torus Catalogue Primitive

7.4.13 Rectangular Torus (SRTO)The rectangular torus is similar to the circular torus except that it is rectangular in cross-section. SRTO has particular attributes as follows:

• PAAX, PBAX - direction of axes normal to the end faces of the torus• PDIA - width of the cross-section of the torus• PHEI - height of the cross-section of the torus• TVISI - visibility of top face• BVISI - visibility of bottom face

Figure 7:12. Rectangular Torus Catalogue Primitive

7.4.14 Snout (LSNO)The Snout primitive is a cylindrical element of varying diameter along its length. It may beeccentric or concentric. LSNO has particular attributes as follows:

• PAAX - direction of axis normal to top surface of snout (the A axis)• PBAX - offset direction• PTDI, PBDI - distance along A axis to top, bottom surfaces of snout• PTDM, PBDM - diameter of top, bottom surfaces of snout• POFF - the offset/eccentricity of the snout as measured in the PBAX direction• TVISI - visibility of top face• BVISI - visibility of bottom face

12.07:13


Figure 7:13. Snout Catalogue Primitive

The sizes of the top and bottom surfaces of the snout may be defined in terms of their radiiinstead of their diameters.

• PTRA, PBRA - radius of top, bottom surfaces of snout

7.4.15 Sphere (SSPH)SSPH has particular attributes as follows:

• PAXI - direction of axis on which centre of sphere lies• PDIS - distance along axis to centre of sphere• PDIA - diameter of sphere

Figure 7:14. Sphere Catalogue Primitive

7.4.16 Tube (TUBE)Components whose GTYPE attribute is TUBE can use TUBE Geomset elements to give, forexample, implied tube of circular cross-section. TUBE has particular attributes as follows:

• PDIAM - tube diameter• TVISI - visibility of top face• BVISI - visibility of bottom face

12.07:14


7.4.17 User-defined Extrusion (SEXT)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 called Vertices (SVER).The lines joining adjacent SVERs form the edges of the SLOO. The extrusion distance isdefined 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 appliesa convex or concave fillet to the loop at that point.

SEXT has particular attributes as follows:• PX, PY, PZ - coordinates of origin of SLOO• PAAX, - directions of axes of SLOO• PBAX - (these will define coordinate system for SVERs)• PHEI - distance by which 2D SLOO is extruded to form 3D SEXT

SLOO has no special attributes.

SVER has particular attributes as follows:• PX, PY - coordinates of vertex• PRAD - fillet radius of loop at vertex position

Figure 7:15. User-defined Extrusion Catalogue Primitive

7.4.18 Solid of Revolution (SREV)This primitive is generated by rotating a user-defined 2D shape, known as a Loop (SLOO),whose outline is defined by a set of member elements called Vertices (SVER), through anangle about an axis. The swept angle must be in the range -360 to +360 degrees, 360degrees giving a solid which is axially symmetrical.

In addition to the attributes defining its position, each SVER can have a radius which appliesa convex or concave fillet to the loop at that point.

SREV has particular attributes as follows:• PX, PY, PZ - coordinates of origin of SLOO• PAAX, - directions of axes of SLOO• PBAX - (these will define coordinate system for SVERs)• PANGLE - angle through which 2D SLOO is rotated to form 3D SREV

12.07:15


SLOO has no special attributes.

SVER has particular attributes as follows:• PX, PY - coordinates of vertex• PRAD - fillet radius of loop at vertex position

Figure 7:16. Solid of Revolution Catalogue Primitive

7.5 Negative 3D Geomsets (NGMSET) and Negative PrimitivesA NGMSET is a grouping of negative 3D primitive elements which are used to representholes or end preparations for structural items. It specifies the dimensions, orientation andobstruction geometry of each negative primitive. The attributes of NGMSETs are the sameas those of their positive equivalents (see 3D Geomsets (GMSET) and 3D GeomsetPrimitives).

The Negative Geomset defines the symbol that is drawn for a particular Component byPARAGON (and DESIGN) and also defines the obstruction geometry of the Component foruse when checking for clashes.

Each symbol is built up from a combination of the following negative primitives:• NSBO - negative rectangular box• NBOX - negative boxing• NSCO - negative cone• NLCY - negative cylinder• NSCY - negative cylinder• NSSL - negative slope bottomed cylinder• NLPY - negative pyramid• NSCT - negative circular torus• NSRT - negative rectangular torus• NLSN - negative snout• NSSP - negative sphere• NTUB - negative tubing• NSEX - negative user-defined extrusion• NSRE - negative solid of revolution• NSRU - negative ruled surface

12.07:16


Negative Primitives have the same attributes as the corresponding positive primitives, withthe addition of the NAPP (Negative APPlies to) attribute, which controls whether thenegative primitive is removed from the item itself, or the attached or owning item. Theallowed values are:

1 - Default. See following table:

0 - Negative Primitive will not be removed from anything.1 - Negative Primitive will be removed from Attached item2 - Negative Primitive will be removed from Owner4 - Negative Primitive will be removed from the item itself7 - Negative Primitive will be removed from all items.

The positive values can be combined so that the hole will be created in more than one item.For example, NAPP=6 means that the volume will be removed from the item itself and theitem’s owner.

The following table shows what Attached and Owner mean for items that can referencedNGMSEs.

For example, if a SUBJoint references a NGMSE which contains an NSBOX with NAPP=1,the NSBOX will be removed from the Subjoint’s attached Section.

Item Remove from

PJOInt Attached SCTN or GENSEC

SJOInt Attached SCTN or GENSEC

SUBJoint Attached SCTN or GENSEC

SCOJoint Owning PANEl

PFITting Owning PANEl

COFItting Owning PANEl

FITTing Owning SCTN

FIXIng Owning GENSEC

Item Attached Owner

PJOInt Attached SCTN or GENSEC -

SJOInt Attached SCTN or GENSEC Owning SCTN or GENSEC

SUBJoint - Owning PCOJ/SCOJ

SCOJoint - Owning SCTN or GENSEC

PFITting - Owning PANEl

COFItting - Owning PANEl

FITTing - Owning SCTN

FIXIng - Owning GENSEC

12.07:17


7.6 Structural Geomsets (GMSSET)A GMSSET is a grouping of 2D primitive elements used to make up structural Profiles. Itspecifies the dimensions, orientation and obstruction geometry of each primitive. TheGeomset defines the symbol that is drawn for a particular Component by PARAGON (andDESIGN) and also defines the obstruction geometry of the Component for use when clashchecking. Each symbol is built up from a combination of the following three types ofprimitive:

• SREC - rectangle• SANN - annulus• SPRO - user-defined profile

Like the member elements of a 3D Geomset, each member element of a StructuralGeomset has LEVEL, CLFLA, TUFLA and OBST attributes.

Note: For correct clash detection, the maximum number of primitives with OBST set to 1 or2 in any GMSSET is 20; the order of these in the members list is not important. Seethe DESIGN Reference Manual for details of the best way of setting up Componentdata so as to minimise processing time for clash detection.

The primitives have additional attributes as described in the next section.

7.7 Structural Geomset PrimitivesThe following primitive elements are used by Structural Geomsets. They all have thestandard attributes and the common attributes LEVEL, CLFLA, TUFLA and OBST. Theadditional particular attributes of each element are as described below.

Note that each 2D primitive has effectively two types of positional attributes which allow itsgeometry to be changed progressively as it is extruded in space to create a 3D designelement (such as a structural SCTN or GENSEC element). The P... attributes define thegeometry at the Start of an extruded section, while the D... attributes define the change inthat geometry between the Start and End of the extruded section.

7.7.1 Structural Rectangle (SREC)SREC has particular attributes as follows:

• PXLE, PYLE - rectangle dimensions in X, Y directions• DXLE, DYLE - difference in rectangle dimensions in X, Y directions for tapered sections• PX, PY - coordinates of centre of rectangle • DX, Dy - offset of coordinates of centre of rectangle between ends of section• PLAXI - direction of Y axis of rectangle

12.07:18


Figure 7:17. SREC Catalogue Primitive

7.7.2 Structural Annulus (SANN)SANN has particular attributes as follows:

• PX, PY - coordinates of centre of annulus• DX, DY - offset of coordinates of centre of annulus between ends of section• PRAD - external radius• DRAD - change of external radius between ends of section• PWID - width of annulus• DWID - change of width between ends of section• PANG - angle subtended by annulus• PLAXI - start angle

Note: PANG must be in the range -180_ to +180_. Positive angles are anticlockwise whenthe primitive is viewed in the -Z direction.

12.07:19


Figure 7:18. SANN Catalogue Primitive

7.7.3 Structural Profile (SPRO)This element represents a user-defined 2D shape whose outline is defined by a set ofmember elements called Structural Profile Vertices (SPVE). The lines joining adjacentSPVEs form the edges of the SPRO.

In addition to the attributes defining its position, each SPVE can have a radius which appliesa convex or concave fillet to the profile at that point.

SPRO has particular attributes as follows:• PLAXI - direction of Y axis of profile (this defines coordinate system for SPVEs)

SPVE has particular attributes as follows:• PX, PY - coordinates of vertex• DX, DY - offset of coordinates between start and end of a tapered section• PRAD - fillet radius of profile at vertex position• DRAD - change of fillet radius of profile at vertex position between ends of section

12.07:20


Figure 7:19. SPRO and SPVE Catalogue Primitives

7.8 Detailing TextDetailing Text (SDTE) elements contain descriptive text relating to a Component, which isused during the construction of drawings, reports, take-off sheets etc. An SDTE elementexists 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 theSpecification.

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 attributesRTEX, STEX or TTEX. The text is input simply by typing the attribute name followed by thetext 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 tobe used will be specified from that module. The format of the text depends on the detailingmodule in use - see the appropriate Reference Guide for details.

RTEX is used by ISODRAFT, which also uses another SDTE attribute, SKEY. SKEY is afour-character code which represents a geometric description of the associated Componenttype. RTEX and SKEY must be set in order for ISODRAFT to work correctly. A typical pair ofcommands would be:

RTEX ’COUPLING - SOCKET WELD 3000LB’SKEY ’COSW’

(The SKEY codes are fixed for a given element type - see the ISODRAFT Reference Guidefor a list.)

12.07:21


7.9 Material TextMaterial Text (SMTE) elements contain descriptive text describing the material(s) fromwhich the physical component is constructed, and is used during the construction ofdrawings, reports, take-off sheets etc. An SMTE element exists at the same level in theCatalogue database hierarchy as a Component element (i.e. it is a member of a Section orCategory) 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 attributesXTEX, YTEX or ZTEX. The text is input simply by typing the attribute name followed by thetext 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.

7.10 Connection Compatibility TablesThe Connection Compatibility Table (element name CCTA) holds a list of all the compatibleconnection types for Piping Components in a set project. A CCTA is an administrativeelement which exists at the same level as CATA in the hierarchy. A CCTA has ConnectionCompatibility (COCO) elements as its members, each of which has a pair of codedconnection types stored as its CTYPE attribute. These connection types are those referredto 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.

Note: That ISODRAFT uses the connection codes to derive bolting requirements, and sothe connection codes used must conform to certain standards - see Appendix B andthe ISODRAFT Reference Guide for details. Setting up the Connection CompatibilityTable should be one of the first tasks to be carried out when commencing a designproject using PDMS.

If an attempt is made to connect two pipework components in DESIGN, then a check ismade to see if the p-leave PCON attribute of the first component and the p-arrive PCONattribute of the second component appear as a matching pair in the connection table. Ifthere is such a matching pair then the components are connected, otherwise a similar checkis 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 foundthen an ‘incompatible connection type’ error message is output and the second componentis left in its original position and orientation.

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)

12.07:22


7.10.1 COCDES ElementsCOCDES provide the means of associating a long description to a COCO pair.

Create a COCDES element below a CCTA as follows:

NEW COCDESDESC 'This is a long description of a COCO element'COCONNECTION FBB

7.11 Bolting TablesThe Bolt Table hierarchy contains information describing the nature of the boltedconnections of Piping Components in a project. Although the Bolt Table is part of theCatalogue database, and so must be set up using PARAGON, it has been designed for theexclusive use of ISODRAFT and so is described in detail in the ISODRAFT ReferenceGuide; only a summary is presented here. Element creation and attribute setting is done inthe usual way.

The Bolt Table hierarchy is illustrated below:

The element types are as follows:

• BTSE - the Bolt Set is the administrative element for catalogue component boltinginformation. It owns Bolt P-point (BLTP) elements.

• BLTP - the Bolt P-point stores the bolting information for an individual bolt for aparticular type of flange. It has the following attributes:

• BLTA - the Bolt Table is an administrative element.

• BLIS - the Bolt List is an administrative element which groups together Standard Bolt(SBOL) elements.

NUMBER - the bolt hole number in the bolt circle

BDIA - the bolt diameter

BTHK - the bolt length

BTYPE - the type of bolt

12.07:23


• SBOL - the Standard Bolt element. This has the attributes:

• LTAB - the Length Table holds a number of Diameter Tables.

• DTAB - the Diameter Table stores information on standard bolt lengths, held as astring of values in its BLEN attribute. DTAB is accessed from the NSTD attribute of theSBOL element.

7.12 Branch Reducer and Nominal Bore Size TablesThe TABWLD element is a top level administrative element providing the following tablestructures.

Nominal Bore Size Tables are created with the following element types:

A Branch/Reducer tables uses the following elements:

NSTD - a pointer to a non-standard length array

BITEM - additional bolt items to be used when calculating bolt length

BITL - the lengths of the additional bolt items

NOMTAB - is the administrative element for nominal Size Range Table

SNOTAB - nominal bores in mm are stored in a element

SNOTAB - the wall thickness of a bore is recorded in this element

BRTAB - A Purpose attribute controls the underlying table purpose suchas Branch/Reducer

SBRTAB - Contains the bore size 'from part'

SSBRTA - Contains the bore size 'to part'

12.07:24


7.13 Unit TypesPARAGON enables unit types to be set up which will then be linked to relevant attributes ofthe various elements which appear throughout the PDMS databases. The most commonunits (the default units) are millimetres, inches or feet and inches, which are usuallyassigned to bore and distance attributes. These units currently apply to all PDMS modulesexcept 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. TheUNITS hierarchy is shown below:

The elements of the UNITS hierarchy are as follows:

• UNIT - The UNIT element is the top-level element of the hierarchy. It has three specialattributes: BUNI, DUNI and DFUN. BUNI and DUNI can be set to determine the defaultBore and Distance units, respectively. They are set to any of MM, INCH, MIL or FINC(for feet and inches). A typical sequence of setup commands would be:

NEW UNITBUNI INCHDUNI FINC

This would mean that, by default, all bore values are interpreted as inches and alldistance values, e.g. HEIGHT, DISTANCE, as feet and inches. If user-defined units areto be used, then an MSET element should be named in the DFUN attribute of the UNIT,indicating that MSET element should be used as the default measurement set. EachPDMS module has its default units initialised at run time to those defined in the firstUNIT element of the first Catalogue DB in the MDB being used. BUNI and DUNI mayalso be set to NULL.

• MSET - Measurement Set. This element is used to form a collection of MTYP(measurement type) elements. It is the MSET which is named in the DFUN attribute ofthe UNIT element to indicate which collection of units are to be used. In practice MSETmay relate to say ‘S.I.’ or ‘IMPERIAL’.

• MTYP - Measurement Type. This element forms the link between a collection ofattributes and the Units Definition (UDEF) to be used for them. The attributes areaccessed via the ATLI (Attribute List) elements owned by the MTYP and the UnitsDefinition via its UREF attribute. The latter simply contains the name of the UDEFelement 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 ofthe attribute for which the UREF (see above) applies.

12.07:25


• USEC - Unit Section. This is an administrative element used to collect together UDEFelements.

• UDEF - Units Definition. One UDEF is required for each non-PDMS unit that you wishto implement. UDEF has the following special attributes:

• ABREV - Abbreviation. This is the abbreviation used when outputting a valueunder the control of this UDEF, or when inputting a value which is in a UNIT that isnot the one for that attribute in the current MSET. The attribute is an eight-charactertext.

• MULT - Multiplier. This is a conversion factor which is used in conjunction withADEN, to convert from input/output units to PDMS stored units. This is done on thebasis that:

The exponential facility is useful in the accurate setting of MULT and ADEN. Forexample:

MULT 0.12345 EX -8

will set MULT to 0.0000000012345

• ADEN - see MULT above.

• SIGF and DECP - Significant Figures and Decimal Places. These relate to theoutput of units.To summarise, the unit is defined as:(input_value * MULT ) + ADENand is output to SIG significant figures with DEC decimal places and suffixed by thenotation ABREV ( e.g. ‘psi’).

7.13.1 Use of UnitsIn certain PDMS modules, e.g. PROPCON, the choice of units to be used can be indicatedby using the command:

UNITS name

where name is the name of an MSET. If this is not done, the units will be those given by theDFUN attribute of the UNIT element, as explained above.

Following this, whenever the value of a special attribute is set or queried, its name (e.g.TEMP for temperature) will be compared with the ATNA attributes of all ATLIs under thecurrent MSET. If a match is found, then the UREF of the MTYP owning the matching ATLIwill be used to access the relevant UDEF.

When output, such values are followed by their abbreviations to remind you which units arebeing used.

If you wish to input a value which is in a UDEF that is not referred to from the current MSET,then you may use the abbreviation of that value as a key. For instance, in PROPCON, if thecurrent temperature unit is centigrade, but there is a UDEF defining Fahrenheit (withabbreviation ‘deg. F’), it would appear as

TEMP 35 ’deg. F’

• Output value = (Stored value - ADEN) / MULT

• Stored value = (Input value * MULT) + ADEN

12.07:26


As an example, if you require a PROPCON attribute ACBO (Actual Bore) to be output ininches, then the following syntax would be required:

This results in the following hierarchy:

If ACBO is referred to in PROPCON, the attribute name (ATNA) is searched for in the UNIThierarchy. The search then moves up the hierarchy to find the MTYP attribute UREF. TheMULT attribute of the UDEF (found from the UREF) is then applied to the stored ACBOattribute and the ABREV is output with the resulting value.

As a further example, to define and use a unit system called /IMPERIAL, for whichtemperatures (TEMP, PTEM and RTEM) will be in Fahrenheit and pressures (PRES, RPREand IPRE) will be in PSI, the instruction sequence would be:

NEW UNIT /EXAMPLE-OF-UNITSNEW USECNEW UDEF /PSIABRE ’lbf/in2’ ADEN 0 MULT 6895.0NEW UDEF /FABRE ’deg. F’ ADEN -17.778 MULT 0.55556NEW MSET /IMPERIALNEW MTYP /IMPERIAL/TEMPUREF /FNEW ATLI ATNA TEMPNEW ATLI ATNA PTEMNEW ATLI ATNA RTEM

NEW USEC create a new Unit Section

NEW UDEF /INCH create and name a new Units Definition

ABREV ’IN’ -set ABREV and MULT attributes

MULT 0.254 EX 2

NEW MSET create a Measurement SetNEW

MTYP create a Measurement Type

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

12.07:27


NEW MTYP /IMPERIAL/PRESSUREUREF /PSINEW ATLI ATNA IPRENEW ATLI ATNA RPRENEW ATLI ATNA PRES

Note: It is possible to set up UNIT elements with MSETs containing duplicated ATNAs. Thisis not prevented, but a warning is given on attempting to use such an MSET.

7.14 General Text ElementsA TEXT element is used to store additional information about an owning or adjacentelement. The text string itself exists as the setting of the STEX attribute of the TEXT, andcan be up to 120 characters long. It is set in the usual way; for example

STEX ’High pressure pipeline’

Note that the STEX attribute of a TEXT element is completely independent of the STEXattributes of the Detailing Text (SDTE) elements described in Detailing Text. The TEXTelement can occupy many positions in the hierarchy - it can be owned by UNIT, CATA,SECT, CATE, STSE, STCA, CCTA, SPEC, BLTA, BLIS, LTAB or MBLI elements.

7.15 User-defined Nominal DimensionsFor users who required bores, bolt diameters and lengths, and rod diameters that are notincluded in the standard nominal values stored in core, a facility exists for the creation oftables that hold the required values in the catalogue database.

When being switched from module to module, the catalogue database is scanned for aNBRWLD element with the PURP attribute set to BORE indicating that user-defined nominalbores 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, amacro of standard PDMS bores is provided (nominal_bore.mac), which enables a user toedit the values concerned and then input the User-defined Nominal Bore table into thecatalogue.

Bolts

When there is a need to use a bolting catalogue with both Imperial and Metric projects, thereis not always a direct conversion from one system to the other. For example, a ½ inch boltmay convert to a 12mm rather than a 13mm one.

To overcome the problem, User-defined Nominal Bolting tables for diameter and length canbe set up, as for the User-defined Nominal Bore table. The PURP attribute is set to BDIA forbolt diameters and BLEN for bolt lengths.

Rods

When rods for hangers and supports are specified, the rod diameter is related to the borediameter. It is, therefore, necessary to have User-defined Nominal Rod Diameter tables, ifUser-defined Nominal bores are being used.

12.07:28


If a hanger connects to a branch with different bores, the rod diameter is selected to matchthe branch with the User-defined Nominal bore or, if this applies to neither branch, thestandard 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

12.07:29


12.07:30

Catalogues and Specifications Reference ManualCreating Datasets in PARAGON

8 Creating Datasets in PARAGON

A Dataset (DTSE) is a collection of DATA elements. These can be used to store any items ofcatalogue data which need to be queried directly from within the DESIGN or DRAFTmodules and which are not accessible by other means.

8.1 Attributes of DATA ElementsEach DATA element has the following special attributes:

The PPRO attribute is evaluated in response to the Q PROP... command in DESIGN orDRAFT. The parameters in the expression may not be defined until the item is added to themodel. It can include any attributes which are valid for the design element, including user-defined attributes; for example:

• ((:COST OF OWNER) * :LENGT).

The PPRO attribute can also be set to a parameterised expression which will be used in thedefinition of Pointsets and Geomsets. See Controlling the Detailed Checking Procedure.

DKEY Data Key. A PDMS word which allows a specific DATA element to bereferenced from within DESIGN or DRAFT using the Q PROP dkey command.

PTYP Property Type.

DTIT Data Title. A text string describing the property stored in the DATA.

PPRO Property. Any expression which defines a property of the item with which thedataset is associated.

DPRO Default Property Value. The value to be used if the true setting of the Propertycannot be evaluated at any time. See Controlling the Detailed CheckingProcedure.

PURP Purpose. A PDMS word showing the purpose for which the stored property isrelevant. For example, PARA (for catalogue parameters), DESP (for designparameters), DATA (for general properties).

NUMB Number. An integer which may be set to further categorise the specificproperty stored in the DATA. For example, the identifying number of a PARAMor DESPARAM.

PUNI Property Units. The units used when evaluating the Property value.

RUSE Real Property Flag. See Controlling the Detailed Checking Procedure.

12.08:1


8.2 Querying Properties in DESIGNConsider the following examples, which allow you to query two properties of thisparameterised I-beam in DESIGN:

Example 1: The depth of the beam• Datakey: DEPT• Dtitle: ’Depth of beam’• Pproperty: (PARAM [1] )• Dproperty: 600• Purpose: DATA• Number: 1

The command Q PROP DEPT in DESIGN or DRAFT will return the depth of the currentbeam (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 moreclearly. 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

• Q PRDE XSEC Data description

• Q PRPU XSEC Data purpose

12.08:2


8.3 Real Properties of P-points, P-Lines and GeomsetsPointset and Geomset attributes can be defined in terms of a Dataset pseudo-attributeRPROP (Real Property). For example, the PBORE of a P-point can be defined by theexpression:

PBORE ( PARAM[1] + 20 )

If the dataset associated with the component contains a DATA element with the DatakeyDBOR, and DBOR has its PPRO attribute set to the expression ( PARAM[1] + 20 ), PBOREcan be defined as:

PBORE ( RPROP DBOR )

Pointset and Geomsets with attributes defined in terms of RPROPs will have their RFLGflag set to 1. Only elements with RFLG set to 1 need to be pre-evaluated when the item isadded to a model.

DATA elements have an attribute RUSE. If this attribute is set, the PROP attribute (or defaultProperty DPRO, see Controlling the Detailed Checking Procedure) cannot be set to a textexpression or to an expression containing the OF notation. RUSE is set (=1) and unset (=0)using the commands:

SETRuse UNSETRuse

DATA elements with PROP attributes property which can be used as RPROPs should havetheir RUSE flags set. Only elements with RUSE set to 1 need to be pre-evaluated.

8.3.1 Default ValuesThe DATA element attribute DPRO can be used to store a default property value. When aDesign element is added to the model, the associated dataset is pre-evaluated and thedefault value used if the PPRO attribute in the Dataset unset or cannot be evaluated.

The default property value can be queried from DESIGN using the pseudo-attribute PRDE.

8.3.2 QueryingThe value of RPROP can be queried using the command:

Q RPROP datakey

This command will return the result ‘RPROP unset’ if the corresponding PPRO attributecontains a text string rather than a real value.

The default value of a text or real property value may be queried from a Design componentusing the command:

Q PRDE datakey

A list of the datakeys available at a Design item can be obtained using the command:

Q PRLS

12.08:3


12.08:4

Catalogues and Specifications Reference ManualChecking Catalogue Database Consistency using PARAGON

9 Checking Catalogue Database Consistency using PARAGON

To avoid having to transfer component design or specification errors from the Cataloguedatabase to the Design database before data inconsistencies can be detected, a facility isprovided 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.)

9.1 Initiating a Standard Data Consistency CheckThe 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 componentsreferenced via the starting element will be checked. If you start the check at componentlevel (COMP), only that component and elements below it will be checked.

(See Controlling the Detailed Checking Procedure for details of the ways in which you canmodify the default checking procedures.)

9.2 What the Checking Facility DoesThe following tests may be carried out:

At SPEC level:• Check that no question in the specification is repeated.• Check that one question in the specification is TYPE.• 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 SDTE 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, BLTREF. (The BLTREF need be set only if the connection type begins with F orL.)

12.09:1


At COMP or equivalent level:• Check that there is a valid PTREF and GMREF.• 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 usescatalogue parameters, so that if a primitive is constructed only from design andinsulation parameters, spurious warnings will be generated.

• Check that each P-point connection type exists in the COCO tables. P-points used forconstruction purposes can have connections of 0.0, NUL or NULL. The connectiontype will not be checked for validity for a specific type of component.

• Check that a P-point bore is valid for a recognised set of nominal bores. P-points usedfor construction purposes, and a P-point with connection type CLOS, can have a zerobore.

9.3 Controlling the Detailed Checking ProcedureYou can modify the effect of the CHECK command by using additional syntax so that youcan 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 aSPCO.

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.

These defaults are:• Do not check any CMPREFs.• Ignore GMREF settings for ATTA, FLAN, TUBE and BOLT.• Check nominal bores in the range 6 mm to 2150 mm.• Check all ISODRAFT-related settings.

12.09:2


To query any of the current data consistency checking settings, use the correspondingcommand format

Q TOLerance CATAlogue ...

9.4 Error MessagesError 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

C220 Gmset error: Unknown parameter integer for primitive

C230 Gmset error: Axis defined with unknown Ppointinteger for primitive

C240 Isometric error: Ppointinteger not defined

C250 Isometric error: Cannot calculate angle between Ppointinteger and Ppointinteger

C260 Isometric error: Incorrect angle between Ppointinteger and Ppointinteger. Angleis value and should be value.

12.09:3


C270 Isometric error: Incorrect angle between Ppointinteger and Ppointinteger. Theyshould not be parallel.

C280 Gmset error: primitive may be a degenerate primitive

C290 Isometric error: Ppoint1, Ppoint2 and Ppoint0 should be colinear

C300 Gmset error: primitive cannot be constructed

C310 Gmset error: Expression error for primitive

C820 SKEY not set

C830 SKEY word is used with generic type word, not word

C840 SKEY word not known. Assumed to be user defined.

12.09:4

Catalogues and Specifications Reference ManualPiping Components in PARAGON

10 Piping Components in PARAGON

You must use the following conventions for numbering the P-points of Piping Componentsso that ISODRAFT can recognise them:

• For tube components, there must only be one P-point, P1, which defines the bore andconnection 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 tailbranch) must be P1.

• For two-way components, the arrive and leave P-points must be numbered P1 andP2 (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 spindledirection 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/P2and 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 indicatedby P3. Eccentric reducers with a connection point must use P3, with a valid boreset, to indicate the connection point and must use P9, with bore unset, for orientation ofthe flat side.

• For U-bends, the P-points must be set as shown in Figure 10:1.: P-point NumberingConvention for U-bends.

Figure 10:1. P-point Numbering Convention for U-bends

See the ISODRAFT Reference Manual for further details.

12.010:1


10.1 Special Components

10.1.1 Implied TubeImplied tube is special because it only requires one ppoint and does not require a geometryset. Because tube has a default geometry set, the parameters for tube are fixed byconvention as:

Parameter 1 Nominal Bore

Parameter 2 Outside Diameter

Parameter 3 Connection Type

Parameter 4 onwards may be used for any other purpose but will not affect the geometry.

10.1.2 Mitred BendsMitred Bends are essentially piping components fabricated from tube cut at angles andwelded together. Prior to version 12.0 of PDMS, these components were cataloguecomponents with a complex geometry set. Although the bend shown appears to have asquare end, the tube lengths are calculated to the longest side of the cuts and the start andend segments are treated as part of the arrive and leave tube for material purposes. Thesetwo end parts are deemed as virtual segments in PDMS because they don't cut the pipe atP1 and P2

To enable this more intelligent use of mitred bends, a default geometry set has been built into PDMS for conventional mitred bend types. The default geometry set is used in a similarway to tube where a default geometry set is used if the component GTYP is a BEND and thegeometry reference is unset.

A bend pointset is required to define arrive and leave points with P1 and P2 defined andpositioned by either parameters or DDANGLE and DDRADIUS. The same pointset will beapplicable if it is a pulled or mitred bend.

In the design database, a BEND element now has a new attribute NCUTS which determineshow many cuts to apply to each bend. This is only used if the bend has no geometry set, soexisting bends will be unaffected. Any bends with NCUTS set to zero or less will be treatedas a pulled bend. The default value for NCUTS is 0.

Pipe Bore, Connection type and PPOINT positions are all required to enable connectionbetween components. Additionally a pipe outside diameter is required to enable thecomponent size to be determined. Like implied tube, the order in which these parametersare built is important and should be as follows:

12.010:2


Parameter 1 Nominal Bore

Parameter 2 Outside Diameter

Parameter 3 Connection Type

Parameter 4 default NCUTS

Parameter 5 onwards may be used for any other purpose but will not affect the geometry

10.1.3 How Number of Cuts (NCUTS) WorkThe values assigned to parameter 4 are important in how they apply to the design. Anypositive values of NCUTs from zero will be interpreted in the design as the number of cutsso if parameter 4 is set to 3 then the design component will have 3 cuts regardless of thesetting in DESIGN. Setting parameter 4 to 0 will mean that the bend is treated like a pulledbend and will not have any cuts available.

This means that the parameter4 setting will override any changes to the NCUTS attribute inDESIGN and the user will not be able to modify it. This is necessary so that the type ofbends to be used can be controlled via a specification and so that ISODRAFT can get thecorrect SKEY and number of cuts.

If the user wants to have fully variable cuts and freedom to re-specify NCUTS then settingparameter 4 to a negative number will result in an uncontrolled bend where the user mustspecify how many cuts to use. The maximum number of cuts per bend is 25.

10.1.4 Dynamic PPOINTSIn order to calculate dimensions and tube lengths, a set of dynamic ppoints are provided tosuit the number of cuts being used. For example on a single cut bend we would require appoint on the inside centre and outside as shown below plus extra cuts if insulation isadded.

The points are arranged with the centreline ppoint as number 10, Inside point as 11 outsidepoint as 12 and then points 13 and 14 as the inside and outside insulation pointsrespectively.

12.010:3


Because of the dynamic nature of the ppoints, the ppoint numbers are directly related toindividual cuts, multiplied by ten, so cut 1 will have five ppoints numbered from 10 to 14 andcut 2 will have five ppoints from 20 to 24. additional ppoints will be available for eachadditional cut defined by the cut number times ten with the same configuration as describedearlier.

10.1.5 Pseudo Attributes To find out if a bend is a new type of mitred bend, there is a new pseudo attribute ACTNCUto get the actual ncuts value in either the catalogue or from the design. If ACTNCU returnszero, then it is not a mitred bend.

The pseudo attributes ATLE, LTLE, TLE and FITLEN now return the maximum cut length ofthe relevant implied tube. To get the tube lengths of the individual segments and virtualsegments the following can be used.

10.1.6 Implied Geometry sets in PARAGONComponents with implied geometry sets cannot currently be visualised in PARAGON otherthan showing the pointset locations.

10.2 Naming ConventionsIt is important that certain items in the Catalogue database are named as they arereferenced from other databases as well as internally. It would be impracticable to allowsystem-generated database reference numbers to be referenced as this would lead tomeaningless output from reports and isometrics.

Figure 10:2.: Design, Specification and Catalogue databases shows the relationshipbetween the Design, Specification, and Catalogue databases. Consistency when namingitems is important, making cross-database connections as easily identifiable as possible.

In ISODRAFT, bolt lengths for Piping Components are derived by referring to the SBOLname. Item detail is picked up from the RTEX attribute of the DTEX and the material ispicked up from the XTEX attribute of the MTEX.

Note that the item code name on an isometric is obtained from the second part of theSPREF attribute of a Component, i.e. its name in the Specification. In the example in Figure10:2.: Design, Specification and Catalogue databases, the name would be output asFLANWN300100. See the ISODRAFT Reference Manual for further details.

BSCLL Bend Segment Centre-Line Length

BSMXL Bend Segment MaXimum Length

BSMNL Bend Segment MiNimum Length

BVSCLL Bend Virtual Segment Centre-Line Length

BVSMXL Bend Virtual Segment MaXimum Length

BVSMNL Bend Virtual Segment MiNimum Length

12.010:4


10.3 Example Connection Type CodesNaming 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 forworking out bolting details. The rules for ISODRAFT are as follows:

• The first letter of the PCON attribute of a flange must be ‘F’ or ‘L’ (the latter for lapjoints)

• The first letter of the PCON attribute of a gasket must be ‘G’• The first letter of the PCON attribute of a wafer fitting must be ‘W’

The list below is not exhaustive and only shows example codes - it is not mandatory.

Figure 10:2. Design, Specification and Catalogue databases

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

12.010:5


10.4 Connection Compatibility TableThe table in the previous section can be used to construct a PDMS ConnectionCompatibility 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 ismade to see if the p-leave PCON attribute of the first component and the p-arrive PCONattribute of the second component appear as a matching pair in the connection table. Ifthere is such a matching pair then the components are connected, otherwise a similar checkis 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 foundthen an ‘incompatible connection type’ error message is output and the second componentis left in its original position and orientation.

The following sample connection table uses the connection list given in the previoussection:

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 allowableconnections are easily queried.

The above table shows, for example, that tube can be connected to a screwed femaleconnection but not to a screwed male connection.

Different ratings of flanges and gaskets should have different connection attributes toensure that different pressure fittings cannot be connected without a warning messagebeing issued. This principle also applies to different flange face characteristics, e.g. flat faceand raised face: however, there are some exceptions. On some jobs a flat-faced flange ona piece of equipment may be butted up to a raised-face flange. If this is a commonoccurrence, it may be worth inputting a new COCO to allow the connection.

12.010:6


10.5 Construction of Typical Piping ComponentsThis section gives sample macros for the construction of typical Catalogue PipingComponents using PARAGON.

Each macro starts at CATEGORY level. The view parameters used to produce the drawingsshown vary between each example, and so are not given here. Each drawing hasREPRESENTATION settings of TUBE ON CENTRELINE ON PPOINTS ON NUMBERSON. Some of the Components are too large to fit onto a typical view area when drawn at thedefault SCALE value of 1. Values of 0.5 are suggested for examples 1 and 3, and 0.05 forexample 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 havebeen combined.

Figure 10:3. A Control Valve, using the SDSH primitive

NEW PTSE /CVMWPSNEW GMSE /CVMWGSNEW SCOM /CVMWGTYP INST PARA 25 100 133 17.5 FLGDPTRE /CVMWPSGMRE /CVMWGSMODEL CEGOTO PTRENEW PTAXPCON (PARAM[5]) NUMB 1 PBOR (PARAM[1])PDIS (PARAM[2]) PAXI -YNEW PTAXPCON (PARAM[5]) NUMB 2 PBOR (PARAM[1])PDIS (PARAM[2]) PAXI YNEW PTAXPCON NULL NUM 3 PBOR 0 PDIS (2.50 * PARAM[4]) PAXI X

12.010:7


/CVMWGOTO GMRENEW SCYLPDIS (PARAM[2]) PHEI (-2 * PARAM[2]) PDIA (PARAM[3]) PAXI YNEW SCYLPDIS 0 PHEI (2.5 * PARAM[2]) PDIA (1.6 * PARAM[2]) PAXI XNEW SSPHOBST 0 CLFL TRUE TUFL TRUE PDIS 0 PAXI -Y PDIA (0.50 * PARAM[1])NEW SCON OBST 0 CLFL TRUE TUFL TRUE PDIS (2.5 * PARAM[2]) PDIA (1.6 * PARAM[2])PAXI X NEW SDSH CLFL TRUE TUFL TRUE PDIA (1.6 * PARAM[2]) PHEI (0.8 * PARAM[2])PDIS (2.5 * PARAM[2]) PAXI XNEW SCYL OBST 0 TUFL TRUE PDIS (PARAM[2]) PHEI (-1 * PARAM[4])PDIA (PARAM[3] + IPARAM[1]) PAXI -YNEW SCYL COPY PREV PAXI YOBST 0 TUFL TRUE PDIS (PARAM[2]) PHEI (-1.0 * PARAM[4])PDIA (PARAM[3] + IPARAM[1]) PAXI YNEW LSNO OBST 0 TUFL TRUE PTDI (PARAM[2] - PARAM[4]) PBDI 0PTDM (PARAM[3] + IPARAM[1]) PBDM (1 + IPARAM[1])PAAX -Y PBAX Z NEW LSNO COPY PREV PAAX Y NEW LSNO OBST 0 CLFL TRUE PTDI (PARAM[2]) PBDI 0PTDM (PARAM[3] + IPARAM[1]) PBDM (1 + IPARAM[1])PAAX -Y PBAX ZNEW LSNO COPY PREV PAAX Y$.

12.010:8


Figure 10:4. An Unequal Tee

NEW PTSE /MWTPTSET NEW GMSE /MWTGMSET NEW SCOM /MWNEQTEE GTYP TEE PARA 100 80 114 90 BWD 105 80 15 10 PTRE /MWTPTSET GMRE /MWTGMSET MODEL CE GOTO PTRE NEW PTAX PCON (PARAM[5]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[6]) PAXI -Y NEW PTAX COPY PREV PAXI Y NUM 2 NEW PTAX PCON (PARAM[5]) NUMB 3 PBOR (PARAM[2]) PDIS (PARAM[7]) PAXI X /MWNEQTEE GOTO GMRE NEW LINE OBST 0 CLFL TRUE P1 P2 NEW LINE OBST 0 CLFL TRUE P3 P0 NEW SSPH OBST 0 CLFL TRUE PDIS 0 PAXI P1 PDIA (PARAM[8]) NEW SSPH COPY PREV PAXI P2 NEW SSPH OBST 0 CLFL TRUE LEVE 0 2 PDIS 0 PAXI P3 PDIA (PARAM[9]) NEW SCYL TUFL TRUE PDIS 0 PHEI (-2 * PARAM[6]) PDIA (PARAM[3]) PAXI P1 NEW SCYL TUFL TRUE PDIS 0 PHEI (PARAM[7]) PDIA (PARAM[4]) PAXI X END $.

12.010:9


Figure 10:5. A Weld Neck Flange

NEW PTSE /MWFLPS NEW GMSE /MWFLGS NEW SCOM /MWWNFLAN GTYP FLAN PARA 100 114 254 30 56 180 TUB FLGD 20 PTRE /MWFLPS GMRE /MWFLGS MODEL CE GOTO PTRE NEW PTAX PCON (PARAM[8]) NUMB 1 PBOR (PARAM[1]) PDIS 0 PAXI -Y 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 $.

12.010:10


Figure 10:6. A Concentric Reducer

NEW PTSE /MWRPTSET NEW GMSE /MWRGMSET NEW SCOM /MWCR2 GTYP REDU PARA 100 80 110 90 102 0 BWD 15 10 PTRE /MWRPTSET GMRE /MWRGMSET MODEL CE GOTO PTRE NEW PTAX NUMB 1 PCON (PARAM[7]) PBOR (PARAM[1]) PDIS 0 PAXI -Y NEW PTCA NUMB 2 PCON (PARAM[7]) PBOR (PARAM[2]) PX 0 PY (PARAM[5]) PZ (-1 * PARAM[6]) NEW PTAX NUMB 3 PDIS 0 PAXI -Z /MWCR2 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 $.

12.010:11


Figure 10:7. An Elbow

NEW PTSE /MWPS35 NEW GMSE /MWGS34 NEW SCOM /MWEL5 GTYP ELBO PARA 50 60 25 75 15 SWF PTRE /MWPS35 GMRE /MWGS34 MODEL CE GOTO PTRE NEW PTAX PCON (PARAM[6]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[3]) PAXI -Y NEW PTAX PCON (PARAM[6]) NUMB 2 PBOR (PARAM[1]) PDIS (PARAM[3]) PAXI Y 45 X /MWEL5 GOTO GMRE NEW LINE OBST 0 CLFL TRUE P1 T0 P2 NEW SCTO TUFL TRUE PAAX P1 PBAX P2 PDIA (PARAM[2] + IPARAM[1]) 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 $.

12.010:12


Figure 10:8. A Mitred Elbow, using SSLC Primitives

NEW PTSE /MWPTESTC1 NEW GMSE /MWGTESTC1 NEW SCOM /MWLOBST-51 GTYP ELBO PARA 500 2000 398.7 -550 -152.2 -1234.6 -585.5 BWDN PTRE /MWPTESTC1 GMRE /MWGTESTC1 MODEL CE GOTO PTRE NEW PTAX PCON (PARAM[8]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[2]) 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 $.

12.010:13


Figure 10:9. A Rectangular Cross Section Pipe, using BOXI primitives

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 PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 250 PAXI Z END OF END NEW PTSE /PWELD NEW PTAX PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 0 PAXI Y END NEW PTAX PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 0 PAXI -Y END OF END NEW GMSE /GWELD NEW SSPH CLFL TRUE TUFL TRUE PAXI P1 PDIA (PARAM[2]) END OF END NEW SCOM /BOX100 GTYP TUBE PARA 300100 100 300 END OLD SCOM /BOX100

12.010:14


PTRE PTSE /PBOXI2 GMRE GMSE /GBOXI2 NEW SCOM /HELBO100 GTYP ELBO PARA 300100 300 100 END OLD SCOM /HELBO100 PTRE /PELBO GMRE /GELBO NEW SCOM /VELBO100 GTYP ELBO PARA 300100 100 300 END OLD SCOM /VELBO100 PTRE /PVELBO GMRE /GELBO NEW SCOM /BWELD100 GTYP WELD PARA 300100 200 END OLD SCOM /BWELD100 PTRE /PWELD GMRE /GWELD

SPECON Macro:NEW SPECIFICATION /BOXI.SPEC

MATREF =0 FLUREF =0 RATING 0.000 LINETYPE NULHEADING

TYPE NAME PBOR0 CATREF DETAIL MATXT CMPREF BLTREF TUBE */D300X100 300100.0 /BOX101 =0 =0 =0 =0HEADING 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 =0HEADING 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 alreadyexists in your database.

12.010:15


12.010:16

Catalogues and Specifications Reference ManualSpecification Constructor

11 Specification Constructor

SPECON, the Specification Constructor, is used to create or modify the Specification(SPEC) elements in Catalogue Databases.

These Specifications govern the choice of components from the catalogue. They must havebeen set up, together with the rest of the Catalogue DB, before design work takes place. Inprinciple, therefore, SPECONMODE within PARAGON will be one of the first modules to beused when a new PDMS project is initiated, although in practice it is likely that a company-wide library of Catalogues and Specifications will be created independently of any individualdesign project and accessed by subsequent users to ensure overall standardisation andquality control.

SPECON enables you to input new Specifications, to modify existing Specifications, and tooutput Specifications to your terminal or to a file (to be printed or input again at a later date).

A facility is provided so that you can make changes to a Specification without losingcompatibility between existing design data and earlier versions of that Specification. This isachieved by maintaining valid references to obsolescent components in the Specificationwhile preventing their selection in new designs.

The part of the hierarchy below a Catalogue element which is relevant when consideringSpecifications is shown in Figure 11:1.: Part of the structure of a CATA element. (Theoptions CATE, STCAT and TEXT have been omitted; see Catalogue Database Structure fora fuller explanation.)

Figure 11:1. Part of the structure of a CATA element

12.011:1


The functions of the individual types of element are as follows:

11.1 Content and Format of a SpecificationThe component Specifications, which define the availability of components for particulartypes of use, are held in the SPWLD (Specification World) Elements of the Catalogue DB.These elements, which are at the same hierarchic level as the CATA elements, can own thesimple hierarchy of elements shown in Figure 11:2.: The structure of a SPWLD element.

Figure 11:2. The structure of a SPWLD element

A SPEC is equivalent to an engineering specification for a given class of piping or structuralcomponent. It may contain all components of a given material, for example carbon steel, orall components for a given class of use, for example all piping components with a particularpressure rating. Such a SPEC comprises tabulated data of the type illustrated in Figure11:3.: Part of a typical Specification for piping components, where each headed ‘question’column represents a SELEC and each horizontal row represents an SPCOM.

SECT Piping Section and Structural Section elements are administrativeSTSECT subdivisions of the owning CATA element.

COMP Component elements hold the definitions of piping components. Thesedefinitions comprise pointers to GMSET (Geomset) and PTSET (Pointset)elements, plus lists of parameters which specify the exact type, size andgeometry of each component (that is, the component’s Attributes, includingits GTYPE).

PROF Profile, Joint and Fitting elements hold the definitions of corresponding

JOIN structural components. These definitions comprise pointers to GMSET,FITT GMSSET, PTSET and PTSSET elements, plus lists of specificattributes, in a similar way to COMP elements.

DTEXT Detailing Text elements hold text which may be used to describecomponents in schedules and on isometrics. (They also hold the SKEYswhich define the symbols used to represent components in isometricdrawings; see the PDMS ISODRAFT Reference Manual.)

MTEXT Material Text elements hold text which may be used to describe thematerials of construction of the components.

12.011:2


It is possible to allocate a default value to most SELEC options, to be used if that particularattribute is not defined during the selection process. The default setting is shown in thetabulated SPEC immediately below the corresponding column heading (the SELECelement) for that attribute.

Note: Default values are not allowed for NAME or TYPE, or for reference pointers such asCATREF and DETAIL.

It is also possible to define overall specification pointers and settings which apply to thewhole SPEC, not just to individual SPCOMs. These are shown at the top of the SPEClisting, before the Heading, as shown by the entries MATREF, FLUREF, RATING andLINETYPE in Figure 11:3.: Part of a typical Specification for piping components.

The meanings of the various parts of the Specification, and lists of valid attributes(corresponding to the column headings) which apply to particular types of componentspecification, are detailed in Typical Specifications.

Figure 11:3. Part of a typical Specification for piping components

12.011:3


11.2 How Component Selection WorksThis section explains how the tabulated Specification (SPEC) data is used to choose anappropriate piping component from the complete catalogue. Similar principles apply tostructural components and equipment nozzles, although for these you may also use thecatalogue without a Specification.

The SELEC elements are generated automatically from the tabular SPECON input for agiven SPEC and hold all information about those attributes of a component which determineits availability for a given purpose. For any given set of design criteria, the route through theSELECtors follows a ‘question and answer’ sequence to determine which SPCOM issuitable. Each question relates to a specific item in the specification and each answer leadsto the next relevant question in a logical progression. Any given combination of answersshould correspond to one, and only one, SPCOM.

The types of information considered at the SELEC decision points for PDMS pipingcomponents might include:

• Generic type; for example, BEND, TEE, VALV etc.• Bore(s)• Angle(s) between multiple inlets/outlets and so on.

In addition to these specifying attributes, each SPCOM contains a pointer to a COMP, whichmeets all the listed specifications, in a CATA element. It is this pointer, known as theCatalogue Reference (CATREF), which forms the key to correct component selectionwhen new pipework is being designed.

Each SPCOM also contains pointers to detailing text (DETAIL points to DTEXT), materialtext (MATXT points to MTEXT), bolting requirements (BLTREF points to BLTAB),component properties (CMPREF points to CMPT in a Properties DB) and partrequirements (PRTREF).

There are two essential links which ensure that an appropriate component is selectedduring the design of new pipework or a new structure, namely:

• Design Component to Specification• Specification to Catalogue Component

Thus, when a new pipe component is to be selected for inclusion in a Design DB, thefollowing sequence is applied:

• The design component is allocated a Specification Reference (SPREF) which isselected from the required SPEC. You usually define the Pipe Specification (PSPEC)as soon as you create a new pipe, and this is then applied to all components which thePipe owns unless you override it.

• The SPREF points to an SPCOM (in the Catalogue DB).• The SPCOM points to a suitable catalogue component (COMP) via the CATREF

pointer.

(The SPCOM also points to a DTEXT via the DETAIL pointer, an MTEXT via the MATXTpointer, a BLTAB element via the BLTREF pointer, and a CMPT element in a Properties DBvia the CMPREF pointer, as appropriate.) This is illustrated below.

12.011:4


Figure 11:4. The links between Design Data, Specifications and Catalogue

EXAMPLE:

As an illustration of the principles of the selection process, consider the following questionand answer sequence which might apply when choosing a valve from the /RF300Specification represented in Figure 11:3.: Part of a typical Specification for pipingcomponents:

SELEC_1 TYPE?

Answer VALV, which leads to the next question ...

SELEC_2 PBOR0?

Answer 25.0, which leads to a choice of three STYPs

SELEC_3 STYP?

Answer GA, which in this example offers only one choice for SHOP

SELEC_4 SHOP?

Answer TRUE

The resulting combination of SELEC answers, namely a 25mm bore Gate Valve with itsSHOP attribute set to TRUE, is represented in the SPEC by one, and only one, SPCOM,namely */25GA. This points to the component in the Catalogue which completely matchesthe specification, via the CATREF /VGAFF. The corresponding descriptive DTEXT is pointedto by the DETAIL /DGA.V.SW, and so on. Note that the CATREF is unique within this SPEC,whereas the same DETAIL applies to other components such as */20GA.

PIPECOMPONENT

SPREF

SPECCOMPONENT

DETAILMATXT

DTEXT

MTEXT

(SPCOM)(PSPEC)

COMP

CATREF

BLTREF

BLTAB

CATALOGUESPECIFICATIONSDESIGN DATA

CMPREF

CMPT(PROPS DB)

viaSELECs

12.011:5


12.011:6

Catalogues and Specifications Reference ManualManipulating the Catalogue Database using SPECONMODE

12 Manipulating the Catalogue Database using SPECONMODE

SPECON is used for all aspects of Specification creation, modification and interrogation.This chapter explains how to carry out the following tasks:

• Create a new SPEC (Creating a Specification)• Access an existing SPEC (Accessing an Existing Specification)• Input data (SELECs and SPCOMs) to a SPEC (Entering Tabular Data)• Edit an existing SPEC (Editing an Existing Specification)• Copy an existing SPEC as the basis for a new SPEC (Copying a Specification)• Output the contents of a SPEC to a selected device (Outputting a Specification)• Use macro input techniques to simplify SPECON usage (Using Macros For SPECON

Inputs)

12.1 Creating a SpecificationIn PARAGON command line type SPECONMODE to use the SPECON command syntax.

To create a new SPEC, use one of the commands

NEW SPECification specnameNEW specname

where specname is the PDMS name which will be used to refer to the completeSpecification.

Note: The short form of the command is all that is necessary, since a SPEC is the onlyelement type which you can create at this level in SPECON (the lower level elementsSELEC and SPCOM are created indirectly when the tabular data is entered; seeEntering Tabular Data).

For example, either of the following commands:

NEW SPEC /RF300NEW /RF300

would create a new SPEC called /RF300.

To associate a descriptive text with the SPEC name, use the syntax

TEXT text

12.012:1


For example, the SPEC created in the preceding example might be given an associated textby entering the command:

TEXT ’300 psi Piping Specification’

Note: The delimiting apostrophes enclosing the text string, which must not exceed 50characters.

This text, which is stored in a TEXT element in the hierarchy, will be shown after the SPECname when the Specification is output; see Outputting a Specification.

Two system attributes on the PDMS SPECIFICATION element are used when the productVPRM is the source of PDMS Specifications.

When a specification is imported to PDMS the attributes FISSUE and FINPUTBY hold theVPRM information.

• FISSUE holds VPRM issue number• FINPUTBY holds information indicating that the source was VPRM and includes the

date of issue

The system attribute FSTATUS also holds the VPRM status of the specification, usuallyworking or approved.

For example:

Finputby |VPRM at 26-NOV-2003 12:04|

Fissue |00|

Fstatus |APPROVED|

12.2 Accessing an Existing SpecificationAccess a SPEC by using any of the following commands:

OLD SPECification specnameOLD specnameSPECification specname specname

where specname is the name of an existing SPEC.

For example, enter any of the following commands:

OLD SPEC /RF300OLD /RF300SPEC /RF300/RF300

to access the SPEC created in Creating a Specification. Clearly, the simplest method is toenter just the name of the SPEC required.

You may interrogate the SPWLD hierarchy by using the command, or change to a differentSPEC element within it by using any of the standard DB navigational commands such asFIRST, NEXT, etc., in the usual way.

12.012:2


12.3 Entering Tabular Data

12.3.1 General PrinciplesYou must have created or accessed a SPEC (as described in Creating a Specification andAccessing an Existing Specification, respectively) before you can enter tabular data.

Each Specification may contain any number of separate tables. For example, that part of theSPEC named /RF300 listed in Figure 11:3.: Part of a typical Specification for pipingcomponents contains four tables (one for each of the component types VALV, TEE, ELBOand FLAN), although the complete SPEC would probably contain many more.A tablecomprises three distinct types of data:

• A Heading (or Question Line)• Defaults• Answer Lines

The heading must be at the top of the table; the defaults, if specified, must immediatelyfollow the heading; and the answer lines (one for each SPCOM) form the remainder. Thissequence is illustrated in Figure 11:3.: Part of a typical Specification for piping components.

12.3.2 Special Characters in SPEC DataIn addition to conventional alphanumeric PDMS names and attribute values, the followingspecial characters may be used in the SPEC data entries:

• * The star or asterisk character is used throughout PDMS as an abbreviation which youcan set to the name of an owning element when naming a member element in a DBhierarchy. In most modules you must define this character by using the command, but itis set automatically by SPECON so that it always refers to the name of the currentSPEC. For example, in the SPEC named /RF300 shown in Figure 11:3.: Part of atypical Specification for piping components, the component listed as */20GA has thefull PDMS name /RF300/20GA.

• + The plus character means ditto; it enables you to repeat the setting above it in thetable with the minimum of keystrokes.

• - The minus or dash character, which may be used only in the default line of a table,means ‘not applicable’ or ‘unspecified’. If a default line is present, this character mustappear under TYPE and NAME, and under any SELEC questions for which defaultanswers are not set. It must not appear under CATREF, DETAIL, MATXT etc., for whichdefaults are never allowed.

• = The equals character, when used in the default line of a table, means that the answerwill default to the first selector in list order after all other questions have beenanswered.

As an example, consider the following part of a table (which incorporates all four of thecharacters * - + and = ):HEADINGTYPE NAME PBOR0 STYP CATREF DETAIL MATXT CMPREF BLTREFDEFAULTS- - - =

FLAN */FG 20.0 S /FSAAPAPP /20FL /ASA-20F =0 /SBOL/20FFLAN */FX + P + + /ASA-20FX =0 +...

This includes two SPCOMs which differ only in the Selector STYP (Subtype) and whichhave pointers, for the purpose of this example, to different Material Texts. When this SPECis used to select a component without specifying the required STYP, the = default option will

12.012:3


select the first SPCOM (*/FG) in the list order, which points to the MTEXT identified as /ASA-20F.

Note: The equals signs within the body of the table, in the form =0, simply show that thosepointers have not been set. They have no relevance to the equals sign in a defaultline.

Since PDMS does not allow any SPREF to exist more than once, items in a SPEC whichare identical but which need to be distinguished from each other may be allocated suffixes.ISODRAFT can be made to ignore such a suffix by recognising the delimiting characterwhich separates the suffix from the rest of the SPREF. For example, if the delimitingcharacter is defined as a colon (:), which is the default, ISODRAFT will identify twocomponents with the SPREFs /TEE.FS:AA and /TEE.FS:AB as having the same item code /TEE.FS. See the ISODRAFT Reference Manual for further details, including the way inwhich you may specify which character is to be recognised as the delimiter.

12.3.3 HeadingsThe heading line, which defines the column headings for the rest of the table, contains fourdistinct sorts of information:

• TYPE is the generic type (GTYPE) of the component represented by an SPCOM.• NAME is the unique identifier for each SPCOM.• Selector Questions define the SELEC choices which will be used to choose an

appropriate SPCOM for a given design purpose (e.g. STYPE, ANGLE etc.).• Reference Pointers link each SPCOM to the corresponding definitions in the other

parts of the Catalogue (e.g. CATREF points to a COMP, DETAIL points to a DTEXT,and so on).

(For full details of the available options for Selector Questions and Reference Pointers, seeSelectors and Pointers for Piping Components, Selectors and Pointers for StructuralComponents, or Selectors and Pointers for Insulation.)

To define a heading, use the command syntax

Heading TYpe NAme questions pointers

noting that the command is entered on two lines (i.e. you must press RETURN after thecommand HEADING, as well as after the last entry in the second heading line).

Note: When new data is entered into a Specification, the input sequence is TYPE NAME ...etc.; when an existing Specification is modified (see Editing an ExistingSpecification), or when its contents are output (see Outputting a Specification), thecorresponding sequence is NAME TYPE ... etc. Examples of possible commands fordefining headings are as follows:

For generic type TUBE -HEADINGTYPE NAME PBOR0 SCHE SHOP CATREF DETAIL MATXT CMPREF BLTREF

For generic type ELBO -HEADINGTYPE NAME PBOR0 STYP ANGL SHOP CATREF DETAIL MATXT CMPREF BLTREF

12.012:4


For generic type REDU -HEADINGTYPE NAME PBOR0 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF

For generic type BEAM -HEADINGTYPE NAME STYP GRAD DEPT WIDT WEIG INER CATREF

and so on. See Typical Specifications for explanations of the SELEC questions used inthese headings.

The maximum number of entries in a heading line (that is, the maximum number of columnsin the table) is 20.

Note: The number of columns in an existing Specification cannot be changed, so it isimportant that you choose the headings carefully when you create a newSpecification.

12.3.4 DefaultsTo define the default settings for the SELEC answers, use the command syntax

Defaultsdefault_settings

which, as with the HEADING command, occupies two input lines.

Each SELEC question column must be set to either a definite answer (value, word, etc.) orto a - or = character (as defined in Special Characters in SPEC Data). The TYPE and NAMEcolumns must have - (null) defaults and the Reference Pointer columns must have nodefault entries at all.

For example, heading and default lines for a table of VALV Specifications might be enteredas follows:

HEADINGTYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREFBLTREFDEFAULTS

- - - GATE =

Any VALV selected without specifying the STYPE (for example, by using the commandNEW VALV SEL in a design module) will have the word GATE assigned as the answer tothe SELEC question for its STYPE.

12.3.5 Selector AnswersTo complete the main area of the table, enter the TYPE and NAME, followed by anappropriate answer (value, word etc.) under each column heading, for each SPCOM line inturn. The spacing between the answers is not critical, although interpretation of the SPECtable may be easier if you align the headings and answers in vertical columns, as illustratedin Figure 11:3.: Part of a typical Specification for piping components. Note, however, that thetabulation used when data in input to a SPEC is not retained when that SPEC issubsequently output.

Remember that you can use the * and + characters, defined in Special Characters in SPECData, to save repetitive typing when entering the SPEC data from a keyboard.

12.012:5


Note: You must take care not to use any of the dimensional units (MM, M, IN, FT, FE etc.)in answers which are expected to be words. This applies particularly to the STYPESelector (see Subtype Selectors: A Special Case). If, for example, a Specificationincluded the adjacent headings PBOR0 STYPE and you entered the answers 25 forthe bore and FT for the STYPE, SPECON would interpret this as a bore of 25 feetand would try to assign the next answer or reference pointer to the STYPE.

12.3.6 Subtype Selectors: A Special CaseSubtype (STYP or equivalent) selector answers can be tabulated in either of two formats: asa PDMS word (up to four letters), or as a text string (of any length) enclosed betweenapostrophes. If you use the latter format, you must precede the text string with the wordTEXT to avoid possible confusion with user-defined dimensioning units.

For example, the STYP for a gate valve (generic type VALV) could be listed either as GATEor as the equivalent form TEXT ’GATE’. If these are to be truly equivalent, you must useuppercase characters for GATE in the text answer. Alternatively, the text version could beextended to give a more explicit description; for example, TEXT ’High Pressure Gate’.

12.3.7 Including User-defined Attributes in SpecificationsTo include the settings of user-defined attributes in a Specification, for subsequent use byISODRAFT, use the command syntax

EXTRA :uda_name attribute_setting

For example:

EXTRA :colour ’green’(where :colour is a uda of type text)EXTRA :diagonal 226.87(where :diagonal is a uda of type real)

User-defined attribute settings included in this way (one per line) will be correctly output andre-input when you list the SPEC using macros.

Note: User-defined attributes to be used in this way must have been defined in LEXICONwith SPCOMs as valid components.

12.3.8 Including Comments in SpecificationsTo include a comment in a Specification, typically to clarify details of its content for futureusers, use the command syntax

COMMENT text

All text between apostrophes following the COMMENT command will be ignored when theSPEC is interpreted, but will be correctly output and re-input when you list the SPEC usingmacros.

12.012:6


12.4 Editing an Existing Specification

12.4.1 Adding a New SPCOMTo add one or more new SPCOM lines to an existing SPEC, use the same syntax as thatdescribed in Entering Tabular Data for setting up a new SPEC; that is, enter the commandlines

HeadingTYpe NAme questions pointersDefaults(optional)default_settings(optional)selector_answers pointer_settings

The heading line ‘TYPE NAME questions pointers’ must be the same as the correspondingline in the existing SPEC. SPCOMs entered in this way will be merged into the table for therelevant component type when the SPEC is output.

12.4.2 Deleting or Removing a SPEC or SPCOMThe terminology used here is significant:

• If a SPEC or SPCOM is deleted, all aspects of it are eliminated from the Catalogue DB.If an existing design includes a component with an SPREF which points to the deleteddata, any future access to the Design DB, say to produce a drawing, will result in anerror since no matching SPCOM will be found.

• If a SPEC or SPCOM is removed, the data held within it is transferred to a specialarchive Specification named /*LIMBOSPEC. The data still exists, so that references toit are still valid, but it no longer forms part of the original named SPEC. This facility isuseful:• when a component is withdrawn from use for new designs but its continued use in

existing designs is permitted• when use of a component is to be suspended temporarily while modifications are

made.

Note: If you are using more than one Catalogue DB, there is one archive Specification foreach DB. This avoids inadvertent transfer of data between DBs due to removal andsubsequent restoration of SPECs or SPCOMs. Such multiple archive Specificationsare named /*LIMBOSPEC, /*LIMBOSPEC_1, /*LIMBOSPEC_2 etc. Only the singleform /*LIMBOSPEC will be referred to in the remainder of this manual.

To delete individual SPCOM lines from a SPEC, use the command syntax

DELETE spcom1 spcom2 ...

where spcom1, spcom2 etc. identify the relevant SPCOMs. For example,

/RF300DELETE */20GA */25GA

will access the SPEC /RF300 and delete the SPCOMs /RF300/20GA and /RF300/25GA.

To delete a complete Specification, use the command syntax

DELETE SPECification specname

12.012:7


where specname is the name of the SPEC. For example,

/RF300DELETE SPEC /RF300

will access and then delete the entire SPEC named /RF300.

To delete all SPCOMs from a SPEC without deleting the SPEC itself, enter the command

DELETE ALL

Note: The DELETE command should be used with care. No checks are made against anydesign data before the SPCOMs are deleted and any references to such SPCOMs ina Design DB will become invalid. If in doubt, use the REMOVE command.

To remove individual SPCOM lines from a SPEC, use the command syntax

REMove spcom1 spcom2 ...

where spcom1, spcom2 etc. identify the relevant SPCOMs.

The effect of this command is to remove all answers from the named SPCOM lines, exceptfor the pointers CATREF and DETAIL, and to transfer those SPCOMs to the archiveSpecification /*LIMBOSPEC. If a Specification Reference (SPREF) in a Design DB points toan SPCOM which cannot be found in the currently named SPEC, it will automatically lookfor that SPCOM in /*LIMBOSPEC.

To remove the entire contents of a SPEC, enter the command

REMove ALL

To reinstate a removed SPCOM, ensure that you are pointing to the correct current SPECand then use the syntax for modifying an SPCOM, as defined in Deleting or Removing aSPEC or SPCOM, but incorporate the name of the SPCOM to be reinstated. The SPCOMwill automatically be moved back from /*LIMBOSPEC into the original SPEC.

12.5 Copying a SpecificationIt is sometimes necessary to have two SPECs which are very similar, perhaps differing onlyin the CATREF and DETAIL pointers of their member SPCOMs. To enable you to createthese easily, SPECON allows you to make a copy of an existing SPEC which you can thenrename and edit as required. To do so, use the command syntax

COPY specname REName name1 name2

where specname identifies the complete SPEC which is to be copied and name1 andname2 define the old and new name parts, respectively, for the individual SPCOM linesthroughout the SPEC. In most cases name1 will be the same as specname.

For example, to create a new Specification /SPEC2 derived from an existing and similarSpecification /SPEC1, enter the commands

NEW SPEC /SPEC2COPY /SPEC1 RENAME /SPEC1 /SPEC2

/SPEC2 will contain exactly the same headings, default settings and SPCOM lines as /SPEC1 except that all SPCOMs which were named /SPEC1/... in the latter will have beenrenamed /SPEC2/... in the former.

You can now change any individual answers (attribute settings or pointers) in /SPEC2 byusing the editing commands described in Editing an Existing Specification.

12.012:8


12.6 Outputting a Specification

12.6.1 Defining the DestinationYou can output the content of a SPEC to your terminal or to a file (perhaps for subsequentprinting). The device to which SPECON is to send the output may be defined by using thestandard device-selection commands described in the PDMS MONITOR ReferenceManual. The default is TERMINAL.

12.6.2 Outputting Complete SpecificationsTo output one or more complete SPECs, use the command syntax

OUTput specname1 specname2 ...

For example, to send the content of Specification /RF300 to a file named /RF300.SPEC inyour current OS directory, enter the commands

FILE /RF300.SPECOUTPUT /RF300

The data will be output to the selected device in a similar tabular format to that in which itwas entered into the SPEC, although the precise tabulation settings will have been modifiedto suit the linewidth of the destination device (but see also Controlling the Output Format).

SPEC data output in this way has the same NAME TYPE ... sequence as that which applieswhen existing data is being accessed for editing; not the TYPE NAME ... sequence in whichit was entered. To output a SPEC with the heading sequence TYPE NAME ... (to be used,for example, as input at a later time; see Using Macros For SPECON Inputs), use theextended command syntax

OUTput NEW specname1 specname2

(The default version of the OUTPUT command is equivalent to OUTPUT OLD, but there isno advantage in using the longer form.)

12.6.3 Controlling the Output FormatBy default, the tabulated layout of data derived the output macro is the same as that in theoriginal SPEC. You can compact the output macro file by replacing multiple spaces by asingle space. This saves disk space, but can make the tables more difficult to read. To doso, use the command

COMPact

To restore the tabulated format with aligned columns, use the command

ALIGned

12.6.4 Outputting Parts of SpecificationsTo generate output which is restricted to one or more specified types of component, includethe generic types of the required components by using one of the syntax formats

OUTput gtype1 gtype2 ... specname1 specname2 ...OUTput OLD gtype1 gtype2 ... specname1 specname2 ...OUTput NEW gtype1 gtype2 ... specname1 specname2 ...

12.012:9


where gtype1, gtype2 etc. are the component types to be included and specname1,specname2 etc. are the Specifications from which the data is to be extracted.

For example, to create a file containing just the valve and flange data from the Specification/RF300, in a format suitable for use as input to a different Specification, you might use thecommands

FILE /SPECDATAOUTPUT NEW VALV FLAN /RF300

12.6.5 How Bores Are OutputAlthough all pipe bores are stored in the PDMS databases in mm, they may be input andoutput in either metric or imperial units. The program converts from one set of units to theother by applying the factor 25.4 mm/inch.

PDMS holds tables of standard nominal bore pipe sizes and, unless specified otherwise,compares each actual bore against the values in the appropriate (metric or imperial) table. Ifthe actual bore falls within a predefined tolerance of one of the nominal bores, it is assumedthat the standard sized pipe is suitable and so that nominal bore is output.

You may specify whether component bores within the Specification data are to be output asactual or nominal sizes by using the command syntax

BOREs ACTualBOREs NOMinal

The default is BORES NOMINAL.

Note: RADI and HEIG questions use the current Distance unit.

Nominal Pipe Size Tables contains the tables used by PDMS to define metric and imperialpipe sizes.

12.7 Using Macros For SPECON InputsWhile it is possible to create or modify SPECs and SPCOMs interactively, it is usually moreefficient to use macros for this purpose.

The tabular format of the SPECON input is easily achieved using any normal text editor andthe data file thus created can be checked for errors before it is read into the Catalogue DB.If any syntax errors are found when the macro file is run in SPECON, the file may be editedto correct the mistakes and rerun with the minimum amount of effort.

The format of the macro input file is exactly the same as that produced by the OUTPUTNEW command described in Outputting Complete Specifications; that is, TYPE mustprecede NAME in the heading and SPCOM lines. This means that Specifications whichhave been sent to a file may be edited independently of PDMS, using any available texteditor in your computer system, and then reloaded via SPECON. This is often the mosteffective way of carrying out major revisions of existing SPECs. Any part of an SPCOM linemay be changed in this way other than the NAME or TYPE; if these were changed SPECONwould not be able to locate the SPCOM to overwrite it.

Remember, when creating SPECON input macros from the keyboard, that the symbols *(automatically set to the Specification Name) and + (equivalent to ditto) can be used to saverepetitive typing (see Special Characters in SPEC Data).

12.012:10


To update an existing macro to use text strings instead of PDMS words for STYPE selectoranswers (see Subtype Selectors: A Special Case), edit the macro so that each four-character word representing an STYP (or equivalent) is replaced by the keyword TEXTfollowed by the replacement text enclosed between apostrophes. For example, you wouldreplace GATE by TEXT ’GATE’. Note that the text must be in uppercase characters if it is tobe interpreted in the same way as the equivalent PDMS word.

12.012:11


12.012:12

Catalogues and Specifications Reference ManualTypical Specifications

13 Typical Specifications

This section explains, with examples, typical data entries which might be used inSpecifications for the main types of design components (piping components, structuralcomponents and insulation).

13.1 Selectors and Pointers for Piping Components

13.1.1 ApplicabilityThe headings in this section may apply to components from the following list of GTYPEs:

ATTAchment

NOZZle

Bend OLEts

Bolt PCLamp

CAP PCOmp

CLOsure REDucer

COUpling ROD

CROSs SCLamp

DUCting SHU

Elbow TEE

FBLind TUBe

FILter TRAP

FLAnge UNIon

FLG VALve

FTUbe VENt

GASket VFWay

HELement VTWay

12.013:1


(For Insulation, see Pipework Insulation)

13.1.2 SelectorsThere are very few constraints on the SELEC questions, and the order in which you listthem, when defining SPECs for piping components. The following headings should meetmost of your requirements:

Pbore integer

Specifies the bore of p-point integer. For multiway components (such as a Tee), morethan one PBORE SELEC may be specified (PBORE1, PBORE2 etc.).

PConn integer

Specifies the connection type of p-point integer.

Note: See P-Point Zero: A Special Case for important information about the use of thespecial cases PBORE0 and PCONN0 which may be applied to the precedingSELECs.

SType

Defines the Specific Type of the component; it is effectively a subdivision of a GTYPE.For example, a component of GTYPE VALV may have an STYPE GATE, GLOB,CHEC etc.

ANGle

Defines the required angle of an ELBO or BEND, when DDANGL has been used inthe component pointset (PTSET). The answer to this SELEC question in an SPCOMmay be a single value (e.g. 90.0) or a range of values (e.g. 45.0,90.0).

RADius

Defines the required radius of an ELBO or BEND, when DDRADI has been used inthe component pointset (PTSET). May be a single value or a range.

TEMperature

Defines the operating temperature.

PRessure

Defines the operating pressure.

RATing

Defines the pressure rating.

SHOP

Defines whether the component is intended for shop fabrication (SPCOM answerTRUE or SHOP) or on-site assembly (SPCOM answer FALSE or SITE).

In addition to the standard SELEC headings, you may use any word (up to four letters), withor without a numeric qualifier, to define your own questions. For example, if you wished to

INSTrument WELD

LJSE

ATTAchment

12.013:2


include a range of colour-coded reducers in your Catalogue (perhaps having a base colourand a marker colour to indicate suitability for particular types of use), you might include thequestions COL1 and COL2 as SELEC headings in the Specification for TYPE REDU. TheSPCOMs containing the answers to these questions will be considered by the selectionprocess if the appropriate option is specified in your design module command; for example

SELECT NEW REDU ... WITH COL1 RED WITH COL2 BLUE

If COL1 and/or COL2 are omitted, the default colours (answers) will be used.

13.1.3 P-Point Zero: A Special CaseNormally, when the bore or connection type of a p-point is used as a SELEC question, theanswer provided will apply to a specific p-point number. For example, PBORE1 will be thecomponent’s arrive bore, PBORE2 will be its in-line leave bore, and so on. However, undersome circumstances this need not apply. In such cases you may use the Selectors PBORE0and/or PCONN0 to represent either the arrive or leave p-point of the component.

For example, assume that you wish to select a flange. Normally P1 would represent p-arriveand P2 would represent p-leave, so that the Selector PBORE1 could be matched againstthe p-leave bore of the preceding component to select a suitable flange. If, however, theflange is reversed (‘flipped’), P2 becomes the p-arrive and so a Specification based on theSelector PBORE1 will not allocate a correct match.

If the SELEC is defined as PBORE0, all p-points of the new component will be tested, innumeric order, against the p-leave of the preceding component. Thus, in the case of ourflipped flange, if a P1 match cannot be found then P2 will be tested as a second choice. Ifeither P1 or P2 matches the answer given for PBORE0, then a flange will be selected.

The same principle applies to the connector type PCONN0.

You will find the P-point Zero convention very useful when compiling Specifications. Figure11:3.: Part of a typical Specification for piping components, for example, illustrates the useof PBORE0 (abbreviated to PBOR0) for four component types.

13.1.4 Reference Pointers and SettingsThe following reference pointers and settings are applicable to the specification of pipingcomponents (see the examples below).

Individual Specification Component Pointers

These pointers, which are attributes of SPCOM elements, are set individually for each line ina Specification table. Only the CATREF pointer is obligatory; the other pointers may beomitted from the heading when the Specification is created or they may be left as unset (=0)in individual SPCOM lines.

CATREF - Catalogue Reference:

Points to one particular component in the Catalogue DB which meets all the SELECrequirements specified for an individual SPCOM. A CATREF heading is obligatory for everySPEC table since it is the essential link between the design specification and the choice of acomponent from the Catalogue. It is important that the component pointed to by theCATREF already exists when the SPCOM is defined, otherwise you will receive the errormessage ‘Undefined Name’ and the CATREF in the Specification will be shown as =0 (i.e.unset).

12.013:3


DETAIL - Detail Text:

Points to a DTEXT element in the Catalogue DB. This holds any general text which isused to describe the corresponding component in schedules, on isometric drawings,etc. (see Catalogue Database Structure).

MATXT - Material Text:

Points to an MTEXT element in the Catalogue DB. This holds the text which is used todescribe the materials of construction of the corresponding component in schedules,on isometric drawings, etc. (see Component Parts and the ISODRAFT ReferenceManual).

BLTREF - Bolt Reference:

Points to a BLTAB element in the Catalogue DB. This contains details of the boltsneeded to connect the corresponding component into a pipeline (see the ISODRAFTReference Manual). This heading is, of course, applicable only to components whichrequire bolts (flanges etc.).

CMPREF - Component Reference:

Points to a CMPT element in the Properties DB (see Properties Constructor).

• Overall Specification PointersThese pointers, which are attributes of SPEC elements, are set for an entire Specification.Their settings are shown at the beginning of the Specification, immediately after the name,and always appear, even if they remain unset.

MATREF - Material Reference:

Points to a SOLID element in the Properties DB. This holds information about theproperties of the materials of construction of the piping components (see PropertiesConstructor).

FLUREF - Fluid Reference:

Points to a FLUID element in the Properties DB. This holds information about theproperties of the liquids or gases for use with which the piping components aresuitable (see Properties Constructor).

• Overall Specification SettingsThese are not pointers to other elements but are local to the Specification itself. Theirsettings are shown at the beginning of the Specification, immediately after the MATREF andFLUREF pointers, and always appear, having default settings if you have not specifiedotherwise. These attribute settings are used only by ISODRAFT and are relevant only whenfixed length piping is being used. You are referred to the section entitled ‘Fixed LengthPiping’ in the ISODRAFT Reference Manual for fuller details.

RATING - Pipeline Pressure Rating:

May be set to the maximum pressure at which the components covered by theSpecification are intended for service. ISODRAFT can then use this setting todetermine those points in a composite pipeline at which the pressure rating changes.The default setting is zero.

LINETYPE - Fixed Length Piping Line Type:

May be set to either of the identifiers

12.013:4


FP - Fixed Pipe

FX - Fixed Length

ISODRAFT uses this setting to decide whether or not to append the length of a componentto its item code in a material list. The length is appended if linetype is set to FP, but isassumed to be incorporated into the standard code if linetype is set to FX. The defaultsetting is NUL (i.e. variable length piping between components is assumed).

13.1.5 Examples From Piping Component SpecificationsTo keep the examples brief, very few lines (SPCOMs) are shown for each GTYPE.NEW SPECIFICATION /RF300MATREF =0FLUREF =0RATING 0.000LINETYPE NULHEADINGTYPE NAME PBOR0 SHOP CATREF DETAIL MATXT CMPREF BLTREF - - - =TUBE */20TU 20.0 TRUE /TUEE /DTUB1 /MTUB =0 =0TUBE */25TU 25.0 TRUE /TUFF /DTUB1 /MTUB =0 =0...HEADINGTYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF- - - PE =FTUB */20FT 20.0 PE TRUE /FTEE /DFTUB /MFTUB =0 =0FTUB */25FT 25.0 PE TRUE /FTFF /DFTUB /MFTUB =0 =0...HEADINGTYPE NAME PBOR0 RADI ANGL SHOP CATREF DETAIL MATXT CMPREF BLTREF- - - - = =BEND */20VB1 20.0 100.0 90.0 TRUE /VBEE /DVBEND1 /MVBEND =0 =0BEND */20VB3 20.0 100.0 180.0 TRUE /BEEE /DBEND1 /MVBEND =0 =0BEND */20VB2 20.0 60.0 90.0 TRUE /VBEE /DVBEND2 /MVBEND =0 =0BEND */20VB4 20.0 60.0 180.0 TRUE /BEEE /DBEND2 /MVBEND =0 =0BEND */25VB1 25.0 125.0 90.0 TRUE /VBFF /DVBEND1 /MVBEND =0 =0...HEADINGTYPE NAME PBOR0 CATREF DETAIL MATXT CMPREF BLTREFGASK */20G 20.0 /GAEE /DGASK /MGASK =0 =0GASK */25G 25.0 /GAFF /DGASK /MGASK =0 =0...HEADINGTYPE NAME PBOR1 PBOR2 STYPE SHOP CATREF DETAIL MATXT CMPREF BLTREF- - - - CONC =REDU */25RC1 25.0 20.0 CONC TRUE /RCFE /DRED.C /MRED =0 =0REDU */25RE1 25.0 20.0 ECC TRUE /REFE /DRED.E /MRED =0 =0REDU */32RC1 32.0 25.0 CONC TRUE /RCGF /DRED.C /MRED =0 =0REDU */32RE1 32.0 25.0 ECC TRUE /REGF /DRED.E /MRED =0 =0...

and so on.

(See Figure 11:3.: Part of a typical Specification for piping components for some otherexamples.)

12.013:5


13.2 Selectors and Pointers for Structural Components

13.2.1 ApplicabilityThe headings within this section may apply to components from the following list ofGTYPEs:

BASEBEAMBRACeCOLUmnFITTingGANTryGIRDerJOINtJOIStKNEEPILEPROFilePURLinRIDGeRODSCTNSDRAilSPLIceSTANchionSTIFfenerSTRUtTIE

13.2.2 SelectorsThe following SELEC questions are those which you are likely to use when defining SPECsfor structural components:

SType

Defines the Specific Type of the component; particularly applicable to the generalgeneric types PROF, JOIN and FITT. Examples of STYPE answers which might beapplied to structural components to cover European, American and British standardsinclude:

STYPE Meaning

C Channel section or American standard C–shapes (tapered flanges)

CHS Circular hollow section

CRSJ Castellated rolled steel joists

CUB Castellated universal beams

CUC Castellated universal columns

CZB Castellated Z–beams

EAI Imperial equal angles

12.013:6


DEPth

The depth (height) of a structural section; e.g. 100 mm.

WIDth

The width of a structural section; e.g. 100 mm.

WEIGht

The weight per unit length; e.g. 100 kg/m.

DIMEnsion integer:

Any dimension. The qualifying integer is optional; suggested conventions are:

DIME1Depth or long leg

DIME2Width or short leg

EAM Metric equal angles

HD European columns (wide flanges)

HE European beams (wide flanges)

HL/HX European beams (very wide flanges)

HP Bearing piles (wide flanges)

IPE European beams (parallel faced flanges)

IPN European standard beams (tapered flanges)

LST Long stalk tee–bars

M/W American I–shapes (wide flanges)

RHS Rectangular hollow section

RSJ Rolled steel joists

S American standard I–shapes (tapered flanges)

T Tee bars

TUB Tees cut from universal beams

TUC Tees cut from universal columns

U European small channels

UB Universal beams

UBP Universal bearing piles

UC Universal columns

UEAI Imperial unequal angles

UEAM Metric unequal angles

UPN European standard channels

PLAT Plate girders

STYPE Meaning

12.013:7


CTYPE integer

A connection type. The qualifying integer is optional; suggested conventions are:

CTYPE1Start connection

CTYPE2End connection

CTYPE3Attached connection

CTYPE4Owning connection

with the possible answers RIVET, BOLT, WELD, GLUE etc.

CTYStart

Start connection (equivalent to CTYPE1).

CTYEnd

End connection (equivalent to CTYPE2).

CTYAttached

Attached connection (equivalent to CTYPE3).

CTYOwning

Owning connection (equivalent to CTYPE4).

INERtia integer

Moment of inertia about a specified axis; e.g. 280 cm$. (It is usually convenient to usecm rather than mm here to avoid having to list large values.) The qualifying integer isoptional; suggested conventions are:

INER1Inertia about x-x

INER2Inertia about y-y

INER3Inertia about u-u

INER4Inertia about v-v

THICkness integer

Plate thickness within a section; e.g. 10 mm. The qualifying integer is optional;suggested conventions are:

THIC1Web thickness

THIC2Flange thickness

12.013:8


FIXty

Joint fixity; e.g. FIXED, PINNED, PLASTIC, HINGED, RIGID etc.

GRADe

Material grade for fire-resistant insulation; e.g. 43. (See Structural Insulation.)

FIREsistance

Degree of fire resistance for insulation; e.g. 2 hr. (See Structural Insulation.)

ITHIckness

Insulation thickness; e.g. 50 mm. (See Structural Insulation.)

AREA

Area of a section; e.g. 100 cm².

As for piping component specifications, you may also use any word, with or without anumeric qualifier, to define your own questions. See Selectors.

13.2.3 Reference Pointers and SettingsThe pointers and attribute settings which you may specify for structural componentspecifications are the same as those defined in Reference Pointers and Settings for pipingcomponents, although the relative importance of the references will differ (for example,FLUREF, RATING and LINETYPE are unlikely to be relevant). As for piping components,only the CATREF pointer is obligatory.

13.2.4 Examples From Structural Component SpecificationsThe following excerpt from a Specification for structural steelwork components illustratessome of the features defined in the preceding sections:

Note: The Reference Pointers DETAIL, MATXT, CMPREF and BLTREF have been omittedto save space. Although these are available to give consistency with PipingSpecifications, you are unlikely to use these for structural components (BLTREF, inparticular, would have no meaning for a structural component). No defaults havebeen set in this example.

NEW SPECIFICATION /BS4.PT1MATREF =0FLUREF =0RATING 0.000LINETYPE NULTEXT ’Middlesbrough Mills’HEADINGTYPE NAME STYP GRADE WIDTH DEPTH WEIGHT INERTIA CATREFBEAM */UB1 UB 43 465 153 82 32435 /457X152X82UB+ */UB2 + 50 465 153 82 32435 /457X152X82UB+ */UB3 + 43 310 125 48 9504 /305X127X48UB...HEADINGTYPE NAME STYP GRADE DEPTH WIDTH WEIGHT INERTIA CATREFBRAC */UEA1 UEAM 43 200 150 47 2376 /200X150X18L+ */UEA2 + 50 200 150 47 2376 /200X150X18L+ */UEA3 + 43 125 75 18 354 /125X75X12L...HEADINGTYPE NAME STYP WIDTH DEPTH WEIGHT INER1 INER2 CATREFPROF */BS.C1 C 102.0 432.0 65.5 21399.0 628.6 /432X102X65KG.C+ */BS.C2 + 102.0 381.0 55.1 14894.0 579.8 /381X102X55KG.C

12.013:9


...PROF */BS.CRSJ1 CRSJ 102.0 305.0 25.3 5372.0 162.5 /305X102X25KG.CRSJ+ */BS.CRSJ2 + 102.0 267.0 21.5 3562.0 139.1 /267X102X21KG.CRSJHEADINGTYPE NAME STYP DEPT WIDT WEIG INER1 INER2 CATREFPROF */BS.CUB1 CUB 1371.0 419.0 388.0 1661103.0 42443.0 /1371X419X388KG.CUB+ */BS.CUB2 CUB 1371.0 419.0 343.0 1449837.0 36223.0 /1371X419X343KG.CUB...

and so on.

13.3 Selectors and Pointers for InsulationThe information given in this section applies specifically to the generic type INSulation.

13.3.1 Pipework InsulationYou do not select and store Insulation in the same way that you select piping componentsfrom other modules. The Insulation Specification is interrogated automatically by modulessuch as DESIGN each time insulation details are required. When setting up an InsulationSpecification you must follow a strict format if this automatic selection is to work properly.

For any specific insulation material, the correct insulation thickness for a given pipeworkapplication is usually derived from two Selector questions:

Note: Although usually derived from two Selector questions this is optional. Refer toSample Insulation Specification.

TEMPerature:

The working temperature; usually specified as a temperature range (e.g. 101,200)

PBOR0:

The nominal diameter of the component; usually specified as a range of bore sizes(e.g 1, 2½ using inch bores or 25,70 using metric bores)

These might be related to the available thicknesses in the following way:

where the bores and insulation thickness are defined in inches. It is assumed in thisexample that the minimum insulation thickness which can be handled conveniently is 1 inchand so this has been applied to all pipe sizes in the low temperature range (0 to 100degrees).

Temperature Range Bore Range Insulation Thicknes

101 - 200 1 - 2½ 1

101 - 200 3 - 8 1½

201 - 400 1 - 2½ 2

201 - 400 3 - 8 3

0 - 100 1 - 8 1

12.013:10


This data would result in an Insulation Specification of the following form:NEW SPEC /INSPECHEADINGTYPE NAME TEMP PBOR0 CATREF DETAILINSU */IN1 0,100 1,8 /IC1 /CAL.SILINSU */IN2 101,200 1,2.5 /IC1 /CAL.SILINSU */IN3 101,200 3,8 /IC1.5 /CAL.SILINSU */IN4 201,400 1,2.5 /IC2 /CAL.SILINSU */IN5 201,400 3,8 /IC3 /CAL.SIL

Note: Because of possible ambiguity due to the overlapping ranges of PBOR0, the order inwhich the SELEC headings are tabulated is important. For the successful selectionof Insulation the TEMP question must be tabulated before the PBOR0 question.

Sample Insulation Specification

The following example shows an Insulation Specification not using Temperature as aselector:$S- -- Synonym translation OFF-- ------------------------------------------------- Data Listing Date : 27 Jan 2010 10:20

ONERROR GOLABEL /ERROR0

-- Navigate to existing location/E

NEW SPWL /AvevaPipeISPECS

-- *NEW SPECIFICATION /20mm_FibreGlassMatref /FIBERGLASS-INSULATIONPURP INSUDESCR 'Aveva Pipe 20mm insulation' LNTP unsetQUES TYPETDEF 'NONE'

NEW TEXTDESCR 'Aveva Pipe 20mm insulation'STEX 'INSUL'

NEW SELECQUES PBORTANS 'INSU'TDEF 'NONE'

NEW SPCOMPONENTMAXA 100000CATR SCOMPONENT /INS20

-- *NEW SPECIFICATION /25mm_FibreGlassMatref /FIBERGLASS-INSULATIONPURP INSUDESCR 'Aveva Pipe 25mm insulation' LNTP unsetQUES TYPETDEF 'NONE'

NEW TEXTDESCR 'Aveva Pipe 25mm insulation'STEX 'INSUL'

12.013:11


NEW SELECQUES PBORTANS 'INSU'TDEF 'NONE'

NEW SPCOMPONENTMAXA 100000CATR SCOMPONENT /INS25 etc

13.3.2 Structural InsulationInsulation for Sections, Joints and Fittings may be selected from an Insulation Specificationby using the selection criteria Grade, Fire Resistance and Insulation Thickness derived fromthe current component. An extract from a typical Insulation Specification for use in structuraldesign might be as follows:NEW SPECIFICATION /BS4.PT1.INSULHEADINGTYPE NAME GRADE FIRE ITHI CATREFDEFAULTS- - 43 - -INSU */IN1 43 1,2 20 /IN25+ */IN2 40 1,2 40 /IN50+ */IN3 43 2,4 20 /IN50+ */IN4 50 2,4 40 /IN75+ */IN5 43 4,10 20 /IN75+ */IN6 50 4,10 40 /IN100

12.013:12

Catalogues and Specifications Reference ManualSPECONMODE Command Syntax Diagrams

14 SPECONMODE Command Syntax Diagrams

This section contains the legal command and interrogation syntax diagrams relevant toSPECON. These diagrams formalise the precise command sequences which may be usedand are intended to supplement the explanations given in the appropriate sections of thismanual.

14.1 Syntax DiagramsThe diagrams are listed approximately in the order in which they are described in thismanual.

14.1.1 <speca>.----------------------------<----------------------------./ |

>---*--- NEW ---+--- SPECification ---. || | | || ‘---------------------+--- name ----------------|| ||---OLD ---+--- SPECification ---. || | | || ‘---------------------+ || | ||--- SPECification --------------+--- <id> -----------------|| ||--- <table> ---> || ||--- REMove ---. .----<-----. || | / | ||--- DELETE ---+---*--- <id> ---+----. || | | || |--- ALL -------------| || | | || ‘--- SPECification ---+----------------------|| ||--- TEXT --- text -----------------------------------------|| ||--- OUTput ---+--- NEW ---. || | | || |--- OLD ---| .-----<-------. || | |/ | || ‘-----------*--- <gtype> ---’ .----<-----. || | / | || ‘---------------*--- <id> ---+---|| ||--- COMPact ---. || | ||--- ALIGned ---+-------------------------------------------|| ||--- <copy> ------------------------------------------------|| ||--- MATRef ---. |

12.014:1


| | ||--- FLURef ---+--- <id> -----------------------------------|| ||--- RATIng --- value --------------------------------------|| ||--- LINETYpe --- word -------------------------------------|| |‘--- BOREs ---+--- ACTual ----. |

| | |‘--- NOMinal ---+-----------------------------+--->

14.1.2 <table>.--------<--------./ |

>--- <heading> ---*--- <default> -----|| ||--- <linesp> ------’|‘--->

14.1.3 <heading>.---------------------------.

/ |>--- Heading - nl --+-- TYpe - NAme --. .--*--- PBore --- integer -------|

| | | | |‘-- NAme - TYpe --+--’ |--- PConn --- integer -------|

| ||--- SType -------------------|| ||--- ANGle -------------------|| ||--- RADius ------------------|| ||--- TEMperature -------------|| ||--- PRessure ----------------|| ||--- RATing ------------------|| ||--- SHOP --------------------|| ||--- CATref ------------------|| ||--- DETail ------------------|| ||--- MATXt -------------------|| ||--- CMPref ------------------|| ||--- BLTref ------------------|| ||--- DEPth -------------------|| ||--- WIDth -------------------|| ||--- CTYStart ----------------|| ||--- CTYEnd ------------------|| ||--- CTYAttached -------------|| ||--- CTYOwning ---------------|| ||--- FIXty -------------------|| ||--- GRADe -------------------|| ||--- FIREsistance ------------|| ||--- ITHIckness --------------|| ||--- AREA --------------------|| ||--- WEIGht ------------------|

12.014:2


| ||--- DIMEnsion ---. || | ||--- CTYPE -------| || | ||--- INERtia -----| || | ||--- THICkness ---| || | ||--- word --------+-- value --|| | |‘----> ‘-----------’

14.1.4 <default>.------------./ |

>--- Defaults --- nl --- sign --- sign ---*--- <uval> ---|| ||--- sign -----|| ||--- word -----|| ||--- equals ---’|‘--->

14.1.5 <linesp>>--+--- noun ---.

| ||--- sign ----+--- name -----.| |‘--- <id> ---+--- noun -----|

| ||--- sign -----| .-----------------------------------------.| |/ |‘--------------*--- word ----------------------------------|

| ||--- TEXT --- text -------------------------|| ||--- EXTRA --- :uda_name --- uda_setting ---|| ||--- COMMENT --- text ----------------------|| ||--- <uval> ---+--- comma --- <uval> ----. || | | || ‘-------------------------+--|| ||--- sign ----------------------------------|| ||--- <id> ----------------------------------’|‘--->

14.1.6 <id>>----+--- name ---.

| |‘--- refno ---+--->

14.1.7 <copy>>--- COPY --- <id> ----+--- REName --- name --- name ---.

| |‘--------------------------------+---><uval>

>---+--- value ----------. | | ‘--- <expression> ---+--- EXponential --- value ---. | | ‘-----------------------------+--- MM -------. | | |--- Metres ---| | |

12.014:3


|--- INches ---| | | |--- FT -------| | | |--- FEet -----| | | |--- text -----| | | ‘--------------+--->

14.2 Other PDMS Command SyntaxCommon commands which may be legally used from within SPECON, but which are notdirectly related to this module, include the following:

Function(s) Syntax Diagram Name

Actions setting (i.e. ACTIONS command) <actset>

Element identification and database navigation <gid> and its subsidiary syntax

Device control <devvic>

Date and time (real & elapsed) <klok> and <datxtr>

Querying specific options:

Actions <qact>

Reading banner <qbann>

Buffers <qbuff>

Input/output device <qdevc>

Input/output counters <qioc>

Project details <qproj>

Defining the current (default) units of measurement <setun>

Attribute type references <satt>

Module selection <smodu>

Giving system commands <syscom>

Defining logical expressions etc. <pml>

12.014:4

Catalogues and Specifications Reference ManualSPECONMODE Error Messages

15 SPECONMODE Error Messages

The following is a list of those error messages specific to SPECON. All such error messageshave a message number beginning with 17. Any other messages that may be output are notdescribed here as they are not specific to SPECON.

Note: Since some other modules access the Specifications directly during their normalfunctioning (for example, to select insulation data) you may receive SPECON errormessages while working in those modules.

(17:2) Cannot access ID

The element specified does not appear to exist in this DB. Check that you have entered theidentifier correctly.

(17:3) Cannot access SPECIFICATION

Check that you have entered the identifier for the SPEC correctly.

(17:4) Cannot create SPCOM or SELEC

You can only add a new SPCOM line or SELEC question after you have created a newSPEC or have accessed an existing SPEC (see Creating a Specification to EnteringTabular Data).

(17:5) Cannot create SPECIFICATION

You can only create a new SPEC as a member of a Specification World (SPWLD) elementin a CATALOGUE DB. Check your current position in the hierarchy. (See Structure of theCatalogue Database and Content and Format of a Specification.) An accompanyingmessage should give a fuller explanation.

(17:6) CATREF already used in heading

You have specified two CATREF pointers in a heading line. The second entry will beignored, but should preferably be deleted.

(17:7) Answers select previously defined spcom

The combination of answers listed for this SPCOM line leads to an SPCOM which hasalready been defined. The second SPCOM line will, therefore, never be reached during theselection process.

(17:9) DB unsuitable for SPEC

You can only create a new SPEC as a member of a Specification World (SPWLD) elementin a CATALOGUE DB (see Structure of the Catalogue Database and Content and Formatof a Specification).

12.015:1


(17:10) DITTO IN FIRST LINE

The ditto symbol (+) means ‘repeat the corresponding entry in the preceding line’ and istherefore only valid in the second or subsequent lines of the table.

(17:11) No SPECIFICATION defined

You must have created a new SPEC or accessed an existing SPEC before you can add to,modify, or output any tabulated Specification data (see Manipulating the CatalogueDatabase using SPECONMODE).

(17:12) ID name/refno does not correspond to column heading

An element identifier in an SPCOM line must correspond to a relevant Reference Pointer inthe heading line. It cannot be given as an answer under a SELEC question in the heading(see How Component Selection Works).

(17:13) ID is not a SPEC

The identifier given in an OUTPUT command must refer to an accessible SPEC (seeOutputting a Specification). Check that you have entered the identifier correctly.

(17:14) Too many headings for output

You cannot output more than 20 headings in a table.

(17:15) More answers than questions - extra answers ignored

You have more entries in an SPCOM answer line than you have corresponding entries inthe heading line. Check for unintentional spaces.

(17:16) More defaults than questions - extra defaults ignored

You have more entries in the defaults line than you have corresponding entries in theheading line.

(17:17) More than 20 HEADINGS

The maximum number of entries permitted in a heading line is 20.

(17:18) DETAIL already used in heading

You have specified two DETAIL pointers in a heading line. The line will be ignored.

(17:19) Name already defined. Name/refno will remain unnamed.

The NAME specified for this SPCOM has already been used and so this second SPCOMline will have only its PDMS refno as its identifier. Redefine this line with a new NAME ifrequired.

(17:20) No. of QUESTIONS and ANSWERS do not match up

If the answers in a given SPCOM line do not correspond in a relevant way with the SELECquestions in the heading then that SPCOM will be ignored. (See the Note in SelectorAnswers for one possible cause of this problem.)

(17:22) Reserve name /*LIMBOSPEC has been used - object withthis name has been unnamed

The Specification /*LIMBOSPEC is reserved for holding REMOVED SPCOMs (seeDeleting or Removing a SPEC or SPCOM). You cannot use it for any other purpose.

12.015:2


(17:23) SPCOM does not exist

Check that you have entered the SPCOM identifier correctly when modifying an existingSpecification.

(17:24) SPEC does not exist

Check that you have entered the SPEC identifier correctly.

(17:26) This command only allowed in SPEC

You can only use a DELETE or REMOVE command after you have accessed anappropriate SPEC (see Accessing an Existing Specification and Deleting or Removing aSPEC or SPCOM), otherwise SPECON does not know which Specification you are telling itto modify.

(17:28) TYPE required as first answer

When adding a new SPCOM you must enter its TYPE (a PDMS noun) before its NAME.You may only use the reverse order when referring to an existing SPCOM (see EnteringTabular Data).

(17:29) Unable to create TEXT element

You can only specify one string of descriptive text for each SPEC.

(17:30) Unable to put CATREF

You are unable to set this Reference Pointer to the element specified. Possibly you havespecified it incorrectly.

(17:33) Undefined name

Check that you have entered the required identifier correctly.

(17:34) SPEC or an offspring is locked.

The SPEC is protected against modification. Use the UNLOCK command before trying touse any of the SPECON editing facilities.

(17:35) SPEC is not empty

When using the COPY command, the SPEC into which the copy is transferred (name1 inCopying a Specification) must be empty. You cannot concatenate SPECs with the COPYcommand.

(17:36) ID must be SPCOM

The REMOVE command can only be used to remove SPCOMs. You cannot remove anentire SPEC, although you may use the REMOVE ALL option to empty it of its contents(see Deleting or Removing a SPEC or SPCOM).

(17:38) No databases to work from

(17:39) No SPEC database

The specified MDB does not contain an appropriate CATALOGUE DB in which SPECONcan create SPECs.

12.015:3


(17:40) TEXT longer than 50 characters

The text associated with a SPEC cannot exceed 50 characters in length (see Creating aSpecification).

(17:41) Unable to put CMPREF


(17:42) Unable to put DETAIL


(17:43) Unable to put MATXT


(17:44) Unable to put BLTREF


(17:45) You may not delete /*LIMBOSPEC

The SPEC named /*LIMBOSPEC, used to hold removed SPCOMs, is createdautomatically by PDMS and cannot be deleted, otherwise future REMOVE commandswould not work (see Deleting or Removing a SPEC or SPCOM).

(17:46) You cannot REMOVE SPEC - use REMOVE ALL

The REMOVE command applies only to the contents of a SPEC. Use REMOVE ALL toempty the SPEC of all contents or DELETE SPEC specname to eliminate the completeSPEC. (See Deleting or Removing a SPEC or SPCOM.)

(17:47) You cannot REMOVE items from /*LIMBOSPEC

The REMOVE command can only transfer SPCOMs to /*LIMBOSPEC. Only by re-enteringan SPCOM under its existing name can it be transferred back from /*LIMBOSPEC into auser-defined SPEC. (See Deleting or Removing a SPEC or SPCOM.)

(17:48) MATXT already used in heading

You have specified two MATXT pointers in a heading line. The second entry will be ignored,but should preferably be deleted.

(17:49) CMPREF already used in heading

You have specified two CMPREF pointers in a heading line. The second entry will beignored, but should preferably be deleted.

(17:50) BLTREF already used in heading

You have specified two BLTREF pointers in a heading line. The second entry will beignored, but should preferably be deleted.

(17:51) SPCON NAME name already exists

You must use a unique name for each SPCON. The new SPCON will be rejected.

12.015:4


(17:52) word is not valid as a GTYPE

See Applicability for examples of valid GTYPEs.

(17:53) TMPR already used in heading

You have specified two TMPR pointers in a heading line. The second entry will be ignored,but should preferably be deleted.

(17:54) Unable to put TMPR


12.015:5


12.015:6

Catalogues and Specifications Reference ManualNominal Pipe Size Tables

16 Nominal Pipe Size Tables

As explained in Outputting Parts of Specifications, PDMS holds tables of nominal pipe sizeswhich it uses in preference to actual sizes if an actual and a nominal size fall within apredefined tolerance band. These tables comprise the following diameters:

Metric Units(mm)

Imperial Units(inches

Metric Units(mm)

Imperial Units(inches)

6.0 0.125 900.0 36.0

8.0 0.250 950.0 38.0

10.0 0.375 1000.0 40.015.0 0.500 1050.0 42.0

20.0 0.750 1100.0 44.0

25.0 1.00 1150.0 46.032.0 1.25 1200.0 48.0

40.0 1.50 1250.0 50.0

50.0 2.00 1300.0 52.0

65.0 2.50 1350.0 54.080.0 3.00 1400.0 56.0

0.0 3.50 1450.0 58.0

100.0 4.00 1500.0 60.0125.0 5.00 1600.0 64.0

150.0 6.00 1650.0 66.0

200.0 8.00 1750.0 68.0250.0 10.0 1800.0 72.0

300.0 12.0 1850.0 74.0

350.0 14.0 1900.0 76.0400.0 16.0 1950.0 78.0

450.0 18.0 2000.0 80.0

500.0 20.0 2050.0 82.0550.0 22.0 2100.0 84.0

600.0 24.0 2200.0 88.0

650.0 26.0 2400.0 96.0700.0 28.0 2600.0 104.0

750.0 30.0 2800.0 152.0

800.0 32.0 3000.0 120.0850.0 34.0 3200.0 128.0

3400.0 136.0

3600.0 136.03800.0 1

4000.0 136.0

12.016:1

Catalogues and Specifications Reference ManualNominal Pipe Size Tables

12.016:2

Catalogues and Specifications Reference ManualProperties Constructor

17 Properties Constructor

The PROPCON (PROPerties CONstructor) is used to input and edit data within theProperties database (DB). PROPCON commands are input directly into the PARAGONcommand line.

Properties data is used to hold properties of components and materials which may beneeded for stress analysis or safety auditing of all or part of a design. PROPCON alsoincludes data such as the material densities needed by the DESIGN structural applicationsfor calculating weights and centres of gravity of steelwork items.

The Properties DB hierarchy is as follows:

Figure 17:1. Properties Database Hierarchy

12.017:1


17.1 Setting Up a Properties DatabaseA Properties database (DB) is created in the ADMIN module in the same way as a Design orCatalogue DB. The DB will be assigned, typically, to the team responsible for pipe stressing.The syntax for creating a Properties DB is:

>-- CReate -- DB -- teamname/dbname -- PROP -->

Before the Properties DB can be used, it must be added to a multiple database (MDB).

17.2 DescriptionFull details of the Properties database structure and of the elements held within it, refer tothe Data Model Reference Manual. The types of data stored may be grouped into thefollowing categories:

17.2.1 Design Layout DataFor a full description of Design layout data refer to the DESIGN Reference Manual.

17.2.2 Material Property DataThis consists of expansion coefficients, Young’s modulus of elasticity etc., for each material.This includes the actual pipe material, such as steel, and the fluid, such as water, which thepipe contains.

17.2.3 Case DataCase data consists of the particular values of temperature and pressure that can be appliedto a pipe at any one time. A pipe may have several ‘cases’ if the temperature and/orpressure parameters vary.

17.2.4 Component DataThe Catalogue does not give extensive information on components, only size attributes. TheProperties DB component data element can be referenced from individual specificationcomponents and consists of physical data, such as weight, flexibility factors, wall thickness,etc.

17.2.5 Constraint Data This constraint data is split between the Properties DB and the Design DB. In the DesignDB, an attachment point is created having a reference attribute which points to a constraintin the Properties DB. This constraint has data referring to forces, moments etc.

17.2.6 Run DataThis is the information needed to carry out a ‘run’ that is not held elsewhere in PDMS andcould consist of a header card, for instance, which would contain a person’s name and thetype of analysis to be performed. This run data will depend on the type of stressing packageinterfaced to the Properties DB.

12.017:2


17.3 Material Property Data

17.3.1 Hierarchy DescriptionThe Material World (MATW) comes below World in the Properties hierarchy. It is purely anadministrative element that groups material data together.

Below MATW are two elements: SOLI and FLUI. The material properties are subdividedsuch that SOLI holds data for the pipe itself and FLUI holds data for the fluid within the pipe.

17.3.2 Material PropertiesThe pipework material properties associated with flexibility and stress analysis are asfollows:

POISSON’S RATIOCOEFFICIENT OF EXPANSIONYOUNG’S MODULUSALLOWABLE STRESSDENSITY

There can also be three general properties known as A, B and C properties. These are usedto store any additional properties that may be needed. Each of these may be a function oftemperature and/or pressure.

To enable the properties to be stored against temperature and pressure values, the data isstored in a tabular format which incorporates a ‘table’ element for each type of property:TYOU (table of Young’s modulus values), TSTR (table of allowable stresses), etc.

Below these are ‘spot’ elements, SYOU, SSTR etc. The ‘spot’ elements have attributesPRES and TEMP where values of pressure and temperature may be input. Each elementalso has an attribute to allow the input of the corresponding value of its own property; forexample, SYOU has an attribute YOUN where a value of Young’s modulus may be stored,SAPR has an attribute APRO where a value of APROPERTY may be stored, and so on.

At different temperatures and pressures, the value of Young’s modulus may vary, and somore spot Young’s modulus elements (SYOUs) may be created with different temperature,pressure and Young’s modulus values. Thus the attributes settings for a specific SYOUmight be:

TYPE SYOU (Spot Young’s modulus)

NAME

LOCK

OWNE

TEMP 20 (Temperature)

PRES 101EX+3 (Pressure)

YOUN 210EX+9 (Young’s modulus value; see Exponential Numbers for adescription of the exponential format of numbers)

12.017:3


The table that these spot properties create can then be used by a suitable stressingpackage. The table effectively forms a graph with the spot property, temperature andpressure. From this table, therefore, the stressing package can interpolate other values itmay need.

The PDMS unit for TEMP is degrees centigrade and for PRES and YOUN is N/m².Therefore, this material at a temperature of 20 degrees centigrade and a pressure of 101kN/m² would have a value for Young’s modulus (E) of 210 GN/m². For a change of units, seeUse of Groups.

Note: FLUI does not have the elements relating to allowable stress, nor Poisson's ratio, i.e.TSTR, TPOI, SSTR and SPOI.

The elements SOLI and FLUI have an attribute DESC (Description) which is a 120-character text string.

The table elements (TPOI, TEXP etc) have an attribute PQUA (Property Qualifier) which issome qualification under which the property applies. There is provision for 4 characters.

The table elements also have an attribute SREF (Source Reference). This may be the nameof a book from where the spot values were obtained and is a 12-character text string.

The elements TAPR, TBPR and TCPR also have an attribute PNAM (Property Name) whichis a 12-character text string.

At the same level as the table elements is an element TEXT which has an attribute STEXwhich is a 50-character text string.

17.3.3 Pointers from the Design DB and SpecificationThe Specification Component (SPCOM) has attributes MATR and FLUR. These arematerial reference and fluid reference, which point to the pipe material (SOLI) and the fluidwithin the pipe (FLUI), respectively.

In the Design DB, Pipes and Branches also have these attributes MATR and FLUR. If theseare set, the references from the Specification Component are ignored, but if they are unset,the references from the Specification Component are used.

17.4 Case Data

17.4.1 Hierarchy DescriptionThe Case World (CASWL) is a member of World in the Properties hierarchy and is anadministrative element used to keep all Case data together.

Below CASWL come two elements, Case (CASE) and Case Type (CAST). CASE may bedirectly below CASWL or may come under CAST.

CAST is an administrative element to further group cases if there are several of them andthey can be split into case types.

A Case has of a number of attributes which describe different conditions to which a pipe issubjected. For every ‘run’ of a pipe there may be a number of ‘cases’.

12.017:4


CASE has the following attributes:

The attributes WEFA, WPRE, WIFA, IPRE, RPRE, PTEM, RTEM and TGRA are all realnumbers; SHOC is a 3-element real array; APPL is a 20-character text string.

17.4.2 Pointer from the Design DBThe elements Pipe and Branch in the Design DB have an attribute Case Reference (CASR)which points to a Group of Cases applicable for that pipe in the Properties DB. The use ofGroups for Cases is described in Use of Groups.

17.5 Component Data

17.5.1 Hierarchy DescriptionThe Component World (CMPWL) is a member of World in the Properties hierarchy. It is anadministrative element to keep component data together. Below CMPWL there isComponent Type (CMPT), which is also a purely administrative element. Under CMPT canbe found Component Data (CMPD) and Tube Data (TUBD).

Insufficient data is held in the Catalogue and Design DBs about components for a stressing‘run’ to take place. Therefore further data can be stored as attributes of CMPD or TUBD.

TYPE CASE

NAME

LOCK

OWNE

WEFA (weight factor)

WPRE (wind pressure)

WIFA (wind factor)

IPRE (internal pressure)

RPRE (reference pressure)

PTEM (pipe temperature)

RTEM (reference temperature)

TGRA (temperature gradient)

SHOC (shock load vector)

APPL (application)

12.017:5


CMPD has the following attributes:

The element TUBD has the same attributes, except that it does not have DFFL, DMFL orRMFL and, instead of having CWEI and CIWE, it has UWEI, which is weight per unit length(unit weight), and UIWE, which is weight per unit insulation.

The attributes OUTD, ACBO, BTOL, WTOL, CWEI, CIWE, WDIA, SHAP, PRFC, CORA,EFAC, PWAS, BFLE and MRKR are real numbers; RINE, SIF and SDTH are 3-element realarrays; DFFL, DMFL and RMFL are six- and nine-figure flexibility matrices.

To enable Weight and Centre of Gravity calculations to be performed in all disciplines, theCWEI and UWEI attributes have been updated to use parameterised properties, i.e. theycan be set using standard expression syntax such as:

(weight (ATTRIB PARA[2] + ATTRIB PARA[3])

Existing syntax is still valid, for example:

UWEI 2.5

TYPE CMPD

NAME

LOCK

OWNE

OUTD (outside diameter)

ACBO (actual bore)

BTOL (bore tolerance)

WTOL (weight tolerance)

CWEI (component weight)

CIWE (component insulation weight)

WDIA (wind diameter)

SHAP (shape factor)

RINE (rotational inertia vector)

SIF (stress intensification factor)

PRFC (pressure factor)

SDTH (saddle thickness)

CORA (corrosion allowance)

EFAC (Young’s modulus factor)

BFLE (bend flexibility)

DFFL (displacement force flexibility)

DMFL (displacement moment flexibility)

RMFL (rotational moment flexibility)

MRKR (component marker)

12.017:6


The rest of the real number attributes (other than MRKR) have also been parameterised.

17.5.2 Querying Calculated ResultsThe pseudo-attribute PROPRE is provided to allow the querying of the calculated result of aproperty attribute. This is a valid attribute at the design element which indirectly referencesthe property component such as a pipe or branch. This attribute has a qualifier, which is theproperty attribute to be evaluated, for example:

Q PROPRE OUTD

17.5.3 Pointer from the SpecificationThe Specification Component (SPCOM) has a reference to the Component Data or TubeData relevant to that particular component. This reference is called CMPR (ComponentReference).

17.6 Constraints Data

17.6.1 Hierarchy DescriptionThe Constraint World (CONW) is a member of World. It owns Constraint Type (CONT),which is an administrative element that groups constraint data into types. Below CONT isConstraint (CONS). This element has attributes that store particular conditions to which aconstraint may be subjected.

CONS owns the Case Table element (TCAS). This is a reference to a particular case forwhich the constraint data is applicable.

One constraint may own more than one TCAS. This could mean that the attribute ofconstraint is valid for more than one case (for different temperatures and pressures etc.).

If there is no TCAS, then this could mean that the attributes of CONS are valid for anyparticular case.

CONS has the following attributes:

TYPE CONS

NAME

LOCK

OWNER

APPL (application)

FORC (applied force (load))

MOME (applied moment)

DISP (applied displacement)

ROTA (applied rotation)

DLIM (displacement limits)

RLIM (rotation limits)

12.017:7


The attribute APPL (application) is a 20-character text string; FORC, MOME, DISP, ROTA,FLIM, MLIM, DFLF, RFLF, FCOE, CPUL and CPUT are 3-element real arrays; DLIM andRLIM are 6-element real arrays.

The element CONT has an attribute RTYP (Restraint Type) which is a 12-character textstring.

The element TCAS (Case Table element) has an attribute CASR (Case Reference) whichreferences a case applicable for that constraint.

17.6.2 Pointer from the Design DBIn the Design DB, Pipe has a legal member called ATTA (Attachment Point). This elementhas an attribute CSTR (Constraint Reference) which points to a constraint in the PropertiesDB, and therefore to all its attributes and conditions.

17.7 Run Data

17.7.1 Hierarchy DescriptionThe Run World (RUNW) is a member of World and owns the element RUN. RUN is a textelement with an attribute DATE, which is a 9-character text string, and UNAME (UserName), which is a 12-character text string. RUN owns Card (CARD) which has attributesCard Type (CATY) and Card Text (CTXT), which is a 120-character text string.

These text attributes are used to store information necessary to run a specific stressanalysis package, e.g. a header card containing a person’s name, type of analysis to beperformed, etc.

FLIM (force limits)

MLIM (moment limits)

DFLF (translational flexibility factor - distance/force)

RFLF (rotation flexibility factor)

FCOE (friction coefficient)

CPUL (cold pull (translational))

CPUT (cold pull (twist))

12.017:8

Catalogues and Specifications Reference ManualUse of Groups

18 Use of Groups

Groups are used in PROPCON to group Cases together. This is done to save space andtime spent creating Cases. Several Cases with the same attributes may be reproduced indifferent Case Types if groups are not used.

The syntax for adding or removing cases from a group is:

>---+--- ADD ------. .-----------.| | / |‘--- REMOVE ---+--- <gid> ---*--- <gid> ---’

|‘----->

Note: Do not delete cases from a group or you will delete them from the Propertiesdatabase. Use the REMOVE syntax

The element Group has an attribute FUNC (Function) which is a 12-character text string.

12.018:1

Catalogues and Specifications Reference ManualUse of Groups

12.018:2

Catalogues and Specifications Reference ManualExponential Numbers

19 Exponential Numbers

Exponential numbers may be input into PROPCON with the following syntax:>--- attribute --- value --- EXponential --- exponent_value --->

For example:

YOUN 210 EX 9

means that the value of Young’s modulus input is 210 x 109.

Values may be input non-exponentially subject to a maximum number of 11 digits. Use ofthe EX command allows larger numbers to be input, depending on the particular machineused.

Negative exponential numbers may be input, if required, by using a minus sign. The defaultis positive.

PROPCON will output numbers in exponential format if the number is large enough or smallenough.

12.019:1

Catalogues and Specifications Reference ManualExponential Numbers

12.019:2

Catalogues and Specifications Reference ManualPROPCON Command Syntax Diagrams

20 PROPCON Command Syntax Diagrams

This section contains the legal command and interrogation syntax diagrams relevant toPROPCON. These diagrams formalise the precise command sequences which may beused and are intended to supplement the explanations given in the appropriate sections ofthis manual.

20.1 Syntax Diagrams<sadj>>---+--- <watt> -------- word ---.

| ||--- DESCription --- text ---|| ||--- SREFerence ---- text ---|| ||--- PNAMe --------- text ---|| ||--- APPLication --- text ---|| ||--- RTYPe --------- text ---|| ||--- UNAMe --------- text ---|| ||--- STEXt --------- text ---|| ||--- FUNCtion ------ text ---|| ||--- DATe ---------- text ---|| |‘--- CTXT ---------- text ----+--->

<satt>>---+--- OWNer --------------.

| ||--- TEMPerature --------|| ||--- PRESsure -----------|| ||--- DENSity ------------|| ||--- STREss -------------|| ||--- POISsons -----------|| ||--- EXPAnsion ----------|| ||--- YOUNgs -------------|| |

12.020:1


|--- APROperty ----------|| ||--- BPROperty ----------|| ||--- CPROperty ----------|| ||--- RTEMperature -------|| ||--- RPREssure ----------|| ||--- WEFActor -----------|| ||--- WPREssure ----------|| ||--- WIFActor -----------|| ||--- IPREssure ----------|| ||--- RPREssure ----------|| ||--- PTEMperature -------|| ||--- TGRAdient ----------|| ||--- SHOCkload ----------|| ||--- OUTDiameter --------|| ||--- ACBOre -------------|| ||--- BTOLerance ---------|| ||--- WTOLerance ---------|| ||--- UWEIght ------------|| ||--- UIWEight -----------|| ||--- WDIAmeter ----------|| ||--- SHAPe --------------|| ||--- RINErtia -----------|| ||--- SIF ----------------|| ||--- PRFC ---------------|| ||--- SDTHickness --------|| ||--- CORAllowance -------|| ||--- EFACtor ------------|| ||--- DFLFactors ---------|| ||--- FORCe --------------|| ||--- MOMEnt -------------|| ||--- DISPlacement -------|| ||--- ROTAtion -----------|| |

12.020:2


|--- DLIMit -------------|| ||--- RLIMit -------------|| ||--- FLIMit -------------|| ||--- MLIMit -------------|| ||--- DFFLexibility ------|| ||--- FCOEfficient -------|| ||--- CPULl --------------|| ||--- CASReference -------|| ||--- CATYpe -------------|| ||--- CTXT ---------------|| ||--- DMFLexibility ------|| ||--- RMFLexibility ------|| ||--- CPUTwist -----------|| ||--- RFLFactors ---------|| ||--- BFLExibility -------|| ||--- CWEIght ------------|| ||--- CIWEight -----------|| |‘--- PWAStage -----------+--->

<snoun>>---+--- MATWorlds --------.

| ||--- SOLIds -----------|| ||--- FLUIds -----------|| ||--- TDENsity ---------|| ||--- TDENsities -------|| ||--- TSTResses --------|| ||--- TPOIssons --------|| ||--- TEXPansions ------|| ||--- TYOungs ----------|| ||--- TAPRoperties -----|| ||--- TAPRoperty -------|| ||--- TBPRoperties -----|| ||--- TBPRoperty -------|| |

12.020:3


|--- TCPRoperties -----|| ||--- TCPRoperty -------|| ||--- SDENsity ---------|| ||--- SDENsities -------|| ||--- SSTResses --------|| ||--- SPOIssons --------|| ||--- SEXPansions ------|| ||--- SYOUngs ----------|| ||--- SAPRoperty -------|| ||--- SAPRoperties -----|| ||--- SBPRoperty -------|| ||--- SBPRoperties -----|| ||--- SCPRoperty -------|| ||--- SCPRoperties -----|| ||--- CASWorlds --------|| ||--- CASEs ------------|| ||--- CMPWorlds --------|| ||--- CMPTypes ---------|| ||--- CMPData ----------|| ||--- CONWorlds --------|| ||--- CONTypes ---------|| ||--- CONStraints ------|| ||--- TCASes -----------|| ||--- RUNWorlds --------|| ||--- RUNdecks ---------|| ||--- CARDs ------------|| ||--- TEXts ------------|| ||--- CASTypes ---------|| ||--- TUBDatas ---------|| |‘--- GPWLds -----------+--->

12.020:4


<squer>>---+--- CTXT -------------.

| ||--- <watt> -----------|| ||--- DESCription ------|| ||--- SREFerence -------|| ||--- PNAMe ------------|| ||--- APPLication ------|| ||--- RTYPe ------------|| ||--- UNAMe ------------|| ||--- STEXt ------------|| ||--- FUNCtion ---------|| |‘--- DATe -------------+--->

<watt>>----+--- PQUAlifier -----.

| |‘--- MRKR -----------+--->

12.020:5


12.020:6

Index


AABREV . . . . . . . . . . . . . . . . . . . . . . . . . 7:26ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4ADEN . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26AIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4ALPHA . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2ALPHA FILE . . . . . . . . . . . . . . . . . . . . . . 3:2ALPHA LOG . . . . . . . . . . . . . . . . . . . . . . 3:2APARAM . . . . . . . . . . . . . . . . . . . . . 4:7, 5:4ATLI . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:25

BBLIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23BLTA . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23BLTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23BOXI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7BTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:23

CCATA . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Catalogue . . . . . . . . . . . . . . . . . . . . . . . . 4:3Catalogue Element Types . . . . . . . . . . . . 2:5CATE . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Category . . . . . . . . . . . . . . . . . . . . . . . . . 4:4CCTA . . . . . . . . . . . . . . . . . . . . . 7:22, 10:6CE . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4, 6:1CENTRELINE See CL . . . . . . . . . . . . . 6:14CL . . . . . . . . . . . . . . . . . . . . . . . . . 6:5, 6:14COCO . . . . . . . . . . . . . . . . . . . . . 7:22, 10:6COLOUR . . . . . . . . . . . . . . . . . . . . . . . . . 3:4comma . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3COMP . . . . . . . . . . . . . . . . . . . . . . 4:5, 4:10

Cursor-picking Identifier . . . . . . . . . . 2:4, 2:8

DDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1DDANGLE . . . . . . . . . .5:12, 5:16, 6:1, 6:11DDHEIGHT . . . . . . . . . . . . . . . . . . 6:1, 6:11DDRADIUS . . . . . . . . . . . . . . . . . . 6:1, 6:11DECP . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26DES APARAM . . . . . . . . . . . . . . . . . . . . 4:8DES OPARAM . . . . . . . . . . . . . . . . . . . . 4:8DES PARAM . . . . . . . . . . . . . . . . . . . . . 4:8Dimensions . . . . . . . . . . . . . . . . . . . . . . 2:4DTAB . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24DTEX . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5DTSET . . . . . . . . . . . . . . . . . . . . . . . 4:5, 8:1

EExpressions . . . . . . . . . . . . . . . . . . . . . . 2:4

Ffilename . . . . . . . . . . . . . . . . . . . . . . . . . 2:3FINISH . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2FITT . . . . . . . . . . . . . . . . . . . . . . . . 4:6, 4:12

GGETWORK . . . . . . . . . . . . . . . . . . . . . . . 3:1GMSET . . . . . . . . . . . . . . . . . 4:5, 5:17, 7:5GMSSET . . . . . . . . . . . . . . . 4:6, 5:20, 7:18

12.0Index page 1


IINCBOR . . . . . . . . . . . . . . . . . . . . . . . . 7:29INSULATION . . . . . . . . . . . . . . . . . . . . 6:17integer . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3IPARAM . . . . . . . . . . . . . . . . . . . . . 4:7, 5:5

JJOIN . . . . . . . . . . . . . . . . . . . . . . . 4:6, 4:11

LLCYL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8LENGTH . . . . . . . . . . . . . . . . . . . 6:18, 6:19letter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3LEVEL . . . . . . . . . . . . . . . . . . . . . . 6:5, 6:16LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11LPYR . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12LSNO . . . . . . . . . . . . . . . . . . . . . . . . . . 7:13LTAB . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24

Mminus . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3MMBOR . . . . . . . . . . . . . . . . . . . . . . . . 7:29MODEL . . . . . . . . . . . . . . . . . . . . . 6:1, 6:11MSET . . . . . . . . . . . . . . . . . . . . . . . . . . 7:25MTEX . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5MTYP . . . . . . . . . . . . . . . . . . . . . . . . . . 7:25MULT . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26

NNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3NEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3NGMSET . . . . . . . . . . . . . . . . . . . . 4:5, 7:16NOMINB . . . . . . . . . . . . . . . . . . . . . . . . 7:29NRBWLD . . . . . . . . . . . . . . . . . . . . . . . 7:29NUMBER . . . . . . . . . . . . . . . . . . . . . . . 5:14NUMBERS . . . . . . . . . . . . . . . . . . . . . . 6:18

OOBST . . . . . . . . . . . . . . . . . . . . . . 7:6, 7:18OBSTRUCTION . . . . . . . . . . . . . . 6:5, 6:17OPARAM . . . . . . . . . . . . . . . . . . . . . . . . 4:7

PPAAX . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22PARAM . . . . . . . . . . . . . . . . . . . . . . 4:6, 5:4PAXI . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22

PBORE . . . . . . . . . . . . . . . . . . . . . . . . . 5:14PCON . . . . . . . . . . . . . . . . . . . . . . 10:5, 10:6PCONNECTION . . . . . . . . . . . . . . . . . . 5:14PDISTANCE . . . . . . . . . . . . . . . . . . . . . 5:13PKEY . . . . . . . . . . . . . . . . . 5:16, 5:17, 6:19PLAXI . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16PLINE . . . . . . . . . . . . . . . . . . . . . . . 5:15, 7:3PLINES . . . . . . . . . . . . . . . . . 6:4, 6:5, 6:19plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3PPOINT . . . . . . . . . . . . .5:9, 5:10, 5:11, 7:1PPOINTS . . . . . . . . . . . . . . . . . . . . 6:2, 6:18PROF . . . . . . . . . . . . . . . . . . . . . . . 4:6, 4:11PROFILE . . . . . . . . . . . . . . . . . . . . . . . 6:15PSKEY . . . . . . . . . . . . . . . . . . . . . . . . . 5:14PTAXI . . . . . . . . . . . . . . . . . . . 5:9, 5:12, 7:2PTCAR . . . . . . . . . . . . . . . . . . . . . . 5:10, 7:3PTCDIRECTION . . . . . . . . . . . . . . . . . 5:14PTMIX . . . . . . . . . . . . . . . . . . . . . . 5:11, 7:3PTSET . . . . . . . . . . . . . . . . . . . 4:5, 5:9, 7:1PTSSET . . . . . . . . . . . . . . . . . 4:5, 5:15, 7:3PURP . . . . . . . . . . . . . . . . . . . . . . . . . . 7:29PX . . . . . . . . . . . . . . . . . . . . . . . . 5:13, 5:17PY . . . . . . . . . . . . . . . . . . . . . . . . 5:13, 5:17PZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13

QQUERY . . . . . . . . . . . . . . . . . . . . . . . . . 5:4QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

RREPRESENTATION 6:2, 6:4, 6:5, 6:14, 6:15,

6:16, 6:17, 6:18, 6:19

SSANN . . . . . . . . . . . . . . . . . . . . . . 5:20, 7:19SAVEWORK . . . . . . . . . . . . . . . . . . . . . 3:1SBOL . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24SBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6SCOM See COMP . . . . . . . . . . . . . . . . . 4:5SCON . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7SCTO . . . . . . . . . . . . . . . . . . . . . . . . . . 7:12SCYL . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9SDIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:10SDSH . . . . . . . . . . . . . . . . . . . . . . . . . . 7:11SDTE . . . . . . . . . . . . . . . . . . . . . . . . . . 7:21SDTE See DTEX . . . . . . . . . . . . . . . . . . 4:5SECT . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Section . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4SETTINGS . . . . . . . . . . . . . . . . . . . 6:1, 6:11SEXT . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15SFIT See FITT . . . . . . . . . . . . . . . . . . . . 4:6

12.0Index page 2


SIGF . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26SJOI See JOIN . . . . . . . . . . . . . . . . . . . . 4:6SKEY . . . . . . . . . . . . . . . . . . . . . . . . . . 5:14SLOO . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15SMTE . . . . . . . . . . . . . . . . . . . . . . . . . . 7:22SMTE See MTEX . . . . . . . . . . . . . . . . . . 4:5solid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3space . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3Specific Element Identifier . . . . . . . . . . . 2:7SPRF See PROF . . . . . . . . . . . . . . . . . . 4:6SPRO . . . . . . . . . . . . . . . . . . . . . . . . . . 7:20SPVE . . . . . . . . . . . . . . . . . . . . . . . . . . 7:20SREC . . . . . . . . . . . . . . . . . . . . . 5:20, 7:18SREV . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15SRTO . . . . . . . . . . . . . . . . . . . . . . . . . . 7:13SSLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:9SSPH . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14star . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3STCA . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4STSEC . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4SVER . . . . . . . . . . . . . . . . . . . . . . . . . . 7:15Syntax diagram conventions . . . . . . . . . . 2:1

TTEXT . . . . . . . . . . . . . . . . . . . . . . . 4:6, 7:28text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3TUBE . . . . . . . . . . . . . . . . . . 6:5, 6:14, 7:14

UUDEF . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:25UNITS . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26USEC . . . . . . . . . . . . . . . . . . . . . . . . . . 7:26

Vvalue . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3varid . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3VISIBLE . . . . . . . . . . . . . . . . . . . . . . . . . 3:4

Wword . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

12.0Index page 3

catalogues and specifications reference manualcatalogues and specifications reference manual

Documents

aveva products

aveva product names

subsidiariesaveva solutions

subsidiaries disclaimany

tribon trademarks

associated software

intellectual property

unlicensed use