Catalogues and Specifications Reference Manual

Disclaimer

Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any 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 or entity 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.

Copyright

Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation 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 in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made.

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

The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective license agreements, and in accordance with the relevant User 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

Trademarks

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

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its subsidiaries, 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 or logo belongs to its respective owner.

Catalogues and Specifications Reference

Manual

Contents

Page

Reference Manual

Introduction . . . 1:1

About this Manual . . . 1:1

How this Manual is Organised . . . 1:1

Intended Audience . . . 1:2

Assumptions . . . 1:2

Document Conventions . . . 2:1

Command Description Format . . . 2:1

Syntax Diagrams . . . 2:1

Standard Command Tools . . . 2:3

Common Commands . . . 3:1

Entering PARAGON . . . 3:1

Saving Work and Updating Databases . . . 3:1

Exit PARAGON without Saving Changes . . . 3:2

Saving the Alpha Readout to File . . . 3:2

Switching Text Output Off . . . 3:3

Defining Colours . . . 3:4

Catalogue Database Structure . . . 4:1

What is the Catalogue For?. . . 4:1

Principal Features of the Catalogue Database . . . 4:1

12.0 ii

Structure of the Catalogue Database . . . 4:2

Catalogue (CATA) . . . 4:3

Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA) . . 4:4

Elements Used in Both Types of Catalogue Section/Category . . . 4:5

Elements Used in Piping Sections/Categories . . . 4:5

Elements Used in Structural Sections/Categories . . . 4:5

Text (TEXT) . . . 4:6

Parameters . . . 4:6

Component Parameters . . . 4:6

Insulation Parameters . . . 4:7

Structural Parameters . . . 4:7

Design DB Parameters. . . 4:8

Catalogue Components . . . 4:9

Piping Component (COMP; SCOM). . . 4:10

Profile (PROF; SPRF) . . . 4:11

Joint (JOIN; SJOI) . . . 4:11

Fitting (FITT; SFIT). . . 4:12

Component Parts . . . 4:12

Hierarchy

. . . 4:12

Selection Tables . . . 4:13

Hierarchy

. . . 4:14

Manipulating the Catalogue Database using PARAGON . . . 5:1

Basic Element Operation Commands . . . 5:1

Querying

. . . 5:1

Creation, Deletion etc. . . 5:1

Implicit Element Referencing . . . 5:2

List Position Changing . . . 5:2

Standard Attribute Setting . . . 5:2

Creating Catalogues, Sections and Catalogue Components. . . 5:3

Using Parameters. . . 5:4

Introduction. . . 5:4

Expressions Using Parameters . . . 5:5

Examples of Parameterisation . . . 5:6

Constructing 3D Pointsets . . . 5:9

PTAXI

. . . 5:9

PTCAR

. . . 5:10

PTMIX

. . . 5:11

Example of Defining a 3D Pointset. . . 5:12

Defining an Axis . . . 5:12

Defining a Distance . . . 5:13

Defining an Explicit Position . . . 5:13

Defining a Direction . . . 5:14

Defining Connection, Bore and Number. . . 5:14

Controlling the Appearance . . . 5:14

Specifying Pipe End Conditions for use by ISODRAFT . . . 5:14

Constructing Structural Pointsets . . . 5:15

Example of Defining a Structural Pointset . . . 5:15

The Neutral Axis Reference . . . 5:16

Defining an Axis . . . 5:16

Defining a Position . . . 5:17

Defining a Key . . . 5:17

Controlling the Appearance . . . 5:17

Constructing 3D Geomsets . . . 5:17

Constructing Structural Geomsets . . . 5:20

Reference Section . . . 5:21

Parameter-Controlled Attributes. . . 5:21

Axial Attributes . . . 5:22

Component Design and Representation in PARAGON . . . 6:1

Component Design . . . 6:1

P-point and P-line Representation . . . 6:2

P-points

. . . 6:2

P-lines

. . . 6:4

