Design Reference Manual - Creating the Model

Design Reference Manual

Creating the Model

DisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaimany and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct described in this publication may be incorporated into any third-party software, product,machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective licence agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthoriseduse of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solutions Ltd

DESIGN Reference Manual

Contents Page


Creating the ModelIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1About the DESIGN Reference Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Organisation of the DESIGN Reference Manual . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Organisation of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Equipment and Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Primitive Modelling Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Sizing Primitive Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Choosing Nozzle Size, Rating and Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2Modelling Detail Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3Obstruction Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4

Positioning at a Known Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5Positioning at a Coordinate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5Polar Positioning from the Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:8General Polar Positioning from the Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9

Orientation and Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10Design Element Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10Design Element Reorientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:12Primitive Element Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:14

Moving by a Known Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:15Moving Along Axes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:15Moving in any Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:16Moving in any Direction: Distance Given in Different Plane. . . . . . . . . . . . . . . . . . . . . . . . 2:18

12.0i


Moving Through Defined Intersection Planes. . . . . . . . . . . . . . . . . . . . . . . . . . 2:19Moving Through an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:19Moving Either Side of an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:21General Moving to an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:23

Moving In Front of or Behind Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:25Moving Either Side of a Fixed Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:26Moving On Top of or Under a Fixed Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:28Moving an Item Using Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:31

Moving to a Specified Clearance between Items . . . . . . . . . . . . . . . . . . . . . . . 2:33Moving to a Clearance Either Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:34Moving an Object to Clear Another Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:36Moving to a Vertical Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:38General Moving to a Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:41

Reflecting a Position in a Plane (Mirroring). . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:42

Piping, Ducting and Cable Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Defining a Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Branch and Hanger Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Connecting the Head or Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2The Head or Tail Connection Reference Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Positioning Head or Tail in Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5Head or Tail Positioning Using End Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6Head and Tail Positioning by Bottom or Top of Pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7Moving the Head or Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9Reconnecting Pipes after an Equipment Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11

Selecting Component and Tube Details from Specifications . . . . . . . . . . . . . 3:11Choosing Components from a Displayed List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12Selecting Components from Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16Selecting the Default Specification Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17Selecting from Several Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17Selecting ‘Out-of-Specification’ Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19Selecting Components and Tube Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20Direct Selection by Shortcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21

Re-selection of Existing Components and Tube . . . . . . . . . . . . . . . . . . . . . . . 3:22Re-selecting the New Default Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22General Reselection of Components and Tube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23

Standard Component Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24Position and Orientation Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26

12.0ii


Component Arrive and Leave Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26Swapping the Arrive and Leave P-points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:27The Component Specification Reference Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:28Variable Length Tube (and Rod) Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:29Insulation Specification Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:30Trace Heating Specification Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:31The Fabrication Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:31Position and Orientation Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:32Variable Component Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:32Offline/Straight-Through Component Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:33Multi-Way Component Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:34

Orientation and Connection of Components. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:35Component Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:35Direction-Changing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:37Component Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:39Forced Component Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:41

Moving by a Known Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:42Moving Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:42General Moving of Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:43

Positioning Components using Reference Planes . . . . . . . . . . . . . . . . . . . . . . 3:44Positioning with respect to the Previous Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:44Positioning the Component through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:46Positioning with respect to an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:48General Positioning through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:51

Positioning Components ‘Point-to-Surface’ . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:52Positioning Components Either Side of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:52Positioning Components On Top of or Under an Object . . . . . . . . . . . . . . . . . . . . . . . . . . 3:55General Component Positioning Using Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:57

Component Clearance Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:59Clearance from the Previous Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:59Component Clearance Either Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:60Component Clearance Vertically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:62Tube (Bottom of Pipe) Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:63General Clearance of Components and Tube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:66

Dragging Equipment and Piping Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:67Dragging Equipment and Nozzles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:68Dragging Piping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:72

Automatic Pipe Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

12.0iii


Accessing the Automatic Pipe Routing Facilities. . . . . . . . . . . . . . . . . . . . . . . . 4:1Entering and Leaving Autoroute Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Pipe Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Routing Pipes along Preferred Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Setting Routing Planes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Setting Penalty Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Invoking the Automatic Routing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Setting the Nozzle Offset Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4

Refining the Automatic Pipe Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5Defining the Rack to be Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5Defining the Direction of Spread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6Defining the Base Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6Spreading Pipes about the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7Setting the Bottom-of-Pipe Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7Combined Spreading and BOP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8

Structural Design Using Catalogue Components . . . . . . . . . . . . . . 5:1Creating and Positioning Primary Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Creating and Connecting Sections Automatically . . . . . . . . . . . . . . . . . . . . . . . 5:3Section Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Cross-Sectional Profile via a Specification Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Generic Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Start and End Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Start and End Plane Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6Orientation Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6Joint Start and End References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7Start and End Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8Start and End Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8

Creating and Positioning Secondary Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9Creating and Positioning Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10Creating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11Creating Secondary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11Setting Joint Geometry via a Specification Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12Positioning and Orientating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12Positioning and Orientating Secondary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13

Attributes of Connected Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15Connection Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15Cutting Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16

12.0iv


Cutback Allowance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16

Manually Connecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17Connecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17Disconnecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:18Reconnecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:19

Repositioning Steelwork Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20Reversing Section Start and End Positions (‘Flipping’) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20Moving Steelwork Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:21Modifying Lengths of Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22Reorientating Steelwork Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:23

Positioning and Orientating Using P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:25Identifying P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:26Positioning by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:27Orientating by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29

Creating and Connecting Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29Creating a Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29Splitting a Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:30Connecting Panels using Linear Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:31

Fittings, Hangers and Equipment Load Points . . . . . . . . . . . . . . . . . . . . . . . . . 5:33Fittings and Panel Fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:33Structure-to-Pipework Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34Structure-to-Equipment Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34

DESIGN, Owning and Attached Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34Setting DESIGN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34Setting Owning and Attached Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36

Representing Curved Beams and Walls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36Defining a Generic Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:37More About Curve Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:38How P-lines Are Used For Generic Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:39Positioning Items Relative to Generic Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:41Generic Fixings Representing Joints and Fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42

Representing Building Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42Using Element Soft Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42Controlling Edge Representation in DRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:43

Design Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

12.0v


Design Template Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Application Data Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2Functional Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4Application Data and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4Extension to Design Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Valid Value Elements Additional Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Extension to Design Data Associated Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Special Design Data Property names in scope of a DDSE . . . . . . . . . . . . . . . . . . . . . . . . . 6:6

Parameterisation using Design Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7Assigning Local Names to Template Elements . . . . . . . . . . . . . . . . . . . . . . . . . 6:8Setting Local Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9Using Local Names in Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9

Setting Priorities for Evaluating Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10Adding Design Points to Template Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11Using a Design Template Item in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12Portsets and Linksets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13

12.0vi

12.0i


Creating The Model


12.0ii

DESIGN Reference ManualIntroduction

1 Introduction

1.1 About the DESIGN Reference ManualThe DESIGN Reference Manual describes all the Design commands in detail.

DESIGN is normally used interactively. The Graphical User Interface (GUI) providesdiscipline-based applications which help you to create, check and report on the model. Howto use the applications is described in user guides and on-line help.

This manual is written for experienced users of PDMS DESIGN who need to usecommands, for example, to write batch macros or to customise the GUI. If you are going tocustomise the GUI, you will also need to refer to the Software Customisation Guide andSoftware Customisation Reference Manual for information about PML, the AVEVAprogramming language.

1.2 Organisation of the DESIGN Reference ManualThe DESIGN Reference Manual has three parts:

• Part 1, General Commands, describes general Design commands, which are used, forexample, for setting up the display, and querying and navigating around the DesignDatabase. It also describes how to use the command syntax graphs, which are used toshow all the options available for each command.

• Part 2, (this volume), describes the commands for creating database elements andsetting their attributes.

• Part 3, Utilities, describes the Design Utilities for data consistency checking and clashdetection, and for exporting Design data to programs such as Review.

1.3 Organisation of this ManualYou should refer to Part 1 of the DESIGN Reference Manual for general information aboutcreating elements and setting the standard attributes which all Design elements have.

This manual, Part 2, is divided into the following chapters:• Equipment and Primitives describes the commands for modelling, including

positioning, orientating and connecting commands applicable to these elements.• Piping, Ducting and Cable Trays describes the commands for modelling, including

selecting Components from the Catalogue, and positioning, orientating and connectingcommands applicable to these elements.

• Automatic Pipe Routing describes the commands for users who require these facilitiesshould enquire about AVEVA’s Advanced Router product.

12.02 1:1

DESIGN Reference ManualIntroduction

• Structural Design Using Catalogue Components, describes its main focus on structuralsteelwork design, with extensions of the concepts to include their use for representingwalls and floors in more general building design.

• Design Templates are groups of elements which can be defined and stored as a singleparameterised element, and then inserted into a model.

For a comprehensive list of all PDMS attributes and pseudo-attributes, see the Plant DesignSoftware Customisation Reference Manual.

12.02 1:2

DESIGN Reference ManualEquipment and Primitives

2 Equipment and Primitives

This chapter describes the modelling and layout of process equipment and civil items.These include items such as pumps, vessels, walls and heat exchangers, which aremodelled within the major hierarchical elements Equipment, Structure, Ptrack andSubstructure. These elements own primitive geometric shapes and holes which aredimensioned and assembled to form a suitable model. The items can then be positionedand orientated as a whole by using one of the comprehensive positioning commands -DESIGN items can either be positioned at a known co-ordinate, or moved by a givendistance or clearance. The same commands can be used to modify existing positions,orientations and dimensions. There are also a number of special plant modification facilitiesthat are described in a later part of the manual.

2.1 Primitive Modelling AttributesThe DESIGN hierarchy is a ‘skeleton’ structure of the elements which represent the chosenorganisation of the model. The physical appearance and layout of the process items aredetermined by the value of each element’s attributes; for example, a Box only looks like abox if its XLEN, YLEN and ZLEN attributes are set (on creation they are zero).

This section describes those physical primitive element attributes that give a shape to themodel. Generally, these attributes will either be set by typing in their values directly or frommacros. It is important, however, to recognise that regardless of how it was input, the basicattribute information is the stored physical description of the designed plant.

2.1.1 Sizing Primitive Building Blocks

Keywords:

XLENGTH YLENGTH ZLENGTH DIAMETER HEIGHT RADIUS XOFF YOFF XTOP YTOPXBOTTOM YBOTTOM DTOP DBOTTOM RINSIDE ROUTSIDE XTSHEAR YTSHEARXBSHEAR YBSHEAR

Description:

The physical shapes of equipment, structural and civil items in the plant are built up bycreating, dimensioning and assembling basic geometric elements. These commandsdirectly set the attributes of basic modelling primitives which give them their precisedimensions. The following primitive shapes are available:

12.02 2:1

Administrator

Line

Administrator

Line


Holes may be plunged through ‘solid’ primitives using a corresponding set of negativeprimitives. The examples given in this subsection refer to the Box and Cylinder; a completedescription of all primitive elements and their attributes can be found in Data ModelReference Manual.

Command Syntax:

Refer to the Data Model Reference Manual.

Figure 2:1. Dimensioning a CYLINDER primitive

2.1.2 Choosing Nozzle Size, Rating and Height

Keywords:

CATREF HEIGHT

Description:

The Nozzle is the only basic equipment primitive that obtains some of its physicaldimensions directly from the PDMS Catalogue. The size and rating are determined by

Box Cone Dish

Cylinder Slope-bottomed Cylinder Snout

Circular TorusRectangular Torus Pyramid

Example:

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

DIAMETER

HEIGHT

12.02 2:2

Administrator

Line

Administrator

Line


setting the CATREF (Catalogue Reference) attribute which refers to an element in theCatalogue. The Nozzle height, however, is determined on site by setting the correspondingHeight attribute. If the CATREF attribute is not set, the ‘Nozzle’ is merely a hierarchicalelement with no geometry.

Command Syntax:>-- CATref name -->

>-- HEIght <uval> -->

2.1.3 Modelling Detail Levels

Keywords:

LEVEL

Description:

This command sets the attribute, common to all primitive elements, that controls modellingdetail. The command specifies a range of modelling ‘levels’ which determine the permanentvisibility characteristics of the element in DESIGN. The attribute allows plant items to beassembled from overlaid primitives representing varying levels of detail. In this way, severalgraphical versions of the same object can be available for different purposes. For example,it may be decided to represent an I-section beam as a single box for simple space-modellingin DESIGN, while using its full cross-section for 2D drawing data in DRAFT.

The LEVEL attribute is specified as two numbers, representing the inclusive range in whichthat item will be drawn. In DESIGN, only primitives of visible items whose LEVEL rangeincludes the LEVEL setting specified by the REPRESENTATION command will be drawn(see Chapter 4 in Part 1 of the DESIGN Reference Manual).

LEVEL ranges for Nozzles and piping are specified in the Catalogue. A company will usuallyestablish rigid standards for the use of LEVELs which are defined permanently in theCatalogue and therefore must be complied with during Equipment and Civils modelling.

Examples:

CATR /NFAARPMM (At Nozzle)

The size and rating of the Nozzle are set by naming the appropriate Catalogue choice.

HEI 2’6 (At Nozzle)

The Height of the Nozzle becomes 2’6.

Example:

LEVEL 6 10

The current primitive will be drawn if the operative drawing LEVEL is within the specifiedrange.

12.02 2:3

Administrator

Underline


Command Syntax:>-- LEVel integer integer -->

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

2.1.4 Obstruction Settings

Keywords:

OBSTRUCTION

Description:

The OBSTRUCTION attribute indicates to the clash detection facility whether a primitiveshould be considered as a ‘Hard’ or ‘Soft’ obstruction, or not at all. Obstructions can bespecified 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.).

Holes (i.e. negative primitives) also have the OBSTRUCTION attribute. OBSTRUCTIONsettings for Nozzles and Piping are given in the Catalogue.

Note: See also Chapter 4 in Part 1 of the DESIGN Reference Manual for details of theSpatial 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.

12.02 2:4

Administrator

Line

Administrator

Line


Command Syntax:>-- OBStruction --+-- integer --.

| ||-- HARD -----|| ||-- SOFT -----|| |‘-- NONE -----+-->

Figure 2:3. Obstruction settings for use in clash detection

2.2 Positioning at a Known PointThese commands allow you to place the Current Element at a known position in space. Youcan:

• Specify explicit coordinates • Specify the position of an existing p-point • Cursor pick with a working grid (WGRID) position

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

2.2.1 Positioning at a Coordinate

Keywords:

POSITION AT

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.

Examples:

12.02 2:5

Administrator

Underline

Administrator

Underline


Description:

This command positions the Current Element directly by giving the 3D coordinates, thename of another element or p-point position, or visually by using the cursor.

Command Syntax:>--+-- POSition <marke> --.

| |‘----------------------+-- AT <bpos> -->

Querying:>-- Query POSition --+-- <bpos> --.

| |‘------------+-- WRT --.

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

Examples:

AT E3’ N4’6 U1’ Current Element will be placed at the specified ownercoordinate position (see Figure 2:4.: Positioning the CurrentElement at a known point).

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

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

POS PIN5 AT E3000 The specified PIN and Current Element will be positioned asa single rigid item, so that the PIN is at E3000 N0 U0 (seeFigure 2:5.: Positioning a PIN and the current elementtogether at a known point).

12.02 2:6


Querying Examples:

Figure 2:4. Positioning the Current Element at a known point

Figure 2:5. Positioning a PIN and the current element together at a known point

Q POS Gives position of Current Element origin in owner coordinates

Q POS IN SITE Gives 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

12.02 2:7


2.2.2 Polar Positioning from the Origin

Keywords:

POLAR DISTANCE

Description:

This command is used to position the Current Element using polar coordinates. This isparticularly useful for positioning Nozzles. The coordinates are relative to the owner’sorigin.


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


| |‘------------+-- WRT --.

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

Examples:

POLAR E45N DIST 300 The Current Element will be placed 300 from itsowner’s origin along E45N (see Figure 2:6.: Polarpositioning from the origin).

POLAR PIN1 DIST 3000 The Current Element will be placed 3000 from itsowner’s origin along the direction of PIN1 (seeFigure 2:6.: Polar positioning from the origin).

POS IDP@ POLAR S1OW DIST3 The p-point hit and the current element will bemoved as a rigid entity so that the p-point is thespecified polar distance from the owner’s origin.

12.02 2:8

Administrator

Underline

Administrator

Underline


Figure 2:6. Polar positioning from the origin

2.2.3 General Polar Positioning from the Origin

Keywords:

POLAR PLANE DISTANCE

Description:

This command differs from the basic polar option by allowing the distance from the owner’sorigin to be specified more generally. The PLANE element of the command enables thisdistance to be given in a direction different from the polar direction. For example, an elementmay be placed on a line North 25 East, and at N250 from the owner’s origin.

Examples:

Command Syntax:>-+- POSition <marke> -.

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

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

Example:

POLAR N30E PLANE NDIST 1000

Positions the Current Element along the N30E line from theowner origin at N1000 (see Figure 2:7.: General polarpositioning from the origin by specifying a plane).

12.02 2:9



| |‘------------+-- WRT --.

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

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

2.3 Orientation and ConnectionThese commands allow the Current Element to be rotated. In the case of connection, theitem is also repositioned.

For both commands, the specification of a single axial direction or p-point on the CurrentElement is sufficient to perform a reorientation. However, a second direction must bespecified if the orientation is to be fixed in 3D space.

2.3.1 Design Element Orientation

Keywords:

ORIENTATE

Description:

Every Design element has its own co ordinate system which consists of a right-handed setof East (X), North (Y) and Up (Z) axes. The precise orientation of an element must be givenas two statements fixing the direction of two axes, e.g. ORI Y IS NORTH AND Z IS UP.When rotating symmetrical items, such as cylinders, it may be sufficient to give one axisdirection only (allowing DESIGN to choose the other), e.g. ORI P1 IS N45E. Regardless ofthe command given, orientation always occurs about the Current Element origin.

12.02 2:10

Administrator

Rectangle

Administrator

Underline


Command Syntax:>- ORIentate -+- <bdir> IS <bdir> -.

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

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

Querying:>-- Query ORIentation --+-- WRT --.

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

Figure 2:8. Design element orientation (1)

Examples:

ORI Y IS N AND Z IS UP The Current Element is rotated about its origin so thatits Y axis is pointing North (in owner coordinates) andits Z axis is pointing up (see Figure 2:8.: Designelement orientation (1)).

ORI P1 IS E The Current Element is rotated so that its P1 p-point ispointing East in owner coordinates (see Figure 2:9.:Design element orientation (2)).

12.02 2:11

Administrator

Rectangle


Figure 2:9. Design element orientation (2)

2.3.2 Design Element Reorientation

Keywords:

ROTATE BY ABOUT THROUGH AND

Description:

The ROTATE command allows you to rotate any Design element, including a Group. Therotation required may be specified in any of the following ways:

• As a specified angle of rotation about the element’s default axis (i.e. the Z axis).• As a specified angle of rotation about a given axis, the latter defined by its direction

and/or through point. If the direction and/or through point are omitted, the defaultdirection is that of the Neutral Axis or Z axis; the default through point is the Origin.

• By reference to the element’s axes.

Example:

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

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

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

ROT THRO P3 ABOUT SBY -25

Rotates element about an axis which passes in the N-Sdirection through its p-point 3 position. The rotation is 25°anticlockwise when looking S along this axis.

ROTATE AND Y IS N45W25D

Rotates element until the Y axis points as closely aspossible to the N45W25D direction.

12.02 2:12

Administrator

Underline

Administrator

Underline

Administrator

Rectangle


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

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

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> -.| | || ‘----------------+->‘->

12.02 2:13

Administrator

Underline


2.3.3 Primitive Element Connection

Keywords:

CONNECT

Description:

The command allows the current primitive element to be ‘connected’ to another element ormapping pin. Any p-point on the Design element may be connected to any other p-point(except p-points on the same element). Mapping pins can also be used to great effect asthey can connect and be connected to. In the former case, both the pin and Current Elementmove as a rigid entity; in the latter, the Current Element moves to the static pin.

The connection operation includes positioning and orientation of the Current Element sothat the two specified Design Points are coincident and of opposite direction.

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> -->|‘-->

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

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

Example:

CONN P2 TO P1 OF /A

The P2 of the Current Element is connected to the specifiedp-point on another element (see Figure 2:10.: Connectingprimitives by direct specification).

CONN PIN1 TO IDP@ The Current Element and PIN1 are moved and rotated sothat PIN1 connects to the p-point hit.

CONN IDP@ TO IDP@AND X IS N

The first point hit (belonging to the Current Element) isconnected to the second point (belonging to anotherelement). The Current Element is rotated so that its X axis isNorth in owner coordinates (see Figure 2:11.: Connectingprimitives by using cursor selection).

12.02 2:14

Administrator

Underline

Administrator

Highlight

Administrator

Underline


Figure 2:10. Connecting primitives by direct specification

Figure 2:11. Connecting primitives by using cursor selection

2.4 Moving by a Known DistanceAll the commands described in this section move the Current Element by a specifieddistance in a given direction. The simplest method is to move from the present positionalong an axis direction using a command such as BY EAST 1000. However, the commandoptions provided enable more complex manoeuvres to be made. For instance, an elementmay be moved ‘towards’ another item until its Easting has changed by a given amount.

2.4.1 Moving Along Axes

Keywords:

BY

Description:

This command displaces the Current Element by given amounts along any East, North, Up(etc.) axes. These are normally the axes of the owner, but the axial system of any element,such as the SITE, can be specified if required.

12.02 2:15

Administrator

Underline

Administrator

Underline

Administrator

Highlight


Command Syntax:>-- BY <pos> --+-- <axes> --.

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


| |‘------------+-- WRT --.

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

Figure 2:12. Moving along specified axes

2.4.2 Moving in any Direction

Keywords:

MOVE ALONG TOWARDS DISTANCE

Description:

This command displaces the Current Element in any specified direction by a given distance.

Examples:

BY E300 N400 Moves the Current Element by the specified amounts alongthe owner’s axes (see Figure 2:12.: Moving along specifiedaxes).

BY E3000 WRT SITE Moves the Current Element by the specified amount alongthe Site’s East axis (see Figure 2:12.: Moving along specifiedaxes).

N

E

N

E

BY E3000 WRT SITE

BY E3000

CE

OWNERAXES

SITEAXES

12.02 2:16

Administrator

Highlight

Administrator

Underline

Administrator

Line

Administrator

Underline


Command Syntax:>-- MOVe --+-- ALOng --.

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


| |‘------------+-- WRT --.

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

Figure 2:13. Moving a given distance in a given direction (1)

Examples:

MOVE N45E DIST 100 The Current Element is displaced along East 45 North inowner coordinates by the specified distance (see Figure2:13.: Moving a given distance in a given direction (1)).

MOVE TOW IDP@ DIST100

The Current Element is displaced towards the picked p-pointby the specified amount (see Figure 2:14.: Moving a givendistance in a given direction (2)).

12.02 2:17

Administrator

Underline


Figure 2:14. Moving a given distance in a given direction (2)

2.4.3 Moving in any Direction: Distance Given in Different Plane

Keywords:

MOVE ALONG TOWARDS PLANE DISTANCE

Description:

This command differs from the basic option by allowing the distance moved to be specifiedin a different plane from the actual movement direction.

Command Syntax:>-- MOVe --+- ALOng -.

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

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


| |‘------------+-- WRT --.

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

Example:

MOVE TOW /DATUM PLANE E DIST1000

The Current Element is moved towards the specified designitem until its Easting (in owner coordinates) has changed by1000 (see Figure 2:15.: Moving in a direction specified in adifferent plane).

12.02 2:18

Administrator

Underline


Figure 2:15. Moving in a direction specified in a different plane

2.5 Moving Through Defined Intersection PlanesThe commands described in this section move the Current Element along a given directionuntil it intersects with a fixed Reference Plane.

Any p-point on the Current Element may be used for the manoeuvre, although the default isthe origin. This point is moved to the Reference Plane which is specified by the 3D positionthrough which it passes. The orientation of the Reference Plane defaults to perpendicular tothe movement direction.

In no case is the volumetric geometry of any of the Design model considered. Although youdo not need to know the actual distance moved, you must provide ‘point-to-point’dimensions in these commands. In other words, these commands cannot calculate physicalclearances (see Moving In Front of or Behind Items and Moving to a Specified Clearancebetween Items for such commands).

2.5.1 Moving Through an Intersection

Keywords:

MOVE THROUGH

Description:

This command moves the Current Element until its origin intersects with the ReferencePlane through a fixed 3D point.

12.02 2:19

Administrator

Underline

Administrator

Underline

Administrator

Underline


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


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


| |‘------------+-- WRT --.

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

Figure 2:16. Moving along a given direction through an intersection

Examples:

MOVE N30W THR /BOX Moves the Current Element along the given direction untilit ‘intersects’ the Reference Plane through the origin ofthe named element (see Figure 2:16.: Moving along agiven direction through an intersection).

MOVE E THR E3000 Moves the Current Element along the given owner axisuntil it ‘intersects’ the Reference Plane through E3000 N0U0 (see Figure 2:17.: Moving to intersect a plane througha given point).

MOVE ALONG N45E THRIDP@

Moves the Current Element along the given direction untilit ‘intersects’ the Reference Plane through the picked p-point (see Figure 2:18.: Moving to intersect a planethrough a given point).

12.02 2:20

Administrator

Rectangle


Figure 2:17. Moving to intersect a plane through a given point

Figure 2:18. Moving to intersect a plane through a given point

2.5.2 Moving Either Side of an Intersection

Keywords:

MOVE DISTANCE FROM TO

