SPECON Reference Manual

8/12/2019 SPECON Reference Manual

1/67

PDMS SPECONReference Manual

Version 11.6SP1

pdms1161/SPECON Reference Manualissue 280605


2/67

PLEASE NOTE:

AVEVA Solutions has a policy of continuing product development: therefore, the

information contained in this document may be subject to change without notice. AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TOTHIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE.

While every effort has been made to verify the accuracy of this document, AVEVASolutions shall not be liable for errors contained herein or direct, indirect, special,incidental or consequential damages in connection with the furnishing, performance oruse of this material.

This manual provides documentation relating to products to which you may not haveaccess or which may not be licensed to you. For further information on which Productsare licensed to you please refer to your licence conditions.

Copyright 1991 through 2005 AVEVA Solutions Limited

All rights reserved. No part of this document may be reproduced, stored in a retrievalsystem or transmitted, in any form or by any means, electronic, mechanical,photocopying, recording or otherwise, without prior written permission of AVEVASolutions.

The software programs described in this document are confidential information andproprietary products of AVEVA Solutions or its licensors.

For details of AVEVA's worl dwide sales and suppo rt offices, see our website athttp://www.aveva.com

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
http://www.aveva.com/engineeringit/world/http://www.aveva.com/engineeringit/world/http://www.aveva.com/engineeringit/world/


3/67

Revision History

Date Version Notes

August 2004 11.6 Section 3.6.5 info added re height units.

June 2005 11.6.SP1 Updates and corrections at this release.

VANTAGE PDMS SPECON Reference Manual Revision-History-iVersion 11.6SP1


4/67


5/67

Contents

1 Introducing SPECON.................................................................................... 1-1

1.1 What SPECON is Used For ........................................................................................1-1 1.2 Who This Manual is Meant For ...................................................................................1-1 1.3 How This Manual is Set Out .......................................................................................1-2 1.4 Conventions Used in the Text.....................................................................................1-2

2 Catalogues and Specifications.................................................................... 2-1

2.1 The Catalogue DB ......................................................................................................2-1 2.2 The Content and Format of a Specification ................................................................2-3 2.3 How Component Selection Works ..............................................................................2-6

3 How To Use SPECON................................................................................... 3-1

3.1 Creating a Specification..............................................................................................3-1 3.2 Accessing an Existing Specification............................................................................3-2 3.3 Entering Tabular Data.................................................................................................3-3

3.3.1 The General Principles .................................................................................3-3 3.3.2 Special Characters in SPEC Data.................................................................3-4 3.3.3 Headings.......................................................................................................3-5 3.3.4 Defaults.........................................................................................................3-6 3.3.5 Selector Answers ..........................................................................................3-7 3.3.6 Subtype Selectors: A Special Case ..............................................................3-7 3.3.7 Including User-defined Attributes in Specifications.......................................3-7 3.3.8 Including Comments in Specifications ..........................................................3-8

3.4 Editing an Existing Specification .................................................................................3-8 3.4.1 Adding a New SPCOM..................................................................................3-8 3.4.2 Deleting or Removing a SPEC or SPCOM ...................................................3-8

3.5 Copying a Specification ............................................................................................3-10 3.6 Outputting a Specification.........................................................................................3-10

3.6.1 Defining the Destination..............................................................................3-10 3.6.2 Outputting Complete Specifications............................................................3-10 3.6.3 Controlling the Output Format.....................................................................3-11 3.6.4 Outputting Parts of Specifications...............................................................3-11 3.6.5 How Bores Are Output ................................................................................3-12

3.7 Using Macros For SPECON Inputs...........................................................................3-12

4 Details of Typical Specifications................................................................. 4-1

4.1 Selectors and Pointers for Piping Components ..........................................................4-1 4.1.1 Applicability ...................................................................................................4-1 4.1.2 Selectors .......................................................................................................4-1 4.1.3 P-Point Zero: A Special Case .......................................................................4-3 4.1.4 Reference Pointers and Settings ..................................................................4-3

4.1.5 Examples From Piping Component Specifications .......................................4-6

VANTAGE PDMS SPECON Reference Manual Contents-iVersion 11.6SP1

i


6/67

Contents

4.2 Selectors and Pointers for Structural Components .................................................... 4-7 4.2.1 Applicability................................................................................................... 4-7

4.2.2 Selectors....................................................................................................... 4-7 4.2.3 Reference Pointers and Settings................................................................ 4-10 4.2.4 Examples From Structural Component Specifications ............................... 4-11

4.3 Selectors and Pointers for Insulation........................................................................ 4-12 4.3.1 Pipework Insulation .................................................................................... 4-12 4.3.2 Structural Insulation.................................................................................... 4-13

A Command Syntax Diagrams........................................................................A-1

A.1 Introduction.................................................................................................................A-1 A.2 Conventions ............................................................................................................... A-1 A.3 Command Arguments.................................................................................................A-3 A.4 The Syntax Diagrams.................................................................................................A-3 A.5 Other PDMS Command Syntax ...................................................................................A-9 B Error Messages ...........................................................................................B-1

C Nominal Pipe Size Tables...........................................................................C-1

contents-ii VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


7/67

1 Introducing SPECON

1.1 What SPECON is Used For

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

These Specifications govern the choice of components from the catalogue. They musthave been set up, together with the rest of the Catalogue DB, before design work takesplace. In principle , therefore, SPECON will be one of the first modules to be used when anew PDMS project is initiated, although in practice it is likely that a company-widelibrary of Catalogues and Specifications will be created independently of any individualdesign project and accessed by subsequent users to ensure overall standardisation andquality control.

SPECON enables you to input new Specifications, to modify existing Specifications, andto output Specifications to your terminal or to a file (to be printed or input again at alater date).

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

1.2 Who This Manual is Meant For

In most companies the responsibility for creating Catalogues and Specifications isrestricted to a team of Standards Engineers within the Production EngineeringDepartment 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 structuraldesigner who needs to use a Specification to select a suitable component and who wishesto understand the principles underlying the selection process.

You are assumed to be familiar with the general principles of using PDMS, althoughsome of the most relevant points are repeated in this manual as a reminder.

You might already have used the Catalogue Constructor module PARAGON to set upother parts of a Catalogue DB, but this manual does not assume that you are familiarwith the details of that module.

VANTAGE PDMS SPECON Reference Manual 1-1Version 11.6SP1


8/67

Introducing SPECON

1.3 How This Manual is Set Out

Chapter 2 describes the structure and use of the Catalogue DB. Thisexplains where the Specifications created by SPECON fit into the overallcomponent selection process.

Chapter 3 explains how to use the various SPECON commands for creating,modifying or interrogating Specifications.

Chapter 4 expands the information given in Chapter 3 by detailing all theoptions which you are likely to use when setting up Specifications for themost relevant classes of design components (Pipework, Structures andInsulation).

Appendix A formalises the full command syntax applicable to each useroption. It is the definitive reference section for clarifying any commandqueries which arise.

Appendix B explains the significance of any error messages which might beoutput during the use of SPECON.

Appendix C contains the tables of pipe nominal bore sizes held withinPDMS.

The manual concludes with an Index.

1.4 Conventions Used in the Text

The following conventions are used throughout this manual to highlight certain featuresof the text:

Common words which have special meanings in PDMS have initial capitalletters where it is thought that this will clarify their meaning; for example,Element, Team etc. In particular, the word Specification has a capital letterwhen it refers to a PDMS SPEC element.

Command words are shown as a combination of uppercase and lowercasecharacters, using a different typeface from that used for normal text; forexample, SPECification. The uppercase part of the word (SPEC in thepreceding example) is the minimum permissible abbreviation. Where acommand word is first introduced, or where its use is defined, it will usuallybe shown in bold type, thus

SPECification

Command arguments are shown in lowercase italic type; for example,argument .

Examples of interactive input and output sequences are shown in a specialtypeface, thus

Example of Input/Output Sequence Typeface

1-2 VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


9/67

Introducing SPECON

Character strings which begin with a slash character / are either names ofelements in the databases or the names of files in the operating system

directories. For example, /ELEMENT or /filename. Character strings enclosed between angled brackets are the names of

individual Syntax Diagrams, as listed in Appendix A. For example,.



10/67


11/67

2 Catalogues and Specifications

This chapter gives an overview of the structure of a typical Catalogue DB, whichcontains information about standard piping and structural components available in aPDMS project, and explains how the Specifications are used within this hierarchy. Formore detailed explanations of the setting up of a Catalogue DB, see the PARAGONReference Manual .

