Design Reference Manual - Creating the Model

Design Reference Manual Creating the Model

AVEVA Sol ut io n s L t d

Disclaimer Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim any 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 or entity 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.

Copyright Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to AVEVA AVEVA Solutions Ltd or its subsidiaries. All other rights are reserved to AVEV VEVA A Solutions Ltd and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product 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 by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms and conditions of the respective license agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published September 2007 © AVEVA AVEVA Solutions Ltd, and its subsidiaries AVEV AVEVA A Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks AVEV AVEVA A and Tribon are registered trademarks of AVEVA AVEVA Solutions Ltd or its subsidiaries. Unauthorised use of the AVEV VEVA A or Tribon trademarks is strictly forbidden. AVEV AVEVA A product names are trademarks or registered trademarks of AVEV VEVA A Solutions Ltd or its subsidiaries, 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 or logo belongs to its respective owner.

DESIGN DESIGN Refer Referenc ence e Manual

DESIGN Reference Manual

Co n t en t s

Pag e

Creatin Creating g the th e Model Intr oduc od ucti tion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Ab ou t t he DESIGN Ref eren ce Manual Man ual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Organi sati on of the th e DESIG DESIGN N Referenc Referenc e Manu Manual al . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 1:1 Organi sation sati on of this th is Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Equip ment and Prim itives it ives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Prim it ive iv e Modelli ng A tt ribu ri butes tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 2:1 Sizing Primitive Primitive Building Blocks Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Choosing Nozzle Nozzle Size, Rating Rating and Height Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 Modelling Detail Detail Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 Obstruction Settings Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4

Positi Posi ti oni ng at a Known Kno wn Point Poin t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5 2:5 Positioning at a Coordinate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5 Polar Positioning Positioning from the Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:8 General Polar Positioning from from the Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9

Orient ation atio n and Connect ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10 2:10 Design Element Element Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10 Design Element Element Reorientation Reorientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:12 Primitive Element Element Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:14

Moving Movi ng by a K now n Distanc Dis tance e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:15 2:15 Moving Along Along Axes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:15 Moving in any any Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:16 Moving in any any Direction: Distance Distance Given in Different Plane. . . . . . . . . . . . . . . . . . . . . . . . 2:18

i

12.0

DESIGN DESIGN Refer Referenc ence e Manual

Movi ng Thr oug h Defin ed Inter section sect ion Planes . . . . . . . . . . . . . . . . . . . . . . . . . . 2:19 2:19 Moving Through Through an Intersection. Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:19 Moving Either Side Side of an Intersection. Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:21 General Moving Moving to an Intersection Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:23

Moving Movi ng In Front Fron t of o f o r Behin B ehind d Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:25 Moving Either Side Side of a Fixed Object Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:26 Moving On Top of of or Under a Fixed Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:28 Moving an Item Using Using Reference Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:31

Movi ng t o a Specif ied Clearanc e between Items . . . . . . . . . . . . . . . . . . . . . . . 2:33 2:33 Moving to a Clearance Clearance Either Side. Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:34 Moving an Object Object to Clear Another Another Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:36 Moving to a Vertical Vertical Clearance Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:38 General Moving Moving to a Clearance Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:41

