Design Reference Manual - Creating The Model

Manual de Referencia de diseño
Creación del modelo

AVEVA Solutions Ltd
Renuncia
La información de carácter técnico, y los detalles del producto y su uso, es proporcionada por
AVEVA Solutions Ltd y sus subsidiarias sin garantía. AVEVA Solutions Ltd y sus subsidiarias
renuncian a todas y cada una de las garantías y condiciones, expresas o implícitas, en la máxima
medida permitida por la ley.
El autor ni AVEVA Solutions Ltd, ni ninguna de sus subsidiarias, serán responsables ante ninguna
persona o entidad por cualquier acción, reclamo, pérdida o daño que surja del uso o posesión de
cualquier información, datos o errores en esta publicación, o cualquier uso del producto, en absoluto.
Copyright
Los derechos de autor y todos los demás derechos de propiedad intelectual de este manual y del
software asociado, así como de todas las partes del mismo (incluido el código fuente, el código objeto,
los datos que contiene, el manual y cualquier otra documentación suministrada con él) pertenecen a
AVEVA Solutions Ltd o sus subsidiarias.
Todos los demás derechos están reservados a AVEVA Solutions Ltd y sus subsidiarias. La
información contenida en este documento es comercialmente sensible, y no se copiará, reproducirá,
almacenará en un sistema de recuperación ni se transmitirá sin el permiso previo por escrito de
AVEVA Solutions Ltd Cuando se conceda dicho permiso, expresamente requiere que este aviso de
Exención de Responsabilidad y Derechos de Autor se muestre prominentemente al principio de cada
copia que se hace
El manual y la documentación asociada no pueden ser adaptados, reproducidos o copiados, en

ningún material o forma electrónica, sin el permiso previo por escrito de AVEVA Solutions Ltd. El
usuario tampoco puede realizar ingeniería inversa, descompilar, copiar o adaptar el software
asociado. Ni la totalidad, ni parte del producto descrito en esta publicación pueden incorporarse a
ningún software, producto, máquina o sistema de terceros sin el permiso previo por escrito de
AVEVA Solutions Ltd, salvo lo permitido por la ley. Cualquier acción no autorizada está
estrictamente prohibida, y puede dar lugar a responsabilidades civiles y proceso penal.
Los productos AVEVA descritos en esta guía deben instalarse y operarse estrictamente de acuerdo
con los términos y condiciones de los respectivos acuerdos de licencia, y de acuerdo con la
documentación del usuario pertinente. El uso no autorizado o sin licencia del producto está
estrictamente prohibido.
Publicado por primera vez en septiembre de 2007

© AVEVA Solutions Ltd y sus subsidiarias 2007
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, Reino Unido.
Marcas
AVEVA y Tribon son marcas comerciales registradas de AVEVA Solutions Ltd o sus subsidiarias.
Queda estrictamente prohibido el uso no autorizado de las marcas comerciales AVEVA o Tribon.
Los nombres de productos de AVEVA son marcas comerciales o marcas comerciales registradas
de AVEVA Solutions Ltd o sus subsidiarias, registradas en el Reino Unido, Europa y otros países
(en todo el mundo).
Los derechos de autor, derechos de marca u otros derechos de propiedad intelectual sobre
cualquier otro producto, su nombre o logotipo pertenecen a su respectivo propietario.
DESIGN Reference Manual
Manual de referencia DESIGN
Contenido Page
Creación del Modelo

Introducción___________________________________________________ 1:1
Acerca del Manual de Referencia de Diseño ________________________1:1
Organización del Manual de Referencia de Diseño___________________ 1:1
Organización de este Manual ____________________________________ 1:1
Equipos y Primitivos _____________________________________ 2:1
Atributos primitivos de Modelado _________________________________2:1
Dimensionamiento de bloques de Construcción Primitivos _____________2:1
La elección del tamaño, la clasificación y la altura de la boquilla_________________ 2:2
Niveles de detalle de Modelado___________________________________________2:3
Configuración de obstrucción____________________________________________2:4
Posicionamiento en un punto conocido________________________ 2:5
Posicionamiento de una coordenada_______________________________________2:5
Posicionamiento polar desde el origen______________________________________2:8
Posicionamiento Polar General desde el Origen______________________________ 2:9
Orientación y Conexión __________________________________________2:10
Orientación de elementos________________________________________________2:10
Reorientación de elementos de diseño______________________________________2:12
Conexión de elementos primitivos__________________________________________2:14
Moverse por una distancia conocida________________________________ 2:15
Moving Along Axes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:15
Mabinga in any Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2:16
Moving in any Direction: Distance Given in Different Plane. . . . . . . . . . . . . . . . . . . . . . . . 2:18
Moving Through Defined Intersection Planes. . . . . . . . . . . . . . . . . . . . . . . . . . 2:19
Moving Through an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:19
Moving Either Side of an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:21
General Moving to an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:23
Moving In Front of or Behind Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:25
© 2007 AVEVA Solutions Ltd i 12.0

Moving Either Side of a Fixed Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:26

Moving On Top of or Under a Fixed Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:28
Moving an Item Using Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:31
Moving to a Specified Clearance between Items . . . . . . . . . . . . . . . . . . . . . . . 2:33
Moving to a Clearance Either Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:34
Moving an Object to Clear Another Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:36
Moving to a Vertical Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:38
General Moving to a Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:41
Reflecting a Position in a Plane (Mirroring). . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:42
Piping, Ducting and Cable Trays. . . . . . . . . . . . . . . . . . . . . . . . . . . .3:1
Defining a Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Branch and Hanger Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
Connecting the Head or Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
The Head or Tail Connection Reference Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Positioning Head or Tail in Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
Head or Tail Positioning Using End Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6
Head and Tail Positioning by Bottom or Top of Pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
Moving the Head or Tail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
Reconnecting Pipes after an Equipment Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11
Selecting Component and Tube Details from Specifications . . . . . . . . . . . . . 3:11
Choosing Components from a Displayed List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12
Selecting Components from Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16
Selecting the Default Specification Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Selecting from Several Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Selecting ‘Out-of-Specification’ Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
Selecting Components and Tube Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20
Direct Selection by Shortcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21
Re-selection of Existing Components and Tube . . . . . . . . . . . . . . . . . . . . . . . 3:22
Re-selecting the New Default Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
General Reselection of Components and Tube. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23
Standard Component Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24
Position and Orientation Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26
Component Arrive and Leave Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26
Swapping the Arrive and Leave P-points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:27
The Component Specification Reference Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:28
Variable Length Tube (and Rod) Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:29
Insulation Specification Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:30
© 2007 AVEVA Solutions Ltd ii 12.0

Trace Heating Specification Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:31

The Fabrication Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:31
Position and Orientation Status Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:32
Variable Component Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:32
Offline/Straight-Through Component Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:33
Multi-Way Component Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:34
Orientation and Connection of Components. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:35
Component Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:35
Direction-Changing Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:37
Component Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:39
Forced Component Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:41
Moving by a Known Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:42
Moving Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:42
General Moving of Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:43
Positioning Components using Reference Planes. . . . . . . . . . . . . . . . . . . . . . 3:44
Positioning with respect to the Previous Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:44
Positioning the Component through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:46
Positioning with respect to an Intersection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:48
General Positioning through an Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:51
Positioning Components ‘Point-to-Surface’ . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:52
Positioning Components Either Side of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:52
Positioning Components On Top of or Under an Object . . . . . . . . . . . . . . . . . . . . . . . . . . 3:55
General Component Positioning Using Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:57
Component Clearance Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:59
Clearance from the Previous Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:59
Component Clearance Either Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:60
Component Clearance Vertically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:62
Tube (Bottom of Pipe) Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:63
General Clearance of Components and Tube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:66
Dragging Equipment and Piping Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:67
Dragging Equipment and Nozzles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:68
Dragging Piping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:72
Automatic Pipe Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4:1

Accessing the Automatic Pipe Routing Facilities. . . . . . . . . . . . . . . . . . . . . . . . 4:1
Entering and Leaving Autoroute Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Pipe Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Routing Pipes along Preferred Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
© 2007 AVEVA Solutions Ltd iii 12.0

Setting Routing Planes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3

Setting Penalty Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3
Invoking the Automatic Routing Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Setting the Nozzle Offset Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Refining the Automatic Pipe Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Defining the Rack to be Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Defining the Direction of Spread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Defining the Base Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Spreading Pipes about the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7
Setting the Bottom-of-Pipe Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7
Combined Spreading and BOP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8
Structural Design Using Catalogue Components . . . . . . . . . . . . . .5:1

Creating and Positioning Primary Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Creating and Connecting Sections Automatically . . . . . . . . . . . . . . . . . . . . . . . 5:3
Section Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4
Cross-Sectional Profile via a Specification Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4
Generic Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4
Start and End Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5
Start and End Plane Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6
Orientation Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6
Joint Start and End References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7
Start and End Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8
Start and End Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8
Creating and Positioning Secondary Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9
Creating and Positioning Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10
Creating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11
Creating Secondary Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:11
Setting Joint Geometry via a Specification Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12
Positioning and Orientating Primary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:12
Positioning and Orientating Secondary Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:13
Attributes of Connected Joints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15
Connection Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:15
Cutting Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16
Cutback Allowance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:16
Manually Connecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17

Connecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17
Disconnecting Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:18
© 2007 AVEVA Solutions Ltd iv 12.0

Reconnecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:19

Repositioning Steelwork Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20
Reversing Section Start and End Positions (‘Flipping’) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:20
Moving Steelwork Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:21
Modifying Lengths of Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:22
Reorientating Steelwork Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:23
Positioning and Orientating Using P-lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:25
Identifying P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:26
Positioning by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:27
Orientating by Using P-lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29
Creating and Connecting Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29
Creating a Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:29
Splitting a Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:30
Connecting Panels using Linear Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:31
Fittings, Hangers and Equipment Load Points . . . . . . . . . . . . . . . . . . . . . . . . . 5:33
Fittings and Panel Fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:33
Structure-to-Pipework Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34
Structure-to-Equipment Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34
DESIGN, Owning and Attached Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34
Setting DESIGN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:34
Setting Owning and Attached Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36
Representing Curved Beams and Walls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:36
Defining a Generic Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:37
More About Curve Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:38
How P-lines Are Used For Generic Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:39
Positioning Items Relative to Generic Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:41
Generic Fixings Representing Joints and Fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42
Representing Building Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42
Using Element Soft Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:42
Controlling Edge Representation in DRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:43
Design Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6:1

Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Design Template Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Application Data Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Functional Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4
Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4
Application Data and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4
© 2007 AVEVA Solutions Ltd v 12.0

Extension to Design Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5

Valid Value Elements Additional Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5
Extension to Design Data Associated Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5
Special Design Data Property names in scope of a DDSE . . . . . . . . . . . . . . . . . . . . . . . . . 6:6
Parameterisation using Design Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7
Assigning Local Names to Template Elements . . . . . . . . . . . . . . . . . . . . . . . . . 6:8
Setting Local Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9
Using Local Names in Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9
Setting Priorities for Evaluating Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10
Adding Design Points to Template Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11
Using a Design Template Item in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12
Portsets and Linksets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
© 2007 AVEVA Solutions Ltd vi 12.0

Creación del Modelo

Introducción
1.1 Acerca del Manual de Referencia de Diseño

El Manual de referencia DESIGN describe todos los comandos de diseño en detalle.
DESIGN se utiliza normalmente de forma interactiva. La interfaz gráfica de usuario (GUI)

proporciona aplicaciones basadas en disciplinas que le ayudan a crear, comprobar e
informar sobre el modelo. Cómo utilizar las aplicaciones se describe en las guías de
usuario y la ayuda en línea.
interfaz gráfica de usuario (GUI) proporciona aplicaciones basadas en disciplinas que le

ayudan a crear, comprobar e informar sobre el modelo. Cómo utilizar las aplicaciones se
describe en las guías de usuario y la ayuda en línea.
manual está escrito para usuarios experimentados de PDMS DESIGN que necesitan
utilizar comandos, por ejemplo, para escribir macros por lotes o para personalizar la GUI.
Si va a personalizar la GUI, también tendrá que consultar la Guía de personalización de
software y el Manual de referencia de personalización de software para obtener
información sobre PML, el lenguaje de programación AVEVA.
1.2 Organización del Manual de Referencia de Diseño

Manual de Referencia DESIGN consta de tres partes:
• Parte 1, Comandos generales, describe los comandos de diseño generales, que se

utilizan, por ejemplo, para configurar la visualización y consultar y navegar por la base
de datos de diseño. También describe cómo utilizar los gráficos de sintaxis de
comandos, que se utilizan para mostrar todas las opciones disponibles para cada
comando.
• La Parte 2, (este volumen), describe los comandos para crear elementos de base de
datos y establecer sus atributos.
• Parte 3, Utilidades, describe las Utilidades de diseño para la comprobación de

coherencia de datos y detección de conflictos, y para exportar datos de diseño a
programas como Revisión.
1.3 Organización de este Manual
© 2007 AVEVA Solutions Ltd 12.0

Debe consultar la Parte 1 del Manual de Referencia de DESIGN para obtener
información general sobre la creación de elementos y Equipment and Primitives
describe los comandos para el modelado, incluido el posicionamiento, la
orientación y la conexión de comandos aplicables a estos elementos.
• bandejas de tuberías, conductos y cables describen los comandos para el

modelado, incluida la selección de componentes en el catálogo y la colocación,
orientación y conexión de comandos aplicables a estos elementos.
• El enrutamiento automático de tuberías describe los comandos para los usuarios

que requieren estas instalaciones deben preguntar sobre el producto Advanced
Router de AVEVA.
• Diseño estructural mediante componentes de catálogo, describe su enfoque

principal en el diseño de acería estructural, con extensiones de los conceptos para
incluir su uso para representar paredes y pisos en el diseño de edificios más
general.
• Las plantillas de diseño son grupos de elementos que se pueden definir y

almacenar como un único elemento parametrizado y, a continuación, insertar en
un modelo.
obtener una lista completa de todos los atributos y pseudoatributos de PDMS,

consulte el Manual de referencia de personalización del software de diseño de
plantas.
© 2007 AVEVA Solutions Ltd 12.0

Equipment and Primitives
2 Equipos y primitivos
Este capítulo describe el modelado y la disposición de equipos de proceso y elementos
civiles. Estos incluyen elementos tales como bombas, recipientes, paredes e
intercambiadores de calor, que se modelan dentro de los principales elementos jerárquicos
Equipo, Estructura, Ptrack y Subestructura. Estos elementos poseen formas geométricas
primitivas y agujeros que se acotan y se ensamblan para formar un modelo adecuado. A
continuación, los elementos se pueden colocar y orientar como un todo mediante uno de
los comandos de posicionamiento completos Los elementos DESIGN se pueden colocar
en una coordenada conocida o moverse por una distancia o distancia determinada. Los
mismos comandos se pueden utilizar para modificar las posiciones, orientaciones y cotas
existentes. También hay una serie de instalaciones especiales de modificación de la planta
que se describen en una parte posterior del manual.
2.1 Atributos de modelado primitivos

La jerarquía DESIGN es una estructura 'esqueleto' de los elementos que representan la
organización elegida del modelo. La apariencia física y el diseño de los elementos de proceso
están determinados por el valor de los atributos de cada elemento; por ejemplo, un Box sólo
se parece a un cuadro si sus atributos XLEN, YLEN y ZLEN están establecidos (en la
creación son cero).
En esta sección se describen los atributos de elemento sprimitivo físico que dan una forma
al modelo. Por lo general, estos atributos se establecerán escribiendo sus valores
directamente o desde macros. Sin embargo, es importante reconocer que,
independientemente de cómo se haya introducido, la información básica del atributo es la
descripción física almacenada de la planta.
2.1.1 Dimensionamiento de bloques de construcción

primitivos
Palabras clave:
XLENGTH YLENGTH ZLENGTH DIAMETER HEIGHT RADIUS XOFF YOFF XTOP YTOP
XBOTTOM YBOTTOM DTOP DBOTTOM RINSIDE ROUTSIDE XTSHEAR YTSHEAR
XBSHEAR YBSHEAR
Descripción:
Las formas físicas de equipos, elementos estructurales y civiles de la planta se
construyen creando, dimensionando y ensamblando elementos geométricos básicos. Estos
comandos establecen directamente los atributos de los primitivos de modelado básico que
les dan sus dimensiones precisas. Están las siguientes formas primitivas:
Caja Cono Plato
Cilindro Cilindro con fondo de pendiente Hocico
Circular Torus Rectangular Torus Pirámide
© 2007 AVEVA Solutions Ltd 2 2:1 12.0

Los agujeros pueden sumergirse a través de primitivas "sólidas" utilizando un conjunto

correspondiente de primitivos negativos. Los ejemplos dados en esta subsección se
refieren a la caja y el cilindro; Una descripción completa de todos los elementos primitivos
y sus atributos se puede encontrar en el Manual de referencia del modelo de datos.
.
Example:
XLEN 1000 (At a Box)
The xlength dimension of the box becomes 1000
DIA 3 FT (At a Cylinder)
The diameter of the cylinder becomes 3 feet
Command Syntax:
Refer to the Data Model Reference Manual.
DIAMETER
HEIGHT
Figure 2:1. Dimensioning a CYLINDER primitive
2.1.2 Choosing Nozzle Size, Rating and Height

Keywords:
CATREF
HEIGHT
Description:
The Nozzle is the only basic equipment primitive that obtains some of its physical
dimensions directly from the PDMS Catalogue. The size and rating are determined by
setting the CATREF (Catalogue Reference) attribute which refers to an element in the
Catalogue. The Nozzle height, however, is determined on site by setting the corresponding
Height attribute. If the CATREF attribute is not set, the ‘Nozzle’ is merely a hierarchical
element with no geometry.

Examples:
CATR /NFAARPMM (At Nozzle)
The size and rating of the Nozzle are set by naming the appropriate Catalogue choice.
HEI 2’6 (At Nozzle)
The Height of the Nozzle becomes 2’6.
Command Syntax:
>-- CATref name -->
>-- HEIght <uval> -->
2.1.3 Modelling Detail Levels

Keywords:
LEVEL
Description:
This command sets the attribute, common to all primitive elements, that controls modelling
detail. The command specifies a range of modelling ‘levels’ which determine the permanent
visibility characteristics of the element in DESIGN. The attribute allows plant items to be
assembled from overlaid primitives representing varying levels of detail. In this way, several
graphical versions of the same object can be available for different purposes. For example,
it may be decided to represent an I-section beam as a single box for simple space-
modelling in DESIGN, while using its full cross-section for 2D drawing data in DRAFT.
The LEVEL attribute is specified as two numbers, representing the inclusive range in which
that item will be drawn. In DESIGN, only primitives of visible items whose LEVEL range
includes the LEVEL setting specified by the REPRESENTATION command will be drawn
(see Chapter 4 in Part 1 of the DESIGN Reference Manual).
LEVEL ranges for Nozzles and piping are specified in the Catalogue. A company will
usually establish rigid standards for the use of LEVELs which are defined permanently in
the Catalogue and therefore must be complied with during Equipment and Civils modelling.
Example:
LEVEL 6 10
The current primitive will be drawn if the operative drawing LEVEL is within the specified
range.
Command Syntax:

>-- LEVel integer integer -->
Figure 2:2. Some modelling detail levels for an I-section beam
2.1.4 Obstruction Settings

Keywords:
OBSTRUCTION
Description:
The OBSTRUCTION attribute indicates to the clash detection facility whether a primitive
should be considered as a ‘Hard’ or ‘Soft’ obstruction, or not at all. Obstructions can be
specified as HARD, SOFT or NONE, or alternatively they can be specified numerically as
follows:
For ordinary primitives, the following rules apply:
• No obstruction (internal graphical details)
• Soft obstruction (access volumes etc.) • Hard obstruction
(vessel ‘envelopes’ etc.).
Holes (i.e. negative primitives) also have the OBSTRUCTION attribute. OBSTRUCTION
settings for Nozzles and Piping are given in the Catalogue.
Note: See also Chapter 4 in Part 1 of the DESIGN Reference Manual for details of the
Spatial Map which is used during clash-checking.
Examples:
OBST SOFT (At a primitive)
Current Element will be considered as a ‘soft’ obstruction.
OBST HARD (At a primitive)
Current Element will be considered as a ‘hard’ obstruction.

Examples:
OBST NONE (At a primitive)
Current Element will be ignored during clash detection.
OBST 2 (At a primitive)
Current Element will be considered as a ‘hard’ obstruction.
Command Syntax:
>-- OBStruction --+-- integer --.
| | |-- HARD
-----|
| | |-- SOFT
-----|
| |
‘-- NONE -----+-->
Figure 2:3. Obstruction settings for use in clash detection
2.2 Positioning at a Known Point

These commands allow you to place the Current Element at a known position in space.
You can:
• Specify explicit coordinates
• Specify the position of an existing p-point
• Cursor pick with a working grid (WGRID) position
The position of the Current Element is normally defined as that of its origin. However
options exist to allow any p-point belonging to the item to be used as the positioning
reference.

2.2.1 Positioning at a Coordinate

Keywords:
POSITION AT
Description:
This command positions the Current Element directly by giving the 3D coordinates, the
name of another element or p-point position, or visually by using the cursor.
Examples:
AT E3’ N4’6 U1’ Current Element will be placed at the specified owner
coordinate position (see Figure 2:4.: Positioning the Current
Element at a known point).
AT 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.: Positioning a PIN and the current element
together at a known point).
Command Syntax:
>--+-- POSition <marke> --.
| |
‘----------------------+-- AT <bpos> -->
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
N
1'
OWNER ORIGIN 4' 6"
3'
E
Figure 2:4. Positioning the Current Element at a known point
Figure 2:5. Positioning a PIN and the current element together at a known point
2.2.2 Polar Positioning from the Origin
Keywords: POLAR
DISTANCE
Description:
This command is used to position the Current Element using polar coordinates. This is
particularly useful for positioning Nozzles. The coordinates are relative to the owner’s
origin.
Examples:

POLAR E45N DIST 300 The Current Element will be placed 300 from its
owner’s origin along E45N (see Figure 2:6.: Polar
positioning from the origin).
POLAR PIN1 DIST 3000 The Current Element will be placed 3000 from its
owner’s origin along the direction of PIN1 (see
Figure 2:6.: Polar positioning from the origin).
POS 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 owner’s origin.
Command Syntax:
| |
‘----------------------+-- POLar <bdir> DISTance <uval> -->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 2:6. Polar positioning from the origin

2.2.3 General Polar Positioning from the Origin

Keywords:
POLAR PLANE DISTANCE
Description:
This command differs from the basic polar option by allowing the distance from the owner’s
origin to be specified more generally. The PLANE element of the command enables this
distance to be given in a direction different from the polar direction. For example, an
element may be placed on a line North 25 East, and at N250 from the owner’s origin.
Examples:
Example:
POLAR N30E PLANE N Positions the Current Element along the N30E line from the
DIST 1000 owner origin at N1000 (see Figure 2:7.: General polar
positioning from the origin by specifying a plane).
Command Syntax:
>-+- POSition <marke> -.
| |
‘--------------------+- POLar <bdir> -+- PLAne <bdir> -.
| |
‘----------------+- DISTance <uval> ->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 2:7. General polar positioning from the origin by specifying a plane
2.3 Orientation and Connection

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

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

Keywords:
ORIENTATE
Description:
Every Design element has its own co ordinate system which consists of a right-handed set
of East (X), North (Y) and Up (Z) axes. The precise orientation of an element must be given
as two statements fixing the direction of two axes, e.g. ORI Y IS NORTH AND Z IS UP.
When rotating symmetrical items, such as cylinders, it may be sufficient to give one axis
direction only (allowing DESIGN to choose the other), e.g. ORI P1 IS N45E. Regardless of
the command given, orientation always occurs about the Current Element origin.
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:8.: Design
element orientation (1)).
ORI P1 IS E The Current Element is rotated so that its P1 p-point is

pointing East in owner coordinates (see Figure 2:9.:
Design element orientation (2)).
Command Syntax:
>- ORIentate -+- <bdir> IS <bdir> -.
||
‘--------------------+- AND <bdir> IS <bdir> -.
| |
‘------------------------+-->
Querying:
>-- Query ORIentation --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:8. Design element orientation (1)
Figure 2:9. Design element orientation (2)
2.3.2 Design Element Reorientation

