SPECON Reference Manual

PDMS SPECON
Reference Manual
Version 11.6SP1

pdms1161/SPECON Reference Manual
issue 280605

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 TO
THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
While every effort has been made to verify the accuracy of this document, AVEVA
Solutions shall not be liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing, performance or
use of this material.

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

Copyright 1991 through 2005 AVEVA Solutions Limited
All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without prior written permission of AVEVA
Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions or its licensors.

For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK

Revision History
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-i
Version 11.6SP1
Revision History
Revision-History-ii VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1

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-i
Version 11.6SP1
i
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 Manual
Version 11.6SP1

1 Introducing SPECON
1.1 What SPECON is Used For
SPECON, the PDMS Specification Constructor module, is used to create or modify the
Specification (SPEC) elements in Catalogue Databases.
These Specifications govern the choice of components from the catalogue. They must
have been set up, together with the rest of the Catalogue DB, before design work takes
place. In principle, therefore, SPECON will be one of the first modules to be used when a
new PDMS project is initiated, although in practice it is likely that a company-wide
library of Catalogues and Specifications will be created independently of any individual
design project and accessed by subsequent users to ensure overall standardisation and
quality control.
SPECON enables you to input new Specifications, to modify existing Specifications, and
to output Specifications to your terminal or to a file (to be printed or input again at a
later date).
A facility is provided so that you can make changes to a Specification without losing
compatibility between existing design data and earlier versions of that Specification.
This is achieved by maintaining valid references to obsolescent components in the
Specification 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 is
restricted to a team of Standards Engineers within the Production Engineering
Department or its equivalent. You might, therefore, be a member of such a team setting
up or updating a Specification. Alternatively, you might be a pipework or structural
designer who needs to use a Specification to select a suitable component and who wishes
to understand the principles underlying the selection process.
You are assumed to be familiar with the general principles of using PDMS, although
some of the most relevant points are repeated in this manual as a reminder.
You might already have used the Catalogue Constructor module PARAGON to set up
other parts of a Catalogue DB, but this manual does not assume that you are familiar
with the details of that module.
VANTAGE PDMS SPECON Reference Manual 1-1
Version 11.6SP1
Introducing SPECON
1.3 How This Manual is Set Out
Chapter 2 describes the structure and use of the Catalogue DB. This
explains where the Specifications created by SPECON fit into the overall
component 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 the
options which you are likely to use when setting up Specifications for the
most relevant classes of design components (Pipework, Structures and
Insulation).
Appendix A formalises the full command syntax applicable to each user
option. It is the definitive reference section for clarifying any command
queries which arise.
Appendix B explains the significance of any error messages which might be
output during the use of SPECON.
Appendix C contains the tables of pipe nominal bore sizes held within
PDMS.
The manual concludes with an Index.
1.4 Conventions Used in the Text
The following conventions are used throughout this manual to highlight certain features
of the text:
Common words which have special meanings in PDMS have initial capital
letters where it is thought that this will clarify their meaning; for example,
Element, Team etc. In particular, the word Specification has a capital letter
when it refers to a PDMS SPEC element.
Command words are shown as a combination of uppercase and lowercase
characters, using a different typeface from that used for normal text; for
example, SPECification. The uppercase part of the word (SPEC in the
preceding example) is the minimum permissible abbreviation. Where a
command word is first introduced, or where its use is defined, it will usually
be 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 special
typeface, thus
Example of Input/Output Sequence Typeface
1-2 VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1
Introducing SPECON
Character strings which begin with a slash character / are either names of
elements 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,
<diagram_name>.
Version 11.6SP1
Introducing SPECON
Version 11.6SP1