Description:

This command moves the Current Element until its origin intersects the Reference Plane agiven distance either side of a fixed 3D point.

12.02 2:21

Administrator

Rectangle

Administrator

Rectangle

Administrator

Underline

Administrator

Underline


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


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

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


| |‘------------+-- WRT --.

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

Figure 2:19. Moving either side of an intersection

Examples:

MOVE N30W DIST 30TO(or FROM) /BOX

Move the Current Element N30W until its origin intersects aReference Plane 30 before (or beyond) the origin of /BOX(see Figure 2:19.: Moving either side of an intersection).

MOVE E DIST 1000 FROM /VESSEL5

Move the Current Element East until its origin intersects aReference Plane 1000 beyond the origin of /VESSEL5 (seeFigure 2:20.: Moving either side of a plane specified relativeto another element).

MOVE ALONG N45E DIST 20 TO /COL8

Move the Current Element along N45E until its originintersects a Reference Plane 20 before the origin of /COL8(see Figure 2:21.: Moving either side of a plane specifiedrelative to another element).

30

REFERENCEPLANES

... DISTANCE 30 FROM /BOX

... DISTANCE 30 TO /BOX

(START POSITION)CEMOVE N30W...

12.02 2:22


Figure 2:20. Moving either side of a plane specified relative to another element

Figure 2:21. 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 DISTANCE

Description:

This command differs from the basic options by allowing the movement direction andReference Plane to be specified independently. For example, by specifying PLANE NORTHan element may be moved towards a point until a particular Northing in the Site isintersected. In addition, any design point on the Current Element (not only the origin) can beused as the positioning datum; for instance, the p-point on the flanged face of a nozzle.

12.02 2:23

Administrator

Underline


Note: DISTANCE is measured in the direction of the Reference Plane and not themovement direction.

Command Syntax:>- MOVe -+- <marke> -.

| |‘-----------+- ALOng -.

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

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

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

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


| |‘------------+-- WRT --.

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

Examples:

MOVE IDP@ TOW /DATUM PLANE N THROUGH N1000

Move the picked p-point (or the Current Element) towards /DATUM until it intersects N1000 (see Figure 2:22.: Moving toan intersection by separately specifying direction and plane).

MOVE ALONG E PLANEN45W DIST 20 TO /

TANK5

Move the Current Element East until it intersects an obliqueReference Plane 20 before the origin of /TANK5 (see Figure2:23.: Moving to an intersection by separately specifyingdirection and plane).

12.02 2:24


Figure 2:22. Moving to an intersection by separately specifying direction and plane

Figure 2:23. Moving to an intersection by separately specifying direction and plane

2.6 Moving In Front of or Behind Items The commands described in this section move the Current Element to the intersection witha Reference Plane, a specified distance from the surface of a fixed geometric object.

Any p-point on the Current Element may be specified as the positioning datum, although thedefault is the origin. In no case is the geometry of the Current Element considered.However, the full geometry of the fixed element is taken into account. Although the designerdoes not need to know the actual distance moved, he must provide a ‘point-to-surface’dimension.

12.02 2:25

Administrator

Underline

Administrator

Underline


2.6.1 Moving Either Side of a Fixed Object

Keywords:

MOVE DISTANCE INFRONT BEHIND

Description:

This command moves the Current Element until its origin is a specified distance one side orthe other of a fixed geometric object. This takes into account the volume of the referencedelement but not of the Current Element. Therefore it is applicable to, say, spacing thecentreline of a vessel or column a certain distance from the surface of a wall.

Command Syntax:>- MOVe -+- ALOng -.

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

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

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

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


| |‘------------+-- WRT --.

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

Examples:

MOVE E DIST 1000 BEH /WALL10

The Current Element is moved East until its origin is 1000beyond the far side of /WALL10 (see Figure 2:24.: Movingeither side of a fixed object).

MOVE N45E DISTANCE20 INFRONT /EXCH5

The Current Element is moved until its origin is 20 to the nearside of /EXCH5 (see Figure 2:24.: Moving either side of afixed object and Figure 2:25.: Moving either side of a fixedobject in a specified direction).

12.02 2:26

Administrator

Underline

Administrator

Rectangle


Figure 2:24. Moving either side of a fixed object

12.02 2:27


Figure 2:25. Moving either side of a fixed object in a specified direction

2.6.2 Moving On Top of or Under a Fixed Object

Keywords:

MOVE DISTANCE ONTOP UNDER

Description:

This command moves the Current Element until its origin is a specified distance above orbelow a fixed geometric object. This takes into account the shape of the referenced objectbut not that of the Current Element. It is therefore applicable to, say, placing the centreline ofa vessel a certain distance above the top surface of a beam.

12.02 2:28

Administrator

Underline


Note: ONTOP means above in owner co-ordinates regardless of original Current Elementposition. The DISTANCE is always measured vertically in owner co-ordinates.


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

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

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

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


| |‘------------+-- WRT --.

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

Example:

MOVE D ONTO /BOX Moves the Current Element along a vertical line until itsorigin lies in the upper surface of /BOX (see Figure 2:27.:Moving above/below a fixed object).

MOVE ALONG E45D DISTANCE 3000 UNDER /BEAM

Moves the Current Element along E45D until its origin is3000 vertically below /BEAM (see Figure 2:26.: Movingabove/below a fixed object in a specified direction andFigure 2:27.: Moving above/below a fixed object).

12.02 2:29


Figure 2:26. Moving above/below a fixed object in a specified direction

12.02 2:30


Figure 2:27. Moving above/below a fixed object

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 on the Current Elementto be moved to a specified distance from the surface of a fixed design item. In addition thedistance may be specified in a direction independent of the movement direction.

12.02 2:31

Administrator

Underline


Command Syntax:>- MOVe <marke> -+- ALOng -.

| |‘---------+- <bdir> PLAne <bdir> DISTance <uval> <repla> ->

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

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


| |‘------------+-- WRT --.

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

Examples:

MOVE P1 E INFRONT /BOX The Current Element will be movedEast 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 bypositioning the Nozzle at the specifiedlocation.

12.02 2:32


Figure 2:28. Moving to a point at a specified distance from a surface

2.7 Moving to a Specified Clearance between ItemsThese commands allow the Current Element to be moved to a specified clearance from afixed object or position. Their separation takes into account both the Current Elementvolume and the referenced element volume. For the basic options, the clearance dimensionis always specified in the movement direction. It is therefore important to place the CurrentElement at an appropriate position from which to make the clearance move. A simpleralternative is available for placing the Current Element vertically above or below thereference element independently of movement direction. In these instances a verticalclearance can be specified directly using the ONTOP or UNDER options.

12.02 2:33


2.7.1 Moving to a Clearance Either Side

Keywords:

MOVE CLEARANCE INFRONT BEHIND

Description:

This command moves the Current Element until its geometric volume is a specifiedclearance from a fixed Design element, Point or position.

Command Syntax:>- MOVe <marke> -+- ALOng -.

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

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

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


| |‘------------+-- WRT --.

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

Examples:

MOVE ALONG E45N CLEAR BEHIND /BOX

Move the Current Element until its volume is zero clearancebehind BOX (see Figure 2:29.: Moving to a given clearance ina specified direction).

MOVE E CLEAR 1000INFRONT /DATUMBOX

Move the Current Element East until its volume is 1000 thisside of the given fixed item (see Figure 2:30.: Moving to agiven clearance).

MOVE E45N CLEAR 100 BEH IDP@

Move the Current Element along E45N until its volume is 100beyond the cursor hit p-point (see Figure 2:30.: Moving to agiven clearance).

12.02 2:34

Administrator

Underline


Figure 2:29. Moving to a given clearance in a specified direction

12.02 2:35


Figure 2:30. Moving to a given clearance

2.7.2 Moving an Object to Clear Another Object

Keywords:

MOVE CLEARANCE INFRONT BEHIND ONTOP UNDER

Description:

This command takes into account the geometry of both the Current and Referencedelements. In this way a minimum clearance can be specified between two Design items (forexample, to ensure that a walkway is a sufficient distance away from a heated autoclave).

12.02 2:36



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

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

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


| |‘------------+-- WRT --.

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

Example:

MOVE E CLEARANCE 1000 BEH /WALL10

The Current Element is moved East until its entire volume is1000 clear of the side of /WALL10 (see Figure 2:31.: Movingto clear another object).

MOVE D CLEARANCE ONTO /BEAM

The Current Element is moved down until it has a zeroclearance above the element /BEAM (see Figure 2:31.:Moving to clear another object).

12.02 2:37


Figure 2:31. Moving to clear another object

2.7.3 Moving to a Vertical Clearance

Keywords:

MOVE CLEARANCE ONTOP UNDER

Description:

This command moves the Current Element until its volume is a specified vertical clearanceabove or below a fixed element, Point or position.

12.02 2:38

Administrator

Underline



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

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

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


| |‘------------+-- WRT --.

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

Example:

MOVE ALONG U30W CLEAR ONTO /BEAM

The Current Element will be moved vertically until it is zeroclearance above /BEAM (see Figure 2:32.: Moving to a givenvertical clearance in a specified direction).

MOVE E60D CLEAR 1000 UNDER PIN6

The Current Element will be moved E60D until it is 1000below the specified Design point (see Figure 2:33.: Moving toa given vertical clearance).

12.02 2:39


Figure 2:32. Moving to a given vertical clearance in a specified direction

12

12.02 2:40


Figure 2:33. Moving to a given vertical clearance

2.7.4 General Moving to a Clearance

Keywords:

MOVE PLANE CLEARANCE INFRONT BEHIND

Description:

This command differs from the basic option by allowing the movement direction andclearance to be specified in different planes.

Example:

MOVE TOWARD /TANK5 PLANE E CLEARANCE 30 INF /TANK5

The Current Element will be moved towards /TANK5 until it has 30 clearance ‘this side’ in anEast/West direction (see Figure 2:34.: Moving toa given clearance relative to a specified plane).

12.02 2:41

Administrator

Underline

Administrator

Underline



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

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

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

| |‘- BEHind --|

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


| |‘------------+-- WRT --.

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

Figure 2:34. 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 or group byreflecting it in a specified plane. The current element and its hierarchy of members will berepositioned so as to achieve a mirror image of their initial relative positions. If the currentelement is a Group, all members of the group and their hierarchies of members will bereflected.

12.02 2:42

Administrator

Underline

Administrator

Underline

Administrator

Underline

Administrator

Underline


The values of positional attributes and directional attributes are derived by direct reflectionin the plane.

Orientations are processed such that they remain right-handed. For most elements this isachieved by reflecting the Y and Z axes directly, while reflecting and reversing the X axis.The exceptions to this rule are:

• Toruses (CTOR, RTOR, NCTO, NRTO), whose X and Y axes are reflected directlywhile 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 for the reversal. For example,an ELBO with p-point directions along X and Y will be reversed in the Z direction.

You will most likely use the mirror positioning options in conjunction with the COPYcommand (see Sections 2.1.5 and 2.1.6 of Database Management Reference Manual) tocreate a new part of the design model which is a mirror image of an existing part.

Note: Since mirror-image components will not always be available in the Catalogue, noattempt is made to reflect catalogue geometry or to reference alternative cataloguecomponents.

Keywords:

MIRROR

Description:

Moves the current element to a new position which is calculated by reflecting the initialposition in a specified plane.

Command Syntax:>-- MIRRor -- <plane> -->

where <plane> is any of the standard ways of specifying a plane through a given point in agiven direction:<plane> = >-+- PLAne <bdir> -+- DISTance <uval> -+- <repla> ------.

| | | || | ‘----------------|| | || |- <repla> --------------------------|| | || |- THRough <bpos> -------------------|| | || ‘- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -|| | || |- <planf> -|| | || ‘-----------||- DISTance - <uval> -+- <repla> -. || | | || |- <planf> -| |

Example:

MIRROR PLANE E45DTHRO /TANK5

Reflects position of current element in plane which has givendirection and which passes through /TANK5 (see Figure2:35.: Mirroring a position in a plane).

12.02 2:43

Administrator

Underline


| | | || ‘-----------+-------------------|| ||- CLEArance -+- <uval> -. || | | || ‘----------+- <repla> -. || | | || |- <planf> -| || | | || ‘-----------+----------------|| ||- <repla> -------------------------------------------|| ||- THRough <bpos> ------------------------------------|| |‘- <planf> -------------------------------------------+->

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

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

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

Figure 2:35. Mirroring a position in a plane

/TANK5

Current Element(owning threeprimitives)

E45DPlane direction

Plane through /TANK5

MIRROR PLANE E45D THRO /TANK5

12.02 2:44

DESIGN Reference ManualPiping, Ducting and Cable Trays

3 Piping, Ducting and Cable Trays

This chapter describes the commands to create Piping (including Hangers), Ducting andCable Trays. Then the commands to position, orientate and connect piping components aredescribed.

The key element in these disciplines is the Branch. This is a two-ended entity that can bejoined with other Branches to form a network. The network can finish where a Branch isconnected to an Equipment Nozzle, reaches the site limits, or stops at a vent or drain valve.The Branch element owns Component elements drawn from the PDMS Catalogue whosesequence and position define the centreline route. Straight variable lengths of Tube areautomatically routed between adjacent Components and are therefore not individualComponent elements themselves.

There are no special Design hierarchy elements for ducting and cable trays. They arerouted as Branches, but with Components drawn from parts of the Catalogue dedicated tothe relevant discipline. It is convenient, therefore, to refer to pipes, ducting and cable trayscollectively as ‘piping’, since PDMS treats them similarly. The principles applied to ‘routing’two-ended pipe Hangers are also identical to those used for Branches. Where no distinctionis made, the term ‘piping’ also applies to Hangers.

3.1 Defining a BranchBefore routing takes place, various preparatory steps are taken to define the Specificationand the start and end points of the Branch or Hanger. The Piping Specification andInsulation Specification are defined first, so that all Components created within the Branchcan be selected correctly.

The Head and Tail attributes can be set either by explicit positioning or by connection toanother item (e.g. a Nozzle). The Tail position may be in free space, when it is determinedby the Leave point of the final Component in the Branch. It is quite normal in suchcircumstances to route the pipe with only the HEAD attributes set up. (The reverse may alsoapply if routing backwards.)

When a Branch is connected to another item, the attributes of the element that it isconnected to are set to refer to the Branch. For example, if a Branch Head is connected to aNozzle, then the CREF (Connection Reference) attribute of the Nozzle is set to refer to theBranch.

Note that when a Branch is connected to a Nozzle, the Nozzle may be part of a database towhich the piping engineer does not have write-access. In this case, an Inter-DB ConnectionMacro is created, which can be run by the designer who does have write access to thesecond database. This macro is a sequence of commands that, for example, sets the CREFof a Nozzle that has been connected to by the piping designer. For more information, seeDatabase Management Reference Manual.

12.02 3:1

Administrator

Underline

Administrator

Underline


3.2 Branch and Hanger SpecificationsKeywords:

PSPE HSPE

Description:

On creation of a Branch (or Hanger) these are normally the first attributes to be set. If theSpecification of the Pipe has already been set, then this will automatically be cascadeddown to Branch level when it is created. The PSPE attribute of a Branch controls allsubsequent Component selection operations which choose a Component’s physical detailsfrom the stated Specification.

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

Command Syntax:>-- PSPEcification name -->

3.3 Connecting the Head or TailKeywords:

CONNECT

Description:

The CONNECT command, when applied to Branches (or Hangers), sets up the Head or Tailto match exactly the item to which it has been connected. For example, if the Head isconnected to a 3-inch flanged-faced nozzle at E3000 and pointing North, the CONNECTcommand will set all the Head attributes (HBOR, HCON, HPOS and HDIR) tocorresponding values. In addition, the Head and Nozzle are logically ‘tied together’ by twoattributes which ‘point’ to each other - the Nozzle CREF will point to the Branch, and theBranch HREF (Head Reference) will point to the Nozzle.

The final effect of CONNECT, which only applies to Heads, is that the Tube (or Rod) thatmay be required between the Head and the first Component 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:

PSPEC /A35B8(At Pipe level)

The PSPE attribute of the Pipe and all subsequently createdBranches will be set to /A35B8.

PSPEC /A15A2(At Branch level)

The PSPE attribute of the Branch will be set to /A15A2. Allsubsequent selection commands at that Branch or one of itsComponents will use that Specification by default.

12.02 3:2

Administrator

Underline

Administrator

Underline


Note: Before a CONNECT command is given, the Branch Specification attribute must beset. Connection to elements not within the designer’s jurisdiction (Read Only) willcause an inter-DB connection macro to be created automatically (see the DatabaseManagement Reference Manual).

Command Syntax:>-- CONnect <marke> TO --+-- <marke> --.

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

Querying:>-- Query --+-- PHead --.

| ||-- HHead --|| ||-- PTail --|| |‘-- HTail --+-->

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

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

Examples:

CONN PH TO /1205-N5(Where /1205-N5 is a Nozzle)

The Head attributes of the current element(Branch or Hanger) are set to match the position,orientation, bore and connection type of theNozzle (see Figure 3:1.: Connecting a BranchHead or Tail).