NOTE: Words of four or five uppercase characters in this chapter representPDMS elements (for example, CATA, BLTAB, SPREF). PDMS storesthese as four character names only; the fifth character is given here tomake the abbreviations easier to understand. For example, SPREF(rather than SPRE) is used for Specification Reference

The elements referred to throughout this manual by the names COMP,FITT, DTEXT and MTEXT are stored in the PDMS database hierarchyas SCOM, SFIT, SDTE and SMTE elements, respectively. Thesimplified names, which omit the S prefix, are used here because theyare easier to interpret as you read the manual.

2.1 The Catalogue DB

The information held in a Catalogue DB is split into several functional groups whichtogether completely define every aspect of the components listed within that catalogue.These functional groups, which are the highest level elements in the Catalogue DBbelow WORLD, are shown in Figure 2-1.

WORLD

CATA SPWLD CCTAB BLTAB UNITS GPWLD

Figure 2-1 The top-level structure of a Catalogue DB



12/67

Catalogues and Specifications

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

CATA Component Catalogue elements hold the physical descriptions of bothpiping and structural components (Geomsets, Pointsets etc.), plus any textused to describe the components in schedules, on isometrics etc. It isprimarily the elements below CATA which will be accessed via theSpecifications.

SPWLD Specification World elements hold the detailed Specifications which enableyou to select suitable components from the CATAs for a given purpose. It isthe elements below SPWLD which are manipulated by SPECON and whichare, therefore, of most relevance in this manual.

CCTAB Connection Compatibility (COCO) Tables hold lists of all compatibletypes of connection.

BLTAB Bolt Tables contain details of all bolts needed to connect flangedcomponents together in any legal combinations. The BLTAB members will bereferenced from the Specifications for appropriate types of component.

UNITS Dimensional Unit elements define the default units of measurement forgeometric information.

GPWLD Group Worlds hold definitions of any groups of elements which may havebeen created. See the DESIGN Reference Manual for further details.

That part of the hierarchy below a Catalogue element which is relevant whenconsidering Specifications is shown in Figure 2-2. (The options CATE, STCAT and TEXT

have been omitted; see the PARAGON Reference Manual for a fuller explanation.)

COMP DTEXT MTEXT

CATA

PROF JOIN FITT

SECT STSECT

DTEXT MTEXT

Figure 2-2 Part of the structure of a CATA element



13/67


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

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

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

PROF Profile, Joint and Fitting elements hold the definitions of correspondingJOIN structural components. These definitions comprise pointers to GMSET, FITT

GMSSET, PTSET and PTSSET elements, plus lists of specific attributes, in asimilar way to COMP elements.

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

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

2.2 The Content and Format of a Specification

The component Specifications, which define the availability of components for particulartypes of use, are held in the SPWLD (Specification World) Elements of the CatalogueDB. These elements, which are at the same hierarchic level as the CATA elements, canown the simple hierarchy of elements shown in Figure 2-3.

SPWLD

SPEC

SELEC

SPCOM

SELEC

Specification World

Specification

Selectors(one level for eachspecification decision')

Specification Component

Figure 2-3 The structure of a SPWLD element



14/67


A SPEC is equivalent to an engineering specification for a given class of piping orstructural component. It may contain all components of a given material, for example

carbon steel, or all components for a given class of use, for example all pipingcomponents with a particular pressure rating. Such a SPEC comprises tabulated data ofthe type illustrated in Figure 2-4, where each headed question column represents aSELEC and each horizontal row represents an SPCOM.

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

NOTE : Default values are not allowed for NAME or TYPE, or for referencepointers such as CATREF and DETAIL.

It is also possible to define overall specification pointers and settings which applyto the whole SPEC, not just to individual SPCOMs. These are shown at the top of theSPEC listing, before the Heading, as shown by the entries MATREF, FLUREF, RATINGand LINETYPE in Figure 2-4.

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 Chapter 4.



15/67


HEADING NAME

*/20GA*/20GL*/20RV*/25GA*/25CH

*/25GL

SPECIFICATION /RF300MATREF =0

FLUREF =0RATING 0.000LINETYPE NUL

SELEC QUESTIONS'

SPCOMS

REFERENCE POINTERS

DEFAULTS-

DEFAULT SETTINGS

SPEC NAME

OVERALL SPEC POINTERS

TYPE STYP SHOPPBOR0 CATREF DETAIL MATXT CMPREF BLTREF

- GA- =VALV GA TRUE20.0 /VGAEE /DGA.V.SW /MGA.V /SB20=0VALV GL20.0 TRUE /VGLEE /DGL.V.SW /MGL.V =0 /SB20VALV RV20.0 FALS /VRVEE /DRV.V.FL /MRV.V =0 /SB20VALV GA25.0 TRUE /VGAFF /DGA.V.SW /MGA.V =0 /SB25VALV CH25.0 TRUE /VCHFF /DCH.V.SW /MCH.V =0 /SB25

VALV GL25.0 TRUE /VGLFF /DGL.V.SW /MGL.V =0 /SB25...

OVERALL SPEC SETTINGS

HEADINGNAME TYPE PBOR0 PBOR3 SHOP CATREF DETAIL MATXT CMPREF BLTREFDEFAULTS

- - - = =*/25T TEE 25.0 25.0 TRUE /TEFF /DTEE.SW /MTEE =0 =0*/25TV TEE 25.0 25.0 FALS /TEFFV /DTEE.SW /MTEE =0 =0*/25T1 TEE 25.0 20.0 TRUE /TRFE /DTEE.SW /MTEE =0 =0*/32T TEE 32.0 32.0 TRUE /TEGG /DTEE.SW /MTEE =0 =0*/32TV TEE 32.0 32.0 FALS /TEGGV /DTEE.SW /MTEE =0 =0*/32T1 TEE 32.0 25.0 TRUE /TRGF /DTEE.SW /MTEE =0 =0

... HEADINGNAME TYPE PBOR0 ANGL SHOP CATREF DETAIL MATXT CMPREF

BLTREFDEFAULTS

- - - - =*/20EL ELBO 20.0 90.0 TRUE /ELEE90 /DELB90.SW /MELB =0 =0*/20EF ELBO 20.0 45.0 TRUE /ELEE45 /DELB45.SW /MELB =0 =0*/25EL ELBO 25.0 90.0 TRUE /ELFF90 /DELB90.SW /MELB =0 =0*/25EF ELBO 25.0 45.0 TRUE /ELFF45 /DELB45.SW /MELB =0 =0*/32EL ELBO 32.0 90.0 TRUE /ELGG90 /DELB90.SW /MELB =0 =0*/32EF ELBO 32.0 45.0 TRUE /ELGG45 /DELB45.SW /MELB =0 =0

...HEADINGNAME TYPE PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREF

BLTREFDEFAULTS

- - - SO =*/20FS FLAN 20.0 SW TRUE /FSWEE /DFLAN.SW /MFLAN =0 /SB20*/20FL FLAN 20.0 LAP TRUE /FLAPEE /DFLAN.LAP /MFLAN =0 /SB20*/25FS FLAN 25.0 SW TRUE /FSWFF /DFLAN.SW /MFLAN =0 /SB25*/25FL FLAN 25.0 LAP TRUE /FLAPFF /DFLAN.LAP /MFLAN =0 /SB25*/32FS FLAN 32.0 SW TRUE /FSWGG /DFLAN.SW /MFLAN =0 /SB32

...

Figure 2-4 Part of a typical Specification for piping components



16/67


2.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 whichdetermine its availability for a given purpose. For any given set of design criteria, theroute through the SELECtors follows a question and answer sequence to determinewhich SPCOM is suitable. Each question relates to a specific item in the specificationand each answer leads to the next relevant question in a logical progression. Any given

combination of answers should 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,which meets all the listed specifications, in a CATA element. It is this pointer, known asthe 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 toBLTAB), and component properties (CMPREF points to CMPT in a Properties DB;see the PROPCON Reference Manual ).

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) whichis selected from the required SPEC. You usually define the PipeSpecification (PSPEC) as soon as you create a new pipe, and this is thenapplied to all components which the Pipe 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 theCATREF pointer.



17/67


(The SPCOM also points to a DTEXT via the DETAIL pointer, an MTEXT via theMATXT pointer, a BLTAB element via the BLTREF pointer, and a CMPT element in a

Properties DB via the CMPREF pointer, as appropriate.) This is illustrated below.

PIPECOMPONENT

SPREF

SPECCOMPONENT

DETAIL

MATXT

DTEXT

