Tài liệu phần mềm pdms

i liệu này là tutorial có sẵn trong PDMS do tác giả Trịnh Hoài ... cách sử dụng các cửa sổ, menu và form trong giao diện của PDMS. ... thiết kế hiện tại trong cửa số 3D View, và tập cách kiểm sóat khung nhìn. ... Trong phần thực hành này, ta sẽ chọn A3B làm thông số mặc định cho tất cả các component. i liệu này là tutorial có sẵn trong PDMS do tác giả Trịnh Hoài ... cách sử dụng các cửa sổ, menu và form trong giao diện của PDMS. ... thiết kế hiện tại trong cửa số 3D View, và tập cách kiểm sóat khung nhìn. ... Trong phần thực hành này, ta sẽ chọn A3B làm thông số mặc định cho tất cả các component. i liệu này là tutorial có sẵn trong PDMS do tác giả Trịnh Hoài ... cách sử dụng các cửa sổ, menu và form trong giao diện của PDMS. ... thiết kế hiện tại trong cửa số 3D View, và tập cách kiểm sóat khung nhìn. ... Trong phần thực hành này, ta sẽ chọn A3B làm thông số mặc định cho tất cả các component.

Reference Manual

Information 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

Copyright

Copyright 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 material

or 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 licence 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 2007

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

Catalogues and Specifications Reference

Manual

Catalogues and Specifications

Introduction 1:1 About this Manual 1:1 Manual Structure 1:1 Who is this Manual Meant For 1:1 Communicating within PDMS 2:1 Commands 2:1

Command Description Format 2:1 Syntax Diagrams 2:1 Standard Command Tools 2:2

General PDMS Commands 3:1 Entering PARAGON or SPECON 3:1 Leaving PARAGON or SPECON 3:1 Saving and Restoring the Current Display Status 3:1 Saving Work and Updating Databases 3:2 Exit from PARAGON, SPECON or PROPCON without Saving Changes 3:3 Saving the Alpha Readout to File 3:3 Audible Error Trace 3:4 Switching Text Output Off 3:5 Defining Colours 3:5

Catalogue DB 4:1 Content and Format of a Specification 4:3 How Component Selection Works 4:5 General Description 1:1 Catalogue Database 2:1 What is the Catalogue For? 2:1 Principal Features of the Catalogue Database 2:1 Structure of the Catalogue Database 2:2 Catalogue (CATA) 2:3 Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA) 2:4

Elements Used in Both Types of Catalogue Section/Category 2:5 Elements Used in Piping Sections/Categories 2:5 Elements Used in Structural Sections/Categories 2:5

Text (TEXT) 2:6 Parameters 2:6

Component Parameters 2:7 Insulation Parameters 2:7 Structural Parameters 2:7 Design DB Parameters 2:8

Catalogue Components 2:9

Piping Component (COMP; SCOM) 2:10 Profile (PROF; SPRF) 2:11 Joint (JOIN; SJOI) 2:12 Fitting (FITT; SFIT) 2:12

Accessing an Element via a Reference Pointer 3:3 Other Navigation Commands 3:3 Component Design and Representation 4:1 Component Design 4:1 P-point and P-line Representation 4:2

P-points 4:2 P-lines 4:4

Geomset Primitive Representation 4:5 Reference Section 4:11

Model Settings 4:11 Setting Representation for Piping Components 4:13 Setting Profile Representation for Steelwork 4:14 Setting Level Representation 4:15 Setting Obstruction and Insulation Representation 4:16 Setting P-Point Representation 4:17 Setting P-Line Representation 4:18 Full REPRESENTATION Syntax 4:18

Pointsets and Geomsets 5:1

D Pointsets (PTSET) 5:1

Axial P-point (PTAXI) 5:2 Cartesian P-point (PTCAR) 5:2 Mixed Type P-point (PTMIX) 5:3 Position Type P-point (PTPOS) 5:3

Structural Pointsets (PTSSET) 5:3

D Geomsets (GMSET) 5:5

D Geomset Primitives 5:6