2 Catalogues and Specifications
This chapter gives an overview of the structure of a typical Catalogue DB, which
contains information 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 names only; the fifth character is given here to
make 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 hierarchy
as SCOM, SFIT, SDTE and SMTE elements, respectively. The
simplified names, which omit the S prefix, are used here because they
are 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 which
together completely define every aspect of the components listed within that catalogue.
These functional groups, which are the highest level elements in the Catalogue DB
below 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
Version 11.6SP1
Catalogues and Specifications
The functions of the individual types of element are as follows:
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, on isometrics 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 CATAs for a given purpose. It is
the elements below SPWLD which are manipulated by SPECON and which
are, therefore, of most relevance 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 BLTAB members will be
referenced from the Specifications for appropriate types 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.
That part of the hierarchy below a Catalogue element which is relevant when
considering 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
Version 11.6SP1
The functions of the individual types of element are as follows:
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 exact type, size and
geometry of each component (that is, the components Attributes, 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 SKEYs
which define the symbols used to represent components in isometric
drawings; see the VANTAGE PDMS ISODRAFT Reference Manual.)
MTEXT Material Text elements hold text which may be used to describe the
materials of construction of the components.
2.2 The Content and Format of a Specification
The component Specifications, which define the availability of components for particular
types 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 the simple hierarchy of elements shown in Figure 2-3.
SPWLD
SPEC
SELEC
SPCOM
SELEC
Specification World
Specification
Selectors
(one level for each
specification `decision')
Specification Component

Figure 2-3 The structure of a SPWLD element
Version 11.6SP1
A SPEC is equivalent to an engineering specification for a given class of piping or
structural 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 piping
components with a particular pressure rating. Such a SPEC comprises tabulated data of
the type illustrated in Figure 2-4, where each headed question column represents a
SELEC and each horizontal row represents an SPCOM.
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 the tabulated SPEC immediately below the corresponding column heading (the
SELEC element) 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
SPEC listing, before the Heading, as shown by the entries MATREF, FLUREF, RATING
and 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 component
specification, are detailed in Chapter 4.
Version 11.6SP1
HEADING
NAME
*/20GA
*/20GL
*/20RV
*/25GA
*/25CH
*/25GL
SPECIFICATION /RF300
MATREF =0
FLUREF =0
RATING 0.000
LINETYPE NUL
SELEC `QUESTIONS'
SPCOMS
REFERENCE POINTERS
DEFAULTS
-
DEFAULT SETTINGS
SPEC NAME
OVERALL SPEC POINTERS
TYPE STYP SHOP PBOR0 CATREF DETAIL MATXT CMPREF BLTREF
-
GA - =
VALV GA TRUE 20.0 /VGAEE /DGA.V.SW /MGA.V /SB20 =0
VALV GL 20.0 TRUE /VGLEE /DGL.V.SW /MGL.V =0 /SB20
VALV RV 20.0 FALS /VRVEE /DRV.V.FL /MRV.V =0 /SB20
VALV GA 25.0 TRUE /VGAFF /DGA.V.SW /MGA.V =0 /SB25
VALV CH 25.0 TRUE /VCHFF /DCH.V.SW /MCH.V =0 /SB25
VALV GL 25.0 TRUE /VGLFF /DGL.V.SW /MGL.V =0 /SB25
...
OVERALL SPEC SETTINGS

HEADING
NAME TYPE PBOR0 PBOR3 SHOP CATREF DETAIL MATXT CMPREF BLTREF
DEFAULTS
- - - = =
*/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
...
HEADING
NAME TYPE PBOR0 ANGL SHOP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - - =
*/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
...HEADING
NAME TYPE PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - 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

Version 11.6SP1
2.3 How Component Selection Works
This section explains how the tabulated Specification (SPEC) data is used to choose an
appropriate piping component from the complete catalogue. Similar principles apply to
structural components and equipment nozzles, although for these you may also use the
catalogue without a Specification.
The SELEC elements are generated automatically from the tabular SPECON input for a
given SPEC and hold all information about those attributes of a component which
determine its availability for a given purpose. For any given set of design criteria, the
route through the SELECtors follows a question and answer sequence to determine
which SPCOM is suitable. 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 answers should correspond to one, and only one, SPCOM.
The types of information considered at the SELEC decision points for PDMS piping
components 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 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), 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 selected
during 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, the
following sequence is applied:
The design component is allocated a Specification Reference (SPREF) which
is selected 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 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 the
CATREF pointer.
Version 11.6SP1
(The SPCOM also points to a DTEXT via the DETAIL pointer, an MTEXT via the
MATXT 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.
PIPE
COMPONENT
SPREF
SPEC
COMPONENT
DETAIL
MATXT
DTEXT
MTEXT
(SPCOM)
(PSPEC)
COMP
CATREF
BLTREF
BLTAB
CATALOGUE SPECIFICATIONS DESIGN DATA
CMPREF
CMPT
(PROPS DB)
via
SELECs

Figure 2-5 The links between Design Data, Specifications and Catalogue
EXAMPLE:
As an illustration of the principles of the selection process, consider the following
question 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 its
SHOP attribute set to TRUE, is represented in the SPEC by one, and only one, SPCOM,
namely */25GA. This points to the component in the Catalogue which completely
matches the specification, via the CATREF /VGAFF. The corresponding descriptive
DTEXT is pointed 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.
Version 11.6SP1
Version 11.6SP1

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 specname
NEW specname
where specname is the PDMS name which will be used to refer to the complete
Specification.
NOTE: The short form of the command is all that is necessary, since a SPEC is
the only element type which you can create at this level in SPECON
(the lower level elements SELEC and SPCOM are created indirectly
when the tabular data is entered; see Section 3.3).
For example, either of the following commands:
NEW SPEC /RF300
NEW /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 associated
text by entering the command
TEXT 300 psi Piping Specification
(Note the delimiting apostrophes enclosing the text string, which must not exceed 50
characters.)
Version 11.6SP1
How To Use SPECON
This text, which is stored in a TEXT element in the hierarchy, will be shown after the
SPEC name when the Specification is output; see Section 3.6.
Two system attributes on the PDMS SPECIFICATION element are used when the
product VANTAGE Project Resource Management (VPRM) is the source of PDMS
Specifications.
When a specification is imported to PDMS the attributes FISSUE and FINPUTBY hold
the 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, usually
working 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 specname
OLD specname
SPECification specname
specname
where specname is the name of an existing SPEC.
For example, enter any of the following commands:
OLD SPEC /RF300
OLD /RF300
SPEC /RF300
/RF300
to access the SPEC created in Section 3.1. Clearly, the simplest method is to enter just
the name of the SPEC required.
You may interrogate the SPWLD hierarchy by using the command, or change to a
different SPEC element within it by using any of the standard DB navigational
commands such as FIRST, NEXT, etc., in the usual way.
Version 11.6SP1
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 of
the SPEC named /RF300 listed in Figure 2-4 contains four tables (one for each of the
component types VALV, TEE, ELBO and FLAN), although the complete SPEC would
probably contain many more.
Version 11.6SP1
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 immediately
follow 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, the
following special characters may be used in the SPEC data entries:
* The star or asterisk character is used throughout PDMS as an abbreviation which
you can set to the name of an owning element when naming a member element in
a DB hierarchy. In most modules you must define this character by using the
command, but it is set automatically by SPECON so that it always refers to the
name of the current SPEC. For example, in the SPEC named /RF300 shown in
Figure 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 the
table with the minimum of keystrokes.
- The minus or dash character, which may be used only in the default line of a table,
means not applicable or unspecified. If a default line is present, this character
must appear under TYPE and NAME, and under any SELEC questions for which
default answers are not set. It must not appear under CATREF, DETAIL, MATXT
etc., for which defaults are never allowed.
= The equals character, when used in the default line of a table, means that the
answer will default to the first selector in list order after all other questions have
been answered.
As an example, consider the following part of a table (which incorporates all four of the
characters * - + and = ):
HEADING
TYPE NAME PBOR0 STYP CATREF DETAIL MATXT CMPREF
BLTREF
DEFAULTS
- - - =
FLAN */FG 20.0 S /FSAAPAPP /20FL /ASA-20F =0
/SBOL/20F
FLAN */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
Version 11.6SP1
How To Use SPECON
SPEC is used to select a component without specifying the required STYP, the = default
option 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 a
default line.
Since PDMS does not allow any SPREF to exist more than once, items in a SPEC which
are identical but which need to be distinguished from each other may be allocated
suffixes. ISODRAFT can be made to ignore such a suffix by recognising the delimiting
character which separates the suffix from the rest of the SPREF. For example, if the
delimiting character is defined as a colon (:), which is the default, ISODRAFT will
identify 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 the
delimiter.
3.3.3 Headings
The heading line, which defines the column headings for the rest of the table, contains
four distinct sorts of information:
TYPE is the generic type (GTYPE) of the component represented by an
SPCOM.
NAME is the unique identifier for each SPCOM.
Selector Questions define the SELEC choices which will be used to choose
an appropriate SPCOM for a given design purpose (e.g. STYPE, ANGLE
etc.).
Reference Pointers link each SPCOM to the corresponding definitions in the
other parts of the Catalogue (e.g. CATREF points to a COMP, DETAIL
points to a DTEXT, and so on).
(For full details of the available options for Selector Questions and Reference Pointers,
see Section 4.1 for piping components, Section 4.2 for structural components, or Section
4.3 for insulation.)
To define a heading, use the command syntax
Heading
TYpe NAme questions pointers
noting that the command is entered on two lines (i.e. you must press RETURN after the
command 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 is
TYPE NAME ... etc.; when an existing Specification is modified (see
Section 3.4), or when its contents are output (see Section 3.6), the
corresponding sequence is NAME TYPE ... etc.
Version 11.6SP1
How To Use SPECON
Examples of possible commands for defining headings are as follows:
For generic type TUBE -
HEADING
TYPE NAME PBOR0 SCHE SHOP CATREF DETAIL MATXT CMPREF BLTREF
For generic type ELBO -
HEADING
TYPE NAME PBOR0 STYP ANGL SHOP CATREF DETAIL MATXT CMPREF
BLTREF
For generic type REDU -
HEADING
TYPE NAME PBOR0 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF
BLTREF
For generic type BEAM -
HEADING
TYPE NAME STYP GRAD DEPT WIDT WEIG INER CATREF
and so on. See Chapter 4 for explanations of the SELEC questions used in these
headings.
The maximum number of entries in a heading line (that is, the maximum number of
columns in the table) is 20.
NOTE: The number of columns in an existing Specification cannot be changed, so it is
important that you choose the headings carefully when you create a new
Specification.
3.3.4 Defaults
To define the default settings for the SELEC answers, use the command syntax
Defaults
default_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 columns
must have - (null) defaults and the Reference Pointer columns must have no default
entries at all.
For example, heading and default lines for a table of VALV Specifications might be
entered as follows:
HEADING
TYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXT
CMPREF BLTREF
DEFAULTS
- - - GATE =
Version 11.6SP1
How To Use SPECON
Any VALV selected without specifying the STYPE (for example, by using the command
NEW VALV SEL in a design module) will have the word GATE assigned as the answer to
the 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 an
appropriate answer (value, word etc.) under each column heading, for each SPCOM line
in turn. The spacing between the answers is not critical, although interpretation of the
SPEC table may be easier if you align the headings and answers in vertical columns, as
illustrated in Figure 2-4. Note, however, that the tabulation used when data in input to
a 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 save
repetitive 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, FE
etc.) in answers which are expected to be words. This applies particularly to the
STYPE Selector (see Section 3.3.6). If, for example, a Specification included the
adjacent headings PBOR0 STYPE and you entered the answers 25 for the bore
and FT for the STYPE, SPECON would interpret this as a bore of 25 feet and
would 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 two
formats: 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 text
string with the word TEXT to avoid possible confusion with user-defined dimensioning
units.
For example, the STYP for a gate valve (generic type VALV) could be listed either as
GATE or as the equivalent form TEXT GATE. If these are to be truly equivalent, you
must use uppercase characters for GATE in the text answer. Alternatively, the text
version could be extended to give a more explicit description; for example, TEXT High
Pressure Gate.
3.3.7 Including User-defined Attributes in Specifications
To include the settings of user-defined attributes in a Specification, for subsequent use
by 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)