Reflecti ng a Posit ion in a Plane (Mir (Mir rori ro ri ng) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:42

Pipin g, Ductin Duct ing g and Cabl Cable e Trays Trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Defini Defi ni ng a Branch Br anch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Branch Br anch and Hanger Specif icatio ic ations ns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 Connecti Conn ecting ng the th e Head Head or Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2 The Head or Tail Tail Connection Connection Reference Attribute Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4 Positioning Head or Tail in Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5 Head or Tail Positioning Positioning Using Using End Components Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6 Head and Tail Tail Positioning by Bottom or Top of of Pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7 Moving the Head Head or Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9 Reconnecting Reconnecting Pipes after an Equipment Equipment Move Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11

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

Re-sele Re-selecti cti on o f Exis tin g Compo nents and Tube . . . . . . . . . . . . . . . . . . . . . . . 3:22 Re-selecting the New Default Default Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22 General Reselection Reselection of Components Components and Tube Tube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23

Standard Component Comp onent Attr At trib ibut utes. es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24 Position and Orientation Attributes. Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26

ii

12.0


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

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

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

Positi onin g Compo nents u sing Reference Planes . . . . . . . . . . . . . . . . . . . . . . 3:44 Positioning with respect to the Previous Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:44 Positioning the Component through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:46 Positioning with respect to an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:48 General Positioning through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:51

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

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

Draggi ng Equ ipment and Pipi ng Netwo rks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:67 Dragging Equipment and Nozzles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:68 Dragging Piping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:72

Automat ic Pipe Rout in g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

ii i

12.0


Ac ces si ng th e Au to mat ic Pi pe Ro ut in g Facili ti es . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Entering and Leaving Autoroute Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

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

Refini ng t he Automati c Pipe Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Defining the Rack to be Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Defining the Direction of Spread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Defining the Base Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6 Spreading Pipes about the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 Setting the Bottom-of-Pipe Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 Combined Spreading and BOP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8

Struct ural Design Using Catalogu e Compo nents . . . . . . . . . . . . . . 5:1 Creating and Positioni ng Prim ary Nod es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2 Creatin g and Connecti ng Sectio ns A utom atically . . . . . . . . . . . . . . . . . . . . . . . 5:3 Sectio n Att ri but es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Cross-Sectional Profile via a Specification Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Generic Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Start and End Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5 Start and End Plane Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Orientation Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Joint Start and End References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7 Start and End Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8 Start and End Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8

Creating and Posit ionin g Second ary Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9 Creating and Positioning Jo ints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10 Creating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11 Creating Secondary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11 Setting Joint Geometry via a Specification Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12 Positioning and Orientating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12 Positioning and Orientating Secondary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13

At tri bu tes of Con nected J oi nt s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5: 15 Connection Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15 Cutting Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16

iv

12.0


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

Manually Connect ing Secti ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17 Connecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17 Disconnecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:18 Reconnecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:19

Repositi oni ng Steelwor k Element s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20 Reversing Section Start and End Positions (‘Flipping’) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20 Moving Steelwork Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:21 Modifying Lengths of Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22 Reorientating Steelwork Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:23

Positi oni ng and Orient ating Using P-li nes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:25 Identifying P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:26 Positioning by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:27 Orientating by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29

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

Fitt ings, Hangers and Equi pment Load Poi nts . . . . . . . . . . . . . . . . . . . . . . . . . 5:33 Fittings and Panel Fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:33 Structure-to-Pipework Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34 Structure-to-Equipment Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34

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

Representi ng Cur ved Beams and Walls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36 Overview

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36

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

Representi ng B uildi ng Com pon ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42 Using Element Soft Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42 Controlling Edge Representation in DRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:43

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

v

12.0


Desig n Temp late Hierar chy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Ap pl ic ati on Data A reas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 Functional Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Naming

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4

Application Data and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Extension to Design Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Valid Value Elements Additional Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Extension to Design Data Associated Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Special Design Data Property names in scope of a DDSE . . . . . . . . . . . . . . . . . . . . . . . . . 6:6

Parameterisation using Desi gn Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7 As si gn in g L oc al Names to Temp lat e Elem ent s . . . . . . . . . . . . . . . . . . . . . . . . . 6: 8 Setting Local Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9 Using Local Names in Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9

Settin g Pri orities f or Evaluati ng Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10 Ad di ng Design Poi nt s t o Tem pl ate El ements . . . . . . . . . . . . . . . . . . . . . . . . . . 6: 11 Using a Design Templ ate Item in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12 Ports ets and Li nksets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13

vi

12.0


Creating The Model

i

12.0


ii

12.0

DESIGN Reference Manual Introduction

1

Introduction

1.1

About the DESIGN Reference Manual The DESIGN Reference Manual describes all the Design commands in detail. DESIGN is normally used interactively. The Graphical User Interface (GUI) provides discipline-based applications which help you to create, check and report on the model. How to 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 use commands, for example, to write batch macros or to customise the GUI. If you are going to customise the GUI, you will also need to refer to the Software Customisation Guide and Software Customisation Reference Manual for information about PML, the AVEVA programming language.

1.2

Organisation of the DESIGN Reference Manual The DESIGN Reference Manual has three parts:

1.3

•

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

•

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

•

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

Organisation of this Manual You should refer to Part 1 of the DESIGN Reference Manual for general information about creating 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 connecting commands applicable to these elements.

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

2 1:1

12.0

DESIGN Reference Manual Introduction

•

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

•

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

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

2 1:2

12.0

DESIGN Reference Manual Equipment 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 are modelled within the major hierarchical elements Equipment, Structure, Ptrack and Substructure. These elements own primitive geometric shapes and holes which are dimensioned and assembled to form a suitable model. The items can then be positioned and 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 given distance or clearance. The same commands can be used to modify existing positions, orientations and dimensions. There are also a number of special plant modification facilities that are described in a later part of the manual.

2.1

Pr im it iv e Mo del lin g A ttr ib ut es The DESIGN hierarchy is a ‘skeleton’ structure of the elements which represent the chosen organisation of the model. The physical appearance and layout of the process items are determined by the value of each element’s attributes; for example, a Box only looks like a box if its XLEN, YLEN and ZLEN attributes are set (on creation they are zero). This section describes those physical primitive element attributes that give a shape to the model. Generally, these attributes will either be set by typing in their values directly or from macros. It is important, however, to recognise that regardless of how it was input, the basic attribute information is the stored physical description of the designed plant.

2.1.1

Si zi ng Pr im it iv e B ui ld in g Bl oc ks Keywords:

XLENGTH YLENGTH ZLENGTH DIAMETER HEIGHT RADIUS XOFF YOFF XTOP YTOP XBOTTOM YBOTTOM DTOP DBOTTOM RINSIDE ROUTSIDE XTSHEAR YTSHEAR XBSHEAR YBSHEAR Description:

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

2 2:1

12.0


Box

Cone

Dish

Cylinder

Slope-bottomed Cylinder

Snout

Circular

TorusRectangular Torus

Pyramid

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

Example:

XLEN 1000

(At a Box)

The xlength dimension of the box becomes 1000

DI A 3 FT

(At a Cylinder)

The diameter of the cylinder becomes 3 feet Command Syntax:

Refer to the Data Model Reference Manual.

DIAMETER

HEIGHT

Figure 2:1.

2.1.2

Dimensioning a CYLINDER primitive

Choosing Nozzle Size, Rating and Height Keywords:

CATREF

HEIGHT

Description:

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

2 2:2

12.0


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

Examples:

CATR / NFAARPMM

(At Nozzle)

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

HEI 2’ 6

(At Nozzle)

The Height of the Nozzle becomes 2’6. Command Syntax:

>- - CATr ef name - - > >- - HEI ght - - >

2.1.3

Mo del li ng Detai l L ev el s Keywords:

LEVEL Description:

This command sets the attribute, common to all primitive elements, that controls modelling detail. The command specifies a range of modelling ‘levels’ which determine the permanent visibility characteristics of the element in DESIGN. The attribute allows plant items to be assembled from overlaid primitives representing varying levels of detail. In this way, several graphical 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-modelling in 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 which that item will be drawn. In DESIGN, only primitives of visible items whose LEVEL range includes 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 usually establish rigid standards for the use of LEVELs which are defined permanently in the Catalogue and therefore must be complied with during Equipment and Civils modelling.

Example:

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

2 2:3

12.0


Command Syntax:

>- - LEVel integer integer - - >

Figure 2:2.

2.1.4

Some modelling detail levels for an I-section beam

Obst ructi on Sett ings Keywords:

OBSTRUCTION Description:

The OBSTRUCTION attribute indicates to the clash detection facility whether a primitive should be considered as a ‘Hard’ or ‘Soft’ obstruction, or not at all. Obstructions can be specified as HARD, SOFT or NONE, or alternatively they can be specified numerically as follows: 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. OBSTRUCTION settings 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 the Spatial Map which is used during clash-checking.

Examples:

OBST SOFT

(At a primitive)

Current Element will be considered as a ‘soft’ obstruction.

OBST HARD

(At a primitive)

Current Element will be considered as a ‘hard’ obstruction.

2 2:4

12.0


Examples:

OBST NONE

(At a primitive)

Current Element will be ignored during clash detection.

OBST 2

(At a primitive)

Current Element will be considered as a ‘hard’ obstruction. Command Syntax:

>- - OBSt r uct i on - - +- | |-| |-| ‘--

Figure 2:3.

2.2

i nt eger - - . | HARD - - - - - | | SOFT - - - - - | | NONE - - - - - +- - >

Obstruction settings for use in clash detection

Positioning at a Known Point These commands allow you to place the Current Element at a known position in space. You can: •

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 options exist to allow any p-point belonging to the item to be used as the positioning reference.

2.2.1

Po si ti on in g at a Co or di nat e Keywords:

POSITION

AT

2 2:5

12.0


Description:

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

AT E3’ N4’ 6 U1’

Current Element will be placed at the specified owner coordinate position (see Figure 2:4.: Positioning the Current Element at a known point ).

AT I DP@

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

AT@

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

POS PI N5 AT E3000

The specified PIN and Current Element will be positioned as a single rigid item, so that the PIN is at E3000 N0 U0 (see Figure 2:5.: Positioning a PIN and the current element together at a known point ).

Command Syntax:

>- - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - AT - - > Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

2 2:6

12.0


Querying Examples:

Q POS

Gives position of Current Element origin in owner coordinates

Q POS I N SI TE

Gives position of Current Element origin in Site

Q POS I DP@

Gives position of picked p-point

U

CE ORIGIN

N

1' 4' 6"

OWNER ORIGIN

3'

E

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

2 2:7

12.0


2.2.2

Po lar Po si ti on in g fr om t he Or ig in Keywords:

POLAR

DISTANCE

Description:

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

Examples:

POLAR E45N DI ST 300

The Current Element will be placed 300 from its owner’s origin along E45N (see Figure 2:6.: Polar positioning from the origin ).

POLAR PI N1 DI ST 3000

The Current Element will be placed 3000 from its owner’s origin along the direction of PIN1 (see Figure 2:6.: Polar positioning from the origin ).

POS I DP@ POLAR S1OW DI ST3 The p-point hit and the current element will be moved as a rigid entity so that the p-point is the specified polar distance from the owner’s origin. Command Syntax:

>- - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - POL ar DI STanc e - - > Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- | ‘-->

2 2:8

- - >

12.0

DESIGN DESIGN Refer Referenc ence e Manual Equipment and Primitives

Figu Figure re 2:6 2:6..

2.2.3

Pola Polarr posi positi tion onin ing g from from the the orig origin in

Genera nerall Pola Polarr Posi Positio tionin ning g from from the Origin rigin Keywords:

POLAR

PLANE

DISTANCE

Description:

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

POLAR POLAR N30E PLAN PL ANE N Positions the Current Element along the N30E line from the DI ST 1000 owner origin at N1000 (see Figure 2:7.: General polar positioning from the origin by specifying a plane ). Command Syntax: >- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- POLar Lar -+-+- PLAn LAne - . | | ‘ - - - - - - - - - - - - - - - - +- DI STanc e - >

2 2:9

12.0


Querying: >- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - ++- - WRT - - . | | | - - I N - - - +- | ‘ -- >

Figure Figure 2:7. 2:7.

2.3

- - >

General General polar polar positi positioning oning from the origin by specifying specifying a plane plane

Or ie ien ta tat io io n an d Co nn nn ec ec ti ti on on These commands allow the Current Element to be rotated. In the case of connection, the item is also repositioned. For both commands, the specification of a single axial direction or p-point on the Current Element is sufficient to perform a reorientation. However, a second direction must be specified if the orientation is to be fixed in 3D space.

2.3.1

Des ig ig n El El em em en en t Or Or ie ien ta tat io io n Keywords:

ORIENTATE Description:

Every Design element has its own co ordinate system which consists of a right-handed set of East (X), North (Y) and Up (Z) axes. The precise orientation of an element must be given as 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 axis direction only (allowing DESIGN to choose the other), e.g. ORI P1 IS N45E. Regardless of the command given, orientation always occurs about the Current Element origin.

2 2:10

12.0


Examples:

ORI Y I S N AN AND Z I S UP

The Current Element is rotated about its origin so that its Y axis is pointing North (in owner coordinates) and its Z axis is pointing up (see Figure 2:8.: Design element orientation (1) ).

ORI P1 I S E

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

Command Syntax:

>- ORI ent ent at e - +- I S - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- AND I S - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - +- - > Querying:

>- - Quer y ORI ent ent at i on - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->


Desi Design gn ele eleme ment nt ori orien enta tati tion on (1) (1)

2 2:11

12.0



2.3.2

Desi Design gn ele eleme ment nt ori orien enta tati tion on (2) (2)

Design sign Eleme lement nt Reorie orient nta ation tion Keywords:

ROTATE

BY ABOUT

THROUGH

AND

Description:

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

As a specifi specified ed angle angle of rotati rotation on about about the element’s element’s default default axis (i.e. the Z axis).

•

As a specifi specified ed angle angle of rotatio rotation n about a given given axis, axis, the latter latter defined defined by its its direction direction and/or through point. If the direction and/or through point are omitted, the default direction is that of the Neutral Axis or Z axis; the default through point is the Origin.

•

By refe referen rence ce to the the ele eleme ment’ nt’s s axe axes. s.

Example:

ROTATE TATE BY - 45

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

ROTATE BY 45 ABO ABOUT E

Rotates by 45° about the E-W axis (clockwise when looking E).

ROTATE ABO ABOUT E BY 45

The same as the preceding example.

ROT THRO THRO P3 ABO ABOUT S BY - 25

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

ROTATE AND Y I S N45W Rotates element until the Y axis points as closely as 25D possible to the N45W25D direction.

2 2:12

12.0


Command Syntax: Rotation about a given axis: >- ROTat e ABOut + THRough - +- BY - +- - - - - - - - - - - - - - - - - . | | | | | | ‘ - TOwar ds - | | | | | ‘ - AND I S - - - - - - - - - +- > | | BY - +- - - - - - - - - - - - - - - - - . | | | | ‘ - TOwards - +- > | | ‘ AND I S - +- THRough - . | | ‘ - - - - - - - - - - - - - - - - - - +- >

Rotation to pass thro ugh a given point: >- ROTat e THRough + ABOut + BY + - - - - - - - - - - - - - - - . | | | | | | ‘ TOwar ds | | | | | ‘ AND I S - - - - - - +- > | | BY - +- - - - - - - - - - - - - - - - . | | | | ‘ - TOwar ds + ABOut . | | | | ‘ - - - - - - - - - - - - - - +- > | | ‘ AND I S + ABOut - . | | ‘ - - - - - - - - - - - - - - - +- >

Rotation b y a specified amount: >- ROTat e BY + - - - - - - - - - - - - - - - . | | ‘ TOwar ds + ABOut - +- THRough - . | | | | ‘ - - - - - - - - - - - - - - - - - - +- > | | THRough - +- ABOut - . | | | | ‘ - - - - - - - - - - - - - - - - +- > ‘ ->

Rotation to give a specified orientation: >- ROTat e AND I S - +- ABOut - +- THRough - . | | | | ‘ - - - - - - - - - - - - - - - - - - +- > | | - THRough - +- ABOut - . | | | | ‘ - - - - - - - - - - - - - - - - +- > ‘ ->

2 2:13

12.0


2.3.3

Pr im it iv e El em en t Co nn ec ti on Keywords:

CONNECT Description:

The command allows the current primitive element to be ‘connected’ to another element or mapping 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 as they can connect and be connected to. In the former case, both the pin and Current Element move 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 so that the two specified Design Points are coincident and of opposite direction.

Example:

CONN P2 TO P1 OF / A

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

CONN PI N1 TO I DP@

The Current Element and PIN1 are moved and rotated so that PIN1 connects to the p-point hit.

CONN I DP@ TO I DP@ AND X I S N

The first point hit (belonging to the Current Element) is connected to the second point (belonging to another element). The Current Element is rotated so that its X axis is North in owner coordinates (see Figure 2:11.: Connecting primitives by using cursor selection ).

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

>- - CONnect TO - +- AND I S - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - +- - > Querying:

>- - Quer y ORI ent at i on - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘--> >- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

2 2:14

12.0


2.4

Figure 2:10.

Connecting primitives by direct specification

Figure 2:11.

Connecting primitives by using cursor selection

Moving by a Known Distance All the commands described in this section move the Current Element by a specified distance in a given direction. The simplest method is to move from the present position along an axis direction using a command such as BY EAST 1000. However, the command options provided enable more complex manoeuvres to be made. For instance, an element may be moved ‘towards’ another item until its Easting has changed by a given amount.

2.4.1

Moving Along Axes Keywords:

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.

2 2:15

12.0


Examples:

BY E300 N400

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

BY E3000 WRT SI TE

Moves the Current Element by the specified amount along the Site’s East axis (see Figure 2:12.: Moving along specified axes).

Command Syntax:

>- - BY

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

Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘--> N N BY E3000 WRT SITE CE

BY E3000

OWNER AXES

E

E

SITE AXES

Figure 2:12.

2.4.2

Moving along specified axes

Mov in g i n an y Di rec ti on Keywords:

MOVE

ALONG TOWARDS

DISTANCE

Description:

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

2 2:16

12.0


Examples:

MOVE N45E DI ST 100 The Current Element is displaced along East 45 North in owner coordinates by the specified distance (see Figure 2:13.: Moving a given distance in a given direction (1) ).

MOVE TOW I DP@ DI ST The Current Element is displaced towards the picked p-point 100 by the specified amount (see Figure 2:14.: Moving a given distance in a given direction (2) ). Command Syntax:

>- - MOVe - - +- - ALOng - - . | | ‘ - - - - - - - - - - - +- - DI STance - - > Querying:


Figure 2:13.

Moving a given distance in a given direction (1)

2 2:17

12.0


Figure 2:14.

2.4.3

Moving a given distance in a given direction (2)

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 specified in a different plane from the actual movement direction.

Example:

The Current Element is moved towards the specified design MOVE TOW / DATUM PLANE E DI ST item until its Easting (in owner coordinates) has changed by 1000 1000 (see Figure 2:15.: Moving in a direction specified in a different plane). Command Syntax: >- - MOVe - - +- ALOng - . | | ‘ - - - - - - - - - +- - +- - PLAne - - . | | ‘ - - - - - - - - - - - - - - - - - - +- - DI STanc e - >

Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- | ‘-->

2 2:18

- - >

12.0


Figure Figure 2:15. 2:15.

2.5

Moving Moving in a direction direction specif specified ied in a different different plane plane

Movin ov ing g Thr Throu ough gh De Define fined d Int Inte erse rsectio ction n Pla Plane nes s The commands described in this section move the Current Element along a given direction until it intersects with a fixed Reference Plane. Any p-point on the Current Element may be used for the manoeuvre, although the default is the origin. This point is moved to the Reference Plane which is specified by the 3D position through which it passes. The orientation of the Reference Plane defaults to perpendicular to the movement direction. In no case is the volumetric geometry of any of the Design model considered. Although you do not need to know the actual distance moved, you must provide ‘point-to-point’ dimensions in these commands. In other words, these commands cannot calculate physical clearances (see Moving In Front of or Behind Items and Moving to a Specified Clearance between Items for such commands).

2.5.1

Mo vi vi ng ng Th Th ro ro ug ug h an an In In te ter se sec ti ti on on Keywords:

MOVE

THROUGH

Description:

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

2 2:19

12.0


Examples:

MOVE N30W THR / BO BOX

Moves the Current Element along the given direction until it ‘intersects’ the Reference Plane through the origin of the named element (see Figure 2:16.: Moving along a given direction through an intersection ).

MOVE E THR THR E3000

Moves the Current Element along the given owner axis until it ‘intersects’ the Reference Plane through E3000 N0 U0 (see Figure 2:17.: Moving to intersect a plane through a given point ).

MOVE ALO ALONG N45E 45E THR I DP@

Moves the Current Element along the given direction until it ‘intersects’ the Reference Plane through the picked ppoint (see Figure 2:18.: Moving to intersect a plane through a given point ).

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

>- - MOVe - - +- - ALOng - - . | | ‘ - - - - - - - - - - - +- - THRough - - > Querying:


Figure Figure 2:16. Moving Moving along along a given direc direction tion through through an an intersect intersection ion

2 2:20

12.0


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

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

2.5.2

Movin oving g Eith Eithe er Sid Side e of an an Inte Inters rse ectio ction n Keywords:

MOVE

DISTANCE

FROM

TO

Description:

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

2 2:21

12.0


Examples:

MOVE N30W DI ST 30 TO( TO( or FRO FROM) / BO BOX

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

MOVE E DI ST 1000 F Move the Current Element East until its origin intersects a ROM / VESSEL5 Reference Plane 1000 beyond the origin of /VESSEL5 (see Figure 2:20.: Moving either side of a plane specified relative to another element ).

MOVE ALO ALONG N45E 45E DI ST 20 TO / CO COL8

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

Note: The Reference Plane is perpendicular to the movement direction. Command Syntax: >- - MOVe - - +- - ALOn LOng - - . | | ‘ - - - - - - - - - - - +- -

DI STan Tance - - +- - FRO FROm - - . | | ‘ - - TO - - - - +- - - - >

Querying:


... DISTANCE 30 FROM /BOX

30

REFERENCE PLANES

... DISTANCE 30 TO /BOX

MOVE N30W...

CE

(START POSITION)

Figure Figure 2:19. 2:19. Moving Moving either either side of an intersect intersection ion

2 2:22

12.0


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 and Reference Plane to be specified ind ependently. For example, by specifying PLANE NORTH an element may be moved towards a point until a particular Northing in the Site is intersected. In addition, any design point on the Current Element (not only the origin) can be used as the positioning datum; for instance, the p-point on the flanged face of a nozzle.

2 2:23

12.0


Examples:

Move the picked p-point (or the Current Element) towards / MOVE I DP@ TOW / DATUM PLANE N THRO DATUM until it intersects N1000 (see Figure 2:22.: Moving to UGH N1000 an intersection by separately specifying direction and plane ).

MOVE ALONG E PLANE Move the Current Element East until it intersects an oblique N45W DI ST 20 TO / Reference Plane 20 before the origin of /TANK5 (see Figure TANK5 2:23.: Moving to an intersection by separately specifying direction and plane ). Note: DISTANCE is measured in the direction of the Reference Plane and not the movement direction. Command Syntax: >- MOVe - +- - . | | ‘ - - - - - - - - - - - +- AL Ong - . | | ‘ - - - - - - - - - +- - . | | ‘ - - - - - - - - - - +- PLANe - +| | | | | || || ‘-

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

= >- DI STance - - >

Querying:


2 2:24

12.0


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

Mo vi ng In Fr on t o f o r B eh in d Item s The commands described in this section move the Current Element to the intersection with a 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 the default 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 designer does not need to know the actual distance moved, he must provide a ‘point-to-surface’ dimension.

2 2:25

12.0


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 or the other of a fixed geometric object. This takes into account the volume of the referenced element but not of the Current Element. Therefore it is applicable to, say, spacing the centreline of a vessel or column a certain distance from the surface of a wall.

Examples:

MOVE E DI ST 1000 B The Current Element is moved East until its origin is 1000 EH / WALL10 beyond the far side of /WALL10 (see Figure 2:24.: Moving either side of a fixed object ).

MOVE N45E DI STANCE The Current Element is moved until its origin is 20 to the near 20 I NFRONT / EXCH5 side of /EXCH5 (see Figure 2:24.: Moving either side of a fixed object and Figure 2:25.: Moving either side of a fixed object in a specified direction ). Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- DI STance - +- FROm - . | | ‘ - TO - - - +- - +- I NFront - . | | ‘ - BEHi nd - - +- - - . | | | - marke> - | | | ‘ - - +- >

Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - >

2 2:26

12.0


Figure 2:24.

Moving either side of a fixed object

2 2:27

12.0


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 or below a fixed geometric object. This takes into account the shape of the referenced object but not that of the Current Element. It is therefore applicable to, say, placing the centreline of a vessel a certain distance above the top surface of a beam.

2 2:28

12.0


Example:

MOVE D ONTO / BOX

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

MOVE ALONG E45D DI STA Moves the Current Element along E45D until its origin is NCE 3000 UNDER / BEAM 3000 vertically below /BEAM (see Figure 2:26.: Moving above/below a fixed object in a specified direction and Figure 2:27.: Moving above/below a fixed object ). Note: ONTOP means above in owner co-ordinates regardless of original Current Element position. The DISTANCE is always measured vertically in owner co-ordinates. Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- DI STance - +- FROm - . | | ‘ - TO - - - +- - +- UNDer - . | | ‘ - ONTop - +- - - . | | | - - | | | ‘ - - +- >

Querying:


2 2:29

12.0


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

2 2:30

12.0


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

2 2:31

12.0


Examples:

MOVE P1 E I NFRONT / BOX

The Current Element will be moved East until the specified p-point is zero distance in front of /BOX (see Figure 224).

MOVE NOZZLE1 S DI ST 200 I NF / RACK ( at an Equi pment el ement )

Moves the current Equipment by positioning the Nozzle at the specified location.

Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- PLAne DI STance - >

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

FROm - - . | TO - - - - +- - - - > I NFr ont - - . | BEHi nd - - - | | UNDer - - - - | | ONTop - - - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - >

Querying:


2 2:32

12.0


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

2.7

Moving to a Specified Clearance between Items These commands allow the Current Element to be moved to a specified clearance from a fixed object or position. Their separation takes into account both the Current Element volume and the referenced element volume. For the basic options, the clearance dimension is always specified in the movement direction. It is therefore important to place the Current Element at an appropriate position from which to make the clearance move. A simpler alternative is available for placing the Current Element vertically above or below the reference element independently of movement direction. In these instances a vertical clearance can be specified directly using the ONTOP or UNDER options.

2 2:33

12.0


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 specified clearance from a fixed Design element, Point or position.

Examples:

MOVE ALONG E45N CL Move the Current Element until its volume is zero clearance EAR BEHI ND / BOX behind BOX (see Figure 2:29.: Moving to a given clearance in a specified direction ).

MOVE E CLEAR 1000 I NFRONT / DATUMBOX

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

MOVE E45N CLEAR 10 Move the Current Element along E45N until its volume is 100 0 BEH I DP@ beyond the cursor hit p-point (see Figure 2:30.: Moving to a given clearance). Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- CLEAr ance - +- I NFront - . | | ‘ - BEHi nd - - +- - - . | | | - - | | | ‘ - - +- >

Querying:

>- - Quer y POSi t i on - - +- - - - . | | ‘ - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - >

2 2:34

12.0


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

2 2:35

12.0


Figure 2:30.

2.7.2

Moving to a given clearance

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 Referenced elements. In this way a minimum clearance can be specified between two Design items (for example, to ensure that a walkway is a sufficient distance away from a heated autoclave).

2 2:36

12.0


Example:

MOVE E CLEARANCE 1 The Current Element is moved East until its entire volume is 000 BEH / WALL10 1000 clear of the side of /WALL10 (see Figure 2:31.: Moving to clear another object ).

MOVE D CLEARANCE O The Current Element is moved down until it has a zero NTO / BEAM clearance above the element /BEAM (see Figure 2:31.: Moving to clear another object ). Command Syntax:

>- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- CLEAr ance - +| || || ‘-

I NFront - . | BEHi nd - - | | UNDer - - - | | ONTop - - - +- - - . | | | - - | | | ‘ - - - +- >

Querying:


2 2:37

12.0


Figure 2:31.

2.7.3

Moving to clear another object

Moving to a Vertical Clearance Keywords:

MOVE

CLEARANCE

ONTOP

UNDER

Description:

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

2 2:38

12.0


Example:

MOVE ALONG U30W CL The Current Element will be moved vertically until it is zero EAR ONTO / BEAM clearance above /BEAM (see Figure 2:32.: Moving to a given vertical clearance in a specified direction ).

MOVE E60D CLEAR 10 The Current Element will be moved E60D until it is 1000 00 UNDER PI N6 below the specified Design point (see Figure 2:33.: Moving to a given vertical clearance ). Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- CLEAr ance - +- UNDer - . | | ‘ - ONTop - +- - - . | | | - - | | | ‘ - - - +- > Querying:


2 2:39

12.0


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

2 2:40

12.0


Figure 2:33.

2.7.4

Moving to a given vertical clearance

General Moving to a Clearance Keywords:

MOVE

PLANE

CLEARANCE

INFRONT

BEHIND

Description:

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

Example:

MOVE TOWARD / TANK5 PLANE E The Current Element will be moved towards / CLEARANCE 30 I NF / TANK5 TANK5 until it has 30 clearance ‘this side’ in an East/West direction (see Figure 2:34.: Moving to a given clearance relative to a specified plane ).

2 2:41

12.0


Command Syntax: >- MOVe - +- ALOng - . | | ‘ - - - - - - - - - +- - +- PLAne - . | | ‘ - - - - - - - - - - - - - - - - +- TOwar ds - . | . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ’ | ‘ - CLEARance +- I NFr ont - . | | ‘ - BEHi nd - - | | - - - . | | | - - | | | ‘ - - - +- > Querying:


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 by reflecting it in a specified plane. The current element and its hierarchy of members will be repositioned so as to achieve a mirror image of their initial relative positions. If the current element is a Group, all members of the group and their hierarchies of members will be reflected.

2 2:42

12.0


The values of positional attributes and directional attributes are derived by direct reflection in the plane. Orientations are processed such that they remain right-handed. For most elements this is achieved 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 directly while the Z axis is reflected and reversed;

•

The piping elements Tee, Nozzle, Elbow, Coupling, Reducer and Flange, where the ppoints 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 COPY command (see Sections 2.1.5 and 2.1.6 of Database Management Reference Manual ) to create 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, no attempt is made to reflect catalogue geometry or to reference alternative catalogue components. Keywords:

MIRROR Description:

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

Example:

MI RROR PLANE E45D THRO / TANK5

Reflects position of current element in plane which has given direction and which passes through /TANK5 (see Figure 2:35.: Mirroring a position in a plane ).

Command Syntax: >- - MI RRor - - - - >

where is any of the standard ways of specifying a plane through a given point in a given direction: = >- +- PLAne - +- DI STance - +- - - - - - - . | | | | | | ‘----------------| | | | | | - - - - - - - - - - - - - - - - - - - - - - - - - - - | | | | | | - THRough - - - - - - - - - - - - - - - - - - - | | | | | ‘ - CLEAr ance - +- - . | | | | | | ‘ - - - - - - - - - - +- - | | | | | | - - | | | | | ‘-----------| | - DI STance - - +- - . | | | | | | | - - | |

2 2:43

12.0


| | | || | | | | | | || || ‘-

| | | ‘ - - - - - - - - - - - +- - - - - - - - - - - - - - - - - - - | | CLEAr ance - +- - . | | | | ‘ - - - - - - - - - - +- - . | | | | | - - | | | | | ‘ - - - - - - - - - - - +- - - - - - - - - - - - - - - - | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | THRough - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- >

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

I NFr ont - - . | BEHi nd - - - +- - - - - . | | | - - - - | | | ‘ - - - - - | | FROm - - . | | | TO - - - - +- - - - - - - - +- - >

= >- - +- - ONTop - - . | | ‘ - - UNDer - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - >

/TANK5

Plane through /TANK5

Plane direction E45D

Current Element (owning three primitives)

MIRROR PLANE E45D THRO /TANK5

Figure 2:35.

Mirroring a position in a plane

2 2:44

12.0

DESIGN Reference Manual Piping, Ducting and Cable Trays

3

Piping, Ducting and Cable Trays This chapter describes the commands to create Piping (including Hangers), Ducting and Cable Trays. Then the commands to position, orientate and connect piping components are described. The key element in these disciplines is the Branch. This is a two-ended entity that can be joined with other Branches to form a network. The network can finish where a Branch is connected 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 whose sequence and position define the centreline route. Straight variable lengths of Tube are automatically routed between adjacent Components and are therefore not individual Component elements themselves. There are no special Design hierarchy elements for ducting and cable trays. They are routed as Branches, but with Components drawn from parts of the Catalogue dedicated to the relevant discipline. It is convenient, therefore, to refer to pipes, ducting and cable trays collectively 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 distinction is made, the term ‘piping’ also applies to Hangers.

3.1

Defining a Branch Before routing takes place, various preparatory steps are taken to define the Specification and the start and end points of the Branch or Hanger. The Piping Specification and Insulation Specification are defined first, so that all Components created within the Branch can be selected correctly. The Head and Tail attributes can be set either by explicit positioning or by connection to another item (e.g. a Nozzle). The Tail position may be in free space, when it is determined by the Leave point of the final Component in the Branch. It is quite normal in such circumstances to route the pipe with only the HEAD attributes set up. (The reverse may also apply if routing backwards.) When a Branch is connected to another item, the attributes of the element that it is connected to are set to refer to the Branch. For example, if a Branch Head is connected to a Nozzle, then the CREF (Connection Reference) attribute of the Nozzle is set to refer to the Branch. Note that when a Branch is connected to a Nozzle, the Nozzle may be part of a database to which the piping engineer does not have write-access. In this case, an Inter-DB Connection Macro is created, which can be run by the designer who does have write access to the second database. This macro is a sequence of commands that, for example, sets the CREF of a Nozzle that has been connected to by the piping designer. For more information, see Database Management Reference Manual .

2 3:1

12.0


3.2

Branch and Hanger Specifications Keywords:

PSPE HSPE Description:

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

Examples:

PSPEC / A35B8 ( At Pi pe l evel )

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

PSPEC / A15A2 ( At Br anch l evel )

The PSPE attribute of the Branch will be set to /A15A2. All subsequent selection commands at that Branch or one of its Components will use that Specification by default.

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

>- - PSPEci f i cat i on name - - >

3.3

Co nn ec ti ng th e Head or Tai l Keywords:


The CONNECT command, when applied to Branches (or Han gers), sets up the Head or Tail to match exactly the item to which it has been connected. For example, if the Head is connected to a 3-inch flanged-faced nozzle at E3000 and pointing North, the CONNECT command will set all the Head attributes (HBOR, HCON, HPOS and HDIR) to corresponding values. In addition, the Head and Nozzle are logically ‘tied together’ by two attributes which ‘point’ to each other - the Nozzle CREF will point to the Branch, and the Branch HREF (Head Reference) will point to the Nozzle. The final effect of CONNECT, which only applies to Heads, is that the Tube (or Rod) that may 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)

2 3:2

12.0


Examples:

CONN PH TO / 1205- N5 ( Wher e / 1205- N5 i s a Nozzl e)

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

CONN PT TO LAST MEM

The Tail attributes of the current element will be set to match the Leave Point of the last Component (that is not an Attachment point).

CONN PT TO / 100- A8/ T2 ( Wher e / 100- A8/ T2 i s a TEE) CONN PT TO P4 OF / VF205 ( Wher e / VF205 i s a VFWA. )

The Tail attributes of the current element will be set to match the free p-point on the specified TEE (see Figure 3:1.: Connecting a Branch Head or Tail). The Tail attributes of the current element will be set to match the specified p-point.

CONN PH TO PT OF / 100- A8/ 1 The Head attributes of the current element will be ( Wher e / 100- A8/ 1 i s set to match the Tail of the specified Branch. anot her Br anch) CONN PH TO I D NOZZ@

As in the first example, but with the Nozzle identified by cursor selection.

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

>- - CONnect TO - - +- - - - . | | ‘ - - - - - - +- - > Querying:

>- - Quer y - - +- - PHead - - . | | | - - HHead - - | | | | - - PTai l - - | | | ‘ - - HTai l - - +- - > >- - Quer y - - +- - HPosi t i on - - . | | ‘ - - TPosi t i on - - +- - WRT - - . | | ‘ - - I N - - - +- - - - >

2 3:3

12.0


CE H E A D

CONN PH TO /1205-N5

/1205-N5

BRANCH

T A I L

PH

CONN PT TO /100-A8/T2 BRANCH CENTRELINE

PT

PA

PL

/100-A8/T2 Figure 3:1.

3.3.1

Connecting a Branch Head or Tail

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, but they may also be set explicitly. When they are set, the corresponding attribute (CREF, HREF or TREF) of the item connected to is reset so as to point back to the Branch or Hanger.

Examples:

TREF / PI PE2 HEAD HREF NULREF

Sets TREF of current element to point to Head of /PIPE2 and setsHREF of /PIPE2 to point back to the current element. Unsets HREF; i.e. disconnects Head from any other element.

Command Syntax:

>- - +- - HRef - - . | | ‘ - - TRef - - +- | | |

- - +- - HEAD - - . | | | - - TAI L - - | | |

2 3:4

12.0


| ‘----------+ | | ‘ - - NULREF - - - - - - - - - - - - - - +- - > Querying:

>- - Quer y - - +- | |-| |-| ‘->- - Quer y - - +- | ‘--

3.3.2

CE - - - - - - . | HEAd - - - - | | BRANch - - | | TAI l - - - - +- - > HREF - - . | TREF - - +- - >

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 of TUBE (or ROD) and no Head or Tail connection can be made, it is necessary to set the Head/Tail attributes individually.

Examples:

HPOS E10 N5 U5

The Head position is set as specified in owner coordinates.

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

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

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

HPos - - . | TPos - - +- - - - > HDi r - - . | TDi r - - +- - - - > HBOr e - - . | TBor e - - +- - - - >

2 3:5

12.0


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

>- - Quer y - - +- | |-| |-| ‘--

3.3.3

PHead - - . | HHead - - | | PTai l - - | | HTai l - - +- - >

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 in that Branch or Hanger. This will normally occur when the Tail is to finish with a piece of variable length Tube. This command treats the Tail position as a pseudo-Component and places it at the specified point along the previous Component’s Leave p-point direction. If the Head is to be positioned in this way, Backwards Routing Mode must be in force. Example:

POS PT DI STANCE 1000

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

POS PH THROUGH E3000 ( I n BACKWARDS mode)

The HPOS attribute will be set to the intersection between the line from the Arrive p-point of the Previous Component and the perpendicular plane through E3000 N0 U0 in owner coordinates.

Command Syntax:

>- - POSi t i on - - +- | |-| |-| ‘--

PHead - - . | PTai l - - | | HHead - - | | HTai l - - +- - DI STance - - . | | ‘ - - THRough - - - +- - >

Querying:

>- - Quer y - - +- - PHead - - - - - - . | | | - - PTai l - - - - - - | | |

2 3:6

12.0


|-| |-| |-| ‘--

HTai l - - - - - - | | HHead - - - - - - | | HPosi t i on - - | | TPosi t i on - - +- - >

LAST COMPONENT

PL

D

D PT

1000

POS PT DISTANCE 1000

N

PH D

PA

D

LAST COMPONENT (BACKWARDS MODE)

30 OWNER AXES

E

POS PH THROUGH E30

Figure 3:2.

3.3.4

Head/Tail positioning using end components

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 specified clearance above or below a Design element or Point. If the Head or Tail Tube has been selected, then its cross-section will be taken into account. (Otherwise the HPOS or TPOS will be moved to the specified clearance, as no Tube geometry is available.)

2 3:7

12.0


Example:

BOP ONTO / BEAM ( At t he Head)

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

TOP UNDER U3000 ( At t he Tai l )

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

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

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

FROm - - . | TO - - - - +- - - - > I NFr ont - - . | BEHi nd - - - | | ONTop - - - - | | UNDer - - - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - >

Querying:

>- - Quer y - - +- | |-| |-| |-| |-| ‘--

PHead - - - - - - . | PTai l - - - - - - | | HTai l - - - - - - | | HHead - - - - - - | | HPosi t i on - - | | TPosi t i on - - +- - >

2 3:8

12.0


UP

PH

PT

BOP ONTO /BEAM

TOP UNDER U3000

PH PT 3000 /BEAM

OWNER AXES

HORIZONTAL

Figure 3:3.

3.3.5

Head/Tail positioning by Bottom/Top of pipe

Mo vi ng t he Head o r Tai l Keywords:

MOVE

BY

DISTANCE

Description:

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

Examples:

MOVE PT DI ST - 2000

Moves the Tail by 2000 from its current position, in the opposite direction to PT.

MOVE PT BY E2000 S500

Moves the Tail by 2000 East and 500 South from its current position

2 3:9

12.0


Command Syntax:

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

PHead - - . | HHead - - | | PTai l - - | | HTai l - - +- - BY - - +- - WRT - - . | | | | | - - I N - - - +- - - - > | | | ‘--> | ‘ - - DI STance - - >

Querying:

>- - Quer y - - +- | |-| |-| |-| |-| ‘--

Figure 3:4.

PHead - - - - - - . | PTai l - - - - - - | | HTai l - - - - - - | | HHead - - - - - - | | HPosi t i on - - | | TPosi t i on - - +- - >

Moving the Head or Tail

2 3:10

12.0


3.3.6

Reconnecting Pipes after an Equipment Move Note: 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 the Branches connected to it will move with it. RECONNECT will reconnect all the HEADS and TAILS of Branches connected to an Equipment, moving th em to new positions if necessary. Other elements in the Branches are not affected and must be realigned using ordinary routing commands.

Example:

RECON

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

Command Syntax:

>- - RECOnnect - - >

3.4

Selecting Component and Tube Details from Specifications Selecting from Specifications in PDMS is fundamental to all Piping design work. When you created a Component element (say an ELBO), you must then give the CHOOSE (or SELECT) command to form a link from the Component to the Catalogue description of the item, via the chosen Specification. As the correct choice of Component can involve a large number of considerations, each Selection would be very arduous if conducted manually. DESIGN assists you by automatically examining the current element and its immediate neighbours for default parameters, then searching for an appropriate item in the Specification. Of course, ultimate control rests with the designer, who can fully or partially override this choice. However, in the majority of cases, the default Selection will be suitable. In a similar manner, the straight TUBE between ad jacent Components is Selected from a Specification. This is usually done automatically at the same time as Component Selection, so the designer only needs to be concerned with separate TUBE selection in certain special circumstances 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 own company Catalogue and Specifications with your Catalogue Administrator before reading this section. In order to make the correct Selections, you will also need a printed copy of each Specification that you wish to use.

2 3:11

12.0


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 theOK button is to set the SPREF and LSTUBE attributes of the current Component, taking into account the choice made and the current bore. Specification-dependent Design attributes (if any) will also be set, i.e. HEIG, ANGL, RADI and SHOP. The Component may (optionally) be positioned and connected to the previous (or next) Component (or to the pipe head or tail). If the Cancel button is selected, the Component’s attributes will 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 incompatible connection types. In such a case, the new Component will be force-connected and a warning 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 if connection types are incompatible.

•

If the force-connect facility is OFF, a connection attempt will still be made following component selection. In this case however, the newly selected Component will be left at the Site origin if connection types are incompatible. This action can be turned off by giving 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 there are no valid choices, for example there are no Components of a particular type for the specified bore, an error alert is displayed.

2 3:12

12.0


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 in the specification. Example form:

CHOOSE TEXT

Displays a Selection form listing choices based on the Specification Component’s (SPCOM’s) Detail Description Text (obtained from the RTEX attribute of the relevant DTEX element) and Material Description Text (obtained from the XTEX attribute of the relevant MTEX element). Example form:

2 3:13

12.0


Example:

CHOOSE RTEX CHOOSE STEX CHOOSE TTEX

Displays a Selection form listing choices based on the SPCOM’s Detail Description Text (obtained from the RTEX, STEX or TTEX attribute of the relevant DTEX element). Example form:

CHOOSE XTEX CHOOSE YTEX CHOOSE ZTEX

Displays a Selection form listing choices based on the SPCOM’s Material Description Text (obtained from the XTEX, YTEX, or ZTEX attribute of the relevant MTEX element). Example form:

CHOOSE ALL

Combines the above CHOOSE and CHOOSE TEXT options.

2 3:14

12.0


Example: Example form:

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

CHOOSE DEFAULT

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

Choose from Reducers with specified arrive and leave NEW REDU CHOOSE WI TH ABOR 1 bores only 00 LBOR 80

NEW ELBO CHOOSE WI TH STYP LR

Choose from long-radius Elbows only.

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

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

The first level must contain the question TYPE

•

The second level must contain the question PBOR or BORE

Command Syntax: >- CHOOse - +- AUTOConnect - - . | | | - FORCEConnect - +- ON - - . | | | | ‘ - OFF - +- > | | - SPec - . | | ‘ - - - - - - - - - - - - - - +- DEFaul t - . | | ‘ - - - - - - - - - - - +- RTEX - . | | | - STEX - | | |

2 3:15

12.0


| - TTEX - | | | | - XTEX - | | | | - YTEX - | | | | - ZTEX - | | | | - TEXT - | | | | - ALL - - | . - - - - <- - - - . | | / | ‘ - - - - - - - - +- WI TH - *- - - | | | | | ‘ - - +- > ‘ ->

where: i s>- - +- | |-| |-| |-| | -| |-| |-| ‘--

PBOr e i nt eger - - . | ANgl e - - - - - - - - - - | | RAdi us - - - - - - - - - | | ABOr e - - - - - - - - - - | | LBOr e - - - - - - - - - - | | PREs sur e - - - - - - - | | TEMper at ur e - - - - | | RATi ng - - - - - - - - - +- - - - >

and i s >- - +- | |-| |-| |-| |-| ‘--

3.4.2

STYpe - - . | TYpe - - - | | ACOnn - - | | LCOnn - - +- - wor d - - > PCOnn i nt eger word - - > wor d - - +- - val ue - - . | | ‘ - - wor d - - - +- - >

Selecting Components from Specifications An alternative method of selecting items from a Specification is to create the piping Component, and then to ask the system to select a component of the correct type from the current piping Specification. If there is a choice of component during selection, it is sometimes necessary to specify answers to specification questions such as STYPE or BORE before the correct item is selected. Typical commands could be as follows:

NEW ELBO SEL WI TH STYP LR NEW TEE SEL WI PBOR 3 150 NEW FLAN SEL WI STYP WN NEW REDU SEL WI STYP ECC LBOR 100

2 3:16

12.0

DESIGN DESIGN Refer Referenc ence e Manual Piping, Ducting and Cable Trays

3.4.3

Selecti lecting ng the the De Default fault Spe Specif cifica icatio tion n Comp Compone onent nt Keywords:

SELECT Description:

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

3.4.4

SPECIFICATION

Obtained from the PSPE attribute of the Branch.

(ARRIVE) BORE

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

ANGL E, HEIGHT, 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.

Select lectin ing g from from Se Severa verall Alte Alterna rnative tives Keywords:

SELECT Description:

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

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

•

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

In both instances, the designer must specify the relevant Headings with the required Entry as part of the SELECT command. After a successful SELECT command, the design attributes will be updated with the relevant values from the Specification. The relevant attributes are ANGLE, RADIUS and SHOP, SHOP, and HEIGHT if specified in the SELECT command.

2 3:17

12.0


Examples:

SELECT

The default Component and Leave Tube will be selected from the Branch Specification. The Current Element SPREF and LSTU attributes will be set to the chosen Specification Component names.

SEL WI STYPE BALL BALL

The current element and Leave Tube will be selected using the default choices except for the STYPE Heading which has been specified.

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

SEL WI ANGLE 45

The current element and Leave Tube will be selected using the default choice except for the ANGLE heading. Also, the ANGLE attribute of the Current Component will be set to 45. (Similar behaviour occurs with HEIGHT and RADIUS.)

SEL WI LBOR 50

The current element will be selected using the default choice. However the Leave p-point and Leave Tube will be selected with the specified nominal bore.

Command Syntax:

. - - - - - - <- - - - - - - . / | >- - SEl ect WI t h - - *- - SPec - - | | | | - - - - - - - - | | | | - - - - - - - ’ | ‘--> For Selection criteria that are only in the Specification, the Specification itself may also contain information to assist default Selection. This information is in the Default Line of the Specification. Querying:

>- - Quer y - - +- - SPRef - - . | | ‘ - - TUbe - - - +- - > . - - - - - <<- - - - - . / | >- - Q SPE SPEC Ci f i cat cat i on - - *- - - - +- - >

2 3:18

12.0


where is:

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

3.4.5

PBO PBOr e i nt eger - - . | ANgl e - - - - - - - - - - | | RAdi us - - - - - - - - - | | ABOr e - - - - - - - - - - | | L BOr e - - - - - - - - - - | | PREs s ur e - - - - - - - | | TEMper at ur e - - - - | | RATi ng - - - - - - - - - | | STYpe - - - - - - - - - - | | TYpe - - - - - - - - - - - | | PCO PCOnn i nt eger - - | | ACOnn - - - - - - - - - - | | L COnn - - - - - - - - - - | | wor d - - - - - - - - - - - +- - >

Selecti lecting ng ‘Out‘Out-ofof-S Specif pecifica icatio tion’ n’ Comp Compone onent nts s Keywords:

SELECT SPEC Description:

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

SEL WI SPEC / A3AH A3AH

The current element will be Selected from the given Specification using the default choice.

SEL SEL WI SPEC SPEC / A3AH A3AH STYPE CTRL

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

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

2 3:19

12.0


Command Syntax:

. - - - - - <<- - - - - . | >- - SEl ec t WI t h SPec - - * | | - - - - - | | | | - - - - ’ | | - - - - > | ‘--> /

and are explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual . Querying:

. - - - - - <<- - - - - . / | >- - Quer y SPEC PECi f i cat cat i on - - *- - - - +- - > is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual .

>- - Quer y - - +- - SPRef - - . | | ‘ - - TUbe - - - +- - >

3.4.6

Selecti lecting ng Comp Compone onent nts s and and Tube Tube Separa parate tely ly 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 owning Component, or vice versa. This command enables separate Selection to occur. SELECT TUBE is most frequently used at the HEAD of a Branch where there is Tube between the Head and the First Component.

Examples:

SEL SEL TUB TUBE( At Br anch) anch)

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