CONN PT TO LAST MEM The Tail attributes of the current element will beset to match the Leave Point of the lastComponent (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 beset to match the free p-point on the specified TEE(see Figure 3:1.: Connecting a Branch Head orTail).

CONN PT TO P4 OF /VF205(Where /VF205 is a VFWA.)

The Tail attributes of the current element will beset to match the specified p-point.

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

The Head attributes of the current element will beset to match the Tail of the specified Branch.

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

12.02 3:3

Administrator

Rectangle


Figure 3:1. Connecting a Branch Head or Tail

3.3.1 The Head or Tail Connection Reference Attribute

Keywords:

HREF TREF

Description:

These attributes hold the name of the element to which the Branch or Hanger is connected.They are usually set automatically as a result of a CONNECT PH (or PT) command, butthey may also be set explicitly. When they are set, the corresponding attribute (CREF, HREFor TREF) of the item connected to is reset so as to point back to the Branch or Hanger.

Command Syntax:>--+-- HRef --.

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

| | || |-- TAIL --|| | |

HEAD

TAIL

CONN PHTO /1205-N5/1205-N5

PH

BRANCH

CE

CONN PT TO/100-A8/T2

BRANCHCENTRELINE

PT

PLPA

/100-A8/T2

Examples:

TREF /PIPE2 HEAD Sets TREF of current element to point to Head of /PIPE2 andsetsHREF of /PIPE2 to point back to the current element.

HREF NULREF Unsets HREF; i.e. disconnects Head from any other element.

12.02 3:4

Administrator

Underline

Administrator

Underline


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

Querying:>-- Query --+-- CE ------.

| ||-- HEAd ----|| ||-- BRANch --|| |‘-- TAIl ----+-->

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

3.3.2 Positioning Head or Tail in Free Space

Keywords:

HPOS HBOR HDIR HCON TPOS TBOR TDIR TCON

Description:

It is sometimes necessary to terminate a Branch (or Hanger) in free space; for instance,where a Branch reaches the Battery Limits. Where this termination ends with a length ofTUBE (or ROD) and no Head or Tail connection can be made, it is necessary to set theHead/Tail attributes individually.

Note: If a data consistency error is to be avoided, the HCONN or TCONN of a free endmust 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> -->

Examples:

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

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

HBOR 80 The Head Bore is set as specified.

HCON OPEN The Head Connection Type is set as specified.

12.02 3:5

Administrator

Rectangle


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

Querying:>-- Query --+-- PHead --.

| ||-- HHead --|| ||-- PTail --|| |‘-- HTail --+-->

3.3.3 Head or Tail Positioning Using End Components

Keywords:

POSITION PH PT THROUGH DISTANCE

Description:

These commands allow the Head or Tail position to be set by using the end Component inthat Branch or Hanger. This will normally occur when the Tail is to finish with a piece ofvariable length Tube. This command treats the Tail position as a pseudo-Component andplaces it at the specified point along the previous Component’s Leave p-point direction. Ifthe Head is to be positioned in this way, Backwards Routing Mode must be in force.

Command Syntax:>-- POSition --+-- PHead --.

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

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

Querying:>-- Query --+-- PHead ------.

| ||-- PTail ------|| |

Example:

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

POS PH THROUGH E3000(In BACKWARDS mode)

The HPOS attribute will be set to the intersectionbetween the line from the Arrive p-point of thePrevious Component and the perpendicular planethrough E3000 N0 U0 in owner coordinates.

12.02 3:6

Administrator

Underline

Administrator

Underline


|-- HTail ------|| ||-- HHead ------|| ||-- HPosition --|| |‘-- TPosition --+-->

Figure 3:2. Head/Tail positioning using end components

3.3.4 Head and Tail Positioning by Bottom or Top of Pipe

Keywords:

BOP TOP INFRONT BEHIND ONTOP UNDER

Description:

This command allows the Head or Tail of a Branch to be moved vertically to a specifiedclearance above or below a Design element or Point. If the Head or Tail Tube has beenselected, then its cross-section will be taken into account. (Otherwise the HPOS or TPOSwill be moved to the specified clearance, as no Tube geometry is available.)

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

12.02 3:7

Administrator

Underline

Administrator

Underline


Note: If no Tube can be found emerging from the point specified, then only the point’sposition can be used.

Command Syntax:>--+-- BOP --.

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

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

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

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


| ||-- PTail ------|| ||-- HTail ------|| ||-- HHead ------|| ||-- HPosition --|| |‘-- TPosition --+-->

Example:

BOP ONTO /BEAM(At the Head)

This will position the Tube on top of /BEAM with a clearanceof 0.

TOP UNDER U3000(At the Tail)

This will position the Tail under the elevation U3000 with aclearance of 0.

12.02 3:8


Figure 3:3. Head/Tail positioning by Bottom/Top of pipe

3.3.5 Moving the Head or Tail

Keywords:

MOVE BY DISTANCE

Description:

This command allows the Head or Tail position to be moved by a specified distance, relativeto its current position, in the direction of PH or PT. Alternatively, it allows the Head or Tail tobe moved by an amount specified in any coordinates.

OWNERAXES

UP

HORIZONTAL

PH PT

BOPONTO/BEAM

PH

TOPUNDERU3000

PT

/BEAM

3000

Examples:

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

MOVE PT BY E2000 S500 Moves the Tail by 2000 East and 500 South from itscurrent position

12.02 3:9

Administrator

Underline


Command Syntax:>-- MOVe --+-- PHead --.

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

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


| ||-- PTail ------|| ||-- HTail ------|| ||-- HHead ------|| ||-- HPosition --|| |‘-- TPosition --+-->

Figure 3:4. Moving the Head or Tail

12.02 3:10


3.3.6 Reconnecting Pipes after an Equipment MoveNote: Applicable to Nozzles that have been moved since a Branch was connected to them.

Largely superseded by the DRAG command.

Keywords:

RECONNECT

Description:

If an Equipment item is moved using an ordinary positioning command, none of theBranches connected to it will move with it. RECONNECT will reconnect all the HEADS andTAILS of Branches connected to an Equipment, moving them to new positions if necessary.Other elements in the Branches are not affected and must be realigned using ordinaryrouting commands.

Command Syntax:>-- RECOnnect -->

3.4 Selecting Component and Tube Details from SpecificationsSelecting from Specifications in PDMS is fundamental to all Piping design work. When youcreated a Component element (say an ELBO), you must then give the CHOOSE (orSELECT) command to form a link from the Component to the Catalogue description of theitem, via the chosen Specification.

As the correct choice of Component can involve a large number of considerations, eachSelection would be very arduous if conducted manually. DESIGN assists you byautomatically examining the current element and its immediate neighbours for defaultparameters, then searching for an appropriate item in the Specification.

Of course, ultimate control rests with the designer, who can fully or partially override thischoice. However, in the majority of cases, the default Selection will be suitable. In a similarmanner, the straight TUBE between adjacent Components is Selected from a Specification.This is usually done automatically at the same time as Component Selection, so thedesigner only needs to be concerned with separate TUBE selection in certain specialcircumstances detailed in this section.

Most of the examples here assume that certain common PDMS conventions are followed,(e.g. P3 of a TEE is the off-line p-point). It is advisable to discuss the structure of your owncompany Catalogue and Specifications with your Catalogue Administrator before readingthis section. In order to make the correct Selections, you will also need a printed copy ofeach Specification that you wish to use.

Example:

RECON Finds all Nozzle elements which are Offspring of the currentelement. For each Nozzle, any Branch Head (or Tail) which isconnected to it is repositioned at the Nozzle.

12.02 3:11

Administrator

Underline

Administrator

Underline


3.4.1 Choosing Components from a Displayed List Keywords:

CHOOSE

Description:

This is only available in DEV GRAPHICS mode.• The CHOOSE command displays Selection options on screen forms which can be

picked using the cursor. Once an element has been created using the NEW command,CHOOSE may be used to list what is available in the Specification.

• The effect of choosing from the displayed list and applying the form setting via the OKbutton is to set the SPREF and LSTUBE attributes of the current Component, takinginto account the choice made and the current bore. Specification-dependent Designattributes (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 (orto the pipe head or tail). If the Cancel button is selected, the Component’s attributeswill remain unchanged.

• It may be that a newly selected Component is unsuitable for connection to the previous(or next) Component (or to the Pipe Head or Tail), for example due to incompatibleconnection types. In such a case, the new Component will be force-connected and awarning alert displayed. This action can be turned off by giving the command

CHOOSE FORCECONNECT OFF

• Connection attempt will still be made, but Component will be left at Site origin ifconnection types are incompatible.

• If the force-connect facility is OFF, a connection attempt will still be made followingcomponent selection. In this case however, the newly selected Component will be leftat the Site origin if connection types are incompatible. This action can be turned off bygiving the command

CHOOSE AUTOCONNECT OFF

• No connection attempt will be made; Component will be left at Site origin.• The default state is CHOOSE FORCECONNECT ON.• If only one choice of Component is available, for example flanges of only one type are

valid at a particular bore, DESIGN will set SPREF and LSTUBE automatically. If thereare no valid choices, for example there are no Components of a particular type for thespecified bore, an error alert is displayed.

12.02 3:12

Administrator

Underline

Administrator

Underline


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

Example:

CHOOSE Displays a general Selection form for the current element.Selection criteria displayed will depend on those available inthe specification.

Example form:

CHOOSE TEXT Displays a Selection form listing choices based on theSpecification Component’s (SPCOM’s) Detail DescriptionText (obtained from the RTEX attribute of the relevantDTEX element) and Material Description Text (obtainedfrom the XTEX attribute of the relevant MTEX element).

Example form:

12.02 3:13


CHOOSE RTEXCHOOSE STEXCHOOSE TTEX

Displays a Selection form listing choices based on theSPCOM’s Detail Description Text (obtained from theRTEX, STEX or TTEX attribute of the relevant DTEXelement).

Example form:

CHOOSE XTEXCHOOSE YTEXCHOOSE ZTEX

Displays a Selection form listing choices based on theSPCOM’s Material Description Text (obtained from theXTEX, YTEX, or ZTEX attribute of the relevant MTEXelement).

Example form:

CHOOSE ALL Combines the above CHOOSE and CHOOSE TEXToptions.

Example:

12.02 3:14


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

The CHOOSE function assumes that the Specification hierarchy is as follows, and use ofthe 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 -|| |

Example form:

CHOOSE SPEC /RF150 As CHOOSE, but selections are made from the namedspecification rather than from that of the owning Branch.

CHOOSE DEFAULT Default settings will be selected wherever they occur inthe Specification. For example, if the default STYP for aReducer is CONC, only Concentric Reducers will belisted in the selection form.

NEW REDUCHOOSE WITH ABOR 100 LBOR 80

Choose from Reducers with specified arrive and leavebores only

NEW ELBO CHOOSE WITH STYP LR

Choose from long-radius Elbows only.

Example:

12.02 3:15

Administrator

Underline


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

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

where:<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 SpecificationsAn alternative method of selecting items from a Specification is to create the pipingComponent, and then to ask the system to select a component of the correct type from thecurrent piping Specification. If there is a choice of component during selection, it issometimes necessary to specify answers to specification questions such as STYPE orBORE before the correct item is selected.

Typical commands could be as follows:

NEW ELBO SEL WITH STYP LRNEW TEE SEL WI PBOR 3 150NEW FLAN SEL WI STYP WNNEW REDU SEL WI STYP ECC LBOR 100

12.02 3:16

Administrator

Underline

Administrator

Rectangle


3.4.3 Selecting the Default Specification Component

Keywords:

SELECT

Description:

The SELECT command chooses a Component and its ‘Leave’ Tube from the BranchSpecification. Selecting the default Specification Component allows DESIGN to choose theappropriate item. This is based upon information DESIGN can obtain from the Design andfrom ‘default’ controls within the Specification. Default Selection is particularly applicable tocommon fittings such as FLANGEs, GASKETs, ELBOWs etc. The information automaticallydetermined from the current element and its surroundings is as follows:

3.4.4 Selecting from Several Alternatives

Keywords:

SELECT

Description:

The SELECT command chooses a Component and Leave Tube from the Specification andsets the appropriate current element attributes. In order to make a Selection from theSpecification, parameters for all the Specification Headings for that type of Component mustbe automatically obtained or provided by the designer. In many cases, the default choicemay not be suitable. This may be because:

• One or more of the Specification Headings has no default parameter for thatComponent (e.g. the Leave bore of a Reducer cannot be assumed)

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

In both instances, the designer must specify the relevant Headings with the required Entryas part of the SELECT command.

After a successful SELECT command, the design attributes will be updated with therelevant values from the Specification. The relevant attributes are ANGLE, RADIUS andSHOP, and HEIGHT if specified in the SELECT command.

SPECIFICATION Obtained from the PSPE attribute of the Branch.

(ARRIVE) BORE Obtained from the (Leave) bore of the Previous element(reverse in Backwards Mode).

ANGLE, HEIGHT, RADIUS

Obtained from the corresponding Current Element attributes.

SHOP Obtained from the corresponding Current Element attribute.

TEMPERATURE, PRESSURE

Obtained from the corresponding Branch attributes.

12.02 3:17

Administrator

Underline


Command Syntax:.------<-------.

/ |>-- SElect WIth --*-- SPec <gid> --|

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

For Selection criteria that are only in the Specification, the Specification itself may alsocontain information to assist default Selection. This information is in the Default Line of theSpecification.

Querying:>-- Query --+-- SPRef --.

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

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

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

Examples:

SELECT The default Component and Leave Tube willbe selected from the Branch Specification.The Current Element SPREF and LSTUattributes will be set to the chosenSpecification Component names.

SEL WI STYPE BALL The current element and Leave Tube will beselected using the default choices except forthe STYPE Heading which has beenspecified.

SEL WI STYPE ECC PBOR 2 50 The current element and Leave Tube will beselected using the default choice except forthe Headings specified. (If the ComponentLEAVE is 2, then the Leave Tube will alsobe 50 bore.

SEL WI ANGLE 45 The current element and Leave Tube will beselected using the default choice except forthe ANGLE heading. Also, the ANGLEattribute of the Current Component will be setto 45. (Similar behaviour occurs with HEIGHTand RADIUS.)

SEL WI LBOR 50 The current element will be selected usingthe default choice. However the Leave p-pointand Leave Tube will be selected with thespecified nominal bore.

12.02 3:18


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 SPEC

Description:

If an ‘out-of-specification’ Component is required, this can be Selected using the SELECTWITH SPEC command. This command uses the stated Specification rather than the defaultSpecification. Other Headings necessary to specify which ‘out-of-specification’ item isrequired can be given in the same command.

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

Examples:

SEL WI SPEC /A3AH The current element will be Selected from the givenSpecification using the default choice.

SEL WI SPEC /A3AH STYPE CTRL

The current element will be Selected from the givenSpecification using the default choice except for STYPE.

12.02 3:19

Administrator

Underline


Command Syntax:.-----<-----.

/ |>-- SElect WIth SPec <gid> --* |

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

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

Querying:.-----<-----.

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

<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGNReference Manual.>-- Query --+-- SPRef --.

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

3.4.6 Selecting Components and Tube Separately

Keywords:

SELECT SPREF TUBE ROD HSTUBE LSTUBE LSROD HSROD

Description:

In some instances it may be necessary to Select Tube (or Rod) separately from its owningComponent, or vice versa. This command enables separate Selection to occur. SELECTTUBE is most frequently used at the HEAD of a Branch where there is Tube between theHead and the First Component.

Command Syntax:>-- SElect --+-- SPref ---.

| ||-- LStube --|| ||-- HStube --|| |

Examples:

SEL TUBE(At Branch) The Branch HSTU attribute (Head Specification Tube)will be Selected according to the default choice ofTUBE.

SEL TUBE WI STYP GLAS(At Component)

The Component LSTU attribute (Leave SpecificationTube) will be Selected with the default choice ofTUBE except for STYPE.

12.02 3:20

Administrator

Underline


|-- LSrod ---|| ||-- HSrod ---|| ||-- TUbe ----| .-----<-----.| | / |‘-- ROD -----+-- WIth -- *-- <wivl> ---|

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

Querying:.-----<-----.

/ |>-- Query SPECification --*-- <qspci> --+-->>-- Query --+-- SPRef ---.

| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| |‘-- HSrod ---+-->

3.4.7 Direct Selection by Shortcode

Keywords:

SHORTCODE

Description:

The actual Specification Component name (SPREF for Components, LSTU or HSTU forTube) can be specified in order to Select a Component. This overrides the ordinarySelection process by directly choosing the required item. The shortcode option assumesSelection from the Current Branch Specification by automatically providing the specnamepart. Thus it is assumed that the Specification Component name is of the form /specname/shortcode.

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

Examples:

SHOR /EL50 The current element SPRE attribute will be set to /specname/EL50 where /specname is obtained from theBranch.

SHOR TUB /TU50 The current element LSTU (or HSTU) attribute will beset to /specname/TU50 where /specname is obtainedfrom the Branch.

12.02 3:21

Administrator

Underline

Administrator

Underline


Command Syntax:>-- SHORtcode --+-- SPRef ---.

| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| ||-- HSrod ---|| |‘------------+-- name -->

Querying:>-- Query --+-- SPRef ---.

| ||-- TUbe ----|| ||-- LStube --|| ||-- HStube --|| ||-- LSrod ---|| |‘-- HSrod ---+-->

3.5 Re-selection of Existing Components and TubeIf a Component or Tube is required to be respecified, you may restate any of the Selectioncommands described elsewhere in this manual. However, each time this is done all thenon-default Specification entries must be restated, even if most or all of these are identicalto the old Specification Component.

The RESELECT command allows the designer to make use of the original Selectionparameters for a Component to simplify the Selection of a new Component. This is usefulfor situations where only a single change has taken place since the original Selection; forexample, if the Branch Specification (PSPE attribute) was changed or the nominal bore of agroup of Components had to be increased.

The RESELECT command operates as follows:

1. Any new Selection parameters are considered (either changed defaults or specified bythe user).

2. If any more parameters are required, they are obtained from the old SpecificationComponent.

3.5.1 Re-selecting the New Default Component

Keywords:

RESELECT

Description:

The RESELECT command chooses a new Component and its Leave Tube from the BranchSpecification. The default Selection parameters are obtained from the current element’s

12.02 3:22


surroundings (in the same way as for SELECT). If any further Selection parameters areneeded, they are obtained from the old Component Specification entries. The need torespecify is therefore reduced.

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

Command Syntax:>-- RESElect -->

Querying:.-----<-----.

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

<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGNReference Manual..>-- Query --+-- SPRef ---.

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

3.5.2 General Reselection of Components and Tube

Keywords:

RESELECT

Description:

This command allows existing Components and Tube to be Reselected according to newparameters. Where new parameters are not stated or available through defaults, they areobtained from the old Component Specification entries.

Examples:

RESEL The current element and Leave Tube will be Selectedfrom the new default choice(s). Any parameters requiredthat are not obtainable from defaults will be derived fromthe old Specification Component.

Examples:

RESEL WITH STYPE BALL The current element and Leave Tube will beSelected using any default parameters and theSTYPE specified. Any further parametersrequired will be obtained from the oldSpecification Component.

12.02 3:23


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 the DESIGNReference Manual.>-- Query --+-- SPRef ---.

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

3.6 Standard Component AttributesThis section describes the standard Component element attributes that provide theircomplete logical and physical descriptions. Although you may set them directly, many ofthese attributes are automatically determined when using the Specification selection andpipe routing commands described elsewhere.

Two classes of standard attribute exist for Components:• Those which ‘point’ to a Specification item that provides a fixed Catalogue description

of the Component

RESEL WI SPEC /NEWSPEC The current element and Leave Tube will beSelected using the new Specification and anydefault parameters. The remaining necessaryparameters will be obtained from the oldSpecification Component.

RESEL TUBE WI STYPE GLAS(At Branch)

The current element HSTU attribute will beSelected using default parameters and thespecified STYPE. If any further parameters arenecessary they will be obtained from the oldSpecification Component.

Examples:

12.02 3:24

Administrator

Underline


• Those which cannot be part of the Catalogue description, as they are unique to eachoccurrence in the Design

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 Tube emergingfrom the current element Leave Point.

ISPEC This points to an Insulation Specification. The Branch‘TEMPERATURE’ attribute is automatically used to determinean 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 (neither Branchnor Pipe have a POSITION, though Branch has head and tailpositions (HPOS and TPOS).

ORIENTATION The Component’s orientation in Zone coordinates (neitherBranch nor Pipe have an ORIENTATION, though Branch hashead 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 by PDMSto determine if the Component has been oriented.

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

The following attributes do not occur in all Components, but are sufficiently common to beconsidered 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, whetherthe Component breaks the Tube either side of it.

12.02 3:25


3.6.1 Position and Orientation Attributes

Keywords:

POSITION ORIENTATION

Description:

The Component position and orientation attributes describe their location with respect toZone co-ordinates. This is because neither Branch nor Pipe have position or orientationattributes and therefore do not have a co-ordinate system.

Command Syntax:

Component position and orientation are established using the pipe routing or ordinarypositioning 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.6.2 Component Arrive and Leave Attributes

Keywords:

ARRIVE LEAVE

Description:

This command sets the attributes that control which p-points are the Arrive and Leave for aComponent. It is usual to set those attributes before Selection and Positioning as they candefine:

• The automatic Selection Parameters for that item (particularly REDUCERS)• The centreline Logical Route that will affect positioning and orientation of the

Component.

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

CRFA (Multi-way Component Connection Reference.) Indicates theelements that are connected to the free (neither Arrive norLeave) p-points of the Current Element.

12.02 3:26

Administrator

Underline

Administrator

Underline


However, as the p-point details for Arrive (PA) and Leave (PL) are obtained from theCatalogue, these may only be used or interrogated after Selection.

Note: Default is Arrive 1, Leave 2.

Command Syntax:>--+-- ARRive --.

| |‘-- LEAve ---+-- P --------.

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

3.6.3 Swapping the Arrive and Leave P-points

Keywords:

FLIP

Description:

This command swaps the Arrive and Leave p-point numbers of a Component so that it canbe ‘Flipped’. It does not actually rotate the Component until the next orientation command isgiven. The FLIP command can be given before Selection, as the Arrive and Leave p-pointnumbers are Design attributes independent of the Catalogue.

As most Specifications are organised with Reducers having PBOR1 larger than PBOR2, theSelect mechanism needs to be told that the Arrive is at P2 by FLIP Selection. ThereforeNEW REDU FLIP SELECT WITH LBORE 100 would be a typical command for a boreincrease.

When working in BACKWARDS mode, this situation reverses - the REDU need only beFlipped if a bore reduction is required.

Command Syntax:>-- FLIP -->

Querying:>-- Query --+-- ARRive --.

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

Example:

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

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

Example:

FLIP Reverses the current Arrive and Leave p-point numbers forthat Component.

12.02 3:27

Administrator

Rectangle

Administrator

Underline

Administrator

Pencil


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

3.6.4 The Component Specification Reference Attribute

Keywords:

SPREF

Description:

All Piping Components (including ducting, cable trays and pipe hangers) obtain theirgeometries from the PDMS Catalogue through a Specification. The SPREF (SpecificationReference) attribute of these items refers to a Specification Component in a chosen ProjectSpecification that obtains its physical dimensions from the Catalogue. If the SPREF is notset, a Valve, for example, is merely a hierarchical element and has no geometry.

Note: This attribute is usually inserted automatically as a direct result of the CHOOSE (orSELECT) command. It can, however, be set directly to the name of the requiredSpecification Component.

PH

PT

P2

P1

LEAVE

ARRIVE

CE

FLIP(ARRIVE 2 LEAVE 1)

Example:

SPREF /SPEC208/EL50BW The current element is specified by the chosenSpecification Component.

12.02 3:28


Command Syntax:>-- SPRef name -->

3.6.5 Variable Length Tube (and Rod) Attributes

Keywords:

LSTUBE LSROD HSTUBE HSROD

Description:

Straight lengths of Tube (ducting, trays and rod) between Components are not defined asPDMS elements in the hierarchy. Instead, they are extruded from the Leave p-point of aComponent to the Arrive p-point of the next. Their geometric cross-section details are storedin the Catalogue and are pointed at from the Upstream Component via its LSTU attribute. Atthe Head of a Branch, there is no Upstream Component; therefore a special Branchattribute exists to allow Tube from the Head to the first Component to be specified (HSTU).

Generally, you need not be concerned about specifying Tube between Components, as it isautomatically determined during the Component Selection process described elsewhere. Ifshort fixed-length stubs of Tube are required, it is usually appropriate to create aComponent FTUB element to ensure that this minimum length is adhered to. Similarly,where Tube changes direction, a Component must be inserted (usually a BEND), asvariable length Tube is always straight.

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

Command Syntax:>--+-- LSTube --.

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

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

Examples:

LSTU /SPEC502/100L(At Branch Component)

The Tube between the Leave p-point of thisComponent and the Arrive of the Next (or Tail)is specified by the named SpecificationComponent.

HST /SPEC502/100L(At Branch)

As above, but between the Head and Arriveof First Component (or Tail).

LSR /HS20/2.5(At Hanger Component)

As first example.

HSR /HS20/2.5(At Hanger Component)

As second example.

12.02 3:29


3.6.6 Insulation Specification Attribute

Keywords:

ISPEC

Description:

This attribute points to an insulation Specification. It is automatically cascaded down fromthe Branch ISPE setting, but can also be set on an individual basis. In conjunction with theBranch TEMPERATURE attribute, the ISPE insulates the Component and the Tube from itsLeave point.

Note: If a whole Branch is to be insulated, the Branch ISPE should be set beforeComponents are created. This setting will then cascade down to all newComponents.

Command Syntax:>-- ISPec --+-- name ---.

| |‘-- NULREF -+-->

Querying:>-- Query INSUlation -->

Gives the insulation thickness.

Figure 3:6. Variable length Tube between Components

Examples:

ISPE /I500-HAV The Current Component and Tube from its Leave p-point willbe insulated according to the named Specification. (Thetemperature parameters required to determine insulationthickness will be obtained from the Branch element.)

ISP NULREF The Component and Tube from its Leave p-point will beuninsulated.

Figure Missing!!

12.02 3:30


3.6.7 Trace Heating Specification Attribute

Keywords:

TSPE

Description:

This attribute provides ISODRAFT with trace heating information. The trace heatingSpecification pointed to is a dummy Specification defined in SPECON, having nosignificance other than its name.

Note: If the same trace heating is required for an entire Branch, TSPE should be set atBranch level, from where it will cascade down to all new Components.

Command Syntax:>-- TSPec --+-- name ---.

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

3.6.8 The Fabrication Flags

Keywords:

SHOP BUILT

Description:

These attributes indicate the location and status of construction of each Component. TheSHOP flag is used by ISODRAFT to determine in which material list the item will appear.The BUILT flag can indicate whether or not the Component has been fabricated/built duringconstruction.

Command Syntax:>--+-- SHOP ---.

| |‘-- BUIlt --+-- TRue ---.

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

Example:

TSPE /TR50A The Current Component will be noted by ISODRAFT with thegiven trace heating requirements.

TSPE NULREF Trace heating is removed.

Examples:

SHOP TRUE The current element will be itemised as ‘SHOPFABRICATED’ in ISODRAFT.

BUILT FALSE Information attribute indicating that current element has notbeen built.

12.02 3:31


3.6.9 Position and Orientation Status Flags

Keywords:

ORIFLAG POSFLAG

Description:

These attributes are automatically set to TRUE when the Component is positioned andorientated. They are used by DESIGN in several situations where it requires to know if aComponent has been properly positioned.

Note: If either POSFLAG or ORIFLAG remains FALSE, the next Component cannot bepositioned using ordinary routing commands.

Command Syntax:

These attributes are set automatically by DESIGN when positioning and orientation takesplace. However, they can be set explicitly as follows:>--+-- ORIFlag --.

| |‘-- POSFlag --+-- TRue ---.

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

Querying:>-- Query --+-- POSFlag --.

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

3.6.10 Variable Component Attributes

Keywords:

ANGLE HEIGHT RADIUS DESPARAMETERS

Description

Some Components have variable dimensions that must be specified in situ by the designer.Once a Component has been selected from the Specification, altering, say, the ANGLE maychange its physical appearance.

Examples:

POSF FALSE This setting will occur if the Components have beentransferred from a P&ID and not positioned. TheComponent will not be drawn in the views.

ORIF FALSE POSF TRUE This setting will occur if the item has been Selected inDESIGN but not oriented.

ORIF TRUE POSF TRUE After the Component is oriented it will be shown in normalline type.

12.02 3:32


Although many Component elements possess the ANGLE, HEIGHT or RADIUS attributesor use Design Parameters, it is the Catalogue that determines whether the value of theseattributes will affect the physical Component. For example, changing the ANGLE attribute ofa 90-degree fixed-angle elbow to 45 degrees will have no effect. In some cases, thevariable value may be difficult to determine. For instance, a BEND in a pipe may possess anangle resulting from an oblique change in direction. In such instances, the DIRECTIONcommand (described elsewhere) can be used to determine the ANGLE settingautomatically.

The ANGLE, HEIGHT and RADIUS attributes can also be set before selection as a meansof choosing between, say, 90-degree or 45-degree fixed-angle elbows.

Command Syntax:>-- ANGle --+-- <uval> -----------------.

| |‘-- <bdir> TOwards <bdir> --+-->

>-- HEIght <uval> -->

>-- RADius <uval> -->

>-- DESParameters <uval> -->

3.6.11 Offline/Straight-Through Component Attribute

Keywords:

LOFF

Description:

This attribute controls whether a Component is considered to be ‘in-line’ or ‘off-line’. If it isoff-line, the reporting utility will treat it as a continuous part of the Tube either side of theComponent and will only report one pipe length. This is useful for BENDS (bends incontinuous Tube) and OLETS (which tap off the side of a piece of Tube). If the Componentis left as in-line, the Tube will be split into two sections with no account being taken of theArrive-to-Leave length of the Component.

Examples:

ANGL 45(Before Selection)

When the CHOOSE (or SELECT) command is given, it willchoose the ‘ANGLE45’ option if available in the Specification.

HEIG 300(After Selection)

If a variable height component, this dimension will alter asspecified.

12.02 3:33


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

Command Syntax:>--+-- LOFFline --.

| |‘-- OFFLine ---+-- TRue ---.

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

3.6.12 Multi-Way Component Attributes

Keywords:

CREF CRFA

Description:

In addition to Arrive and Leave p-points, some Components have further p-points which canbecome the ends of other Branches. For three-way Components (e.g. TEE), the attributeCREF (Connection Reference) is used to show which Branch is connected to the free p-point. This is usually set automatically as a result of a CONNECT command, but it may alsobe set explicitly. For Components with more than three p-points (e.g. CROSS), the attributeCRFA stores the names of up to 10 Branches which connect to this item. Although a DesignComponent element can possess a CREF or CRFA attribute, it is the Catalogue whichcontrols whether the item can actually be connected to by other Branches.

Command Syntax:>-- CREF --+-- <gid> --+-- HEAD --.

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

Examples:

LOFF FALSE In the reporting utility, the current element will be treated as afull Component which breaks the Tube lengths either side.

OFFL TRUE In the reporting utility, the current element will be included aspart of a single Tube length running through its Arrive-to-Leave centreline.

Examples:

CREF /PIPE1 TAIL Sets CREF of current element to point to Tail of /PIPE1 andsets TREF of /PIPE1 to point back to the current element.

CREF NULREF Unsets CREF; i.e. disconnects this point from any otherelement.

12.02 3:34


Querying:>-- Query --+-- CREf --.

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

3.7 Orientation and Connection of ComponentsOrientation and Connection commands make use of the constrained centreline of a Piperoute. When a Component is Selected, it is automatically positioned next to the adjacentComponent so that it can be seen. However, it is essential in DESIGN that the item is eitheroriented or Connected. DESIGN insists on this minimum to ensure that each Component isdeliberately manipulated by the user.

All the examples in this section assume Forwards routing mode is in operation. Generally, ifBackwards is being used, then the effect of these commands will logically reverse.

3.7.1 Component Orientation

Keywords:

ORIENTATE

Description:

This command rotates the Component about its origin so that (in forwards mode) the Arrivep-point is in the opposite direction to the previous 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 of an off-line p-point. If it is not possible toachieve an orientation because of the direction of the constrained centreline, DESIGN willleave this off-line direction in the closest orientation to that requested.

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

Command Syntax:>- ORIentate -+- <bdir> IS <bdir> -.

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

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

Examples:

ORI Rotate the current element about its origin so that (inforwards mode) its Arrive Point is in the opposite direction tothe previous Component’s Leave Point (see Figure 3:7.:Orienting a Concentric Component).

ORI AND P3 IS U As above, and orient the off-line p-point (P3) in the specifieddirection (see Figure 3:8.: Orienting a non-concentricComponent by means of an off-line p-point).

12.02 3:35


Querying:.-------------------<----------------.

/ |>-- Query <marke> --*-- DIRection --. |

| | |‘---------------+-- WRT --. |

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

Figure 3:7. Orienting a Concentric Component

12.02 3:36


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

3.7.2 Direction-Changing Components

Keywords:

DIRECTION

Description:

The DIRECTION command orients the Component along the constrained centreline andpoints the specified p-point in a new direction. Unlike the ORI command, if that newdirection requires a change in the ANGLE of a variable-angle Component (e.g. a BEND),this will automatically be adjusted. The ability of a Component to adjust in this way iscontrolled by the Catalogue.

12.02 3:37


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

Command Syntax:>-- DIRection --+-- AND <marke> IS --.

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

Querying:.-------------------<----------------.

/ |>-- Query <marke> --*-- DIRection --. |

| | |‘---------------+-- WRT --. |

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

Examples:

DIR E Rotate the Component about its origin such that (in forwardsmode) its Arrive point is in the opposite direction to theprevious Component’s leave point, and its leave point is East.If this requires a change of angle and the Component has avariable ANGLE attribute, then this will be altered to suit (seeFigure 3:9.: Changing the direction of variable-angleComponents).

DIR AND P3 IS U45E As above, but P3 (rather than PL) is pointed to the newdirection (see Figure 3:9.: Changing the direction of variable-angle Components).

12.02 3:38


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

3.7.3 Component Connection

Keywords:

CONNECT

Description:

This command places a p-point on the current Component face-to-face with the p-point ofan adjacent Component. If the Connection Types or nominal bores of the Connected facesare not compatible, DESIGN automatically Flips (reverses Arrive and Leave) theComponent and tries again. If the adjacent element is an Attachment Point (ATTA) then thisis ignored and Connection is attempted on the Next Component.

12.02 3:39


Note: Only adjacent Components (not Attachment Points) may be connected to; ifConnection Types or bores are incompatible, then an automatic FLIP takes placeand CONNECT is attempted again.

Command Syntax:>- CONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> ->

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

Querying:.------------------<----------------.

/ |>-- Query <marke> --*-- POSition --. |

| | |‘--------------+-- WRT --. |

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

Examples:

CONNECT The arrive p-point of the Component is connected to theleave p-point of the Previous Component (see Figure 3:10.:Component connection).

CONNECT TO NEXT The leave p-point of the Component is connected to thearrive p-point of the next Component (see Figure 3:10.:Component connection).

CONNECT AND P3 ISU

As first example and the off-line p-point is oriented upwards(see Figure 3:10.: Component connection).

12.02 3:40


Figure 3:10. Component connection

3.7.4 Forced Component Connection

Keywords:

CONNECT

Description:

This operates exactly as the CONNECT command, but ignores Connection and Borecompatibility. The Component will be shown fully positioned, but data consistency checkingwill still report incompatible connections unless the items are moved apart later.

12.02 3:41


Note: Only adjacent Components (not Attachment Points) may be force-connected. Nocheck on compatibility of bore or Connection Type occurs.

Command Syntax:>- FCONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> -->

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

3.8 Moving by a Known DistanceThese commands move the Component a specified distance along the constrainedcentreline. All the commands move the Component from its current position. The distancemoved may either be measured along the constrained centreline or some other planardirection. All the examples in this section assume Forwards routing mode is in operation.Generally, if Backwards is being used, then the effect of each command will be logicallyreversed.

3.8.1 Moving Components

Keywords:

MOVE DISTANCE

Description:

This command moves the Component along the constrained centreline by a specifieddistance.

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

Examples:

FCONN The Arrive p-point of the Component is force-connected tothe Leave p-point of the previous Component.

FCONN TO TAIL The Leave p-point of the Component is force-connected tothe Tail.

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

Example:

MOVE DISTANCE 1000 The Current Component is moved from its present position1000 along the constrained centreline (see Figure 3:11.:Moving a Component by a given distance).

12.02 3:42


Command Syntax:>-- MOVe DISTance <uval> -->

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 DISTANCE

Description:

This command moves the Component along the constrained centreline. The distancemoved may be specified either in the direction moved or another planar direction.

Command Syntax:>-- MOVe PLAne <bdir> DISTance <uval> -->

Querying:>-- Query POSition <bpos> --+-- WRT --.

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

Example:

MOVE PLANE N45E DIST 1000

The current Component is moved from its present positionalong the constrained centreline by 1000 along the N45Edirection (see Figure 3:12.: Moving a Component by adistance specified in another plane).

12.02 3:43


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 the constrainedcentreline 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 ispositioned along the constrained centreline through the reference plane which is defined bythe 3D position through which it passes. The orientation of the reference plane defaults toperpendicular to the constrained centreline, although a different planar direction can bespecified.

In no case is the volumetric geometry of the 3D model considered. These commands aretherefore not suitable for ‘clearance’ positioning.

All the examples in this section assume Forwards routing mode. Generally, if Backwards isbeing used, then the effect of each command will be logically reversed.

3.9.1 Positioning with respect to the Previous Component

Keywords:

DISTANCE POSITION

Description:

This command positions the Component on the constrained centreline at a specifieddistance from the origin of previous Component. Any p-point on the current element may beused, the default being the origin.

12.02 3:44



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

Querying:>-- Query --+-- POSition --.

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

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

Figure 3:13. Positioning with respect to Previous Component

Examples:

DIST 1000 The Component will be positioned on the constrainedcentreline 1000 from the origin of the previous Component(see Figure 3:13.: Positioning with respect to PreviousComponent).

POS PA DIST 1000 As above, but the Arrive point of the Component is used (seeFigure 3:14.: Positioning with respect to PreviousComponent).

12.02 3:45


Figure 3:14. Positioning with respect to Previous Component

3.9.2 Positioning the Component through an Intersection

Keywords:

THROUGH POSITION

Description:

This command allows the designer to position the Component through the intersection witha fixed design element or position (say a Nozzle) or a cursor position. The Component ispositioned along the constrained centreline where the reference plane intersecting, say, thespecified Nozzle, cuts at right angles. For cursor positioning it is therefore advisable to useorthogonal views for orthogonal piping.

Examples:

POS THR /TANK5 The origin of the current Component will be positioned on theconstrained centreline where this intersects the perpendicularreference plane through the named element (see Figure3:15.: Positioning through an intersection).

POS PA THR E3000 The Arrive point of the current Component will be positionedon the constrained centreline where the perpendicularreference plane through E3000 N0 U0 intersects (see Figure3:16.: Positioning through an intersection.

THR @ The Component will be placed on the constrained centrelinewhere the perpendicular reference plane indicated by thecursor intersects (see Figure 3:17.: Positioning through anintersection).

12.02 3:46


Note: The reference plane is perpendicular to the constrained centreline. If the cursor isused, the position will be located on the working grid nearest to the cursor.


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

Querying:>-- Query --+-- POSition --.

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

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

Figure 3:15. Positioning through an intersection

12.02 3:47




3.9.3 Positioning with respect to an Intersection

Keywords:

POSITION DISTANCE FROM TO

Description:

This command positions the current Component so that its origin (or specified p-point)intersects the reference plane either side of the specified fixed position.

12.02 3:48


Note: The reference plane is perpendicular to the constrained centreline. TO means closerto the Previous Component than the reference plane. FROM means further from theprevious Component than the reference plane.


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

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

Querying:>-- Query <marke> --+-- POSition --.

| |‘--------------+-- WRT --.

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

Examples:

DIST 50 FROM /TANK5 The Component will be moved along the constrainedcentreline until its origin is 50 beyond theperpendicular plane through the named element (seeFigure 3:18.: Positioning with respect to anintersection).

DIST 1000 TO NEXT The Component will be placed on the constrainedcentreline so that its origin is 1000 before of the NextComponent’s origin (see Figure 3:19.: Positioning withrespect to an intersection).

POS PA DIST 20 FROM PL OF PREV

The Component will be placed on the constrainedcentreline so that its Arrive point is 20 from theprevious Component’s Leave point (see Figure 3:20.:Positioning with respect to an intersection).

12.02 3:49


Figure 3:18. Positioning with respect to an intersection


12.02 3:50



3.9.4 General Positioning through an Intersection

Keywords:

POSITION PLANE DISTANCE THROUGH FROM TO

Description:

This command differs from the basic options by allowing the reference plane to be specifiedindependently of the constrained centreline. This is particularly relevant for routing slopinglines where a specific Easting or Northing is to be intersected.


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

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

‘- THrough <bpos> ->


| |‘--------------+-- WRT --.

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

Example:

PLANE E DIST 1000 The Component will be placed on the constrained centrelineso that its origin is 1000 from the previous Component’sorigin in an East/West direction (see Figure 3:21.: Positioningthrough an intersection defined in an independent plane).

12.02 3:51


Figure 3:21. Positioning through an intersection defined in an independent plane

3.10 Positioning Components ‘Point-to-Surface’This section describes commands which position a Component on the constrainedcentreline at a specified distance from the surface of a fixed design item.

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

• If the item is a Design element, then its complete geometry will be considered.• If the item is a Piping p-point at the Arrive or Leave of another Component, 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, if Backwards mode isbeing used, the effect of each command is logically reversed.

3.10.1 Positioning Components Either Side of an Object

Keywords:

POSITION DISTANCE INFRONT BEHIND

Description:

This command positions the Component on the constrained centreline at a specifieddistance from a geometric object, point or position.

12.02 3:52



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

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

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


| |‘--------------+-- WRT --.

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

Examples:

DISTANCE 30 INFRONT/WALL

The Component will be placed on the ConstrainedCentreline so that its origin is 30 ‘this side’ of the specifiedobject (see Figure 3:22.: Positioning Components eitherside of an object and Figure 3:23.: PositioningComponents relative to a specified object).

DISTANCE 125 BEHINDIDP @

The Component will be placed such that its origin is 125the ‘other side’ of the picked p-point. If this point is anArrive or Leave, then the Tube cross-section will be takeninto account (see Figure 3:23.: Positioning Componentsrelative to a specified object).

POS PL INF /ACCESS The Component will be placed such that its Leave Point iszero distance ‘this side’ of the specified object (see Figure3:23.: Positioning Components relative to a specifiedobject).

12.02 3:53


Figure 3:22. Positioning Components either side of an object

12.02 3:54


Figure 3:23. Positioning Components relative to a specified object

3.10.2 Positioning Components On Top of or Under an Object

Keywords:

POSITION DISTANCE ONTOP UNDER

Description:

This command positions the Component on the constrained centreline at a vertical distanceabove or below a fixed geometric object. This takes into account the shape of thereferenced object, but not of the current element.

12.02 3:55



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

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

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


| |‘--------------+-- WRT --.

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

Examples:

DISTANCE 35 ONTO /BEAM The Component will be placed on the ConstrainedCentreline so that its origin is 35 above the specifiedobject (see Figure 3:24.: Positioning above/below anobject).

DISTANCE 125 UNDER IDP @ The Component will be placed on the ConstrainedCentreline so that its origin is 125 below the pickedpoint. If this point is an Arrive or Leave, then theTube cross-section will be taken into account (seeFigure 3:24.: Positioning above/below an object).

12.02 3:56


Figure 3:24. Positioning above/below an object

3.10.3 General Component Positioning Using Planes

Keywords:

POSITION PLANE DISTANCE INFRONT BEHIND ONTOP UNDER

Description:

This command differs from the basic options by allowing the reference plane to be specifiedin a different direction from that of the constrained centreline.

12.02 3:57



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

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

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

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


| |‘------------+-- WRT --.

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

Figure 3:25. Positioning relative to an object specified in a different plane

Example:

PLANE E DIST 1000INFRONT /WALL

The Component will be placed on the constrained centrelinesuch that its origin is 1000 ‘this side’ of /WALL, measuredEast-West (see Figure 3:25.: Positioning relative to an objectspecified in a different plane).

12.02 3:58


3.11 Component Clearance PositioningThe commands in this section position the Component on the constrained centreline to givea specified clearance distance from a fixed design item.

The clearance specified usually takes into account both the current element and referencedelement geometric shapes. However, the following rules also apply:

• If the current element or referenced element is used and has a geometric shape, thenthis is considered.

• If an Arrive or Leave p-point on the current element or referenced element is used, thenthe Tube cross-sectional geometry at that point is considered (not the Componentgeometry).

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

A selection of Bottom of Pipe (BOP) commands are also available that provide clearance forthe Tube cross-section at a Component Leave Point. All the examples in this sectionassume Forwards routing mode. If Backwards is in use, then the effect of each command islogically reversed.

3.11.1 Clearance from the Previous Component

Keywords:

CLEARANCE

Description:

This command places the Component at a specified clearance from the previousComponent on the constrained centreline. The whole geometry of both Components isconsidered.

Command Syntax:>-- CLEArance <uval> -->


| ||-- BOP -------|| |‘-- TOP -------+-- WRT --.

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

Example:

CLEA 500 The Component will be placed on the constrained centreline500 clear of the Previous Component (see Figure 3:26.:Clearance from a Previous Component).

12.02 3:59


Figure 3:26. Clearance from a Previous Component

3.11.2 Component Clearance Either Side

Keywords:

CLEARANCE INFRONT BEHIND

Description:

This command places the current Component on the constrained centreline at a specifiedclearance in front of or behind a fixed design object. If the Arrive or Leave point of thereferenced object is used, then the Tube cross-section at this point is considered rather thanthe full item geometry.

Command Syntax:>-- CLEArance --+-- <uval> --.

| |‘------------+-- INFront --.

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

| |

Examples:

CLEAR BEHIND /WALL The Component will be placed on the constrainedcentreline with zero clearance on the ‘far side’ ofthe specified element (see Figure 3:27.:Component clearance either side of a fixedobject).

CLEAR 1200 INF PL OF NEXT The Component will be placed on the constrainedcentreline with 1200 clearance ‘this side’ of theTube emerging from the Component’s Leavepoint (see Figure 3:27.: Component clearanceeither side of a fixed object).

12.02 3:60


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


| ||-- BOP -------|| |‘-- TOP -------+-- WRT --.

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

Figure 3:27. Component clearance either side of a fixed object

12.02 3:61


3.11.3 Component Clearance Vertically

Keywords:

CLEARANCE ONTOPUNDER

Description:

This command places the current Component on the constrained centreline at a specifiedvertical clearance above or below a fixed object. If the Arrive or Leave point of thereferenced object is used, then the Tube cross-section emerging at this point is consideredrather than the full item geometry.

Command Syntax:>-- CLEArance --+-- <uval> --.

| |‘------------+-- ONTop --.

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

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


| ||-- BOP -------|| |‘-- TOP -------+-- WRT --.

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

Examples:

CLEARANCE ONTO /BEAM

The current Component will be placed on the constrainedcentreline at zero clearance above the specified object(see Figure 3:28.: Component clearance above/below afixed object).

CLEARANCE 50 UNDER/BEAM

The current Component will be placed on the constrainedcentreline at 50 vertical clearance below the specifiedobject (see Figure 3:28.: Component clearance above/below a fixed object).

CLEAR 50 ONTO IDP @ The current Component will be placed on the constrainedcentreline at a clearance of 50 vertically above the pickedp-point. If this p-point is an Arrive or Leave, then the Tubecross-section will be taken into account (see Figure 3:28.:Component clearance above/below a fixed object).

12.02 3:62


Figure 3:28. Component clearance above/below a fixed object

3.11.4 Tube (Bottom of Pipe) Clearance

Keywords:

BOP TOP ONTOP UNDER INFRONT BEHIND

Description:

This command places the current Component on the constrained centreline so that theTube cross-section at its Leave point is a specified clearance from another fixed object. Theclearance can either be specified as a dimension along the constrained centreline in-front-of/behind the object or vertically on top/under it. If the Arrive or Leave points of the fixedobject are used, then its Tube cross-section will also be considered. Using this command,pipes can be spaced on the beams of a rack by Tube-to-Tube clearance.

12.02 3:63


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 are merelyprovided to allow a sensible choice of syntax.


| ||-- BOP -------|| |‘-- TOP -------+-- WRT --.

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

Examples:

BOP ONTO /BEAM The Component will be positioned on the constrainedcentreline so that the Tube emerging from its Leavepoint is zero clearance above /BEAM (see Figure 3:29.:Tube clearance relative to a fixed object).

BOP 30 BEHIND /FLAN The Component will be positioned on the constrainedcentreline so that the Tube emerging from its Leavepoint is 30 clear of the ‘far side’ of /FLAN (see Figure3:29.: Tube clearance relative to a fixed object).

BOP 30 BEHIND PL OF /FLAN

As above, but 30 to the far side of the Leave Tube of /FLAN (see Figure 3:30.: Tube clearance taking intoaccount the Tube diameter).

12.02 3:64


Figure 3:29. Tube clearance relative to a fixed object

Figure 3:30. Tube clearance taking into account the Tube diameter

12.02 3:65


3.11.5 General Clearance of Components and Tube

Keywords:

POSITION PLANE CLEARANCE INFRONT BEHIND ONTOP UNDER

Description:

This command differs from the basic options in two respects:• The clearance dimension can be in an independent plane from the constrained

centreline.• The current element Arrive or Leave Tube can be used (similar to BOP) rather than the

whole element geometry.


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

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

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

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

Querying:

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

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

Examples:

PLANE E CLEARANCE 1000 The current Component will be placed on theconstrained centreline so that it is 1000 clear of thePrevious Component in an East-West direction (seeFigure 3:31.: Component clearance specified relative toan independent plane).

POS PL CLEAR 100 ONTO/BEAM

The current Component will be placed on theconstrained centreline so that the Tube from its LeavePoint is 100 vertically above /BEAM (same as BOP)

12.02 3:66


Figure 3:31. Component clearance specified relative to an independent plane

3.12 Dragging Equipment and Piping NetworksIf equipment is repositioned using ordinary positioning commands, the pipes connected to itdo not automatically move with the item. The DRAG command is used to moveConstrained Networks of Piping, Equipment and Nozzle elements all together. How theconstrained network is created depends on the direction of the dragging operation and thetype of item being dragged.

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

Items that can be dragged are:• Piping Components

In this case the network is formed by searching outwards in all directions from thecomponent until a legal end is found for each ‘leg’ of the network.

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

12.02 3:67


• EquipmentThe piping networks connected to all Nozzles owned by the equipment are searchedfor 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 displacement without 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 the designer’s access

rights

In some instances, the DRAG operation may fail to establish a constrained network. Thismay be because:

• The internal search limit has been reached• A LOCKED element has been found in the network

3.12.1 Dragging Equipment and Nozzles

Keywords:

DRAG AT BY POSITION MOVE

Description:

This command repositions the current element and constrained network to the specifiedposition. The DRAG command can be followed by any standard Equipment and Civilspositioning or moving command.

Command Syntax:

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

Examples:

DRAG AT E3000 The current element and constrained network will be draggedto the specified position.

DRAG BY N500 U500 The current element and constrained network will be draggedby the specified amount.

DRAG MOVE E2000 The current element and constrained network will be movedto the specified position.

DRAG MOVE N CLEAR1000 INF /BUILD10

The current element and constrained network are movedNorth to the specified clearance in front of element /BUILD10.

12.02 3:68


>-- 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> ---+--------+-->

<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> -------------------------------------------+>

12.02 3:69


<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> --------------------------------+->

12.02 3:70


Figure 3:32. Dragging Equipment and Nozzles by a specified amount

Figure 3:33. Dragging Equipment and Nozzles to a specified position

12.02 3:71


Figure 3:34. 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 the previous subsectionexcept that, if the current element is a Branch, the bottom/top of piping positioning syntaxcan be used.

Examples:

DRAG THRO @ The current element and constrained network aremoved along the constrained centreline until the originof the current element lies on a reference plane whichpasses through the cursor position.

DRAG MOVE S DISTANCE1000

The current element and constrained network aremoved South by the specified distance.

12.02 3:72


Note: As it changes orientation as well as position, CONNECT cannot be used inconjunction with DRAG.

Command Syntax:>-- DRAG --+-- <absol> --.

| ||-- <relat> --|| |‘-- <botop> --+-->

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

| |‘------------+-- <repla> --.

| |‘-- <planf> --+-->

Figure 3:35. Dragging Piping to a specified position

DRAG DISTANCE 1000 ONTO/GRADE

The current element and constrained network aredragged so that the origin of the current element is1000 above /GRADE.

DRAG BOP ONTO /BEAM2-1 CLEAR 150

The current (Branch) element and constrainednetwork are dragged so that the Tube will bepositioned on top of /BEAM2-1 with a clearance of150.

Examples:

12.02 3:73


Figure 3:36. Dragging Piping to a specified position

Figure 3:37. Dragging Piping to a given distance from a fixed object

12.02 3:74

DESIGN Reference ManualAutomatic Pipe Routing

4 Automatic Pipe Routing

The automatic pipe-routing facilities of DESIGN enable simple orthogonal pipe routes to begenerated automatically. Additionally, a number of pipes can be ordered and spread acrosspipe racks once the provisional routes have been determined.

In its simplest form, a single Branch may be routed from one point to another, by setting thehead and tail positions and using the route command. In a more complex role, thesefacilities can be used to route a complex set of pipes, avoiding obstructions and followingpreferred paths.

For more complex pipe routing, Ptrac, Pvol and Rplane elements may be used to steer theautomatic routing process along preferred areas. These must be created and positionedbefore entry to automatic routing, because the autoroute process operates with restrictedcommand syntax, which does not allow elements to be created.

4.1 Accessing the Automatic Pipe Routing FacilitiesThe automatic pipe routing facilities are set aside from the rest of the DESIGN commands ina separate command structure called Autoroute Mode.

4.1.1 Entering and Leaving Autoroute Mode

Keywords:

AUTOROUTE EXIT

Description:

The AUTOROUTE command is used to enter the automatic pipe-routing facilities. Once inautoroute mode, the command syntax is restricted to those commands necessary forautomatic routing and rack ordering. To return to the full DESIGN syntax, the EXITcommand is used.

Example:

AUTOROUTE Enters Autoroute mode

EXIT Returns to the full DESIGN syntax

12.02 4:1


4.2 Pipe RoutingPipe routing may be simple and direct, or it may be precisely defined, according to theconstraints and preferences you set. The autoroute process creates a centreline route usingElbows or Bends which are created during the autoroute operation.

The simplest route is one with no constraints, which will result in the shortest possible route,ignoring all other elements in the database. By adding constraints, you can force theautomatic routing process to consider alternatives and avoid obstructions.

The pipes to be routed must contain empty Branches whose Head and Tail references arecorrectly set. The constraints which can be applied are as follows:

• Obstruction Elements such as Equipment items and Structures may be defined asobstructions which must be avoided by the automatic routing process.

• Penalty Volumes - Denote, by means of weighting factors, volumes in space whichcan be either preferred or prohibited areas for pipe routing. Penalty Volumes arecreated as PVOL elements in the Design database, The WEIGH attribute is used todetermine whether the PVOL is a prohibited or preferred area according to its value.High values indicate prohibited areas, low values indicate a preferred area.

• Routing Planes - Routing Planes are elements which are used to guide the automaticrouting mechanism into preferred areas. For example, if a rack was to be positionedbetween two rows of vessels an RPLANE element would be created along thecentreline of the proposed rack. Without the RPLANE element, the autoroute processwould route the two rows of pipes either side of the preferred area, rather than downthe middle.

4.2.1 Routing Pipes along Preferred Axes The automatic pipe routing process will only route pipes orthogonally. However it may followan axis system other than those of the world. Before any routing can take place, therequired axis system must be defined.

Keywords:

AXES

Description:

All pipe routing will be orthogonal to the axes defined by the AXES command. This may betaken as the current axes of any element in the database, but it must be orthogonal with theNozzles and pipe head directions which are being considered.

Example:

WEIGH 100 .01 100 Indicate that the X and Z axes are prohibited and theY axis is preferred.

Example:

AXES /ZONE1 The routing axes will be set to the axes of /ZONE1

12.02 4:2


Command Syntax:>-- AXes <sgid> -->

4.2.2 Setting Routing Planes

Keywords:

RPLANE

Description:

The RPLANE command sets up the list of elements which are to be considered as routingplanes.

Command Syntax:.-----<----.

/ |>-- RPlanes --*-- <sgid> --+-->

4.2.3 Setting Penalty Volumes

Keywords:

PVOL

Description:

The PVOL command sets the list of penalty volumes which will be considered during theautomatic routing process.

Example:

RPLANE /PTRAC1 Sets /ZONE1 as an element in the Routing Plane list. AllRPLAN elements, in the hierarchy below /ZONE1 will beconsidered.

RP /RP1 /RP2 Adds /RP1 and /RP2 to the list. A maximum of 150 RPLANelements may be considered by the automatic routingprocess.

RP Clears the list of Routing Planes.

Example:

PVOL /PV1 Adds /PV1 into the list of Penalty Volumes. If the elementbeing added is not a PVOL, then all items below it in thehierarchy are scanned.

12.02 4:3


Command Syntax:.----<-----./ |

>-- PVolumes --+--*-- <sgid> --+-->|‘-->

4.2.4 Invoking the Automatic Routing ProcessAutomatic pipe routing can be invoked by issuing the ROUTE command with a list of Pipesto be routed. The Pipes to be routed must have empty Branches, with Head and Tailreferences set.

Keywords:

ROUTE

Description:

The ROUTE command begins the procedure of finding logical routes for all of the branchesincluded in the routing list. Each time a successful route has been found, a message isoutput stating the total Pipe length and the number of Elbows used. During the routingprocess, Elbows are selected automatically from the Pipe Specification by default. Bendsmay be selected in preference to Elbows by specifying this option as part of the ROUTEcommand.

Command Syntax:>-- ROute --+-- WIth --+-- ELbows --.

| | || ‘-- BEnds ---| .-----<----.| | / |‘-----------------------+-*- <sgid> --+-->

4.2.5 Setting the Nozzle Offset Factor

Keywords:

OFFSETFACTOR

PV /PZONE1 /PZONE2 Adds /PZONE1 and /PZONE2 to the list. A maximum of 1000PVOLS may be considered during automatic routing.

PV Clears the list of Penalty Volumes.

Example:

Example:

ROUTE /PIPES All of the Branches belonging to /PIPES will be routed.

ROUTE WITH BENDS /PIPES All of the branches belonging to /PIPES will be routedusing Bends in preference to Elbows.

12.02 4:4


Description:

Branches which are routed from Nozzles have default Routing Planes a set distance awayfrom the Nozzle. This is to allow a sensible pipe length between the Nozzle and the firstchange of direction. The default value for this offset is three times the bore of the associatednozzle, and is input in the same terms. For example, a value of 4 would mean that the offsetwould be four times the Nozzle bore.

Command Syntax:>-- OFFSETfactor integer -->

Querying:>-- Query OFFSET -->

4.3 Refining the Automatic Pipe RoutesThe automatic routing process often results in a set of common centreline routes down thecentre of a rack. The following section describes the rack ordering facilities which are able torefine these routes into a more acceptable form.

The rack ordering process works by spreading a number of pipes across a predefined rackvolume. You have various options which may be set to control the spacing of pipes and thedirection of spread across the rack. The parameters 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

4.3.1 Defining the Rack to be Used.

Keywords:

RACK

Description:

The rack is defined by the axes of a PVOL element in the database whose size should besimilar to the physical rack area expected. The PVOL width is important, because its edgesdetermine the position of the first pipe if the pipes are to be spread from one side of the rack.

Command Syntax:>-- RAck <sgid> -->

Example:

OFFSET 5 Sets the offset to be five times the bore of its associated Nozzle.

Example:

RACK /PVOL1 Sets /PVOL1 to be the rack.

12.02 4:5


4.3.2 Defining the Direction of Spread

Keywords:

SDIR

Description:

The spread direction is the direction in which the pipes will be spread laterally when they areordered along the rack. The default position from which the pipes are spread is the centre ofthe PVOL. This may be changed to the side of the PVOL by adding the parameterFROMSIDE to the command.

Note: If no spread direction is specified, the default is taken as the direction of the secondlargest side of the PVOL

Command Syntax:>-- SDir <bdir> --+-- FRomside -----.

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

4.3.3 Defining the Base Direction

Keywords:

BASE

Description:

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 the PVOL.

Command Syntax:>-- BAse <bdir> -->

Examples:

SDIR E Sets the spread direction to be East about the centre of the PVOL

SD N FR Ssets the spread direction to be North, starting from the south side ofthe PVOL

SD N AB As above, but pipes to be spread about centre of rack

Example:

BASE W Sets the base direction to be West. (This should always beperpendicular to the spread direction.)

12.02 4:6


4.3.4 Spreading Pipes about the Rack

Keywords:

SPREAD

Description:

SPREAD moves the pipes laterally across the rack in the SDIR direction to give thespecified clearance. The default clearance is 50mm between pipe walls on the samecentreline.

Command Syntax:>-- SPread --+-- WW ---.

| ||-- FF ---|| ||-- WF ---|| ||-- ALL --|| |‘---------+-- <uval> --. .-----<----.

| | / |‘------------+-*-- <sgid> --+-->

4.3.5 Setting the Bottom-of-Pipe Position

Keywords:

BOP

Description:

The BOP command moves the specified pipes such that their outside diameters are restingon the rack plane in the BASE direction.

Examples:

SPREAD /PIPES Spreads the pipes in /PIPES about the designated rack

SP /PIPES WW 100 Spreads the pipes such that the wall-to-wall clearance is100mm

SP /PIPES WF 4IN Spreads the pipes such that the diameter of Flanges will beconsidered as part of the calculation. In this case, thedistance between a Flange o/d and its adjacent pipe wall, willbe a minimum of 4 inches.

SP /ZONE1 FF 75 Spreads the pipes such that two opposing Flange diameterswill have a minimum clearance of 75mm. Pipes with noFlanges would have a wall-to-wall clearance of 75mm.

SP ALL Repeat previously defined order sequence (for example, on asubsequent rack).

12.02 4:7


Command Syntax:>-- BOP --+-- ALL -->

||-- <uval> --. .-----<----.| | / |‘------------+-*-- <sgid> --+-->

Note: No ordering takes place with the BOP command; it is expected that the BOPcommand is used after a spread.

4.3.6 Combined Spreading and BOP Operations

Keywords:

ORDER

Description:

The ORDER command combines both the SPREAD and BOP operations. It spreads thepipes across the rack to give the required clearances, and then moves them into contactwith the rack plane.

Command Syntax:>-- ORder --+-- WW ---.

| ||-- FF ---|| ||-- WF ---|| ||-- ALL --|| |‘---------+-- <uval> --. .-----<----.

| | / |‘------------+-*-- <sgid> --+-->

Examples:

BOP /ZONE1 Sets the BOP of all pipes in /ZONE1 to sit on the specified rack

BOP ALL Repeat previously defined order sequence

Examples:

ORDER /PIPES WW 100 Spreads the pipes such that the wall-to-wall clearance is100mm and then sets the BOP positions to sit on the rack.

OR /ZONE1 FF 75 Spreads the pipes such that the Flange-to-Flangeclearances are 75mm, and then sets the BOP positions tosit on the rack.

OR ALL Repeat previously defined order sequence

12.02 4:8

DESIGN Reference ManualStructural Design Using Catalogue Components

5 Structural Design Using Catalogue Components

This chapter first describes how logically connected structural steelwork may be built up inDESIGN by choosing Components from the Catalogue. Such structures will normally existin the DESIGN hierarchy at Framework (FRMW) or Subframework (SBFR) level. Theconcepts are then extended for use in building designs, using other materials such asconcrete.

The principal types of element involved in steelwork design are:

Nodes

These define the points within the 3D design model between which steel constructionmembers are to run. Primary Nodes have their position defined in free space, whereasSecondary Nodes have their position defined relative to an owning steel Section. Nodaldata, including the attributes of member elements of Nodes, is particularly relevant for stressanalysis of the steelwork structure.

Sections

Sections represent the physical steel members (columns, beams, bracing struts etc.) whichmake up the interconnected structure. Their cross-sections are defined by reference toCatalogue 2D Profile elements, while their lengths are derived from the positions of theNodes between which the Sections run.

Joints

These are Catalogue items which represent the physical connections between structuralmembers. Primary Joints are owned by Primary Nodes; Secondary Joints are owned bySecondary Nodes. Multiple connections are represented by Primary or SecondaryCompound Joints, which own a SubJoint for each connection point. Linear Joints areused to connect the edges of panels to structural sections or to other panels.

Panels

Panels represent any sheet materials used to clad a structural model. Their shape isdetermined by linking together a set of Panel Vertex elements to form a 2D Panel Loop,which is then extruded in the third dimension to give the required panel thickness.

Fittings

Steelwork Fittings and Panel Fittings are Catalogue items which can represent any ancillaryitem related to, but not an inherent part of, the structure, such as web stiffeners, lifting lugs,

12.02 5:1


access ports, and so on. They are owned by Sections and Panels, respectively. CompoundFittings and Compound Panel Fittings, each of which owns Subfittings, are used torepresent more complex geometry (such as penetrations, where one or more elements passthrough another element).

Generic Sections (GENSECs)

GENSECs can be used to represent any structural item whose geometry can be generatedby sweeping a 2D profile along a linear or curved path. The path, defined by a Spineelement, is determined by a sequence of Spine Points and Curves. In their simplest linearformat, GENSECs may be used instead of Sections and Panels; in more complex formatsthey can represent curved beams, curved walls, etc.

Fixings

Generic fixingscan represent any joint or fitting owned (indirectly) by a GENSEC.

5.1 Creating and Positioning Primary NodesKeywords:

NEW PNODE NPOS

Description:

The first step in creating a new piece of structural steelwork is often the creation andpositioning of a network of Primary Nodes within the 3D design model. PNOD elements arecreated, as for other Design elements, by using the NEW command. They may bepositioned either by using a standard positioning command or by setting the NPOS (NodePosition) attribute directly.

Nodes have no physical size: their positions are used to define the points in space betweenwhich steel Sections are to be positioned/strung.

Command Syntax:>-- NPOSition -- <bpos> -->

(The standard element creation syntax is described in Part 1 of the DESIGN ReferenceManual.)

Example:

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 E1000

Creates a Primary Node which is displaced from theprevious one in the specified way.

NEW PNOD /PNOD3 NPOS E2000 N1000 D500

Creates /PNOD3, then places it at the specifiedposition.

12.02 5:2


Querying:Q NPOS

5.2 Creating and Connecting Sections AutomaticallyKeywords:

STRING FROM TO

Description:

The STRING command is a very powerful multi-functional tool which performs the followingoperations automatically:

• A Section (SCTN) element is created, running between two named Nodes. The Nodepositions are used to set the Section’s POSS (Start Position) and POSE (End Position)attributes. The order of occurrence of the named Nodes in the STRING command lineis used to set the DRNS (Start Direction) and DRNE (End Direction) attributes (on thebasis that the Section is strung FROM start TO end).

• Joint elements (PJOI or SJOI) are created at each Node and are orientated so as to becompatible with the new Section. Thus, both the OPDI (Origin Plane Direction) attributeand the normal to the Cutting Plane (as defined by the CUTP attribute) of each PJOIwill be the same as the DRNS/DRNE attribute of the Section.

• 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 to position the physicalSection within the structural design model. It leaves you at the new Section (SCTN) levelwithin the hierarchy.

Note: The presence of a Section is shown on the DESIGN graphical display as acentreline-only representation (broken line) at this stage. The Section has nophysical form, other than a derived length (related to the inter-Node separation), untilits cross-section has been defined by setting a reference to a Catalogue Profileelement.

Command Syntax:>-- STRIng -+- name -.

| |‘--------+- word -.

| |‘--------+- FRom - <gid> - TO - <gid> -.

| |‘- TO - <gid> - FRom - <gid> -+-->

Example:

STRING /COLUMN1 FROM /PNOD1 TO /PNOD2

Strings a Section named /COLUMN1 between thespecified Primary Nodes.

STRING BEAM FROM /PNOD2 TO /SNOD3 NAME /UB80.LEV2

Strings a Section of GTYPE BEAM between the namedPrimary and Secondary Nodes. The Beam is namedseparately in the second command line.

12.02 5:3


5.3 Section AttributesA 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 are assumed to have uniformproperties throughout their length, including uniform 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 2D Profileelement stored in the Catalogue DB.

• Its length is derived from the separation between the points defined by its StartPosition (POSS) and End Position (POSE) attributes.

This section describes the main attributes which together define a Section as a 3D physicalentity within the interconnected structure.

5.3.1 Cross-Sectional Profile via a Specification Reference

Keywords:

SPREF

Description:

The SPREF (Specification Reference) attribute of a Section must point to a valid Profileelement in a Catalogue DB in order for the Section to be given a physical representation byDESIGN. This is achieved by setting SPREF to the name of a Specification Component in aProject Specification.

Command Syntax:SPRef name

Querying:Q SPRef

5.3.2 Generic Type

Keywords:

GTYPE

Description:

The GTYP attribute may be set to a PDMS word which indicates the purpose of the Sectionwithin the structure. Its setting is not obligatory. (See the Catalogues and SpecificationsUser Guide for a list of suggested GTYP word settings for Profile elements.)

Example:

SPRE /203X203X55KG.UB Sets the Specification Reference of the current Sectionto point to a Profile in the Catalogue. (The .UB suffix inthe Specification Component name would normallyindicate that this Profile represents a Universal Beam.)

12.02 5:4


Command Syntax:>--- GTYPe --- word --->

Querying:Q GTYPe

5.3.3 Start and End Positions

Keywords:

POSSTART POSEND

Description:

When a Section is Strung (see Creating and Connecting Sections Automatically), its startand 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 Manually ConnectingSections), the settings of POSS and POSE are derived from the intersections of the Jlinethrough the End Cutting Planes of the Section and the Joints. In either case, POSS andPOSE are set automatically.

It is also possible to set POSS and POSE specifically; for example, where a Section extendsinto free space, with at least one end unconnected. This may be done by specifying thecoordinates directly, or by relating them to the position of another design element.

Command Syntax:>--+-- POSStart --.

| |‘-- POSEnd ----+-- <bpos> -->

Querying:Q POSStart

Q POSEnd

Example:

GTYP BEAM Sets the GTYP of the current Section to BEAM.

Example:

POSE E1250 N2000 D750 Positions the Section’s end at the specified point.

POSS /PNOD1 Positions the Section’s start at the NPOS of thespecified Primary Node.

12.02 5:5


5.3.4 Start and End Plane Directions

Keywords:

DRNSTART DRNEND

Description:

The directions of the start and end cutting planes of a Section (that is, the directions of theperpendiculars to the planes which define the ‘cut’ ends of the Section) are usually definedautomatically when the Section is connected within the structural model; either by Stringing(see Creating and Connecting Sections Automatically) or manually (see ManuallyConnecting Sections). The settings of the corresponding DRNS and DRNE attributes arethen derived automatically from the directions of the associated Joint’s Cutting Planes.

It is also possible to set DRNS and DRNE specifically; for example, where a Sectionextends into free space, with at least one end unconnected. In this case each cutting planedirection must be in the general direction of the other end of the Section.

Command Syntax:>--+-- DRNStart --.

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

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

Querying:Q DRNStart

Q DRNEnd

5.3.5 Orientation Angle

Keywords:

BANGLE

Description:

The orientation of a Section about its Neutral Axis is defined in terms of an angularclockwise rotation when viewed in the POSS-to-POSE direction. The angle of rotation fromthe default orientation is held as the setting of the Beta Angle (BANG) attribute of theSection.

Example:

DRNS N45W Sets DRNS to the specified direction, regardless of thedirection of the Section’s Z-axis.

DRNE PERP Sets DRNE so that the end cutting plane is perpendicular tothe Section’s Z-axis (giving a square end as opposed to achamfered end for a Section which has a skewedconnection).

12.02 5:6


Command Syntax:>-- BANGle value -->

Querying:Q BANGle

5.3.6 Joint Start and End References

Keywords:

JOISTART JOIEND

Description:

Section ends which have been connected in the structure have their JOIS (Joint Start) andJOIE (Joint End) attributes set such that they cross-refer to the Joints to which those endsare connected. (The Joints have a similar cross-reference, the CREF attribute, back to theattached Section.)

These attributes are set automatically when a Section is connected and you will not usuallyneed to set them specifically.

Command Syntax:>--+-- JOIStart --.

| |‘-- JOIEnd ----+-- <gid> -->

Querying:Q JOIStart

Q JOIEnd

Example:

BANG 90

POSS

DRNS

POSE

DRNE

BANGNA

SPREF of SCTNpoints to PROFin Catalogue

Example:

JOIE /PJOI.RB.2 Sets logical connection from Section’s end to named PrimaryJoint.

12.02 5:7


5.3.7 Start and End Connection Types

Keywords:

CTYSTART CTYEND

Description:

Section ends which have been connected in the structure have their CTYS (StartConnection Type) and CTYE (End Connection Type) attributes set such that they matchthose of the Joints to which those ends are connected. This is done by setting CTYS/CTYEto a word which matches the Joint’s CTYA attribute in the Catalogue; see the Cataloguesand Specifications User Guide.

These attributes are set automatically when a Section is connected and you will not usuallyneed to set them specifically.

Command Syntax:>--+-- CTYStart --.

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

Querying:Q CTYStart

Q CTYEnd

5.3.8 Start and End Releases

Keywords:

SRELEASE ERELEASE

Description:

The two Release attributes, the Section Start Release (SREL) and the Section End Release(EREL), may be used to define how the Section behaves under the effect of applied forcesand moments. They are relevant only for stress analysis of the structure.

The attribute settings allow for two types of movement of the Section ends when externalforces are applied, namely:

• Linear movement along a specific axis (DX, DY, DZ)• Rotation about a specific axis (RX, RY, RZ)

Example:

CTYS BOLT The Section’s start is to be connected to its attached Joint bymeans of bolts. (The CTYA of the Joint must also be set toBOLT for a compatible connection; see Part 3 of the DESIGNReference Manual for information about data consistencychecking.)

12.02 5:8


Command Syntax:>--+-- SRELease --. .---<---.

| | / |‘-- ERELease --+--*-- DX ---|

| ||-- DY ---|| ||-- DZ ---|| ||-- RX ---|| ||-- RY ---|| ||-- RZ ---|| |‘-- sign --+-->

Querying:Q SRELease

Q ERELease

5.4 Creating and Positioning Secondary NodesA Secondary Node is owned by, and positioned relative to, an existing Section. It enablesyou to position and connect another Section (an Attached Section) at any point along thelength of the first Section (the Owning Section), rather than having to define the position ofthe Attached Section in ‘free space’.

Keywords:

NEW SNODE ZDISTANCE

Description:

SNOD elements are created, as for other Design elements, by using the NEW command.

They are positioned by specifying their distance from their owning Section’s Start Position,measured along the Neutral Axis towards the End Position. This distance, which is held inthe Node’s ZDIST attribute, may be specified as an absolute length, as a proportion of theoverall distance between POSS and POSE (i.e. a proportion of the derived length of theSection), or by reference to any marker (pin, p-point, p-line etc.), element or plane.

Example:

SREL DX RX RY The Start of the Section is constrained such that it can move onlyin the X direction and can rotate only about the X and Y axes.

12.02 5:9


Command Syntax:>-- ZDIStance --+-- <uval> --------------.

| ||-- PROPortion -- value -+-- FRom --+-- STart --.| | | || | |-- ENd ----|| | | || | ‘-- <gid> --|| | || ‘----------------------+| || ||-- <marke> ------------------------------------|| |‘-- <plane> ------------------------------------+->

Querying:Q ZDIStance

5.5 Creating and Positioning JointsJoints elements constitute the physical means by which Sections are connected together.

A Primary Joint (PJOI) is owned by a Primary Node. Its position is derived from that of itsowning Node.

A Secondary Joint (SJOI) is owned by a Secondary Node. Its position is derived from thatof its owning Node, and thus, in turn, from the position of the Section which owns that Node.

Example:

NEW SNOD /SNOD1 ZDIST 1500(At SCTN level)

Creates a Secondary Node named /SNOD1 atthe specified distance from the start of theSection. The Node is positioned on the NeutralAxis of the owning Section.

NEW SNOD /SNOD2 IS 1250 FROM END

The position of the new Node is measured fromthe POSE position rather than from the defaultreference of POSS.

NEW SNOD /SNOD4 ZDIS PROP .33

The new Node is positioned one third of the wayalong the Section’s Neutral Axis, measured fromthe start of the Section.

NEW SNOD /SNOD3 ZDIS PROP 0.25 FROM END

The new Node is positioned one quarter of theway along the Section’s Neutral Axis, measuredfrom the end of the Section.

NEW SNODE /SNOD5 ZDIS PLANE W30N DIST 0.0

The new Node is positioned at the intersection ofthe owning section’s neutral axis with the definedplane.

12.02 5:10


A Compound Joint (PCOJ or SCOJ) is positioned relative to a Node, as for a PJOI or anSJOI, but all settings which define its connections are associated with subsidiary SubJointsowned by the Compound Joint (one SubJoint for each connection).

You will most often create and position Joints automatically using the STRING command(see Creating and Connecting Sections Automatically). This section describes how you cancarry out these operations independently and how you can modify the positions of Jointswhich have been created previously.

A Joint is a Catalogue Component, which is selected in the design by setting its SPREFattribute to point to the required Component Specification.

5.5.1 Creating Primary Joints

Keywords:

NEW PJOINT

Description:

A new Primary Joint can only be created at PNOD level.

Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGN ReferenceManual.

5.5.2 Creating Secondary Joints

Keywords:

NEW SJOINT

Description:

A new Secondary Joint can only be created at SNOD level.

Example:

NEW PJOI /JOINT1 Creates a new PJOI with a default position and orientation.The default position places the DELPOS (Delta Position) ofthe Joint at the NPOS of the Node. The default orientationdirects the OPDI (Origin Plane Direction) of the Joint UP.

Example:

NEW SJOI /SJOINT1 Creates a new SJOI with a default position and orientation.The default position places the POSL (Position Line) of theJoint through the owning SNOD.The default orientationdirects the CUTP (Cutting Plane Direction) of the Joint Up.

12.02 5:11


Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGN ReferenceManual.

5.5.3 Setting Joint Geometry via a Specification Reference

Keywords:

SPREF

Description:

Both PJOIs and SJOIs must have their geometry defined by setting their SPREF attributesto point to a valid Specification Component in a Project Specification in the Catalogue DB.Both types of Joint may point to the same Specification Component if required.

Command Syntax:>--- SPRef name --->

Querying:Q SPRef

5.5.4 Positioning and Orientating Primary Joints

Keywords:

DELPOSITION OPDIRECTION BANGLE

Description:

The position and orientation of a Primary Joint are defined by the settings of the followingthree attributes:

• The Delta Position (DELP) is the offset between the Joint’s Origin Plane and theposition of its owning Node (the NPOS of the PNOD), expressed in the coordinatesystem which applies to the 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 the normal to the plane throughthe Joint’s origin, as defined in the Catalogue representation of the Joint.

• The Beta Angle (BANG) is the angle of rotation of the Joint about its Origin PlaneDirection, measured clockwise as viewed along that direction. The default setting iszero, so that the Joint’s orientation is as defined by its Catalogue representation.

Example:

SPRE /10X10.BRAK90 (The .BRAK90 suffix in the Specification Component namewould normally indicate that this represents a 90 degreebracket joint.)

12.02 5:12


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) BANGLE

Description:

The position and orientation of a Secondary Joint are defined with respect to its owningSecondary Node. The position of this Node is separately defined with respect to its owningSection, as described Creating and Positioning Secondary Nodes. The Joint’s position withrespect to the Section depends, therefore, upon the settings of two attributes:

• The Z-axis Distance (ZDIST) attribute of the owning SNOD.

Example:

DELP N4.5 Offsets the Joint by 4.5 (mm) in a northerly direction.

OPDI N Orientates the Joint so that the normal to its Origin Planepoints North.

BANG 180 otates the Joint about its current Origin Plane Direction by180 degrees.

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

12.02 5:13


• The Positioning Line (POSL) attribute of the SJOI itself. This defines the position ofthe Joint in relation to the p-line system which has been set up for the owning Section’sProfile within the Catalogue. The default POSL setting is NA (Neutral Axis), so that theJoint’s Origin (more strictly, its JLIN) lies on the Section’s Neutral Axis at the positionspecified 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 Joint about its Origin PlaneDirection. The default setting is zero, so that the Joint’s orientation is as defined by itsCatalogue representation.

Command Syntax:>-- POSLine word -->

where word is usually one of the following:

>-- BANGle --+-- value ------------------.| |‘-- <bdir> TOwards <bdir> --+-->

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)

Example:

POSL TOS The Positioning Line of the Joint is coincident with the TOS(Top of Steel) p-line of the Section.

POSL BOS The Positioning Line of the Joint is coincident with the BOS(Bottom of Steel) p-line of the Section.

NA (Neutral Axis)

TOS (Top of Steel)

BOS (Bottom of Steel)

12.02 5:14


Querying:

5.6 Attributes of Connected JointsThe attributes and their settings described in Creating and Positioning Joints are applicableto any Joints, whether or not they have been connected to attached Sections. In addition,Joints which have been fully connected (that is, those which have both an Owning and anAttached Section) have other relevant attributes set. These are described in this section.

5.6.1 Connection Reference

Keywords:

CREFerence

Description:

The Connection Reference attribute (CREF) of a Joint points to the identifier of the AttachedSection.

This attribute is set automatically when a Section is connected and you will not usually needto set it specifically.

Command Syntax:>-- CREFerence --+-- <gid> --+-- STart* --.

| | || |--- ENd ----|| | || ‘------------+| |‘--- NULref --------------+-->

where <gid> identifies the Section to be connected.

Q POSLine (At the SJOI)

Q ZDISTance (At the SNOD)

Q BANGle (At the SJOI)

Examples:

CREF /BEAM1 START Sets Connection Reference to start of named Section.

CREF /BEAM2 END Sets Connection Reference to end of named Section.

CREF /COLUMN2 Sets Connection Reference to start of named Section.

CREF NULREF Disconnects the Joint.

12.02 5:15


Querying:Q CREFerence

5.6.2 Cutting Plane

Keywords:

CUTPlane

Description:

The position of a Joint which has an Attached Section is derived from the intersection of theAttached Section’s Joining Line (JLIN) and the Joint’s Cutting Plane. The Cutting PlaneDirection, that is the direction of the normal to the Cutting Plane, is defined by the setting ofthe CUTP attribute. The default direction is Up.

It is the position of the Joint’s Cutting Plane which defines the effective length of the Section(but see also Cutback Allowance).

Command Syntax:>-- CUTPlane --+-- <bdir> ---------.

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

Querying:Q CUTP

5.6.3 Cutback Allowance

Keywords:

CUTBack

Description:

The derived length of an attached Section is, unless otherwise specified, the distancebetween the Cutting Planes of the Joints at its two ends. The CUTB attribute allows you tospecify a length by which the Section should be shortened or extended to allow for any localfitting geometry at the Joint’s attachment point (to allow for weld metal, packing pieces etc.).

A positive value of CUTB shortens the derived length of a Section attached to the Joint; anegative CUTB lengthens the attached Section. The default is a CUTB setting of zero.

Example:

CUTP N45D The normal to the Cutting Plane points in the specifieddirection.

CUTP PERP The normal to the Cutting Plane is set perpendicular to theJoint’s Origin Plane.

12.02 5:16


Command Syntax:>-- CUTBack <uval> -->

Querying:Q CUTBack

5.7 Manually Connecting SectionsThis section describes the commands which allow you to connect Sections and Joints‘manually’; that is, without using the STRING command. The relevant Nodes and Jointsmust have been created first, as described in the preceding sections of this chapter.

This section also explains how to disconnect and reconnect Sections and Joints, so that youcan modify existing interconnected structural designs.

5.7.1 Connecting Sections

Keywords:

CONNECT START END FREE RECALCULATE

Description:

When a Section is connected manually, the relevant End Cutting Plane of the Section(DRNS/DRNE) is superimposed on the Cutting Plane (CUTP) of the connecting Joint. Thisrequires that the direction and through point of the Section have been correctly specified;that is, that the correct end points are on an extension of the Section’s Neutral Axis.

In cases of misalignment, the Section’s position and orientation are given highest priority.Thus, connecting a Section will not cause the Section to move or rotate. The Joint will bealigned with the Section, if possible (but see the FREE option, below).

When the connection is made, the connection cross-references between the Section andthe Joint are set. That is, the JOIS/JOIE of the Section and the CREF of the Joint arematched. Further, the relevant Connection Type attribute of the Section (CTYS or CTYE) isset to point to the Attached Connection Type attribute (CTYA) of the Catalogue Joint.

The FREE option allows the existing joint position to remain fixed, and the POSS and/orPOSE of the section to be adjusted. This may cause the section to be displaced sideways,or its direction to rotate. It may also cause SNODEs and FITTINGs along the section to bedisplaced (even with RECALCULATE).

When the connection has been made, the corresponding Start or End Point of the Section(POSS/POSE) is calculated from the intersection of the Z axis of the Section with the newCutting Plane which passes through the end of the Joint’s JLIN.

Example:

CUTB 6 An attached section will have its derived length reduced by 6mm.

CUTB -6 An attached section will have its derived length increased by 6mm.

12.02 5:17


The RECALCULATE option causes the positions of elements which are members of aSection to be recalculated so that they remain in the same positions if the Section is moved.For example, the ZDIS defining the position of a Secondary Node would be recalculated ifthe 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 of FITTINGs and SNODEsalong the section are recalculated to be as close as possible to their original positions.

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.7.2 Disconnecting Sections

Keywords:

DISCONNECT START END RECALCULATE

Description:

When a Section is disconnected, the connection cross-references (JOIS/JOIE - CREF) areunset 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 theconnection operation) is returned to its default position.

The RECALCULATE option causes the positions of elements which are members of aSection to be recalculated so that they remain in the same positions if the Section is moved.

Example:

CONN END TO /SJOINT3 Where the current element is a Section.

CONN WITH START OF /BEAM1

Where the current element is a Joint.

CONN START TO /PJOIN2 RECALC

Connects the start of the current Section without movingthe positions of any secondary elements owned by theSection.

12.02 5:18


For example, the ZDIST defining the position of a Secondary Node would be recalculated ifthe POSS (from which ZDIST is measured) were moved as a result of a DISCONNECTcommand, so that the SNOD remained unmoved.

Command Syntax:>-- DISConnect --+-- STart --.

| ||-- ENd ----|| |‘-----------+-- RECALCulate --.

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

5.7.3 Reconnecting Sections

Keywords:

RECONNECT START END RECALCULATE

Description:

The RECONNECT command would typically be used to reconnect a disconnected Sectionin the following circumstances:

• Following the movement of a Joint: the attached Section is moved to the new Jointposition.

• Following the resetting of a cutback allowance at a Joint (see Cutback Allowance): thelength of the Section is modified to allow for the new cutback distance.

• Following the movement of a Primary Node which has a member Joint attached to anexisting Section.

In each case the RECONNECT command attempts to restore the consistency of theconnected model.

The RECALCULATE option causes the positions of elements which are members of aSection to be recalculated so that they remain in the same positions if the Section is moved.For example, the ZDIST defining the position of a Secondary Node would be recalculated ifthe POSS (from which ZDIST is measured) were moved as a result of a RECONNECTcommand, so that the SNOD remained unmoved.

Example:

DISCO START Disconnects the start of the current Section.

DISCO END Disconnects the end of the current Section.

DISCO Disconnects both the start and end of the current Section.

DISCO END RECALC Disconnects the end of the current Section, but retains thepositions of any secondary elements owned by the Section.

12.02 5:19


Command Syntax:>-- RECOnnect --+-- STart --.

| ||-- ENd ----|| |‘-----------+-- RECALCulate --.

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

5.8 Repositioning Steelwork ElementsThe concept of connectivity in structural steelwork influences the types of repositioningoperations which are allowed. Repositioning operations using the standard DESIGNcommands will also move items whose positions depend on those of the items being directlymoved.

5.8.1 Reversing Section Start and End Positions (‘Flipping’)

Keywords:

FLIP

Description:

The FLIP command mutually exchanges references to the Start and End of a steelworkSection, effectively reversing its orientation. This is mainly of use for reorientating a Sectionwith a non-symmetrical profile if you have mistakenly strung it the wrong way round. It isbest used before any Secondary Nodes or Fittings are placed along the Section.

FLIP causes the settings of the following pairs of attributes to be exchanged:• POSS and POSE (Start and End Positions)• DRNS and DRNE (Start and End Plane Directions)• JOIS and JOIE (Start and End Joint References)

Note: It is not intended that Sections with secondary connections be Flipped, although youcan do so if you fully understand the effects outlined below. These effects may notgive the results you had intended and may therefore require further designmodifications to be made:

The settings of the SREL and EREL (Start and End Release) attributes are not exchanged.Since, however, the ends to which they refer have changed (since the original Start is nowthe End, and vice versa), their effects will be reversed in the physical model.

Example:

RECON START Reconnects the start of the current Section.

RECON END Reconnects the end of the current Section.

RECON econnects both the start and end of the current Section.

12.02 5:20


• The Member List of the Flipped Section remains unchanged, so that any cross-references to member elements by list position remain correct. The ZDIST attributesof any SNODs, FITTINGs, etc. remain the same, so that their positions are now derivedfrom the opposite end of the Section (the new Start end), thereby causing thesemember elements to move.

• Any Connected items referenced via SJOIs will not move, since the positions of thecorresponding SJOIs will not move to the new SNOD positions until they areDisconnected. If you wish to reverse a Section with existing secondary connectionsyou should, 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 their associated SJOIs

(now disconnected) in the reversed locations.• Reorientate all connected Sections so that they realign with the modified SJOI

locations along the Flipped Section (or reset the ZDIST attributes of the SNODs so thatthey are repositioned where you want them).

• Reconnect the Flipped Section to all the attached Sections.

Command Syntax:>--- FLIP --->

Querying:

You may find the following querying commands, used both before and after giving the FLIPcommand, helpful in checking the precise effects of the command:

5.8.2 Moving Steelwork ElementsNote: The positioning/moving syntax described in Equipment and Primitives, also applies

to Structural steelwork elements.

Keywords:

MOVE ALONG BY AT

Description:

Movement relative to a fixed starting position (MOVE, ALONG, BY commands) is possiblefor all structural elements which have a directly defined location in the 3D model; forexample, Frameworks, Subframeworks, Primary Joints and Nodes (but not SecondaryJoints and Nodes, whose positions are dependent on that of a Section), Routing Planes,Panels, etc.

Example:

FLIP Reverses the Start and End attribute settings for the current element asoutlined in the preceding description.

Q ATT For checking, in particular, all Start and End related settings(POSS/POSE, DRNS/DRNE, etc).

Q DER POS For checking the derived positions of SNODs and/or SJOIs.

12.02 5:21


Absolute positioning (AT command) is possible only for Sections, Primary Nodes, RoutingPlanes and Panels.

5.8.3 Modifying Lengths of Sections

Keywords:

EXTEND START END PROPORTIONAL RECALCULATE

Description:

Once positioned, a Section may have its ends repositioned independently by using theEXTEND command. This effectively lengthens or shortens the Section by a specifiedamount and resets its POSS and/or POSE attributes accordingly. (You could, of course, setPOSS and/or POSE directly, as described in Start and End Positions, but this would needprior calculation of the new positions needed to achieve the required length change.)

The increase or decrease in length may be specified as a direct measurement or as aproportion of the current length of the Section.

The <plane> allows you to define the amount of extension required by intersecting theneutral axis with a defined plane. The section is extended (or shortened) to meet the plane.

The RECALCULATE option causes the positions of elements which are members of themodified Section to be recalculated so that they remain in the same positions after thechange. For example, the ZDIST defining the position of a Secondary Node would berecalculated if the POSS (from which ZDIST is measured) were moved by the EXTENDcommand, so that the SNOD remained unmoved.

Example:

MOVE ALONG E45N DISTANCE 500

Moves Current Element in specified direction by specifieddistance.

BY N1000 E5000 U7000 Moves Current Element as specified relative to its currentposition.

AT E2000 N2000 U1000 Moves the Current Element to the specified position. In thecase of a Section, POSS is set to this position; in the caseof a Primary Node, NPOS is set to this position.

Example:

EXTEND END BY E1000 Move POSE by 1000mm Eastward.

EXTEND BY E1000 As above (defaults to END).

EXTEND START BY W1000RECALC

Move POSS by 1000mm Westward and recalculate thepositions of all member SNODs, FITTs etc. so that theyremain unmoved.

12.02 5:22


Command Syntax:>-- EXTend --+- STart -.

| ||-- ENd* -|| |‘---------+- PROPortional - value -.

| ||- BY --- <axpos> ------|| || ||- <plane> -------------|| |‘- <uval> --------------+- RECALCulate --.

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

5.8.4 Reorientating Steelwork Elements

Keywords:

ROTATE BY ABOUT THROUGH AND

Description:

The method of rotating a Section about its Neutral Axis by setting its BANG attribute wasdescribed in Orientation Angle. This section explains the use of the ROTATE command toachieve a greater range of reorientating effects on Sections and on other steelworkelements.

The command allows you to specify the rotation required in any of the following ways:• As a specified angle of rotation about a default axis (similar in effect to setting the

BANG attribute). This default axis is the Neutral Axis for Sections, Joints and Fittings,and the Z axis for other elements.

• As a specified angle of rotation about a given axis, the latter defined by its directionand/or through point. If the direction and/or through point are omitted, the default

EXTEND START BY U500 E2000 S500

Move POSS by the given amounts.

EXTEND END 1750 Move POSE so as to increase the Section’s length by1750mm (default units).

EXTEND -1750 Move POSE (defaults to END) so as to decrease theSection’s length by 1750mm (default units).

EXTEND START PROP 0.25 Move POSS so as to increase the Section’s currentlength by 25%.

EXTEND PROP -0.2 Moves POSE (defaults to END) so as to decrease theSection’s length by 20%.

EXTEND END PLANE E30N DIST 0.0

Moves POSE to meet the defined plane.

Example:

12.02 5:23


direction is that of the Neutral Axis or Z axis; the default through point is the Origin orStart Position (depending on the type of element involved).

• By reference to the component’s axes or p-lines.

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

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

Example:

ROTATE BY -45 Rotates by 45° about the element’s NeutralAxis or Z axis (anticlockwise when lookingfrom Start to End or in the +Z direction, sincethe rotation is specified as a negative angle).

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

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

ROT THRO POSE ABOUT S BY -25 Rotates a Section about an axis whichpasses in the N-S direction through its Endposition. The rotation is 25° anticlockwisewhen looking S along this axis.

ROT ABOUT PPLIN TOS BY 45 Rotates by 45° about the Top-of-Steel p-line(clockwise when looking in the Start to Enddirection).

ROT AND PPLIN BOS IS E45N Rotates element about its Neutral Axis untilthe Bottom-of-Steel p-line points as closelyas possible to the E45N direction.

ROTATE AND Y IS N45W25D Rotates element until the Y axis points asclosely as possible to the N45W25Ddirection.

ROT AND PPLIN TOS IS PPLIN BOS OF /SCTN1 LEAV DIR WRT /STRU1

Rotates element until its TOS p-line points inthe direction of the BOS p-line of / SCTN1 inthe specified coordinate system.

12.02 5:24


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.9 Positioning and Orientating Using P-linesP-lines in a 3D structure represent lines, derived from points defined in the Catalogue forcorresponding Profiles or Joints, which have associated direction vectors in the X-Y plane.A typical configuration for an ‘extruded’ I-section component is illustrated in Figure 5:1.:Typical P-lines and Axes for a Section; typical p-lines associated with a wider range ofprofiles are illustrated in the guide Structural Design Using PDMS.

A p-line can provide a very convenient reference line or axis within an element’s 3Dgeometry (as derived in the design model) for positioning or orientating the element itself, orfor defining some other geometry relative to the element. Positions may be defined alongthe length of a p-line; directions may be defined in terms of a p-line’s coordinate axes (the p-line direction being, by default, along its +Z axis).

12.02 5:25


Some examples have already been introduced in the earlier sections of this chapter. Thissection further illustrates the possible uses of such techniques.

Figure 5:1. Typical P-lines and Axes for a Section

5.9.1 Identifying P-lines

Keywords:

PPLINE IDPLINE

Description:

A p-line may be identified in either of the following ways:• By reference to its PKEY attribute (see the Catalogues and Specifications User Guide

for details of how this is set) and its owning element (if this is not the current element).• By picking it on the display using the cursor.

Command Syntax:

(This is the <plin> syntax referred to elsewhere in this manual.)

>--+-- PPLINe -- word --+-- OF <gid> --.

PLIN BOS

PLIN NA

PLIN TOS

Z

X

Y

BOS axes

SITE axes

Z

X

Y

TOS axes

Y X

Z

SCTN axes

Y X

Z

POSE

POSS

Example:

PPLINE TOS Specifies the Top-of-Steel p-line of the current element.

PPLINE BOS OF /BEAM2 Specifies the Bottom-of-Steel p-line of /BEAM2.

IDPLINE @ Specifies the p-line to be picked using the cursor.

12.02 5:26


| | || ‘---------------+| |‘--- IDPLine -- @ ----------------------+-->

where word is the setting of the p-line’s PKEY attribute, as defined in the Catalogue; forexample: 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 OFFSET

Description:

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 the POSS of a Section) or

its end (typically POSE).• As a proportional distance along the p-line, expressed as a fraction 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.

Example:

POSITION PPLINEBOS 500

Calculated position is on the BOS p-line, 500mm from itsstart (by default); for setting a variable or for querying.

POS PPLIN TOS 1000FROM END

Calculated position is on the TOS p-line, 1000mm fromits end.

POS AT PPLIN NA OF/SCTN2 PROP .25

Calculated position is on the Neutral Axis of /SCTN2,25% along its length as measured from its start (bydefault).

POS AT PPLIN TOS OF/BEAM1 END

Position is defined as the end of the TOS p-line of /BEAM1 (probably, but not necessarily, the POSE settingfor /BEAM1).

BY PPLIN TOS OFFSETFROM PPLIN BOS

Moves the current element (Section or Joint) by theoffset distance between its TOS and BOS p-lines.

BY PPLIN BOS OFFSETFROM PPLIN TOS

Moves the same distance as the preceding example, butin the opposite direction.

BY PPLIN TOS -OFFSETFROM PPLIN BOS

The same effect as the preceding example.

12.02 5:27


Command Syntax:

Note: The following syntax describes only the p-line referencing options for defining aposition. These are in addition to the positioning/moving syntax described inEquipment and Primitives, which also apply 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 Identifying P-lines.

Querying:Q <plin> --+-- <uval> --------------.

| ||-- PROPortion - value --+--------------------------.| | || ‘-- FROm --. || | |‘-----------------------------------+-- STart* --. |

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

Q <plin> -- OFFSet --+-- FROm -- <plin> --.| |‘--------------------+-->

Querying Examples:

Q PPLIN TOS END Position of end of p-line.

Q PPLIN BOS PROP 0.3 Position of point 30% of distance along BOS from start(by default) towards end.

Q PPLIN NA PROP -1.5 FROM END

Position of point which is 1.5 times length of NeutralAxis away from end of p-line in direction away fromstart.

Q PPLIN TOS OFFS FROMPPLIN BOS

Offset distance between TOS and BOS.

Q PPLIN TOS OFFS Offset distance between TOS and Neutral Axis (bydefault).

12.02 5:28


5.9.3 Orientating by Using P-lines

Keywords:

PPLINE DIRECTION X Y Z LEAVE

Description:

You can orientate a structural element by referring its axes to the directions of one or morep-lines. By default, references will be taken from the Z (or LEAVE) direction.

Command Syntax:>-- <plin> --+-- X ------.

| ||-- Y ------|| ||-- Z ------|| ||-- LEAve --|| |‘-----------+-- DIRection -->

Querying:Q <plin> --+-- X ------.

| ||-- Y ------|| ||-- Z ------|| ||-- LEAve --|| |‘-----------+-- DIRection -->

5.10 Creating and Connecting Panels

5.10.1 Creating a PanelA Panel (PANE) element represents any sheet material used to clad a structural model. Thegeometry of a Panel is defined by a subsidiary Panel Loop (PLOO) element. The 2D shapeof the Panel Loop is defined by linking together a set of Panel Vertex (PAVE) elements,each of which has a specific position in the Panel’s coordinate system. The polygon thusformed defines the shape of the Panel in the same way that a Profile defines the cross-sectional area of a Section. The Height (HEIG) attribute of the PLOO defines the distance

Example:

ORI Y IS PPLIN TOS OF /SCTN1 X DIR AND Z IS U

Orientates the current element such that its Y axis points inthe X direction of the TOS p-line of /SCTN1 and its Z axispoints Up. If, for example, the X direction of the TOS p-line of /SCTN1 points East, then this command line is equivalent toORI Y IS E AND Z IS U.

12.02 5:29


through which this 2D shape is extruded to form the 3D Panel; that is, it defines the Panelthickness, thus:

Each PAVE can have an optional fillet radius which defines a circular arc which bulges into(negative radius) or out of (positive radius) the PLOO area. The default fillet radius of zerodenotes a point.

To define a new Panel, you must, therefore, first create a PANE element (using NEW PANEetc.), then create a PLOO below it in the hierarchy, and then create and position as manymember PAVEs as necessary to define the shape of the PLOO and thus the PANE. (The Zco-ordinates of the PAVEs are ignored; they are constrained to lie in the plane of the PLOO.)

5.10.2 Splitting a Panel

Keywords:

SPLIT ON

Description:

You can split a Panel along its line of intersection with a given plane or Section. The Panel issplit into two or more new Panels which have same owner as the original one. More thanone new Panel may result if the original one has re-entrant vertices.

The vertices of the original Panel are moved to the new Panel(s) as appropriate and newvertices are created where the intersection line crosses the edges of the original Panel.

Command Syntax:>-- SPLIT --+-- PLANE <dir> -- THROugh <bpos> --.

| |‘-- ON <section_id> ----------------+-->

= Panel Loop (PLOO)

= Panel Vertex (PAVE)HEIGof PLOO

Example:

SPLIT PLANE N THRO N1000

Splits current panel along its line of intersection with thespecified plane

SPLIT ON /BEAM1 Splits current panel along the Neutral Axis (projected ifnecessary) of the named section

12.02 5:30


5.10.3 Connecting Panels using Linear JointsLinear joints are used to connect structural items along edges or faces. They effectivelyhave linear (2D) connectivity, whereas Primary and Secondary Joints 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 to connect twoPanels together. The start and end of the PALJ are defined by two Panel Vertex (PAVE)points. Logical connections from the attached Panel are made by setting Master Vertex(MVERT) attributes of two of the Panel’s PAVEs to point to the corresponding PAVEs on thelinear joint, thus:

In this example, PANE1 is the Owning Panel and PANE2 is the Attached Panel.

A Section Linear Joint (SELJ), owned by a Section, is used to connect a Panel to aSection. The start and end of the SELJ are defined by two Section Vertex (SEVE) points.Logical connections from the attached Panel are made by setting Master Vertex (MVERT)attributes of two of the Panel’s PAVEs to point to the corresponding SEVE’s on the linearjoint, thus:

Keywords:

LINK UNLINK

= PALJ (owned by PANE1)= PAVE (PLOO of PANE1)= PAVE (owned by PALJ)

MVERT attribute of PAVEpoints to PAVE of PALJ

PALJ

PANE1

PANE2

*

*

*

*

*

= SELJ (owned by SCTN)= PAVE (PLOO of PANE)= SEVE (owned by SELJ)

MVERT attribute of PAVEpoints to SEVE of SELJ

SELJ

PANE

SCTN

*

*

*

*

*

12.02 5:31


Description:

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 of consecutive 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 slave vertices, while thevertices of the item linked to (which define the properties at the connection point) aredefined as master vertices.

When you link a panel, any new panel vertices needed will be created automatically tocorrespond with the master vertices of the item connected to. You can specify the positionand direction of creation of the new vertices in the Panel Loop’s vertex sequence as part ofthe command. If the panel has no PLOOP, one will be created automatically.

UNLINK unsets the connection cross-references created by a LINK command.

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:

Example:

LINK VERT CE TO /PAVE2 Links current vertex (slave) to vertex /PAVE2 (master).

LINK PANEL /PANE3 TO EDGE /PAVE5 /PAVE6 AFTER /PAVE2

Links panel /PANE3 to edge between /PAVE5 and /PAVE6 and positions any new vertices needed after /PAVE2 in the PLOOP of /PANE3.

<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)