Keywords:
ROTATE BY ABOUT THROUGH AND
Description:
The ROTATE command allows you to rotate any Design element, including a Group. The
rotation required may be specified in any of the following ways:
• As a specified angle of rotation about the element’s default axis (i.e. the Z axis).
• As a specified angle of rotation about a given axis, the latter defined by its direction
and/or through point. If the direction and/or through point are omitted, the default
direction is that of the Neutral Axis or Z axis; the default through point is the Origin.
• By reference to the element’s axes.
Example:
ROTATE BY -45 Rotates by 45° about the element’s Z axis
(anticlockwise when looking in the +Z direction, since 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
Rotates element about an axis which passes in the N-S
BY -25
direction through its p-point 3 position. The rotation is 25°
anticlockwise when looking S along this axis.
ROTATE AND Y IS N45W Rotates element until the Y axis points as closely as
25D 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> -.
| |
‘------------------+->
Rotation to pass through a given point:

>- ROTate THRough <bpos> + ABOut <bdir> + BY + <uval> ---------------.
| | | | | | ‘ <bdir>
TOwards <bdir> |
| | | | ‘ AND <bdir> IS <bdir>
------+->
|
| BY -+- <uval> ---------------.
| | |
| ‘- <bdir> TOwards <bdir> + ABOut <bdir> .
| | | | ‘--------------+->
|
|
‘ AND <bdir> IS <bdir> + ABOut <bdir> -.
| |
‘---------------+->
Rotation by a specified amount:

>- ROTate BY + <uval> ---------------.
| |
‘ <bdir> TOwards <bdir> + ABOut <bdir> -+- THRough <bpos> -.
| | | | ‘------------------+->
|
| THRough <bpos> -+- ABOut <bdir> -.
| | | | ‘----------------+-
>
‘->
Rotation to give a specified orientation:

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

| | | | ‘------------------+->
|
|- THRough <bpos> -+- ABOut <bdir> -.
| | | | ‘----------------+->
‘->
2.3.3 Primitive Element Connection
Keywords:
CONNECT
Description:
The command allows the current primitive element to be ‘connected’ to another element or
mapping pin. Any p-point on the Design element may be connected to any other p-point
(except p-points on the same element). Mapping pins can also be used to great effect as
they can connect and be connected to. In the former case, both the pin and Current
Element move as a rigid entity; in the latter, the Current Element moves to the static pin.
The connection operation includes positioning and orientation of the Current Element so
that the two specified Design Points are coincident and of opposite direction.
Example:
CONN P2 TO P1 OF / The P2 of the Current Element is connected to the specified
A p-point on another element (see Figure 2:10.: Connecting
primitives by direct specification).
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@ The first point hit (belonging to the Current Element) is
AND X IS N connected to the second point (belonging to another
element). The Current Element is rotated so that its X axis is
North in owner coordinates (see Figure 2:11.: Connecting
primitives by using cursor selection).
Note: The first p-point in the command must belong to the Current Element.
Command Syntax:
>-- CONnect <marke> TO <marke> -+- AND <bdir> IS <bdir> --.
| |
‘-------------------------+-->
Querying:
>-- Query ORIentation --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
| |
‘------------+-- WRT --.
| |

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

|
‘-->
Figure 2:10. Connecting primitives by direct specification
Figure 2:11. Connecting primitives by using cursor selection
2.4 Moving by a Known Distance

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

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

Examples:
BY E300 N400 Moves the Current Element by the specified amounts along
the owner’s axes (see Figure 2:12.: Moving along specified
axes).
BY E3000 WRT SITE Moves the Current Element by the specified amount along
the Site’s East axis (see Figure 2:12.: Moving along specified
axes).
Command Syntax:
>-- BY <pos> --+-- <axes> --.
| |
‘------------+-->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
N
BY E3000 WRT SITE
CE
BY E3000
OWNER
AXES
E
SITE
AXES E
Figure 2:12. Moving along specified axes
2.4.2 Moving in any Direction

Keywords:
MOVE ALONG TOWARDS DISTANCE
Description:

This command displaces the Current Element in any specified direction by a given
distance.
Examples:
MOVE N45E DIST 100 The Current Element is displaced along East 45 North in
owner coordinates by the specified distance (see Figure 2:13.:
Moving a given distance in a given direction (1)).
MOVE TOW IDP@ DIST The Current Element is displaced towards the picked p-point
100 by the specified amount (see Figure 2:14.: Moving a given
distance in a given direction (2)).
Command Syntax:
>-- MOVe --+-- ALOng --.
| |
‘-----------+-- <bdir> DISTance <uval> -->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 2:13. Moving a given distance in a given direction (1)

Figure 2:14. Moving a given distance in a given direction (2)
2.4.3 Moving in any Direction: Distance Given in Different Plane

Keywords:
MOVE ALONG TOWARDS PLANE DISTANCE
Description:
This command differs from the basic option by allowing the distance moved to be specified
in a different plane from the actual movement direction.
Example:
MOVE TOW / The Current Element is moved towards the specified design
DATUM PLANE E DIST item until its Easting (in owner coordinates) has changed by
1000 1000 (see Figure 2:15.: Moving in a direction specified in a
different plane).
Command Syntax:
>-- MOVe --+- ALOng -.
| |
‘---------+- <bdir> -+-- PLAne <bdir> --.
| |
‘------------------+-- DISTance <uval> ->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:15. Moving in a direction specified in a different plane
2.5 Moving Through Defined Intersection Planes

The commands described in this section move the Current Element along a given direction
until it intersects with a fixed Reference Plane.
Any p-point on the Current Element may be used for the manoeuvre, although the default is
the origin. This point is moved to the Reference Plane which is specified by the 3D position
through which it passes. The orientation of the Reference Plane defaults to perpendicular
to the movement direction.
In no case is the volumetric geometry of any of the Design model considered. Although you
do not need to know the actual distance moved, you must provide ‘point-to-point’
dimensions in these commands. In other words, these commands cannot calculate physical
clearances (see Moving In Front of or Behind Items and Moving to a Specified Clearance
between Items for such commands).
2.5.1 Moving Through an Intersection

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

Examples:
MOVE N30W THR /BOX Moves the Current Element along the given direction until
it ‘intersects’ the Reference Plane through the origin of
the named element (see Figure 2:16.: Moving along a
given direction through an intersection).
MOVE E THR E3000 Moves the Current Element along the given owner axis
until it ‘intersects’ the Reference Plane through E3000 N0
U0 (see Figure 2:17.: Moving to intersect a plane through
a given point).
MOVE ALONG N45E THR Moves the Current Element along the given direction until
IDP@ it ‘intersects’ the Reference Plane through the picked p-
point (see Figure 2:18.: Moving to intersect a plane
through a given point).
Note: The Reference Plane is perpendicular to the movement direction.
Command Syntax:
>-- MOVe --+-- ALOng --.
| |
‘-----------+-- <bdir> THRough <bpos> -->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:16. Moving along a given direction through an intersection
Figure 2:17. Moving to intersect a plane through a given point
Figure 2:18. Moving to intersect a plane through a given point
2.5.2 Moving Either Side of an Intersection

Keywords:
MOVE DISTANCE FROM TO
Description:
This command moves the Current Element until its origin intersects the Reference Plane a
given distance either side of a fixed 3D point.
Examples: MOVE E DIST 1000 F ROM /VESSEL5
MOVE N30W DIST 30

TO(or FROM) /BOX
MOVE ALONG N45E DI
ST 20 TO /COL8

Move the Current Element Move the Current Element East until its origin intersects a Reference
N30W until its origin intersects Plane 1000 beyond the origin of /VESSEL5 (see Figure 2:20.: Moving
a Reference Plane 30 before either side of a plane specified relative to another element).
(or beyond) the origin of /BOX
(see Figure 2:19.: Moving Move the Current Element along N45E until its origin intersects a
either side of an intersection). Reference Plane 20 before the origin of /COL8 (see Figure 2:21.:
Moving either side of a plane specified relative to another element).
Note: The Reference Plane is perpendicular to the movement direction.
Command Syntax:
>-- MOVe --+-- ALOng --.
| |
‘-----------+-- <bdir> DISTance <uval> --+-- FROm --.
| |
‘-- TO ----+-- <bpos> -->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
... DISTANCE 30 FROM /BOX
30
REFERENCE
PLANES ... DISTANCE 30 TO /BOX
MOVE N30W... CE (START POSITION )
Figure 2:19. Moving either side of an intersection

Figure 2:20. Moving either side of a plane specified relative to another element
Figure 2:21. Moving either side of a plane specified relative to another element
2.5.3 General Moving to an Intersection

Keywords:
MOVE PLANE THROUGH FROM TO DISTANCE
Description:
This command differs from the basic options by allowing the movement direction and
Reference Plane to be specified 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
Examples:be used as the positioning

DATUMdatum; for instance,
PLANE N THROtheUGH
p-point on the flanged face of a nozzle.
N1000
MOVE ALONG E PLANE

MOVE IDP@ TOW /
N45W DIST 20 TO /

TANK5 2:22.: Moving to an intersection by separately specifying direction

Move the picked p-point (or and plane).
the Current Element)
towards / DATUM until it Move the Current Element East until it intersects an oblique
intersects N1000 (see Figure Reference Plane 20 before the origin of /TANK5 (see Figure 2:23.:
Moving to an intersection by separately specifying direction and
plane).
Note: DISTANCE is measured in the direction of the Reference Plane and not the
movement direction.
Command Syntax:
>- MOVe -+- <marke> -.
| |
‘-----------+- ALOng -.
| |
‘---------+- <bdir> -.
| |
‘----------+- PLANe <bdir> -+- <dist> -+- FROm -.
| | |
| |- TO ---+- <bpos> -.
| | | |
‘-------------------|
| | |- FROm ----. |
| | | |- TO ------| |
| | |
‘- THRough -+- <bpos> ---------+->
<dist> = >- DISTance - <uval> ->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:22. Moving to an intersection by separately specifying direction and plane
Figure 2:23. Moving to an intersection by separately specifying direction and plane
2.6 Moving In Front of or Behind Items

The commands described in this section move the Current Element to the intersection with
a Reference Plane, a specified distance from the surface of a fixed geometric object.
Any p-point on the Current Element may be specified as the positioning datum, although
the default is the origin. In no case is the geometry of the Current Element considered.
However, the full geometry of the fixed element is taken into account. Although the
designer does not need to know the actual distance moved, he must provide a ‘point-to-
surface’ dimension.

2.6.1 Moving Either Side of a Fixed Object

Keywords:
MOVE DISTANCE INFRONT BEHIND
Description:
This command moves the Current Element until its origin is a specified distance one side or
the other of a fixed geometric object. This takes into account the volume of the referenced
element but not of the Current Element. Therefore it is applicable to, say, spacing the
centreline of a vessel or column a certain distance from the surface of a wall.
Examples:
MOVE E DIST 1000 B The Current Element is moved East until its origin is 1000
EH /WALL10 beyond the far side of /WALL10 (see Figure 2:24.: Moving
either side of a fixed object).
The Current Element is moved until its origin is 20 to the
MOVE N45E DISTANCE near side of /EXCH5 (see Figure 2:24.: Moving either side of
20 INFRONT /EXCH5 a
fixed object and Figure 2:25.: Moving either side of a fixed
object in a specified direction).
Command Syntax:
>- MOVe -+- ALOng -.
| |
‘---------+- <bdir> DISTance <uval> -+- FROm -.
||
‘- TO ---+- <bpos> -+- INFront -.
| |
‘- BEHind --+- <gid> --.
| | |-
marke> -|
| |
‘- <bpos> -+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> ---.
| |
‘----------------------+-->

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

Figure 2:25. Moving either side of a fixed object in a specified direction
2.6.2 Moving On Top of or Under a Fixed Object

Keywords:
MOVE DISTANCE ONTOP UNDER
Description:
This command moves the Current Element until its origin is a specified distance above or
below a fixed geometric object. This takes into account the shape of the referenced object
but not that of the Current Element. It is therefore applicable to, say, placing the centreline
of a vessel a certain distance above the top surface of a beam.
Example:
MOVE ALONG E45D DISTA
NCE 3000 UNDER /BEAM
MOVE D ONTO /BOX Moves the Current Element along a vertical line until its origin
lies in the upper surface of /BOX (see Figure 2:27.: Moving
above/below a fixed object).

Moves the Current Element along 2:26.: Moving above/below a fixed object in a specified direction
E45D until its origin is 3000 and Figure 2:27.: Moving above/below a fixed object).
vertically below /BEAM (see Figure
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:
| |
‘---------+- <bdir> DISTance <uval> -+- FROm -.
||
‘- TO ---+- <bpos> -+- UNDer -.
| |
‘- ONTop -+- <gid> --.
| | |-<marke> -|
| |
‘- <bpos> -+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

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

Figure 2:27. Moving above/below a fixed object
2.6.3 Moving an Item Using Reference Points

Keywords:
MOVE ALONG PLANE DISTANCE INFRONT BEHIND ONTOP UNDER
Description:
This command differs from the basic options by allowing any point on the Current Element
to be moved to a specified distance from the surface of a fixed design item. In addition the
distance may be specified in a direction independent of the movement direction.

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
224).
MOVE NOZZLE1 S DIST 200 INF / Moves the current Equipment by

RACK (at an Equipment element) positioning the Nozzle at the specified
location.
Command Syntax:
>- MOVe <marke> -+- ALOng -.
| |
‘---------+- <bdir> PLAne <bdir> DISTance <uval> <repla> ->
<repla> = >--+-- FROm --.

| |
|-- TO ----+-- <bpos> -->
|
|-- INFront --.
| | |--
BEHind ---|
| | |--
UNDer ----| |
|
‘-- ONTop ----+-- <gid> ---.
| | |-- <marke>
--|
| |
‘-- <bpos> ---+-->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:28. Moving to a point at a specified distance from a surface
2.7 Moving to a Specified Clearance between Items

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

2.7.1 Moving to a Clearance Either Side

Keywords:
MOVE CLEARANCE INFRONT BEHIND
Description:
This command moves the Current Element until its geometric volume is a specified
clearance from a fixed Design element, Point or position.
Examples:
MOVE ALONG E45N CL Move the Current Element until its volume is zero clearance
EAR BEHIND /BOX behind BOX (see Figure 2:29.: Moving to a given clearance
in a specified direction).
MOVE E CLEAR 1000 Move the Current Element East until its volume is 1000 this
INFRONT /DATUMBOX side of the given fixed item (see Figure 2:30.: Moving to a
given clearance).
MOVE E45N CLEAR 10 Move the Current Element along E45N until its volume is 100
0 BEH IDP@ beyond the cursor hit p-point (see Figure 2:30.: Moving to a
given clearance).
Command Syntax:
>- MOVe <marke> -+- ALOng -.
| |
‘---------+- <bdir> CLEArance <uval> -+- INFront -.
||
‘- BEHind --+- <gid>--.
| | |-
<marke>-|
| |
‘- <bpos> -+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> --.
| |
‘----------------------+-->

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

Figure 2:30. Moving to a given clearance
2.7.2 Moving an Object to Clear Another Object

Keywords:
MOVE CLEARANCE INFRONT BEHIND ONTOP UNDER
Description:
This command takes into account the geometry of both the Current and Referenced
elements. In this way a minimum clearance can be specified between two Design items (for
example, to ensure that a walkway is a sufficient distance away from a heated autoclave).
Example:
MOVE D CLEARANCE O
NTO /BEAM
MOVE E CLEARANCE 1
000 BEH /WALL10

The Current Element is moved 1000 clear of the side of /WALL10 (see Figure 2:31.: Moving to clear
East until its entire volume is another object).
The Current Element is moved down until it has a zero clearance

above the element /BEAM (see Figure 2:31.: Moving to clear another
object).
Command Syntax:
| |
‘---------+- CLEArance <uval> -+- INFront -.
| | |-
BEHind --|
| | |-
UNDer ---| |
|
‘- ONTop ---+- <gid> --.
| | |-
<marke> -|
| |
‘- <bpos> --+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 2:31. Moving to clear another object
2.7.3 Moving to a Vertical Clearance

Keywords:
MOVE CLEARANCE ONTOP UNDER
Description:
This command moves the Current Element until its volume is a specified vertical clearance
above or below a fixed element, Point or position.
Example: MOVE ALONG U30W CL EAR ONTO /BEAM