Version 11.6SP1
How To Use SPECON
User-defined attribute settings included in this way (one per line) will be correctly
output 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 as
valid components.
3.3.8 Including Comments in Specifications
To include a comment in a Specification, typically to clarify details of its content for
future 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 the
SPEC 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 that
described in Section 3.3 for setting up a new SPEC; that is, enter the command lines
Heading
TYpe NAme questions pointers
Defaults (optional)
default_settings (optional)
selector_answers pointer_settings
The heading line TYPE NAME questions pointers must be the same as the
corresponding line in the existing SPEC. SPCOMs entered in this way will be merged
into the table for the relevant component type when the SPEC is output.
3.4.2 Deleting or Removing a SPEC or SPCOM
The terminology used here is significant:
If a SPEC or SPCOM is deleted, all aspects of it are eliminated from the Catalogue
DB. If an existing design includes a component with an SPREF which points to the
deleted data, any future access to the Design DB, say to produce a drawing, will
result 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 special
archive Specification named /*LIMBOSPEC. The data still exists, so that references
to it are still valid, but it no longer forms part of the original named SPEC. This
facility is useful:
Version 11.6SP1
How To Use SPECON
a. when a component is withdrawn from use for new designs but its continued use in
existing designs is permitted
b. when use of a component is to be suspended temporarily while modifications are
made.
NOTE: If you are using more than one Catalogue DB, there is one archive Specification
for each DB. This avoids inadvertent transfer of data between DBs due to
removal and subsequent restoration of SPECs or SPCOMs. Such multiple
archive Specifications are named /*LIMBOSPEC, /*LIMBOSPEC_1,
/*LIMBOSPEC_2 etc. Only the single form /*LIMBOSPEC will be referred to in
the remainder of this manual.
To delete individual SPCOM lines from a SPEC, use the command syntax
DELETE spcom1 spcom2 ...
where spcom1, spcom2 etc. identify the relevant SPCOMs. For example,
/RF300
DELETE */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 /RF300
will access and then delete the entire SPEC named /RF300.
To delete all SPCOMs from a SPEC without deleting the SPEC itself, enter the
command
DELETE ALL
NOTE: The DELETE command should be used with care. No checks are made
against any design data before the SPCOMs are deleted and any
references to such SPCOMs in a Design DB will become invalid. If in
doubt, use the REMOVE command.
To remove individual SPCOM lines from a SPEC, use the command syntax
REMove spcom1 spcom2 ...
where spcom1, spcom2 etc. identify the relevant SPCOMs.
The effect of this command is to remove all answers from the named SPCOM lines,
except for the pointers CATREF and DETAIL, and to transfer those SPCOMs to the
archive Specification /*LIMBOSPEC. If a Specification Reference (SPREF) in a Design
DB points to an SPCOM which cannot be found in the currently named SPEC, it will
automatically look for that SPCOM in /*LIMBOSPEC.
To remove the entire contents of a SPEC, enter the command
REMove ALL
Version 11.6SP1
How To Use SPECON
To reinstate a removed SPCOM, ensure that you are pointing to the correct
current 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 will
automatically 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 differing
only in the CATREF and DETAIL pointers of their member SPCOMs. To enable you to
create these easily, SPECON allows you to make a copy of an existing SPEC which you
can 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 and
name2 define the old and new name parts, respectively, for the individual SPCOM lines
throughout 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 similar
Specification /SPEC1, enter the commands
NEW SPEC /SPEC2
COPY /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 /SPEC2
by 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 for
subsequent printing). The device to which SPECON is to send the output may be defined
by using the standard device-selection commands described in the PDMS Monitor
Reference 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 ...
Version 11.6SP1
How To Use SPECON
For example, to send the content of Specification /RF300 to a file named /RF300.SPEC in
your current OS directory, enter the commands
FILE /RF300.SPEC
OUTPUT /RF300
The data will be output to the selected device in a similar tabular format to that in
which it was entered into the SPEC, although the precise tabulation settings will have
been 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 which
applies 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 TYPE
NAME ... (to be used, for example, as input at a later time; see Section 3.7), use the
extended command syntax
OUTput NEW specname1 specname2
(The default version of the OUTPUT command is equivalent to OUTPUT OLD, but there
is 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 in
the original SPEC. You can compact the output macro file by replacing multiple spaces
by 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 the
Specification /RF300, in a format suitable for use as input to a different Specification,
you might use the commands
FILE /SPECDATA
OUTPUT NEW VALV FLAN /RF300
Version 11.6SP1
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 input
and output in either metric or imperial units. The program converts from one set of
units 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, it
is 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 output
as actual or nominal sizes by using the command syntax
BOREs ACTual
BOREs 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 editor
and the data file thus created can be checked for errors before it is read into the
Catalogue DB. If any syntax errors are found when the macro file is run in SPECON,
the file may be edited to correct the mistakes and rerun with the minimum amount of
effort.
The format of the macro input file is exactly the same as that produced by the OUTPUT
NEW command described in Section 3.6.2; that is, TYPE must precede NAME in the
heading and SPCOM lines. This means that Specifications which have been sent to a file
may 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 carrying
out major revisions of existing SPECs. Any part of an SPCOM line may be changed in
this way other than the NAME or TYPE; if these were changed SPECON would not be
able to locate the SPCOM to overwrite it.
Remember, when creating SPECON input macros from the keyboard, that the symbols *
(automatically set to the Specification Name) and + (equivalent to ditto) can be used to
save repetitive typing (see Section 3.3.2).
To update an existing macro to use text strings instead of PDMS words for STYPE
selector answers (see Section 3.3.6), edit the macro so that each four-character word
representing an STYP (or equivalent) is replaced by the keyword TEXT followed by the
replacement text enclosed between apostrophes. For example, you would replace GATE
Version 11.6SP1
How To Use SPECON
by TEXT GATE. Note that the text must be in uppercase characters if it is to be
interpreted in the same way as the equivalent PDMS word.
Version 11.6SP1
How To Use SPECON
Version 11.6SP1

4 Details of Typical Specifications
This chapter explains, with examples, typical data entries which might be used in
Specifications for the main types of design components (piping components, structural
components 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 of
GTYPEs:
ATTAchment
NOZZle
Bend OLEts
Bolt PCLamp
CAP PCOmp
CLOsure REDucer
COUpling ROD
CROSs SCLamp
DUCting SHU
Elbow TEE
FBLind TUBe
FILter TRAP
FLAnge UNIon
FLG VALve
FTUbe VENt
GASket VFWay
HELement VTWay
INSTrument 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 list
them, when defining SPECs for piping components. The following headings should meet
most of your requirements:
Version 11.6SP1
Details of Typical Specifications
Pbore integer
Specifies the bore of p-point integer. For multiway components (such as a Tee), more
than one PBORE SELEC may be specified (PBORE1, PBORE2 etc.).
PConn integer
Specifies the connection type of p-point integer.
NOTE: See Section 4.1.3 for important information about the use of the special
cases PBORE0 and PCONN0 which may be applied to the preceding
SELECs.
SType
Defines the Specific Type of the component; it is effectively a subdivision of a
GTYPE. For example, a component of GTYPE VALV may have an STYPE GATE,
GLOB, CHEC etc.
ANGle
Defines the required angle of an ELBO or BEND, when DDANGL has been used in
the component pointset (PTSET). The answer to this SELEC question in an SPCOM
may be a single value (e.g. 90.0) or a range of values (e.g. 45.0,90.0).
RADius
Defines the required radius of an ELBO or BEND, when DDRADI has been used in
the component pointset (PTSET). May be a single value or a range.
TEMperature
Defines the operating temperature.
PRessure
Defines the operating pressure.
RATing
Defines the pressure rating.
SHOP
Defines whether the component is intended for shop fabrication (SPCOM answer
TRUE or SHOP) or on-site assembly (SPCOM answer FALSE or SITE).
In addition to the standard SELEC headings, you may use any word (up to four letters),
with or without a numeric qualifier, to define your own questions. For example, if you
wished to include a range of colour-coded reducers in your Catalogue (perhaps having a
base colour and a marker colour to indicate suitability for particular types of use), you
might include the questions COL1 and COL2 as SELEC headings in the Specification
for TYPE REDU. The SPCOMs containing the answers to these questions will be
considered by the selection process if the appropriate option is specified in your design
module command; for example
SELECT NEW REDU ... WITH COL1 RED WITH COL2 BLUE
If COL1 and/or COL2 are omitted, the default colours (answers) will be used.
Version 11.6SP1
4.1.3 P-Point Zero: A Special Case
Normally, when the bore or connection type of a p-point is used as a SELEC question,
the answer provided will apply to a specific p-point number. For example, PBORE1 will
be the components arrive bore, PBORE2 will be its in-line leave bore, and so on.
However, under some circumstances this need not apply. In such cases you may use the
Selectors PBORE0 and/or PCONN0 to represent either the arrive or leave p-point of the
component.
For example, assume that you wish to select a flange. Normally P1 would represent p-
arrive and P2 would represent p-leave, so that the Selector PBORE1 could be matched
against the p-leave bore of the preceding component to select a suitable flange. If,
however, the flange is reversed (flipped), P2 becomes the p-arrive and so a Specification
based on the Selector PBORE1 will not allocate a correct match.
If the SELEC is defined as PBORE0, all p-points of the new component will be tested, in
numeric order, against the p-leave of the preceding component. Thus, in the case of our
flipped flange, if a P1 match cannot be found then P2 will be tested as a second choice. If
either P1 or P2 matches the answer given for PBORE0, then a flange will be selected.
The same principle applies to the connector type PCONN0.
You will find the P-point Zero convention very useful when compiling Specifications.
Figure 2-4, for example, illustrates the use of PBORE0 (abbreviated to PBOR0) for four
component types.
4.1.4 Reference Pointers and Settings
The following reference pointers and settings are applicable to the specification of piping
components (see the examples in Section 0
Individual Specification Component Pointers
These pointers, which are attributes of SPCOM elements, are set individually for each
line in a Specification table. Only the CATREF pointer is obligatory; the other pointers
may be omitted from the heading when the Specification is created or they may be left
as unset (=0) in individual SPCOM lines.
CATREF - Catalogue Reference:
Points to one particular component in the Catalogue DB which meets all the SELEC
requirements specified for an individual SPCOM. A CATREF heading is obligatory
for every SPEC table since it is the essential link between the design specification
and the choice of a component from the Catalogue. It is important that the
component pointed to by the CATREF already exists when the SPCOM is defined,
otherwise you will receive the error message Undefined Name and the CATREF in
the Specification will be shown as =0 (i.e. unset).
DETAIL - Detail Text:
Points to a DTEXT element in the Catalogue DB. This holds any general text which
Version 11.6SP1
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 used
to describe the materials of construction of the corresponding component in
schedules, on isometric drawings, etc. (see the PARAGON and ISODRAFT Reference
Manuals).
BLTREF - Bolt Reference:
Points to a BLTAB element in the Catalogue DB. This contains details of the bolts
needed to connect the corresponding component into a pipeline (see the ISODRAFT
Reference 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 Reference
Manual).
OverallSpecificationPointers
These pointers, which are attributes of SPEC elements, are set for an entire
Specification. Their settings are shown at the beginning of the Specification,
immediately after the name, and always appear, even if they remain unset.
MATREF - Material Reference:
Points to a SOLID element in the Properties DB. This holds information about the
properties 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 the
properties of the liquids or gases for use with which the piping components are
suitable (see the PROPCON Reference Manual).
Overall Specification Settings
These are not pointers to other elements but are local to the Specification itself. Their
settings are shown at the beginning of the Specification, immediately after the MATREF
and FLUREF pointers, and always appear, having default settings if you have not
specified otherwise. These attribute settings are used only by ISODRAFT and are
relevant only when fixed length piping is being used. You are referred to the section
entitled 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 the
Specification are intended for service. ISODRAFT can then use this setting to
Version 11.6SP1
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 Pipe
FX Fixed Length
ISODRAFT uses this setting to decide whether or not to append the length of a
component to its item code in a material list. The length is appended if linetype is set to
FP, but is assumed to be incorporated into the standard code if linetype is set to FX. The
default setting is NUL (i.e. variable length piping between components is assumed).
Version 11.6SP1
4.1.5 Examples From Piping Component Specifications
To keep the examples brief, very few lines (SPCOMs) are shown for each GTYPE.
NEW SPECIFICATION /RF300
MATREF =0
FLUREF =0
RATING 0.000
LINETYPE NUL
HEADING
TYPE NAME PBOR0 SHOP CATREF DETAIL MATXT CMPREF BLTREF
- - - =
TUBE */20TU 20.0 TRUE /TUEE /DTUB1 /MTUB =0 =0
TUBE */25TU 25.0 TRUE /TUFF /DTUB1 /MTUB =0 =0
...
HEADING
TYPE NAME PBOR0 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF
- - - PE =
FTUB */20FT 20.0 PE TRUE /FTEE /DFTUB /MFTUB =0 =0
FTUB */25FT 25.0 PE TRUE /FTFF /DFTUB /MFTUB =0 =0
...
HEADING
TYPE NAME PBOR0 RADI ANGL SHOP CATREF DETAIL MATXT CMPREF
BLTREF
- - - - = =
BEND */20VB1 20.0 100.0 90.0 TRUE /VBEE /DVBEND1 /MVBEND =0 =0
BEND */20VB3 20.0 100.0 180.0 TRUE /BEEE /DBEND1 /MVBEND =0 =0
BEND */20VB2 20.0 60.0 90.0 TRUE /VBEE /DVBEND2 /MVBEND =0 =0
BEND */20VB4 20.0 60.0 180.0 TRUE /BEEE /DBEND2 /MVBEND =0 =0
BEND */25VB1 25.0 125.0 90.0 TRUE /VBFF /DVBEND1 /MVBEND =0 =0
...
HEADING
TYPE NAME PBOR0 CATREF DETAIL MATXT CMPREF BLTREF
GASK */20G 20.0 /GAEE /DGASK /MGASK =0 =0
GASK */25G 25.0 /GAFF /DGASK /MGASK =0 =0
...
HEADING
TYPE NAME PBOR1 PBOR2 STYPE SHOP CATREF DETAIL MATXT CMPREF
BLTREF
- - - - CONC =
REDU */25RC1 25.0 20.0 CONC TRUE /RCFE /DRED.C /MRED =0 =0
REDU */25RE1 25.0 20.0 ECC TRUE /REFE /DRED.E /MRED =0 =0
REDU */32RC1 32.0 25.0 CONC TRUE /RCGF /DRED.C /MRED =0 =0
REDU */32RE1 32.0 25.0 ECC TRUE /REGF /DRED.E /MRED =0 =0
...
and so on.
(See Figure 2-4 for some other examples.)
Version 11.6SP1
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 of
GTYPEs:
BASE
BEAM
BRACe
COLUmn
FITTing
GANTry
GIRDer
JOINt
JOISt
KNEE
PILE
PROFile
PURLin
RIDGe
ROD
SCTN
SDRAil
SPLIce
STANchion
STIFfener
STRUt
TIE
4.2.2 Selectors
The following SELEC questions are those which you are likely to use when defining
SPECs for structural components:
SType
Defines the Specific Type of the component; particularly applicable to the general
generic types PROF, JOIN and FITT. Examples of STYPE answers which might be
applied to structural components to cover European, American and British
standards include:
Version 11.6SP1
STYPE Meaning
C Channel section or American standard Cshapes (tapered flanges)
CHS Circular hollow section
CRSJ Castellated rolled steel joists
CUB Castellated universal beams
CUC Castellated universal columns
CZB Castellated Zbeams
EAI Imperial equal angles
EAM Metric equal angles
HD European columns (wide flanges)
HE European beams (wide flanges)
HL/HX European beams (very wide flanges)
HP Bearing piles (wide flanges)
IPE European beams (parallel faced flanges)
IPN European standard beams (tapered flanges)
LST Long stalk teebars
M/W American Ishapes (wide flanges)
RHS Rectangular hollow section
RSJ Rolled steel joists
S American standard Ishapes (tapered flanges)
T Tee bars
TUB Tees cut from universal beams
TUC Tees cut from universal columns
U European small channels
UB Universal beams
UBP Universal bearing piles
UC Universal columns
UEAI Imperial unequal angles
UEAM Metric unequal angles
UPN European standard channels
PLAT Plate girders
Version 11.6SP1
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 leg
DIME2 Width or short leg
CTYPE integer
A connection type. The qualifying integer is optional; suggested conventions are:
CTYPE1 Start connection
CTYPE2 End connection
CTYPE3 Attached connection
CTYPE4 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 to
use cm rather than mm here to avoid having to list large values.) The qualifying
integer is optional; suggested conventions are:
Version 11.6SP1
INER1 Inertia about x-x
INER2 Inertia about y-y
INER3 Inertia about u-u
INER4 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 thickness
THIC2 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 a
numeric 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 component
specifications 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.
Version 11.6SP1
4.2.4 Examples From Structural Component Specifications
The following excerpt from a Specification for structural steelwork components
illustrates some of the features defined in the preceding sections:
NOTE: The Reference Pointers DETAIL, MATXT, CMPREF and BLTREF have
been omitted to save space. Although these are available to give
consistency with Piping Specifications, you are unlikely to use these for
structural components (BLTREF, in particular, would have no meaning
for a structural component). No defaults have been set in this example.
NEW SPECIFICATION /BS4.PT1
MATREF =0
FLUREF =0
RATING 0.000
LINETYPE NUL
TEXT Middlesbrough Mills
HEADING
TYPE NAME STYP GRADE WIDTH DEPTH WEIGHT INERTIA CATREF
BEAM */UB1 UB 43 465 153 82 32435 /457X152X82UB
+ */UB2 + 50 465 153 82 32435 /457X152X82UB
+ */UB3 + 43 310 125 48 9504 /305X127X48UB
...
HEADING
TYPE NAME STYP GRADE DEPTH WIDTH WEIGHT INERTIA CATREF
BRAC */UEA1 UEAM 43 200 150 47 2376 /200X150X18L
+ */UEA2 + 50 200 150 47 2376 /200X150X18L
+ */UEA3 + 43 125 75 18 354 /125X75X12L
...
HEADING
TYPE NAME STYP WIDTH DEPTH WEIGHT INER1 INER2 CATREF
PROF */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
HEADING
TYPE NAME STYP DEPT WIDT WEIG INER1 INER2 CATREF
PROF */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.
Version 11.6SP1
4.3 Selectors and Pointers for Insulation
The information given in this section applies specifically to the generic type INSulation.
4.3.1 Pipework Insulation
You do not select and store Insulation in the same way that you select piping
components from other modules. The Insulation Specification is interrogated
automatically by modules such as DESIGN each time insulation details are required.
When setting up an Insulation Specification you must follow a strict format if this
automatic selection is to work properly.
For any specific insulation material, the correct insulation thickness for a given
pipework application is usually derived from two Selector questions:
TEMPerature:
The working temperature; usually specified as a temperature range (e.g. 101,200)
PBOR0:
The nominal diameter of the component; usually specified as a range of bore sizes
(e.g 1, 2 using inch bores or 25,70 using metric bores)
These might be related to the available thicknesses in the following way:
Temperature Range Bore Range Insulation Thickness
101 - 200 1 - 2
1
/2 1
101 - 200 3 - 8 1
1
/2
201 - 400 1 - 2
1
/2 2
201 - 400 3 - 8 3
0 - 100 1 - 8 1
where the bores and insulation thickness are defined in inches. It is assumed in this
example that the minimum insulation thickness which can be handled conveniently is 1
inch and so this has been applied to all pipe sizes in the low temperature range (0 to 100
degrees).
This data would result in an Insulation Specification of the following form:
NEW SPEC /INSPEC
HEADING
TYPE NAME TEMP PBOR0 CATREF DETAIL
INSU */IN1 0,100 1,8 /IC1 /CAL.SIL
INSU */IN2 101,200 1,2.5 /IC1 /CAL.SIL
INSU */IN3 101,200 3,8 /IC1.5 /CAL.SIL
INSU */IN4 201,400 1,2.5 /IC2 /CAL.SIL
INSU */IN5 201,400 3,8 /IC3 /CAL.SIL
NOTE: Because of possible ambiguity due to the overlapping ranges of PBOR0,
the order in which the SELEC headings are tabulated is important. For
the successful selection of Insulation the TEMP question must be
tabulated before the PBOR0 question.
Version 11.6SP1
4.3.2 Structural Insulation
Insulation for Sections, Joints and Fittings may be selected from an Insulation
Specification by using the selection criteria Grade, Fire Resistance and Insulation
Thickness derived from the current component. An extract from a typical Insulation
Specification for use in structural design might be as follows:
NEW SPECIFICATION /BS4.PT1.INSUL
HEADING
TYPE NAME GRADE FIRE ITHI CATREF
DEFAULTS
- - 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
Version 11.6SP1
Version 11.6SP1