Box (SBOX) 5:6 Boxing (BOXI) 5:7 Cone (SCON) 5:7 Cylinder (LCYL) 5:8 Cylinder (SCYL) 5:8 Slope-Bottomed Cylinder (SSLC) 5:9 Disc (SDIS) 5:10 Dish (SDSH) 5:10 Line (LINE) 5:11 Line (SLINE) 5:11 Pyramid (LPYR) 5:11

Circular Torus (SCTO) 5:12 Rectangular Torus (SRTO) 5:13 Snout (LSNO) 5:13 Sphere (SSPH) 5:14 Tube (TUBE) 5:14 User-defined Extrusion (SEXT) 5:15 Solid of Revolution (SREV) 5:15

Negative 3D Geomsets (NGMSET) and Negative Primitives 5:16 Structural Geomsets (GMSSET) 5:18 Structural Geomset Primitives 5:18

Structural Rectangle (SREC) 5:18 Structural Annulus (SANN) 5:19 Structural Profile (SPRO) 5:20

Manipulating the Catalogue Database 6:1 Basic Element Operation Commands 6:1

Querying: 6:1 Creation, deletion etc: 6:1 Implicit element referencing: 6:1 List position changing: 6:2 Standard attribute setting 6:2

Creating Catalogues, Sections and Catalogue Components 6:2 Using Parameters 6:4

Introduction 6:4 Expressions Using Parameters 6:4

Examples of Parameterisation 6:5 Constructing 3D Pointsets 6:8

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

Constructing Structural Pointsets 6:15

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

Constructing 3D Geomsets 6:17 Constructing Structural Geomsets 6:20 Reference Section 6:21

Parameter-Controlled Attributes 6:21 Axial Attributes 6:22

Other Uses of PARAGON 7:1 Detailing Text 7:1 Material Text 7:2 Connection Compatibility Tables 7:2 Bolting Tables 7:3 Unit Types 7:4

Use of Units 7:5

General Text Elements 7:7 User-defined Nominal Dimensions 7:7 Datasets 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 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 P-point Conventions for Piping Components A:1

Special Components A:1

Implied Tube A:1 Mitred Bends A:2 How End Cuts Work A:3 Dynamic PPOINTS A:3 Pseudo Attributes A:4 Implied Geometry sets in PARAGON A:4

Setting Up a Catalogue B:1 Naming Conventions B:1 Example Connection Type Codes B:1 The Connection Compatibility Table B:2 Construction of Typical Piping Components C:1 Summary of Element Types D:1 Glossary D:1 Functional Groups D:4 General Description 1:1 Who This Manual is Meant For 1:1 How This Manual is Set Out 1:1 Catalogues and Specifications 2:1 Catalogue DB 2:1 Content and Format of a Specification 2:3 How Component Selection Works 2:4 How To Use SPECON 3:1 Creating a Specification 3:1 Accessing an Existing Specification 3:2 Entering Tabular Data 3:2

General Principles 3:2 Special Characters in SPEC Data 3:3 Headings 3:4 Defaults 3:5 Selector Answers 3:5 Subtype Selectors: A Special Case 3:5 Including User-defined Attributes in Specifications 3:6

Including Comments in Specifications 3:6

Editing an Existing Specification 3:6

Adding a New SPCOM 3:6 Deleting or Removing a SPEC or SPCOM 3:6

Copying a Specification 3:8 Outputting a Specification 3:8

Defining the Destination 3:8 Outputting Complete Specifications 3:8 Controlling the Output Format 3:9 Outputting Parts of Specifications 3:9 How Bores Are Output 3:9

Using Macros For SPECON Inputs 3:10 Details of Typical Specifications 4:1 Selectors and Pointers for Piping Components 4:1

Applicability 4:1 Selectors 4:2 P-Point Zero: A Special Case 4:3 Reference Pointers and Settings 4:3 Examples From Piping Component Specifications 4:5

Selectors and Pointers for Structural Components 4:5

Applicability 4:5 Selectors 4:6 Reference Pointers and Settings 4:9 Examples From Structural Component Specifications 4:9

Selectors and Pointers for Insulation 4:10

Pipework Insulation 4:10 Structural Insulation 4:11

Command Syntax Diagrams .A:1 Introduction A:1 Conventions A:1 Command Arguments A:2 Syntax Diagrams A:3

<speca> A:3

<table> A:3

<heading> A:4

