Pdms Design

pdms1131/man30/doc1Issue181200

PDMSDESIGN

Reference ManualPart 1: General Commands

Version 11.3

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

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

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

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

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

Copyright 1990 through 2001 Cadcentre Limited

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

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

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

http://www.cadcentre.com/location

PDMS DESIGN Reference Manual Contents-iPart 1: General CommandsVersion 11.3

Contents

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

2 How to Use the Syntax Graphs....................................................................2-12.1 Commands...........................................................................................................2-22.2 Command Arguments .........................................................................................2-22.3 Standard Syntax Graphs ....................................................................................2-4

2.3.1 Universal Expression <expr>........................................................................2-52.3.2 Date/Time <date>..........................................................................................2-62.3.3 Physical Dimension <uval>...........................................................................2-72.3.4 Design Element Type <snoun> or <noun> ...................................................2-82.3.5 Design Element Identity <gid>...................................................................2-102.3.6 3D Design Points <marke> .........................................................................2-132.3.7 Axial Position <pos> <axes> ......................................................................2-142.3.8 3D Position <bpos>.....................................................................................2-162.3.9 3D Axis Direction <dir> .............................................................................2-172.3.103D Direction <bdir>....................................................................................2-192.3.11Selection <selatt> ........................................................................................2-20

2.4 Command Input Modes.....................................................................................2-22

3 General PDMS Commands...........................................................................3-13.1 Entering DESIGN...............................................................................................3-13.2 Saving..................................................................................................................3-1

3.2.1 Saving DESIGN Work...................................................................................3-13.2.2 Saving and Restoring the Display ................................................................3-1

3.3 The Alpha Display ..............................................................................................3-23.3.1 Saving the Alpha Log ....................................................................................3-23.3.2 Clearing the Alpha Views .............................................................................3-3

3.4 Leaving DESIGN ................................................................................................3-43.4.1 Changing Modules.........................................................................................3-43.4.2 Exit from DESIGN without Saving Changes ...............................................3-4

3.5 Setting Working Units and Tolerances ..............................................................3-53.5.1 Setting Working Units ..................................................................................3-53.5.2 Setting Output Precision of Distance Units .................................................3-63.5.3 Switching between Actual and Nominal Bores ............................................3-8

3.6 Audible Error Trace ............................................................................................3-83.7 Switching Text Output Off .................................................................................3-93.8 Giving Operating System Commands from PDMS............................................3-93.9 General Querying Facilities..............................................................................3-10

3.9.1 Querying Your Current Module..................................................................3-103.9.2 Querying Your System ................................................................................3-10

Contents

Contents-ii PDMS DESIGN Reference ManualPart 1: General Commands

Version 11.3

3.9.3 Querying Your Current Output Devices.....................................................3-113.9.4 Querying the Command Implementation Mode.........................................3-123.9.5 Asking for a Unique Workstation Code ......................................................3-123.9.6 Querying Elements and Attributes in DBs ................................................3-12

4 DESIGN Databases and MDBs.....................................................................4-14.1 MDB Mode...........................................................................................................4-14.2 Checking the Current User Status.....................................................................4-24.3 Checking the Current System Status ................................................................4-34.4 Listing Project Information ................................................................................4-44.5 Sessions ...............................................................................................................4-5

4.5.1 Session Comments.........................................................................................4-54.6 Querying MDB Information ...............................................................................4-6

4.6.1 Querying Individual Database Information .................................................4-64.7 Change Management ..........................................................................................4-7

4.7.1 Querying the Last Modification to an Element or Attribute .......................4-74.7.2 Querying the Session History for an Element or Attribute .........................4-84.7.3 Querying Details of a Specific Session..........................................................4-84.7.4 Querying Session Number for a Given Time................................................4-9

4.8 Using Multiwrite Databases...............................................................................4-94.8.1 User Claims .................................................................................................4-104.8.2 Notes on Standard Multiwrite DBs ............................................................4-114.8.3 Extract Databases .......................................................................................4-114.8.4 How to Find Out What You Can Claim......................................................4-14

4.9 Comparing Database Changes .........................................................................4-174.9.1 Comparing Database States at Different Times ........................................4-17

4.10 Creating Database Update Macros ..................................................................4-184.11 Inter-DB Connection Macros ............................................................................4-19

5 Display ...........................................................................................................5-15.1 Adding Elements to the Display.........................................................................5-1

5.1.1 Selecting Graphics Colours Automatically ...................................................5-25.1.2 Removing Elements from the Display ..........................................................5-55.1.3 Defining Colours............................................................................................5-5

5.2 Element Representation .....................................................................................5-85.2.1 Setting Tube Representation for Piping Components..................................5-85.2.2 Setting Profile Representation for Steelwork...............................................5-95.2.3 Setting Drawing Level Representation ......................................................5-105.2.4 Setting Obstruction and Insulation Representation ..................................5-115.2.5 Setting P-Point Representation ..................................................................5-125.2.6 Setting Structural Node Representation ....................................................5-135.2.7 Setting P-Line Representation....................................................................5-145.2.8 Setting Holes Representation .....................................................................5-165.2.9 Setting Arc Tolerance Representation........................................................5-165.2.10Refreshing the Graphical View...................................................................5-17

5.3 Specifying Axes .................................................................................................5-175.4 Graphical Labelling of Design Elements..........................................................5-185.5 Using Design Aids.............................................................................................5-195.6 Highlighting Components in the Designs ........................................................5-245.7 Spatial Maps .....................................................................................................5-25

Contents

PDMS DESIGN Reference Manual Contents-iiiPart 1: General CommandsVersion 11,3

5.7.1 Checking the Spatial Maps .........................................................................5-255.7.2 Creating or Updating Spatial Maps............................................................5-26

6 Using Rules to Define Attribute Settings ....................................................6-16.1 Setting Attribute Rules.......................................................................................6-16.2 Verifying Attribute Rules ...................................................................................6-26.3 Executing Attribute Rules ..................................................................................6-36.4 Deleting Attribute Rules.....................................................................................6-3

7 Interacting with a Graphical View................................................................7-17.1 Identifying Displayed Items and Points.............................................................7-1

7.1.1 Identifying Displayed Elements using the Cursor .......................................7-17.1.2 Identifying Tube using the Cursor................................................................7-27.1.3 Identifying Displayed Points using the Cursor ............................................7-27.1.4 Identifying Items with a 2D Pick..................................................................7-3

7.2 3D Pins ................................................................................................................7-47.2.1 Setting a Pin’s Position and Direction Explicitly .........................................7-57.2.2 Making a Pin Visible .....................................................................................7-57.2.3 Locating a Pin by Copying or Connecting.....................................................7-67.2.4 Moving a Pin..................................................................................................7-77.2.5 General Pin Moves ........................................................................................7-7

7.3 Constructs ...........................................................................................................7-8

8 Design Database Elements ..........................................................................8-18.1 Elements..............................................................................................................8-1

8.1.1 Creating Elements.........................................................................................8-18.1.2 Creating Elements at a Given Position in the Member List........................8-28.1.3 Deleting Elements .........................................................................................8-38.1.4 Reorganising the Hierarchy ..........................................................................8-48.1.5 Copying ..........................................................................................................8-58.1.6 Copying and Renaming .................................................................................8-6

8.2 The Standard Design Element Attributes .........................................................8-78.2.1 The Type of Element and its Owner .............................................................8-78.2.2 Naming Design Elements .............................................................................8-88.2.3 Renaming Elements and their Offspring......................................................8-88.2.4 Locking Elements Against Alteration and Deletion....................................8-98.2.5 The Position and Orientation Attributes......................................................8-9

8.3 Navigation .........................................................................................................8-108.3.1 Going to the Previously Accessed Element.................................................8-118.3.2 Going to an Implied Tube or Rod ................................................................8-118.3.3 Ascending the Design Hierarchy ................................................................8-128.3.4 Other Navigation Commands .....................................................................8-12

8.4 Setting a Synonym for an Element Name........................................................8-13

9 Error Messages .............................................................................................9-1

Index

PDMS DESIGN Reference Manual 1-1Part 1: General CommandsVersion 11.3

1 Introduction

1.1 About the DESIGN Reference Manual

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

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

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

1.2 Organisation of the DESIGN Reference Manual

The DESIGN Reference Manual has four parts:

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

• Part 2, Creating the Model, describes the commands for creatingdatabase elements and setting their attributes.

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

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

Introduction

PDMS DESIGN Reference ManualPart 1: General Commands

Version 11.3

1-2

1.3 Organisation of this Manual

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

• Chapter 2 describes How to use the Syntax Graphs, and also shows thestandard syntax graphs which are often referenced from other graphs.

• Chapter 3, General PDMS Commands, describes commands used forsaving work, setting units and tolerances, and handling alphanumericoutput. These commands are common to several PDMS modules, but areincluded here for convenience.

• Chapter 4, Design Databases and MDBs, describes how to handlemultiple databases from within DESIGN, database sessions, how toquery information about the project, and how to used multiwritedatabases.

• Chapter 5, Display, describes how to control the way the model isdisplayed in a graphical view.

• Chapter 6, Using Rules, gives some examples of using rules in DESIGNto control attribute settings.

• Chapter 7, Interacting with a Graphical View, describes how commandscan accept input from picked items in the graphical view, and how todefine construction aids and label the design elements. Note that thecommands in this chapter have generally been superseded by newergraphical facilities available from the GUI, and are only included asinformation for users maintaining older code.

• Chapter 8, Design Database Elements, describes the commands to createDesign elements and set the attributes common to all Design elements,and how to navigate about a Design database hierarchy.

• Chapter 9, Error Messages, explains some of the error messages whichmay be generated by DESIGN.


2 How to Use the Syntax Graphs

The commands described in this chapter are presented in the form of syntaxgraphs.

• Syntax graphs are read from top left to bottom right. The start point isshown by >, and you can follow any path through the graph until the exitpoint, shown by >, is reached.

• Points marked with a plus sign (+) are option junctions which allowyou to input any one of the commands to the right of the junction. Forexample:

>----+--- ABC -----.| ||--- PQR -----|| |`-------------+--->

means you can type in ABC or PQR or just press Enter to get the defaultoption.

• Text in angle brackets <. . . > is the name of another syntax graph. Thisconvention is used for syntax which occurs in many places. The graphsreferred to are described at the end of this section. For example:

>----+--- ABC -----.| ||--- PQR -----|| ||--- <dia> ---|| |`-------------+--->

means you can type in ABC or PQR or any command allowed by thesyntax given in diagram <dia> or just press Enter to get the defaultoption.

• Points marked with an asterisk (*) are loop back junctions. Commandoptions following these may be repeated as required. For example:

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

>---*--- option1 ---|| ||--- option2 ---|| |`--- option3 ---+--->

How to Use the Syntax Graphs


Version 11.3

2-2

means that you can enter any combination of option1 and/or option2and/or option3, where the options can be commands, other syntaxdiagrams, or command arguments.

The simplified format:

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

>---*--- name ----+--->

means that you may type in a list of PDMS names, separated by at leastone space.

2.1 Commands

Commands are shown in a combination of uppercase and lowercase letters,where the capital letters indicate the minimum abbreviation. (Note: Thisconvention does not mean that the second part of the command must be typedin lowercase letters; commands may be entered in any combination ofuppercase and lowercase letters.)

For example, the command

CONStruct

can be input in any of the following forms:

CONSCONSTCONSTRCONSTRUCONSTRUCCONSTRUCT

Commands shown in all uppercase letters cannot be abbreviated.

2.2 Command Arguments

Command arguments are shown in lowercase letters. These are justdescriptions of what you need to enter. The most commonly used descriptionsare as follows:

integer A positive or negative whole number. For example:2 –5 25

value A signed number with or without a decimal point. For example:2.5 5 –3.8

letter A single alphabetic character


PDMS DESIGN Reference ManualPart 1: General CommandsVersion11.3

2-3

word A sequence of up to four letters, e.g. GATE WN P (may belonger in some cases, but only the first four characters aresignificant).

text A string of alphanumeric or symbol characters, which mayinclude spaces, enclosed between single closing quotationmarks or | characters.This is normally used to add descriptive material to anappropriate attribute. For example

DUTY ’Low Pressure’

space The space bar (not usually specified unless of specialsignificance)

name A sequence of characters preceded by a slash / andrepresenting a PDMS Element name. For example:

/BRANCH7 /305.ABC /P4/NOZNote: A name should always be followed by a space

(unless at the end of a line).

filename An external file name of the form/filename

varid An identifier (for use with the VARIABLE command withinmacros) of the form

!name where ‘name’ is a text string. For example:

!COUNTER, !height

comma The ‘,’ character, which can be used to concatenate DESIGNcommands. For example:

NEW FLANGE SELECT WITH STYP WN, CONNECT

plus minus star slashThese are the + (add), – (subtract), * (multiply) and / (divide)operators, which can be used in arithmetic expressions. Forexample:

(1 + 2), (1 – 2), (1 * 2), (1 / 2)

Note that there must be a space before and after each of theseoperators.

Note: PML 1 expressions and variables are explained in the CadcentreSoftware Customisation Reference Manual.



Version 11.3

2-4

2.3 Standard Syntax Graphs

If a syntax graph refers to a second syntax graph, the name of the secondgraph is shown in angle brackets. This convention is usually used for standardsyntax graphs which are widely used.

These syntax graphs are summarised below, and then shown in detail.

<expr> Mathematical, textual or logical expressions

<uval> Physical dimension specification

<snoun> or <noun> Design element type

<gid> Design element identity

<marke> 3D Design points(P-points, pins or P-lines)

<pos> or <axes> Axial position

<bpos> 3D position

<dir> Axial direction

<bdir> 3D direction

<selatt> Selection



2-5

2.3.1 Universal Expression <expr>

If a value given in a command needs to be calculated from other known values,you can enter an expression, which is evaluated by DESIGN as it executes thecommand.

You will find details of PML 1 expressions in the Cadcentre SoftwareCustomisation Reference Guide. On-line help describing expressions syntax isavailable from within DESIGN applications.



Version 11.3

2-6

2.3.2 Date/Time <date>

<date> has the general format Time Day Month Year.

Time has the format hour:mins. If no Time is given, the default is 23:59.

Day is a single or two-digit integer. If no Day is given, the default is today. Ifno Time is given, Day must be specified.

Month may be entered as a word, or as a number surrounded by spaced /characters. If no Month is given, the default is the current month.

Year may be entered as four digits or as two digits. Two-digit years areinterpreted within the date window

current_year – 99 to current_year

For example, in the year 2004:

03 means 200304 means 200405 means 1905

If no year is given, the default is the current year.

Examples

12:00 22 August 1999

9:30 29 / 8 / 99 Note spaces in numeric date format

10:30 Assumes current date

22 / 8 / 1999 Assumes time to be 23:59

22 August Assumes current year and time 23:59



2-7

2.3.3 Physical Dimension <uval>

This syntax allows you to override the working (default) units for dimensions .

>--+-- value ----.| |`-- <expr> ---+-- EXponential value --.

| |`-----------------------+-- MM ------.

| ||-- Metres --|| ||-- INches --|| ||-- FT ------|| ||-- FEet ----|| ||-- text ----|| |`------------+-->

Examples

5 5 in current working units

EX3 5500 in current working units

5.3/4 5.75 in current working units

5’ 5 feet (only use when working units are FINCH)

5’6 5 feet 6 inches (only use when working units are FINCH)

5’6.3/4 5 feet 6.75 inches (only use when working units are FINCH)

5 INCHES 5 inches (regardless of current working units)

5 M 5 metres (regardless of current working units)

5’6.3/4 IN 5 feet 6.75 inches (regardless of current working units)

(5 + 2) IN 7 inches (regardless of current working units)

NOTE: Values are always held within DESIGN as metric units. When output,values are rounded as follows:

• Millimetres to the nearest millimetre

• Inches to the nearest 1/32 or 0.1 inch



Version 11.3

2-8

2.3.4 Design Element Type <snoun> or <noun>

This syntax graph refers to an Element Type in the Design hierarchy. To savespace, the available element types are presented as simple lists rather than assyntax diagrams:

Administrative:

WORLds SITes ZONes GPWlds GROups

Equipment and Civils:

EQUipments STRuctures SUBEquipmentsSUBStructures PTRacks CYLindersCONEs SNOuts DIShesSLCylinders BOXes PYRamidsRTORuses CTORuses RPLanesPVOlumes NOZzles POHedronsPOGons EXTRusions REVOlutionsLOOPs VERTEX NBOXesNCYLinders NCONes NSNOutsNDISHes NSLCylinders NPYRamidsNCTOruses NRTOruses NXTRusionsNREVolutions

Steelwork:

RPLGroups FRMWorks SBFRameworksPNODes SNODes PJOIntsSJOInts SCTNs FITTingsLOAPoints PANEls PLOOpsPAVErtex STRUctures SUBStructuresPFITtings CMFittings CMPFittingsSBFIttings

Piping, Hangers and Supports:

PIPes BRAnches RESTraintsHANGers INSTruments ELBowsBENds TEEs VALvesREDucers FLAnges FLGSGASkets WELds PCOmponentsOLEts ATTAchments DUCtingsVENts FTUbes SHUsCOUplings CLOsures LJSesFBLinds CAPs VTWaysVFWays TRAps FILtersUNIons CROsses HELEmentsSCLAmps PCLAmps RODs



2-9

HVAC:

HVACBRAnches

The following are soft-types for use with the HVAC Designer application:

AHU Air handling unitBATT Battery: heater, coolerBRCO Branch connector: boot, square, fish, angled, tapered, mitred etc.COWL Roof cowlDAMP DamperFLEX Flexible tube, flexible bend, material connectionGASK GasketGRIL GrilleHACC Access panelHFAN Centrifugal fanHSAD SaddleIDAM Internal damperMESH Mesh endOFST Offset: cranked, mitred, radiusedPLAT Spigot platePLEN Spigot box, plenumSILE SilencerSKIR SkirtSPLI Splitter: flow splitter, deflectrol, air turning vanesSTIF Stiffening flangeSTRT StraightTAPE TaperTHRE Threeway: radiused, twin bend, breeches etc.TP Test point, test holesTRNS Transformation: square to round, square to flat oval, oval A to

oval B etc.

Datums and Constraints:

BOUNdary DRAWIngs DATumsPOInts IPOints TANpointsGRDmodels TEXts



Version 11.3

2-10

2.3.5 Design Element Identity <gid>

This syntax identifies a Design Element. The main syntax graph is <gid>,shown below. The sub-graphs follow.

.-------------------------------.| |

<gid> >----+-- <nexid> ------------+-------|| | ||-- <snoun> -+----------| || | | || |- <next> -+- OF --’| | || | ‘---------.| | || ‘-- <id> ------------|| ||-- <othid> ----------------------|| ||-- <id> -------------------------|| |`-- <clos> -----------------------+----->

Direct identification: by reference to name/reference number <id>, hierarchy <othid>, or to a point selected from

display <curid>:

<id> >--+-- name ---.| |`-- refno --+-->