12.02 5:32


<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 the panel. Defaultsare implied start to implied end of joint.

The FORWARDS/BACKWARDS options specify the direction of vertices within the joint.

The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loop at which tocreate vertices corresponding to those of the joint (master vertices).

<qualifier2>:>--+-- AFTer <vid> ----------.

| ||-- BEFore <vid> ---------|| ||-- BETween <vid> <vid> --|| |‘-------------------------+->

The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loop at which tocreate vertices corresponding to those of the master vertices.>-- UNLINK --+-- <vid> -- FRom -- <vid> --.

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

Querying:

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, such as a pipehanger attachment, or an ancillary item related to, but not an inherent 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 Neutral Axis of theSCTN at a point defined by the ZDIST attribute (in the same way as for a SNOD). TheFitting may be geometrically modelled in the Catalogue, and selected from the Catalogue, ina similar way to a Joint, as described in Creating and Positioning Joints.

Q LINKS Queries connection references between vertices

12.02 5:33


A Panel Fitting (PFIT) element serves a similar function to a FITT, but is owned by a Paneland positioned relative to the Panel’s origin. A Cofitting (COFI) element is used where afitting spans the junction betwen two or more Panels. In the latter case, one of the Panelsowns a PFIT while the others each own a COFI. Each COFI has its Panel FittingReference (PFRE) attribute set to point to the associated PFIT; the PFIT has its CofittingReference Array (CFRA) attribute set to point to the COFIs.

