Pdms Design

pdms1131/man30/doc2Issue 181200

PDMSDESIGN

Reference ManualPart 2: Creating the Model

Version 11.3

Cadcentre Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK

PLEASE NOTE:Cadcentre has a policy of continuing product development: therefore, the information contained in thisdocument may be subject to change without notice.

CADCENTRE MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENT,INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE.

While every effort has been made to verify the accuracy of this document, Cadcentre shall not beliable for errors contained herein or direct, indirect, special, incidental or consequential damages inconnection with the furnishing, performance or use of this material.

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

Copyright 1990 through 2001 Cadcentre Limited

All rights reserved. No part of this document may be reproduced, stored in a retrieval system ortransmitted, in any form or by any means, electronic, mechanical, photocopying, recording orotherwise, without prior written permission of Cadcentre.

The software programs described in this document are confidential information and proprietaryproducts of Cadcentre Ltd or its licensors.

For details of Cadcentre's worldwide sales and support offices, see our website athttp://www.cadcentre.com/location

http://www.cadcentre.com/location

PDMS DESIGN Reference Manual Contents-iPart 2: Creating the ModelVersion 11.3

Contents

1 Introduction ...................................................................................................1-11.1 About the DESIGN Reference Manual.............................................................1-11.2 Organisation of the DESIGN Reference Manual .............................................1-11.3 Organisation of this Manual.............................................................................1-2

2 Equipment and Primitives ............................................................................2-12.1 The Primitive Modelling Attributes .................................................................2-1

2.1.1 Sizing Primitive Building Blocks ..................................................................2-22.1.2 Choosing Nozzle Size, Rating and Height ....................................................2-32.1.3 Modelling Detail Levels.................................................................................2-32.1.4 Obstruction Settings .....................................................................................2-4

2.2 Positioning at a Known Point ...........................................................................2-62.2.1 Positioning at a Coordinate...........................................................................2-62.2.2 Polar Positioning from the Origin.................................................................2-82.2.3 General Polar Positioning from the Origin...................................................2-9

2.3 Orientation and Connection............................................................................2-102.3.1 Design Element Orientation .......................................................................2-112.3.2 Design Element Reorientation....................................................................2-122.3.3 Primitive Element Connection....................................................................2-14

2.4 Moving by a Known Distance .........................................................................2-162.4.1 Moving Along Axes ......................................................................................2-162.4.2 Moving in any Direction..............................................................................2-172.4.3 Moving in any Direction: Distance Given in Different Plane ....................2-19

2.5 Moving Through Defined Intersection Planes................................................2-192.5.1 Moving Through an Intersection ................................................................2-202.5.2 Moving Either Side of an Intersection........................................................2-222.5.3 General Moving to an Intersection .............................................................2-24

2.6 Moving In Front of or Behind Items...............................................................2-272.6.1 Moving Either Side of a Fixed Object .........................................................2-272.6.2 Moving On Top of or Under a Fixed Object ................................................2-302.6.3 Moving an Item Using Reference Points ....................................................2-33

2.7 Moving to a Specified Clearance between Items............................................2-352.7.1 Moving to a Clearance Either Side .............................................................2-352.7.2 Moving an Object to Clear Another Object.................................................2-382.7.3 Moving to a Vertical Clearance...................................................................2-402.7.4 General Moving to a Clearance...................................................................2-43

2.8 Reflecting a Position in a Plane (Mirroring)...................................................2-44

3 Piping, Ducting and Cable Trays .................................................................3-13.1 Defining a Branch .............................................................................................3-13.2 Branch and Hanger Specifications ...................................................................3-23.3 Connecting the Head or Tail .............................................................................3-3

3.3.1 The Head or Tail Connection Reference Attribute.......................................3-5

Contents

Contents-ii PDMS DESIGN Reference Manual Part 2: Creating the Model

Version 11.3

3.3.2 Positioning Head or Tail in Free Space ........................................................3-63.3.3 Head or Tail Positioning Using End Components........................................3-73.3.4 Head and Tail Positioning by Bottom or Top of Pipe ...................................3-93.3.5 Moving the Head or Tail .............................................................................3-113.3.6 Reconnecting Pipes after an Equipment Move...........................................3-13

3.4 Selecting Component and Tube Details from Specifications .........................3-133.4.1 Choosing Components from a Displayed List.............................................3-143.4.2 Selecting Components from Specifications.................................................3-193.4.3 Selecting the Default Specification Component .........................................3-203.4.4 Selecting from Several Alternatives ...........................................................3-203.4.5 Selecting ‘Out-of-Specification’ Components ..............................................3-223.4.6 Selecting Components and Tube Separately ..............................................3-233.4.7 Direct Selection by Shortcode .....................................................................3-24

3.5 Re-selection of Existing Components and Tube .............................................3-263.5.1 Re-selecting the New Default Component..................................................3-263.5.2 General Reselection of Components and Tube ...........................................3-27

3.6 Standard Component Attributes ....................................................................3-283.6.1 Position and Orientation Attributes ...........................................................3-303.6.2 Component Arrive and Leave Attributes....................................................3-313.6.3 Swapping the Arrive and Leave P-points ...................................................3-313.6.4 The Component Specification Reference Attribute ....................................3-333.6.5 Variable Length Tube (and Rod) Attributes...............................................3-333.6.6 Insulation Specification Attribute ..............................................................3-353.6.7 Trace Heating Specification Attribute........................................................3-353.6.8 The Fabrication Flags .................................................................................3-363.6.9 Position and Orientation Status Flags .......................................................3-373.6.10Variable Component Attributes..................................................................3-383.6.11Offline/Straight-Through Component Attribute ........................................3-393.6.12Multi-Way Component Attributes ..............................................................3-39

3.7 Orientation and Connection of Components ..................................................3-403.7.1 Component Orientation...............................................................................3-413.7.2 Direction-Changing Components................................................................3-433.7.3 Component Connection ...............................................................................3-453.7.4 Forced Component Connection ...................................................................3-46

3.8 Moving by a Known Distance .........................................................................3-473.8.1 Moving Components ....................................................................................3-473.8.2 General Moving of Components ..................................................................3-48

3.9 Positioning Components using Reference Planes ..........................................3-493.9.1 Positioning with respect to the Previous Component ................................3-493.9.2 Positioning the Component through an Intersection .................................3-513.9.3 Positioning with respect to an Intersection................................................3-533.9.4 General Positioning through an Intersection .............................................3-57

3.10 Positioning Components ‘Point-to-Surface’ ....................................................3-583.10.1Positioning Components either side of an Object.......................................3-593.10.2Positioning Components On Top of or Under an Object ............................3-623.10.3General Component Positioning Using Planes...........................................3-64

3.11 Component Clearance Positioning..................................................................3-663.11.1Clearance from the Previous Component ...................................................3-663.11.2Component Clearance Either Side..............................................................3-683.11.3Component Clearance Vertically ................................................................3-70

Contents

PDMS DESIGN Reference Manual Contents-iiiPart 2: Creating the ModelVersion 11.3

3.11.4Tube (Bottom of Pipe) Clearance ................................................................3-723.11.5General Clearance of Components and Tube .............................................3-74

3.12 Dragging Equipment and Piping Networks ...................................................3-773.12.1Dragging Equipment and Nozzles ..............................................................3-783.12.2Dragging Piping...........................................................................................3-82

4 Automatic Pipe Routing................................................................................4-14.1 Accessing the Automatic Pipe Routing Facilities.............................................4-1

4.1.1 Entering and Leaving Autoroute Mode ........................................................4-14.2 Pipe Routing ......................................................................................................4-2

4.2.1 Routing Pipes along Preferred Axes .............................................................4-24.2.2 Setting Routing Planes..................................................................................4-34.2.3 Setting Penalty Volumes...............................................................................4-34.2.4 Invoking the Automatic Routing Process .....................................................4-44.2.5 Setting the Nozzle Offset Factor...................................................................4-5

4.3 Refining the Automatic Pipe Routes.................................................................4-54.3.1 Defining the Rack to be Used........................................................................4-64.3.2 Defining the Direction of Spread ..................................................................4-64.3.3 Defining the Base Direction..........................................................................4-74.3.4 Spreading Pipes about the Rack ...................................................................4-74.3.5 Setting the Bottom-of-Pipe Position .............................................................4-84.3.6 Combined Spreading and BOP Operations ..................................................4-8

5 Structural Design Using Catalogue Components ......................................5-15.1 Creating and Positioning Primary Nodes.........................................................5-25.2 Creating and Connecting Sections Automatically............................................5-35.3 Section Attributes .............................................................................................5-4

5.3.1 Cross-Sectional Profile via a Specification Reference ..................................5-45.3.2 Generic Type..................................................................................................5-55.3.3 Start and End Positions ................................................................................5-55.3.4 Start and End Plane Directions....................................................................5-65.3.5 Orientation Angle..........................................................................................5-75.3.6 Joint Start and End References ....................................................................5-85.3.7 Start and End Connection Types ..................................................................5-85.3.8 Start and End Releases.................................................................................5-9

5.4 Creating and Positioning Secondary Nodes ...................................................5-115.5 Creating and Positioning Joints .....................................................................5-12

5.5.1 Creating Primary Joints .............................................................................5-125.5.2 Creating Secondary Joints ..........................................................................5-135.5.3 Setting Joint Geometry via a Specification Reference ...............................5-135.5.4 Positioning and Orientating Primary Joints ..............................................5-145.5.5 Positioning and Orientating Secondary Joints...........................................5-15

5.6 Attributes of Connected Joints .......................................................................5-175.6.1 Connection Reference ..................................................................................5-175.6.2 Cutting Plane...............................................................................................5-185.6.3 Cutback Allowance ......................................................................................5-18

5.7 Manually Connecting Sections........................................................................5-195.7.1 Connecting Sections ....................................................................................5-195.7.2 Disconnecting Sections................................................................................5-215.7.3 Reconnecting Sections .................................................................................5-21

Contents

Contents-iv PDMS DESIGN Reference Manual Part 2: Creating the Model

Version 11.3

5.8 Repositioning Steelwork Elements.................................................................5-225.8.1 Reversing Section Start and End Positions (‘Flipping’) .............................5-225.8.2 Moving Steelwork Elements .......................................................................5-245.8.3 Modifying Lengths of Sections ....................................................................5-255.8.4 Reorientating Steelwork Elements.............................................................5-26

5.9 Positioning and Orientating Using P-lines ....................................................5-295.9.1 Identifying P-lines .......................................................................................5-305.9.2 Positioning by Using P-lines .......................................................................5-305.9.3 Orientating by Using P-lines ......................................................................5-32

5.10 Creating and Connecting Panels ....................................................................5-345.10.1Creating a Panel..........................................................................................5-345.10.2Splitting a Panel..........................................................................................5-345.10.3Connecting Panels using Linear Joints ......................................................5-35

5.11 Fittings, Hangers and Equipment Load Points .............................................5-385.11.1Fittings and Panel Fittings .........................................................................5-385.11.2Structure-to-Pipework Connections............................................................5-395.11.3Structure-to-Equipment Connections.........................................................5-39

5.12 Design, Owning and Attached Parameters ....................................................5-405.12.1Setting Design Parameters .........................................................................5-405.12.2Setting Owning and Attached Parameters.................................................5-41

5.13 Representing Curved Beams and Walls .........................................................5-435.13.1Overview ......................................................................................................5-435.13.2Defining a Generic Section..........................................................................5-445.13.3More About Curve Types.............................................................................5-455.13.4How P-lines Are Used For Generic Sections ..............................................5-465.13.5Positioning Items Relative to Generic Sections..........................................5-485.13.6Generic Fixings Representing Joints and Fittings.....................................5-49

5.14 Representing Building Components ...............................................................5-505.14.1Using Element Soft Types...........................................................................5-505.14.2Controlling Edge Representation in DRAFT..............................................5-51

6 Design Templates .........................................................................................6-16.1 The Concepts .....................................................................................................6-16.2 The Design Template Hierarchy.......................................................................6-26.3 Parameterisation using Design Datasets.........................................................6-36.4 Assigning Local Names to Template Elements................................................6-4

6.4.1 Setting Local Names .....................................................................................6-56.4.2 Using Local Names in Expressions...............................................................6-5

6.5 Setting Priorities for Evaluating Rules ............................................................6-66.6 Adding Design Points to Template Elements...................................................6-76.7 Using a Design Template Item in a Design......................................................6-96.8 Portsets and Linksets .......................................................................................6-9

7 Groups ...........................................................................................................7-17.1 Defining Group Contents ..................................................................................7-17.2 Accessing Groups ..............................................................................................7-27.3 Deleting Groups ................................................................................................7-37.4 Copying a Group................................................................................................7-3

Index

PDMS DESIGN Reference Manual 1-1Part 2: Creating the ModelVersion 11.3

1 Introduction

1.1 About the DESIGN Reference Manual

The PDMS DESIGN Reference Manual describes all the DESIGN commandsin detail. It also describes how the Design database is structured, the Designdatabase elements and their attributes.

DESIGN is normally used interactively. The Graphical User Interface (GUI)provides discipline-based applications which help you to create, check andreport on the model. How to use the applications is described in user guidesand on-line help.

This manual is written for experienced users of PDMS DESIGN who need touse commands, for example, to write batch macros or to customise the GUI. Ifyou are going to customise the GUI, you will also need to refer to the CadcentreSoftware Customisation Guide and Cadcentre Software CustomisationReference Manual for information about PML, the Cadcentre programminglanguage.

1.2 Organisation of the DESIGN Reference Manual

The DESIGN Reference Manual has four parts:

• Part 1, General Commands, describes general DESIGN commands, whichare used, for example, for setting up the display, and querying andnavigating around the Design database. It also describes how to use thecommand syntax graphs, which are used to show all the options availablefor each command.

• Part 2, (this volume), describes the commands for creating databaseelements and setting their attributes.

• Part 3, Elements and Attributes, contains details of all the elementswhich can be created in the Design database, their position in thedatabase hierarchy and their attributes.

• Part 4, Utilities, describes the DESIGN Utilities for data consistencychecking and clash detection, and for exporting DESIGN data toprograms such as REVIEW.

Introduction

PDMS DESIGN Reference ManualPart 2: Creating the Model

Version 11.3

1-2

1.3 Organisation of this Manual

You should refer to Part 1 of the DESIGN Reference Manual for generalinformation about creating elements and setting the standard attributes whichall Design elements have.

This manual, Part 2, is divided into the following chapters:

• Chapter 2 describes the commands for modelling Equipment and Civils,including positioning, orientating and connecting commands applicable tothese elements.

• Chapter 3 describes the commands for modelling Piping, Ducting andCable Trays, including selecting Components from the Catalogue, andpositioning, orientating and connecting commands applicable to theseelements.

• Chapter 4 describes the commands for Automatic Pipe Routing. Userswho require these facilites should enquire about Cadcentre’s AdvancedRouter product. (See the addresses at the end of this manual.)

• Chapter 5 describes Structural Design Using Catalogue Components,including positioning, orientating and connecting commands applicable tostructural elements. Its main focus is on structural steelwork design,with extensions of the concepts to include their use for representing wallsand floors in more general building design.

• Chapter 6 describes DESIGN Templates, which are groups of elementswhich can be defined and stored as a single parameterised element, andthen inserted into a model.

• Chapter 7 describes Groups, which have now been largely replaced byLists and Collections, defined using expressions.

For a comprehensive list of all PDMS attributes and pseudo-attributes, see theCadcentre Software Customisation Reference Manual.


2 Equipment and Primitives

This chapter describes the modelling and layout of process equipment and civilitems. These include items such as pumps, vessels, walls and heat exchangers,which are modelled within the major hierarchical elements Equipment,Structure, Ptrack and Substructure. These elements own primitive geometricshapes and holes which are dimensioned and assembled to form a suitablemodel. The items can then be positioned and orientated as a whole by usingone of the comprehensive positioning commands - Design items can either bepositioned at a known co-ordinate, or moved by a given distance or clearance.The same commands can be used to modify existing positions, orientations anddimensions. There are also a number of special plant modification facilitiesthat are described in a later part of the manual.

2.1 The Primitive Modelling Attributes

The plant design hierarchy is a ‘skeleton’ structure of the elements whichrepresent the chosen organisation of the plant model. The physicalappearance and layout of the process items are determined by the value ofeach element’s attributes; for example, a Box only looks like a box if its XLEN,YLEN and ZLEN attributes are set (on creation they are zero).

This section describes those physical primitive element attributes that give ashape to the model. Generally, these attributes will either be set by typing intheir values directly or from macros. It is important, however, to recognise thatregardless of how it was input, the basic attribute information is the storedphysical description of the designed plant.

Equipment and Primitives


Version 11.3

2-2

2.1.1 Sizing Primitive Building Blocks

Keywords: XLENGTH YLENGTH ZLENGTH DIAMETERHEIGHT RADIUSXOFF YOFF XTOP YTOP XBOTTOM YBOTTOMDTOP DBOTTOM RINSIDE ROUTSIDEXTSHEAR YTSHEAR XBSHEAR YBSHEAR

Description: The physical shapes of equipment, structural and civil items in theplant are built up by creating, dimensioning and assembling basicgeometric elements. These commands directly set the attributes ofbasic modelling primitives which give them their precise dimensions.The following primitive shapes are available:

Box Cone DishCylinder Slope-bottomed Cylinder SnoutCircular Torus Rectangular Torus Pyramid

Holes may be plunged through ‘solid’ primitives using a correspondingset of negative primitives. The examples given in this subsection referto the Box and Cylinder; a complete description of all primitiveelements and their attributes can be found in Part 3 of the PDMSDESIGN Reference Manual..

Examples:

XLEN 1000 (At a Box)The xlength dimension of the box becomes 1000

DIA 3 FT (At a Cylinder)The diameter of the cylinder becomes 3 feet

Command Syntax:

Refer to Part 3 of the DESIGN Reference Manual.

DIAMETER

HEIGHT

Figure 2-1 Dimensioning a CYLINDER primitive


PDMS DESIGN Reference ManualPart 2: Creating the ModelVersion 11.2

2-3

2.1.2 Choosing Nozzle Size, Rating and Height

Keywords: CATREF HEIGHTDescription: The Nozzle is the only basic equipment primitive that obtains some of

its physical dimensions directly from the PDMS Catalogue. The sizeand rating are determined by setting the CATREF (CatalogueReference) attribute which refers to an element in the Catalogue. TheNozzle height, however, is determined on site by setting thecorresponding Height attribute. If the CATREF attribute is not set,the ‘Nozzle’ is merely a hierarchical element with no geometry.

Examples:

CATR /NFAARPMM (At Nozzle)The size and rating of the Nozzle are set by naming the appropriateCatalogue choice.

HEI 2’6 (At Nozzle)The Height of the Nozzle becomes 2’6.

Command Syntax:

>-- CATref name -->

>-- HEIght <uval> -->

2.1.3 Modelling Detail Levels

Keywords: LEVELDescription: This command sets the attribute, common to all primitive elements,

that controls modelling detail. The command specifies a range ofmodelling ‘levels’ which determine the permanent visibilitycharacteristics of the element in DESIGN. The attribute allows plantitems to be assembled from overlaid primitives representing varyinglevels of detail. In this way, several graphical versions of the sameobject can be available for different purposes. For example, it may bedecided to represent an I-section beam as a single box for simplespace-modelling in DESIGN, while using its full cross-section for 2Ddrawing data in DRAFT.

The LEVEL attribute is specified as two numbers, representing theinclusive range in which that item will be drawn. In DESIGN, onlyprimitives of visible items whose LEVEL range includes the LEVELsetting specified by the REPRESENTATION command will be drawn(see Chapter 5 in Part 1 of this manual).



Version 11.3

2-4

LEVEL ranges for Nozzles and piping are specified in the Catalogue. Acompany will usually establish rigid standards for the use of LEVELswhich are defined permanently in the Catalogue and therefore mustbe complied with during Equipment and Civils modelling.

Examples:

LEVEL 6 10The current primitive will be drawn if the operative drawing LEVEL iswithin the specified range.

Command Syntax:

>-- LEVel integer integer -->

Figure 2-2 Some modelling detail levels for an I-section beam

2.1.4 Obstruction Settings

Keywords: OBSTRUCTIONDescription: The OBSTRUCTION attribute indicates to the clash detection facility

whether a primitive should be considered as a ‘Hard’ or ‘Soft’obstruction, or not at all. Obstructions can be specified as HARD,SOFT or NONE, or alternatively they can be specified numerically asfollows:

For ordinary primitives, the following rules apply:

• No obstruction (internal graphical details)

• Soft obstruction (access volumes etc.)

• Hard obstruction (vessel ‘envelopes’ etc.).



2-5

Holes (i.e. negative primitives) also have the OBSTRUCTIONattribute. OBSTRUCTION settings for Nozzles and Piping are given inthe Catalogue.

Note: See also Chapter 5 in Part 1 of the DESIGN Reference Manual fordetails of the Spatial Map which is used during clash-checking.

Examples:

OBST SOFT (At a primitive)Current Element will be considered as a ‘soft’ obstruction.

OBST HARD (At a primitive)Current Element will be considered as a ‘hard’ obstruction.

OBST NONE (At a primitive)Current Element will be ignored during clash detection.

OBST 2 (At a primitive)Current Element will be considered as a ‘hard’ obstruction.

Command Syntax:

>-- OBStruction --+-- integer --.| ||-- HARD -----|| ||-- SOFT -----|| |‘-- NONE -----+-->

Figure 2-3 Obstruction settings for use in clash detection



Version 11.3

2-6

2.2 Positioning at a Known Point

These commands allow you to place the Current Element at a known positionin space. You can:

• Specify explicit coordinates

• Specify the position of an existing p-point

• Cusor pick with a working grid (WGRID) position

The position of the Current Element is normally defined as that of its origin.However options exist to allow any p-point belonging to the item to be used asthe positioning reference.

2.2.1 Positioning at a Coordinate

Keywords: POSITION ATDescription: This command positions the Current Element directly by giving the

3D coordinates, the name of another element or p-point position, orvisually by using the cursor.

Examples:

AT E3’ N4’6 U1’Current Element will be placed at the specified owner coordinate position(see Figure 2-4).

AT IDP@Current Element will be placed at the p-point picked by the cursor.

AT@ The Current Element will be placed at the toleranced working gridposition indicated by the cursor hit. Prompt alerts appear, and the positionis generated by hits in two orthogonal views.

POS PIN5 AT E3000The specified PIN and Current Element will be positioned as a single rigiditem, so that the PIN is at E3000 N0 U0 (see Figure 2-5).

Command Syntax:

>--+-- POSition <marke> --.| |‘----------------------+-- AT <bpos> -->



2-7

Querying:

>-- Query POSition --+-- <bpos> --.| |‘------------+-- WRT --.

| ||-- IN ---+-- <gid> -->|‘-->

Querying Examples:

Q POSGives position of Current Element origin in owner coordinates

Q POS IN SITEGives position of Current Element origin in Site

Q POS IDP@Gives position of picked p-point

U

E

N

1'

4' 6"

3'

CE ORIGIN

OWNER ORIGIN

AT E 3' N 4' 6" U 1'

Figure 2-4 Positioning the Current Element at a known point



Version 11.3

2-8

Figure 2-5 Positioning a PIN and the current element together at a knownpoint

2.2.2 Polar Positioning from the Origin

Keywords: POLAR DISTANCEDescription: This command is used to position the Current Element using polar

coordinates. This is particularly useful for positioning Nozzles. Thecoordinates are relative to the owner’s origin.

Examples:

POLAR E45N DIST 300The Current Element will be placed 300 from its owner’s origin along E45N(see Figure 2-6).

POLAR PIN1 DIST 3000The Current Element will be placed 3000 from its owner’s origin along thedirection of PIN1 (see Figure 2-6).

POS IDP@ POLAR S1OW DIST3The p-point hit and the current element will be moved as a rigid entity sothat the p-point is the specified polar distance from the owner’s origin.

Command Syntax:

>--+-- POSition <marke> --.| |‘----------------------+-- POLar <bdir> DISTance <uval> -->



2-9

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

Figure 2-6 Polar positioning from the origin

2.2.3 General Polar Positioning from the Origin

Keywords: POLAR PLANE DISTANCEDescription: This command differs from the basic polar option by allowing the

distance from the owner’s origin to be specified more generally. ThePLANE element of the command enables this distance to be given in adirection different from the polar direction. For example, an elementmay be placed on a line North 25 East, and at N250 from the owner’sorigin.



Version 11.3

2-10

Examples:

POLAR N30E PLANE N DIST 1000Positions the Current Element along the N30E line from the owner originat N1000 (see Figure 2-7).

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- POLar <bdir> -+- PLAne <bdir> -.

| |‘----------------+- DISTance <uval> ->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

Figure 2-7 General polar positioning from the origin by specifying a plane

2.3 Orientation and Connection

These commands allow the Current Element to be rotated. In the case ofconnection, the item is also repositioned.

For both commands, the specification of a single axial direction or p-point onthe Current Element is sufficient to perform a reorientation. However, asecond direction must be specified if the orientation is to be fixed in 3D space.



2-11

2.3.1 Design Element Orientation

Keywords: ORIENTATEDescription: Every Design element has its own co ordinate system which consists of

a right-handed set of East (X), North (Y) and Up (Z) axes. The preciseorientation of an element must be given as two statements fixing thedirection of two axes, e.g. ORI Y IS NORTH AND Z IS UP. When rotatingsymmetrical items, such as cylinders, it may be sufficient to give oneaxis direction only (allowing DESIGN to choose the other), e.g. ORI P1IS N45E. Regardless of the command given, orientation always occursabout the Current Element origin.

Examples:

ORI Y IS N AND Z IS UPThe Current Element is rotated about its origin so that its Y axis is pointingNorth (in owner coordinates) and its Z axis is pointing up (see Figure 2-8a).

ORI P1 IS EThe Current Element is rotated so that its P1 p-point is pointing East inowner coordinates (see Figure 2-8b).

Command Syntax:

>- ORIentate -+- <bdir> IS <bdir> -.| |‘--------------------+- AND <bdir> IS <bdir> -.

| |‘------------------------+-->

Querying:

>-- Query ORIentation --+-- WRT --.| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

2-12

Figure 2-8a Design element orientation (1)

Figure 2-8b Design element orientation (2)

2.3.2 Design Element Reorientation

Keywords: ROTATE BY ABOUT THROUGH ANDDescription: The ROTATE command allows you to rotate any Design element,

including a Group. The rotation required may be specified in any ofthe following ways:

• As a specified angle of rotation about the element’s default axis(i.e. the Z axis).



2-13

• As a specified angle of rotation about a given axis, the latterdefined by its direction and/or through point. If the directionand/or through point are omitted, the default direction is that ofthe Neutral Axis or Z axis; the default through point is theOrigin.

• By reference to the element’s axes.

Examples:

ROTATE BY -45Rotates by 45° about the element’s Z axis (anticlockwise when looking in the+Z direction, since the rotation is specified as a negative angle).

ROTATE BY 45 ABOUT ERotates by 45° about the E-W axis (clockwise when looking E).

ROTATE ABOUT E BY 45The same as the preceding example.

ROT THRO P3 ABOUT S BY -25Rotates element about an axis which passes in the N-S direction through itsp-point 3 position. The rotation is 25° anticlockwise when looking S alongthis axis.

ROTATE AND Y IS N45W25DRotates element until the Y axis points as closely as possible to theN45W25D direction.

Command Syntax:

Rotation about a given axis:

>- ROTate ABOut <bdir> + THRough <bpos> -+- BY -+- <uval> ----------------.| | | || | ‘- <bdir> TOwards <bdir> -|| | || ‘- AND <bdir> IS <bdir> ---------+->|| BY -+- <uval> ----------------.| | || ‘- <bdir> TOwards <bdir> -+->||‘ AND <bdir> IS <bdir> -+- THRough <bpos> -.

| |‘------------------+->



Version 11.3

2-14

Rotation to pass through a given point:

>- ROTate THRough <bpos> + ABOut <bdir> + BY + <uval> ---------------.| | | || | ‘ <bdir> TOwards <bdir> || | || ‘ AND <bdir> IS <bdir> ------+->|| BY -+- <uval> ---------------.| | || ‘- <bdir> TOwards <bdir> + ABOut <bdir> .| | || ‘--------------+->||‘ AND <bdir> IS <bdir> + ABOut <bdir> -.

| |‘----------------+->

Rotation by a specified amount:

>- ROTate BY + <uval> ---------------.| |‘ <bdir> TOwards <bdir> + ABOut <bdir> -+- THRough <bpos> -.