<default> A:4

Design Layout Data 2:1 Material Property Data 2:1 Case Data 2:1 Component Data 2:1 Constraint Data 2:2 Run Data 2:2

Material Property Data 2:2

Hierarchy Description 2:2 Material Properties 2:2 Pointers from the Design DB and Specification 2:3

Case Data 2:4

Hierarchy Description 2:4 Pointer from the Design DB 2:4

Component Data 2:5

Hierarchy Description 2:5 Querying Calculated Results 2:6 Pointer from the Specification 2:6

Constraints Data 2:6

Hierarchy Description 2:6 Pointer from the Design DB 2:7

Run Data 2:8

Hierarchy Description 2:8

Some General Commands 3:1 Introduction 3:1

CLOCK Command 3:1 COPY Command 3:2 DELETE Command 3:2 END Command 3:2 GOTO Command 3:2 INCLUDE Command 3:2 LOCK Command 3:3 NAME Command 3:3 NEW Command 3:3 OLD Command 3:3 QUERY Command 3:4 RENAME Command 3:4 REORDER Command 3:4 SAME Command 3:5 UNLOCK Command 3:5 UNNAME Command 3:5 Reference Numbers 3:5 Exit from PROPCON 3:5 Use of Groups 4:1 Exponential Numbers 5:1 PROPCON Syntax Graphs A:1 Introduction A:1 Conventions A:1 Command Arguments A:2 The PROPCON Syntax Graphs A:2 Properties Database Elements .B:1 Properties Database Hierarchy B:1 Database Elements B:1 Attributes of Material Data Elements B:3

Material World (MATW) B:3 Solid (SOLI) B:3

Fluid (FLUI) B:3 Table of Density (TDEN) B:3 Table of Stress (TSTR) B:3 Table of Poisson’s Ratio (TPOI) B:4 Table of Coefficient of Expansion (TEXP) B:4 Table of Young’s Modulus (TYOU) B:4 Table of A Property (TAPR) B:4 Table of B Property (TBPR) B:4 Table of C Property (TCPR) B:5 Text (TEXT) B:5 Spot Density (SDEN) B:5 Spot Stress (SSTR) B:5 Spot Poisson’s Ratio (SPOI) B:5 Spot Coefficient of Expansion (SEXP) B:6 Spot Young’s Modulus (SYOU) B:6 Spot A Property (SAPR) B:6 Spot B Property (SBPR) B:6 Spot C Property (SCPR) B:6

Attributes of Case Data Elements B:7

Case World (CASW) B:7 Case Type (CAST) B:7 Case (CASE) B:7

Attributes of Component Data Elements B:7

Component World (CMPW) B:7 Component Type (CMPT) B:8 Component Data (CMPD) B:8 Tube Data (TUBD) B:8

Attributes of Constraint Data Elements B:9

Constraint World (CONW) B:9 Constraint Type (CONT) B:9 Constraint (CONS) B:9 Case Table Element (TCAS) B:10

Attributes of Run Data Elements B:10

Run World (RUNW) B:10 Run (RUN) B:10 Card (CARD) B:10

Attributes of Group Elements B:10

Group World (GPWL) B:10 Group (GROU) B:11

Index of Commands C:1 Introduction C:1 List of Commands C:1

General

1 Introduction

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 PDMS training course and are familiar with the basicconcepts underlying the use of PDMS

This manual is broken down in to four parts:

• Part 1 gives generic command details

• Part 2 gives details of the PARAGON commands

• Part 3 gives details of the SPECON commands

• Part 4 gives details of the PROPCON commands

In most companies the responsibility for creating Catalogues and Specifications is restricted

to 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 use

a Specification to select a suitable component and who wishes to understand the principlesunderlying the selection process

You 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

This manual does not assume that you are familiar with the details of that module

2 Communicating within PDMS

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.1 Command Description Format

Once you have located the required command in this manual, you will find that it isdescribed 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 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 The

notation used for commands is described below (Syntax Diagrams)

• Querying The relevant querying options are listed.

2.1.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 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 terminal 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

For example, the commandDEFault

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

2.1.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 controlthe behaviour of the macro when it is executed