5.11.2 Structure-to-Pipework ConnectionsPiping models may be linked logically to the Structural model by means of cross-referencesbetween the Connection Reference (CREF) attribute of a Fitting on the Structure and theHead or Tail Reference (HREF/TREF) of a Hanger on the Pipework. A Fitting may beregarded, therefore, as the Structural equivalent of an Attachment Point (ATTA) in Pipeworkdesign.

For connection type compatibility, the Connection Type attribute (CTYA) of the Fitting mustmatch the Connection Type (HCON/TCON) of the Hanger.

5.11.3 Structure-to-Equipment ConnectionsEquipment models may be linked logically to the Structural model by means of cross-references between the Connection Reference (CREF) attribute of a Fitting on the Structureand the Connection Reference (CREF) of a Load Point (LOAP) element owned by theEquipment.

A Load Point has a position within the Equipment model, but no size or orientation. Itbehaves in this respect like a Node in the Structural model. If an Equipment is moved, anymember Load Points which point to Fittings in a Structure will not move, their positions beingconstrained by the attached Structure.

5.12 DESIGN, Owning and Attached Parameters

5.12.1 Setting DESIGN Parameters

Keywords:

DESPARAMETERS

Description:

DESIGN parameters (DESP) are array-type attributes of any element which has aSpecification Reference (Sections, Joints, Fittings etc.), each of which may store up to 100real values. They may be used to transfer design data to a corresponding Cataloguecomponent, or to a component’s attached or owning design element.

