design reference manual - general commands

Design Reference Manual

General Commands

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

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

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

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

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

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

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries 2007

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

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

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

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

AVEVA Solutions Ltd

DESIGN Reference Manual

Contents Page


General CommandsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1About the DESIGN Reference Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Organisation of the DESIGN Reference Manual . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Organisation of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

How to Use the Syntax Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2Command Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2Standard Syntax Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3Universal Expression <expr> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4Date/Time <date>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4Physical Dimension <uval> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5Design Element Identity <gid> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6D Design Points <marke> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:8Axial Position <pos> <axes> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:9D Position <bpos> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10D Axis Direction <dir>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:11D Direction <bdir> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:12Selection <selatt>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:13

Command Input Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:14

General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Entering DESIGN or Outfitting Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

12.0i© 2007 AVEVA Solutions Ltd


Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Saving DESIGN Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Alpha Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Saving the Alpha Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Clearing the Alpha Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

Leaving DESIGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Changing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Exit from DESIGN without Saving Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3

Setting Working Units and Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Setting Working Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Setting Output Precision of Distance Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5Switching between Actual and Nominal Bores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6

Audible Error Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7Switching Text Output Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7Giving Operating System Commands from PDMS . . . . . . . . . . . . . . . . . . . . . . . 3:8General Querying Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8Querying Your Current Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8Querying Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9Querying Your Current Output Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10Querying the Command Implementation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10Asking for a Unique Workstation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10Querying Elements and Attributes in DBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10

Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Adding Elements to the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Selecting Graphics Colours Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Removing Elements from the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5Defining Colours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6

Element Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8Setting Tube Representation for Piping Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9Setting Profile Representation for Steelwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9Setting Drawing Level Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10Setting Obstruction & Insulation Representation for Piping Components . . . . . . . . . . . . . 4:11Setting Obstruction Representation for Steelwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:12Setting P-Point Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13Setting Structural Node Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14Setting P-Line Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:15Setting Holes Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16

12.0ii© 2007 AVEVA Solutions Ltd


Setting Arc Tolerance Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17Refreshing the Graphical View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:17

Specifying Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:18Graphical Labelling of Design Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19Using Design Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:19Highlighting Components in the Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:22Spatial Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23Checking the Spatial Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:23Creating or Updating Spatial Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:24

Interacting with a Graphical View . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Identifying Displayed Items and Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Identifying Displayed Elements using the Cursor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Identifying Tube using the Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Identifying Displayed Points using the Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Identifying Items with a 2D Pick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4

D Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Setting a Pin’s Position and Direction Explicitly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Making a Pin Visible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5Locating a Pin by Copying or Connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6Moving a Pin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7General Pin Moves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:7

Constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:8ISODRAFT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

12.0iii© 2007 AVEVA Solutions Ltd

12.0© 2007 AVEVA Solutions Ltd i


General Commands

DESIGN Reference ManualIntroduction

1 Introduction

1.1 About the DESIGN Reference ManualThe AVEVA PDMS DESIGN Reference Manual describes all the DESIGN commands indetail. It also describes how the DESIGN database is structured.

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

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

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

• Part 1 (this volume) describes general DESIGN commands, which are used, forexample, for setting up the display, and querying and navigating around the DESIGNdatabase. It also describes how to use the command syntax graphs, which are used toshow all the options available for each command.

• Part 2, Creating the Model, describes the commands for creating database elementsand setting their attributes.

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

1.3 Organisation of this ManualThis manual, Part 1, is divided into the following chapters:

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

• Chapter 3, General Commands, describes commands used for saving work, settingunits and tolerances, and handling alphanumeric output. These commands arecommon to several PDMS modules, but are included here for convenience.

• Chapter 4, Display, describes how to control the way the model is displayed in agraphical view.

• Chapter 5, Interacting with a Graphical View, describes how commands can acceptinput from picked items in the graphical view, and how to define construction aids andlabel the design elements. Note that the commands in this chapter have generally been

12.01 1:1© 2007 AVEVA Solutions Ltd

DESIGN Reference ManualIntroduction

superseded by newer graphical facilities available from the GUI, and are only includedas information for users maintaining older code.

• Chapter 6, Error Messages, explains some of the error messages which may begenerated by DESIGN.


DESIGN Reference ManualHow to Use the Syntax Graphs

2 How to Use the Syntax Graphs

The commands described in this chapter are presented in the form of syntax graphs. • Syntax graphs are read from top left to bottom right. The start point is shown by >, and

you can follow any path through the graph until the exit point, shown by >, is reached.• Points marked with a plus sign (+) are option junctions which allow you to input any

one of the commands to the right of the junction. For example:

>----+--- ABC -----.| ||--- PQR -----|| |‘-------------+--->

• means you can type in ABC or PQR or just press Enter to get the default option.• Text in angle brackets <. . . > is the name of another syntax graph. This convention is

used for syntax which occurs in many places. The graphs referred to are described atthe end of this section. For example:

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

• means you can type in ABC or PQR or any command allowed by the syntax given indiagram <dia> or just press Enter to get the default option.

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

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

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

• means that you can enter any combination of option1 and/or option2 and/or option3,where the options can be commands, other syntax diagrams, or command arguments.

• The simplified format:



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

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

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

2.1 CommandsCommands

These are shown in a combination of uppercase and lowercase letters, where the capitalletters indicate the minimum abbreviation.

Note: This convention does not mean that the second part of the command must be typedin lowercase letters; commands may be entered in any combination of uppercaseand 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 ArgumentsCommand arguments

These are shown in lowercase letters. These are just descriptions of what you need to enter.The most commonly used descriptions are 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

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 descriptivematerial to an appropriate attribute.For example: DUTY ’Low Pressure’



Note: PML 1 expressions and variables are explained in the Software CustomisationReference Manual.

2.3 Standard Syntax GraphsIf a syntax graph refers to a second syntax graph, the name of the second graph is shown inangle brackets. This convention is usually used for standard syntax graphs which are widelyused.

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

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/NOZ

Note: A name should always be followed by a space (unless atthe 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 slash

These are the + (add), - (subtract), * (multiply) and / (divide)operators, which can be used in arithmetic expressions.

For example:

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

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

<expr> Mathematical, textual or logical expressions

<uval> Physical dimension specification

<snoun> or <noun> Design element type

<gid> Design element identity



2.3.1 Universal Expression <expr>If a value given in a command needs to be calculated from other known values, you canenter an expression, which is evaluated by DESIGN as it executes the command.

You will find details of PML 1 expressions in the Database Reference Manual. On-line helpdescribing expressions syntax is available from within DESIGN applications.

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. If no Time is given,Day must be specified.

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

Year may be entered as four digits or as two digits. Two-digit years are interpreted within thedate window

current_year - 99 to current_year

For example, in the year 2004:

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

<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

<expr> Mathematical, textual or logical expressions

03 means 2003

04 means 2004

05 means 1905

Examples:

12:00 22 August 1999

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



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

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

• Millimetres to the nearest millimetre

10:30 Assumes current date

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

22 August Assumes current year and time 23:59

Examples:

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)



• Inches to the nearest 1/32 or 0.1 inch

2.3.4 Design Element Identity <gid>This syntax identifies a Design Element. The main syntax graph is <gid>, shown below. Thesub-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 fromdisplay <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 databasehierarchy

<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 given direction(default is zero);

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

Examples:

/EQUIP10 Named design Element

SAME Previous Element accessed



2.3.5 D 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 ----------|| |

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 EAST Closest valve to current element in East direction indesign model (note that syntax accepts onlycardinal directions, which must be entered in full)

CLOS VALV NORTH FROM E100 N200 U300

Closest valve in North direction starting from givenposition (valves found before this position areignored)

Examples:



|-- PHead -----------|| ||-- PTail -----------|| ||-- HHead -----------|| ||-- HTail -----------|| |‘-- Ppoint integer --+-- OF <gid> --.

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

Cursor:>-- IDPpoint @ -->

2.3.6 Axial Position <pos> <axes>This syntax specifies a 3D position in space in terms of an axial coordinate system.

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

where:

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

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



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

and where:

<nsy> = >--+-- North --.| ||-- Y ------|| |‘-- South --+-- <uval> -->

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

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

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

2.3.7 D Position <bpos>This syntax provides a 3D position in terms of a specified coordinate, a known identity orpoint, or a cursor position.

Examples:

E1000 East 1000

Z10 Up 10