SEL TUB TUBE WI STYP GLAS The Component LSTU attribute (Leave Specification ( At Component ponent ) Tube) will be Selected with the default choice of TUBE except for STYPE. Command Syntax:

>- - SEl ec t - - +- - SPr ef - - - . | | | - - L St ube - - | | | | - - HSt ube - - | | |

2 3:20

12.0


|-| |-| |-| ‘--

LSr od - - - | | HSr o d - - - | | TUbe - - - - | . - - - - - <- - - - - . | / | ROD - - - - - +- - WI t h - - *- - - - - | | | | - - - - ’ | | - - - - > | ‘-->

Querying:

. - - - - - <- - - - - . / | >- - Quer y SPECi f i cat i on - - *- - - - +- - > >- - Quer y - - +- - SPRef - - - . | | | - - TUbe - - - - | | | | - - LSt ube - - | | | | - - HSt ube - - | | | | - - LSr od - - - | | | ‘ - - HSr o d - - - +- - >

3.4.7

Di rec t Sel ec ti on by Sh or tc od e Keywords:

SHORTCODE Description:

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

Examples:

SHOR / EL50

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

SHOR TUB / TU50

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

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

2 3:21

12.0


Command Syntax:

>- - SHORt code - - +- - SPRef - - - . | | | - - TUbe - - - - | | | | - - L St ube - - | | | | - - HSt ube - - | | | | - - LSr od - - - | | | | - - HSr od - - - | | | ‘ - - - - - - - - - - - - +- - name - - > Querying:

>- - Quer y - - +- | |-| |-| |-| |-| ‘--

3.5

SPRef - - - . | TUbe - - - - | | LSt ube - - | | HSt ube - - | | LSr od - - - | | HSr o d - - - +- - >

Re-selection of Existing Components and Tube If a Component or Tube is required to be respecified, you may restate any of the Selection commands described elsewhere in this manual. However, each time this is done all the non-default Specification entries must be restated, even if most or all of these are identical to the old Specification Component. The RESELECT command allows the designer to make use of the original Selection parameters for a Component to simplify the Selection of a new Component. This is useful for situations where only a single change has taken place since the original Selection; for example, if the Branch Specification (PSPE attribute) was changed or the nominal bore of a group of Components had to be increased. The RESELECT command operates as follows: 1. Any new Selection parameters are considered (either changed defaults or specified by the user). 2. If any more parameters are required, they are obtained from the old Specification Component.

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 Branch Specification. The default Selection parameters are obtained from the current element’s

2 3:22

12.0


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

RESEL

The current element and Leave Tube will be Selected from the new default choice(s). Any parameters required that are not obtainable from defaults will be derived from the old Specification Component.

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

>- - RESEl ect - - > Querying:

. - - - - - <- - - - - . / | >- - Quer y SPECi f i cat i on - - *- - - - +- - > is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual..

>- - Quer y - - +- - 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 new parameters. Where new parameters are not stated or available through defaults, they are obtained from the old Component Specification entries. Examples:

RESEL WI TH STYPE BALL

The current element and Leave Tube will be Selected using any default parameters and the STYPE specified. Any further parameters required will be obtained from the old Specification Component.

2 3:23

12.0


Examples:

RESEL WI SPEC / NEWSPEC

The current element and Leave Tube will be Selected using the new Specification and any default parameters. The remaining necessary parameters will be obtained from the old Specification Component.

RESEL TUBE WI STYPE GLAS The current element HSTU attribute will be ( At Br anch) Selected using default parameters and the specified STYPE. If any further parameters are necessary they will be obtained from the old Specification Component. Command Syntax:

>- - RESEl ect - - +- | |-| |-| |-| |-| |-| ‘--

SPr ef - - - . | LSt ube - - | | HSt ube - - | | LSr od - - - | | HSr o d - - - | | TUbe - - - - | . - - - - - - - <- - - - - - . | / | ROD - - - - - +- - WI t h - - *- - SPec - - | | | | - - - - - - - - | | | | - - - - - - - ’ | ‘-->

Querying:

. - - - - - <- - - - - . / | >- - Q SPECi f i cat i on - - *- - - - +- - > is explained in the section on Standard syntax Graphs in Part 1 of the DESIGN Reference Manual.

>- - Quer y - - +- - SPRef - - - . | | ‘ - - TUbe - - - - +- - >

3.6

Stan dar d Co mp on en t A tt ri bu tes This section describes the standard Component element attributes that provide their complete logical and physical descriptions. Although you may set them directly, many of these attributes are automatically determined when using the Specification selection and pipe 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

2 3:24

12.0


•

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

The standard Specification attributes of a Component are: SPREF

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

LSTUBE

These point to a Specification Component that provides the complete Catalogue LSROD description of the Tube emerging from the current element Leave Point.

ISPEC

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

TSPEC

This points to a dummy Tracing Specification and is used by ISODRAFT to indicate trace heating requirements.

The remaining standard attributes are: POSITION

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

ORIENTATION