MOVE E60D CLEAR 10 Figure 2:32.: Moving to a given vertical clearance in a specified
00 UNDER PIN6 direction).
The Current Element will be
The Current Element will be moved E60D until it is 1000 below the
moved vertically until it is zero
specified Design point (see Figure 2:33.: Moving to a given vertical
clearance above /BEAM (see
clearance).
Command Syntax:
||
‘---------+- <bdir> CLEArance <uval> -+- UNDer -.
| |
‘- ONTop -+- <gid> --.
| | |- <marke>
-|
| |
‘- <bpos> --+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

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

Figure 2:33. Moving to a given vertical clearance
2.7.4 General Moving to a Clearance

Keywords:
MOVE PLANE CLEARANCE INFRONT BEHIND
Description:
This command differs from the basic option by allowing the movement direction and
clearance to be specified in different planes.
Example:
MOVE TOWARD /TANK5 PLANE E The Current Element will be moved towards /
CLEARANCE 30 INF /TANK5 TANK5 until it has 30 clearance ‘this side’ in an
East/West direction (see Figure 2:34.: Moving to
a given clearance relative to a specified plane).

Command Syntax:
||
‘---------+- <bdir> -+- PLAne <bdir> -.
| |
‘----------------+- TOwards <bpos> -.
|
.--------------------------------<-------------------------------’
|
‘- CLEARance <uval> +- INFront -.
| | ‘- BEHind --| |-
<gid> --.
| | |-
<marke> -|
| |
‘- <bpos> --+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 2:34. Moving to a given clearance relative to a specified plane
2.8 Reflecting a Position in a Plane (Mirroring)

The mirroring facility lets you change the position of the current element or group by
reflecting it in a specified plane. The current element and its hierarchy of members will be

repositioned so as to achieve a mirror image of their initial relative positions. If the current
element is a Group, all members of the group and their hierarchies of members will be
reflected.
The values of positional attributes and directional attributes are derived by direct reflection
in the plane.
Orientations are processed such that they remain right-handed. For most elements this is
achieved by reflecting the Y and Z axes directly, while reflecting and reversing the X axis.
The exceptions to this rule are:
• Toruses (CTOR, RTOR, NCTO, NRTO), whose X and Y axes are reflected directly
while the Z axis is reflected and reversed;
• The piping elements Tee, Nozzle, Elbow, Coupling, Reducer and Flange, where the
ppoints are used to decide the axis of greatest symmetry for the reversal. For
example, an ELBO with p-point directions along X and Y will be reversed in the Z
direction.
You will most likely use the mirror positioning options in conjunction with the COPY
command (see Sections 2.1.5 and 2.1.6 of Database Management Reference Manual) to
create a new part of the design model which is a mirror image of an existing part.
Note: Since mirror-image components will not always be available in the Catalogue, no
attempt is made to reflect catalogue geometry or to reference alternative catalogue
components.
Keywords:
MIRROR
Description:
Moves the current element to a new position which is calculated by reflecting the initial
position in a specified plane.
Example:
MIRROR PLANE E45D Reflects position of current element in plane which has given
THRO /TANK5 direction and which passes through /TANK5 (see Figure
2:35.: Mirroring a position in a plane).
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> = >-+- PLAne <bdir> -+- DISTance <uval> -+- <repla> ------.
| | | | | | ‘----------------|
| | | | |- <repla> --------------------------|
| | | | |- THRough <bpos> -------------------|
| | | | ‘- CLEArance -+- <uval> -. |
| | | | | ‘----------+- <repla> -|
| | | | |- <planf> -|
| | | | ‘-----------| |- DISTance - <uval> -+-
<repla> -. |

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

| |
|-- BEHind ---+-- <sgid> ---.
| | | | |-- <marke>
--|
| | | | ‘-- <bpos>
---|
| | |-- FROm --. |
| | |
‘-- TO ----+-- <bpos> ------+-->
<planf> = >--+-- ONTop --.

| |
‘-- UNDer --+-- <sgid> ---.
| | |-- <marke>
--|
| |
‘-- <bpos> ---+-->
/TANK5
Plane through /TANK5
Plane direction Current Element

E45D (owning three
primitives)
MIRROR PLANE E45D THRO /TANK5
Figure 2:35. Mirroring a position in a plane

Piping, Ducting and Cable Trays
3 Piping, Ducting and Cable Trays

This chapter describes the commands to create Piping (including Hangers), Ducting and
Cable Trays. Then the commands to position, orientate and connect piping components are
described.
The key element in these disciplines is the Branch. This is a two-ended entity that can be
joined with other Branches to form a network. The network can finish where a Branch is
connected to an Equipment Nozzle, reaches the site limits, or stops at a vent or drain valve.
The Branch element owns Component elements drawn from the PDMS Catalogue whose
sequence and position define the centreline route. Straight variable lengths of Tube are
automatically routed between adjacent Components and are therefore not individual
Component elements themselves.
There are no special Design hierarchy elements for ducting and cable trays. They are
routed as Branches, but with Components drawn from parts of the Catalogue dedicated to
the relevant discipline. It is convenient, therefore, to refer to pipes, ducting and cable trays
collectively as ‘piping’, since PDMS treats them similarly. The principles applied to ‘routing’
two-ended pipe Hangers are also identical to those used for Branches. Where no
distinction is made, the term ‘piping’ also applies to Hangers.
3.1 Defining a Branch

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

On creation of a Branch (or Hanger) these are normally the first attributes to be set. If the
Specification of the Pipe has already been set, then this will automatically be cascaded
down to Branch level when it is created. The PSPE attribute of a Branch controls all
subsequent Component selection operations which choose a Component’s physical details
from the stated Specification.
Examples:
PSPEC /A35B8 The PSPE attribute of the Pipe and all subsequently created (At
Pipe level) Branches will be set to /A35B8.
PSPEC /A15A2 The PSPE attribute of the Branch will be set to /A15A2. All
(At Branch level) 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.3 Connecting the Head or Tail

Keywords:
CONNECT
Description:
The CONNECT command, when applied to Branches (or Hangers), sets up the Head or
Tail to match exactly the item to which it has been connected. For example, if the Head is
connected to a 3-inch flanged-faced nozzle at E3000 and pointing North, the CONNECT
command will set all the Head attributes (HBOR, HCON, HPOS and HDIR) to
corresponding values. In addition, the Head and Nozzle are logically ‘tied together’ by two
attributes which ‘point’ to each other - the Nozzle CREF will point to the Branch, and the
Branch HREF (Head Reference) will point to the Nozzle.
The final effect of CONNECT, which only applies to Heads, is that the Tube (or Rod) that
may be required between the Head and the first Component is automatically selected.
A Branch Head or Tail can connect to the following items:
• A Nozzle
• The Head or Tail of another Branch
• A ‘free’ p-point of a multi-way Component in another Branch (e.g. a Tee)
Examples: CONN PT TO LAST MEM
CONN PH TO /1205-N5
(Where /1205-N5 is a
Nozzle) CONN PT TO /100-A8/T2

(Where /100-A8/T2 is a The Tail attributes of the current element will be set to
TEE) match the Leave Point of the last Component (that is not
The Head attributes of the current an Attachment point).
element (Branch or Hanger) are set to
match the position, orientation, bore The Tail attributes of the current element will be set to
and connection type of the Nozzle (see match the free p-point on the specified TEE (see Figure
Figure 3:1.: Connecting a Branch Head 3:1.: Connecting a Branch Head or
or Tail). Tail).
CONN PT TO P4 OF /VF205 The Tail attributes of the current element will be (Where
/VF205 is a VFWA.) set to match the specified p-point.
CONN PH TO PT OF /100-A8/1 The Head attributes of the current element will be

(Where /100-A8/1 is set to match the Tail of the specified Branch. another Branch)
CONN PH TO ID NOZZ@ As in the first example, but with the Nozzle

identified by cursor selection.
Note: Before a CONNECT command is given, the Branch Specification attribute must be set.
Connection to elements not within the designer’s jurisdiction (Read Only) will cause an inter-DB
connection macro to be created automatically (see the Database Management Reference
Manual).
Command Syntax:
>-- CONnect <marke> TO --+-- <marke> --.
| |
‘-- <gid> ----+-->
Querying:
>-- Query --+-- PHead --.
| | |-- HHead --|
| | |-- PTail --|
| |
‘-- HTail --+--> >--
Query --+-- HPosition --. | |
‘-- TPosition --+-- WRT --.
| |
‘-- IN ---+-- <gid> -->

CE
H T
E BRANCH A
CONN PH A I
/1205-N5 TO /1205-N5 D L
PH
CONN PT TO
/100-A8/T2
BRANCH
CENTRELINE
PT
PA PL
/100-A8/T2
Figure 3:1. Connecting a Branch Head or Tail
3.3.1 The Head or Tail Connection Reference Attribute

Keywords:
HREF TREF
Description:
These attributes hold the name of the element to which the Branch or Hanger is connected.
They are usually set automatically as a result of a CONNECT PH (or PT) command, but
they may also be set explicitly. When they are set, the corresponding attribute (CREF,
HREF or TREF) of the item connected to is reset so as to point back to the Branch or
Hanger.
Examples:
TREF /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 ----+-->
>-- Query --+-- HREF --.
| |
‘-- TREF --+-->
3.3.2 Positioning Head or Tail in Free Space

Keywords:
HPOS HBOR HDIR HCON TPOS TBOR TDIR TCON
Description:
It is sometimes necessary to terminate a Branch (or Hanger) in free space; for instance,
where a Branch reaches the Battery Limits. Where this termination ends with a length 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 -->
Querying:
>-- Query --+-- PHead --.
| | |-- HHead
--|
| | |-- PTail
--|
| |
‘-- HTail --+-->
3.3.3 Head or Tail Positioning Using End Components

Keywords:
POSITION PH PT THROUGH DISTANCE
Description:
These commands allow the Head or Tail position to be set by using the end Component in
that Branch or Hanger. This will normally occur when the Tail is to finish with a piece of
variable length Tube. This command treats the Tail position as a pseudo-Component and
places it at the specified point along the previous Component’s Leave p-point direction. If
the Head is to be positioned in this way, Backwards Routing Mode must be in force.
Example:
POS PT 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 The HPOS attribute will be set to the intersection
(In BACKWARDS mode) 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> ---+-->
Querying:
>-- Query --+-- PHead ------.
| | |-- PTail
------|
| |
|-- HTail ------|
| | |-- HHead
------|
| | |-- HPosition
--|
| |
‘-- TPosition --+-->
POS PT DISTANCE 1000
POS PH THROUGH E30
Figure 3:2. Head/Tail positioning using end components
3.3.4 Head and Tail Positioning by Bottom or Top of Pipe

Keywords:
BOP TOP INFRONT BEHIND ONTOP UNDER

Description:

This command allows the Head or Tail of a Branch to be moved vertically to a specified
clearance above or below a Design element or Point. If the Head or Tail Tube has been
selected, then its cross-section will be taken into account. (Otherwise the HPOS or TPOS
will be moved to the specified clearance, as no Tube geometry is available.)
Example:
BOP ONTO /BEAM This will position the Tube on top of /BEAM with a clearance
(At the Head) of 0.
TOP UNDER U3000 This will position the Tail under the elevation U3000 with a
(At the Tail) clearance of 0.
Note: If no Tube can be found emerging from the point specified, then only the point’s
position can be used.
Command Syntax:
>--+-- BOP --.
| |
‘-- TOP --+-- <uval> --.
| |
‘------------+-- FROm --.
| |
|-- TO ----+-- <bpos> -->
|
|
|-- INFront --.
|| |-- BEHind
---|
|| |-- ONTop
----| | |
‘-- UNDer ----+-- <gid> ---.
| | |-- <marke>
--|
| |
‘-- <bpos> ---+-->
Querying:
>-- Query --+-- PHead ------.
| | |-- PTail
------|
| | |-- HTail
------|
| | |-- HHead
------|
| | |-- HPosition
--|
| |

Figure 3:3. Head/Tail positioning by Bottom/Top of pipe
3.3.5 Moving the Head or Tail

Keywords:
MOVE BY DISTANCE
Description:
This command allows the Head or Tail position to be moved by a specified distance,
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 ---+-- <gid> -->
| | | ‘-->
|
‘-- DISTance <uval> -->
Querying:
>-- Query --+-- PHead ------.
| | |-- PTail
------|
| | |-- HTail
------|
| | |-- HHead
------|
| | |-- HPosition
--|
| |

Figure 3:4. Moving the Head or Tail

3.3.6 Reconnecting Pipes after an Equipment Move
Note: Applicable to Nozzles that have been moved since a Branch was connected to them.
Largely superseded by the DRAG command.
Keywords:
RECONNECT
Description:
If an Equipment item is moved using an ordinary positioning command, none of the
Branches connected to it will move with it. RECONNECT will reconnect all the HEADS and
TAILS of Branches connected to an Equipment, moving them to new positions if necessary.
Other elements in the Branches are not affected and must be realigned using ordinary
routing commands.
Example:
RECON Finds all Nozzle elements which are Offspring of the current
element. For each Nozzle, any Branch Head (or Tail) which is
connected to it is repositioned at the Nozzle.
Command Syntax:
>-- RECOnnect -->
3.4 Selecting Component and Tube Details from

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

3.4.1 Choosing Components from a Displayed List

Keywords:
CHOOSE
Description:
This is only available in DEV GRAPHICS mode.
• The CHOOSE command displays Selection options on screen forms which can be
picked using the cursor. Once an element has been created using the NEW
command, CHOOSE may be used to list what is available in the Specification.
• The effect of choosing from the displayed list and applying the form setting via the OK
button is to set the SPREF and LSTUBE attributes of the current Component, taking
into account the choice made and the current bore. Specification-dependent Design
attributes (if any) will also be set, i.e. HEIG, ANGL, RADI and SHOP. The Component
may (optionally) be positioned and connected to the previous (or next) Component (or
to the pipe head or tail). If the Cancel button is selected, the Component’s attributes
will remain unchanged.
• It may be that a newly selected Component is unsuitable for connection to the
previous (or next) Component (or to the Pipe Head or Tail), for example due to
incompatible connection types. In such a case, the new Component will be force-
connected and a warning alert displayed. This action can be turned off by giving the
command
CHOOSE FORCECONNECT OFF
• Connection attempt will still be made, but Component will be left at Site origin if
connection types are incompatible.
• If the force-connect facility is OFF, a connection attempt will still be made following
component selection. In this case however, the newly selected Component will be left
at the Site origin if connection types are incompatible. This action can be turned off by
giving the command
CHOOSE AUTOCONNECT OFF
• No connection attempt will be made; Component will be left at Site origin.
• The default state is CHOOSE FORCECONNECT ON.
• If only one choice of Component is available, for example flanges of only one type are
valid at a particular bore, DESIGN will set SPREF and LSTUBE automatically. If there
are no valid choices, for example there are no Components of a particular type for the
specified bore, an error alert is displayed.
The CHOOSE command may be used within the same command line as a NEW command.
Example:
CHOOSE Displays a general Selection form for the current element.

Selection criteria displayed will depend on those available in
the specification.
Example form:

CHOOSE TEXT Displays a Selection form listing choices based on the

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

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

options.
Example: CHOOSE SPEC /RF150
CHOOSE DEFAULT
NEW REDU CHOOSE WITH ABOR 1 00 LBOR 80
NEW ELBO CHOOSE WI

TH STYP LR

Example form: As CHOOSE, but selections are made from the named
specification rather than from that of the owning Branch.
Default settings will be selected wherever they occur in the

Specification. For example, if the default STYP for a Reducer is
CONC, only Concentric Reducers will be listed in the selection
form.
Choose from Reducers with specified arrive and leave bores

only
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:
<wivl> is>--+-- PBOre integer --.

| | |-- ANgle
----------|
| | |-- RAdius
---------|
| | |-- ABOre
----------|
| | |-- LBOre
----------|
| | |-- PREssure
-------|
| | |-- TEMperature
----|
| |
‘-- RATing ---------+-- <uval> -->
and
<wiwor> is >--+-- STYpe --.
| | |-- TYpe
---|
| | |-- ACOnn
--|
| |
|-- LCOnn --+-- word -->
|
|-- PCOnn integer word -->
|
‘-- word --+-- value --.
| |
‘-- word ---+-->
3.4.2 Selecting Components from Specifications

An alternative method of selecting items from a Specification is to create the piping
Component, and then to ask the system to select a component of the correct type from the
current piping Specification. If there is a choice of component during selection, it is
sometimes necessary to specify answers to specification questions such as STYPE or
BORE before the correct item is selected.
Typical commands could be as follows:
NEW ELBO SEL WITH STYP LR
NEW TEE SEL WI PBOR 3 150
NEW FLAN SEL WI STYP WN
NEW REDU SEL WI STYP ECC LBOR 100
3.4.3 Selecting the Default Specification Component
Keywords:
SELECT
Description:
The SELECT command chooses a Component and its ‘Leave’ Tube from the Branch
Specification. Selecting the default Specification Component allows DESIGN to choose the
appropriate item. This is based upon information DESIGN can obtain from the Design and
from ‘default’ controls within the Specification. Default Selection is particularly applicable to
common fittings such as FLANGEs, GASKETs, ELBOWs etc. The information
automatically determined from the current element and its surroundings is as follows:
SPECIFICATION Obtained from the PSPE attribute of the Branch.

(ARRIVE) BORE Obtained from the (Leave) bore of the Previous element
(reverse in Backwards Mode).
ANGLE, HEIGHT, Obtained from the corresponding Current Element attributes.
RADIUS
SHOP Obtained from the corresponding Current Element attribute.
TEMPERATURE, Obtained from the corresponding Branch attributes.

PRESSURE
3.4.4 Selecting from Several Alternatives
Keywords:
SELECT
Description:
The SELECT command chooses a Component and Leave Tube from the Specification and
sets the appropriate current element attributes. In order to make a Selection from the
Specification, parameters for all the Specification Headings for that type of Component
must be automatically obtained or provided by the designer. In many cases, the default
choice may not be suitable. This may be because:
• One or more of the Specification Headings has no default parameter for that Component
(e.g. the Leave bore of a Reducer cannot be assumed)
• You wish to choose a non-default item (e.g. socket weld, not a weld-neck)
In both instances, the designer must specify the relevant Headings with the required Entry
as part of the SELECT command.
After a successful SELECT command, the design attributes will be updated with the
relevant values from the Specification. The relevant attributes are ANGLE, RADIUS and
SHOP, 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 ---+-->
.-----<-----.
/ |
>-- Q SPECification --*-- <qspci> --+-->
where <qspci> is:
>--+-- PBOre integer --.
| | |-- ANgle
----------|
| | |-- RAdius
---------|
| | |-- ABOre
----------|
| | |-- LBOre
----------|
| | |-- PREssure
-------|
| | |-- TEMperature
----|
| | |-- RATing
---------|
| | |-- STYpe
----------|
| | |-- TYpe
-----------|
| | |-- PCOnn
integer --|
| | |-- ACOnn
----------|

| | |-- LCOnn
----------|
| |
‘-- word -----------+-->
3.4.5 Selecting ‘Out-of-Specification’ Components

Keywords:
SELECT SPEC
Description:
If an ‘out-of-specification’ Component is required, this can be Selected using the SELECT
WITH SPEC command. This command uses the stated Specification rather than the default
Specification. Other Headings necessary to specify which ‘out-of-specification’ item is
required can be given in the same command.
Examples:
SEL WI SPEC /A3AH The current element will be Selected from the given
Specification using the default choice.
SEL WI SPEC / The current element will be Selected from the given A3AH
STYPE CTRL Specification using the default choice except for STYPE.
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 ---+-->

3.4.6 Selecting Components and Tube Separately

Keywords:
SELECT SPREF TUBE ROD HSTUBE LSTUBE LSROD HSROD
Description:
In some instances it may be necessary to Select Tube (or Rod) separately from its 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 The Component LSTU attribute (Leave Specification
(At Component) Tube) will be Selected with the default choice of TUBE except
for STYPE.
Command Syntax:
>-- SElect --+-- SPref ---.
| | |-- LStube
--|
| | |-- HStube
--|
| |
|-- LSrod ---|
| | |-- HSrod
---| | |
|-- TUbe ----| .-----<-----.
| | / |
‘-- ROD -----+-- WIth -- *-- <wivl> ---|
| | |-- <wiwor>
--’
|
|-- <gid> -->
| ‘--
>
Querying:
.-----<-----.
/ |
>-- Query --+-- SPRef ---.
| | |-- TUbe
----|

| | |-- LStube
--|
| | |-- HStube
--|
| | |-- LSrod
---|
| |
‘-- HSrod ---+-->
3.4.7 Direct Selection by Shortcode

Keywords:
SHORTCODE
Description:
The actual Specification Component name (SPREF for Components, LSTU or HSTU for
Tube) can be specified in order to Select a Component. This overrides the ordinary
Selection process by directly choosing the required item. The shortcode option assumes
Selection from the Current Branch Specification by automatically providing the specname
part. Thus it is assumed that the Specification Component name is of the form /specname/
shortcode.
Examples:
SHOR /EL50 The current element SPRE attribute will be set to /
specname/EL50 where /specname is obtained from the
Branch.
SHOR TUB /TU50 The current element LSTU (or HSTU) attribute will be
set to /specname/TU50 where /specname is obtained
from the Branch.
Note: /specname is shown as * on PDMS Specification listings.

Command Syntax:
>-- SHORtcode --+-- SPRef ---.
| | |-- TUbe
----|
| | |--
LStube --|
| | |--
HStube --|
| | |-- LSrod
---|
| | |-- HSrod
---|
| |
‘------------+-- name -->
Querying:
>-- Query --+-- SPRef ---.

| | |-- TUbe
----|
| | |-- LStube
--|
| | |-- HStube
--|
| | |-- LSrod
---|
| | ‘-- HSrod
---+-->
3.5 Re-selection of Existing Components and Tube

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

Keywords:
RESELECT
Description:
The RESELECT command chooses a new Component and its Leave Tube from the Branch
Specification. The default Selection parameters are obtained from the current element’s
surroundings (in the same way as for SELECT). If any further Selection parameters are
needed, they are obtained from the old Component Specification entries. The need to
respecify is therefore reduced.
Examples:
RESEL The current element and Leave Tube will be Selected from the new
default choice(s). Any parameters required that are not
obtainable from defaults will be derived from the old
Specification Component.
Note: This command only operates on Components that have already been Selected.

Command Syntax:
>-- RESElect -->
Querying:
.-----<-----.
/ |
<qspci> is explained in the section on Standard Syntax Graphs in Part 1 of the DESIGN
Reference Manual..
>-- Query --+-- SPRef ---.
| |
‘-- TUbe ----+-->
3.5.2 General Reselection of Components and Tube

Keywords:
RESELECT
Description:
This command allows existing Components and Tube to be Reselected according to new
parameters. Where new parameters are not stated or available through defaults, they are
obtained from the old Component Specification entries.
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.

Examples: (At Branch)

The current element and Leave Tube will be Selected
RESEL WI SPEC /NEWSPEC using the new Specification and any default
parameters. The remaining necessary parameters will
be obtained from the old Specification Component.
The current element HSTU attribute will be Selected

using default parameters and the specified STYPE. If
RESEL TUBE WI STYPE GLAS any further parameters are
necessary they will be obtained from the old
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 Standard Component Attributes

This section describes the standard Component element attributes that provide their
complete logical and physical descriptions. Although you may set them directly, many of
these attributes are automatically determined when using the Specification selection and
pipe routing commands described elsewhere.
Two classes of standard attribute exist for Components:

• Those which ‘point’ to a Specification item that provides a fixed Catalogue description
of the Component
• Those which cannot be part of the Catalogue description, as they are unique to each
occurrence in the Design
The standard Specification attributes of a Component are:
SPREF This points to a Specification Component that provides the
complete Catalogue description of the current element.
LSTUBE These point to a Specification Component that provides the
complete Catalogue LSROD description of the Tube emerging
from the current element Leave Point.
ISPEC This points to an Insulation Specification. The Branch
‘TEMPERATURE’ attribute is automatically used to determine
an insulation thickness from this Specification.
TSPEC This points to a dummy Tracing Specification and is used by
ISODRAFT to indicate trace heating requirements.
The remaining standard attributes are:
POSITION The Component’s position in Zone coordinates (neither Branch
nor Pipe have a POSITION, though Branch has head and tail
positions (HPOS and TPOS).
ORIENTATION The Component’s orientation in Zone coordinates (neither
Branch nor Pipe have an ORIENTATION, though Branch has
head and tail directions (HDIR and TDIR).
ARRIVE The Catalogue p-point that is on the Arrive side of the
Component.
LEAVE The Catalogue p-point that is on the Leave side of the
Component.
BUILT Management information to indicate if the item has actually
been built.
SHOP (Shop fabrication flag.) Used by ISODRAFT to determine in
which material list the item is to be shown.
ORIFLAG (Logical orientation flag.) Set and used automatically by PDMS
to determine if the Component has been oriented.
POSIFLAG (Logical position flag.) Set and used automatically by PDMS to
determine if the Component has been positioned.
The following attributes do not occur in all Components, but are sufficiently common to be
considered as standard:
ANGLE The (variable) angle of a Component.
HEIGHT The (variable) height of a Component.
RADIUS The (variable) radius of a Component.
LOFFLINE (Logical Offline flag.) Indicates, for reporting purposes, whether

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

CRFA (Multi-way Component Connection Reference.) Indicates the

elements that are connected to the free (neither Arrive nor Leave)
p-points of the Current Element.
3.6.1 Position and Orientation Attributes

Keywords:
POSITION ORIENTATION
Description:
The Component position and orientation attributes describe their location with respect to
Zone co-ordinates. This is because neither Branch nor Pipe have position or orientation
attributes and therefore do not have a co-ordinate system.
Command Syntax:
Component position and orientation are established using the pipe routing or ordinary
positioning commands described elsewhere.
Querying:
>-- Query --+-- POSition --+-- <bpos> --.
| | | | ‘------------|
| |
‘-- ORIentation ------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
>-- Query POSition -->
Gives the Component position in ZONE co-ordinates.
>-- Query ORIentation WRT SITE -->
Gives the Component orientation in SITE co-ordinates.
3.6.2 Component Arrive and Leave Attributes

Keywords:
ARRIVE LEAVE
Description:
This command sets the attributes that control which p-points are the Arrive and Leave for 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.
Example:
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 --+-->
3.6.3 Swapping the Arrive and Leave P-points

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

ARRIVE
P1 PH
CE
LEAVE
FLIP
(ARRIVE 2 LEAVE 1)
P2
PT
Figure 3:5. Component Arrive and Leave attributes (standard and Flipped)
3.6.4 The Component Specification Reference Attribute

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

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
Command Syntax:
>-- SPRef name -->

3.6.5 Variable Length Tube (and Rod) Attributes

Keywords:
LSTUBE LSROD HSTUBE HSROD
Description:
Straight lengths of Tube (ducting, trays and rod) between Components are not defined as
PDMS elements in the hierarchy. Instead, they are extruded from the Leave p-point of a
Component to the Arrive p-point of the next. Their geometric cross-section details are
stored in the Catalogue and are pointed at from the Upstream Component via its LSTU
attribute. At the Head of a Branch, there is no Upstream Component; therefore a special
Branch attribute exists to allow Tube from the Head to 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.
Examples:
LSTU /SPEC502/100L The Tube between the Leave p-point of this
(At Branch Component) Component and the Arrive of the Next (or
Tail) is specified by the named Specification
Component.
HST /SPEC502/100L As above, but between the Head and Arrive
(At Branch) of First Component (or Tail).
LSR /HS20/2.5 As first example.

(At Hanger Component)
HSR /HS20/2.5 As second example.
(At Hanger Component)
Note: These attributes are usually set automatically when the CHOOSE (or SELECT)
command is used.
Command Syntax:
>--+-- LSTube --.
| | |--
HSTube --|
| | |--
LSRod ---| | |
‘-- HSRod ---+-- name ----.
| |
‘-- NULREF --+-->
3.6.6 Insulation Specification Attribute
Keywords:

ISPEC
Description:
This attribute points to an insulation Specification. It is automatically cascaded down from
the Branch ISPE setting, but can also be set on an individual basis. In conjunction with the
Branch TEMPERATURE attribute, the ISPE insulates the Component and the Tube from its
Leave point.
Examples:
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 -->
Gives the insulation thickness.
Figure Missing!!
Figure 3:6. Variable length Tube between Components

3.6.7 Trace Heating Specification Attribute

Keywords:
TSPE
Description:
This attribute provides ISODRAFT with trace heating information. The trace heating
Specification pointed to is a dummy Specification defined in SPECON, having no
significance other than its name.
Example:
TSPE /TR50A The Current Component will be noted by ISODRAFT with the
given trace heating requirements.
TSPE NULREF Trace heating is removed.
Note: If the same trace heating is required for an entire Branch, TSPE should be set at
Branch level, from where it will cascade down to all new Components.
Command Syntax:
>-- TSPec --+-- name ---.
| |
‘-- NULREF --+-->
3.6.8 The Fabrication Flags

Keywords:
SHOP BUILT
Description:
These attributes indicate the location and status of construction of each Component. The
SHOP flag is used by ISODRAFT to determine in which material list the item will appear.
The BUILT flag can indicate whether or not the Component has been fabricated/built during
construction.
Examples:
SHOP TRUE The current element will 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.6.9 Position and Orientation Status Flags
Keywords: ORIFLAG
POSFLAG
Description:
These attributes are automatically set to TRUE when the Component is positioned and
orientated. They are used by DESIGN in several situations where it requires to know if a
Component has been properly positioned.
Examples:
POSF FALSE This setting will occur if the Components have been
transferred from a P&ID and not positioned. The Component will not
be drawn in the views.
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 --+-->
3.6.10 Variable Component Attributes

Keywords:
ANGLE HEIGHT RADIUS DESPARAMETERS
Description

Some Components have variable dimensions that must be specified in situ by the designer.
Once a Component has been selected from the Specification, altering, say, the ANGLE
may change its physical appearance.
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 When the CHOOSE (or SELECT) command is given, it will

(Before Selection) choose the ‘ANGLE45’ option if available in the Specification.
HEIG 300 If a variable height component, this dimension will alter as (After
Selection) specified.
Command Syntax:
>-- ANGle --+-- <uval> -----------------.
| |
‘-- <bdir> TOwards <bdir> --+-->
>-- HEIght <uval> -->
>-- RADius <uval> -->
>-- DESParameters <uval> -->
3.6.11 Offline/Straight-Through Component Attribute

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

Examples:
LOFF FALSE In the reporting utility, the current element will be treated as
a full Component which breaks the Tube lengths either side.
OFFL TRUE In the reporting utility, the current element will be included as
part of a single Tube length running through its Arrive-
toLeave centreline.
Note: The default setting for this attribute is dependent upon Component type.
Command Syntax:
>--+-- LOFFline --.
| |
‘-- OFFLine ---+-- TRue ---.
| |
‘-- FALse --+-->
3.6.12 Multi-Way Component Attributes

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

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

Keywords:
ORIENTATE
Description:
This command rotates the Component about its origin so that (in forwards mode) the Arrive
p-point is in the opposite direction to the previous Component’s Leave p-point.
If the Component is not concentric, it is necessary to specify the off-line orientation as well.
This is usually done by giving the direction of an off-line p-point. If it is not possible to
achieve an orientation because of the direction of the constrained centreline, DESIGN will
leave this off-line direction in the closest orientation to that requested.
Examples:
ORI Rotate the current element about its origin so that (in forwards mode) its Arrive Point
is in the opposite direction to the previous Component’s
Leave Point (see Figure 3:7.: Orienting a Concentric
Component).
ORI AND P3 IS U As above, and orient the off-line p-point (P3) in the specified
direction (see Figure 3:8.: Orienting a non-concentric
Component by means of an off-line p-point).
Note: The ORIENTATE command will not change the ANGLE, RADIUS etc. of a variable
Component to accommodate an oblique off-line direction.
Command Syntax:
>- ORIentate -+- <bdir> IS <bdir> -.
||
‘--------------------+- AND <bdir> IS <bdir> -.

| |
‘------------------------+-->
Querying:
.-------------------
<----------------. / |
>-- Query <marke> --*-- DIRection --. |
| | |
‘---------------+-- WRT --. |
| | | |-- IN ---+--
<gid> --’
|
‘-->
Figure 3:7. Orienting a Concentric Component

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

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

Examples:
DIR E Rotatethe Component about its origin such that (in forwards mode) its Arrive
point is in the opposite direction to the previous Component’s
leave point, and its leave point is East. If this requires a
change of angle and the Component has a variable ANGLE
attribute, then this will be altered to suit (see Figure 3:9.:
Changing the direction of variable-angle Components).
DIR AND P3 IS U45E As above, but P3 (rather than PL) is pointed to the new
direction (see Figure 3:9.: Changing the direction of
variableangle Components).
Note: If the new direction cannot be adopted by a fixed-angle Component, the item will be
pointed in the closest direction to that specified.
Command Syntax:
>-- DIRection --+-- AND <marke> IS --.
| |
‘--------------------+-- <bdir> -->
Querying:
.-------------------
<----------------. / |
>-- Query <marke> --*-- DIRection --. |
| | |
‘---------------+-- WRT --. |
| | | |-- IN ---+--
<gid> --’
|
‘-->

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

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

Examples:
CONNECT The arrive p-point of the Component is connected to the
leave p-point of the Previous Component (see Figure 3:10.:
Component connection).
CONNECT TO NEXT The leave p-point of the Component is connected to the
arrive p-point of the next Component (see Figure 3:10.:
Component connection).
CONNECT AND P3 IS As first example and the off-line p-point is oriented upwards
U (see Figure 3:10.: Component connection).
Note: Only adjacent Components (not Attachment Points) may be connected to; if
Connection Types or bores are incompatible, then an automatic FLIP takes place
and CONNECT is attempted again.
Command Syntax:
>- CONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> ->
| | |
| | ‘-->
| ‘-->
‘-->
Querying:
.------------------
<----------------. / |
>-- Query <marke> --*-- POSition --. |
| | |
‘--------------+-- WRT --. |
|| | |-- IN ---+--
<gid> --’
|
‘-->

Figure 3:10. Component connection
3.7.4 Forced Component Connection

Keywords:
CONNECT
Description:
This operates exactly as the CONNECT command, but ignores Connection and Bore
compatibility. The Component will be shown fully positioned, but data consistency checking
will still report incompatible connections unless the items are moved apart later.
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.

Examples:
Note: Only adjacent Components (not Attachment Points) may be force-connected. No
check on compatibility of bore or Connection Type occurs.
Command Syntax:
>- FCONnect -+- <marke> -+- TO <marke> -+- AND <bdir> IS <bdir> -->
| | |
| | ‘-->
| ‘--> ‘-->
3.8 Moving by a Known Distance

These commands move the Component a specified distance along the constrained
centreline. All the commands move the Component from its current position. The distance
moved may either be measured along the constrained centreline or some other planar
direction. All the examples in this section assume Forwards routing mode is in operation.
Generally, if Backwards is being used, then the effect of each command will be logically
reversed.
3.8.1 Moving Components

Keywords: MOVE
DISTANCE
Description:
This command moves the Component along the constrained centreline by a specified
distance.
Example:
MOVE DISTANCE 1000 The Current Component is moved from its present position
1000 along the constrained centreline (see Figure 3:11.:
Moving a Component by a given distance).
Note: A positive dimension moves the Component away from the Previous Component.
Command Syntax:
>-- MOVe DISTance <uval> -->
Querying:
>-- Query POSition <bpos> --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 3:11. Moving a Component by a given distance
3.8.2 General Moving of Components

Keywords:
MOVE PLANE DISTANCE
Description:
This command moves the Component along the constrained centreline. The distance
moved may be specified either in the direction moved or another planar direction.
Example:
MOVE PLANE N45E DI The current Component is moved from its present position
ST 1000 along the constrained centreline by 1000 along the N45E
direction (see Figure 3:12.: Moving a Component by a
distance specified in another plane).
Command Syntax:
>-- MOVe PLAne <bdir> DISTance <uval> -->
Querying:
>-- Query POSition <bpos> --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 3:12. Moving a Component by a distance specified in another plane
3.9 Positioning Components using Reference Planes

This section describes commands that position the Component on the constrained
centreline at the intersection with a fixed reference plane.
Any p-point on the Component may be used, although the default is the origin. This point is
positioned along the constrained centreline through the reference plane which is defined by
the 3D position through which it passes. The orientation of the reference plane defaults to
perpendicular to the constrained centreline, although a different planar direction can be
specified.
In no case is the volumetric geometry of the 3D model considered. These commands are
therefore not suitable for ‘clearance’ positioning.
All the examples in this section assume Forwards routing mode. Generally, if Backwards is
being used, then the effect of each command will be logically reversed.
3.9.1 Positioning with respect to the Previous Component

Keywords: DISTANCE
POSITION
Description:
This command positions the Component on the constrained centreline at a specified
distance from the origin of previous Component. Any p-point on the current element may be
used, the default being the origin.
Examples:

DIST 1000 The Component will be positioned on the constrained centreline 1000 from
the origin of the previous Component (see Figure 3:13.:
Positioning with respect to Previous Component).
POS PA DIST 1000 As above, but the Arrive point of the Component is used (see
Figure 3:14.: Positioning with respect to
Previous Component).
Command Syntax:
| |
‘----------------------+-- DISTance <uval> -->
Querying:
>-- Query --+-- POSition --.
| |
‘--------------+-- <marke> --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 3:13. Positioning with respect to Previous Component

Figure 3:14. Positioning with respect to Previous Component
3.9.2 Positioning the Component through an Intersection

Keywords: THROUGH
POSITION
Description:
This command allows the designer to position the Component through the intersection with
a fixed design element or position (say a Nozzle) or a cursor position. The Component is
positioned along the constrained centreline where the reference plane intersecting, say, the
specified Nozzle, cuts at right angles. For cursor positioning it is therefore advisable to use
orthogonal views for orthogonal piping.
Examples:
POS THR /TANK5 The origin of the current Component will be positioned on the
constrained centreline where this intersects the
perpendicular reference plane through the named element
(see Figure 3:15.: Positioning through an intersection).
POS PA THR E3000 The Arrive point of the current Component will be positioned
on the constrained centreline where the perpendicular
reference plane through E3000 N0 U0 intersects (see Figure
3:16.: Positioning through an intersection.
THR @ The Component will be placed on the constrained centreline

where the perpendicular reference plane indicated by the
cursor intersects (see Figure 3:17.: Positioning through an
intersection).
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:
| |
‘----------------------+-- THRough <bpos> -->
Querying:
>-- Query --+-- POSition --.
| |
‘--------------+-- <marke> --+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 3:15. Positioning through an intersection

3.9.3 Positioning with respect to an Intersection

Keywords:
POSITION DISTANCE FROM TO
Description:
This command positions the current Component so that its origin (or specified p-point)
intersects the reference plane either side of the specified fixed position.
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:18.: Positioning with
respect to an intersection).
DIST 1000 TO NEXT The Component will be placed on the constrained centreline
so that its origin is 1000 before of the Next
Component’s origin (see Figure 3:19.: Positioning
with respect to an intersection).
POS PA DIST 20 FROM PL The Component will be placed on the constrained

OF PREV centreline so that its Arrive point is 20 from the
previous Component’s Leave point (see Figure 3:20.:
Positioning with respect to an intersection).
Note: The reference plane is perpendicular to the constrained centreline. TO means closer
to the Previous Component than the reference plane. FROM means further from the
previous Component than the reference plane.
Command Syntax:
||
‘--------------------+- DISTance <uval> -+- FRom -.
| |
‘- TO ---+- <bpos> ->
Querying:
>-- Query <marke> --+-- POSition --.
||
‘--------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 3:18. Positioning with respect to an intersection

3.9.4 General Positioning through an Intersection

Keywords:
POSITION PLANE DISTANCE THROUGH FROM TO
Description:
This command differs from the basic options by allowing the reference plane to be specified
independently of the constrained centreline. This is particularly relevant for routing sloping
lines where a specific Easting or Northing is to be intersected.
Example:
PLANE E DIST 1000 The Component will be placed on the constrained centreline so
that its origin is 1000 from the previous Component’s origin in
an East/West direction (see Figure 3:21.: Positioning through
an intersection defined in an independent plane).
Command Syntax:
| |
‘--------------------+- PLANe <bdir> -+- DISTance <uval> -+- FRom -.
| | |
| ‘- TO ---+- <bpos> ->
|
‘- THrough <bpos> ->
Querying:
| |
‘--------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->

|
‘-->
Figure 3:21. Positioning through an intersection defined in an independent plane
3.10 Positioning Components ‘Point-to-Surface’

This section describes commands which position a Component on the constrained
centreline at a specified distance from the surface of a fixed design item.
Any p-point on the current element may be used for the manoeuvre, although the default is
the origin. In no case is the geometry of the current element considered. However, the
geometry of the referenced item is considered in one of three ways:
• If the item is a Design element, then its complete geometry will be considered.
• If the item is a Piping p-point at the Arrive or Leave of another Component, then the
Tube cross-section at that point will be considered.
• If the item has no geometry, i.e. a non-piping p-point, or is a position, then only that
point will be considered.
All the examples in this section assume Forwards mode. Generally, if Backwards mode is
being used, the effect of each command is logically reversed.
3.10.1 Positioning Components Either Side of an Object

Keywords:
POSITION DISTANCE INFRONT BEHIND
Description:
This command positions the Component on the constrained centreline at a specified
distance from a geometric object, point or position.
Examples: DISTANCE 30 INFRONT /WALL

DISTANCE 125 BEHIND (see Figure 3:22.: Positioning Components either side of an object
IDP @ and Figure 3:23.: Positioning
Components relative to a specified object).
The Component will be placed such that its origin is 125 the ‘other
side’ of the picked p-point. If this point is an Arrive or Leave, then
POS PL INF /ACCESS the Tube cross-section will be taken into account (see Figure
The Component will be placed 3:23.: Positioning Components relative to a specified object).
on the Constrained
The Component will be placed such that its Leave Point is zero
Centreline so that its origin is 30
distance ‘this side’ of the specified object (see Figure 3:23.:
‘this side’ of the specified object
Positioning Components relative to a specified object).
Command Syntax:
| |
‘--------------------+- DISTance <uval> -+- INFront -.
| |
‘- BEHind --+- <gid> --.
| | |-
<marke> -|
| |
‘- <bpos> --+->
Querying:
| |
‘--------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

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

Figure 3:23. Positioning Components relative to a specified object
3.10.2 Positioning Components On Top of or Under an Object

Keywords:
POSITION DISTANCE ONTOP UNDER
Description:
This command positions the Component on the constrained centreline at a vertical 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:24.: Positioning above/below an
object).
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:24.: Positioning above/below an object).
Command Syntax:
| |
‘--------------------+- DISTance <uval> -+- ONTop -.
| |
‘- UNDer -+- <gid> --.
| | |-
<marke> -|
| |
‘- <bpos> --+->
Querying:
| |
‘--------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->

Figure 3:24. Positioning above/below an object
3.10.3 General Component Positioning Using Planes

Keywords:
POSITION PLANE DISTANCE INFRONT BEHIND ONTOP UNDER
Description:
This command differs from the basic options by allowing the reference plane to be specified
in a different direction from that of the constrained centreline.

Example:
PLANE E DIST 1000 The Component will be placed on the constrained centreline
INFRONT /WALL such that its origin is 1000 ‘this side’ of /WALL, measured East-West
(see Figure 3:25.: Positioning relative to an object specified
in a different plane).
Command Syntax:
| |
‘--------------------+- PLAne <bdir> -.
| |
‘----------------+- DISTance <uval> -+- ONTop ---.
| | |-
UNDer ---|
| | |-
INFront -| |
|
‘- BEHind --+- <gid> --.
| | |- <marke>
-|
| |
‘- <bpos> --+->
Querying:
| |
‘------------+-- WRT --.
| |
|-- IN ---+-- <gid> -->
|
‘-->
Figure 3:25. Positioning relative to an object specified in a different plane

3.11 Component Clearance Positioning

The commands in this section position the Component on the constrained centreline to give
a specified clearance distance from a fixed design item.
The clearance specified usually takes into account both the current element and referenced
element geometric shapes. However, the following rules also apply:
• If the current element or referenced element is used and has a geometric shape, then
this is considered.
• If an Arrive or Leave p-point on the current element or referenced element is used,
then the Tube cross-sectional geometry at that point is considered (not the
Component geometry).
• If the current element or referenced element has no geometry, or a p-point is used that
is not an Arrive or Leave, or a position is used, then only the position is considered.
A selection of Bottom of Pipe (BOP) commands are also available that provide clearance
for the Tube cross-section at a Component Leave Point. All the examples in this section
assume Forwards routing mode. If Backwards is in use, then the effect of each command is
logically reversed.
3.11.1 Clearance from the Previous Component

Keywords:
CLEARANCE
Description:
This command places the Component at a specified clearance from the previous
Component on the constrained centreline. The whole geometry of both Components is
considered.
Example:
CLEA 500 The Component will be placed on the constrained centreline 500 clear of the
Previous Component (see Figure 3:26.: Clearance from a
Previous Component).
Command Syntax: >--

CLEArance <uval> -->
Querying:
|| |-- BOP
-------| | |
‘-- TOP -------+-- WRT --.
| |
‘-- IN ---+-- <gid> -->

Figure 3:26. Clearance from a Previous Component
3.11.2 Component Clearance Either Side

Keywords:
CLEARANCE INFRONT BEHIND
Description:
This command places the current Component on the constrained centreline at a 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:27.: Component clearance either
side of a fixed object).
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 Component’s Leave
point (see Figure 3:27.: Component clearance
either side of a fixed object).
Command Syntax:
>-- CLEArance --+-- <uval> --.
||
‘------------+-- INFront --.
||
‘-- BEHind ---+-- <gid> ---.
| |