| | || ‘------------------+->|| THRough <bpos> -+- ABOut <bdir> -.| | || ‘----------------+->‘->

Rotation to give a specified orientation:

>- ROTate AND <bdir> IS <bdir> -+- ABOut <bdir> -+- THRough <bpos> -.| | || ‘------------------+->||- THRough <bpos> -+- ABOut <bdir> -.| | || ‘----------------+->‘->

2.3.3 Primitive Element Connection

Keywords: CONNECTDescription: This command allows the current primitive element to be ‘connected’

to another element or mapping pin. Any p-point on the Design elementmay be connected to any other p-point (except p-points on the sameelement). Mapping pins can also be used to great effect as they canconnect and be connected to. In the former case, both the pin andCurrent Element move as a rigid entity; in the latter, the CurrentElement moves to the static pin.

The connection operation includes positioning and orientation of theCurrent Element so that the two specified Design Points arecoincident and of opposite direction.



2-15

Examples:

CONN P2 TO P1 OF /AThe P2 of the Current Element is connected to the specified p-point onanother element (see Figure 2-9).

CONN PIN1 TO IDP@The Current Element and PIN1 are moved and rotated so that PIN1connects to the p-point hit.

CONN IDP@ TO IDP@ AND X IS NThe first point hit (belonging to the Current Element) is connected to thesecond point (belonging to another element). The Current Element isrotated so that its X axis is North in owner coordinates (see Figure 2-10).

Note: The first p-point in the command must belong to the Current Element.

Command Syntax:

>-- CONnect <marke> TO <marke> -+- AND <bdir> IS <bdir> --.| |‘-------------------------+-->

Querying:

>-- Query ORIentation --+-- WRT --.| ||-- IN ---+-- <gid> -->|‘-->


| ||-- IN ---+-- <gid> -->|‘-->

Figure 2-9 Connecting primitives by direct specification



Version 11.3

2-16

Figure 2-10 Connecting primitives by using cursor selection

2.4 Moving by a Known Distance

All the commands described in this section move the Current Element by aspecified distance in a given direction. The simplest method is to move fromthe present position along an axis direction using a command such as BY EAST

1000. However, the command options provided enable more complexmanoeuvres to be made. For instance, an element may be moved ‘towards’another item until its Easting has changed by a given amount.

2.4.1 Moving Along Axes

Keywords: BYDescription: This command displaces the Current Element by given amounts along

any East, North, Up (etc.) axes. These are normally the axes of theowner, but the axial system of any element, such as the SITE, can bespecified if required.

Examples:

BY E300 N400Moves the Current Element by the specified amounts along the owner’s axes(see Figure 2-11).

BY E3000 WRT SITEMoves the Current Element by the specified amount along the Site’s Eastaxis (see Figure 2-11).



2-17

Command Syntax:

>-- BY <pos> --+-- <axes> --.| |‘------------+-->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

N

E

N

E

BY E3000 WRT SITE

BY E3000

CE

OWNERAXES

SITEAXES

Figure 2-11 Moving along specified axes

2.4.2 Moving in any Direction

Keywords: MOVE ALONG TOWARDS DISTANCEDescription: This command displaces the Current Element in any specified

direction by a given distance.

Examples:

MOVE N45E DIST 100The Current Element is displaced along East 45 North in owner coordinatesby the specified distance (see Figure 2-12a).

MOVE TOW IDP@ DIST 100The Current Element is displaced towards the picked p-point by thespecified amount (see Figure 2-12b).



Version 11.3

2-18

Command Syntax:

>-- MOVe --+-- ALOng --.| |‘-----------+-- <bdir> DISTance <uval> -->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

Figure 2-12a Moving a given distance in a given direction (1)

Figure 2-12b Moving a given distance in a given direction (2)



2-19

2.4.3 Moving in any Direction: Distance Given in Different Plane

Keywords: MOVE ALONG TOWARDS PLANE DISTANCEDescription: This command differs from the basic option by allowing the distance

moved to be specified in a different plane from the actual movementdirection.

Examples:

MOVE TOW /DATUM PLANE E DIST 1000The Current Element is moved towards the specified design item until itsEasting (in owner coordinates) has changed by 1000 (see Figure 2-13).

Command Syntax:

>-- MOVe --+- ALOng -.| |‘---------+- <bdir> -+-- PLAne <bdir> --.

| |‘------------------+-- DISTance <uval> ->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

Figure 2-13 Moving in a direction specified in a different plane

2.5 Moving Through Defined Intersection Planes

The commands described in this section move the Current Element along agiven direction until it intersects with a fixed Reference Plane.

Any p-point on the Current Element may be used for the manoeuvre, althoughthe default is the origin. This point is moved to the Reference Plane which isspecified by the 3D position through which it passes. The orientation of theReference Plane defaults to perpendicular to the movement direction.

In no case is the volumetric geometry of any of the Design model considered.Although you do not need to know the actual distance moved, you must provide‘point-to-point’ dimensions in these commands. In other words, these



Version 11.3

2-20

commands cannot calculate physical clearances (see Sections 2.6 and 2.7 forsuch commands).

2.5.1 Moving Through an Intersection

Keywords: MOVE THROUGHDescription: This command moves the Current Element until its origin intersects

with the Reference Plane through a fixed 3D point.

Examples:

MOVE N30W THR /BOXMoves the Current Element along the given direction until it ‘intersects’ theReference Plane through the origin of the named element (see Figure 2-14).

MOVE E THR E3000Moves the Current Element along the given owner axis until it ‘intersects’the Reference Plane through E3000 N0 U0 (see Figure 2-15).

MOVE ALONG N45E THR IDP@Moves the Current Element along the given direction until it ‘intersects’ theReference Plane through the picked p-point (see Figure 2-16).

Note: The Reference Plane is perpendicular to the movement direction.

Command Syntax:

>-- MOVe --+-- ALOng --.| |‘-----------+-- <bdir> THRough <bpos> -->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



2-21

Figure 2-14 Moving along a given direction through an intersection

Figure 2-15 Moving to intersect a plane through a given point



Version 11.3

2-22

Figure 2-16 Moving to intersect a plane through a given point

2.5.2 Moving Either Side of an Intersection

Keywords: MOVE DISTANCE FROM TODescription: This command moves the Current Element until its origin intersects

the Reference Plane a given distance either side of a fixed 3D point.

Examples:

MOVE N30W DIST 30 TO(or FROM) /BOXMove the Current Element N30W until its origin intersects a ReferencePlane 30 before (or beyond) the origin of /BOX (see Figure 2-17).

MOVE E DIST 1000 FROM /VESSEL5Move the Current Element East until its origin intersects a Reference Plane1000 beyond the origin of /VESSEL5 (see Figure 2-18a).

MOVE ALONG N45E DIST 20 TO /COL8Move the Current Element along N45E until its origin intersects aReference Plane 20 before the origin of /COL8 (see Figure 2-18b).

Note: The Reference Plane is perpendicular to the movement direction.

Command Syntax:

>-- MOVe --+-- ALOng --.| |‘-----------+-- <bdir> DISTance <uval> --+-- FROm --.

| |‘-- TO ----+-- <bpos> -->



2-23

Querying:


| ||-- IN ---+-- <gid> -->|‘-->

30

REFERENCEPLANES

... DISTANCE 30 FROM /BOX

... DISTANCE 30 TO /BOX

(START POSITION)CEMOVE N30W...

Figure 2-17 Moving either side of an intersection

Figure 2-18a Moving either side of a plane specified relative to another element



Version 11.3

2-24

Figure 2-18b Moving either side of a plane specified relative to another element

2.5.3 General Moving to an Intersection

Keywords: MOVE PLANE THROUGH FROM TO DISTANCEDescription: This command differs from the basic options by allowing the

movement direction and Reference Plane to be specifiedindependently. For example, by specifying PLANE NORTH an elementmay be moved towards a point until a particular Northing in the Siteis intersected. In addition, any design point on the Current Element(not only the origin) can be used as the positioning datum; forinstance, the p-point on the flanged face of a nozzle.

Examples:

MOVE IDP@ TOW /DATUM PLANE N THROUGH N1000Move the picked p-point (or the Current Element) towards /DATUM until itintersects N1000 (see Figure 2-19a).

MOVE ALONG E PLANE N45W DIST 20 TO /TANK5Move the Current Element East until it intersects an oblique ReferencePlane 20 before the origin of /TANK5 (see Figure 2-19b).

Note: DISTANCE is measured in the direction of the Reference Plane andnot the movement direction.



2-25

Command Syntax:

>- MOVe -+- <marke> -.| |‘-----------+- ALOng -.

| |‘---------+- <bdir> -.

| |‘----------+- PLANe <bdir> -+- <dist> -+- FROm -.

| | || |- TO ---+- <bpos> -.| | || ‘-------------------|| ||- FROm ----. || | ||- TO ------| || | |‘- THRough -+- <bpos> ---------+->

<dist> = >- DISTance - <uval> ->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

2-26

Figure 2-19(a) Moving to an intersection by separately specifying directionand plane

Figure 2-19(b) Moving to an intersection by separately specifying directionand plane



2-27

2.6 Moving In Front of or Behind Items

The commands described in this section move the Current Element to theintersection with a Reference Plane, a specified distance from the surface of afixed geometric object.

Any p-point on the Current Element may be specified as the positioningdatum, although the default is the origin. In no case is the geometry of theCurrent Element considered. However, the full geometry of the fixed elementis taken into account. Although the designer does not need to know the actualdistance moved, he must provide a ‘point-to-surface’ dimension.

2.6.1 Moving Either Side of a Fixed Object

Keywords: MOVE DISTANCE INFRONT BEHINDDescription: This command moves the Current Element until its origin is a

specified distance one side or the other of a fixed geometric object. Thistakes into account the volume of the referenced element but not of theCurrent Element. Therefore it is applicable to, say, spacing thecentreline of a vessel or column a certain distance from the surface ofa wall.

Examples:

MOVE E DIST 1000 BEH /WALL10The Current Element is moved East until its origin is 1000 beyond the farside of /WALL10 (see Figure 2-20).

MOVE N45E DISTANCE 20 INFRONT /EXCH5The Current Element is moved until its origin is 20 to the near side of/EXCH5 (see Figure 2-20 and Figure 2-21).

Command Syntax:

>- MOVe -+- ALOng -.| |‘---------+- <bdir> DISTance <uval> -+- FROm -.

| |‘- TO ---+- <bpos> -+- INFront -.

| |‘- BEHind --+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->



Version 11.3

2-28

Querying:


| ||-- IN ---+-- <gid> ---.| |‘-----------------------+-->

Figure 2-20 Moving either side of a fixed object



2-29

Figure 2-21 Moving either side of a fixed object in a specified direction



Version 11.3

2-30

2.6.2 Moving On Top of or Under a Fixed Object

Keywords: MOVE DISTANCE ONTOP UNDERDescription: This command moves the Current Element until its origin is a

specified distance above or below a fixed geometric object. This takesinto account the shape of the referenced object but not that of theCurrent Element. It is therefore applicable to, say, placing thecentreline of a vessel a certain distance above the top surface of abeam.

Examples:

MOVE D ONTO /BOXMoves the Current Element along a vertical line until its origin lies in theupper surface of /BOX (see Figure 2-23).

MOVE ALONG E45D DISTANCE 3000 UNDER /BEAMMoves the Current Element along E45D until its origin is 3000 verticallybelow /BEAM (see Figure 2-22 and Figure 2-23).

Note: ONTOP means above in owner co-ordinates regardless of originalCurrent Element position. The DISTANCE is always measuredvertically in owner co-ordinates.

Command Syntax:

>- MOVe -+- ALOng -.| |‘---------+- <bdir> DISTance <uval> -+- FROm -.

| |‘- TO ---+- <bpos> -+- UNDer -.

| |‘- ONTop -+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



2-31

Figure 2-22 Moving above/below a fixed object in a specified direction



Version 11.3

2-32

Figure 2-23 Moving above/below a fixed object



2-33

2.6.3 Moving an Item Using Reference Points

Keywords: MOVE ALONG PLANE DISTANCE INFRONT BEHIND ONTOP UNDER

Description: This command differs from the basic options by allowing any point onthe Current Element to be moved to a specified distance from thesurface of a fixed design item. In addition the distance may bespecified in a direction independent of the movement direction.

Examples:

MOVE P1 E INFRONT /BOXThe Current Element will be moved East until the specified p-point is zerodistance in front of /BOX (see Figure 2-24).

MOVE NOZZLE1 S DIST 200 INF /RACK (at an Equipment element)Moves the current Equipment by positioning the Nozzle at the specifiedlocation.

Command Syntax:

>- MOVe <marke> -+- ALOng -.| |‘---------+- <bdir> PLAne <bdir> DISTance <uval> <repla> ->

<repla> = >--+-- FROm --.| ||-- TO ----+-- <bpos> -->||-- INFront --.| ||-- BEHind ---|| ||-- UNDer ----|| |‘-- ONTop ----+-- <gid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

2-34

Figure 2-24 Moving to a point at a specified distance from a surface



2-35

2.7 Moving to a Specified Clearance between Items

These commands allow the Current Element to be moved to a specifiedclearance from a fixed object or position. Their separation takes into accountboth the Current Element volume and the referenced element volume. For thebasic options, the clearance dimension is always specified in the movementdirection. It is therefore important to place the Current Element at anappropriate position from which to make the clearance move. A simpleralternative is available for placing the Current Element vertically above orbelow the reference element independently of movement direction. In theseinstances a vertical clearance can be specified directly using the ONTOP orUNDER options.

2.7.1 Moving to a Clearance Either Side

Keywords: MOVE CLEARANCE INFRONT BEHINDDescription: This command moves the Current Element until its geometric volume

is a specified clearance from a fixed Design element, Point or position.

Examples:

MOVE ALONG E45N CLEAR BEHIND /BOXMove the Current Element until its volume is zero clearance behind BOX(see Figure 2-25).

MOVE E CLEAR 1000 INFRONT /DATUMBOXMove the Current Element East until its volume is 1000 this side of thegiven fixed item (see Figure 2-26).

MOVE E45N CLEAR 100 BEH IDP@Move the Current Element along E45N until its volume is 100 beyond thecursor hit p-point (see Figure 2-26).

Command Syntax:

>- MOVe <marke> -+- ALOng -.| |‘---------+- <bdir> CLEArance <uval> -+- INFront -.

| |‘- BEHind --+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->



Version 11.3

2-36

Querying:


| ||-- IN ---+-- <gid> --.| |‘----------------------+-->

Figure 2-25 Moving to a given clearance in a specified direction



2-37

Figure 2-26 Moving to a given clearance



Version 11.3

2-38

2.7.2 Moving an Object to Clear Another Object

Keywords: MOVE CLEARANCE INFRONT BEHIND ONTOP UNDERDescription: This command takes into account the geometry of both the Current

and Referenced elements. In this way a minimum clearance can bespecified between two Design items (for example, to ensure that awalkway is a sufficient distance away from a heated autoclave).

Examples:

MOVE E CLEARANCE 1000 BEH /WALL10The Current Element is moved East until its entire volume is 1000 clear ofthe side of /WALL10 (see Figure 2-27).

MOVE D CLEARANCE ONTO /BEAMThe Current Element is moved down until it has a zero clearance above theelement /BEAM (see Figure 2-27).

Command Syntax:

>- MOVe -+- ALOng -.| |‘---------+- CLEArance <uval> -+- INFront -.

| ||- BEHind --|| ||- UNDer ---|| |‘- ONTop ---+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



2-39

Figure 2-27 Moving to clear another object



Version 11.3

2-40

2.7.3 Moving to a Vertical Clearance

Keywords: MOVE CLEARANCE ONTOP UNDERDescription: This command moves the Current Element until its volume is a

specified vertical clearance above or below a fixed element, Point orposition.

Examples:

MOVE ALONG U30W CLEAR ONTO /BEAMThe Current Element will be moved vertically until it is zero clearanceabove /BEAM (see Figure 2-28).

MOVE E60D CLEAR 1000 UNDER PIN6The Current Element will be moved E60D until it is 1000 below thespecified Design point (see Figure 2-29).

Command Syntax:

>- MOVe -+- ALOng -.| |‘---------+- <bdir> CLEArance <uval> -+- UNDer -.

| |‘- ONTop -+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



2-41

Figure 2-28 Moving to a given vertical clearance in a specified direction



Version 11.3

2-42

Figure 2-29 Moving to a given vertical clearance



2-43

2.7.4 General Moving to a Clearance

Keywords: MOVE PLANE CLEARANCE INFRONT BEHINDDescription: This command differs from the basic option by allowing the movement

direction and clearance to be specified in different planes.

Examples:

MOVE TOWARD /TANK5 PLANE E CLEARANCE 30 INF /TANK5The Current Element will be moved towards /TANK5 until it has 30clearance ‘this side’ in an East/West direction (see Figure 2-30).

Command Syntax:

>- MOVe -+- ALOng -.| |‘---------+- <bdir> -+- PLAne <bdir> -.

| |‘----------------+- TOwards <bpos> -.

|.--------------------------------<-------------------------------’|‘- CLEARance <uval> +- INFront -.

| |‘- BEHind --|

|- <gid> --.| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

2-44

Figure 2-30 Moving to a given clearance relative to a specified plane

2.8 Reflecting a Position in a Plane (Mirroring)

The mirroring facility lets you change the position of the current element orgroup by reflecting it in a specified plane. The current element and itshierarchy of members will be repositioned so as to achieve a mirror image oftheir initial relative positions. If the current element is a Group, all membersof the group and their hierarchies of members will be reflected.

The values of positional attributes and directional attributes are derived bydirect reflection in the plane.

Orientations are processed such that they remain right-handed. For mostelements this is achieved by reflecting the Y and Z axes directly, whilereflecting and reversing the X axis. The exceptions to this rule are:

• Toruses (CTOR, RTOR, NCTO, NRTO), whose X and Y axes are reflecteddirectly while the Z axis is reflected and reversed;

• The piping elements Tee, Nozzle, Elbow, Coupling, Reducer and Flange,where the p-points are used to decide the axis of greatest symmetry forthe reversal. For example, an ELBO with p-point directions along X andY will be reversed in the Z direction.

You will most likely use the mirror positioning options in conjunction with theCOPY command (see Sections 8.1.5 and 8.1.6 of Part 1) to create a new part ofthe design model which is a mirror image of an existing part.



2-45

Note: Since mirror-image components will not always be available in theCatalogue, no attempt is made to reflect catalogue geometry or toreference alternative catalogue components.

Keywords: MIRRORDescription: Moves the current element to a new position which is calculated by

reflecting the initial position in a specified plane.

Examples:

MIRROR PLANE E45D THRO /TANK5Reflects position of current element in plane which has given direction andwhich passes through /TANK5 (see Figure 2-31).

Command Syntax:

>-- MIRRor -- <plane> -->

where <plane> is any of the standard ways of specifying a plane through agiven point in a given direction:

<plane> = >-+- PLAne <bdir> -+- DISTance <uval> -+- <repla> ------.| | | || | ‘----------------|| | || |- <repla> --------------------------|| | || |- THRough <bpos> -------------------|| | || ‘- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -|| | || |- <planf> -|| | || ‘-----------||- DISTance - <uval> -+- <repla> -. || | | || |- <planf> -| || | | || ‘-----------+-------------------|| ||- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -. || | | || |- <planf> -| || | | || ‘-----------+----------------|| ||- <repla> -------------------------------------------|| ||- THRough <bpos> ------------------------------------|| |‘- <planf> -------------------------------------------+->



Version 11.3

2-46

<repla> = >--+-- INFront --.| ||-- BEHind ---+-- <sgid> ---.| | || |-- <marke> --|| | || ‘-- <bpos> ---|| ||-- FROm --. || | |‘-- TO ----+-- <bpos> ------+-->

<planf> = >--+-- ONTop --.| |‘-- UNDer --+-- <sgid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

/TANK5

Current Element(owning threeprimitives)

E45DPlane direction

Plane through /TANK5

MIRROR PLANE E45D THRO /TANK5

Figure 2-31 Mirroring a position in a plane


3 Piping, Ducting and Cable Trays

This chapter describes the commands to create Piping (including Hangers),Ducting and Cable Trays. Then the commands to position, orientate andconnect piping components are described.

The key element in these disciplines is the Branch. This is a two-ended entitywhich can be joined with other Branches to form a network. The network canfinish where a Branch is connected to an Equipment Nozzle, reaches the sitelimits, or stops at a vent or drain valve. The Branch element owns Componentelements drawn from the PDMS Catalogue whose sequence and position definethe centreline route. Straight variable lengths of Tube are automaticallyrouted between adjacent Components and are therefore not individualComponent elements themselves.

There are no special Design hierarchy elements for ducting and cable trays.They are routed as Branches, but with Components drawn from parts of theCatalogue dedicated to the relevant discipline. It is convenient, therefore, torefer to pipes, ducting and cable trays collectively as ‘piping’, since PDMStreats them similarly. The principles applied to ‘routing’ two-ended pipeHangers are also identical to those used for Branches. Where no distinction ismade, the term ‘piping’ also applies to Hangers.

3.1 Defining a Branch

Before routing takes place, various preparatory steps are taken to define theSpecification and the start and end points of the Branch or Hanger. The PipingSpecification and Insulation Specification are defined first, so that allComponents created within the Branch can be selected correctly.

The Head and Tail attributes can be set either by explicit positioning or byconnection to another item (e.g. a Nozzle). The Tail position may be in freespace, when it is determined by the Leave point of the final Component in theBranch. It is quite normal in such circumstances to route the pipe with onlythe HEAD attributes set up. (The reverse may also apply if routingbackwards.)

When a Branch is connected to another item, the attributes of the element thatit is connected to are set to refer to the Branch. For example, if a Branch Headis connected to a Nozzle, then the CREF (Connection Reference) attribute ofthe Nozzle is set to refer to the Branch.

Note that when a Branch is connected to a Nozzle, the Noxzzle may be part ofa database to which the piping engineer does not have write-access. In thiscase, an Inter-DB Connection Macro is created, which can be run by the

Piping, Ducting and Cable Trays


Version 11.3

3-2

designer who does have write access to the second database. This macro is asequence of commands that, for example, sets the CREF of a Nozzle that hasbeen connected to by the piping designer. For more information, see Part 1 ofthe DESIGN Reference Manual.

3.2 Branch and Hanger Specifications

Keywords: PSPE HSPE

Description: On creation of a Branch (or Hanger) these are normally the firstattributes to be set. If the Specification of the Pipe has already beenset, then this will automatically be cascaded down to Branch levelwhen it is created. The PSPE attribute of a Branch controls allsubsequent Component selection operations which choose aComponent’s physical details from the stated Specification.

Examples:

PSPEC /A35B8 (At Pipe level)The PSPE attribute of the Pipe and all subsequently created Branches willbe set to /A35B8.

PSPEC /A15A2 (At Branch level)The PSPE attribute of the Branch will be set to /A15A2. All subsequentselection commands at that Branch or one of its Components will use thatSpecification by default.

Note: The Specification named must be currently available to the designer.

Command Syntax:

>-- PSPEcification name -->



3-3

3.3 Connecting the Head or Tail

Keywords: CONNECTDescription: The CONNECT command, when applied to Branches (or Hangers), sets

up the Head or Tail to match exactly the item to which it has beenconnected. For example, if the Head is connected to a 3-inch flanged-faced nozzle at E3000 and pointing North, the CONNECT commandwill set all the Head attributes (HBOR, HCON, HPOS and HDIR) tocorresponding values. In addition, the Head and Nozzle are logically‘tied together’ by two attributes which ‘point’ to each other - the NozzleCREF will point to the Branch, and the Branch HREF (HeadReference) will point to the Nozzle.

The final effect of CONNECT, which only applies to Heads, is that theTube (or Rod) that may be required between the Head and the firstComponent is automatically selected.

A Branch Head or Tail can connect to the following items:

• A Nozzle

• The Head or Tail of another Branch

• A ‘free’ p-point of a multi-way Component in another Branch (e.g.a Tee)

Examples:

CONN PH TO /1205-N5 (Where /1205-N5 is a Nozzle)The Head attributes of the current element (Branch or Hanger) are set tomatch the position, orientation, bore and connection type of the Nozzle (seeFigure 3-1).

CONN PT TO LAST MEMThe Tail attributes of the current element will be set to match the LeavePoint of the last Component (that is not an Attachment point).

CONN PT TO /100-A8/T2 (Where /100-A8/T2 is a TEE)The Tail attributes of the current element will be set to match the free p-point on the specified TEE (see Figure 3-1).

CONN PT TO P4 OF /VF205 (Where /VF205 is a VFWA.)The Tail attributes of the current element will be set to match the specifiedp-point.

CONN PH TO PT OF /100-A8/1 (Where /100-A8/1 is anotherBranch)

The Head attributes of the current element will be set to match the Tail ofthe specified Branch.

CONN PH TO ID NOZZ@As in the first example, but with the Nozzle identified by cursor selection.



Version 11.3

3-4

Note: Before a CONNECT command is given, the Branch Specificationattribute must be set. Connection to elements not within thedesigner’s jurisdiction (Read Only) will cause an inter-DB connectionmacro to be created automatically (see Part 1 of the DESIGNReference Manual).

Command Syntax:

>-- CONnect <marke> TO --+-- <marke> --.| |‘-- <gid> ---+-->

Querying:

>-- Query --+-- PHead --.| ||-- HHead --|| ||-- PTail --|| |‘-- HTail --+-->

>-- Query --+-- HPosition --.| |‘-- TPosition --+-- WRT --.

| |‘-- IN ---+-- <gid> -->

HEAD

TAIL

CONN PHTO /1205-N5/1205-N5

PH

BRANCH

CE

CONN PT TO/100-A8/T2

BRANCHCENTRELINE

PT

PLPA

/100-A8/T2

Figure 3-1 Connecting a Branch Head or Tail



3-5

3.3.1 The Head or Tail Connection Reference Attribute

Keywords: HREF TREFDescription: These attributes hold the name of the element to which the Branch or

Hanger is connected. They are usually set automatically as a result ofa CONNECT PH (or PT) command, but they may also be set explicitly.When they are set, the corresponding attribute (CREF, HREF orTREF) of the item connected to is reset so as to point back to theBranch or Hanger.

Examples:

TREF /PIPE2 HEADSets TREF of current element to point to Head of /PIPE2 and setsHREF of/PIPE2 to point back to the current element.

HREF NULREFUnsets HREF; i.e. disconnects Head from any other element.

Command Syntax:

>--+-- HRef --.| |‘-- TRef --+-- <gid> --+-- HEAD --.

| | || |-- TAIL --|| | || ‘----------+| |‘-- NULREF -------------+-->

Querying:

>-- Query --+-- CE ------.| ||-- HEAd ----|| ||-- BRANch --|| |‘-- TAIl ----+-->

>-- Query --+-- HREF --.| |‘-- TREF --+-->



Version 11.3

3-6

3.3.2 Positioning Head or Tail in Free Space

Keywords: HPOS HBOR HDIR HCON TPOS TBORTDIR TCON

Description: It is sometimes necessary to terminate a Branch (or Hanger) in freespace; for instance, where a Branch reaches the Battery Limits. Wherethis termination ends with a length of TUBE (or ROD) and no Head orTail connection can be made, it is necessary to set the Head/Tailattributes individually.

Examples:

HPOS E10 N5 U5The Head position is set as specified in owner coordinates.

HDIR N WRT WORLDThe Head direction is set as specified in World coordinates.

HBOR 80The Head Bore is set as specified.

HCON OPENThe Head Connection Type is set as specified.

Note: If a data consistency error is to be avoided, the HCONN or TCONN ofa free end must be set to one of the following: OPEN, CLOS, VENT,DRAN (drain), or NULL.

Command Syntax:

>--+-- HPos --.| |‘-- TPos --+-- <bpos> -->

>--+-- HDir --.| |‘-- TDir --+-- <bdir> -->

>--+-- HBOre --.| |‘-- TBore --+-- <uval> -->

>--+-- HCOnn --.| |‘-- TCOnn --+-- word -->



3-7

Querying:

>-- Query --+-- PHead --.| ||-- HHead --|| ||-- PTail --|| |‘-- HTail --+-->

3.3.3 Head or Tail Positioning Using End Components

Keywords: POSITION PH PT THROUGH DISTANCEDescription: These commands allow the Head or Tail position to be set by using the