The Component’s orientation in Zone coordinates (neither Branch nor Pipe have an ORIENTATION, though Branch has head and tail directions (HDIR and TDIR).

ARRIVE

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

LEAVE

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

BUILT

Management information to indicate if the item has actually been built.

SHOP

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

ORIFLAG

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

POSIFLAG

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

The following attributes do not occur in all Components, but are sufficiently common to be considered as standard: ANGL E

The (variable) angle of a Component.

HEIGHT

The (variable) height of a Component.

RADIUS

The (variable) radius of a Component.

LOFFLINE

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

2 3:25

12.0


3.6.1

CREF

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

CRFA

(Multi-way Component Connection Reference.) Indicates the elements that are connected to the free (neither Arrive nor Leave) p-points of the Current Element.

Position and Orientation Attributes Keywords:

POSITION ORIENTATION Description:

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

Component position and orientation are established using the pipe routing or ordinary positioning commands described elsewhere. Querying:

>- - Quer y - - +- - POSi t i on - - +- - - - . | | | | ‘------------| | | ‘ - - ORI ent at i on - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘--> >- - Quer y POSi t i on - - > Gives the Component position in ZONE co-ordinates.

>- - Quer y ORI ent at i on WRT SI TE - - > 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 a Component. It is usual to set those attributes before Selection and Positioning as they can define: •

The automatic Selection Parameters for that item (particularly REDUCERS)

•

The centreline Logical Route that will affect positioning and orientation of the Component.

2 3:26

12.0


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

ARR 2 LEAV 1

The Logical Route will Arrive P1 of the Component.

ARR 3 LEAV 2

The Logical Route will Arrive at P3 and Leave at P2 of the Component.

at

P2 and Leave

at

Note: Default is Arrive 1, Leave 2. Command Syntax:

>- - +- - ARRi ve - - . | | ‘ - - 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 can be ‘Flipped’. It does not actually rotate the Component until the next orientation command is given. The FLIP command can be given before Selection, as the Arrive and Leave p-point numbers are Design attributes independent of the Catalogue. As most Specifications are organised with Reducers having PBOR1 larger than PBOR2, the Select mechanism needs to be told that the Arrive is at P2 by FLIP Selection. Therefore NEW REDU FLIP SELECT WITH LBORE 100 would be a typical command for a bore increase. When working in BACKWARDS mode, this situation reverses - the REDU need only be Flipped if a bore reduction is required. Example:

FLI P

Reverses the current Arrive and Leave p-point numbers for that Component.

Command Syntax:

>- - FLI P - - > Querying:

>- - Quer y - - +- - ARRi ve - - . | | ‘ - - L EAve - - - +- - >

2 3:27

12.0


ARRIVE

P1

PH

CE

LEAVE FLIP (ARRIVE 2 LEAVE 1) P2

PT Figure 3:5.

3.6.4

Component Arrive and Leave attributes (standard and Flipped)

The Component Specification Reference Attribute Keywords:

SPREF Description:

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

SPREF / SPEC208/ EL50BW The current element is specified by the chosen Specification Component. Note: This attribute is usually inserted automatically as a direct result of the CHOOSE (or SELECT) command. It can, however, be set directly to the name of the required Specification Component.

2 3:28

12.0


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 as PDMS elements in the hierarchy. Instead, they are extruded from the Leave p-point of a Component to the Arrive p-point of the next. Their geometric cross-section details are stored in the Catalogue and are pointed at from the Upstream Component via its LSTU attribute. At the Head of a Branch, there is no Upstream Component; therefore a special Branch attribute exists to allow Tube from the Head to t he first Component to be spe cified (HSTU). Generally, you need not be concerned about specifying Tube between Components, as it is automatically determined during the Component Selection process described elsewhere. If short fixed-length stubs of Tube are required, it is usually appropriate to create a Component FTUB element to ensure that this minimum length is adhered to. Similarly, where Tube changes direction, a Component must be inserted (usually a BEND), as variable length Tube is always straight. Examples:

LSTU / SPEC502/ 100L ( At Br anch Component )

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

HST / SPEC502/ 100L ( At Br anch)

As above, but between the of First Component (or Tail).

LSR / HS20/ 2. 5 ( At Hanger Component )

As first example.

HSR / HS20/ 2. 5 ( At Hanger Component )

As second example.

Head

and

Arrive

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

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

LSTube - - . | HSTube - - | | L SRod - - - | | HSRod - - - +- - name - - - - . | | ‘ - - NULREF - - +- - >

2 3:29

12.0


3.6.6

Insulation Specification Attribute Keywords:

ISPEC Description:

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

Examples:

I SPE / I 500- HAV

The Current Component and Tube from its Leave p-point will be insulated according to the named Specification. (The temperature parameters required to determine insulation thickness will be obtained from the Branch element.)

I SP NULREF

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

Note: If a whole Branch is to be insulated, the Branch ISPE should be set before Components are created. This setting will then cascade down to all new Components. Command Syntax:

>- - I SPec - - +- - name - - - . | | ‘ - - NULREF - +- - > Querying:

>- - Quer y I NSUl at i on - - > Gives the insulation thickness.

Figure Missing!!

Figure 3:6.

Variable length Tube between Components

2 3:30

12.0


3.6.7

Trace Heating Specification Attribute Keywords:

TSPE Description:

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

TSPE / TR50A

The Current Component will be noted by ISODRAFT with the given trace heating requirements.

TSPE NULREF

Trace heating is removed.

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

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

3.6.8

The Fabr icat io n Fl ag s Keywords:

SHOP

BUILT

Description:

These attributes indicate the location and status of construction of each Component. The SHOP 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 during construction. Examples:

SHOP TRUE

The current element will FABRICATED’ in ISODRAFT.

BUI LT FALSE

Information attribute indicating that current element has not been built.

be

itemised

as

‘SHOP

Command Syntax:

>- - +- - SHOP - - - . | | ‘ - - BUI l t - - +- - TRue - - - . | | ‘ - - FAL se - - +- - >

2 3:31

12.0


3.6.9

Position and Orientation Status Flags Keywords:

ORIFLAG

POSFLAG

Description:

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

Examples:

POSF FALSE

This setting will occur if the Components have been transferred from a P&ID and not positioned. The Component will not be drawn in the views.

ORI F FALSE POSF TRUE This setting will occur if the item has been Selected in DESIGN but not oriented.

ORI F TRUE POSF TRUE

After the Component is oriented it will be shown in normal line type.

Note: If either POSFLAG or ORIFLAG remains FALSE, the next Component cannot be positioned using ordinary routing commands. Command Syntax:

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

>- - +- - ORI Fl ag - - . | | ‘ - - POSFl ag - - +- - TRue - - - . | | ‘ - - FAL se - - +- - > Querying:

>- - Quer y - - +- - POSFl ag - - . | | ‘ - - ORI Fl ag - - +- - >

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 may change its physical appearance.

2 3:32

12.0


Although many Component elements possess the ANGLE, HEIGHT or RADIUS attributes or use Design Parameters, it is the Catalogue that determines whether the value of these attributes will affect the physical Component. For example, changing the ANGLE attribute of a 90-degree fixed-angle elbow to 45 degrees will have no effect. In some cases, the variable value may be difficult to determine. For instance, a BEND in a pipe may possess an angle resulting from an oblique change in direction. In such instances, the DIRECTION command (described elsewhere) can be used to determine the ANGLE setting automatically. The ANGLE, HEIGHT and RADIUS attributes can also be set before selection as a means of choosing between, say, 90-degree or 45-degree f ixed-angle elbows.

Examples:

ANGL 45 ( Bef or e Sel ect i on)

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

HEI G 300 ( Af t er Sel ect i on)

If a variable height component, this dimension will alter as specified.

Command Syntax:

>- - ANGl e - - +- - - - - - - - - - - - - - - - - - - . | | ‘ - - TOwar ds - - +- - > >- - HEI ght - - > >- - RADi us - - > >- - DESPar amet er s - - >

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 is off-line, the reporting utility will treat it as a continuous part of the Tube either side of the Component and will only report one pipe length. This is useful for BENDS (bends in continuous Tube) and OLETS (which tap off the side of a piece of Tube). If the Component is left as in-line, the Tube will be split into two sections with no account being taken of the Arrive-to-Leave length of the Component.

2 3:33

12.0


Examples:

LOFF FALSE

In the reporting utility, the current element will be treated as a full Component which breaks the Tube lengths either side.

OFFL TRUE

In the reporting utility, the current element will be included as part of a single Tube length running through its Arrive-toLeave centreline.

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

>- - +- - LOFFl i ne - - . | | ‘ - - OFFLi ne - - - +- - TRue - - - . | | ‘ - - FAL se - - +- - >

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 can become the ends of other Branches. For three-way Components (e.g. TEE), the attribute CREF (Connection Reference) is used to show which Branch is connected to the free ppoint. This is usually set automatically as a result of a CONNECT command, but it may also be set explicitly. For Components with more than three p-points (e.g. CROSS), the attribute CRFA stores the names of up to 10 Branches which connect to this item. Although a Design Component element can possess a CREF or CRFA attribute, it is the Catalogue which controls whether the item can actually be connected to by other Branches.

Examples:

CREF / PI PE1 TAI L

Sets CREF of current element to point to Tail of /PIPE1 and sets TREF of /PIPE1 to point back to th e current element.

CREF NULREF

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

Command Syntax:

>- - CREF - - +- - - - +- - HEAD - - . | | | | | - - TAI L - - | | | | | ‘----------+ | | ‘ - - NULREF - - - - - - - - - - - - - +- - >

2 3:34

12.0


Querying:

>- - Quer y - - +- - CREf - - . | | ‘ - - CRFA - - +- - >

3.7

Orientation and Connection of Components Orientation and Connection commands make use of the constrained centreline of a Pipe route. When a Component is Selected, it is automatically positioned next to the adjacent Component so that it can be seen. However, it is essential in DESIGN that the item is either oriented or Connected. DESIGN insists on this minimum to ensure that each Component is deliberately manipulated by the user. All the examples in this section assume Forwards routing mode is in operation. Gener ally, if Backwards is being used, then the effect of these commands will logically reverse.

3.7.1

Com pon en t Or ientat ion Keywords:

ORIENTATE Description:

This command rotates the Component about its origin so that (in forwards mode) the Arrive p-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 to achieve an orientation because of the direction of the constrained centreline, DESIGN will leave this off-line direction in the closest orientation to that requested. Examples:

ORI

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

ORI AND P3 I S U

As above, and orient the off-line p-point (P3) in the specified direction (see Figure 3:8.: Orienting a non-concentric Component by means of an off-line p-point ).

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

>- ORI ent at e - +- I S - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- AND I S - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - +- - >

2 3:35

12.0


Querying:

>- - Quer y

Figure 3:7.

. - - - - - - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - . / | - - *- - DI Rect i on - - . | | | | ‘ - - - - - - - - - - - - - - - +- - WRT - - . | | | | | - - I N - - - +- - - - ’ | ‘-->

Orienting a Concentric Component

2 3:36

12.0


Figure 3:8.

3.7.2

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

Direction-Changing Components Keywords:

DIRECTION Description:

The DIRECTION command orients the Component along the constrained centreline and points the specified p-point in a new direction. Unlike the ORI command, if that new direction 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 is controlled by the Catalogue.

2 3:37

12.0


Examples:

DI R E

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

DI R AND P3 I S U45E As above, but P3 (rather than PL) is pointed to the new direction (see Figure 3:9.: Changing the direction of variableangle Components). Note: If the new direction cannot be adopted by a fixed-angle Component, the item will be pointed in the closest direction to that specified. Command Syntax:

>- - DI Rect i on - - +- - AND I S - - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- - - - > Querying:

. - - - - - - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - . / | >- - Quer y - - *- - DI Rect i on - - . | | | | ‘ - - - - - - - - - - - - - - - +- - WRT - - . | | | | | - - I N - - - +- - - - ’ | ‘-->

2 3:38

12.0


Figure 3:9.

3.7.3

Changing the direction of variable-angle Components

Com pon en t Co nn ect ion Keywords:


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

2 3:39

12.0


Examples:

CONNECT

The arrive p-point of the Component is connected to the leave 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 the arrive p-point of the next Component (see Figure 3:10.: Component connection).

CONNECT AND P3 I S U

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

Note: Only adjacent Components (not Attachment Points) may be connected to; if Connection Types or bores are incompatible, then an automatic FLIP takes place and CONNECT is attempted again. Command Syntax:

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

- +- TO - +- AND I S - > | | | ‘--> ‘-->

Querying:

. - - - - - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - . / | >- - Quer y - - *- - POSi t i on - - . | | | | ‘ - - - - - - - - - - - - - - +- - WRT - - . | | | | | - - I N - - - +- - - - ’ | ‘-->

2 3:40

12.0


Figure 3:10. Component connection

3.7.4

Fo rc ed Co mp on en t Co nn ec ti on Keywords:


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

2 3:41

12.0


Examples:

FCONN

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

FCONN TO TAI L

The Leave p-point of the Component is force-connected to the Tail.

FCONN AND P3 I S U

As first example and the off-line p-point is oriented upwards.

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

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

3.8

- +- TO - +- AND I S - - > | | | ‘--> ‘-->

Moving by a Known Distance These commands move the Component a specified distance along the constrained centreline. All the commands move the Component from its current position. The distance moved may either be measured along the constrained centreline or some other planar direction. 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 logically reversed.

3.8.1

Moving Components Keywords:

MOVE

DISTANCE

Description:

This command moves the Component along the constrained centreline by a specified distance.

Example:

MOVE DI STANCE 1000 The Current Component is moved from its present position 1000 along the constrained centreline (see Figure 3:11.: Moving a Component by a given distance ). Note: A positive dimension moves the Component away from the Previous Component.

2 3:42

12.0


Command Syntax:

>- - MOVe DI STance - - > Querying:

>- - Quer y POSi t i on - - +- - WRT - - . | | | - - I N - - - +- | ‘-->

Figure 3:11.

3.8.2

- - >

Moving a Component by a given distance

Gen er al Mo vi ng o f Co mp on en ts Keywords:

MOVE

PLANE

DISTANCE

Description:

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

MOVE PLANE N45E DI ST 1000

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

Command Syntax:

>- - MOVe PLAne DI STance - - > Querying:

>- - Quer y POSi t i on - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

2 3:43

12.0


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 constrained centreline at the intersection with a fixed reference plane. Any p-point on the Component may be used, although the def ault is the origin. This point is positioned along the constrained centreline through the reference plane which is defined by the 3D position through which it passes. The orientation of the reference plane defaults to perpendicular to the constrained centreline, although a different planar direction can be specified. In no case is the volumetric geometry of the 3D model considered. These commands are therefore not suitable for ‘clearance’ positioning. All the examples in this section assume Forwards routing mode. Generally, if Backwards is being used, then the effect o f 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 specified distance from the origin of previous Component. Any p-point on the current element may be used, the default being the origin.

2 3:44

12.0


Examples:

DI ST 1000

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

POS PA DI ST 1000

As above, but the Arrive point of the Component is used (se e Figure 3:14.: Positioning with respect to Previous Component).

Command Syntax:

>- - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - DI STance - - > Querying:

>- - Quer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

Figure 3:13. Positioning with respect to Previous Component

2 3:45

12.0


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 with a fixed design element or position (say a Nozzle) or a cursor position. The Component is positioned along the constrained centreline where the reference plane intersecting, say, the specified Nozzle, cuts at right angles. For cursor positioning it is therefore advisable to use orthogonal views for orthogonal piping.

Examples:

POS THR / TANK5

The origin of the current Component will be positioned on the constrained centreline where this intersects the perpendicular reference plane through the named element (see Figure 3:15.: Positioning through an intersection ).

POS PA THR E3000

The Arrive point of the current Component will be positioned on the constrained centreline where the perpendicular reference plane through E3000 N0 U0 intersects (see Figure 3:16.: Positioning through an intersection .

THR @

The Component will be placed on the constrained centreline where the perpendicular reference plane indicated by the cursor intersects (see Figure 3:17.: Positioning through an intersection ).

2 3:46

12.0


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

>- - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - - - - - - - - - +- - THRough - - > Querying:

>- - Quer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

Figure 3:15. Positioning through an intersection

2 3:47

12.0




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.

2 3:48

12.0


Examples:

DI ST 50 FROM / TANK5

The Component will be moved along the constrained centreline until its origin is 50 beyond the perpendicular plane through the named element (see Figure 3:18.: Positioning with respect to an intersection).

DI ST 1000 TO NEXT

The Component will be placed on the constrained centreline so that its origin is 1000 before of the Next Component’s origin (see Figure 3:19.: Positioning with respect to an intersection ).

POS PA DI ST 20 FROM PL OF PREV

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

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

>- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- DI STanc e - +- FRom - . | | ‘ - TO - - - +- - > Querying:

>- - Quer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- - - - > | ‘-->

2 3:49

12.0


Figure 3:18.

Positioning with respect to an intersection

Figure 3:19.


2 3:50

12.0


Figure 3:20.

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 specified independently of the constrained centreline. This is particularly relevant for routing sloping lines where a specific Easting or Northing is to be intersected. Example:

PLANE E DI ST 1000

The Component will be placed on the constrained centreline so that its origin is 1000 from the previous Component’s origin in an East/West direction (see Figure 3:21.: Positioning through an intersection defined in an independent plane ).

Command Syntax: >- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- PLANe - +- DI STance - +- FRom- . | | | | ‘ - TO - - - +- - > | ‘ - THr ough - >

Querying: >- - Quer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- | ‘ -- >

2 3:51

- - >

12.0


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 constrained centreline 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 is the origin. In no case is the geometry of the current element considered. However, the geometry 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 is being 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 specified distance from a geometric object, point or position.

2 3:52

12.0


Examples:

DI STANCE 30 I NFRONT / WALL

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

DI STANCE 125 BEHI ND I DP @

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

POS PL I NF / ACCESS

The Component will be placed such that its Leave Point is zero distance ‘this side’ of the specified object (see Figure 3:23.: Positioning Components relative to a specified object).

Command Syntax: >- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- DI STanc e - +- I NFr ont - . | | ‘ - BEHi nd - - +- - - . | | | - - | | | ‘ - - - +- > Querying: >- - Quer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- | ‘ -- >

2 3:53

- - >

12.0


Figure Figure 3:22. Positionin Positioning g Component Components s either either side side of an object object

2 3:54

12.0


Figure Figure 3:23. Positioning Positioning Compo Components nents relative relative to a specif specified ied object object

3.10 3.10.2 .2

Positioning Compone Components nts On Top of or Unde Underr an an Obje Object ct Keywords:

POSITION

DISTANCE

ONTOP

UNDER

Description:

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

2 3:55

12.0


Examples:

DI STANCE STANCE 35 ONTO / BEAM BEAM

The Component will be placed on the Constrained Centreline so that its origin is 35 above the specified object (see Figure 3:24.: Positioning above/below an object).

DI STANCE STANCE 125 UNDER I DP @ The Component will be placed on the Constrained Centreline so that its origin is 125 below the picked point. If this point is an Arrive or Leave, then the Tube cross-section will be taken into account (see Figure 3:24.: Positioning above/below an object ). Command Syntax: >- +- POSi POSi t i on on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- DI STanc e - +- ONTop - . | | ‘ - UNDer - +- - - . | | | - - | | | ‘ - bpos> - - +- >

Querying: >- - Quer uer y - - +- - POSi t i on - - . | | ‘ - - - - - - - - - - - - - - +- - WRT - - . | | | - - I N - - - +- | ‘ -- >

2 3:56

- - >

12.0


Figure Figure 3:24. 3:24. Positionin Positioning g above/ above/below below an object object

3.10.3

Genera nerall Compone Component nt Positioni Positioning ng Using Using Pla Plane nes s Keywords:

POSITION

PLANE

DISTANCE

INFRONT

BEHIND

ONTOP

UNDER

Description:

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

2 3:57

12.0


Example:

PLANE E DI ST 1000 I NFRONT / WALL

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

Command Syntax: >- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- PLAne - . | | ‘ - - - - - - - - - - - - - - - - +- DI STance - +| || || ‘-

ONTop - - - . | UNDer - - - | | I NFront - | | BEHi nd - - +- - - . | | | - - | | | ‘ - - - +- >

Querying:


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

2 3:58

12.0


3.11

Component Clearance Positioning The commands in this section position the Component on the constrained centreline to give a specified clearance distance from a f ixed design item. The clearance specified usually takes into account both the current element and referenced element geometric shapes. However, the following rules also apply: •

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

•

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

•

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

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

3.11.1

Clearance from the Previous Component Keywords:

CLEARANCE Description:

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

Example:

CLEA 500

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

Command Syntax:

>- - CLEAr ance - - > Querying:

>- - Quer y - - +- - POSi t i on - - . | | | - - BOP - - - - - - - | | | ‘ - - TOP - - - - - - - +- - WRT - - . | | ‘ - - I N - - - +- - - - >

2 3:59

12.0


Figure 3:26.

3.11.2

Clearance from a Previous Component

Component Clearance Either Side Keywords:

CLEARANCE

INFRONT

BEHIND

Description:

This command places the current Component on the constrained centreline at a specified clearance in front of or behind a fixed design object. If the Arrive or Leave point of the referenced object is used, then the Tube cross-section at this point is conside red rather than the full item geometry.

Examples:

CLEAR BEHI ND / WALL

The Component will be placed on the constrained centreline with zero clearance on the ‘far side’ of the specified element (see Figure 3:27.: Component clearance either side of a fixed object).

CLEAR 1200 I NF PL OF NEXT

The Component will be placed on the constrained centreline with 1200 clearance ‘this side’ of the Tube emerging from the Component’s Leave point (see Figure 3:27.: Component clearance either side of a fixed object ).

Command Syntax: >- - CLEAr ance - - +- - - - . | | ‘ - - - - - - - - - - - - +- - I NFr ont - - . | | ‘ - - BEHi nd - - - +- |

2 3:60

- - - . |

12.0


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

Querying:


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

2 3:61

12.0


3.11.3

Component Clearance Vertically Keywords:

CLEARANCE

ONTOPUNDER

Description:

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

Examples:

CLEARANCE ONTO / BEAM

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

CLEARANCE 50 UNDER / BEAM

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

CLEAR 50 ONTO I DP @ The current Component will be placed on the constrained centreline at a clearance of 50 vertically above the picked p-point. If this p-point is an Arrive or Leave, then the Tube cross-section will be taken into account (see Figure 3:28.: Component clearance above/below a fixed object ). Command Syntax:

>- - CLEAr ance - - +- - - - . | | ‘ - - - - - - - - - - - - +- - ONTop - - . | | ‘ - - UNDer - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - > Querying:


2 3:62

12.0


Figure 3:28.

3.11.4

Component clearance above/below a fixed object

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 the Tube cross-section at its Leave point is a specified clearance from another fixed object. The clearance can either be specified as a dimension along the constrained centreline in-frontof/behind the object or vertically on top/under it. If the Arrive or Leave points of the fixed object 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.

2 3:63

12.0


Examples:

BOP ONTO / BEAM

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

BOP 30 BEHI ND / FLAN

The Component will be positioned on the constrained centreline so that the Tube emerging from its Leave point is 30 clear of the ‘far side’ of /FLAN (see Figure 3:29.: Tube clearance relative to a fixed object ).

BOP 30 BEHI ND PL OF / As above, but 30 to the far side of the Leave Tube of / FLAN FLAN (see Figure 3:30.: Tube clearance taking into account the Tube diameter ). Command Syntax:

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

FROm - - . | TO - - - - +- - - - > ONTop - - - - . | UNDer - - - - | | I NFr ont - - | | BEHi nd - - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - >

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


2 3:64

12.0


Figure 3:29.

Tube clearance relative to a fixed object

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

2 3:65

12.0


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.

Examples:

PLANE E CLEARANCE 1000 The current Component will be placed on the constrained centreline so that it is 1000 clear of the Previous Component in an East-West direction (see Figure 3:31.: Component clearance specified relative to an independent plane).

POS PL CLEAR 100 ONTO / BEAM

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

Command Syntax: >- +- POSi t i on - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- PLAne - . | | ‘ - - - - - - - - - - - - - - - - +- CLEARance - +| || || ‘-

ONTop - - - . | UNDer - - - | | I NFront - | | BEHi nd - - +- - - . | | | - - | | | ‘ - - - +>

Querying:


2 3:66

12.0


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

3.12

Dragging Equipment and Piping Networks If equipment is repositioned using ordinary positioning commands, the pipes connected to it do not automatically move with the item. The DRAG command is used to move Constrained Networks of Piping, Equipment and Nozzle elements all together. How the constrained network is created depends on the direction of the dragging operation and the type of item being dragged. When a DRAG command is given, the current element is displayed normally, together with the constrained network. This network finishes where a legal end is found. Items that can be dragged are: •

Pi pi ng Co mp on en ts In this case the network is formed by searching outwards in all directions from the component until a legal end is found for each ‘leg’ of the network.

•

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

2 3:67

12.0


•

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

A legal end for a constrained network can be: •

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

•

A piece of tube that can be compressed parallel to the 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. This may be because:

3.12.1

•

The internal search limit has been reached

•

A LOCKED element has been found in the network

Dragging Equipment and Nozzles Keywords:

DRAG

AT

BY

POSITION

MOVE

Description:

This command repositions the current element and constrained network to the specified position. The DRAG command can be followed by any standard Equipment and Civils positioning or moving command.

Examples:

DRAG AT E3000

The current element and constrained network will be dragged to the specified position.

DRAG BY N500 U500

The current element and constrained network will be dragged by the specified amount.

DRAG MOVE E2000

The current element and constrained network will be moved to the specified position.

DRAG MOVE N CLEAR 1000 I NF / BUI LD10

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

Command Syntax:

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

2 3:68

12.0


>- - DRAG - - +- - - - . | | ‘ - - - - +- - > where: defines any absolute positioning command, e.g. AT, POS, etc. defines any relative positioning command, e.g. BY, MOVE, etc.

The full expanded syntax is given below for reference: = >- - +- - AT - - +- - - - - . | | | | ‘ - - - - | | | | - - - - . | | | | ‘ - - - - - +- - - - - - - - +- - > = >- - +- - POLar - - . | | ‘ - - - - - - - - - - - - - - - - - - - +- - - - > = >- - POSi t i on - - +- - - - +- - AT - - +- - - - - . | | | | | | ‘ - - - - | | | | | ‘ - - - - - - - - - - - - - | | | | - - AT - - . | | | | ‘ - - - - - - - - +- - - - - . | | | | ‘ - - - - +- - - - - - - - - - - - - +- - > = >- +- PLAne - +- DI STance - +- - - - - - - . | | | | | | ‘----------------| | | | | | - - - - - - - - - - - - - - - - - - - - - - - - - - - | | | | | | - THRough - - - - - - - - - - - - - - - - - - - | | | | | ‘ - CLEAr ance - +- - . | | | | | | ‘ - - - - - - - - - - +- - | | | | | | - - | | | | | ‘-----------| | - DI STance - - +- - . | | | | | | | - - | | | | | | | ‘ - - - - - - - - - - - +- - - - - - - - - - - - - - - - - - - | | | | - CLEAr ance - +- - . | | | | | | ‘ - - - - - - - - - - +- - . | | | | | | | - - | | | | | | | ‘ - - - - - - - - - - - +- - - - - - - - - - - - - - - - | | | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | | | - THRough - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +>

2 3:69

12.0


= >- - +- - I NFr ont - - . | | | - - BEHi nd - - - +- - - - - . | | | | | - - - - | | | | | ‘ - - - - - | | | | - - FROm - - . | | | | ‘ - - TO - - - - +- - - - - - - - +- - > = >- - +- - ONTop - - . | | ‘ - - UNDer - - +- - - - - . | | | - - - - | | | ‘ - - - - - +- - > = >- - +- - BY - - +- - WRT - - . | | | | | - - I N - - - +- - - - . | | | | ‘----------------------| | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- - > = >- MOVe - +- - +- ALOng - . | | | | | - - - - - - - - - +- - - - - . | | | | | - BY - +- WRT - . | | | | | | | | ‘ - I N - - +- - | | | | | ‘ - - - - - - - - - - - - - - - - - - - - - - | | | | - ALOng - . | | | | | - - - - - - - - - +- - - - - - - - - - - - - - - - - | | | | - BY - - +- WRT - . | | | | | | ‘ - I N - - +- - - - - - - - - - - - | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- >

2 3:70

12.0


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

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

2 3:71

12.0


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

3.12.2

Dr ag gi ng Pi pi ng Keywords:

DRAG AT BY POSITION MOVE DISTANCE THROUGH CLEARANCE INFRONT BEHIND ONTOP UNDER

FROM

TO

Description:

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

Examples:

DRAG THRO @

The current element and constrained network are moved along the constrained centreline until the origin of the current element lies on a reference plane which passes through the cursor position.

DRAG MOVE S DI STANCE 1000

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

2 3:72

12.0


Examples:

DRAG DI STANCE 1000 ONTO The current element and constrained network are / GRADE dragged so that the origin of the current element is 1000 above /GRADE.

DRAG BOP ONTO / BEAM2- 1 CLEAR 150

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

Note: As it changes orientation as well as position, CONNECT cannot be used in conjunction with DRAG. Command Syntax:

>- - DRAG - - +- - - - . | | | - - - - | | | ‘ - - - - +- - > = >- - +- - BOP - - . | | ‘ - - TOP - - +- - - - . | | ‘ - - - - - - - - - - - - +- - - - . | | ‘ - - - - +- - >

Figure 3:35.

Dragging Piping to a specified position

2 3:73

12.0


Figure 3:36.

Dragging Piping to a specified position

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

2 3:74

12.0

DESIGN Reference Manual Automatic Pipe Routing

4

Automatic Pipe Routing The automatic pipe-routing facilities of DESIGN enable simple orthogonal pipe routes to be generated automatically. Additionally, a number of pipes can be ordered and spread across pipe 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 the head and tail positions and using the route command. In a more complex role, these facilities can be used to route a complex set of pipes, avoiding obstructions and following preferred paths. For more complex pipe routing, Ptrac, Pvol and Rplane elements may be used to steer the automatic routing process along preferred areas. These must be created and positioned before entry to automatic routing, because the autoroute process operates with restricted command syntax, which does not allow elements to be created.

4.1

Accessing the Automatic Pipe Routing Facilities The automatic pipe routing facilities are set aside from the rest of the DESIGN commands in a separate command structure called Au to ro ut e Mod e.

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 in autoroute mode, the command syntax is restricted to those commands necessary for automatic routing and rack ordering. To return to the full DESIGN syntax, the EXIT command is used.

Example:

AUTOROUTE

Enters Autoroute mode

EXI T

Returns to the full DESIGN syntax

2 4:1

12.0


4.2

Pipe Routing Pipe routing may be simple and direct, or it may be precisely defined, according to the constraints and preferences you set. The autoroute process creates a centreline route using Elbows 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 the automatic routing process to consider alternatives and avoid obstructions. The pipes to be routed must contain empty Branches whose Head and Tail references are correctly set. The constraints which can be applied are as follows: •

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

•

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

WEI GH 100 . 01 100

•

4.2.1

Indicate that the X and Z axes are prohibited and the Y axis is preferred.

Routing Planes - Routing Planes are elements which are used to guide the automatic routing mechanism into preferred areas. For example, if a rack was to be positioned between two rows of vessels an RPLANE element would be created along the centreline of the proposed rack. Without the RPLANE element, the autoroute process would route the two rows of pipes either side of the preferred area, rather than down the middle.

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

AXES Description:

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

Example:

AXES / ZONE1

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

2 4:2

12.0


Command Syntax:

>- - AXes - - >

4.2.2

Set ti ng Rou ti ng Pl an es Keywords:

RPLANE Description:

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

Example:

RPLANE / PTRAC1

Sets /ZONE1 as an element in the Routing Plane list. All RPLAN elements, in the hierarchy below /ZONE1 will be considered.

RP / RP1 / RP2

Adds /RP1 and /RP2 to the list. A maximum of 150 RPLAN elements may be considered by the automatic routing process.

RP

Clears the list of Routing Planes.

Command Syntax:

. - - - - - <- - - - . / | >- - RPl anes - - *- - - - +- - >

4.2.3

Set ti ng Pen al ty Vo lu mes Keywords:

PVOL Description:

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

Example:

PVOL / PV1

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

2 4:3

12.0


Example:

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

PV

Clears the list of Penalty Volumes.

Command Syntax:

. - - - - <- - - - - . / | >- - PVol umes - - +- - *- - - - +- - > | ‘-->

4.2.4

Invoking the Automatic Routing Process Automatic pipe routing can be invoked by issuing the ROUTE command with a list of Pipes to be routed. The Pipes to be routed must have empty Branches, with Head and Tail references set. Keywords:

ROUTE Description:

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

Example:

ROUTE / PI PES

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

ROUTE WI TH BENDS / PI PES All of the branches belonging to /PIPES will be routed using Bends in preference to Elbows. Command Syntax:

>- - ROut e - - +- - WI t h - - +- - ELbows - - . | | | | ‘ - - BEnds - - - | . - - - - - <- - - - . | | / | ‘ - - - - - - - - - - - - - - - - - - - - - - - +- *- - - +- - >

4.2.5

Setting the Nozzle Offset Factor Keywords:

OFFSETFACTOR

2 4:4

12.0


Description:

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

OFFSET 5

Sets the offset to be five times the bo re of its associated Nozzle.

Command Syntax:

>- - OFFSETf act or integer - - > Querying:

>- - Quer y OFFSET - - >

4.3

Refining the Automatic Pipe Routes The automatic routing process often results in a set of common centreline routes down the centre of a rack. The following section describes the rack ordering facilities which are able to refine these routes into a more acceptable form. The rack ordering process works by spreading a number of pipes across a predefined rack volume. You have various options which may be set to control the spacing of pipes and the direction of spread across the rack. The parameters which need to be input are:

4.3.1

•

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

Def in in g t he Rac k t o be Us ed . Keywords:

RACK Description:

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

RACK / PVOL1

Sets /PVOL1 to be the rack.

Command Syntax:

>- - RAck - - >

2 4:5

12.0


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 are ordered along the rack. The default position from which the pipes are spread is the centre of the PVOL. This may be changed to the side of the PVOL by adding the parameter FROMSIDE to the command. Examples:

SDI R 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 of the PVOL

SD N AB

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

Note: If no spread direction is specified, the default is taken as the direction of the second largest side of the PVOL Command Syntax:

>- - SDi r - - +- - FRomsi de - - - - - . | | | - - ABout cent r e - - | | | ‘ - - - - - - - - - - - - - - - - - +- - >

4.3.3

Def in in g t he B as e Di rec ti on 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. Example:

BASE W

Sets the base direction to be West. (This should always be perpendicular to the spread direction.)

Command Syntax:

>- - BAse - - >

2 4:6

12.0


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 the specified clearance. The default clearance is 50mm between pipe walls on the same centreline. Examples:

SPREAD / PI PES

Spreads the pipes in /PIPES about the designated rack

SP / PI PES WW 100

Spreads the pipes such that the wall-to-wall clearance is 100mm

SP / PI PES WF 4I N

Spreads the pipes such that the diameter of Flanges will be considered as part of the calculation. In this case, the distance between a Flange o/d and its adjacent pipe wall, will be a minimum of 4 inches.

SP / ZONE1 FF 75

Spreads the pipes such that two opposing Flange diameters will have a minimum clearance of 75mm. Pipes with no Flanges would have a wall-to-wall clearance of 75mm.

SP ALL

Repeat previously defined order sequence (for example, on a subsequent rack).

Command Syntax:

>- - SPr ead - - +- - WW - - - . | | | - - FF - - - | | | | - - WF - - - | | | | - - ALL - - | | | ‘ - - - - - - - - - +- - - - . . - - - - - <- - - - . | | / | ‘ - - - - - - - - - - - - +- * - - - - +- - >

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 resting on the rack plane in the BASE direction.

2 4:7

12.0


Examples:

BOP / ZONE1

Sets the BOP of all pipes in /ZONE1 to sit on the specified rack

BOP ALL

Repeat previously defined order sequence

Command Syntax:

>- - BOP - - +- - ALL - - > | | - - - - . . - - - - - <- - - - . | | / | ‘ - - - - - - - - - - - - +- * - - - - +- - > Note: No ordering takes place with the BOP command; it is expected that the BOP command 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 the pipes across the rack to give the required clearances, and then moves them into contact with the rack plane. Examples:

ORDER / PI PES WW 100 Spreads the pipes such that the wall-to-wall clearance is 100mm and then sets the BOP positions to sit on the rack.

OR / ZONE1 FF 75

Spreads the pipes such that the Flange-to-Flange clearances are 75mm, and then sets the BOP positions to sit on the rack.

OR ALL

Repeat previously defined order sequence

Command Syntax:

>- - ORder - - +- - WW - - - . | | | - - FF - - - | | | | - - WF - - - | | | | - - ALL - - | | | ‘ - - - - - - - - - +- - - - . . - - - - - <- - - - . | | / | ‘ - - - - - - - - - - - - +- * - - - - +- - >

2 4:8

12.0

DESIGN Reference Manual Structural Design Using Catalogue Components

5

Structural Design Using Catalogue Components This chapter first describes how logically connected structural steelwork may be built up in DESIGN by choosing Components from the Catalogue. Such structures will normally exist in the DESIGN hierarchy at Framework (FRMW) or Subframework (SBFR) level. The concepts are then extended for use in building designs, using other materials such as concrete. The principal types of element involved in st eelwork design are: Nodes

These define the points within the 3D design model between which steel construction members are to run. Primary Nodes have their position defined in free space, whereas Secondary Nodes have their position defined relative to an owning steel Section. Nodal data, including the attributes of member elements of Nodes, is particularly relevant for stress analysis of the steelwork structure. Sections

Sections represent the physical steel members (columns, beams, bracing struts etc.) which make up the interconnected structure. Their cross-sections are defined by reference to Catalogue 2D Profile elements, while their lengths are derived from the positions of the Nodes between which the Sections run. Joints

These are Catalogue items which represent the physical connections between structural members. Primary Joints are owned by Primary Nodes; Secondary Joints are owned by Secondary Nodes. Multiple connections are represented by Primary or Secondary Compound Joints , which own a SubJoint for each connection point. Linear Joints are used 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 is determined 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 repre sent any ancillary item related to, but not an inherent part of, the structure, such as web stiffeners, lifting lugs,

2 5:1

12.0


access ports, and so on. They are owned by Sections and Panels, respectively. Compound Fittings and Compound Panel Fittings, each of which owns Subfittings, are used to represent more complex geometry (such as penetrations, where one or more elements pass through another element). Generic Sections (GENSECs)

GENSECs can be used to represent any structural item whose geometry can be generated by sweeping a 2D profile along a linear or curved path. The path, defined by a Spine element, is determined by a sequence of Spine Points and Curves. In their simplest linear format, GENSECs may be used instead of Sections and Panels; in more complex formats they can represent curved beams, curved walls, etc. Fixings

Generic fixingscan represent any jo in t or fitting owned (indirectly) by a GENSEC.

5.1

Creating and Positioning Primary Nodes Keywords:

NEW

PNODE

NPOS

Description:

The first step in creating a new piece of structural steelwork is often the creation and positioning of a network of Primary Nodes within the 3D design model. PNOD elements are created, as for other Design elements, by using the NEW command. They may be positioned either by using a standard positioning command or by setting the NPOS (Node Position) attribute directly. Nodes have no physical size: their positions are used to define the points in space between which steel Sections are to be positioned/strung.

Example:

NEW PNOD / PNOD1 AT E1000 N500 U500 ( At FRMW or SBFR l evel )

Creates a Primary Node named /PNOD1 at the specified position.

NEW PNOD / PNOD2 COPY PREV BY E1000

Creates a Primary Node which is displaced from the previous one in the specified way.

NEW PNOD / PNOD3 NPOS E2000 N1000 D500

Creates /PNOD3, then places it at the specified position.

Command Syntax:

>- - NPOSi t i on - - - - > (The standard element creation syntax is described in Part 1 of the DESIGN Reference Manual.)

2 5:2

12.0


Querying:

Q NPOS

5.2

Creating and Connecting Sections Automatically Keywords:

STRING

FROM

TO

Description:

The STRING command is a very powerful multi-functional tool which performs the following operations automatically: •

A Section (SCTN) element is created, running between two named Nodes. The Node positions 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 line is used to set the DRNS (Start Direction) and DRNE (End Direction) attributes (on the basis 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 be compatible with the new Section. Thus, both the OPDI (Origin Plane Directio n) attribute and the normal to the Cutting Plane (as defined by the CUTP attribute) of each PJOI will 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 physical Section within the structural design model. It leaves you at the new Section (SCTN) level within the hierarchy.

Example:

STRI NG / COLUMN1 FROM / PNOD1 TO / PNOD2

Strings a Section named /COLUMN1 between the specified Primary Nodes.

STRI NG BEAM FROM / PNOD2 TO / SNOD3 NAME / UB80. LEV2

Strings a Section of GTYPE BEAM between the named Primary and Secondary Nodes. The Beam is named separately in the second command line.

Note: The presence of a Section is shown on the DESIGN graphical display as a centreline-only representation (broken line) at this stage. The Section has no physical form, other than a derived length (related to the inter-Node separation), until its cross-section has been defined by setting a reference to a Catalogue Profile element. Command Syntax:

>- - STRI ng - +- name - . | | ‘ - - - - - - - - +- word - . | | ‘ - - - - - - - - +- FRom - - TO | ‘ - TO - - FRom -

2 5:3

- . | - +- - >

12.0


5.3

Section Attributes A Section is a linear structural component such as a universal beam, column, brace, tie, strut, etc. Sections are assumed to be ‘prismatic’; that is, they are assumed to have uniform properties 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 Profile element stored in the Catalogue DB.

•

Its length is derived from the separation between the points defined by its Start Position (POSS) and End Position (POSE) attributes.

This section describes the main attributes which together define a Section as a 3D physical entity 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 Profile element in a Catalogue DB in order for the Section to be given a physical representation by DESIGN. This is achieved by setting SPREF to the name of a Specification Component in a Project Specification.

Example:

SPRE / 203X203X55KG. UB Sets the Specification Reference of the current Section to point to a Profile in the Catalogue. (The .UB suffix in the Specification Component name would normally indicate that this Profile represents a Universal Beam.) 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 Section within the structure. Its setting is not obligatory. (See the Catalogues and Specifications User Guide for a list of suggested GTYP word settings for Profile elements.)

2 5:4

12.0


Example:

GTYP BEAM

Sets the GTYP of the current Section to BEAM.

Command Syntax:

>- - - GTYPe - - - word - - - > Querying:

Q GTYPe

5.3.3

Star t an d En d Pos it io ns Keywords:

POSSTART

POSEND

Description:

When a Section is Strung (see Creating and Connecting Sections Automatically ), its start and end positions (POSS and POSE) are set to the positions of the start and end Nodes. When a Section is manually Connected or Reconnected (see Manually Connecting Sections), the settings of POSS and POSE are derived from the intersections of the Jline through the End Cutting Planes of the Section and the Joints. In either case, POSS and POSE are set automatically. It is also possible to set POSS and POSE specifically; for example, where a Section extends into free space, with at least one end unconnected. This may be done by specifying the coordinates directly, or by relating them to the position o f another design element.

Example:

POSE E1250 N2000 D750

Positions the Section’s end at the sp ecified point.

POSS / PNOD1

Positions the Section’s start at the NPOS of the specified Primary Node.

Command Syntax:

>- - +- - POSSt ar t - - . | | ‘ - - POSEnd - - - - +- - - - > Querying:

Q POSSt ar t Q POSEnd

2 5:5

12.0


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 the perpendiculars to the planes which define the ‘cut’ ends of the Section) are usually defined automatically when the Section is connected within the structural model; either by Stringing (see Creating and Connecting Sections Automatically ) or manually (see Manually Connecting Sections). The settings of the corresponding DRNS and DRNE attributes are then derived automatically from the dire ctions of the associated Joint’s Cutting Planes. It is also possible to set DRNS and DRNE specifically; for example, where a Section extends into free space, with at least one end unconnected. In this case each cutting plane direction must be in the general direction of the other end of the Section.

Example:

DRNS N45W

Sets DRNS to the specified direction, regardless of the direction of the Section’s Z-axis.

DRNE PERP

Sets DRNE so that the end cutting plane is perpendicular to the Section’s Z-axis (giving a square end as opposed to a chamfered end for a Section which has a skewed connection).

Command Syntax:

>- - +- - DRNSt ar t - - . | | ‘ - - DRNEnd - - - - +- - - - - - - - - - - . | | ‘ - - PERPendi cul ar - - +- - > Querying:

Q DRNSt ar t 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 angular clockwise rotation when viewed in the POSS-to-POSE direction. The angle of rotation from the default orientation is held as the setting of the Beta Angle (BANG) attribute of the Section.

2 5:6

12.0


SPREF of SCTN points to PROF

POSS

in Catalogue

POSE DRNS

DRNE

BANG

NA

Example:

BANG 90 Command Syntax:

>- - BANGl e value - - > Querying:

Q BANGl e

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) and JOIE (Joint End) attributes set such that they cross-refer to the Joints to which those ends are connected. (The Joints have a similar cross-reference, the CREF attribute, back to the attached Section.) These attributes are set automatically when a Section is connected and you will not usually need to set them specifically.

Example:

J OI E / PJ OI . RB. 2

Sets logical connection from Section’s end to named Primary Joint.

Command Syntax:

>- - +- - J OI St ar t - - . | | ‘ - - J OI End - - - - +- - - - > Querying:

Q J OI St ar t Q J OI End

2 5:7

12.0


5.3.7

Start and End Connection Types Keywords:

CTYSTART

CTYEND

Description:

Section ends which have been connected in the structure have their CTYS (Start Connection Type) and CTYE (End Connection Type) attributes set such that they match those of the Joints to which those ends are connected. This is done by setting CTYS/CTYE to a word which matches the Joint’s CTYA attribute in the Catalogue; see the Catalogues and Specifications User Guide. These attributes are set automatically when a Section is connected and you will not usually need to set them specifically.

Example:

CTYS BOLT

The Section’s start is to be connected to its attached Joint by means of bolts. (The CTYA of the Joint must also be set to BOLT for a compatible connection; see Part 3 of the DESIGN Reference Manual for information about data consistency checking.)

Command Syntax:

>- - +- - CTYSt ar t - - . | | ‘ - - CTYEnd - - - - +- - word - - > Querying:

Q CTYSt ar t Q CTYEnd

5.3.8

Star t an d En d Rel eas es 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 forces and 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 external forces are applied, namely: •

Linear movement along a specific axis (DX, DY, DZ)

•

Rotation about a specific axis (RX, RY, RZ)

2 5:8

12.0


Example:

SREL DX RX RY

The Start of the Section is constrained such that it can move only in the X direction and can rotate only about the X and Y axes.

Command Syntax:

>- - +- - SRELeas e - - . . - - - <- - - . | | / | ‘ - - ERELeas e - - +- - * - - DX - - - | | | | - - DY - - - | | | | - - DZ - - - | | | | - - RX - - - | | | | - - RY - - - | | | | - - RZ - - - | | | ‘ - - sign - - +- - > Querying:

Q SRELease Q ERELease

5.4

Creating and Positioning Secondary Nodes A Secondary Node is owned by, and positioned relative to, an existing Section. It enables you to position and connect another Section (an At tached Sect io n ) at any point along the length of the first Section (the Owning Section ), rather than having to define the position of the 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 in the Node’s ZDIST attribute, may be specified as an absolute length, as a proportion of the overall distance between POSS and POSE (i.e. a proportion of the derived length of the Section), or by reference to any marker (pin, p-point, p-line etc.), element or plane.

2 5:9

12.0


Example:

NEW SNOD / SNOD1 ZDI ST 1500 Creates a Secondary Node named /SNOD1 at ( At SCTN l evel ) the specified distance from the start of the Section. The Node is positioned on the Neutral Axis of the owning Section.

NEW SNOD / SNOD2 I S 1250 FROM END

The position of the new Node is measured from the POSE position rather than from the default reference of POSS.

NEW SNOD / SNOD4 ZDI S PROP . 33

The new Node is positioned one third of the way along the Section’s Neutral Axis, measured from the start of the Section.

NEW SNOD / SNOD3 ZDI S PROP 0. 25 FROM END

The new Node is positioned one quarter of the way along the Section’s Neutral Axis, measured from the end of the Section.

NEW SNODE / SNOD5 ZDI S PLANE W30N DI ST 0. 0

The new Node is positioned at the intersection of the owning section’s neutral axis with the defined plane.

Command Syntax:

>- - ZDI St ance - - +- | |-| | | | | | | | | -| ‘ --

- - - - - - - - - - - - - - . | PROPor t i on - - val ue - +- - FRom - - +- - STar t - - . | | | | | - - ENd - - - - | | | | | ‘ - - - - | | | ‘----------------------+ | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- >

Querying:

Q ZDI St ance

5.5

Cr eati ng an d Po si ti on in g Jo in ts Joints 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 its owning Node. A Secondary Joint (SJOI) is owned by a Secondary Node. Its position is derived from that of its owning Node, and thus, in turn, from the position of the Section which owns that Node.

2 5:10

12.0


A Compound Joint (PCOJ or SCOJ) is positioned relative to a Node, as for a PJOI or an SJOI, but all settings which define its connect ions are associated with subsidiary SubJoints owned 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 can carry out these operations independently and how you can modify the positions of Joints which have been created previously. A Joint is a Catalogue Component, which is selected in the design by setting its SPREF attribute to point to the required Component Specification.

5.5.1

Cr eat ing Pr im ar y Jo in ts Keywords:

NEW

PJOINT

Description:

A new Primary Joint can only be created at PNOD level.

Example:

NEW PJ OI / J OI NT1

Creates a new PJOI with a default position and orientation. The default position places the DELPOS (Delta Position) of the Joint at the NPOS of the Node. The default orientation directs the OPDI (Origin Plane Direction) of the Joint UP.

Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGN Reference Manual.

5.5.2

Cr eat in g Sec on dar y J oi nts Keywords:

NEW

SJOINT

Description:

A new Secondary Joint can only be created at SNOD level.

Example:

NEW SJ OI / SJ OI NT1

Creates a new SJOI with a default position and orientation. The default position places the POSL (Position Line) of the Joint through the owning SNOD.The default orientation directs the CUTP (Cutting Plane Direction) of the Joint Up.

2 5:11

12.0


Command Syntax:

The standard element creation syntax is described in Part 1 of the DESIGN Reference Manual.

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

Example:

SPRE / 10X10. BRAK90 (The .BRAK90 suffix in the Specification Component name would normally indicate that this represents a 90 degree bracket joint.) 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 following three attributes: •

The Delta Position (DELP) is the offset between the Joint’s Origin Plane and the position of its owning Node (the NPOS of the PNOD), expressed in the coordinate system which applies to the FRMW or SBFR. The default is a zero offset, so that the Joint’s Origin Plane passes through the owning Node.

•

The Origin Plane Direction (OPDI) is the direction of the normal to the plane through the 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 Plane Direction, measured clockwise as viewed along that direction. The default setting is zero, so that the Joint’s orientation is as defined by its Catalogue representation.

2 5:12

12.0


BAN

de ines orientation about Z axis OPDI defines orientation about X,Y axes

Z Y X

DZ DY

DELP defines X,Y,Z offset relative to PNode

DX

PNode

NPOS defines X,Y,Z coords of PNode

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 Plane points North.

BANG 180

otates the Joint about its current Origin Plane Direction by 180 degrees.

Command Syntax:

>- - - DELPosi t i on - - - - - - > >- - - OPDI r ect i on - - - - - - > >- - - BANGl e - - - +- - - value - - - - - - - - - - - - - - - - - - - - - - - - - - - . | | ‘ - - - - - - TOwar ds - - - - - - +- > Querying:

Q DELPosi t i on Q OPDI r ect i on Q BANGl e

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 owning Secondary Node. The position of this Node is separately defined with respect to its owning Section, as described Creating and Positioning Secondary Nodes . The Joint’s position with respect to the Section depends, therefore, upon the settings of two attributes: •

The Z-axis Distance (ZDIST) attribute of the owning SNOD.

2 5:13

12.0


•

The Positioning Line (POSL) attribute of the SJOI itself. This defines the position of the Joint in relation to the p-line system which has been set up for the owning Section’s Profile within the Catalogue. The default POSL setting is NA (Neutral Axis), so that the Joint’s Origin (more strictly, its JLIN) lies on the Section’s Neutral Axis at the position specified by the ZDIST: that is, the Joint’s Origin is coincident with the position of its owning SNOD.

The Beta Angle (BANG) specifies the angular rotation of the Joint about its Origin Plane Direction. The default setting is zero, so that the Joint’s orientation is as defined by its Catalogue representation.

BANG defines orientation about Z axis Z

OPDI defines orientation about X,Y axes

Y X

POSL (here set to TOS) defines position

Owning Section (2D view only)

TOS NA

SNode

BOS ZDIST defines position of SNode relative to POSS of Sectio

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.

Command Syntax:

>- - POSLi ne word - - > where word is usually one of the following:

NA

(Neutral Axis)

TOS

(Top of Steel)

BOS

(Bottom of Steel)

>- - BANGl e - - +- - value - - - - - - - - - - - - - - - - - - . | | ‘ - - TOwar ds - - +- - >

2 5:14

12.0


Querying:

5.6

Q POSLi ne

(At the SJOI)

Q ZDI STance

(At the SNOD)

Q BANGl e

(At the SJOI)

A tt rib utes o f Co nn ect ed Jo in ts The attributes and their settings described in Creating and Positioning Joints are applicable to 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 an At tac hed Section) have other relevant attributes set. These are described in this section.