|-- <marke> --|

| |
‘-- <bpos> ---+-->
Querying:
|| |-- BOP
-------| | |
‘-- TOP -------+-- WRT --.
| |
‘-- IN ---+-- <gid> -->
Figure 3:27. Component clearance either side of a fixed object

3.11.3 Component Clearance Vertically
Keywords:
CLEARANCE ONTOPUNDER

Description:
This command places the current Component on the constrained centreline at a specified
vertical clearance above or below a fixed object. If the Arrive or Leave point of the
referenced object is used, then the Tube cross-section emerging at this point is considered
rather than the full item geometry.
Examples:
CLEARANCE ONTO / The current Component will be placed on the constrained
BEAM centreline at zero clearance above the specified object
(see Figure 3:28.: Component clearance above/below a
fixed object).
CLEARANCE 50 The current Component will be placed on the constrained
UNDER /BEAM centreline at 50 vertical clearance below the specified
object (see Figure 3:28.: Component clearance above/
below a fixed object).
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:28.:
Component clearance above/below a fixed object).
Command Syntax:
>-- CLEArance --+-- <uval> --.
| |
‘------------+-- ONTop --.
| |
‘-- UNDer --+-- <gid> ---.
| | |--
<marke> --|
| |
‘-- <bpos> ---+-->
Querying:
|| |-- BOP
-------| | |
‘-- TOP -------+-- WRT --.
| |
‘-- IN ---+-- <gid> -->

Figure 3:28. Component clearance above/below a fixed object
3.11.4 Tube (Bottom of Pipe) Clearance

Keywords:
BOP TOP ONTOP UNDER INFRONT BEHIND
Description:
This command places the current Component on the constrained centreline so that 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:29.:
Tube clearance relative to a fixed object).
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:29.: Tube clearance relative to a fixed object).
BOP 30 BEHIND PL OF / As above, but 30 to the far side of the Leave Tube of /
FLAN FLAN (see Figure 3:30.: Tube clearance taking into
account the Tube diameter).
Command Syntax:
>--+-- BOP --.
| |
‘-- TOP --+-- <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.
Querying:
| | |-- BOP
-------| | |
‘-- TOP -------+-- WRT --.
| |
‘-- IN ---+-- <gid> -->

Figure 3:29. Tube clearance relative to a fixed object
Figure 3:30. Tube clearance taking into account the Tube diameter

3.11.5 General Clearance of Components and Tube

Keywords:
POSITION PLANE CLEARANCE INFRONT BEHIND ONTOP UNDER
Description:
This command differs from the basic options in two respects:
• The clearance dimension can be in an independent plane from the constrained
centreline.
• The current element Arrive or Leave Tube can be used (similar to BOP) rather than
the whole element geometry.
Examples:
PLANE E CLEARANCE 1000 The current Component will be placed on the
constrained centreline so that it is 1000 clear of the
Previous Component in an East-West direction (see
Figure 3:31.: Component clearance specified relative
to an independent plane).
POS PL CLEAR 100 The current Component will be placed on the
ONTO /BEAM constrained centreline so that the Tube from its Leave
Point is 100 vertically above /BEAM (same as BOP)
Command Syntax:
| |
‘--------------------+- PLAne <bdir> -.
| |
‘----------------+- CLEARance <uval> -+- ONTop ---.
| | |-
UNDer ---|
| | |-
INFront -| | |
‘- BEHind --+- <gid> --.
| | |-
<marke>-|
| |
‘- <bpos> --+>
Querying:
|| |-- BOP
-------| | |
‘-- TOP -------+-- WRT --.
| |
‘-- IN ---+-- <gid> -->

Figure 3:31. Component clearance specified relative to an independent plane
3.12 Dragging Equipment and Piping Networks

If equipment is repositioned using ordinary positioning commands, the pipes connected to it
do not automatically move with the item. The DRAG command is used to move
Constrained Networks of Piping, Equipment and Nozzle elements all together. How the
constrained network is created depends on the direction of the dragging operation and the
type of item being dragged.
When a DRAG command is given, the current element is displayed normally, together with
the constrained network. This network finishes where a legal end is found.
Items that can be dragged are:
• Piping Components
In this case the network is formed by searching outwards in all directions from the
component until a legal end is found for each ‘leg’ of the network.
• Nozzles
The piping network connected to the Nozzle is searched for legal ends.
• Equipment

The piping networks connected to all Nozzles owned by the equipment are searched
for legal ends.
A legal end for a constrained network can be:
• A piece of tube that can be extended parallel to the displacement
• A piece of tube that can be compressed parallel to the displacement without becoming
negative in length
• A Nozzle
• A point between two mis-aligned components
• A point between two incompatibly-connected components
• Any component that has not yet been positioned and orientated
• Any element in a design area that cannot be modified due to the designer’s access
rights
In some instances, the DRAG operation may fail to establish a constrained network. This
may be because:
• The internal search limit has been reached
• A LOCKED element has been found in the network
3.12.1 Dragging Equipment and Nozzles

Keywords:
DRAG AT BY POSITION MOVE
Description:
This command repositions the current element and constrained network to the 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.
The current element and constrained network are moved
DRAG MOVE N CLEAR North to the specified clearance in front of element
1000 INF /BUILD10 /BUILD10.
Command Syntax:
The full DRAG command syntax is extensive but may be summarised as follows:
>-- DRAG --+-- <absol> --.
| |
‘-- <relat> --+-->

where:
<absol> defines any absolute positioning command, e.g. AT,
POS, etc.
<relat> defines any relative positioning command, e.g. BY,
MOVE, etc.
The full expanded syntax is given below for reference:
<absol> = >--+-- AT --+-- <bpos> ---.
| | | | ‘--
<polar> --|
| | |-- <pppos> --. |
| | |
‘-- <polar> ---+--------+-->
<polar> = >--+-- POLar <bdir> --.
| |
‘-------------------+-- <plane> -->
<pppos> = >-- POSition --+-- <marke> --+-- AT --+-- <bpos> ---.
| | | | | | ‘--
<polar> --|
| | | | ‘-- <polar>
-----------|
| | |-- AT --. |
| | | ‘--------+-- <bpos> ---. |
| | |
‘-- <polar> --+-------------+-->
<plane> = >-+- PLAne <bdir> -+- DISTance <uval> -+- <repla> ------.
| | | | | | ‘----------------|
| | | | |- <repla> --------------------------|
| | | | |- THRough <bpos> -------------------|
| | | | ‘- CLEArance -+- <uval> -. |
| | | | | ‘----------+- <repla> -|
| | | | |- <planf> -|
| | | | ‘-----------| |- DISTance - <uval> -+-
<repla> -. |
| | | | | |- <planf> -||
| | | | | ‘-----------+-------------------|
| | |- CLEArance -+- <uval> -. |
| | | | | ‘----------+- <repla> -. |
| | | | | |- <planf> -||
| | | | | ‘-----------+----------------|
| | |- <repla>
-------------------------------------------| | | |-
THRough <bpos> ------------------------------------| |
|
‘- <planf> -------------------------------------------+>
<repla> = >--+-- INFront --.
| |
|-- BEHind ---+-- <sgid> ---.
| | | | |-- <marke>
--|
| | | | ‘-- <bpos>
---|
| | |-- FROm --. |
| | |
‘-- TO ----+-- <bpos> ------+-->
<planf> = >--+-- ONTop --. |
|
‘-- UNDer --+-- <sgid> ---.
| | |-- <marke>
--|
| |
‘-- <bpos> ---+-->

<relat> = >--+-- BY <pos> --+-- WRT --.

| | |
| |-- IN ---+-- <sgid> --.
| | | | ‘----------------------|
| |
‘-- <relmo> --------------------------+-->
<relmo> = >- MOVe -+- <marke> -+- ALOng -.
| | |
| |---------+- <bdir> <plane> ----.
| | | | |- BY <pos> -+- WRT -. |
| | | | | | | ‘- IN
--+- <sgid> -|
| | | | ‘- <plane>
---------------------|
| | |- ALOng -.|
| | | |---------+- <bdir> <plane>
----------------| | | |- BY - <pos> -+-
WRT -. |
| | | | | ‘- IN --+- <sgid>
-----------|
| |
‘-- <plane> --------------------------------+->
Figure 3:32. Dragging Equipment and Nozzles by a specified amount

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

Keywords:
DRAG AT BY POSITION MOVE DISTANCE THROUGH
FROM TO CLEARANCE INFRONT BEHIND ONTOP
UNDER
Description:
This command is identical to the DRAG command described in the previous subsection
except that, if the current element is a Branch, the bottom/top of piping positioning syntax
can be used.

Examples:
DRAG THRO @ The current element and constrained network are moved along the
constrained centreline until the origin of the current
element lies on a reference plane which passes
through the cursor position.
DRAG MOVE S DISTANCE The current element and constrained network are 1000
moved South by the specified distance.
Examples: CLEAR 150

The current element and constrained network are dragged so
DRAG DISTANCE 1000 ONTO that the origin of the current element is 1000 above /GRADE.
/GRADE
The current (Branch) element and constrained network are
dragged so that the Tube will be positioned on top of
DRAG BOP ONTO /BEAM2-1 /BEAM2-1 with a clearance of 150.
Note: As it changes orientation as well as position, CONNECT cannot be used in conjunction with
DRAG.
Command Syntax:
>-- DRAG --+-- <absol> --.
| | |-- <relat> --|
| |
‘-- <botop> --+-->
<botop> = >--+-- BOP --. | |
‘-- TOP --+-- <uval> --. | |
‘------------+-- <repla> --.
| |
‘-- <planf> --+-->
Figure 3:35. Dragging Piping to a specified position

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

Automatic Pipe Routing
4 Automatic Pipe Routing

The automatic pipe-routing facilities of DESIGN enable simple orthogonal pipe routes to be
generated automatically. Additionally, a number of pipes can be ordered and spread across
pipe racks once the provisional routes have been determined.
In its simplest form, a single Branch may be routed from one point to another, by setting the
head and tail positions and using the route command. In a more complex role, these
facilities can be used to route a complex set of pipes, avoiding obstructions and following
preferred paths.
For more complex pipe routing, Ptrac, Pvol and Rplane elements may be used to steer the
automatic routing process along preferred areas. These must be created and positioned
before entry to automatic routing, because the autoroute process operates with restricted
command syntax, which does not allow elements to be created.
4.1 Accessing the Automatic Pipe Routing Facilities

The automatic pipe routing facilities are set aside from the rest of the DESIGN commands
in a separate command structure called Autoroute Mode.
4.1.1 Entering and Leaving Autoroute Mode

Keywords:
AUTOROUTE
EXIT
Description:
The AUTOROUTE command is used to enter the automatic pipe-routing facilities. Once in
autoroute mode, the command syntax is restricted to those commands necessary for
automatic routing and rack ordering. To return to the full DESIGN syntax, the EXIT
command is used.
Example:
AUTOROUTE Enters Autoroute mode
Returns to the full DESIGN
EXIT syntax
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.1 Routing Pipes along Preferred Axes

The automatic pipe routing process will only route pipes orthogonally. However it may
follow an axis system other than those of the world. Before any routing can take place, the
required axis system must be defined.
Keywords:
AXES
Description:
All pipe routing will be orthogonal to the axes defined by the AXES command. This may be
taken as the current axes of any element in the database, but it must be orthogonal with the
Nozzles and pipe head directions which are being considered.
Example:
AXES /ZONE1 The routing axes will be set to the axes of /ZONE1
Command Syntax:
>-- AXes <sgid> -->
4.2.2 Setting Routing Planes

Keywords:
RPLANE

Description:
The RPLANE command sets up the list of elements which are to be considered as routing
planes.
Example:
RPLANE /PTRAC1 Sets /ZONE1 as an element in the Routing Plane list. All
RPLAN elements, in the hierarchy below /ZONE1 will be
considered.
RP /RP1 /RP2 Adds /RP1 and /RP2 to the list. A maximum of 150 RPLAN
elements may be considered by the automatic routing
process.
RP Clears the list of Routing Planes.
Command Syntax:
.-----<----.
/ |
>-- RPlanes --*-- <sgid> --+-->
4.2.3 Setting Penalty Volumes

Keywords:
PVOL
Description:
The PVOL command sets the list of penalty volumes which will be considered during the
automatic routing process.
Example:
PVOL /PV1 Adds /PV1 into the list of Penalty Volumes. If the element being added is
not a PVOL, then all items below it in the hierarchy are
scanned.
Example:
PV /PZONE1 /PZONE2 Adds /PZONE1 and /PZONE2 to the list. A maximum of 1000
PVOLS may be considered during automatic routing.
PV Clears the list of Penalty Volumes.
Command Syntax:
.----<-----.
/ |

>-- PVolumes --+--*-- <sgid> --+-->

|
‘-->
4.2.4 Invoking the Automatic Routing Process

Automatic pipe routing can be invoked by issuing the ROUTE command with a list of Pipes
to be routed. The Pipes to be routed must have empty Branches, with Head and Tail
references set.
Keywords:
ROUTE
Description:
The ROUTE command begins the procedure of finding logical routes for all of the branches
included in the routing list. Each time a successful route has been found, a message is
output stating the total Pipe length and the number of Elbows used. During the routing
process, Elbows are selected automatically from the Pipe Specification by default. Bends
may be selected in preference to Elbows by specifying this option as part of the ROUTE
command.
Example:
ROUTE /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.2.5 Setting the Nozzle Offset Factor

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

OFFSET 5 Sets the offset to be five times the bore of its associated Nozzle.
Command Syntax:
>-- OFFSETfactor integer -->
Querying:
>-- Query OFFSET -->
4.3 Refining the Automatic Pipe Routes

The automatic routing process often results in a set of common centreline routes down the
centre of a rack. The following section describes the rack ordering facilities which are able
to refine these routes into a more acceptable form.
The rack ordering process works by spreading a number of pipes across a predefined rack
volume. You have various options which may be set to control the spacing of pipes and the
direction of spread across the rack. The parameters which need to be input are:
• The location and dimensions of the rack (the RACK command)
• How the pipes are to be arranged on the rack (the SDIR command)
• The order in which the pipes will be placed • The minimum clearance between
adjacent pipes
4.3.1 Defining the Rack to be Used.

Keywords:
RACK
Description:
The rack is defined by the axes of a PVOL element in the database whose size should be
similar to the physical rack area expected. The PVOL width is important, because its edges
determine the position of the first pipe if the pipes are to be spread from one side of the
rack.
Example:
RACK /PVOL1 Sets /PVOL1 to be the rack.
Command Syntax:
>-- RAck <sgid> -->
4.3.2 Defining the Direction of Spread
Keywords:
SDIR
Description:

The spread direction is the direction in which the pipes will be spread laterally when they
are ordered along the rack. The default position from which the pipes are spread is the
centre of the PVOL. This may be changed to the side of the PVOL by adding the parameter
FROMSIDE to the command.
Examples:
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.3.3 Defining the Base Direction

Keywords:
BASE
Description:
This is the direction in which the pipes will be moved in order to sit on the rack. By default,
this is the direction of the smallest side of the PVOL.
Example:
BASE W Sets the base direction to be West. (This should always be

perpendicular to the spread direction.)
Command Syntax:
>-- BAse <bdir> -->

4.3.4 Spreading Pipes about the Rack

Keywords:
SPREAD
Description:
SPREAD moves the pipes laterally across the rack in the SDIR direction to give the
specified clearance. The default clearance is 50mm between pipe walls on the same
centreline.
Examples:
SPREAD /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-to-wall clearance of 75mm.
SP ALL Repeat previously defined order sequence (for example, on

a subsequent rack).
Command Syntax:
>-- SPread --+-- WW ---.
| | |--
FF ---|
| | |--
WF ---|
| | |--
ALL --| |
|
‘---------+-- <uval> --. .-----<----.
| | / |
‘------------+-*-- <sgid> --+-->
4.3.5 Setting the Bottom-of-Pipe Position

Keywords:
BOP
Description:

The BOP command moves the specified pipes such that their outside diameters are resting
on the rack plane in the BASE direction.
Examples:
BOP /ZONE1 Sets the BOP of all pipes in /ZONE1 to sit on the specified rack
BOP ALL Repeat previously defined order sequence
Command Syntax:
>-- BOP --+-- ALL -->
|
|-- <uval> --. .-----<----.
| | / |
‘------------+-*-- <sgid> --+-->
Note: No ordering takes place with the BOP command; it is expected that the BOP
command is used after a spread.
4.3.6 Combined Spreading and BOP Operations

Keywords:
ORDER
Description:
The ORDER command combines both the SPREAD and BOP operations. It spreads the
pipes across the rack to give the required clearances, and then moves them into contact
with the rack plane.
Examples:
ORDER /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
---|

Structural Design Using Catalogue Components
| | |-- ALL
--| | |
‘---------+-- <uval> --. .-----<----.
| | / |
‘------------+-*-- <sgid> --+-->
5 Structural Design Using Catalogue
Components
This chapter first describes how logically connected structural steelwork may be built up in
DESIGN by choosing Components from the Catalogue. Such structures will normally exist
in the DESIGN hierarchy at Framework (FRMW) or Subframework (SBFR) level. The
concepts are then extended for use in building designs, using other materials such as
concrete.
The principal types of element involved in steelwork design are:
Nodes
These define the points within the 3D design model between which steel construction
members are to run. Primary Nodes have their position defined in free space, whereas
Secondary Nodes have their position defined relative to an owning steel Section. Nodal
data, including the attributes of member elements of Nodes, is particularly relevant for
stress analysis of the steelwork structure.
Sections
Sections represent the physical steel members (columns, beams, bracing struts etc.) which
make up the interconnected structure. Their cross-sections are defined by reference to
Catalogue 2D Profile elements, while their lengths are derived from the positions of the
Nodes between which the Sections run.
Joints
These are Catalogue items which represent the physical connections between structural
members. Primary Joints are owned by Primary Nodes; Secondary Joints are owned by
Secondary Nodes. Multiple connections are represented by Primary or Secondary
Compound Joints, which own a SubJoint for each connection point. Linear Joints are
used to connect the edges of panels to structural sections or to other panels.
Panels
Panels represent any sheet materials used to clad a structural model. Their shape is
determined by linking together a set of Panel Vertex elements to form a 2D Panel Loop,
which is then extruded in the third dimension to give the required panel thickness.
Fittings
Steelwork Fittings and Panel Fittings are Catalogue items which can 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 Creating and Positioning Primary Nodes

Keywords:
NEW PNODE NPOS
Description:
The first step in creating a new piece of structural steelwork is often the creation and
positioning of a network of Primary Nodes within the 3D design model. PNOD elements are
created, as for other Design elements, by using the NEW command. They may be
positioned either by using a standard positioning command or by setting the NPOS (Node
Position) attribute directly.
Nodes have no physical size: their positions are used to define the points in space between
which steel Sections are to be positioned/strung.
Examples:
NEW PNOD /PNOD1 AT E1000 Creates a Primary Node named /PNOD1 at the
N500 U500 specified position.
(At FRMW or SBFR level)
NEW PNOD /PNOD2 COPY Creates a Primary Node which is displaced from the PREV
BY E1000 previous one in the specified way.
NEW PNOD /PNOD3 NPOS Creates /PNOD3, then places it at the specified
E2000 N1000 D500 position.
Command Syntax:
>-- NPOSition -- <bpos> -->
(The standard element creation syntax is described in Part 1 of the DESIGN Reference
Manual.)

Querying:
Q NPOS
5.2 Creating and Connecting Sections Automatically