Geomset Primitive Representation . . . 6:5

Reference Section . . . 6:11

Model Settings . . . 6:11

Setting Representation for Piping Components . . . 6:14

Setting Profile Representation for Steelwork . . . 6:15

Setting Level Representation . . . 6:16

Setting Obstruction and Insulation Representation . . . 6:17

Setting P-Point Representation . . . 6:18

Setting P-Line Representation . . . 6:19

Full REPRESENTATION Syntax . . . 6:20

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

12.0 iv

3D Pointsets (PTSET) . . . 7:1

Axial P-point (PTAXI) . . . 7:2

Cartesian P-point (PTCAR) . . . 7:3

Mixed Type P-point (PTMIX) . . . 7:3

Position Type P-point (PTPOS) . . . 7:3

Structural Pointsets (PTSSET) . . . 7:3

3D Geomsets (GMSET) . . . 7:5

3D Geomset Primitives . . . 7:6

Box (SBOX) . . . 7:6

Boxing (BOXI) . . . 7:7

Cone (SCON) . . . 7:7

Cylinder (LCYL) . . . 7:8

Cylinder (SCYL) . . . 7:9

Slope-Bottomed Cylinder (SSLC). . . 7:9

Disc (SDIS). . . 7:10

Dish (SDSH). . . 7:11

Line (LINE) . . . 7:11

Line (SLINE). . . 7:11

Pyramid (LPYR) . . . 7:12

Circular Torus (SCTO) . . . 7:12

Rectangular Torus (SRTO) . . . 7:13

Snout (LSNO). . . 7:13

Sphere (SSPH). . . 7:14

Tube (TUBE) . . . 7:14

User-defined Extrusion (SEXT) . . . 7:15

Solid of Revolution (SREV) . . . 7:15

Negative 3D Geomsets (NGMSET) and Negative Primitives . . . 7:16

Structural Geomsets (GMSSET) . . . 7:18

Structural Geomset Primitives . . . 7:18

Structural Rectangle (SREC) . . . 7:18

Structural Annulus (SANN). . . 7:19

Structural Profile (SPRO) . . . 7:20

Detailing Text . . . 7:21

Material Text . . . 7:22

Connection Compatibility Tables . . . 7:22

COCDES Elements . . . 7:23

Bolting Tables . . . 7:23

Branch Reducer and Nominal Bore Size Tables . . . 7:24

Unit Types . . . 7:25

Use of Units . . . 7:26

General Text Elements . . . 7:28

User-defined Nominal Dimensions. . . 7:28

Creating Datasets in PARAGON . . . 8:1

Attributes of DATA Elements . . . 8:1

Querying Properties in DESIGN . . . 8:2

Real Properties of P-points, P-Lines and Geomsets . . . 8:3

Default Values . . . 8:3

Querying

. . . 8:3

Checking Catalogue Database Consistency using PARAGON . . . 9:1

Initiating a Standard Data Consistency Check . . . 9:1

What the Checking Facility Does . . . 9:1

Controlling the Detailed Checking Procedure. . . 9:2

Error Messages . . . 9:3

Piping Components in PARAGON. . . 10:1

Special Components . . . 10:2

Implied Tube. . . 10:2

Mitred Bends . . . 10:2

How Number of Cuts (NCUTS) Work. . . 10:3

Dynamic PPOINTS. . . 10:3

Pseudo Attributes . . . 10:4

Implied Geometry sets in PARAGON. . . 10:4

Naming Conventions . . . 10:4

Example Connection Type Codes . . . 10:5

Connection Compatibility Table . . . 10:6

Construction of Typical Piping Components . . . 10:7

Specification Constructor . . . 11:1

Content and Format of a Specification . . . 11:2

How Component Selection Works . . . 11:4

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

12.0 vi

Creating a Specification . . . 12:1

Accessing an Existing Specification . . . 12:2

Entering Tabular Data . . . 12:3

General Principles . . . 12:3

Special Characters in SPEC Data . . . 12:3