E30 D10 S20 East 30 Down 10 South 20

E0 IN SITE East 0 in Site

General axial position:

(see previous subsection)

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

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

General element identity: <gid> (see above)

Cursor position: >-- @ -->



Note: Cursor positioning (e.g. AXES AT @) can only be carried out in orthogonal views.

2.3.8 D 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 -----|

Examples:

E300 N1000 U2500 Coordinate position

PIN6 Pin position

/VESSEL10 Origin of /VESSEL10

@ Working grid position closest to the crosshair position andthrough the Current Element Origin plane



| | | |‘-- South ---+--> ‘-- West --+-->

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

2.3.9 D Direction <bdir>This syntax provides a 3D direction by making use of a specified axis direction, a designpoint, or two 3D positions.

Examples:

E East

E45N East 45 North

W-33D West 33 Up

Y North

N45E33D North 45 East 33 Down

N10E10 North 45 East

General axial direction: >-- <dir> --+-- <axes> ---.| |‘-------------+-->

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

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

3D position direction:

(see above for <bpos>)

>--+-- FRom <bpos> TOwards <bpos> -->|‘-- TOwards <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



2.3.10 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 specify whether allmembers are to be included, or whether only items (the lowest level components in thehierarchy below a given element) should be included. See <selcla> below.

• A logical expression to be satisfied for all selected elements. These expressionsreturn either True or False, and are usually used to check the values of attributes. Seethe Plant Design Software Customisation Reference Manual.

• A physical volume in which all selected elements must lie. This volume is alwaysorthogonal to the World coordinate axes. You can specify this in terms of two diagonallyopposite points of an enclosing box, or as a volume around an element (with anoptional clearance around the element selected). See <selvol> below.

• A point in the hierarchy below which all selected elements must lie. You can follow thiswith an exclusion list to exclude elements from the selection. See <selhie> below.

• A list (or collection), such as a drawlist, obstruction list or claimlist, of which theselected elements must be members.

All of these criteria are optional, except for class. If all element types are valid, this shouldbe ALL.

If you specify more than one criterion, the specifications must be in the above order, asshown by the following graphs:<selatt>= >-+- ALL -----------------------.

| || .------<-----. || | | |‘- <selcla> -*- <selcla> -’ |

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

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

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

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

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

where <selcla> gives the class of items to be selected:<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 be selected:<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 --+-->

You can minimise the time taken for any selection operation by making the selection criteriaas specific as possible, so that only relevant parts of the databases are searched for therequired elements. Where known, specify the element type (e.g. ALL BOX ...), the databaseelement under which the search is to be restricted (e.g. ALL BOX FOR /ZONE1 ...), thevolume in which you are interested (e.g. ALL BOX WITHIN N5000 E5000 U0 TO N10000E12000 U8000 ...), and so on. If you do not do this, all databases in the current MDB will besearched, whether or not they contain relevant types of element, and performance will beimpaired.

2.4 Command Input ModesGenerally, in DESIGN you are able to access the full range of DESIGN command syntax.However there are two modes where the syntax is restricted to commands only relevant tothat mode. The modes are:

• MDB mode allows you to change or query databases during a DESIGN session.Described in DESIGN Databases and MDBs.

Examples:

ALL Selects all elements

ALL FRMW Selects all framework elements

ALL BRANCH MEMBERS Selects all piping components

ITEMS OF EQUI /VESS1 Selects all primitives below /VESS1

(/PIPE1 /PIPE2) Selects just /PIPE1 and /PIPE2

ALL WITH (XLEN GT 1000)

Selects all elements where XLEN is greater than1000mm

ALL WITHIN W8000N17000U1000 TO W1400N13500U1200

Selects all elements within the defined volume

ALL PIPE WITHIN VOLUME /PIPE1 1500

Selects all piping elements within a volume defined as abox drawn around /PIPE1, with a clearance of 1500mmbetween the edges of /PIPE1 and the volume box.



• DESCLASH mode allows you to check the design for clashes. Described in theDESIGN Reference Manual Part 3: Utilities.

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


DESIGN Reference ManualGeneral Commands

3 General Commands

3.1 Entering DESIGN or Outfitting DesignKeyword:

DESIGN , OUTFITTING

Description:

Use the DESIGN command to enter Plant DESING or in the case of Marine projects use theOUTFITTING command to enter Outfitting Design. These command are availablethroughout PDMS.

3.2 Saving

3.2.1 Saving DESIGN Work See Database Reference Manual Section 7

3.3 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 of output are available,depending on the command used.

ALPHA LOG enables the contents of either or both of the COMMANDS and REQUESTSalpha regions to be written to a file.

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

The ALPHA LOG and ALPHA FILE commands may be used to save data such as theresults of a data consistency check, or be used as a general output facility.



Note: After an ALPHA file has been opened, subsequent output will be directed to both thefile and the screen until the file is closed, or until you change to another PDMSmodule.

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

Examples:

ALP LOG /LF1 COMMANDS Log information displayed in the COMMANDS regionin file /LF1

ALP LOG /LF1 OVER COMM Log information displayed in the COMMANDS regionin file /LF1. Any existing file /LF1 will be overwritten.

ALP LOG /LF Log information displayed in both alpha regions in file/LF2

ALP FILE /LF2 Log information displayed in REQUESTS region only

ALP LOG ENDALP FILE END

Finish logging data

Examples:

ALPHA COMMANDS CLEAR Clears the text from the COMMANDS region only.

ALPHA REQUESTS CLEAR Clears the text from the REQUESTS region only.



Command Syntax:>-- ALPha --+-- COMMands --.

| |‘-- REQuests --+-- CLEAR -->

3.4 Leaving DESIGN

3.4.1 Changing ModulesYou can change to another PDMS module by typing the name of the module. DESIGNautomatically 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 display setup. QUIT has theeffect of deleting any changes made since the last SAVEWORK, module change or MDBchange.

FINISH also exits from DESIGN without saving any changes, but in this case you are takendirectly to the operating system of your computer.

Command Syntax:>-- QUIT --+-- modulename --.

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

>-- FINISH -->

3.5 Setting Working Units and TolerancesThese functions let you set the dimensioning units and precision for design placement andelement searching operations. The designer can choose at any time to work with metric orimperial units and can differentiate between the units used for nominal pipe bores and forgeneral linear dimensions. Tolerance settings are available for general 3D positioning, plusspecial tolerance controls for pipe and structural steelwork layouts. A search radius (the ‘hitradius’) can be specified for cursor picking operations.

Examples:

QUIT Exit from DESIGN (and enter Monitor)

QUIT ISODRAFT Exit from DESIGN and enter Isodraft

FINISH Exit from DESIGN to the operating system



3.5.1 Setting Working Units

Keywords:

Description:

You can choose to work with units for nominal bores and dimensions other than thosespecified in the Catalogue. The PDMS default is to work in millimetres for nominal bores anddistances. However, the Catalogue can contain company-specific instructions that alter thedefaults; say, feet and inches. After the units setting is changed, all input and output will takeplace in the new units unless specifically stated.

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

Command Syntax:>--+-- MILlimetre --.

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

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

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

MILLIMETRE MM INCH FINCH

Examples:

MM BORE All bores will be input and output in mm

FINCH DIS All distances and coordinates will be input and output in feetand inches

UNITS /PERCHES All distances and coordinates will be input and output in theunits defined in the units definition element /PERCHES in theProperties Database

UNITS DEF Uses the default Catalogue database units

UNITS ’Standard’ PDMS units



Querying:

3.5.2 Setting Output Precision of Distance UnitsNote: You must not change the precision if you are customising the AVEVA

Applicationware. You should only use this command if you are writing a completelynew application.

Keywords:

PRECISION

Description:

Output dimensions, in the current units, are normally rounded to the following degrees ofprecision:

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

You may control the output precision of distances in some modules by using thePRECISION command. This allows you to specify the number of decimal places for MM orINCH output, or the largest fraction denominator for FINCH output. Precision levels forgeneral output and for the setting of variables are specified separately.

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 the following:

If opt1 is omitted:• Both Output and Variables are set if opt2 is DEFAULT• Output only is set if opt2 is TO

Q UNIts

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

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)

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)

OUTput For general dimensions

VARiables For setting variables



opt2 defines whether you are changing to a newly-defined precision or back to the defaultsettings. 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 availablechoices are:

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

