Pdms Specon: Reference Manual
Pdms Specon: Reference Manual
Reference Manual
Version 11.5
pdms1151/man33/doc2
issue 140403
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.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
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.
• 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.
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
• 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>.
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 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
SECT STSECT
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.
SPEC Specification
SELEC Selectors
6
6 (one level for each
6 specification `decision')
SELEC
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.
(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.
COMP
SPEC
PIPE COMPONENT
COMPONENT via (SPCOM)
(PSPEC) SELECs DTEXT
CATREF
DETAIL
SPREF
MATXT MTEXT
BLTREF
CMPREF
BLTAB
CMPT
(PROPS DB)
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.
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)
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.
+ 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
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.
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 =
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.
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.
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
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.
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.
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
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
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.
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.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
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:
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.
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).
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).
properties of the liquids or gases for use with which the piping components are
suitable (see the PROPCON Reference Manual).
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
determine those points in a composite pipeline at which the pressure rating changes.
The default setting is zero.
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).
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:
STYPE Meaning
C Channel section or American standard C–shapes (tapered flanges)
CHS Circular hollow section
CRSJ Castellated rolled steel joists
CUB Castellated universal beams
CUC Castellated universal columns
CZB Castellated Z–beams
EAI Imperial equal angles
EAM Metric equal angles
HD European columns (wide flanges)
HE European beams (wide flanges)
HL/HX European beams (very wide flanges)
HP Bearing piles (wide flanges)
IPE European beams (parallel faced flanges)
IPN European standard beams (tapered flanges)
LST Long stalk tee–bars
M/W American I–shapes (wide flanges)
RHS Rectangular hollow section
RSJ Rolled steel joists
S American standard I–shapes (tapered flanges)
T Tee bars
TUB Tees cut from universal beams
TUC Tees cut from universal columns
U European small channels
UB Universal beams
UBP Universal bearing piles
UC Universal columns
UEAI Imperial unequal angles
UEAM Metric unequal angles
UPN European standard channels
PLAT Plate girders
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:
CTYPE integer
A connection type. The qualifying integer is optional; suggested conventions are:
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:
THICkness integer
Plate thickness within a section; e.g. 10 mm. The qualifying integer is optional;
suggested conventions are:
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.
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.
The information given in this section applies specifically to the generic type INSulation.
PBOR0:
The nominal diameter of the component; usually specified as a range of bore sizes
(e.g 1,2¹@2 using inch bores or 25,70 using metric bores)
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
• Syntax diagrams are generally read from top left to bottom right.
• Points marked with a plus sign (+) are option junctions which allow you to
input any one of the commands to the right of the junction. Thus
>--+-- 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.
These are inputs which are necessary to qualify command words. They are distinguished
by appearing in italics.
The diagrams are listed approximately in the order in which they are described in this
manual.
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 ---+-----------------------------+--->
A.4.2 <table>
.--------<--------.
/ |
>--- <heading> ---*--- <default> -----|
| |
|--- <linesp> ------’
|
‘--->
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 --|
| | |
‘----> ‘-----------’
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> ----------------------------------’
|
‘--->
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 -----|
| |
‘--------------+--->
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>
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.
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 136.0
4000.0 136.0