<othid> >--+-- CE ---------.| ||-- SAMe -------|| ||-- ELEMent ----|| |`-- <curid> ----+-->

<curid> >-- IDentify --+-- <snoun> ---.| ||-- Tube ------|| |`--------------+-- @ -->

Indirect identification: by reference to other elements, parts of elements or adjacent members in the database hierarchy



2-11

<nextid> >-+- HEad ----.| ||- TAil ----|| ||- ILeave --|| ||- IArrive -+-- <tubid> ---.| ||-- <next> -- <snoun> -----|| ||-- OWNer -----------------|| |`-- END -------------------+--->

<tubid> >-+-- TUBe--.| |`-- ROD --+-->

<next> >-+-- LAst -----.| ||-- FIrst ----|| ||-- PREvious -|| ||-- NEXt -----+-- integer --.| | || ‘-------------+-- MEMbers--.| |`-- integer -----------------------------+-- OF ->

Identification by physical position in the design model:

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

<clos> >- CLOSest -*- <snoun> -+- WITH <expr> -.| |`---------------+- UP ----.

|- DOWN --||- EAST --||- WEST --||- NORTH -|`- SOUTH -+-.

.----------------------------<--------------------’`-+- EXTENT <expr> -.

| |`-----------------+- AFTER <expr> -.

| |`----------------+- FROM <bpos> -.

| |`---------------+->

WITH specifies rule restricting choice of element (default is no restriction);

EXTENT specifies how far to search before giving up (default is 10 metres);

AFTER specifies that search is to start after given distance in givendirection (default is zero);

FROM specifies reference position from which search is initiated (default isCE).



Version 11.3

2-12

Examples

/EQUIP10 Named design Element

SAME Previous Element accessed

OWN Owner of Current Element

GOTO SPRE Specification of Current (piping) Element

NEXT 2 Second Next Element at same level

4 Fourth Member of Current Element

LAST 3 MEM Third Last Member of Current Element

END Next element up in hierarchy

SITE Site above Current Element

ZONE 3 Third Zone

NEXT 2 PIPE Second Next Pipe

PREV BOX

FIRST ZONE OF /SITE 5

PIPE OF /VALV101

FIRST MEM OF BRAN3 OF /PIPE10

HEAD OF FIRST BRAN

CLOSEST VALV EASTClosest valve to current element in East direction in designmodel (note that syntax accepts only cardinal directions,which must be entered in full)

CLOS VALV NORTH FROM E100 N200 U300Closest valve in North direction starting from givenposition (valves found before this position are ignored)



2-13

2.3.6 3D Design Points <marke>

This syntax describes 3D Design Points and their Attributes. A Design Point is

• A P-point

• A temporary Pin

• A cursor position

Pin:

>-- PIn integer -->

P-point:

>--+-- PArrive ---------.| ||-- PLeave ----------|| ||-- PHead -----------|| ||-- PTail -----------|| ||-- HHead -----------|| ||-- HTail -----------|| |`-- Ppoint integer --+-- OF <gid> --.

| |`---------------+-->

Cursor:

>-- IDPpoint @ -->

Examples

P3 P-point 3 of Current Element

PL OF PREV Leave P-point of previous element

PH Branch Head P-point

HT OF /HANG5 Hanger Tail P-point of named Hanger

IDP @ Cursor pick



Version 11.3

2-14

2.3.7 Axial Position <pos> <axes>

This syntax specifies a 3D position in space in terms of an axial coordinatesystem.

>-- <pos> --+-- <axes> --.| |`------------+-->

where:

<pos> = >--+-- <nsy> --+-- <udz> ----- <ewx> ---.| | || |-- <ewx> --+-- <udz> ---|| | | || | `------------|| | || `------------------------|| ||-- <udz> --+-- <nsy> ----- <ewx> ---|| | || |-- <ewx> --+-- <nsy> ---|| | | || | `------------|| | || ‘------------------------|| |`-- <ewx> --+-- <udz> ----- <nsy> ---|

| ||-- <nsy> --+-- <udz> ---|| | || `------------|| |`------------------------+-->

and where:<nsy> = >--+-- North --.

| ||-- Y ------|| |‘-- South --+-- <uval> -->

<udz> = >--+-- Up ----.| ||-- Z -----|| |‘-- Down --+-- <uval> -->

<ewz> = >--+-- East --.| ||-- X -----|| |‘-- West --+-- <uval> -->

<axes> = >--+-- WRT --.| |‘-- IN ---+-- <gid> -->



2-15

Examples

E1000 East 1000

Z10 Up 10

E30 D10 S20 East 30 Down 10 South 20

E0 IN SITE East 0 in Site



Version 11.3

2-16

2.3.8 3D Position <bpos>

This syntax provides a 3D position in terms of a specified coordinate, a knownidentity or point, or a cursor position.

General axial position: >-- <pos> --+-- <axes> --.| |‘------------+-->

(see previous subsection)

3D Design point: <marke> (see above)

General element identity: <gid> (see above)

Cursor position: >-- @ -->

Examples

E300 N1000 U2500 Coordinate position

PIN6 Pin position

/VESSEL10 Origin of /VESSEL10

@ Working grid position closest to the crosshairposition and through the Current ElementOrigin plane

NOTE: Cursor positioning (e.g. AXES AT @) can only be carried out inorthogonal views.



2-17

2.3.9 3D Axis Direction <dir>

This syntax provides a 3D direction expressed in terms of a coordinate system.

>-+-<nsy>-+-<exp_val>-+-<ewx>-+-<exp_val>-+-<udz>-+-<exp_val>--.| | | | | | || | | | | ‘-------------|| | | | ‘----------------------|| | | ‘--------------------------------|| | | || | |-<udz>-+-<exp_val>-+-<ewx>-+-<exp_val>---|| | | | | | || | | | | ‘-------------|| | | | ‘---------------------|| | | ‘---------------------------------|| | ‘-----------------------------------------|| ‘---------------------------------------------------||-<udz>-+-<exp_val>-+-<nsy>-+-<exp_val>-+-<ewx>-+-<exp_val>--|| | | | | | || | | | | ‘-------------|| | | | ‘----------------------|| | | ‘--------------------------------|| | | || | |-<ewx>-+-<exp_val>-+-<nsy>-+-<exp_val>---|| | | | | | || | | | | ‘-------------|| | | | ‘---------------------|| | | ‘---------------------------------|| | ‘-----------------------------------------|| ‘---------------------------------------------------|| |‘-<ewx>-+-<exp_val>-+-<nsy>-+-<exp_val>-+-<udz>-+-<exp_val>--|

| | | | | || | | | ‘--------------|| | | ‘-----------------------|| | ‘---------------------------------|| | || |-<udz>-+-<exp_val>-+-<nsy>-+-<exp_val>----|| | | | | || | | | ‘--------------|| | | ‘----------------------|| | ‘----------------------------------|| ‘------------------------------------------|‘----------------------------------------------------+-->

where:

<nsy> = >--+-- North ---. <ewx> = >--+-- East --.| | | ||-- Y ------| |-- X -----|| | | |‘-- South --+--> ‘-- West --+-->

<udz> = >--+-- Up -----. <exp_val> = >--+-- <expr> --.| | | ||-- Z -----| ‘-- value ---+-->| |‘-- Down --+-->



Version 11.3

2-18

Examples

E East

E45N East 45 North

W-33D West 33 Up

Y North

N45E33D North 45 East 33 Down

N10E10 North 45 East



2-19

2.3.10 3D Direction <bdir>

This syntax provides a 3D direction by making use of a specified axis direction,a design point, or two 3D positions.

General axial direction

>-- <dir> --+-- <axes> ---.| |‘-------------+-->

(See previous subsections for <dir> and <axes>)

3D Design point direction:

<marke> (see above)

3D position direction:

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

(see above for <bpos>)

Examples

N45E Axis direction

PL Design point direction

TOW E0 WRT SITE From Current Element Origin to SITE origin

FROM PIN6 TO PIN7 From Pin 6 to Pin 7



Version 11.3

2-20

2.3.11 Selection <selatt>

This syntax lets you describe elements you want to include in, or exclude from,operations. Typically, the following criteria are used to define a selection:

• A class of elements or element types to be selected. You can specifywhether all members are to be included, or whether only items (thelowest level components in the hierarchy below a given element) shouldbe included. See <selcla> below.

• A logical expression to be satisfied for all selected elements. Theseexpressions return either True or False, and are usually used to checkthe values of attributes. See the Cadcentre Software CustomisationReference Manual.

• A physical volume in which all selected elements must lie. This volumeis always orthogonal to the World coordinate axes. You can specify this interms of two diagonally opposite points of an enclosing box, or as avolume around an element (with an optional clearance around theelement selected). See <selvol> below.

• A point in the hierarchy below which all selected elements must lie. Youcan follow this with an exclusion list to exclude elements from theselection. See <selhie> below.

• A list (or collection), such as a drawlist, obstruction list or claimlist, ofwhich the selected elements must be members.

All of these criteria are optional, except for class. If all element types arevalid, this should be ALL.

If you specify more than one criterion, the specifications must be in the aboveorder, as shown by the following graphs:

<selatt>= >-+- ALL -----------------------.| || .------<-----. || | | |‘- <selcla> -*- <selcla> -’ |

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

|.-----------------<------------------------’|+- WIth --.| ||- WHere -+- <expr> -.| |‘--------------------+- <selvol> -.

| |‘------------+- <selhie> -.

| |‘------------+- <selfrom> -.

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

where <selcla> gives the class of items to be selected:



2-21

<selcla>= >--+-- <noun> ---.| |‘--- <gid> ---+-- MEMbers --.

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

<selvol> allows you to specify a volume to be selected:

<selvol>= >-+- WITHIN -----------.| |‘- EXCLusive WITHIN -+-- VOLume - <gid> -+- <expr> -.

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

<selhie> gives the point in the hierarchy below which elements are to beselected:

<selhie>= >-- FOR -- <gid> --+-- <gid> ------------.| |‘-- EXCLude - <gid> --+-->

<selfrom> limits the elements available to those in a specified list or collection:

<selfrom>= >-- FROM --+-- !VAR -------.| ||-- DRAWLIST ---|| ||-- OBSTLIST ---|| |‘-- CLAIMLIST --+-->

Examples

ALL Selects all elementsALL FRMW

Selects all framework elementsALL BRANCH MEMBERS

Selects all piping componentsITEMS OF EQUI /VESS1

Selects all primitives below /VESS1(/PIPE1 /PIPE2)

Selects just /PIPE1 and /PIPE2ALL WITH (XLEN GT 1000)

Selects all elements where XLEN is greaterthan 1000mm

ALL WITHIN W8000N17000U1000 TO W1400N13500U1200

Selects all elements within the defined volume



Version 11.3

2-22

ALL PIPE WITHIN VOLUME /PIPE1 1500

Selects all piping elements within a volumedefined as a box drawn around /PIPE1, with aclearance of 1500mm between the edges of/PIPE1 and the volume box.

You can minimise the time taken for any selection operation by making theselection criteria as specific as possible, so that only relevant parts of thedatabases are searched for the required elements. Where known, specify theelement type (e.g. ALL BOX ...), the database element under which the searchis to be restricted (e.g. ALL BOX FOR /ZONE1 ...), the volume in which you areinterested (e.g. ALL BOX WITHIN N5000 E5000 U0 TO N10000 E12000U8000 ...), and so on. If you do not do this, all databases in the current MDBwill be searched, whether or not they contain relevant types of element, andperformance will be impaired.

2.4 Command Input Modes

Generally, in DESIGN you are able to access the full range of DESIGNcommand syntax. However there are two modes where the syntax is restrictedto commands only relevant to that mode. The modes are:

• MDB mode allows you to change or query databases during a DESIGNsession. Described in Chapter 4.

• DESCLASH mode allows you to check the design for clashes. Describedin the Design Reference Manual Part 4: Utilities.

To return to normal DESIGN mode, enter the command EXIT.


3 General PDMS Commands

3.1 Entering DESIGN

Keyword: DESIGN

Description: Enters DESIGN. This command is available throughout PDMS.

3.2 Saving

3.2.1 Saving DESIGN Work

Keyword: SAVEWORK [n] GETWORK [n]

Description: SAVEWORK saves the current DESIGN changes without leavingDESIGN. It is good practice to use this command on a regular basisduring a long DESIGN session to ensure maximum data security.

The optional number n can be used to specify a particular database forthe command. The number is the number of the database in the orderoutput by the STATUS command (see Section 4.2). If no number isgiven, the SAVEWORK applies to the whole MDB.

GETWORK refreshes the view of all READ databases to pick up anychanges that other users may have made since you first opened them.The optional n works in the same way as for SAVEWORK. You wouldnormally only use GETWORK if you know of specific changes you wishto pick up and use. Please note that GETWORK slows up subsequentdatabase access, as the information has to be re-read from disk.Therefore, you should use this command sparingly.

3.2.2 Saving and Restoring the Display

Keywords: RECREATE INSTALL

Description: These commands let you save and restore the graphical view(s) andthe forms as displayed before you exit from DESIGN.

NOTE: Forms resized or moved using the cursor will be INSTALLed to theiroriginal size.

General PDMS Commands


Version 11.3

3-2

Examples:

RECREATE /DS1 Saves the display definition in file /DS1.

RECREATE /DS1 OVERSaves the display status in file /DS1. Anyexisting file /DS1 is overwritten.

RECRE DISPLAY /DS1Saves modal settings, e.g. working grid, units,representation etc. Read back in using $M/name

INSTALL SETUP /DS1Restores the display definition stored in file/DS1

Command Syntax:

>-- RECReate --+-- DISPlay --.| |‘-------------+-- name --+-- OVERwrite --.

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

>-- INSTALL SETUP name -->

3.3 The Alpha Display

3.3.1 Saving the Alpha Log

Keywords: ALPHA LOG ALPHA FILE

Description: Lets you save the alpha display information to a text file. Two types ofoutput are available, depending on the command used.

ALPHA LOG enables the contents of either or both of the COMMANDSand REQUESTS alpha regions to be written to a file.

ALPHA FILE enables the contents of the REQUESTS regions only to bewritten to file.

The ALPHA LOG and ALPHA FILE commands may be used to save datasuch as the results of a data consistency check, or be used as a generaloutput facility.

NOTE: After an ALPHA file has been opened, subsequent output will bedirected to both the file and the screen until the file is closed, or untilyou change to another PDMS module.



3-3

Examples:

ALP LOG /LF1 COMMANDSLog information displayed in the COMMANDSregion in file /LF1

ALP LOG /LF1 OVER COMMLog information displayed in the COMMANDSregion in file /LF1. Any existing file /LF1 will beoverwritten.

ALP LOG /LF2 Log information displayed in both alpha regionsin file /LF2

ALP FILE /LF2 Log information displayed in REQUESTS regiononly

ALP LOG END Finish logging dataALP FILE END

Command Syntax:

>-- ALPha --+-- LOG --+-- name --+- OVERwrite --.| | | || | |- APPend -----|| | | || | ‘--------------+-- COMMands -.| | | || | |-- REQuests -|| | | || | ‘-------------|| | || ‘-- END --------------------------------|| |‘-- FILE --+-- name --+-- OVERwrite --------------|

| | || |-- APPend -----------------|| | || ‘---------------------------|| |‘-- END -------------------------------+->

3.3.2 Clearing the Alpha Views

Keywords: ALPHA CLEAR

Description: Each alpha region may be cleared by using a variation of the ALPHAcommand.

Examples:

ALPHA COMMANDS CLEARClears the text from the COMMANDS regiononly.



Version 11.3

3-4

ALPHA REQUESTS CLEARClears the text from the REQUESTS regiononly.

Command Syntax:

>-- ALPha --+-- COMMands --.| |‘-- REQuests --+-- CLEAR -->

3.4 Leaving DESIGN

3.4.1 Changing Modules

You can change to another PDMS module by typing the name of the module.DESIGN automatically saves your work before changing module.

3.4.2 Exit from DESIGN without Saving Changes

Keywords: QUIT FINISH

Description: QUIT exits from DESIGN without saving any changes or the displaysetup. QUIT has the effect of deleting any changes made since the lastSAVEWORK, module change or MDB change.FINISH also exits from DESIGN without saving any changes, but inthis case you are taken directly to the operating system of yourcomputer.

Examples:

QUIT Exit from DESIGN (and enter MONITOR)

QUIT ISODRAFT Exit from DESIGN and enter ISODRAFT

FINISH Exit from DESIGN to the operating system

Command Syntax:

>-- QUIT --+-- modulename --.| |‘----------------+-->

>-- FINISH -->



3-5

3.5 Setting Working Units and Tolerances

These functions let you set the dimensioning units and precision for designplacement and element searching operations. The designer can choose at anytime to work with metric or imperial units and can differentiate between theunits used for nominal pipe bores and for general linear dimensions. Tolerancesettings are available for general 3D positioning, plus special tolerancecontrols for pipe and structural steelwork layouts. A search radius (the ‘hitradius’) can be specified for cursor picking operations.

3.5.1 Setting Working Units

Keywords: MILLIMETRE MM INCH FINCH

Description: You can choose to work with units for nominal bores and dimensionsother than those specified in the Catalogue. The PDMS default is towork in millimetres for nominal bores and distances. However, theCatalogue can contain company-specific instructions that alter thedefaults; say, feet and inches. After the units setting is changed, allinput and output will take place in the new units unless specificallystated.

Examples:

MM BOREAll bores will be input and output in mm

FINCH DISAll distances and coordinates will be input and output in feet and inches

UNITS /PERCHESAll distances and coordinates will be input and output in the units definedin the units definition element /PERCHES in the Properties Database

UNITS DEFUses the default Catalogue database units

UNITS ‘Standard’ PDMS units

NOTE: 3 feet 6 inches must be input as 3’6 when using FINCH units.



Version 11.3

3-6

Command Syntax:

>--+-- MILlimetre --.| ||-- MM ----------|| ||-- INch --------|| |‘-- FInch -------+-- BOres ------.

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

>-- UNITS --+-- <id> -----.| ||-- DEFault --|| |‘-------------+-->

Querying:

Q UNIts

Q DISPLAY Gives tolerance and level settings, as well as unit settings

3.5.2 Setting Output Precision of Distance Units

NOTE: You must not change the precision if you are customising theCadcentre Applicationware. You should only use this command if youare writing a completely new application.

Keywords: PRECISION

Description:

Output dimensions, in the current units, are normally rounded to the followingdegrees of precision:

Millimetres To the nearest mm (e.g. 316)

Inches To the nearest 0.1 inch (e.g. 38.8)

Feet and inches To the nearest 1/32 inch (e.g. 3’7.15/32)

Output for setting variables defaults to the following, higher, precisions:

Millimetres To two decimal places (e.g. 316.25)

Inches To two decimal places (e.g. 38.75)

Feet and inches To the nearest 1/64 inch (e.g. 3’7.31/64)

You may control the output precision of distances in some modules by usingthe PRECISION command. This allows you to specify the number of decimalplaces for MM or INCH output, or the largest fraction denominator for FINCHoutput. Precision levels for general output and for the setting of variables arespecified separately.



3-7

To specify the output precision, use the command:

PRECision opt1 DIstance opt2 value opt3