3.5.3 Switching between Actual and Nominal BoresThe PRECISION command also allows you to output actual bore dimensions (rather thanNominal bore values) when required.

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

PRECISION BORE ACTUAL

To switch back to using nominal bore values:

PRECISION BORE NOMINAL

DECimals Decimal places

DPls Decimal places

THs As in 64ths

NDs As in 32nds

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 INCH units)

PREC OUT DI 4 DEC Set output to 4 decimal places (MM or INCH units)

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

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



3.6 Audible Error TraceKeywords:

ALARM

Description:

When a macro error occurs, there is an audible alarm at the workstation to signal that theerror has occurred. Occasionally, macro errors can be anticipated and no audible warning isrequired. This command 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 is displayed. The defaultsetting is ON .

Command Syntax: >-- ALARM --+-- ON ---.

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

3.7 Switching Text Output OffKeywords:

TRACE

Description:

This command, applicable in TTY mode only, controls the automatic output of the CurrentElement name and attributes. When macros are being run, TRACE is always set to OFFautomatically.

Note: ON is the default setting.

Command Syntax:>-- TRAce --+-- ON ---.

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

Examples:

ALARM ON Sets the audible tone to be on.

ALARM OFF Suppresses the audible tone until it is turned on again.

Examples:

TRACE OFF Stops the automatic output of Current Element name.

TRACE ON Restarts automatic output of Current Element name.



3.8 Giving Operating System Commands from PDMSKeywords:

SYSCOMmand

Description:

PDMS normally assumes that any command input in response to its prompt character (*) isan instruction to the current module, and will check its validity on that assumption. You canissue an operating system (OS) command to the host computer from within PDMS byentering the SYSCOM command followed immediately (without pressing Return) by the OScommand enclosed between apostrophes (’) or vertical bars (|). The effect applies only tothe single command line; as soon as the OS command has been executed, control isreturned to PDMS.

Note: Do not try to issue OS commands which might disrupt PDMS operations; forexample, commands which would close or amend files currently in use by PDMS.

3.9 General Querying FacilitiesYou will often find, when working in PDMS, that you need to check existing informationabout 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 the station you are

running it from (useful for generating unique workfile names).• The current setting, perhaps the default setting, of a command option.• The contents of part of a particular DB; for example, the current setting of an attribute

or the list of member elements owned by a specific element.• 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 willfind more specific querying syntax throughout this set of manuals.)

3.9.1 Querying Your Current ModuleTo check the version number or revision date of your current module, enter one of thefollowing:

Q BANnerQ BANner FULL

This will cause PDMS to redisplay the banner which was shown when you first enteredDESIGN.

Example:

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



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 by DESIGN).

3.9.2 Querying Your SystemTo ask about your current MDB, enter

Q MDB

To output all valid teams for the current user, enter

Q TEAM

To output the current PDMS user name, enter

Q USER

To output your login name, enter

Q LOGIN/NAME

To output the value of an environment variable, enter

Q EVARiable <evar>

Note: If the environment variable name contains any non-letter characters, it must beenclosed 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 by the attribute<att> which can be:

Note: In all the above, environment variables in filenames are always expanded, even forNAME.

NAME The name of the file as typed in the OPENFILE Command

MODE The mode as given in the OPENFILE command

FULLName The fully specified filename

ENTRY 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 increaseas it is written to)

DTM The date and time the file was last modified

OWNER The owner (creator) of the file

LOCK Indicates if the file is locked (valid only for OPENFILE)

SORT Type: File, Directory or Other (e.g. a link)



3.9.3 Querying Your Current Output DevicesTo check the current types of alphanumeric and graphics devices to which DESIGN isexpecting to send your output, especially if you have not changed the default settings, enter

Q DEVice

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

Q DEVice ALPha

Q DEVice GRAphics

To check the current settings for your graphics device, enter any of the following (the list isnot comprehensive):

3.9.4 Querying the Command Implementation ModeTo check the current state of the command implementation mode, that is, whether you haveActions On or Off , enter

Q ACTions

3.9.5 Asking for a Unique Workstation CodeTo generate a unique string, based upon your current process and workstation in use, enter

Q UNIQueid

This returns a unique string, which is machine dependent. This is useful for generatingworkfile names that will not clash with names generated by other users.

3.9.6 Querying Elements and Attributes in DBsTo check what the current element is, enter

Q CE

To check the membership list of the current element, enter

Q MEMbers

The members will be listed in the order of their positions in the membership list.

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

Q SETPens Gives all logical pen settings

Q SETPens number Gives setting for logical pen number

Q LINESTyle Gives line type (dotted, dashed etc.)

Q COLours or Q COLORs Gives colours of all logical colour numbers

Q COLours number ives colour of logical colour number

Q COLours BACKground gives colour set for display background

Q COLours ALPHa Gives colour set for alphabetic characters and so on.



Q OWNer

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

Q LISt

To 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 given type. Theoptional UPDATE can be used to tell you whether the identified element can be updated ornot.

The responses to this query are:

To ask what elements match specified criteria, enter

Q ALL <select>

where <select> is the selection expression. All elements matching your entered selectioncriteria 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 greater than 100 for theattribute 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 attribute list.)

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

Q (<attribute> OF <id>)

For example:

Q (XLEN OF BOX1)

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

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

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

TRUE If you specified <type> and the element exists and is also of the given<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 was used).



and so on.

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

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


DESIGN Reference ManualDisplay

4 Display

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

4.1 Adding Elements to the DisplayKeywords:

ADD COLOUR

Description:

Allows selected Design items to be added to the Draw List, which defines which elementsare to be displayed. If an element is to be displayed in a colour which is different from thedefault colour, this can be specified as part of the command line.

Items added to the display are added to all volume views with the scale and view directionappropriate to that view.

The syntax applies to views attached to a Gobal drawlist.

The Draw List can contain significant elements only. The following is a partial list ofsignificant elements as an example:

EQUI SUBE DATU GRDM PTRA BOUN BRAN HANG PVOL* RPLA* STRU SUBS SCTNPNOD 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 wholesignificant element will be added as well. If an element above a significant element (e.g. aPIPE) is added, then all significant elements owned by that element will be added; not thehigh-level element itself.

Only significant elements (e.g. an EQUI) appear in the drawlist. What appears in the 3Dview are all the primitives (e.g. BOX, CYLI, ...) that are owned by the significant element.ADD ONLY will add the significant element to the drawlist but only add the given primitive(s)to the 3D view rather than all the primitives below the significant element.



Command Syntax:>-- ADD --+-- Only --+ .----<-------.

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

|‘-->

where:<colno> = >--+-- integer --.

| ||-- ACTive ---|| ||-- VISIble --|| ||-- CE -------|| ||-- CLASH ----|| ||-- OBST -----|| |‘-- AIDS -----+-->

Examples:

ADD ONLY /VESS1/N1 adds /VESS1 to the drawlist but only nozzle /VESS1/N1 to the 3D view

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.



Querying:

4.1.1 Selecting Graphics Colours Automatically

Keywords:

AUTOCOLOUR

Description:

Lets you define a set of rules for automating the selection of colours for items added tographical views. Each rule consists of a set of selection criteria for particular types ofelement, together with an associated colour (which may be an explicit colour number or anexpression).

When an element is added to the drawlist, the selection rules are scanned in sequence untila rule is found to be true for that element. The element is then added in the colourcorresponding to that rule. If the colour is invalid, the search is continued. If no rule is truefor the element, the default colour is used. The order in which the rules are set up issignificant, since the first rule found to be true determines the colour.

Automatic colour selection may be switched on or off as required. If it is on, the colourspecified by the rule is used rather than any other colour entered as part of the ADDcommand. If dynamic autocolouring is specified, the autocolour will be checked every timean attribute is changed and, if necessary, the relevant element will be re-added in thecurrent colour.

Each autocolour may be drawn either as a solid colour (default) or as a translucent shade. Ifusing translucency, you can also specify whether or not the edges of an item should bedrawn (as in wireline mode) to give a more distinct outline.

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 the colourwith which each Draw List member was added

Q DRAW r COLOUR Queries the colour number of the referenced item, r. Itreturns unset if the item is not in the Draw List.

Q DRAW r TRANSLUENCY Queries the translucency number of the referenceditem, r. It returns unset if the item is not in the Draw List.

