Professional Documents
Culture Documents
PLEASE NOTE: Cadcentre has a policy of continuing product development: therefore, the information contained in this document may be subject to change without notice. CADCENTRE MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. While every effort has been made to verify the accuracy of this document, Cadcentre shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance or use of this material.
This manual provides documentation relating to products which you may not have access to or which may not be licensed to you. For further information on which products are licensed to you please refer to your licence conditions.
All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of Cadcentre. The software programs described in this document are confidential information and proprietary products of Cadcentre Ltd or its licensors.
For details of Cadcentre's worldwide sales and support offices, see our website at
http://www.cadcentre.com/location
Contents
1
1.1 1.2 1.3
Introduction ...................................................................................................1-1
About the DESIGN Reference Manual............................................................. 1-1 Organisation of the DESIGN Reference Manual ............................................. 1-1 Organisation of this Manual ............................................................................. 1-2
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
3
3.1 3.2 3.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Contents
3.3.2 Positioning Head or Tail in Free Space ........................................................ 3-6 3.3.3 Head or Tail Positioning Using End Components........................................ 3-7 3.3.4 Head and Tail Positioning by Bottom or Top of Pipe ................................... 3-9 3.3.5 Moving the Head or Tail ............................................................................. 3-11 3.3.6 Reconnecting Pipes after an Equipment Move........................................... 3-13 3.4 Selecting Component and Tube Details from Specifications ......................... 3-13 3.4.1 Choosing Components from a Displayed List............................................. 3-14 3.4.2 Selecting Components from Specifications................................................. 3-19 3.4.3 Selecting the Default Specification Component ......................................... 3-20 3.4.4 Selecting from Several Alternatives ........................................................... 3-20 3.4.5 Selecting Out-of-Specification Components .............................................. 3-22 3.4.6 Selecting Components and Tube Separately .............................................. 3-23 3.4.7 Direct Selection by Shortcode ..................................................................... 3-24 3.5 Re-selection of Existing Components and Tube ............................................. 3-26 3.5.1 Re-selecting the New Default Component.................................................. 3-26 3.5.2 General Reselection of Components and Tube ........................................... 3-27 3.6 Standard Component Attributes .................................................................... 3-28 3.6.1 Position and Orientation Attributes ........................................................... 3-30 3.6.2 Component Arrive and Leave Attributes.................................................... 3-31 3.6.3 Swapping the Arrive and Leave P-points ................................................... 3-31 3.6.4 The Component Specification Reference Attribute .................................... 3-33 3.6.5 Variable Length Tube (and Rod) Attributes............................................... 3-33 3.6.6 Insulation Specification Attribute .............................................................. 3-35 3.6.7 Trace Heating Specification Attribute........................................................ 3-35 3.6.8 The Fabrication Flags ................................................................................. 3-36 3.6.9 Position and Orientation Status Flags ....................................................... 3-37 3.6.10Variable Component Attributes .................................................................. 3-38 3.6.11Offline/Straight-Through Component Attribute ........................................ 3-39 3.6.12Multi-Way Component Attributes .............................................................. 3-39 3.7 Orientation and Connection of Components .................................................. 3-40 3.7.1 Component Orientation............................................................................... 3-41 3.7.2 Direction-Changing Components ................................................................ 3-43 3.7.3 Component Connection ............................................................................... 3-45 3.7.4 Forced Component Connection ................................................................... 3-46 3.8 Moving by a Known Distance ......................................................................... 3-47 3.8.1 Moving Components .................................................................................... 3-47 3.8.2 General Moving of Components .................................................................. 3-48 3.9 Positioning Components using Reference Planes .......................................... 3-49 3.9.1 Positioning with respect to the Previous Component ................................ 3-49 3.9.2 Positioning the Component through an Intersection ................................. 3-51 3.9.3 Positioning with respect to an Intersection................................................ 3-53 3.9.4 General Positioning through an Intersection ............................................. 3-57 3.10 Positioning Components Point-to-Surface .................................................... 3-58 3.10.1Positioning Components either side of an Object....................................... 3-59 3.10.2Positioning Components On Top of or Under an Object ............................ 3-62 3.10.3General Component Positioning Using Planes........................................... 3-64 3.11 Component Clearance Positioning.................................................................. 3-66 3.11.1Clearance from the Previous Component ................................................... 3-66 3.11.2Component Clearance Either Side.............................................................. 3-68 3.11.3Component Clearance Vertically ................................................................ 3-70
Contents-ii
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Contents
3.11.4Tube (Bottom of Pipe) Clearance ................................................................ 3-72 3.11.5General Clearance of Components and Tube ............................................. 3-74 3.12 Dragging Equipment and Piping Networks ................................................... 3-77 3.12.1Dragging Equipment and Nozzles .............................................................. 3-78 3.12.2Dragging Piping........................................................................................... 3-82
4
4.1 4.2
4.3
5
5.1 5.2 5.3
5.4 5.5
5.6
5.7
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Contents
5.8
5.9
5.10
5.11
5.12 5.13
5.14
Repositioning Steelwork Elements ................................................................. 5-22 5.8.1 Reversing Section Start and End Positions (Flipping) ............................. 5-22 5.8.2 Moving Steelwork Elements ....................................................................... 5-24 5.8.3 Modifying Lengths of Sections .................................................................... 5-25 5.8.4 Reorientating Steelwork Elements ............................................................. 5-26 Positioning and Orientating Using P-lines .................................................... 5-29 5.9.1 Identifying P-lines ....................................................................................... 5-30 5.9.2 Positioning by Using P-lines ....................................................................... 5-30 5.9.3 Orientating by Using P-lines ...................................................................... 5-32 Creating and Connecting Panels .................................................................... 5-34 5.10.1Creating a Panel.......................................................................................... 5-34 5.10.2Splitting a Panel.......................................................................................... 5-34 5.10.3Connecting Panels using Linear Joints ...................................................... 5-35 Fittings, Hangers and Equipment Load Points ............................................. 5-38 5.11.1Fittings and Panel Fittings ......................................................................... 5-38 5.11.2Structure-to-Pipework Connections............................................................ 5-39 5.11.3Structure-to-Equipment Connections ......................................................... 5-39 Design, Owning and Attached Parameters .................................................... 5-40 5.12.1Setting Design Parameters ......................................................................... 5-40 5.12.2Setting Owning and Attached Parameters................................................. 5-41 Representing Curved Beams and Walls ......................................................... 5-43 5.13.1Overview ...................................................................................................... 5-43 5.13.2Defining a Generic Section.......................................................................... 5-44 5.13.3More About Curve Types............................................................................. 5-45 5.13.4How P-lines Are Used For Generic Sections .............................................. 5-46 5.13.5Positioning Items Relative to Generic Sections.......................................... 5-48 5.13.6Generic Fixings Representing Joints and Fittings..................................... 5-49 Representing Building Components ............................................................... 5-50 5.14.1Using Element Soft Types........................................................................... 5-50 5.14.2Controlling Edge Representation in DRAFT.............................................. 5-51
6
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8
7
7.1 7.2 7.3 7.4
Groups ...........................................................................................................7-1
Defining Group Contents .................................................................................. 7-1 Accessing Groups .............................................................................................. 7-2 Deleting Groups ................................................................................................ 7-3 Copying a Group................................................................................................ 7-3
Index
Contents-iv
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Introduction
1.1
1.2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
1-1
Introduction
1.3
For a comprehensive list of all PDMS attributes and pseudo-attributes, see the Cadcentre Software Customisation Reference Manual.
1-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
2.1
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
2-1
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: Box Cylinder Circular Torus Cone Slope-bottomed Cylinder Rectangular Torus Dish Snout 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 Part 3 of the PDMS DESIGN Reference Manual.. Examples: XLEN 1000 (At a Box) The xlength dimension of the box becomes 1000 DIA 3 FT (At a Cylinder) The diameter of the cylinder becomes 3 feet Command Syntax: Refer to Part 3 of the DESIGN Reference Manual.
DIAMETER
HEIGHT
Figure 2-1
2-2
Examples: CATR /NFAARPMM (At Nozzle) The size and rating of the Nozzle are set by naming the appropriate Catalogue choice. HEI 26 (At Nozzle) The Height of the Nozzle becomes 26. Command Syntax: >-- CATref name --> >-- HEIght <uval> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-3
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. Examples: LEVEL 6 10 The current primitive will be drawn if the operative drawing LEVEL is within the specified range. Command Syntax:
>-- LEVel integer integer -->
Figure 2-2
2-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Holes (i.e. negative primitives) also have the OBSTRUCTION attribute. OBSTRUCTION settings for Nozzles and Piping are given in the Catalogue. Note: Examples: OBST SOFT (At a primitive) Current Element will be considered as a soft obstruction. OBST HARD (At a primitive) Current Element will be considered as a hard obstruction. OBST NONE (At a primitive) Current Element will be ignored during clash detection. OBST 2 (At a primitive) Current Element will be considered as a hard obstruction. Command Syntax:
>-- OBStruction --+-| |-| |-| -integer --. | HARD -----| | SOFT -----| | NONE -----+-->
See also Chapter 5 in Part 1 of the DESIGN Reference Manual for details of the Spatial Map which is used during clash-checking.
Figure 2-3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-5
2.2
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.
Examples: AT E3 N46 U1 Current Element will be placed at the specified owner coordinate position (see Figure 2-4). AT IDP@ Current Element will be placed at the p-point picked by the cursor. AT@ The Current Element will be placed at the toleranced working grid position indicated by the cursor hit. Prompt alerts appear, and the position is generated by hits in two orthogonal views. POS PIN5 AT E3000 The specified PIN and Current Element will be positioned as a single rigid item, so that the PIN is at E3000 N0 U0 (see Figure 2-5). Command Syntax:
>--+-- POSition <marke> --. | | ----------------------+-- AT <bpos> -->
2-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Querying Examples: Q POS Gives position of Current Element origin in owner coordinates Q POS IN SITE Gives position of Current Element origin in Site Q POS IDP@ Gives position of picked p-point
CE ORIGIN
1'
OWNER ORIGIN
4' 6"
3'
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-7
Figure 2-5
Examples: POLAR E45N DIST 300 The Current Element will be placed 300 from its owners origin along E45N (see Figure 2-6). POLAR PIN1 DIST 3000 The Current Element will be placed 3000 from its owners origin along the direction of PIN1 (see Figure 2-6). POS IDP@ POLAR S1OW DIST3 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 owners origin. Command Syntax:
>--+-- POSition <marke> --. | | ----------------------+-- POLar <bdir> DISTance <uval> -->
2-8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 2-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-9
Examples: POLAR N30E PLANE N DIST 1000 Positions the Current Element along the N30E line from the owner origin at N1000 (see Figure 2-7). Command Syntax:
>-+- POSition <marke> -. | | --------------------+- POLar <bdir> -+- PLAne <bdir> -. | | ----------------+- DISTance <uval> ->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 2-7
2.3
2-10
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: ORI Y IS N AND Z IS 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-8a). ORI P1 IS E The Current Element is rotated so that its P1 p-point is pointing East in owner coordinates (see Figure 2-8b). Command Syntax:
>- ORIentate -+- <bdir> IS <bdir> -. | | --------------------+- AND <bdir> IS <bdir> -. | | ------------------------+-->
Querying:
>-- Query ORIentation --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-11
Figure 2-8a
Figure 2-8b
2-12
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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 direction is that of the Neutral Axis or Z axis; the default through point is the Origin. By reference to the elements axes.
Examples:
ROTATE BY -45 Rotates by 45 about the elements Z axis (anticlockwise when looking in the +Z direction, since the rotation is specified as a negative angle). ROTATE BY 45 ABOUT E Rotates by 45 about the E-W axis (clockwise when looking E). ROTATE ABOUT E BY 45 The same as the preceding example. ROT THRO P3 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 IS N45W25D Rotates element until the Y axis points as closely as possible to the N45W25D direction. Command Syntax: Rotation about a given axis:
>- ROTate ABOut <bdir> + THRough <bpos> -+- BY -+- <uval> ----------------. | | | | | | - <bdir> TOwards <bdir> -| | | | | - AND <bdir> IS <bdir> ---------+-> | | BY -+- <uval> ----------------. | | | | - <bdir> TOwards <bdir> -+-> | | AND <bdir> IS <bdir> -+- THRough <bpos> -. | | ------------------+->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-13
2-14
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: 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-9). CONN PIN1 TO IDP@ The Current Element and PIN1 are moved and rotated so that PIN1 connects to the p-point hit. CONN IDP@ TO IDP@ AND X IS 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-10). Note: The first p-point in the command must belong to the Current Element.
Command Syntax:
>-- CONnect <marke> TO <marke> -+- AND <bdir> IS <bdir> --. | | -------------------------+-->
Querying:
>-- Query ORIentation --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 2-9
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-15
Figure 2-10
2.4
Examples: BY E300 N400 Moves the Current Element by the specified amounts along the owners axes (see Figure 2-11). BY E3000 WRT SITE Moves the Current Element by the specified amount along the Sites East axis (see Figure 2-11).
2-16
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>-- BY <pos> --+-- <axes> --. | | ------------+-->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
N
N
BY E3000 WRT SITE CE
OWNER AXES
BY E3000
E
SITE AXES
Figure 2-11
MOVE ALONG
TOWARDS DISTANCE
This command displaces the Current Element in any specified direction by a given distance.
2-17
Command Syntax:
>-- MOVe --+-- ALOng --. | | -----------+-- <bdir> DISTance <uval> -->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 2-12a
Figure 2-12b
2-18
This command differs from the basic option by allowing the distance moved to be specified in a different plane from the actual movement direction.
Examples: MOVE TOW /DATUM PLANE E DIST 1000 The Current Element is moved towards the specified design item until its Easting (in owner coordinates) has changed by 1000 (see Figure 2-13). Command Syntax:
>-- MOVe --+- ALOng -. | | ---------+- <bdir> -+-- PLAne <bdir> --. | | ------------------+-- DISTance <uval> ->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 2-13
2.5
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-19
commands cannot calculate physical clearances (see Sections 2.6 and 2.7 for such commands).
Command Syntax:
>-- MOVe --+-- ALOng --. | | -----------+-- <bdir> THRough <bpos> -->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
2-20
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-14
Figure 2-15
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-21
Figure 2-16
This command moves the Current Element until its origin intersects the Reference Plane a given distance either side of a fixed 3D point.
Command Syntax:
>-- MOVe --+-- ALOng --. | | -----------+--
2-22
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
30
REFERENCE PLANES
MOVE N30W...
CE
(START POSITION)
Figure 2-17
Figure 2-18a
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-23
Figure 2-18b
This command differs from the basic options by allowing the movement direction and Reference Plane to be specified independently. 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.
Examples: MOVE IDP@ TOW /DATUM PLANE N THROUGH N1000 Move the picked p-point (or the Current Element) towards /DATUM until it intersects N1000 (see Figure 2-19a). MOVE ALONG E PLANE N45W DIST 20 TO /TANK5 Move the Current Element East until it intersects an oblique Reference Plane 20 before the origin of /TANK5 (see Figure 2-19b). Note: DISTANCE is measured in the direction of the Reference Plane and not the movement direction.
2-24
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>- MOVe -+- <marke> -. | | -----------+- ALOng -. | | ---------+- <bdir> -. | | ----------+- PLANe <bdir> -+| | | | | || || -
<dist> -+- FROm -. | | |- TO ---+- <bpos> -. | | -------------------| | FROm ----. | | | TO ------| | | | THRough -+- <bpos> ---------+->
<dist>
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-25
Figure 2-19(a)
Figure 2-19(b)
2-26
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
2.6
Examples: MOVE E DIST 1000 BEH /WALL10 The Current Element is moved East until its origin is 1000 beyond the far side of /WALL10 (see Figure 2-20). MOVE N45E DISTANCE 20 INFRONT /EXCH5 The Current Element is moved until its origin is 20 to the near side of /EXCH5 (see Figure 2-20 and Figure 2-21). Command Syntax:
>- MOVe -+- ALOng -. | | ---------+- <bdir> DISTance <uval> -+- FROm -. | | - TO ---+- <bpos> -+- INFront -. | | - BEHind --+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-27
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-- <gid> ---. | | -----------------------+-->
Figure 2-20
2-28
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-21
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-29
Examples: 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-23). MOVE ALONG E45D DISTANCE 3000 UNDER /BEAM Moves the Current Element along E45D until its origin is 3000 vertically below /BEAM (see Figure 2-22 and Figure 2-23). 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 -. | | ---------+- <bdir> DISTance <uval> -+- FROm -. | | - TO ---+- <bpos> -+- UNDer -. | | - ONTop -+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
2-30
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-22
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-31
Figure 2-23
2-32
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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.
Examples: MOVE P1 E INFRONT /BOX The Current Element will be moved East until the specified p-point is zero distance in front of /BOX (see Figure 2-24). MOVE NOZZLE1 S DIST 200 INF /RACK (at an Equipment element) Moves the current Equipment by positioning the Nozzle at the specified location. Command Syntax:
>- MOVe <marke> -+- ALOng -. | | ---------+- <bdir> PLAne <bdir> DISTance <uval> <repla> ->
FROm --. | TO ----+-- <bpos> --> INFront --. | BEHind ---| | UNDer ----| | ONTop ----+-- <gid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-33
Figure 2-24
2-34
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
2.7
MOVE CLEARANCE INFRONT BEHIND This command moves the Current Element until its geometric volume is a specified clearance from a fixed Design element, Point or position.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-35
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-- <gid> --. | | ----------------------+-->
Figure 2-25
2-36
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-26
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-37
Examples: MOVE E CLEARANCE 1000 BEH /WALL10 The Current Element is moved East until its entire volume is 1000 clear of the side of /WALL10 (see Figure 2-27). MOVE D CLEARANCE ONTO /BEAM The Current Element is moved down until it has a zero clearance above the element /BEAM (see Figure 2-27). Command Syntax:
>- MOVe -+- ALOng -. | | ---------+- CLEArance <uval> -+| || || -
INFront -. | BEHind --| | UNDer ---| | ONTop ---+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
2-38
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-27
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-39
Examples: MOVE ALONG U30W CLEAR ONTO /BEAM The Current Element will be moved vertically until it is zero clearance above /BEAM (see Figure 2-28). MOVE E60D CLEAR 1000 UNDER PIN6 The Current Element will be moved E60D until it is 1000 below the specified Design point (see Figure 2-29). Command Syntax:
>- MOVe -+- ALOng -. | | ---------+- <bdir> CLEArance <uval> -+- UNDer -. | | - ONTop -+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
2-40
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 2-28
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-41
Figure 2-29
2-42
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
MOVE PLANE CLEARANCE INFRONT BEHIND This command differs from the basic option by allowing the movement direction and clearance to be specified in different planes.
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-43
Figure 2-30
2.8
You will most likely use the mirror positioning options in conjunction with the COPY command (see Sections 8.1.5 and 8.1.6 of Part 1) to create a new part of the design model which is a mirror image of an existing part.
2-44
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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. MIRROR Moves the current element to a new position which is calculated by reflecting the initial position in a specified plane.
MIRROR PLANE E45D THRO /TANK5 Reflects position of current element in plane which has given direction and which passes through /TANK5 (see Figure 2-31). Command Syntax:
>-- MIRRor -- <plane> -->
where <plane> is any of the standard ways of specifying a plane through a given point in a given direction:
<plane> = >-+| | | | | | | | | | | | | | || | | | | || | | | | | | || || DISTance <uval> -+- <repla> ------. | | ----------------| | <repla> --------------------------| | THRough <bpos> -------------------| | CLEArance -+- <uval> -. | | | | ----------+- <repla> -| | | |- <planf> -| | | -----------| DISTance - <uval> -+- <repla> -. | | | | |- <planf> -| | | | | -----------+-------------------| | CLEArance -+- <uval> -. | | | | ----------+- <repla> -. | | | | |- <planf> -| | | | | -----------+----------------| | <repla> -------------------------------------------| | THRough <bpos> ------------------------------------| | <planf> -------------------------------------------+-> PLAne <bdir> -+| | | || || -
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.2
2-45
INFront --. | BEHind ---+-- <sgid> ---. | | |-- <marke> --| | | -- <bpos> ---| | FROm --. | | | TO ----+-- <bpos> ------+-->
>--+-- ONTop --. | | -- UNDer --+-- <sgid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
/TANK5
Figure 2-31
2-46
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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 Noxzzle 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
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-1
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 Part 1 of the DESIGN Reference Manual.
3.2
Keywords: 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 Components physical details from the stated Specification.
Examples: PSPEC /A35B8 (At Pipe level) The PSPE attribute of the Pipe and all subsequently created Branches will be set to /A35B8. PSPEC /A15A2 (At Branch level) 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:
>-- PSPEcification
name -->
3-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3.3
Keywords: Description:
Examples: CONN PH TO /1205-N5 (Where /1205-N5 is a Nozzle) The Head attributes of the current element (Branch or Hanger) are set to match the position, orientation, bore and connection type of the Nozzle (see Figure 3-1). 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 (Where /100-A8/T2 is a TEE) The Tail attributes of the current element will be set to match the free ppoint on the specified TEE (see Figure 3-1). CONN PT TO P4 OF /VF205 (Where /VF205 is a VFWA.) The Tail attributes of the current element will be set to match the specified p-point. (Where /100-A8/1 is another Branch) The Head attributes of the current element will be set to match the Tail of the specified Branch. CONN PH TO PT OF /100-A8/1 CONN PH TO ID NOZZ@ As in the first example, but with the Nozzle identified by cursor selection.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-3
Note:
Before a CONNECT command is given, the Branch Specification attribute must be set. Connection to elements not within the designers jurisdiction (Read Only) will cause an inter-DB connection macro to be created automatically (see Part 1 of the DESIGN Reference Manual).
Command Syntax:
>-- CONnect <marke> TO --+-- <marke> --. | | -- <gid> ---+-->
Querying:
>-- Query --+-| |-| |-| -PHead --. | HHead --| | PTail --| | HTail --+-->
>-- Query --+-- HPosition --. | | -- TPosition --+-- WRT --. | | -- IN ---+--
<gid> -->
CE
/1205-N5
PH
CONN PH TO /1205-N5
H E A D
BRANCH
T A I L
PT
PA
PL
/100-A8/T2
Figure 3-1
3-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: TREF /PIPE2 HEAD Sets TREF of current element to point to Head of /PIPE2 and setsHREF of /PIPE2 to point back to the current element. HREF NULREF Unsets HREF; i.e. disconnects Head from any other element. Command Syntax:
>--+-- HRef --. | | -- TRef --+-- <gid> --+-- HEAD --. | | | | |-- TAIL --| | | | | ----------+ | | -- NULREF -------------+-->
Querying:
>-- Query --+-| |-| |-| -CE ------. | HEAd ----| | BRANch --| | TAIl ----+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-5
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. HDIR N WRT WORLD The Head direction is set as specified in World coordinates. HBOR 80 The Head Bore is set as specified. HCON OPEN The Head Connection Type is set as specified. 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 --+-- <bpos> --> >--+-- HDir --. | | -- TDir --+-- <bdir> --> >--+-- HBOre --. | | -- TBore --+-- <uval> --> >--+-- HCOnn --. | | -- TCOnn --+-- word -->
3-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
>-- Query --+-| |-| |-| -PHead --. | HHead --| | PTail --| | HTail --+-->
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 Components Leave p-point direction. If the Head is to be positioned in this way, Backwards Routing Mode must be in force.
Examples: POS PT DISTANCE 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 (In 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:
>-- POSition --+-| |-| |-| -PHead --. | PTail --| | HHead --| | HTail --+-- DISTance <uval> --. | | -- THRough <bpos> ---+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-7
Querying:
>-- Query --+-| |-| |-| |-| |-| -PHead ------. | PTail ------| | HTail ------| | HHead ------| | HPosition --| | TPosition --+-->
LAST COMPONENT
PL
D PT
1000
PH D
PA
30
OWNER AXES
Figure 3-2
3-8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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 crosssection will be taken into account. (Otherwise the HPOS or TPOS will be moved to the specified clearance, as no Tube geometry is available.)
Examples: BOP ONTO /BEAM (At the Head) This will position the Tube on top of /BEAM with a clearance of 0. TOP UNDER U3000 (At the Tail) This will position the Tail under the elevation U3000 with a clearance of 0. Note: If no Tube can be found emerging from the point specified, then only the points position can be used.
Command Syntax:
>--+-- BOP --. | | -- TOP --+-- <uval> --. | | ------------+-| |-| | |-| |-| |-| --
FROm --. | TO ----+-- <bpos> --> INFront --. | BEHind ---| | ONTop ----| | UNDer ----+-- <gid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-9
Querying:
>-- Query --+-| |-| |-| |-| |-| -PHead ------. | PTail ------| | HTail ------| | HHead ------| | HPosition --| | TPosition --+-->
UP
PH
PT
PH PT 3000 /BEAM
OWNER AXES
HORIZONTAL
Figure 3-3
3-10
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
This command allows the Head or Tail position to be moved by a specified distance, relative 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 DIST -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 Command Syntax:
>-- MOVe --+-| |-| |-| -PHead --. | HHead --| | PTail --| | HTail --+-- BY <pos> --+-- WRT --. | | | | |-- IN ---+-| | | --> | -- DISTance <uval> -->
<gid> -->
Querying:
>-- Query --+-| |-| |-| |-| |-| -PHead ------. | PTail ------| | HTail ------| | HHead ------| | HPosition --| | TPosition --+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-11
Figure 3-4
3-12
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: 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
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-13
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.
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. The CHOOSE command may be used within the same command line as a NEW command. Examples: CHOOSE Displays a general Selection form for the current element. Selection criteria displayed will depend on those available in the specification. Example form:
CHOOSE Current bore 100.00 mm Forced Connections are ON RATI 150.00 300.00
OK
CANCEL
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-15
CHOOSE TEXT Displays a Selection form listing choices based on the Specification Components (SPCOMs) 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:
CHOOSE Current bore 100.00 mm Forced Connections are ON Component Description EQUAL TEE BW SCH 40 X 40 REDUC TEE BW SCH 40 X 80 REDUC TEE BW SCH 40 X 80 Unset Unset
OK
CANCEL
CHOOSE RTEX CHOOSE STEX CHOOSE TTEX Displays a Selection form listing choices based on the SPCOMs Detail Description Text (obtained from the RTEX, STEX or TTEX attribute of the relevant DTEX element). Example form:
CHOOSE Current bore 100.00 mm Forced Connections are ON Component Description 150# RING GASKET 3MM THK 300# RING GASKET 3MM THK
OK
CANCEL
3-16
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
CHOOSE XTEX CHOOSE YTEX CHOOSE ZTEX Displays a Selection form listing choices based on the SPCOMs Material Description Text (obtained from the XTEX, YTEX, or ZTEX attribute of the relevant MTEX element). Example form:
CHOOSE Current bore 100.00 mm Forced Connections are ON Component Description SPIRAL WOUND SS ASBESTOS FILLED SPIRAL WOUND SS ASBESTOS FILLED
OK
CANCEL
CHOOSE ALL Combines the above CHOOSE and CHOOSE TEXT options. Example form:
CHOOSE Current bore 100.00 mm Forced Connections are ON RATI
150.00 150# RING GASKET 3MM THK SPIRAL WOUND SS ASBESTOS FILLED 300.00 300# RING GASKET 3MM THK SPIRAL WOUND SS ASBESTOS FILLED
OK
CANCEL
CHOOSE SPEC /RF150 As CHOOSE, but selections are made from the named specification rather than from that of the owning Branch.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-17
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. NEW REDU CHOOSE WITH ABOR 100 LBOR 80 Choose from Reducers with specified arrive and leave bores only NEW ELBO CHOOSE WITH 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 <gid> -. | | --------------+- DEFault -. | | -----------+- RTEX -. | | |- STEX -| | | |- TTEX -| | | |- XTEX -| | | |- YTEX -| | | |- ZTEX -| | | |- TEXT -| | | |- ALL --| .----<----. | | / | --------+- WITH -*- <wivl> --| | | | | - <wiwor> -+-> ->
where:
3-18
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
<wivl> is
>--+-- PBOre integer --. | | |-- ANgle ----------| | | |-- RAdius ---------| | | |-- ABOre ----------| | | |-- LBOre ----------| | | |-- PREssure -------| | | |-- TEMperature ----| | | -- RATing ---------+-- <uval> -->
and
<wiwor> is >--+-- STYpe --. | | |-- TYpe ---| | | |-- ACOnn --| | | |-- LCOnn --+-- word --> | |-- PCOnn integer word --> | -- word --+-- value --. | | -- word ---+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-19
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
3-20
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
attributes are ANGLE, RADIUS and SHOP, and HEIGHT if specified in the SELECT command. 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 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 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:
.------<-------. / | >-- SElect WIth --*-- SPec <gid> --| | | |-- <wivl> ------| | | |-- <wiwor> ----- | -->
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:
>-- Query --+-- SPRef --. | | -- TUbe ---+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-21
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 The current element will be Selected from the given Specification using the default choice. SEL WI SPEC /A3AH STYPE CTRL The current element will be Selected from the given Specification using the default choice except for STYPE.
3-22
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Note:
The Leave Tube will be selected from the default (Branch) Specification in all cases.
Command Syntax:
.-----<-----. | >-- SElect WIth SPec <gid> --* | |-- <wivl> ---| | | |-- <wiwor> -- | |-- <gid> --> | --> /
<wivl> and <wiwor> are explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual. Querying:
.-----<-----. / | >-- Query SPECification --*-- <qspci> --+-->
<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual.
>-- Query --+-- SPRef --. | | -- TUbe ---+-->
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 TUBE (At Branch) The Branch HSTU attribute (Head Specification Tube) will be Selected according to the default choice of TUBE. SEL TUBE WI STYP GLAS (At Component) The Component LSTU attribute (Leave Specification Tube) will be Selected with the default choice of TUBE except for STYPE.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-23
Command Syntax:
>-- SElect --+-| |-| |-| |-| |-| |-| -SPref ---. | LStube --| | HStube --| | LSrod ---| | HSrod ---| | TUbe ----| .-----<-----. | / | ROD -----+-- WIth -- *-- <wivl> ---| | | |-- <wiwor> -- | |-- <gid> --> | -->
Querying:
.-----<-----. / | >-- Query SPECification --*-- <qspci> --+--> >-- Query --+-| |-| |-| |-| |-| -SPRef ---. | TUbe ----| | LStube --| | HStube --| | LSrod ---| | HSrod ---+-->
3-24
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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.
Command Syntax:
>-- SHORtcode --+-- SPRef ---. | | |-- TUbe ----| | | |-- LStube --| | | |-- HStube --| | | |-- LSrod ---| | | |-- HSrod ---| | | ------------+-- name -->
Querying:
>-- Query --+-| |-| |-| |-| |-| -SPRef ---. | TUbe ----| | LStube --| | HStube --| | LSrod ---| | HSrod ---+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-25
3.5
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:
>-- RESElect -->
3-26
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
.-----<-----. / | >-- Query SPECification --*-- <qspci> --+-->
<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN Reference Manual..
>-- Query --+-- SPRef ---. | | -- TUbe ----+-->
Examples: RESEL WITH 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. 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 (At Branch) The current element HSTU attribute will be Selected using default parameters and the specified STYPE. If any further parameters are necessary they will be obtained from the old Specification Component.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-27
Command Syntax:
>-- RESElect --+-| |-| |-| |-| |-| |-| -SPref ---. | LStube --| | HStube --| | LSrod ---| | HSrod ---| | TUbe ----| .-------<------. | / | ROD -----+-- WIth -- *-- SPec <gid> --| | | |-- <wivl> ------| | | |-- <wiwor> ----- | -->
Querying:
.-----<-----. / | >-- Q SPECification --*-- <qspci> --+-->
<qspci> is explained in the section on Standard syntax Graphs in Part 1 of the DESIGN Reference Manual.
>-- Query --+-- SPRef ---. | | -- TUbe ----+-->
3.6
3-28
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
The standard Specification attributes of a Component are: SPREF LSTUBE This points to a Specification Component that provides the complete Catalogue description of the current element. These point to a Specification Component that provides the complete Catalogue LSROD description of the Tube emerging from the current element Leave Point. This points to an Insulation Specification. The Branch TEMPERATURE attribute is automatically used to determine an insulation thickness from this Specification. This points to a dummy Tracing Specification and is used by ISODRAFT to indicate trace heating requirements.
ISPEC
TSPEC
The remaining standard attributes are: POSITION The Components position in Zone coordinates (neither Branch nor Pipe have a POSITION, though Branch has head and tail positions (HPOS and TPOS). The Components orientation in Zone coordinates (neither Branch nor Pipe have an ORIENTATION, though Branch has head and tail directions (HDIR and TDIR). ARRIVE LEAVE BUILT SHOP ORIFLAG POSIFLAG The Catalogue p-point that is on the Arrive side of the Component. The Catalogue p-point that is on the Leave side of the Component. Management information to indicate if the item has actually been built. (Shop fabrication flag.) Used by ISODRAFT to determine in which material list the item is to be shown. (Logical orientation flag.) Set and used automatically by PDMS to determine if the Component has been oriented. (Logical position flag.) Set and used automatically by PDMS to determine if the Component has been positioned.
ORIENTATION
The following attributes do not occur in all Components, but are sufficiently common to be considered as standard: ANGLE HEIGHT RADIUS LOFFLINE The (variable) angle of a Component. The (variable) height of a Component. The (variable) radius of a Component. (Logical Offline flag.) Indicates, for reporting purposes, whether the Component breaks the Tube either side of it.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-29
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. (Multi-way Component Connection Reference.) Indicates the elements that are connected to the free (neither Arrive nor Leave) p-points of the Current Element.
CRFA
Command Syntax:
<gid> -->
3-30
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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.
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. Examples: ARR 2 LEAV 1 The Logical Route will Arrive at P2 and Leave at P1 of the Component. ARR 3 LEAV 2 The Logical Route will Arrive at P3 and Leave at P2 of the Component. Note: Default is Arrive 1, Leave 2.
Command Syntax:
>--+-- ARRive --. | | -- LEAve ---+-- P --------. | | -- integer --+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-31
When working in BACKWARDS mode, this situation reverses - the REDU need only be Flipped if a bore reduction is required. Examples: FLIP Reverses the current Arrive and Leave p-point numbers for that Component. Command Syntax:
>-- FLIP -->
Querying:
>-- Query --+-- ARRive --. | | -- LEAve ---+-->
ARRIVE
P1 CE
PH
PT Figure 3-5 Component Arrive and Leave attributes (standard and Flipped)
3-32
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: 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.
Command Syntax:
>-- SPRef name -->
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 the first Component to be specified (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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-33
Examples: LSTU /SPEC502/100L (At Branch 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 Branch) As above, but between the Head and Arrive of First Component (or Tail). LSR /HS20/2.5 As first example. HSR /HS20/2.5 As second example. Note: (At Hanger Component.) (At Hanger Component.)
These attributes are usually set automatically when the CHOOSE (or SELECT) command is used.
Command Syntax:
>--+-| |-| |-| -LSTube --. | HSTube --| | LSRod ---| | HSRod ---+-- name ----. | | -- NULREF --+-->
Figure 3-6
3-34
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: ISPE /I500-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.) ISP 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:
>-- ISPec --+-- name ---. | | -- NULREF --+-->
Querying:
>-- Query INSUlation -->
Examples: TSPE /TR50A The Current Component will be noted by ISODRAFT with the given trace heating requirements.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-35
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 --+-->
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 be itemised as SHOP FABRICATED in ISODRAFT. BUILT FALSE Information attribute indicating that current element has not been built. Command Syntax:
>--+-- SHOP ---. | | -- BUIlt --+-- TRue ---. | | -- FALse --+-->
3-36
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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. ORIF FALSE POSF TRUE This setting will occur if the item has been Selected in DESIGN but not oriented. ORIF 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:
>--+-- ORIFlag --. | | -- POSFlag --+-- TRue ---. | | -- FALse --+-->
Querying:
>-- Query --+-- POSFlag --. | | -- ORIFlag --+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-37
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. 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 fixed-angle elbows.
Examples: ANGL 45 (Before Selection) When the CHOOSE (or SELECT) command is given, it will choose the ANGLE45 option if available in the Specification. HEIG 300 (After Selection) If a variable height component, this dimension will alter as specified. Command Syntax:
>-- ANGle --+-- <uval> -----------------. | | -- <bdir> TOwards <bdir> --+--> >-- HEIght <uval> --> >-- RADius <uval> --> >-- DESParameters <uval> -->
3-38
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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-to-Leave centreline. Note: The default setting for this attribute is dependent upon Component type.
Command Syntax:
>--+-- LOFFline --. | | -- OFFLine ---+-- TRue ---. | | -- FALse --+-->
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
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-39
is the Catalogue which controls whether the item can actually be connected to by other Branches. Examples: CREF /PIPE1 TAIL Sets CREF of current element to point to Tail of /PIPE1 and sets TREF of /PIPE1 to point back to the current element. CREF NULREF Unsets CREF; i.e. disconnects this point from any other element. Command Syntax:
>-- CREF --+-- <gid> --+-- HEAD --. | | | | |-- TAIL --| | | | | ----------+ | | -- NULREF -------------+-->
Querying:
>-- Query --+-- CREf --. | | -- CRFA --+-->
3.7
3-40
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>- ORIentate -+- <bdir> IS <bdir> -. | | --------------------+- AND <bdir> IS <bdir> -. | | ------------------------+-->
Querying:
.-------------------<----------------. / | <marke> --*-- DIRection --. | | | | ---------------+-- WRT --. | | | | |-- IN ---+-- <gid> -- | -->
>-- Query
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-41
Figure 3-7
Figure 3-8
3-42
Examples: DIR E Rotate the Component about its origin such that (in forwards mode) its Arrive point is in the opposite direction to the previous Components 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). DIR AND P3 IS U45E As above, but P3 (rather than PL) is pointed to the new direction (see Figure 3-9). Note: If the new direction cannot be adopted by a fixed-angle Component, the item will be pointed in the closest direction to that specified.
Command Syntax:
>-- DIRection --+-- AND <marke> IS --. | | --------------------+-- <bdir> -->
Querying:
.-------------------<----------------. / | >-- Query <marke> --*-- DIRection --. | | | | ---------------+-- WRT --. | | | | |-- IN ---+-- <gid> -- | -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-43
Figure 3-9
3-44
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: CONNECT The arrive p-point of the Component is connected to the leave p-point of the Previous Component (see Figure 310). 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). CONNECT AND P3 IS U As first example and the off-line p-point is oriented upwards (see Figure 310). 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 -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> -> | | | | | --> | --> -->
Querying:
.------------------<----------------. / | >-- Query <marke> --*-- POSition --. | | | | --------------+-- WRT --. | | | | |-- IN ---+-- <gid> -- | -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-45
Figure 3-10
Component connection
Examples: FCONN The Arrive p-point of the Component is force-connected to the Leave p-point of the previous Component. FCONN TO TAIL The Leave p-point of the Component is force-connected to the Tail. FCONN AND P3 IS U As first example and the off-line p-point is oriented upwards.
3-46
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Note:
Only adjacent Components (not Attachment Points) may be forceconnected. No check on compatibility of bore or Connection Type occurs.
Command Syntax:
>- FCONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> --> | | | | | --> | --> -->
3.8
This command moves the Component along the constrained centreline by a specified distance.
Command Syntax:
>-- MOVe DISTance <uval> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-47
Querying:
>-- Query POSition <bpos> --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 3-11
This command moves the Component along the constrained centreline. The distance moved may be specified either in the direction moved or another planar direction.
Examples: MOVE PLANE N45E DIST 1000 The current Component is moved from its present position along the constrained centreline by 1000 along the N45E direction (see Figure 3-12). Command Syntax:
>-- MOVe PLAne <bdir> DISTance <uval> -->
Querying:
>-- Query POSition <bpos> --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
3-48
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-12
3.9
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-49
Examples: DIST 1000 The Component will be positioned on the constrained centreline 1000 from the origin of the previous Component (see Figure 3-13a). POS PA DIST 1000 As above, but the Arrive point of the Component is used (see Figure 3-13b). Command Syntax:
>--+-- POSition <marke> --. | | ----------------------+-- DISTance <uval> -->
Querying:
>-- Query --+-- POSition --. | | --------------+-- <marke> --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
3-50
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-13(b)
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-14). 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-15a). THR @ The Component will be placed on the constrained centreline where the perpendicular reference plane indicated by the cursor intersects (see Figure 3-15b).
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-51
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:
>--+-- POSition <marke> --. | | ----------------------+-- THRough <bpos> -->
Querying:
>-- Query --+-- POSition --. | | --------------+-- <marke> --+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
Figure 3-14
3-52
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-15(a)
Figure 3-15(b)
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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-53
Examples: DIST 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-16). DIST 1000 TO NEXT The Component will be placed on the constrained centreline so that its origin is 1000 before of the Next Components origin (see Figure 3-17a). POS PA DIST 20 FROM PL OF PREV The Component will be placed on the constrained centreline so that its Arrive point is 20 from the previous Components Leave point (see Figure 3-17b). 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:
>-+- POSition <marke> -. | | --------------------+- DISTance <uval> -+- FRom -. | | - TO ---+- <bpos> ->
Querying:
>-- Query <marke> --+-- POSition --. | | --------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
3-54
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-16
Figure 3-17a
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-55
Figure 3-17b
3-56
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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.
Examples: PLANE E DIST 1000 The Component will be placed on the constrained centreline so that its origin is 1000 from the previous Components origin in an East/West direction (see Figure 3-18). Command Syntax:
>-+- POSition <marke> -. | | --------------------+- PLANe <bdir> -+- DISTance <uval> -+- FRom -. | | | | - TO ---+- <bpos> -> | - THrough <bpos> ->
Querying:
>-- Query <marke> --+-- POSition --. | | --------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-57
Figure 3-18
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-58
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
POSITION
DISTANCE
INFRONT
BEHIND
This command positions the Component on the constrained centreline at a specified distance from a geometric object, point or position.
Querying:
>-- Query <marke> --+-- POSition --. | | --------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-59
Figure 3-19
3-60
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-20
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-61
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.
Examples: DISTANCE 35 ONTO /BEAM The Component will be placed on the Constrained Centreline so that its origin is 35 above the specified object (see Figure 3-21). DISTANCE 125 UNDER IDP @ The Component will be placed on the Constrained Centreline so that 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-21). Command Syntax:
>-+- POSition <marke> -. | | --------------------+- DISTance <uval> -+- ONTop -. | | - UNDer -+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query <marke> --+-- POSition --. | | --------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
3-62
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-21
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-63
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.
Examples: PLANE E DIST 1000 INFRONT /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-22). Command Syntax:
>-+- POSition <marke> -. | | --------------------+- PLAne <bdir> -. | | ----------------+- DISTance <uval> -+| || || -
ONTop ---. | UNDer ---| | INFront -| | BEHind --+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query POSition --+-- <bpos> --. | | ------------+-- WRT --. | | |-- IN ---+-| -->
<gid> -->
3-64
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-22
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-65
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.
Examples: CLEA 500 The Component will be placed on the constrained centreline 500 clear of the Previous Component (see Figure 3-23). Command Syntax:
>-- CLEArance <uval> -->
3-66
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Querying:
>-- Query <marke> --+-- POSition --. | | |-- BOP -------| | | -- TOP -------+-- WRT --. | | -- IN ---+--
<gid> -->
Figure 3-23
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-67
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 considered rather than the full item geometry.
Examples: CLEAR BEHIND /WALL The Component will be placed on the constrained centreline with zero clearance on the far side of the specified element (see Figure 3-24). CLEAR 1200 INF PL OF NEXT The Component will be placed on the constrained centreline with 1200 clearance this side of the Tube emerging from the Components Leave point (see Figure 3-24). Command Syntax:
>-- CLEArance --+-- <uval> --. | | ------------+-- INFront --. | | -- BEHind ---+-- <gid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
Querying:
>-- Query <marke> --+-- POSition --. | | |-- BOP -------| | | -- TOP -------+-- WRT --. | | -- IN ---+--
<gid> -->
3-68
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-24
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-69
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-25). 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-25). CLEAR 50 ONTO IDP @ 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-25). Command Syntax:
>-- CLEArance --+-- <uval> --. | | ------------+-- ONTop --. | | -- UNDer --+-- <gid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
Querying:
>-- Query <marke> --+-- POSition --. | | |-- BOP -------| | | -- TOP -------+-- WRT --. | | -- IN ---+--
<gid> -->
3-70
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-25
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-71
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.
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-26a). BOP 30 BEHIND /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-26a). BOP 30 BEHIND PL OF /FLAN As above, but 30 to the far side of the Leave Tube of /FLAN (see Figure 326b). Command Syntax:
>--+-- BOP --. | | -- TOP --+-- <uval> --. | | ------------+-| |-| |-| |-| |-| --
FROm --. | TO ----+-- <bpos> --> ONTop ----. | UNDer ----| | INFront --| | BEHind ---+-- <gid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
Note:
The meanings of BOP and TOP in this context are identical. They are merely provided to allow a sensible choice of syntax.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-72
Querying:
>-- Query <marke> --+-- POSition --. | | |-- BOP -------| | | -- TOP -------+-- WRT --. | | -- IN ---+--
<gid> -->
Figure 3-26a
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-73
Figure 3-26b
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.
3-74
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>-+- POSition <marke> -. | | --------------------+- PLAne <bdir> -. | | ----------------+- CLEARance <uval> -+| || || -
ONTop ---. | UNDer ---| | INFront -| | BEHind --+- <gid> --. | | |- <marke> -| | | - <bpos> --+->
Querying:
>-- Query <marke> --+-- POSition --. | | |-- BOP -------| | | -- TOP -------+-- WRT --. | | -- IN ---+--
<gid> -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-75
Figure 3-27
3-76
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
In some instances, the DRAG operation may fail to establish a constrained network. This may be because: The internal search limit has been reached A LOCKED element has been found in the network
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-77
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 INF /BUILD10 The current element and constrained network are moved specified clearance in front of element /BUILD10. Command Syntax: The full DRAG command syntax is extensive but may be summarised as follows:
>-- DRAG --+-- <absol> --. | | -- <relat> --+-->
North to the
where <absol> defines any absolute positioning command, e.g. AT, POS, etc. <relat> defines any relative positioning command, e.g. BY, MOVE, etc. The full expanded syntax is given below for reference:
<absol> = >--+-- AT --+-- <bpos> ---. | | | | -- <polar> --| | | |-- <pppos> --. | | | | -- <polar> --+--------+-->
3-78
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
<polar> = >--+-- POLar <bdir> --. | | ------------------+-- <plane> --> <pppos> = >-- POSition --+-- <marke> --+-- AT --+-- <bpos> ---. | | | | | | -- <polar> --| | | | | -- <polar> -----------| | | |-- AT --. | | | | --------+-- <bpos> ---. | | | | -- <polar> --+-------------+--> <plane> = >-+| | | | | | | | | | | | | | || | | | | || | | | | | | || || DISTance <uval> -+- <repla> ------. | | ----------------| | <repla> --------------------------| | THRough <bpos> -------------------| | CLEArance -+- <uval> -. | | | | ----------+- <repla> -| | | |- <planf> -| | | -----------| DISTance - <uval> -+- <repla> -. | | | | |- <planf> -| | | | | -----------+-------------------| | CLEArance -+- <uval> -. | | | | ----------+- <repla> -. | | | | |- <planf> -| | | | | -----------+----------------| | <repla> -------------------------------------------| | THRough <bpos> ------------------------------------| | <planf> -------------------------------------------+> PLAne <bdir> -+| | | || || -
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-79
INFront --. | BEHind ---+-- <sgid> ---. | | |-- <marke> --| | | -- <bpos> ---| | FROm --. | | | TO ----+-- <bpos> ------+-->
>--+-- ONTop --. | | -- UNDer --+-- <sgid> ---. | | |-- <marke> --| | | -- <bpos> ---+-->
<relat> = >--+-- BY <pos> --+-- WRT --. | | | | |-- IN ---+-- <sgid> --. | | | | ----------------------| | | -- <relmo> --------------------------+--> <relmo> = >- MOVe -+- <marke> -+- ALOng -. | | | | |---------+- <bdir> <plane> ----. | | | | |- BY <pos> -+- WRT -. | | | | | | | | - IN --+- <sgid> -| | | | | - <plane> ---------------------| | | |- ALOng -. | | | | |---------+- <bdir> <plane> ----------------| | | |- BY - <pos> -+- WRT -. | | | | | | - IN --+- <sgid> -----------| | | -- <plane> --------------------------------+->
3-80
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Figure 3-29(a)
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-81
Figure 3-29(b)
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 DISTANCE 1000 The current element and constrained network are moved South by the specified distance. DRAG DISTANCE 1000 ONTO /GRADE The current element and constrained network are 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.
3-82
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Note:
As it changes orientation as well as position, CONNECT cannot be used in conjunction with DRAG.
Command Syntax:
>-- DRAG --+-- <absol> --. | | |-- <relat> --| | | -- <botop> --+--> <botop> = >--+-- BOP --. | | -- TOP --+-- <uval> --. | | ------------+-- <repla> --. | | -- <planf> --+-->
Figure 3-30(a)
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
3-83
Figure 3-30(b)
Figure 3-31
3-84
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4.1
Examples: AUTOROUTE Enters Autoroute mode EXIT Returns to the full DESIGN syntax
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4-1
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: WEIGH 100 .01 100 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.
4-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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 Command Syntax:
>-- AXes <sgid> -->
Command Syntax:
.-----<----. / | >-- RPlanes --*-- <sgid> --+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4-3
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:
.----<-----. / | >-- PVolumes --+--*-- <sgid> --+--> | -->
Examples: ROUTE /PIPES All of the Branches belonging to /PIPES will be routed. ROUTE WITH BENDS /PIPES All of the branches belonging to /PIPES will be routed using Bends in preference to Elbows. Command Syntax:
>-- ROute --+-- WIth --+-- ELbows --. | | | | -- BEnds ---| .-----<----. | | / | -----------------------+--*-- <sgid> --+-->
4-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: OFFSET 5 Sets the offset to be five times the bore of its associated Nozzle. Command Syntax:
>-- OFFSETfactor integer -->
Querying:
>-- Query OFFSET -->
4.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4-5
Examples: SDIR E Sets the spread direction to be East about the centre of the PVOL SD N FR Ssets the spread direction to be North, starting from the south side 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:
>-- SDir <bdir> --+-- FRomside -----. | | |-- ABoutcentre --| | | -----------------+-->
4-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: BASE W Sets the base direction to be West. (This should always be perpendicular to the spread direction.) Command Syntax:
>-- BAse <bdir> -->
Examples: SPREAD /PIPES Spreads the pipes in /PIPES about the designated rack SP /PIPES WW 100 Spreads the pipes such that the wall-to-wall clearance is 100mm SP /PIPES WF 4IN 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-towall clearance of 75mm. SP ALL Repeat previously defined order sequence (for example, on a subsequent rack).
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4-7
Command Syntax:
>-- SPread --+-- WW ---. | | |-- FF ---| | | |-- WF ---| | | |-- ALL --| | | ---------+-- <uval> --. .-----<----. | | / | ------------+--*-- <sgid> --+-->
BOP The BOP command moves the specified pipes such that their outside diameters are resting on the rack plane in the BASE direction.
Note:
No ordering takes place with the BOP command; it is expected that the BOP command is used after a spread.
4-8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: ORDER /PIPES 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 --| | | ---------+-- <uval> --. .-----<----. | | / | ------------+--*-- <sgid> --+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
4-9
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-1
Fittings Steelwork Fittings and Panel Fittings are Catalogue items which can represent any ancillary item related to, but not an inherent part of, the structure, such as web stiffeners, lifting lugs, 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 joint or fitting owned (indirectly) by a GENSEC.
5.1
Keywords: 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.
Examples: NEW PNOD /PNOD1 AT E1000 N500 U500 (At FRMW or SBFR level) 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.
5-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>-- NPOSition -- <bpos> -->
(The standard element creation syntax is described in Part 1 of the DESIGN Reference Manual.) Querying:
Q NPOS
5.2
Keywords: 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 Sections 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 Direction) 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. Examples: STRING /COLUMN1 FROM /PNOD1 TO /PNOD2 Strings a Section named /COLUMN1 between the specified Primary Nodes. STRING 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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-3
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:
>-- STRIng -+- name -. | | --------+- word -. | | --------+- FRom - <gid> - TO | - TO - <gid> - FRom -
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.
Examples: 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.)
5-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
SPRef name
Querying:
Q SPRef
Examples: GTYP BEAM Sets the GTYP of the current Section to BEAM. Command Syntax:
>--- GTYPe --- word --->
Querying:
Q GTYPe
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-5
Examples: POSE E1250 N2000 D750 Positions the Sections end at the specified point. POSS /PNOD1 Positions the Sections start at the NPOS of the specified Primary Node. Command Syntax:
>--+-- POSStart --. | | -- POSEnd ----+-- <bpos> -->
Querying:
Q POSStart Q POSEnd
5-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
DRNE PERP Sets DRNE so that the end cutting plane is perpendicular to the Sections Z-axis (giving a square end as opposed to a chamfered end for a Section which has a skewed connection). Command Syntax:
>--+-- DRNStart --. | | -- DRNEnd ----+-- <bdir> ---------. | | -- PERPendicular --+-->
Querying:
Q DRNStart Q DRNEnd
POSE
NA
Querying:
Q BANGle
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-7
<gid> -->
Querying:
Q JOIStart Q JOIEnd
5-8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: CTYS BOLT The Sections 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 4 of the DESIGN Reference Manual for information about data consistency checking.) Command Syntax:
>--+-- CTYStart --. | | -- CTYEnd ----+-- word -->
Querying:
Q CTYStart Q CTYEnd
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-9
Command Syntax:
>--+-- SRELease --. .---<---. | | / | -- ERELease --+--*-- DX ---| | | |-- DY ---| | | |-- DZ ---| | | |-- RX ---| | | |-- RY ---| | | |-- RZ ---| | | -- sign --+-->
Querying:
Q SRELease Q ERELease
5-10
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5.4
Keywords: Description:
NEW
SNODE ZDISTANCE
SNOD elements are created, as for other Design elements, by using the NEW command. They are positioned by specifying their distance from their owning Sections Start Position, measured along the Neutral Axis towards the End Position. This distance, which is held in the Nodes 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, ppoint, p-line etc.), element or plane.
Examples: NEW SNOD /SNOD1 ZDIST 1500 (At SCTN level) Creates a Secondary Node named /SNOD1 at the specified distance from the start of the Section. The Node is positioned on the Neutral Axis of the owning Section. NEW SNOD /SNOD2 IS 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 ZDIS PROP .33 The new Node is positioned one third of the way along the Sections Neutral Axis, measured from the start of the Section. NEW SNOD /SNOD3 ZDIS PROP 0.25 FROM END The new Node is positioned one quarter of the way along the Sections Neutral Axis, measured from the end of the Section. NEW SNODE /SNOD5 ZDIS PLANE W30N DIST 0.0 The new Node is positioned at the intersection of the owning sections neutral axis with the defined plane.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-11
Command Syntax:
>-- ZDIStance --+-| |-| | | | | | | | |-| -<uval> --------------. | PROPortion -- value --+-- FRom --+-- STart --. | | | | |-- ENd ----| | | | | -- <gid> --| | | ----------------------+ | | <marke> ------------------------------------| | <plane> ------------------------------------+->
Querying:
Q ZDIStance
5.5
NEW
PJOINT
Examples: NEW PJOI /JOINT1 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.
Examples: SPRE /10X10.BRAK90 (The .BRAK90 suffix in the Specification Component name would normally indicate that this represents a 90 degree bracket joint.)
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-13
Command Syntax:
>--- SPRef name --->
Querying:
Q SPRef
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 Joints 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 Joints Origin Plane passes through the owning Node. The Origin Plane Direction (OPDI) is the direction of the normal to the plane through the Joints 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 Joints orientation is as defined by its Catalogue representation.
BANG defines orientation about Z axis OPDI defines orientation about X,Y axes
Z Y X
DY DZ
PNode
DX
Examples: DELP N4.5 Offsets the Joint by 4.5 (mm) in a northerly direction.
5-14
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
OPDI N Orientates the Joint so that the normal to its Origin Plane points North. BANG 180 Rotates the Joint about its current Origin Plane Direction by 180 degrees. Command Syntax:
>--- DELPosition --- <bpos> ---> >--- OPDIrection --- <bdir> ---> >--- BANGle ---+--- value ----------------------------. | | --- <bdir> --- TOwards --- <bdir> ---+--->
Querying:
Q DELPosition Q OPDIrection Q BANGle
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 Section 5.4. The Joints position with respect to the Section depends, therefore, upon the settings of two attributes: The Z-axis Distance (ZDIST) attribute of the owning SNOD. The Positioning Line (POSL) attribute of the SJOI itself. This defines the position of the Joint in relation to the p-line system which has been set up for the owning Sections Profile within the Catalogue. The default POSL setting is NA (Neutral Axis), so that the Joints Origin (more strictly, its JLIN) lies on the Sections Neutral Axis at the position specified by the ZDIST: that is, the Joints 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 Joints orientation is as defined by its Catalogue representation.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-15
SNode
TOS NA BOS
ZDIST defines position of SNode relative to POSS of Sectio
Examples: POSL TOS The Positioning Line of the Joint is coincident with the TOS (Top of Steel) pline 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:
>-- POSLine word -->
where word is usually one of the following: NA (Neutral Axis) TOS (Top of Steel) BOS (Bottom of Steel)
>-- BANGle --+-- value ------------------. | | -- <bdir> TOwards <bdir> --+-->
Querying:
Q POSLine Q ZDISTance Q BANGle
5-16
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5.6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-17
Querying:
Q CUTP
5-18
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: 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 <uval> -->
Querying: Q CUTBack
5.7
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-19
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 Joints JLIN. 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. Examples: CONN END TO /SJOINT3 Where the current element is a Section. CONN WITH START OF /BEAM1 Where the current element is a Joint. CONN START TO /PJOIN2 RECALC Connects the start of the current Section without moving the positions of any secondary elements owned by the Section. Command Syntax: At Section level:
>- CONnect -+- STart -. | | - ENd ---+- FREE -. | | --------+- TO
<gid> -->
5-20
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Following the resetting of a cutback allowance at a Joint (see Section 5.6.3): 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. Examples: RECON START Reconnects the start of the current Section. RECON END Reconnects the end of the current Section. RECON Command Syntax:
>-- RECOnnect --+-- STart --. | | |-- ENd ----| | | -----------+-- RECALCulate --. | | -----------------+-->
5.8
5-22
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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: Caution: POSS and POSE (Start and End Positions) DRNS and DRNE (Start and End Plane Directions) JOIS and JOIE (Start and End Joint References)
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. The Member List of the Flipped Section remains unchanged, so that any cross-references 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.
Examples:
FLIP Reverses the Start and End attribute settings for the current element as outlined in the preceding description.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-23
Command Syntax:
>--- FLIP --->
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: Q ATT Q DER POS For checking, in particular, all Start and End related settings (POSS/POSE, DRNS/DRNE, etc). For checking the derived positions of SNODs and/or SJOIs.
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. Absolute positioning (AT command) is possible only for Sections, Primary Nodes, Routing Planes and Panels.
Examples: MOVE ALONG E45N DISTANCE 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-24
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-25
EXTEND PROP -0.2 Moves POSE (defaults to END) so as to decrease the Sections length by 20%. EXTEND END PLANE E30N DIST 0.0 Moves POSE to meet the defined plane. Command Syntax:
>-- EXTend --+- STart -. | | |-- ENd* -| | | ---------+| || | || -
PROPortional - value -. | BY --- <axpos> ------| | | <plane> -------------| | <uval> --------------+- RECALCulate --. | | ----------------+->
5-26
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: ROTATE BY -45 Rotates by 45 about the elements 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 E-W axis (clockwise when looking E). ROTATE ABOUT E BY 45 The same as the preceding example. ROT THRO POSE ABOUT S BY -25 Rotates a Section about an axis which passes in the N-S direction through its End position. The rotation is 25 anticlockwise when looking S along this axis. ROT ABOUT PPLIN TOS BY 45 Rotates by 45 about the Top-of-Steel p-line (clockwise when looking in the Start to End direction). ROT AND PPLIN BOS IS 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 IS N45W25D Rotates element until the Y axis points as closely as possible to the N45W25D direction. ROT AND PPLIN TOS IS PPLIN BOS OF /SCTN1 LEAV DIR WRT /STRU1 Rotates element until its TOS p-line points in the direction of the BOS pline of /SCTN1 in the specified coordinate system. Command Syntax: Rotation about a given axis:
>- ROTate ABOut -+- <plin> -. | | - <bdir> -+- THRough - <bpos> -+- BY -+- <uval> -------------------. | | | | | | - <bdir> TOwards <bdir> ---| | | | | - AND -+- <plin> -. | | | | | | - <bdir> -+- IS <bdir> ----| | | |- BY - +- <uval> --------------------. | | | | | | - <bdir> - TOwards - <bdir> -+ | | | | - AND -+- <plin> -. | | | | | | - <bdir> -+- IS - <bdir> ----+- THRough <bpos> -| | | ------------------+-->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-27
Note:
5-28
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5.9
Z Y X PLIN NA POSE Y
Z X SITE axes
SCTN axes
Figure 5-1
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-29
Examples:
PPLINE TOS Specifies the Top-of-Steel p-line of the current element. PPLINE BOS OF /BEAM2 Specifies the Bottom-of-Steel p-line of /BEAM2. IDPLINE @ Specifies the p-line to be picked using the cursor. Command Syntax: (This is the <plin> syntax referred to elsewhere in this manual.)
>--+-- PPLINe -- word --+-- OF <gid> --. | | | | ---------------+ | | --- IDPLine -- @ -------------------+-->
where word is the setting of the p-lines 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-30
Examples: POSITION PPLINE BOS 500 Calculated position is on the BOS p-line, 500mm from its start (by default); for setting a variable or for querying. POS PPLIN TOS 1000 FROM END Calculated position is on the TOS p-line, 1000mm from its end. POS AT PPLIN NA OF /SCTN2 PROP .25 Calculated position is on the Neutral Axis of /SCTN2, 25% along its length as measured from its start (by default). POS AT PPLIN TOS OF /BEAM1 END Position is defined as the end of the TOS p-line of /BEAM1 (probably, but not necessarily, the POSE setting for /BEAM1). BY PPLIN TOS OFFSET FROM PPLIN BOS Moves the current element (Section or Joint) by the offset distance between its TOS and BOS p-lines. BY PPLIN BOS OFFSET FROM PPLIN TOS Moves the same distance as the preceding example, but in the opposite direction. BY PPLIN TOS -OFFSET FROM PPLIN BOS The same effect as the preceding example. 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 Chapter 2, Equipment and Primitives, which also apply to Structural steelwork elements.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-31
Querying:
Q <plin> --+-- <uval> --------------. | | |-- PROPortion - value --+--------------------------. | | | | -- FROm --. | | | | -----------------------------------+-- STart* --. | | | | -- ENd -----+--+--> Q <plin> -- OFFSet --+-- FROm -- <plin> --. | | --------------------+-->
Querying Examples: Q PPLIN TOS END Position of end of p-line. Q PPLIN BOS PROP 0.3 Position of point 30% of distance along BOS from start (by default) towards end. Q PPLIN NA PROP -1.5 FROM END Position of point which is 1.5 times length of Neutral Axis away from end of p-line in direction away from start. Q PPLIN TOS OFFS FROM PPLIN BOS Offset distance between TOS and BOS. Q PPLIN TOS OFFS Offset distance between TOS and Neutral Axis (by default).
Examples: ORI Y IS PPLIN TOS OF /SCTN1 X DIR AND Z IS 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.
5-32
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Command Syntax:
>-- <plin> --+-- X ------. | | |-- Y ------| | | |-- Z ------| | | |-- LEAve --| | | -----------+-- DIRection -->
Querying:
Q <plin> --+-- X ------. | | |-- Y ------| | | |-- Z ------| | | |-- LEAve --| | | -----------+-- DIRection -->
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-33
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-34
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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. Examples: SPLIT PLANE N THRO N1000 Splits current panel along its line of intersection with the specified plane SPLIT ON /BEAM1 Splits current panel along the Neutral Axis (projected if necessary) of the named section Command Syntax:
>-- SPLIT --+-- PLANE <dir> -- THROugh <bpos> --. | | -- ON <section_id> ----------------+-->
* *
PANE2 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 Panels PAVEs to point to the corresponding SEVEs on the linear joint, thus:
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-35
* *
PANE
* *
SCTN SELJ
Keywords: Description:
LINK UNLINK 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 Loops 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.
5-36
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Examples: LINK VERT CE TO /PAVE2 Links current vertex (slave) to vertex /PAVE2 (master). LINK PANEL /PANE3 TO EDGE /PAVE5 /PAVE6 AFTER /PAVE2 Links panel /PANE3 to edge between /PAVE5 and /PAVE6 and positions any new vertices needed after /PAVE2 in the PLOOP of /PANE3. Command Syntax:
>- LINK -+-+----------. | | | | - VERTex -+- <vidlist> - TO - VERTex - <vid> -------------. | | |--- EDGE - <eidlist> - TO - EDGE - <eid> -------------------| | | --- PANEl - <pid> - TO -+- JOINt - <jid> ---- <qualifier1> -| | | |- VERTex - <vid> -. | | | | - EDGE - <eid> ---+- <qualifier2> -+-->
where: <vid> is a vertex identifier (name, refno, treename) <vidlist> is a list of vertex identifiers <eid> is an edge identifier (pair of consecutive vids) <eidlist> is a list of edge identifiers (must be an even number of vids) <pid> is a panel identifier (name, refno, treename) <jid> is a joint identifier (name, refno, treename) <qualifier1>:
>-+- FROM -+- START - TO -+- <vid> -. | | |- END ---| | | ---------+--. | |- END - TO ---+- <vid> -. | | | |- START -| | | | ---------+--| | |- <vid> - TO -+- <vid> -. | | | |- START -| | | | |- END ---| | | | ---------+--| | ---------------------------| ------------------------------------+- FORWards --. - BACKwards -+- AFTer <vid> ---------. |- BEFore <vid> --------| |- BETween <vid> <vid> -| -----------------------+->
The FROM/TO options specify which portion of the joint is to be linked to the panel. Defaults are implied start to implied end of joint. The FORWARDS/BACKWARDS options specify the direction of vertices within the joint.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-37
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). <qualifier2>:
>--+-- AFTer <vid> ----------. | | |-- BEFore <vid> ---------| | | |-- BETween <vid> <vid> --| | | -------------------------+->
The AFTER/BEFORE/BETWEEN options specify the position in the Panel Loop at which to create vertices corresponding to those of the master vertices.
>-- UNLINK --+-- <vid> -- FRom -- <vid> --. | | -- ALL ---------------------+-->
5-38
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-39
Command Syntax: Setting parameters in default order in the array, starting at parameter number 1:
5-40
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
.--------------<------------. / | >-- DESParameters --+-- <expres> -----------------| | | |-- <uval> -------------------| | | |-- READ ---------------------| | | -- word --+-- OF -- <gid> --| | | ------------------+-->
Querying:
.--------------<-------------. / | Q --*-- DESParameters - integer ---+--->
Querying Examples: Q DESP 1 DESP 3 Outputs values of design parameters 1 and 3. Q DESP Outputs values of all design parameters. Q (WDESP[1]) Extracts a word from within DESP 1. FINCH DIST Q (DDESP[2]) Extracts a distance (in feet and inches) from within DESP 2.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-41
As with the design parameters described in Section 5.12.1, an OPAR or APAR is referenced in the design by means of its numbered position in the corresponding array.
5-42
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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:
A straight line (this is the default) A circular arc, defined by a radius and a conditioning point. An arc passing through a specified through-point position. An arc defined by a bulge factor and a conditioning point. A fillet arc and two adjacent straights, defined by a radius and a pole position. 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 GENSECs 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
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-43
(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.
Examples: 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 SPINE Creates Spine with no defined path. NEW POINSP First Spine Point defines Start Position (POSS). NEW POINSP Last Spine Point defines End Position (POSE). Spine at this stage is a straight line. NEW CURVE (Created between POINSPs). The attributes of this curve determine the shape of the Spine path between the adjacent POINSPs. (See Section 5.13.3.)
5-44
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
nearest POINSP to the circle lies on the circle; the arc terminates on this point. 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-46
in the case of a CURVE, the POINSP to be used as the origin from which DISTANCE and PROPORTION are measured; the segment of the GENSEC to which PROPORTION is applied as: the named CURVE, the segment following the POINSP (from START), or the segment preceding the POINSP (from END).
For example: PPLINE TOS PROPORTION 0.4 FROM END VIA SPINE OF /CURVE3 calculates a position 40% along /CURVE3 measured from its end. If no POINSP or CURVE is specified, PROPORTION is calculated from the start of the GENSEC. Directions and Offsets Derived From P-lines (see Section 5.9.3): Directions and offsets derived from p-lines can have a derived position 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: PPLINE TOS X DIRECTION PROP 0.4 VIA PLINE FROM END OF /CURVE3 PPLINE TOS OFFSET FROM PPLINE BOS DISTANCE 200 FROM END If no position is given, the direction/offset is calculated using the start of the GENSEC 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: PPLINE pline_name NORMAL/CUTBACK NEAR direction THROUGH position [VIA SPINE/PLINE] BOUND/UNBOUND The probe line starts at the THROUGH position and extends in the specified direction. 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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-47
Identifying P-line Elements: P-line expressions can be used in any positioning command (DISTANCE, PROPORTION, NEAR etc.) in the following way: ID SEGMENT PPLINE ... positioning_command ID ONPLINE PPLINE ... 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 pline.) The following expressions use keywords analogous to the OFFSET option between the p-line specification and the subsequent positioning command: PPLINE PPLINE PPLINE PPLINE pline_name pline_name pline_name pline_name PLDIST positioning_command PLKEY positioning_command SEGMENT positioning_command ONPLINE positioning_command
PPLINE...SEGMENT and PPLINE...ONPLINE return references to the segment and p-line, respectively, on which the point is specified. PPLINE...PLDIST returns the distance 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 name (the PKEY) of the p-line on which the point lies.
5-48
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 attribute settings: TPREF and HPREF specify, by reference to POINSPs of the parent GENSEC (more strictly, its Spine), the start and end points, respectively, 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
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.
5-49
including a POINSP which has been specially inserted for this purpose if necessary, as summarised in Section 5.13.5. 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 plines 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.
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 Section (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 user-defined 2D shape through a specified distance (equivalent to the Panel's height/thickness). This could be used, for example, to represent a column, where the 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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
5-51
DUNION = 0
DUNION = 1
DUNION = 2
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.
5-52
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
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
The 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.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
6-1
Design Templates
6.2
World (/*) SITE ZONE EQUI BOX Copy NBOX NBOX TPWL TMAR TMPL BOX
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:
TPWL TMAR TMPL BOX NBOX Copy and Execute Rules PFIT TMPL BOX NBOX PANE PLOO PAVEs
6-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Design Templates
6.3
PFIT local TMPL current local BOX current DDSE(2) DDSE(1) template
The pseudoattributes available for accessing the properties data in the various types of dataset are as follows:
Current Dataset List of property keys Real property values Text or real property values Text or real property default values Reference settings CDPL CDPR TCDP TCDD CFDP Local Dataset DEPL LDPR DEPR DEPD LFDP Template Dataset PRLS TDPR PROP PRDE TFDP
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
6-3
Design Templates
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 elements 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 reexecuted to give the correct XLEN.
6.4
6-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Design Templates
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.
Examples: LNAME /ANTHONY Sets local name for current element LNAME UNSET Unsets local name for current element Command Syntax:
>--- LNAMe ---*--- local_name ---. | | --- UNSET --------+--->
Querying: Q LNAMe Gives local name for current element Q LNLST Lists all local names for elements under current template Q ATT (Note that local names are stored in a compressed numeric format)
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
6-5
Design Templates
MLNID /JOE Identifies element defined in member template (i.e. in template owned by current element) (XLEN OF LNID /SID) Uses dimension of locally named element in expression (XLEN OF MLNID /JOE) Command Syntax:
>---+--- LNid ----. | | --- MLNid ---+--- local_name --->
Querying: Q LNID /SID Q MLNID /JOE For element in current template For element in member template
6.5
Keywords: Description:
RSEQNUMBER 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.
6-6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Design Templates
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: 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
6.6
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
6-7
Design Templates
Z Y
Origin
Design Point
Orientation
Direction of Normal
A Cylindrical P-point is specified as a position on the surface of a cylinder at a given position and with given dimensions, thus:
Design Orientation Point Direction of Normal
Z Y
Origin
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 Y
Origin
Orientation Direction of Normal Direction radius acts in, defining point position wrt sphere's centre
6-8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Design Templates
6.7
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.
6.8
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
6-9
Groups
The commands described in this chapter allow you to define groups of items that can then be manipulated as a single entity. Note that these commands have largely been superceded by the use of lists and collections, defined using expressions.
7.1
Keywords: Description:
Examples:
GADD /ZONE1 /VALVE2 Adds /ZONE1 and /VALVE2 to the current Group, starting from the current list position GREMOVE /ZONE1 /BOX3 Removes /ZONE1 and /BOX3 from the current Group and moves the current list position pointer to the Head position
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
7-1
Groups
GADD MEM OF /BRANCH1 /BRANCH2 Adds all the pipe Components in Branches /BRANCH1 and /BRANCH2 to the current Group, starting from the current list position GREM MEM OF /PIPE100 MEM OF /EQUI-B Removes all Branches of the Pipe /PIPE100 and all members of Equipment /EQUI-B from the current Group GREM ITEMS OF /ZONE2 Removes from the current Group all occurrences of those offspring of /ZONE2 which are items GADD ALL EQU BRAN OF /ZONE1 /ZONE2 Adds all offspring of /ZONE1 and /ZONE2 which are of types Equip or Branch to the current Group, starting from the current list position Command Syntax:
>--+-- GADD -----. .-------------. | | / | -- GREMove --+---*-- <selatt> ---+--->
7.2
Accessing Groups
END Groups exist outside the normal design hierarchy in a Group World (GPWL). The available Group Worlds can be seen by querying Members at the top (WORLD) level in the hierarchy. Groups can be accessed either directly by name, or by descending the hierarchy in the normal way. The items in a Group are shown as Members, but it is important to appreciate that the Group does not actually own them. These Members all have normal locations in the design hierarchy, but are also Members of a Group.
Keywords: Description:
Examples: END (At a Group Member) If the current element was accessed via the Group, the Group will be accessed. Otherwise the current elements owner will be accessed. OWNER (At a Group Member) The current elements owner will always be accessed regardless of the method of access to the current element. Command Syntax: See the navigation commands described in Part 1 of the PDMS Design Reference Manual.
7-2
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Groups
7.3
Deleting Groups
DELETE The action of this command differs from normal behaviour if the current element is a Group.
DELETE GROUP Only the current element and any Offspring that are Groups will be deleted. DELETE GPWLD Only the current element and any Offspring that are Groups will be deleted. DELETE GROUP MEM The Members of the Group are deleted in the following way: If the member is not a Group, it is deleted with all its Offspring. If the member is a Group, only the member and any Offspring that are Groups are deleted.
Command Syntax:
>-- DELETE <snoun> -+-- MEMbers --+-- integer --+-- TO integer -> | | | | | --> | --> -->
7.4
Copying a Group
COPY Groups may be copied with a slightly different effect to normal elements.
COPY /GROUP21 (At a Group.) The Current Group will contain exactly the same Members as /GROUP21. No new elements have been created. COPY MEM OF /GROUP21 (At a Zone.) The current Zone will contain new elements which are identical to the Members of /GROUP21 provided these elements are all legal members of a Zone. COPY MEM OF /GROUP21 RENAME /MAIN /SPARE As above, but with renaming.
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
7-3
Groups
Command Syntax:
>- COPY -+- MEMbers -+- integer -+- TO integer -. | | | | | -----------+--------------+- OF <sgid> -+- REName name name -> | | | -> |- ALL OF -. | | ----------+- <sgid> -+- REName name name -> | ->
7-4
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Index
<plin> syntax, 5-30 ALONG command, 2-33 ARRIVE command, 3-31 AT command, 2-6 Attached parameters, 5-41 Attributes of primitives, 2-1 sections, 5-4 AUTOROUTE command, 4-1 AXES command pipe routing, 4-2 BANGLE command, 5-7, 5-14 BASE command pipe routing, 4-7 BEHIND command, 2-27, 3-9, 3-59 Beta angle joints, 5-14 sections, 5-7 BOP command, 3-9, 3-72 pipe routing, 4-8 Branch head, 3-3 tail, 3-3 Buildings, 5-50 BUILT flag, 3-36 BY command, 2-16 Cartesian p-point in design pointset, 6-7 CDPR attribute, 6-4 CHOOSE command, 3-14 CLEARANCE command, 2-35, 3-66
Cofitting element, 5-38 Cofitting Reference Array attribute, 5-38 Compound fitting element, 5-2 Compound Floor element, 5-50 Compound joint element, 5-1 Compound panel fitting element, 5-2 Compound Screed element, 5-50 Compound Wall element, 5-50 CONNECT command, 2-14, 3-3, 3-45, 5-19 Connection forced, 3-46 CRFA attribute, 3-39 CTYEND command, 5-8 CTYSTART command, 5-8 Current design dataset, 6-3 Current Design Dataset Property attribute, 6-4 CURTYP attribute, 5-43, 5-45 Curve element, 5-43 Curve Type attribute, 5-43, 5-45 CUTBACK command, 5-18 CUTPLANE command, 5-18 Cylindrical p-point in design pointset, 6-8 DDAT element, 6-3 DDDF attribute, 6-3 DDPR attribute, 6-3 DDSE element, 6-3 DELPOSITION command, 5-14 Design Data Default attribute, 6-3 Design Data element, 6-3 Index-1
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Index
Design Data Property attribute, 6-3 Design Dataset element, 6-3 Design parameters, 5-40 Design Pointset element, 6-7 Design Template element, 6-2 DESPARAMETER command, 5-40 Detail level, 2-3 DIRECTION command, 3-43 DISCONNECT command, 5-21 DISTANCE command, 3-49, 3-53 DKEY attribute, 6-3 DPSE element, 6-7 DRAFT Union attribute, 5-51 DRAG command, 3-78 DRNEND command, 5-6 DRNSTART command, 5-6 DUNION attribute, 5-51 Edge drawing, 5-51 Elements connecting, 2-14 moving, 2-16 orientating, 2-11 rotating, 2-12 End position (section), 5-4, 5-5 ERELEASE command, 5-9 EXTEND command, 5-25 FCONNECT command, 3-46 Fitting element, 5-2, 5-38 compound, 5-2 panel, 5-2 Fixing element, 5-2, 5-44, 5-49 FLIP command, 3-31, 5-22 Floors, 5-50 FORCECONNECT command, 3-14 Forced connection, 3-46 FROM command, 3-53 GADD command, 7-1 Index-2
Generic Fixing element, 5-49 Generic Section element, 5-2, 5-43 GENSEC element, 5-2, 5-43 GREMOVE command, 7-1 Group element, 7-1 HBOR command, 3-6 HCON command, 3-6 HDIR command, 3-6 Head of branch, 3-3 HPOS command, 3-6 HREF command, 3-5 HSPE command, 3-2 HSROD attribute, 3-33 HSTUBE attribute, 3-33 IDPLINE command, 5-30 INFRONT command, 2-27, 3-9, 3-59 Instance Design templates, 6-1 Insulation specification, 3-35 ISPEC attribute, 3-35 JLDATUM element, 5-43, 5-48 JOIEND command, 5-8 Joint creating, 5-12 Joint element compound, 5-1 linear, 5-1 primary, 5-1, 5-12 secondary, 5-1, 5-13 Joints attributes, 5-17 linear, 5-35 primary, 5-14 secondary, 5-15 JOISTART command, 5-8 Justification Line Datum element, 5-43, 5-48
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Index
LEAVE command, 3-31 LEVEL command, 2-3 Linear joint element, 5-1 Linear joints, 5-35 LINK command, 5-36 LNAME, 6-5 LNID, 6-5 Local design dataset, 6-3 Local name Design templates, 6-4 LOFF attribute, 3-39 LSROD attribute, 3-33 LSTUBE attribute, 3-33 MIRROR command, 2-45 MLNID, 6-5 MOVE command, 2-17, 3-11, 3-47 Node element primary, 5-1 secondary, 5-1 Nodes primary, 5-2 secondary, 5-11 Nozzle offset factor pipe routing, 4-5 Nozzles specifying, 2-3 OBSTRUCTION command, 2-4 Obstruction level clash detection, 2-4 OFFSETFACTOR command, 4-5 ONTOP command, 2-30, 3-9, 3-62 OPDIRECTION command, 5-14 ORDER command pipe routing, 4-8 ORIENTATE command, 2-11, 3-41 Orientation, 2-11 ORIFLAG attribute, 3-37
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Owning parameters, 5-41 Panel fitting element compound, 5-2 Panel Fitting element, 5-2, 5-38 Panel Fitting Reference attribute, 5-38 Panel Loop element, 5-1 Panel Vertex element, 5-1 Panels connecting, 5-35 creating, 5-34 splitting, 5-34 Parameters attached, 5-41 design, 5-40 owning, 5-41 Penalty volume pipe routing, 4-2, 4-3 PH command, 3-7 Pipe rack pipe routing, 4-6 Pipe routing, 4-1 PJOINT command, 5-12 PLDATUM element, 5-44, 5-48 Pline Datum element, 5-44, 5-48 PNODE command, 5-2 POINSP element, 5-43 POLAR command, 2-8 Polar positioning, 2-8 POSEND command, 5-5 POSFLAG attribute, 3-37 POSITION command, 2-6, 3-49 Positioning, 2-6 POSLINE command, 5-15 POSSTART command, 5-5 PPLINE command, 5-30 Primitives attributes, 2-1 Index-3
Index
Profile element, 5-1, 5-4 PSPE command, 3-2 PT command, 3-7 PVOL command, 4-3 RACK command, 4-6 RECONNECT command, 3-13, 5-21 RESELECT command, 3-26 Ring Wall element, 5-51 Rod attributes, 3-33 ROTATE command, 2-12 ROUTE command, 4-4 Routing plane pipe routing, 4-2, 4-3 RPLANE command, 4-3 RSEQNUMBER, 6-6 Rule sequence number Design templates, 6-6 Screeds, 5-50 SDIR command pipe routing, 4-6 Sections attributes, 5-4 connecting, 5-19 creating, 5-3 disconnecting, 5-21 modifying lengths, 5-25 reconnecting, 5-21 SELECT command, 3-20 SHOP flag, 3-36 SHORTCODE command, 3-24 SJOINT command, 5-13 SNODE command, 5-11 Soft types, 5-50 Spherical p-point in design pointset, 6-8 Spine element, 5-2, 5-43 Index-4
Spine Point element, 5-43 SPLIT command, 5-34 SPREAD command pipe routing, 4-7 SPREF attribute, 3-33 SRELEASE command, 5-9 Start position (section), 5-4, 5-5 Steelwork fittings, 5-2 fixings, 5-2 generic sections, 5-2 joints, 5-1 nodes, 5-1 panels, 5-1 sections, 5-1 Straight Wall element, 5-51 STRING command, 5-3 Subfitting element, 5-2 Subjoint element, 5-1 Tail of branch, 3-3 TBOR command, 3-6 TCON command, 3-6 TDIR command, 3-6 Template Area element, 6-2 Template design dataset, 6-3 Template World element, 6-2 THROUGH command, 3-51 TMAR element, 6-2 TMPL element, 6-2 TO command, 3-53 TOP command, 3-9, 3-72 TPOS command, 3-6 TPWL element, 6-2 Trace specification, 3-35 TREF command, 3-5 TSPE attribute, 3-35 Tube
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Index
attributes, 3-33 UNDER command, 2-30, 3-9, 3-62 Unioning edges, 5-51 UNLINK command, 5-36
UNTIE, 6-9 Wall element, 5-51 Walls, 5-50 ZDISTANCE command, 5-11
PDMS DESIGN Reference Manual Part 2: Creating the Model Version 11.3
Index-5