where the command options (opt1, opt2 and opt3) are as follows:

opt1 defines how the specified precision is to be applied. It is one of thefollowing:

OUTput For general dimensionsVARiables For setting variables

If opt1 is omitted:

• Both Output and Variables are set if opt2 is DEFAULT

• Output only is set if opt2 is TO

opt2 defines whether you are changing to a newly-defined precision or back tothe default settings. It is one of the following:

TODEFault

If opt2 is omitted, TO is assumed.

opt3, which only applies if opt2 is TO, qualifies the number specified by value.The available choices are:

DECimals Decimal placesDPls Decimal placesTHs As in 64thsNDs As in 32nds

If opt3 is omitted, value is assumed to apply as follows:

• If current units are MM or INCH: value is Decimals• If current units are FINCH: value is THs or NDs

Examples:

PREC OUT DI DEF Set default precision for output

PREC VAR DEF Set default precision for variables

PREC DI DEF Set default precision for output and variables

PREC DI 1 DP Set output to 1 decimal place (MM or INCHunits)

PREC OUT DI 4 DECSet output to 4 decimal places (MM or INCHunits)

PREC VAR DI 3 DP Set variables to 3 decimal places (MM or INCHunits)

PREC DI 64THS Set output to 1/64 inch precision (FINCH units)



Version 11.3

3-8

3.5.3 Switching between Actual and Nominal Bores

The PRECISION command also allows you to output actual bore dimensions(rather than Nominal bore values) when required.

To switch to output of actual bore dimensions, use the command:

PRECISION BORE ACTUALTo switch back to using nominal bore values:

PRECISION BORE NOMINAL

3.6 Audible Error Trace

Keywords: ALARM

Description: When a macro error occurs, there is an audible alarm at theworkstation to signal that the error has occurred. Occasionally, macroerrors can be anticipated and no audible warning is required. Thiscommand allows the audible warning to be switched on or off eitherinteractively or via a macro.

If the audible warning is ON, it will sound whenever an error alert isdisplayed. The default settingis ON .

Examples:

ALARM ON Sets the audible tone to be on.

ALARM OFF Suppresses the audible tone until it is turned onagain.

Command Syntax:

>-- ALARM --+-- ON ---.| |‘-- OFF --+-->



3-9

3.7 Switching Text Output Off

Keywords: TRACE

Description: This command, applicable in TTY mode only, controls the automaticoutput of the Current Element name and attributes. When macros arebeing run, TRACE is always set to OFF automatically.

Examples:

TRACE OFF Stops the automatic output of Current Elementname.

TRACE ON Restarts automatic output of Current Elementname.

Note: ON is the default setting.

Command Syntax:

>-- TRAce --+-- ON ---.| |‘-- OFF --+-->

3.8 Giving Operating System Commands from PDMS

Keywords: SYSCOMmandDescription: PDMS normally assumes that any command input in response to its

prompt character (*) is an instruction to the current module, and willcheck its validity on that assumption. You can issue an operatingsystem (OS) command to the host computer from within PDMS byenetring the SYSCOM command. followed immediately (withoutpressing Return) by the OS command enclosed between apostrophes (’)or vertical bars (|). The effect applies only to the single command line;as soon as the OS command has been executed, control is returned toPDMS.

NOTE: Do not try to issue OS commands which might disrupt PDMSoperations; for example, commands which would close or amend filescurrently in use by PDMS.

Examples:

SYSCOM 'dir' Lists directory from which you entered PDMS.



Version 11.3

3-10

3.9 General Querying Facilities

You will often find, when working in PDMS, that you need to check existinginformation about some aspect of the program’s operations; for example:

• Current usage in terms of users, modules and DBs.

• The currently selected output device.

• The unique code which identifies the process you are running and thestation you are running it from (useful for generating unique workfilenames).

• The current setting, perhaps the default setting, of a command option.

• The contents of part of a particular DB; for example, the current settingof an attribute or the list of member elements owned by a specificelement.

• The elements which match specific selection criteria entered by you.

To ask for such information from within DESIGN, type

Query (almost always abbreviated to Q)

followed by the relevant querying option as described in the following sections.(You also will find more specific querying syntax throughout this set ofmanuals.)

3.9.1 Querying Your Current Module

To check the version number or revision date of your current module, enterone of the following:

Q BANnerQ BANner FULL

This will cause PDMS to redisplay the banner which was shown when you firstentered DESIGN. For example:

Design Mk11.3.1 (WINDOWS-NT 4.0) (29 Feb 2000 : 22.40)

(the FULL option will also display data about the software components used byDESIGN).

3.9.2 Querying Your System

To ask about your current MDB, enter

Q MDBTo output all valid teams for the current user, enter

Q TEAM



3-11

To output the current PDMS user name, enter

Q USERTo output your login name, enter

Q LOGIN/NAMETo output the value of an environment variable, enter

Q EVARiable <evar>

NOTE: If the environment variable name contains any non-letter characters,it must be enclosed in quotes.

To output information about a file, enter

Q FILE <filename> <att>

To output information about an open file, enter

Q OPENFILE <token> <att>

with the file identified by <token>. The information returned is governed bythe attribute <att> which can be:

NAME The name of the file as typed in the OPENFILE commandMODE The mode as given in the OPENFILE commandFULLName The fully specified filenameENTRY The entry name of the file (i.e. without directories)SIZE The size of the file in bytes when it was last closed (it does

not increase as it is written to)DTM The date and time the file was last modifiedOWNER The owner (creator) of the fileLOCK Indicates if the file is locked (valid only for OPENFILE)SORT Type: File, Directory or Other (e.g. a link)

NOTE: In all the above, environment variables in filenames are alwaysexpanded, even for NAME.

3.9.3 Querying Your Current Output Devices

To check the current types of alphanumeric and graphics devices to whichDESIGN is expecting to send your output, especially if you have not changedthe default settings, enter

Q DEViceTo check either type of device separately, enter one of the following:

Q DEVice ALPhaQ DEVice GRAphics



Version 11.3

3-12

To check the current settings for your graphics device, enter any of thefollowing (the list is not comprehensive):

Q SETPens Gives all logical pen settingsQ SETPens number Gives setting for logical pen numberQ LINESTyle Gives line type (dotted, dashed etc.)Q COLours orQ COLORs Gives colours of all logical colour numbersQ COLours number Gives colour of logical colour numberQ COLours BACKground

Gives colour set for display backgroundQ COLours ALPHa Gives colour set for alphabetic characters

and so on.

3.9.4 Querying the Command Implementation Mode

To check the current state of the command implementation mode, that is,whether you have Actions On or Off , enter

Q ACTions

3.9.5 Asking for a Unique Workstation Code

To generate a unique string, based upon your current process and workstationin use, enter

Q UNIQueidThis returns a unique string, which is machine dependent. This is useful forgenerating workfile names that will not clash with names generated by otherusers.

3.9.6 Querying Elements and Attributes in DBs

To check what the current element is, enter

Q CETo check the membership list of the current element, enter

Q MEMbersThe members will be listed in the order of their positions in the membershiplist.

To find out which element owns the current element (the inverse of thepreceding example), type

Q OWNer



3-13

To ask what types of element may legally be members of the currentelement, type

Q LIStTo ask whether an element exists, type

Q EXISTS <element name/refno> [<type>] [UPDATE]The optional <type> lets you check whether the identified element is of a giventype. The optional UPDATE can be used to tell you whether the identifiedelement can be updated or not.

The responses to this query are:

TRUEA If you did not specify <type> and the element exists.

TRUEB If you specified <type> and the element exists and is also of thegiven <type>.

TRUEC If the element exists and can be updated.

FALSEA If the element does not exist.

FALSEB If the element exists but is not of the given <type>.

FALSEC If the element exists but cannot be updated (if UPDATE wasused).

To ask what elements match specified criteria, enter

Q ALL <select>

where <select> is the selection expression. All elements matching your enteredselection criteria will be output. For example

Q ALL BRANCH WHERE (HBORE GT 100) FOR /ATEST

will output all branches in the element /ATEST which have values greaterthan 100 for the attribute HBORE.

To check the settings of all attributes of the current element, type

Q ATTributes(Any user-defined attributes (UDAs) will be output at the end of the attributelist.)

To check the setting of an attribute of a specific element, type

Q (<attribute> OF <id>)For example:

Q (XLEN OF BOX1)



Version 11.3

3-14

To check the settings of specific attributes only, query them by name, thus:

Q XLEngthQ BOReQ POSitionQ ORIentationQ :TESTED (where :TESTED is a UDA)

and so on.

You may query several specified attributes in a single command line. Forexample,

Q POS ORI XLEN YLEN ZLEN :TESTED

To query the contents of part of an array, enter

Q arrayname[index]For example:

Q DESP[10]

To query the PDMS version from which the current DB was created, enter

Q CRINFO


4 DESIGN Databases and MDBs

It is sometimes necessary to access or change Multiple Databases during aPDMS session.

4.1 MDB Mode

Keywords: MDB UPDATE NOUPDATE

Description: The MDB command puts you into MDB Mode, where you can use alimited number of MONITOR commands. This lets you change thecurrent multiple database during a DESIGN session without having toleave DESIGN and enter MONITOR.

When you enter MDB mode, you can either update the current MDB tosave your design changes, or ignore any changes made since your lastSAVEWORK command, by specifying UPDATE or NOUPDATE.

When you are in MDB mode, you can give the following commands,which are the same as the corresponding MONITOR commands. Formore information, see the PDMS MONITOR Reference Manual.

Examples:

MDB UPDATE Save design changes and enter MDB Mode.

MDB NOUPDATE Enter MDB Mode without saving designchanges.

EXCHANGE Alter the databases in the current list of theDEFER current MDBCURRENT

PROTECT Temporarily alters your access rights tospecified databases.

USER username Changes the current user

PROJECT code Changes the current project

LIST Allows you to query:Users, including the number of active users,Teams including the set (current) Team,Databases, including copied Databases,MDBs, Macros and Variables

DESIGN Databases and MDBs


Version 11.3

4-2

/PIPING Change to MDB /PIPING.

/PIPING READONLYChange to MDB /PIPING in read-only mode.

EXIT Return to Design Mode.

Command Syntax:

>-- MDB --+-- UPdate ----.| |‘-- NOUPdate --+-->

4.2 Checking the Current User Status

Keywords: STATUS

Description: Gives you information about your current status as a user and aboutthe DBs to which you have access.

Example:

A typical response to the STATUS command could be:

Project: XYZUser: CSI (758)Teams: BMDB: /DESIGNCurrent DBS:1 PIPING/SITE RW2 MASTER/CATLOG R

Deferred DBS:3 STRUCT/STEEL

This indicates that the designer has identified himself as being PDMS userCSI, that he is logged in to the computer as user 758, that he is a member ofteam B, that he is accessing Project XYZ, and that he has selected an MDBcalled /DESIGN.

Command Syntax:

>-- STATus -->



4-3

4.3 Checking the Current System Status

Keyword: SYSTAT

Description: The SYstem STATus command gives you information about thecurrent active status of the project in which you are working. It listsall users who are currently accessing the project, the modules anddatabases which they are using, and whether they are examining(Read-only status) or modifying (Read/Write status) the database. Italso gives the workstation identifier for each user.

Example:

A typical response to the SYSTAT command could be:

PROJECT XYZ==============

USER SYSTEM (57b)MODULE ADMINMDB ** UNSET **

USER HHJ (752)MODULE DESIGNMDB /STEEL

DB MODEMASTER/AREA-A RMASTER/AREA-B RSTRUC/AREA-C RW

This shows that two users are currently logged in and are using PDMS forwork on Project XYZ. The Project Coordinator is using ADMIN but is notaccessing any databases. User 752 is using DESIGN. He is accessing the MDBnamed /STEEL, whose constituent DBs are as listed. He has Read-only statusfor the DBs owned by the MASTER (System) team and Read/Write access tothe DB STRUC/AREA-C.

Command Syntax:

>-- SYStat -->



Version 11.3

4-4

4.4 Listing Project Information

Keywords: LIST

Description: Lets you list most of the project information held in the SystemDatabase, with the exception of confidential details such as otherusers’ passwords, which can only be listed by the SystemAdministrator in PDMS ADMIN.

Examples:

A typical response to the LIST MDB command could be:

List of MDBS for project XXX==============================MDB: /DESIGNCurrent DBS:1 PIPING/AREA-A DESI Exclusive2 PIPING/AREA-C DESI Update3 MASTER/AREA-D DESI Exclusive

Deferred DBS:4 PIPING/AREA-B DESI Exclusive5 MASTER/AREA-E DESI Update

MDB:/STEELCurrent DBS:1 MASTER/AREA-A DESI Exclusive2 MASTER/AREA-B DESI Exclusive3 STRUCT/AREA-C DESI Exclusive

Deferred DBS:**NONE**

MDB: /ANSICurrent DBS:1 CATAL/AREA-E CATA Update

Deferred DBS:**NONE**

A typical response to the LIST USERS command could be:

List of USERS for project ZZZ===============================SYSTEM (FREE)TEAMS :MASTER STAB

Z (FREE)TEAMS :***NONE**

GEN (GENERAL)TEAMS :TEST



4-5

The information generated by the LIST command can either be displayed onscreen or sent to a file.

Command Syntax:

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

>-- LIst --*-- USers --|| ||-- MDBs ---|| ||-- DBs ----|| ||-- TEams --’|‘-------------->

4.5 SessionsEach time you enter DESIGN or save your design changes, a new session iscreated for each database changed. You can then query when specific items ofdesign data were modified by reference to the corresponding sessionnumber(s). Sessions can be used by the System Administrator to backtrackchanges to a given date or session if necessary.

4.5.1 Session Comments

You can add a comment for each session, which can help identify the workdone in each session.

Keyword: SESSION COMMENT

Description: Lets you associate comment text with the current design session. Youcan query this text later to help you identify a particular session inwhich modifications were made to elements and/or attribute settings.You should enter the session comment before you issue a SAVEWORKcommand.

Note: Sessions 1 and 2 are created in ADMIN (when the DESIGN DB and itsWorld element, respectively, are created), so the first true DESIGNsession will be Session 3.

Examples:

SESSION COMMENT ’Addition of upper platform’

Command Syntax:

>-- SESSION COMMENT -- text -->



Version 11.3

4-6

Querying:

Q SESSComment integer

where integer is the session number.

4.6 Querying MDB Information

Keywords: QUERY

Description: Lets you query details of the current MDB. This is a supplementaryquerying facility to the LIST command (Section 4.4). It allows specificinformation about features of the project configuration to beinterrogated.

Command Syntax:

>-- Query --+-- USer word ---.| ||-- TEam word ---|| ||-- DB dbname ---|| |‘-- MDB name ----+-->

4.6.1 Querying Individual Database Information

Keywords: QUERY

Description: Lets you query details of the current DB for a given element.

Examples:

Q DBNAME Gives name of current DB; e.g. TEST/DESI

Q DBTYPE Gives type of current DB; e.g. DESI

Q DBFNUMBER Gives file number for current DB; e.g. 6

Q DBFILE Gives pathname for current DB file; e.g.\usr\pdms\projects\SAM\sam006 (NT)/net/pdms/projects/SAM/sam006 (Unix)



4-7

Command Syntax:

>-- Query --+-- DBNAme -----.| ||-- DBTYpe -----|| ||-- DBFNumber --|| |‘-- DBFIle -----+-->

4.7 Change Management

You can query the following aspects of the history of modifications to thecurrent database:

• When and by whom an element or attribute was last modified.

• A complete history of the sessions in which an element or attribute hasbeen modified.

• Details of a given session.

• The session number for a given date.

4.7.1 Querying the Last Modification to an Element or Attribute

Keywords: LASTMOD SESSMOD USERMOD

Description: Lets you query details of the most recent change to a given element orattribute.

Examples:

Q LASTMODGives date for last modification to current element.

Q SESSMODGives session number for last modification to current element.

Q USERMODGives name of user who last modified current element.

Q LASTMOD HIERGives dates for last modifications to current element and its members.

Q LASTMOD XLENGives date for last modification to XLEN attribute of current element..



Version 11.3

4-8

Command Syntax:

Q --+-- LASTMod --.| ||-- SESSMod --|| |‘-- USERMod --+--+-- <selatt> --.

| | || ‘--------------+-- HIERarchy --.| | || ‘---------------+-->|‘-- attribute_name -->

4.7.2 Querying the Session History for an Element or Attribute

Keywords: HISTORY

Description: Lets you query modification history for a given attribute; i.e. sessionnumbers during which the attribute was modified.

Examples:

Q HISTORY DIAMGives all sessions in which DIAM attribute was modified.

Note: HISTORY is an array type pseudo-attribute, so that qualifyingpositions may be appended to query specific occurrences in themodification history. For example:

Q HISTORY[2] DIAMgives second most recent session in which DIAM attribute wasmodified.

History records are restricted to a maximum of 120 sessions.

Command Syntax:Q HISTORY attribute_name

4.7.3 Querying Details of a Specific Session

Keywords: SESSCOMMENT SESSUSER SESSDATE

Description: Lets you query details of any specific session. This is particularlyuseful to get details of sessions listed by a HISTORY command.

Examples:

Q SESSCOMM 58 Gives comment text associated with session 58

Q SESSUSER 58 Gives name of user responsible for session 58.

Q SESSDATE 58 Gives date and time at which session 58 was created.

Note: All session queries are for the current DB.



4-9

Command Syntax:

Q --+-- SESSComment --.| ||-- SESSUser -----|| |‘-- SESSDate -----+-- integer -->

4.7.4 Querying Session Number for a Given Time

Keywords: SESSION ON

Description: Lets you query which session was current at a given time. (This is theinverse of the Q SESSDATE option described in Section 4.7.3.)

Examples:

Q SESSION ON 12:00 22 August 1995

Q SESSION ON 9 / 9 /96Time defaults to 23:59, so returns last session number on given date.

Command Syntax:Q SESSION ON <date>

where <date> is a standard syntax graph, see Chapter 2. Remember that<date> actually specifies a time (to the nearest minute), so take care if you useany defaults here.

4.8 Using Multiwrite Databases

If a DESIGN DB has been created as a multiwrite database, several userscan write to it simultaneously, although they cannot change the same element.

Multiwrite databases can either be Standard multiwrite databases, orExtract databases. In both types, an element must be claimed before it canbe modified. Claiming an element prevents other users claiming (andmodifying) the element; the element must be unclaimed or released beforeanother user can change it.

Claiming can be either explicit, where the user must use the CLAIM commandbefore attempting to modify the element, or implicit, where the claim is madeautomatically when the user tries to modify the element. The claim mode is setwhen the DB is created. For full details see the PDMS ADMIN ReferenceManual.



Version 11.3

4-10

4.8.1 User Claims

Keywords: CLAIM UNCLAIM

Description: In a Standard multiwrite database, you must claim an element beforechanging it. This is known as a user claim. If the claim mode isexplicit (see below for details of how to check this), you must firstclaim each element that you want to modify using the CLAIM command.If the claim mode is implicit, the claim will be made automatically(although you can still give explicit CLAIM commands if you want toprevent other users claiming specific elements).