A Command Syntax Diagrams
A.1 Introduction
This appendix contains the legal command and interrogation syntax diagrams relevant
to the PDMS SPECON module. These diagrams formalise the precise command
sequences which may be used and are intended to supplement the explanations given in
the 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 lowercase
letters enclosed in angled brackets, e.g. <gid>. These short names, which are
used for crossreferencing purposes in the text and within other syntax
diagrams, are supplemented by fuller descriptions where they are not self-
explanatory.
Commands to be input from the 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 and lowercase letters.)
For example, the command
REMove
may be input in any of the following forms:
REM
REMO
REMOV
REMOVE
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-1
Version 11.6SP1
Command Syntax Diagrams
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
>--+-- ABC ----.
| |
|-- PQR ----|
| |
|-- <dia> --|
| |
-----------+-->
means you may type in ABC or PQR or any command allowed by the syntax given in
diagram <dia> or just press 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
.-----<-----.
/ |
>--*-- option1 --|
| |
|-- option2 --|
| |
-- option3 --+-->
permits any combination of option1 and/or option2 and/or option3 to be used (where
the options may define commands, other syntax diagrams, or command arguments).
This may form an exception to the rule of reading from top left to bottom right.
The simplified format
.---<----.
/ |
>--*-- name --+-->
means that you may type in a list of PDMS names, separated by at least one space.
A-2 VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1
A.3 Command Arguments
These are inputs which are necessary to qualify command words. They are distinguished
by appearing in italics.
Name Definition Example
name PDMS element name /ABCDE
refno PDMS reference number =23/1403
integer a positive integer 0, 3
value signed number 3.142, -23.66, -34
word alphabetic word NULL, VALV (4 chars. max.)
text alphanumeric string Enclose Between Apostrophes
sign 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 this
manual.
Version 11.6SP1
A.4.1 <speca>
.----------------------------<----------------------------.
/ |
>---*--- NEW ---+--- SPECification ---. |
| | | |
| ---------------------+--- name ----------------|
| |
|---OLD ---+--- SPECification ---. |
| | | |
| ---------------------+ |
| | |
|--- SPECification --------------+--- <id> -----------------|
| |
|--- <table> ---> |
| |
|--- REMove ---. .----<-----. |
| | / | |
|--- DELETE ---+---*--- <id> ---+----. |
| | | |
| |--- ALL -------------| |
| | | |
| --- SPECification ---+----------------------|
| |
|--- TEXT --- text -----------------------------------------|
| |
|--- OUTput ---+--- NEW ---. |
| | | |
| |--- OLD ---| .-----<-------. |
| | |/ | |
| -----------*--- <gtype> --- .----<-----. |
| | / | |
| ---------------*--- <id> ---+---|
| |
|--- COMPact ---. |
| | |
|--- ALIGned ---+-------------------------------------------|
| |
|--- <copy> ------------------------------------------------|
| |
|--- MATRef ---. |
| | |
|--- FLURef ---+--- <id> -----------------------------------|
| |
|--- RATIng --- value --------------------------------------|
| |
|--- LINETYpe --- word -------------------------------------|
| |
--- BOREs ---+--- ACTual ----. |
| | |
--- NOMinal ---+-----------------------------+--->
Version 11.6SP1
A.4.2 <table>
.--------<--------.
/ |
>--- <heading> ---*--- <default> -----|
| |
|--- <linesp> ------
|
--->
Version 11.6SP1
A.4.3 <heading>
.---------------------------.
/ |
>--- Heading - nl --+-- TYpe - NAme --. .--*--- PBore --- integer -------|
| | | | |
-- NAme - TYpe --+-- |--- PConn --- integer -------|
| |
|--- SType -------------------|
| |
|--- ANGle -------------------|
| |
|--- RADius ------------------|
| |
|--- TEMperature -------------|
| |
|--- PRessure ----------------|
| |
|--- RATing ------------------|
| |
|--- SHOP --------------------|
| |
|--- CATref ------------------|
| |
|--- DETail ------------------|
| |
|--- MATXt -------------------|
| |
|--- CMPref ------------------|
| |
|--- BLTref ------------------|
| |
|--- DEPth -------------------|
| |
|--- WIDth -------------------|
| |
|--- CTYStart ----------------|
| |
|--- CTYEnd ------------------|
| |
|--- CTYAttached -------------|
| |
|--- CTYOwning ---------------|
| |
|--- FIXty -------------------|
| |
|--- GRADe -------------------|
| |
|--- FIREsistance ------------|
| |
|--- ITHIckness --------------|
| |
|--- AREA --------------------|
| |
|--- WEIGht ------------------|
| |
|--- DIMEnsion ---. |
| | |
|--- CTYPE -------| |
| | |
|--- INERtia -----| |
| | |
|--- THICkness ---| |
| | |
|--- word --------+-- value --|
| | |
----> -----------
Version 11.6SP1
A.4.4 <default>
.------------.
/ |
>--- Defaults ---
nl
---
sign
---
sign
---*--- <uval> ---|
| |
|--- sign -----|
| |
|--- word -----|
| |
|--- equals ---
|
--->
A.4.5 <linesp>
>--+--- noun ---.
| |
|---
sign
----+--- name -----.
| |
--- <id> ---+--- noun -----|
| |
|--- sign -----| .-----------------------------------------.
| |/ |
--------------*--- word ----------------------------------|
| |
|--- TEXT --- text -------------------------|
| |
|--- EXTRA --- :uda_name --- uda_setting ---|
| |
|--- COMMENT --- text ----------------------|
| |
|--- <uval> ---+--- comma --- <uval> ----. |
| | | |
| -------------------------+--|
| |
|--- sign ----------------------------------|
| |
|--- <id> ----------------------------------
|
--->
Version 11.6SP1
A.4.6 <id>
>---+--- name---.
| |
--- refno---+--->
A.4.7 <copy>
>--- COPY --- <id> ---+--- REName --- name --- name ---.
| |
--------------------------------+--->
A.4.8 <uval>
>---+--- value ----------.
| |
--- <expression> ---+--- EXponential --- value ---.
| |
-----------------------------+--- MM -------.
| |
|--- Metres ---|
| |
|--- INches ---|
| |
|--- FT -------|
| |
|--- FEet -----|
| |
|--- text -----|
| |
--------------+--->
Version 11.6SP1
A.5 Other PDMS Command Syntax
Common commands which may be legally used from within SPECON, but which are not
directly related to this module, include the following:
Function(s) Syntax Diagram Name
Actions setting (i.e. ACTIONS command) <actset>
Element identification and database navigation <gid> and its subsidiary syntax
Device control <devvic>
Date and time (real & elapsed) <klok> and <datxtr>
Querying specific options:
Actions <qact>
Heading banner <qbann>
Buffers <qbuff>
Input/output device <qdevc>
Input/output counters <qioc>
Project details <qproj>
Defining the current (default) units of measurement <setun>
Attribute type references <satt>
Module selection <smodu>
Giving system commands <syscom>
Defining logical expressions etc. <pml>
Version 11.6SP1
Version 11.6SP1