end Component in that Branch or Hanger. This will normally occurwhen the Tail is to finish with a piece of variable length Tube. Thiscommand treats the Tail position as a pseudo-Component and places itat the specified point along the previous Component’s Leave p-pointdirection. If the Head is to be positioned in this way, BackwardsRouting Mode must be in force.

Examples:

POS PT DISTANCE 1000The TPOS attribute will be set to the position 1000 from the leave p-point ofthe last Branch member (i.e. previous Component).

POS PH THROUGH E3000 (In BACKWARDS mode)The HPOS attribute will be set to the intersection between the line from theArrive p-point of the Previous Component and the perpendicular planethrough E3000 N0 U0 in owner coordinates.

Command Syntax:

>-- POSition --+-- PHead --.| ||-- PTail --|| ||-- HHead --|| |‘-- HTail --+-- DISTance <uval> --.

| |‘-- THRough <bpos> ---+-->



Version 11.3

3-8

Querying:

>-- Query --+-- PHead ------.| ||-- PTail ------|| ||-- HTail ------|| ||-- HHead ------|| ||-- HPosition --|| |‘-- TPosition --+-->

LAST COMPONENT

D PT

1000

PL

POS PT DISTANCE 1000

LAST COMPONENT

D PA

(BACKWARDS MODE)

N

E

30

OWNERAXES

POS PH THROUGH E30

PH

D

D

Figure 3-2 Head/Tail positioning using end components



3-9

3.3.4 Head and Tail Positioning by Bottom or Top of Pipe

Keywords: BOP TOP INFRONT BEHIND ONTOP UNDERDescription: This command allows the Head or Tail of a Branch to be moved

vertically to a specified clearance above or below a Design element orPoint. If the Head or Tail Tube has been selected, then its cross-section will be taken into account. (Otherwise the HPOS or TPOS willbe moved to the specified clearance, as no Tube geometry is available.)

Examples:

BOP ONTO /BEAM (At the Head)This will position the Tube on top of /BEAM with a clearance of 0.

TOP UNDER U3000 (At the Tail)This will position the Tail under the elevation U3000 with a clearance of 0.

Note: If no Tube can be found emerging from the point specified, then onlythe point’s position can be used.

Command Syntax:

>--+-- BOP --.| |‘-- TOP --+-- <uval> --.

| |‘------------+-- FROm --.

| ||-- TO ----+-- <bpos> -->|||-- INFront --.| ||-- BEHind ---|| ||-- ONTop ----|| |‘-- UNDer ----+-- <gid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->



Version 11.3

3-10

Querying:


OWNERAXES

UP

HORIZONTAL

PH PT

BOPONTO/BEAM

PH

TOPUNDERU3000

PT

/BEAM

3000

Figure 3-3 Head/Tail positioning by Bottom/Top of pipe



3-11

3.3.5 Moving the Head or Tail

Keywords: MOVE BY DISTANCEDescription: This command allows the Head or Tail position to be moved by a

specified distance, relative to its current position, in the direction ofPH or PT. Alternatively, it allows the Head or Tail to be moved by anamount specified in any coordinates.

Examples:

MOVE PT DIST -2000Moves the Tail by 2000 from its current position, in the opposite direction toPT.

MOVE PT BY E2000 S500Moves the Tail by 2000 East and 500 South from its current position

Command Syntax:

>-- MOVe --+-- PHead --.| ||-- HHead --|| ||-- PTail --|| |‘-- HTail --+-- BY <pos> --+-- WRT --.

| | || |-- IN ---+-- <gid> -->| || ‘-->|‘-- DISTance <uval> -->

Querying:




Version 11.3

3-12

Figure 3-4 Moving the Head or Tail



3-13

3.3.6 Reconnecting Pipes after an Equipment Move

Note: Applicable to Nozzles that have been moved since a Branch wasconnected to them. Largely superseded by the DRAG command.

Keywords: RECONNECTDescription: If an Equipment item is moved using an ordinary positioning

command, none of the Branches connected to it will move with it.RECONNECT will reconnect all the HEADS and TAILS of Branchesconnected to an Equipment, moving them to new positions ifnecessary. Other elements in the Branches are not affected and mustbe realigned using ordinary routing commands.

Examples:

RECONFinds all Nozzle elements which are Offspring of the current element. Foreach Nozzle, any Branch Head (or Tail) which is connected to it isrepositioned at the Nozzle.

Command Syntax:

>-- RECOnnect -->

3.4 Selecting Component and Tube Details fromSpecifications

Selecting from Specifications in PDMS is fundamental to all Piping designwork. When you created a Component element (say an ELBO), you must thengive the CHOOSE (or SELECT) command to form a link from the Component tothe Catalogue description of the item, via the chosen Specification.

As the correct choice of Component can involve a large number ofconsiderations, each Selection would be very arduous if conducted manually.DESIGN assists you by automatically examining the current element and itsimmediate neighbours for default parameters, then searching for anappropriate item in the Specification.

Of course, ultimate control rests with the designer, who can fully or partiallyoverride this choice. However, in the majority of cases, the default Selectionwill be suitable. In a similar manner, the straight TUBE between adjacentComponents is Selected from a Specification. This is usually doneautomatically at the same time as Component Selection, so the designer onlyneeds to be concerned with separate TUBE selection in certain specialcircumstances detailed in this section.



Version 11.3

3-14

Most of the examples here assume that certain common PDMS conventions arefollowed, (e.g. P3 of a TEE is the off-line p-point). It is advisable to discuss thestructure of your own company Catalogue and Specifications with yourCatalogue Administrator before reading this section. In order to make thecorrect Selections, you will also need a printed copy of each Specification thatyou wish to use.

3.4.1 Choosing Components from a Displayed List

Keywords: CHOOSEDescription: This is only available in DEV GRAPHICS mode.

The CHOOSE command displays Selection options on screen formswhich can be picked using the cursor. Once an element has beencreated using the NEW command, CHOOSE may be used to list whatis available in the Specification.

The effect of choosing from the displayed list and applying the formsetting via the OK button is to set the SPREF and LSTUBE attributesof the current Component, taking into account the choice made andthe current bore. Specification-dependent Design attributes (if any)will also be set, i.e. HEIG, ANGL, RADI and SHOP. The Componentmay (optionally) be positioned and connected to the previous (or next)Component (or to the pipe head or tail). If the Cancel button isselected, the Component’s attributes will remain unchanged.

It may be that a newly selected Component is unsuitable forconnection to the previous (or next) Component (or to the Pipe Head orTail), for example due to incompatible connection types. In such acase, the new Component will be force-connected and a warning alertdisplayed. This action can be turned off by giving the command

CHOOSE FORCECONNECT OFF

Connection attempt will still be made, but Component will be left atSite origin if connection types are incompatible.

If the force-connect facility is OFF, a connection attempt will stillbe made following component selection. In this case however, thenewly selected Component will be left at the Site origin if connectiontypes are incompatible. This action can be turned off by giving thecommand

CHOOSE AUTOCONNECT OFF

No connection attempt will be made; Component will be left at Siteorigin.

The default state is CHOOSE FORCECONNECT ON.



3-15

If only one choice of Component is available, for example flanges ofonly one type are valid at a particular bore, DESIGN will set SPREFand LSTUBE automatically. If there are no valid choices, for examplethere are no Components of a particular type for the specified bore, anerror alert is displayed.

The CHOOSE command may be used within the same command lineas a NEW command.

Examples:

CHOOSEDisplays a general Selection form for the current element. Selection criteriadisplayed will depend on those available in the specification.Example form:

NEW GASK CHOOSE

CHOOSE

Current bore 100.00 mm

Forced Connections are ON

RATI

OK

300.00150.00

CANCEL



Version 11.3

3-16

CHOOSE TEXTDisplays a Selection form listing choices based on the SpecificationComponent’s (SPCOM’s) Detail Description Text (obtained from the RTEXattribute of the relevant DTEX element) and Material Description Text(obtained from the XTEX attribute of the relevant MTEX element).Example form:

NEW TEE CHOOSE TEXT

CHOOSE



Component Description

OK

REDUC TEE BW SCH 40 X 80EQUAL TEE BW SCH 40 X 40

CANCEL

REDUC TEE BW SCH 40 X 80UnsetUnset

CHOOSE RTEXCHOOSE STEXCHOOSE TTEXDisplays a Selection form listing choices based on the SPCOM’s DetailDescription Text (obtained from the RTEX, STEX or TTEX attribute of therelevant DTEX element).Example form:

NEW GASK CHOOSE RTEX (or STEX or TTEX)

CHOOSE




OK CANCEL

150# RING GASKET 3MM THK300# RING GASKET 3MM THK



3-17

CHOOSE XTEXCHOOSE YTEXCHOOSE ZTEXDisplays a Selection form listing choices based on the SPCOM’s MaterialDescription Text (obtained from the XTEX, YTEX, or ZTEX attribute of therelevant MTEX element).Example form:

NEW GASK CHOOSE XTEX (or YTEX or ZTEX)

CHOOSE




OK CANCEL

SPIRAL WOUND SS ASBESTOS FILLEDSPIRAL WOUND SS ASBESTOS FILLED

CHOOSE ALLCombines the above CHOOSE and CHOOSE TEXT options.Example form:

NEW GASK CHOOSE ALL

CHOOSE



RATI

OK

300.00 300# RING GASKET 3MM THK SPIRAL WOUND SS ASBESTOS FILLED150.00 150# RING GASKET 3MM THK SPIRAL WOUND SS ASBESTOS FILLED

CANCEL

CHOOSE SPEC /RF150As CHOOSE, but selections are made from the named specification ratherthan from that of the owning Branch.



Version 11.3

3-18

CHOOSE DEFAULTDefault settings will be selected wherever they occur in the Specification.For example, if the default STYP for a Reducer is CONC, only ConcentricReducers will be listed in the selection form.

NEW REDU

CHOOSE WITH ABOR 100 LBOR 80Choose from Reducers with specified arrive and leave bores only

NEW ELBO CHOOSE WITH STYP LRChoose from long-radius Elbows only.

Note: The Selection criteria (see syntax diagram) are independent.

The CHOOSE function assumes that the Specification hierarchy is asfollows, and use of the command will generate an error if this is not so:

• The first level must contain the question TYPE

• The second level must contain the question PBOR or BORE

Command Syntax:

>- CHOOse -+- AUTOConnect --.| ||- FORCEConnect -+- ON --.| | || ‘- OFF -+->||- SPec <gid> -.| |‘--------------+- DEFault -.

| |‘-----------+- RTEX -.

| ||- STEX -|| ||- TTEX -|| ||- XTEX -|| ||- YTEX -|| ||- ZTEX -|| ||- TEXT -|| ||- ALL --| .----<----.| | / |‘--------+- WITH -*- <wivl> --|

| | || ‘- <wiwor> -+->‘->

where:



3-19

<wivl> is >--+-- PBOre integer --.| ||-- ANgle ----------|| ||-- RAdius ---------|| ||-- ABOre ----------|| ||-- LBOre ----------|| ||-- PREssure -------|| ||-- TEMperature ----|| |‘-- RATing ---------+-- <uval> -->

and

<wiwor> is >--+-- STYpe --.| ||-- TYpe ---|| ||-- ACOnn --|| ||-- LCOnn --+-- word -->||-- PCOnn integer word -->|‘-- word --+-- value --.

| |‘-- word ---+-->

3.4.2 Selecting Components from Specifications

An alternative method of selecting items from a Specification is to create thepiping Component, and then to ask the system to select a component of thecorrect type from the current piping Specification. If there is a choice ofcomponent during selection, it is sometimes necessary to specify answers tospecification questions such as STYPE or BORE before the correct item isselected.

Typical commands could be as follows:

NEW ELBO SEL WITH STYP LR

NEW TEE SEL WI PBOR 3 150

NEW FLAN SEL WI STYP WN

NEW REDU SEL WI STYP ECC LBOR 100



Version 11.3

3-20

3.4.3 Selecting the Default Specification Component

Keywords: SELECTDescription: The SELECT command chooses a Component and its ‘Leave’ Tube from

the Branch Specification. Selecting the default SpecificationComponent allows DESIGN to choose the appropriate item. This isbased upon information DESIGN can obtain from the Design and from‘default’ controls within the Specification. Default Selection isparticularly applicable to common fittings such as FLANGEs,GASKETs, ELBOWs etc. The information automatically determinedfrom the current element and its surroundings is as follows:

SPECIFICATION Obtained from the PSPE attributeof the Branch.

(ARRIVE) BORE Obtained from the (Leave) bore ofthe Previous element (reverse inBackwards Mode).

ANGLE, HEIGHT, RADIUS Obtained from the correspondingCurrent Element attributes.

SHOP Obtained from the correspondingCurrent Element attribute.

TEMPERATURE, PRESSURE Obtained from the correspondingBranch attributes.

3.4.4 Selecting from Several Alternatives

Keywords: SELECTDescription: The SELECT command chooses a Component and Leave Tube from the

Specification and sets the appropriate current element attributes. Inorder to make a Selection from the Specification, parameters for allthe Specification Headings for that type of Component must beautomatically obtained or provided by the designer. In many cases, thedefault choice may not be suitable. This may be because:

• One or more of the Specification Headings has no defaultparameter for that Component (e.g. the Leave bore of a Reducercannot be assumed)

• You wish to choose a non-default item (e.g. socket weld, not aweld-neck)

In both instances, the designer must specify the relevant Headingswith the required Entry as part of the SELECT command.

After a successful SELECT command, the design attributes will beupdated with the relevant values from the Specification. The relevant



3-21

attributes are ANGLE, RADIUS and SHOP, and HEIGHT if specifiedin the SELECT command.

Examples:

SELECTThe default Component and Leave Tube will be selected from the BranchSpecification. The Current Element SPREF and LSTU attributes will be setto the chosen Specification Component names.

SEL WI STYPE BALLThe current element and Leave Tube will be selected using the defaultchoices except for the STYPE Heading which has been specified.

SEL WI STYPE ECC PBOR 2 50The current element and Leave Tube will be selected using the defaultchoice except for the Headings specified. (If the Component LEAVE is 2,then the Leave Tube will also be 50 bore.)

SEL WI ANGLE 45The current element and Leave Tube will be selected using the defaultchoice except for the ANGLE heading. Also, the ANGLE attribute of theCurrent Component will be set to 45. (Similar behaviour occurs withHEIGHT and RADIUS.)

SEL WI LBOR 50The current element will be selected using the default choice. However theLeave p-point and Leave Tube will be selected with the specified nominalbore.

Command Syntax:

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

>-- SElect WIth --*-- SPec <gid> --|| ||-- <wivl> ------|| ||-- <wiwor> -----’|‘-->

For Selection criteria that are only in the Specification, the Specification itselfmay also contain information to assist default Selection. This information is inthe Default Line of the Specification.

Querying:

>-- Query --+-- SPRef --.| |‘-- TUbe ---+-->



Version 11.3

3-22

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

>-- Q SPECification --*-- <qspci> --+-->

where <qspci> is:

>--+-- PBOre integer --.| ||-- ANgle ----------|| ||-- RAdius ---------|| ||-- ABOre ----------|| ||-- LBOre ----------|| ||-- PREssure -------|| ||-- TEMperature ----|| ||-- RATing ---------|| ||-- STYpe ----------|| ||-- TYpe -----------|| ||-- PCOnn integer --|| ||-- ACOnn ----------|| ||-- LCOnn ----------|| |‘-- word ----+-->

3.4.5 Selecting ‘Out-of-Specification’ Components

Keywords: SELECT SPECDescription: If an ‘out-of-specification’ Component is required, this can be Selected

using the SELECT WITH SPEC command. This command uses thestated Specification rather than the default Specification. OtherHeadings necessary to specify which ‘out-of-specification’ item isrequired can be given in the same command.

Examples:

SEL WI SPEC /A3AHThe current element will be Selected from the given Specification using thedefault choice.

SEL WI SPEC /A3AH STYPE CTRLThe current element will be Selected from the given Specification using thedefault choice except for STYPE.



3-23

Note: The Leave Tube will be selected from the default (Branch)Specification in all cases.

Command Syntax:

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

>-- SElect WIth SPec <gid> --* ||-- <wivl> ---|| ||-- <wiwor> --’||-- <gid> -->|‘-->

<wivl> and <wiwor> are explained in the section on Standard Syntax Graphsin Part 1 of the DESIGN Reference Manual.

Querying:

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

>-- Query SPECification --*-- <qspci> --+-->

<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of theDESIGN Reference Manual.

>-- Query --+-- SPRef --.| |‘-- TUbe ---+-->

3.4.6 Selecting Components and Tube Separately

Keywords: SELECT SPREF TUBE ROD HSTUBE LSTUBELSROD HSROD

Description: In some instances it may be necessary to Select Tube (or Rod)separately from its owning Component, or vice versa. This commandenables separate Selection to occur. SELECT TUBE is most frequentlyused at the HEAD of a Branch where there is Tube between the Headand the First Component.

Examples:

SEL TUBE (At Branch)The Branch HSTU attribute (Head Specification Tube) will be Selectedaccording to the default choice of TUBE.

SEL TUBE WI STYP GLAS(At Component)The Component LSTU attribute (Leave Specification Tube) will be Selectedwith the default choice of TUBE except for STYPE.



Version 11.3

3-24

Command Syntax:

>-- SElect --+-- SPref ---.| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| ||-- HSrod ---|| ||-- TUbe ----| .-----<-----.| | / |‘-- ROD -----+-- WIth -- *-- <wivl> ---|

| ||-- <wiwor> --’||-- <gid> -->|‘-->

Querying:

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


>-- Query --+-- SPRef ---.| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| |‘-- HSrod ---+-->

3.4.7 Direct Selection by Shortcode

Keywords: SHORTCODEDescription: The actual Specification Component name (SPREF for Components,

LSTU or HSTU for Tube) can be specified in order to Select aComponent. This overrides the ordinary Selection process by directlychoosing the required item. The shortcode option assumes Selectionfrom the Current Branch Specification by automatically providing thespecname part. Thus it is assumed that the Specification Componentname is of the form /specname/shortcode.



3-25

Examples:

SHOR /EL50The current element SPRE attribute will be set to /specname/EL50 where/specname is obtained from the Branch.

SHOR TUB /TU50The current element LSTU (or HSTU) attribute will be set to/specname/TU50 where /specname is obtained from the Branch.

Note: /specname is shown as * on PDMS Specification listings.

Command Syntax:

>-- SHORtcode --+-- SPRef ---.| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| ||-- HSrod ---|| |‘------------+-- name -->

Querying:

>-- Query --+-- SPRef ---.| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| |‘-- HSrod ---+-->



Version 11.3

3-26

3.5 Re-selection of Existing Components and Tube

If a Component or Tube is required to be respecified, you may restate any ofthe Selection commands described elsewhere in this manual. However, eachtime this is done all the non-default Specification entries must be restated,even if most or all of these are identical to the old Specification Component.

The RESELECT command allows the designer to make use of the originalSelection parameters for a Component to simplify the Selection of a newComponent. This is useful for situations where only a single change has takenplace since the original Selection; for example, if the Branch Specification(PSPE attribute) was changed or the nominal bore of a group of Componentshad to be increased.

The RESELECT command operates as follows:

1. Any new Selection parameters are considered (either changed defaults orspecified by the user).

2. If any more parameters are required, they are obtained from the oldSpecification Component.

3.5.1 Re-selecting the New Default Component

Keywords: RESELECTDescription: The RESELECT command chooses a new Component and its Leave

Tube from the Branch Specification. The default Selection parametersare obtained from the current element’s surroundings (in the sameway as for SELECT). If any further Selection parameters are needed,they are obtained from the old Component Specification entries. Theneed to respecify is therefore reduced.

Examples:

RESELThe current element and Leave Tube will be Selected from the new defaultchoice(s). Any parameters required that are not obtainable from defaultswill be derived from the old Specification Component.

Note: This command only operates on Components that have already beenSelected.

Command Syntax:

>-- RESElect -->



3-27

Querying:

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


<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of theDESIGN Reference Manual..

>-- Query --+-- SPRef ---.| |‘-- TUbe ----+-->

3.5.2 General Reselection of Components and Tube

Keywords: RESELECTDescription: This command allows existing Components and Tube to be Reselected

according to new parameters. Where new parameters are not stated oravailable through defaults, they are obtained from the old ComponentSpecification entries.

Examples:

RESEL WITH STYPE BALLThe current element and Leave Tube will be Selected using any defaultparameters and the STYPE specified. Any further parameters required willbe obtained from the old Specification Component.

RESEL WI SPEC /NEWSPECThe current element and Leave Tube will be Selected using the newSpecification and any default parameters. The remaining necessaryparameters will be obtained from the old Specification Component.

RESEL TUBE WI STYPE GLAS (At Branch)The current element HSTU attribute will be Selected using defaultparameters and the specified STYPE. If any further parameters arenecessary they will be obtained from the old Specification Component.



Version 11.3

3-28

Command Syntax:

>-- RESElect --+-- SPref ---.| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| ||-- HSrod ---|| ||-- TUbe ----| .-------<------.| | / |‘-- ROD -----+-- WIth -- *-- SPec <gid> --|

| ||-- <wivl> ------|| ||-- <wiwor> -----’|‘-->

Querying:

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

>-- Q SPECification --*-- <qspci> --+-->

<qspci> is explained in the section on Standard syntax Graphs in Part 1 of theDESIGN Reference Manual.

>-- Query --+-- SPRef ---.| |‘-- TUbe ----+-->

3.6 Standard Component Attributes

This section describes the standard Component element attributes thatprovide their complete logical and physical descriptions. Although you may setthem directly, many of these attributes are automatically determined whenusing the Specification selection and pipe routing commands describedelsewhere.

Two classes of standard attribute exist for Components:

• Those which ‘point’ to a Specification item that provides a fixedCatalogue description of the Component

• Those which cannot be part of the Catalogue description, as they areunique to each occurrence in the Design



3-29

The standard Specification attributes of a Component are:

SPREF This points to a Specification Component that provides thecomplete Catalogue description of the current element.

LSTUBE These point to a Specification Component that provides thecomplete Catalogue LSROD description of the Tubeemerging from the current element Leave Point.

ISPEC This points to an Insulation Specification. The Branch‘TEMPERATURE’ attribute is automatically used todetermine an insulation thickness from this Specification.

TSPEC This points to a dummy Tracing Specification and is used byISODRAFT to indicate trace heating requirements.

The remaining standard attributes are:

POSITION The Component’s position in Zone coordinates (neitherBranch nor Pipe have a POSITION, though Branch hashead and tail positions (HPOS and TPOS).

ORIENTATIONThe Component’s orientation in Zone coordinates (neitherBranch nor Pipe have an ORIENTATION, though Branchhas head and tail directions (HDIR and TDIR).

ARRIVE The Catalogue p-point that is on the Arrive side of theComponent.

LEAVE The Catalogue p-point that is on the Leave side of theComponent.

BUILT Management information to indicate if the item has actuallybeen built.

SHOP (Shop fabrication flag.) Used by ISODRAFT to determine inwhich material list the item is to be shown.

ORIFLAG (Logical orientation flag.) Set and used automatically byPDMS to determine if the Component has been oriented.

POSIFLAG (Logical position flag.) Set and used automatically by PDMSto determine if the Component has been positioned.

The following attributes do not occur in all Components, but are sufficientlycommon to be considered as standard:

ANGLE The (variable) angle of a Component.

HEIGHT The (variable) height of a Component.

RADIUS The (variable) radius of a Component.

LOFFLINE (Logical Offline flag.) Indicates, for reporting purposes,whether the Component breaks the Tube either side of it.



Version 11.3

3-30

CREF (3-way Component Connection Reference.) Indicates theelement that is connected to the third (neither Arrive norLeave) p-point of the Current Element.

CRFA (Multi-way Component Connection Reference.) Indicatesthe elements that are connected to the free (neither Arrivenor Leave) p-points of the Current Element.

3.6.1 Position and Orientation Attributes

Keywords: POSITION ORIENTATIONDescription: The Component position and orientation attributes describe their

location with respect to Zone co-ordinates. This is because neitherBranch nor Pipe have position or orientation attributes and thereforedo not have a co-ordinate system.

Command Syntax:

Component position and orientation are established using the piperouting or ordinary positioning commands described elsewhere.

Querying:

>-- Query --+-- POSition --+-- <bpos> --.| | || ‘------------|| |‘-- ORIentation ------------+-- WRT --.

| ||-- IN ---+-- <gid> -->|‘-->

>-- Query POSition -->

Gives the Component position in ZONE co-ordinates.

>-- Query ORIentation WRT SITE -->

Gives the Component orientation in SITE co-ordinates.



3-31

3.6.2 Component Arrive and Leave Attributes

Keywords: ARRIVE LEAVEDescription: This command sets the attributes that control which p-points are the

Arrive and Leave for a Component. It is usual to set those attributesbefore Selection and Positioning as they can define:

• The automatic Selection Parameters for that item (particularlyREDUCERS)

• The centreline Logical Route that will affect positioning andorientation of the Component.

However, as the p-point details for Arrive (PA) and Leave (PL) areobtained from the Catalogue, these may only be used or interrogatedafter Selection.

Examples:

ARR 2 LEAV 1The Logical Route will Arrive at P2 and Leave at P1 of the Component.

ARR 3 LEAV 2The Logical Route will Arrive at P3 and Leave at P2 of the Component.

Note: Default is Arrive 1, Leave 2.

Command Syntax:

>--+-- ARRive --.| |‘-- LEAve ---+-- P --------.

| |‘-- integer --+-->

3.6.3 Swapping the Arrive and Leave P-points

Keywords: FLIPDescription: This command swaps the Arrive and Leave p-point numbers of a

Component so that it can be ‘Flipped’. It does not actually rotate theComponent until the next orientation command is given. The FLIPcommand can be given before Selection, as the Arrive and Leave p-point numbers are Design attributes independent of the Catalogue.As most Specifications are organised with Reducers having PBOR1larger than PBOR2, the Select mechanism needs to be told that theArrive is at P2 by FLIP Selection. Therefore NEW REDU FLIP SELECTWITH LBORE 100 would be a typical command for a bore increase.



Version 11.3

3-32

When working in BACKWARDS mode, this situation reverses - theREDU need only be Flipped if a bore reduction is required.

Examples:

FLIPReverses the current Arrive and Leave p-point numbers for thatComponent.

Command Syntax:

>-- FLIP -->

Querying:

>-- Query --+-- ARRive --.| |‘-- LEAve ---+-->

PH

PT

P2

P1

LEAVE

ARRIVE

CE

FLIP(ARRIVE 2 LEAVE 1)

Figure 3-5 Component Arrive and Leave attributes (standard and Flipped)



3-33

3.6.4 The Component Specification Reference Attribute

Keywords: SPREFDescription: All Piping Components (including ducting, cable trays and pipe

hangers) obtain their geometries from the PDMS Catalogue through aSpecification. The SPREF (Specification Reference) attribute of theseitems refers to a Specification Component in a chosen ProjectSpecification that obtains its physical dimensions from the Catalogue.If the SPREF is not set, a Valve, for example, is merely a hierarchicalelement and has no geometry.

Examples:

SPREF /SPEC208/EL50BWThe current element is specified by the chosen Specification Component.

Note: This attribute is usually inserted automatically as a direct result ofthe CHOOSE (or SELECT) command. It can, however, be set directly tothe name of the required Specification Component.

Command Syntax:

>-- SPRef name -->

3.6.5 Variable Length Tube (and Rod) Attributes

Keywords: LSTUBE LSROD HSTUBE HSRODDescription: Straight lengths of Tube (ducting, trays and rod) between Components

are not defined as PDMS elements in the hierarchy. Instead, they areextruded from the Leave p-point of a Component to the Arrive p-pointof the next. Their geometric cross-section details are stored in theCatalogue and are pointed at from the Upstream Component via itsLSTU attribute. At the Head of a Branch, there is no UpstreamComponent; therefore a special Branch attribute exists to allow Tubefrom the Head to the first Component to be specified (HSTU).

Generally, you need not be concerned about specifying Tube betweenComponents, as it is automatically determined during the ComponentSelection process described elsewhere. If short fixed-length stubs ofTube are required, it is usually appropriate to create a ComponentFTUB element to ensure that this minimum length is adhered to.Similarly, where Tube changes direction, a Component must beinserted (usually a BEND), as variable length Tube is always straight.



Version 11.3

3-34

Examples:

LSTU /SPEC502/100L (At Branch Component)The Tube between the Leave p-point of this Component and the Arrive ofthe Next (or Tail) is specified by the named Specification Component.

HST /SPEC502/100L (At Branch)As above, but between the Head and Arrive of First Component (or Tail).

LSR /HS20/2.5 (At Hanger Component.)As first example.

HSR /HS20/2.5 (At Hanger Component.)As second example.

Note: These attributes are usually set automatically when the CHOOSE (orSELECT) command is used.

Command Syntax:

>--+-- LSTube --.| ||-- HSTube --|| ||-- LSRod ---|| |‘-- HSRod ---+-- name ----.

| |‘-- NULREF --+-->

Figure 3-6 Variable length Tube between Components



3-35

3.6.6 Insulation Specification Attribute

Keywords: ISPECDescription: This attribute points to an insulation Specification. It is automatically

cascaded down from the Branch ISPE setting, but can also be set onan individual basis. In conjunction with the Branch TEMPERATUREattribute, the ISPE insulates the Component and the Tube from itsLeave point.

Examples:

ISPE /I500-HAVThe Current Component and Tube from its Leave p-point will be insulatedaccording to the named Specification. (The temperature parametersrequired to determine insulation thickness will be obtained from the Branchelement.)

ISP NULREFThe Component and Tube from its Leave p-point will be uninsulated.

Note: If a whole Branch is to be insulated, the Branch ISPE should be setbefore Components are created. This setting will then cascade down toall new Components.

Command Syntax:

>-- ISPec --+-- name ---.| |‘-- NULREF --+-->

Querying:

>-- Query INSUlation -->

Gives the insulation thickness.

3.6.7 Trace Heating Specification Attribute

Keywords: TSPEDescription: This attribute provides ISODRAFT with trace heating information.

The trace heating Specification pointed to is a dummy Specificationdefined in SPECON, having no significance other than its name.

Examples:

TSPE /TR50AThe Current Component will be noted by ISODRAFT with the given traceheating requirements.



Version 11.3

3-36

TSPE NULREFTrace heating is removed.

Note: If the same trace heating is required for an entire Branch, TSPEshould be set at Branch level, from where it will cascade down to allnew Components.

Command Syntax:

>-- TSPec --+-- name ---.| |‘-- NULREF --+-->

3.6.8 The Fabrication Flags

Keywords: SHOP BUILTDescription: These attributes indicate the location and status of construction of

each Component. The SHOP flag is used by ISODRAFT to determinein which material list the item will appear. The BUILT flag canindicate whether or not the Component has been fabricated/builtduring construction.

Examples:

SHOP TRUEThe current element will be itemised as ‘SHOP FABRICATED’ inISODRAFT.

BUILT FALSEInformation attribute indicating that current element has not been built.

Command Syntax:

>--+-- SHOP ---.| |‘-- BUIlt --+-- TRue ---.

| |‘-- FALse --+-->



3-37

3.6.9 Position and Orientation Status Flags

Keywords: ORIFLAG POSFLAGDescription: These attributes are automatically set to TRUE when the Component

is positioned and orientated. They are used by DESIGN in severalsituations where it requires to know if a Component has been properlypositioned.

Examples:

POSF FALSEThis setting will occur if the Components have been transferred from aP&ID and not positioned. The Component will not be drawn in the views.

ORIF FALSE POSF TRUEThis setting will occur if the item has been Selected in DESIGN but notoriented.

ORIF TRUE POSF TRUEAfter the Component is oriented it will be shown in normal line type.

Note: If either POSFLAG or ORIFLAG remains FALSE, the nextComponent cannot be positioned using ordinary routing commands.

Command Syntax:

These attributes are set automatically by DESIGN when positioning andorientation takes place. However, they can be set explicitly as follows:

>--+-- ORIFlag --.| |‘-- POSFlag --+-- TRue ---.

| |‘-- FALse --+-->

Querying:

>-- Query --+-- POSFlag --.| |‘-- ORIFlag --+-->



Version 11.3

3-38

3.6.10 Variable Component Attributes

Keywords: ANGLE HEIGHT RADIUS DESPARAMETERSDescription: Some Components have variable dimensions that must be specified in

situ by the designer. Once a Component has been selected from theSpecification, altering, say, the ANGLE may change its physicalappearance.

Although many Component elements possess the ANGLE, HEIGHT orRADIUS attributes or use Design Parameters, it is the Cataloguethat determines whether the value of these attributes will affect thephysical Component. For example, changing the ANGLE attribute of a90-degree fixed-angle elbow to 45 degrees will have no effect. In somecases, the variable value may be difficult to determine. For instance, aBEND in a pipe may possess an angle resulting from an obliquechange in direction. In such instances, the DIRECTION command(described elsewhere) can be used to determine the ANGLE settingautomatically.

The ANGLE, HEIGHT and RADIUS attributes can also be set beforeselection as a means of choosing between, say, 90-degree or 45-degreefixed-angle elbows.

Examples:

ANGL 45 (Before Selection)When the CHOOSE (or SELECT) command is given, it will choose the‘ANGLE45’ option if available in the Specification.

HEIG 300 (After Selection)If a variable height component, this dimension will alter as specified.

Command Syntax:

>-- ANGle --+-- <uval> -----------------.| |‘-- <bdir> TOwards <bdir> --+-->

>-- HEIght <uval> -->

>-- RADius <uval> -->

>-- DESParameters <uval> -->



3-39

3.6.11 Offline/Straight-Through Component Attribute

Keywords: LOFFDescription: This attribute controls whether a Component is considered to be ‘in-

line’ or ‘off-line’. If it is off-line, the reporting utility will treat it as acontinuous part of the Tube either side of the Component and will onlyreport one pipe length. This is useful for BENDS (bends in continuousTube) and OLETS (which tap off the side of a piece of Tube). If theComponent is left as in-line, the Tube will be split into two sectionswith no account being taken of the Arrive-to-Leave length of theComponent.

Examples:

LOFF FALSEIn the reporting utility, the current element will be treated as a fullComponent which breaks the Tube lengths either side.

OFFL TRUEIn the reporting utility, the current element will be included as part of asingle Tube length running through its Arrive-to-Leave centreline.

Note: The default setting for this attribute is dependent upon Componenttype.

Command Syntax:

>--+-- LOFFline --.| |‘-- OFFLine ---+-- TRue ---.

| |‘-- FALse --+-->

3.6.12 Multi-Way Component Attributes

Keywords: CREF CRFADescription: In addition to Arrive and Leave p-points, some Components have

further p-points which can become the ends of other Branches. Forthree-way Components (e.g. TEE), the attribute CREF (ConnectionReference) is used to show which Branch is connected to the free p-point. This is usually set automatically as a result of a CONNECTcommand, but it may also be set explicitly. For Components with morethan three p-points (e.g. CROSS), the attribute CRFA stores thenames of up to 10 Branches which connect to this item. Although aDesign Component element can possess a CREF or CRFA attribute, it



Version 11.3

3-40

is the Catalogue which controls whether the item can actually beconnected to by other Branches.

Examples:

CREF /PIPE1 TAILSets CREF of current element to point to Tail of /PIPE1 and sets TREF of/PIPE1 to point back to the current element.

CREF NULREFUnsets CREF; i.e. disconnects this point from any other element.

Command Syntax:

>-- CREF --+-- <gid> --+-- HEAD --.| | || |-- TAIL --|| | || ‘----------+| |‘-- NULREF -------------+-->

Querying:

>-- Query --+-- CREf --.| |‘-- CRFA --+-->

3.7 Orientation and Connection of Components

Orientation and Connection commands make use of the constrained centrelineof a Pipe route. When a Component is Selected, it is automatically positionednext to the adjacent Component so that it can be seen. However, it is essentialin DESIGN that the item is either oriented or Connected. DESIGN insists onthis minimum to ensure that each Component is deliberately manipulated bythe user.

All the examples in this section assume Forwards routing mode is in operation.Generally, if Backwards is being used, then the effect of these commands willlogically reverse.



3-41

3.7.1 Component Orientation

Keywords: ORIENTATEDescription: This command rotates the Component about its origin so that (in

forwards mode) the Arrive p-point is in the opposite direction to theprevious Component’s Leave p-point.

If the Component is not concentric, it is necessary to specify the off-line orientation as well. This is usually done by giving the direction ofan off-line p-point. If it is not possible to achieve an orientationbecause of the direction of the constrained centreline, DESIGN willleave this off-line direction in the closest orientation to that requested.

Examples:

ORI Rotate the current element about its origin so that (in forwards mode)its Arrive Point is in the opposite direction to the previous Component’sLeave Point (see Figure 3-7).

ORI AND P3 IS UAs above, and orient the off-line p-point (P3) in the specified direction (seeFigure 3-8).

Note: The ORIENTATE command will not change the ANGLE, RADIUS etc.of a variable Component to accommodate an oblique off-line direction.

Command Syntax:

>- ORIentate -+- <bdir> IS <bdir> -.| |‘--------------------+- AND <bdir> IS <bdir> -.

| |‘------------------------+-->

Querying:

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

>-- Query <marke> --*-- DIRection --. || | |‘---------------+-- WRT --. |

| | ||-- IN ---+-- <gid> --’|‘-->



Version 11.3

3-42

Figure 3-7 Orienting a Concentric Component

Figure 3-8 Orienting a non-concentric Component by means of an off-line p-point



3-43

3.7.2 Direction-Changing Components

Keywords: DIRECTIONDescription: The DIRECTION command orients the Component along the

constrained centreline and points the specified p-point in a newdirection. Unlike the ORI command, if that new direction requires achange in the ANGLE of a variable-angle Component (e.g. a BEND),this will automatically be adjusted. The ability of a Component toadjust in this way is controlled by the Catalogue.

Examples:

DIR ERotate the Component about its origin such that (in forwards mode) itsArrive point is in the opposite direction to the previous Component’s leavepoint, and its leave point is East. If this requires a change of angle and theComponent has a variable ANGLE attribute, then this will be altered to suit(see Figure 3-9).

DIR AND P3 IS U45EAs above, but P3 (rather than PL) is pointed to the new direction (seeFigure 3-9).

Note: If the new direction cannot be adopted by a fixed-angle Component,the item will be pointed in the closest direction to that specified.

Command Syntax:

>-- DIRection --+-- AND <marke> IS --.| |‘--------------------+-- <bdir> -->

Querying:

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

>-- Query <marke> --*-- DIRection --. || | |‘---------------+-- WRT --. |

| | ||-- IN ---+-- <gid> --’|‘-->



Version 11.3

3-44

Figure 3-9 Changing the direction of variable-angle Components



3-45

3.7.3 Component Connection

Keywords: CONNECTDescription: This command places a p-point on the current Component face-to-face

with the p-point of an adjacent Component. If the Connection Types ornominal bores of the Connected faces are not compatible, DESIGNautomatically Flips (reverses Arrive and Leave) the Component andtries again. If the adjacent element is an Attachment Point (ATTA)then this is ignored and Connection is attempted on the NextComponent.

Examples:

CONNECTThe arrive p-point of the Component is connected to theleave p-point of the Previous Component (see Figure 3-10).

CONNECT TO NEXTThe leave p-point of the Component is connected to the arrive p-point of thenext Component (see Figure 3-10).

CONNECT AND P3 IS UAs first example and the off-line p-point is oriented upwards (see Figure 3-10).

Note: Only adjacent Components (not Attachment Points) may be connectedto; if Connection Types or bores are incompatible, then an automaticFLIP takes place and CONNECT is attempted again.

Command Syntax:

>- CONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> ->| | || | ‘-->| ‘-->‘-->

Querying:

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

>-- Query <marke> --*-- POSition --. || | |‘--------------+-- WRT --. |

| | ||-- IN ---+-- <gid> --’|‘-->



Version 11.3

3-46

Figure 3-10 Component connection

3.7.4 Forced Component Connection

Keywords: FCONNECTDescription: This operates exactly as the CONNECT command, but ignores

Connection and Bore compatibility. The Component will be shownfully positioned, but data consistency checking will still reportincompatible connections unless the items are moved apart later.

Examples:

FCONNThe Arrive p-point of the Component is force-connected to the Leave p-pointof the previous Component.

FCONN TO TAILThe Leave p-point of the Component is force-connected to the Tail.

FCONN AND P3 IS UAs first example and the off-line p-point is oriented upwards.



3-47

Note: Only adjacent Components (not Attachment Points) may be force-connected. No check on compatibility of bore or Connection Typeoccurs.

Command Syntax:

>- FCONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> -->| | || | ‘-->| ‘-->‘-->

3.8 Moving by a Known Distance

These commands move the Component a specified distance along theconstrained centreline. All the commands move the Component from itscurrent position. The distance moved may either be measured along theconstrained centreline or some other planar direction. All the examples in thissection assume Forwards routing mode is in operation. Generally, ifBackwards is being used, then the effect of each command will be logicallyreversed.

3.8.1 Moving Components

Keywords: MOVE DISTANCEDescription: This command moves the Component along the constrained centreline

by a specified distance.

Examples:

MOVE DISTANCE 1000The Current Component is moved from its present position 1000 along theconstrained centreline (see Figure 3-11).

Note: A positive dimension moves the Component away from the PreviousComponent.

Command Syntax:

>-- MOVe DISTance <uval> -->



Version 11.3

3-48

Querying:

>-- Query POSition <bpos> --+-- WRT --.| ||-- IN ---+-- <gid> -->|‘-->

Figure 3-11 Moving a Component by a given distance

3.8.2 General Moving of Components

Keywords: MOVE PLANE DISTANCEDescription: This command moves the Component along the constrained centreline.

The distance moved may be specified either in the direction moved oranother planar direction.

Examples:

MOVE PLANE N45E DIST 1000The current Component is moved from its present position along theconstrained centreline by 1000 along the N45E direction (see Figure 3-12).

Command Syntax:

>-- MOVe PLAne <bdir> DISTance <uval> -->

Querying:

>-- Query POSition <bpos> --+-- WRT --.| ||-- IN ---+-- <gid> -->|‘-->



3-49

Figure 3-12 Moving a Component by a distance specified in another plane

3.9 Positioning Components using Reference Planes

This section describes commands that position the Component on theconstrained centreline at the intersection with a fixed reference plane.

Any p-point on the Component may be used, although the default is the origin.This point is positioned along the constrained centreline through the referenceplane which is defined by the 3D position through which it passes. Theorientation of the reference plane defaults to perpendicular to the constrainedcentreline, although a different planar direction can be specified.

In no case is the volumetric geometry of the 3D model considered. Thesecommands are therefore not suitable for ‘clearance’ positioning.

All the examples in this section assume Forwards routing mode. Generally, ifBackwards is being used, then the effect of each command will be logicallyreversed.

3.9.1 Positioning with respect to the Previous Component

Keywords: DISTANCE POSITIONDescription: This command positions the Component on the constrained centreline

at a specified distance from the origin of previous Component. Any p-point on the current element may be used, the default being the origin.



Version 11.3

3-50

Examples:

DIST 1000The Component will be positioned on the constrained centreline 1000 fromthe origin of the previous Component (see Figure 3-13a).

POS PA DIST 1000As above, but the Arrive point of the Component is used (see Figure 3-13b).

Command Syntax:

>--+-- POSition <marke> --.| |‘----------------------+-- DISTance <uval> -->

Querying:

>-- Query --+-- POSition --.| |‘--------------+-- <marke> --+-- WRT --.

| ||-- IN ---+-- <gid> -->|‘-->

Figure 3-13 (a) Positioning with respect to Previous Component



3-51

Figure 3-13(b) Positioning with respect to Previous Component

3.9.2 Positioning the Component through an Intersection

Keywords: THROUGH POSITIONDescription: This command allows the designer to position the Component through

the intersection with a fixed design element or position (say a Nozzle)or a cursor position. The Component is positioned along theconstrained centreline where the reference plane intersecting, say, thespecified Nozzle, cuts at right angles. For cursor positioning it istherefore advisable to use orthogonal views for orthogonal piping.

Examples:

POS THR /TANK5The origin of the current Component will be positioned on the constrainedcentreline where this intersects the perpendicular reference plane throughthe named element (see Figure 3-14).

POS PA THR E3000The Arrive point of the current Component will be positioned on theconstrained centreline where the perpendicular reference plane throughE3000 N0 U0 intersects (see Figure 3-15a).

THR @ The Component will be placed on the constrained centrelinewhere the perpendicular reference plane indicated by the cursorintersects (see Figure 3-15b).



Version 11.3

3-52

NOTE: The reference plane is perpendicular to the constrained centreline. Ifthe cursor is used, the position will be located on the working gridnearest to the cursor.

Command Syntax:

>--+-- POSition <marke> --.| |‘----------------------+-- THRough <bpos> -->

Querying:

>-- Query --+-- POSition --.| |‘--------------+-- <marke> --+-- WRT --.

| ||-- IN ---+-- <gid> -->|‘-->

Figure 3-14 Positioning through an intersection



3-53

Figure 3-15(a) Positioning through an intersection

Figure 3-15(b) Positioning through an intersection

3.9.3 Positioning with respect to an Intersection

Keywords: POSITION DISTANCE FROM TODescription: This command positions the current Component so that its origin (or

specified p-point) intersects the reference plane either side of thespecified fixed position.



Version 11.3

3-54

Examples:

DIST 50 FROM /TANK5The Component will be moved along the constrained centreline until itsorigin is 50 beyond the perpendicular plane through the named element (seeFigure 3-16).

DIST 1000 TO NEXTThe Component will be placed on the constrained centreline so that its originis 1000 before of the Next Component’s origin (see Figure 3-17a).

POS PA DIST 20 FROM PL OF PREVThe Component will be placed on the constrained centreline so that its Arrivepoint is 20 from the previous Component’s Leave point (see Figure 3-17b).

Note: The reference plane is perpendicular to the constrained centreline. TOmeans closer to the Previous Component than the reference plane.FROM means further from the previous Component than the referenceplane.

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- DISTance <uval> -+- FRom -.

| |‘- TO ---+- <bpos> ->

Querying:

>-- Query <marke> --+-- POSition --.| |‘--------------+-- WRT --.

| ||-- IN ---+-- <gid> -->|‘-->



3-55

Figure 3-16 Positioning with respect to an intersection

Figure 3-17a Positioning with respect to an intersection



Version 11.3

3-56

Figure 3-17b Positioning with respect to an intersection



3-57

3.9.4 General Positioning through an Intersection

Keywords: POSITION PLANE DISTANCE THROUGH FROM TODescription: This command differs from the basic options by allowing the reference

plane to be specified independently of the constrained centreline. Thisis particularly relevant for routing sloping lines where a specificEasting or Northing is to be intersected.

Examples:

PLANE E DIST 1000The Component will be placed on the constrained centreline so that itsorigin is 1000 from the previous Component’s origin in an East/Westdirection (see Figure 3-18).

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- PLANe <bdir> -+- DISTance <uval> -+- FRom -.

| | || ‘- TO ---+- <bpos> ->|‘- THrough <bpos> ->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

3-58

Figure 3-18 Positioning through an intersection defined in an independentplane

3.10 Positioning Components ‘Point-to-Surface’

This section describes commands which position a Component on theconstrained centreline at a specified distance from the surface of a fixeddesign item.

Any p-point on the current element may be used for the manoeuvre, althoughthe default is the origin. In no case is the geometry of the current elementconsidered. However, the geometry of the referenced item is considered in oneof three ways:

• If the item is a Design element, then its complete geometry will beconsidered.

• If the item is a Piping p-point at the Arrive or Leave of anotherComponent, then the Tube cross-section at that point will be considered.

• If the item has no geometry, i.e. a non-piping p-point, or is a position,then only that point will be considered.

All the examples in this section assume Forwards mode. Generally, ifBackwards mode is being used, the effect of each command is logicallyreversed.



3-59

3.10.1 Positioning Components either side of an Object

Keywords: POSITION DISTANCE INFRONT BEHINDDescription: This command positions the Component on the constrained centreline

at a specified distance from a geometric object, point or position.

Examples:

DISTANCE 30 INFRONT /WALLThe Component will be placed on the Constrained Centreline so that itsorigin is 30 ‘this side’ of the specified object (see Figure 3-19 and Figure 3-20).

DISTANCE 125 BEHIND IDP @The Component will be placed such that its origin is 125 the ‘other side’ ofthe picked p-point. If this point is an Arrive or Leave, then the Tube cross-section will be taken into account (see Figure 3-20).

POS PL INF /ACCESSThe Component will be placed such that its Leave Point is zero distance‘this side’ of the specified object (see Figure 3-20).

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- DISTance <uval> -+- INFront -.

| |‘- BEHind --+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



Version 11.3

3-60

Figure 3-19 Positioning Components either side of an object



3-61

Figure 3-20 Positioning Components relative to a specified object



Version 11.3

3-62

3.10.2 Positioning Components On Top of or Under an Object

Keywords: POSITION DISTANCE ONTOP UNDERDescription: This command positions the Component on the constrained centreline

at a vertical distance above or below a fixed geometric object. Thistakes into account the shape of the referenced object, but not of thecurrent element.

Examples:

DISTANCE 35 ONTO /BEAMThe Component will be placed on the Constrained Centreline so that itsorigin is 35 above the specified object (see Figure 3-21).

DISTANCE 125 UNDER IDP @The Component will be placed on the Constrained Centreline so that itsorigin is 125 below the picked point. If this point is an Arrive or Leave, thenthe Tube cross-section will be taken into account (see Figure 3-21).

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- DISTance <uval> -+- ONTop -.

| |‘- UNDer -+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



3-63

Figure 3-21 Positioning above/below an object



Version 11.3

3-64

3.10.3 General Component Positioning Using Planes

Keywords: POSITION PLANE DISTANCE INFRONT BEHIND ONTOPUNDER

Description: This command differs from the basic options by allowing the referenceplane to be specified in a different direction from that of theconstrained centreline.

Examples:

PLANE E DIST 1000 INFRONT /WALLThe Component will be placed on the constrained centreline such that itsorigin is 1000 ‘this side’ of /WALL, measured East-West (see Figure 3-22).

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- PLAne <bdir> -.

| |‘----------------+- DISTance <uval> -+- ONTop ---.

| ||- UNDer ---|| ||- INFront -|| |‘- BEHind --+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| ||-- IN ---+-- <gid> -->|‘-->



3-65

Figure 3-22 Positioning relative to an object specified in a different plane



Version 11.3

3-66

3.11 Component Clearance Positioning

The commands in this section position the Component on the constrainedcentreline to give a specified clearance distance from a fixed design item.

The clearance specified usually takes into account both the current elementand referenced element geometric shapes. However, the following rules alsoapply:

• If the current element or referenced element is used and has a geometricshape, then this is considered.

• If an Arrive or Leave p-point on the current element or referencedelement is used, then the Tube cross-sectional geometry at that point isconsidered (not the Component geometry).

• If the current element or referenced element has no geometry, or a p-point is used that is not an Arrive or Leave, or a position is used, thenonly the position is considered.

A selection of Bottom of Pipe (BOP) commands are also available that provideclearance for the Tube cross-section at a Component Leave Point. All theexamples in this section assume Forwards routing mode. If Backwards is inuse, then the effect of each command is logically reversed.

3.11.1 Clearance from the Previous Component

Keywords: CLEARANCEDescription: This command places the Component at a specified clearance from the

previous Component on the constrained centreline. The wholegeometry of both Components is considered.

Examples:

CLEA 500The Component will be placed on the constrained centreline 500 clear of thePrevious Component (see Figure 3-23).

Command Syntax:

>-- CLEArance <uval> -->



3-67

Querying:

>-- Query <marke> --+-- POSition --.| ||-- BOP -------|| |‘-- TOP -------+-- WRT --.

| |‘-- IN ---+-- <gid> -->

Figure 3-23 Clearance from a Previous Component



Version 11.3

3-68

3.11.2 Component Clearance Either Side

Keywords: CLEARANCE INFRONT BEHINDDescription: This command places the current Component on the constrained

centreline at a specified clearance in front of or behind a fixed designobject. If the Arrive or Leave point of the referenced object is used,then the Tube cross-section at this point is considered rather than thefull item geometry.

Examples:

CLEAR BEHIND /WALLThe Component will be placed on the constrained centreline with zeroclearance on the ‘far side’ of the specified element (see Figure 3-24).

CLEAR 1200 INF PL OF NEXTThe Component will be placed on the constrained centreline with 1200clearance ‘this side’ of the Tube emerging from the Component’s Leave point(see Figure 3-24).

Command Syntax:

>-- CLEArance --+-- <uval> --.| |‘------------+-- INFront --.

| |‘-- BEHind ---+-- <gid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

Querying:


| |‘-- IN ---+-- <gid> -->



3-69

Figure 3-24 Component clearance either side of a fixed object



Version 11.3

3-70

3.11.3 Component Clearance Vertically

Keywords: CLEARANCE ONTOP UNDERDescription: This command places the current Component on the constrained

centreline at a specified vertical clearance above or below a fixedobject. If the Arrive or Leave point of the referenced object is used,then the Tube cross-section emerging at this point is considered ratherthan the full item geometry.

Examples:

CLEARANCE ONTO /BEAMThe current Component will be placed on the constrained centreline at zeroclearance above the specified object (see Figure 3-25).

CLEARANCE 50 UNDER /BEAMThe current Component will be placed on the constrained centreline at 50vertical clearance below the specified object (see Figure 3-25).

CLEAR 50 ONTO IDP @The current Component will be placed on the constrained centreline at aclearance of 50 vertically above the picked p-point. If this p-point is anArrive or Leave, then the Tube cross-section will be taken into account (seeFigure 3-25).

Command Syntax:

>-- CLEArance --+-- <uval> --.| |‘------------+-- ONTop --.

| |‘-- UNDer --+-- <gid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

Querying:


| |‘-- IN ---+-- <gid> -->



3-71

Figure 3-25 Component clearance above/below a fixed object



Version 11.3

3-72

3.11.4 Tube (Bottom of Pipe) Clearance

Keywords: BOP TOP ONTOP UNDER INFRONT BEHINDDescription: This command places the current Component on the constrained

centreline so that the Tube cross-section at its Leave point is aspecified clearance from another fixed object. The clearance can eitherbe specified as a dimension along the constrained centreline in-front-of/behind the object or vertically on top/under it. If the Arrive or Leavepoints of the fixed object are used, then its Tube cross-section will alsobe considered. Using this command, pipes can be spaced on the beamsof a rack by Tube-to-Tube clearance.

Examples:

BOP ONTO /BEAMThe Component will be positioned on the constrained centreline so that theTube emerging from its Leave point is zero clearance above /BEAM (seeFigure 3-26a).

BOP 30 BEHIND /FLANThe Component will be positioned on the constrained centreline so that theTube emerging from its Leave point is 30 clear of the ‘far side’ of /FLAN (seeFigure 3-26a).

BOP 30 BEHIND PL OF /FLANAs above, but 30 to the far side of the Leave Tube of /FLAN (see Figure 3-26b).

Command Syntax:

>--+-- BOP --.| |‘-- TOP --+-- <uval> --.

| |‘------------+-- FROm --.

| ||-- TO ----+-- <bpos> -->||-- ONTop ----.| ||-- UNDer ----|| ||-- INFront --|| |‘-- BEHind ---+-- <gid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

Note: The meanings of BOP and TOP in this context are identical. They aremerely provided to allow a sensible choice of syntax.



3-73

Querying:


| |‘-- IN ---+-- <gid> -->

Figure 3-26a Tube clearance relative to a fixed object



Version 11.3

3-74

Figure 3-26b Tube clearance taking into account the Tube diameter

3.11.5 General Clearance of Components and Tube

Keywords: POSITION PLANE CLEARANCE INFRONT BEHIND ONTOPUNDER

Description: This command differs from the basic options in two respects:

• The clearance dimension can be in an independent plane fromthe constrained centreline.

• The current element Arrive or Leave Tube can be used (similarto BOP) rather than the whole element geometry.

Examples:

PLANE E CLEARANCE 1000The current Component will be placed on the constrained centreline so that itis 1000 clear of the Previous Component in an East-West direction (seeFigure 3-27).

POS PL CLEAR 100 ONTO /BEAMThe current Component will be placed on the constrained centreline so thatthe Tube from its Leave Point is 100 vertically above /BEAM (same as BOP)



3-75

Command Syntax:

>-+- POSition <marke> -.| |‘--------------------+- PLAne <bdir> -.

| |‘----------------+- CLEARance <uval> -+- ONTop ---.

| ||- UNDer ---|| ||- INFront -|| |‘- BEHind --+- <gid> --.

| ||- <marke> -|| |‘- <bpos> --+->

Querying:


| |‘-- IN ---+-- <gid> -->



Version 11.3

3-76

Figure 3-27 Component clearance specified relative to an independent plane



3-77

3.12 Dragging Equipment and Piping Networks

If equipment is repositioned using ordinary positioning commands, the pipesconnected to it do not automatically move with the item.The DRAG commandis used to move Constrained Networks of Piping, Equipment and Nozzleelements all together. How the constrained network is created depends on thedirection of the dragging operation and the type of item being dragged.

When a DRAG command is given, the current element is displayed normally,together with the constrained network. This network finishes where a legalend is found.

Items that can be dragged are:

• Piping Components.In this case the network is formed by searching outwards in all directionsfrom the component until a legal end is found for each ‘leg’ of thenetwork.

• Nozzles.The piping network connected to the Nozzle is searched for legal ends.

• Equipment.The piping networks connected to all Nozzles owned by the equipmentare searched for legal ends.

A legal end for a constrained network can be:

• A piece of tube that can be extended parallel to the displacement

• A piece of tube that can be compressed parallel to the displacementwithout becoming negative in length

• A Nozzle

• A point between two mis-aligned components

• A point between two incompatibly-connected components

• Any component that has not yet been positioned and orientated

• Any element in a design area that cannot be modified due to thedesigner’s access rights

In some instances, the DRAG operation may fail to establish a constrainednetwork. This may be because:

• The internal search limit has been reached

• A LOCKED element has been found in the network



Version 11.3

3-78

3.12.1 Dragging Equipment and Nozzles

Keywords: DRAG AT BY POSITION MOVEDescription: This command repositions the current element and constrained

network to the specified position. The DRAG command can be followedby any standard Equipment and Civils positioning or movingcommand.

Examples:

DRAG AT E3000The current element and constrained network will be dragged to thespecified position.

DRAG BY N500 U500The current element and constrained network will be dragged by thespecified amount.

DRAG MOVE E2000The current element and constrained network will be moved to the specifiedposition.

DRAG MOVE N CLEAR 1000 INF /BUILD10The current element and constrained network are moved North to thespecified clearance in front of element /BUILD10.

Command Syntax:

The full DRAG command syntax is extensive but may be summarised asfollows:

>-- DRAG --+-- <absol> --.| |‘-- <relat> --+-->

where<absol> defines any absolute positioning command, e.g. AT, POS,

etc.<relat> defines any relative positioning command, e.g. BY,

MOVE, etc.

The full expanded syntax is given below for reference:

<absol> = >--+-- AT --+-- <bpos> ---.| | || ‘-- <polar> --|| ||-- <pppos> --. || | |‘-- <polar> --+--------+-->



3-79

<polar> = >--+-- POLar <bdir> --.| |‘------------------+-- <plane> -->

<pppos> = >-- POSition --+-- <marke> --+-- AT --+-- <bpos> ---.| | | || | ‘-- <polar> --|| | || ‘-- <polar> -----------|| ||-- AT --. || | |‘--------+-- <bpos> ---. |

| | |‘-- <polar> --+-------------+-->

<plane> = >-+- PLAne <bdir> -+- DISTance <uval> -+- <repla> ------.| | | || | ‘----------------|| | || |- <repla> --------------------------|| | || |- THRough <bpos> -------------------|| | || ‘- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -|| | || |- <planf> -|| | || ‘-----------||- DISTance - <uval> -+- <repla> -. || | | || |- <planf> -| || | | || ‘-----------+-------------------|| ||- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -. || | | || |- <planf> -| || | | || ‘-----------+----------------|| ||- <repla> -------------------------------------------|| ||- THRough <bpos> ------------------------------------|| |‘- <planf> -------------------------------------------+>



Version 11.3

3-80

<repla> = >--+-- INFront --.| ||-- BEHind ---+-- <sgid> ---.| | || |-- <marke> --|| | || ‘-- <bpos> ---|| ||-- FROm --. || | |‘-- TO ----+-- <bpos> ------+-->

<planf> = >--+-- ONTop --.| |‘-- UNDer --+-- <sgid> ---.

| ||-- <marke> --|| |‘-- <bpos> ---+-->

<relat> = >--+-- BY <pos> --+-- WRT --.| | || |-- IN ---+-- <sgid> --.| | || ‘----------------------|| |‘-- <relmo> --------------------------+-->

<relmo> = >- MOVe -+- <marke> -+- ALOng -.| | || |---------+- <bdir> <plane> ----.| | || |- BY <pos> -+- WRT -. || | | | || | ‘- IN --+- <sgid> -|| | || ‘- <plane> ---------------------|| ||- ALOng -. || | ||---------+- <bdir> <plane> ----------------|| ||- BY - <pos> -+- WRT -. || | | || ‘- IN --+- <sgid> -----------|| |‘-- <plane> --------------------------------+->



3-81

Figure 3-28 Dragging Equipment and Nozzles by a specified amount

Figure 3-29(a) Dragging Equipment and Nozzles to a specified position



Version 11.3

3-82

Figure 3-29(b) Dragging Equipment and Nozzles to a specified position

3.12.2 Dragging Piping

Keywords: DRAG AT BY POSITION MOVE DISTANCE THROUGH FROM TO CLEARANCE INFRONT BEHIND ONTOP UNDER

Description: This command is identical to the DRAG command described in theprevious subsection except that, if the current element is a Branch,the bottom/top of piping positioning syntax can be used.

Examples:

DRAG THRO @The current element and constrained network are moved along theconstrained centreline until the origin of the current element lies on areference plane which passes through the cursor position.

DRAG MOVE S DISTANCE 1000The current element and constrained network are moved South by thespecified distance.

DRAG DISTANCE 1000 ONTO /GRADEThe current element and constrained network are dragged so that the originof the current element is 1000 above /GRADE.

DRAG BOP ONTO /BEAM2-1 CLEAR 150The current (Branch) element and constrained network are dragged so thatthe Tube will be positioned on top of /BEAM2-1 with a clearance of 150.



3-83

Note: As it changes orientation as well as position, CONNECT cannot beused in conjunction with DRAG.

Command Syntax:

>-- DRAG --+-- <absol> --.| ||-- <relat> --|| |‘-- <botop> --+-->

<botop> = >--+-- BOP --.| |‘-- TOP --+-- <uval> --.

| |‘------------+-- <repla> --.

| |‘-- <planf> --+-->

Figure 3-30(a) Dragging Piping to a specified position



Version 11.3

3-84

Figure 3-30(b) Dragging Piping to a specified position

Figure 3-31 Dragging Piping to a given distance from a fixed object


4 Automatic Pipe Routing

The automatic pipe-routing facilities of DESIGN enable simple orthogonal piperoutes to be generated automatically. Additionally, a number of pipes can beordered and spread across pipe racks once the provisional routes have beendetermined.

In its simplest form, a single Branch may be routed from one point to another,by setting the head and tail positions and using the route command. In a morecomplex role, these facilities can be used to route a complex set of pipes,avoiding obstructions and following preferred paths.

For more complex pipe routing, Ptrac, Pvol and Rplane elements may be usedto steer the automatic routing process along preferred areas. These must becreated and positioned before entry to automatic routing, because theautoroute process operates with restricted command syntax, which does notallow elements to be created.

4.1 Accessing the Automatic Pipe Routing Facilities

The automatic pipe routing facilities are set aside from the rest of the DESIGNcommands in a separate command structure called Autoroute Mode.

4.1.1 Entering and Leaving Autoroute Mode

Keywords: AUTOROUTE EXITDescription: The AUTOROUTE command is used to enter the automatic pipe-

routing facilities. Once in autoroute mode, the command syntax isrestricted to those commands necessary for automatic routing andrack ordering. To return to the full DESIGN syntax, the EXITcommand is used.

Examples:

AUTOROUTEEnters Autoroute mode

EXITReturns to the full DESIGN syntax

Automatic Pipe Routing


Version 11.3

4-2

4.2 Pipe Routing

Pipe routing may be simple and direct, or it may be precisely defined,according to the constraints and preferences you set. The autoroute processcreates a centreline route using Elbows or Bends which are created during theautoroute operation.

The simplest route is one with no constraints, which will result in the shortestpossible route, ignoring all other elements in the database. By addingconstraints, you can force the automatic routing process to consideralternatives and avoid obstructions.

The pipes to be routed must contain empty Branches whose Head and Tailreferences are correctly set. The constraints which can be applied are asfollows:

• Obstruction Elements such as Equipment items and Structures maybe defined as obstructions which must be avoided by the automaticrouting process.

• Penalty Volumes - Denote, by means of weighting factors, volumes inspace which can be either preferred or prohibited areas for pipe routing.Penalty Volumes are created as PVOL elements in the Design database,The WEIGH attribute is used to determine whether the PVOL is aprohibited or preferred area according to its value. High values indicateprohibited areas, low values indicate a preferred area.

Example:

WEIGH 100 .01 100Indicate that the X and Z axes are prohibited and the Y axis is preferred.

• Routing Planes - Routing Planes are elements which are used to guidethe automatic routing mechanism into preferred areas. For example, if arack was to be positioned between two rows of vessels an RPLANEelement would be created along the centreline of the proposed rack.Without the RPLANE element, the autoroute process would route thetwo rows of pipes either side of the preferred area, rather than down themiddle.

4.2.1 Routing Pipes along Preferred Axes

The automatic pipe routing process will only route pipes orthogonally.However it may follow an axis system other than those of the world. Beforeany routing can take place, the required axis system must be defined.

Keywords: AXESDescription: All pipe routing will be orthogonal to the axes defined by the AXES

command. This may be taken as the current axes of any element in the



4-3

database, but it must be orthogonal with the Nozzles and pipe headdirections which are being considered.

Example:

AXES /ZONE1The routing axes will be set to the axes of /ZONE1

Command Syntax:

>-- AXes <sgid> -->

4.2.2 Setting Routing Planes

Keywords: RPLANEDescription: The RPLANE command sets up the list of elements which are to be

considered as routing planes.

Examples:

RPLANE /PTRAC1Sets /ZONE1 as an element in the Routing Plane list. All RPLAN elements,in the hierarchy below /ZONE1 will be considered.

RP /RP1 /RP2Adds /RP1 and /RP2 to the list. A maximum of 150 RPLAN elements may beconsidered by the automatic routing process.

RP Clears the list of Routing Planes.

Command Syntax:

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

>-- RPlanes --*-- <sgid> --+-->

4.2.3 Setting Penalty Volumes

Keywords: PVOLDescription: The PVOL command sets the list of penalty volumes which will be

considered during the automatic routing process.

Examples:

PVOL /PV1Adds /PV1 into the list of Penalty Volumes. If the element being added isnot a PVOL, then all items below it in the hierarchy are scanned.



Version 11.3

4-4

PV /PZONE1 /PZONE2Adds /PZONE1 and /PZONE2 to the list. A maximum of 1000 PVOLS maybe considered during automatic routing.

PV Clears the list of Penalty Volumes.

Command Syntax:

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

>-- PVolumes --+--*-- <sgid> --+-->|‘-->

4.2.4 Invoking the Automatic Routing Process

Automatic pipe routing can be invoked by issuing the ROUTE command with alist of Pipes to be routed. The Pipes to be routed must have empty Branches,with Head and Tail references set.

Keywords: ROUTEDescription: The ROUTE command begins the procedure of finding logical routes

for all of the branches included in the routing list. Each time asuccessful route has been found, a message is output stating the totalPipe length and the number of Elbows used. During the routingprocess, Elbows are selected automatically from the Pipe Specificationby default. Bends may be selected in preference to Elbows byspecifying this option as part of the ROUTE command.

Examples:

ROUTE /PIPESAll of the Branches belonging to /PIPES will be routed.

ROUTE WITH BENDS /PIPESAll of the branches belonging to /PIPES will be routed using Bends inpreference to Elbows.

Command Syntax:

>-- ROute --+-- WIth --+-- ELbows --.| | || ‘-- BEnds ---| .-----<----.| | / |‘-----------------------+--*-- <sgid> --+-->



4-5

4.2.5 Setting the Nozzle Offset Factor

Keywords: OFFSETFACTORDescription: Branches which are routed from Nozzles have default Routing Planes

a set distance away from the Nozzle. This is to allow a sensible pipelength between the Nozzle and the first change of direction. Thedefault value for this offset is three times the bore of the associatednozzle, and is input in the same terms. For example, a value of 4would mean that the offset would be four times the Nozzle bore.

Examples:

OFFSET 5Sets the offset to be five times the bore of its associated Nozzle.

Command Syntax:

>-- OFFSETfactor integer -->

Querying:

>-- Query OFFSET -->

4.3 Refining the Automatic Pipe Routes

The automatic routing process often results in a set of common centrelineroutes down the centre of a rack. The following section describes the rackordering facilities which are able to refine these routes into a more acceptableform.

The rack ordering process works by spreading a number of pipes across apredefined rack volume. You have various options which may be set to controlthe spacing of pipes and the direction of spread across the rack. Theparameters which need to be input are:

• The location and dimensions of the rack (the RACK command)

• How the pipes are to be arranged on the rack (the SDIR command)

• The order in which the pipes will be placed

• The minimum clearance between adjacent pipes



Version 11.3

4-6

4.3.1 Defining the Rack to be Used.

Keywords: RACKDescription: The rack is defined by the axes of a PVOL element in the database

whose size should be similar to the physical rack area expected. ThePVOL width is important, because its edges determine the position ofthe first pipe if the pipes are to be spread from one side of the rack.

Examples:

RACK /PVOL1Sets /PVOL1 to be the rack.

Command Syntax:

>-- RAck <sgid> -->

4.3.2 Defining the Direction of Spread

Keywords: SDIRDescription: The spread direction is the direction in which the pipes will be spread

laterally when they are ordered along the rack. The default positionfrom which the pipes are spread is the centre of the PVOL. This maybe changed to the side of the PVOL by adding the parameterFROMSIDE to the command.

Examples:

SDIR ESets the spread direction to be East about the centre of the PVOL

SD N FRSsets the spread direction to be North, starting from the south side of thePVOL

SD N ABAs above, but pipes to be spread about centre of rack

Note: If no spread direction is specified, the default is taken as the directionof the second largest side of the PVOL

Command Syntax:

>-- SDir <bdir> --+-- FRomside -----.| ||-- ABoutcentre --|| |‘-----------------+-->



4-7

4.3.3 Defining the Base Direction

Keywords: BASEDescription: This is the direction in which the pipes will be moved in order to sit on

the rack. By default, this is the direction of the smallest side of thePVOL.

Examples:

BASE WSets the base direction to be West. (This should always be perpendicular tothe spread direction.)

Command Syntax:

>-- BAse <bdir> -->

4.3.4 Spreading Pipes about the Rack

Keywords: SPREADDescription: SPREAD moves the pipes laterally across the rack in the SDIR

direction to give the specified clearance. The default clearance is50mm between pipe walls on the same centreline.

Examples:

SPREAD /PIPESSpreads the pipes in /PIPES about the designated rack

SP /PIPES WW 100Spreads the pipes such that the wall-to-wall clearance is 100mm

SP /PIPES WF 4INSpreads the pipes such that the diameter of Flanges will be considered aspart of the calculation. In this case, the distance between a Flange o/d andits adjacent pipe wall, will be a minimum of 4 inches.

SP /ZONE1 FF 75Spreads the pipes such that two opposing Flange diameters will have aminimum clearance of 75mm. Pipes with no Flanges would have a wall-to-wall clearance of 75mm.

SP ALLRepeat previously defined order sequence (for example, on a subsequentrack).



Version 11.3

4-8

Command Syntax:

>-- SPread --+-- WW ---.| ||-- FF ---|| ||-- WF ---|| ||-- ALL --|| |‘---------+-- <uval> --. .-----<----.

| | / |‘------------+--*-- <sgid> --+-->

4.3.5 Setting the Bottom-of-Pipe Position

Keywords: BOPDescription: The BOP command moves the specified pipes such that their outside

diameters are resting on the rack plane in the BASE direction.

Examples:

BOP /ZONE1Sets the BOP of all pipes in /ZONE1 to sit on the specified rack

BOP ALLRepeat previously defined order sequence

Command Syntax:

>-- BOP --+-- ALL -->||-- <uval> --. .-----<----.| | / |‘------------+--*-- <sgid> --+-->

Note: No ordering takes place with the BOP command; it is expected thatthe BOP command is used after a spread.

4.3.6 Combined Spreading and BOP Operations

Keywords: ORDERDescription: The ORDER command combines both the SPREAD and BOP

operations. It spreads the pipes across the rack to give the requiredclearances, and then moves them into contact with the rack plane.



4-9

Examples:

ORDER /PIPES WW 100Spreads the pipes such that the wall-to-wall clearance is 100mm and thensets the BOP positions to sit on the rack.

OR /ZONE1 FF 75Spreads the pipes such that the Flange-to-Flange clearances are 75mm, andthen sets the BOP positions to sit on the rack.

OR ALLRepeat previously defined order sequence

Command Syntax:

>-- ORder --+-- WW ---.| ||-- FF ---|| ||-- WF ---|| ||-- ALL --|| |‘---------+-- <uval> --. .-----<----.

| | / |‘------------+--*-- <sgid> --+-->


5 Structural Design Using CatalogueComponents

This chapter first describes how logically connected structural steelwork maybe built up in DESIGN by choosing Components from the Catalogue. Suchstructures will normally exist in the Design hierarchy at Framework (FRMW)or Subframework (SBFR) level. The concepts are then extended for use inbuilding designs, using other materials such as concrete.

The principal types of element involved in steelwork design are:

NodesThese define the points within the 3D design model between which steelconstruction members are to run. Primary Nodes have their position definedin free space, whereas Secondary Nodes have their position defined relativeto an owning steel Section. Nodal data, including the attributes of memberelements of Nodes, is particularly relevant for stress analysis of the steelworkstructure.

SectionsSections represent the physical steel members (columns, beams, bracing strutsetc.) which make up the interconnected structure. Their cross-sections aredefined by reference to Catalogue 2D Profile elements, while their lengths arederived from the positions of the Nodes between which the Sections run.

JointsThese are Catalogue items which represent the physical connections betweenstructural members. Primary Joints are owned by Primary Nodes;Secondary Joints are owned by Secondary Nodes. Multiple connections arerepresented by Primary or Secondary Compound Joints, which own aSubJoint for each connection point. Linear Joints are used to connect theedges of panels to structural sections or to other panels.

PanelsPanels represent any sheet materials used to clad a structural model. Theirshape is determined by linking together a set of Panel Vertex elements toform a 2D Panel Loop, which is then extruded in the third dimension to givethe required panel thickness.

Structural Design Using Catalogue Components


Version 11.3

5-2

FittingsSteelwork Fittings and Panel Fittings are Catalogue items which canrepresent any ancillary item related to, but not an inherent part of, thestructure, such as web stiffeners, lifting lugs, access ports, and so on. They areowned by Sections and Panels, respectively. Compound Fittings andCompound Panel Fittings, each of which owns Subfittings, are used torepresent more complex geometry (such as penetrations, where one or moreelements pass through another element).

Generic Sections (GENSECs)GENSECs can be used to represent any structural item whose geometry can begenerated by sweeping a 2D profile along a linear or curved path. The path,defined by a Spine element, is determined by a sequence of Spine Pointsand Curves. In their simplest linear format, GENSECs may be used instead ofSections and Panels; in more complex formats they can represent curvedbeams, curved walls, etc.

FixingsGeneric fixingscan represent any joint or fitting owned (indirectly) by aGENSEC.

5.1 Creating and Positioning Primary Nodes

Keywords: NEW PNODE NPOSDescription: The first step in creating a new piece of structural steelwork is often

the creation and positioning of a network of Primary Nodes within the3D design model. PNOD elements are created, as for other Designelements, by using the NEW command. They may be positioned eitherby using a standard positioning command or by setting the NPOS(Node Position) attribute directly.

Nodes have no physical size: their positions are used to define thepoints in space between which steel Sections are to bepositioned/strung.

Examples:

NEW PNOD /PNOD1 AT E1000 N500 U500(At FRMW or SBFR level) Creates a Primary Node named /PNOD1 at thespecified position.

NEW PNOD /PNOD2 COPY PREV BY E1000Creates a Primary Node which is displaced from the previous one in thespecified way.

NEW PNOD /PNOD3

NPOS E2000 N1000 D500Creates /PNOD3, then places it at the specified position.



5-3

Command Syntax:

>-- NPOSition -- <bpos> -->

(The standard element creation syntax is described in Part 1 of the DESIGNReference Manual.)

Querying:

Q NPOS

5.2 Creating and Connecting Sections Automatically

Keywords: STRING FROM TODescription: The STRING command is a very powerful multi-functional tool which

performs the following operations automatically:

• A Section (SCTN) element is created, running between twonamed Nodes. The Node positions are used to set the Section’sPOSS (Start Position) and POSE (End Position) attributes. Theorder of occurrence of the named Nodes in the STRING commandline is used to set the DRNS (Start Direction) and DRNE (EndDirection) attributes (on the basis that the Section is strungFROM start TO end).

• Joint elements (PJOI or SJOI) are created at each Node and areorientated so as to be compatible with the new Section. Thus,both the OPDI (Origin Plane Direction) attribute and the normalto the Cutting Plane (as defined by the CUTP attribute) of eachPJOI will be the same as the DRNS/DRNE attribute of theSection.

• The Section-to-Joint cross-references (JOIS/JOIE for the Section;CREF for the Joints) are set so that they are self-consistent.

Thus the STRING command creates all new elements required toposition the physical Section within the structural design model. Itleaves you at the new Section (SCTN) level within the hierarchy.

Examples:

STRING /COLUMN1 FROM /PNOD1 TO /PNOD2Strings a Section named /COLUMN1 between the specified Primary Nodes.

STRING BEAM FROM /PNOD2 TO /SNOD3

NAME /UB80.LEV2Strings a Section of GTYPE BEAM between the named Primary andSecondary Nodes. The Beam is named separately in the second commandline.



Version 11.3

5-4

Note: The presence of a Section is shown on the DESIGN graphical displayas a centreline-only representation (broken line) at this stage. TheSection has no physical form, other than a derived length (related tothe inter-Node separation), until its cross-section has been defined bysetting a reference to a Catalogue Profile element.

Command Syntax:

>-- STRIng -+- name -.| |‘--------+- word -.

| |‘--------+- FRom - <gid> - TO - <gid> -.

| |‘- TO - <gid> - FRom - <gid> -+-->

5.3 Section Attributes

A Section is a linear structural component such as a universal beam, column,brace, tie, strut, etc. Sections are assumed to be ‘prismatic’; that is, they areassumed to have uniform properties throughout their length, includinguniform cross-sectional dimensions.

The overall dimensions of a 3D design Section are derived from two sources:

• Its cross-sectional dimensions are defined by a cross-reference to a 2DProfile element stored in the Catalogue DB.

• Its length is derived from the separation between the points defined byits Start Position (POSS) and End Position (POSE) attributes.

This section describes the main attributes which together define a Section as a3D physical entity within the interconnected structure.

5.3.1 Cross-Sectional Profile via a Specification Reference

Keywords: SPREFDescription: The SPREF (Specification Reference) attribute of a Section must point

to a valid Profile element in a Catalogue DB in order for the Section tobe given a physical representation by DESIGN. This is achieved bysetting SPREF to the name of a Specification Component in a ProjectSpecification.

Examples:

SPRE /203X203X55KG.UBSets the Specification Reference of the current Section to point to a Profilein the Catalogue. (The .UB suffix in the Specification Component namewould normally indicate that this Profile represents a Universal Beam.)



5-5

Command Syntax:

SPRef name

Querying:

Q SPRef

5.3.2 Generic Type

Keywords: GTYPEDescription: The GTYP attribute may be set to a PDMS word which indicates the

purpose of the Section within the structure. Its setting is notobligatory. (See the PARAGON Reference Manual for a list ofsuggested GTYP word settings for Profile elements.)

Examples:

GTYP BEAMSets the GTYP of the current Section to BEAM.

Command Syntax:

>--- GTYPe --- word --->

Querying:

Q GTYPe

5.3.3 Start and End Positions

Keywords: POSSTART POSENDDescription: When a Section is Strung (see Section 5.2), its start and end positions

(POSS and POSE) are set to the positions of the start and end Nodes.When a Section is manually Connected or Reconnected (see Section5.7), the settings of POSS and POSE are derived from theintersections of the Jline through the End Cutting Planes of theSection and the Joints. In either case, POSS and POSE are setautomatically.

It is also possible to set POSS and POSE specifically; for example,where a Section extends into free space, with at least one endunconnected. This may be done by specifying the coordinates directly,or by relating them to the position of another design element.



Version 11.3

5-6

Examples:

POSE E1250 N2000 D750Positions the Section’s end at the specified point.

POSS /PNOD1Positions the Section’s start at the NPOS of the specified Primary Node.

Command Syntax:

>--+-- POSStart --.| |‘-- POSEnd ----+-- <bpos> -->

Querying:

Q POSStart

Q POSEnd

5.3.4 Start and End Plane Directions

Keywords: DRNSTART DRNENDDescription: The directions of the start and end cutting planes of a Section (that is,

the directions of the perpendiculars to the planes which define the ‘cut’ends of the Section) are usually defined automatically when theSection is connected within the structural model; either by Stringing(see Section 5.2) or manually (see Section 5.7). The settings of thecorresponding DRNS and DRNE attributes are then derivedautomatically from the directions of the associated Joint’s CuttingPlanes.

It is also possible to set DRNS and DRNE specifically; for example,where a Section extends into free space, with at least one endunconnected. In this case each cutting plane direction must be in thegeneral direction of the other end of the Section.

Examples:

DRNS N45WSets DRNS to the specified direction, regardless of the direction of theSection’s Z-axis.



5-7

DRNE PERPSets DRNE so that the end cutting plane is perpendicular to the Section’sZ-axis (giving a square end as opposed to a chamfered end for a Sectionwhich has a skewed connection).

Command Syntax:

>--+-- DRNStart --.| |‘-- DRNEnd ----+-- <bdir> ---------.

| |‘-- PERPendicular --+-->

Querying:

Q DRNStart

Q DRNEnd

5.3.5 Orientation Angle

Keywords: BANGLEDescription: The orientation of a Section about its Neutral Axis is defined in terms

of an angular clockwise rotation when viewed in the POSS-to-POSEdirection. The angle of rotation from the default orientation is held asthe setting of the Beta Angle (BANG) attribute of the Section.

POSS

DRNS

POSEDRNE

BANGNA

SPREF of SCTNpoints to PROFin Catalogue

Examples:

BANG 90

Command Syntax:

>-- BANGle value -->

Querying:

Q BANGle



Version 11.3

5-8

5.3.6 Joint Start and End References

Keywords: JOISTART JOIENDDescription: Section ends which have been connected in the structure have their

JOIS (Joint Start) and JOIE (Joint End) attributes set such that theycross-refer to the Joints to which those ends are connected. (The Jointshave a similar cross-reference, the CREF attribute, back to theattached Section.)

These attributes are set automatically when a Section is connectedand you will not usually need to set them specifically.

Examples:

JOIE /PJOI.RB.2Sets logical connection from Section’s end to named Primary Joint.

Command Syntax:

>--+-- JOIStart --.| |‘-- JOIEnd ----+-- <gid> -->

Querying:

Q JOIStart

Q JOIEnd

5.3.7 Start and End Connection Types

Keywords: CTYSTART CTYENDDescription: Section ends which have been connected in the structure have their

CTYS (Start Connection Type) and CTYE (End Connection Type)attributes set such that they match those of the Joints to which thoseends are connected. This is done by setting CTYS/CTYE to a wordwhich matches the Joint’s CTYA attribute in the Catalogue; see thePARAGON Reference Manual.

These attributes are set automatically when a Section is connectedand you will not usually need to set them specifically.



5-9

Examples:

CTYS BOLTThe Section’s start is to be connected to its attached Joint by means of bolts.(The CTYA of the Joint must also be set to BOLT for a compatibleconnection; see Part 4 of the DESIGN Reference Manual for informationabout data consistency checking.)

Command Syntax:

>--+-- CTYStart --.| |‘-- CTYEnd ----+-- word -->

Querying:

Q CTYStart

Q CTYEnd

5.3.8 Start and End Releases

Keywords: SRELEASE ERELEASEDescription: The two Release attributes, the Section Start Release (SREL) and the

Section End Release (EREL), may be used to define how the Sectionbehaves under the effect of applied forces and moments. They arerelevant only for stress analysis of the structure.

The attribute settings allow for two types of movement of the Sectionends when external forces are applied, namely:

• Linear movement along a specific axis (DX, DY, DZ)

• Rotation about a specific axis (RX, RY, RZ)

Examples:

SREL DX RX RYThe Start of the Section is constrained such that it can move only in the Xdirection and can rotate only about the X and Y axes.



Version 11.3

5-10

Command Syntax:

>--+-- SRELease --. .---<---.| | / |‘-- ERELease --+--*-- DX ---|

| ||-- DY ---|| ||-- DZ ---|| ||-- RX ---|| ||-- RY ---|| ||-- RZ ---|| |‘-- sign --+-->

Querying:

Q SRELease

Q ERELease



5-11

5.4 Creating and Positioning Secondary Nodes

A Secondary Node is owned by, and positioned relative to, an existing Section.It enables you to position and connect another Section (an Attached Section)at any point along the length of the first Section (the Owning Section), ratherthan having to define the position of the Attached Section in ‘free space’.

Keywords: NEW SNODE ZDISTANCEDescription: SNOD elements are created, as for other Design elements, by using

the NEW command.

They are positioned by specifying their distance from their owningSection’s Start Position, measured along the Neutral Axis towards theEnd Position. This distance, which is held in the Node’s ZDISTattribute, may be specified as an absolute length, as a proportion ofthe overall distance between POSS and POSE (i.e. a proportion of thederived length of the Section), or by reference to any marker (pin, p-point, p-line etc.), element or plane.

Examples:

NEW SNOD /SNOD1 ZDIST 1500(At SCTN level) Creates a Secondary Node named /SNOD1 at the specifieddistance from the start of the Section. The Node is positioned on the NeutralAxis of the owning Section.

NEW SNOD /SNOD2IS 1250 FROM ENDThe position of the new Node is measured from the POSE position ratherthan from the default reference of POSS.

NEW SNOD /SNOD4 ZDIS PROP .33The new Node is positioned one third of the way along the Section’s NeutralAxis, measured from the start of the Section.

NEW SNOD /SNOD3ZDIS PROP 0.25 FROM ENDThe new Node is positioned one quarter of the way along the Section’sNeutral Axis, measured from the end of the Section.

NEW SNODE /SNOD5ZDIS PLANE W30N DIST 0.0The new Node is positioned at the intersection of the owning section’sneutral axis with the defined plane.



Version 11.3

5-12

Command Syntax:

>-- ZDIStance --+-- <uval> --------------.| ||-- PROPortion -- value --+-- FRom --+-- STart --.| | | || | |-- ENd ----|| | | || | ‘-- <gid> --|| | || ‘----------------------+| || ||-- <marke> ------------------------------------|| |‘-- <plane> ------------------------------------+->

Querying:

Q ZDIStance

5.5 Creating and Positioning Joints

Joints elements constitute the physical means by which Sections are connectedtogether.

A Primary Joint (PJOI) is owned by a Primary Node. Its position is derivedfrom that of its owning Node.

A Secondary Joint (SJOI) is owned by a Secondary Node. Its position isderived from that of its owning Node, and thus, in turn, from the position ofthe Section which owns that Node.

A Compound Joint (PCOJ or SCOJ) is positioned relative to a Node, as for aPJOI or an SJOI, but all settings which define its connections are associatedwith subsidiary SubJoints owned by the Compound Joint (one SubJoint foreach connection).

You will most often create and position Joints automatically using the STRINGcommand (see Section 5.2). This section describes how you can carry out theseoperations independently and how you can modify the positions of Joints whichhave been created previously.

A Joint is a Catalogue Component, which is selected in the design by settingits SPREF attribute to point to the required Component Specification.

5.5.1 Creating Primary Joints

Keywords: NEW PJOINTDescription: A new Primary Joint can only be created at PNOD level.



5-13

Examples:

NEW PJOI /JOINT1Creates a new PJOI with a default position and orientation. The defaultposition places the DELPOS (Delta Position) of the Joint at the NPOS of theNode. The default orientation directs the OPDI (Origin Plane Direction) ofthe Joint UP.

Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGNReference Manual.

5.5.2 Creating Secondary Joints

Keywords: NEW SJOINTDescription: A new Secondary Joint can only be created at SNOD level.

Examples:

NEW SJOI /SJOINT1Creates a new SJOI with a default position and orientation. The defaultposition places the POSL (Position Line) of the Joint through the owningSNOD.The default orientation directs the CUTP (Cutting Plane Direction)of the Joint Up.

Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGNReference Manual.

5.5.3 Setting Joint Geometry via a Specification Reference

Keywords: SPREFDescription: Both PJOIs and SJOIs must have their geometry defined by setting

their SPREF attributes to point to a valid Specification Component ina Project Specification in the Catalogue DB. Both types of Joint maypoint to the same Specification Component if required.

Examples:

SPRE /10X10.BRAK90(The .BRAK90 suffix in the Specification Component name would normallyindicate that this represents a 90 degree bracket joint.)



Version 11.3

5-14

Command Syntax:

>--- SPRef name --->

Querying:

Q SPRef

5.5.4 Positioning and Orientating Primary Joints

Keywords: DELPOSITION OPDIRECTION BANGLEDescription: The position and orientation of a Primary Joint are defined by the

settings of the following three attributes:

• The Delta Position (DELP) is the offset between the Joint’sOrigin Plane and the position of its owning Node (the NPOS ofthe PNOD), expressed in the coordinate system which applies tothe FRMW or SBFR. The default is a zero offset, so that theJoint’s Origin Plane passes through the owning Node.

• The Origin Plane Direction (OPDI) is the direction of thenormal to the plane through the Joint’s origin, as defined in theCatalogue representation of the Joint.

• The Beta Angle (BANG) is the angle of rotation of the Jointabout its Origin Plane Direction, measured clockwise as viewedalong that direction. The default setting is zero, so that theJoint’s orientation is as defined by its Catalogue representation.

PNode

OPDI

BANG

DELP defines X,Y,Z offset relative to PNode

NPOS defines X,Y,Z coords of PNode

DXDY

DZ

Z

X

Y

defines orientation about X,Y axes

defines orientation about Z axis

Examples:

DELP N4.5Offsets the Joint by 4.5 (mm) in a northerly direction.



5-15

OPDI NOrientates the Joint so that the normal to its Origin Plane points North.

BANG 180Rotates the Joint about its current Origin Plane Direction by 180 degrees.

Command Syntax:

>--- DELPosition --- <bpos> --->

>--- OPDIrection --- <bdir> --->

>--- BANGle ---+--- value ----------------------------.| |‘--- <bdir> --- TOwards --- <bdir> ---+--->

Querying:

Q DELPosition

Q OPDIrection

Q BANGle

5.5.5 Positioning and Orientating Secondary Joints

Keywords: POSLINE (ZDISTANCE) BANGLEDescription: The position and orientation of a Secondary Joint are defined with

respect to its owning Secondary Node. The position of this Node isseparately defined with respect to its owning Section, as describedSection 5.4. The Joint’s position with respect to the Section depends,therefore, upon the settings of two attributes:

• The Z-axis Distance (ZDIST) attribute of the owning SNOD.

• The Positioning Line (POSL) attribute of the SJOI itself. Thisdefines the position of the Joint in relation to the p-line systemwhich has been set up for the owning Section’s Profile within theCatalogue. The default POSL setting is NA (Neutral Axis), sothat the Joint’s Origin (more strictly, its JLIN) lies on theSection’s Neutral Axis at the position specified by the ZDIST:that is, the Joint’s Origin is coincident with the position of itsowning SNOD.

The Beta Angle (BANG) specifies the angular rotation of the Jointabout its Origin Plane Direction. The default setting is zero, so thatthe Joint’s orientation is as defined by its Catalogue representation.



Version 11.3

5-16

SNode

OPDI

BANG

ZDIST

Z

X

Y defines orientation about X,Y axes

defines orientation about Z axis

defines position of SNode relative to POSS of Sectio

TOSNA

POSL (here set to TOS) defines position

BOSOwning Section(2D view only)

Examples:

POSL TOSThe Positioning Line of the Joint is coincident with the TOS (Top of Steel) p-line of the Section.

POSL BOSThe Positioning Line of the Joint is coincident with the BOS (Bottom ofSteel) p-line of the Section.

Command Syntax:

>-- POSLine word -->

where word is usually one of the following:NA (Neutral Axis)TOS (Top of Steel)BOS (Bottom of Steel)

>-- BANGle --+-- value ------------------.| |‘-- <bdir> TOwards <bdir> --+-->

Querying:

Q POSLine (At the SJOI)

Q ZDISTance (At the SNOD)

Q BANGle (At the SJOI)



5-17

5.6 Attributes of Connected Joints

The attributes and their settings described in Section 5.5 are applicable to anyJoints, whether or not they have been connected to attached Sections. Inaddition, Joints which have been fully connected (that is, those which haveboth an Owning and an Attached Section) have other relevant attributes set.These are described in this section.

5.6.1 Connection Reference

Keywords: CREFerenceDescription: The Connection Reference attribute (CREF) of a Joint points to the

identifier of the Attached Section.

This attribute is set automatically when a Section is connected andyou will not usually need to set it specifically.

Examples:

CREF /BEAM1 STARTSets Connection Reference to start of named Section.

CREF /BEAM2 ENDSets Connection Reference to end of named Section.

CREF /COLUMN2Sets Connection Reference to start of named Section.

CREF NULREFDisconnects the Joint.

Command Syntax:

>-- CREFerence --+-- <gid> --+-- STart* --.| | || |--- ENd ----|| | || ‘------------+| |‘--- NULref --------------+-->

where <gid> identifies the Section to be connected.

Querying:

Q CREFerence



Version 11.3

5-18

5.6.2 Cutting Plane

Keywords: CUTPlaneDescription: The position of a Joint which has an Attached Section is derived from

the intersection of the Attached Section’s Joining Line (JLIN) and theJoint’s Cutting Plane. The Cutting Plane Direction, that is thedirection of the normal to the Cutting Plane, is defined by the settingof the CUTP attribute. The default direction is Up.

It is the position of the Joint’s Cutting Plane which defines theeffective length of the Section (but see also Section 5.6.3).

Examples:

CUTP N45DThe normal to the Cutting Plane points in the specified direction.

CUTP PERPThe normal to the Cutting Plane is set perpendicular to the Joint’s OriginPlane.

Command Syntax:

>-- CUTPlane --+-- <bdir> ---------.| |‘-- PERPendicular --+-->

Querying:

Q CUTP

5.6.3 Cutback Allowance

Keywords: CUTBackDescription: The derived length of an attached Section is, unless otherwise

specified, the distance between the Cutting Planes of the Joints at itstwo ends. The CUTB attribute allows you to specify a length by whichthe Section should be shortened or extended to allow for any localfitting geometry at the Joint’s attachment point (to allow for weldmetal, packing pieces etc.).

A positive value of CUTB shortens the derived length of a Sectionattached to the Joint; a negative CUTB lengthens the attachedSection. The default is a CUTB setting of zero.



5-19

Examples:

CUTB 6An attached section will have its derived length reduced by 6mm.

CUTB -6An attached section will have its derived length increased by 6mm.

Command Syntax:

>-- CUTBack <uval> -->

Querying:

Q CUTBack

5.7 Manually Connecting Sections

This section describes the commands which allow you to connect Sections andJoints ‘manually’; that is, without using the STRING command. The relevantNodes and Joints must have been created first, as described in the precedingsections of this chapter.

This section also explains how to disconnect and reconnect Sections and Joints,so that you can modify existing interconnected structural designs.

5.7.1 Connecting Sections

Keywords: CONNECT START END FREE RECALCULATEDescription: When a Section is connected manually, the relevant End Cutting

Plane of the Section (DRNS/DRNE) is superimposed on the CuttingPlane (CUTP) of the connecting Joint. This requires that the directionand through point of the Section have been correctly specified; that is,that the correct end points are on an extension of the Section’s NeutralAxis.

In cases of misalignment, the Section’s position and orientation aregiven highest priority. Thus, connecting a Section will not cause theSection to move or rotate. The Joint will be aligned with the Section, ifpossible (but see the FREE option, below).

When the connection is made, the connection cross-references betweenthe Section and the Joint are set. That is, the JOIS/JOIE of theSection and the CREF of the Joint are matched. Further, the relevantConnection Type attribute of the Section (CTYS or CTYE) is set topoint to the Attached Connection Type attribute (CTYA) of theCatalogue Joint.



Version 11.3

5-20

The FREE option allows the existing joint position to remain fixed, andthe POSS and/or POSE of the section to be adjusted. This may causethe section to be displaced sideways, or its direction to rotate. It mayalso cause SNODEs and FITTINGs along the section to be displaced(even with RECALCULATE).

When the connection has been made, the corresponding Start or EndPoint of the Section (POSS/POSE) is calculated from the intersectionof the Z axis of the Section with the new Cutting Plane which passesthrough the end of the Joint’s JLIN.

The RECALCULATE option causes the positions of elements which aremembers of a Section to be recalculated so that they remain in thesame positions if the Section is moved. For example, the ZDIS definingthe position of a Secondary Node would be recalculated if the POSS(from which ZDIS is measured) were moved as a result of a CONNECTcommand, so that the SNOD remained unmoved.

If both RECALCULATE and FREE are specified, the position ofFITTINGs and SNODEs along the section are recalculated to be asclose as possible to their original positions.

Examples:

CONN END TO /SJOINT3Where the current element is a Section.

CONN WITH START OF /BEAM1Where the current element is a Joint.

CONN START TO /PJOIN2 RECALCConnects the start of the current Section without moving the positions ofany secondary elements owned by the Section.

Command Syntax:

At Section level:

>- CONnect -+- STart -.| |‘- ENd ---+- FREE -.

| |‘--------+- TO <gid> -+- RECALCulate -.

| |‘---------------+->

where <gid> identifies a Joint.

At Joint level:

>-- CONnect WITH --+-- STart --.| |‘-- ENd ----+-- OF <gid> -->

where <gid> identifies a Section.



5-21

5.7.2 Disconnecting Sections

Keywords: DISCONNECT START END RECALCULATEDescription: When a Section is disconnected, the connection cross-references

(JOIS/JOIE - CREF) are unset and the connection type cross-references (CTYS/CTYE ) are set to Nulref.

The position and length of the Section are not changed, but the Joint(if moved during the connection operation) is returned to its defaultposition.

The RECALCULATE option causes the positions of elements which aremembers of a Section to be recalculated so that they remain in thesame positions if the Section is moved. For example, the ZDISTdefining the position of a Secondary Node would be recalculated if thePOSS (from which ZDIST is measured) were moved as a result of aDISCONNECT command, so that the SNOD remained unmoved.

Examples:

DISCO STARTDisconnects the start of the current Section.

DISCO ENDDisconnects the end of the current Section.

DISCODisconnects both the start and end of the current Section.

DISCO END RECALCDisconnects the end of the current Section, but retains the positions of anysecondary elements owned by the Section.

Command Syntax:

>-- DISConnect --+-- STart --.| ||-- ENd ----|| |‘-----------+-- RECALCulate --.

| |‘-----------------+-->

5.7.3 Reconnecting Sections

Keywords: RECONNECT START END RECALCULATEDescription: The RECONNECT command would typically be used to reconnect a

disconnected Section in the following circumstances:

• Following the movement of a Joint: the attached Section ismoved to the new Joint position.



Version 11.3

5-22

• Following the resetting of a cutback allowance at a Joint (seeSection 5.6.3): the length of the Section is modified to allow forthe new cutback distance.

• Following the movement of a Primary Node which has a memberJoint attached to an existing Section.

In each case the RECONNECT command attempts to restore theconsistency of the connected model.

The RECALCULATE option causes the positions of elements which aremembers of a Section to be recalculated so that they remain in thesame positions if the Section is moved. For example, the ZDISTdefining the position of a Secondary Node would be recalculated if thePOSS (from which ZDIST is measured) were moved as a result of aRECONNECT command, so that the SNOD remained unmoved.

Examples:

RECON STARTReconnects the start of the current Section.

RECON ENDReconnects the end of the current Section.

RECON Reconnects both the start and end of the current Section.

Command Syntax:

>-- RECOnnect --+-- STart --.| ||-- ENd ----|| |‘-----------+-- RECALCulate --.

| |‘-----------------+-->

5.8 Repositioning Steelwork Elements

The concept of connectivity in structural steelwork influences the types ofrepositioning operations which are allowed. Repositioning operations using thestandard DESIGN commands will also move items whose positions depend onthose of the items being directly moved.

5.8.1 Reversing Section Start and End Positions (‘Flipping’)

Keywords: FLIPDescription: The FLIP command mutually exchanges references to the Start and

End of a steelwork Section, effectively reversing its orientation. This is



5-23

mainly of use for reorientating a Section with a non-symmetricalprofile if you have mistakenly strung it the wrong way round. It is bestused before any Secondary Nodes or Fittings are placed along theSection.

FLIP causes the settings of the following pairs of attributes to beexchanged:

• POSS and POSE (Start and End Positions)

• DRNS and DRNE (Start and End Plane Directions)

• JOIS and JOIE (Start and End Joint References)

Caution: It is not intended that Sections with secondary connections be Flipped,although you can do so if you fully understand the effects outlinedbelow. These effects may not give the results you had intended andmay therefore require further design modifications to be made:

The settings of the SREL and EREL (Start and End Release)attributes are not exchanged. Since, however, the ends to which theyrefer have changed (since the original Start is now the End, and viceversa), their effects will be reversed in the physical model.

• The Member List of the Flipped Section remains unchanged, sothat any cross-references to member elements by list positionremain correct. The ZDIST attributes of any SNODs,FITTINGs, etc. remain the same, so that their positions are nowderived from the opposite end of the Section (the new Start end),thereby causing these member elements to move.

• Any Connected items referenced via SJOIs will not move, sincethe positions of the corresponding SJOIs will not move to thenew SNOD positions until they are Disconnected. If you wish toreverse a Section with existing secondary connections youshould, therefore, use the following sequence of operations:

• Disconnect the Section to be Flipped from all attached Sections.

• Flip the Section, thereby repositioning all of its SNODs and theirassociated SJOIs (now disconnected) in the reversed locations.

• Reorientate all connected Sections so that they realign with themodified SJOI locations along the Flipped Section (or reset theZDIST attributes of the SNODs so that they are repositionedwhere you want them).

• Reconnect the Flipped Section to all the attached Sections.

Examples:

FLIPReverses the Start and End attribute settings for the current element asoutlined in the preceding description.



Version 11.3

5-24

Command Syntax:

>--- FLIP --->

Querying:

You may find the following querying commands, used both before and aftergiving the FLIP command, helpful in checking the precise effects of thecommand:

Q ATT For checking, in particular, all Start and End relatedsettings (POSS/POSE, DRNS/DRNE, etc).

Q DER POS For checking the derived positions of SNODs and/or SJOIs.

5.8.2 Moving Steelwork Elements

NOTE: The positioning/moving syntax described in Chapter 2, Equipment andPrimitives, also applies to Structural steelwork elements.

Keywords: MOVE ALONG BY AT

Description: Movement relative to a fixed starting position (MOVE, ALONG, BYcommands) is possible for all structural elements which have adirectly defined location in the 3D model; for example, Frameworks,Subframeworks, Primary Joints and Nodes (but not Secondary Jointsand Nodes, whose positions are dependent on that of a Section),Routing Planes, Panels, etc.

Absolute positioning (AT command) is possible only for Sections,Primary Nodes, Routing Planes and Panels.

Examples:

MOVE ALONG E45N DISTANCE 500Moves Current Element in specified direction by specified distance.

BY N1000 E5000 U7000Moves Current Element as specified relative to its current position.

AT E2000 N2000 U1000Moves the Current Element to the specified position. In the case of aSection, POSS is set to this position; in the case of a Primary Node, NPOS isset to this position.



5-25

5.8.3 Modifying Lengths of Sections

Keywords: EXTEND START END PROPORTIONAL RECALCULATEDescription: Once positioned, a Section may have its ends repositioned

independently by using the EXTEND command. This effectivelylengthens or shortens the Section by a specified amount and resets itsPOSS and/or POSE attributes accordingly. (You could, of course, setPOSS and/or POSE directly, as described in Section 11.3.3, but thiswould need prior calculation of the new positions needed to achievethe required length change.)

The increase or decrease in length may be specified as a directmeasurement or as a proportion of the current length of the Section.

The <plane> allows you to define the amount of extension required byintersecting the neutral axis with a defined plane. The section isextended (or shortened) to meet the plane.

The RECALCULATE option causes the positions of elements which aremembers of the modified Section to be recalculated so that theyremain in the same positions after the change. For example, theZDIST defining the position of a Secondary Node would berecalculated if the POSS (from which ZDIST is measured) were movedby the EXTEND command, so that the SNOD remained unmoved.

Examples:

EXTEND END BY E1000Move POSE by 1000mm Eastward.

EXTEND BY E1000As above (defaults to END).

EXTEND START BY W1000 RECALCMove POSS by 1000mm Westward and recalculate the positions of allmember SNODs, FITTs etc. so that they remain unmoved.

EXTEND START BY U500 E2000 S500Move POSS by the given amounts.

EXTEND END 1750Move POSE so as to increase the Section’s length by 1750mm (defaultunits).

EXTEND -1750Move POSE (defaults to END) so as to decrease the Section’s length by1750mm (default units).

EXTEND START PROP 0.25Move POSS so as to increase the Section’s current length by 25%.



Version 11.3

5-26

EXTEND PROP -0.2Moves POSE (defaults to END) so as to decrease the Section’s length by20%.

EXTEND END PLANE E30N DIST 0.0Moves POSE to meet the defined plane.

Command Syntax:

>-- EXTend --+- STart -.| ||-- ENd* -|| |‘---------+- PROPortional - value -.

| ||- BY --- <axpos> ------|| || ||- <plane> -------------|| |‘- <uval> --------------+- RECALCulate --.

| |‘----------------+->

5.8.4 Reorientating Steelwork Elements

Keywords: ROTATE BY ABOUT THROUGH ANDDescription: The method of rotating a Section about its Neutral Axis by setting its

BANG attribute was described in Section 5.3.5. This section explainsthe use of the ROTATE command to achieve a greater range ofreorientating effects on Sections and on other steelwork elements.

The command allows you to specify the rotation required in any of thefollowing ways:

• As a specified angle of rotation about a default axis (similar ineffect to setting the BANG attribute). This default axis is theNeutral Axis for Sections, Joints and Fittings, and the Z axis forother elements.

• As a specified angle of rotation about a given axis, the latterdefined by its direction and/or through point. If the directionand/or through point are omitted, the default direction is that ofthe Neutral Axis or Z axis; the default through point is theOrigin or Start Position (depending on the type of elementinvolved).

• By reference to the component’s axes or p-lines.



5-27

Examples:

ROTATE BY -45Rotates by 45° about the element’s Neutral Axis or Z axis (anticlockwisewhen looking from Start to End or in the +Z direction, since the rotation isspecified as a negative angle).

ROTATE BY 45 ABOUT ERotates by 45° about the E-W axis (clockwise when looking E).

ROTATE ABOUT E BY 45The same as the preceding example.

ROT THRO POSE ABOUT S BY -25Rotates a Section about an axis which passes in the N-S direction throughits End position. The rotation is 25° anticlockwise when looking S along thisaxis.

ROT ABOUT PPLIN TOS BY 45Rotates by 45° about the Top-of-Steel p-line (clockwise when looking in theStart to End direction).

ROT AND PPLIN BOS IS E45NRotates element about its Neutral Axis until the Bottom-of-Steel p-linepoints as closely as possible to the E45N direction.

ROTATE AND Y IS N45W25DRotates element until the Y axis points as closely as possible to theN45W25D direction.

ROT AND PPLIN TOS IS PPLIN BOS OF /SCTN1 LEAV DIR WRT/STRU1Rotates element until its TOS p-line points in the direction of the BOS p-line of /SCTN1 in the specified coordinate system.

Command Syntax:

Rotation about a given axis:>- ROTate ABOut -+- <plin> -.

| |‘- <bdir> -+- THRough - <bpos> -+- BY -+- <uval> -------------------.

| | | || | ‘- <bdir> TOwards <bdir> ---|| | || ‘- AND -+- <plin> -. || | | || ‘- <bdir> -+- IS <bdir> ----|| ||- BY - +- <uval> --------------------. || | | || ‘- <bdir> - TOwards - <bdir> -+ || | |‘- AND -+- <plin> -. | |

| | | |‘- <bdir> -+- IS - <bdir> ----+- THRough <bpos> -|

| |‘------------------+-->



Version 11.3

5-28

Rotation to pass through a given point:>- ROTate THRough - <bpos> -+- ABOut -+- <plin> -.

| | || ‘- <bdir> -+- BY -+- <uval> -----------------------.| | | || | ‘- <bdir> - TOwards - <bdir> ----|| | || ‘- AND -+- <plin> -. || | | || ‘- <bdir> -+- IS - <bdir> ------|| ||- BY -+- <uval> --------------------. || | | || ‘- <bdir> - TOwards - <bdir> -+- ABOut -+- <plin> -. || | | | || | ‘- <bdir>- +--|| | || ‘-----------------------|| |‘- AND -+- <plin> -. |

| | |‘- <bdir> -+- IS - <bdir> -+- ABOut -+- <plin> -. |

| | | || ‘- <bdir>- +----|| |‘-------------------------+-->

Rotation by a specified amount:>- ROTate BY - -+- <uval> --------------------.

| |‘- <bdir> - TOwards - <bdir> -+- ABOut -+- <plin> -.

| | || ‘- <bdir> -+- THRough - <bpos> ---.| | || ‘----------------------|| ||- THRough - <bpos> -+- ABOut -+- <plin> -. || | | | || | ‘- <bdir> -+-|| | || ‘----------------------|| |‘-------------------------------------------+->

Rotation to give a specified orientation:>- ROTate AND -+- <plin> -.

| |‘- <bdir> -+- IS - <bdir> -+- ABOut -+- <plin> -.

| | || ‘- <bdir> -+- THRough - <bpos> ----.| | || ‘-----------------------|| ||- THRough - <bpos> -+- ABOut -+- <plin> -. || | | | || | ‘- <bdir> -+--|| | || ‘-----------------------|| |‘--------------------------------------------+-->

Note: In each of the preceding diagrams <plin> identifies a specific p-line.



5-29

5.9 Positioning and Orientating Using P-lines

P-lines in a 3D structure represent lines, derived from points defined in theCatalogue for corresponding Profiles or Joints, which have associated directionvectors in the X-Y plane. A typical configuration for an ‘extruded’ I-sectioncomponent is illustrated in Figure 5-1; typical p-lines associated with a widerrange of profiles are illustrated in the guide Structural Design Using PDMS.

A p-line can provide a very convenient reference line or axis within anelement’s 3D geometry (as derived in the design model) for positioning ororientating the element itself, or for defining some other geometry relative tothe element. Positions may be defined along the length of a p-line; directionsmay be defined in terms of a p-line’s coordinate axes (the p-line directionbeing, by default, along its +Z axis).

Some examples have already been introduced in the earlier sections of thischapter. This section further illustrates the possible uses of such techniques.

PLIN BOS

PLIN NA

PLIN TOSZ

X

Y

BOS axes

SITE axes

Z

X

Y

TOS axes

Y X

Z

SCTN axes

Y X

Z

POSE

POSS

Figure 5-1 Typical P-lines and Axes for a Section



Version 11.3

5-30

5.9.1 Identifying P-lines

Keywords: PPLINE IDPLINEDescription: A p-line may be identified in either of the following ways:

• By reference to its PKEY attribute (see the PARAGON ReferenceManual for details of how this is set) and its owning element (ifthis is not the current element).

• By picking it on the display using the cursor.

Examples:

PPLINE TOSSpecifies the Top-of-Steel p-line of the current element.

PPLINE BOS OF /BEAM2Specifies the Bottom-of-Steel p-line of /BEAM2.

IDPLINE @Specifies the p-line to be picked using the cursor.

Command Syntax:

(This is the <plin> syntax referred to elsewhere in this manual.)

>--+-- PPLINe -- word --+-- OF <gid> --.| | || ‘---------------+| |‘--- IDPLine -- @ -------------------+-->

where word is the setting of the p-line’s PKEY attribute, as defined in theCatalogue; for example: TOS (Top of Steel), BOS (Bottom of Steel), NA(Neutral Axis), NF (Near Face), FF (Far Face), etc.

5.9.2 Positioning by Using P-lines

Keywords: PPLINE START END OFFSETDescription: A position relative to a p-line may be specified in any of the following

ways:

• As a specific distance along the p-line from its start (typically thePOSS of a Section) or its end (typically POSE).

• As a proportional distance along the p-line, expressed as afraction of its length (typically the distance from POSS to POSE).

• As one of its extremities; that is, at the p-line’s start or end.

• As an offset, expressed as the distance between two specified p-lines.



5-31

Examples:

POSITION PPLINE BOS 500Calculated position is on the BOS p-line, 500mm from its start (by default);for setting a variable or for querying.

POS PPLIN TOS 1000 FROM ENDCalculated position is on the TOS p-line, 1000mm from its end.

POS AT PPLIN NA OF /SCTN2 PROP .25Calculated position is on the Neutral Axis of /SCTN2, 25% along its lengthas measured from its start (by default).

POS AT PPLIN TOS OF /BEAM1 ENDPosition is defined as the end of the TOS p-line of /BEAM1 (probably, butnot necessarily, the POSE setting for /BEAM1).

BY PPLIN TOS OFFSET FROM PPLIN BOSMoves the current element (Section or Joint) by the offset distance betweenits TOS and BOS p-lines.

BY PPLIN BOS OFFSET FROM PPLIN TOSMoves the same distance as the preceding example, but in the oppositedirection.

BY PPLIN TOS -OFFSET FROM PPLIN BOSThe same effect as the preceding example.

Command Syntax:

Note: The following syntax describes only the p-line referencing options fordefining a position. These are in addition to the positioning/movingsyntax described in Chapter 2, Equipment and Primitives, which alsoapply to Structural steelwork elements.

Defining a specific position:

>- <plin> -+- <uval> -------------.| ||- PROPortion - value -+----------------------.| | || ‘- FROm -. || | |‘-------------------------------+- STart* -. |

| | |‘- ENd ----+--+-->

Defining a distance as the offset between two p-lines:

>-- <plin> --+-- sign --.| |‘----------+-- OFFSet FROm <plin> -->

where <plin>, which identifies a specific p-line, is defined in Section 5.9.1.



Version 11.3

5-32

Querying:

Q <plin> --+-- <uval> --------------.| ||-- PROPortion - value --+--------------------------.| | || ‘-- FROm --. || | |‘-----------------------------------+-- STart* --. |

| | |‘-- ENd -----+--+-->

Q <plin> -- OFFSet --+-- FROm -- <plin> --.| |‘--------------------+-->

Querying Examples:

Q PPLIN TOS ENDPosition of end of p-line.

Q PPLIN BOS PROP 0.3Position of point 30% of distance along BOS from start (by default) towardsend.

Q PPLIN NA PROP -1.5 FROM ENDPosition of point which is 1.5 times length of Neutral Axis away from end ofp-line in direction away from start.

Q PPLIN TOS OFFS FROM PPLIN BOSOffset distance between TOS and BOS.

Q PPLIN TOS OFFSOffset distance between TOS and Neutral Axis (by default).

5.9.3 Orientating by Using P-lines

Keywords: PPLINE DIRECTION X Y Z LEAVEDescription: You can orientate a structural element by referring its axes to the

directions of one or more p-lines. By default, references will be takenfrom the Z (or LEAVE) direction.

Examples:

ORI Y IS PPLIN TOS OF /SCTN1 X DIR AND Z IS UOrientates the current element such that its Y axis points in the X directionof the TOS p-line of /SCTN1 and its Z axis points Up. If, for example, the Xdirection of the TOS p-line of /SCTN1 points East, then this command lineis equivalent to ORI Y IS E AND Z IS U.



5-33

Command Syntax:

>-- <plin> --+-- X ------.| ||-- Y ------|| ||-- Z ------|| ||-- LEAve --|| |‘-----------+-- DIRection -->

Querying:

Q <plin> --+-- X ------.| ||-- Y ------|| ||-- Z ------|| ||-- LEAve --|| |‘-----------+-- DIRection -->



Version 11.3

5-34

5.10 Creating and Connecting Panels

5.10.1 Creating a Panel

A Panel (PANE) element represents any sheet material used to clad astructural model. The geometry of a Panel is defined by a subsidiary PanelLoop (PLOO) element. The 2D shape of the Panel Loop is defined by linkingtogether a set of Panel Vertex (PAVE) elements, each of which has a specificposition in the Panel’s coordinate system. The polygon thus formed defines theshape of the Panel in the same way that a Profile defines the cross-sectionalarea of a Section. The Height (HEIG) attribute of the PLOO defines thedistance through which this 2D shape is extruded to form the 3D Panel; thatis, it defines the Panel thickness, thus:

= Panel Loop (PLOO)

= Panel Vertex (PAVE)HEIGof PLOO

Each PAVE can have an optional fillet radius which defines a circular arcwhich bulges into (negative radius) or out of (positive radius) the PLOO area.The default fillet radius of zero denotes a point.

To define a new Panel, you must, therefore, first create a PANE element (usingNEW PANE etc.), then create a PLOO below it in the hierarchy, and thencreate and position as many member PAVEs as necessary to define the shapeof the PLOO and thus the PANE. (The Z co-ordinates of the PAVEs areignored; they are constrained to lie in the plane of the PLOO.)

5.10.2 Splitting a Panel

Keywords: SPLIT ONDescription: You can split a Panel along its line of intersection with a given plane

or Section. The Panel is split into two or more new Panels which havesame owner as the original one. More than one new Panel may resultif the original one has re-entrant vertices.



5-35

The vertices of the original Panel are moved to the new Panel(s) asappropriate and new vertices are created where the intersection linecrosses the edges of the original Panel.

Examples:

SPLIT PLANE N THRO N1000Splits current panel along its line of intersection with the specified plane

SPLIT ON /BEAM1Splits current panel along the Neutral Axis (projected if necessary) of thenamed section

Command Syntax:

>-- SPLIT --+-- PLANE <dir> -- THROugh <bpos> --.| |‘-- ON <section_id> ----------------+-->

5.10.3 Connecting Panels using Linear Joints

Linear joints are used to connect structural items along edges or faces. Theyeffectively have linear (2D) connectivity, whereas Primary and SecondaryJoints have only point (1D) connectivity (even though they have 3D geometry).

A Panel Linear Joint (PALJ), owned by a PANE, FRMW or SBFR, is used toconnect two Panels together. The start and end of the PALJ are defined by twoPanel Vertex (PAVE) points. Logical connections from the attached Panel aremade by setting Master Vertex (MVERT) attributes of two of the Panel’sPAVEs to point to the corresponding PAVEs on the linear joint, thus:

= PALJ (owned by PANE1)= PAVE (PLOO of PANE1)= PAVE (owned by PALJ)

MVERT attribute of PAVEpoints to PAVE of PALJ

PALJ

PANE1

PANE2

*

*

*

*

*

In this example, PANE1 is the Owning Panel and PANE2 is the AttachedPanel.

A Section Linear Joint (SELJ), owned by a Section, is used to connect aPanel to a Section. The start and end of the SELJ are defined by two SectionVertex (SEVE) points. Logical connections from the attached Panel are madeby setting Master Vertex (MVERT) attributes of two of the Panel’s PAVEs topoint to the corresponding SEVE’s on the linear joint, thus:



Version 11.3

5-36

= SELJ (owned by SCTN)= PAVE (PLOO of PANE)= SEVE (owned by SELJ)

MVERT attribute of PAVEpoints to SEVE of SELJ

SELJ

PANE

SCTN

*

*

*

*

*

Keywords: LINK UNLINKDescription: The LINK command lets you set up the necessary connection references

for:

• a vertex to another vertex

• an edge to an edge (an edge is the line between a pair ofconsecutive vertices)

• a panel to a joint

• a panel to a vertex

• a panel to an edge

In each case, the vertices of the item being linked are defined as slavevertices, while the vertices of the item linked to (which define theproperties at the connection point) are defined as master vertices.

When you link a panel, any new panel vertices needed will be createdautomatically to correspond with the master vertices of the itemconnected to. You can specify the position and direction of creation ofthe new vertices in the Panel Loop’s vertex sequence as part of thecommand. If the panel has no PLOOP, one will be createdautomatically.

UNLINK unsets the connection cross-references created by a LINKcommand.



5-37

Examples:

LINK VERT CE TO /PAVE2Links current vertex (slave) to vertex /PAVE2 (master).

LINK PANEL /PANE3 TO EDGE /PAVE5 /PAVE6 AFTER /PAVE2Links panel /PANE3 to edge between /PAVE5 and /PAVE6 and positionsany new vertices needed after /PAVE2 in the PLOOP of /PANE3.

Command Syntax:

>- LINK -+-+----------.| | || ‘- VERTex -+- <vidlist> - TO - VERTex - <vid> -------------.| ||--- EDGE - <eidlist> - TO - EDGE - <eid> -------------------|| |‘--- PANEl - <pid> - TO -+- JOINt - <jid> ---- <qualifier1> -|

| ||- VERTex - <vid> -. || | |‘- EDGE - <eid> ---+- <qualifier2> -+-->

where:<vid> is a vertex identifier (name, refno, treename)<vidlist> is a list of vertex identifiers<eid> is an edge identifier (pair of consecutive vids)<eidlist> is a list of edge identifiers (must be an even number

of vids)<pid> is a panel identifier (name, refno, treename)<jid> is a joint identifier (name, refno, treename)

<qualifier1>:

>-+- FROM -+- START - TO -+- <vid> -.| | |- END ---|| | ‘---------+--.| |- END - TO ---+- <vid> -. || | |- START -| || | ‘---------+--|| |- <vid> - TO -+- <vid> -. || | |- START -| || | |- END ---| || | ‘---------+--|| ‘---------------------------|‘------------------------------------+- FORWards --.

‘- BACKwards -+- AFTer <vid> ---------.|- BEFore <vid> --------||- BETween <vid> <vid> -|‘-----------------------+->

The FROM/TO options specify which portion of the joint is to be linked to thepanel. Defaults are implied start to implied end of joint.

The FORWARDS/BACKWARDS options specify the direction of vertices withinthe joint.



Version 11.3

5-38

The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loopat which to create vertices corresponding to those of the joint (mastervertices).

<qualifier2>:

>--+-- AFTer <vid> ----------.| ||-- BEFore <vid> ---------|| ||-- BETween <vid> <vid> --|| |‘-------------------------+->

The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loopat which to create vertices corresponding to those of the master vertices.

>-- UNLINK --+-- <vid> -- FRom -- <vid> --.| |‘-- ALL ---------------------+-->

Querying:

Q LINKS Queries connection references between vertices

5.11 Fittings, Hangers and Equipment Load Points

5.11.1 Fittings and Panel Fittings

A Fitting (FITT) element allows you to indicate a connected implied load, suchas a pipe hanger attachment, or an ancillary item related to, but not aninherent part of, the structure, such as a web stiffener or a flange plate.

A Fitting is owned by a Section (SCTN) and is positioned along the NeutralAxis of the SCTN at a point defined by the ZDIST attribute (in the same wayas for a SNOD). The Fitting may be geometrically modelled in the Catalogue,and selected from the Catalogue, in a similar way to a Joint, as described inSection 5.5.

A Panel Fitting (PFIT) element serves a similar function to a FITT, but isowned by a Panel and positioned relative to the Panel’s origin. A Cofitting(COFI) element is used where a fitting spans the junction betwen two or morePanels. In the latter case, one of the Panels owns a PFIT while the others eachown a COFI. Each COFI has its Panel Fitting Reference (PFRE) attributeset to point to the assciated PFIT; the PFIT has its Cofitting ReferenceArray (CFRA) attribute set to point to the COFIs.



5-39

5.11.2 Structure-to-Pipework Connections

Piping models may be linked logically to the Structural model by means ofcross-references between the Connection Reference (CREF) attribute of aFitting on the Structure and the Head or Tail Reference (HREF/TREF) of aHanger on the Pipework. A Fitting may be regarded, therefore, as theStructural equivalent of an Attachment Point (ATTA) in Pipework design.

For connection type compatibility, the Connection Type attribute (CTYA) of theFitting must match the Connection Type (HCON/TCON) of the Hanger.

5.11.3 Structure-to-Equipment Connections

Equipment models may be linked logically to the Structural model by means ofcross-references between the Connection Reference (CREF) attribute of aFitting on the Structure and the Connection Reference (CREF) of a Load Point(LOAP) element owned by the Equipment.

A Load Point has a position within the Equipment model, but no size ororientation. It behaves in this respect like a Node in the Structural model. Ifan Equipment is moved, any member Load Points which point to Fittings in aStructure will not move, their positions being constrained by the attachedStructure.



Version 11.3

5-40

5.12 Design, Owning and Attached Parameters

5.12.1 Setting Design Parameters

Keywords: DESPARAMETERSDescription: Design parameters (DESP) are array-type attributes of any element

which has a Specification Reference (Sections, Joints, Fittings etc.),each of which may store up to 100 real values. They may be used totransfer design data to a corresponding Catalogue component, or to acomponent’s attached or owning design element.

As an example, this enables one or more dimensions of a Joint to bederived from the dimensions of the Section(s) to which it is attached,rather than from preset dimensions defined for it in the Catalogue.

A DESP is referenced in the design by its numbered position in thearray. Its value must be set before the corresponding component isselected from the Catalogue, so that the required setting is availablewithin the design.

Examples:

DESP 2.5 7Sets first two design parameters to 2.5 and 7 respectively.

DESP N3 -5.5Sets third design parameter to -5.5.

DESP N3 POSS OF /SCTN1Sets design parameters 3, 4 and 5 to X,Y,Z coordinates (respectively) ofPOSS of element /SCTN1.

Note: In the last example, a range of three design parameters, needed to holdthe co-ordinates of the defined point, was set automatically, startingwith the specified third parameter.

Command Syntax:

Setting parameters in default order in the array, starting at parameternumber 1:



5-41

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

>-- DESParameters --+-- <expres> -----------------|| ||-- <uval> -------------------|| ||-- READ ---------------------|| |‘-- word --+-- OF -- <gid> --|

| |‘------------------+-->

Setting individually specified parameters within the array:

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

>- DESParameters -*- Number - integer -+- <expres> ------------|| ||- <uval> --------------|| ||- READ ----------------|| |‘- word -+- OF - <gid> -|

| |‘--------------+->

Querying:

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

Q --*-- DESParameters - integer ---+--->

Querying Examples:

Q DESP 1 DESP 3Outputs values of design parameters 1 and 3.

Q DESPOutputs values of all design parameters.

Q (WDESP[1])Extracts a word from within DESP 1.

FINCH DISTQ (DDESP[2])Extracts a distance (in feet and inches) from within DESP 2.

5.12.2 Setting Owning and Attached Parameters

Owning and attached parameters (OPAR and APAR, respectively) are real-array attributes of Joints. They are set in the Catalogue, and allow the Joint toderive data (usually dimensions) from its owning or attached Section(s) whenit is introduced into the design. See the PARAGON Reference Manual fordetails about the setting of these arrays.



Version 11.3

5-42

As with the design parameters described in Section 5.12.1, an OPAR or APARis referenced in the design by means of its numbered position in thecorresponding array.



5-43

5.13 Representing Curved Beams and Walls

5.13.1 Overview

Curved structural items are represented by Generic Section (GENSEC)elements, the geometry of which is defined by sweeping a 2D catalogue profilealong a path. This path is represented by a Spine element, owned by theGENSEC, whose route is specified in terms of a sequence of member SpinePoints (POINSP) and, optionally, Curves. For example:

= SPINE= POINSP

Start POINSP

End POINSP

PROFILE

CURVE

CURVE

There are six types of Curve, defined by setting the CURTYP (Curve Type)attribute, which govern the way in which the shape of the curve is specified.

The options are:

LINE A straight line (this is the default)

RADI A circular arc, defined by a radius and a conditioning point.

THRU An arc passing through a specified through-point position.

BULG An arc defined by a bulge factor and a conditioning point.

FILL A fillet arc and two adjacent straights, defined by a radiusand a pole position.

CENT A fillet arc and two adjacent straights, defined by a circlecentre point, a radius and a conditioning point.

A Spine with only two POINSP members behaves in a similar way to a linearSection (SCTN). The first POINSP owned by the Spine defines its startposition (equivalent to the POSS of the Section); the last POINSP defines itsend position (equivalent to the POSE of the Section).

Items connected to a GENSEC are positioned and orientated relative to a set ofp-lines which follow the same path as that defined by the GENSEC’s Spine;that is, the p-lines may be curved. These p-lines are referenced by attacheditems via Justification Line Datum (JLDATUM) and P-line Datum



Version 11.3

5-44

(PLDATUM) elements, which define the frames of reference to be used forpositioning and orientating the attached items relative to the parent GENSEC.

Fittings and joints are represented by generic Fixing (FIXING) elements, thegeometry of which is defined by reference to catalogue items. Fixings can ownother Fixings, so that although they behave somewhat like the more restrictiveFitting and Joint elements, they are more versatile for representing compoundfittings and joints.

5.13.2 Defining a Generic Section

Keywords: GENSEC SPINE POINSP CURVEDescription: Each GENSEC, representing a linear or curved beam or wall, must

own a Spine defining its shape. The Spine must own at least two SpinePoints, defining its start and end positions. It can also ownintermediate Spine Points and Curves to give a non-linearconfiguration.

Examples:

NEW GENSECCreates GENSEC with no defined geometry.

SPREF /203X203X55KG.UBSets SpecRef of GENSEC to point to catalogue profile. GENSEC now hasdefined cross-section, but no geometry defining its path.

NEW SPINECreates Spine with no defined path.

NEW POINSPFirst Spine Point defines Start Position (POSS).

NEW POINSPLast Spine Point defines End Position (POSE). Spine at this stage is astraight line.

NEW CURVE (Created between POINSPs).The attributes of this curve determine the shape of the Spine path betweenthe adjacent POINSPs. (See Section 5.13.3.)



5-45

5.13.3 More About Curve Types

The ways in which the various types of Curve are specified are as follows:

• CURTYP = LINESpecifies a straight line between the adjacent POINSPs. This is thedefault if curved geometry is not defined between two POINSP elements.

• CURTYP = RADISpecifies a single circular arc between adjacent POINSP elements. Thearc is defined by the RADI (radius) and CPOS (conditioning point)attributes. The conditioning point and the preceding and following pointsdefine the plane of the arc. The choice of minor or major arc is governedby the arc which approaches closest to the conditioning point. If RADS =false, the specified radius is ignored and the minimum radius iscalculated such that the curve is a semicircle between the adjacentPOINSPs.

• CURTYP = THRUSpecifies a single circular arc. The arc is defined by the POS attribute,which is interpreted as a through-point on the curve. The through-pointand the preceding and following points define the plane of the arc.

• CURTYP = BULGSpecifies a single circular arc. The arc is defined by the BULG (bulgefactor) and CPOS (conditioning point) attributes. The conditioning pointand the preceding and following points define the plane of the arc. Thechoice of minor or major arc is governed by the size of the bulge factor.The sign of the bulge factor determines whether the arc curves towardsthe conditioning point (positive bulge factor) or away from theconditioning point (negative bulge factor).

• CURTYP = FILLSpecifies a combination of an arc and up to two straights. The curve isdefined by the RADI (radius) and POS attributes, where the POS settingis interpreted as the pole point of the arc (the intersection of the two endtangents). The pole point and the preceding and following points definethe plane of the arc. If RADS = false, the specified radius is ignored andthe maximum radius that will fit into the pole is calculated; an endpointtriangle ensures that the fillet terminates on at least one of the endpoints.

• CURTYP = CENTSpecifies a combination of an arc and up to two straights. The curve isdefined by the RADI (radius), CPOS (conditioning point) and POSattributes, where the POS setting is interpreted as the circle centrepoint. The centre point and the preceding and following points define theplane of the arc. The choice of minor or major arc is governed by the arcwhich approaches closest to the conditioning point; the conditioning pointneed not lie in the plane of the arc. If RADS = false, the specified radiusis ignored and the maximum radius is calculated to ensure that the



Version 11.3

5-46

nearest POINSP to the circle lies on the circle; the arc terminates on thispoint.

Note: Displayed GENSECs treat each segment of the Spine as a separateextrusion. At the vertices between segments, i.e. at the POINSPpositions, these extrusions merge together if there is a tangentcontinuity. If there is a tangent discontinuity, the extrusions aremitred along a plane normal to the mean of the two tangent vectors atthe POINSP position.

5.13.4 How P-lines Are Used For Generic Sections

P-lines defined in the Pointset of the Section Profile (as referenced by theSpecRef) follow the path defined by the GENSEC’s Spine. This means that, fora curved GENSEC, the p-line directions are not constant over their lengths.This must be taken into consideration when using them as datums referencedby attached items.

The command syntax used for referencing p-lines for SCTNs, as detailed inSection 11.9, is extended when applied to GENSECS. The additional commandoptions available are summarised here.

Positions Derived From P-lines (see Section 5.9.2):

The distance value along the p-line may be preceded by the keywordDISTANCE. For example:

PPLINE TOS DISTANCE distance FROM END ...

The position along the p-line may be measured from the plane normal to theend of the GENSEC, from the cutback plane, or from the joint end preparationcutback. For example:

PPLINE TOS OF /BEAM1 NORMAL ...PPLINE TOS OF /BEAM1 NOCUTBACK ...PPLINE TOS OF /BEAM1 CUTBACK ...

It is possible to define a proportional and an absolute distance position at thesame time. For example:

PPLINE TOS PROPORTION value DISTANCE distance ...

Positions may be measured along the actual p-line specified, or along the Spineand then projected onto the p-line. For example:

PPLINE TOS distance VIA SPINE FROM END ...PPLINE TOS PROPORTION value VIA PLINE ...

The element specified by the OF keyword may be a POINSP or a CURVE. Thisredefines the element to be the GENSEC owning the POINSP or CURVE,rather than the current element or an element defined with the p-line choice.This sets:

• the direction along which DISTANCE and PROPORTION are to bemeasured;



5-47

• in the case of a CURVE, the POINSP to be used as the origin from whichDISTANCE and PROPORTION are measured;

• the segment of the GENSEC to which PROPORTION is applied as:

• the named CURVE,

• the segment following the POINSP (from START), or

• the segment preceding the POINSP (from END).

For example:

PPLINE TOS PROPORTION 0.4 FROM END VIA SPINE OF /CURVE3

calculates a position 40% along /CURVE3 measured from its end.

If no POINSP or CURVE is specified, PROPORTION is calculated from thestart of the GENSEC.

Directions and Offsets Derived From P-lines (see Section 5.9.3):

Directions and offsets derived from p-lines can have a derived position insertedafter the direction/offset option and before the OF option. This lets you specifythe position along the p-line at which the direction/offset is to be calculated.For example:

PPLINE TOS X DIRECTION PROP 0.4 VIA PLINE FROM END OF/CURVE3PPLINE TOS OFFSET FROM PPLINE BOS DISTANCE 200 FROM END

If no position is given, the direction/offset is calculated using the start of theGENSEC or element specified by the OF option.

Picked Positions on P-lines:The following syntax lets you derive a position on a p-line which is nearest to aprobe line:

PPLINE pline_name NORMAL/CUTBACK NEAR direction THROUGHposition [VIA SPINE/PLINE] BOUND/UNBOUND

The probe line starts at the THROUGH position and extends in the specifieddirection. The expression returns the nearest point on PLINE pline_name.

If BOUND is set, the point is either on the p-line or at the ends (where itintersects the NORMAL or CUTBACK end of the GENSEC). If UNBOUND is set,the point can be on the tangential extension of the p-line.

The point returned will be in or above the plane through the THROUGHposition, normal to the probe line; that is, the point will not be behind theTHROUGH position.

The VIA SPINE/PLINE option is used if the point is to be returned with itsdistance along the p-line from the start of the segment.

If pline_name is specified as ANY, all plines of the GENSEC will be probed andthe closest p-line will be used.



Version 11.3

5-48

Identifying P-line Elements:P-line expressions can be used in any positioning command (DISTANCE,PROPORTION, NEAR etc.) in the following way:

ID SEGMENT PPLINE ... positioning_commandID ONPLINE PPLINE ... positioning_command

ID SEGMENT returns the identity of the POINSP at the start of the segmenton which the specified position occurs. ID ONPLINE returns the identity of thep-line on which the specified position occurs. (The latter is only useful for thePPLINE ANY option, otherwise it simply returns the identity of the specified p-line.)

The following expressions use keywords analogous to the OFFSET optionbetween the p-line specification and the subsequent positioning command:

PPLINE pline_name PLDIST positioning_commandPPLINE pline_name PLKEY positioning_commandPPLINE pline_name SEGMENT positioning_commandPPLINE pline_name ONPLINE positioning_command

PPLINE...SEGMENT and PPLINE...ONPLINE return references to the segmentand p-line, respectively, on which the point is specified. PPLINE...PLDISTreturns the distance along the segment on which the point lies, in the directionspecified in the positioning_command (FROM START or FROM END).PPLINE...PLKEY returns the name (the PKEY) of the p-line on which the pointlies.

5.13.5 Positioning Items Relative to Generic Sections

A GENSEC cannot own Fixings directly, but only via member JustificationLine Datum and P-line Datum elements which together define the p-lineconfigurations to be used as references for positioning and orientating theFixings.

The Justification Line Datum (JLDATUM) element defines a frame ofreference for its members based on the p-line system of its owning GENSEC.Each JLDATUM can own a set of P-line Datum (PLDATUM) elements, eachof which defines a frame of reference for its members based on a nominated p-line of its owning JLDATUM. By manipulating a JLDATUM, all of its memberPLDATUMs can be manipulated as a group, together with any Fixings ownedby the latter.

Note: The JLDATUM and PLDATUM elements together serve similarfunctions to the Secondary Nodes (SNOD) used for positioning Fittings(FITT), Compound Fittings (CMFI), Secondary Joints (SJOI) andCompound Secondary Joints (SCOJ) relative to Sections (SCTN). Theyalso provide similar functions to those used for positioning PanelFittings (PFIT) and Compound Panel Fittings (CMPF), depending onthe GENSEC configuration (remember that a GENSEC can model awide range of geometries, including structural sections and panels).



5-49

Specifying Position:The position of a JLDATUM origin may be queried via a pseudo-attribute (QPOS), but this cannot be set explicitly. The position is derived from thefollowing attribute settings:

• TPREF and HPREF specify, by reference to POINSPs of the parentGENSEC (more strictly, its Spine), the start and end points, respect-ively, between which interpolated positions will be calculated. If both areunset, TPREF defaults to start of the GENSEC and HPREF defaults tothe end of the GENSEC. If only one is set, the other defaults to the nextPOINSP in the appropriate direction.

• PKDI specifies a point, as a proportion of the distance from TPREF toHPREF, from which ZDIST is to be measured. The default setting is 0,giving a position at TPREF. If PKDI is less than 0 or greater than 1, theposition will be on the preceding or following segment, respectively, ofthe Spine.

• ZDIST specifies the distance of the JLDATUM origin from the PKDIpoint, as measured along the Justification Line (JUSL) or NA p-line ofthe GENSEC.

= Spine of GENSEC= POINSP

PKDI=0 PKDI=0.5 PKDI=1

ZDIST

= JLDATUM Position

TPREF HPREF

for PKDI=0.5

Specifying Orientation:The orientation of a JLDATUM may be queried via a pseudo-attribute (Q ORI),but this cannot be set explicitly. The orientation is such that its Z axis is in thedirection of the Spine (i.e. the NA p-line) at the POS. The Y axis is in the Ydirection (YDIR) of the Spine, modified by the Beta Angle (BANG) setting, atthe POS.

5.13.6 Generic Fixings Representing Joints and Fittings

A Fixing can represent any type of joint or fitting attached to a GenericSection. It can own other Fixings, so that it can also represent compound jointsand fittings. Its geometry is defined by a reference to a parameterisedCatalogue item in the usual way.

The position and orientation of a Fixing attached (indirectly) to a GENSEC arespecified by reference to the coordinate systems of the parent PLDATUM andJLDATUM. These can be set relative to any POINSP under the GENSEC,



Version 11.3

5-50

including a POINSP which has been specially inserted for this purpose ifnecessary, as summarised in Section 5.13.5. The default position andorientation of the Fixing relative to its owning PLDATUM are specified by itsPOS and ORI attributes, respectively.

Fixings Representing Joints:The detailed position of a Fixing whose SPREF attribute points to a CatalogueJoint is specified using the Joining Line attributes of the owning and attachedsections: JLNS (start) and JLNE (end). The JNLS/JNLE are related to theorigin and orientation of the joint; if the attached GENSEC is curved, these p-lines are taken as parallel to the attached end of the GENSEC. Whenconnected, the JLNS/JLNE line of the attached section intersects with theJLIN line of the Fixing on the Joint Origin Plane.

A GENSEC attached to a joint at one end will have either its JOIS (start) orJOIE (end) attribute set to reference the Fixing; conversely, the CREF(Connection Reference) attribute of the Fixing will reference the attachedGENSEC. This two-way cross-reference is used when either the Fixing or theGENSEC is modified, or when a CONNECT command is used.

5.14 Representing Building Components

The elements used to represent structural steelwork designs can also be usedto represent the components involved in building design; for example, walls,floors, floor screeds, doors, windows, etc. It is recommended that such elementsare created by using the DESIGN Walls & Floors applicationware rather thanfrom the command line, since this will ensure that all relevant attributes areset in a consistent way, but the options are summarised in this section forreference purposes.

5.14.1 Using Element Soft Types

To distinguish the elements used for building representation rather than forother types of structural design, element soft types are used. These areelements which have the same attributes as standard (hard type) elements,but which have different names to identify their functions.

The soft types used for building design are as follows:

Compound Wall (CWALL): a soft type of Subframework (SBFR), used tohold one or more wall components representing, say, one storey of a multi-storey building.

Compound Floor (CFLOOR): a soft type of Subframework (SBFR), usedto hold one or more floor components representing, say, one storey of a multi-storey building.

Compound Screed (CSCREED): a soft type of Subframework (SBFR),used to hold one or more screed components representing, say, one storey of amulti-storey building.



5-51

Straight Wall (STWALL): a soft type of Section (SCTN), used to represent awall created by extruding a 2D catalogue profile from a start position to an endposition.

[Curved] Wall (WALL): a soft type of Generic Section (GENSEC). Thiscan, in principle, be used to represent any shape of wall created by extruding a2D catalogue profile along a path defined by a Spine. The Walls & Floorsapplication for Version 11.3 restricts the use of this element to therepresentation of a Ring Wall, for which the Spine path is all or part of acircle.

General Wall (GWALL): a soft type of a Panel (PANE), used to represent awall created by extruding a user-defined 2D shape through a specified distance(equivalent to the Panel's height/thickness). This could be used, for example, torepresent a column, where the 2D shape of the column's cross-section isextruded vertically to the required column height.

Wall and Floor Fittings, such as doors, windows, manholes etc.,can berepresented by Compound Fittings (CMPF), Sub-Compound Fittings(SBFI), Fittings (FITT), Panel Fittings (PFIT) or Fixings (FIXI) in theusual way.

5.14.2 Controlling Edge Representation in DRAFT

When you plot walls and floors in DRAFT, you may want to remove the lineswhich represent common edges between such elements (referred to as'unioning' the elements) to give a more realistic appearance. The elementsused to represent buildings have an attribute specifically for this purpose: theDRAFT Union (DUNION) attribute.

The elements to which this attibute applies are: Zone, Structure, Framework,Subframework, Compound Wall, Compound Floor and Compound Screed.

In each case, the DUNION attribute can take one of the following values:

DUNION=0 Common edges always shownAll common edges between adjoining elements will be drawn in DRAFT.

DUNION=1 Common edges not shown between membersCommon edges between adjoining elements will be drawn in DRAFT unless apair of such elements are both members of a common parent, in which case theedge lines will be removed.

DUNION=2 Common edges not shown between members and peersCommon edges between adjoining elements will be drawn in DRAFT unless apair of such elements are either both members of a common owner or are at thesame hierarchic level with a common parent, in which cases the edge lines willbe removed.

In the simplest cases, the effects are as shown in the following diagram:



Version 11.3

5-52

DUNION = 0

DUNION = 1

DUNION = 2

The overall effect in DRAFT is determined by the composite effects of thesettings for all significant elements (i.e. all elements which have a DUNIONattribute) above those being drawn. For example:

When DUNION = 0, all members of the current element will be 'assembled'together rather than 'unioned': joint lines will therefore be shown betweentouching members (e.g. between adjoining Panels).

When DUNION = 1 for a FRMW or SBFR (or equivalent soft types), allmembers will be unioned: joint lines between touching members (e.g. adjoiningPanels) with the same owner will not be shown. The FRMW or SBFR will notitself be unioned with another FRMW or SBFR.

When DUNION = 1 for a ZONE, STRU or FRWM, all member STRUs, FRMWsand SBFRs with DUNION = 2 will be unioned. Thus, joint lines will not beshown between adjoining Panels with different owners. The ZONE, STRU orFRMW will not itself be unioned with another ZONE, STRU or FRMW.

When DUNION = 2 for any element, all members with DUNION = 2 will beunioned, and the current element will also be unioned to others which sharethe same owner and which have DUNION = 2 as long as the owner hasDUNION = 1 or 2.


6 Design Templates

This chapter explains the concept of Design Templates, which let you createand store standard design configurations for subsequent use, and the DesignDatasets which hold the parameterised data settings for such templates.

6.1 The Concepts

A design template is a set of design primitives, panels and nozzles that may begrouped together and then referenced from within another part of the designdatabase as though it were a single item. In many ways, a design templatebehaves in a similar way to a catalogue component, except that the templateitems are stored in a special area of the Design DB, rather than in a separateCatalogue DB, and they can use the more powerful sets of primitives andparameterisation facilities available from within DESIGN. Unlike a cataloguecomponent, a design template can be split down into its constituent parts forselective reporting, dimensioning, MTO, etc.

A design template is used in a design by creating an instance of the template.When a design template is instanced, the template contents are copied into thedesign hierarchy and a reference is set to the original template definition. Atthis release version, a design template may only be copied under a PanelFitting, a Section Fitting or a Primary Joint. A design element cannot ownmore than one design template, nor can one design template own anothertemplate.

Design templates may be parameterised to allow a single template definitionto be used in different circumstances. The parameterisation facilities useDesign Datasets to store named parameters, which may then be referenced ingeometric and p-point definitions. The value assigned to a parameter can bedefined in terms of a rule by using any of the standard PDMS expressionsyntax.

Note: The definition of Design Templates is likely to be done by the personwho organises PDMS Catalogue and Specification data in a company,while the use of Design Templates for building up a design model willbe carried out by a plant designer. Therefore, although both functionsare carried out in DESIGN, this chapter is relevant to two differenttypes of PDMS user.

Design Templates


Version 11.3

6-2

6.2 The Design Template Hierarchy

Design Template (TMPL) elements are usually stored in a separate DesignDB under an administrative Template World (TPWL), which is itself dividedinto administrative Template Areas (TMAR).

Each TMPL is initially created as a copy of an existing set of design elementswhich have been created in a part of the usual hierarchy below a SITE. TheTMPL may then be modified by the addition of positive and/or negativeprimitives, negative extrusions, etc. For example, a very simple template,consisting of a positive box and a negative box, could be created thus:

World (/*)

SITE

ZONE

EQUI

BOX

NBOX

TPWL

TMAR

TMPL

BOX

NBOXCopy

When this template is instanced in a design model, say under a panel fitting,its constituent elements are copied back and all parameterisation rules areexecuted so that the attributes of the copy are set to suit the local designrequirements, thus:

PANE

PLOO

PAVEs

PFIT

TMPL

BOX

NBOX

TMAR

TMPL

BOX

NBOX

TPWL

Copy and Execute Rules

All attributes of the copy are locked to prevent unintentional changes.

Design Templates


6-3

6.3 Parameterisation using Design Datasets

Design Datasets (DDSE) are used to store the properties of design templateitems, which may then be used to define the template’s parameters. Eachproperty is stored in a Design Data (DDAT) element under a DDSE, witheach DDAT being identified by a keyword held in its DKEY attribute. Theproperty definition can be specified by an expression held in the DDPR(Design Data Property) attribute, while a default value for the property (to beused if the expression cannot be evaluated for any reason) can be stored in theDDDF (Design Data Default) attribute.

Unlike a design reference to a catalogue component, which can access only asingle catalogue dataset via its DTREF setting, a reference to a designtemplate can access more than one design dataset. A local design dataset isowned directly by the current element, a template design dataset is ownedby the first template below the current element, while a current designdataset is at the same level as the current element and has the same owner.

The following diagram illustrates the relative positions of these types ofdataset for a simple hierarchy:

PFIT

DDSE(1)TMPL

DDSE(2)BOX

local

template

local

current

current

The pseudo–attributes available for accessing the properties data in thevarious types of dataset are as follows:

List of property keys

Real property values

Text or real property values

Text or real property default values

CurrentDataset

Local Dataset

Template Dataset

CDPL

CDPR

TCDP

TCDD

DEPL

LDPR

DEPR

DEPD

PRLS

PROP

PRDE

Reference settings

TDPR

CFDP LFDP TFDP

Design Templates


Version 11.3

6-4

Note: The dataset attributes PRLS, PROP and PRDE are also used to referto catalogue dataset properties. If you query any of these attributes, asearch for a catalogue dataset will be made first; if this fails, a searchfor a design template dataset will be made.

Most commonly, a design attribute value will be defined in terms of a designproperty by using the CDPR (Current Design Dataset Property) attribute. TheCDPR can also be used to define a property in one dataset in terms of aproperty in another dataset. When a CDPR is used in a rule for a componentwhose owner can own datasets, the current datasets will be those at the samelevel as the component: otherwise, the current datasets will be those under thefirst dataset-owning element above the component. When a CDPR is used in aproperty expression within a dataset, it refers to a property in the currentdataset for the item at which CDPR is evaluated.

When used in a querying command or in an expression (for example, whendefining a parameterisation rule), the attributes for a specific property areidentified by the DKEY for that property. For example:

Q CDPLLists all DKEYs for properties in current dataset.

Q CDPR LENGGives value of LENG property in current dataset.

RULE SET XLEN (CDPR LENG)Sets rule for current element’s XLEN attribute using value from LENGproperty in current dataset.

Note: Usually default values are assigned to properties, which are then usedto evaluate expressions during the creation of a design template. Thislets you see the template geometry in a graphical view, at a practicalscale, as you define it. Thus a default value for LENG in the lastexample would allow a sensible XLEN dimension to be evaluated fromthe rule for display purposes. When instanced in a design, the value ofthe LENG property would be derived from, say, a design parameterand the rule would be re–executed to give the correct XLEN.

6.4 Assigning Local Names to Template Elements

When a design template is copied, confusion can arise in the identification ofmembers of the template instance. If a template rule refers to an element byits hierarchic position (e.g. BOX 1 OF TMPL 1 OF ... etc.), rule executionerrors can arise if the template instance is modified in any way which affectsthe ordering of the members list. Even if the element has a PDMS nameunder the Template World, this name will be lost when the template is copiedbecause an element name cannot be used more than once in a Design database.

To avoid these problems, you can assign a local name (LNAME) to a templatemember. Each local name, and the reference of the corresponding element, is

Design Templates


6-5

stored in an array attribute of the template. Local names are therefore set andqueried at member element level, even though they are stored at templatelevel. The local name survives a template copy operation.

6.4.1 Setting Local Names

Keywords: LNAMEDescription: Lets you assign a local name to a template member, or unset an

existing local name. A local name can have a maximum of 20characters; a maximum of 500 local names can be stored on onetemplate. The local name cannot be modified if either the element orits owning template is locked.

Examples:

LNAME /ANTHONY

Sets local name for current element

LNAME UNSET

Unsets local name for current element

Command Syntax:

>--- LNAMe ---*--- local_name ---.| |‘--- UNSET --------+--->

Querying:

Q LNAMe Gives local name for current element

Q LNLST Lists all local names for elements under current template

Q ATT (Note that local names are stored in a compressed numeric format)

6.4.2 Using Local Names in Expressions

Keywords: LNID MLNIDDescription: Lets you identify an element by its local name in a rule or dataset

expression.

Examples:

LNID /SID

Identifies element defined in current template

Design Templates


Version 11.3

6-6

MLNID /JOE

Identifies element defined in member template (i.e. in template owned bycurrent element)

(XLEN OF LNID /SID)

Uses dimension of locally named element in expression (XLEN OF MLNID/JOE)

Command Syntax:

>---+--- LNid ----.| |‘--- MLNid ---+--- local_name --->

Querying:

Q LNID /SID For element in current template

Q MLNID /JOE For element in member template

6.5 Setting Priorities for Evaluating Rules

By default, the rules for the member elements of a design template areexecuted in descending hierarchic order. If the rule for one member elementincludes a reference to the result of a rule for another member, it is importantthat the latter rule is executed before the former, otherwise an incorrect resultwill be obtained.

You can control the order in which the rules for a given template will beexecuted by assigning a rule sequence number to any element which has alocal name. When the template rules are re-executed, the rules for suchelements will be executed in ascending order of their sequence numbers: therules for elements with sequence numbers unset (or zero) will then be executedin the default order. Each rule sequence number, and the reference of thecorresponding element, is stored in an array attribute of the template. Rulesequence numbers are therefore set and queried at member element level, eventhough they are stored at template level.

Keywords: RSEQNUMBERDescription: Lets you assign a rule sequence number to any design template

member which has a local name. The rule sequence number must be apositive integer (zero is equivalent to unset). The same sequencenumber may be assigned to more than one element, but this is notrecommended.

Design Templates


6-7

Examples:

RSEQN 3

Sets rule sequence number for current element (which must be a member ofa design template and must already have a local name)

RSEQN UNSET

Unsets rule sequence number for current element

Command Syntax:

>--- RSEQNumber ---+--- integer ---.| |‘--- UNSET -----+--->

Querying:

Q RSEQN

Gives sequence number for current element

Q RSEQA

Lists sequence numbers for all elements under current template (in theorder in which their local names were set)

Q RSEQFA

Lists local names for elements under current template, sorted by rulesequence number; i.e. in order of rule execution priority

6.6 Adding Design Points to Template Elements

The design datasets for a template, as discussed in Section 6.3, approximate tothe Geomset data for a catalogue component. In a similar way, designtemplates can also own Design Pointsets (DPSE), which approximate to thePointset data for a catalogue component. These let you assign p-points todesign template items, to be used as references for subsequent positioning andorientating operations.

A design pointset can store three types of p-point (note that these are not thesame as those available in catalogue pointsets):

• A Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only,thus:

Design Templates


Version 11.3

6-8

ZY

X

Origin

Orientation

Direction of Normal

DesignPoint

• A Cylindrical P-point is specified as a position on the surface of acylinder at a given position and with given dimensions, thus:

ZY

X

Origin

Orientation

Direction of Normal

DesignPoint

Cylinder defined by its position, height and radius

Angle defining point position wrt Y axis

• A Spherical P-point is specified as a position on the surface of a sphereat a given position and with given dimensions, thus:

ZY

X

Origin

OrientationDirection of Normal

Design Point

Sphere defined by its position and radius

Direction radius acts in, defining point position wrt sphere's centre

Design Templates


6-9

6.7 Using a Design Template Item in a Design

To create an instance of a ‘source’ design template in a design model, you mustfirst create a template below the owning design element and then copy intothis the details of the source template (which must be in a template world)from which it is to derive its data. The commands (at the design elementwhich is to own the instance) are:

NEW TMPLCOPY REXEcute template_identifier

where template_identifier is the name of the source template. The effects areas follows:

• All elements below the original design template are copied below the newTMPL.

• All template rules are copied and re–executed, thus setting the attributesof the new TMPL members to suit the design data.

• The Origin Reference (ORRF) attributes for the new TMPL elements areset to point to their equivalents in the source template.

• All elements below the new TMPL are locked to prevent unintentionalchanges to any of their attributes.

If you want to change an attribute explicitly, thereby causing it to differ fromthe design as specified in the source template, you must first unset the ORRFreferences which point back to the source and unlock the members. To do so,use the command

UNTIE template_instance

where template_instance is the name of the copy TMPL in the design modelhierarchy.

6.8 Portsets and Linksets

If you list the possible members of most types of design element, you will seetwo new elements called Portsets (PORS) and Linksets (LNKS). These havebeen added to the database definition to permit future developments whichwill allow logical connections to be made to items derived from designtemplates. They are not intended for general use at this release version ofPDMS.


7 Groups

The commands described in this chapter allow you to define groups of itemsthat can then be manipulated as a single entity. Note that these commandshave largely been superceded by the use of lists and collections, defined usingexpressions.

7.1 Defining Group Contents

Keywords: GADD GREMOVE MEMBERS ITEMS ALL OFDescription: The contents of a Group are defined by adding or removing references

to or from the list part of the Group.

In order to use the commands described in this section, the currentelement must be the Group whose member list you wish to modify.Specified elements are then added to the list part of the currentelement starting from the current list position or are removed from thelist part of the current element such that the current list positionbecomes the Head position.

The elements to be added to, or removed from, the Group’s memberlist may be specified in any of the following ways:

• Explicitly, by name or (system-assigned) reference number.

• As members of specified elements, where a member of anelement is defined as any element immediately below it in theDB hierarchy

• As items of specified elements, where an item of an element isany element anywhere below it in the hierarchy which has no listpart (such as a Valve, Point, Box, etc.)

• By type (such as Equipment, Branch, Pipe, etc.)

Examples:

GADD /ZONE1 /VALVE2Adds /ZONE1 and /VALVE2 to the current Group, starting from the currentlist position

GREMOVE /ZONE1 /BOX3Removes /ZONE1 and /BOX3 from the current Group and moves the currentlist position pointer to the Head position

Groups


Version 11.3

7-2

GADD MEM OF /BRANCH1 /BRANCH2Adds all the pipe Components in Branches /BRANCH1 and /BRANCH2 tothe current Group, starting from the current list position

GREM MEM OF /PIPE100 MEM OF /EQUI-BRemoves all Branches of the Pipe /PIPE100 and all members of Equipment/EQUI-B from the current Group

GREM ITEMS OF /ZONE2Removes from the current Group all occurrences of those offspring of/ZONE2 which are items

GADD ALL EQU BRAN OF /ZONE1 /ZONE2Adds all offspring of /ZONE1 and /ZONE2 which are of types Equip orBranch to the current Group, starting from the current list position

Command Syntax:

>--+-- GADD -----. .-------------.| | / |‘-- GREMove --+---*-- <selatt> ---+--->

7.2 Accessing Groups

Keywords: ENDDescription: Groups exist outside the normal design hierarchy in a Group World

(GPWL). The available Group Worlds can be seen by queryingMembers at the top (WORLD) level in the hierarchy. Groups can beaccessed either directly by name, or by descending the hierarchy in thenormal way. The items in a Group are shown as Members, but it isimportant to appreciate that the Group does not actually own them.These Members all have normal locations in the design hierarchy, butare also Members of a Group.

Examples:

END (At a Group Member)If the current element was accessed via the Group, the Group will beaccessed. Otherwise the current element’s owner will be accessed.

OWNER (At a Group Member)The current element’s owner will always be accessed regardless of themethod of access to the current element.

Command Syntax:

See the navigation commands described in Part 1 of the PDMS DesignReference Manual.

Groups


7-3

7.3 Deleting Groups

Keywords: DELETEDescription: The action of this command differs from normal behaviour if the

current element is a Group.

Examples:

DELETE GROUPOnly the current element and any Offspring that are Groups will be deleted.

DELETE GPWLDOnly the current element and any Offspring that are Groups will be deleted.

DELETE GROUP MEMThe Members of the Group are deleted in the following way:

• If the member is not a Group, it is deleted with all its Offspring.

• If the member is a Group, only the member and any Offspring that areGroups are deleted.

Command Syntax:

>-- DELETE <snoun> -+-- MEMbers --+-- integer --+-- TO integer ->| | || | ‘-->| ‘-->‘-->

7.4 Copying a Group

Keywords: COPYDescription: Groups may be copied with a slightly different effect to normal

elements.

Examples:

COPY /GROUP21 (At a Group.)The Current Group will contain exactly the same Members as /GROUP21.No new elements have been created.

COPY MEM OF /GROUP21 (At a Zone.)The current Zone will contain new elements which are identical to theMembers of /GROUP21 provided these elements are all legal members of aZone.

COPY MEM OF /GROUP21 RENAME /MAIN /SPAREAs above, but with renaming.

Groups


Version 11.3

7-4

Command Syntax:

>- COPY -+- MEMbers -+- integer -+- TO integer -.| | | || ‘-----------+--------------+- OF <sgid> -+- REName name name ->| || ‘->|- ALL OF -.| |‘----------+- <sgid> -+- REName name name ->

|‘->

PDMS DESIGN Reference Manual Index-1Part 2: Creating the ModelVersion 11.3

Index

<plin> syntax, 5-30

ALONG command, 2-33

ARRIVE command, 3-31

AT command, 2-6

Attached parameters, 5-41

Attributes

of primitives, 2-1

sections, 5-4

AUTOROUTE command, 4-1

AXES command

pipe routing, 4-2

BANGLE command, 5-7, 5-14

BASE command

pipe routing, 4-7

BEHIND command, 2-27, 3-9, 3-59

Beta angle

joints, 5-14

sections, 5-7

BOP command, 3-9, 3-72

pipe routing, 4-8

Branch

head, 3-3

tail, 3-3

Buildings, 5-50

BUILT flag, 3-36

BY command, 2-16

Cartesian p-point

in design pointset, 6-7

CDPR attribute, 6-4

CHOOSE command, 3-14

CLEARANCE command, 2-35, 3-66

Cofitting element, 5-38

Cofitting Reference Array attribute, 5-38

Compound fitting element, 5-2

Compound Floor element, 5-50

Compound joint element, 5-1

Compound panel fitting element, 5-2

Compound Screed element, 5-50

Compound Wall element, 5-50

CONNECT command, 2-14, 3-3, 3-45,5-19

Connection

forced, 3-46

CRFA attribute, 3-39

CTYEND command, 5-8

CTYSTART command, 5-8

Current design dataset, 6-3

Current Design Dataset Propertyattribute, 6-4

CURTYP attribute, 5-43, 5-45

Curve element, 5-43

Curve Type attribute, 5-43, 5-45

CUTBACK command, 5-18

CUTPLANE command, 5-18

Cylindrical p-point


DDAT element, 6-3

DDDF attribute, 6-3

DDPR attribute, 6-3

DDSE element, 6-3

DELPOSITION command, 5-14

Design Data Default attribute, 6-3

Design Data element, 6-3

Index


Version 11.3

Index-2

Design Data Property attribute, 6-3

Design Dataset element, 6-3

Design parameters, 5-40

Design Pointset element, 6-7

Design Template element, 6-2

DESPARAMETER command, 5-40

Detail level, 2-3

DIRECTION command, 3-43

DISCONNECT command, 5-21

DISTANCE command, 3-49, 3-53

DKEY attribute, 6-3

DPSE element, 6-7

DRAFT Union attribute, 5-51

DRAG command, 3-78

DRNEND command, 5-6

DRNSTART command, 5-6

DUNION attribute, 5-51

Edge drawing, 5-51

Elements

connecting, 2-14

moving, 2-16

orientating, 2-11

rotating, 2-12

End position (section), 5-4, 5-5

ERELEASE command, 5-9

EXTEND command, 5-25

FCONNECT command, 3-46

Fitting element, 5-2, 5-38

compound, 5-2

panel, 5-2

Fixing element, 5-2, 5-44, 5-49

FLIP command, 3-31, 5-22

Floors, 5-50

FORCECONNECT command, 3-14

Forced connection, 3-46

FROM command, 3-53

GADD command, 7-1

Generic Fixing element, 5-49

Generic Section element, 5-2, 5-43

GENSEC element, 5-2, 5-43

GREMOVE command, 7-1

Group element, 7-1

HBOR command, 3-6

HCON command, 3-6

HDIR command, 3-6

Head of branch, 3-3

HPOS command, 3-6

HREF command, 3-5

HSPE command, 3-2

HSROD attribute, 3-33

HSTUBE attribute, 3-33

IDPLINE command, 5-30

INFRONT command, 2-27, 3-9, 3-59

Instance

Design templates, 6-1

Insulation specification, 3-35

ISPEC attribute, 3-35

JLDATUM element, 5-43, 5-48

JOIEND command, 5-8

Joint

creating, 5-12

Joint element

compound, 5-1

linear, 5-1

primary, 5-1, 5-12

secondary, 5-1, 5-13

Joints

attributes, 5-17

linear, 5-35

primary, 5-14

secondary, 5-15

JOISTART command, 5-8

Justification Line Datum element, 5-43,5-48

Index


Index-3

LEAVE command, 3-31

LEVEL command, 2-3

Linear joint element, 5-1

Linear joints, 5-35

LINK command, 5-36

LNAME, 6-5

LNID, 6-5

Local design dataset, 6-3

Local name


LOFF attribute, 3-39

LSROD attribute, 3-33

LSTUBE attribute, 3-33

MIRROR command, 2-45

MLNID, 6-5

MOVE command, 2-17, 3-11, 3-47

Node element

primary, 5-1

secondary, 5-1

Nodes

primary, 5-2

secondary, 5-11

Nozzle offset factor

pipe routing, 4-5

Nozzles

specifying, 2-3

OBSTRUCTION command, 2-4

Obstruction level

clash detection, 2-4

OFFSETFACTOR command, 4-5

ONTOP command, 2-30, 3-9, 3-62

OPDIRECTION command, 5-14

ORDER command

pipe routing, 4-8

ORIENTATE command, 2-11, 3-41

Orientation, 2-11

ORIFLAG attribute, 3-37

Owning parameters, 5-41

Panel fitting element

compound, 5-2

Panel Fitting element, 5-2, 5-38

Panel Fitting Reference attribute, 5-38

Panel Loop element, 5-1

Panel Vertex element, 5-1

Panels

connecting, 5-35

creating, 5-34

splitting, 5-34

Parameters

attached, 5-41

design, 5-40

owning, 5-41

Penalty volume

pipe routing, 4-2, 4-3

PH command, 3-7

Pipe rack

pipe routing, 4-6

Pipe routing, 4-1

PJOINT command, 5-12

PLDATUM element, 5-44, 5-48

Pline Datum element, 5-44, 5-48

PNODE command, 5-2

POINSP element, 5-43

POLAR command, 2-8

Polar positioning, 2-8

POSEND command, 5-5

POSFLAG attribute, 3-37

POSITION command, 2-6, 3-49

Positioning, 2-6

POSLINE command, 5-15

POSSTART command, 5-5

PPLINE command, 5-30

Primitives

attributes, 2-1

Index


Version 11.3

Index-4

Profile element, 5-1, 5-4

PSPE command, 3-2

PT command, 3-7

PVOL command, 4-3

RACK command, 4-6

RECONNECT command, 3-13, 5-21

RESELECT command, 3-26

Ring Wall element, 5-51

Rod

attributes, 3-33

ROTATE command, 2-12

ROUTE command, 4-4

Routing plane

pipe routing, 4-2, 4-3

RPLANE command, 4-3

RSEQNUMBER, 6-6

Rule sequence number


Screeds, 5-50

SDIR command

pipe routing, 4-6

Sections

attributes, 5-4

connecting, 5-19

creating, 5-3

disconnecting, 5-21

modifying lengths, 5-25

reconnecting, 5-21

SELECT command, 3-20

SHOP flag, 3-36

SHORTCODE command, 3-24

SJOINT command, 5-13

SNODE command, 5-11

Soft types, 5-50

Spherical p-point


Spine element, 5-2, 5-43

Spine Point element, 5-43

SPLIT command, 5-34

SPREAD command

pipe routing, 4-7

SPREF attribute, 3-33

SRELEASE command, 5-9

Start position (section), 5-4, 5-5

Steelwork

fittings, 5-2

fixings, 5-2

generic sections, 5-2

joints, 5-1

nodes, 5-1

panels, 5-1

sections, 5-1

Straight Wall element, 5-51

STRING command, 5-3

Subfitting element, 5-2

Subjoint element, 5-1

Tail of branch, 3-3

TBOR command, 3-6

TCON command, 3-6

TDIR command, 3-6

Template Area element, 6-2

Template design dataset, 6-3

Template World element, 6-2

THROUGH command, 3-51

TMAR element, 6-2

TMPL element, 6-2

TO command, 3-53

TOP command, 3-9, 3-72

TPOS command, 3-6

TPWL element, 6-2

Trace specification, 3-35

TREF command, 3-5

TSPE attribute, 3-35

Tube

Index


Index-5

attributes, 3-33

UNDER command, 2-30, 3-9, 3-62

Unioning edges, 5-51

UNLINK command, 5-36

UNTIE, 6-9

Wall element, 5-51

Walls, 5-50

ZDISTANCE command, 5-11

Pdms Design

Documents

Transcript of Pdms Design