Only significant elements can be claimed, that is:

WORLD SITE ZONE EQUI SUBE PIPE BRAN STRU SUBSFRMW SBFR REST HANG SCTN GPWL PANE HVAC PTRARPLG

You can claim a specified element only, or a specified element plus allof the significant elements below it in the hierarchy. If the claimedelement is not a significant element, the significant element above itin the hierarchy will be claimed.

An element must be unclaimed before another user can claim it andchange it. User claims are always unclaimed when you changemodules or leaves PDMS, and you can also unclaim elements at anytime during a PDMS session using the UNCLAIM command.

Examples:

CLAIM /ZoneA /EQUIP100 /PIPE-100-AClaims named elements

CLAIM /ZoneA HIERARCHYClaims named element and all of its owned hierarchy

CLAIM /ELBOW-33Claims Branch which owns named component, since ELBO is not asignificant element

UNCLAIM /PIPE-100 /PIPE-200Unclaims named elements

UNCLAIM ALLUnclaims all elements currently claimed

Command Syntax:

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

>-- CLAIM ----*-- elementname --+-- HIERARCHY ---.| |‘----------------+-->



4-11

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

>-- UNCLAIM ---*-- elementname --+-- HIERARCHY ---.| | |`-- ALL ----------+----------------+-->

4.8.2 Notes on Standard Multiwrite DBs

• Elements cannot be claimed if recent changes have been made to them byother users. You must issue a GETWORK command first.

• Elements cannot be unclaimed if there are updates outstanding. Youmust issue a SAVEWORK command first.

• You can insert/remove significant elements in a members list withoutclaiming the owner. For example, you can add a Branch to a Pipe withoutclaiming the Pipe. Thus two users can add different Branches to thesame Pipe: any discrepancies will be resolved when a SAVEWORK isattempted.

• Before an element can be deleted, that element and all of its sub-hierarchy must be claimed.

• The following potential problems may not be revealed until you try tosave changes:

• If two concurrent users allocate the same name to differentelements, the second user to attempt a SAVEWORK will show up anerror. The second user must rename their element.

• If one user inserts a significant element into another element’s list,while a concurrent user deletes the latter element, an attempt toSAVEWORK will show up an error. Either the first user must deleteor move the significant element, or the second user must QUITwithout saving the deletion.

4.8.3 Extract Databases

Keywords: EXTRACT REFRESH ISSUE FLUSH RELEASE DROP

Description: Unlike standard multiwrite databases, extracts allow users to keepelements claimed when they exit from PDMS or change module. Theycan also be used, together with Data Access Control, to manageworkflow. See the PDMS ADMIN User Guide for more information.

An extract is created from an existing Database. When an Extract iscreated, it will be empty, with pointers back to the owing or masterdatabase. Extracts can only be created from Multiwrite databases, andall extracts are themselves Multiwrite. An extract can be worked on byone User at the same time as another user is working on the master or



Version 11.3

4-12

another extract.

When a user works on the extract, an extract claim is made as well asa user claim.

If the claim mode is explicit, the extract claim will be madeautomatically when you make a user claim using the CLAIMcommand. You can also claim to the extract only using the EXTRACTCLAIM command.

If an element is claimed to an extract, only users with write access tothe extract will be able to make a user claim and start work on theelement:

• If the databases are set up with implicit claim, when the usermodifies the element, the element will be claimed both to theextract and then to the user. If the element is already claimed tothe extract, then the claim will only be made to the user.

• If the databases are set up with explicit claim, then the user willneed to use the CLAIM command before modifying the element.

• Once a user has made a user claim, no other users will be able towork on the elements claimed, as in a normal multiwritedatabase.

• If a user unclaims an element, it will remain claimed to theextract until the extract claim is released or issued.

When an extract User does a SAVEWORK, the changed data will besaved to the Extract. The unchanged data will still be read viapointers back to the master DB. The changes made to the extractcan written back to the master, or dropped. Also, the extract canbe refreshed with changes made to the master.

Examples:

EXTRACT CLAIM /STRU1 /STRU2 /STRU3Claims named elements to the extract

EXTRACT CLAIM /STRU1 /STRU2 /ZONE-A HIERARCHYClaims the named elements, and all the elements in the hierarchy tothe extractThe HIERARCHY keyword must be the last on the command line. It willattempt to claim to the extract all members of the elements listed inthe command which are not already claimed to the extract.

EXTRACT FLUSH DB PIPE/PIPEWrites all changes to the database back to the owing extract. TheExtract claim is maintained.

EXTRACT FLUSH /STRU1 /STRU2 /STRU3Writes the changes to the named elements back to the owing extract.The Extract claim is maintained.



4-13

EXTRACT ISSUE DB PIPE/PIPEWrites all the changes to the database back to the owning extract andreleases the extract claim

EXTRACT ISSUE /ZONE-A HIERARCHYWrites all the changes to the named element and all elements under itin the hierarchy back to the owning extract and releases the extractclaim

EXTRACT ISSUE /STRU1 /STRU2 /STRU3Writes the changes to the named elements back to the owning extractand releases the extract claim

EXTRACT RELEASE DB PIPE/PIPEReleases the extract claim: this command can only be given to releasechanges that have already been flushed.

EXTRACT RELEASE /STRU1 /STRU2 /STRU3Releases the extract claim: this command can only be given to releasechanges that have already been flushed.

EXTRACT RELEASE /ZONE-A HIERARCHYReleases the extract claim to the named element and all: elementsunder it in the hierarchy.

EXTRACT DROP DB PIPE/PIPEDrops changes that have not been flushed or issued. The user claimmust have been unclaimed before this command can be given.

EXTRACT DROP DB PIPE/PIPEDrops changes that have not been flushed or issued. The user claimmust have been unclaimed before this command can be given.

The elements required can be specified by selection criteria, using a PMLexpression. For example:

EXTRACT CLAIM ALL STRU WHERE (:OWNER EQ ‘USERA’) HIERARCHY

Command Syntax:

>- EXTRACT -+- FLUSH ---------------.| ||- FLUSHWithoutrefresh -|| ||- RELEASE -------------|| ||- ISSUE ---------------|| ||- DROP ----------------| .-------<-------.| | / |`- REFRESH -------------+--*-- elementname --+- HIERARCHY -.

| || || |`-- DB dbname ---------------------+->



Version 11.3

4-14

4.8.4 How to Find Out What You Can Claim

Keywords: Q CLAIMLIST

Description: Before you start work on an extract, you should do a GETWORK andan EXTRACT REFRESH, which will ensure that you have an up-to-date view of the database.

This section explains what different users will see as a result of QCLAIMLIST commands.

For this example, take the case of a database PIPE/PIPE, accessed byUSERA, with two extracts. Users USERX1 and USERX2 are workingon the extracts.

USERA creates a Pipe and flushes the database back to the owningdatabase, PIPE/PIPE. The results of various Q CLAIMLIST commands bythe three Users, together with the extract control commands whichthey have to give to make the new data available, are shown in theFigure 3-1.

Note:

Q CLAIMLIST EXTRACTtells you what you can flush

Q CLAIMLIST OTHERStells you want you can't claim

DB PIPE/PIPEX1

USERX1

DB PIPE/PIPE-X2

USERX2

DB PIPE/PIPE

USERA



4-15

Figure 3-1 Querying extract claimlists

When you create an element, PDMS only sees it as a user claim, notan extract claim, until the element is flushed. It will then be reportedas an extract claim (as well as a user claim, if it has not beenunclaimed).

Note that a change in the claim status of an existing element will beshown by the appropriate Q CLAIMLIST command as soon as appropriateupdates take place, but a user will have to GETWORK as usual to seethe changes to the Design model data.

We recommend that:

USERX1 creates PIPE-100

EXTRACT FLUSH DB PIPE/PIPE

Q CLAIMLIST:none

Q CLAIMLIST OTHER:none

Q CLAIMLIST EXTRACT:/PIPE-100

USERA:

EXTRACT REFRESH DB PIPE/PIPE

Q CLAIMLIST:none

Q CLAIMLIST OTHER:/PIPE-100 Extract PIPE/PIPE_EX7001

Q CLAIMLIST EXTRACT:/PIPE-100

USERX2:

EXTRACT REFRESH DB PIPE/PIPE

Q CLAIMLIST:none

Q CLAIMLIST OTHER:/PIPE-100 Extract PIPE/PIPE_EX7001

Q CLAIMLIST EXTRACT:none

Note that USERX2 must useQ CLAIMLIST OTHER(not Q CLAIMLIST EXTRACT) to see theclaim



Version 11.3

4-16

• Before you make a user or extract claim, you should do anEXTRACT REFRESH and GETWORK.

• If you need to claim many elements to an extract, itimproves performance if the elements are claimed in asingle command, for example, by using a collection:

EXTRACT CLAIM ALL FROM !COLL

Examples:

Q DBNAMEReturns the name of the database which you are actually writing to.

Q CLAIMLISTOutputs a list of all elements currently claimed by yourself:

Q CLAIMLIST OTHEROutputs a list of all elements currently claimed by other users who areaccessing the same DB:

Q CLAIMLIST EXTRACTShows the extract claimlist for all the writable extracts in the MDB.

Q CLAIMLIST EXTRACT DB dbnameShows the extract claimlist for the named extract DB.

Q CLAIMLIST EXTRACT FREE DB dbnameShows the elements claimed to the current extract and not claimed toanother extract or user. That is, the elements which can be released

Q CLAIMLIST EXTRACT OTHER DB dbnameShows the elements claimed to the current extract and claimed toanother extract or user.

Q CLAIMLIST CONTROL DB dbnameShows the extract claimlist for a CONTROLLED named extract DB.

Q DBACQueries the access mode of the database. DBAC is a pseudo-attributewhich can have the text settings CONTROL, UPDATE orMULTIWRITE.

Q DBCLQueries the claim mode of the database. DBCL is a pseudo-attributewhich can have the text settings EXPLICIT or IMPLICIT.

Q LCLMQueries whether or not the current element is claimed by anotheruser. Returns TRUE or FALSE.



4-17

Command Syntax:

>-- Q CLAIMLIST --+- OTHER -----.| ||- EXTRACT ---+- OTHER --.| | || |- FREE ---|| | || `----------|| ||- CONTROL --------------|| ||------------------------+-- DB dbname --.| |`----------------------------------------+-->

4.9 Comparing Database Changes

4.9.1 Comparing Database States at Different Times

You can compare details of your current database settings with thecorresponding settings at a specified earlier time and generate a report listingall differences. The types of change reported include:

• Creation and deletion of elements.

• Changes to the attribute settings of elements.

• Changes in the list order for BRANCH, POGON, DRAWI and BOUNDelements.

Keywords: DIFFERENCE SINCE

Description: Lets you report all changes to one or more specified database elementssince an earlier version of that database. The output is in the form of areport listing all elements and attributes which have changed, withtheir old and new values. The report can be sent to a file by using theALPHA FILE or ALPHA LOG commands.

Note: The database states are compared between SAVEWORK operations.For example, if you last saved your design changes at 9:30 and ask fora comparison since 10:00, the current settings will be compared withthose at 9:30.

Examples:

DIFFERENCE ALL BRANCH FOR /ATEST SINCE 21 JANUARY

DIFF CE SINCE 10:00Assumes current day.

DIFF /ZONE1 Compares current settings with those at yourlast SAVEWORK command.



Version 11.3

4-18

DIFF SITE SINCE SESSION 66Compares current settings with those at theend of session 66 of the current database.

Command Syntax:

>- DIFFerence <selele> SINCE -+- <date/time> -+-----------------------.| | ||- LATEST ------| || | ||--SESSION nn --| || | |`---------------+- EXTRACT -+- extname -|

| |`- extno ---+->

4.10 Creating Database Update Macros

The OUTPUT command produces macros which can be re-input to recreate ormodify specified parts of the DESIGN DB. You can include only the elementswhich have been changed since a specified time (i.e. those elements whichwould be listed by the DIFFERENCE command). The output is generated inthree stages:

1. Any elements which were originally locked are unlocked. Elementdeletions, name changes and type changes are output. Note thatreordering or insertion of elements in their owner’s members list istreated as deletion followed by creation, so that Refno attribute settingsmay be changed.

2. Newly created elements and all standard attribute settings are output.

3. Reference attribute settings and rules are output. Elements which wereoriginally locked are relocked and GADD commands are included if anyelements were included in Groups.

Keywords: OUTPUT CHANGES SINCE

Description: Lets you output all changes to one or more specified databaseelements since an earlier version of that database. The output is in theform of a macro which can recreate the changes when run on, say, acopy of the original DB. The macro is sent to a file by using thestandard ALPHA FILE or ALPHA LOG commands.

Examples:

OUTPUT /ZONE-AOutputs all elements, whether or not they have ever been changed.

OUTPUT ALL PIPE FOR /ZONE CHANGES SINCE 21 JANUARYOutputs all changes to named element and its members since thegiven date.



4-19

OUTPUT /PIPE-100 CHANGES Outputs all changes to named element and its members since lastSAVEWORK command.

OUTPUT /PIPE-1 CHANGES SINCE EXTRACTIn an extract database, outputs all changes since the extract wascreated.

OUTPUT /PIPE-1 CHANGES SINCE LATEST EXTRACTIn an extract database, outputs all changes compared with the latestversion of the parent extract.

OUTPUT /PIPE-1 CHANGES SINCE EXTRACT 44OUTPUT /PIPE-1 CHANGES SINCE EXTRACT PIPE/PIPE-X1

In an extract database, outputs all changes compared with the latestversion of the given extract, which must be higher in the extracthierarchy.

OUTPUT /PIPE-1 CHANGES SINCE SESSION 77 EXTRACT 44OUTPUT /PIPE-1 CHANGES SINCE OCT 2000 EXTRACT PIPE/PIPE-X1

In an extract database, outputs all changes compared with the givenextract, which must be higher in the extract hierarchy, at the givensession or date.

The macro is sent to a file by using the standard ALPHA FILE or ALPHA LOGcommands (see Section 3.3).

You can also give a PDMS session number. The database states are comparedbetween SAVEWORK operations. For example, if you last saved your designchanges at 9:30 and ask for a macro containing changes since 10:00, the macrowill contain all changes since 9:30.

Command Syntax:

>- OUTPUT <selele> SINCE -+- <date/time> -+-----------------------.| | ||- LATEST ------| || | ||--SESSION nn --| || | |`---------------+- EXTRACT -+- extname -|