MTEXT

(SPCOM)(PSPEC)

COMP

CATREF

BLTREF

BLTAB

CATALOGUESPECIFICATIONSDESIGN DATA

CMPREF

CMPT(PROPS DB)

viaSELECs

Figure 2-5 The links between Design Data, Specifications and Catalogue

EXAMPLE:

As an illustration of the principles of the selection process, consider the followingquestion and answer sequence which might apply when choosing a valve from the/RF300 Specification represented in Figure 2-4:

SELEC_1 TYPE? Answer VALV, which leads to the next question ...

SELEC_2 PBOR0? Answer 25.0, which leads to a choice of three STYPs

SELEC_3 STYP? Answer GA, which in this example offers only one choice for SHOP

SELEC_4 SHOP? Answer TRUE

The resulting combination of SELEC answers, namely a 25mm bore Gate Valve with itsSHOP attribute set to TRUE, is represented in the SPEC by one, and only one, SPCOM,namely */25GA. This points to the component in the Catalogue which completelymatches the specification, via the CATREF /VGAFF. The corresponding descriptiveDTEXT is pointed to by the DETAIL /DGA.V.SW, and so on. Note that the CATREF isunique within this SPEC, whereas the same DETAIL applies to other components suchas */20GA.



18/67




19/67

3 How To Use SPECON

SPECON is used for all aspects of Specification creation, modification and interrogation.This chapter explains how to carry out the following tasks:

Create a new SPEC (Section 3.1)

Access an existing SPEC (Section 3.2)

Input data (SELECs and SPCOMs) to a SPEC (Section 3.3)

Edit an existing SPEC (Section 3.4) Copy an existing SPEC as the basis for a new SPEC (Section 3.5)

Output the contents of a SPEC to a selected device (Section 3.6)

Use macro input techniques to simplify SPECON usage (Section 3.7)

3.1 Creating a Specification

To create a new SPEC , use one of the commands

NEW SPECification specnameNEW specname

where specname is the PDMS name which will be used to refer to the completeSpecification.

NOTE : The short form of the command is all that is necessary, since a SPEC isthe only element type which you can create at this level in SPECON(the lower level elements SELEC and SPCOM are created indirectlywhen the tabular data is entered; see Section 3.3).

For example, either of the following commands:

NEW SPEC /RF300NEW /RF300

would create a new SPEC called /RF300.

To associate a descriptive text with the SPEC name, use the syntax

TEXT text

For example, the SPEC created in the preceding example might be given an associatedtext by entering the command

TEXT 300 psi Piping Specification

(Note the delimiting apostrophes enclosing the text string, which must not exceed 50

characters.)



20/67

How To Use SPECON

This text, which is stored in a TEXT element in the hierarchy, will be shown after theSPEC name when the Specification is output; see Section 3.6.

Two system attributes on the PDMS SPECIFICATION element are used when theproduct VANTAGE Project Resource Management (VPRM) is the source of PDMSSpecifications.

When a specification is imported to PDMS the attributes FISSUE and FINPUTBY holdthe VPRM information.

FISSUE holds VPRM issue number FINPUTBY holds information indicating that the source was VPRM and includes

the date of issue

The system attribute FSTATUS also holds the VPRM status of the specification, usuallyworking or approved.

For example:

Finputby |VPRM at 26-NOV-2003 12:04|

Fissue |00|

Fstatus |APPROVED|

3.2 Accessing an Existing Specification

Access a SPEC by using any of the following commands:

OLD SPECification specnameOLD specnameSPECification specnamespecname

where specname is the name of an existing SPEC.

For example, enter any of the following commands:

OLD SPEC /RF300

OLD /RF300SPEC /RF300/RF300

to access the SPEC created in Section 3.1. Clearly, the simplest method is to enter justthe name of the SPEC required.

You may interrogate the SPWLD hierarchy by using the command, or change to adifferent SPEC element within it by using any of the standard DB navigationalcommands such as FIRST , NEXT, etc., in the usual way.



21/67

How To Use SPECON

3.3 Entering Tabular Data

3.3.1 The General Principles

You must have created or accessed a SPEC (as described in Sections 3.1 and 3.2,respectively) before you can enter tabular data.

Each Specification may contain any number of separate tables. For example, that part ofthe SPEC named /RF300 listed in Figure 2-4 contains four tables (one for each of thecomponent types VALV, TEE, ELBO and FLAN), although the complete SPEC wouldprobably contain many more.



22/67

How To Use SPECON

A table comprises three distinct types of data:

A Heading (or Question Line)

Defaults

Answer Lines

The heading must be at the top of the table; the defaults, if specified, must immediatelyfollow the heading; and the answer lines (one for each SPCOM) form the remainder.This sequence is illustrated in Figure 2-4.

3.3.2 Special Characters in SPEC Data

In addition to conventional alphanumeric PDMS names and attribute values, thefollowing special characters may be used in the SPEC data entries:

* The star or asterisk character is used throughout PDMS as an abbreviation whichyou can set to the name of an owning element when naming a member element ina DB hierarchy. In most modules you must define this character by using thecommand, but it is set automatically by SPECON so that it always refers to thename of the current SPEC. For example, in the SPEC named /RF300 shown inFigure 2-4, the component listed as */20GA has the full PDMS name /RF300/20GA.

+ The plus character means ditto ; it enables you to repeat the setting above it in thetable with the minimum of keystrokes.

- The minus or dash character, which may be used only in the default line of a table,means not applicable or unspecified . If a default line is present, this charactermust appear under TYPE and NAME, and under any SELEC questions for whichdefault answers are not set. It must not appear under CATREF, DETAIL, MATXTetc., for which defaults are never allowed.

= The equals character, when used in the default line of a table, means that theanswer will default to the first selector in list order after all other questions havebeen answered.

As an example, consider the following part of a table (which incorporates all four of thecharacters * - + and = ):

HEADINGTYPE NAME PBOR0 STYP CATREF DETAIL MATXT CMPREFBLTREFDEFAULTS

- - - =FLAN */FG 20.0 S /FSAAPAPP /20FL /ASA-20F =0/SBOL/20FFLAN */FX + P + + /ASA-20FX =0 +...

This includes two SPCOMs which differ only in the Selector STYP (Subtype) and which

have pointers, for the purpose of this example, to different Material Texts. When this



23/67

How To Use SPECON

SPEC is used to select a component without specifying the required STYP, the = defaultoption will select the first SPCOM (*/FG) in the list order, which points to the MTEXT

identified as /ASA-20F.NOTE: The equals signs within the body of the table, in the form =0, simply show that

those pointers have not been set. They have no relevance to the equals sign in adefault line.

Since PDMS does not allow any SPREF to exist more than once, items in a SPEC whichare identical but which need to be distinguished from each other may be allocatedsuffixes . ISODRAFT can be made to ignore such a suffix by recognising the delimitingcharacter which separates the suffix from the rest of the SPREF. For example, if thedelimiting character is defined as a colon (:), which is the default, ISODRAFT willidentify two components with the SPREFs /TEE.FS:AA and /TEE.FS:AB as having the

same item code /TEE.FS. See the ISODRAFT Reference Manual for further details,including the way in which you may specify which character is to be recognised as thedelimiter.

3.3.3 Headings

The heading line, which defines the column headings for the rest of the table, containsfour distinct sorts of information:

TYPE is the generic type (GTYPE) of the component represented by anSPCOM.

NAME is the unique identifier for each SPCOM. Selector Questions define the SELEC choices which will be used to choose

an appropriate SPCOM for a given design purpose (e.g. STYPE, ANGLEetc.).

Reference Pointers link each SPCOM to the corresponding definitions in theother parts of the Catalogue (e.g. CATREF points to a COMP, DETAILpoints to a DTEXT, and so on).

(For full details of the available options for Selector Questions and Reference Pointers,see Section 4.1 for piping components, Section 4.2 for structural components, or Section4.3 for insulation.)

To define a heading , use the command syntax

HeadingTYpe NAme questions pointers

noting that the command is entered on two lines (i.e. you must press RETURN after thecommand HEADING, as well as after the last entry in the second heading line).

IMPORTANT NOTE :When new data is entered into a Specification, the input sequence isTYPE NAME ... etc.; when an existing Specification is modified (seeSection 3.4), or when its contents are output (see Section 3.6), the

corresponding sequence is NAME TYPE ... etc.



24/67

How To Use SPECON

Examples of possible commands for defining headings are as follows:

For generic type TUBE -