B Error Messages
The following is a list of those error messages specific to SPECON. All such error
messages have a message number beginning with 17. Any other messages that may be
output are not described here as they are not specific to SPECON.
NOTE: Since some other modules access the Specifications directly during their
normal functioning (for example, to select insulation data) you may
receive SPECON error messages while working in those modules.
(17:2) Cannot access ID
The element specified does not appear to exist in this DB. Check that you
have entered the identifier correctly.
(17:3) Cannot access SPECIFICATION
Check that you have entered the identifier for the SPEC correctly.
(17:4) Cannot create SPCOM or SELEC
You can only add a new SPCOM line or SELEC question after you have
created a 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 the
hierarchy. (See Sections 2.1 and 2.2.) An accompanying message should give
a fuller explanation.
(17:6) CATREF already used in heading
You have specified two CATREF pointers in a heading line. The second entry
will 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 SPCOM
which 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 LINE
The ditto symbol (+) means repeat the corresponding entry in the preceding
line and is therefore only valid in the second or subsequent lines of the table.
VANTAGE PDMS SPECON Reference Manual B-1
Version 11.6SP1
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 Chapter
3).
(17:12) ID name/refno does not correspond to column heading
An element identifier in an SPCOM line must correspond to a relevant
Reference Pointer in the heading line. It cannot be given as an answer under
a SELEC question in the heading (see Section 2.3).
(17:13) ID is not a SPEC
The identifier given in an OUTPUT command must refer to an accessible
SPEC (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 have
corresponding 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 corresponding
entries in the heading line.
(17:17) More than 20 HEADINGS
The maximum number of entries permitted in a heading line is 20.
(17:18) DETAIL already used in heading
You have specified two DETAIL pointers in a heading line. The line will be
ignored.
(17:19) Name already defined. Name/refno will remain unnamed.
The NAME specified for this SPCOM has already been used and so this
second SPCOM line will have only its PDMS refno as its identifier. Redefine
this line with a new NAME if required.
(17:20) No. of QUESTIONS and ANSWERS do not match up
If the answers in a given SPCOM line do not correspond in a relevant way
with the 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 has
been unnamed
The Specification /*LIMBOSPEC is reserved for holding REMOVEd SPCOMs
(see Section 3.4.3). You cannot use it for any other purpose.
B-2 VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1
Error Messages
(17:23) SPCOM does not exist
Check that you have entered the SPCOM identifier correctly when modifying
an existing Specification.
(17:24) SPEC does not exist
Check that you have entered the SPEC identifier correctly.
(17:26) This command only allowed in SPEC
You can only use a DELETE or REMOVE command after you have accessed
an appropriate SPEC (see Sections 3.2 and 3.4.3), otherwise SPECON does
not know which Specification you are telling it to modify.
(17:28) TYPE required as first answer
When adding a new SPCOM you must enter its TYPE (a PDMS noun) before
its NAME. You may only use the reverse order when referring to an existing
SPCOM (see 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 name
Check that you have entered the required identifier correctly.
(17:34) SPEC or an offspring is locked.
The SPEC is protected against modification. Use the UNLOCK command
before trying to use any of the SPECON editing facilities.
(17:35) SPEC is not empty
When using the COPY command, the SPEC into which the copy is
transferred (name1 in Section 3.5) must be empty. You cannot concatenate
SPECs with the COPY command.
(17:36) ID must be SPCOM
The REMOVE command can only be used to remove SPCOMs. You cannot
remove an entire SPEC, although you may use the REMOVE ALL option to
empty 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 database
The specified MDB does not contain an appropriate CATALOGUE DB in
which SPECON can create SPECs.
Version 11.6SP1
Error Messages
(17:40) TEXT longer than 50 characters
The text associated with a SPEC cannot exceed 50 characters in length (see
Section 3.1).
(17:41) Unable to put CMPREF
(17:42) Unable to put DETAIL
(17:43) Unable to put MATXT
(17:44) Unable to put BLTREF
(17:45) You may not delete /*LIMBOSPEC
The SPEC named /*LIMBOSPEC, used to hold removed SPCOMs, is created
automatically by PDMS and cannot be deleted, otherwise future REMOVE
commands would not work (see Section 3.4.3).
(17:46) You cannot REMOVE SPEC - use REMOVE ALL
The REMOVE command applies only to the contents of a SPEC. Use REMOVE
ALL to empty the SPEC of all contents or DELETE SPEC specname to
eliminate the complete SPEC. (See Section 3.4.3.)
(17:47) You cannot REMOVE items from /*LIMBOSPEC
The REMOVE command can only transfer SPCOMs to /*LIMBOSPEC. Only
by re-entering an SPCOM under its existing name can it be transferred back
from /*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 entry
(17:49) CMPREF already used in heading
You have specified two CMPREF pointers in a heading line. The second entry
(17:50) BLTREF already used in heading
You have specified two BLTREF pointers in a heading line. The second entry
(17:51) SPCON NAME name already exists
You must use a unique name for each SPCON. The new SPCON will be
Version 11.6SP1
Error Messages
rejected.
(17:52) word is not valid as a GTYPE
See Sections 4.1.1 and 4.2.1for examples of valid GTYPEs.
(17:53) TMPR already used in heading
You have specified two TMPR pointers in a heading line. The second entry
(17:54) Unable to put TMPR

Version 11.6SP1
Error Messages
Version 11.6SP1

C Nominal Pipe Size Tables
As explained in Section 3.6.4, PDMS holds tables of nominal pipe sizes which it uses in
preference to actual sizes if an actual and a nominal size fall within a predefined
tolerance band. These tables comprise the following diameters:
Metric Units Imperial Units Metric Units Imperial Units
(mm) (inches) (mm) (inches)
6.0 0.125 900.0 36.0
8.0 0.250 950.0 38.0
10.0 0.375 1000.0 40.0
15.0 0.500 1050.0 42.0
20.0 0.750 1100.0 44.0
25.0 1.00 1150.0 46.0
32.0 1.25 1200.0 48.0
40.0 1.50 1250.0 50.0
50.0 2.00 1300.0 52.0
65.0 2.50 1350.0 54.0
80.0 3.00 1400.0 56.0
0.0 3.50 1450.0 58.0
100.0 4.00 1500.0 60.0
125.0 5.00 1600.0 64.0
150.0 6.00 1650.0 66.0
200.0 8.00 1750.0 68.0
250.0 10.0 1800.0 72.0
300.0 12.0 1850.0 74.0
350.0 14.0 1900.0 76.0
400.0 16.0 1950.0 78.0
450.0 18.0 2000.0 80.0
500.0 20.0 2050.0 82.0
550.0 22.0 2100.0 84.0
600.0 24.0 2200.0 88.0
650.0 26.0 2400.0 96.0
700.0 28.0 2600.0 104.0
750.0 30.0 2800.0 152.0
800.0 32.0 3000.0 120.0
850.0 34.0 3200.0 128.0
3400.0 136.0
3600.0 136.0
3800.0 1
4000.0 136.0
VANTAGE PDMS SPECON Reference Manual C-1
Version 11.6SP1
Nominal Pipe Size Tables

C-2 VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1
Index
Index
NOTES:
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-5
Bolt Table (BLTAB) 2-2, 2-6, 4-5
BORES command 3-11, A-4
CATALOGUE DB 1-1, 2-1
Catalogue Reference (CATREF) 2-6, 4-4, A-5
CCTAB element 2-2
COMMENT command 3-7, A-6
COMP - see Piping Component
COMPACT command 3-10
Component Catalogue (CATA) 2-2
Component Properties (CMPREF, CMPT) 2-6, 4-4, A-5
Connection Compatibility (COCO) Tables 2-2
COPY command 3-9, A-6
CTYATTACHED 4-9, A-5
CTYPE 4-9, A-5
CTYEND 4-9, A-5
CTYOWNING 4-9, A-5
CTYSTART 4-9, A-5
Defaults 2-4, 3-3, 3-5, A-6
DELETE command 3-8, A-4
Delimiting character 3-4
DEPTH 4-9, A-5
Detailing Text (DETAIL, DTEXT) 2-3, 2-6, 4-4, A-5
DIMENSION 4-9, A-5
EXTRA command 3-6, A-6
FIRESISTANCE 4-10, 4-13, A-5
Fitting (FITT) 2-3, 4-7
Fixed length piping 4-5
VANTAGE PDMS SPECON Reference Manual index-i
Version 11.6SP1
Index
FIXTY 4-10, A-5
Fluid Reference (FLUREF) 4-4, A-4
Generic type (GTYPE) 2-3, 3-4, 4-1, 4-7
Geomset (GMSET) 2-3
GRADE 4-10, 4-13, A-5
Group World (GPWLD) 2-2
Headings 3-3, 3-4, A-5
INERTIA 4-9, A-5
Insulation 4-10, 4-12
ITHICKNESS 4-10, 4-13, A-5
Joint (JOIN) 2-2, 4-7
LIMBOSPEC 3-7, 3-8
LINETYPE 4-5, A-4
Macro input 3-11
Material Reference (MATREF) 4-4, A-4
Material Text (MATXT, MTEXT) 2-3, 2-6, 4-4, A-5
Name (of SPCOM) 3-4, A-5
NEW command 3-1, A-4
Nominal bore sizes - see BORES command
OLD command 3-2, A-4
OUTPUT command 3-9, A-4
PBORE 4-2, 4-3, 4-12, A-5
PCONN 4-2, 4-3, A-5
Piping Component (COMP) 2-3
Piping Section (SECT) 2-2
Pointset (PTSET) 2-3
PRESSURE 4-2, A-5
Profile (PROF) 2-3, 4-7
RADIUS 4-2, A-5
RATING 4-2, 4-5, A-4, A-5
REMOVE command 3-8, A-4
RENAME command 3-9, A-6
SECT - see Piping Section
Selector (SELEC) 2-4, 2-6, 3-4, 3-6, 4-2, 4-8
SHOP 4-2, A-5
SPECIFICATION command 3-2, A-4
Specification Component (SPCOM) 2-4, 2-6, 3-6, 3-7
Specification (SPEC) 2-4, 3-1
Specification World (SPWLD) 2-2, 2-4
Structural Section (STSECT) 2-2
STYPE 4-2, 4-8, A-5
Suffix (to SPREF) 3-4
index-ii VANTAGE PDMS SPECON Reference Manual
Version 11.6SP1
Index
TEMPERATURE 4-2, 4-12, A-5
TEXT command 3-1, A-4
Text answers 3-6
THICKNESS 4-10, A-5
TYPE (of SPCOM) 3-4, A-5
UNITS element 2-2
Userdefined attributes 3-6
WEIGHT 4-9, A-5
WIDTH 4-9, A-5
* (star) character 3-3
+ character 3-3
- character 3-3
= character 3-3
/*LIMBOSPEC - see LIMBOSPEC

VANTAGE PDMS SPECON Reference Manual index-iii
Version 11.6SP1

SPECON Reference Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPECON Reference Manual

Uploaded by

Copyright:

Available Formats

PDMS SPECON

You might also like