| |`- extno ---+->

4.11 Inter-DB Connection Macros

Access to a DB is usually controlled in such a way that only one user canmodify the content of that DB at any one time; that is, only one user can haveWrite access to the DB. Other users may have simultaneous Read access,depending how access rights have been set up in the ADMIN module. (See alsoSection 4.9, which describes a new multiwrite DB facility.)

In a multi-disciplinary PDMS project, in which different teams of users workon different aspects of the design, an individual user will usually have



Version 11.3

4-20

Read/Write access to the DBs controlled by their own team and Read-onlyaccess to DBs controlled by other teams. This works well until a user needs toconnect an item in their team’s DB to an item in another team’s DB; forexample, a member of the Piping team may wish to connect a Branch in aPiping DB to a Nozzle in an Equipment DB (to which they have Read-onlyaccess). In such a case, the design changes needed in the Equipment DB arestored in a ‘buffer’ file known as an inter-DB connection macro. Only whenthis macro is run by a member of the Equipment team, with Write access tothe Equipment DB, are the changes implemented.

The sequence of events which would occur is illustrated in the followingexample.

Assume that Project ABC has separate Piping and Equipment design teams.Assume that User P has Read/Write access to a Piping DB and Read-onlyaccess to an Equipment DB, while User E has Read/Write access to theEquipment DB and Read-only access to the Piping DB.

User P wishes to connect a Branch Tail in their Piping DB to a Nozzle in UserE’s Equipment DB; that is, they wish to set the Branch’s TREF in their PipingDB to point to the CREF of the Nozzle (which they can do) and to set the CREFof the Nozzle to point to the TREF of their Branch (which they can not do),thus:

TREF CREFBranch in Piping DBowned by User P'steam

Nozzle inEquipment DBowned by UserE's team

Only User Ecan set this

Only User Pcan set this

• User P sets the TREF of their Branch to point to the CREF of the Nozzlein the Equipment DB.

• When User P tries to set the Nozzle’s CREF, they receive a messagetelling them that they are trying to connect to a read-only DB and thatan inter-DB connection macro is being created automatically. This macro,which stores the commands needed to set the CREF, is given a namewith the format abc001.mac (where the macro number, 001 here, isallocated sequentially), and is held in the directory ABCMAC (or asdefined by the project’s environmental variables).

• When User E next enters MONITOR (usually when entering or leavingPDMS), they receive a message asking them to run the inter-DBconnection macro abc001.mac and to delete it when they have done so.

• User E enters DESIGN and runs the inter-DB connection macro bygiving the command

$M /%ABCMAC%/abc001.mac



4-21

This sets the CREF for the Nozzle to point to the TREF of the Branchand completes the link between the two DBs.

• User E enters MONITOR (or ADMIN if they have sufficient accessrights) and deletes the redundant macro by giving the command

DELETE MACRO 1

where 1 is the macro number.

Note: If User P checks their DB for data consistency errors between Stages 2and 4, when the macro has been created but not yet run, they will getan ‘incompatible connection reference’ message. They cannot finalisetheir design until User E has run the macro. Thus, the successful useof inter-DB connection macros relies on good co-operation between theteams involved.Inter-DB connection macros are also created in multiwrite DBs if anattachment is claimed by another user.


5 Display

The commands described in this chapter control how the items are displayed ina 3D (Volume) View. For information about creating View windows, see theCadcentre Software Customisation Guide and the Cadcentre SoftwareCustomisation Reference Manual.

5.1 Adding Elements to the Display

Keywords: ADD COLOUR

Description: Allows selected Design items to be added to the Draw List, whichdefines which elements are to be displayed. If an element is to bedisplayed in a colour which is different from the default colour, thiscan be specified as part of the command line.Items added to the display are added to all volume views with thescale and view direction appropriate to that view.

The Draw List can contain significant elements only. Significantelements in DESIGN are:

EQUI SUBE DATU GRDM PTRA BOUN

BRAN HANG PVOL* RPLA* STRU SUBS

SCTN PNOD PALJ PANE

(* only if directly below a Site or Zone.)

If an element below a significant element (i.e. a primitive) is added,then the whole significant element will be added as well.If an element above a significant element (e.g. a PIPE) is added, thenall significant elements owned by that element will be added; not thehigh-level element itself.

Examples:

ADD /P100A /P100A is added to the Draw List

ADD CE The current element will be added to the DrawList

ADD /ZONE1 /ZONE2 COLOUR 5/ZONE1 and /ZONE2 will be added in colour 5.If you wish to add items in other colours, youmust use separate commands.

Display


Version 11.3

5-2

Command Syntax:

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

>-- ADD --*-- <selatt> --+-- COLour <colno> -->|‘-->

where:

<colno> = >--+-- integer --.| ||-- ACTive ---|| ||-- VISIble --|| ||-- CE -------|| ||-- CLASH ----|| ||-- OBST -----|| |‘-- AIDS -----+-->

Querying:

Q DRAW Queries the contents of the Draw List

Q DRAW COUNT Queries the number of items in the Draw List

Q DRAW FULL Queries the contents of the Draw List and thecolour with which each Draw List member wasadded

5.1.1 Selecting Graphics Colours Automatically

Keywords: AUTOCOLOUR

Description: Lets you define a set of rules for automating the selection of colours foritems added to graphical views. Each rule consists of a set of selectioncriteria for particular types of element, together with an associatedcolour (which may be an explicit colour number or an expression).

When an element is added to the drawlist, the selection rules arescanned in sequence until a rule is found to be true for that element.The element is then added in the colour corresponding to that rule. Ifthe colour is invalid, the search is continued. If no rule is true for theelement, the default colour is used. The order in which the rules areset up is significant, since the first rule found to be true determinesthe colour.

Automatic colour selection may be switched on or off as required. If itis on, the colour specified by the rule is used rather than any other

Display


5-3

colour entered as part of the ADD command. If dynamic autocolouringis specified, the autocolour will be checked every time an attribute ischanged and, if necessary, the relevant element will be readded in thecurrent colour.

Each autocolour may be drawn either as a solid colour (default) or as atranslucent shade. If using translucency, you can also specify whetheror not the edges of an item should be drawn (as in wireline mode) togive a more distinct outline.

Examples:

AUTOCOLOUR ALL EQUI COLOUR 4All Equipment items to be added in colour 4

AUTOCOLOUR ALL EQUI COLOUR 4 TRANSLUCENCY 25 EDGES ONAll Equipment items to be added in colour 4with 25% translucency and edges drawn.

AUTOCOLOUR ALL BRAN WITH (HBORE GT 100) COLOUR 10All Branches with head bores greater than 100to be added in colour 10.

AUTOCOLOUR ALL SCTN COLOUR (:COLOUR OF SPRE)All Sections to be added as defined by the UDA:COLOUR derived via their SpecRefs.

AUTOCOLOUR ALL COLOUR (:COLOUR)Uses the UDA :COLOUR to denote the colourfor all displayed elements. If you enter this asthe final rule, it will provide a default colour ifall other rules prove false.

AUTOCOLOUR ON Colours will be chosen according to autocolourrules. If Off (the default), colour specified in theADD command will be used.

AUTOCOLOUR DYNAMIC ONUpdates autocolour each time an attributechanges. (Use with care!)

AUTOCOLOUR RESETClears all current autocolour rules.

AUTOCOLOUR REMOVE 2Removes the second rule from the current list.

AUTOCOLOUR REORDER 2 TO 4Moves rule number 2 to position 4 in the list.

Display


Version 11.3

5-4

Command Syntax:

>- AUTOCOLOUR -+- selection_rule - COLOUR - expression -+->| || .-----------------------<--------------'| || '- TRANSLucency - expression -+->| || '- EDGES - ON/OFF ->|- ON/OFF ->||- DYNAMIC - ON/OFF ->||- RESET ->||- REMOVE - integer ->|‘- REORDER - integer1 - TO - integer2 ->

NOTE: The expression for Translucency must be in the range 0–99: the actualtranslucency will be set to the nearest of 12, 25, 37, 50, 62, 75 or 87(0 = transparent; 99 = opaque).AUTOCOLOUR ON must be in force to see the effect of AUTOCOLOURDYNAMIC ON.

Querying:

Q AUTOCOLOUR NUMberGives number of colour rules.

Q AUTOCOLOUR MODEQueries autocolour mode; i.e. On or Off.

Q AUTOCOLOUR integerGives selection criteria for rule integer.

Q AUTOCOLOUR DYNAMICChecks whether dynamic updating is on or off.

Q AUTOCOLOUR FOR id COLOURQueries colour that would be selected foridentified element (this is of most use for batchtesting).

Q AUTOCOLOUR FOR id TRANSLUCENCYQueries translucency setting for identifiedelement.

Q AUTOCOLOUR FOR id EDGESQueries whether or not edges are to be drawnfor identified element (only relevant iftranslucency is being applied).

Display


5-5

5.1.2 Removing Elements from the Display

Keywords: REMOVE

Description: These commands remove elements from the Draw List and thedisplay.

Examples:

REMOVE /BRANCH1 /BRANCH1 will be removed from the Draw Listand the display

REM SITE /PIPING The site /PIPING will be removed

REM ALL All items in the Draw List, and on the screen,will be removed

Note: If an element below a significant element (i.e. a primitive) isremoved, then the whole significant element will be removed as well.This is because the Draw List may only contain significant elements.Significant elements are EQUI, SUBE, DATU, GRDM, PTRA, BOUN,BRAN, HANG, PVOL*, RPLA*, STRU, SUBS, SCTN, PNOD, PALJ,PANE. (* only if directly below a Site or Zone.)

Command Syntax:

>-- REMove -- <selatt> ------>

5.1.3 Defining Colours

Keywords: COLOUR ACTIVE CE VISIBLE CLASH OBST AIDS

Description: These commands allow colours to be defined so that different types ofitem in the display may be distinguished by means of colour. Certainitems such as current element and active element colours have defaultsettings, but these may also be redefined.

The colours may be assigned by using the COLOUR command to definethe Red-Green-Blue mix for a colour number or to assign a predefinedcolour mix by name. DESIGN allows the use of 115 user-definablecolours, plus some specific ones which are assigned to items whichneed to be readily distinguishable in the display.

Definitions:

• The Active element is the significant element (and its components)being worked on.

Display


Version 11.3

5-6

• The Current Element (CE) is the actual element currently beingaccessed.

• The Visible design consists of the design elements which you wish to bedisplayed (but which you are not currently working on).

• A Clashing element is an element whose current position and geometryare being tested for interferences against other elements in the designand which has been found to clash (see Chapter 15).

• An Obstructing element is any of the elements in the design againstwhich a clashing element is being tested for interferences and which hasbeen found to clash (see Chapter 15).

• An Aid includes tags (markers), axes and other graphical annotations.

The predefined colour mixes which you may specify by name are as follows:

Colour Red Green Blue Colour Red Green Blue

black 0 0 0 springgreen 0 100 50white 100 100 100 green 0 80 0whitesmoke 96 96 96 forestgreen 14 56 14ivory 93 93 88 darkgreen 18 31 18grey 66 66 66 cyan 0 93 93lightgrey 75 75 75 turquoise 0 75 80darkgrey 32 55 55 aquamarine 46 93 78darkslate 18 31 31 blue 0 0 80red 80 0 0 royalblue 28 46 100brightred 100 0 0 navyblue 0 0 50coralred 80 36 27 powderblue 69 88 90tomato 100 39 28 midnight 18 18 31plum 55 40 55 steelblue 28 51 71deeppink 93 7 54 indigo 20 0 40pink 80 57 62 mauve 40 0 60salmon 98 50 44 violet 93 51 93orange 93 60 0 magenta 87 0 87brightorange 100 65 0 beige 96 96 86orangered 100 50 0 wheat 96 87 70maroon 56 14 42 tan 86 58 44yellow 80 80 0 sandybrown 96 65 37gold 93 79 20 brown 80 17 17lightyellow 93 93 82 khaki 62 62 37lightgold 93 91 67 chocolate 93 46 13yellowgreen 60 80 20 darkbrown 55 27 8

Display


5-7

The default colour assignments are:

Colour No Colour

Active design orangeCurrent element yellowVisible design lightgreyClashing element redObstructing element tomatoAids blue1 grey2 red3 orange4 yellow5 green6 cyan7 blue8 violet9 brown10 white11 pink12 mauve13 turquoise14 indigo15 black16 magenta

Examples:

COL 5 DARKGREENColour 5 will be changed to dark green

COL 3 MIX RED 50 GRE 50 BLU 5Colour 3 will change to the specified mix of red, green and blue

COL ACTIVE BRIGHTREDSets the colour for displaying active elements to bright red

Note: When colours are mixed in their Red, Green and Blue constituents, thecommand line must contain values for all three constituents in thecorrect order. The numbers entered for the relative proportions of thebasic colours must each be in the range 0-100, but they are notpercentages of the overall colour and so do not need to add up to 100.

Display


Version 11.3

5-8

Command Syntax:

>- COLour -+- integer -.| ||- ACTive --|| ||--AIDS-----|| ||- VISIble -|| ||- CE ------|| ||- CLASH ---|| |‘- OBST ----+-- colour_name --->

|‘-- MIX RED integer GREen integer BLUe integer ->

where colour_name is the name of any of the predefined colour mixes listedabove.

Querying:

>-- Q COLour --+-- integer -----.| ||-- CE ----------|| ||-- ACTive ------|| ||-- VISIble -----|| ||-- CLASH -------|| ||-- OBST --------|| |‘-- AIDS --------+-->

5.2 Element Representation

There are a number of options which determine how items in the graphicaldisplay are to be shown on the screen. These are controlled by theREPRESENTATION command.

5.2.1 Setting Tube Representation for Piping Components

Keywords: REPRESENTATION TUBE CL (CENTRELINE)

Description: The REPRESENTATION command allows tubing to be represented in acentreline or as a solid tube. In some cases, it helps to switch betweenthe two representations to simplify an otherwise complicated view.

TUBE and CENTRELINE representation are not instantly updated onthe screen. To see the effects of a representation change, it is

Display


5-9

necessary to replace the affected items in the Draw List by Removingand Adding them.

Examples:

REPR TUBE ON CL OFFSets tubing representation as solid tube.

REPR CL ON TUBE OFFSets tubing representation as centreline.

REPR TUBE ON CL ONSets both types of representation on (but centreline will not be visible incolour-shaded mode, as it will be hidden by solid tube).

Command Syntax:

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

>-- REPResentation --*-- CL -------------------------. || | ||-- CENTreline -----------------| || | |‘-- TUbe -----------------------+-- ON ---|

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

Querying:

Q REPR TUBE

Q REPR CL

Q REPR PROF

Q REPR Queries all Representation options.

5.2.2 Setting Profile Representation for Steelwork

Keywords: REPRESENTATION PROFILE

Description: The REPRESENTATION PROFILE commands allow structural steelprofiles to be represented in a centreline or solid profile format. Insome cases, it helps to switch between the two representations tosimplify an otherwise complicated view.

TUBE and CENTRELINE representation are not instantly updated onthe screen. To see the effects of a representation change, it isnecessary to replace the affected items in the Draw List by Removingand Adding them.

Display


Version 11.3

5-10

Examples:

REPR PROF ON CL OFFSets profile representation as solid profile.

REPR PROF CL ON TUBE OFFSets profile representation as centreline.

REPR PROF ON CL ONSets both types of representation on.

Command Syntax:

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

>-- REPResentation --*-- PROFile --+-- CL -----------. || | ||-- CENTreline ---| || | ||-- OBSTruction --| || | |‘-- INSUlation ---+-- ON ---|

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

Querying:

Q REPR PROF TUBE

Q REPR PROF CL

Q REPR Queries all Representation options.

5.2.3 Setting Drawing Level Representation

Keywords: REPRESENTATION LEVEL

Description: This command enables individual drawing levels to be specified for thedisplay of piping, nozzles, structural elements and other designdatabase elements.

Every basic primitive shape in the design has an associated drawinglevel range attribute (for piping and structural steelwork components,these are stored in the Catalogue). If the specified drawing levelcoincides with this range, the 3D object will be drawn when it is addedto the Draw List.

The practical effect of this facility is that it allows you to minimisevisible detail when representing Design items. For example, atdrawing level 3 steelwork may be represented as single line only,whereas at level 1 the full detail may be visible. Level 3 may well beadequate for design purposes.

Display


5-11

LEVEL manipulation is not instantly updated on the screen. To seethe effects of a level change, it is necessary to replace the affecteditems in the Draw List by Removing and Adding them.

Examples:

REPR LEVEL PIPE 5Sets piping level to 5. All pipes which are added after this command will bedrawn at level 5. Those already in the view will remain unchanged.REPR LEVEL NOZZ 1Sets Nozzle level to 1REPR LEVEL 2Set level for all other Component types to 2

Command Syntax:

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

>- REPResentation --*-- LEVel --+-- PIPE -------. || | ||-- NOZZle -----| || | ||-- STRUcture --| || | |‘---------------+-- integer --+->

Querying:

Q REPR Lists all REPRE options

Q REPR LEVEL Lists levels at which other Components are drawn

Q REPR LEV PIPE Gives the level at which pipes are drawn

Q REPR LEV NOZZ Gives the level at which Nozzles are drawn

Q DISPLAY Gives units and tolerance settings, as well asrepresentation levels

5.2.4 Setting Obstruction and Insulation Representation

Keywords: REPRESENTATION OBSTRUCTION INSULATION TRANSLUCENCY

Description: Component Obstructions are often given LEVELS or TUBE andCENTRELINE settings which render them invisible. Setting theRepresentation of OBST On forces the system to override normalLEVEL and TUBE settings and show all of the primitives, regardlessof the other settings.

Setting the Representation of INSU On or Off determines whether ornot insulation is shown on primitives.

Display


Version 11.3

5-12

These have the effect of considering all primitives which have anobstruction level greater than zero and all primitives which areaffected by insulation parameters. As with changes to LEVELrepresentation, the graphics display is not updated instantly. Itemsmust be removed and re-added to the Draw List to become visible.

To avoid obscuring the view in colour-shaded mode, obstruction and/orinsulation can be shown as translucent, the degree of translucencybeing controllable.

Examples:

REPR OBST ON INSU OFF

REPR INSU ON

REPR INSU ON TRANSLUCENCY 25

Command Syntax:

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

>- REPResentation -*- OBSTruction -. || | |‘- INSUlation --+- ON --+------------------------|

| | || '- TRANSLucency - value -|| |‘- OFF --------------------------+->

NOTE: value must be in the range 0–99: the actual translucency will be set tothe nearest of 25, 50, 75 or 87 (0 = transparent; 99 = opaque).

Querying:

Q REPR Lists all Representation settings

Q REPR INSU Queries if insulation is ON or OFF

Q REPR OBST Queries if OBST is ON or OFF

Q REPR INSU TRANSLQueries translucency setting for insulation

5.2.5 Setting P-Point Representation

Keywords: REPRESENTATION PPOINTS LENGTH NUMBERS

Description: P-point representation may be set to ON or OFF. The default setting isPPOINTS OFF, although p-points will be shown automatically as partof an identification operation.

Display


5-13

When p-points are on, they are drawn as small arrows with a cross atthe p-point position and with the arrow indicating the p-pointdirection. The size of the arrow is controlled by the LENGTH option. P-point numbers may also be displayed, as controlled by the NUMBERSoption.As with changes to other representation settings, the graphics displayis not updated instantly. Items must be removed and re-added to theDraw List before changes to the display of p-points becomes visible.

Examples:

REPR PPOINTS ONSets the p-point representation to ON

REPR PPOINTS LENGTH 5Sets size of p-point arrows

REPR PPOINTS NUMB ONShows p-point numbers

Command Syntax:

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

>-- REPResentation --*-- PPoints --+-- ON ---|| ||-- OFF --+-->||-- LENgth -- value -->|‘-- NUMbers --+-- ON ---.

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

Querying:

Q REPR PPOINTS

5.2.6 Setting Structural Node Representation

Keywords: REPRESENTATION PNODES SNODES

Description: These options allow Primary and/or Secondary Nodes on structuralsteelwork items to be shown on the display in specified colours andsizes.By default, both types of node are shown in the current visible colour,with a size equivalent to 10mm diameter.

Examples:

REPR PNOD ONOnly Primary Nodes will be shown in the display.

Display


Version 11.3

5-14

REPR SNOD OFFThe display of Secondary Nodes will be suppressed.

REPR PNOD COL BRIGHTREDPrimary Nodes will be shown in bright red colour.

REPR SNOD COL 12Secondary Nodes will be shown in the currently defined mix for colournumber 12.

REPR PNOD SIZE 15REPR SNOD SIZE 6Primary Nodes will be emphasized by being drawn at 15mm diameter,while Secondary Nodes are drawn at only 6mm diameter.

Command Syntax:

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

>-- REPResentation --*-- PNODes --. .-------------------. || |/ | |‘-- SNODes --*-- ON ---------------| |

| | ||-- OFF --------------| || | ||-- SIZe <uval> ------| || | |‘-- COLour <colour> --+--+-->

Querying:

Q REPR PNOD

Q REPR PNOD SIZE

Q REPR PNOD COL

Q REPR SNOD

Q REPR SNOD SIZE

Q REPR SNOD COL

5.2.7 Setting P-Line Representation

Keywords: REPRESENTATION PLINES LENGTH PKEY

Description: P-line representation for structural Sections may be set to ON or OFF.The default setting is PLINES OFF.

When p-lines are on, the size of the arrow showing their direction iscontrolled by the LENGTH option. P-line identifiers, in the form of thesettings of their PKEY attributes (TOS, BOS, NA, etc.) may also bedisplayed, as controlled by the PKEY option.As with changes to other representation settings, the graphics display

Display


5-15

is not updated instantly. Items must be removed and re-added to theDraw List before changes to the display of p-lines becomes visible.

Examples:

REPR PLINES ONSets the p-line representation to ON

REPR PLINES LENGTH 6Sets size of p-line arrows

REPR PLINES PKEY ONShows p-line identifiers (settings of PKEY attributes)

Command Syntax:

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

>-- REPResentation --*-- PLINes --+-- ON ---|| ||-- OFF --+-->||-- LENgth -- value -->|‘-- PKEY --+-- ON ---.

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

Querying:

Q REPR PLINES

Display


Version 11.3

5-16

5.2.8 Setting Holes Representation

Keywords: REPRESENTATION HOLES

Description: Determines the appearance of holes in volume views. ON gives a morerealistic view of a hole, with objects behind the hole being visiblethrough it. OFF represents holes as patterned regions on the surfaceof the component.

Examples:

REPR HOLES ONSets the holes representation to ON

Command Syntax:

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

>-- REPResentation --*-- HOLes ---+-- ON ---|| |‘-- OFF --+-->

Querying:

Q REPR HOLES

5.2.9 Setting Arc Tolerance Representation

Keywords: REPRESENTATION DARCTOLERANCE

Description: Controls the arc tolerance used when representing certain curves aspolygon segments or facetting planes. The smaller the arc tolerance,the smoother the curve drawn, but the slower the graphicalperformance.The tolerances used for most curve drawing in DESIGN are controlledautomatically by the graphical system. The REPRE DARC commandcontrols the following aspects only:

• Filleted vertices used in the representation of extrusions; forexample, Section Profiles from the Catalogue, Panel Loops, etc.

• Items which include holes (but only when REPRE HOLES is set toOn; see Section 5.2.8).

The default setting is 10 mm. The minimum permitted setting is 1mm.

Display


5-17

Example:

REPR DARC 5Sets the arc tolerance to 5 mm.

REP DARC DEFResets arc tolerance to 10 mm.

Command Syntax:

>-- REPResentation -- DARCtolerance --+-- <uval> ---.| |‘-- DEFault --+-->

Querying:

Q REPR DARC

5.2.10 Refreshing the Graphical View

Keywords: REPRESENTATION UPDATE

Description: Lets you refresh the graphical display, after modifying any of therepresentation settings, without having to remove and add back allitems in the drawlist.

Examples:

REPR UPDATE

Command Syntax:

>-- REPResentation -- UPDATE -->

5.3 Specifying Axes

Keywords: AXES

Description: Lets you specify and position a set of axes on the display. The axesrepresent the compass directions of the World co-ordinate system andmay be positioned anywhere on the display.

Axes remain visible until they are switched off or deleted. Switchingaxes off renders them invisible, whilst deletion removes themaltogether. Switched-off axes can be made visible again by switchingthem back on.

Display


Version 11.3

5-18

Examples:

AXES AT @Positions a set of axes at the graphics cursor

AXES HEIGHT 300 AT @Positions a new set of axes at the graphics cursor, with a height of 300mm(default size is 1000mm)

AXES OFFRemoves axes from the screen (although they still exist)

AXES ONRedisplays axes as previously shown.

AXES DELETEDeletes axes (i.e. AXES ON will have no effect)

Command Syntax:

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

>-- AXEs --*-- HEIght value -----------------------|| ||-- AT <bpos> --------------------------|| ||-- AT POLar <bdir> DISTance <uval> ---'||-- AT @ ----.| ||-- ON ------|| ||-- OFF -----|| ||-- DELete --|| |‘------------+----------------------------->

5.4 Graphical Labelling of Design Elements

Keywords: MARK UNMARK

Description: This facility allows specific design elements or lengths of Tube to belabelled in the display.

Frequently referenced items may be marked with a constant graphiclabel which will stay with that item even if it is moved or rescaled.Items can also be unmarked (which removes the label).

Labels are shown in all permitted regions where the item’s origin iswithin the current sub-view. The label always points to the origin or,in the case of a Branch or Hanger, to its Head or Tail (where the namewill be suffixed with + or – respectively).

Display


5-19

You can specify selection criteria for marking, and specify any textualexpression for the marker.

Examples:

MARK /DATUM5Element /DATUM5 will be labelled with its name.

UNMARK /DATUM5The specified element will cease to be labelled.

MARK WITH ’Outer Boundary’ ID @Labels the picked element with the given text.

MARK WITH NAME ALL BRANLabels all Branches with their PDMS names.

MARK WITH NAME OF SPREF ALL VALVE WHERE PBORE GT 100Labels all valves larger than the specified bore with their specificationreferences in the catalogue.

UNMARK ALLRemoves all marking from the screen.

Command Syntax:

>-- MArk --+-- WITH -- text expression --.| |‘-----------------------------+-- <selatt> -->

>-- UNMark -- <selatt> -->

5.5 Using Design Aids

Keywords: AID LINE ARROW CEARROW ARC SPHERE BOX CYLINDER

Description: This facility lets you incorporate lines, arrows, arcs, spheres, boxes orcylinders in a view to help you with the design construction. Designaids can be grouped together (using the NUMBER option) and given anumber for identification.

Aid lines are drawn between two defined 3D positions. The linestylecan be solid, dashed, dotted or dash-dot, and you can label them withtext markers at defined positions.

Aid arrows are used to complement lines for showing dimensions etc.You can control both the overall height of an arrow and the proportionof its height occupied by the conical arrow-head, thus changing itsemphasis.

Display


Version 11.3

5-20

A special aid arrow, the CEArrow, is positioned automatically to pointto the current element. You can specify whether the arrow points tothe Origin (default), P-arrive or P-leave of the current element.NOTE: These terms relate primarily to piping components. For

other element types, they are interpreted in a logical way.For example, for a SCTN, Origin = P-arrive = POSS, P-leave= POSE; for a PANE, Origin = Vertex 1; for a VERT, Origin= vertex position; etc.

Aid arcs are defined in terms of two points at their extremities andeither a third 'through' point or a tangent point through which asecond-order Bezier curve is constructed.

Aid spheres are defined by the position of the centre and the radius.

Aid boxes are defined in terms of their position, orientation, andX,Y,Z dimensions. They may be drawn in wireline mode (like penaltyvolumes or clipping boxes) or in solid mode (like box primitives).

Aid cylinders are defined in terms of their position, orientation,diameter and height. They may be drawn in wireline or solid (filled)mode.

Examples:

AID LINE E1200S3500U0 TO E760N1200U50Draws a line between the two 3D positions.

AID LINE NUMBER 5 E1200S3500U0 TO E760N1200U50 LINESTYLEDOTTEDGroups the new line with other such lines with the same number (5 thisexample) and draws it in the dotted linestyle.

AID CLEAR LINE 5Deletes line number 5

AID ARROW AT E760N1200U50 DIR E HEI 100 PROP 0.5Positions 100mm arrow with given position and direction; arrow head is50mm long.

AID BOX POS PIN 6 ORI X IS UP Y TOWARDS /PUMP1 XLEN 200YLEN 200 ZLEN 200 FILL OFFPositions a wireline cubic box, with 200mm sides, at Pin 6 with the specifiedorientation.

AID CLEAR SPHERE UNNDeletes all unnumbered aid spheres.

Display


5-21

Command Syntax:

>- AID LINE -+--------------.| |‘- NUMber int -+- <bpos> TO <bpos> -+- LINEStyle -+- SOLId ---.

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

| ||- DOTTEd --|| |‘- DASHDot -+->

>- AID TEXT - NUMber int - text_expression - AT <bpos> ->

>- AID ARROW -+--------------.| |‘- NUMber int -+-- AT <bpos> -- DIRection <bdir> -.

|.----------------------------------------------’|‘- HEIght val -+------------------.

| |‘- PROPortion val -+->

>- AID CEARROW -+- ON/OFF ->|'- HEIght val -+------------------.

| |‘- PROPortion val -+- ARRIVE -.

| ||- LEAVE --|| |'- ORIGIN -+->

>- AID ARC -+--------------.| |‘- NUMber int -+- <bpos> TO <bpos> -+- TANPoint <bpos> -.

| |'- THRU <bpos> -----+->

>- AID SPHERE -+--------------.| |‘- NUMber int -+- <bpos> - DIAmeter <expre> ->

>- AID BOX -+--------------. .-------------------.| | / |‘- NUMber int -+-*- POSition <bpos> ---|

| ||- ORIentation <ori> -|| ||- XLENgth <expre> ---|| ||- YLENgth <expre> ---|| ||- ZLENgth <expre> ---|| |‘- FILLed -+- ON --. |

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

Display


Version 11.3

5-22

>- AID CYLinder -+--------------. .-------------------.| | / |‘- NUMber int -+-*- POSition <bpos> ---|

| ||- AT <bpos> ---------|| ||- ORIentation <ori> -|| ||- DIAmeter <expre> --|| ||- HEIght <expre> ----|| |‘- FILLed -+- ON --. |

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

>- AID CLEAR -+- ALL-------------------------.| ||- LINE -----. || | ||- ARROW ----| || | ||- CEARROW --| || | ||- ARC ------| || | ||- SPHERE ---| || | ||- BOX ------| || | |'- CYLInder -+- int --------. |

| | ||- ALL --------| || | |‘- UNNumbered -+--+->

Querying:

>- Q AID -+- LINE -----.| ||- ARROW ----|| ||- CEARROW --|| ||- ARC ------|| ||- SPHERE ---|| ||- BOX ------|| |'- CYLInder -+- integer ----.

| ||- UNNumbered -|| |‘- ALL --------+->

Note: Q AID ARC lists arcs using the THRU (not TANP) definition, since allarcs may be represented in this way.

Display


5-23

>- Q AID - NEXT -+- LINEnumber -----.| ||- ARROWnumber ----|| ||- ARCnumber ------|| ||- SPHEREnumber ---|| ||- CYLIndernumber -|| |'- BOXnumber ------+->

(Gives next available aid number for specified type)

Display


Version 11.3

5-24

5.6 Highlighting Components in the Designs

Keywords: ENHANCE UNENHANCE SOLELY

Description: This facility lets you highlight components visually in the design. Forexample, all sections of implied tube and rod could be highlighted, allpiping components and so on.

A particular use of this facility would be to highlight componentswhich fail error checking.

The SOLELY keyword clears all previous highlighting beforehighlighted the defined components.

You can also highlight specific lengths of tube or rod.

Examples:

ENHANCE SOLELY ALL REDU WITH (ABOR GT 10) COLOUR 13Highlights all RED components that match the selection criteria with colour13 (turquoise)

ENHANCE /PIPE1 /PIPE2 COLOUR 5Highlights PIPE1 and PIPE2 in green

ENHANCE LENGTH 20 OF LEAVE TUBE COLOUR 7Highlights 20mm of LEAVE TUBE in blue

Command Syntax:

>-- ENHANCE --+-- SOLELY ---. .--------------.| | | |‘-------------+-- <selatt> --+-- <selatt> --’.

| || ‘-- COLour -- <colno> --.| |+- LENGth - <uval> - OF -. || | |‘- TOTAl ----------------+- <hlid>-----+-->

Where <hlid> is:

>--+- LEAVE --.| ||- ARRIVE -|| ||- HEAD ---|| |‘- TAIL ---+- ROD --.

| |‘- TUBE -+- OF - <gid> -- COLour -- <colno> -->

Display


5-25

.--------------.| |

>-- UNENHANCE ---+-- <selatt> --+-- <selatt> --’| |+- <HLID> -----+-------------------+--->

5.7 Spatial Maps

Spatial maps of the model are based on the obstruction limit boxessurrounding each Design element, rather than using fully detailed geometricrepresentations. The spatial maps allow faster data access, and they are usedfor tasks such as clash detection where fast data access is required and wherethe simplified representation is adequate.

Spatial maps are maintained automatically as the design model is updated,but may need to be rebuilt explicitly if the Catalogue data, from which the mapgeometry is derived, is changed.

5.7.1 Checking the Spatial Maps

Keywords: MAP CHECK

Description: You can check one or more of the spatial maps to ensure that theyaccurately reflect the current state of the design. To avoid spuriousresults, it is advisable to do this before carrying out a clash check. Thisis particularly important if the geometry of any geometry elements hasbeen modified.

Examples:

MAP CHECK MDBChecks the spatial maps for all Design DBs within the current MDB againstthe current design and catalogue data. If there are any discrepancies,appropriate messages are output; you should then rebuild the map (seeSection 5.7.2)

MAP CHECK PIPES/AREA1Checks the up-to-date status of the spatial map for the named Design DBonly.

Command Syntax:

>--- MAP CHEck ---+--- MDB -------------------------------.| || .-----------<---------. || / | |‘--- word ---*--- name --+-- word ---’ |

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

where word and name define the full name of a current Design DB.

Display


Version 11.3

5-26

5.7.2 Creating or Updating Spatial Maps

Keywords: MAP BUILD

Description: Lets you update existing spatial maps to take into account all designand catalogue changes which have taken place. This is only necessaryif the MAP CHECK command (Section 5.7.1) shows that the map is outof date.

Examples:

MAP BUILD MDBUpdates the spatial maps for all Design DBs within the current MDB.

MAP BUILD STEEL/AREA2Updates the spatial map for the DB STEEL/AREA2.

Command Syntax:

>--- MAP BUIld ---+--- MDB --->|| .-----------<-----------.| / |‘--- word ---*--- name ---+--- word ---’

|‘--->

where word and name denote the full name of a current Design DB.


6 Using Rules to Define Attribute Settings

Rather than being set explicitly, the values of some types of attribute can bespecified in terms of rules; that is, expressions from which the attribute valuescan be evaluated. Rules can be set only for attributes of the following types(including user-defined attributes): text, scalar (integer, real or logical),position, orientation, direction; they cannot be set for reference attributes. Astatic rule will change the attribute setting only when verified or executedexplicitly, whereas a dynamic rule will update the attribute setting wheneverany part of the expression changes (the default type is static).

6.1 Setting Attribute Rules

Keywords: RULE SET STATIC DYNAMIC

Description: Lets you set a rule for the value of a single named attribute. The rulemay contain any valid expression of the type applicable to theattribute setting.

Examples:

RULE SET ZLEN (XLEN + YLEN)Sets rule that ZLEN of the current element is the sum of its XLEN andYLEN values. The ZLEN will be updated to reflect changes to XLEN orYLEN only when the rule is verified or executed (i.e. it is a static rule).

RULE SET XLEN DYNAM (YLEN + 2)XLEN will be updated automatically whenever YLEN is changed.

RULE SET POS (N300 E400 U500) ON ALL BOX FOR /PUMP1Sets rule for position attribute for all boxes in /PUMP1

RULE SET POS DYNAM (N100 FROM /BOX2 )If /BOX2 moves, the element with this attribute rule will move with itautomatically. (Note space between last character of element name andclosing parenthesis.)

Using Rules to Define Attribute Settings


Version 11.3

6-2

Command Syntax:

>- RULE SET - attribute_name -+- STAtic --.| ||- DYNamic -|| |‘-----------+- <expre> -+- ON -.

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

|.------’|‘-+- <selatt> -.| |‘------------+->

Querying:

Q ATT Displays all attribute values and all rules forthe current element.

Q RULES Displays all rules for current element.

Q RUL OF XLEN Displays rule for XLEN attribute of currentelement.

6.2 Verifying Attribute Rules

Keywords: RULE VERIFY

Description: When a rule is verified, the expression held in the rule is evaluatedand both the result of the evaluation and the current value of theattribute are displayed.

Examples:

RULE VERIFY ALLVerifies all rules for the current element.

RULE VER HEIG ON CYLI 1 FOR /PUMP1Verifies rule for height attribute on first cylinder of /PUMP1.

Command Syntax:

>-- RULE VERify --+-- attribute_name --.| |‘-- ALL -------------+-- ON --.

| |‘--------+-- <selatt> --.

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

Using Rules to Define Attribute Settings


6-3

6.3 Executing Attribute Rules

Keywords: RULE EXECUTE

Description: When a rule is executed, the expression held in the rule is evaluatedand the value of the attribute is replaced by the result of theevaluation.

Examples:

RULE EXECUTE :TEMP1Executes rule for uda :TEMP1 for the current element.

RULE EXE ALL ON ALL BOX FOR /PUMP1Executes all rules for all boxes owned by /PUMP1.

Command Syntax:

>-- RULE EXEcute --+-- attribute_name --.| |‘-- ALL -------------+-- ON --.

| |‘--------+-- <selatt> --.

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

6.4 Deleting Attribute Rules

Keywords: RULE DELETE

Description: Lets you delete one or more rules for the current element or forspecified elements.

Examples:

RULE DELETE ALLDeletes all rules for the current element.

RULE DEL ALL ON ALL FOR /PUMP1Deletes all rules for all primitives owned by /PUMP1.

Command Syntax:

>-- RULE DELete --+-- attribute_name --.| |‘-- ALL -------------+-- ON --.

| |‘--------+-- <selatt> --.

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


7 Interacting with a Graphical View

Note: The commands described in this chapter should not be used very often.Most of the functionality they provided has been superseded by Event-driven Graphics, and they are included here for compatibility withearlier versions of PDMS.

7.1 Identifying Displayed Items and Points

A displayed element from the visible model can be accessed directly by movingthe cursor over it and clicking the left-hand mouse button. The followingsections describe the different ways of selecting database elements from thedisplay by using the cursor. These commands let you use the visible design inorder to move to elements in the Design hierarchy and points in 3D space.

In each case, an appropriate prompt is displayed.

7.1.1 Identifying Displayed Elements using the Cursor

Keywords: IDENTIFY

Description: If a particular type of element is to be located, a selective search canbe made using the IDENTIFY command followed by a keywordidentifying the element type. If a specific element type is notrequested, the element hit will always be a geometric primitive orcomponent. Any displayed line or p-point of an item may be hit. Toabort, press the Cancel button on the displayed form.

Examples:

ID @ Pressed Enter (or Return), move the cursor overthe desired item and click the left-hand mousebutton. The name of the element under thecursor is displayed on the command line. Thepicked element becomes the current elementand is displayed in a different colour. (This isthe general response to all variations of theIDENTIFY command.)

ID EQUIP @ As above, but the search is restricted to EQUIelements.

Interacting with a Graphical View


Version 11.3

7-2

Command Syntax:

>-- IDentify --+-- <snoun> --.| |‘-------------+-- @ -->

7.1.2 Identifying Tube using the Cursor

Keywords: IDENTIFY TUBE

Description: Variable length Tube (and Rod) from the visible design can be accessedby picking with the cursor. As Tube is not an element in the Designhierarchy, it cannot be accessed. Instead, the component on theupstream side of the Tube (downstream if routing backwards) will beaccessed. This means that the next component to be created will beinserted in the picked Tube. Any visible Tube can be picked regardlessof whether it is shown in single or double line representation.

Examples:

ID T @ The name of the component on the upstreamside of the Tube under the cursor is displayed onthe command line.

Command Syntax:

>-- IDentify Tube @ -->

7.1.3 Identifying Displayed Points using the Cursor

Keywords: IDPPOINT PPOINT

Description: The cursor can be used to pick any p-point in the visible design or anymapping pin. This form of picking will not change the currentelement.

Note: IDPPOINT cannot be used in isolation. It must be used with anothercommand.Only those p-points which are defined in the Catalogue as beingvisible in DESIGN will be available for picking in this way.

Examples:

Q IDP @ Press and hold down left-hand mouse button whencursor is over element. Element will be highlightedwith p-points visible and cursor will change to asquare shape. With left-hand mouse button still helddown, move cursor over required p-point. When over ap-point, cursor will change to a square shape withcrosshairs. Release the button to select the p-point.



7-3

Command Syntax:

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

>-- Query <marke> --+--*-- <ppatt> --+-->||-- <axes> -->|‘-->

<ppatt> = >--+-- CONnection --------------.| ||-- BORe --------------------|| ||-- OD ----------------------|| ||-- POSition ---. || | ||-- DIRection --| || | ||-- East -------| || | ||-- X ----------| || | ||-- West -------| || | ||-- North ------| || | ||-- Y ----------| || | ||-- South ------| || | ||-- Up ---------| || | ||-- Z ----------| || | ||-- Down -------| || | ||-- GRADient ---| || | ||-- BOP --------| || | |‘-- TOP --------+-- <axes> --|

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

7.1.4 Identifying Items with a 2D Pick

Use a working plane in preference to this older functionality.

Keywords: TWODPLANE TWODPICK

Description: This facility lets you define a plane which is normal to the viewdirection. You can then use the cursor to pick a point in an orthogonalview such that the third coordinate of the required point is derivedautomatically from this plane.



Version 11.3

7-4

The TWODPLANE command defines the 2D picking plane in terms of apoint within the plane.

The AT TWODPICK @ command may then be used to request a cursorposition which identifies a point within the 2D picking plane. Theplane is generated dynamically from the TWODPLANE point and theview direction.

Examples:

TWODPLANE E 1000 N 2000 U 500Defines 2D picking plane which passes throughgiven point and which is normal to viewdirection

AT TWODPICK @ Using the preceding 2D picking plane definition,a cursor hit at E 1234 N 5678 in a plan view willreturn the position E 1234 N 5678 U 500 inWorld coordinates

Note: Cursor positions are always returned in World coordinates. In order toobtain the correct result, the 2D picking plane must therefore be set toan absolute World position.

Command Syntax:

>-- TWODPLane -- <bpos> -->

>-- AT TWODPick @ -->

Querying:

>-- Q -- TWODPLane -->

7.2 3D Pins

The DESIGN pins are a set of ten temporary marker points which have a 3Dposition and direction. They can be moved around using positioning andorientation commands similar to those available for permanent Designelements.

Once positioned, a pin may either be used as a static reference point or as atemporary p-point.

The commands described here only show how to make pins visible and positionand orientate them. Once this has been done they can be used for positioningand orientating Design elements in any command that uses point as anargument.



7-5

7.2.1 Setting a Pin’s Position and Direction Explicitly

Keywords: PIN AT DIRECTION

Description: The position and direction of a pin can be set explicitly in the sameway as an ordinary design element. Unless stated otherwise, thepositional parameters described below are in the coordinate system ofthe current element.

Examples:

PIN 5 AT E1000 Pin 5 will be moved to the coordinate positionEast 1000 from the Site origin.

PIN5 DIR W WRT SITEPin 5 will be orientated in a direction West withrespect to the current SITE.

Command Syntax:

>-- PIn integer --+-- AT --+-- <bpos> ------------------------.| | || ‘-- POLar <bdir> DISTance <uval> --|| |‘-- DIRection <bdir> -----------------------+-->

Querying:

>-- Q PIn integer POSition <bpos> --+-- <axes> --.| |‘------------+-->

>-- Q PIn integer DIRection <bdir> --+-- <axes> --.| |‘------------+-->

7.2.2 Making a Pin Visible

Keywords: PIN

Description: This command allows a particular pin to be switched in and out of theDisplay.

When a pin is visible, it will be drawn as a numbered arrow markerwhich indicates its position and direction in each volume view. Visiblepins can be hit with the cursor during any IDPPOINT operation. Whena pin is switched off, it is erased from the display, but it still existsand can be referred to by name.

Examples:

PIN 5 Pin 5 will be drawn into all volume views, andcan be hit by the cursor.



Version 11.3

7-6

PIN 5 OFF Pin 5 will be erased.

Command Syntax:

>-- PIn integer --+-- OFF --.| |‘---------+-->

Querying:

(As in previous subsection.)

7.2.3 Locating a Pin by Copying or Connecting

Keywords: PIN COPY CONNECT

Description: A pin’s position and direction can be set by copying or connecting toany other p-point or pin, the only difference being that the CONNECToperation orientates the specified pin in the opposite direction (seeexamples below).

Examples:

PIN 5 C0PY IDP @ Pin 5 will be placed at the same position andorientation as the p-point or pin hit by thecursor.

PIN 5 CONNECT TO PHPin 5 will be placed at the Branch Head, butpointing in the opposite direction to HDIR(Head direction). This command must be givenat BRANCH level. Pin 5 can be an existing pinor a new one.

Command Syntax:

>-- PIn integer --+-- Copy --------------.| |‘-- CONnect --+-- TO --|

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

Querying:

>-- Q PIN integer --+-- POSition ---.| |‘-- DIRection --+-- WRT --.

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



7-7

7.2.4 Moving a Pin

Keywords: PIN BY THROUGH DISTANCE

Description: These commands allow a pin to be moved from its current position inany axis direction or along its own direction. If moved along its owndirection, a specified distance can be given or, alternatively, anintersection. (Moving in this manner is very similar to the pipe-routing options.)

Examples:

PIN 6 BY E3000 N2000Pin 6 is moved by the given directions anddistances

PIN 6 DIST 600 Pin 6 is moved along its own direction by thegiven amount

PIN 6 THR /NOZZ5 Pin 6 is moved along its own direction until itintersects a plane through /NOZZ5

Command Syntax:

>-- PIn integer --+-- BY <pos> ---------.| ||-- THRough <bpos> ---|| |‘-- DISTance <uval> --+-- WRT --.

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

Querying:

>-- Q PIN integer --+-- POSition ---.| |‘-- DIRection --+-- WRT --.

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

7.2.5 General Pin Moves

Keywords: PIN

Description: Pins may be moved in exactly the same manner as piping components,using the same command options. The movement direction is alwaysin the pin direction, so it is important to ensure that this isappropriate before a move is attempted. As these commands are quite



Version 11.3

7-8

extensive, they are not repeated here; see the pipe routing commandsin Chapter 8.

Examples:

PIN 6 DISTANCE 600 INFRONT ID @Pin 6 is moved along its direction until it is 600distance units in front of the item picked withthe cursor.

Command Syntax:

>-- PIn integer <plane> -->

(see Chapter 8 for the <plane> construction)

7.3 Constructs

Note: Use the Constructs options on the Utilities menu in preference tothese older facilities.

Keywords: CONSTRUCT POSITION DIRECTION DISTANCE ANGLELINE PLANE

Description: The construction aids available in DESIGN let you displaycoordinates, directions, distances, angles and plane definitions.

The constructed quantities are written out into the REQUESTS regionof your display. These quantities can be written into variables for lateruse. The commands used to define constructed quantities make use ofp-points, p-lines, pins, directions, positions and orientations.

The different methods for constructing these entities are:

• CONStruct Angle position1 TO position2 TO position3

direction1 AND direction2line1 line2line planeplane1 plane2plane line

• CONStruct DISTance position1 TO position2

position TO lineposition TO planeline1 TO line2

projection of any of the above ALong a given direction



7-9

• CONStruct Position NEArest position ON line

NEArest position ON planeINTersect plane1 plane2 plane3INTersect line planeINTersect line1 line2 (gives result on line1 if lines are skew orparallel) plane line

• CONStruct DIRection NORmal plane

ORTHogonal direction1 AND direction2ORTHogonal direction AND lineORTHogonal line1 AND line2ORTHogonal line AND directionposition1 TO position2planeline

• CONStruct LINe JOIn position1 TO position2

direction THRough positionPARallel line THRough positionNORmal line THRough positionNORmal plane THRough positionPROJection line ON planeINTersect plane1 plane2

• CONStruct Plane THRough position1 AND position2 AND position3

direction THRough positiondirection THRough a p-point, pin or digitised point (optionally offseta given DISTance or relative to existing geometry: INFront orBEHind an element, p-point or position: FROm or TO a position)

Note: In all of the above, position, direction, line or plane is defined innormal PDMS format, or by reference to a p-point, pin or marker, orpicked from an appropriate view.

Examples:

CONS POS P2 OF FLAN 4 OF BRAN /PIPE1-1 TO PLANE PIN 7The intersection between the specified point and the plane perpendicular topin 7 is shown.

VAR 5 CONS POS PL TO LINE PA OF NEXTThe closest point on the line from PLEAVE to the intersection of the twolines is placed in Variable 5.



Version 11.3

7-10

CONS POS PIN5 TO PLA PIN6The intersection between the direction of pin 5 and the plane perpendicularto pin 6 is written out into the request region.

CONS DIR PLThe direction of the line is output in World coordinates into the requestregion.

CONS DIST PA TO PLThe dimension from the first to the second p-point of the current element iswritten out into the Request region.

VAR 5 CONS DIST PL TO LIN PA OF NEXTThe minimum distance between PLEAVE of the current element and thespecified line will be be placed in Variable 5

CONS ANG PIN1 TO PIN2 TO PIN3The angle between the three specified points is written out into the Requestregion.

CONS ANGL PL LIN PA OF NEXTThe angle between the lines from the two specified p-points is written outinto the request region.

CONS LINE JOIN P0 TO P1Constructs a line joining the two p-points, displaying the line descriptionin the request region.

CONS PLANE P3 DIST 900The plane perpendicular to the specified point and 900 from it is written outinto the request region.

CONS PLANE PL THROUGH /NOZZ5The plane perpendicular to the specified point and intersecting /NOZZ5 iswritten out into the request region.

CONS PLANE PA DIST 500 BEH /COL19A plane perpendicular to the specified point will be defined and written outinto the request region. The plane will be positioned 500 to the far side of/COL19.


8 Design Database Elements

This chapter describes the commands to create, copy and name databaseelements, and also the commands to navigate around the database hierarchyonce you have created some elements.

These commands can be used throughout DESIGN. For information aboutcreating the elements which build up the model, and setting their attributes,see Part 2 and Part 3 of the Design Reference Manual. For a comprehensivelist of all valid PDMS attributes, see the Cadcentre Software CustomisationReference Manual.

8.1 Elements

8.1.1 Creating Elements

Keywords: NEW

Description: This command creates a new element in the Design hierarchy. Theattributes of that element can then be specified or further elementsmay be created as members.

Elements can only be created at appropriate levels in the hierarchy.For example a Site can own a Zone, but not a Valve. In some cases youmust navigate to the correct position in the hierarchy before you cancreate a new element, but in other cases DESIGN will navigate to thecorrect level automatically: see Examples below.

For Branch and Hanger elements, the location of the new Componentin their member list defines the route logic. It is therefore necessary tonavigate to the Component adjacent to the insertion point in themember list (upstream if routing forwards, downstream if routingbackwards). If the new Component is required at the end of themember list then accessing the Branch or Hanger Head or Tail willinsert the Component in the correct position.

Examples:

NEW ZONE /Z1The Zone element is created as a member of the current Site. The Zone isnow the current element. Its NAME attribute is /Z1.

Design Database Elements


Version 11.3

8-2

NEW TEEIf the current element is the fourth member in a Branch member list, theTee element is inserted as the fifth member. The Tee is now the currentelement.

NEW EQUIP /1301If the current element is a Box owned by another EQUIP which is Member 2of Zone /Z1, the new Equipment element is inserted as member 3 of theZone and named /1301. The new Equipment is now the current element.

NEW GASKETIf this command is given when the current element is the Branch Head, theGasket is inserted as the first member of the Branch and is now the currentelement.

Command Syntax:

>-- NEW --+-- name <snoun> --------.| |‘-- <snoun> --+-- name --|

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

Querying:

Q LISt Indicates all the design element types that can becreated as members of the current element.

8.1.2 Creating Elements at a Given Position in the Member List

Keywords: NEW

Description: You can place elements in any location in a legal member list byspecifying the existing element adjacent to where the new element isrequired. The new element may be inserted either before or after thespecified element.

Examples:

NEW VALVE BEF (At a Branch Component)The Valve will be inserted before the current element in the current list.

NEW ZONE BEF 2 (At Site level)The Zone will be inserted before member 2 of the Site.

NEW BOX (At a CYLI which is a member of a STRU)A new BOX will be inserted as the next member of the STRU (after theCYLI in member list order).

NEW BOX (At a SUBS which is a member of a STRU)A new BOX will be inserted as a member of the SUBS (at the top of themember list).



8-3

Command Syntax:

>-- NEW --+-- name <snoun> --------.| |‘-- <snoun> --+-- name --|

| |‘----------+-- BEFore --.

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

8.1.3 Deleting Elements

Keywords: DELETE

Description: The basic delete operation can only be performed on the currentelement. Its effect, however, is to delete this element and all itsoffspring (i.e. members and their members, etc.) from the model. TheMEMBERS option only deletes the offspring, leaving the currentelement intact. When an element is deleted, its owner becomes thenew current element.

Examples:

DELETE NOZZDeletes the current element - a Nozzle. The EQUI owning the Nozzlebecomes the current element.

DELETE ZONEDeletes the current element - a Zone and all its offspring. The Site owningthe Zone becomes the current element.

DELETE SITE MEMDeletes all the members of the current element (SITE) and their offspring.

Command Syntax:

>-- DELETE <snoun> --+-- MEMbers --+-- integer --+-- TO integer -->| | || | ‘-->| ‘-->‘-->



Version 11.3

8-4

8.1.4 Reorganising the Hierarchy

Keywords: REORDER INCLUDE

Description: If it is necessary to reorganise the hierarchy, two options are available.REORDER allows the elements in a single member list (e.g.Components of a pipe) to be rearranged. INCLUDE allows elements tobe relocated to another part of the hierarchy (e.g. an EQUIPMENTmay be moved into a different Zone). In both operations the elementsand their offspring are transferred to their new location in the Designhierarchy. In the case of INCLUDE, the element’s owner changes. If theold and new owner are in different positions in World coordinates,then the element will change position.

Elements can also be moved to new locations in the hierarchy byplacing them before or after a specified element.

Examples:

REORDER /B/B, which must be in the member list of the current element, is relocatedafter the current member list position.

INCLUDE /EQUIPThe current element must be a Zone, which is the only element which canown an Equipment. /EQUIP is inserted into the Zone’s member list.

REORD /B AFTER 3(Both elements must be in the member list of the current element.) Element/B is located after the third element in the member list.

INCL /EQUIP BEF 3The element /EQUIP is brought from its location in another Zone to beforethe third element in the member list of the current Zone.

Command Syntax:

>--+-- REOrder --.| |‘-- INClude --+-- <gid> --+-- BEFore --.

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



8-5

8.1.5 Copying

This subsection describes how to copy elements, together with their offspring.When elements are copied, all attributes are duplicated except:

• NAME, which must be unique.

• LOCK, which will always be unlocked in the new element.

Keywords: COPY

Description: The COPY command provides an extremely powerful facility. Not onlyis it possible to copy all the attributes of a specified element into thecurrent element, it is also possible to duplicate any offspring thatelement may have. This means that anything from a single primitiveshape to a whole equipment item (or even a Site) can be copied.

Examples:

COPY PREVFor example, if both the current and previous elements are Boxes, theattributes of the previous element will be copied to the current element.

COPY /EQUIP10For example, if the current element is an Equipment, the attributes andoffspring of /EQUIP10 are copied to the current element. (The NAME andLOCK attributes of the current element do not change.)

Command Syntax:

>-- COPY --+--------------------.| ||-- ATTributes - OF -|| |+-- LIKE ------------+ -- <gid> --.| |‘-- ADJacent ------ <selatt>------+--->

• The ATTRIBUTES option copies all attributes (except for direct designreferences) from the identified element to the current element. Themembers hierarchy is not copied. The source and current elements do nothave to be the same type. If the types are different, only the attributesvalid for the target (current) element are copied.

• The LIKE option works in a similar fashion to ATTRIBUTES, except thatany position, direction, orientation or angle atributes are not copied.

• The ADJACENT option causes a list of elements, selected by <selatt>, tobe copied alongside their original positions in the database. For example,if the list included a SCTN and a PNOD, each of these items would becopied so that the new SCTN shared the same owner as the old SCTN,and the new PNOD shared the same owner as the original PNOD. Notethat as this option copies elements, rather than just attributes, the COPYoption can be used.



Version 11.3

8-6

8.1.6 Copying and Renaming

Keywords: COPY RENAME

Description: This command allows automatic renaming of the current element andany new offspring that possess a standard name part. You can alsochoose to copy only the members (and their offspring) of an element,leaving the attributes of the current element unchanged.

Examples:

COPY MEM OF /EQUIP10 (At another EQUIP element.)If the current element is an Equipment, all the offspring of /EQUIP10 arecopied into the current element. The attributes of the current element do notchange.

COPY /P1/PIPE RENAME /P1 /P2The attributes and offspring of /P1/PIPE are copied into the current element.Where /P1 is found as the name or part of the name, it is renamed as /P2 inthe current element and its offspring.

COPY MEM 4 TO 10 OF PREV BRANThe attributes and offspring of the fourth element in the current element’smember list are copied into the tenth element in the member list of theprevious BRAN element in the current member list.

Command Syntax:

>- COPY -+- MEMbers -+- n -.| | || ‘-----+- TO n -.| | || ‘--------+- OF <gid> -+- REName name name -.| | || ‘--------------------||- ALL OF -. || | |‘----------+- <gid> -+- REName name name --------------------|

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



8-7

8.2 The Standard Design Element Attributes

The range of information attributes carried by each Design element dependsupon the element type; for example, a Cylinder has DIAMETER and HEIGHTamong its attributes, whereas a PIPE has a PRESSURE attribute. Allelements, however, possess the following basic core of four essential attributes(known as the standard attributes):

TYPE This is given by the user as part of the element creationcommand, e.g. NEW BOX (where the TYPE is BOX).

NAME This can either be provided by the user or, in the case ofminor items, is generated automatically (as a referencenumber).

OWNER This attribute indicates the element’s owner and isautomatically set when the element is created.

LOCK This is allows you to prevent an element from beingaltered or deleted.

In addition, most Design elements possess the two additional attributes:

POSITION The position of the element relative to its owner.

ORIENTATION The orientation of the element relative to its owner.

Both of these attributes are set automatically during 3D element positioningand routing operations.

8.2.1 The Type of Element and its Owner

Keywords: TYPE OWNER

Description: An element’s TYPE and OWNER attributes are set automaticallywhen it is created. They cannot be changed explicitly.

Command Syntax:

See Sections 8.1.1 and 8.1.2 on element creation (NEW command).



Version 11.3

8-8

8.2.2 Naming Design Elements

Keywords: NAME UNNAME

Description: All elements except the WORLD can be named. Although Designelements are often given suitable names while being created, latername changes can be made by giving a new name or by removing theold name. The name of any element must be unique; that is, notalready used for another currently accessible element.

Examples:

NAME /ZONE5DThe current element is given the specified name provided it has not beenused elsewhere.

UNN The current element loses its name (it is still identifiable by itsautomatically allocated reference number).

Command Syntax:

>-- NAMe --+-- ALL name name --.| |‘-- name -----------+-->

>-- UNName -->

8.2.3 Renaming Elements and their Offspring

Keywords: RENAME

Description: The name of the current element and offspring can be modified wherea standard name part occurs.

Examples:

REN ALL /Z1 /Z2All occurrences of /Z1 in the names of the current element and its offspringwill be changed to /Z2.

Command Syntax:

>-- REName --+-- ALL name name --.| |‘-- name -----------+-->



8-9

8.2.4 Locking Elements Against Alteration and Deletion

Keywords: LOCK UNLOCK

Description: Locking a design element prevents it from being modified or deleted.The LOCK command allows either a single element to be controlled, orall its offspring too. (A complete Site can be locked if required.) Thisprovides you with personal security control over your area of work.(General security restrictions affecting the whole Project areestablished in the ADMINISTRATION module of PDMS.)

Examples:

LOCK ALLThe current element and all its offspring are locked.

UNLOCKThe current element is unlocked.

Command Syntax:

>--+-- LOCK ----.| |‘-- UNLOck --+-- ALL --.

| |‘---------+-- <snoun> --.

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

8.2.5 The Position and Orientation Attributes

Keywords: POSITION ORIENTATION

Description: Virtually every element in the Design hierarchy has its own coordinatesystem which consists of a set of axes giving an origin position andorientation. The POSITION and ORIENTATION of an element are theposition of its origin and the orientation of its axes relative to itsowner. On creation, an element starts with the position E0 N0 U0(i.e. at the origin of its owner) and is orientated with its axes alignedwith those of its owner. The commands which alter position andorientation are all the element placement, connection and routingfacilities described elsewhere in this manual.



Version 11.3

8-10

Querying:

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

|‘-->

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

Querying examples:

Q POS Returns the current element position in its owner co ordinates

Q ORI WRT SITEReturns the current element orientation in Site coordinates

Q POS IDP@ WRT WORLDReturns the position of the Design point hit by the cursor in Worldcoordinates

8.3 Navigation

You can navigate around the Design database in the following ways:

• Going to a Design element whose identity or position in the hierarchy isknown

• Going to a Design element whose position in the hierarchy relative to thecurrent position is known

• Going to a Design element by picking it a graphical display.

Note that you can navigate to any element in the Design database, and not justthe items currently shown in the graphical display.

As well as the commands described in this Section, you can go to an elementby:

• Picking it in the Graphical View.

• Picking it in the Members List

• Typing in its name or reference number.



8-11

8.3.1 Going to the Previously Accessed Element

Keywords: SAME CE

Description: SAME takes you to the element you were at before you accessed thecurrent element. Repeating the SAME command has the effect ofmoving repeatedly between two items - it does not move back alongthe list of items accessed. (If the previously accessed element has beendeleted, the next available element in the list will be accessed.)

CE takes you to the current element itself. (This facility may seemrather pointless in this situation; however the CE keyword is used inmany commands as a means of identifying an element to be the objectof that command.)

Examples:

CHECK CECheck the current element for data inconsistencies.

ADD CEAdd the current element to the display.

Command Syntax:

>-- CE -->

>-- SAMe -->

8.3.2 Going to an Implied Tube or Rod

Keywords: IARRIVE ILEAVE HEAD TAIL TUBE ROD

Description: You can navigate to implied tube or rod within a branch or hanger(although if the derived length is less than 1mm, the system does notconsider it to exist).

To make an implied rod or tube the current element, you must alsoindicate whether the head, tail, arrive or leave tube or rod is intended.

Example:

IARRIVE TUBE OF /PIPE1Go to arrive of implied tube of /PIPE1.



Version 11.3

8-12

Command Syntax:

>--+-- IArrive ---.| ||-- ILeave ----|| ||-- HEAd ------|| |‘-- TAIl ------+---+-- TUBe --.

| |‘-- ROD ---+-- OF ---<gid>---.

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

8.3.3 Ascending the Design Hierarchy

Keywords: OWNER END

Description: Moving up the hierarchy involves fewer decisions than movingdownwards, as any element can have only one Owner. Two commands(OWNER and END) allow you to move up to the immediate parent.

END differs from OWNER by allowing you to return to a Groupelement from which the current element was accessed. As the Groupdoes not own that element, the command OWNER would go to theelement’s true Owner and not the Group.

You can move up the hierarchy by more than one level by inputtingthe type of element you want to access. For example, navigation froman Elbow to its parent Zone would involve three successive ENDcommands. However the command ZONE would scan up the hierarchyto find the Zone which owns the current element list, thus saving twoEND commands.

8.3.4 Other Navigation Commands

Keywords: FIRST LAST NEXT PREVIOUS MEMBEREND TYPE

Description: Navigate to the specified position in the members list. Most can beused with the OF keyword to go to members of other elements.

Examples:

FIRST BRANCH OF ZONE /Z25ALAST NOZZLE OF PREVIOUS 3 EQUIPMENTSFIRST ZONE OF /SITE 5PIPE 2 OF /Z100AELBOW 1 OF NEXT BRANCH



8-13

8.4 Setting a Synonym for an Element Name

Keywords SETSTAR

Description To save repeatedly typing an element's name, you can define theasterisk or star symbol (*) to represent any specified element. Bydefault, if no element identifier is given, the current element isassumed. After setting, the * symbol may be entered in any commandto represent the full name of the element.

Examples:

SETSTAR * will now represent current element

SETSTAR /element_name* will now represent the specified element

Command Syntax:

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


9 Error Messages

This chapter lists error messages specific to DESIGN. These messages have amessage number beginning with 61. Any other messages that may be outputare not described here as they are not specific to DESIGN.

Note that in the following element_identifier denotes an element name or (forunnamed elements) an element reference number. The latter is a ‘system’number which is assigned automatically whenever an element is created.

(61:1) Unable to calculate the orientation(61:2) element_identifier is not a piping or a hanger component or has not been

positioned oriented or selected.(61:3) element_identifier is not a branch or piping component(61:4) element_identifier is not a hanger or hanger component(61:5) Unable to position element_identifier(61:6) element_identifier does not have a position(61:7) Unable to orientate element_identifier(61:8) element_identifier does not have an orientation(61:9) Unable to set the head position of element_identifier(61:10) Unable to set the tail position of element_identifier(61:11) Unable to set the head direction of element_identifier(61:12) Unable to set the tail direction of element_identifier(61:13) Trying to connect element_identifier to itself(61:14) Unable to set the head reference of element_identifier(61:15) Unable to set the tail reference of element_identifier(61:16) Current element does not have a head or a tail attribute(61:17) Default orientation only available for piping and hanger components.(61:18) Default orientation cannot be found. Previous element either not

positioned and oriented or not selected.(61:19) Direction undefined for towards origin of current element(61:20) Current element type unsuitable for DIRECTION command(61:21) SPREF can only be selected for a piping or hanger component(61:22) LSTUBE can only be selected for a piping component(61:23) HSTUBE can only be selected for a BRANCH(61:24) LSROD can only be selected for a hanger component(61:25) HSROD can only be selected for a HANGER(61:26) TUBE can only be selected for a BRANCH or a piping component(61:27) ROD can only be selected for a HANGER or a hanger component(61:28) Only BRANCHs, HANGERs, and piping and hanger components can be

selected(61:29) element_identifier is not a SPEC(61:30) element_identifier is not a SPCOM(61:31) Cannot find SPCOM name

Error Messages


Version 11.3

9-2

(61:32) Appending name to specification name gives a name of more than 50characters.

(61:33) Angle attributes can only be given values between -180 and +180 degrees.(61:34) Degenerate orientation specified(61:35) Pins cannot be used for connecting piping or hanger components(61:36) Reconnecting element_identifier(61:37) Connection to element_identifier is invalid ( HREF / TREF do not point

back to nozzle )(61:38) element_identifier is locked, reconnection fails(61:39) element_identifier is in a read-only database, reconnection fails(61:40) Plane parallel to movement direction(61:41) Default movement direction only available for piping and hanger

components.(61:42) Default movement direction not available. Previous element either not

positioned and oriented or not selected.(61:43) ARRIVE / LEAVE ppoint cannot be determined. Current element has

probably not been selected.(61:44) Default movement origin cannot be determined.(61:45) BOP and TOP can only be used with piping and hanger components.(61:46) DIRECTION command only operates on ppoints of the current element(61:47) Bad DIRECTION - zero degree angle specified(61:48) Point set does not allow variable angle. Angle is unchanged, direction is

in correct plane.(61:49) Unable to achieve specified direction - probably due to unconventional

pointset(61:50) Pin numbers must be in the range 1 to 10(61:51) Unable to position pin integer(61:52) Unable to orientate pin integer(61:53) Unable to copy the marker(61:75) element_identifier is not a branch, reconnect fails(61:76) Connection to a database that is not open, reconnection fails(61:77) Cannot find P-point 1 - Nozzle catalogue reference probably not set(61:78) Reconnect not allowed at WORLD or GPWL level(61:79) element_identifier cannot own nozzles(61:80) Cannot access SPCOM from which to reselect(61:81) To position the HEAD / TAIL of a branch or hanger use POS / MOVE

PH / PT / HH / HT ...(61:82) BOP / TOP cannot be used on a HEAD / TAIL that has not been positioned(61:83) Default clearance is only available for piping or hanger components(61:84) Shear attributes can only be given values between -89 and +89 degrees.(61:85) element_identifier cannot be flipped - it does not have ARRIVE and LEAVE

attributes.(61:86) Warning - Angle is greater than maximum specified in SPREF(61:87) Warning - Angle is less than minimum specified in SPREF(61:88) SPREF not found or unset(61:89) element_identifier does not have a Local-axes attribute(61:120) Too many views shown(61:121) Form name too word for screen

Error Messages


9-3

(61:122) Unable to set form gadget value or gadget not found(61:123) Form name not found(61:125) Gadget name not found(61:126) Item invalid as contents of view(61:127) Form name already shown(61:128) Form name may not be hidden(61:129) Cannot open Recreate file(61:130) File error while restoring data - RESTORE aborted(61:131) File error while restoring data - please exit from module and reenter(61:132) Unable to RESTORE - databases modified since module state SAVEd(61:133) Unable to SAVE - cannot access SAVE file(61:134) Unable to SAVE - SAVE file already in use(61:135) Unable to RESTORE - SAVE file already in use(61:136) Unable to RESTORE - cannot access SAVE file(61:137) Unable to RESTORE - cannot find SAVE file(61:138) Unable to RESTORE - current database files are not those which were in

use when module state SAVEd(61:139) Unable to RESTORE - module version number/screen size/font size is not

the same as SAVE file(61:140) Do you wish to save changes?(61:150) Only piping components, nozzles and equipments can be dragged(61:151) element_identifier is connected to element_identifier which is in a read

only database. This connection will be broken by drag.(61:152) element_identifier has a connection to an unknown element. This

connection will be broken by drag.(61:153) element_identifier is locked, drag aborted(61:154) The connection from element_identifier to element_identifier will be broken

by drag.(61:155) Attachment points can only be dragged if they have been positioned and

oriented(61:160) Spec is not set up correctly for CHOOSE command(61:161) element_identifier is not a piping component(61:162) SPEC does not contain word elements(61:163) SPEC does not contain correct bore structure for CHOOSE(61:164) SPEC does not contain elements matching given criterea(61:165) Previous component, element_identifier, has zero bore(61:166) Unforced Connections are word(61:167) Forced Connections are word(61:168) Connections are OFF(61:169) Warning - Requested bore value does not match current bore word(61:175) HOFFSET must be positive ( not zero )(61:190) Fatal error detected by Graphics Package forcing a return to MONITOR

module(61:191) Are your databases to be updated with the changes made this session(Y

or N)(61:192) Fatal error detected by SPLASH forcing a return to MONITOR module(61:193) WARNING - System storage area value % full. Remove items from drawlist

to avoid fatal error.

Error Messages


Version 11.3

9-4

(61:194) WARNING - Graphics storage area value % full.(61:199) Cannot access directory name(61:201) No more than 20 items can be given to AUTO(61:206) XR and YR values must be in the range 0 to 1.0.(61:207) Specified region is too narrow.(61:208) Illegal autolimits produced. ( Does it have any primitives? )(61:209) Mix values for colours are percentages ( 0 - 100 )(61:211) Only colours 1 to integer may be assigned to pens(61:220) Failed to connect.(61:221) Cannot calculate default orientation.(61:225) Usable colours are system colours plus user colours 1 to integer(61:226) Autolimits may only be set for graphic views, Please select a graphics

view and retry(61:230) Error reading from plotfile ..(61:231) Unrecognised code in plotfile(61:272) Already using file - name for alpha output(61:273) Cannot open alpha output file(61:274) No alpha output file in use.(61:275) Already using log file - name(61:276) Cannot open log file(61:278) No log file in use.(61:303) Direction cannot be calculated between two design points with the same

position - UP is assumed(61:304) Position cannot be calculated as lines are parallel - first point given is

assumed(61:305) Position cannot be calculated as line and plane are parallel - first point

given is assumed(61:306) Angle cannot be calculated as two points are coincident - zero assumed(61:307) Only significant and drawable elements can be tagged by type(61:351) The WORLD and GPWLs cannot be added / removed. SITEs can only be

added using ’ADD SITE’ in a setup context.(61:355) No more than ten elements can be added at one time(61:357) element_identifier is not a SITE(61:358) Only SITEs or ZONEs can be specified for ADD WITHIN. The default is all

sites in the multiple database.(61:461) Hit radius must be at least 1mm.(61:462) Hit radius must be no more than 100mm.(61:463) Working grid must be at least 1mm.(61:471) Cursor abandoned(61:495) Form name may not be changed(61:499) Menus may not be iconned(61:561) Workstation screen is not available, using TTY(61:564) Cursor input not allowed on alpha device(61:565) Point entered is not in a suitable view(61:599) Forms may not be updated

Error Messages


9-5

(61:800) Reference DETAIL not set(61:810) DETAIL refers to non-existent nDTE(61:820) SKEY not set(61:830) SKEY TSFL is used with generic type TEE, not TRAP(61:840) SKEY element_identifier not known. Assumed to be user defined.

PDMS DESIGN Reference Manual Index-1Part 1: General CommandsVersion 11.3

Index

<axes> syntax, 2-14

<bdir> syntax, 2-19

<bpos> syntax, 2-16

<date> syntax, 2-6

<dir> syntax, 2-17

<expr> syntax, 2-5

<gid> syntax, 2-10

<marke> syntax, 2-13

<noun> syntax, 2-8

<pos> syntax, 2-14

<selatt> syntax, 2-20

<snoun> syntax, 2-8

<uval> syntax, 2-7

Accessing DESIGN, 3-1

Active element, 5-5

ADD command

drawlist, 5-1

AID command, 5-19

Aids

graphical, 5-6, 5-19

ALARM command, 3-8

ALPHA CLEAR command, 3-2, 3-3

ALPHA FILE command, 3-2

ALPHA LOG command, 3-2

ARC command

design aids, 5-19

ARROW command

design aids, 5-19

Attributes

standard, 8-7

Audible error trace, 3-8

AUTOCOLOUR command, 5-2

AXES command, 5-17

BOX command

design aids, 5-19

BUILD command

spatial maps, 5-26

CE command, 8-11

CEARROW command

design aids, 5-19

CHANGES command, 4-18

Changing modules, 3-4

CHECK command

spatial maps, 5-25

Clashing element, 5-6

CLOSEST command, 2-11

COLOUR command, 5-5

displayed items, 5-1

Colour mixes

predefined, 5-6

Colours

active element, 5-5

clashing element, 5-5

current element, 5-5

default assignments, 5-7

defining, 5-5

graphical aids, 5-5

obstruction element, 5-5

visible element, 5-5

Index

Index-2 PDMS DESIGN Reference ManualPart 1: General Commands

Version 11.3

Commands

input mode, 2-22

COMMENT command, 4-5

CONSTRUCT command, 7-8

Construction aids, 7-8

Coordinates, 2-14

COPY command, 8-5

Creating elements, 8-1

Current element, 5-6

CYLINDER command

design aids, 5-19

Database

querying current, 4-6

Database changes

creating update macro, 4-18

querying history, 4-7

Date, 2-6

DELETE command, 8-3

rules, 6-3

Design aids, 5-19

DESIGN command, 3-1

Design points, 2-13

DIFFERENCE command, 4-17

Dimensions, 2-7

Direction

axial, 2-17

general, 2-19

Display

saving, 3-1

Draw list, 5-1

Drawing levels, 5-10

DYNAMIC command

attribute rules, 6-1

Elements

creating, 8-1

deleting, 8-3

identifying, 2-10, 2-20

locking, 8-9

naming, 8-8

renaming, 8-8

selecting, 2-20

types, 2-8

END command, 8-12

ENHANCE command, 5-24

Entering DESIGN, 3-1

Errors

alarm, 3-8

EXECUTE command, 6-3

Explicit mode

multiwrite DBs, 4-9

Expressions, 2-5

Extracts, 4-11

master, 4-11

FINCH command, 3-5

FINISH command, 3-4, 4-10

FIRST command, 8-12

GETWORK command, 3-1

Graphical aids, 5-19

Highlighting graphical items, 5-24

HISTORY command, 4-8

IARRIVE command, 8-11

ID @ command, 7-1

IDENTIFY command, 7-1

Identifying displayed items, 7-1

IDPPOINT command, 7-2

ILEAVE command, 8-11

Imperial units

setting, 3-5

Implicit mode

multiwrite DBs, 4-9

Implied tube, 8-11

INCH command, 3-5

INCLUDE command, 8-4

INSTALL command, 3-1

Index

PDMS DESIGN Reference Manual Index-3Part 1: General CommandsVersion11.3

INSULATION command, 5-11

LAST command, 8-12

LASTMOD command, 4-7

Leaving DESIGN, 3-4

Leaving PDMS, 3-4

LINE command

design aids, 5-19

LIST command, 4-4

LOCK attribute, 8-7

LOCK command, 8-9

MAP command, 5-25

Mapping pins, 7-4

MARK command, 5-18

Master database

of extract, 4-11

MDB command, 4-1

MDB mode, 4-1

Metric units

setting, 3-5

MILLIMETRE command, 3-5

MM command, 3-5

Multiple database, 4-1

querying, 4-6

NAME attribute, 8-7, 8-8

NAME command, 8-8

NEW command, 8-1

NEXT command, 8-12

Obstructing element, 5-6

OBSTRUCTION command, 5-11

ORIENTATION attribute, 8-7, 8-9

OUTPUT command, 4-18

OWNER attribute, 8-7

OWNER command, 8-12

PIN command, 7-5

Position

axial, 2-14

general, 2-16

POSITION attribute, 8-7, 8-9

PRECISION command, 3-6, 3-7

PREVIOUS command, 8-12

QUERY command, 3-10

QUIT command, 3-4

RECREATE command, 3-1

REMOVE command

drawlist, 5-5

RENAME command, 8-6, 8-8

REORDER command, 8-4

REPRESENTATION command

CENTRELINE, 5-8

DARCTOLERANCE, 5-16

HOLES, 5-16

LEVEL, 5-10

OBSTRUCTION/INSULATION, 5-11

PLINES, 5-14

PNODES/SNODES, 5-13

PPOINTS, 5-12

PROFILE, 5-9

TRANSLUCENCY, 5-11

TUBE, 5-8

UPDATE, 5-17

Rules

deleting, 6-3

executing, 6-3

setting, 6-1

verifying, 6-2

SAME command, 8-11

SAVEWORK command, 3-1

Selection

of elements, 2-20

SESSCOMMENT command, 4-8

SESSDATE command, 4-8

Session

comment, 4-5

number, 4-5

Index

Index-4 PDMS DESIGN Reference ManualPart 1: General Commands

Version 11.3

SESSION command, 4-5

SESSION ON command, 4-9

SESSMOD command, 4-7

SESSUSER command, 4-8

SET command


SETSTAR command, 8-13

Significant element, 5-1

SINCE command, 4-17, 4-18

SOLELY command, 5-24

Spatial map, 5-25

SPHERE command

design aids, 5-19

Standard attributes, 8-7

STATIC command


STATUS command, 4-2

Synonym, 8-13

SYSCOMMAND command, 3-9

SYSTAT command, 4-3

System status, 4-3

Text output, 3-9

TRACE command, 3-9

TRANSLUCENCY command, 5-11

TWODPICK command, 7-3

TWODPLANE command, 7-3

TYPE attribute, 8-7

UNENHANCE command, 5-24

Units of measurement, 2-7

setting, 3-5

UNLOCK command, 8-9

UNMARK command, 5-18

UNNAME command, 8-8

User status, 4-2

USERMOD command, 4-7

VERIFY command, 6-2

Visible element, 5-6

Pdms Design

Documents

Transcript of Pdms Design