HEADINGTYPE NAME PBOR0 SCHE SHOP CATREF DETAIL MATXT CMPREF BLTREF

For generic type ELBO -

HEADINGTYPE NAME PBOR0 STYP ANGL SHOP CATREF DETAIL MATXT CMPREFBLTREF

For generic type REDU -

HEADINGTYPE NAME PBOR0 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREFBLTREF

For generic type BEAM -

HEADINGTYPE NAME STYP GRAD DEPT WIDT WEIG INER CATREF

and so on. See Chapter 4 for explanations of the SELEC questions used in theseheadings.

The maximum number of entries in a heading line (that is, the maximum number ofcolumns in the table) is 20.

NOTE : The number of columns in an existing Specification cannot be changed, so it isimportant that you choose the headings carefully when you create a newSpecification.

3.3.4 Defaults

To define the default settings for the SELEC answers, use the command syntax

Defaultsdefault_settings

which, as with the HEADING command, occupies two input lines.

Each SELEC question column must be set to either a definite answer ( value , word , etc.)or to a - or = character (as defined in Section 3.3.2). The TYPE and NAME columnsmust have - (null) defaults and the Reference Pointer columns must have no defaultentries at all.

For example, heading and default lines for a table of VALV Specifications might beentered as follows:

HEADINGTYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXTCMPREF BLTREFDEFAULTS

- - - GATE =



25/67

How To Use SPECON

Any VALV selected without specifying the STYPE (for example, by using the commandNEW VALV SEL in a design module) will have the word GATE assigned as the answer tothe SELEC question for its STYPE.

3.3.5 Selector Answers

To complete the main area of the table, enter the TYPE and NAME, followed by anappropriate answer ( value , word etc.) under each column heading, for each SPCOM linein turn. The spacing between the answers is not critical, although interpretation of theSPEC table may be easier if you align the headings and answers in vertical columns, asillustrated in Figure 2-4. Note, however, that the tabulation used when data in input toa SPEC is not retained when that SPEC is subsequently output.

Remember that you can use the * and + characters, defined in Section 3.3.2, to saverepetitive typing when entering the SPEC data from a keyboard.

NOTE : You must take care not to use any of the dimensional units (MM, M, IN, FT, FEetc.) in answers which are expected to be words. This applies particularly to theSTYPE Selector (see Section 3.3.6). If, for example, a Specification included theadjacent headings PBOR0 STYPE and you entered the answers 25 for the boreand FT for the STYPE, SPECON would interpret this as a bore of 25 feet andwould try to assign the next answer or reference pointer to the STYPE.

3.3.6 Subtype Selectors: A Special Case

Subtype (STYP or equivalent) selector answers can be tabulated in either of twoformats: as a PDMS word (up to four letters), or as a text string (of any length)enclosed between apostrophes. If you use the latter format, you must precede the textstring with the word TEXT to avoid possible confusion with user-defined dimensioningunits.

For example, the STYP for a gate valve (generic type VALV) could be listed either asGATE or as the equivalent form TEXT GATE . If these are to be truly equivalent, youmust use uppercase characters for GATE in the text answer. Alternatively, the textversion could be extended to give a more explicit description; for example, TEXT HighPressure Gate .

3.3.7 Including User-defined Attributes in Specifications

To include the settings of user-defined attributes in a Specification, for subsequent useby ISODRAFT, use the command syntax

EXTRA :uda_name attribute_setting

For example:

EXTRA :colour green (where :colour is a uda of type text) EXTRA :diagonal 226.87 (where :diagonal is a uda of type real)



26/67

How To Use SPECON

User-defined attribute settings included in this way (one per line) will be correctlyoutput and re-input when you list the SPEC using macros. Note: User-defined

attributes to be used in this way must have been defined in LEXICON with SPCOMs asvalid components.

3.3.8 Including Comments in Specifications

To include a comment in a Specification, typically to clarify details of its content forfuture users, use the command syntax

COMMENT text

All text between apostrophes following the COMMENT command will be ignored when

the SPEC is interpreted, but will be correctly output and re-input when you list theSPEC using macros.

3.4 Editing an Existing Specification

3.4.1 Adding a New SPCOM

To add one or more new SPCOM lines to an existing SPEC, use the same syntax as thatdescribed in Section 3.3 for setting up a new SPEC; that is, enter the command lines

HeadingTYpe NAme questions pointersDefaults (optional)default_settings (optional)selector_answers pointer_settings

The heading line TYPE NAME questions pointers must be the same as thecorresponding line in the existing SPEC. SPCOMs entered in this way will be mergedinto the table for the relevant component type when the SPEC is output.

3.4.2 Deleting or Removing a SPEC or SPCOMThe terminology used here is significant:

If a SPEC or SPCOM is deleted , all aspects of it are eliminated from the CatalogueDB. If an existing design includes a component with an SPREF which points to thedeleted data, any future access to the Design DB, say to produce a drawing, willresult in an error since no matching SPCOM will be found.

If a SPEC or SPCOM is removed, the data held within it is transferred to a specialarchive Specification named /*LIMBOSPEC . The data still exists, so that referencesto it are still valid, but it no longer forms part of the original named SPEC. This

facility is useful:



27/67

How To Use SPECON

a. when a component is withdrawn from use for new designs but its continued use inexisting designs is permitted

b. when use of a component is to be suspended temporarily while modifications aremade.

NOTE: If you are using more than one Catalogue DB, there is one archive Specificationfor each DB. This avoids inadvertent transfer of data between DBs due toremoval and subsequent restoration of SPECs or SPCOMs. Such multiplearchive Specifications are named /*LIMBOSPEC, /*LIMBOSPEC_1,/*LIMBOSPEC_2 etc. Only the single form /*LIMBOSPEC will be referred to inthe remainder of this manual.

To delete individual SPCOM lines from a SPEC, use the command syntax

DELETE spcom1 spcom2 ...

where spcom1 , spcom2 etc. identify the relevant SPCOMs. For example,

/RF300DELETE */20GA */25GA

will access the SPEC /RF300 and delete the SPCOMs /RF300/20GA and /RF300/25GA.

To delete a complete Specification , use the command syntax

DELETE SPECification specname

where specname is the name of the SPEC. For example,

/RF300

DELETE SPEC /RF300will access and then delete the entire SPEC named /RF300.

To delete all SPCOMs from a SPEC without deleting the SPEC itself, enter thecommand

DELETE ALL

NOTE: The DELETE command should be used with care. No checks are madeagainst any design data before the SPCOMs are deleted and anyreferences to such SPCOMs in a Design DB will become invalid. If indoubt, use the REMOVE command.

To remove individual SPCOM lines from a SPEC, use the command syntaxREMove spcom1 spcom2 ...

where spcom1 , spcom2 etc. identify the relevant SPCOMs.