Examples:

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

AUTOCOLOUR ALL EQUI COLOUR 4 TRANSLUCENCY 25 EDGES ON

All Equipment items to be added in colour 4with 25% translucency and edges drawn.

AUTOCOLOUR ALL BRAN WITH (HBORE GT 100) COLOUR 10

All Branches with head bores greater than 100to be added in colour 10.



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 actual translucencywill be set to the nearest of 12, 25, 37, 50, 62, 75 or 87(99 = transparent; 0 = opaque).AUTOCOLOUR ON must be in force to see the effect of AUTOCOLOUR DYNAMICON.

AUTOCOLOUR ALL SCTN COLOUR (:COLOUR OF SPRE)

All Sections to be added as defined by theUDA :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 if allother 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 ON Updates autocolour each time an attributechanges. (Use with care!)

AUTOCOLOUR RESET Clears all current autocolour rules.

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

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

Examples:



Querying:

4.1.2 Removing Elements from the Display

Keywords:

REMOVE

Description:

These commands remove elements from the Draw List and the display.

Note: If an element below a significant element (i.e. a primitive) is removed, then thewhole significant element will be removed as well. To avoid this behaviour theRemove ONLY command should be used. REMOVE ONLY will not remove thesignificant element but only remove the given primitive from the 3D view (theprimitives that have been added/removed can be seen on the primitives tab of thedrawlist form). (Note: if the element being added/removed is significant or above asignificant element then ADD/REMOVE ONLY will have the same effect as ADD/REMOVE).

Q AUTOCOLOUR NUMber Gives number of colour rules.

Q AUTOCOLOUR MODE Queries autocolour mode; i.e. On or Off.

Q AUTOCOLOUR integer Gives selection criteria for rule integer.

Q AUTOCOLOUR DYNAMIC Checks whether dynamic updating is on or off.

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

Q AUTOCOLOUR FOR id TRANSLUCENCY

Queries translucency setting for identifiedelement.

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

Examples:

REMOVE ONLY /VESS1N1 removes only nozzle /VESS/N1 from the 3D view

REMOVE /BRANCH1 BRANCH1 will be removed from the Draw List andthe display

REM SITE /PIPING The site /PIPING will be removed

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



Command Syntax:>-- REMove --+-- Only --+

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

4.1.3 Defining Colours

Keywords:

COLOUR ACTIVE CE VISIBLE CLASH OBST AIDS

Description:

These commands allow colours to be defined so that different types of item in the displaymay be distinguished by means of colour. Certain items such as current element and activeelement colours have default settings, but these may also be redefined.

The colours may be assigned by using the COLOUR command to define the Red-Green-Blue mix for a colour number or to assign a predefined colour mix by name. DESIGN allowsthe use of 115 user-definable colours, plus some specific ones which are assigned to itemswhich need to be readily distinguishable in the display.

Definitions:

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

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

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

• A Clashing element is an element whose current position and geometry are beingtested for interferences against other elements in the design and which has been foundto clash (see Design Reference Manual Pt 3: Utilities).

• An Obstructing element is any of the elements in the design against which a clashingelement is being tested for interferences and which has been found to clash (seeDesign Reference Manual Pt 3: Utilities).

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

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

Predefined Colour Mixes

black pink darkgreen beige

white salmon cyan wheat

whitesmoke orange turquoise tan

ivory brightorange aquamarine sandybrown

grey orangered blue brown

lightgrey maroon royalblue khaki

darkgrey yellow navyblue chocolate

darkslate gold powderblue darkbrown



The default colour assignments are:

red lightyellow midnight blueviolet

brightred lightgold steelblue firebrick

coralred yellowgreen indigo darkorchid

tomato springgreen mauve dimgrey

plum green violet coral

deeppink forestgreen magenta indianred

lightblue limegreen mediumaquamarine sienna

stateblue

Colour No Colour

Active design orange

Current element yellow

Visible design lightgrey

Clashing element red

Obstructing element tomato

Aids blue

1 grey

2 red

3 orange

4 yellow

5 green

6 cyan

7 blue

8 violet

9 brown

10 white

11 pink

12 mauve

13 turquoise

14 indigo

15 black

16 magenta

Predefined Colour Mixes



Note: When colours are mixed in their Red, Green and Blue constituents, the commandline must contain values for all three constituents in the correct order. The numbersentered for the relative proportions of the basic colours must each be in the range 0-100, but they are not percentages of the overall colour and so do not need to add upto 100.

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

Querying:>-- Q COLour --+-- integer -----.

| ||-- CE ----------|| ||-- ACTive ------|| ||-- VISIble -----|| ||-- CLASH -------|| ||-- OBST --------|| |‘-- AIDS --------+-->

4.2 Element RepresentationThere are a number of options which determine how items in the graphical display are to beshown on the screen. These are controlled by the REPRESENTATION command.

Examples:

COL 5 DARKGREEN Colour 5 will be changed to dark green

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

COL ACTIVE BRIGHTRED Sets the colour for displaying active elementsto bright red



4.2.1 Setting Tube Representation for Piping Components

Keywords:

REPRESENTATION TUBE CL (CENTRELINE)

Description:

The REPRESENTATION command allows tubing to be represented in a centreline or as asolid tube. In some cases, it helps to switch between the two representations to simplify anotherwise complicated view.

TUBE and CENTRELINE representation are not instantly updated on the screen. To see theeffects of a representation change, use the REPResentation UPDATE command to makeany changes visible.

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

/ |>-- REPResentation --*-- CL -------------------------. |

| | ||-- CENTreline -----------------| || | |‘-- TUbe -----------------------+-- ON ---|

| |‘-- OFF --+->

Querying:

4.2.2 Setting Profile Representation for Steelwork

Keywords:

REPRESENTATION PROFILE

Examples:

REPR TUBE ON CL OFF Sets tubing representation as solid tube.

REPR CL ON TUBE OFF Sets tubing representation as centreline.

REPR TUBE ON CL ON Sets both types of representation on (but centreline willnot be visible in colour-shaded mode, as it will be hiddenby solid tube).

Q REPR TUBE

Q REPR CL

Q REPR PROF

Q REPR Queries all Representation options.



Description:

The REPRESENTATION PROFILE commands allow structural steel profiles to berepresented in a centreline or solid profile format. In some cases, it helps to switch betweenthe two representations to simplify an otherwise complicated view.

TUBE and CENTRELINE representation are not instantly updated on the screen. To see theeffects of a representation change, use the REPResentation UPDATE command to makeany changes visible.

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

/ |>-- REPResentation --*-- PROFile --+-- CL -----------. |

| | ||-- CENTreline ---| || | ||-- OBSTruction --| || | |‘-- INSUlation ---+-- ON ---|

| |‘-- OFF --+->

Querying:

4.2.3 Setting Drawing Level Representation

Keywords:

REPRESENTATION LEVEL

Description:

This command enables individual drawing levels to be specified for the display of piping,nozzles, structural elements and other design database elements.

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

Examples:

REPR PROF ON CL OFF Sets profile representation as solid profile.

REPR PROF CL ON TUBE OFF Sets profile representation as centreline.

REPR PROF ON CL ON Sets both types of representation on.

Q REPR PROF TUBE

Q REPR PROF CL

Q REPR Queries all Representation options.



The practical effect of this facility is that it allows you to minimise visible detail whenrepresenting Design items. For example, at drawing level 3 steelwork may be representedas single line only, whereas at level 1 the full detail may be visible. Level 3 may well beadequate for design purposes.

LEVEL manipulation is not instantly updated on the screen. To see the effects of a levelchange, use the REPResentation UPDATE command to make any changes visible.

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

/ |>- REPResentation --*-- LEVel --+-- PIPE -------. |

| | ||-- NOZZle -----| || | ||-- STRUcture --| || | |‘---------------+-- integer --+->

Querying:

4.2.4 Setting Obstruction & Insulation Representation for Piping Components

Keywords:

REPRESENTATION OBSTRUCTION INSULATION TRANSLUCENCY

Description:

Component Obstructions are often given LEVELS or TUBE and CENTRELINE settingswhich render them invisible. Setting the Representation of OBST On forces the system to

Examples:

REPR LEVEL PIPE 5 Sets piping level to 5. All pipes which are added after thiscommand will be drawn at level 5. Those already in the viewwill remain unchanged.