Headings

. . . 12:4

Defaults

. . . 12:5

Selector Answers . . . 12:5

Subtype Selectors: A Special Case . . . 12:6

Including User-defined Attributes in Specifications . . . 12:6

Including Comments in Specifications . . . 12:6

Editing an Existing Specification . . . 12:7

Adding a New SPCOM. . . 12:7

Deleting or Removing a SPEC or SPCOM. . . 12:7

Copying a Specification . . . 12:8

Outputting a Specification . . . 12:9

Defining the Destination . . . 12:9

Outputting Complete Specifications . . . 12:9

Controlling the Output Format . . . 12:9

Outputting Parts of Specifications . . . 12:9

How Bores Are Output . . . 12:10

Using Macros For SPECON Inputs . . . 12:10

Typical Specifications . . . 13:1

Selectors and Pointers for Piping Components . . . 13:1

Applicability . . . 13:1

Selectors

. . . 13:2

P-Point Zero: A Special Case. . . 13:3

Reference Pointers and Settings . . . 13:3

Examples From Piping Component Specifications . . . 13:5

Selectors and Pointers for Structural Components . . . 13:6

Applicability . . . 13:6

Selectors

. . . 13:6

Reference Pointers and Settings . . . 13:9

Examples From Structural Component Specifications . . . 13:9

Selectors and Pointers for Insulation . . . 13:10

Pipework Insulation . . . 13:10

Structural Insulation . . . 13:12

SPECONMODE Command Syntax Diagrams . . . 14:1

Syntax 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:1

Setting Up a Properties Database . . . 17:2

Description . . . 17:2

Design Layout Data . . . 17:2

Material Property Data . . . 17:2

Case Data . . . 17:2

Component Data . . . 17:2

Constraint Data . . . 17:2

Run Data

. . . 17:2

Material Property Data . . . 17:3

Hierarchy Description . . . 17:3

Material Properties . . . 17:3

Pointers from the Design DB and Specification . . . 17:4

Case Data . . . 17:4

Hierarchy Description . . . 17:4

Pointer from the Design DB . . . 17:5

Component Data . . . 17:5

Hierarchy Description . . . 17:5

Querying Calculated Results . . . 17:7

Pointer from the Specification . . . 17:7

Constraints Data . . . 17:7

Hierarchy Description . . . 17:7

Pointer from the Design DB . . . 17:8

Run Data . . . 17:8

12.0 viii

Hierarchy Description . . . 17:8

Use of Groups . . . 18:1

Exponential Numbers . . . 19:1

PROPCON Command Syntax Diagrams . . . 20:1

Syntax Diagrams . . . 20:1

1

Introduction

1.1

About this Manual

This document is a Reference Manual for the Catalogues and Specifications. It describes all of the PARAGON, SPECON and PROPCON keyboard-entered commands in detail. If you need information on how to use the Graphical User Interfaces refer to the Catalogue and Specifications User Guide.

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

1.2

How this Manual is Organised

This manual is divided into chapters, as follows:

Document Conventions describes notation and conventions used when entering commands.

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

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

Database using PARAGON

explains the procedure for defining the various types of element which represent the design components within the Catalogue database.

Component Design and Representation in PARAGON

introduces the principles of catalogue component design 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, bolting tables and unit of measurements.

Creating Datasets in PARAGON explains the concept of datasets, used to store catalogue data which needs to be queried from DESIGN or DRAFT and which is not accessible by other means.

Checking Catalogue Database Consistency using PARAGON

describes how to check the catalogue database for inconsistencies from within PARAGON, so that errors can be corrected before the data is used in a design. Piping Components in PARAGON summarises some p-point conventions which should be

12.0 1:2

1.3

Intended Audience

In most companies the responsibility for creating Catalogues and Specifications is restricted to a team of Standards Engineers within the Production Engineering Department or its equivalent. You might, therefore, be a member of such a team setting up or updating a Specification. Alternatively, you might be a pipework or structural designer who needs to use a Specification to select a suitable component and who wishes to understand the principles underlying the selection process.