As an example, this enables one or more dimensions of a Joint to be derived from thedimensions of the Section(s) to which it is attached, rather than from preset dimensionsdefined for it in the Catalogue.

A DESP is referenced in the design by its numbered position in the array. Its value must beset before the corresponding component is selected from the Catalogue, so that therequired setting is available within the design.

12.02 5:34


Note: In the last example, a range of three design parameters, needed to hold the co-ordinates of the defined point, was set automatically, starting with the specified thirdparameter.

Command Syntax:

Setting parameters in default order in the array, starting at parameter number 1:.--------------<------------.

/ |>-- 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 -----+--->

Example:

DESP 2.5 7 Sets first two design parameters to 2.5 and 7respectively.

DESP N3 -5.5 Sets third design parameter to -5.5.

DESP N3 POSS OF /SCTN1 Sets design parameters 3, 4 and 5 to X,Y,Zcoordinates (respectively) of POSS of element /SCTN1.

12.02 5:35


Querying Examples:

5.12.2 Setting Owning and Attached ParametersOwning and attached parameters (OPAR and APAR, respectively) are real-array attributesof Joints. They are set in the Catalogue, and allow the Joint to derive data (usuallydimensions) from its owning or attached Section(s) when it is introduced into the design.See the Catalogues and Specifications User Guide for details about the setting of thesearrays.

As with the design parameters described in Setting DESIGN Parameters, an OPAR orAPAR is referenced in the design by means of its numbered position in the correspondingarray.