Keywords:
STRING FROM TO
Description:
The STRING command is a very powerful multi-functional tool which performs the following
operations automatically:
• A Section (SCTN) element is created, running between two named Nodes. The Node
positions are used to set the Section’s POSS (Start Position) and POSE (End
Position) attributes. The order of occurrence of the named Nodes in the STRING
command line is used to set the DRNS (Start Direction) and DRNE (End Direction)
attributes (on the basis that the Section is strung FROM start TO end).
• Joint elements (PJOI or SJOI) are created at each Node and are orientated so as to
be compatible with the new Section. Thus, both the OPDI (Origin Plane 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 Strings a Section named /COLUMN1 between the /PNOD1
TO /PNOD2 specified Primary Nodes.
STRING BEAM FROM Strings a Section of GTYPE BEAM between the named
/PNOD2 TO /SNOD3 NAME Primary and Secondary Nodes. The Beam is named
/UB80.LEV2 separately in the second command line.
Note: The presence of a Section is shown on the DESIGN graphical display as a

centreline-only representation (broken line) at this stage. The Section has no
physical form, other than a derived length (related to the inter-Node separation),
until its cross-section has been defined by setting a reference to a Catalogue Profile
element.
Command Syntax:
>-- STRIng -+- name -.
| |
‘--------+- word -.
| |

‘--------+- FRom - <gid> - TO - <gid> -.

| |
‘- TO - <gid> - FRom - <gid> -+-->
5.3 Section Attributes
A Section is a linear structural component such as a universal beam, column, brace, tie,
strut, etc. Sections are assumed to be ‘prismatic’; that is, they are assumed to have uniform
properties throughout their length, including uniform cross-sectional dimensions.
The overall dimensions of a 3D design Section are derived from two sources:
• Its cross-sectional dimensions are defined by a cross-reference to a 2D Profile
element stored in the Catalogue DB.
• Its length is derived from the separation between the points defined by its Start
Position (POSS) and End Position (POSE) attributes.
This section describes the main attributes which together define a Section as a 3D physical
entity within the interconnected structure.
5.3.1 Cross-Sectional Profile via a Specification Reference

Keywords:
SPREF
Description:
The SPREF (Specification Reference) attribute of a Section must point to a valid Profile
element in a Catalogue DB in order for the Section to be given a physical representation by
DESIGN. This is achieved by setting SPREF to the name of a Specification Component in
a Project Specification.
Example:
SPRE /203X203X55KG.UB Sets the Specification Reference of the current Section

to point to a Profile in the Catalogue. (The .UB suffix in
the Specification Component name would normally
indicate that this Profile represents a Universal Beam.)
Command Syntax:
SPRef name
Querying:
Q SPRef
5.3.2 Generic Type

Keywords:
GTYPE
Description:

The GTYP attribute may be set to a PDMS word which indicates the purpose of the Section
within the structure. Its setting is not obligatory. (See the PARAGON Reference Manual for
a list of suggested GTYP word settings for Profile elements.)
Example:
GTYP BEAM Sets the GTYP of the current Section to BEAM.
Command Syntax:
>--- GTYPe --- word --->
Querying:
Q GTYPe
5.3.3 Start and End Positions

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

specified Primary Node.
Command Syntax:
>--+-- POSStart --.
| |
‘-- POSEnd ----+-- <bpos> -->
Querying:
Q POSStart

Q POSEnd
5.3.4 Start and End Plane Directions
Keywords:
DRNSTART DRNEND
Description:
The directions of the start and end cutting planes of a Section (that is, the directions of the
perpendiculars to the planes which define the ‘cut’ ends of the Section) are usually defined
automatically when the Section is connected within the structural model; either by Stringing
(see Creating and Connecting Sections Automatically) or manually (see Manually
Connecting Sections). The settings of the corresponding DRNS and DRNE attributes are
then derived automatically from the directions of the associated Joint’s Cutting Planes.
It is also possible to set DRNS and DRNE specifically; for example, where a Section
extends into free space, with at least one end unconnected. In this case each cutting plane
direction must be in the general direction of the other end of the Section.
Examples:
DRNS N45W Sets DRNS to the specified direction, regardless of the
direction of the Section’s Z-axis.
DRNE PERP Sets DRNE so that the end cutting plane is perpendicular to
the Section’s Z-axis (giving a square end as opposed to a
chamfered end for a Section which has a skewed
connection).
Command Syntax:
>--+-- DRNStart --.
| |
‘-- DRNEnd ----+-- <bdir> ---------.
| |
‘-- PERPendicular --+-->
Querying:
Q DRNStart
Q DRNEnd
5.3.5 Orientation Angle

Keywords:
BANGLE
Description:
The orientation of a Section about its Neutral Axis is defined in terms of an angular
clockwise rotation when viewed in the POSS-to-POSE direction. The angle of rotation from

the default orientation is held as the setting of the Beta Angle (BANG) attribute of the
Section.
BANG
NA
Example:
BANG 90
Command Syntax:
>-- BANGle value -->
Querying:
Q BANGle
5.3.6 Joint Start and End References

Keywords:
JOISTART JOIEND
Description:
Section ends which have been connected in the structure have their JOIS (Joint Start) and
JOIE (Joint End) attributes set such that they cross-refer to the Joints to which those ends
are connected. (The Joints have a similar cross-reference, the CREF attribute, back to the
attached Section.)
These attributes are set automatically when a Section is connected and you will not usually
need to set them specifically.
Example:
JOIE /PJOI.RB.2 Sets logical connection from Section’s end to named Primary
Joint.
Command Syntax:
>--+-- JOIStart --.
| |
‘-- JOIEnd ----+-- <gid> -->
Querying:

Q JOIStart
Q JOIEnd
5.3.7 Start and End Connection Types
Keywords:
CTYSTART CTYEND
Description:
Section ends which have been connected in the structure have their CTYS (Start
Connection Type) and CTYE (End Connection Type) attributes set such that they match
those of the Joints to which those ends are connected. This is done by setting CTYS/CTYE
to a word which matches the Joint’s CTYA attribute in the Catalogue; see the VANTAGE
PDMS PARAGON Reference Manual.
These attributes are set automatically when a Section is connected and you will not usually
need to set them specifically.
Example:
CTYS BOLT The Section’s start is to be connected to its attached Joint by means of
bolts. (The CTYA of the Joint must also be set to BOLT for a
compatible connection; see Part 3 of the DESIGN Reference
Manual for information about data consistency checking.)
Command Syntax:
>--+-- CTYStart --.
| |
‘-- CTYEnd ----+-- word -->
Querying:
Q CTYStart
Q CTYEnd
5.3.8 Start and End Releases

Keywords: SRELEASE
ERELEASE
Description:
The two Release attributes, the Section Start Release (SREL) and the Section End
Release (EREL), may be used to define how the Section behaves under the effect of
applied forces and moments. They are relevant only for stress analysis of the structure.
The attribute settings allow for two types of movement of the Section ends when external
forces are applied, namely:
• Linear movement along a specific axis (DX, DY, DZ)

• Rotation about a specific axis (RX, RY, RZ)
Example:
SREL DX RX RY The Start of the Section is constrained such that it can move only
in the X direction and can rotate only about the X and Y axes.
Command Syntax:
>--+-- SRELease --. .---<---.
| | / |
‘-- ERELease --+--*-- DX ---|
| | |-- DY
---|
| | |-- DZ
---|
| | |-- RX
---|
| | |-- RY
---|
| | |-- RZ
---|
| |
‘-- sign --+-->
Querying:
Q SRELease
Q ERELease
5.4 Creating and Positioning Secondary Nodes

A Secondary Node is owned by, and positioned relative to, an existing Section. It enables
you to position and connect another Section (an Attached Section) at any point along the
length of the first Section (the Owning Section), rather than having to define the position of
the Attached Section in ‘free space’.
Keywords:
NEW SNODE ZDISTANCE
Description:
SNOD elements are created, as for other Design elements, by using the NEW command.
They are positioned by specifying their distance from their owning Section’s Start Position,
measured along the Neutral Axis towards the End Position. This distance, which is held in
the Node’s ZDIST attribute, may be specified as an absolute length, as a proportion of the
overall distance between POSS and POSE (i.e. a proportion of the derived length of the
Section), or by reference to any marker (pin, p-point, p-line etc.), element or plane.

Examples: PLANE W30N DIST 0.0
Creates a Secondary Node named /SNOD1 at
NEW SNOD /SNOD1 ZDIST the specified distance from the start of the
1500 (At SCTN level) Section. The Node is positioned on the Neutral
Axis of the owning Section.
The position of the new Node is measured from

NEW SNOD /SNOD2 IS 1250 the POSE position rather than from the default
FROM END reference of POSS.
The new Node is positioned one third of the way

NEW SNOD /SNOD4 ZDIS PROP along the Section’s Neutral Axis, measured from
.33 the start of the Section.
The new Node is positioned one quarter of the

way along the Section’s Neutral Axis, measured
NEW SNOD /SNOD3 ZDIS PROP
from the end of the Section.
0.25 FROM END
The new Node is positioned at the intersection of
the owning section’s neutral axis with the defined
NEW SNODE /SNOD5 ZDIS plane.
Command Syntax:
>-- ZDIStance --+-- <uval>
--------------. |
|
|-- PROPortion -- value -+-- FRom --+--
STart --.
| | | | | | |-- ENd ----|
| | | | | | ‘-- <gid> --|
| | | |
‘----------------------+
|
| | |-- <marke>
------------------------------------| |
|
‘-- <plane>
------------------------------------+->
Querying:
Q ZDIStance
5.5 Creating and Positioning Joints

Joints elements constitute the physical means by which Sections are
connected together.
A Primary Joint (PJOI) is owned by a Primary Node. Its position is derived
from that of its owning Node.
A Secondary Joint (SJOI) is owned by a Secondary Node. Its position is
derived from that of its owning Node, and thus, in turn, from the position of the
Section which owns that Node.
A Compound Joint (PCOJ or SCOJ) is positioned relative to a Node, as for a
PJOI or an SJOI, but all settings which define its connections are associated
with subsidiary SubJoints owned by the Compound Joint (one SubJoint for
each connection).
© 2007 AVEVA Solutions Ltd 2 5:10

You will most often create and position Joints automatically using the STRING
command (see Creating and Connecting Sections Automatically). This section
describes how you can carry out these operations independently and how you
can modify the positions of Joints which have been created previously.
A Joint is a Catalogue Component, which is selected in the design by setting
its SPREF attribute to point to the required Component Specification.
5.5.1 Creating Primary Joints

Keywords:
NEW PJOINT
Description:
A new Primary Joint can only be created at PNOD level.
Example:
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.
5.5.2 Creating Secondary Joints

Keywords:
NEW SJOINT
Description:
A new Secondary Joint can only be created at SNOD level.
Example:
NEW SJOI /SJOINT1 Creates a new SJOI with a default position and
orientation. The default position places the
POSL (Position Line) of the Joint through the
owning SNOD.The default orientation directs the
CUTP (Cutting Plane Direction) of the Joint Up.
Command Syntax:
The standard element creation syntax is described in Part 1 of the DESIGN
Reference Manual.

5.5.3 Setting Joint Geometry via a Specification Reference
Keyw
ords:
SPRE
F
Description:
Both PJOIs and SJOIs must have their geometry defined by setting their
SPREF attributes to point to a valid Specification Component in a Project
Specification in the Catalogue DB.
Both types of Joint may point to the same Specification Component if required.
Example:
SPRE /10X10.BRAK90 (The .BRAK90 suffix in the Specification

Component name would normally indicate that
this represents a 90 degree bracket joint.)
Command Syntax:
>--- SPRef name --->
Querying:
Q SPRef
5.5.4 Positioning and Orientating Primary Joints

Keywords:
DELPOSITION OPDIRECTION BANGLE
Description:
The position and orientation of a Primary Joint are defined by the settings of
the following three attributes:
• The Delta Position (DELP) is the offset between the Joint’s Origin Plane
and the position of its owning Node (the NPOS of the PNOD), expressed
in the coordinate system which applies to the FRMW or SBFR. The
default is a zero offset, so that the Joint’s Origin Plane passes through
the owning Node.
• The Origin Plane Direction (OPDI) is the direction of the normal to the
plane through the Joint’s origin, as defined in the Catalogue
representation of the Joint.
• The Beta Angle (BANG) is the angle of rotation of the Joint about its
Origin Plane Direction, measured clockwise as viewed along that
direction. The default setting is zero, so that the Joint’s orientation is as
defined by its Catalogue representation.

BANG defines orientation about Z axis
OPDI defines orientation about

X,Y axes
Z
Y
X DZ
D
D DELP defines X,Y,Z offset relative to
PNode Y
PNode
X
NPOS defines X,Y,Z coords of PNode
Example:
DELP N4.5 Offsets the Joint by 4.5 (mm) in a northerly direction.
OPDI N Orientates the Joint so that the normal to its Origin Plane
points North.
BANG 180 otates the Joint about its current Origin Plane Direction by
180 degrees.
Command Syntax:
>--- DELPosition --- <bpos> --->
>--- OPDIrection --- <bdir> --->
>--- BANGle ---+--- value ---------------------------.
| |
‘--- <bdir> --- TOwards --- <bdir> ---+->
Querying:
Q DELPosition
Q OPDIrection
Q BANGle
5.5.5 Positioning and Orientating Secondary Joints

Keywords:
POSLINE (ZDISTANCE) BANGLE
Description:
The position and orientation of a Secondary Joint are defined with respect to its owning
Secondary Node. The position of this Node is separately defined with respect to its owning
Section, as described Creating and Positioning Secondary Nodes. The Joint’s position with
respect to the Section depends, therefore, upon the settings of two attributes:

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

• The Positioning Line (POSL) attribute of the SJOI itself. This defines the position of
the Joint in relation to the p-line system which has been set up for the owning
Section’s Profile within the Catalogue. The default POSL setting is NA (Neutral Axis),
so that the Joint’s Origin (more strictly, its JLIN) lies on the Section’s Neutral Axis at
the position specified by the ZDIST: that is, the Joint’s Origin is coincident with the
position of its owning SNOD.
The Beta Angle (BANG) specifies the angular rotation of the Joint about its Origin Plane
Direction. The default setting is zero, so that the Joint’s orientation is as defined by its
Catalogue representation.
TOS
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) p-line of the Section.
POSL BOS The Positioning Line of the Joint is coincident with the BOS
(Bottom of Steel) p-line of the Section.
Command Syntax:
>-- POSLine word -->
where word is usually one of the following:
NA (Neutral Axis)
TOS (Top of Steel)
BOS (Bottom of Steel)
>-- BANGle --+-- value ------------------.

| |
‘-- <bdir> TOwards <bdir> --+-->
Querying:
Q POSLine (At the SJOI)
Q ZDISTance (At the SNOD)

Q BANGle (At the SJOI)
5.6 Attributes of Connected Joints

The attributes and their settings described in Creating and Positioning Joints are applicable
to any Joints, whether or not they have been connected to attached Sections. In addition,
Joints which have been fully connected (that is, those which have both an Owning and an
Attached Section) have other relevant attributes set. These are described in this section.
5.6.1 Connection Reference

Keywords:
CREFerence
Description:
The Connection Reference attribute (CREF) of a Joint points to the identifier of the
Attached Section.
This attribute is set automatically when a Section is connected and you will not usually
need to set it specifically.
Examples:
CREF /BEAM1 START Sets Connection Reference to start of named Section.
CREF /BEAM2 END Sets Connection Reference to end of named Section.
CREF /COLUMN2 Sets Connection Reference to start of named Section.
CREF NULREF Disconnects the Joint.
Command Syntax:
>-- CREFerence --+-- <gid> --+-- STart* --.
| | | | |--- ENd ----|
| | | | ‘------------+
| |
‘--- NULref --------------+-->
where <gid> identifies the Section to be connected.

Querying:
Q CREFerence
5.6.2 Cutting Plane

Keywords:
CUTPlane

Description:
The position of a Joint which has an Attached Section is derived from the intersection of the
Attached Section’s Joining Line (JLIN) and the Joint’s Cutting Plane. The Cutting Plane
Direction, that is the direction of the normal to the Cutting Plane, is defined by the setting of
the CUTP attribute. The default direction is Up.
It is the position of the Joint’s Cutting Plane which defines the effective length of the Section
(but see also Cutback Allowance).
Examples:
CUTP N45D The normal to the Cutting Plane points in the specified
direction.
CUTP PERP The normal to the Cutting Plane is set perpendicular to the
Joint’s Origin Plane.
Command Syntax:
>-- CUTPlane --+-- <bdir> ---------.
| |
‘-- PERPendicular --+-->
Querying:
Q CUTP
5.6.3 Cutback Allowance

Keywords:
CUTBack
Description:
The derived length of an attached Section is, unless otherwise specified, the distance
between the Cutting Planes of the Joints at its two ends. The CUTB attribute allows you to
specify a length by which the Section should be shortened or extended to allow for any
local fitting geometry at the Joint’s attachment point (to allow for weld metal, packing pieces
etc.).
A positive value of CUTB shortens the derived length of a Section attached to the Joint; a
negative CUTB lengthens the attached Section. The default is a CUTB setting of zero.
Example:
CUTB 6 An attached section will have its derived length reduced by 6mm.
An attached section will have its derived length increased by
CUTB -6 6mm.
Command Syntax: >--

CUTBack <uval> -->

Querying:
Q CUTBack
5.7 Manually Connecting Sections

This section describes the commands which allow you to connect Sections and Joints
‘manually’; that is, without using the STRING command. The relevant Nodes and Joints
must have been created first, as described in the preceding sections of this chapter.
This section also explains how to disconnect and reconnect Sections and Joints, so that
you can modify existing interconnected structural designs.
5.7.1 Connecting Sections

Keywords:
CONNECT START END FREE RECALCULATE
Description:
When a Section is connected manually, the relevant End Cutting Plane of the Section
(DRNS/DRNE) is superimposed on the Cutting Plane (CUTP) of the connecting Joint. This
requires that the direction and through point of the Section have been correctly specified;
that is, that the correct end points are on an extension of the Section’s Neutral Axis.
In cases of misalignment, the Section’s position and orientation are given highest priority.
Thus, connecting a Section will not cause the Section to move or rotate. The Joint will be
aligned with the Section, if possible (but see the FREE option, below).
When the connection is made, the connection cross-references between the Section and
the Joint are set. That is, the JOIS/JOIE of the Section and the CREF of the Joint are
matched. Further, the relevant Connection Type attribute of the Section (CTYS or CTYE) is
set to point to the Attached Connection Type attribute (CTYA) of the Catalogue Joint.
The FREE option allows the existing joint position to remain fixed, and the POSS and/or
POSE of the section to be adjusted. This may cause the section to be displaced sideways,
or its direction to rotate. It may also cause SNODEs and FITTINGs along the section to be
displaced (even with RECALCULATE).
When the connection has been made, the corresponding Start or End Point of the Section
(POSS/POSE) is calculated from the intersection of the Z axis of the Section with the new
Cutting Plane which passes through the end of the Joint’s JLIN.
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 / Where the current element is a Joint. BEAM1
CONN START TO /PJOIN2 Connects the start of the current Section without moving
RECALC the positions of any secondary elements owned by the
Section.
Command Syntax:
At Section level:
>- CONnect -+- STart -.
| |
‘- ENd ---+- FREE -.
| |
‘--------+- TO <gid> -+- RECALCulate -.
| |
‘---------------+->
where <gid> identifies a Joint.
At Joint level:
>-- CONnect WITH --+-- STart --.
| |
‘-- ENd ----+-- OF <gid> -->
where <gid> identifies a Section.
5.7.2 Disconnecting Sections

Keywords:
DISCONNECT START END RECALCULATE
Description:
When a Section is disconnected, the connection cross-references (JOIS/JOIE - CREF) are
unset and the connection type cross-references (CTYS/CTYE ) are set to Nulref.
The position and length of the Section are not changed, but the Joint (if moved during the
connection operation) is returned to its default position.
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 DISCONNECT
command, so that the SNOD remained unmoved.
Examples:
DISCO START Disconnects the start of the current Section.
DISCO END Disconnects the end of the current Section.

DISCO Disconnects both the start and end of the current Section.
DISCO END RECALC Disconnects the end of the current Section, but retains the
positions of any secondary elements owned by the Section.
Command Syntax:
>-- DISConnect --+-- STart --.
| | |-- ENd
----| | |
‘-----------+-- RECALCulate --.
| |
‘-----------------+-->
5.7.3 Reconnecting Sections

Keywords:
RECONNECT START END RECALCULATE
Description:
The RECONNECT command would typically be used to reconnect a disconnected Section
in the following circumstances:
• Following the movement of a Joint: the attached Section is moved to the new Joint
position.
• Following the resetting of a cutback allowance at a Joint (see Cutback Allowance): the
length of the Section is modified to allow for the new cutback distance.
• Following the movement of a Primary Node which has a member Joint attached to an
existing Section.
In each case the RECONNECT command attempts to restore the consistency of the
connected model.
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.

econnects both the start and end of the current
RECON Section.
Command Syntax:
>-- RECOnnect --+-- STart --.
| | |-- ENd
----| | |
‘-----------+-- RECALCulate --.
| |
‘-----------------+-->
5.8 Repositioning Steelwork Elements

The concept of connectivity in structural steelwork influences the types of repositioning
operations which are allowed. Repositioning operations using the standard DESIGN
commands will also move items whose positions depend on those of the items being
directly moved.
5.8.1 Reversing Section Start and End Positions (‘Flipping’)

Keywords:
FLIP
Description:
The FLIP command mutually exchanges references to the Start and End of a steelwork
Section, effectively reversing its orientation. This is mainly of use for reorientating a Section
with a non-symmetrical profile if you have mistakenly strung it the wrong way round. It is
best used before any Secondary Nodes or Fittings are placed along the Section.
FLIP causes the settings of the following pairs of attributes to be exchanged:
• POSS and POSE (Start and End Positions)
• DRNS and DRNE (Start and End Plane Directions)
• JOIS and JOIE (Start and End Joint References)
Note: It is not intended that Sections with secondary connections be Flipped, although you
can do so if you fully understand the effects outlined below. These effects may not
give the results you had intended and may therefore require further design
modifications to be made:
The settings of the SREL and EREL (Start and End Release) attributes are not exchanged.
Since, however, the ends to which they refer have changed (since the original Start is now
the End, and vice versa), their effects will be reversed in the physical model.

• The Member List of the Flipped Section remains unchanged, so that any
crossreferences to member elements by list position remain correct. The ZDIST
attributes of any SNODs, FITTINGs, etc. remain the same, so that their positions are
now derived from the opposite end of the Section (the new Start end), thereby causing
these member elements to move.
• Any Connected items referenced via SJOIs will not move, since the positions of the
corresponding SJOIs will not move to the new SNOD positions until they are
Disconnected. If you wish to reverse a Section with existing secondary connections
you should, therefore, use the following sequence of operations:
• Disconnect the Section to be Flipped from all attached Sections.
• Flip the Section, thereby repositioning all of its SNODs and their associated SJOIs
(now disconnected) in the reversed locations.
• Reorientate all connected Sections so that they realign with the modified SJOI
locations along the Flipped Section (or reset the ZDIST attributes of the SNODs so
that they are repositioned where you want them).
• Reconnect the Flipped Section to all the attached Sections.
Example:
FLIP Reverses the Start and End attribute settings for the current element as
outlined in the preceding description.
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 For checking, in particular, all Start and End related settings (POSS/POSE,
DRNS/DRNE, etc).
Q DER POS For checking the derived positions of SNODs and/or SJOIs.
5.8.2 Moving Steelwork Elements

Note: The positioning/moving syntax described in Equipment and Primitives, also applies to
Structural steelwork elements.
Keywords:
MOVE ALONG BY AT
Description:
Movement relative to a fixed starting position (MOVE, ALONG, BY commands) is possible
for all structural elements which have a directly defined location in the 3D model; for
example, Frameworks, Subframeworks, Primary Joints and Nodes (but not Secondary

Joints and Nodes, whose positions are dependent on that of a Section), Routing Planes,
Panels, etc.
Absolute positioning (AT command) is possible only for Sections, Primary Nodes, Routing
Planes and Panels.
Examples:
MOVE ALONG E45N Moves Current Element in specified direction by specified

DISTANCE 500 distance.
BY N1000 E5000 U7000 Moves Current Element as specified relative to its current
position.
AT E2000 N2000 U1000 Moves the Current Element to the specified position. In the
case of a Section, POSS is set to this position; in the case
of a Primary Node, NPOS is set to this position.
5.8.3 Modifying Lengths of Sections

Keywords:
EXTEND START END PROPORTIONAL RECALCULATE
Description:
Once positioned, a Section may have its ends repositioned independently by using the
EXTEND command. This effectively lengthens or shortens the Section by a specified
amount and resets its POSS and/or POSE attributes accordingly. (You could, of course, set
POSS and/or POSE directly, as described in Start and End Positions, but this would need
prior calculation of the new positions needed to achieve the required length change.)
The increase or decrease in length may be specified as a direct measurement or as a
proportion of the current length of the Section.
The <plane> allows you to define the amount of extension required by intersecting the
neutral axis with a defined plane. The section is extended (or shortened) to meet the plane.
The RECALCULATE option causes the positions of elements which are members of the
modified Section to be recalculated so that they remain in the same positions after the
change. For example, the ZDIST defining the position of a Secondary Node would be
recalculated if the POSS (from which ZDIST is measured) were moved by the EXTEND
command, so that the SNOD remained unmoved.
Examples:
EXTEND END BY E1000 Move POSE by 1000mm Eastward.
EXTEND BY E1000 As above (defaults to END).
EXTEND START BY W1000 Move POSS by 1000mm Westward and recalculate the

RECALC positions of all member SNODs, FITTs etc. so that they

remain unmoved.
Examples:
EXTEND START BY U500 Move POSS by the given amounts.
E2000 S500
EXTEND END 1750 Move POSE so as to increase the Section’s length by
1750mm (default units).
EXTEND -1750 Move POSE (defaults to END) so as to decrease the
Section’s length by 1750mm (default units).
EXTEND START PROP 0.25 Move POSS so as to increase the Section’s current
length by 25%.
EXTEND PROP -0.2 Moves POSE (defaults to END) so as to decrease the
Section’s length by 20%.
EXTEND END PLANE E30N Moves POSE to meet the defined plane.
DIST 0.0
Command Syntax:
>-- EXTend --+- STart -.
| | |--
ENd* -| |
|
‘---------+- PROPortional - value -.
| | |- BY --- <axpos>
------|
| |
| | |- <plane>
-------------| | |
‘- <uval> --------------+- RECALCulate --.
| |
‘----------------+->
5.8.4 Reorientating Steelwork Elements

Keywords:
ROTATE BY ABOUT THROUGH AND
Description:
The method of rotating a Section about its Neutral Axis by setting its BANG attribute was
described in Orientation Angle. This section explains the use of the ROTATE command to
achieve a greater range of reorientating effects on Sections and on other steelwork
elements.
The command allows you to specify the rotation required in any of the following ways:

• As a specified angle of rotation about a default axis (similar in effect to setting the
BANG attribute). This default axis is the Neutral Axis for Sections, Joints and Fittings,
and the Z axis for other elements.
• As a specified angle of rotation about a given axis, the latter defined by its direction
and/or through point. If the direction and/or through point are omitted, the default

direction is that of the Neutral Axis or Z axis; the default through point is the Origin or
Start Position (depending on the type of element involved).
• By reference to the component’s axes or p-lines.
Examples:
ROTATE BY -45 Rotates by 45° about the element’s Neutral
Axis or Z axis (anticlockwise when looking
from Start to End or in the +Z direction,
since the rotation is specified as a negative
angle).
ROTATE BY 45 ABOUT E Rotates by 45° about the 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 Rotates element until its TOS p-line points in
BOS OF /SCTN1 LEAV DIR the direction of the BOS p-line of / SCTN1 in
WRT /STRU1 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> -|
| |
‘------------------+-->
Rotation to pass through a given point:
>- ROTate THRough - <bpos> -+- ABOut -+- <plin> -.
| | |
| ‘- <bdir> -+- BY -+- <uval> -----------------------.
| | | | | | ‘- <bdir> - TOwards - <bdir> ----|
| | | | ‘- AND -+- <plin> -. |
| | | | | ‘- <bdir> -+- IS - <bdir> ------|
| | |- BY -+- <uval> --------------------. |

| | | | | ‘- <bdir> - TOwards - <bdir> -+- ABOut -+- <plin> -. |

| | | | | | | ‘- <bdir>- +--|
| | | | ‘-----------------------|
| | ‘- AND -+- <plin> -. |
| | |
‘- <bdir> -+- IS - <bdir> -+- ABOut -+- <plin> -. |
| | | | | ‘- <bdir>- +----|
| |
‘-------------------------+->
Rotation by a specified amount:

>- ROTate BY - -+- <uval> --------------------.
| |
‘- <bdir> - TOwards - <bdir> -+- ABOut -+- <plin> -.
|| |
| ‘- <bdir> -+- THRough - <bpos> ---.
| | | | ‘----------------------|
| | |- THRough - <bpos> -+- ABOut -+- <plin>
-. |
| | | | | | | ‘- <bdir> -+-|
| | | | ‘----------------------|
| |
‘-------------------------------------------+->
Rotation to give a specified orientation:

>- ROTate AND -+- <plin> -.
| |
‘- <bdir> -+- IS - <bdir> -+- ABOut -+- <plin> -.
| | |
| ‘- <bdir> -+- THRough - <bpos> ----.
| | | | ‘-----------------------|
| | |- THRough - <bpos> -+- ABOut -+- <plin>
-. |
| | | | | | | ‘- <bdir> -+--|
| | | | ‘-----------------------|
| |
‘--------------------------------------------+-->
Note: In each of the preceding diagrams <plin> identifies a specific p-line.
5.9 Positioning and Orientating Using P-lines

P-lines in a 3D structure represent lines, derived from points defined in the Catalogue for
corresponding Profiles or Joints, which have associated direction vectors in the X-Y plane.
A typical configuration for an ‘extruded’ I-section component is illustrated in Figure 5:1.:
Typical P-lines and Axes for a Section; typical p-lines associated with a wider range of
profiles are illustrated in the guide Structural Design Using PDMS.
A p-line can provide a very convenient reference line or axis within an element’s 3D
geometry (as derived in the design model) for positioning or orientating the element itself,
or for defining some other geometry relative to the element. Positions may be defined along
the length of a p-line; directions may be defined in terms of a p-line’s coordinate axes (the
pline direction being, by default, along its +Z axis).
Some examples have already been introduced in the earlier sections of this chapter. This
section further illustrates the possible uses of such techniques.
Z Z
PLIN NA YX
POSE

POSS

YX
SCTN axesSITE axes
ZY
TOS axes
X
X
PLIN TOSBOS axes
Z
PLIN BOS
Figure 5:1. Typical P-lines and Axes for a Section
5.9.1 Identifying P-lines

Keywords:
PPLINE
IDPLINE
Description:
A p-line may be identified in either of the following ways:
• By reference to its PKEY attribute (see the VANTAGE PDMS PARAGON Reference
Manual for details of how this is set) and its owning element (if this is not the current
element).
• By picking it on the display using the cursor.
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-line’s PKEY attribute, as defined in the Catalogue; for
example: TOS (Top of Steel), BOS (Bottom of Steel), NA (Neutral Axis), NF (Near Face),
FF (Far Face), etc.
5.9.2 Positioning by Using P-lines

Keywords:
PPLINE START END OFFSET
Description:
A position relative to a p-line may be specified in any of the following ways:
• As a specific distance along the p-line from its start (typically the POSS of a Section)
or its end (typically POSE).
• As a proportional distance along the p-line, expressed as a fraction of its length
(typically the distance from POSS to POSE).
• As one of its extremities; that is, at the p-line’s start or end.
• As an offset, expressed as the distance between two specified p-lines.
Examples:
POSITION PPLINE Calculated position is on the BOS p-line, 500mm from
BOS 500 its start (by default); for setting a variable or for
querying.
POS PPLIN TOS 1000 Calculated position is on the TOS p-line, 1000mm from
FROM END its end.
POS AT PPLIN NA OF Calculated position is on the Neutral Axis of /SCTN2,
/SCTN2 PROP .25 25% along its length as measured from its start (by
default).
POS AT PPLIN TOS OF Position is defined as the end of the TOS p-line of /
/BEAM1 END BEAM1 (probably, but not necessarily, the POSE setting
for /BEAM1).
BY PPLIN TOS OFFSET Moves the current element (Section or Joint) by the
FROM PPLIN BOS offset distance between its TOS and BOS p-lines.
BY PPLIN BOS OFFSET Moves the same distance as the preceding example, but
FROM PPLIN TOS in the opposite direction.
BY PPLIN TOS -OFFSET The same effect as the preceding example.
FROM PPLIN BOS
Command Syntax:
Note: The following syntax describes only the p-line referencing options for defining a
position. These are in addition to the positioning/moving syntax described in
Equipment and Primitives, which also apply to Structural steelwork elements.

Defining a specific position:

>- <plin> -+- <uval> -------------.
| |
|- PROPortion - value -+----------------------.
| | | | ‘- FROm -. |
| | |
‘-------------------------------+- STart* -. |
| | |
‘- ENd ----+--+->
Defining a distance as the offset between two p-lines:
>-- <plin> --+-- sign --.
| |
‘----------+-- OFFSet FROm <plin> -->
where <plin>, which identifies a specific p-line, is defined in Identifying P-lines.
Querying:
Q <plin> --+-- <uval> --------------.
| |
|-- PROPortion - value --+--------------------------.
| | | | ‘-- FROm --. |
| | |
‘-----------------------------------+-- STart* --. |
| | |
‘-- ENd -----+--+-->
Q <plin> -- OFFSet --+-- FROm -- <plin> --.
| |
‘--------------------+-->
Querying Examples:
Q PPLIN TOS END Position of end of p-line.
Q PPLIN BOS PROP 0.3 Position of point 30% of distance along BOS from
start (by default) towards end.
Q PPLIN NA PROP -1.5 Position of point which is 1.5 times length of Neutral
FROM END Axis away from end of p-line in direction away from
start.
Q PPLIN TOS OFFS FROM Offset distance between TOS and BOS.
PPLIN BOS
Q PPLIN TOS OFFS Offset distance between TOS and Neutral Axis (by
default).
5.9.3 Orientating by Using P-lines
Keywords:
PPLINE DIRECTION X Y Z LEAVE
Description:
You can orientate a structural element by referring its axes to the directions of one or more
p-lines. By default, references will be taken from the Z (or LEAVE) direction.

Example:
ORI Y IS PPLIN Orientates the current element such that its Y axis points in TOS OF
/SCTN1 X the X direction of the TOS p-line of /SCTN1 and its Z axis
DIR AND Z IS U points Up. If, for example, the X direction of the TOS p-line of /
SCTN1 points East, then this command line is equivalent to
ORI Y IS E AND Z IS U.
Command Syntax:
>-- <plin> --+-- X ------.
| | |-- Y
------|
| | |-- Z
------|
| | |--
LEAve --|
| |
‘-----------+-- DIRection -->
Querying:
Q <plin> --+-- X ------.
| | |-- Y
------|
| | |-- Z
------|
| | |-- LEAve
--|
| |
‘-----------+-- DIRection -->
5.10 Creating and Connecting Panels
5.10.1 Creating a Panel

A Panel (PANE) element represents any sheet material used to clad a structural model.
The geometry of a Panel is defined by a subsidiary Panel Loop (PLOO) element. The 2D
shape of the Panel Loop is defined by linking together a set of Panel Vertex (PAVE)
elements, each of which has a specific position in the Panel’s coordinate system. The
polygon thus formed defines the shape of the Panel in the same way that a Profile defines
the crosssectional area of a Section. The Height (HEIG) attribute of the PLOO defines the
distance through which this 2D shape is extruded to form the 3D Panel; that is, it defines
the Panel thickness, thus:

HEIG
of PLOO = Panel Vertex (PAVE ) = Panel Loop (PLOO)
Each PAVE can have an optional fillet radius which defines a circular arc which bulges into
(negative radius) or out of (positive radius) the PLOO area. The default fillet radius of zero
denotes a point.
To define a new Panel, you must, therefore, first create a PANE element (using NEW
PANE etc.), then create a PLOO below it in the hierarchy, and then create and position as
many member PAVEs as necessary to define the shape of the PLOO and thus the PANE.
(The Z co-ordinates of the PAVEs are ignored; they are constrained to lie in the plane of
the PLOO.)
5.10.2 Splitting a Panel

Keywords:
SPLIT ON
Description:
You can split a Panel along its line of intersection with a given plane or Section. The Panel
is split into two or more new Panels which have same owner as the original one. More than
one new Panel may result if the original one has re-entrant vertices.
The vertices of the original Panel are moved to the new Panel(s) as appropriate and new
vertices are created where the intersection line crosses the edges of the original Panel.
Examples:
SPLIT PLANE N THRO Splits current panel along its line of intersection with the
N1000 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> ----------------+-->

5.10.3 Connecting Panels using Linear Joints

Linear joints are used to connect structural items along edges or faces. They effectively
have linear (2D) connectivity, whereas Primary and Secondary Joints have only point (1D)
connectivity (even though they have 3D geometry).
A Panel Linear Joint (PALJ), owned by a PANE, FRMW or SBFR, is used to connect two
Panels together. The start and end of the PALJ are defined by two Panel Vertex (PAVE)
points. Logical connections from the attached Panel are made by setting Master Vertex
(MVERT) attributes of two of the Panel’s PAVEs to point to the corresponding PAVEs on
the linear joint, thus:
*
PANE1
MVERT attribute of PAVE
* points to PAVE of PALJ
PALJ
*
PANE2 = PALJ (owned by PANE 1)
* = PAVE (PLOO of PANE 1)
= PAVE (owned by PALJ )
In this example, PANE1 is the Owning Panel and PANE2 is the Attached Panel.
A Section Linear Joint (SELJ), owned by a Section, is used to connect a Panel to a
Section. The start and end of the SELJ are defined by two Section Vertex (SEVE) points.
Logical connections from the attached Panel are made by setting Master Vertex (MVERT)
attributes of two of the Panel’s PAVEs to point to the corresponding SEVE’s on the linear
joint, thus:

Structural
* Design Using Catalogue Components
*
PANE
SELJ
*
SCTN
*
MVERT attribute of PAVE
points to SEVE of SELJ
= SELJ (owned by SCTN)

= PAVE (PLOO of PANE) = SEVE
(owned by SELJ)
Keywords:
LINK UNLINK
Description:
The LINK command lets you set up the necessary connection references for:
• a vertex to another vertex
• an edge to an edge (an edge is the line between a pair of consecutive vertices)
• a panel to a joint
• a panel to a vertex
• a panel to an edge
In each case, the vertices of the item being linked are defined as slave vertices, while the
vertices of the item linked to (which define the properties at the connection point) are
defined as master vertices.
When you link a panel, any new panel vertices needed will be created automatically to
correspond with the master vertices of the item connected to. You can specify the position
and direction of creation of the new vertices in the Panel Loop’s vertex sequence as part of
the command. If the panel has no PLOOP, one will be created automatically.
UNLINK unsets the connection cross-references created by a LINK command.
Examples:
LINK VERT CE TO /PAVE2 Links current vertex (slave) to vertex /PAVE2 (master).
LINK PANEL /PANE3 TO Links panel /PANE3 to edge between /PAVE5 and / EDGE
/PAVE5 /PAVE6 PAVE6 and positions any new vertices needed after / AFTER
/PAVE2 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.
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 ---------------------+-->
Querying:
Q LINKS Queries connection references between vertices
5.11 Fittings, Hangers and Equipment Load Points

5.11.1 Fittings and Panel Fittings
A Fitting (FITT) element allows you to indicate a connected implied load, such as a pipe
hanger attachment, or an ancillary item related to, but not an inherent part of, the structure,
such as a web stiffener or a flange plate.
A Fitting is owned by a Section (SCTN) and is positioned along the Neutral Axis of the
SCTN at a point defined by the ZDIST attribute (in the same way as for a SNOD). The
Fitting may be geometrically modelled in the Catalogue, and selected from the Catalogue,
in a similar way to a Joint, as described in Creating and Positioning Joints.
A Panel Fitting (PFIT) element serves a similar function to a FITT, but is owned by a Panel
and positioned relative to the Panel’s origin. A Cofitting (COFI) element is used where a
fitting spans the junction betwen two or more Panels. In the latter case, one of the Panels
owns a PFIT while the others each own a COFI. Each COFI has its Panel Fitting
Reference (PFRE) attribute set to point to the associated PFIT; the PFIT has its Cofitting
Reference Array (CFRA) attribute set to point to the COFIs.
5.11.2 Structure-to-Pipework Connections

Piping models may be linked logically to the Structural model by means of cross-references
between the Connection Reference (CREF) attribute of a Fitting on the Structure and the
Head or Tail Reference (HREF/TREF) of a Hanger on the Pipework. A Fitting may be
regarded, therefore, as the Structural equivalent of an Attachment Point (ATTA) in
Pipework design.
For connection type compatibility, the Connection Type attribute (CTYA) of the Fitting must
match the Connection Type (HCON/TCON) of the Hanger.
5.11.3 Structure-to-Equipment Connections

Equipment models may be linked logically to the Structural model by means of
crossreferences between the Connection Reference (CREF) attribute of a Fitting on the
Structure and the Connection Reference (CREF) of a Load Point (LOAP) element owned
by the Equipment.
A Load Point has a position within the Equipment model, but no size or orientation. It
behaves in this respect like a Node in the Structural model. If an Equipment is moved, any
member Load Points which point to Fittings in a Structure will not move, their positions
being constrained by the attached Structure.

5.12 DESIGN, Owning and Attached Parameters
5.12.1 Setting DESIGN Parameters

Keywords:
DESPARAMETERS
Description:
DESIGN parameters (DESP) are array-type attributes of any element which has a
Specification Reference (Sections, Joints, Fittings etc.), each of which may store up to 100
real values. They may be used to transfer design data to a corresponding Catalogue
component, or to a component’s attached or owning design element.
As an example, this enables one or more dimensions of a Joint to be derived from the
dimensions of the Section(s) to which it is attached, rather than from preset dimensions
defined for it in the Catalogue.
A DESP is referenced in the design by its numbered position in the array. Its value must be
set before the corresponding component is selected from the Catalogue, so that the
required setting is available within the design.
Example:
DESP 2.5 7 Sets first two design parameters to 2.5 and 7

respectively.
DESP N3 -5.5 Sets third design parameter to -5.5.
DESP N3 POSS OF /SCTN1 Sets design parameters 3, 4 and 5 to X,Y,Z

coordinates (respectively) of POSS of element /
SCTN1.
Note: In the last example, a range of three design parameters, needed to hold the
coordinates of the defined point, was set automatically, starting with the specified
third parameter.
Command Syntax:
Setting parameters in default order in the array, starting at parameter number 1:
.--------------<------------.
/ |
>-- DESParameters --+-- <expres> -----------------|
| | |-- <uval>
-------------------|
| | |-- READ
---------------------|
| |
‘-- word --+-- OF -- <gid> --|
| |
‘------------------+-->

Setting individually specified parameters within the array:

.--------------------
<----------------------. / |
>- DESParameters -*- Number - integer -+- <expres> ------------|
| | |- <uval>
--------------|
| | |- READ
----------------|
| |
‘- word -+- OF - <gid> -|
| |
‘--------------+->
Querying:
.--------------<----------------.
/ |
Q --*-- DESParameters - integer -----+--->
Querying Examples:
Q DESP 1 DESP 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.
5.12.2 Setting Owning and Attached Parameters

Owning and attached parameters (OPAR and APAR, respectively) are real-array attributes
of Joints. They are set in the Catalogue, and allow the Joint to derive data (usually
dimensions) from its owning or attached Section(s) when it is introduced into the design.
See the VANTAGE PDMS PARAGON Reference Manual for details about the setting of
these arrays.
As with the design parameters described in Setting DESIGN Parameters, an OPAR or
APAR is referenced in the design by means of its numbered position in the corresponding
array.
5.13 Representing Curved Beams and Walls

5.13.1 Overview
Curved structural items are represented by Generic Section (GENSEC) elements, the
geometry of which is defined by sweeping a 2D catalogue profile along a path. This path is
represented by a Spine element, owned by the GENSEC, whose route is specified in terms
of a sequence of member Spine Points (POINSP) and, optionally, Curves. For example:

There are six types of Curve, defined by setting the CURTYP (Curve Type) attribute, which
govern the way in which the shape of the curve is specified.
The options are:
LINE
A straight line (this is the default)
RADI
A circular arc, defined by a radius and a conditioning point.
THRU
An arc passing through a specified through-point position.
BULG
An arc defined by a bulge factor and a conditioning point.
FILL
A fillet arc and two adjacent straights, defined by a radius and a pole position.
CENT
A fillet arc and two adjacent straights, defined by a circle centre point, a radius and a
conditioning point.
A Spine with only two POINSP members behaves in a similar way to a linear Section
(SCTN). The first POINSP owned by the Spine defines its start position (equivalent to the
POSS of the Section); the last POINSP defines its end position (equivalent to the POSE of
the Section).
Items connected to a GENSEC are positioned and orientated relative to a set of p-lines
which follow the same path as that defined by the GENSEC’s Spine; that is, the p-lines may
be curved. These p-lines are referenced by attached items via Justification Line Datum
(JLDATUM) and P-line Datum (PLDATUM) elements, which define the frames of
reference to be used for positioning and orientating the attached items relative to the parent
GENSEC.
Fittings and joints are represented by generic Fixing (FIXING) elements, the geometry of
which is defined by reference to catalogue items. Fixings can own other Fixings, so that
although they behave somewhat like the more restrictive Fitting and Joint elements, they
are more versatile for representing compound fittings and joints.
5.13.2 Defining a Generic Section

Keywords:

GENSEC SPINE POINSP CURVE
Description:
Each GENSEC, representing a linear or curved beam or wall, must own a Spine defining its
shape. The Spine must own at least two Spine Points, defining its start and end positions.
It can also own intermediate Spine Points and Curves to give a non-linear configuration.
Example:
NEW GENSEC Creates GENSEC with no defined geometry.
SPREF /203X203X55KG.UB Sets SpecRef of GENSEC to point to catalogue profile.

GENSEC now has defined cross-section, but no
geometry defining its path.
NEW SPINE Creates Spine with no defined path.
Example:
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 The attributes of this curve determine the shape of (Created between
POINSPs) the Spine path between the adjacent POINSPs. (See More About Curve
Types.)
5.13.3 More About Curve Types

The ways in which the various types of Curve are specified are as follows:
• CURTYP = LINE
Specifies a straight line between the adjacent POINSPs. This is the default if curved
geometry is not defined between two POINSP elements.
• CURTYP = RADI
Specifies a single circular arc between adjacent POINSP elements. The arc is defined
by the RADI (radius) and CPOS (conditioning point) attributes. The conditioning point
and the preceding and following points define the plane of the arc. The choice of minor
or major arc is governed by the arc which approaches closest to the conditioning
point. If RADS = false, the specified radius is ignored and the minimum radius is
calculated such that the curve is a semicircle between the adjacent POINSPs.
• CURTYP = THRU
Specifies a single circular arc. The arc is defined by the POS attribute, which is
interpreted as a through-point on the curve. The through-point and the preceding and
following points define the plane of the arc.
• CURTYP = BULG
Specifies a single circular arc. The arc is defined by the BULG (bulge factor) and
CPOS (conditioning point) attributes. The conditioning point and the preceding and
following points define the plane of the arc. The choice of minor or major arc is
governed by the size of the bulge factor. The sign of the bulge factor determines

whether the arc curves towards the conditioning point (positive bulge factor) or away
from the conditioning point (negative bulge factor).
• CURTYP = FILL
Specifies a combination of an arc and up to two straights. The curve is defined by the
RADI (radius) and POS attributes, where the POS setting is interpreted as the pole
point of the arc (the intersection of the two end tangents). The pole point and the
preceding and following points define the plane of the arc. If RADS = false, the
specified radius is ignored and the maximum radius that will fit into the pole is
calculated; an endpoint triangle ensures that the fillet terminates on at least one of the
end points.
• CURTYP = CENT
Specifies a combination of an arc and up to two straights. The curve is defined by the
RADI (radius), CPOS (conditioning point) and POS attributes, where the POS setting
is interpreted as the circle centre point. The centre point and the preceding and
following points define the plane of the arc. The choice of minor or major arc is
governed by the arc which approaches closest to the conditioning point; the
conditioning point need not lie in the plane of the arc. If RADS = false, the specified
radius is ignored and the maximum radius is calculated to ensure that the nearest
POINSP to the circle lies on the circle; the arc terminates on this point.
Note: Displayed GENSECs treat each segment of the Spine as a separate extrusion. At the
vertices between segments, i.e. at the POINSP positions, these extrusions merge
together if there is a tangent continuity. If there is a tangent discontinuity, the
extrusions are mitred along a plane normal to the mean of the two tangent vectors at
the POINSP position.
5.13.4 How P-lines Are Used For Generic Sections

P-lines defined in the Pointset of the Section Profile (as referenced by the SpecRef) follow
the path defined by the GENSEC’s Spine. This means that, for a curved GENSEC, the p-
line directions are not constant over their lengths. This must be taken into consideration
when using them as datums referenced by attached items.
The command syntax used for referencing p-lines for SCTNs, as detailed in Positioning
and Orientating Using P-lines, is extended when applied to GENSECS. The additional
command options available are summarised here.
Positions Derived From P-lines (see Positioning by Using P-lines):

The distance value along the p-line may be preceded by the keyword DISTANCE. For
example:
PPLINE TOS DISTANCE distance FROM END ...
The position along the p-line may be measured from the plane normal to the end of the
GENSEC, from the cutback plane, or from the joint end preparation cutback. For example:
PPLINE TOS OF /BEAM1 NORMAL ...
PPLINE TOS OF /BEAM1 NOCUTBACK ...
PPLINE TOS OF /BEAM1 CUTBACK ...
It is possible to define a proportional and an absolute distance position at the same time.
For example:
PPLINE TOS PROPORTION value DISTANCE distance ...
Positions may be measured along the actual p-line specified, or along the Spine and then
projected onto the p-line. For example:

PPLINE TOS distance VIA SPINE FROM END ...

PPLINE TOS PROPORTION value VIA PLINE ...
The element specified by the OF keyword may be a POINSP or a CURVE. This redefines
the element to be the GENSEC owning the POINSP or CURVE, rather than the current
element or an element defined with the p-line choice. This sets:
• the direction along which DISTANCE and PROPORTION are to be measured;
• in the case of a CURVE, the POINSP to be used as the origin from which DISTANCE
and PROPORTION are measured;
• the segment of the GENSEC to which PROPORTION is applied as:
• the named CURVE,
• the segment following the POINSP (from START), or
• the segment preceding the POINSP (from END).
For example:
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 Orientating by Using P-lines):
Directions and offsets derived from p-lines can have a derived position inserted after the
direction/offset option and before the OF option. This lets you specify the position along the
p-line at which the direction/offset is to be calculated. For example:
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.
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 p-line.)
The following expressions use keywords analogous to the OFFSET option between the
pline specification and the subsequent positioning command:
PPLINE pline_name PLDIST positioning_command
PPLINE pline_name PLKEY positioning_command
PPLINE pline_name SEGMENT positioning_command
PPLINE pline_name ONPLINE positioning_command
PPLINE...SEGMENT and PPLINE...ONPLINE return references to the segment and p-line,
respectively, on which the point is specified. PPLINE...PLDIST returns the distance 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.13.5 Positioning Items Relative to Generic Sections
A GENSEC cannot own Fixings directly, but only via member Justification Line Datum and
P-line Datum elements which together define the p-line configurations to be used as
references for positioning and orientating the Fixings.
The Justification Line Datum (JLDATUM) element defines a frame of reference for its
members based on the p-line system of its owning GENSEC. Each JLDATUM can own a
set of P-line Datum (PLDATUM) elements, each of which defines a frame of reference for
its members based on a nominated p-line of its owning JLDATUM. By manipulating a
JLDATUM, all of its member PLDATUMs can be manipulated as a group, together with any
Fixings owned by the latter.
Note: The JLDATUM and PLDATUM elements together serve similar functions to the
Secondary Nodes (SNOD) used for positioning Fittings (FITT), Compound Fittings
(CMFI), Secondary Joints (SJOI) and Compound Secondary Joints (SCOJ) relative
to Sections (SCTN). They also provide similar functions to those used for positioning
Panel Fittings (PFIT) and Compound Panel Fittings (CMPF), depending on the
GENSEC configuration (remember that a GENSEC can model a wide range of
geometries, including structural sections and panels).
Specifying Position:
The position of a JLDATUM origin may be queried via a pseudo-attribute (Q POS), but this
cannot be set explicitly. The position is derived from the following attribute settings:
• TPREF and HPREF specify, by reference to POINSPs of the parent GENSEC (more
strictly, its Spine), the start and end points, respect-ively, between which interpolated
positions will be calculated. If both are unset, TPREF defaults to start of the GENSEC
and HPREF defaults to the end of the GENSEC. If only one is set, the other defaults to
the next POINSP in the appropriate direction.
• PKDI specifies a point, as a proportion of the distance from TPREF to HPREF, from
which ZDIST is to be measured. The default setting is 0, giving a position at TPREF. If
PKDI is less than 0 or greater than 1, the position will be on the preceding or following
segment, respectively, of the Spine.
• ZDIST specifies the distance of the JLDATUM origin from the PKDI point, as
measured along the Justification Line (JUSL) or NA p-line of the GENSEC.

TPREF HPREF
ZDIST = Spine of GENSEC

= POINSP
PKDI=0 PKDI=0.5 PKDI=1 = JLDATUM Position
for PKDI=0.5
Specifying Orientation:
The orientation of a JLDATUM may be queried via a pseudo-attribute (Q ORI), but this
cannot be set explicitly. The orientation is such that its Z axis is in the direction of the Spine
(i.e. the NA p-line) at the POS. The Y axis is in the Y direction (YDIR) of the Spine,
modified by the Beta Angle (BANG) setting, at the POS.
5.13.6 Generic Fixings Representing Joints and Fittings
A Fixing can represent any type of joint or fitting attached to a Generic Section. It can own
other Fixings, so that it can also represent compound joints and fittings. Its geometry is
defined by a reference to a parameterised Catalogue item in the usual way.
The position and orientation of a Fixing attached (indirectly) to a GENSEC are specified by
reference to the coordinate systems of the parent PLDATUM and JLDATUM. These can be
set relative to any POINSP under the GENSEC, including a POINSP which has been
specially inserted for this purpose if necessary, as summarised in Positioning Items
Relative to Generic Sections. The default position and orientation of the Fixing relative to its
owning PLDATUM are specified by its POS and ORI attributes, respectively.
Fixings Representing Joints:

The detailed position of a Fixing whose SPREF attribute points to a Catalogue Joint is
specified using the Joining Line attributes of the owning and attached sections: JLNS (start)
and JLNE (end). The JNLS/JNLE are related to the origin and orientation of the joint; if the
attached GENSEC is curved, these p-lines are taken as parallel to the attached end of the
GENSEC. When connected, the JLNS/JLNE line of the attached section intersects with the
JLIN line of the Fixing on the Joint Origin Plane.
A GENSEC attached to a joint at one end will have either its JOIS (start) or JOIE (end)
attribute set to reference the Fixing; conversely, the CREF (Connection Reference)
attribute of the Fixing will reference the attached GENSEC. This two-way cross-reference is
used when either the Fixing or the GENSEC is modified, or when a CONNECT command is
used.
5.14 Representing Building Components

The elements used to represent structural steelwork designs can also be used to represent
the components involved in building design; for example, walls, floors, floor screeds, doors,
windows, etc. It is recommended that such elements are created by using the DESIGN
Walls & Floors applicationware rather than from the command line, since this will ensure
that all relevant attributes are set in a consistent way, but the options are summarised in
this section for reference purposes.