REPR LEVEL NOZZ 1 Sets Nozzle level to 1

REPR LEVEL 2 Set level for all other Component types to 2

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 as representationlevels



override normal LEVEL and TUBE settings and show all of the primitives, regardless of theother settings.

Setting the Representation of INSU On or Off determines whether or not insulation is shownon primitives.

These have the effect of considering all primitives which have an obstruction level greaterthan zero and all primitives which are affected by insulation parameters. The graphicsdisplay is not updated instantly. Use the REPResentation UPDATE command to make anychanges visible.

To avoid obscuring the view in colour-shaded mode, obstruction and/or insulation can beshown as translucent, the degree of translucency being controllable.

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

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

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

Note: value must be in the range 0-99: the actual translucency will be set to the nearest of25, 50, 75 or 87 (99 = transparent; 0 = opaque).

Querying:

4.2.5 Setting Obstruction Representation for Steelwork

Keywords:

REPRESENTATION PROFILE OBSTRUCTION ON/OFF TRANSLUCENCY

Description:

Structural Steel Obstructions are often given LEVELS or TUBE and CENTRELINE settings,which render them invisible. Setting the Representation of OBST On forces the system to

Examples:

REPR OBST ON INSU OFF

REPR INSU ON

REPR INSU ON TRANSLUCENCY 25

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 TRANSL Queries translucency setting for insulation



override normal LEVEL and TUBE settings and show all of the primitives, regardless of theother settings.

Setting the Representation of INSU On or Off determines whether or not insulation is shownon primitives.

These have the effect of considering all primitives which have an obstruction level greaterthan zero and all primitives which are affected by insulation parameters. The graphicsdisplay is not updated instantly. Use the REPResentation UPDATE command to make anychanges visible.

To avoid obscuring the view in colour-shaded mode, obstructions can be shown astranslucent, the degree of translucency being controllable.

Command Syntax:> REPResentation--PROFile--OBSTruction -+- ON - TRANSLucency - value --.

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

Note: value must be in the range 0-99: the actual translucency will be set to the nearest of25, 50, 75 or 87 (99 = transparent; 0 = opaque).

Querying:

4.2.6 Setting P-Point Representation

Keywords:

REPRESENTATION PPOINTS LENGTH NUMBERS

Description:

P-point representation may be set to ON or OFF. The default setting is PPOINTS OFF,although p-points will be shown automatically as part of an identification operation.

When p-points are on, they are drawn as small arrows with a cross at the p-point positionand with the arrow indicating the p-point direction. The size of the arrow is controlled by theLENGTH option. P-point numbers may also be displayed, as controlled by the NUMBERSoption.

Examples:

REPR PROF OBST ON

REPR PROF OBST OFF

REPR PROF OBST ON TRANSLUCENCY 25

Q REPR PROF OBST TRANSL Queries translucency setting for obstructions



As with changes to other representation settings, the graphics display is not updatedinstantly. Use the REPResentation UPDATE command to make changes to the display of p-points visible.

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

/ |>-- REPResentation --*-- PPoints --+-- ON ---|

| ||-- OFF --+-->||-- LENgth -- value -->|‘-- NUMbers --+-- ON ---.

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

Querying:Q REPR PPOINTS

4.2.7 Setting Structural Node Representation

Keywords:

REPRESENTATION PNODES SNODES

Description:

These options allow Primary and/or Secondary Nodes on structural steelwork items to beshown on the display in specified colours and sizes.By default, both types of node are shown in the current visible colour, with a size equivalentto 10mm diameter.

Examples:

REPR PPOINTS ON Sets the p-point representation to ON

REPR PPOINTS LENGTH 5 Sets size of p-point arrows

REPR PPOINTS NUMB ON Shows p-point numbers

Examples:

REPR PNOD ON Only Primary Nodes will be shown in the display.

REPR SNOD OFF The display of Secondary Nodes will be suppressed.

REPR PNOD COL BRIGHTRED

Primary Nodes will be shown in bright red colour.



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

/ |>-- REPResentation --*-- PNODes --. .-------------------. |

| |/ | |‘-- SNODes --*-- ON ---------------| |

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

Querying:Q REPR PNODQ REPR PNOD SIZEQ REPR PNOD COLQ REPR SNODQ REPR SNOD SIZEQ REPR SNOD COL

4.2.8 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 isPLINES OFF.

When p-lines are on, the size of the arrow showing their direction is controlled by theLENGTH option. P-line identifiers, in the form of the settings of their PKEY attributes (TOS,BOS, NA, etc.) may also be displayed, as controlled by the PKEY option.

As with changes to other representation settings, the graphics display is not updatedinstantly. Use the REPResentation UPDATE command to make changes to the display of p-lines visible.

REPR SNOD COL 12 Secondary Nodes will be shown in the currently defined mixfor colour number 12.

REPR PNOD SIZE 15REPR SNOD SIZE 6

Primary Nodes will be emphasised by being drawn at 15mmdiameter, while Secondary Nodes are drawn at only 6mmdiameter.

Examples:



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

/ |>-- REPResentation --*-- PLINes --+-- ON ---|

| ||-- OFF --+-->||-- LENgth -- value -->|‘-- PKEY --+-- ON ---.

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

Querying:Q REPR PLINES

4.2.9 Setting Holes Representation

Keywords:

REPRESENTATION HOLES

Description:

Determines the appearance of holes in volume views. ON gives a more realistic view of ahole, with objects behind the hole being visible through it. OFF represents holes aspatterned regions on the surface of the component.

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

/ |>-- REPResentation --*-- HOLes ---+-- ON ---|

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

Querying:Q REPR HOLES

Examples:

REPR PLINES ON Sets the p-line representation to ON

REPR PLINES LENGTH 6 Sets size of p-line arrows

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

Example:

REPR HOLES ON Sets the holes representation to ON



4.2.10 Setting Arc Tolerance Representation

Keywords:

REPRESENTATION DARCTOLERANCE

Description:

Controls the arc tolerance used when representing certain curves as polygon segments orfaceting planes. The smaller the arc tolerance, the smoother the curve drawn, but the slowerthe graphical performance.

The tolerances used for most curve drawing in DESIGN are controlled automatically by thegraphical system. The REPRE DARC command controls the following aspects only:

Filleted vertices used in the representation of extrusions; for example, Section Profiles fromthe Catalogue, Panel Loops, etc.

Items which include holes (but only when REPRE HOLES is set to On; see Setting HolesRepresentation).

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

Command Syntax:>-- REPResentation -- DARCtolerance --+-- <uval> ---.

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

Querying:Q REPR DARC

4.2.11 Refreshing the Graphical View

Keywords:

REPRESENTATION UPDATE

Description:

Lets you refresh the graphical display, after modifying any of the representation settings,without having to remove and add back all items in the drawlist.

Example:

REPR DARC 5 Sets the arc tolerance to 5 mm.

REP DARC DEF Resets arc tolerance to 10 mm.

Example:

REPR UPDATE



Command Syntax:>-- REPResentation -- UPDATE -->

4.3 Specifying Axes Keywords:

AXES

Description:

Lets you specify and position a set of axes on the display. The axes represent the compassdirections of the World co-ordinate system and may be positioned anywhere on the display.

Axes remain visible until they are switched off or deleted. Switching axes off renders theminvisible, whilst deletion removes them altogether. Switched-off axes can be made visibleagain by switching them back on.

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

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

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 aheight of 300mm (default size is 1000mm)

AXES OFF Removes axes from the screen (although they still exist)

AXES ON Redisplays axes as previously shown.

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



4.4 Graphical Labelling of Design ElementsKeywords:

MARK UNMARK

Description:

This facility allows specific design elements or lengths of Tube to be labelled in the display.

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

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

You can specify selection criteria for marking, and specify any textual expression for themarker.

Command Syntax:>-- MArk --+-- WITH -- text expression --.

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

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

4.5 Using Design AidsKeywords:

AID LINE ARROW CEARROW ARC SPHERE BOX CYLINDER

Examples:

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

UNMARK /DATUM5 The specified element will cease to be labelled.

MARK WITH ’Outer Boundary’ ID @

Labels the picked element with the given text.

MARK WITH NAME ALL BRAN

Labels all Branches with their PDMS names.