The effect of this command is to remove all answers from the named SPCOM lines,except for the pointers CATREF and DETAIL, and to transfer those SPCOMs to thearchive Specification /*LIMBOSPEC. If a Specification Reference (SPREF) in a DesignDB points to an SPCOM which cannot be found in the currently named SPEC, it willautomatically look for that SPCOM in /*LIMBOSPEC.

To remove the entire contents of a SPEC, enter the command

REMove ALL



28/67

How To Use SPECON

To reinstate a removed SPCOM , ensure that you are pointing to the correctcurrent SPEC and then use the syntax for modifying an SPCOM, as defined in Section

3.4.2, but incorporate the name of the SPCOM to be reinstated. The SPCOM willautomatically be moved back from /*LIMBOSPEC into the original SPEC.

3.5 Copying a Specification

It is sometimes necessary to have two SPECs which are very similar, perhaps differingonly in the CATREF and DETAIL pointers of their member SPCOMs. To enable you tocreate these easily, SPECON allows you to make a copy of an existing SPEC which youcan then rename and edit as required. To do so, use the command syntax

COPY specname REName name1 name2

where specname identifies the complete SPEC which is to be copied and name1 andname2 define the old and new name parts, respectively, for the individual SPCOM linesthroughout the SPEC. In most cases name1 will be the same as specname .

For example, to create a new Specification /SPEC2 derived from an existing and similarSpecification /SPEC1, enter the commands

NEW SPEC /SPEC2COPY /SPEC1 RENAME /SPEC1 /SPEC2

/SPEC2 will contain exactly the same headings, default settings and SPCOM lines as/SPEC1 except that all SPCOMs which were named /SPEC1/... in the latter will have

been renamed /SPEC2/... in the former. You can now change any individual answers (attribute settings or pointers) in /SPEC2by using the editing commands described in Section 3.4.

3.6 Outputting a Specification

3.6.1 Defining the Destination

You can output the content of a SPEC to your terminal or to a file (perhaps forsubsequent printing). The device to which SPECON is to send the output may be definedby using the standard device-selection commands described in the PDMS MonitorReference Manual . The default is TERMINAL.

3.6.2 Outputting Complete Specifications

To output one or more complete SPECs, use the command syntax

OUTput specname1 specname2 ...



29/67

How To Use SPECON

For example, to send the content of Specification /RF300 to a file named /RF300.SPEC inyour current OS directory, enter the commands

FILE /RF300.SPECOUTPUT /RF300

The data will be output to the selected device in a similar tabular format to that inwhich it was entered into the SPEC, although the precise tabulation settings will havebeen modified to suit the linewidth of the destination device (but see also Section 3.6.3).

SPEC data output in this way has the same NAME TYPE ... sequence as that whichapplies when existing data is being accessed for editing; not the TYPE NAME ...sequence in which it was entered. To output a SPEC with the heading sequence TYPENAME ... (to be used, for example, as input at a later time; see Section 3.7), use theextended command syntax

OUTput NEW specname1 specname2

(The default version of the OUTPUT command is equivalent to OUTPUT OLD , but thereis no advantage in using the longer form.)

3.6.3 Controlling the Output Format

By default, the tabulated layout of data derived the output macro is the same as that inthe original SPEC. You can compact the output macro file by replacing multiple spacesby a single space. This saves disk space, but can make the tables more difficult to read.To do so, use the command

COMPact

To restore the tabulated format with aligned columns, use the command

ALIGned

3.6.4 Outputting Parts of Specifications

To generate output which is restricted to one or more specified types of component,include the generic types of the required components by using one of the syntax formats

OUTput gtype1 gtype2 ... specname1 specname2 ...OUTput OLD gtype1 gtype2 ... specname1 specname2 ...OUTput NEW gtype1 gtype2 ... specname1 specname2 ...

where gtype1 , gtype2 etc. are the component types to be included and specname1 ,specname2 etc. are the Specifications from which the data is to be extracted.

For example, to create a file containing just the valve and flange data from theSpecification /RF300, in a format suitable for use as input to a different Specification,you might use the commands

FILE /SPECDATAOUTPUT NEW VALV FLAN /RF300



30/67

How To Use SPECON

3.6.5 How Bores Are Output

Although all pipe bores are stored in the PDMS databases in mm, they may be inputand output in either metric or imperial units. The program converts from one set ofunits to the other by applying the factor 25.4 mm/inch.

PDMS holds tables of standard nominal bore pipe sizes and, unless specified otherwise,compares each actual bore against the values in the appropriate (metric or imperial)table. If the actual bore falls within a predefined tolerance of one of the nominal bores, itis assumed that the standard sized pipe is suitable and so that nominal bore is output.

You may specify whether component bores within the Specification data are to be outputas actual or nominal sizes by using the command syntax

BOREs ACTualBOREs NOMinal

The default is BORES NOMINAL .

Note: RADI and HEIG questions use the current Distance unit.

Appendix C contains the tables used by PDMS to define metric and imperial pipe sizes.

3.7 Using Macros For SPECON Inputs

While it is possible to create or modify SPECs and SPCOMs interactively, it is usually

more efficient to use macros for this purpose.The tabular format of the SPECON input is easily achieved using any normal text editorand the data file thus created can be checked for errors before it is read into theCatalogue DB. If any syntax errors are found when the macro file is run in SPECON,the file may be edited to correct the mistakes and rerun with the minimum amount ofeffort.

The format of the macro input file is exactly the same as that produced by the OUTPUTNEW command described in Section 3.6.2; that is, TYPE must precede NAME in theheading and SPCOM lines. This means that Specifications which have been sent to a filemay be edited independently of PDMS, using any available text editor in your computer

system, and then reloaded via SPECON. This is often the most effective way of carryingout major revisions of existing SPECs. Any part of an SPCOM line may be changed inthis way other than the NAME or TYPE; if these were changed SPECON would not beable to locate the SPCOM to overwrite it.

Remember, when creating SPECON input macros from the keyboard, that the symbols *(automatically set to the Specification Name) and + (equivalent to ditto) can be used tosave repetitive typing (see Section 3.3.2).

To update an existing macro to use text strings instead of PDMS words for STYPEselector answers (see Section 3.3.6), edit the macro so that each four-character wordrepresenting an STYP (or equivalent) is replaced by the keyword TEXT followed by thereplacement text enclosed between apostrophes. For example, you would replace GATE



31/67


32/67

How To Use SPECON



33/67

4 Details of Typical Specifications

This chapter explains, with examples, typical data entries which might be used inSpecifications for the main types of design components (piping components, structuralcomponents and insulation).

4.1 Selectors and Pointers for Piping Components

4.1.1 Applicability

The headings in this section may apply to components from the following list ofGTYPEs:

ATTAchmentNOZZle

Bend OLEtsBolt PCLampCAP PCOmp

CLOsure REDucerCOUpling RODCROSs SCLampDUCting SHUElbow TEEFBLind TUBeFILter TRAPFLAnge UNIonFLG VALveFTUbe VENtGASket VFWayHELement VTWayINSTrument WELD

LJSE

(For Insulation, see Section 4.3.1 )

4.1.2 Selectors

There are very few constraints on the SELEC questions, and the order in which you listthem, when defining SPECs for piping components. The following headings should meetmost of your requirements:



34/67


35/67


36/67

Details of Typical Specifications

is used to describe the corresponding component in schedules, on isometric drawings,etc. (see the PARAGON Reference Manual ).

MATXT - Material Text:Points to an MTEXT element in the Catalogue DB. This holds the text which is usedto describe the materials of construction of the corresponding component inschedules, on isometric drawings, etc. (see the PARAGON and ISODRAFT ReferenceManuals ).

BLTREF - Bolt Reference:Points to a BLTAB element in the Catalogue DB. This contains details of the boltsneeded to connect the corresponding component into a pipeline (see the ISODRAFTReference Manual ). This heading is, of course, applicable only to components which

require bolts (flanges etc.).CMPREF - Component Reference:

Points to a CMPT element in the Properties DB (see the PROPCON ReferenceManual ).

Overall Specification Pointers

These pointers, which are attributes of SPEC elements, are set for an entireSpecification. Their settings are shown at the beginning of the Specification,immediately after the name, and always appear, even if they remain unset.

MATREF - Material Reference:Points to a SOLID element in the Properties DB. This holds information about theproperties of the materials of construction of the piping components (see the

PROPCON Reference Manual ).

FLUREF - Fluid Reference:Points to a FLUID element in the Properties DB. This holds information about theproperties of the liquids or gases for use with which the piping components aresuitable (see the PROPCON Reference Manual ).

Overall Specification Settings

These are not pointers to other elements but are local to the Specification itself. Theirsettings are shown at the beginning of the Specification, immediately after the MATREFand FLUREF pointers, and always appear, having default settings if you have notspecified otherwise. These attribute settings are used only by ISODRAFT and arerelevant only when fixed length piping is being used. You are referred to the sectionentitled Fixed Length Piping in the ISODRAFT Reference Manual for fuller details.

RATING - Pipeline Pressure Rating:May be set to the maximum pressure at which the components covered by theSpecification are intended for service. ISODRAFT can then use this setting to



37/67


determine those points in a composite pipeline at which the pressure rating changes.The default setting is zero.

LINETYPE - Fixed Length Piping Line Type:May be set to either of the identifiers

FP Fixed PipeFX Fixed Length

ISODRAFT uses this setting to decide whether or not to append the length of acomponent to its item code in a material list. The length is appended if linetype is set toFP, but is assumed to be incorporated into the standard code if linetype is set to FX. Thedefault setting is NUL (i.e. variable length piping between components is assumed).



38/67


4.1.5 Examples From Piping Component Specifications

To keep the examples brief, very few lines (SPCOMs) are shown for each GTYPE.NEW SPECIFICATION /RF300MATREF =0FLUREF =0RATING 0.000LINETYPE NUL

HEADINGTYPE NAME PBOR0 SHOP CATREF DETAIL MATXT CMPREF BLTREF

- - - =TUBE */20TU 20.0 TRUE /TUEE /DTUB1 /MTUB =0 =0TUBE */25TU 25.0 TRUE /TUFF /DTUB1 /MTUB =0 =0...

HEADINGTYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF

- - - PE =FTUB */20FT 20.0 PE TRUE /FTEE /DFTUB /MFTUB =0 =0FTUB */25FT 25.0 PE TRUE /FTFF /DFTUB /MFTUB =0 =0...

HEADINGTYPE NAME PBOR0 RADI ANGL SHOP CATREF DETAIL MATXT CMPREFBLTREF

- - - - = =

BEND */20VB1 20.0 100.0 90.0 TRUE /VBEE /DVBEND1 /MVBEND =0 =0BEND */20VB3 20.0 100.0 180.0 TRUE /BEEE /DBEND1 /MVBEND =0 =0BEND */20VB2 20.0 60.0 90.0 TRUE /VBEE /DVBEND2 /MVBEND =0 =0BEND */20VB4 20.0 60.0 180.0 TRUE /BEEE /DBEND2 /MVBEND =0 =0BEND */25VB1 25.0 125.0 90.0 TRUE /VBFF /DVBEND1 /MVBEND =0 =0...

HEADINGTYPE NAME PBOR0 CATREF DETAIL MATXT CMPREF BLTREFGASK */20G 20.0 /GAEE /DGASK /MGASK =0 =0GASK */25G 25.0 /GAFF /DGASK /MGASK =0 =0...

HEADINGTYPE NAME PBOR1 PBOR2 STYPE SHOP CATREF DETAIL MATXT CMPREFBLTREF

- - - - CONC =REDU */25RC1 25.0 20.0 CONC TRUE /RCFE /DRED.C /MRED =0 =0REDU */25RE1 25.0 20.0 ECC TRUE /REFE /DRED.E /MRED =0 =0REDU */32RC1 32.0 25.0 CONC TRUE /RCGF /DRED.C /MRED =0 =0REDU */32RE1 32.0 25.0 ECC TRUE /REGF /DRED.E /MRED =0 =0...

and so on.

(See Figure 2-4 for some other examples.)



39/67


4.2 Selectors and Pointers for Structural Components

4.2.1 Applicability

The headings within this section may apply to components from the following list ofGTYPEs:

BASEBEAMBRACeCOLUmn

FITTingGANTryGIRDerJOINtJOIStKNEEPILEPROFilePURLinRIDGe

RODSCTNSDRAilSPLIceSTANchionSTIFfenerSTRUtTIE

4.2.2 Selectors

The following SELEC questions are those which you are likely to use when definingSPECs for structural components:

SType Defines the Specific Type of the component; particularly applicable to the generalgeneric types PROF, JOIN and FITT. Examples of STYPE answers which might beapplied to structural components to cover European, American and Britishstandards include:



40/67


STYPE Meaning

C Channel section or American standard Cshapes (tapered flanges)CHS Circular hollow sectionCRSJ Castellated rolled steel joistsCUB Castellated universal beamsCUC Castellated universal columnsCZB Castellated ZbeamsEAI Imperial equal anglesEAM Metric equal anglesHD European columns (wide flanges)HE European beams (wide flanges)HL/HX European beams (very wide flanges)HP Bearing piles (wide flanges)IPE European beams (parallel faced flanges)IPN European standard beams (tapered flanges)LST Long stalk teebarsM/W American Ishapes (wide flanges)RHS Rectangular hollow sectionRSJ Rolled steel joistsS American standard Ishapes (tapered flanges)T Tee barsTUB Tees cut from universal beamsTUC Tees cut from universal columnsU European small channelsUB Universal beamsUBP Universal bearing pilesUC Universal columnsUEAI Imperial unequal anglesUEAM Metric unequal anglesUPN European standard channelsPLAT Plate girders



41/67


DEPth The depth (height) of a structural section; e.g. 100 mm.

WIDth The width of a structural section; e.g. 100 mm.

WEIGht The weight per unit length; e.g. 100 kg/m.

DIMEnsion integer : Any dimension. The qualifying integer is optional; suggested conventions are:

DIME1 Depth or long legDIME2 Width or short leg

CTYPE integer A connection type. The qualifying integer is optional; suggested conventions are:

CTYPE1 Start connectionCTYPE2 End connectionCTYPE3 Attached connectionCTYPE4 Owning connection

with the possible answers RIVET, BOLT, WELD, GLUE etc.

CTYStart

Start connection (equivalent to CTYPE1 ).CTYEnd

End connection (equivalent to CTYPE2 ).

CTYAttached Attached connection (equivalent to CTYPE3 ).

CTYOwning Owning connection (equivalent to CTYPE4 ).

INERtia integer

Moment of inertia about a specified axis; e.g. 280 cm $. (It is usually convenient touse cm rather than mm here to avoid having to list large values.) The qualifyinginteger is optional; suggested conventions are:



42/67


INER1 Inertia about x-xINER2 Inertia about y-y

INER3 Inertia about u-uINER4 Inertia about v-v

THICkness integer Plate thickness within a section; e.g. 10 mm. The qualifying integer is optional;suggested conventions are:

THIC1 Web thicknessTHIC2 Flange thickness

FIXty Joint fixity; e.g. FIXED, PINNED, PLASTIC, HINGED, RIGID etc.

GRADe Material grade for fire-resistant insulation; e.g. 43. (See Section 4.3.2. )

FIREsistance Degree of fire resistance for insulation; e.g. 2 hr. (See Section 4.3.2. )

ITHIckness Insulation thickness; e.g. 50 mm. (See Section 4.3.2.)

AREA Area of a section; e.g. 100 cm .

As for piping component specifications, you may also use any word, with or without anumeric qualifier, to define your own questions. See Section 4.1.2.

4.2.3 Reference Pointers and Settings

The pointers and attribute settings which you may specify for structural componentspecifications are the same as those defined in Section 4.1.4 for piping components,although the relative importance of the references will differ (for example, FLUREF,RATING and LINETYPE are unlikely to be relevant). As for piping components, only

the CATREF pointer is obligatory.



43/67


4.2.4 Examples From Structural Component Specifications

The following excerpt from a Specification for structural steelwork componentsillustrates some of the features defined in the preceding sections:

NOTE: The Reference Pointers DETAIL, MATXT, CMPREF and BLTREF havebeen omitted to save space. Although these are available to giveconsistency with Piping Specifications, you are unlikely to use these forstructural components (BLTREF, in particular, would have no meaningfor a structural component). No defaults have been set in this example.

NEW SPECIFICATION /BS4.PT1MATREF =0FLUREF =0

RATING 0.000LINETYPE NULTEXT Middlesbrough Mills

HEADINGTYPE NAME STYP GRADE WIDTH DEPTH WEIGHT INERTIA CATREFBEAM */UB1 UB 43 465 153 82 32435 /457X152X82UB+ */UB2 + 50 465 153 82 32435 /457X152X82UB+ */UB3 + 43 310 125 48 9504 /305X127X48UB...

HEADINGTYPE NAME STYP GRADE DEPTH WIDTH WEIGHT INERTIA CATREFBRAC */UEA1 UEAM 43 200 150 47 2376 /200X150X18L+ */UEA2 + 50 200 150 47 2376 /200X150X18L+ */UEA3 + 43 125 75 18 354 /125X75X12L...

HEADINGTYPE NAME STYP WIDTH DEPTH WEIGHT INER1 INER2 CATREFPROF */BS.C1 C 102.0 432.0 65.5 21399.0 628.6 /432X102X65KG.C+ */BS.C2 + 102.0 381.0 55.1 14894.0 579.8 /381X102X55KG.C...PROF */BS.CRSJ1 CRSJ 102.0 305.0 25.3 5372.0 162.5

/305X102X25KG.CRSJ+ */BS.CRSJ2 + 102.0 267.0 21.5 3562.0 139.1/267X102X21KG.CRSJ

HEADINGTYPE NAME STYP DEPT WIDT WEIG INER1 INER2 CATREFPROF */BS.CUB1 CUB 1371.0 419.0 388.0 1661103.0 42443.0/1371X419X388KG.CUB+ */BS.CUB2 CUB 1371.0 419.0 343.0 1449837.0 36223.0/1371X419X343KG.CUB...

and so on.



44/67


45/67


4.3.2 Structural Insulation

Insulation for Sections, Joints and Fittings may be selected from an InsulationSpecification by using the selection criteria Grade, Fire Resistance and InsulationThickness derived from the current component. An extract from a typical InsulationSpecification for use in structural design might be as follows:

NEW SPECIFICATION /BS4.PT1.INSULHEADINGTYPE NAME GRADE FIRE ITHI CATREFDEFAULTS- - 43 - -INSU */IN1 43 1,2 20 /IN25

