• No results found

Selectors and Pointers for Piping Components

13 Typical Specifications

13.1 Selectors and Pointers for Piping Components

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

12.0 13:2

(For Insulation, see Pipework Insulation)

13.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 P-Point Zero: A Special Case 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 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

INSTrument WELD

LJSE

ATTAchment

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.

13.1.3 P-Point Zero: A Special Case

Normally, when the bore or connection type of a p-point is used as a SELEC question, the answer provided will apply to a specific p-point number. For example, PBORE1 will be the component’s arrive bore, PBORE2 will be its in-line leave bore, and so on. However, under some circumstances this need not apply. In such cases you may use the Selectors PBORE0 and/or PCONN0 to represent either the arrive or leave p-point of the component.

For example, assume that you wish to select a flange. Normally P1 would represent p-arrive and P2 would represent p-leave, so that the Selector PBORE1 could be matched against the p-leave bore of the preceding component to select a suitable flange. If, however, the flange is reversed (‘flipped’), P2 becomes the p-arrive and so a Specification based on the Selector PBORE1 will not allocate a correct match.

If the SELEC is defined as PBORE0, all p-points of the new component will be tested, in numeric order, against the p-leave of the preceding component. Thus, in the case of our flipped flange, if a P1 match cannot be found then P2 will be tested as a second choice. If either P1 or P2 matches the answer given for PBORE0, then a flange will be selected.

The same principle applies to the connector type PCONN0.

You will find the P-point Zero convention very useful when compiling Specifications. Figure 11:3.: Part of a typical Specification for piping components, for example, illustrates the use of PBORE0 (abbreviated to PBOR0) for four component types.

13.1.4 Reference Pointers and Settings

The following reference pointers and settings are applicable to the specification of piping components (see the examples below).

Individual Specification Component Pointers

These pointers, which are attributes of SPCOM elements, are set individually for each line in a Specification table. Only the CATREF pointer is obligatory; the other pointers may be omitted from the heading when the Specification is created or they may be left as unset (=0) in individual SPCOM lines.

CATREF - Catalogue Reference:

Points to one particular component in the Catalogue DB which meets all the SELEC requirements specified for an individual SPCOM. A CATREF heading is obligatory for every SPEC table since it is the essential link between the design specification and the choice of a component from the Catalogue. It is important that the component pointed to by the CATREF already exists when the SPCOM is defined, otherwise you will receive the error message ‘Undefined Name’ and the CATREF in the Specification will be shown as =0 (i.e.

unset).

12.0 13:4

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 Catalogue Database Structure).

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 Component Parts and the ISODRAFT Reference Manual).

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 Properties Constructor).

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 Properties Constructor).

FLUREF - Fluid Reference:

Points to a FLUID element in the Properties DB. This holds information about the properties of the liquids or gases for use with which the piping components are suitable (see Properties Constructor).

Overall Specification Settings

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

RATING - Pipeline Pressure Rating:

May be set to the maximum pressure at which the components covered by the Specification are intended for service. ISODRAFT can then use this setting to determine those points in a composite pipeline at which the pressure rating changes.

The default setting is zero.

LINETYPE - Fixed Length Piping Line Type:

May be set to either of the identifiers

FP - Fixed Pipe FX - Fixed Length

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

13.1.5 Examples From Piping Component Specifications

To keep the examples brief, very few lines (SPCOMs) are shown for each GTYPE.

NEW SPECIFICATION /RF300

(See Figure 11:3.: Part of a typical Specification for piping components for some other examples.)

12.0 13:6