MARK WITH NAME OF SPREF ALL VALVE WHERE PBORE GT 100

Labels all valves larger than the specified bore with theirspecification references in the catalogue.

UNMARK ALL Removes all marking from the screen.



Description:

This facility lets you incorporate lines, arrows, arcs, spheres, boxes or cylinders in a view tohelp you with the design construction. Design aids can be grouped together (using theNUMBER option) and given a number for identification.

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

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

A special aid arrow, the CEArrow, is positioned automatically to point to the current element.You can specify whether the arrow points to the Origin (default), P-arrive or P-leave of thecurrent element.

Note: These terms relate primarily to piping components. For other element types, they areinterpreted 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 and either a third 'through'point or a tangent point through which a second-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, and X,Y,Z dimensions. Theymay be drawn in wireline mode (like penalty volumes or clipping boxes) or in solid mode(like box primitives).

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

Command Syntax:>- AID LINE -+--------------.

| |

Examples:

AID LINE E1200S3500U0 TO E760N1200U50

Draws a line between the two 3D positions.

AID LINE NUMBER 5 E1200S3500U0 TO E760N1200U50 LINESTYLE DOTTED

Groups the new line with other such lineswith the same number (5 this example) anddraws it in the dotted linestyle.

AID CLEAR LINE 5 Deletes line number 5

AID ARROW AT E760N1200U50 DIR E HEI 100 PROP 0.5

Positions 100mm arrow with given positionand direction; arrow head is 50mm long.

AID BOX POS PIN 6 ORI X IS UP Y TOWARDS /PUMP1 XLEN 200 YLEN 200 ZLEN 200 FILL OFF

Positions a wireline cubic box, with 200mmsides, at Pin 6 with the specified orientation.

AID CLEAR SPHERE UNNd eletes all unnumbered aid spheres.



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

>- 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 all arcs may berepresented in this way.

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

(Gives next available aid number for specified type)

4.6 Highlighting Components in the DesignsKeywords:

ENHANCE UNENHANCE SOLELY

Description:

This facility lets you highlight components visually in the design. For example, all sections ofimplied tube and rod could be highlighted, all piping components and so on.

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

The SOLELY keyword clears all previous highlighting before highlighted the definedcomponents.

You can also highlight specific lengths of tube or rod.



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

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

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

4.7 Spatial MapsSpatial maps of the model are based on the obstruction limit boxes surrounding eachDesign element, rather than using fully detailed geometric representations. The spatialmaps allow faster data access, and they are used for tasks such as clash detection wherefast data access is required and where the simplified representation is adequate.

Spatial maps are maintained automatically as the design model is updated, but may need tobe rebuilt explicitly if the Catalogue data, from which the map geometry is derived, ischanged.

4.7.1 Checking the Spatial Maps

Keywords:

MAP CHECK

Examples:

ENHANCE SOLELY ALL REDU WITH (ABOR GT 10) COLOUR 13

Highlights all RED components that match theselection criteria with colour 13 (turquoise)

ENHANCE /PIPE1 /PIPE2 COLOUR 5

Highlights PIPE1 and PIPE2 in green

ENHANCE LENGTH 20 OF LEAVE TUBE COLOUR 7

Highlights 20mm of LEAVE TUBE in blue



Description:

You can check one or more of the spatial maps to ensure that they accurately reflect thecurrent state of the design. To avoid spurious results, it is advisable to do this beforecarrying out a clash check. This is particularly important if the geometry of any geometryelements has been modified.

Command Syntax:>--- MAP CHEck ---+--- MDB -------------------------------.

| || .-----------<---------. || / | |‘--- word ---*--- name --+-- word ---’ |

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

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

4.7.2 Creating or Updating Spatial Maps

Keywords:

MAP BUILD

Description:

Lets you update existing spatial maps to take into account all design and catalogue changeswhich have taken place. This is only necessary if the MAP CHECK command (Checking theSpatial Maps) shows that the map is out of date.

Command Syntax:>--- MAP BUIld ---+--- MDB --->

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

Examples:

MAP CHECK MDB Checks the spatial maps for all DESIGN DBs within thecurrent MDB against the current design and cataloguedata. If there are any discrepancies, appropriatemessages are output; you should then rebuild the map(see Creating or Updating Spatial Maps)

MAP CHECK PIPES/AREA1 Checks the up-to-date status of the spatial map for thenamed DESIGN DB only.

Examples:

MAP BUILD MDB Updates the spatial maps for all DESIGN DBs within thecurrent MDB.

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



| / |‘--- word ---*--- name ---+--- word ---’

|‘--->

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


DESIGN Reference ManualInteracting with a Graphical View

5 Interacting with a Graphical View

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

5.1 Identifying Displayed Items and PointsA displayed element from the visible model can be accessed directly by moving the cursorover it and clicking the left-hand mouse button. The following sections describe the differentways of selecting database elements from the display by using the cursor. Thesecommands let you use the visible design in order to move to elements in the DESIGNhierarchy and points in 3D space.

In each case, an appropriate prompt is displayed.

5.1.1 Identifying Displayed Elements using the Cursor

Keywords:

IDENTIFY

Description:

If a particular type of element is to be located, a selective search can be made using theIDENTIFY command followed by a keyword identifying the element type. If a specificelement type is not requested, the element hit will always be a geometric primitive orcomponent. Any displayed line or p-point of an item may be hit. To abort, press the Cancelbutton on the displayed form.

Examples:

ID @ Pressed Enter (or Return), move the cursor over the desireditem and click the left-hand mouse button. The name of theelement under the cursor is displayed on the command line.The picked element becomes the current element and isdisplayed in a different colour. (This is the general responseto all variations of the IDENTIFY command.)

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



Command Syntax:>-- IDentify ----+-- <snoun> --.

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

5.1.2 Identifying Tube using the Cursor

Keywords:

IDENTIFY TUBE

Description:

Variable length Tube (and Rod) from the visible design can be accessed by picking with thecursor. As Tube is not an element in the DESIGN hierarchy, it cannot be accessed. Instead,the component on the upstream side of the Tube (downstream if routing backwards) will beaccessed. This means that the next component to be created will be inserted in the pickedTube. Any visible Tube can be picked regardless of whether it is shown in single or doubleline representation.

Command Syntax:>-- IDentify Tube @ -->

5.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 any mapping pin. Thisform of picking will not change the current element.

Note: IDPPOINT cannot be used in isolation. It must be used with another command.Only those p-points which are defined in the Catalogue as being visible in DESIGNwill be available for picking in this way.

Example:

ID T @ The name of the component on the upstream side of the Tube underthe cursor is displayed on the command line.



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

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

Example:

Q IDP @ Press and hold down left-hand mouse button when cursor is overelement. Element will be highlighted with p-points visible and cursor willchange to a square shape. With left-hand mouse button still held down,move cursor over required p-point. When over a p-point, cursor willchange to a square shape with crosshairs. Release the button to selectthe p-point



5.1.4 Identifying Items with a 2D PickUse 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 view direction. You can then usethe cursor to pick a point in an orthogonal view such that the third coordinate of the requiredpoint is derived automatically from this plane.

The TWODPLANE command defines the 2D picking plane in terms of a point within theplane.

The AT TWODPICK @ command may then be used to request a cursor position whichidentifies a point within the 2D picking plane. The plane is generated dynamically from theTWODPLANE point and the view direction.

Note: Cursor positions are always returned in World coordinates. In order to obtain thecorrect result, the 2D picking plane must therefore be set to an absolute Worldposition.

Command Syntax:>-- TWODPLane -- <bpos> -->>-- AT TWODPick @ -->

Querying:>-- Q -- TWODPLane -->

5.2 D PinsThe Design pins are a set of ten temporary marker points which have a 3D position anddirection. They can be moved around using positioning and orientation commands similar tothose available for permanent Design elements.

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

The commands described here only show how to make pins visible and position andorientate them. Once this has been done they can be used for positioning and orientatingDesign elements in any command that uses point as an argument.

Examples:

TWODPLANE E 1000 N 2000 U 500

Defines 2D picking plane which passes through given pointand which is normal to view direction

AT TWODPICK Using the preceding 2D picking plane definition, a cursor hitat E 1234 N 5678 in a plan view will return the position E1234 N 5678 U 500 in World coordinates