+ */IN2 40 1,2 40 /IN50+ */IN3 43 2,4 20 /IN50+ */IN4 50 2,4 40 /IN75+ */IN5 43 4,10 20 /IN75+ */IN6 50 4,10 40 /IN100



46/67




47/67

A Command Syntax Diagrams

A.1 Introduction

This appendix contains the legal command and interrogation syntax diagrams relevantto the PDMS SPECON module. These diagrams formalise the precise commandsequences which may be used and are intended to supplement the explanations given inthe appropriate sections of this manual.

A.2 Conventions

The following conventions apply to the syntax diagrams in this appendix:

All diagrams have abbreviated names . Such names are composed of lowercaseletters enclosed in angled brackets, e.g. . These short names, which areused for crossreferencing purposes in the text and within other syntaxdiagrams, are supplemented 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 betyped in lowercase letters; commands may be entered in any combination ofuppercase and lowercase letters.)

For example, the command

REMove

may be input in any of the following forms:REMREMOREMOVREMOVE

Commands shown wholly in uppercase letters cannot be abbreviated.

Names written in lowercase italics are command arguments (see Section A.3).

Syntax diagrams are generally read from top left to bottom right.

VANTAGE PDMS SPECON Reference Manual A-1Version 11.6SP1


48/67


49/67

Command Syntax Diagrams

A.3 Command Arguments

These are inputs which are necessary to qualify command words. They are distinguishedby appearing in italics.

Name Definition Examplename PDMS element name /ABCDErefno PDMS reference number =23/1403integer a positive integer 0, 3value signed number 3.142, -23.66, -34word alphabetic word NULL, VALV (4 chars. max.)text alphanumeric string Enclose Between Apostrophessign plus or minus character + (for ditto); - (in default lines)equals equals character = (in default lines)comma comma character 20, 40 (for range of values)nl new line Press the RETURN key

Table A-1 Examples of basic command arguments

A.4 The Syntax Diagrams

The diagrams are listed approximately in the order in which they are described in thismanual.



50/67


A.4.1

.-------------------------------*--- NEW ---+--- SPECification ---. || | | || ---------------------+--- name ----------------|| ||---OLD ---+--- SPECification ---. || | | || ---------------------+ || | ||--- SPECification --------------+--- -----------------|| ||--- ---> || ||--- REMove ---. .----


51/67


A.4.2

.----------- ---*--- -----|| ||--- ------|--->



52/67


A.4.3 .---------------------------.

/ |>--- Heading - nl --+-- TYpe - NAme --. .--*--- PBore --- integer -------|| | | | |-- NAme - TYpe --+-- |--- PConn --- integer -------|

| ||--- SType -------------------|| ||--- ANGle -------------------|| ||--- RADius ------------------|| ||--- TEMperature -------------|| ||--- PRessure ----------------|| ||--- RATing ------------------|| ||--- SHOP --------------------|| ||--- CATref ------------------|| ||--- DETail ------------------|| ||--- MATXt -------------------|| ||--- CMPref ------------------|| ||--- BLTref ------------------|| ||--- DEPth -------------------|| |

|--- WIDth -------------------|| ||--- CTYStart ----------------|| ||--- CTYEnd ------------------|| ||--- CTYAttached -------------|| ||--- CTYOwning ---------------|| ||--- FIXty -------------------|| ||--- GRADe -------------------|| ||--- FIREsistance ------------|| |

|--- ITHIckness --------------|| ||--- AREA --------------------|| ||--- WEIGht ------------------|| ||--- DIMEnsion ---. || | ||--- CTYPE -------| || | ||--- INERtia -----| || | ||--- THICkness ---| || | ||--- word --------+-- value --|| | |----> -----------

A-6 VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


53/67


A.4.4

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

>--- Defaults --- nl --- s g --- s gn ---*--- ---|| ||--- sign -----|| ||--- word -----|| ||--- equals ---|--->

A.4.5 >--+--- noun ---.

| ||--- s gn ----+--- name -----.| |--- ---+--- noun -----|

| ||--- sign -----| .-----------------------------------------.| |/ |--------------*--- word ----------------------------------|

| ||--- TEXT --- text -------------------------|

| ||--- EXTRA --- : uda_name --- uda_setting ---|| ||--- COMMENT --- text ----------------------|| ||--- ---+--- comma --- ----. || | | || -------------------------+--|| ||--- sign ----------------------------------|| ||--- ----------------------------------|--->



54/67


A.4.6

>---+--- name ---.| |--- refno ---+--->

A.4.7

>--- COPY --- ---+--- REName --- name --- name ---.| |--------------------------------+--->

A.4.8 >---+--- value ----------.

| |--- ---+--- EXponential --- value ---.

| |-----------------------------+--- MM -------.

| ||--- Metres ---|| ||--- INches ---|| ||--- FT -------|| ||--- FEet -----|| ||--- text -----|| |--------------+--->



55/67


A.5 Other PDMS Command Syntax

Common commands which may be legally used from within SPECON, but which are notdirectly related to this module, include the following:

Function(s) Syntax Diagram Name

Actions setting (i.e. ACTIONS command) Element identification and database navigation and its subsidiary syntaxDevice control Date and time (real & elapsed) and

Querying specific options:

Actions Heading banner Buffers Input/output device Input/output counters Project details

Defining the current (default) units of measurement

Attribute type references Module selection Giving system commands

Defining logical expressions etc.



56/67




57/67

B Error Messages

The following is a list of those error messages specific to SPECON. All such errormessages have a message number beginning with 17. Any other messages that may beoutput are not described here as they are not specific to SPECON.

NOTE: Since some other modules access the Specifications directly during theirnormal functioning (for example, to select insulation data) you mayreceive SPECON error messages while working in those modules.

(17:2) Cannot access IDThe element specified does not appear to exist in this DB. Check that youhave entered the identifier correctly.

(17:3) Cannot access SPECIFICATIONCheck that you have entered the identifier for the SPEC correctly.

(17:4) Cannot create SPCOM or SELEC You can only add a new SPCOM line or SELEC question after you havecreated a new SPEC or have accessed an existing SPEC (see Sections 3.1-3.3).

(17:5) Cannot create SPECIFICATION You can only create a new SPEC as a member of a Specification World(SPWLD) element in a CATALOGUE DB. Check your current position in thehierarchy. (See Sections 2.1 and 2.2.) An accompanying message should givea fuller explanation.

(17:6) CATREF already used in heading You have specified two CATREF pointers in a heading line. The second entrywill be ignored, but should preferably be deleted.

(17:7) Answers select previously defined spcom

The combination of answers listed for this SPCOM line leads to an SPCOMwhich has already been defined. The second SPCOM line will, therefore,never be reached during the selection process.

(17:9) DB unsuitable for SPEC You can only create a new SPEC as a member of a Specification World(SPWLD) element in a CATALOGUE DB (see Sections 2.1 and 2.2).

(17:10) DITTO IN FIRST LINEThe ditto symbol (+) means repeat the corresponding entry in the precedingline and is therefore only valid in the second or subsequent lines of the table.

VANTAGE PDMS SPECON Reference Manual B-1Version 11.6SP1


58/67

Error Messages

(17:11) No SPECIFICATION defined You must have created a new SPEC or accessed an existing SPEC before you

can add to, modify, or output any tabulated Specification data (see Chapter3).

(17:12) ID name/refno does not correspond to column heading An element identifier in an SPCOM line must correspond to a relevantReference Pointer in the heading line. It cannot be given as an answer undera SELEC question in the heading (see Section 2.3).

(17:13) ID is not a SPECThe identifier given in an OUTPUT command must refer to an accessibleSPEC (see Section 3.6). Check that you have entered the identifier correctly.

(17:14) Too many headings for output You cannot output more than 20 headings in a table.

(17:15) More answers than questions - extra answers ignored You have more entries in an SPCOM answer line than you havecorresponding entries in the heading line. Check for unintentional spaces.

(17:16) More defaults than questions - extra defaults ignored You have more entries in the defaults line than you have correspondingentries in the heading line.

(17:17) More than 20 HEADINGSThe maximum number of entries permitted in a heading line is 20.

(17:18) DETAIL already used in heading You have specified two DETAIL pointers in a heading line. The line will beignored.

(17:19) Name already defined. Name/refno will remain unnamed.The NAME specified for this SPCOM has already been used and so thissecond SPCOM line will have only its PDMS refno as its identifier. Redefinethis line with a new NAME if required.