• Standard Concepts - which apply globally within PARAGON, SPECON or PROPCONSome of the main command tools (or the PARAGON, SPECON or PROPCON variations ofthem) 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 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 anappropriate attribute For example, DUTY ’Low Pressure’ (Note thatpaired 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, DUNIFINC

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

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

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

when entering a value in any expression.)

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 EX 3 5500 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)

SCOMponent COMPonent number

Fitting Components:

Note: FITTing number is not a valid option)

3D Geomset elements:

Negative 3D Geomset elements:

Structural Geomset elements:

SSLCylinder SSPHere LCYLinder SCYLinder

SVERtex

NSCYlinder NSCTorus NSREvolution NSRTorus

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

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

3 General PDMS Commands

The commands in this section are available throughout PDMS

The commands for PARAGON and PROPCON are combined within the PARAGON module

so that you do not need to switch between modules The SPECON commands are withinthe distinct SPECON module To access them from the PARAGON module it is necessary toswitch to the SPECON module

To enter PARAGON type PARAGONMODE

To enter SPECON type SPECONMODE

Commands within PROPCON are accessed from within the PARAGON module so it is notnecessary to switch to a PROPCON module

At any point during a PARAGON or SPECON session, you can elect to leave and enteranother module of PDMS This is simply a matter of inputting the name of the module to beaccessed At this point, PARAGON or SPECON will automatically save the results of theworking session and change to the new module However, all graphical displays, forms andmenus will need to be redefined at the beginning of the next session In order to avoidhaving to redefine a view and screen layout, it is possible to save the current status of a

working session by use of the RECREATE command

Note: Forms resized or moved using the cursor will be INSTALLed to their original size.

Keyword: PARAGON or SPECON

Description: This command is available throughout PDMS, allowing PARAGON or

SPECON to be accessed at any time

Keyword: RECREATE INSTALL

Description: If the intention is to leave PARAGON, SPECON or PROPCON for a short

period only this facility allows the display definition and status (includingthe full forms and menus set) to be saved, for restoration later

> INSTALL SETUP name >

RECREATE /PARA1 - saves the display status in file /PARA1

RECREATE /PARA1 OVER - as above, but an existing file /PARA1 is overwritten

RECRE DISPLAY /PARA1 - saves nodal settings, e.g units, representation etc

- Read back in using $M/name

INSTALL SETUP /PARA1 - restores the display definition stored in file /PARA1

Keyword: SAVEWORK GETWORK

Description: These two commands are complementary SAVEWORK lets you update

the databases to incorporate any changes you have made during yourcurrent PARAGON, SPECON or PROPCON 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 madesince 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 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 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 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 unlessyou really need to use it

3.5 Exit from PARAGON, SPECON or PROPCON without

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 PDMSmodule

Keyword: QUIT FINISH

Description: This command exits from PARAGON, SPECON or PROPCON without

saving any changes or the display setup QUIT has the effect of deleting any changes made since the last SAVEWORK, module

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 ageneral output facility

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

Description: When a macro error occurs, there is an audible alarm at the workstation

to signal that the error has occurred Occasionally, macro errors can beanticipated and no audible warning is required This command allows theaudible warning to be switched on or off either interactively or via amacro

If the audible warning is ON, it will sound whenever an error alert isdisplayed

ALARM ON - Switches the audible tone on (this is the default)

ALARM OFF - Suppresses the audible tone until it is turned on again

3.8 Switching Text Output Off

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

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

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 ofcolour The colours used have default settings, but these may beredefined

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 predefinedcolour mix by name PARAGON, SPECON or PROPCON allows the use

of 100 user-definable colours, plus some speciffic ones which areassigned to items which need to be readily distinguishable in the display

The predefined colour mixes which you may specify by name are as follows:

The default colour assignments are:

Current element yellow

Visible elements lightgrey

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

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 blueCOL VISIBLE BRIGHTRED Sets the colour for displaying components to bright

red

Current element yellow

4 Catalogues and Specifications

This section gives an overview of the structure of a typical Catalogue DB, which containsinformation about standard piping and structural components available in a PDMS project,and explains how the Specifications are used within this hierarchy For more detailed

explanations of the setting up of a Catalogue DB, see the PARAGON Reference Manual.