5.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 same way as an ordinarydesign element. Unless stated otherwise, the positional parameters described below are inthe coordinate system of the current element.

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

5.2.2 Making a Pin Visible

Keywords:

PIN

Description:

This command allows a particular pin to be switched in and out of the Display.

When a pin is visible, it will be drawn as a numbered arrow marker which indicates itsposition and direction in each volume view. Visible pins can be hit with the cursor during anyIDPPOINT operation. When a pin is switched off, it is erased from the display, but it stillexists and can be referred to by name.

Examples:

PIN 5 AT E1000 Pin 5 will be moved to the coordinate position East1000 from the Site origin.

PIN5 DIR W WRT SITE Pin 5 will be orientated in a direction West with respectto the current SITE.



Command Syntax:>-- PIn integer ----+-- OFF --.

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

Querying:

(As in previous subsection.)

5.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 to any other p-point orpin, the only difference being that the CONNECT operation orientates the specified pin inthe opposite direction (see examples below).

Command Syntax:>-- PIn integer --+-- Copy --------------.

| |‘-- CONnect --+-- TO --|

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

Querying:>-- Q PIN integer --+-- POSition ---.

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

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

Examples:

PIN 5 Pin 5 will be drawn into all volume views, and can be hit by thecursor.

PIN 5 OFF Pin 5 will be erased.

Examples:

PIN 5 C0PY IDP @ Pin 5 will be placed at the same position and orientationas the p-point or pin hit by the cursor.

PIN 5 CONNECT TO PH Pin 5 will be placed at the Branch Head, but pointing inthe opposite direction to HDIR (Head direction). Thiscommand must be given at BRANCH level. Pin 5 can bean existing pin or a new one.



5.2.4 Moving a Pin

Keywords:

PIN BY THROUGH DISTANCE

Description:

These commands allow a pin to be moved from its current position in any axis direction oralong its own direction. If moved along its own direction, a specified distance can be givenor, alternatively, an intersection. (Moving in this manner is very similar to the pipe-routingoptions.)

Command Syntax:>-- PIn integer --+-- BY <pos> ---------.

| ||-- THRough <bpos> ---|| |‘-- DISTance <uval> --+-- WRT --.

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

Querying:>-- Q PIN integer --+-- POSition ---.

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

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

5.2.5 General Pin Moves

Keywords:

PIN

Description:

Pins may be moved in exactly the same manner as piping components, using the samecommand options. The movement direction is always in the pin direction, so it is importantto ensure that this is appropriate before a move is attempted. As these commands are quiteextensive, they are not repeated here; see the pipe routing commands in Design ReferenceManual Pt 2: Creating the Model.

Examples:

PIN 6 BY E3000 N2000 Pin 6 is moved by the given directions and distances

PIN 6 DIST 600 Pin 6 is moved along its own direction by the givenamount

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



Command Syntax:>-- PIn integer <plane> -->

5.3 ConstructsNote: Use the Constructs options on the Utilities menu in preference to these older

facilities.

Keywords:

CONSTRUCT POSITION DIRECTION DISTANCE ANGLE LINE PLANE

Description:

The construction aids available in DESIGN let you display coordinates, directions,distances, angles and plane definitions.

The constructed quantities are written out into the REQUESTS region of your display. Thesequantities can be written into variables for later use. The commands used to defineconstructed quantities make use of p-points, p-lines, pins, directions, positions andorientations.

The different methods for constructing these entities are:• CONStruct Angle

position1 TO position2 TO position3direction1 AND direction2line1 line2line planeplane1 plane2plane line

• CONStruct DISTanceposition1 TO position2position TO lineposition TO planeline1 TO line2 projection of any of the above ALong a given direction

• CONStruct PositionNEArest position ON lineNEArest position ON planeINTersect plane1 plane2 plane3INTersect line planeINTersect line1 line2 (gives result on line1 if lines are skew or parallel) plane line

• CONStruct DIRection

Example:

PIN 6 DISTANCE 600 INFRONT ID @

Pin 6 is moved along its direction until it is 600 distance unitsin front of the item picked with the cursor.



NORmal planeORTHogonal direction1 AND direction2ORTHogonal direction AND lineORTHogonal line1 AND line2ORTHogonal line AND directionposition1 TO position2planeline

• CONStruct LINeJOIn position1 TO position2direction THRough position PARallel line THRough position NORmal line THRough position NORmal plane THRough position PROJection line ON plane INTersect plane1 plane2

• CONStruct PlaneTHRough position1 AND position2 AND position3direction THRough positiondirection THRough a p-point, pin or digitised point (optionally offset a given DISTanceor relative to existing geometry: INFront or BEHind an element, p-point or position:FROm or TO a position)

Note: In all of the above, position, direction, line or plane is defined in normal PDMSformat, or by reference to a p-point, pin or marker, or picked from an appropriateview.

Examples:

CONS POS P2 OF FLAN 4 OF BRAN /PIPE1-1 TO PLANE PIN 7

The intersection between the specifiedpoint and the plane perpendicular to pin 7is shown.

VAR 5 CONS POS PL TO LINE PA OF NEXT

The closest point on the line fromPLEAVE to the intersection of the twolines is placed in Variable 5.

CONS POS PIN5 TO PLA PIN6 The intersection between the direction ofpin 5 and the plane perpendicular to pin 6is written out into the request region.

CONS DIR PL The direction of the line is output in Worldcoordinates into the request region.

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

VAR 5 CONS DIST PL TO LIN PA OF NEXT

The minimum distance between PLEAVEof the current element and the specifiedline will be be placed in Variable 5



5.4 ISODRAFT ModeKeywords:

ISODRAFTMODE

Description:

Enables you to enter (a subset of) ISODRAFT syntax within DESIGN. You are thus able toproduce an Isometric plot without having to switch modules.

Note: This syntax is included here for completeness, but you would normally produce“check Isos” in DESIGN using the GUI.

Command Syntax:

>-- ISODRAFTMODE --.|(Isodraft syntax available)|‘-- EXIT > (Return to Design syntax.)

CONS ANG PIN1 TO PIN2 TO PIN3 The angle between the three specifiedpoints is written out into the Requestregion.

CONS ANGL PL LIN PA OF NEXT The angle between the lines from the twospecified p-points is written out into therequest region.

CONS LINE JOIN P0 TO P1 Constructs a line joining the two p-points,displaying the line description in therequest region.

CONS PLANE P3 DIST 900 The plane perpendicular to the specifiedpoint and 900 from it is written out into therequest region.

CONS PLANE PL THROUGH /NOZZ5 The plane perpendicular to the specifiedpoint and intersecting /NOZZ5 is writtenout into the request region.

CONS PLANE PA DIST 500 BEH /COL19

A plane perpendicular to the specifiedpoint will be defined and written out intothe request region. The plane will bepositioned 500 to the far side of /COL19.

Examples:


DESIGN Reference ManualError Messages

6 Error Messages

This chapter lists error messages specific to DESIGN. These messages have a messagenumber beginning with 61. Any other messages that may be output are not described hereas they are not specific to DESIGN.

Note that in the following element_identifier denotes an element name or (for unnamedelements) an element reference number. The latter is a ‘system’ number which is assignedautomatically 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 beenpositioned 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 positionedand 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 beselected

(61:29) element_identifier is not a SPEC

(61:30) element_identifier is not a SPCOM

(61:31) Cannot find SPCOM name