5.6.1

Con nect ion Ref er en ce Keywords:

CREFerence Description:

The Connection Reference attribute (CREF) of a Joint points to the identifier of the Attached Section. This attribute is set automatically when a Section is connected and you will not usually need to set it specifically.

Examples:

CREF / BEAM1 START

Sets Connection Reference to start of n amed 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.

Command Syntax:

>- - CREFer ence - - +- - - - +- - STar t * - - . | | | | | - - - ENd - - - - | | | | | ‘------------+ | | ‘ - - - NULr ef - - - - - - - - - - - - - - +- - > where identifies the Section to be connected.

2 5:15

12.0


Querying:

Q CREFer ence

5.6.2

Cutting Plane Keywords:

CUTPlane Description:

The position of a Joint which has an Attached Section is derived from the intersection of the Attached Section’s Joining Line (JLIN) and the Joint’s Cutting Plane. The Cutting Plane Direction, that is the direction of the normal to the Cutting Plane, is defined by the setting of the 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).

Example:

CUTP N45D

The normal to the Cutting Plane points in the specified direction.

CUTP PERP

The normal to the Cutting Plane is set perpendicular to the Joint’s Origin Plane.

Command Syntax:

>- - CUTPl ane - - +- - - - - - - - - - - . | | ‘ - - PERPendi cul ar - - +- - > Querying:

Q CUTP

5.6.3

Cut back Allowance Keywords:

CUTBack Description:

The derived length of an attached Section is, unless otherwise specified, the distance between the Cutting Planes of the Joints at its two ends. The CUTB attribute allows you to specify a length by which the Section should be shortened or extended to allow for any local fitting geometry at the Joint’s attachment point (to allow for weld metal, packing pieces et c.). A positive value of CUTB shortens the derived length of a Section attached to the Joint; a negative CUTB lengthens the attached Section. The d efault is a CUTB setting of zero.

2 5:16

12.0


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.

Command Syntax:

>- - CUTBack - - > Querying:

Q CUTBack

5.7

Man ual ly Co nn ect in g Sec ti on s This section describes the commands which allow you to connect Sections and Joints ‘manually’; that is, without using the STRING command. The relevant Nodes and Joints must 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 you can modify existing interconnected structural designs.

5.7.1