(17:20) No. of QUESTIONS and ANSWERS do not match upIf the answers in a given SPCOM line do not correspond in a relevant waywith the SELEC questions in the heading then that SPCOM will be ignored.(See the Note in Section 3.3.5 for one possible cause of this problem.)

(17:22) Reserve name /*LIMBOSPEC has been used - object with this name hasbeen unnamedThe Specification /*LIMBOSPEC is reserved for holding REMOVE d SPCOMs(see Section 3.4.3). You cannot use it for any other purpose.

B-2 VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


59/67

Error Messages

(17:23) SPCOM does not existCheck that you have entered the SPCOM identifier correctly when modifying

an existing Specification.

(17:24) SPEC does not existCheck that you have entered the SPEC identifier correctly.

(17:26) This command only allowed in SPEC You can only use a DELETE or REMOVE command after you have accessedan appropriate SPEC (see Sections 3.2 and 3.4.3), otherwise SPECON doesnot know which Specification you are telling it to modify.

(17:28) TYPE required as first answerWhen adding a new SPCOM you must enter its TYPE (a PDMS noun) beforeits NAME. You may only use the reverse order when referring to an existingSPCOM (see Section 3.3).

(17:29) Unable to create TEXT element You can only specify one string of descriptive text for each SPEC.

(17:30) Unable to put CATREF You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.

(17:33) Undefined nameCheck that you have entered the required identifier correctly.

(17:34) SPEC or an offspring is locked.The SPEC is protected against modification. Use the UNLOCK commandbefore trying to use any of the SPECON editing facilities.

(17:35) SPEC is not emptyWhen using the COPY command, the SPEC into which the copy istransferred ( name1 in Section 3.5) must be empty. You cannot concatenateSPECs with the COPY command.

(17:36) ID must be SPCOM

The REMOVE command can only be used to remove SPCOMs. You cannotremove an entire SPEC, although you may use the REMOVE ALL option toempty it of its contents (see Section 3.4.3).

(17:38) No databases to work from You have not specified a suitable MDB before trying to enter SPECON.

(17:39) No SPEC databaseThe specified MDB does not contain an appropriate CATALOGUE DB inwhich SPECON can create SPECs.



60/67

Error Messages

(17:40) TEXT longer than 50 charactersThe text associated with a SPEC cannot exceed 50 characters in length (see

Section 3.1).

(17:41) Unable to put CMPREF You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.

(17:42) Unable to put DETAIL You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.

(17:43) Unable to put MATXT You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.

(17:44) Unable to put BLTREF You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.

(17:45) You may not delete /*LIMBOSPECThe SPEC named /*LIMBOSPEC, used to hold removed SPCOMs, is createdautomatically by PDMS and cannot be deleted, otherwise future REMOVEcommands would not work (see Section 3.4.3).

(17:46) You cannot REMOVE SPEC - use REMOVE ALLThe REMOVE command applies only to the contents of a SPEC. Use REMOVE ALL to empty the SPEC of all contents or DELETE SPEC specname toeliminate the complete SPEC. (See Section 3.4.3.)

(17:47) You cannot REMOVE items from /*LIMBOSPECThe REMOVE command can only transfer SPCOMs to /*LIMBOSPEC. Onlyby re-entering an SPCOM under its existing name can it be transferred backfrom /*LIMBOSPEC into a userdefined SPEC. (See Section 3.4.3.)

(17:48) MATXT already used in heading You have specified two MATXT pointers in a heading line. The second entrywill be ignored, but should preferably be deleted.

(17:49) CMPREF already used in heading You have specified two CMPREF pointers in a heading line. The second entrywill be ignored, but should preferably be deleted.

(17:50) BLTREF already used in heading You have specified two BLTREF pointers in a heading line. The second entrywill be ignored, but should preferably be deleted.

(17:51) SPCON NAME name already exists

You must use a unique name for each SPCON. The new SPCON will be



61/67

Error Messages

rejected.

(17:52)word

is not valid as a GTYPESee Sections 4.1.1 and 4.2.1f or examples of valid GTYPEs.

(17:53) TMPR already used in heading You have specified two TMPR pointers in a heading line. The second entrywill be ignored, but should preferably be deleted.

(17:54) Unable to put TMPR You are unable to set this Reference Pointer to the element specified.Possibly you have specified it incorrectly.



62/67

Error Messages



63/67


64/67

Nominal Pipe Size Tables

C-2 VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


65/67

Index

IndexNOTES :

The index does not normally repeat entries which occur in the Contents List The principal reference in a multiple entry is shown in bold type

(excluding occasions where a second entry refers to a syntax diagram only) References are to page numbers, not section numbers

Actual bore sizes - see BORES command ALIGNED command 3-10 ANGLE 4-2, A-5 Answers 3-6 AREA 4-10, A-5

Bolt Reference (BLTREF) 2-6, 4-4 , A-5Bolt Table (BLTAB) 2-2 , 2-6, 4-5BORES command 3-11, A-4

CATALOGUE DB 1-1, 2-1Catalogue Reference (CATREF) 2-6, 4-4 , A-5CCTAB element 2-2COMMENT command 3-7, A-6

COMP - see Piping ComponentCOMPACT command 3-10Component Catalogue (CATA) 2-2Component Properties (CMPREF, CMPT) 2-6, 4-4 , A-5Connection Compatibility (COCO) Tables 2-2COPY command 3-9, A-6CTYATTACHED 4-9, A-5CTYPE 4-9, A-5CTYEND 4-9, A-5CTYOWNING 4-9, A-5CTYSTART 4-9, A-5

Defaults 2-4, 3-3, 3-5 , A-6DELETE command 3-8, A-4Delimiting character 3-4DEPTH 4-9, A-5Detailing Text (DETAIL, DTEXT) 2-3, 2-6, 4-4 , A-5DIMENSION 4-9, A-5

EXTRA command 3-6, A-6

FIRESISTANCE 4-10 , 4-13, A-5Fitting (FITT) 2-3 , 4-7Fixed length piping 4-5

VANTAGE PDMS SPECON Reference Manual index-iVersion 11.6SP1


66/67

Index

FIXTY 4-10, A-5Fluid Reference (FLUREF) 4-4, A-4

Generic type (GTYPE) 2-3, 3-4 , 4-1, 4-7Geomset (GMSET) 2-3GRADE 4-10 , 4-13, A-5Group World (GPWLD) 2-2

Headings 3-3, 3-4 , A-5

INERTIA 4-9, A-5Insulation 4-10, 4-12ITHICKNESS 4-10 , 4-13, A-5

Joint (JOIN) 2-2 , 4-7

LIMBOSPEC 3-7 , 3-8LINETYPE 4-5, A-4

Macro input 3-11Material Reference (MATREF) 4-4, A-4Material Text (MATXT, MTEXT) 2-3, 2-6, 4-4 , A-5

Name (of SPCOM) 3-4, A-5NEW command 3-1, A-4Nominal bore sizes - see BORES command

OLD command 3-2, A-4OUTPUT command 3-9, A-4

PBORE 4-2 , 4-3, 4-12, A-5PCONN 4-2 , 4-3, A-5Piping Component (COMP) 2-3Piping Section (SECT) 2-2Pointset (PTSET) 2-3PRESSURE 4-2, A-5Profile (PROF) 2-3 , 4-7

RADIUS 4-2, A-5RATING 4-2, 4-5 , A-4, A-5REMOVE command 3-8, A-4

RENAME command 3-9, A-6SECT - see Piping SectionSelector (SELEC) 2-4 , 2-6, 3-4, 3-6, 4-2, 4-8SHOP 4-2, A-5SPECIFICATION command 3-2, A-4Specification Component (SPCOM) 2-4 , 2-6, 3-6, 3-7Specification (SPEC) 2-4 , 3-1Specification World (SPWLD) 2-2 , 2-4Structural Section (STSECT) 2-2STYPE 4-2 , 4-8, A-5Suffix (to SPREF) 3-4

index-ii VANTAGE PDMS SPECON Reference ManualVersion 11.6SP1


67/67

Index

TEMPERATURE 4-2, 4-12 , A-5TEXT command 3-1, A-4

Text answers 3-6THICKNESS 4-10, A-5TYPE (of SPCOM) 3-4, A-5

UNITS element 2-2Userdefined attributes 3-6

WEIGHT 4-9, A-5WIDTH 4-9, A-5

* (star) character 3-3+ character 3-3- character 3-3= character 3-3/*LIMBOSPEC - see LIMBOSPEC

SPECON Reference Manual

Documents

Transcript of SPECON Reference Manual