(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 backto 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 hangercomponents.

(61:42) Default movement direction not available. Previous element either notpositioned and oriented or not selected.

(61:43) ARRIVE / LEAVE ppoint cannot be determined. Current element hasprobably 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 incorrect plane.

(61:49) Unable to achieve specified direction - probably due to unconventionalpointset

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

(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

(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 inuse when module state SAVEd

(61:139) Unable to RESTORE - module version number/screen size/font size is notthe 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 onlydatabase. This connection will be broken by drag.

(61:152) element_identifier has a connection to an unknown element. Thisconnection 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 brokenby drag.

(61:155) Attachment points can only be dragged if they have been positioned andoriented

(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 criteria

(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 MONITORmodule

(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 drawlistto avoid fatal error.

(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 viewand 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 sameposition - UP is assumed

(61:304) Position cannot be calculated as lines are parallel - first point given isassumed

(61:305) Position cannot be calculated as line and plane are parallel - first pointgiven 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 beadded 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 allsites 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

(61:800) Reference DETAIL not set

(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


Index


AAccessing . . . . . . . . . . . . . . . . . . . . . . 1-3:1Active element . . . . . . . . . . . . . . . . . . 1-4:6ADD command:drawlist . . . . . . . . . . . 1-4:1AID command . . . . . . . . . . . . . . . . . . 1-4:19Aids:graphical . . . . . . . . . . . . . 1-4:6, 1-4:19ALARM command . . . . . . . . . . . . . . . . 1-3:7ALPHA CLEAR command . . . . 1-3:1, 1-3:2ALPHA FILE command . . . . . . . . . . . . 1-3:1ALPHA LOG command . . . . . . . . . . . . 1-3:1ARC command:design aids . . . . . . . 1-4:19ARROW command:design aids . . . . 1-4:19Audible error trace . . . . . . . . . . . . . . . 1-3:7AUTOCOLOUR command . . . . . . . . . 1-4:3AXES command . . . . . . . . . . . . . . . . 1-4:18

BBOX command:design aids . . . . . . . 1-4:19BUILD command:spatial maps . . . . . 1-4:24

CCEARROW command:design aids . . 1-4:19Changing modules . . . . . . . . . . . . . . . 1-3:3CHECK command:spatial maps . . . . 1-4:23Clashing element . . . . . . . . . . . . . . . . 1-4:6CLOSEST

command . . . . . . . . . . . . . . . . . . . 1-2:7COLOUR command . . . . . . . . . . . . . . 1-4:6COLOUR command:displayed items . 1-4:1Colour mixes:predefined . . . . . . . . . . . 1-4:6Colours:active element . . . . . . . . . . . . 1-4:6Colours:clashing element . . . . . . . . . . 1-4:6

Colours:current element . . . . . . . . . . . . 1-4:6Colours:default assignments . . . . . . . . 1-4:6Colours:defining . . . . . . . . . . . . . . . . . .1-4:6Colours:graphical aids . . . . . . . . . . . . . 1-4:6Colours:obstruction element . . . . . . . . 1-4:6Colours:visible element . . . . . . . . . . . . 1-4:6Commands:input mode . . . . . . . . . . . 1-2:14CONSTRUCT command . . . . . . . . . . .1-5:8Construction aids . . . . . . . . . . . . . . . . . 1-5:8Coordinates . . . . . . . . . . . . . . . . . . . . . 1-2:9Current element . . . . . . . . . . . . . . . . . .1-4:6CYLINDER command:design aids . . . 1-4:19

DDate . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2:4DESIGN . . . . . . . . . . . . . . . . . . . . . . . .1-3:1Design aids . . . . . . . . . . . . . . . . . . . . 1-4:19DESIGN command . . . . . . . . . . . . . . . .1-3:1Design points . . . . . . . . . . . . . . . . . . . . 1-2:8Dimensions . . . . . . . . . . . . . . . . . . . . . 1-2:5Direction:axial . . . . . . . . . . . . . . . . . . . 1-2:11Direction:general . . . . . . . . . . . . . . . .1-2:12Draw list . . . . . . . . . . . . . . . . . . . . . . . .1-4:1Drawing levels . . . . . . . . . . . . . . . . . .1-4:10

EElements:identifying . . . . . . . . .1-2:6, 1-2:13Elements:selecting . . . . . . . . . . . . . . .1-2:13ENHANCE command . . . . . . . . . . . . . 1-4:22Entering . . . . . . . . . . . . . . . . . . . . . . . .1-3:1Errors:alarm . . . . . . . . . . . . . . . . . . . . .1-3:7Expressions . . . . . . . . . . . . . . . . . . . . . 1-2:4

12.0Index page 1© 2007 AVEVA Solutions Ltd


FFINCH command . . . . . . . . . . . . . . . . 1-3:4FINISH command . . . . . . . . . . . . . . . . 1-3:3

GGraphical aids . . . . . . . . . . . . . . . . . . 1-4:19axes . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:9bdir . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:12bpos . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:10date . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:4dir . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:11expr . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:4marke . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:8pos . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:9selatt . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:13uval . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2:5

HHighlighting graphical items . . . . . . . 1-4:22

IID @ command . . . . . . . . . . . . . . . . . . 1-5:1IDENTIFY command . . . . . . . . . . . . . . 1-5:1Identifying displayed items . . . . . . . . . 1-5:1IDPPOINT command . . . . . . . . . . . . . 1-5:2Imperial units:setting . . . . . . . . . . . . . . 1-3:4INCH command . . . . . . . . . . . . . . . . . 1-3:4INSULATION command . . . . . . . . . . 1-4:11ISODRAFTMODE command . . . . . . 1-5:10

LLeaving . . . . . . . . . . . . . . . . . . . . . . . . 1-3:3LINE command:design aids . . . . . . . 1-4:19 1-2:4, 1-2:5, 1-2:8, 1-2:9, 1-2:10, 1-2:11, 1-

2:12, 1-2:13

MMAP command . . . . . . . . . . . . . . . . . 1-4:23Mapping pins . . . . . . . . . . . . . . . . . . . . 1-5:4MARK command . . . . . . . . . . . . . . . . 1-4:19Metric units:setting . . . . . . . . . . . . . . . 1-3:4MILLIMETRE command . . . . . . . . . . . 1-3:4MM command . . . . . . . . . . . . . . . . . . . 1-3:4

OObstructing element . . . . . . . . . . . . . . 1-4:6OBSTRUCTION command . . 1-4:11, 1-4:12

PPIN command . . . . . . . . . . . . . . . . . . .1-5:5Position:axial . . . . . . . . . . . . . . . . . . . . 1-2:9Position:general . . . . . . . . . . . . . . . . .1-2:10PRECISION command . . . . . . . . . . . . .1-3:5PRECISION command . . . . . . . . . . . . .1-3:5

QQUERY command . . . . . . . . . . . . . . . . 1-3:8QUIT command . . . . . . . . . . . . . . . . . . 1-3:3

RREMOVE command:drawlist . . . . . . . . 1-4:5REPRESENTATION command:CENTRELINE

1-4:9REPRESENTATION command:DARCTOLER-

ANCE . . . . . . . . . . . . . . . . . .1-4:17REPRESENTATION command:HOLES 1-4:16REPRESENTATION command:LEVEL 1-4:10REPRESENTATION command:OBSTRUC-

TION . . . . . . . . . . . . . . . . . . . 1-4:12REPRESENTATION command:OBSTRUC-

TION/INSULATION . . . . . . . . 1-4:11REPRESENTATION command:PLINES 1-4:15REPRESENTATION command:PNODES/SN-

ODES . . . . . . . . . . . . . . . . . .1-4:14REPRESENTATION command:PPOINTS 1-

4:13REPRESENTATION command:PROFILE 1-4:9REPRESENTATION command:TRANSLUCEN-

CY . . . . . . . . . . . . . . .1-4:11, 1-4:12REPRESENTATION command:TUBE . 1-4:9REPRESENTATION command:UPDATE 1-

4:17

SSelection:of elements . . . . . . . . . . . . . 1-2:13SOLELY command . . . . . . . . . . . . . . 1-4:22Spatial map . . . . . . . . . . . . . . . . . . . . 1-4:23SPHERE command:design aids . . . . 1-4:19syntax 1-2:4, 1-2:5, 1-2:8, 1-2:9, 1-2:10, 1-2:11,

1-2:12, 1-2:13SYSCOMMAND command . . . . . . . . .1-3:8

TText output . . . . . . . . . . . . . . . . . . . . . . 1-3:7TRACE command . . . . . . . . . . . . . . . . 1-3:7TRANSLUCENCY command .1-4:11, 1-4:12TWODPICK command . . . . . . . . . . . . .1-5:4



TWODPLANE command . . . . . . . . . . 1-5:4

UUNENHANCE command . . . . . . . . . 1-4:22Units of measurement . . . . . . . . . . . . . 1-2:5Units of measurement:setting . . . . . . . 1-3:3UNMARK command . . . . . . . . . . . . . 1-4:19

VVisible element . . . . . . . . . . . . . . . . . . 1-4:6


design reference manual - general commands

Documents

aveva products

aveva product names

subsidiaries disclaimany

tribon trademarks

unlicensed use

incorrect use

associated software

intellectual property