1.4

Assumptions

You are assumed to be familiar with the general principles of using PDMS, although some of the 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

2

Document Conventions

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

2.1

Command Description Format

You will find that commands are described in a standard format. This format is described below.

• 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 given function.

• 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 conditions are given here.

• Command Syntax This shows the actual command with its possible options. The

notation used for commands is described below (Syntax Diagrams). • Querying The relevant querying options are listed.

2.2

Syntax Diagrams

The commands described in this manual have their legal command and interrogation options presented in the form of syntax diagrams. These diagrams formalise the precise command sequences which may be used and are intended to supplement the explanations given 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 for cross-referencing purposes in the text and within other syntax diagrams, are supplemented by fuller descriptions where they are not self-explanatory.

• Commands to be input from the Command Line are shown in a combination of

uppercase and lowercase letters. In general, these commands can be abbreviated; the capital letters indicate the minimum permissible abbreviation.

Note: This convention does not mean that the second part of the command must be typed

in lowercase letters; commands may be entered in any combination of uppercase and lowercase letters.

12.0 2:2

For example, the command

DEFault

may be input in any of the following forms:

DEF

DEFA

DEFAU

DEFAUL

DEFAULT

Commands shown wholly in uppercase letters cannot be abbreviated. • Syntax diagrams are generally read from top left to bottom right.

• Points marked with a plus sign (+) are option junctions which allow you to input any one of the commands to the right of the junction. Thus

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

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

permits any combination of option1 and/or option2 and/or option3 (each separated by at least one space) to be used. The ‘options’ may define commands, other syntax diagrams, or command arguments). The loop-back construction may form an exception 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 --+--->

2.3

Standard Command Tools

Command Tool is a generic term covering command arguments (or atoms) and command

parts. Both classes of command tool fit into ordinary commands and provide different ways

of 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 of them) summarised for convenience:

Command Arguments