5.13 Representing Curved Beams and Walls

5.13.1 Overview

Curved structural items are represented by Generic Section (GENSEC) elements, thegeometry of which is defined by sweeping a 2D catalogue profile along a path. This path isrepresented by a Spine element, owned by the GENSEC, whose route is specified in termsof a sequence of member Spine Points (POINSP) and, optionally, Curves. For example:

There are six types of Curve, defined by setting the CURTYP (Curve Type) attribute, whichgovern the way in which the shape of the curve is specified.

The options are:

LINEA straight line (this is the default)

Q DESP 1 DESP 3 Outputs values of design parameters 1 and 3.

Q DESP Outputs values of all design parameters.

Q (WDESP[1]) Extracts a word from within DESP 1.

FINCH DIST Q (DDESP[2]) Extracts a distance (in feet and inches) from withinDESP 2.

= SPINE

= POINSPStart POINSP

End POINSP

PROFILE

CURVE

CURVE

12.02 5:36


RADIA circular arc, defined by a radius and a conditioning point.

THRUAn arc passing through a specified through-point position.

BULGAn arc defined by a bulge factor and a conditioning point.

FILLA fillet arc and two adjacent straights, defined by a radius and a pole position.

CENTA fillet arc and two adjacent straights, defined by a circle centre point, a radius and aconditioning point.

A Spine with only two POINSP members behaves in a similar way to a linear Section(SCTN). The first POINSP owned by the Spine defines its start position (equivalent to thePOSS of the Section); the last POINSP defines its end position (equivalent to the POSE ofthe Section).

Items connected to a GENSEC are positioned and orientated relative to a set of p-lineswhich follow the same path as that defined by the GENSEC’s Spine; that is, the p-lines maybe curved. These p-lines are referenced by attached items via Justification Line Datum(JLDATUM) and P-line Datum (PLDATUM) elements, which define the frames of referenceto be used for positioning and orientating the attached items relative to the parent GENSEC.

Fittings and joints are represented by generic Fixing (FIXING) elements, the geometry ofwhich is defined by reference to catalogue items. Fixings can own other Fixings, so thatalthough they behave somewhat like the more restrictive Fitting and Joint elements, theyare more versatile for representing compound fittings and joints.

5.13.2 Defining a Generic Section

Keywords:

GENSEC SPINE POINSP CURVE

Description:

Each GENSEC, representing a linear or curved beam or wall, must own a Spine defining itsshape. The Spine must own at least two Spine Points, defining its start and end positions. Itcan also own intermediate Spine Points and Curves to give a non-linear configuration.

Example:

NEW GENSEC Creates GENSEC with no defined geometry.

SPREF /203X203X55KG.UB Sets SpecRef of GENSEC to point to catalogueprofile. GENSEC now has defined cross-section,but no geometry defining its path.

NEW SPINE Creates Spine with no defined path.

12.02 5:37


5.13.3 More About Curve TypesThe ways in which the various types of Curve are specified are as follows:

• CURTYP = LINESpecifies a straight line between the adjacent POINSPs. This is the default if curvedgeometry is not defined between two POINSP elements.

• CURTYP = RADISpecifies a single circular arc between adjacent POINSP elements. The arc is definedby the RADI (radius) and CPOS (conditioning point) attributes. The conditioning pointand the preceding and following points define the plane of the arc. The choice of minoror major arc is governed by the arc which approaches closest to the conditioning point.If RADS = false, the specified radius is ignored and the minimum radius is calculatedsuch that the curve is a semicircle between the adjacent POINSPs.

• CURTYP = THRUSpecifies a single circular arc. The arc is defined by the POS attribute, which isinterpreted as a through-point on the curve. The through-point and the preceding andfollowing points define the plane of the arc.

• CURTYP = BULGSpecifies a single circular arc. The arc is defined by the BULG (bulge factor) and CPOS(conditioning point) attributes. The conditioning point and the preceding and followingpoints define the plane of the arc. The choice of minor or major arc is governed by thesize of the bulge factor. The sign of the bulge factor determines whether the arc curvestowards the conditioning point (positive bulge factor) or away from the conditioningpoint (negative bulge factor).

• CURTYP = FILLSpecifies a combination of an arc and up to two straights. The curve is defined by theRADI (radius) and POS attributes, where the POS setting is interpreted as the polepoint of the arc (the intersection of the two end tangents). The pole point and thepreceding and following points define the plane of the arc. If RADS = false, thespecified radius is ignored and the maximum radius that will fit into the pole iscalculated; an endpoint triangle ensures that the fillet terminates on at least one of theend points.

• CURTYP = CENTSpecifies a combination of an arc and up to two straights. The curve is defined by theRADI (radius), CPOS (conditioning point) and POS attributes, where the POS setting isinterpreted as the circle centre point. The centre point and the preceding and followingpoints define the plane of the arc. The choice of minor or major arc is governed by thearc which approaches closest to the conditioning point; the conditioning point need notlie in the plane of the arc. If RADS = false, the specified radius is ignored and themaximum radius is calculated to ensure that the nearest POINSP to the circle lies onthe circle; the arc terminates on this point.

NEW POINSP First Spine Point defines Start Position (POSS).

NEW POINSP Last Spine Point defines End Position (POSE).Spine at this stage is a straight line.

NEW CURVE(Created between POINSPs)

The attributes of this curve determine the shape ofthe Spine path between the adjacent POINSPs.(See More About Curve Types.)

Example:

12.02 5:38


Note: Displayed GENSECs treat each segment of the Spine as a separate extrusion. At thevertices between segments, i.e. at the POINSP positions, these extrusions mergetogether if there is a tangent continuity. If there is a tangent discontinuity, theextrusions are mitred 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 SectionsP-lines defined in the Pointset of the Section Profile (as referenced by the SpecRef) followthe path defined by the GENSEC’s Spine. This means that, for a curved GENSEC, the p-linedirections are not constant over their lengths. This must be taken into consideration whenusing them as datums referenced by attached items.

The command syntax used for referencing p-lines for SCTNs, as detailed in Positioning andOrientating Using P-lines, is extended when applied to GENSECS. The additional commandoptions available are summarised here.

Positions Derived From P-lines (see Positioning by Using P-lines):

The distance value along the p-line may be preceded by the keyword DISTANCE. Forexample:

PPLINE TOS DISTANCE distance FROM END ...

The position along the p-line may be measured from the plane normal to the end of theGENSEC, from the cutback plane, or from the joint end preparation cutback. 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 the same time. Forexample:

PPLINE TOS PROPORTION value DISTANCE distance ...

Positions may be measured along the actual p-line specified, or along the Spine and thenprojected 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. This redefinesthe element to be the GENSEC owning the POINSP or CURVE, rather than the currentelement or an element defined with the p-line choice. This sets:

• the direction along which DISTANCE and PROPORTION are to be measured;• in the case of a CURVE, the POINSP to be used as the origin from which DISTANCE

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 the start of theGENSEC.

12.02 5:39


Directions and Offsets Derived From P-lines (see Orientating by Using P-lines):

Directions and offsets derived from p-lines can have a derived position inserted after thedirection/offset option and before the OF option. This lets you specify the position along thep-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 the GENSEC orelement 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 a probe line:

PPLINE pline_name NORMAL/CUTBACK NEAR direction THROUGH position [VIA SPINE/PLINE] BOUND/UNBOUND

The probe line starts at the THROUGH position and extends in the specified direction. Theexpression 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 it intersects theNORMAL or CUTBACK end of the GENSEC). If UNBOUND is set, the point can be on thetangential extension of the p-line.

The point returned will be in or above the plane through the THROUGH position, normal tothe probe line; that is, the point will not be behind the THROUGH position.

The VIA SPINE/PLINE option is used if the point is to be returned with its distance along thep-line from the start of the segment.

If pline_name is specified as ANY, all plines of the GENSEC will be probed and the closestp-line will be used.

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 segment on which thespecified position occurs. ID ONPLINE returns the identity of the p-line on which thespecified position occurs. (The latter is only useful for the PPLINE ANY option, otherwise itsimply returns the identity of the specified p-line.)

The following expressions use keywords analogous to the OFFSET option between 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 segment and p-line,respectively, on which the point is specified. PPLINE...PLDIST returns the distance alongthe segment on which the point lies, in the direction specified in the positioning_command(FROM START or FROM END). PPLINE...PLKEY returns the name (the PKEY) of the p-lineon which the point lies.

12.02 5:40


5.13.5 Positioning Items Relative to Generic SectionsA GENSEC cannot own Fixings directly, but only via member Justification Line Datum andP-line Datum elements which together define the p-line configurations to be used asreferences for positioning and orientating the Fixings.

The Justification Line Datum (JLDATUM) element defines a frame of reference for itsmembers based on the p-line system of its owning GENSEC. Each JLDATUM can own a setof P-line Datum (PLDATUM) elements, each of which defines a frame of reference for itsmembers based on a nominated p-line of its owning JLDATUM. By manipulating aJLDATUM, all of its member PLDATUMs can be manipulated as a group, together with anyFixings owned by the latter.

Note: The JLDATUM and PLDATUM elements together serve similar functions to theSecondary Nodes (SNOD) used for positioning Fittings (FITT), Compound Fittings(CMFI), Secondary Joints (SJOI) and Compound Secondary Joints (SCOJ) relativeto Sections (SCTN). They also provide similar functions to those used for positioningPanel Fittings (PFIT) and Compound Panel Fittings (CMPF), depending on theGENSEC configuration (remember that a GENSEC can model a wide range ofgeometries, including structural sections and panels).

Specifying Position:

The position of a JLDATUM origin may be queried via a pseudo-attribute (Q POS), but thiscannot be set explicitly. The position is derived from the following attribute settings:

• TPREF and HPREF specify, by reference to POINSPs of the parent GENSEC (morestrictly, its Spine), the start and end points, respect-ively, between which interpolatedpositions will be calculated. If both are unset, TPREF defaults to start of the GENSECand HPREF defaults to the end of the GENSEC. If only one is set, the other defaults tothe next POINSP in the appropriate direction.

• PKDI specifies a point, as a proportion of the distance from TPREF to HPREF, fromwhich ZDIST is to be measured. The default setting is 0, giving a position at TPREF. IfPKDI is less than 0 or greater than 1, the position will be on the preceding or followingsegment, respectively, of the Spine.

• ZDIST specifies the distance of the JLDATUM origin from the PKDI point, as measuredalong the Justification Line (JUSL) or NA p-line of the GENSEC.

Specifying Orientation:

The orientation of a JLDATUM may be queried via a pseudo-attribute (Q ORI), but thiscannot be set explicitly. The orientation is such that its Z axis is in the direction of the Spine(i.e. the NA p-line) at the POS. The Y axis is in the Y direction (YDIR) of the Spine, modifiedby the Beta Angle (BANG) setting, at the POS.

= Spine of GENSEC= POINSP

PKDI=0 PKDI=0.5 PKDI=1

ZDIST

= JLDATUM Position

TPREF HPREF

for PKDI=0.5

12.02 5:41


5.13.6 Generic Fixings Representing Joints and FittingsA Fixing can represent any type of joint or fitting attached to a Generic Section. It can ownother Fixings, so that it can also represent compound joints and fittings. Its geometry isdefined by a reference to a parameterised Catalogue item in the usual way.

The position and orientation of a Fixing attached (indirectly) to a GENSEC are specified byreference to the coordinate systems of the parent PLDATUM and JLDATUM. These can beset relative to any POINSP under the GENSEC, including a POINSP which has beenspecially inserted for this purpose if necessary, as summarised in Positioning Items Relativeto Generic Sections. The default position and orientation of the Fixing relative to its owningPLDATUM are specified by its POS and ORI attributes, respectively.

Fixings Representing Joints:

The detailed position of a Fixing whose SPREF attribute points to a Catalogue Joint isspecified using the Joining Line attributes of the owning and attached sections: JLNS (start)and JLNE (end). The JNLS/JNLE are related to the origin and orientation of the joint; if theattached GENSEC is curved, these p-lines are taken as parallel to the attached end of theGENSEC. When connected, 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) or JOIE (end)attribute set to reference the Fixing; conversely, the CREF (Connection Reference) attributeof the Fixing will reference the attached GENSEC. This two-way cross-reference is usedwhen either the Fixing or the GENSEC is modified, or when a CONNECT command is used.

5.14 Representing Building ComponentsThe elements used to represent structural steelwork designs can also be used to representthe components involved in building design; for example, walls, floors, floor screeds, doors,windows, etc. It is recommended that such elements are created by using the DESIGNWalls & Floors applicationware rather than from the command line, since this will ensurethat all relevant attributes are set in a consistent way, but the options are summarised in thissection for reference purposes.

5.14.1 Using Element Soft TypesTo distinguish the elements used for building representation rather than for other types ofstructural design, element soft types are used. These are elements which have the sameattributes as standard (hard type) elements, but which have different names to identify theirfunctions.

The soft types used for building design are as follows:

Compound Wall (CWALL): a soft type of Subframework (SBFR), used to hold one or more wall componentsrepresenting, say, one storey of a multi-storey building.

Compound Floor (CFLOOR): a soft type of Subframework (SBFR), used to hold one or more floor componentsrepresenting, say, one storey of a multi-storey building.

12.02 5:42


Compound Screed (CSCREED): a soft type of Subframework (SBFR), used to hold one or more screed componentsrepresenting, say, one storey of a multi-storey building.

Straight Wall (STWALL): a soft type of Section (SCTN), used to represent a wall created by extruding a 2Dcatalogue profile from a start position to an end position.

[Curved] Wall (WALL): a soft type of Generic Section (GENSEC). This can, in principle, be used to representany shape of wall created by extruding a 2D catalogue profile along a path defined bya Spine. The Walls & Floors application for Version 11.3 restricts the use of thiselement to the representation of a Ring Wall, for which the Spine path is all or part ofa circle.

General Wall (GWALL): a soft type of a Panel (PANE), used to represent a wall 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, to represent a column, where the 2Dshape of the column's cross-section is extruded vertically to the required columnheight.

Wall and Floor Fittings, such as doors, windows, manholes etc., can be represented byCompound Fittings (CMPF), Sub-Compound Fittings (SBFI), Fittings (FITT), PanelFittings (PFIT) or Fixings (FIXI) in the usual way.

5.14.2 Controlling Edge Representation in DRAFTWhen you plot walls and floors in DRAFT, you may want to remove the lines whichrepresent common edges between such elements (referred to as 'unioning' the elements) togive a more realistic appearance. The elements used to represent buildings have anattribute specifically for this purpose: the DRAFT Union (DUNION) attribute.

The elements to which this attribute 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 a pair ofsuch elements are both members of a common parent, in which case the edge lineswill be removed.

DUNION=2 Common edges not shown between members and peersCommon edges between adjoining elements will be drawn in DRAFT unless a pair ofsuch elements are either both members of a common owner or are at the samehierarchic level with a common parent, in which cases the edge lines will be removed.

In the simplest cases, the effects are as shown in the following diagram:

12.02 5:43


The overall effect in DRAFT is determined by the composite effects of the settings for allsignificant elements (i.e. all elements which have a DUNION attribute) above those beingdrawn. For example:

When DUNION = 0, all members of the current element will be 'assembled' together ratherthan 'unioned': joint lines will therefore be shown between touching members (e.g. betweenadjoining Panels).

When DUNION = 1 for a FRMW or SBFR (or equivalent soft types), all members will beunioned: joint lines between touching members (e.g. adjoining Panels) with the same ownerwill not be shown. The FRMW or SBFR will not itself be unioned with another FRMW orSBFR.

When DUNION = 1 for a ZONE, STRU or FRWM, all member STRUs, FRMWs and SBFRswith DUNION = 2 will be unioned. Thus, joint lines will not be shown between adjoiningPanels with different owners. The ZONE, STRU or FRMW will not itself be unioned withanother ZONE, STRU or FRMW.

When DUNION = 2 for any element, all members with DUNION = 2 will be unioned, and thecurrent element will also be unioned to others which share the same owner and which haveDUNION = 2 as long as the owner has DUNION = 1 or 2.

12.02 5:44

DESIGN Reference ManualDesign Templates

6 Design Templates

This chapter explains the concept of Design Templates, which let you create and storestandard design configurations for subsequent use, and the Design Datasets which hold theparameterised data settings for such templates.

6.1 ConceptsA design template is a set of design primitives, panels and nozzles that may be groupedtogether and then referenced from within another part of the Design database as though itwere a single item. In many ways, a design template behaves in a similar way to acatalogue component, except that the template items are stored in a special area of theDesign DB, rather than in a separate Catalogue DB, and they can use the more powerfulsets of primitives and parameterisation facilities available from within DESIGN. Unlike acatalogue component, 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 adesign template is instanced, the template contents are copied into the Design hierarchyand a reference is set to the original template definition. At this release version, a designtemplate may only be copied under a Panel Fitting, a Section Fitting or a Primary Joint. Adesign element cannot own more than one design template, nor can one design templateown another template.

Design templates may be parameterised to allow a single template definition to be used indifferent circumstances. The parameterisation facilities use Design Datasets to store namedparameters, which may then be referenced in geometric and p-point definitions. The valueassigned to a parameter can be defined in terms of a rule by using any of the standardPDMS expression syntax.

Note: The definition of Design Templates is likely to be done by the person who organisesPDMS Catalogue and Specification data in a company, while the use of DesignTemplates for building up a design model will be carried out by a plant designer.Therefore, although both functions are carried out in DESIGN, this chapter isrelevant to two different types of PDMS user.

6.2 Design Template HierarchyDesign Template (TMPL) elements are usually stored in a separate Design DB under anadministrative Template World (TPWL), which is itself divided into administrative TemplateAreas (TMAR).

Each TMPL is initially created as a copy of an existing set of design elements which havebeen created in a part of the usual hierarchy below a SITE. The TMPL may then be modified

12.02 6:1


by the addition of positive and/or negative primitives, negative extrusions, etc. For example,a very simple template, consisting of a positive box and a negative box, could be createdthus:

When this template is instanced in a design model, say under a panel fitting, its constituentelements are copied back and all parameterisation rules are executed so that the attributesof the copy are set to suit the local DESIGN requirements, thus:

All attributes of the copy are locked to prevent unintentional changes.

6.3 Application Data AreasApplication Data Areas and Elements are a new form of definition in the Design Databasethat are provided to assist Appware Applications to store model parts for copying andpropagation within a design. They have some similarities with Templates, but are moregeneral in content, and more restrictive in behaviour.

Application Data Areas and Elements are expected to be used for Piping Assemblies andPlatforms Stairs and Ladders (PSL) applications and perhaps others. They are alsoexpected to be used for storing Multi Discipline Supports (MDS) definitions to make themanagement of these more robust.

The Elements available are administrative elements allowing applications to organise datastorage areas of design objects that are not part of the design itself, but supplementaryobjects used to create and maintain the model. They will not be accessed (unlessspecifically instructed to do so) when performing model queries such as clashing, massproperties, collections etc. They are similar to catalogue definitions and to Templatedefinitions in particular.