Note: Words of four or five uppercase characters in this chapter represent PDMS elements

(for example, CATA, BLTAB, SPREF) PDMS stores these as four character namesonly; the fifth character is given here to make the abbreviations easier to understand.For example, SPREF (rather than SPRE) is used for Specification Reference

Note: The elements referred to throughout this manual by the names COMP, FITT, DTEXT

and MTEXT are stored in the PDMS database hierarchy as SCOM, SFIT, SDTE andSMTE elements, respectively The simplified names, which omit the ‘S’ prefix, areused here because they are easier to interpret as you read the manual

The information held in a Catalogue DB is split into several functional groups which togethercompletely define every aspect of the components listed within that catalogue Thesefunctional groups, which are the highest level elements in the Catalogue DB below WORLD,are shown in Figure 4:1.: The top-level structure of a Catalogue DB

Figure 4:1 The top-level structure of a Catalogue DB

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

That part of the hierarchy below a Catalogue element which is relevant when consideringSpecifications is shown in Figure 4:2.: Part of the structure of a CATA element (The options

CATE, STCAT and TEXT have been omitted; see the PARAGON Reference Manual for a

fuller explanation.)

Figure 4:2 Part of the structure of a CATA element

CATA Component Catalogue elements hold the physical descriptions of

both piping and structural components (Geomsets, Pointsets etc.),plus any text used to describe the components in schedules, onisometrics etc It is primarily the elements below CATA which will

be accessed via the Specifications

SPWLD Specification World elements hold the detailed Specifications

which enable you to select suitable components from the CATAsfor a given purpose It is the elements below SPWLD which aremanipulated by SPECON and which are, therefore, of mostrelevance in this manual

CCTAB Connection Compatibility (COCO) Tables hold lists of all

compatible types of connection

BLTAB Bolt Tables contain details of all bolts needed to connect flanged

components together in any legal combinations The BLTABmembers will be referenced from the Specifications for appropriatetypes of component

UNITS Dimensional Unit elements define the default units of

measurement for geometric information

GPWLD Group Worlds hold definitions of any groups of elements which

may have been created See the DESIGN Reference Manual for

further details

PRTWLD Part Worlds hold definitions of any part families that may have

been created

TABWLD Table Worlds hold definitions of any Coco, Branch or Reducer

tables that may have been created

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

The 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 4:3.: The structure of a SPWLD element

Figure 4:3 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 Figure 4:4.: Part of a typical Specification for piping components, where each headed ‘question’ columnrepresents a SELEC and each horizontal row represents an SPCOM

SECT Piping Section and Structural Section elements are administrative

STSECT subdivisions of the owning CATA element.

COMP Component elements hold the definitions of piping components These

definitions comprise pointers to GMSET (Geomset) and PTSET(Pointset) elements, plus lists of parameters which specify the exacttype, size and geometry of each component (that is, the component’sAttributes, including its 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 specific

attributes, in a similar way to COMP elements

DTEXT Detailing Text elements hold text which may be used to describe

components in schedules and on isometrics (They also hold the SKEYswhich define the symbols used to represent components in isometric

drawings; see the PDMS ISODRAFT Reference Manual.)

MTEXT Material Text elements hold text which may be used to describe the

materials of construction of the components

It is possible to allocate a default value to most SELEC options, to be used if that particular

attribute 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 as

CATREF and DETAIL

It is also possible to define overall specification pointers and settings which apply to the

whole 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 4:4.: 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 Details of Typical Specifications

Figure 4:4 Part of a typical Specification for piping components

4.3 How Component Selection Works

This 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 leads

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

Catalogue Reference (CATREF), which forms the key to correct component selection

when new pipework is being designed

Each SPCOM also contains pointers to detailing text (DETAIL points to DTEXT), material text (MATXT points to MTEXT), bolting requirements (BLTREF points to BLTAB), component properties (CMPREF points to CMPT in a Properties DB) and part requirements (PRTREF)

If the PRTREF is set in the macro then the CATREF, DETAIL MATXT, CMPREF andBLTREF values do not need to be set as these attributes will be copied from the PARTelement when the spec is created

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 CATREFpointer

(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

Figure 4:5 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 4:4.: Part of a typical Specification for piping components:

to 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