Con nec ti ng Sect ion s 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. This requires 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 be aligned with the Section, if possible (but see the FREE option, below). When the connection is made, the connection cross-references between the Section and the Joint are set. That is, the JOIS/JOIE of the Section and the CREF of the Joint are matched. Further, the relevant Connection Type attribute of the Section (CTYS or CTYE) is set 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/or POSE 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 be displaced (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 new Cutting Plane which passes through the end of the Joint’s JLIN.

2 5:17

12.0


The RECALCULATE option causes the positions of elements which are members of a Section 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 if the POSS (from which ZDIS is measured) were moved as a result of a CONNECT command, so that the SNOD remained unmoved. If both RECALCULATE and FREE are specified, the position of FITTINGs and SNODEs along the section are recalculated to be as close as possible to their original positions.

Example:

CONN END TO / SJ OI NT3

Where the current element is a Section.

CONN WI TH START OF / BEAM1

Where the current element is a Joint.

CONN START TO / PJ OI N2 RECALC

Connects the start of the current Section without moving the positions of any secondary elements owned by the Section.

Command Syntax:

At Section level:

>- CONnect - +- STar t - . | | ‘ - ENd - - - +- FREE - . | | ‘ - - - - - - - - +- TO

- +- RECALCul at e - . | | ‘ - - - - - - - - - - - - - - - +- >

where identifies a Joint. At Joint level:

>- - CONnect WI TH - - +- - STar t - - . | | ‘ - - ENd - - - - +- - OF

- - >

where identifies a Section.

5.7.2

Di sco nn ec ti ng Sec ti ons Keywords:

DISCONNECT

START

END

RECALCULATE

Description:

When a Section is disconnected, the connection cross-references (JOIS/JOIE - CREF) are unset and the connection type cross-references (CTYS/CTYE ) are set to Nulref. The position and length of the Section are not changed, but the Joint (if moved during the connection operation) is returned to its default position. The RECALCULATE option causes the positions of elements which are members of a Section to be recalculated so that they remain in the same positions if the Section is moved.

2 5:18

12.0


For example, the ZDIST defining the position of a Secondary Node would be recalculated if the POSS (from which ZDIST is measured) were moved as a result of a DISCONNECT command, so that the SNOD remained unmoved.

Example:

DI SCO START

Disconnects the start of the current Section.

DI SCO END

Disconnects the end of the current Section.

DI SCO

Disconnects both the start and end of the current Section.

DI SCO END RECALC

Disconnects the end of the current Section, but retains the positions of any secondary elements owned by the Section.

Command Syntax:

>- - DI SConnect - - +- - STar t - - . | | | - - ENd - - - - | | | ‘ - - - - - - - - - - - +- - RECALCul at e - - . | | ‘ - - - - - - - - - - - - - - - - - +- - >

5.7.3

Rec on nec ti ng Sect ion s Keywords:

RECONNECT

START

END

RECALCULATE

Description:

The RECONNECT command would typically be used to reconnect a disconnected Section in the following circumstances: •

Following the movement of a Joint: the attached Section is moved to the new Joint position.

•

Following the resetting of a cutback allowance at a Joint (see Cutback Allowance ): the length 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 an existing Section.

In each case the RECONNECT command attempts to restore the consistency of the connected model. The RECALCULATE option causes the positions of elements which are members of a Section 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 if the POSS (from which ZDIST is measured) were moved as a result of a RECONNECT command, so that the SNOD remained unmoved.

2 5:19

12.0


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.

Command Syntax:

>- - RECOnnect - - +- - STar t - - . | | | - - ENd - - - - | | | ‘ - - - - - - - - - - - +- - RECALCul at e - - . | | ‘ - - - - - - - - - - - - - - - - - +- - >

5.8

Repositioning Steelwork Elements The concept of connectivity in structural steelwork influences the types of repositioning operations which are allowed. Repositioning operations using the standard DESIGN commands will also move items whose positions depend on those of the items being direc tly moved.

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 steelwork Section, effectively reversing its orientation. This is mainly of use for reorientating a Section with a non-symmetrical profile if you have mistakenly strung it the wrong way round. It is best 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 you can do so if you fully understand the effects outlined below. These effects may not give the results you had intended and may therefore require further design modifications to be made:

The settings of the SREL and EREL (Start and End Release) attributes are not exchanged. Since, however, the ends to which they refer have changed (since the original Start is now the End, and vice versa), their effects will be reversed in the physical model.

2 5:20

12.0


•

The Member List of the Flipped Section remains unchanged, so that any crossreferences to member elements by list position remain correct. The ZDIST attributes of any SNODs, FITTINGs, etc. remain the same, so that their positions are now derived from the opposite end of the Section (the new Start end), thereby causing these member elements to move.

•

Any Connected items referenced via SJOIs will not move, since the positions of the corresponding SJOIs will not move to the new SNOD positions until they are Disconnected. If you wish to reverse a Section with existing secondary connections you 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 that they are repositioned where you want them).

•

Reconnect the Flipped Section to all the attached Sections.

Example:

FLI P

Reverses the Start and End attribute settings for the current element as outlined in the preceding description.

Command Syntax:

>- - - FLI P - - - > Querying:

You may find the following querying commands, used both before and after giving the FLIP command, helpful in checking the precise effects of the command:

5.8.2

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.

Mo vi ng St eel wo rk El em en ts Note: 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 possible for all structural elements which have a directly defined location in the 3D model; for example, Frameworks, Subframeworks, Primary Joints and Nodes (but not Secondary Joints and Nodes, whose positions are dependent on that of a Section), Routing Planes, Panels, etc.

2 5:21

12.0


Absolute positioning (AT command) is possible only for Sections, Primary Nodes, Routing Planes and Panels.

Example:

MOVE ALONG E45N DI STANCE 500

Moves Current Element in specified direction by specified distance.

BY N1000 E5000 U7000 Moves Current Element as specified relative to its current position.

AT E2000 N2000 U1000 Moves the Current Element to the specified position. In the case of a Section, POSS is set to this position; in the case of a Primary Node, NPOS is set to this position.

5.8.3

Mo di fy in g L en gt hs o f Sec ti on s Keywords:

EXTEND

START

END

PROPORTIONAL

RECALCULATE

Description:

Once positioned, a Section may have its ends repositioned independently by using the EXTEND command. This effectively lengthens or shortens the Section by a specified amount and resets its POSS and/or POSE attributes accordingly. (You could, of course, set POSS and/or POSE directly, as described in Start and End Positions, but this would need prior 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 a proportion of the current length of the Section. The allows you to define the amount of extension required by intersecting the neutral 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 the modified Section to be recalculated so that they remain in the same positions after the change. For example, the ZDIST defining the position of a Secondary Node would be recalculated if the POSS (from which ZDIST is measured) were moved by the EXTEND command, so that the SNOD remained unmoved.

Example:

EXTEND END BY E1000

Move POSE by 1000mm Eastward.

EXTEND BY E1000

As above (defaults to END).

EXTEND START BY W1000 RECALC

Move POSS by 1000mm Westward and recalculate the positions of all member SNODs, FITTs etc. so that they remain unmoved.

2 5:22

12.0


Example:

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 by 1750mm (default units).

EXTEND - 1750

Move POSE (defaults to END) so as to decrease the Section’s length by 1750mm (default units).

EXTEND START PROP 0. 25 Move POSS so as to increase the Section’s current length by 25%.

EXTEND PROP - 0. 2

Moves POSE (defaults to END) so as to decrease the Section’s length by 20%.

EXTEND END PLANE E30N DI ST 0. 0

Moves POSE to meet the defined plane.

Command Syntax:

>- - EXTend - - +- STar t - . | | | - - ENd* - | | | ‘ - - - - - - - - - +| || | || ‘-

5.8.4

PROPor t i onal - value - . | BY - - - - - - - - - | | | - - - - - - - - - - - - - | | - - - - - - - - - - - - - - +- RECAL Cul at e - - . | | ‘ - - - - - - - - - - - - - - - - +- >

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 was described in Orientation Angle. This section explains the use of the ROTATE command to achieve a greater range of reorientating effects on Sections and on other steelwork elements. 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 direction and/or through point. If the direction and/or through point are omitted, the default

2 5:23

12.0


direction is that of the Neutral Axis or Z axis; the default through point is the Origin or Start Position (depending on the type of element involved).

•

By reference to the component’s axes or p-lines.

Example:

ROTATE BY - 45

Rotates by 45° about the element’s Neutral Axis or Z axis (anticlockwise when looking from Start to End or in the +Z direction, since the rotation is specified as a negative angle).

ROTATE BY 45 ABOUT E

Rotates by 45° about the (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 which passes in the N-S direction through its End position. The rotation is 25° anticlockwise when looking S along this axis.

ROT ABOUT PPLI N TOS BY 45

Rotates by 45° about the Top-of-Steel p-line (clockwise when looking in the Start to End direction).

ROT AND PPLI N BOS I S E45N

Rotates element about its Neutral Axis until the Bottom-of-Steel p-line points as closely as possible to the E45N direction.

ROTATE AND Y I S N45W25D

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

ROT AND PPLI N TOS I S PPLI N BOS OF / SCTN1 LEAV DI R WRT / STRU1

Rotates element until its TOS p-line points in the direction of the BOS p-line of / SCTN1 in the specified coordinate system.

E-W

axis

Command Syntax: Rotation about a given axis: >- ROTat e ABOut - +- - . | | ‘ - -+- THRough - - +- BY - +- - - - - - - - - - - - - - - - - - - - . | | | | | | ‘ - TOwar ds - - - | | | | | ‘ - AND - +- - . | | | | | | ‘ - - +- I S - - - - | | | | - BY - +- - - - - - - - - - - - - - - - - - - - - . | | | | | | ‘ - - TOwar ds - - + | | | | ‘ - AND - +- - . | | | | | | ‘ - - +- I S - - - - - +- THRough - | | | ‘ - - - - - - - - - - - - - - - - - - +- - >

2 5:24

12.0


Rotation to pass thro ugh a given point: >- ROTat e THRough - - +- ABOut - +- - . | | | | ‘ - - +- BY - +- - - - - - - - - - - - - - - - - - - - - - - - . | | | | | | ‘ - - TOwar ds - - - - - | | | | | ‘ - AND - +- - . | | | | | | ‘ - - +- I S - - - - - - - | | | | - BY - +- - - - - - - - - - - - - - - - - - - - - . | | | | | | ‘ - - TOwards - - +- ABOut - +- - . | | | | | | | | ‘ - - +- - | | | | | ‘-----------------------| | | ‘ - AND - +- - . | | | | ‘ - - +- I S - - +- ABOut - +- - . | | | | | | ‘ - - +- - - - | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - +- >

Rotation b y a specified amount: >- ROTat e BY - - +- - - - - - - - - - - - - - - - - - - - - . | | ‘ - - TOwar ds - - +- ABOut - +- - . | | | | ‘ - - +- T HRough - - - - . | | | | ‘----------------------| | | | - THRough - - +- ABOut - +- - . | | | | | | | | ‘ - - +- | | | | | ‘----------------------| | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- >

Rotation to give a specified orientation: >- ROTat e AND - +- - . | | ‘ - - +- I S - - +- ABOut - +- - . | | | | ‘ - - +- THRough - - - - - . | | | | ‘-----------------------| | | | - THRough - - +- ABOut - +- - . | | | | | | | | ‘ - - +- - | | | | | ‘-----------------------| | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- - >

Note: In each of the preceding diagrams identifies a specific p-line.

5.9

Positioning and Orientating Using P-lines P-lines in a 3D structure represent lines, derived from points defined in the Catalogue for corresponding 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 of profiles 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 3D geometry (as derived in the design model) for positioning or orientating the element itself, or for defining some other geometry relative to the element. Positions may be defined along the length of a p-line; directions may be defined in terms of a p-line’s coordinate axes (the pline direction being, by default, along its +Z axis).

2 5:25

12.0


Some examples have already been introduced in the earlier sections of this chapter. This section further illustrates the possible uses of such techniques. Z

Z Y

PLIN NA

X

Y

POSE

X SITE axes

SCTN axes

Y Z

Y TOS axes X

X

BOS axes

PLIN TOS

Z POSS

Figure 5:1.

5.9.1

PLIN BOS

Typical P-lines and Axes for a Section

Id en ti fyi ng P-l in es 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.

Example:

PPLI NE TOS

Specifies the Top-of-Steel p-line of the current element.

PPLI NE BOS OF / BEAM2 Specifies the Bottom-of-Steel p-line of /BEAM2. I DPLI NE @

Specifies the p-line to be picked using the cursor.

Command Syntax:

(This is the syntax referred t o elsewhere in this manual.)

>- - +- - PPLI Ne - - word - - +- - OF

2 5:26

- - .

12.0


| | | | ‘---------------+ | | ‘ - - - I DPLi ne - - @ - - - - - - - - - - - - - - - - - - - - - - +- - > where word is the setting of the p-line’s PKEY attribute, as defined in the Catalogue; for example: TOS (Top of Steel), BOS (Bottom of Steel), NA (Neutral Axis), NF (Near Face), FF (Far Face), etc.

5.9.2

Po si ti on in g b y Us in g P-l in es 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:

POSI TI ON PPLI NE BOS 500

Calculated position is on the BOS p-line, 500mm from its start (by default); for setting a variable or for querying.

POS PPLI N TOS 1000 FROM END

Calculated position is on the TOS p-line, 1000mm from its end.

POS AT PPLI N NA OF / SCTN2 PROP . 25

Calculated position is on the Neutral Axis of /SCTN2, 25% along its length as measured from its start (by default).

POS AT PPLI N TOS OF / BEAM1 END

Position is defined as the end of the TOS p-line of / BEAM1 (probably, but not necessarily, the POSE setting for /BEAM1).

BY PPLI N TOS OFFSET FROM PPLI N BOS

Moves the current element (Section or Joint) by the offset distance between its TOS and BOS p-lines.

BY PPLI N BOS OFFSET FROM PPLI N TOS

Moves the same distance as the preceding example, but in the opposite direction.

BY PPLI N TOS - OFFSET FROM PPLI N BOS

The same effect as the preceding example.

2 5:27

12.0


Command Syntax: Note: The following syntax describes only the p-line referencing options for defining a position. These are in addition to the positioning/moving syntax described in Equipment and Primitives, which also apply to Structural steelwork elements.

Defining a specific position:

>- - +- - - - - - - - - - - - - - . | | | - PROPor t i on - value - +- - - - - - - - - - - - - - - - - - - - - - . | | | | ‘ - FROm - . | | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- STar t * - . | | | | ‘ - ENd - - - - +- - +- > Defining a distance as the offset between two p-lines:

>- - - - +- - sign - - . | | ‘ - - - - - - - - - - +- - OFFSet FROm - - > where , which identifies a specific p-line, is defined in Identifying P-lines. Querying:

Q - - +- - - - - - - - - - - - - - - - . | | | - - PROPor t i on - val ue - - +- - - - - - - - - - - - - - - - - - - - - - - - - - . | | | | ‘ - - FROm - - . | | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- - STar t * - - . | | | | ‘ - - ENd - - - - - +- - +- - > Q - - OFFSet - - +- - FROm - - - - . | | ‘ - - - - - - - - - - - - - - - - - - - - +- - > Querying Examples:

Q PPLI N TOS END

Position of end of p-line.

Q PPLI N BOS PROP 0. 3

Position of point 30% of distance along BOS from start (by default) towards end.

Q PPLI N NA PROP - 1. 5 FROM END

Position of point which is 1.5 times length of Neutral Axis away from end of p-line in direction away from start.

Q PPLI N TOS OFFS FROM Offset distance between TOS and BOS. PPLI N BOS Q PPLI N TOS OFFS

Offset distance between TOS and Neutral Axis (by default).

2 5:28

12.0


5.9.3

Or ien tat in g by Us in g P-l in es Keywords:

PPLINE

DIRECTION

X

Y

Z

LEAVE

Description:

You can orientate a structural element by referring its axes to the directions of one or more p-lines. By default, references will be taken from the Z (or LEAVE) direction.

Example:

ORI Y I S PPLI N TOS OF / SCTN1 X DI R AND Z I S U

Orientates the current element such that its Y axis points in the X direction of the TOS p-line of /SCTN1 and its Z axis points Up. If, for example, the X direction of the TOS p-line of / SCTN1 points East, then this command line is equivalent to ORI Y IS E AND Z IS U.

Command Syntax:

>- - - - +- - X - - - - - - . | | |-- Y ---- -- | | | |-- Z -- -- -- | | | | - - LEAve - - | | | ‘ - - - - - - - - - - - +- - DI Rect i on - - > Querying:

Q - - +- - X - - - - - - . | | |-- Y ---- -- | | | |-- Z -- -- -- | | | | - - LEAve - - | | | ‘ - - - - - - - - - - - +- - DI Rect i on - - >

5.10

Creating and Connecting Panels

5.10.1

Creating a Panel A Panel (PANE) element represents any sheet material used to clad a structural model. The geometry of a Panel is defined by a subsidiary Panel Loo p (PLOO) element. The 2D shape of 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 thus formed defines the shape of the Panel in the same way that a Profile defines the crosssectional area of a Section. The Height (HEIG) attribute of the PLOO defines the distance

2 5:29

12.0


through which this 2D shape is extruded to form the 3D Panel; that is, it defines the Panel thickness, thus:

= Panel Loop (PLOO) HEIG of PLOO

= Panel Vertex (PAVE)

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 zero denotes a point. To define a new Panel, you must, therefore, first create a PANE element (using NEW PANE etc.), then create a PLOO below it in the hierarchy, and then create and position as many member PAVEs as necessary to define the shape of the PLOO and thus the PANE. (The Z co-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 is split into two or more new Panels which have same owner as the original one. More than one 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 new vertices are created where the intersection line crosses the edges of the original Panel.

Example:

SPLI T PLANE N THRO Splits current panel along its line of intersection with the N1000 specified plane SPLI T ON / BEAM1

Splits current panel along the Neutral Axis (projected if necessary) of the named section

Command Syntax:

>- - SPLI T - - +- - PLANE - - THROugh - - . | | ‘ - - ON - - - - - - - - - - - - - - - - +- - >

2 5:30

12.0


5.10.3

Connecting Panels using Linear Joints Linear joints are used to connect structural items along edges or faces. They effectively have linear (2D) connectivity, whereas Primary and Secondary Joints have only point (1D) connectivity (even though they have 3D geometry). A Panel Linear Join t ( PALJ ), owned by a PANE, FRMW or SBFR, is used to connect two Panels 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 the linear joint, thus:

*

*

PANE1

MVERT attribute of PAVE points to PAVE of PALJ

*

PALJ

*

= PALJ (owned by PANE1)

PANE2

= PAVE (PLOO of PANE1)

*

= PAVE (owned by PALJ)

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 a Section. 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 linear joint, thus:

*

*

PANE *

MVERT attribute of PAVE points to SEVE of SELJ

SELJ

*

SCTN

= SELJ (owned by SCTN) *

= PAVE (PLOO of PANE) = SEVE (owned by SELJ)

Keywords:

LINK

UNLINK

2 5:31

12.0


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 the vertices of the item linked to (which define the properties at the connection point) are defined as master vertices . When you link a panel, any new panel vertices needed will be created automatically to correspond with the master vertices of the item connected to. You can specify the position and direction of creation of the new vertices in the Panel Loop’s vertex sequence as part of the command. If the panel has no PLOOP, one will be created automatically. UNLINK unsets the connection cross-references created by a LINK command.

Example:

LI NK VERT CE TO / PAVE2 Links current vertex (slave) to vertex /PAVE2 (master). LI NK 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.

Command Syntax: >- L I NK - +- +- - - - - - - - - - . | | | | ‘ - VERTex - +- - TO - VERTex - - - - - - - - - - - - - - . | | | - - - EDGE - - TO - EDGE - - - - - - - - - - - - - - - - - - - - | | | ‘ - - - PANEl - - TO - +- J OI Nt - - - - - - | | | | - VERTex - - . | | | | ‘ - EDGE - - - - +- - +- >

where:

is a vertex identifier (name, refno, treename)

is a list of vertex identifiers

is an edge identifier (pair of consecutive vids)

is a list of edge identifiers (must be an even number of vids)

is a panel identifier (name, refno, treename)

is a joint identifier (name, refno, treename)

2 5:32

12.0


: >- +- FROM - +- START - TO - +- - . | | | - END - - - | | | ‘ - - - - - - - - - +- - . | | - END - TO - - - +- - . | | | | - START - | | | | ‘ - - - - - - - - - +- - | | | - - TO - +- - . | | | | - START - | | | | | - END - - - | | | | ‘ - - - - - - - - - +- - | | ‘ - -- -- -- -- -- -- -- -- -- -- -- -- -- | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +- FORWar ds - - . ‘ - BACKwards - +- AFTer - - - - - - - - - . | - BEFore - - - - - - - - | | - BETween - | ‘ - - - - - - - - - - - - - - - - - - - - - - - +- >

The FROM/TO options specify which portion of the joint is to be linked to the panel. Defaults are 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 to create vertices corresponding to those of the joint (master vertices). : >- - +- - AFTer - - - - - - - - - - . | | | - - BEFor e - - - - - - - - - | | | | - - BETween - - | | | ‘ - - - - - - - - - - - - - - - - - - - - - - - - - +- >

The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loop at which to create vertices corresponding to those of the master vertices. >- - UNLI NK - - +- - - - FRom - - - - . | | ‘ - - ALL - - - - - - - - - - - - - - - - - - - - - +- - >

Querying:

Q LI NKS

Queries connection references between vertices

5.11

Fittings, Hangers and Equipment Load Points

5.11.1

Fittings and Panel Fittings A Fitting (FITT) element allows you to indicate a connected implied load, such as a pipe hanger 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 the SCTN at a point defined by the ZDIST attribute (in the same way as for a SNOD). The Fitting may be geometrically modelled in the Catalogue, and selected from the Catalogue, in a similar way to a Joint, as described in Creating and Positioning Joints .

2 5:33

12.0


A Panel Fittin g (PFIT) element serves a similar function to a FITT, but is owned by a Panel and positioned relative to the Panel’s origin. A Cofitting (COFI) element is used where a fitting spans the junction between two or more Panels. In the latter case, one of the Panels owns a PFIT while the others each own a COFI. Each COFI has its Panel Fitting Reference (PFRE) attribute set to point to the associated PFIT; the PFIT has its Cofitting Reference Array (CFRA) attribute set to point to the COFIs.

5.11.2

Structure-to-Pipework Connections Piping 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 Structure and the Head or Tail Reference (HREF/TREF) of a Hanger on the Pipework. A Fitting may be regarded, therefore, as the Structural equivalent of an Attachment Point (ATTA) in Pipework design. For connection type compatibility, the Connection Type attribute (CTYA) of the Fitting must match the Connection Type (HCON/TCON) of the Hanger.

5.11.3

Structure-to-Equipment Connections Equipment models may be linked logically to the Structural model by means of crossreferences between the Connection Reference (CREF) attribute of a Fitting on the Structure and the Connection Reference (CREF) of a Load Point (LOAP) element owned by the Equipment. A Load Point has a position within the Equipment model, but no size or orientation. It behaves in this respect like a Node in the Structural model. If an Equipment is moved, any member Load Points which point to Fittings in a Structure will not move, their positions being constrained 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 a Specification Reference (Sections, Joints, Fittings etc.), each of which may store up to 100 real values. They may be used to transfer design data to a corresponding Catalogue component, 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 the dimensions of the Section(s) to which it is attached, rather than from preset dimensions defined for it in the Catalogue. A DESP is referenced in the design by its numbered position in the array. Its value must be set before the corresponding component is selected from the Catalogue, so that the required setting is available within the design.

2 5:34

12.0


Example:

DESP 2. 5 7

Sets first two design parameters to 2.5 and 7 respectively.

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,Z coordinates (respectively) of POSS of element / SCTN1.

Note: In the last example, a range of three design parameters, needed to hold the coordinates of the defined point, was set automatically, starting with the specified third parameter. Command Syntax:

Setting parameters in default order in the array, starting at parameter number 1:

. - - - - - - - - - - - - - - <- - - - - - - - - - - - . / | >- - DESPar amet er s - - +- - - - - - - - - - - - - - - - - - - | | | | - - - - - - - - - - - - - - - - - - - - - | | | | - - READ - - - - - - - - - - - - - - - - - - - - - | | | ‘ - - wor d - - +- - OF - - - - | | | ‘ - - - - - - - - - - - - - - - - - - +- - > Setting individually specified parameters within the array:

. - - - - - - - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - - - - - - - . / | >- DESPar amet er s - *- Number - i nt eger - +- - - - - - - - - - - - - | | | | - - - - - - - - - - - - - - - | | | | - READ - - - - - - - - - - - - - - - - | | | ‘ - wor d - +- OF - - | | | ‘ - - - - - - - - - - - - - - +- > Querying:

. - - - - - - - - - - - - - - <- - - - - - - - - - - - - - - - . / | Q - - *- - DESPar amet er s - integer - - - - - +- - - >

2 5:35

12.0


Querying Examples:

5.12.2

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.

FI NCH DI ST Q ( DDESP[ 2] )

Extracts a distance (in feet and inches) from within DESP 2.

Setting Owning and Attached Parameters Owning and attached parameters (OPAR and APAR, respectively) are real-array attributes of Joints. They are set in the Catalogue, and allow the Joint to derive data (usually dimensions) 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 these arrays. As with the design parameters described in Setting DESIGN Parameters, an OPAR or APAR is referenced in the design by means of its numbered position in the corresponding array.

5.13

Representing Curved Beams and Walls

5.13.1

Overview Curved structural items are represented by Generic Section (GENSEC) elements, the geometry of which is defined by sweeping a 2D catalogue profile along a path. This path is represented by a Spine element, owned by the GENSEC, whose route is specified in terms of a sequence of member Spine Points (POINSP) and, optionally, Curves . For example:

End POINSP CURVE

PROFILE

CURVE = SPINE

Start POINSP

= POINSP

There are six types of Curve, defined by setting the CURTYP (Curve Type) attribute, which govern the way in which the shape of the curve is specified. The options are: LINE A straight line (this is the default)

2 5:36

12.0


RADI A circular arc, defined by a radius and a conditioning point. THRU An arc passing through a specified through-point position. BULG An arc defined by a bulge factor and a conditioning point. FILL A fillet arc and two adjacent straights, defined by a radius and a pole position. CENT A fillet arc and two adjacent straights, defined by a circle centre point, a radius and a conditioning 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 the POSS of the Section); the last POINSP defines its end position (equivalent to the POSE of the Section). Items connected to a GENSEC are positioned and orientated relative to a set of p-lines which follow the same path as that defined by the GENSEC’s Spine; that is, the p-lines may be curved. These p-lines are referenced by attached items via Justification Line Datum (JLDATUM) and P-line Datum (PLDATUM) elements, which define the frames of reference to 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 of which is defined by reference to catalogue items. Fixings can own other Fixings, so that although they behave somewhat like the more restrictive Fitting and Joint elements, they are 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 its shape. The Spine must own at least two Spine Points, defining its start and end positions. It can 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 catalogue profile. GENSEC now has defined cross-section, but no geometry defining its path.

NEW SPI NE

Creates Spine with no defined path.

2 5:37

12.0


Example:

NEW POI NSP

First Spine Point defines Start Position (POSS).

NEW POI NSP

Last Spine Point defines End Position (POSE). Spine at this stage is a straight line.

The attributes of this curve determine the shape of NEW CURVE ( Cr eat ed between POI NSPs) the Spine path between the adjacent POINSPs. (See More About Curve Types .)

5.13.3

More About Curve Types The ways in which the various types of Curve are specified are as follows: •

CURTYP = LINE Specifies a straight line between the adjacent POINSPs. This is the default if curved geometry is not defined between two POINSP elements.

•

CURTYP = RADI Specifies a single circular arc between adjacent POINSP elements. The arc is defined by the RADI (radius) and CPOS (conditioning point) attributes. The conditioning point and the preceding and following points define the plane of the arc. The choice of minor or 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 calculated such that the curve is a semicircle between the adjacent POINSPs.

•

CURTYP = THRU Specifies a single circular arc. The arc is defined by the POS attribute, which is interpreted as a through-point on the curve. The through-point and the preceding and following points define the plane of the arc.

•

CURTYP = BULG

Specifies 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 following points define the plane of the arc. The choice of minor or major arc is governed by the size of the bulge factor. The sign of the bulge factor determines whether the arc curves towards the conditioning point (positive bulge factor) or away from the conditioning point (negative bulge factor). •

CURTYP = FILL Specifies a combination of an arc and up to two straights. The curve is defined by the RADI (radius) and POS attributes, where the POS setting is interpreted as the pole point of the arc (the intersection of the two end tangents). The pole point and the preceding and following points define the plane of the arc. If RADS = false, the specified radius is ignored and the maximum radius that will fit into the pole is calculated; an endpoint triangle ensures that the fillet terminates on at least one of the end points.

•

CURTYP = CENT Specifies a combination of an arc and up to two straights. The curve is defined by the RADI (radius), CPOS (conditioning point) and POS attributes, where the POS setting is interpreted as the circle centre point. The centre point and the preceding and following points define the plane of the arc. The choice of minor or major arc is governed by the arc which approaches closest to the conditioning point; the conditioning point need not lie in the plane of the arc. If RADS = false, the specified radius is ignored and the maximum radius is calculated to ensure that the nearest POINSP to the circle lies on the circle; the arc terminates on this point.

2 5:38

12.0


Note: Displayed GENSECs treat each segment of the Spine as a separate extrusion. At the vertices between segments, i.e. at the POINSP positions, these extrusions merge together if there is a tangent continuity. If there is a tangent discontinuity, the extrusions are mitred along a plane normal to the mean of the two tangent vectors at the POINSP position.

5.13.4

How P-lines Are Used For Generic Sections P-lines defined in the Pointset of the Section Profile (as referenced by the SpecRef) follow the path defined by the GENSEC’s Spine. This means that, for a curved GENSEC, the p-line directions are not constant over their lengths. This must be taken into consideration when using them as datums referenced by attached items. The command syntax used for referencing p-lines for SCTNs, as detailed in Positioning and Orientating Using P-lines , is extended when applied to GENSECS. The additional command options available are summarised here. Position s Derived From P-lines (see Positioning by Using P-lines):

The distance value along the p-line may be preceded by the keyword DISTANCE. For example:

PPLI NE TOS DI STANCE distance FROM END . . . The position along the p-line may be measured from the plane normal to the end of the GENSEC, from the cutback plane, or fr om the joint end preparation cutback. For example:

PPLI NE TOS OF / BEAM1 NORMAL . . . PPLI NE TOS OF / BEAM1 NOCUTBACK . . . PPLI NE TOS OF / BEAM1 CUTBACK . . . It is possible to define a proportional and an absolute distance position at the same time. For example:

PPLI NE TOS PROPORTI ON value DI STANCE distance . . . Positions may be measured along the actual p-line specified, or along the Spine and then projected onto the p-line. For example:

PPLI NE TOS distance VI A SPI NE FROM END . . . PPLI NE TOS PROPORTI ON value VI A PLI NE . . . The element specified by the OF keyword may be a POINSP or a CURVE. This redefines the element to be the GENSEC owning the POINSP or CURVE, rather than the current element or an element defined with the p-line choice. This sets: •

the direction along which DISTANCE and PROPORTION are to 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:

PPLI NE TOS PROPORTI ON 0. 4 FROM END VI A SPI NE 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 the GENSEC.

2 5:39

12.0


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 the direction/offset option and before the OF option. This lets you specify the position along the p-line at which the direction/offset is to be calculated. For example:

PPLI NE TOS X DI RECTI ON PROP 0. 4 VI A PLI NE FROM END OF / CURVE3 PPLI NE TOS OFFSET FROM PPLI NE BOS DI STANCE 200 FROM END If no position is given, the direction/offset is calculated using the start of the GENSEC or element specified by the OF option. Picked Positions on P-lines:

The following syntax lets you derive a position on a p-line which is nearest to a probe line:

PPLI NE pline_name NORMAL/ CUTBACK NEAR direction THROUGH position [ VI A SPI NE/ PLI NE] BOUND/ UNBOUND The probe line starts at the THROUGH position and extends in the specified direction. The expression returns the nearest point on PLINE pline_name. If BOUND is set, the point is either on the p-line or at the ends (where it intersects the NORMAL or CUTBACK end of the GENSEC). If UNBOUND is set, the point can be on the tangential extension of the p-line. The point returned will be in or above the plane through the THROUGH position, normal to the 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 the p-line from the start of the segment. If pline_name is specified as ANY, all plines of the GENSEC will be probed and the closest p-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:

I D SEGMENT PPLI NE . . . positioning_command I D ONPLI NE PPLI NE . . . positioning_command ID SEGMENT returns the identity of the POINSP at the start of the segment on which the specified position occurs. ID ONPLINE returns the identity of the p-line on which the specified position occurs. (The latter is only useful for the PPLINE ANY option, otherwise it simply returns the identity of the specified p-line.) The following expressions use keywords analogous to the OFFSET option between the pline specification and the subsequent positioning command:

PPLI NE pline_name PLDI ST positioning_command PPLI NE pline_name PLKEY positioning_command PPLI NE pline_name SEGMENT positioning_command PPLI NE pline_name ONPLI NE 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 along the segment on which the point lies, in the direction specified in the positioning_command (FROM START or FROM END). PPLINE...PLKEY returns the n ame (the PKEY) of the p-line on which the point lies.

2 5:40

12.0


5.13.5

Positioning Items Relative to Generic Sections A GENSEC cannot own Fixings directly, but only via member Justification Line Datum and P-line Datum elements which together define the p-line configurations to be used as references for positioning and orientating the Fixings. The Justification Line Datum (JLDATUM ) element defines a frame of reference for its members based on the p-line system of its owning GENSEC. Each JLDATUM can own a set of P-line Datum ( PLDATUM) elements, each of which defines a frame of reference for its members based on a nominated p-line of its owning JLDATUM. By manipulating a JLDATUM, all of its member PLDATUMs can be manipulated as a group, together with any Fixings owned by the latter. Note: The JLDATUM and PLDATUM elements together serve similar functions to the Secondary Nodes (SNOD) used for positioning Fittings (FITT), Compound Fittings (CMFI), Secondary Joints (SJOI) and Compound Secondary Joints (SCOJ) relative to Sections (SCTN). They also provide similar functions to those used for positioning Panel Fittings (PFIT) and Compound Panel Fittings (CMPF), depending on the GENSEC configuration (remember that a GENSEC can model a wide range of geometries, including structural sections and panels). Specifying Position:

The position of a JLDATUM origin may be queried via a pseudo-attribute (Q POS), but this cannot be set explicitly. The position is derived from the following at tribute settings: •

TPREF and HPREF specify, by reference to POINSPs of the parent GENSEC (more strictly, its Spine), the start and end points, respect-ively, between which interpolated positions will be calculated. If both are unset, TPREF defaults to start of the GENSEC and HPREF defaults to the end of the GENSEC. If only one is set, the other defaults to the next POINSP in the appropriate direction.

•

PKDI specifies a point, as a proportion of the distance from TPREF to HPREF, from which ZDIST is to be measured. The default setting is 0, giving a position at TPREF. If PKDI is less than 0 or greater than 1, the position will be on the preceding or following segment, respectively, of the Spine.

•

ZDIST specifies the distance of the JLDATUM origin from the PKDI point, as measured along the Justification Line (JUSL) or NA p-line of the GENSEC.

TPREF

HPREF

= Spine of GENSEC

ZDIST

= POINSP PKDI=0

PKDI=0.5

PKDI=1

= JLDATUM Position for PKDI=0.5

Specifying Orientation:

The orientation of a JLDATUM may be queried via a pseudo-attribute (Q ORI), but this cannot be set explicitly. The orientation is such that its Z axis is in 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, modified by the Beta Angle (BANG) setting, at the POS.

2 5:41

12.0


5.13.6

Generic Fixings Representing Joints and Fittings A Fixing can represent any type of joint or fitting attached to a Generic Section. It can own other Fixings, so that it can also represent compound joints and fittings. Its geometry is defined 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 by reference to the coordinate systems of the parent PLDATUM and JLDATUM. These can be set relative to any POINSP under the GENSEC, including a POINSP which has been specially inserted for this purpos e if necessary, as summarised in Positioning Items Relative to Generic Sections . The default position and orientation of the Fixing relative to its owning PLDATUM 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 is specified 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 the attached GENSEC is curved, these p-lines are taken as parallel to the attached end of the GENSEC. When connected, the JLNS/JLNE line of the attached section intersects with the JLIN 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) attribute of the Fixing will reference the attached GENSEC. This two-way cross-reference is used when either the Fixing or the GENSEC is modified, or when a CONNECT command is used.

5.14

Representing Building Components The elements used to represent structural steelwork designs can also be used to represent the 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 DESIGN Walls & Floors applicationware rather than from the command line, since this will ensure that all relevant attributes are set in a consistent way, but the options are summarised in this section for reference purposes.

5.14.1

Using Element Soft Types To distinguish the elements used for building representation rather than for other types of structural design, element soft types are used. These are elements which have the same attributes as standard (hard type) elements, but which have different names to identify their functions. The soft types used for building design are as follows: Compound Wall (CWALL): a soft type of Subframework (SBFR), used to hold one or more wall components representing, say, one storey of a multi-storey building. Compound Floor (CFLOOR):

a soft type of Subframework (SBFR), used to hold one or more floor components representing, say, one storey of a multi-storey building.

2 5:42

12.0


Compo und Screed (CSCREED): a soft type of Subframework (SBFR), used to hold one or more screed components representing, 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 2D catalogue profile from a start position to an end position. [Curved] Wall (WALL): a soft type of Generic Sect ion (GENSEC). This can, in principle, be used to represent any shape of wall created by extruding a 2D catalogue profile along a path defined by a Spine. The Walls & Floors application for Version 11.3 restricts the use of this element to the representation of a Ring Wall , for which the Spine path is all or part of a circle. General Wall (GWALL ): a soft type of a Panel (PANE), used to represent a wall created by extruding a userdefined 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 2D shape of the column's cross-section is extruded vertically to the required column height. Wall and Floor Fittings , such as doors, windows, manholes etc., can be represented by Compound Fittings (CMPF) , Sub-Compound Fittings (SBFI) , Fittings (FITT), Panel Fittings (PFIT) or Fixings (FIXI) in the usual way.

5.14.2

Controlling Edge Representation in DRAFT When you plot walls and floors in DRAFT, you may want to remove the lines which represent common edges between such elements (referred to as 'unioning' the elements) to give a more realistic appearance. The elements used to represent buildings have an attribute 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 Commo n edges always shown All common edges between adjoining elements will be drawn in DRAFT. DUNION=1 Common edges not s hown between members Common edges between adjoining elements will be drawn in DRAFT unless a pair of such elements are both members of a common parent, in which case the edge lines will be removed. DUNION=2 Common edges not s hown between members and peers Common edges between adjoining elements will be drawn in DRAFT unless a pair of such elements are either both members of a common owner or are at the same hierarchic 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:

2 5:43

12.0


The overall effect in DRAFT is determined by the composite effects of the settings for all significant elements (i.e. all elements which have a DUNION attribute) above those being drawn. For example: When DUNION = 0, all members of the current element will be 'assembled' together rather than 'unioned': joint lines will therefore be shown between touching members (e.g. between adjoining Panels). When DUNION = 1 for a FRMW or SBFR (or equivalent soft types), all members will be unioned: joint lines between touching members (e.g. adjoining Panels) with the same owner will not be shown. The FRMW or SBFR will not itself be unioned with another FRMW or SBFR. When DUNION = 1 for a ZONE, STRU or FRWM, all member STRUs, FRMWs and SBFRs with DUNION = 2 will be unioned. Thus, joint lines will not be shown between adjoining Panels with different owners. The ZONE, STRU or FRMW will not itself be unioned with another ZONE, STRU or FRMW. When DUNION = 2 for any element, all members with DUNION = 2 will be unioned, and the current element will also be unioned to others which share the same owner and which have DUNION = 2 as long as the owner has DUNION = 1 or 2.

2 5:44

12.0

DESIGN Reference Manual Design Templates

6

Design Templates This chapter explains the concept of Design Templates, which let you create and store standard design configurations for subsequent use, and the Design Datasets which hold the parameterised data settings for such templates.

6.1

Concepts A design template is a set of design primitives, panels and nozzles that may be grouped together and then referenced from within another part of the Design database as though it were a single item. In many ways, a design template behaves in a similar way to a catalogue component, except that the template items are stored in a special area of the Design DB, rather than in a separate Catalogue DB, and they can use the more powerful sets of primitives and parameterisation facilities available from within DESIGN. Unlike a catalogue component, a design template can be split down into its constituent parts for selective reporting, dimensioning, MTO, etc. A design template is used in a design by creating an instance of the template. When a design template is instanced, the template contents are copied into the Design hierarchy and a reference is set to the original template definition. At this release version, a design template may only be copied under a Panel Fitting, a Section Fitting or a Primary Joint. A design element cannot own more than one design template, nor can one design template own another template. Design templates may be parameterised to allow a single template definition to be used in different circumstances. The parameterisation facilities use Design Datasets to store named parameters, which may then be referenced in geometric and p-point definitions. The value assigned to a parameter can be defined in terms of a rule by using any of the standard PDMS expression syntax. Note: The definition of Design Templates is likely to be done by the person who organises PDMS Catalogue and Specification data in a company, while the use of Design Templates 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 is relevant to two different types of PDMS user.

6.2

Desi gn Temp lat e Hi er ar ch y Design Template (TMPL) elements are usually stored in a separate Design DB under an

administrative Templat e World (TPWL), which is itself divided into administrative Template Ar eas (TMAR).

Each TMPL is initially created as a copy of an existing set of design elements which have been created in a part of the usual hierarchy below a SITE. The TMPL may then be modified

2 6:1

12.0


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 created thus:

World (/*) SITE

TPWL

ZONE

TMAR

EQUI

TMPL

BOX

BOX

Copy

NBOX

NBOX

When this template is instanced in a design model, say under a panel fitting, its constituent elements are copied back and all parameterisation rules are executed so that the attributes of the copy are set to suit the local DESIGN requirements, thus:

PANE

TPWL TMAR

PFIT

PLOO

TMPL

TMPL

PAVEs

BOX

NBOX

Copy and Execute Rules

BOX

NBOX

All attributes of the copy are locked to prevent unintentional changes.

6.3

Applicatio n Data Ar eas Application Data Areas and Elements are a new form of definition in the Design Database that are provided to assist Appware Applications to store model parts for copying and propagation within a design. They have some similarities with Templates, but are more general in content, and more restrictive in behaviour. Application Data Areas and Elements are expected to be used for Piping Assemblies and Platforms Stairs and Ladders (PSL) applications and perhaps others. They are also expected to be used for storing Multi Discipline Supports (MDS) definitions to make the management of these more robust. The Elements available are administrative elements allowing applications to organise data storage areas of design objects that are not part of the design itself, but supplementary objects used to create and maintain the model. They will not be accessed (unless specifically instructed to do so) when performing model queries such as clashing, mass properties, collections etc. They are similar to catalogue definitions and to Template definitions in particular.

2 6:2

12.0


The top level element in the DESIGN database is Design WORL. This owns a top level application data element APPLDWorl d

- Application Data World

APPLDW can own APPDAReas

- Application Data Areas

DDAR

- Design Data Set Areas

DDARs are existing element types. They own Design Data Sets (DDSE) for storage of data used by Template expressions and Rules, and by Appware. They can be used for Appware to store data, rules, etc for use in data driven instancing of assemblies. APPDAR can own: APPL DAta - 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 The following diagram illustrates the relative positions of these elements in the DESIGN database hierarchy:

2 6:3

12.0


6.3.1

Functional Quer ies Everything under the Application Data World (APPLDWorld) is treated in the same way that hierarchies under TMWL (Template Worlds) are. In particular, Clash checking on command, spatial mapping and auto clashing will be isolated from normal design data except when specifically queried within the APPLDWorld.

6.3.2

Naming Names in the APPLDWorld are in the same scope as the normal project model and so duplicate names will clash. This is not likely to be an issue as it is expected that application data will be unnamed. It would become an issue if sections of 'real' model data are copied or included (moved) into the APPLDWorld. APPLDA elements have a local name scope so that objects that the APPLDA owns can have local names, allowing any Appware manager that manipulates Application Data to easily identify elements within them in the same way that design templates (TMPLates) are handled. Existing commands and expression functions such as LNAME, LNID etc operate within this scope.

6.3.3

Application Data and Templates A template (TMPLate) can be included in the Application Data World, but only as an instanced template, NOT a template definition. Such templates can be refreshed from their definitions using existing (appware and core) driven functions. However, there is no core supported means to refresh copies of Application Data in the real model.

2 6:4

12.0


6.3.4

Ex ten si on t o Des ig n Data DDAT elements have a new attribute PTOLER that provides a tolerance value as an alternative 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 Attribute Valid Value elements (VVALUE) owned by a DDAT can have a Valid Rule set stored in the attribute VALRULE. VALRULE is an expression attribute that can store an expression that evaluates to a logical true or false value. If the expression does not evaluate to a logical result, or if there are errors in the evaluation of the expression, then the VALRULE will return FALSE when queried. The VVALUE element owns a Valid Value attribute (VALIDV) that is an expression returning a real, logical, text or reference value which supports the owning DDAT element. If the VALRULE is true, or if it is a null expression, then this VALIDV will be available to the DDAT. VALRULEs are used by the system to control the choice of a Valid Value when property queries are made on the owning DDAT. For example a DDAT element might own four VVALUE elements with VALIDV and VALRULE attributes as follows: VValue

VALIDValue expression

VALRULE expression

VVALUE 1 ( ID /ANG35x35x15 )

( LDPR LENG le 1800 )


( LDPR LENG gt 1800 and LDPR LENG le 2400 )


( LDPR LENG gt 2400 and LDPR LENG le 3000 )


( LDPR LENG gt 3000 )

The current set of VALIDValues available for the owning DDAT are the set whose VALRULEs either are unset, or evaluate to TRUE. Those that are not available are those whose VALRULEs either evaluate to FALSE, or whose evaluation generate errors.

6.3.6

Extension to Design Data Associated Pseudo Attributes Local 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 also operate at the DDSE level and within the scope of a DDSE: Attribute

Returns

At Owner of DDSE

At DDSE

Below a DDSE (DDAT, VVALUE etc)

DEPL

List of Property keys

Properties in all owned DDSE

Properties in this DDSE

Properties in owning DDSE

LDPR

Real value

Property in any Property or owned DDSE Default Property in any DDSE owned by owner of DDSE

DEPR

Text value for text and reals

2 6:5

Property in any DDSE owned by owner of owning DDSE

12.0


LFDP

Reference value

DEPD

Text default value for text and reals

Default Property in any owned DDSE

Default Property in any DDSE owned by owner of DDSE

All attributes fail above the owner of the DDSE.

6.3.7

Special Design Data Property names in scope of a DDSE Each of the Local Design Data pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP take 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: 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 a DDEFAUlt without knowing its DKEY

element DDAT special key word

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 VVALUE returns result of evaluated VALIDV if element that does not ERROR, VALRUL evaluates TRUE, else ERROR

DDAT

returns the same value as would be returned using the DKEY of the DDAT. (Either the DPROPerty or DDEFAUlt value). This is a convenient way of obtaining this value without knowing the DKEY

Returns the same value as the DDAT property of the owning DDAT without having to know the actual DKEY value to use.

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 these name keys (they are not reserved in anyway) then the use of the key will operate normally on 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 of many values. This is similar to choosing from a set of values according to some criteria. It is possible to use this as an alternative to the IFTRUE expression, which can, for example when used iteratively, select a set of possible choices depending on a particular criterion. The IFTRUE expressions will increase the expression length with the possibility of exceeding the maximum length of the text attribute. Use of VVAL key will not do this.

2 6:6

12.0


The VVALUEs owned by a DDAT DO NOT modify the return values of design data properties when queried by their owners. It should be noted that if the DPROPerty of a DDAT is inconsistent with the set of VVALUEs that it owns, this will NOT raise an exception or error when querying it directly using its DKEY. It is up to the application using these data values to decide whether to accept the value of a DPROPerty whenever it conflicts with valid values, or maximum or minimum values, or a tolerance. To do otherwise would risk the integrity of existing user and system applications.

6.4

Parameterisation using Design Datasets Design Datasets (DDSE) are used to store the properties of design template items, which may then be used to define the template’s parameters. Each property is stored in aDesign Data (DDAT) element under a DDSE, with each DDAT being identified by a keyword held in

its DKEY attribute. The property definition can be specified by an expression held in the DDPR (Design Data Property) attribute, while a default value for the property (to be used if

the expression cannot be evaluated for any reason) can be stored in the DDDF (Design Data Default) attribute. Unlike a design reference to a catalogue component, which can access only a single catalogue dataset via its DTREF setting, a reference to a design template can access more than one design dataset. A l oc al d esi gn dataset is owned directly by the current element, a template design dataset is owned by the first template below the current element, while a current design dataset is at the same level as the current element and has the same owner.

The following diagram illustrates the relative positions of these types of dataset for a simple hierarchy:

PFIT local TMPL

current

DDSE(1)

template

local BOX

current

DDSE(2)

The pseudo-attributes available for accessing the properties data in the various types of dataset are as follows:

2 6:7

12.0


Template Dataset

Current Dataset

Local Dataset

List of property keys

CDPL

DEPL

PRLS

Real property values

CDPR

LDPR

TDPR

Text or real property values

TCDP

DEPR

PROP

Text or real property default values

TCDD

DEPD

PRDE

Reference settings

CFDP

LFDP

TFDP

Note: The dataset attributes PRLS, PROP and PRDE are also used to refer to catalogue dataset properties. If you query any of these attributes, a search for a catalogue dataset will be made first; if this fails, a search for a design template dataset will be made.

Most commonly, a design attribute value will be defined in terms of a design property by using the CDPR (Current Design Dataset Property) attribute. The CDPR can also be used to define a property in one dataset in terms of a property in another dataset. When a CDPR is used in a rule for a component whose owner can own datasets, the current datasets will be those at the same level as the component: otherwise, the current datasets will be those under the first dataset-owning element above the component. When a CDPR is used in a property expression within a dataset, it refers to a property in the current dataset for the item at which CDPR is evaluated. When used in a querying command or in an expression (for example, when defining a parameterisation rule), the attributes for a specific property are identified by the DKEY for that property. For example:

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 from LENG property in current dataset.

Note: Usually default values are assigned to properties, which are then used to evaluate expressions during the creation of a design template. This lets you see the template geometry in a graphical view, at a practical scale, as you define it. Thus a default value for LENG in the last example would allow a sensible XLEN dimension to be evaluated from the rule for display purposes. When instanced in a design, the value of the LENG property would be derived from, say, a design parameter and the rule would be re-executed to give the correct XLEN.

6.5

Assigning Local Names to Template Elements When a design template is copied, confusion can arise in the identification of members of the 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 is modified in any way which affects the ordering of the members list. Even if the element has

2 6:8

12.0


a PDMS name under the Template World, this name will be lost when the template is copied because 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 array attribute of the template. Local names are therefore set and queried at member element level, even though they are stored at template level. The local name survives a template copy operation.

6.5.1

Set ti ng L ocal Nam es Keywords:

LNAME Description:

Lets you assign a local name to a template member, or unset an existing local name. A local name can have a maximum of 20 characters; a maximum of 500 local names can be stored on one template. The local name cannot be modified if either the element or its owning template is locked.

Examples:

LNAME / ANTHONY

Sets local name for current element

LNAME UNSET

Unsets local name for current element

Command Syntax:

>- - - LNAMe - - - *- - - local_name - - - . | | ‘ - - - UNSET - - - - - - - - +- - - > Querying:

6.5.2

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)

Using Local Names in Expressions Keywords:

LNID

MLNID

Description:

Lets you identify an element by its local name in a rule or dataset expression.

2 6:9

12.0


Example:

LNI D / SI D

Identifies element defined in current template

MLNI D / J OE

Identifies element defined in member template (i.e. in template owned by current element)

( XLEN OF LNI D / SI D)

Uses dimension of locally named element in expression (XLEN OF MLNID /JOE)

Command Syntax:

>- - - +- - - LNi d - - - - . | | ‘ - - - MLNi d - - - +- - - local_name - - - > Querying:

6.6

Q LNI D / SI D

For element in current template

Q MLNI D / J OE

For element in member template

Setting Priorities for Evaluating Rules By default, the rules for the member elements of a design template are executed in descending hierarchic order. If the rule for one member element includes a reference to the result of a rule for another member, it is important that the latter rule is executed before the former, otherwise an incorrect result will be obtained. You can control the order in which the rules for a given template will be executed by assigning a rule sequence number to any element which has a local name. When the template rules are re-executed, the rules for such elements will be executed in ascending order of their sequence numbers: the rules for elements with sequence numbers unset (or zero) will then be executed in the default order. Each rule sequence number, and the reference of the corresponding element, is stored in an array attribute of the template. Rule sequence numbers are therefore set and queried at member element level, even though they are stored at template level. Keywords:

RSEQNUMBER Description:

Lets you assign a rule sequence number to any design template member which has a local name. 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 not recommended.

2 6:10

12.0


Examples:

RSEQN 3

Sets rule sequence number for current element (which must be a member of a design template and must already have a local name)

RSEQN UNSET

Unsets rule sequence number for current element

Command Syntax:

>- - - RSEQNumber - - - +- - - integer - - - . | | ‘ - - - UNSET - - - - - +- - - > Querying:

6.7

Q RSEQN

Gives sequence number for current element

Q RSEQA

Lists sequence numbers for all elements under current template (in the order in which their local names were set)

Q RSEQFA

Lists local names for elements under current template, sorted by rule sequence number; i.e. in order of rule execution priority

Adding Design Points to Template Elements The design datasets for a template, as discussed in Parameterisation using Design Datasets, approximate to the Geomset data for a catalogue component. In a similar way, design templates can also own Design Pointsets (DPSE), which approximate to the Pointset data for a catalogue component. These let you assign p-points to design template items, 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 those available in catalogue pointsets): •

A Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:

Design Point

Z

Orientation

Direction of Normal

Y

Origin X

•

A Cylindrical P-point is specified as a position on the surface of a cylinder at a given position and with given dimensions, thus:

2 6:11

12.0


Design Orientation Point

Direction of Normal Z

Ang le defining point posit io n wrt Y axis

Y

Origin X

•

Cylinder defined by its positio n, height and radius

A Spherical P-point is specified as a position on the surface of a sphere at a given position and with given dimensions, thus:

Design Point Z

Orientation Y

Direction of Normal Direction radius acts in, defining point position wrt sphere's centre

Origin X

Sphere defined by its position and radius

6.8

Using a Design Template Item in a Design To create an instance of a ‘source’ design template in a design model, you must first create a template below the owning design element and then copy into this the details of the source template (which must be in a template world) from which it is to derive its data. The commands (at the design 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 as specified in the source template, you must first unset the ORRF references which point back to the source and unlock the members. To do so, use the command UNTIE

template_instance

where template_instance is the name of the copy TMPL in the design model hierarchy.

2 6:12

12.0


6.9

Portsets and Linksets If the user lists the possible members of most types of design element, you will see two elements called Portsets (PORS) and Linksets (LNKS). These are included in the database definitions to permit logical connections to be made to items derived from design templates by the AVEVA applications.

2 6:13

12.0


2 6:14

12.0


Index

A ALONG command . . . . . . . . . . . . . . . 2-2:31 ARRIVE command . . . . . . . . . . . . . . 2-3:26 AT command . . . . . . . . . . . . . . . . . . . . 2-2:5 Attached parameters . . . . . . . . . . . . . 2-5:36 Attributes:of primitives . . . . . . . . . . . . . 2-2:1 Attributes:sections . . . . . . . . . . . . . . . . 2-5:4 AUTOROUTE command . . . . . . . . . . . 2-4:1 AXES command:pipe routing . . . . . . . 2-4:2

B BANGLE command . . . . . . . . . 2-5:6 2-5:12 BASE command:pipe routing . . . . . . . 2-4:6 BEHIND command . . . 2-2:26 2-3:7 2-3:52 Beta angle:joints . . . . . . . . . . . . . . . . 2-5:12 Beta angle:sections . . . . . . . . . . . . . . . 2-5:6 BOP command . . . . . . . . . . . . 2-3:7 2-3:63 BOP command:pipe routing . . . . . . . . 2-4:7 Branch:head . . . . . . . . . . . . . . . . . . . . 2-3:2 Branch:tail . . . . . . . . . . . . . . . . . . . . . . 2-3:2 Buildings . . . . . . . . . . . . . . . . . . . . . . 2-5:42 BUILT flag . . . . . . . . . . . . . . . . . . . . . 2-3:31 BY command . . . . . . . . . . . . . . . . . . 2-2:15 ,

,

,

,

C CDPR attribute . . . . . . . . . . . . . . . . . . 2-6:8 CHOOSE command . . . . . . . . . . . . . 2-3:12 CLEARANCE command . . . . 2-2:34 2-3:59 Cofitting element . . . . . . . . . . . . . . . . 2-5:34 Cofitting Reference Array attribute . . 2-5:34 Compound fitting element . . . . . . . . . . 2-5:2 Compound Floor element . . . . . . . . . 2-5:42 ,

Compound joint element . . . . . . . . . . . 2-5:1 Compound panel fitting element . . . . . 2-5:2 Compound Screed element . . . . . . . . 2-5:43 Compound Wall element . . . . . . . . . .2-5:42 CONNECT command 2-2:14 2-3:2 2-3:39 25:17 Connection:forced . . . . . . . . . . . . . . .2-3:41 CRFA attribute . . . . . . . . . . . . . . . . . .2-3:34 CTYEND command . . . . . . . . . . . . . . .2-5:8 CTYSTART command . . . . . . . . . . . . . 2-5:8 Current design dataset . . . . . . . . . . . . . 2-6:7 Current Design Dataset Property attribute 2-6:8 CURTYP attribute . . . . . . . . .2-5:36 2-5:38 Curve element . . . . . . . . . . . . . . . . . .2-5:36 Curve Type attribute . . . . . . . .2-5:36 2-5:38 CUTBACK command . . . . . . . . . . . . .2-5:16 CUTPLANE command . . . . . . . . . . . .2-5:16 ,

,

,

,

,

D DDAT element . . . . . . . . . . . . . . . . . . .2-6:7 DDDF attribute . . . . . . . . . . . . . . . . . . .2-6:7 DDPR attribute . . . . . . . . . . . . . . . . . . .2-6:7 DDSE element . . . . . . . . . . . . . . . . . . .2-6:7 DELPOSITION command . . . . . . . . . 2-5:12 Design Data Default attribute . . . . . . . . 2-6:7 Design Data element . . . . . . . . . . . . . .2-6:7 Design Data Property attribute . . . . . . . 2-6:7 Design Dataset element . . . . . . . . . . . . 2-6:7 Design parameters . . . . . . . . . . . . . . .2-5:34 Design Pointset element . . . . . . . . . .2-6:11 Design Template element . . . . . . . . . . 2-6:1 DESPARAMETER command . . . . . . . 2-5:34 Detail level . . . . . . . . . . . . . . . . . . . . . .2-2:3

Index page 1

12.0


DIRECTION command . . . . . . . . . . . 2-3:37 DISCONNECT command . . . . . . . . . 2-5:18 DISTANCE command . . . . . . 2-3:44 2-3:48 DKEY attribute . . . . . . . . . . . . . . . . . . 2-6:7 DPSE element . . . . . . . . . . . . . . . . . 2-6:11 DRAFT Union attribute . . . . . . . . . . . 2-5:43 DRAG command . . . . . . . . . . . . . . . . 2-3:68 DRNEND command . . . . . . . . . . . . . . 2-5:6 DRNSTART command . . . . . . . . . . . . 2-5:6 DUNION attribute . . . . . . . . . . . . . . . 2-5:43 ,

I IDPLINE command . . . . . . . . . . . . . .2-5:26 INFRONT command . 2-2:26 2-3:7 2-3:52 Instance:Design templates . . . . . . . . . . 2-6:1 Insulation specification . . . . . . . . . . . .2-3:30 ISPEC attribute . . . . . . . . . . . . . . . . . 2-3:30 ,

,

J JLDATUM element . . . . . . . . .2-5:37 2-5:41 JOIEND command . . . . . . . . . . . . . . . .2-5:7 Joint element:compound . . . . . . . . . . . 2-5:1 Joint element:linear . . . . . . . . . . . . . . .2-5:1 Joint element:primary . . . . . . . .2-5:1 2-5:11 Joint element:secondary . . . . .2-5:1 2-5:11 Joint:creating . . . . . . . . . . . . . . . . . . .2-5:10 Joints:attributes . . . . . . . . . . . . . . . . . 2-5:15 Joints:linear . . . . . . . . . . . . . . . . . . . .2-5:31 Joints:primary . . . . . . . . . . . . . . . . . . .2-5:12 Joints:secondary . . . . . . . . . . . . . . . .2-5:13 JOISTART command . . . . . . . . . . . . . . 2-5:7 Justification Line Datum element 2-5:37 2-5:41 ,

E Edge drawing in DRAFT . . . . . . . . . . 2-5:43 Elements:connecting . . . . . . . . . . . . . 2-2:14 Elements:moving . . . . . . . . . . . . . . . 2-2:15 Elements:orientating . . . . . . . . . . . . . 2-2:10 Elements:rotating . . . . . . . . . . . . . . . 2-2:12 End position (section) . . . 2-5:4 2-5:5 2-5:9 ERELEASE command . . . . . . . . . . . . 2-5:8 EXTEND command . . . . . . . . . . . . . . 2-5:22 ,

,

F

,

,

,

FCONNECT command . . . . . . . . . . . 2-3:41 Fitting element . . . . . . . . . . . . 2-5:1 2-5:33 Fitting element:compound . . . . . . . . . . 2-5:2 Fitting element:panel . . . . . . . . . . . . . . 2-5:1 Fixing element . . . . . . . 2-5:2 2-5:37 2-5:42 FLIP command . . . . . . . . . . . 2-3:27 2-5:20 Floors . . . . . . . . . . . . . . . . . . . . . . . . 2-5:42 FORCECONNECT command . . . . . . 2-3:12 Forced connection . . . . . . . . . . . . . . 2-3:41 FROM command . . . . . . . . . . . . . . . . 2-3:48 ,

,

,

,

G Generic Fixing element . . . . . . . . . . . Generic Section element . . . . . 2-5:2 GENSEC element . . . . . . . . . . 2-5:2 #106 . . . . . . . . . . . . . . . . . . . 2-6:11 plin . . . . . . . . . . . . . . . . . . . . . . . . . .

,

,

,

2-5:42 2-5:36 2-5:36 2-6:12 2-5:26

L LEAVE command . . . . . . . . . . . . . . . .2-3:26 LEVEL command . . . . . . . . . . . . . . . . .2-2:3 Linear joint element . . . . . . . . . . . . . . .2-5:1 Linear joints . . . . . . . . . . . . . . . . . . . .2-5:31 LINK command . . . . . . . . . . . . . . . . . 2-5:31 LNAME . . . . . . . . . . . . . . . . . . . . . . . . .2-6:9 LNID . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6:9 Local design dataset . . . . . . . . . . . . . .2-6:7 Local name:Design templates . . . . . . . 2-6:9 LOFF attribute . . . . . . . . . . . . . . . . . .2-3:33 LSROD attribute . . . . . . . . . . . . . . . . .2-3:29 LSTUBE attribute . . . . . . . . . . . . . . . .2-3:29 2-5:26 Cartesian p . . . . . . . . . . . . . . . . . . . . .2-6:11 Cylindrical p . . . . . . . . . . . . . . . . . . . .2-6:11 Spherical p . . . . . . . . . . . . . . . . . . . . .2-6:12

H

M

HBOR command . . . . . . . . . . . . . . . . . 2-3:5 HCON command . . . . . . . . . . . . . . . . . 2-3:5 HDIR command . . . . . . . . . . . . . . . . . 2-3:5 Head of branch . . . . . . . . . . . . . . . . . . 2-3:2 HPOS command . . . . . . . . . . . . . . . . . 2-3:5 HREF command . . . . . . . . . . . . . . . . . 2-3:4 HSPE command . . . . . . . . . . . . . . . . . 2-3:2 HSROD attribute . . . . . . . . . . . . . . . . 2-3:29 HSTUBE attribute . . . . . . . . . . . . . . . 2-3:29

MIRROR command . . . . . . . . . . . . . .2-2:43 MLNID . . . . . . . . . . . . . . . . . . . . . . . . .2-6:9 MOVE command . . . . 2-2:16 2-3:9 2-3:42 ,

,

N Node element:primary . . . . . . . . . . . . . 2-5:1 Node element:secondary . . . . . . . . . . . 2-5:1 Nodes:primary . . . . . . . . . . . . . . . . . . .2-5:2

Index page 2

12.0


Nodes:secondary . . . . . . . . . . . . . . . . 2-5:9 Nozzle offset factor:pipe routing . . . . . 2-4:4 Nozzles:specifying . . . . . . . . . . . . . . . 2-2:2

R RACK command . . . . . . . . . . . . . . . . .2-4:5 RECONNECT command . . . .2-3:11 2-5:19 RESELECT command . . . . . . . . . . . .2-3:22 Ring Wall element . . . . . . . . . . . . . . .2-5:43 Rod:attributes . . . . . . . . . . . . . . . . . . .2-3:29 ROTATE command . . . . . . . . . . . . . .2-2:12 ROUTE command . . . . . . . . . . . . . . . .2-4:4 Routing plane:pipe routing . . . . .2-4:2 2-4:3 RPLANE command . . . . . . . . . . . . . . .2-4:3 RSEQNUMBER . . . . . . . . . . . . . . . . .2-6:10 Rule sequence number:Design templates 26:10 ,

O OBSTRUCTION command . . . . . . . . . 2-2:4 Obstruction level:clash detection . . . . 2-2:4 OFFSETFACTOR command . . . . . . . 2-4:4 ONTOP command . . . 2-2:28 2-3:7 2-3:55 OPDIRECTION command . . . . . . . . 2-5:12 ORDER command:pipe routing . . . . . 2-4:8 ORIENTATE command . . . . . 2-2:10 2-3:35 Orientation . . . . . . . . . . . . . . . . . . . . 2-2:10 ORIFLAG attribute . . . . . . . . . . . . . . 2-3:32 Owning parameters . . . . . . . . . . . . . . 2-5:36 ,

,

,

P Panel Fitting element . . . . . . . 2-5:1 2-5:34 Panel fitting element:compound . . . . . 2-5:2 Panel Fitting Reference attribute . . . 2-5:34 Panel Loop element . . . . . . . . . . . . . . 2-5:1 Panel Vertex element . . . . . . . . . . . . . 2-5:1 Panels:connecting . . . . . . . . . . . . . . . 2-5:31 Panels:creating . . . . . . . . . . . . . . . . . 2-5:29 Panels:splitting . . . . . . . . . . . . . . . . . 2-5:30 Parameters:attached . . . . . . . . . . . . . 2-5:36 Parameters:design . . . . . . . . . . . . . . 2-5:34 Parameters:owning . . . . . . . . . . . . . . 2-5:36 Penalty volume:pipe routing . . . 2-4:2 2-4:3 PH command . . . . . . . . . . . . . . . . . . . 2-3:6 Pipe rack:pipe routing . . . . . . . . . . . . . 2-4:5 Pipe routing . . . . . . . . . . . . . . . . . . . . . 2-4:1 PJOINT command . . . . . . . . . . . . . . 2-5:11 PLDATUM element . . . . . . . . 2-5:37 2-5:41 Pline Datum element . . . . . . . 2-5:37 2-5:41 PNODE command . . . . . . . . . . . . . . . 2-5:2 POINSP element . . . . . . . . . . . . . . . . 2-5:36 point:in design pointset . . . . . 2-6:11 2-6:12 POLAR command . . . . . . . . . . . . . . . . 2-2:8 Polar positioning . . . . . . . . . . . . . . . . . 2-2:8 POSEND command . . . . . . . . . . . . . . 2-5:5 POSFLAG attribute . . . . . . . . . . . . . . 2-3:32 POSITION command . . . . . . . 2-2:5 2-3:44 Positioning . . . . . . . . . . . . . . . . . . . . . 2-2:5 POSLINE command . . . . . . . . . . . . . 2-5:13 POSSTART command . . . . . . . . . . . . 2-5:5 PPLINE command . . . . . . . . . . . . . . 2-5:26 Primitives:attributes . . . . . . . . . . . . . . . 2-2:1 Profile element . . . . . . . . . . . . . 2-5:1 2-5:4 PSPE command . . . . . . . . . . . . . . . . . 2-3:2 PT command . . . . . . . . . . . . . . . . . . . . 2-3:6 PVOL command . . . . . . . . . . . . . . . . . 2-4:3 ,

,

,

,

,

,

,

S Screeds . . . . . . . . . . . . . . . . . . . . . . .2-5:42 SDIR command:pipe routing . . . . . . . . 2-4:6 Sections:attributes . . . . . . . . . . . . . . . .2-5:4 Sections:connecting . . . . . . . . . . . . . .2-5:17 Sections:creating . . . . . . . . . . . . . . . . .2-5:3 Sections:disconnecting . . . . . . . . . . . 2-5:18 Sections:modifying lengths . . . . . . . . 2-5:22 Sections:reconnecting . . . . . . . . . . . .2-5:19 SELECT command . . . . . . . . . . . . . .2-3:17 SHOP flag . . . . . . . . . . . . . . . . . . . . .2-3:31 SHORTCODE command . . . . . . . . . .2-3:21 SJOINT command . . . . . . . . . . . . . . .2-5:11 SNODE command . . . . . . . . . . . . . . . .2-5:9 Soft types . . . . . . . . . . . . . . . . . . . . . .2-5:42 Spine element . . . . . . . . . . . . .2-5:2 2-5:36 Spine Point element . . . . . . . . . . . . . .2-5:36 SPLIT command . . . . . . . . . . . . . . . .2-5:30 SPREAD command:pipe routing . . . . . 2-4:7 SPREF attribute . . . . . . . . . . . . . . . . .2-3:28 SRELEASE command . . . . . . . . . . . . . 2-5:8 Start position (section) . . . . . . . .2-5:4 2-5:5 Steelwork:fittings . . . . . . . . . . . . . . . . .2-5:1 Steelwork:fixings . . . . . . . . . . . . . . . . .2-5:2 Steelwork:generic sections . . . . . . . . . 2-5:2 Steelwork:joints . . . . . . . . . . . . . . . . . .2-5:1 Steelwork:nodes . . . . . . . . . . . . . . . . . .2-5:1 Steelwork:panels . . . . . . . . . . . . . . . . .2-5:1 Steelwork:sections . . . . . . . . . . . . . . . .2-5:1 Straight Wall element . . . . . . . . . . . . .2-5:43 STRING command . . . . . . . . . . . . . . . .2-5:3 Subfitting element . . . . . . . . . . . . . . . .2-5:2 Subjoint element . . . . . . . . . . . . . . . . .2-5:1 syntax . . . . . . . . . . . . . . . . . . . . . . . . .2-5:26 ,

,

,

T Tail of branch . . . . . . . . . . . . . . . . . . . .2-3:2

Index page 3

12.0

Design Reference Manual - Creating the Model

Recommend Documents