Beruflich Dokumente
Kultur Dokumente
Reference Manual
Version 11.5
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 2003 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
Contents
1
1.1 1.2 1.3 1.4
Introducing SPECON...................................................................................1-1
What SPECON is Used For .................................................................................... 1-1 Who This Manual is Meant For.............................................................................. 1-1 How This Manual is Set Out .................................................................................. 1-2 Conventions Used in the Text................................................................................. 1-2
2
2.1 2.2 2.3
3
3.1 3.2 3.3
3.7
4
4.1
4.2
Reference Manual
Version 11.5
4.3
4.2.1 Applicability.................................................................................................... 4-8 4.2.2 Selectors .......................................................................................................... 4-8 4.2.3 Reference Pointers and Settings.................................................................. 4-11 4.2.4 Examples From Structural Component Specifications .............................. 4-12 Selectors and Pointers for Insulation ................................................................... 4-13 4.3.1 Pipework Insulation ..................................................................................... 4-13 4.3.2 Structural Insulation.................................................................................... 4-14
B C
contents-ii
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.
Reference Manual
1-1
Version 11.5
Introducing SPECON
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.
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
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>.
Reference Manual
1-3
Version 11.5
Introducing SPECON
1-4
WORLD
CATA
SPWLD
CCTAB
BLTAB
UNITS
GPWLD
Figure 2-1
Reference Manual
2-1
Version 11.5
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. 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. Connection Compatibility (COCO) Tables hold lists of all compatible types of connection. 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. Dimensional Unit elements define the default units of measurement for geometric information. Group Worlds hold definitions of any groups of elements which may have been created. See the DESIGN Reference Manual for further details.
SPWLD
CCTAB BLTAB
UNITS GPWLD
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.)
CATA
SECT
STSECT
COMP
DTEXT
MTEXT
PROF
JOIN
FITT
DTEXT
MTEXT
Figure 2-2
2-2
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.) Material Text elements hold text which may be used to describe the materials of construction of the components.
MTEXT
Specification World Specification Selectors (one level for each specification `decision')
Specification Component
Figure 2-3
Reference Manual
2-3
Version 11.5
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.
2-4
SPECIFICATION /RF300 MATREF =0 FLUREF =0 RATING 0.000 LINETYPE NUL HEADING NAME TYPE DEFAULTS */20GA VALV */20GL VALV */20RV VALV */25GA VALV */25CH VALV VALV */25GL ... PBOR0 20.0 20.0 20.0 25.0 25.0 25.0
SPEC NAME OVERALL SPEC POINTERS OVERALL SPEC SETTINGS SELEC `QUESTIONS' REFERENCE POINTERS
CATREF
DETAIL
=0 =0 =0 =0 =0 =0
SPCOMS
HEADING NAME TYPE DEFAULTS */25T TEE */25TV TEE */25T1 TEE */32T TEE */32TV TEE */32T1 TEE ... NAME
CMPREF =0 =0 =0 =0 =0 =0
BLTREF =0 =0 =0 =0 =0 =0
HEADING 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 ... TYPE PBOR0 ANGL
Figure 2-4
Reference Manual
2-5
Version 11.5
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:
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.
2-6
(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 PIPE COMPONENT (PSPEC) SPREF
via SELECs
DTEXT
MTEXT
BLTAB
DESIGN DATA
Figure 2-5 EXAMPLE:
SPECIFICATIONS
CATALOGUE
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.
VANTAGE PDMS SPECON
Reference Manual
2-7
Version 11.5
2-8
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)
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.)
Reference Manual
3-1
Version 11.5
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.
3-2
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.
+ -
As an example, consider the following part of a table (which incorporates all four of the characters * - + and = ): HEADING TYPE NAME BLTREF DEFAULTS FLAN */FG /SBOL/20F FLAN */FX ... PBOR0 20.0 + STYP CATREF = S P DETAIL MATXT CMPREF
/FSAAPAPP +
/20FL +
/ASA-20F /ASA-20FX
=0 =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
Reference Manual
3-3
Version 11.5
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
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 CMPREF BLTREF DEFAULTS STYP GATE SHOP = CATREF DETAIL MATXT
Reference Manual
3-5
Version 11.5
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-6
(where :colour is a uda of type text) (where :diagonal is a uda of type real)
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.
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.
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.
Reference Manual
3-7
Version 11.5
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: 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 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
3-8
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.
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.
Reference Manual
3-9
Version 11.5
3.6.2
To output one or more complete SPECs, use the command syntax 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
3.6.3
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
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.
3-10
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
3.6.5
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
3.7
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).
Reference Manual
3-11
Version 11.5
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.
3-12
Reference Manual
3-13
Version 11.5
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
4.1.1
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
Reference Manual
4-1
Version 11.5
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.
4-2
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.
Reference Manual
4-3
Version 11.5
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 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). Overall Specification Pointers
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
4-4
properties of the liquids or gases for use with which the piping components are suitable (see the PROPCON Reference Manual).
Reference Manual
4-5
Version 11.5
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. LINETYPE - Fixed Length Piping Line Type: May be set to either of the identifiers FP FX
Fixed Pipe 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-6
STYP PE PE PE
CMPREF =0 =0
BLTREF =0 =0
CATREF DETAIL
MATXT
CMPREF
=0 =0 =0 =0 =0
=0 =0 =0 =0 =0
CMPREF =0 =0
BLTREF =0 =0
PBOR1 PBOR2 25.0 25.0 32.0 32.0 20.0 20.0 25.0 25.0
STYPE SHOP CONC CONC ECC CONC ECC = TRUE TRUE TRUE TRUE
CATREF
DETAIL
MATXT CMPREF
=0 =0 =0 =0
=0 =0 =0 =0
Reference Manual
4-7
Version 11.5
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:
4-8
STYPE C CHS CRSJ CUB CUC CZB EAI EAM HD HE HL/HX HP IPE IPN LST M/W RHS RSJ S T TUB TUC U UB UBP UC UEAI UEAM UPN PLAT
Meaning Channel section or American standard Cshapes (tapered flanges) Circular hollow section Castellated rolled steel joists Castellated universal beams Castellated universal columns Castellated Zbeams Imperial equal angles Metric equal angles European columns (wide flanges) European beams (wide flanges) European beams (very wide flanges) Bearing piles (wide flanges) European beams (parallel faced flanges) European standard beams (tapered flanges) Long stalk teebars American Ishapes (wide flanges) Rectangular hollow section Rolled steel joists American standard Ishapes (tapered flanges) Tee bars Tees cut from universal beams Tees cut from universal columns European small channels Universal beams Universal bearing piles Universal columns Imperial unequal angles Metric unequal angles European standard channels Plate girders
Reference Manual
4-9
Version 11.5
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 DIME2 Depth or long leg Width or short leg
CTYPE integer A connection type. The qualifying integer is optional; suggested conventions are:
CTYPE1 CTYPE2 CTYPE3 CTYPE4 Start connection End connection Attached connection Owning connection
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:
4-10
Inertia about x-x Inertia about y-y Inertia about u-u Inertia about v-v
THICkness integer Plate thickness within a section; e.g. 10 mm. The qualifying integer is optional; suggested conventions are:
THIC1 THIC2 Web thickness 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.
Reference Manual
4-11
Version 11.5
STYP UB + +
GRADE 43 50 43
STYP UEAM + +
GRADE 43 50 43
HEADING TYPE NAME STYP PROF */BS.C1 C + */BS.C2 + ... PROF */BS.CRSJ1 CRSJ /305X102X25KG.CRSJ + */BS.CRSJ2 + /267X102X21KG.CRSJ
WEIGHT INER1 INER2 CATREF 65.5 21399.0 628.6 /432X102X65KG.C 55.1 14894.0 579.8 /381X102X55KG.C 25.3 21.5 5372.0 3562.0 162.5 139.1
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.
4-12
VANTAGE PDMS SPECON
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@2 using inch bores or 25,70 using metric bores)
These might be related to the available thicknesses in the following way:
Temperature Range 101 101 201 201 0 200 200 400 400 100 Bore Range 1 3 1 3 1 2 /2 8 21/2 8 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 INSU */IN1 0,100 INSU */IN2 101,200 INSU */IN3 101,200 INSU */IN4 201,400 INSU */IN5 201,400
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.
Reference Manual
4-13
Version 11.5
4-14
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
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 selfexplanatory. 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.
Reference Manual
A-1
Version 11.5
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
A.3
Command Arguments
These are inputs which are necessary to qualify command words. They are distinguished by appearing in italics. Name name refno integer value word text sign equals comma nl Definition PDMS element name PDMS reference number a positive integer signed number alphabetic word alphanumeric string plus or minus character equals character comma character new line Example /ABCDE =23/1403 0, 3 3.142, -23.66, -34 NULL, VALV (4 chars. max.) Enclose Between Apostrophes + (for ditto); - (in default lines) = (in default lines) 20, 40 (for range of values) Press the RETURN key
Table A-1
Reference Manual
A-3
Version 11.5
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
A.4.2 <table>
.--------<--------. / | >--- <heading> ---*--- <default> -----| | | |--- <linesp> ------ | --->
Reference Manual
A-5
Version 11.5
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-6
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> ---------------------------------- | --->
Reference Manual
A-7
Version 11.5
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 -----| | | --------------+--->
A-8
Reference Manual
A-9
Version 11.5
Error Messages
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. Cannot access SPECIFICATION Check that you have entered the identifier for the SPEC correctly. 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.13.3). 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. 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. 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. 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). 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.
(17:3) (17:4)
(17:5)
(17:6)
(17:7)
(17:9)
(17:10)
Reference Manual
B-1
Version 11.5
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). 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). 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. Too many headings for output You cannot output more than 20 headings in a table. 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. More defaults than questions - extra defaults ignored You have more entries in the defaults line than you have corresponding entries in the heading line. More than 20 HEADINGS The maximum number of entries permitted in a heading line is 20. DETAIL already used in heading You have specified two DETAIL pointers in a heading line. The line will be ignored. 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. 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.) 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.
(17:12)
(17:13)
(17:14) (17:15)
(17:16)
(17:17) (17:18)
(17:19)
(17:20)
(17:22)
B-2
Error Messages
(17:23)
SPCOM does not exist Check that you have entered the SPCOM identifier correctly when modifying an existing Specification. SPEC does not exist Check that you have entered the SPEC identifier correctly. 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. 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). Unable to create TEXT element You can only specify one string of descriptive text for each SPEC. Unable to put CATREF You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. Undefined name Check that you have entered the required identifier correctly. 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. 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. 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). No databases to work from You have not specified a suitable MDB before trying to enter SPECON. No SPEC database The specified MDB does not contain an appropriate CATALOGUE DB in which SPECON can create SPECs.
(17:24) (17:26)
(17:28)
(17:29) (17:30)
(17:33) (17:34)
(17:35)
(17:36)
(17:38) (17:39)
Reference Manual
B-3
Version 11.5
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). Unable to put CMPREF You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. Unable to put DETAIL You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. Unable to put MATXT You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. Unable to put BLTREF You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. 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). 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.) 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.) MATXT already used in heading You have specified two MATXT pointers in a heading line. The second entry will be ignored, but should preferably be deleted. CMPREF already used in heading You have specified two CMPREF pointers in a heading line. The second entry will be ignored, but should preferably be deleted. BLTREF already used in heading You have specified two BLTREF pointers in a heading line. The second entry will be ignored, but should preferably be deleted.
(17:41)
(17:42)
(17:43)
(17:44)
(17:45)
(17:46)
(17:47)
(17:48)
(17:49)
(17:50)
B-4
Error Messages
(17:51)
SPCON NAME name already exists You must use a unique name for each SPCON. The new SPCON will be rejected.
word is not valid as a GTYPE See Sections 4.1.1 and 4.2.1for examples of valid GTYPEs.
(17:52) (17:53)
TMPR already used in heading You have specified two TMPR pointers in a heading line. The second entry will be ignored, but should preferably be deleted. Unable to put TMPR You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly.
(17:54)
Reference Manual
B-5
Version 11.5
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 (mm) 6.0 8.0 10.0 15.0 20.0 25.0 32.0 40.0 50.0 65.0 80.0 0.0 100.0 125.0 150.0 200.0 250.0 300.0 350.0 400.0 450.0 500.0 550.0 600.0 650.0 700.0 750.0 800.0 850.0 Imperial Units Metric Units (inches) (mm) (inches) 0.125 0.250 0.375 0.500 0.750 1.00 1.25 1.50 2.00 2.50 3.00 3.50 4.00 5.00 6.00 8.00 10.0 12.0 14.0 16.0 18.0 20.0 22.0 24.0 26.0 28.0 30.0 32.0 34.0 900.0 950.0 1000.0 1050.0 1100.0 1150.0 1200.0 1250.0 1300.0 1350.0 1400.0 1450.0 1500.0 1600.0 1650.0 1750.0 1800.0 1850.0 1900.0 1950.0 2000.0 2050.0 2100.0 2200.0 2400.0 2600.0 2800.0 3000.0 3200.0 3400.0 3600.0 3800.0 4000.0 Imperial Units 36.0 38.0 40.0 42.0 44.0
46.0 48.0 50.0 52.0 54.0 56.0 58.0 60.0 64.0 66.0 68.0 72.0 74.0 76.0 78.0 80.0 82.0 84.0 88.0 96.0 104.0 152.0 120.0 128.0 136.0 136.0 136.0 136.0
Reference Manual
C-1
Version 11.5
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 FIXTY 4-10, A-5 Fluid Reference (FLUREF) 4-4, A-4
Reference Manual
index-1
Version 11.5
Index
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 TEMPERATURE 4-2, 4-12, A-5 TEXT command 3-1, A-4 Text answers 3-6
Reference Manual Version 11.5
index-2
Index
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
Reference Manual
index-3
Version 11.5