World (/*)

SITE

ZONE

EQUI

BOX

NBOX

TPWL

TMAR

TMPL

BOX

NBOXCopy

PANE

PLOO

PAVEs

PFIT

TMPL

BOX

NBOX

TMAR

TMPL

BOX

NBOX

TPWL

Copy and Execute Rules

12.02 6:2


The top level element in the DESIGN database is Design WORL. This owns a top levelapplication data element

DDARs are existing element types. They own Design Data Sets (DDSE) for storage of dataused by Template expressions and Rules, and by Appware. They can be used for Appwareto store data, rules, etc for use in data driven instancing of assemblies.

The following diagram illustrates the relative positions of these elements in the DESIGNdatabase hierarchy:

APPLDWorld - Application Data World

APPLDW can own

APPDAReas - Application Data Areas

DDAR - Design Data Set Areas

APPDAR can own:

APPLDAta - Application Data. This is logically similar to a Template Definition.

APPLDA is a new element type. It can own

ZONE

DDSE - Design Dataset

DPSE - Design Pointset

ROOM

12.02 6:3


6.3.1 Functional QueriesEverything under the Application Data World (APPLDWorld) is treated in the same way thathierarchies under TMWL (Template Worlds) are. In particular, Clash checking on command,spatial mapping and auto clashing will be isolated from normal design data except whenspecifically queried within the APPLDWorld.

6.3.2 NamingNames in the APPLDWorld are in the same scope as the normal project model and soduplicate names will clash. This is not likely to be an issue as it is expected that applicationdata will be unnamed. It would become an issue if sections of 'real' model data are copied orincluded (moved) into the APPLDWorld.

APPLDA elements have a local name scope so that objects that the APPLDA owns canhave local names, allowing any Appware manager that manipulates Application Data toeasily identify elements within them in the same way that design templates (TMPLates) arehandled. Existing commands and expression functions such as LNAME, LNID etc operatewithin this scope.

6.3.3 Application Data and Templates A template (TMPLate) can be included in the Application Data World, but only as aninstanced template, NOT a template definition. Such templates can be refreshed from theirdefinitions using existing (appware and core) driven functions. However, there is no coresupported means to refresh copies of Application Data in the real model.

12.02 6:4


6.3.4 Extension to Design DataDDAT elements have a new attribute PTOLER that provides a tolerance value as analternative to the MAXMIN values which determine the range of valid values when set.Applications using the Application Data will use this value to validate its data.

6.3.5 Valid Value Elements Additional AttributeValid Value elements (VVALUE) owned by a DDAT can have a Valid Rule set stored in theattribute VALRULE. VALRULE is an expression attribute that can store an expression thatevaluates to a logical true or false value. If the expression does not evaluate to a logicalresult, or if there are errors in the evaluation of the expression, then the VALRULE will returnFALSE when queried. The VVALUE element owns a Valid Value attribute (VALIDV) that isan expression returning a real, logical, text or reference value which supports the owningDDAT element. If the VALRULE is true, or if it is a null expression, then this VALIDV will beavailable to the DDAT.

VALRULEs are used by the system to control the choice of a Valid Value when propertyqueries are made on the owning DDAT.

For example a DDAT element might own four VVALUE elements with VALIDV andVALRULE attributes as follows:

The current set of VALIDValues available for the owning DDAT are the set whoseVALRULEs either are unset, or evaluate to TRUE. Those that are not available are thosewhose VALRULEs either evaluate to FALSE, or whose evaluation generate errors.

6.3.6 Extension to Design Data Associated Pseudo AttributesLocal Design Data Set (DDSE) pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP(which up to release 12 only operated within the scope of the owner of a DDSE) now alsooperate at the DDSE level and within the scope of a DDSE:

VValue VALIDValue expression VALRULE expression

VVALUE 1 ( ID /ANG35x35x15 ) ( LDPR LENG le 1800 )

VVALUE 2 ( ID /ANG40x40x15 ) ( LDPR LENG gt 1800 and LDPR LENG le 2400 )

VVALUE 3 ( ID /ANG45x45x18 ) ( LDPR LENG gt 2400 and LDPR LENG le 3000 )

VVALUE 4 ( ID /ANG50x50x18 ) ( LDPR LENG gt 3000 )

Attribute Returns At Owner ofDDSE

At DDSE Below a DDSE(DDAT, VVALUE etc)

DEPL List ofProperty keys

Properties in allowned DDSE

Properties in thisDDSE

Properties in owningDDSE

LDPR Real value Property in anyowned DDSE

Property orDefault Propertyin any DDSEowned by ownerof DDSE

Property in anyDDSE owned byowner of owningDDSE

DEPR Text value fortext and reals

12.02 6:5


All attributes fail above the owner of the DDSE.

6.3.7 Special Design Data Property names in scope of a DDSEEach of the Local Design Data pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDPtake a qualifier that is the key to a particular design data element (the DKEY of the DDAT).Special values of this key are used to query values within the DDAT and VVALUE elements:

All of these properties will error if queried at the DDSE element or above.

If the Design Data set actually has a data element that has a property with one of thesename keys (they are not reserved in anyway) then the use of the key will operate normallyon the DDSE or its owner, and as listed in the table above on a DDAT or VVALUE.

Use of the VVAL key on a particular DDAT will return the first suitable value from a set ofmany values. This is similar to choosing from a set of values according to some criteria. It ispossible to use this as an alternative to the IFTRUE expression, which can, for examplewhen used iteratively, select a set of possible choices depending on a particular criterion.The IFTRUE expressions will increase the expression length with the possibility ofexceeding the maximum length of the text attribute. Use of VVAL key will not do this.

LFDP Referencevalue

DEPD Text defaultvalue for textand reals

Default Propertyin any ownedDDSE

Default Property inany DDSE owned byowner of DDSE

VALI: for returning evaluation of the VALIDV attribute of a VVALUE

VALR: for returning the evaluation of a VALRUL attribute of a VVALUE

VVAL: for returning a VALIDV/ALUE result with a true VALRULE

DDAT: for returning the value of the local DDAT (either a DPROPerty or else aDDEFAUlt without knowing its DKEY

element special key word

DDAT VVALUE

VALR ERROR, no VALRUL attribute result of evaluated VALRUL attribute

VALI ERROR, no VALIDV attribute result of evaluated VALIDV attribute

VVAL returns VVAL result of first VVALUEelement that does not ERROR,

returns result of evaluated VALIDV ifVALRUL evaluates TRUE, elseERROR

DDAT returns the same value as would bereturned using the DKEY of theDDAT. (Either the DPROPerty orDDEFAUlt value). This is aconvenient way of obtaining thisvalue without knowing the DKEY

Returns the same value as the DDATproperty of the owning DDAT withouthaving to know the actual DKEYvalue to use.

12.02 6:6


The VVALUEs owned by a DDAT DO NOT modify the return values of design dataproperties when queried by their owners.

It should be noted that if the DPROPerty of a DDAT is inconsistent with the set of VVALUEsthat it owns, this will NOT raise an exception or error when querying it directly using itsDKEY. It is up to the application using these data values to decide whether to accept thevalue of a DPROPerty whenever it conflicts with valid values, or maximum or minimumvalues, or a tolerance. To do otherwise would risk the integrity of existing user and systemapplications.

6.4 Parameterisation using Design DatasetsDesign Datasets (DDSE) are used to store the properties of design template items, whichmay then be used to define the template’s parameters. Each property is stored in a DesignData (DDAT) element under a DDSE, with each DDAT being identified by a keyword held inits DKEY attribute. The property definition can be specified by an expression held in theDDPR (Design Data Property) attribute, while a default value for the property (to be used ifthe expression cannot be evaluated for any reason) can be stored in the DDDF (DesignData Default) attribute.

Unlike a design reference to a catalogue component, which can access only a singlecatalogue dataset via its DTREF setting, a reference to a design template can access morethan one design dataset. A local design dataset is owned directly by the current element, atemplate design dataset is owned by the first template below the current element, while acurrent design dataset is at the same level as the current element and has the sameowner.

The following diagram illustrates the relative positions of these types of dataset for a simplehierarchy:

The pseudo-attributes available for accessing the properties data in the various types ofdataset are as follows:

PFIT

DDSE(1)TMPL

DDSE(2)BOX

local

template

local

current

current

12.02 6:7


Note: The dataset attributes PRLS, PROP and PRDE are also used to refer to cataloguedataset properties. If you query any of these attributes, a search for a cataloguedataset will be made first; if this fails, a search for a design template dataset will bemade.

Most commonly, a design attribute value will be defined in terms of a design property byusing the CDPR (Current Design Dataset Property) attribute. The CDPR can also be usedto define a property in one dataset in terms of a property in another dataset. When a CDPRis used in a rule for a component whose owner can own datasets, the current datasets willbe those at the same level as the component: otherwise, the current datasets will be thoseunder the first dataset-owning element above the component. When a CDPR is used in aproperty expression within a dataset, it refers to a property in the current dataset for the itemat which CDPR is evaluated.

When used in a querying command or in an expression (for example, when defining aparameterisation rule), the attributes for a specific property are identified by the DKEY forthat property. For example:

Note: Usually default values are assigned to properties, which are then used to evaluateexpressions during the creation of a design template. This lets you see the templategeometry in a graphical view, at a practical scale, as you define it. Thus a defaultvalue for LENG in the last example would allow a sensible XLEN dimension to beevaluated from the rule for display purposes. When instanced in a design, the valueof the LENG property would be derived from, say, a design parameter and the rulewould be re-executed to give the correct XLEN.

6.5 Assigning Local Names to Template ElementsWhen a design template is copied, confusion can arise in the identification of members ofthe template instance. If a template rule refers to an element by its hierarchic position (e.g.BOX 1 OF TMPL 1 OF ... etc.), rule execution errors can arise if the template instance ismodified in any way which affects the ordering of the members list. Even if the element has

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

Q CDPL Lists all DKEYs for properties in current dataset.

Q CDPR LENG Gives value of LENG property in current dataset.

RULE SET XLEN (CDPR LENG)

Sets rule for current element’s XLEN attribute using value fromLENG property in current dataset.

12.02 6:8


a PDMS name under 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 template member.Each local name, and the reference of the corresponding element, is stored in an arrayattribute of the template. Local names are therefore set and queried at member elementlevel, even though they are stored at template level. The local name survives a templatecopy operation.

6.5.1 Setting Local Names

Keywords:

LNAME

Description:

Lets you assign a local name to a template member, or unset an existing local name. A localname can have a maximum of 20 characters; a maximum of 500 local names can be storedon one template. The local name cannot be modified if either the element or its owningtemplate is locked.

Command Syntax:>--- LNAMe ---*--- local_name ---.

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

Querying:

6.5.2 Using Local Names in Expressions

Keywords:

LNID MLNID

Description:

Lets you identify an element by its local name in a rule or dataset expression.

Examples:

LNAME /ANTHONY Sets local name for current element

LNAME UNSET Unsets local name for current element

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)

12.02 6:9


Command Syntax:>---+--- LNid ----.

| |‘--- MLNid ---+--- local_name --->

Querying:

6.6 Setting Priorities for Evaluating RulesBy default, the rules for the member elements of a design template are executed indescending hierarchic order. If the rule for one member element includes a reference to theresult of a rule for another member, it is important that the latter rule is executed before theformer, otherwise an incorrect result will be obtained.

You can control the order in which the rules for a given template will be executed byassigning a rule sequence number to any element which has a local name. When thetemplate rules are re-executed, the rules for such elements will be executed in ascendingorder of their sequence numbers: the rules for elements with sequence numbers unset (orzero) will then be executed in the default order. Each rule sequence number, and thereference of the corresponding element, is stored in an array attribute of the template. Rulesequence numbers are therefore set and queried at member element level, even thoughthey are stored at template level.

Keywords:

RSEQNUMBER

Description:

Lets you assign a rule sequence number to any design template member which has a localname. The rule sequence number must be a positive integer (zero is equivalent to unset).The same sequence number may be assigned to more than one element, but this is notrecommended.

Example:

LNID /SID Identifies element defined in current template

MLNID /JOE Identifies element defined in member template (i.e. intemplate owned by current element)

(XLEN OF LNID /SID) Uses dimension of locally named element in expression(XLEN OF MLNID /JOE)

Q LNID /SID For element in current template

Q MLNID /JOE For element in member template

12.02 6:10


Command Syntax:>--- RSEQNumber ---+--- integer ---.

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

Querying:

6.7 Adding Design Points to Template ElementsThe design datasets for a template, as discussed in Parameterisation using DesignDatasets, approximate to the Geomset data for a catalogue component. In a similar way,design templates can also own Design Pointsets (DPSE), which approximate to thePointset data for a catalogue component. These let you assign p-points to design templateitems, to be used as references for subsequent positioning and orientating operations.

A design pointset can store three types of p-point (note that these are not the same as thoseavailable in catalogue pointsets):

• A Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:

• A Cylindrical P-point is specified as a position on the surface of a cylinder at a givenposition and with given dimensions, thus:

Examples:

RSEQN 3 Sets rule sequence number for current element (which must be amember of a design template and must already have a localname)

RSEQN UNSET Unsets rule sequence number for current element

Q RSEQN Gives sequence number for current element

Q RSEQA Lists sequence numbers for all elements under current template (inthe order 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

ZY

X

Origin

Orientation

Direction of Normal

DesignPoint

12.02 6:11


• A Spherical P-point is specified as a position on the surface of a sphere at a givenposition and with given dimensions, thus:

6.8 Using a Design Template Item in a DesignTo create an instance of a ‘source’ design template in a design model, you must first createa template below the owning design element and then copy into this the details of thesource template (which must be in a template world) from which it is to derive its data. Thecommands (at the design element which is to own the instance) are:

NEW TMPL COPY REXEcute template_identifier

where template_identifier is the name of the source template. The effects are as follows:• All elements below the original design template are copied below the new TMPL.• All template rules are copied and re-executed, thus setting the attributes of the new

TMPL members to suit the design data.• The Origin Reference (ORRF) attributes for the new TMPL elements are set to point to

their equivalents in the source template.• All elements below the new TMPL are locked to prevent unintentional changes to any

of their attributes.

If you want to change an attribute explicitly, thereby causing it to differ from the design asspecified in the source template, you must first unset the ORRF references which point backto 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 model hierarchy.

ZY

X

Origin

Orientation

Direction of Normal

DesignPoint

Cylinder defined by its position, height and radius

Angle defining point position wrt Y axis

ZY

X

Origin

Orientation

Direction of Normal

Design Point

Sphere defined by its position and radius

Direction radius acts in, defining point position wrt sphere's centre

12.02 6:12


6.9 Portsets and LinksetsIf you list the possible members of most types of design element, you will see two newelements called Portsets (PORS) and Linksets (LNKS). These have been added to thedatabase definition to permit future developments that will allow logical connections to bemade to items derived from design templates. They are not intended for general use at thisrelease version of PDMS.

12.02 6:13


12.02 6:14

Index


AALONG command . . . . . . . . . . . . . . . 2-2:31ARRIVE command . . . . . . . . . . . . . . 2-3:26AT command . . . . . . . . . . . . . . . . . . . . 2-2:5Attached parameters . . . . . . . . . . . . . 2-5:36Attributes:of primitives . . . . . . . . . . . . . 2-2:1Attributes:sections . . . . . . . . . . . . . . . . 2-5:4AUTOROUTE command . . . . . . . . . . . 2-4:1AXES command:pipe routing . . . . . . . 2-4:2

BBANGLE command . . . . . . . . . 2-5:6, 2-5:12BASE command:pipe routing . . . . . . . 2-4:6BEHIND command . . . 2-2:26, 2-3:7, 2-3:52Beta angle:joints . . . . . . . . . . . . . . . . 2-5:12Beta angle:sections . . . . . . . . . . . . . . . 2-5:6BOP command . . . . . . . . . . . . 2-3:7, 2-3:63BOP command:pipe routing . . . . . . . . 2-4:7Branch:head . . . . . . . . . . . . . . . . . . . . 2-3:2Branch:tail . . . . . . . . . . . . . . . . . . . . . . 2-3:2Buildings . . . . . . . . . . . . . . . . . . . . . . 2-5:42BUILT flag . . . . . . . . . . . . . . . . . . . . . 2-3:31BY command . . . . . . . . . . . . . . . . . . 2-2:15

CCDPR attribute . . . . . . . . . . . . . . . . . . 2-6:8CHOOSE command . . . . . . . . . . . . . 2-3:12CLEARANCE command . . . . 2-2:34, 2-3:59Cofitting element . . . . . . . . . . . . . . . . 2-5:34Cofitting Reference Array attribute . . 2-5:34Compound fitting element . . . . . . . . . . 2-5:2Compound Floor element . . . . . . . . . 2-5:42

Compound joint element . . . . . . . . . . .2-5:1Compound panel fitting element . . . . . 2-5:2Compound Screed element . . . . . . . . 2-5:43Compound Wall element . . . . . . . . . .2-5:42CONNECT command 2-2:14, 2-3:2, 2-3:39, 2-

5:17Connection:forced . . . . . . . . . . . . . . . 2-3:41CRFA attribute . . . . . . . . . . . . . . . . . .2-3:34CTYEND command . . . . . . . . . . . . . . . 2-5:8CTYSTART command . . . . . . . . . . . . .2-5:8Current design dataset . . . . . . . . . . . . .2-6:7Current Design Dataset Property attribute 2-6:8CURTYP attribute . . . . . . . . .2-5:36, 2-5:38Curve element . . . . . . . . . . . . . . . . . .2-5:36Curve Type attribute . . . . . . . .2-5:36, 2-5:38CUTBACK command . . . . . . . . . . . . . 2-5:16CUTPLANE command . . . . . . . . . . . .2-5:16

DDDAT element . . . . . . . . . . . . . . . . . . .2-6:7DDDF attribute . . . . . . . . . . . . . . . . . . .2-6:7DDPR attribute . . . . . . . . . . . . . . . . . . .2-6:7DDSE element . . . . . . . . . . . . . . . . . . .2-6:7DELPOSITION command . . . . . . . . . 2-5:12Design Data Default attribute . . . . . . . .2-6:7Design Data element . . . . . . . . . . . . . .2-6:7Design Data Property attribute . . . . . . . 2-6:7Design Dataset element . . . . . . . . . . . . 2-6:7Design parameters . . . . . . . . . . . . . . .2-5:34Design Pointset element . . . . . . . . . .2-6:11Design Template element . . . . . . . . . . 2-6:1DESPARAMETER command . . . . . . .2-5:34Detail level . . . . . . . . . . . . . . . . . . . . . .2-2:3

12.0Index page 1


DIRECTION command . . . . . . . . . . . 2-3:37DISCONNECT command . . . . . . . . . 2-5:18DISTANCE command . . . . . . 2-3:44, 2-3:48DKEY attribute . . . . . . . . . . . . . . . . . . 2-6:7DPSE element . . . . . . . . . . . . . . . . . 2-6:11DRAFT Union attribute . . . . . . . . . . . 2-5:43DRAG command . . . . . . . . . . . . . . . . 2-3:68DRNEND command . . . . . . . . . . . . . . 2-5:6DRNSTART command . . . . . . . . . . . . 2-5:6DUNION attribute . . . . . . . . . . . . . . . 2-5:43

EEdge drawing in DRAFT . . . . . . . . . . 2-5:43Elements:connecting . . . . . . . . . . . . . 2-2:14Elements:moving . . . . . . . . . . . . . . . 2-2:15Elements:orientating . . . . . . . . . . . . . 2-2:10Elements:rotating . . . . . . . . . . . . . . . 2-2:12End position (section) . . . 2-5:4, 2-5:5, 2-5:9ERELEASE command . . . . . . . . . . . . 2-5:8EXTEND command . . . . . . . . . . . . . . 2-5:22

FFCONNECT command . . . . . . . . . . . 2-3:41Fitting element . . . . . . . . . . . . 2-5:1, 2-5:33Fitting element:compound . . . . . . . . . . 2-5:2Fitting element:panel . . . . . . . . . . . . . . 2-5:1Fixing element . . . . . . . 2-5:2, 2-5:37, 2-5:42FLIP command . . . . . . . . . . . 2-3:27, 2-5:20Floors . . . . . . . . . . . . . . . . . . . . . . . . 2-5:42FORCECONNECT command . . . . . . 2-3:12Forced connection . . . . . . . . . . . . . . 2-3:41FROM command . . . . . . . . . . . . . . . . 2-3:48

GGeneric Fixing element . . . . . . . . . . . 2-5:42Generic Section element . . . . . 2-5:2, 2-5:36GENSEC element . . . . . . . . . . 2-5:2, 2-5:36#106 . . . . . . . . . . . . . . . . . . . 2-6:11, 2-6:12plin . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5:26

HHBOR command . . . . . . . . . . . . . . . . . 2-3:5HCON command . . . . . . . . . . . . . . . . . 2-3:5HDIR command . . . . . . . . . . . . . . . . . 2-3:5Head of branch . . . . . . . . . . . . . . . . . . 2-3:2HPOS command . . . . . . . . . . . . . . . . . 2-3:5HREF command . . . . . . . . . . . . . . . . . 2-3:4HSPE command . . . . . . . . . . . . . . . . . 2-3:2HSROD attribute . . . . . . . . . . . . . . . . 2-3:29HSTUBE attribute . . . . . . . . . . . . . . . 2-3:29

IIDPLINE command . . . . . . . . . . . . . . 2-5:26INFRONT command . 2-2:26, 2-3:7, 2-3:52Instance:Design templates . . . . . . . . . . 2-6:1Insulation specification . . . . . . . . . . . .2-3:30ISPEC attribute . . . . . . . . . . . . . . . . . 2-3:30

JJLDATUM element . . . . . . . . .2-5:37, 2-5:41JOIEND command . . . . . . . . . . . . . . . .2-5:7Joint element:compound . . . . . . . . . . .2-5:1Joint element:linear . . . . . . . . . . . . . . . 2-5:1Joint element:primary . . . . . . . .2-5:1, 2-5:11Joint element:secondary . . . . .2-5:1, 2-5:11Joint:creating . . . . . . . . . . . . . . . . . . . 2-5:10Joints:attributes . . . . . . . . . . . . . . . . . 2-5:15Joints:linear . . . . . . . . . . . . . . . . . . . . 2-5:31Joints:primary . . . . . . . . . . . . . . . . . . . 2-5:12Joints:secondary . . . . . . . . . . . . . . . .2-5:13JOISTART command . . . . . . . . . . . . . . 2-5:7Justification Line Datum element 2-5:37, 2-5:41

LLEAVE command . . . . . . . . . . . . . . . . 2-3:26LEVEL command . . . . . . . . . . . . . . . . . 2-2:3Linear joint element . . . . . . . . . . . . . . . 2-5:1Linear joints . . . . . . . . . . . . . . . . . . . . 2-5:31LINK command . . . . . . . . . . . . . . . . . 2-5:31LNAME . . . . . . . . . . . . . . . . . . . . . . . . . 2-6:9LNID . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6:9Local design dataset . . . . . . . . . . . . . .2-6:7Local name:Design templates . . . . . . . 2-6:9LOFF attribute . . . . . . . . . . . . . . . . . .2-3:33LSROD attribute . . . . . . . . . . . . . . . . .2-3:29LSTUBE attribute . . . . . . . . . . . . . . . . 2-3:29 2-5:26Cartesian p . . . . . . . . . . . . . . . . . . . . . 2-6:11Cylindrical p . . . . . . . . . . . . . . . . . . . . 2-6:11Spherical p . . . . . . . . . . . . . . . . . . . . . 2-6:12

MMIRROR command . . . . . . . . . . . . . . 2-2:43MLNID . . . . . . . . . . . . . . . . . . . . . . . . .2-6:9MOVE command . . . . 2-2:16, 2-3:9, 2-3:42

NNode element:primary . . . . . . . . . . . . . 2-5:1Node element:secondary . . . . . . . . . . .2-5:1Nodes:primary . . . . . . . . . . . . . . . . . . .2-5:2

12.0Index page 2


Nodes:secondary . . . . . . . . . . . . . . . . 2-5:9Nozzle offset factor:pipe routing . . . . . 2-4:4Nozzles:specifying . . . . . . . . . . . . . . . 2-2:2

OOBSTRUCTION command . . . . . . . . . 2-2:4Obstruction level:clash detection . . . . 2-2:4OFFSETFACTOR command . . . . . . . 2-4:4ONTOP command . . . 2-2:28, 2-3:7, 2-3:55OPDIRECTION command . . . . . . . . 2-5:12ORDER command:pipe routing . . . . . 2-4:8ORIENTATE command . . . . . 2-2:10, 2-3:35Orientation . . . . . . . . . . . . . . . . . . . . 2-2:10ORIFLAG attribute . . . . . . . . . . . . . . 2-3:32Owning parameters . . . . . . . . . . . . . . 2-5:36

PPanel Fitting element . . . . . . . 2-5:1, 2-5:34Panel fitting element:compound . . . . . 2-5:2Panel Fitting Reference attribute . . . 2-5:34Panel Loop element . . . . . . . . . . . . . . 2-5:1Panel Vertex element . . . . . . . . . . . . . 2-5:1Panels:connecting . . . . . . . . . . . . . . . 2-5:31Panels:creating . . . . . . . . . . . . . . . . . 2-5:29Panels:splitting . . . . . . . . . . . . . . . . . 2-5:30Parameters:attached . . . . . . . . . . . . . 2-5:36Parameters:design . . . . . . . . . . . . . . 2-5:34Parameters:owning . . . . . . . . . . . . . . 2-5:36Penalty volume:pipe routing . . . 2-4:2, 2-4:3PH command . . . . . . . . . . . . . . . . . . . 2-3:6Pipe rack:pipe routing . . . . . . . . . . . . . 2-4:5Pipe routing . . . . . . . . . . . . . . . . . . . . . 2-4:1PJOINT command . . . . . . . . . . . . . . 2-5:11PLDATUM element . . . . . . . . 2-5:37, 2-5:41Pline Datum element . . . . . . . 2-5:37, 2-5:41PNODE command . . . . . . . . . . . . . . . 2-5:2POINSP element . . . . . . . . . . . . . . . . 2-5:36point:in design pointset . . . . . 2-6:11, 2-6:12POLAR command . . . . . . . . . . . . . . . . 2-2:8Polar positioning . . . . . . . . . . . . . . . . . 2-2:8POSEND command . . . . . . . . . . . . . . 2-5:5POSFLAG attribute . . . . . . . . . . . . . . 2-3:32POSITION command . . . . . . . 2-2:5, 2-3:44Positioning . . . . . . . . . . . . . . . . . . . . . 2-2:5POSLINE command . . . . . . . . . . . . . 2-5:13POSSTART command . . . . . . . . . . . . 2-5:5PPLINE command . . . . . . . . . . . . . . 2-5:26Primitives:attributes . . . . . . . . . . . . . . . 2-2:1Profile element . . . . . . . . . . . . . 2-5:1, 2-5:4PSPE command . . . . . . . . . . . . . . . . . 2-3:2PT command . . . . . . . . . . . . . . . . . . . . 2-3:6PVOL command . . . . . . . . . . . . . . . . . 2-4:3

RRACK command . . . . . . . . . . . . . . . . .2-4:5RECONNECT command . . . .2-3:11, 2-5:19RESELECT command . . . . . . . . . . . .2-3:22Ring Wall element . . . . . . . . . . . . . . . 2-5:43Rod:attributes . . . . . . . . . . . . . . . . . . . 2-3:29ROTATE command . . . . . . . . . . . . . . 2-2:12ROUTE command . . . . . . . . . . . . . . . . 2-4:4Routing plane:pipe routing . . . . .2-4:2, 2-4:3RPLANE command . . . . . . . . . . . . . . . 2-4:3RSEQNUMBER . . . . . . . . . . . . . . . . .2-6:10Rule sequence number:Design templates 2-

6:10

SScreeds . . . . . . . . . . . . . . . . . . . . . . .2-5:42SDIR command:pipe routing . . . . . . . . 2-4:6Sections:attributes . . . . . . . . . . . . . . . . 2-5:4Sections:connecting . . . . . . . . . . . . . . 2-5:17Sections:creating . . . . . . . . . . . . . . . . .2-5:3Sections:disconnecting . . . . . . . . . . . 2-5:18Sections:modifying lengths . . . . . . . .2-5:22Sections:reconnecting . . . . . . . . . . . . 2-5:19SELECT command . . . . . . . . . . . . . . 2-3:17SHOP flag . . . . . . . . . . . . . . . . . . . . .2-3:31SHORTCODE command . . . . . . . . . .2-3:21SJOINT command . . . . . . . . . . . . . . . 2-5:11SNODE command . . . . . . . . . . . . . . . . 2-5:9Soft types . . . . . . . . . . . . . . . . . . . . . . 2-5:42Spine element . . . . . . . . . . . . .2-5:2, 2-5:36Spine Point element . . . . . . . . . . . . . . 2-5:36SPLIT command . . . . . . . . . . . . . . . .2-5:30SPREAD command:pipe routing . . . . . 2-4:7SPREF attribute . . . . . . . . . . . . . . . . .2-3:28SRELEASE command . . . . . . . . . . . . .2-5:8Start position (section) . . . . . . . .2-5:4, 2-5:5Steelwork:fittings . . . . . . . . . . . . . . . . .2-5:1Steelwork:fixings . . . . . . . . . . . . . . . . .2-5:2Steelwork:generic sections . . . . . . . . .2-5:2Steelwork:joints . . . . . . . . . . . . . . . . . . 2-5:1Steelwork:nodes . . . . . . . . . . . . . . . . . .2-5:1Steelwork:panels . . . . . . . . . . . . . . . . .2-5:1Steelwork:sections . . . . . . . . . . . . . . . .2-5:1Straight Wall element . . . . . . . . . . . . . 2-5:43STRING command . . . . . . . . . . . . . . . .2-5:3Subfitting element . . . . . . . . . . . . . . . . 2-5:2Subjoint element . . . . . . . . . . . . . . . . .2-5:1syntax . . . . . . . . . . . . . . . . . . . . . . . . .2-5:26

TTail of branch . . . . . . . . . . . . . . . . . . . . 2-3:2

12.0Index page 3


TBOR command . . . . . . . . . . . . . . . . . 2-3:5TCON command . . . . . . . . . . . . . . . . . 2-3:5TDIR command . . . . . . . . . . . . . . . . . . 2-3:5Template Area element . . . . . . . . . . . . 2-6:1Template design dataset . . . . . . . . . . . 2-6:7Template World element . . . . . . . . . . . 2-6:1THROUGH command . . . . . . . . . . . . 2-3:46TMAR element . . . . . . . . . . . . . . . . . . 2-6:1TMPL element . . . . . . . . . . . . . . . . . . . 2-6:1TO command . . . . . . . . . . . . . . . . . . 2-3:48TOP command . . . . . . . . . . . . 2-3:7, 2-3:63TPOS command . . . . . . . . . . . . . . . . . 2-3:5TPWL element . . . . . . . . . . . . . . . . . . 2-6:1Trace specification . . . . . . . . . . . . . . 2-3:31TREF command . . . . . . . . . . . . . . . . . 2-3:4TSPE attribute . . . . . . . . . . . . . . . . . . 2-3:31Tube:attributes . . . . . . . . . . . . . . . . . 2-3:29

UUNDER command . . . 2-2:28, 2-3:7, 2-3:55Unioning drawn elements in DRAFT . 2-5:43UNLINK command . . . . . . . . . . . . . . 2-5:31UNTIE . . . . . . . . . . . . . . . . . . . . . . . . 2-6:12

WWall element . . . . . . . . . . . . . . . . . . . 2-5:43Walls . . . . . . . . . . . . . . . . . . . . . . . . . 2-5:42

ZZDISTANCE command . . . . . . . . . . . . 2-5:9

12.0Index page 4

Design Reference Manual - Creating the Model

Documents