Command arguments are also called atoms because they cannot be broken down any further. They are individual units which PARAGON, SPECON or PROPCON can recognise as constituents of a complete command. They usually need to be separated by spaces so that they are individually distinguishable. Command arguments are distinguished from the other command parts by being written in lower case italics. The principal command arguments are:

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 appropriate attribute. For example, DUTY ’Low Pressure’. (Note that paired quotation marks ‘...’ 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 a PDMS 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 the format !name, where ‘name’ is a text string. For example: !COUNTER !height

comma the , character, which can be used to concatenate PARAGON, SPECON or PROPCON commands; for example: NEW UNIT, BUNI INCH, DUNI FINC plus minus the +, -, * and / characters, which can be used within

12.0 2:4

Command Parts

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

Expressions

Any mathematical, logical or alphabetical expression whose result replaces it in the command syntax.

Dimensions

A physical dimension entered using default or explicit units.

Catalogue Element Types

A word used to represent a specific type of element in the Catalogue database hierarchy.

Element Identifiers

Methods for specifying which database element you want your next commend to act upon.

Cursor-picking Identifier (<sgid>)

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

Expressions (<eval>)

If a value given within a command needs to be calculated from other known values, you can enter an expression from which the required result is to be evaluated by PARAGON, SPECON or PROPCON as it executes the command. Such an expression must be enclosed between parentheses (...) to identify where it begins and ends.

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

Dimensions (<uval>)

Once the working units have been specified, all dimensions input subsequently will be assumed to be in those units unless you override them. (Note that these are simply specific examples of the use of ‘real’ expressions. You can include explicit units of measurement when entering a value in any expression.)

Examples

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 the host 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

12.0 2:6

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

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 relative position 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

12.0 2:8

Examples

Cursor-picking Identifier (<sgid>)

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

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

3

Common Commands

The commands in this section are available throughout PDMS.

3.1

Entering PARAGON

The commands for PARAGON and PROPCON are combined within the PARAGON module so that you do not need to switch between modules. SPECON commands are also available in 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 or SPECON to be accessed at any time.

Keyword: _{SAVEWORK GETWORK}

Description: These two commands are complementary. SAVEWORK lets you update the databases to incorporate any changes you have made during your current PARAGON session (since your last SAVEWORK). GETWORK lets you refresh your view of all READ or Multiwrite databases to pick up any changes that others may have made since you first opened them. Both commands can be restricted to specific databases within the current MDB by following them with a list of numbers. These numbers represent specific databases in the order they appear in the output of the STATUS command, which may be given in MONITOR or in the MDB mode of any GUI module. If no database numbers are given, then the commands apply to the whole MDB.

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

12.0 3:2

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 the

file and the screen until the file is closed, or until you change to another PDMS module.

Keyword: _{QUIT FINISH}

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

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 the computer operating system. Two types of output are available, depending on the command used.

ALPHA LOG enables the contents of either or both of the COMMANDS

and REQUESTS alpha regions to be written to a file.

ALPHA FILE enables the contents of the REQUESTS region only to be

written to file.

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

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 in file /LF1

ALP LOG /LF1 OVER COMM - as above, but overwrite existing file /LF1

ALP LOG /LF2 - log information displayed in both alpha regions in file /LF2 ALP FILE /LF2 - log information displayed in REQUESTS region only

ALP LOG END - finish logging information

ALP FILE END

Keywords: _TRACE

Description: This command, applicable in TTY mode only, controls the automatic output of the Current Element name and attributes. With Trace set to ON, the attributes display is automatically updated for each element accessed. 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.

12.0 3:4

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 the current primitive.

• The CE colour is used for the element currently being accessed (i.e. the element highlighted in the Members list). This may be either a primitive or a significant element. • The Visible colour is used for any element in the display other than those to which the

active or CE colours apply.

• The Active and Visible elements together constitute the Draw List. The predefined colour mixes which you may specify by name are as follows:

Keywords: _{COLOUR ACTIVE CE VISIBLE AIDS}

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

The colours may be assigned by using the COLOUR command to define the Red-Green-Blue mix for a colour number or to assign a predefined colour mix by name. PARAGON allows the use of 100 user-definable colours, plus some specific ones which are assigned to items which need to 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

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

12.0 3:6

The default colour assignments are:

Examples:

Note: When colours are mixed in their Red, Green and Blue constituents, the command

line must contain values for all three constituents in the correct order. The numbers entered for the relative proportions of the basic colours must each be in the range 0-100, but they are not percentages of the overall colour and so do not need to add up to 100.

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, green and blue

COL VISIBLE BRIGHTRED Sets the colour for displaying components to bright red

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.0 3:8

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 (for

example, CATA, BLTA, SPREF) are PDMS element names. When an element’s member list is queried in PDMS, each element type will be displayed as a four-character name. Five or six four-characters are occasionally used in this chapter where this gives a ‘PDMS’ name which is closer to the element’s ‘English’ name, for example 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 pipework designer or structure designer would refer when using ‘conventional’ design methods. It contains details of all available components (piping and structural), including their dimensions, geometry and drawing symbols. Whereas the conventional parts catalogue is a book held in the DESIGN Office, the PDMS Catalogue is a database held on the computer.

4.2

Principal Features of the Catalogue Database

If a new Catalogue database (DB) is required, PARAGON can be used to construct it - see Manipulating the Catalogue Database using PARAGON for details of creating and manipulating a Catalogue DB using PARAGON.

The Catalogue data is held according to a strict hierarchy which is similar in form to that of the 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 a Specification Component (SPCOM) in the Specification. This in turn points to a Catalogue Component (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 Specifications may be specific to a company but general to a number of projects in that company. For example, the same Catalogue Component may be referred to many times in a particular design 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 these macros can then be used to build up a project-specific Catalogue database containing only those Components which might be used on that project.

12.0 4:2

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

4.3

Structure of the Catalogue Database

Catalogues are constructed as a hierarchy of elements. Each element has certain

attributes and some may contain further member elements. The complete Catalogue

hierarchy 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 these are common to all the elements described below.

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

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 be used; e.g. PIPE, FITT.

12.0 4:4

A CATA can contain a number of Catalogue Sections. These are of two types: Piping

Sections (SECT) and Structural Sections (STSEC). They are the principal administrative

elements by which the Catalogue is divided and arranged. The Catalogue can also contain

Text elements (TEXT) - see General Text Elements.

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

Note that the following elements may also exist within the Catalogue database at the same level as CATA:

• Units World (UNITS)

• Connection Tables (CCTAB) • Bolt Tables (BLTAB)

• Specification World (SPWL) • Group World (GPWL)

Units, Connection Tables and Bolt Tables are described in Catalogue Database Elements Setup in PARAGON, the latter element type being described in more detail in the ISODRAFT Reference Manual. Specification World elements are detailed in Specification Constructor.

4.5

Catalogue Sections (SECT and STSEC) and

Categories (CATE and STCA)

Sections and Categories are administrative elements which let you segregate particular types of catalogue data into logical parts of the hierarchy. Sections, which subdivide an overall CATA, are obligatory; Categories, which subdivide Sections, are optional (although their use is recommended).

There are two types of Catalogue Section: Piping Sections (SECT) and Structural

Sections (STSEC). Both have the following attributes:

• 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 Structural

Category (STCA). Both have the following principal attributes:

• DESC - a textual description of the category.

• PURP - a PDMS word showing the specific purpose for which that category is

intended. This should be set to the same STYPE as in the Specification with which it is to be used; e.g. GLOB, GATE etc. for a VALV.

• GTYP - a PDMS word showing the generic type for elements contained in the section.

• SKEY - a textual symbol key showing how the item is represented in isometric

drawings (see the ISODRAFT Reference Manual). • PTRE - a reference to a 3D P-point Set (PTSE).

• GMRE - a reference to a 3D Geometry Set (GMSE).

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

Both types of Catalogue Section or Category contain the elements 3D P-point Set, 3D

Geometry Set, Data Set, Detailing Text and Material Text, as described in Elements Used in Both Types of Catalogue Section/Category. Piping Sections/Categories may also contain

Piping Components, as described in Elements Used in Piping Sections/Categories. Structural Sections/Categories may also contain Structural Components (Profiles, Joints and Fittings), Structural Pointsets, Negative 3D Geometry Sets and Structural

Geometry Sets, as described in Elements Used in Structural Sections/Categories.

4.5.1

Elements Used in Both Types of Catalogue Section/Category

• 3D P-point Set (PTSET) (usually abbreviated to 3D Pointset) - a definition of the

position, direction, connection type and bore of a Component’s P-points, to be used by DESIGN, ISODRAFT, etc.

• 3D Geometry Set (GMSET) (usually abbreviated to 3D Geomset) - a grouping of 3D

primitive elements, defining the dimensions, orientation and obstruction geometry of each 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 is required for use in DESIGN or DRAFT; e.g. the cross-sectional area of a structural steel member calculated from its parameterised dimensions.

• Detailing Text (DTEX) - elements containing general descriptive text relating to a

Component. Referred to from SPCOM elements in the Specification. For further details see Detailing Text.

• Material Text (MTEX) - elements containing text describing the material(s) from which

the physical Component is constructed. Referred to from SPCOM elements in the Specification. For further details see Material Text.

4.5.2

Elements Used in Piping Sections/Categories

A Piping Section or Category may contain all those elements listed in Elements Used in Both Types of Catalogue Section/Category plus the following:

• Piping Component (COMP) - an element defining a piece of pipework. It consists of a

list of values (known as component parameters) and references to a 3D Pointset element and a 3D Geomset element. The Pointset and Geomset make use of the component parameter values in defining the size, geometry and connection types of the Piping Component.

4.5.3

Elements Used in Structural Sections/Categories

A Structural Section or Category may contain all those elements listed in Elements Used in Both Types of Catalogue Section/Category plus the following:

• Structural Pointset (PTSSET) - a definition of the position and direction of a

Component’s P-lines, to be used by DESIGN.

• Negative 3D Geometry Set (NGMSET) (usually abbreviated to Negative 3D Geomset) - a grouping of 3D negative primitive elements (representing holes, end

preparations etc.), defining the dimensions, orientation and obstruction geometry of each primitive. Used by DESIGN and the Drawing modules.

12.0 4:6

• Structural Geometry Set (GMSSET) (usually abbreviated to Structural Geomset) - a

grouping of 2D primitive elements, defining the dimensions, orientation and obstruction geometry 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 to a Structural Pointset element and a Structural Geomset element. The Pointset and Geomset make use of the component parameter values in defining the size and geometry of the Component. In the design process, a length is associated with a Profile to produce a Section.

• Joint (JOIN) - a 3D structural Component defining a physical means of attaching one

Section to another. It consists of a list of component parameters and references to a

Structural Pointset element, a 3D Pointset element and a 3D Geomset element. The

two Pointsets and the Geomset make use of the component parameter values in defining the size and geometry of the Component.

• Fitting (FITT) - a 3D structural Component defining an object which is physically

attached to a Section but is not part of the structure formed by Sections and Joints. For example, a Fitting may be used to attach a pipe hanger to a Section. The element consists of a list of component parameters and references to a 3D Pointset element and a 3D Geomset element. The Pointset and Geomset make use of the component parameter values in defining the size and geometry of the Component.

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

4.6

Text (TEXT)

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

4.7

Parameters

Parameters define the size, geometry and other characteristics of Components. They are used in setting the attributes of the Pointsets, Geomsets and Datasets to which Component elements refer.

All classes of Component can use component parameters, design parameters and

insulation parameters. Structural Components can also use attached and owning design parameters. Component parameters are defined in the Catalogue; the other classes of

parameters allow characteristics to be set during the design process.

4.7.1

Component Parameters

Piping Components (COMP), Profiles (PROF), Joints (JOIN) and Fittings (FITT) all have a PARAM attribute which lists the component parameters.

Creating Catalogues, Sections and Catalogue Components describes how to set up the component parameters of a Component. You may define default values which PARAGON will use if you are working with a Component whose component parameters have not been set 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 for the full syntax of how to set default values.

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

4.7.2

Insulation Parameters

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

Component of the design element.

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

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

MODEL SETTINGS IPARAM 3 25

defines a specimen value for insulation parameter number 3. See Setting Obstruction and Insulation 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 current PARAGON session.

4.7.3

Structural Parameters

These 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 of Joint or Fitting may be adjusted automatically in the Design DB to fit a connected Section of any 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 a Piping Component, Profile, Joint or Fitting. In the case of a Joint, it also depends on how the Component is used in the Design DB.

12.0 4:8

Joints are of two types: primary and secondary. A primary Joint has an attached Section in the Design DB; a secondary Joint has an attached Section and an owning Section. (See the DESIGN Reference Manual for details of primary and secondary Joints.) Note that primary and secondary Joints are represented by the same class of Catalogue Component, but the settings of their attributes and the attributes of their Pointsets and Geomsets are different.

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

Components which have an attached Section (i.e. primary and secondary Joints) can use attached parameters to define the attributes of their Pointsets and Geomsets. Attached parameters correspond to the component parameters of the attached Section. For example, when a Joint component uses APARAM 2, it picks up the value of the PARAM 2 of the Joint’s attached Section.

Similarly, Components which have an owning Section (i.e. secondary Joints and Fittings) can use owning parameters in defining the attributes of their Pointsets and Geomsets. Owning parameters correspond to the component parameters of the owning Section. For example, when a Joint or Fitting component uses OPARAM 5, it picks up the value of the PARAM 5 of the component’s owning Section.

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

MODEL SETTINGS APARAM 2 300

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

4.7.4

Design DB Parameters

These allow structural Components to take dimensions from Design Parameter Arrays in the Design DB. Each design element has a Design Parameter Array with ten values. (See the 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 design

element which refers to it (via the SPREF). For example, the DES PARAM 4 of a Component is the fourth value in the Design Parameter Array of the design element. Design parameters can be used anywhere that component parameters can be used.

Design attached parameters and design owning parameters allow a Joint or Fitting

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

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

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

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

Figure 4:3. Table of Parameters and Components

4.8

Catalogue Components

There are four classes of Catalogue Component: • Piping Component

• Profile • Joint • Fitting

Their attributes are described in the following sections. These attributes (other than the component parameters) must be set to actual values (words or references to other elements). They cannot be defined using parameters.

A reference to an element is usually set to the name of the element, for example /PTSR3, but it can also be set as a general identifier, for example:

PTSE 4 OF SECT 2 OF CATA /ASA-CATA

The attributes of Pointsets and Geomsets may be defined using component parameters, design parameters and insulation parameters. Where appropriate, attributes for structural items may also be defined using design owning parameters and design attached parameters.

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

Catalogue Components do not have member elements. Piping Comp't Profile Prim'y Joint Sec'y Joint 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)

12.0 4:10

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 - gasket

HELE - hanger element

INST - instrument

INSU - insulation

LJSE - lap joint stub end

NOZZ - nozzle

OLET - weldolets

PCOM - pipe component

REDU - reducer

SHU - standard hook-up

TEE - fitting tee

TRAC - tracing

TRAP - steam trap

TUBE - implied tube

UNIO - union

VALV - valve

VENT - open-ended pipe or vent

VFWA - four-way valve

VTWA - three-way valve

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

• DTREF - reference to a Dataset element.

4.8.2

Profile (PROF; SPRF)

• 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:

• DTREF - reference to a Dataset element.

4.8.3

Joint (JOIN; SJOI)

• 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 (the

Joint’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

12.0 4:12

connection type attribute of the attached Section (CTYS or CTYE) has not been set when the Joint is selected in the design process, the attribute will automatically be set to the value of CTYA. The PDMS data consistency checks (see the DESIGN Reference Manual) check whether the connection type attributes of the Joint and attached Section match.

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

• DTREF - reference to a Dataset element.

4.8.4

Fitting (FITT; SFIT)

• 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 pipe hanger (HCON or TCON) has not been set when the Fitting is selected in the design process, the attribute will automatically be set to the value of CTYA. The PDMS data consistency checks (see the DESIGN Reference Manual) check whether the connection type attributes of the Fitting and pipe hanger match.

• DTREF - reference to a Dataset element.

Note: For details of the MODEL SETTINGS command syntax used to set default values

for component parameters, and specimen values for other classes of parameter, see Model Settings.

4.9

Component Parts

The GPART element allows catalogue components to be fully defined in one place and without 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. It is 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, and these can be used for all disciplines except piping.

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

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

4.9.1

Hierarchy

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

4.10

Selection Tables

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

1. Selection Criteria can be used to offer you a choice of Parts based on the current design 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 with matching 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 the

catalogue without using selection tables at all, however the use of selection tables is recommended where only a subset of the whole Part catalogue should be used on a particular project.

12.0 4:14

4.10.1

Hierarchy

Selection 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 least one 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.

5

Manipulating the Catalogue Database using

PARAGON

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

This section describes PARAGON keyboard-entered commands in detail. If you need information on how to use PARAGON to carry out the principal Catalogue design activities with minimal use of the keyboard, by using the Graphical User Interface, refer to the Catalogues 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

12.0 5:2

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 and some are used in this chapter without further explanation. However, the element types which the above commands operate on relate to the Catalogue database rather than the Design database (so, for example, NEXT SITE is meaningless in PARAGON).

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