5.14.1 Using Element Soft Types

To distinguish the elements used for building representation rather than for other types of
structural design, element soft types are used. These are elements which have the same
attributes as standard (hard type) elements, but which have different names to identify their
functions.
The soft types used for building design are as follows:
Compound Wall (CWALL):

a soft type of Subframework (SBFR), used to hold one or more wall components
representing, say, one storey of a multi-storey building.
Compound Floor (CFLOOR):

a soft type of Subframework (SBFR), used to hold one or more floor components
Compound Screed (CSCREED):
a soft type of Subframework (SBFR), used to hold one or more screed components
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
userdefined 2D shape through a specified distance (equivalent to the Panel's height/
thickness). This could be used, for example, to represent a column, where the 2D
shape of the column's cross-section is extruded vertically to the required column
height.
Wall and Floor Fittings, such as doors, windows, manholes etc., can be represented by
Compound Fittings (CMPF), Sub-Compound Fittings (SBFI), Fittings (FITT), Panel
Fittings (PFIT) or Fixings (FIXI) in the usual way.
5.14.2 Controlling Edge Representation in DRAFT

When you plot walls and floors in DRAFT, you may want to remove the lines which
represent common edges between such elements (referred to as 'unioning' the elements)
to give a more realistic appearance. The elements used to represent buildings have an
attribute specifically for this purpose: the DRAFT Union (DUNION) attribute.
The elements to which this attribute applies are: Zone, Structure, Framework,
Subframework, Compound Wall, Compound Floor and Compound Screed.
In each case, the DUNION attribute can take one of the following values:
DUNION=0 Common edges always shown
All common edges between adjoining elements will be drawn in DRAFT.

DUNION=1 Common edges not shown between members

Common edges between adjoining elements will be drawn in DRAFT unless a pair of
such elements are both members of a common parent, in which case the edge lines
will be removed.
DUNION=2 Common edges not shown between members and peers
Common edges between adjoining elements will be drawn in DRAFT unless a pair of
such elements are either both members of a common owner or are at the same
hierarchic level with a common parent, in which cases the edge lines will be
removed.
In the simplest cases, the effects are as shown in the following diagram:
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.

Design Templates
6 Design Templates
This chapter explains the concept of Design Templates, which let you create and store
standard design configurations for subsequent use, and the Design Datasets which hold
the parameterised data settings for such templates.
6.1 Concepts
A design template is a set of design primitives, panels and nozzles that may be grouped
together and then referenced from within another part of the Design database as though it
were a single item. In many ways, a design template behaves in a similar way to a
catalogue component, except that the template items are stored in a special area of the
Design DB, rather than in a separate Catalogue DB, and they can use the more powerful
sets of primitives and parameterisation facilities available from within DESIGN. Unlike a
catalogue component, a design template can be split down into its constituent parts for
selective reporting, dimensioning, MTO, etc.
A design template is used in a design by creating an instance of the template. When a

design template is instanced, the template contents are copied into the Design hierarchy
and a reference is set to the original template definition. At this release version, a design
template may only be copied under a Panel Fitting, a Section Fitting or a Primary Joint. A
design element cannot own more than one design template, nor can one design template
own another template.
Design templates may be parameterised to allow a single template definition to be used in
different circumstances. The parameterisation facilities use Design Datasets to store
named parameters, which may then be referenced in geometric and p-point definitions. The
value assigned to a parameter can be defined in terms of a rule by using any of the
standard PDMS expression syntax.
Note: The definition of Design Templates is likely to be done by the person who organises
PDMS Catalogue and Specification data in a company, while the use of Design
Templates for building up a design model will be carried out by a plant designer.
Therefore, although both functions are carried out in DESIGN, this chapter is
relevant to two different types of PDMS user.
6.2 Design Template Hierarchy

Design Template (TMPL) elements are usually stored in a separate Design DB under an
administrative Template World (TPWL), which is itself divided into administrative
Template Areas (TMAR).
Each TMPL is initially created as a copy of an existing set of design elements which have
been created in a part of the usual hierarchy below a SITE. The TMPL may then be
modified by the addition of positive and/or negative primitives, negative extrusions, etc. For
example, a very simple template, consisting of a positive box and a negative box, could be
created thus:

Design Templates
World (/*)
SITE TPWL
ZONE TMAR
EQUI TMPL
BOX BOX
Copy
NBOX NBOX
When this template is instanced in a design model, say under a panel fitting, its constituent
elements are copied back and all parameterisation rules are executed so that the attributes
of the copy are set to suit the local DESIGN requirements, thus:
TPWL PANE
TMAR PFIT PLOO

TMPL TMPL PAVEs
BOX Copy and BOX

NBOX
Execute Rules
NBOX
All attributes of the copy are locked to prevent unintentional changes.
6.3 Application Data Areas

Application Data Areas and Elements are a new form of definition in the Design Database
that are provided to assist Appware Applications to store model parts for copying and
propagation within a design. They have some similarities with Templates, but are more
general in content, and more restrictive in behaviour.
Application Data Areas and Elements are expected to be used for Piping Assemblies and
Platforms Stairs and Ladders (PSL) applications and perhaps others. They are also
expected to be used for storing Multi Discipline Supports (MDS) definitions to make the
management of these more robust.
The Elements available are administrative elements allowing applications to organise data
storage areas of design objects that are not part of the design itself, but supplementary
objects used to create and maintain the model. They will not be accessed (unless
specifically instructed to do so) when performing model queries such as clashing, mass
properties, collections etc. They are similar to catalogue definitions and to Template
definitions in particular.
The top level element in the DESIGN database is Design WORL. This owns a top level
application data element
APPLDWorld - Application Data World

Design Templates
APPLDW can own

APPDAReas - Application Data Areas
DDAR - Design Data Set Areas
DDARs are existing element types. They own Design Data Sets (DDSE) for storage of data
used by Template expressions and Rules, and by Appware. They can be used for Appware
to store data, rules, etc for use in data driven instancing of assemblies.
APPDAR can own:

APPLDAta - Application Data. This is logically similar to a Template Definition.
APPLDA is a new element type. It can own

ZONE
DDSE - Design Dataset
DPSE - Design Pointset ROOM
The following diagram illustrates the relative positions of these elements in the DESIGN
database hierarchy:

Design Templates
6.3.1 Functional Queries

Everything under the Application Data World (APPLDWorld) is treated in the same way that
hierarchies under TMWL (Template Worlds) are. In particular, Clash checking on
command, spatial mapping and auto clashing will be isolated from normal design data
except when specifically queried within the APPLDWorld.
6.3.2 Naming
Names in the APPLDWorld are in the same scope as the normal project model and so
duplicate names will clash. This is not likely to be an issue as it is expected that application
data will be unnamed. It would become an issue if sections of 'real' model data are copied
or included (moved) into the APPLDWorld.
APPLDA elements have a local name scope so that objects that the APPLDA owns can
have local names, allowing any Appware manager that manipulates Application Data to
easily identify elements within them in the same way that design templates (TMPLates) are
handled. Existing commands and expression functions such as LNAME, LNID etc operate
within this scope.
6.3.3 Application Data and Templates

A template (TMPLate) can be included in the Application Data World, but only as an
instanced template, NOT a template definition. Such templates can be refreshed from their
definitions using existing (appware and core) driven functions. However, there is no core
supported means to refresh copies of Application Data in the real model.
6.3.4 Extension to Design Data
DDAT elements have a new attribute PTOLER that provides a tolerance value as an
alternative to the MAXMIN values which determine the range of valid values when set.
Applications using the Application Data will use this value to validate its data.
6.3.5 Valid Value Elements Additional Attribute

Valid Value elements (VVALUE) owned by a DDAT can have a Valid Rule set stored in the
attribute VALRULE. VALRULE is an expression attribute that can store an expression that
evaluates to a logical true or false value. If the expression does not evaluate to a logical
result, or if there are errors in the evaluation of the expression, then the VALRULE will
return FALSE when queried. The VVALUE element owns a Valid Value attribute (VALIDV)
that is an expression returning a real, logical, text or reference value which supports the
owning DDAT element. If the VALRULE is true, or if it is a null expression, then this
VALIDV will be available to the DDAT.
VALRULEs are used by the system to control the choice of a Valid Value when property
queries are made on the owning DDAT.
For example a DDAT element might own four VVALUE elements with VALIDV and
VALRULE attributes as follows:
VValue VALIDValue expression VALRULE expression
VVALUE 1 ( ID /ANG35x35x15 ) ( LDPR LENG le 1800 )
VVALUE 2 ( ID /ANG40x40x15 ) ( LDPR LENG gt 1800 and LDPR LENG le 2400 )
VVALUE 3 ( ID /ANG45x45x18 ) ( LDPR LENG gt 2400 and LDPR LENG le
3000 )

Design Templates
VVALUE 4 ( ID /ANG50x50x18 ) ( LDPR LENG gt 3000 )

The current set of VALIDValues available for the owning DDAT are the set whose
VALRULEs either are unset, or evaluate to TRUE. Those that are not available are those
whose VALRULEs either evaluate to FALSE, or whose evaluation generate errors.
6.3.6 Extension to Design Data Associated Pseudo Attributes

Local Design Data Set (DDSE) pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP
(which up to release 12 only operated within the scope of the owner of a DDSE) now also
operate at the DDSE level and within the scope of a DDSE:
Attribute Returns At Owner of At DDSE Below a DDSE
DDSE (DDAT, VVALUE etc)
DEPL List of Properties in all Properties in this Properties in owning
Property keys owned DDSE DDSE DDSE
LDPR Real value Property in any Property or Property in any
owned DDSE Default Property DDSE owned by
in any DDSE owner of owning
owned by owner DDSE
of DDSE
DEPR Text value for
text and reals
LFDP Reference
value
DEPD Text default Default Property Default Property in
value for text in any owned any DDSE owned by
and reals DDSE owner of DDSE
All attributes fail above the owner of the DDSE.
6.3.7 Special Design Data Property names in scope of a DDSE

Each of the Local Design Data pseudo attributes DEPL, LDPR, DEPR, DEPD and LFDP
take a qualifier that is the key to a particular design data element (the DKEY of the DDAT).
Special values of this key are used to query values within the DDAT and VVALUE
elements:
VALI: for returning evaluation of the VALIDV attribute of a VVALUE
VALR: for returning the evaluation of a VALRUL attribute of a VVALUE
VVAL: for returning a VALIDV/ALUE result with a true VALRULE
DDAT: for returning the value of the local DDAT (either a DPROPerty or else a
DDEFAUlt without knowing its DKEY
element DDAT VVALUE

special
key word
VALR ERROR, no VALRUL attribute result of evaluated VALRUL attribute

Design Templates
VALI ERROR, no VALIDV attribute result of evaluated VALIDV attribute

VVAL returns VVAL result of first VVALUE returns result of evaluated VALIDV if
element that does not ERROR, VALRUL evaluates TRUE, else
ERROR
DDAT returns the same value as would be Returns the same value as the DDAT
returned using the DKEY of the property of the owning DDAT without
DDAT. (Either the DPROPerty or having to know the actual DKEY
DDEFAUlt value). This is a value to use.
convenient way of obtaining this
value without knowing the DKEY
All of these properties will error if queried at the DDSE element or above.
If the Design Data set actually has a data element that has a property with one of these
name keys (they are not reserved in anyway) then the use of the key will operate normally
on the DDSE or its owner, and as listed in the table above on a DDAT or VVALUE.
Use of the VVAL key on a particular DDAT will return the first suitable value from a set of
many values. This is similar to choosing from a set of values according to some criteria. It is
possible to use this as an alternative to the IFTRUE expression, which can, for example
when used iteratively, select a set of possible choices depending on a particular criterion.
The IFTRUE expressions will increase the expression length with the possibility of
exceeding the maximum length of the text attribute. Use of VVAL key will not do this.
The VVALUEs owned by a DDAT DO NOT modify the return values of design data
properties when queried by their owners.
It should be noted that if the DPROPerty of a DDAT is inconsistent with the set of VVALUEs
that it owns, this will NOT raise an exception or error when querying it directly using its
DKEY. It is up to the application using these data values to decide whether to accept the
value of a DPROPerty whenever it conflicts with valid values, or maximum or minimum
values, or a tolerance. To do otherwise would risk the integrity of existing user and system
applications.
6.4 Parameterisation using Design Datasets

Design Datasets (DDSE) are used to store the properties of design template items, which
may then be used to define the template’s parameters. Each property is stored in a Design
Data (DDAT) element under a DDSE, with each DDAT being identified by a keyword held
in its DKEY attribute. The property definition can be specified by an expression held in the
DDPR (Design Data Property) attribute, while a default value for the property (to be used if
the expression cannot be evaluated for any reason) can be stored in the DDDF (Design
Data Default) attribute.
Unlike a design reference to a catalogue component, which can access only a single
catalogue dataset via its DTREF setting, a reference to a design template can access more
than one design dataset. A local design dataset is owned directly by the current element,
a template design dataset is owned by the first template below the current element, while
a current design dataset is at the same level as the current element and has the same
owner.
The following diagram illustrates the relative positions of these types of dataset for a simple
hierarchy:

Design Templates
The pseudo-attributes available for accessing the properties data in the various types of
dataset are as follows:
Current Local Template
Dataset Dataset Dataset
List of property keys CDPL DEPL PRLS
Real property values CDPR LDPR TDPR
Text or real property values TCDP DEPR PROP
Text or real property default values TCDD DEPD PRDE
Reference settings CFDP LFDP TFDP
Note: The dataset attributes PRLS, PROP and PRDE are also used to refer to catalogue
dataset properties. If you query any of these attributes, a search for a catalogue
dataset will be made first; if this fails, a search for a design template dataset will be
made.
Most commonly, a design attribute value will be defined in terms of a design property by
using the CDPR (Current Design Dataset Property) attribute. The CDPR can also be used
to define a property in one dataset in terms of a property in another dataset. When a CDPR
is used in a rule for a component whose owner can own datasets, the current datasets will
be those at the same level as the component: otherwise, the current datasets will be those
under the first dataset-owning element above the component. When a CDPR is used in a
property expression within a dataset, it refers to a property in the current dataset for the
item at which CDPR is evaluated.
When used in a querying command or in an expression (for example, when defining a
parameterisation rule), the attributes for a specific property are identified by the DKEY for
that property. For example:
Q CDPL Lists all DKEYs for properties in current dataset.
Q CDPR LENG Gives value of LENG property in current dataset.
RULE SET XLEN Sets rule for current element’s XLEN attribute using value from
(CDPR LENG) 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

Design Templates
of the LENG property would be derived from, say, a design parameter and the rule
would be re-executed to give the correct XLEN.
6.5 Assigning Local Names to Template Elements

When a design template is copied, confusion can arise in the identification of members of
the template instance. If a template rule refers to an element by its hierarchic position (e.g.
BOX 1 OF TMPL 1 OF ... etc.), rule execution errors can arise if the template instance is
modified in any way which affects the ordering of the members list. Even if the element has
a PDMS name under the Template World, this name will be lost when the template is
copied because an element name cannot be used more than once in a Design database.
To avoid these problems, you can assign a local name (LNAME) to a template member.
Each local name, and the reference of the corresponding element, is stored in an array
attribute of the template. Local names are therefore set and queried at member element
level, even though they are stored at template level. The local name survives a template
copy operation.
6.5.1 Setting Local Names

Keywords:
LNAME
Description:
Lets you assign a local name to a template member, or unset an existing local name. A
local name can have a maximum of 20 characters; a maximum of 500 local names can be
stored on one template. The local name cannot be modified if either the element or its
owning template is locked.
Examples:
LNAME /ANTHONYSets 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)

Design Templates
6.5.2 Using Local Names in Expressions

Keywords:
LNID
MLNID
Description:
Lets you identify an element by its local name in a rule or dataset expression.
Example:
LNID /SID Identifies element defined in current template
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 For element in current template
Q MLNID /JOE For element in member
template
6.6 Setting Priorities for Evaluating Rules
By default, the rules for the member elements of a design template are executed in
descending hierarchic order. If the rule for one member element includes a reference to the
result of a rule for another member, it is important that the latter rule is executed before the
former, otherwise an incorrect result will be obtained.
You can control the order in which the rules for a given template will be executed by
assigning a rule sequence number to any element which has a local name. When the
template rules are re-executed, the rules for such elements will be executed in ascending
order of their sequence numbers: the rules for elements with sequence numbers unset (or
zero) will then be executed in the default order. Each rule sequence number, and the
reference of the corresponding element, is stored in an array attribute of the template. Rule
sequence numbers are therefore set and queried at member element level, even though
they are stored at template level.
Keywords:
RSEQNUMBER
Description:
Lets you assign a rule sequence number to any design template member which has a local
name. The rule sequence number must be a positive integer (zero is equivalent to unset).

Design Templates
The same sequence number may be assigned to more than one element, but this is not
recommended.
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.7 Adding Design Points to Template Elements

The design datasets for a template, as discussed in Parameterisation using Design
Datasets, approximate to the Geomset data for a catalogue component. In a similar way,
design templates can also own Design Pointsets (DPSE), which approximate to the
Pointset data for a catalogue component. These let you assign p-points to design template
items, to be used as references for subsequent positioning and orientating operations.
A design pointset can store three types of p-point (note that these are not the same as
those available in catalogue pointsets):
• A Cartesian P-point is specified in terms of its X,Y,Z co-ordinates only, thus:
Orientation
Design
Z Point
Y Direction of Normal
Origin
• 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

Design Templates
Point Orientation
Direction of Normal
Z
Angle defining point position
Y wrt Y axis
Origin
Cylinder defined by its
X position, height and radius
• A Spherical P-point is specified as a position on the surface of a sphere at a given

position and with given dimensions, thus:
position and radius
6.8 Using a Design Template Item in a Design

To create an instance of a ‘source’ design template in a design model, you must first create
a template below the owning design element and then copy into this the details of the
source template (which must be in a template world) from which it is to derive its data. The
commands (at the design element which is to own the instance) are:
NEW TMPL
COPY REXEcute template_identifier
where template_identifier is the name of the source template. The effects are as follows:
• All elements below the original design template are copied below the new TMPL.
• All template rules are copied and re-executed, thus setting the attributes of the new
TMPL members to suit the design data.
• The Origin Reference (ORRF) attributes for the new TMPL elements are set to point to
their equivalents in the source template.
• All elements below the new TMPL are locked to prevent unintentional changes to any
of their attributes.
If you want to change an attribute explicitly, thereby causing it to differ from the design as
specified in the source template, you must first unset the ORRF references which point
back to the source and unlock the members. To do so, use the command
UNTIE template_instance
where template_instance is the name of the copy TMPL in the design model hierarchy.

Design Templates
6.9 Portsets and Linksets

If you list the possible members of most types of design element, you will see two new
elements called Portsets (PORS) and Linksets (LNKS). These have been added to the
database definition to permit future developments that will allow logical connections to be
made to items derived from design templates. They are not intended for general use at this
release version of PDMS.

Design Templates

Index
A E
c
A o
L m
O m
N a
G n
d
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 3
. :
. 2
. 6
. A
. T
2 c
- o
2 m
: m
3 a
1 n
A d
R .
R .
I .
V
© 2007 AVEVA Solutions Ltd Index page 1

. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 3
. 6
. A
. tt
. ri
. b
. u
. t
2 e
- s:
2 o
: f
5 p
A ri
tt m
a iti
c v
h e
e s
d .
p .
a .
r .
a .
m .
e .
t .
e .
r .
s .
. .
. .
. 2
. -
. 2
. :
. 1
. A

tt o
ri m
b m
u a
t n
e d
s .
: .
s .
e .
c .
ti .
o .
n .
s .
. .
. .
. 2
. -
. 4
. :
. 1
. A
. X
. E
. S
. c
. o
. m
. m
. a
2 n
- d
5 :
: pi
4 p
A e
U r
T o
O u
R ti
O n
U g
T .
E .
.
c

. B
. A
. S
. E
2 c
- o
4 m
: m
2 a
n
B d
:
B pi
A p
N e
G r
L o
E u
ti
c n
o g
m .
m .
a .
n .
d .
. .
. .
. 2
. -
. 4
. :
. 6
. B
. E
2 H
- I
5 N
: D
6 c
, o
2 m
- m
5 a
: n
1 d
2

. .
. .
. .
2 .
- .
2 .
: .
2 2
6 -
, 5
2 :
- 1
3 2
: B
7 e
, t
2 a
- a
3 n
: gl
5 e
2 :s
e
B
ct
e
io
t
n
a
a s
n .
g .
l .
e .
:j .
o .
i .
n .
t .
s .
.
.
.
.
.
.
.
.
.
.
2
.
-
.
5
.
:
.
6

B :
O pi
P p
e
c r
o o
m u
m ti
a n
n g
d .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 4
. :
. 7
2 B
- r
3 a
: n
7 c
, h
2 :
- h
3 e
: a
6 d
3 .
B .
O .
P .
.
c .
o .
m .
m .
a .
n .
d .

. :
. 2
. B
. ui
. ld
. in
. g
. s
2 .
- .
3 .
: .
2 .
B .
r .
a .
n .
c .
h .
:t .
a .
il .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 4
. 2
. B
. U
. I
. L
. T
. fl
. a
. g
2 .
- .
3

. .
. .
. .
. .
. .
. .
. 2
. -
. 2
. :
. 1
. 5
.
. C
.
. C
. D
. P
. R
2 a
- tt
3 ri
: b
3 u
1 t
B e
Y .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 6

: m
8 m
C a
H n
O d
O .
S .
E .
.
c 2
o -
m 2
m :
a 3
n 4
d ,
. 2
. -
. 3
. :
. 5
. 9
. C
. o
. fit
. ti
. n
. g
. el
2 e
- m
3 e
: n
1 t
2 .
C .
L .
E .
A .
R .
A .
N .
C .
E .
.
c .
o

. o
. m
. p
. o
2 u
- n
5 d
: fit
3 ti
4 n
C g
o el
fi e
tt m
i e
n n
g t
R .
e .
f .
e .
r .
e .
n .
c .
e .
A .
r 2
r -
a 5
y :
a 2
tt C
ri o
b m
u p
t o
e u
. n
. d
2 F
- lo
5 o
: r
3 el
4 e
C m

e .
n .
t .
. 2
. -
. 5
. :
. 1
. C
. o
. m
. p
2 o
- u
5 n
: d
4 p
2 a
C n
o el
m fit
p ti
o n
u g
n el
d e
j m
o e
i n
n t
t .
e .
l .
e .
m .
e 2
n -
t 5
. :
. 2
. C
. o
. m
. p
. o
. u
n

d .
S .
c .
r .
e .
e .
d .
e .
l .
e .
m 2
e -
n 5
t :
. 4
. 2
. C
. O
. N
. N
. E
. C
2 T
- c
5 o
: m
4 m
3 a
C n
o d
m 2
p -
o 2
u :
n 1
d 4
W ,
a 2
ll -
e 3
l :
e 2
m ,
e 2
n -
t 3

: A
3 at
9 tri
, b
2 ut
- e
5:17 ..
C ..
o ..
n ..
n ..
e ..
c ..
ti ..
o ..
n 2
:f -
o 3:
r 3
c 4
e C
d T
. Y
. E
. N
. D
. c
. o
. m
. m
. a
. n
. d
. ..
. ..
. ..
. ..
2 ..
- ..
3 ..
: .2
4 -
1 5:
C 8
R C
F T

Y t
S a
T s
A e
R t
T .
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. 2
. -
. 6
:
.
7
.
C
.
u
.
rr
.
e
2
n
-
t
5
D
: e
8 si
C g
u n
r D
r a
e t
n a
t s
d e
e t
s P
i r
g o
n p
d e
a rt

y 3
a 8
tt C
ri u
b rv
u e
t el
e e
2 m
- e
6 nt
: ..
8 ..
C ..
U ..
R ..
T ..
Y ..
P ..
a ..
tt 2
ri -
b 5:
u 3
t 6
e C
. u
. rv
. e
. T
. y
. p
. e
. at
. tri
2 b
- ut
5 e
: ..
3 ..
6 ..
, ..
2 2
- -
5 5:
: 3

6 A
, N
2 E
- c
5 o
: m
3 m
8 a
C n
U d
T ..
B ..
A ..
C ..
K ..
c ..
o 2
m -
m 5:
a 1
n 6
d
. D
.
. D
. D
. A
. T
. el
e
.
m
.
e
.
n
.
. t
. .
2 .
- .
5 .
.
:
.
1
.
6
.
C
.
U
.
T
.
P
.
L

. D
. D
. P
. R
. a
. tt
. ri
2 b
- u
6 t
: e
7 .
D .
D .
D .
F .
a .
tt .
ri .
b .
u .
t .
e .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 6
. :
. 7
. D
. D
. S
. E
. el
. e
. m
2 e
- nt
6 ..
: ..
7

. ..
. 2
. -
. 5:
. 1
. 2
. D
. e
. si
. g
. n
. D
. at
. a
. D
2 ef
- a
6 ul
: t
7 at
D tri
E b
L ut
P e
O ..
S ..
I ..
T ..
I 2
O -
N 6:
7
c D
o e
m si
m g
a n
n D
d at
. a
. el
. e
. m
. e
. nt
. ..

. ..
. 2
. -
. 6:
. 7
. D
. e
. si
. g
. n
. D
. at
2 a
- s
6 et
: el
7 e
D m
e e
s nt
i ..
g ..
n ..
D ..
a ..
t ..
a 2
P -
r 6:
o 7
p D
e e
rt si
y g
a n
tt p
ri a
b r
u a
t m
e et
. e
. rs
. ..
. ..
. ..

. 2
. -
. 6:
. 1
. 1
. D
. e
. si
. g
2 n
- T
5 e
: m
3 pl
4 at
D e
e el
s e
i m
g e
n nt
P ..
o ..
i ..
n ..
t ..
s 2
e -
t 6:
e 1
l D
e E
m S
e P
n A
t R
. A
. M
. E
. T
. E
. R
. c
. o
. m
. m

a ..
n 2
d -
. 2:
. 3
. D
. I
. R
. E
. C
2 T
- I
5 O
: N
3 c
4 o
D m
e m
t a
a n
il d
l ..
e ..
v ..
e ..
l ..
. .
. 2
. -
. 3:
. 3
. 7
. D
. I
. S
. C
. O
. N
. N
. E
. C
. T
. c
. o
. m
. m

a ,
n 2
d -
. 3:
. 4
. 8
. D
. K
. E
. Y
. a
. tt
2 ri
- b
5 u
: t
1 e
8 .
D .
I .
S .
T .
A .
N .
C .
E .
c .
o .
m .
m .
a .
n .
.
d
.
.
.
. 2
. -
. 6
. :
. 7
2 D
- P
3 S
: E
4 el
4 e

m .
e .
n .
t .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 4
. 3
. D
. R
. A
. G
. c
. o
2 m
- m
6 a
: n
1 d
1 .
D .
R .
A .
F .
T .
U .
n .
i .
o .
n .
a .
tt .
ri .
b .
u .
t 2
e -
. 3
. :
6

8 n
D d
R .
N .
E .
N .
D .
.
c .
o .
m .
m .
a .
n .
d 2
. -
. 5
. :
. 6
. D
. U
. N
. I
. O
. N
. a
. tt
. ri
. b
2 u
- t
5 e
: .
6 .
D .
R .
N .
S .
T .
A .
R .
T .
c .
o .
m .
m .
a

. m
2 e
- n
5 ts
: :c
4 o
3 n
n
E e
ct
E in
d g
g .
e .
d .
r .
a .
w .
i .
n .
g .
i .
n .
D .
R .
A 2
F -
T 2
. :
. 1
. 4
. E
. le
. m
. e
. n
. ts
. :
2 m
- o
5 vi
: n
4 g
3 .
E .
l .
e

. .
. .
. 2
. -
. 2
. :
. 1
. 0
. E
. le
. m
. e
2 n
- ts
2 :r
: o
1 t
5 a
E ti
l n
e g
m .
e .
n .
t .
s .
: .
o .
ri .
e .
n .
t .
a .
ti .
n .
g .
. 2
. -
. 2
. :
. 1
. 2
. E
. n
. d
. p
. o

s a
it n
i d
o .
n .
( .
s .
e .
c .
ti .
o .
n .
) .
. .
. .
. 2
2 -
- 5
5 :
: 8
4 E
, X
2 T
- E
5 N
: D
5 c
, o
2 m
- m
5 a
: n
9 d
E .
R .
E .
L .
E .
A .
S .
E .
.
c .
o .
m .
m .

. el
2 e
- m
5 e
: n
2 t
2 .
.
F .
.
F .
C .
O .
N .
N .
E .
C .
T .
c 2
o -
m 5
m :
a 1
n ,
d 2
. -
. 5
. :
. 3
. 3
. F
. itt
. in
. g
. el
. e
2 m
- e
3 n
: t:
4 c
1 o
F m
it p
ti o
n u
g

n .
d .
. 2
. -
. 5
. :
. 1
. F
. ix
. in
. g
. el
2 e
- m
5 e
: n
2 t
F .
it .
ti .
n .
g .
e .
l .
e 2
m -
e 5
n :
t: 2
p ,
a 2
n -
e 5
l :
. 3
. 7
. ,
. 2
. -
. 5
. :
. 4
. 2
. F
. L
. I

P .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
2 :
- 4
3 2
: F
2 O
7 R
, C
2 E
- C
5 O
: N
2 N
0 E
F C
l T
o c
o o
r m
m
s
a
. n
.
d
.
. .
. .
. .
. .
.

. c
2 o
- m
3 m
: a
1 n
2 d
F .
o .
r .
c .
e .
d .
c .
o .
n .
n .
e .
c .
ti .
o .
n .
. .
. 2
. -
. 3
. :
. 4
. 8
.
. G
.
. G
. e
. n
. e
2 ri
- c
3 F
: ix
4 in
1 g
F el
R e
O m
M e
n

t 2
. ,
. 2
. -
. 5
. :
. 3
. 6
. G
. E
. N
. S
2 E
- C
5 el
: e
4 m
2 e
G n
e t
n .
e .
ri .
c .
S .
e .
c .
ti .
o .
n .
e 2
l -
e 5
m :
e 2
n ,
t 2
. -
. 5
. :
. 3
. 6
2 #
- 1
5 0
: 6

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
2 2
- 6
6
: H
1
1 H
, B
2 O
- R
6 c
: o
1 m
2 m
p a
li n
n d
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
.

. R
. c
. o
. m
. m
2 a
- n
3 d
: .
5 .
H .
C .
O .
N .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. 2
. -
. 3
. :
. 5
. H
. e
. a
. d
. o
. f
. b
. r
. a
2 n
- c
3 h
: .
5 .
H .
D .
I

. .
. 2
. -
. 3
. :
. 5
. H
. R
. E
. F
. c
. o
. m
. m
2 a
- n
3 d
: .
2 .
H .
P .
O .
S .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. 2
. -
. 3
. :
. 4
. H
. S
. P
. E
. c
. o
. m
. m

a .
n .
d .
. .
. .
. .
. .
. .
. 2
. -
. 3
. :
. 2
. 9
. H
. S
. T
. U
. B
. E
2 a
- tt
3 ri
: b
2 u
H t
S e
R .
O .
D .
.
a .
tt .
ri .
b .
u .
t .
e .
. .
. .
. .
. .
. 2
. -
. 3
. :

2 o
9 m
I m
a
I n
D d
P .
L 2
I -
N 2
E :
2
c 6
o
m
,
2
m
-
a
3
n
:
d 7
.
.
,
2
.
-
.
3
.
:
.
5
.
2
.
. In
. st
. a
. n
. c
. e:
2 D
- e
5 si
: g
2 n
6 te
I m
N pl
F at
R e
O s
N ..
T ..
c ..

. 0
. I
. S
. P
2 E
- C
6 at
: tri
1 b
I ut
n e
s ..
u ..
l ..
a ..
ti ..
o ..
n ..
s ..
p .2
e -
c 3:
if 3
i 0
c
a
J
ti
o J
n L
. D
. A
. T
. U
. M
. el
. e
. m
. e
. nt
. ..
. ..
2 ..
- ..
3 .2
: -
3 5:

3 in
7 t
, el
2 e
- m
5 e
: nt
4 :c
1 o
J m
O p
I o
E u
N n
D d
..
c ..
o ..
m ..
m ..
a .2
n -
d 5:
. 1
. J
. oi
. nt
. el
. e
. m
. e
. nt
. :li
. n
. e
. a
. r
. ..
. ..
2 ..
- ..
5 ..
: ..
7 ..
J .2
o -

5 el
: e
1 m
J e
o n
i t:
n s
t e
e c
l o
e n
m d
e a
n r
t: y
p .
ri .
m .
a .
r .
y 2
-
.
5
.
:
.
1
.
. ,
. 2
. -
. 5
2 :
1
-
1
5
J
:
oi
1
n
, t:
2 c
- r
5 e
: a
1 ti
1 n
J g
o .
i .
n .
t

. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 1
. 5
. J
. oi
. nt
2 s:
- li
5 n
: e
1 a
0 r
J ..
o
..
i
..
n
..
t
..
s
..
:
..
a
..
tt
ri ..
b ..
u 2
t -
e 5:
3
s
1
.
J
.
oi
.
nt
.
. s:
. p
. ri
. m
. a
. ry

. ..
. ..
. ..
. ..
. ..
. .2
. -
. 5:
. 1
. 3
. J
. O
. I
. S
. T
. A
. R
. T
. c
2 o
- m
5 m
: a
1 n
2 d
J ..
o ..
i ..
n ..
t ..
s ..
: ..
s 2
e -
c 5:
o 7
n J
d u
a st
r ifi
y c
. a
. ti
. o
. n
. Li

n ..
e ..
D ..
a ..
t ..
u ..
m .2
-
e 3:
l 2
e 6
m L
e E
n V
t E
2 L
- c
5 o
: m
3 m
7 a
, n
2 d
- ..
5 ..
: ..
4 ..
1 ..
..
L ..
..
L
.2
E
-
A
2:
V
3
E
Li
c
n
o
e
m
a
m
r
a
jo
n
in
d t
. el
. e
. m

e ..
n ..
t ..
. ..
. .2
. -
. 5:
. 3
. 1
. LI
. N
. K
. c
. o
. m
. m
. a
. n
2 d
- ..
5 ..
: ..
1 ..
L ..
i ..
n ..
e ..
a .2
r -
j 5:
o 3
i 1
n L
t N
s A
. M
. E
. ..
. ..
. ..
. ..
. ..
. ..
. ..
. ..
. ..

. :9
. L
. o
. c
. al
. d
. e
2 si
- g
6 n
: d
9 at
L a
N s
I et
D ..
. ..
. ..
. ..
. ..
. ..
. ..
. 2
. -
. 6:
. 7
. L
. o
. c
. al
. n
. a
. m
. e:
. D
. e
. si
. g
. n
. te
. m
. pl
. at
2 e
- s
6 ..

. S
. R
. O
. D
. at
2 tri
- b
6 ut
: e
9 ..
L ..
O ..
F ..
F ..
a ..
tt ..
ri ..
b .2
u -
t 3:
e 2
. 9
. L
. S
. T
. U
. B
. E
. at
. tri
. b
. ut
. e
. ..
. ..
. ..
. ..
. ..
. ..
2 ..
- ..
3 2
: -
3 3:
3 2
L 9

li
n
2 d
- ri
5 c
: al
2 p
6 ..
C ..
a ..
rt ..
e ..
s ..
i ..
a ..
n ..
p ..
. 2
. -
. 6:
. 1
. 1
. S
. p
. h
. e
. ri
. c
. al
. p
. ..
. ..
. ..
. ..
. ..
. ..
. ..
. ..
2 ..
- ..
6 .2
: -
1 6:
1 1
C 2
y

M .
.
M .
I .
R .
R .
O .
R .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. 2
. -
. 6
. :
. 9
. M
. O
. V
. E
. c
2 o
- m
2 m
: a
4 n
3 d
M .
L .
N .
I .
D 2
-
. 2
. :
. 1
. 6
.

, 2
2 -
- 5:
3 1
: N
9 o
, d
2 e
- el
3 e
: m
4 e
2 nt
:s
N e
c
N o
o n
d d
e a
e ry
l ..
e ..
m ..
e ..
n ..
t: .2
p -
ri 5:
m 1
a N
r o
y d
. e
. s:
. p
. ri
. m
. a
. ry
. ..
. ..
. ..
. ..
. ..
. ..

. :9
. N
. o
. z
. zl
. e
. of
2 fs
- et
5 fa
: ct
2 o
N r:
o pi
d p
e e
s r
: o
s ut
e in
c g
o ..
n ..
d .
a 2
r -
y 4:
. 4
. N
. o
. z
. zl
. e
. s:
. s
. p
. e
. ci
. fy
. in
. g
. ..
. ..
2 ..
- ..
5 ..

. b
. st
. r
. u
. ct
2 io
- n
2 le
: v
2 el
:c
la
O s
O h
B d
S e
T t
R e
U ct
C io
T n
I .
O .
N .
.
c 2
o -
m 2
m :
a 4
n O
d F
. F
. S
. E
. T
. F
. A
. C
. T
. O
2 R
- c
2 o
: m
4 m
O a

n :
d 5
. 5
. O
. P
. D
. I
. R
. E
2 C
- T
4 I
: O
4 N
O c
N o
T m
O m
P a
n
c d
o .
m .
m .
a .
n .
d .
. .
. .
. 2
2 -
- 5
2 :
: 1
2 2
8 O
, R
2 D
- E
3 R
: c
7 o
m
, m
2 a
- n
3 d

: :
p 1
i 0
p ,
e 2
r -
o 3
u :
ti 3
n 5
g O
. ri
. e
. n
. t
. a
2 ti
- o
4 n
: .
8 .
O .
R .
I .
E .
N .
T .
A .
T .
E .
.
c .
o .
m .
m .
a .
n .
d .
. .
. 2
. -
. 2
. :
2 1
- 0
2 O

R e
I r
F s
L .
A .
G .
.
a .
tt .
ri .
b .
u .
t .
e .
. .
. .
. .
. 2
. -
. 5
. :
. 3
. 6
.
. P
.
. P
. a
2 n
- el
3 F
: itt
3 in
2 g
O el
w e
n m
i e
n n
g t
p .
a .
r .
a .
m .
e .
t .

2 2
- P
5 a
: n
1 el
, F
2 itt
- in
5 g
: R
3 e
4 f
P e
a r
n e
e n
l c
fi e
tt a
i tt
n ri
g b
e u
l t
e e
m .
e .
n .
t: 2
c -
o 5
m :
p 3
o 4
u P
n a
d n
. el
. L
. o
. o
. p
2 el
- e
5 m
: e
n

t .
. .
. .
. .
. 2
. -
. 5
. :
. 1
. P
. a
. n
. el
. s:
. c
2 o
- n
5 n
: e
1 ct
P in
a g
n .
e .
l .
V .
e .
rt .
e .
x .
e .
l .
e .
m .
e .
n .
t .
. 2
. -
. 5
. :
. 3
. 1
. P
. a
. n
el

s .
: .
c .
r .
e .
a .
ti .
n .
g .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 3
. 0
. P
. a
. r
2 a
- m
5 e
: t
2 e
9 r
P s:
a a
n tt
e a
l c
s h
: e
s d
p .
li .
tt .
i .
n .
g .
.

. 3
. 4
. P
. a
. r
. a
2 m
- e
5 t
: e
3 r
6 s:
P o
a w
r ni
a n
m g
e .
t .
e .
r .
s .
: .
d .
e .
s .
i .
g .
n .
. .
. .
. 2
. -
. 5
. :
. 3
. 6
. P
. e
. n
. al
. ty
. v
2 ol
- u
5 m
: e

: .
p .
i .
p .
e .
r .
o .
u .
ti 2
n -
g 3
. :
. 6
. P
2 ip
- e
4 r
: a
2 c
, k:
2 pi
- p
4 e
: r
3 o
P u
H ti
n
c g
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 4
. :
5

P n
i d
p .
e .
r .
o .
u .
ti .
n .
g .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 1
. 1
. P
. L
. D
. A
. T
. U
. M
.
. el
2 e
- m
4 e
: n
1 t
P .
J .
O .
I .
N .
T .
c .
o .
m 2
m -
a

5 4
: 1
3 P
7 N
, O
2 D
- E
5 c
: o
4 m
1 m
P a
li n
n d
e .
D .
a .
t .
u .
m .
.
e .
l .
e .
m .
e .
n .
t .
. .
. 2
. -
. 5
. :
. 2
. P
2 O
- I
5 N
: S
3 P
7 el
, e
m
2
e
-
n
5
: t

. .
. 2
. -
. 6
. :
. 1
. 1
. ,
. 2
. -
. 6
. :
. 1
. 2
. P
. O
2 L
- A
5 R
: c
3 o
6 m
p m
o a
i n
n d
t: .
i .
n .
d .
e .
s .
i .
g .
n .
p .
o .
i .
n .
t .
s .
e .
t 2
. -
. 2
. :
.

8 m
P m
o a
l n
a d
r .
p .
o .
s .
it .
i .
o .
n .
i .
n .
g .
. .
. .
. .
. 2
. -
. 5
. :
. 5
. P
. O
. S
. F
. L
. A
. G
. a
. tt
2 ri
- b
2 u
: t
8 e
P .
O .
S .
E .
N .
D .
.
c .
o

. 4
. 4
. P
. o
. si
. ti
2 o
- ni
3 n
: g
3 .
2 .
P .
O .
S .
I .
T .
I .
O .
N .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. 2
. -
. 2
. :
2 5
- P
2 O
: S
5 L
, I
2 N
- E
3 c
: o
m
m

a .
n .
d .
. 2
. -
. 5
. :
. 5
. P
. P
. L
. I
. N
. E
. c
. o
2 m
- m
5 a
: n
1 d
3 .
P .
O .
S .
S .
T .
A .
R .
T .
c .
o .
m .
m .
a .
n 2
d -
. 5
. :
. 2
. 6
. P
. ri
. m
. iti
. v
e

s .
: .
a .
tt .
ri .
b .
u .
t .
e .
s .
. 2
. -
. 5
. :
. 1
. ,
. 2
. -
. 5
. :
. 4
. P
. S
. P
. E
2 c
- o
2 m
: m
1 a
P n
r d
o .
fi .
l .
e .
e .
l .
e .
m .
e .
n .
t .
. .
. .
. .

. o
. m
. m
2 a
- n
3 d
: .
2 .
P .
T .
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. 2
. -
. 4
. :
. 3
. R
.
. R
. A
. C
. K
.
. c
. o
2 m
- m
3 a
: n
6 d
P
V .
O
L .
c

. m
m
. a
n
. d
. .
. .
. .
. .
2
. -
3
. :
1
. 1
,
.
2
. -
5
. :
1
. 9
. R
2 E
- S
4 E
: L
5 E
C
R T
E
C c
O o
N m
N m
E a
C n
T d
c .
o

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
3 .
:
2 .
2
.
R 2
i -
n 5
g :
4
W 3
a
l R
l o
d
e :
l a
e t
m t
e r
n i
t b
u
. t

e R
s O
T
. A
T
. E
. c
o
. m
m
. a
n
. d
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
2
- .
3 2
: -
2 2
9 :
1

2 2
-
R 4
O :
U 4
T
E R
o
c u
o t
m i
m n
a g
n
d p
l
. a
n
. e
:
. p
i
. p
e
.
r
. o
u
. t
i
. n
g
.
.
.
.
.
.
.
.
.
.
. 2
-
. 4
:
. 2

, .
2 .
-
4 .
: 2
3 -
4
R :
P 3
L
A R
N S
E E
Q
c N
o U
m M
m B
a E
n R
d
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2
. -
6:10
.
S
.
S
. c
2 r
- e
6 e
: d
1 s
0
R .
u
l .
e
s .
e
q .
u
e .
n
c .
e
n .
u
m .
b
e .
r:
D .
e
s .
i
g .
n
t .
e
m .
p
l .
a
t .
e
s .

.
.
.
.
.
.
.
.
.
.
.
.
2 .
- 2
5 -
: 4
4 :
2 6
S S
D e
I c
R t
i
c o
o n
m s
m :
a a
n t
d t
: r
p i
i b
p u
e t
e
r s
o
u .
t
i .
n
g .
. .

. g
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
2
- .
5
: .
4
.
S 2
e -
c 5
t :
i 1
o 7
n
s S
: e
c c
o t
n i
n o
e n
c s
t :
i c
n r

e e
a c
t t
i i
n o
g n
s
. :
d
. i
s
. c
o
. n
n
. e
c
. t
i
. n
g
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
5 .
: 2
3 -
5
S :

1 5
8 :
2
S 2
e
c S
t e
i c
o t
n i
s o
: n
m s
o :
d r
i e
f c
y o
i n
n n
g e
c
l t
e i
n n
g g
t
h .
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-

. .
. .
2
- .
5 2
: -
1 3
9 :
1
S 7
E
L S
E H
C O
T P
c f
o l
m a
m g
a
n .
d
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. .
. .
. .
. .
. .
. .
2
. -
3
. :
2 2
- 1
3
: S
3 J
1 O
S I
H N
O T
R
T c
C o
O m
D m
E a
n
c d
o
m .
m
a .
n
d .
. .
. .
. .
. .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
5 .
:
1 .
1 2
-
S 5
N :
O 9
D
E S
o
c f
o t
m
m t
a y
n p
d e
s
.
.
.
.
.
.
.
.
.
.

e
. l
e
. m
e
. n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
2 -
- 5
5 :
: 2
4 ,
2
2
S -
p 5
i :
n 3
e 6

S 2
p -
i 5
n :
e 3
6
P
o S
i P
n L
t I
T
e
l c
e o
m m
e m
n a
t n
d
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
. 2
-
. 4
2 :
- 7
5 S
: P
3 R
0 E
F
S
P a
R t
E t
A r
D i
b
c u
o t
m e
m
a .
n
d .
:
p .
i
p .
e
.
r
o .
u
t .
i
n .
g
.
.
.
.
.
.
.
.

. .
. .
. .
. .
. .
2
- .
3 2
: -
2 5
8 :
8
S
R S
E t
L a
E r
A t
S
E p
o
c s
o i
m t
m i
a o
n n
d
(
. s
e
. c
t
. i
o
. n
)
.
.
.
.
.
.

. .
. .
. .
. .
. .
2
- .
5
: .
4
, .
2 .
-
5 .
:
5 .
S .
t
e .
e
l .
w 2
o -
r 5
k :
: 1
f S
i t
t e
t e
i l
n w
g o
s r
k
. :
f
. i
x
. i

n l
g w
s o
r
. k
:
. g
e
. n
e
. r
i
. c
. s
e
. c
t
. i
o
. n
s
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
5 .
: 2
2 -
5
S :
t 2
e
e S

t
e .
e
l .
w 2
o -
r 5
k :
: 1
j
o S
i t
n e
t e
s l
w
. o
r
. k
:
. n
o
. d
e
. s
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
5 .
:
1 .
S .
t
e .
e 2
l -
w 5
o :
r 1
k
: S
p t
a e
n e
e l
l w
s o
r
. k
:
. s
e
. c
t
. i
o
. n
s

W
. a
l
. l
. e
l
. e
m
. e
n
. t
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
2
- .
5
: .
1
.
S 2
t -
r 5
a :
i 4
g 3
h
t S
T

R :
I 3
N
G S
u
c b
o f
m i
m t
a t
n i
d n
g
.
e
. l
e
. m
e
. n
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2 .
-
5 .

.
.
.
.
.
.
2 .
-
5 .
:
2 .
S .
u
b .
j 2
o -
i 5
n :
t 1
e s
l y
e n
m t
e a
n x
t
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

n
. c
h
. .
.
. .
.
. .
.
. .
.
. .
.
. .
.
. .
.
. .
.
. .
.
. .
.
. 2
-
. 3
:
. 2
T
. B
2 O
- R
5 c
: o
2 m
6 m
a
T n
d
T
.
a
.
il
.
o
.
f
.
b
.
r
.
a

. :
. 5
. T
. D
. I
. R
. c
. o
. m
. m
2 a
- n
3 d
: .
5 .
T .
C .
O .
N .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. .
. .
. 2
. -
. 3
. :
. 5
. T
. e
. m
. pl
. a
. t
. e
. A
2 r
- e
3 a

e .
l .
e .
m .
e .
n .
t .
. .
. .
. .
. 2
. -
. 6
. :
. 7
. T
. e
. m
. pl
2 a
- t
6 e
: W
1 o
T rl
e d
m el
p e
l m
a e
t n
e t
d .
e .
s .
i .
g .
n .
d .
a .
t .
a .
s .
e 2
t -
. 6
:

1 .
T .
H .
R .
O .
U .
G .
H .
.
c .
o .
m .
m .
a .
n .
d .
. .
. .
. 2
. -
. 6
. :
. 1
. T
. M
. P
. L
. el
2 e
- m
3 e
: n
4 t
6 .
T .
M .
A .
R .
.
e .
l .
e .
m .
e .
n .
t .
.

. c
. o
. m
. m
. a
2 n
- d
6 .
: .
1 .
T .
O .
.
c .
o .
m .
m .
a .
n .
d 2
. -
. 3
. :
. 7
. ,
. 2
. -
. 3
. :
. 6
. 3
. T
. P
. O
. S
. c
. o
. m
2 m
- a
3 n
: d
4 .
8 .
T .
O .
P

. 2
. -
. 6
. :
. 1
. T
. r
. a
. c
. e
. s
. p
. e
2 ci
- fi
3 c
: a
5 ti
T o
P n
W .
L .
e .
l .
e .
m .
e .
n .
t .
. .
. .
. .
. .
. .
. 2
. -
. 3
. :
. 3
. 1
. T
. R
. E
. F
. c
. o
. m

m .
a .
n .
d .
. .
. .
. .
. .
. .
. .
. 2
. -
. 3
. :
. 3
. 1
. T
. u
. b
. e
. :
2 a
- tt
3 ri
: b
4 u
T t
S e
P s
E .
.
a .
tt .
ri .
b .
u .
t .
e .
. .
. .
. .
. .
. .
. .
. .
. .
2

- o
3 ni
: n
2 g
9 d
r
U a
w
U n
N el
D e
E m
R e
n
c ts
o in
m D
m R
a A
n F
d T
. .
. 2
. -
2 5
- :
2 4
: 3
2 U
8 N
, L
2 I
- N
3 K
: c
7 o
, m
2 m
- a
3 n
: d
5 .
5 .
U .
n .
i .

. :
. 1
. 2
.
. W
.
. W
. al
. l
2 el
- e
5 m
: e
3 n
1 t
U .
N .
T .
I .
E .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 4
. 3
. W
. al
. ls
. .
2 .
- .
6 .

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. 2
. -
. 5
. :
. 9
.
.
.
.
2
-
5
:
4
2
Z
Z
D
I
S
T
A
N
C
E
c
o
m
m
a
n
d

Design Reference Manual - Creating The Model

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Design Reference Manual - Creating The Model

Cargado por

Copyright:

Formatos disponibles

Manual de Referencia de diseño

Creación del modelo

El manual y la documentación asociada no pueden ser adaptados, reproducidos o copiados, en

Publicado por primera vez en septiembre de 2007

Manual de referencia DESIGN

Creación del Modelo

© 2007 AVEVA Solutions Ltd i 12.0

Moving Either Side of a Fixed Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:26

© 2007 AVEVA Solutions Ltd ii 12.0

Trace Heating Specification Attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:31

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

© 2007 AVEVA Solutions Ltd iii 12.0

Setting Routing Planes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3

Structural Design Using Catalogue Components . . . . . . . . . . . . . .5:1

Manually Connecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:17

© 2007 AVEVA Solutions Ltd iv 12.0

Reconnecting Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:19

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

© 2007 AVEVA Solutions Ltd v 12.0

Extension to Design Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5

© 2007 AVEVA Solutions Ltd vi 12.0

Creación del Modelo

1.1 Acerca del Manual de Referencia de Diseño

DESIGN se utiliza normalmente de forma interactiva. La interfaz gráfica de usuario (GUI)

interfaz gráfica de usuario (GUI) proporciona aplicaciones basadas en disciplinas que le

1.2 Organización del Manual de Referencia de Diseño

• Parte 1, Comandos generales, describe los comandos de diseño generales, que se

• Parte 3, Utilidades, describe las Utilidades de diseño para la comprobación de

1.3 Organización de este Manual

© 2007 AVEVA Solutions Ltd 12.0

• bandejas de tuberías, conductos y cables describen los comandos para el

• El enrutamiento automático de tuberías describe los comandos para los usuarios

• Diseño estructural mediante componentes de catálogo, describe su enfoque

• Las plantillas de diseño son grupos de elementos que se pueden definir y

obtener una lista completa de todos los atributos y pseudoatributos de PDMS,

© 2007 AVEVA Solutions Ltd 12.0

2.1 Atributos de modelado primitivos

2.1.1 Dimensionamiento de bloques de construcción

Caja Cono Plato

Cilindro Cilindro con fondo de pendiente Hocico

Circular Torus Rectangular Torus Pirámide

© 2007 AVEVA Solutions Ltd 2 2:1 12.0

Los agujeros pueden sumergirse a través de primitivas "sólidas" utilizando un conjunto

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

Figure 2:1. Dimensioning a CYLINDER primitive

2.1.2 Choosing Nozzle Size, Rating and Height

© 2007 AVEVA Solutions Ltd 2 2:2 12.0

CATR /NFAARPMM (At Nozzle)

HEI 2’6 (At Nozzle)

The Height of the Nozzle becomes 2’6.

2.1.3 Modelling Detail Levels

© 2007 AVEVA Solutions Ltd 2 2:3 12.0

>-- LEVel integer integer -->

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

2.1.4 Obstruction Settings

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.

© 2007 AVEVA Solutions Ltd 2 2:4 12.0