51774186 draft user guide part1

5/21/2018 51774186 DRAFT User Guide Part1

1/194

PDMS DRAFTUser Guide

Part 1: Basic Drawing Creation & Output

Version 11.6SP1

pdms1161/DRAFT User Guide Part1issue 270605


2/194

PLEASE NOTE:AVEVA Solutions has a policy of continuing product development: therefore, the

information contained in this document may be subject to change without notice.

AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO

THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE.

While every effort has been made to verify the accuracy of this document, AVEVA

Solutions shall not be liable for errors contained herein or direct, indirect, special,

incidental or consequential damages in connection with the furnishing, performance or

use of this material.

This manual provides documentation relating to products to which you may not have

access or which may not be licensed to you. For further information on which Products

are licensed to you please refer to your licence conditions.

Copyright 1991 through 2005 AVEVA Solutions Limited

All rights reserved. No part of this document may be reproduced, stored in a retrieval

system or transmitted, in any form or by any means, electronic, mechanical,

photocopying, recording or otherwise, without prior written permission of AVEVASolutions.

The software programs described in this document are confidential information and

proprietary products of AVEVA Solutions or its licensors.

For details of AVEVA's worldwide sales and support offices, see our website at

http://www.aveva.com

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
http://www.aveva.com/engineeringit/world/http://www.aveva.com/engineeringit/world/http://www.aveva.com/engineeringit/world/


3/194

Revision History

Date Version Notes

March 2003 11.5 Manual divided into two Parts:

Part 1: Basic Drawing Creation & Output (this manual)

Part 2: Drawing Annotation

Sept 2004 11.6 Background Processes included.

June 2005 11.6.SP1 Minor corrections and updates for this release.

VANTAGE PDMS DRAFT User Guide Revision History-iPart 1: Basic Drawing Creation & OutputVersion 11.6SP1


4/194

Revision History

Revision History-ii VANTAGE PDMS DRAFT User GuidePart 1: Basic Drawing Creation & Output

Version 11.6SP1


5/194

Contents

1 Introducing PDMS DRAFT ............................................................................ 1-1

1.1 What does DRAFT do?................................................................................................1-11.2 The DRAFT Database .................................................................................................1-11.3 Who Should Read this Manual ....................................................................................1-21.4 Organisation of the DRAFT User Guide ......................................................................1-21.5 Organisation of this User Guide...................................................................................1-2

2 General PDMS Commands ........................................................................... 2-1

2.1 Saving..........................................................................................................................2-12.1.1 Saving and Restoring the Current Display Status..........................................2-12.1.2 Saving Work...................................................................................................2-12.1.3 Seeing Changes Made by Other Users .........................................................2-2

2.2 Accessing Multiple Database Information....................................................................2-22.2.1 Finding the Current User Status.....................................................................2-22.2.2 Finding the Current System Status ................................................................2-22.2.3 Listing Multiple-Database Information............................................................2-32.2.4 Querying MDB Information.............................................................................2-42.2.5 Changing Multiple Databases ........................................................................2-4

2.3 Using Multiwrite Databases .........................................................................................2-52.3.1 User Claims....................................................................................................2-52.3.2 Notes on Standard Multiwrite DBs .................................................................2-62.3.3 Extract Databases..........................................................................................2-72.3.4 How to Find Out What You Can Claim...........................................................2-9

2.4 Comparing and Listing Database Changes ...............................................................2-122.4.1 Comparing Database States at Different Times...........................................2-122.4.2 Listing Database Changes...........................................................................2-12

2.5 Miscellaneous Facilities .............................................................................................2-142.5.1 Audible Error Trace......................................................................................2-142.5.2 Switching Text Output Off (DEVICE TTY only)............................................2-142.5.3 Logging the Alpha Display ...........................................................................2-142.5.4 Controlling Output of Warning Messages .................................................... 2-14

3 Drawing the Design....................................................................................... 3-1

3.1 Introducing the DRAFT Database................................................................................3-13.2 Creating a Drawing, a Sheet and a View.....................................................................3-2

3.2.1 Defining the Contents of a View.....................................................................3-33.3 Defining View Contents Using the AUTO Command...................................................3-33.4 Defining VIEW Contents Using Id Lists........................................................................3-4

3.4.1 Adding elements to 3D View..........................................................................3-53.4.2 Selective Additions to the Id List ....................................................................3-63.4.3 The Spatial Map.............................................................................................3-6

3.4.4 Changing the Limits of the View Contents ..................................................... 3-73.4.5 Cleaning Up Id Lists.......................................................................................3-7

VANTAGE PDMS DRAFT User Guide Contents-iPart 1: Basic Drawing Creation & OutputVersion 11.6SP1


6/194

Contents

3.4.6 Querying Id Lists............................................................................................ 3-73.5 Changing the Picture by Changing VIEW Attributes ................................................... 3-8

3.5.1 The VIEW Frame........................................................................................... 3-83.5.2 The View Size................................................................................................ 3-83.5.3 The View Centre............................................................................................ 3-93.5.4 The View Scale............................................................................................ 3-103.5.5 Orientation of View Contents....................................................................... 3-103.5.6 Perspective.................................................................................................. 3-113.5.7 3D View ....................................................................................................... 3-113.5.8 Looking Direction......................................................................................... 3-113.5.9 Representation Ruleset Reference ............................................................. 3-133.5.10 Hatching Ruleset Reference........................................................................ 3-133.5.11 Change Ruleset Reference ......................................................................... 3-133.5.12 Arc Tolerance .............................................................................................. 3-13

3.5.13 View Gap Length......................................................................................... 3-133.6 More on the AUTO command.................................................................................... 3-133.7 Hidden Line Representation...................................................................................... 3-143.8 Querying Commands................................................................................................. 3-18

3.8.1 Querying View Contents.............................................................................. 3-183.8.2 Querying Whether an Element Appears in a View...................................... 3-193.8.3 Querying the Nearest Side to an Item ......................................................... 3-19

3.9 Switching Between Databases.................................................................................. 3-203.10 The Background Process Manager........................................................................... 3-21

3.10.1 Introduction.................................................................................................. 3-213.10.2 Prerequisites................................................................................................ 3-213.10.3 Initiating and Using the BPM ....................................................................... 3-213.10.4 Managing Jobs using the Background Process Manager form................... 3-24

4 Graphical Representation ............................................................................ 4-1

4.1 Representation Styles ................................................................................................. 4-24.2 Representation Rules.................................................................................................. 4-5

4.2.1 Selective Style Allocation .............................................................................. 4-64.2.2 Local Rules.................................................................................................... 4-74.2.3 Setting the VIEW ........................................................................................... 4-7

4.3 Automatic Hatching ..................................................................................................... 4-74.3.1 Hatching Rules .............................................................................................. 4-84.3.2 Hatching Rules .............................................................................................. 4-9

4.3.3 Which Elements can be Hatched .................................................................. 4-94.3.4 Hatching Styles.............................................................................................. 4-94.3.5 The Hatch Pattern ....................................................................................... 4-10

4.4 Querying Commands................................................................................................. 4-114.4.1 Querying Rulesets and Styles ..................................................................... 4-114.4.2 Querying Hatching Rulesets and Styles...................................................... 4-11

5 Section Planes .............................................................................................. 5-1

5.1 Introduction.................................................................................................................. 5-15.2 Creating and Using Planes.......................................................................................... 5-3

5.2.1 Perpendicular Plane (PPLA).......................................................................... 5-55.2.2 Flat Plane (FPLA).......................................................................................... 5-7

5.2.3 Stepped Plane (SPLA) .................................................................................. 5-8

Contents-ii VANTAGE PDMS DRAFT User GuidePart 1: Basic Drawing Creation & Output

Version 11.6SP1


7/194

Contents

5.3 Altering Planes........................................................................................................... 5-115.4 Plane Querying .......................................................................................................... 5-11

6 Using the Cursor ...........................................................................................6-1

6.1 Identifying Elements Using the Cursor.........................................................................6-16.2 Picking P-points and Nodes.........................................................................................6-2

6.2.1 P-point Style...................................................................................................6-36.3 Picking Structural Elements and P-lines......................................................................6-36.4 Querying Position Data ................................................................................................6-46.5 Snapping 2D Points to a Grid ......................................................................................6-46.6 Highlighting Displayed Elements ................................................................................. 6-6

7 Plotting and Drawing Output........................................................................ 7-1

7.1 General ........................................................................................................................7-17.2 Standard DXF Output ..................................................................................................7-2

7.2.1 Creating the DXF File.....................................................................................7-27.2.2 DXF File Contents..........................................................................................7-27.2.3 Sheet migration to AutoCAD..........................................................................7-37.2.4 File Header Options .......................................................................................7-37.2.5 Encoding of Multi-Byte Characters.................................................................7-47.2.6 Scaling ........................................................................................................... 7-4

7.3 Configurable DXF Output.............................................................................................7-57.3.1 Configuration Datasets .................................................................................. 7-57.3.2 Switches and BLOCK Rules to Control DXF Export ......................................7-87.3.3 Limitations....................................................................................................7-14

7.4 Configurable DGN Output..........................................................................................7-147.4.1 Configuration Datasets ................................................................................ 7-147.4.2 Common Features of Option Switches ........................................................7-177.4.3 File-Related and Miscellaneous Options ..................................................... 7-187.4.4 Pen Related Options....................................................................................7-217.4.5 Font Related Options ...................................................................................7-237.4.6 Level-Related Options..................................................................................7-247.4.7 Group Related Options ................................................................................ 7-257.4.8 Product Support Options..............................................................................7-277.4.9 Validation feature and options .....................................................................7-277.4.10 Summary of Switches and Rules to Control DGN Export ............................7-287.4.11 Limitations....................................................................................................7-30

8 Pens and Linestyles......................................................................................8-1

8.1 Introduction ..................................................................................................................8-18.2 Colours.........................................................................................................................8-3 8.3 Line Representations...................................................................................................8-4

8.3.1 Line Thicknesses ...........................................................................................8-58.3.2 Line Patterns..................................................................................................8-58.3.3 Glyphs............................................................................................................8-7 8.3.4 User-defined Glyphs ......................................................................................8-98.3.5 Line Pictures ................................................................................................8-11

8.4 Marker Types............................................................................................................. 8-158.5 Hatch Patterns ........................................................................................................... 8-16

8.6 Defining Pen Settings ................................................................................................8-21

VANTAGE PDMS DRAFT User Guide Contents-iiiPart 1: Basic Drawing Creation & OutputVersion 11.6SP1


8/194

Contents

8.6.1 Defaults ....................................................................................................... 8-218.6.2 User-Definable Pens ................................................................................... 8-23

8.6.3 Graphical Feedback .................................................................................... 8-248.6.4 Querying Pen Settings................................................................................. 8-25

8.7 DRAFT Element Pen Attributes................................................................................. 8-25

9 Reports, Circulation Lists and Revisions ................................................... 9-1

9.1 The Report .................................................................................................................. 9-19.2 The Circulation List...................................................................................................... 9-29.3 Drawing Revisions....................................................................................................... 9-3

10 Change Highlighting................................................................................... 10-1

10.1 Design Change Styles............................................................................................... 10-210.2 Annotation Change Styles......................................................................................... 10-310.3 Change Rules............................................................................................................ 10-3

10.3.1 Design Change Rules.................................................................................. 10-310.3.2 Annotation Change Rules............................................................................ 10-4

10.4 Attribute Setting......................................................................................................... 10-510.5 The Comparison Date ............................................................................................... 10-510.6 UPDATE Command, SHOW CHANGES Option and Error Messages ..................... 10-610.7 Querying Commands................................................................................................. 10-8

10.7.1 Querying Change Rulesets and Design or Annotation Styles..................... 10-8

A DRAFT Database Hierarchy .........................................................................A-1

A.1 Basic Hierarchy ........................................................................................................... A-1

B System Update Commands..........................................................................B-1

B.1 Cross-Database Referencing......................................................................................B-1B.2 Updating Symbol Instances......................................................................................... B-2

C Picture File Naming Conventions................................................................C-1

D Guidelines for Importing DGN files from DRAFT into MicroStation.........D-1

D.1 Introduction..................................................................................................................D-1 D.2 Exporting DRAFT drawings containing PDMS Fonts ..................................................D-1D.3 Installing PDMS Fonts into MicroStation.....................................................................D-2

D.3.1 Creating a new Font resource library ............................................................D-2

D.3.2 Selecting .shx files to add to resource library................................................D-3D.3.3 Selecting the library destination.....................................................................D-3D.3.4 Copying the fonts into the library...................................................................D-3D.3.5 Checking The Installation ..............................................................................D-3D.3.6 Changing MicroStation font numbers ............................................................D-4D.3.7 Select the required .rsc library.......................................................................D-4D.3.8 Creating a new Font Geometry File...............................................................D-4

D.4 Mapping the Installed Fonts ........................................................................................D-5D.5 PDMS font file names..................................................................................................D-5D.6 Colours........................................................................................................................D-7D.7 Line Styles...................................................................................................................D-7

Contents-iv VANTAGE PDMS DRAFT User GuidePart 1: Basic Drawing Creation & Output

Version 11.6SP1


9/194

1 Introducing PDMS DRAFT

1.1 What does DRAFT do?

DRAFT produces fully annotated scale drawings showing selected parts of the design

model created in PDMS DESIGN. DRAFT is fully integrated with DESIGN.

A model can be viewed from any direction, with hidden detail automatically removed orshown in a different linestyle, as required. A drawing may contain more than one view

of a 3D model; for example, a plan view, a front elevation and an isometric view may be

displayed simultaneously.

In DRAFT an annotated drawing is made up of different types of graphics:

Graphics that represent the 3D model.

Graphics to provide backing and overlay sheets which will be common to a number

of drawings.

Graphics providing annotation, including not only dimensioning and text but also

such items as leader lines and label boxes.

All the graphic items exist as, or are defined by, elements in the DRAFT database.

1.2 The DRAFT Database

The DRAFT database contains a complete definition of a DRAFT drawing. The DRAFT

database does not contain information describing the geometry of the graphics that

make up a drawing, but gives a description of how those graphics should be presented

on a drawing.

From this database definition (together with the Design and Catalogue databases which

describe the appropriate 3D model) a drawing is generated which reflects the state of

the design at that particular time. The drawing can be displayed on the screen and

processed to produce a hard copy plotfile.

VANTAGE PDMS DRAFT User Guide 1-1Part 1: Basic Drawing Creation & OutputVersion 11.6SP1


10/194

Introducing PDMS DRAFT

1.3 Who Should Read this Manual

This is a command-level manual, written for people who are writing or customising their

own graphical user interface. It describes all the DRAFT commands, with worked

examples where appropriate. It is assumed that you are familiar with the normal way of

using DRAFT, through the supplied Graphical User Interface (GUI).

For an introduction to using DRAFT via the GUI, seeDrawing Production Using

VANTAGE PDMS, and for further information, see the online help. For information

about DRAFT System Administration, see the VANTAGE PDMSDRAFT Administrator

Application User Guide.

For general information about customising the graphical user interface, see the

VANTAGE Plant Design Software Customisation Guideand VANTAGE Plant Design

Software Customisation Reference Manual.

1.4 Organisation of the DRAFT User Guide

The DRAFT User Guide has two parts:

Part 1, (this volume) describes all aspects of producing a drawing in DRAFT that do not

relate to annotations.

Part 2,Drawing Annotation, describes all aspects of DRAFT relating to annotations.

1.5 Organisation of this User Guide

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

Chapter 2, General PDMS Commands, describes some general PDMS commands,

common to several PDMS modules, which are available in DRAFT.

Chapter 3,Drawing the Design, describes how to create a DRAFT picture without

annotations. It describes the part of the DRAFT database that stores the main

administrative and graphical elements and how to create them. It also describes

Views, which are the areas used to display Design elements, and how to define theircontent.

Chapter 4, Graphical Representation, describes how Design elements are defined and

drawn using Representation Rules. It describes how Representation Rules are

defined and describes the part of the DRAFT database that stores the

Representation Rules. It also describes Hatching Rules, used for the automatic

hatching of faces of Design elements.

Chapter 5, Section Planes, describes how you can construct sections through Design

items, using Planes in DRAFT, which can be displayed at VIEW level.

1-2 VANTAGE PDMS DRAFT User GuidePart 1: Basic Drawing Creation & Output

Version 11.6SP1


11/194


Chapter 6, Using the Cursor, describes how, with many DRAFT commands, you can

use the cursor to identify an element in the graphics window by using the ID

command followed by an @.

Chapter 7,Plotting and Drawing Output, describes how you can generate, at any

time during the drawing process, a plotfile consisting of a single Sheet, View, or the

content of an Area View.

Chapter 8,Pens and Linestyles, defines the attributes that are associated with pens

and describes how to set these attributes.

Chapter 9, Reports, Circulation lists and Revisions, describes how to create the

drawing office administrative elements; reports and circulation lists. It also

describes how DRAFT handles revision numbers.

Chapter 10, Change Highlighting, describes how you use Change Rules to controlhow Design and Annotation elements that have been changed are drawn on a

DRAFT View. It describes how Change Rules are defined and describes the part of

the DRAFT database that stores the Change Rules. It also describes the concept of

Comparison Dates and how these are used to determine whether Design and

Annotation elements have been changed

Appendix A,DRAFT Database Hierarchy, provides a graphical representation of the

DRAFT database structure.

Appendix B, System Update Commands, describes functions in DRAFT that can be

used to minimise problems with cross-database referencing when Design databases

are deleted and rebuilt from macros. It also describes how the UPDATE

INSTANCES command is used to update picture files that use the instancing

mechanism.

Appendix C,Picture File Naming Conventions, describes the structure of picture file

names.

Appendix D, Guidelines for Importing DGN Files from DRAFT into MicroStation,

describes how DRAFT drawings can be output as DGN files that can be imported

into a freshly installed version of MicroStation/J. It contains guidelines for ensuring

that fonts are translated correctly and how to improve other aspects of the

translation.



12/194



Version 11.6SP1


13/194

2 General PDMS Commands

This Section describes some general PDMS commands, common to several PDMS

modules, which are available in DRAFT.

2.1 Saving

2.1.1 Saving and Restoring the Current Display Status

If the intention is to leave DRAFT for a short period only the RECREATE/INSTALL

facility allows the display setup (including the full forms and menus set) to be saved, for

restoration later.

For example:

RECREATE /DS1

- saves the display status in file /DS1.

RECREATE /DS1 OVER

- as above, but an existing file /DS1 is overwritten.

RECRE DISPLAY /DS2

- saves modal settings, e.g. changes from default Pen

configuration, units, text quality etc. Read back in using $M.

INSTALL SETUP /DS1

- restores the display definition stored in file /DS1. (Refers to file

saved by RECREATE, notRECREATE DISPLAY.)

Note: Forms resized or moved using the cursor will be INSTALLed to their original

size.

2.1.2 Saving Work

The command:

SAVEWORK

saves the current DRAFT additions or modifications without leaving DRAFT. It is good

practice to use this command on a regular basis during a long DRAFT session to ensure

maximum data security.



14/194

General PDMS Commands

2.1.3 Seeing Changes Made by Other Users

The command

GETWORK

updates the DRAFT database with the changes made by other users, if the database has

been opened in multi-write mode.

2.2 Accessing Multiple Database Information

The Multiple Database Access facilities allow you to list information about the

databases you are using. It is also possible to change to another Multiple Database (see

Section 2.2.5), thus entering MDB Mode, from which further database-related activitiescan be performed.

2.2.1 Finding the Current User Status

The STATUScommand gives you information about your current user status and that of

the DBs to which you have access.

For example, a typical response to the STATUScommand could be:

Project: XYZUser: RAB (222f-PC378)Teams: BMDB: /DRAFTA1 B/DRAFTA RW2 MASTER/DRAFTAPP R3 MASTER/DRAFTLIB R4 MASTER/CATA R5 MASTER/DESI RDeferred DBS:6 STRUCT/STEEL

This indicates that the designer has identified himself as being PDMS user RAB, that

he is logged in to workstation PC378 as user 222f (a hexadecimal code), that he is a

member of team B, that he is accessing Project XYZ, and that he has selected an MDBcalled /DRAFTA.

His current DBs are B/DRAFTA, to which he has Read/Write access (as a member of the

team which owns it), and MASTER/DRAFTAPP, MASTER/DRAFTLIB, MASTER/CATA

and MASTER/DESI, to which he has Read-only access. The DB STRUCT/STEEL is non-

current and so he has no access to it at present.

2.2.2 Finding the Current System Status

The SYSTATcommand gives you information about the current active status of the

project within which you are working. It lists all users who are currently accessing the


Version 11.6SP1


15/194


project, the modules and databases that they are using, and whether they are examining

(Read-only status) or modifying (Read/Write status) the database. A typical response to

the SYSTATcommand could be:USER USERA (13d3-PC378)MODULE DRAFTMDB /USERB

DB MODEUSER/USERB RWMASTER/DRAFTAPP RMASTER/DRAFTLIB RUSER/DESIB RMASTER/CATA RMASTER/DESI R

This shows that user USERA is currently logged in and using module DRAFT. He is

accessing the MDB named /USERB whose constituent DBs are as listed. He has Read-

only status for the DBs owned by the MASTER (System) team and Read/Write access to

the DB USER/USERB.

2.2.3 Listing Multiple-Database Information

The LISTcommand allows you to list most of the available project information held in

the System Database, with the exception of confidential details such as other users

passwords. The latter can only be listed by the Project Coordinator using the ADMIN

module of PDMS.

A typical response to the LIST MDBcommand could be:

List of MDBS for project DRA==============================MDB: /USERACurrent DBS:1 USER/USERA PADD EXCLUSIVE2 MASTER/DRAFTAPP PADD UPDATE3 MASTER/DRAFTLIB PADD UPDATE4 MASTER/CATA CATA UPDATE5 MASTER/DESI DESI UPDATE

Deferred DBS:

**NONE**MDB: /USERBCurrent DBS:1 USER/USERB PADD EXCLUSIVE2 MASTER/DRAFTAPP PADD UPDATE3 MASTER/DRAFTLIB PADD UPDATE4 USER/DESIB DESI EXCLUSIVE5 MASTER/CATA CATA UPDATE6 MASTER/DESI DESI UPDATE

Deferred DBS:**NONE**

A typical response to the LIST USERScommand could be:



16/194


List of USERS for project DRA===============================

SYSTEM (FREE)TEAMS : MASTER

GEN (GENERAL)TEAMS : TEST

The information generated by the LISTcommand will be displayed within the PDMSDRAFT REQUESTSwindow and can sent to a file - see Section 2.5.3.

2.2.4 Querying MDB Information

You can query the project configuration using the following commands:

QUERY USER

QUERY USER word

QUERY TEAM word

QUERY DB dbname

QUERY MDB name

2.2.5 Changing Multiple Databases

You can change the current multiple database, and also the current User and Projectduring a DRAFT session without having to leave DRAFT and enter MONITOR. The

MDBcommand puts you into MDB Mode, where you can use a limited number of

MONITOR commands,

You can either update the current MDB to save your changes before entering MDB

Mode, or ignore any changes made since your last SAVEWORKcommand (see Section

2.1.2 ).

MDB UPDATE Save design changes and enter MDB Mode.

MDB NOUPDATE Enter MDB Mode without saving changes.

When you are in MDB mode, you can give the following commands, which are the sameas the corresponding MONITOR commands. For more information, see the VANTAGE

PDMSMONITOR Reference Manual.

EXCHANGE alter the databases in the current list of the current MDBDEFERCURRENT

PROTECT temporarily alters your access rights to specified databases.

USER changes the current user and projectPROJECT

VAR allows you to set variables


Version 11.6SP1


17/194


QUERY allows you to query:

Users, including the number of active users,

Teams including the set (current) Team,

Databases, including copied Databases,

MDBs, Macros and Variables

You leave MDB mode and return to normal DRAFT mode by giving the command:

EXIT.

2.3 Using Multiwrite Databases

If a Draft (PADD) DB has been created as a multiwritedatabase, several users can

write to it simultaneously, although they cannot change the same element.Multiwrite databases can either be Standardmultiwrite databases, or Extract

databases. In both types, an element must be claimedbefore it can be modified.

Claiming an element prevents other users claiming (and modifying) the element; the

element must be unclaimedor releasedbefore another user can change it.

Claiming can be either explicit, where the user must use the CLAIMcommand before

attempting to modify the element, or implicit, where the claim is made automatically

when the user tries to modify the element. The claim mode is set when the DB is

created. For full details see the VANTAGEPDMSADMIN Command Reference Manual.

2.3.1 User ClaimsIn a Standard multiwrite database, you must claim an element before changing it. This

is known as a user claim. If the claim mode is explicit(see below for details of how to

check this), you must first claim each element that you want to modify using the CLAIM

command. If the claim mode is implicit, the claim will be made automatically (although

you can still give explicit CLAIMcommands if you want to prevent other users claiming

specific elements).

Only primaryelements can be claimed, that is:

DEPT REGI DRWG LIBY SYLB ISOLB LALB SHLB BACK OVER SHEE

You can claim a specified element only, or a specified element plus all of the primaryelements below it in the hierarchy. If the claimed element is not a primary element, the

primary element above it in the hierarchy will be claimed.

Examples of use of the CLAIM/UNCLAIMcommands are:

CLAIM /SHEE1 /SHEE2 /SHEE3

Claims named Sheets

CLAIM /DRWG HIERARCHY

Claims named Drawing and all of its owned hierarchy

CLAIM /VIEW2-1

Claims Sheet which owns named View (since VIEW is not a primary

element)



18/194


An element must be unclaimedbefore another user can claim it and change it. User

claims are always unclaimed when you change modules or leaves PDMS, and you can

also unclaim elements at any time during a PDMS session using the UNCLAIMcommand.

UNCLAIM /SHEE2 /SHEE3

Unclaims named Sheets

UNCLAIM ALL

Unclaims all elements currently claimed

2.3.2 Notes on Standard Multiwrite DBs

Elements cannot be claimed if other users have made recent changes to them. You

must issue a GETWORKcommand first.

Elements cannot be unclaimed if there are updates outstanding. You must issue a

SAVEWORKcommand first.

You can insert/remove primary elements in a members list without claiming the

owner. For example, you can add a Sheet into a Drawing without claiming the

Drawing. Thus two users can add different Sheets to the same Drawing: any

discrepancies will be resolved when a SAVEWORKis attempted.

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

claimed.

The following potential problems may not be revealed until you try to save changes:

o If two concurrent users allocate the same name to different elements, the second

user to attempt a SAVEWORK will show up an error. The second user must

rename their element.

o If one user inserts a primary element into another elements list, while a

concurrent user deletes the latter element, an attempt to SAVEWORKwill show

up an error. Either the first user must delete or move the primary element, or the

second user must QUITwithout saving the deletion.


Version 11.6SP1


19/194


2.3.3 Extract DatabasesUnlike standard multiwrite databases, extracts allow users to keep elements claimed

when they exit from PDMS or change module. They can also be used, together with Data

Access Control, to manage workflow. See the VANTAGEPDMSADMIN User Guide for

more information.

An extract is created from an existing Database. When an Extract is created, it will be

empty, with pointers back to the owing or masterdatabase. Extracts can only be

created from Multiwrite databases, and all extracts are themselves Multiwrite. An

extract can be worked on by one User at the same time as another user is working on

the master or another extract.

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

If the claim mode is explicit, the extract claim will be made automatically when you

make a user claim using the CLAIMcommand. You can also claim to the extract only

using the EXTRACTCLAIMcommand.

If an element is claimed to an extract, only users with write access to the

extract will be able to make a user claim and start work on the element.

If the databases are set up with implicit claim, when the user modifies the

element, the element will be claimed both to the extract and then to the

user. If the element is already claimed to the extract, then the claim will

only be made to the user.

If the databases are set up with explicit claim, then the user will need to

use the CLAIM command before modifying the element.

Once a user has made a user claim, no other users will be able to work on

the elements claimed, as in a normal multiwrite database.

If a user unclaims an element, it will remain claimed to the extract until

the extract claim is releasedor issued.

When an extract User does a SAVEWORK, the changed data will be saved to the

Extract. The unchanged data will still be read via pointers back to the master DB. The

changes made to the extract can be written back to the master, or dropped. Also, the

extract can be refreshed with changes made to the master.

EXTRACT CLAIM /SHEE1 /SHEE2 /SHEE3

Claims named Sheets to the extract

EXTRACT CLAIM /SHEE1 /SHEE2 /DEPT-PIPE HIERARCHY

Claims the named elements, and all the elements in the hierarchy to

the extract

The HIERARCHYkeyword must be the last on the command line. It will attempt to

claim to the extract all members of the elements listed in the command that are not

already claimed to the extract.



20/194


EXTRACT FLUSH DB PIPE/PIPE

Writes all changes to the database back to the owing extract. The

Extract claim is maintained.EXTRACT FLUSH /SHEE1 /SHEE2 /SHEE3

Writes the changes to the named elements back to the owing extract.

The Extract claim is maintained.

EXTRACT ISSUE DB PIPE/PIPE

Writes all the changes to the database back to the owning extract and

releases the extract claim.

EXTRACT ISSUE /REGI-A HIERARCHY

Writes all the changes to the named element and all elements under it

in the hierarchy back to the owning extract and releases the extract

claim.EXTRACT ISSUE /SHEE1 /SHEE2 /SHEE3

Writes the changes to the named Sheets back to the owning extract

and releases the extract claim.

EXTRACT RELEASE DB PIPE/PIPE

Releases the extract claim: this command can only be given to release

changes that have already been flushed.

EXTRACT RELEASE /SHEE1 /SHEE2 /SHEE3

Releases the extract claim: this command can only be given to release

changes that have already been flushed.

EXTRACT RELEASE /REGI-A HIERARCHYReleases the extract claim to the named element and all: elements

under it in the hierarchy.

EXTRACT DROP DB PIPE/PIPE

Drops changes that have not been flushed or issued. The user claim

must have been unclaimed before this command can be given.

The elements required can be specified by selection criteria, using a PML expression.

For example:

EXTRACT CLAIM ALL SHEET WHERE (:OWNER EQ USERA) HIERARCHY


Version 11.6SP1


21/194


2.3.4 How to Find Out What You Can Claim

Before you start work on an extract, you should do a GETWORKand an EXTRACTREFRESH, which will ensure that you have an up-to-date view of the database.

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

commands.

For this example, take the case of a database PIPE/PIPE, accessed by USERA, with two

extracts. Users USERX1 and USERX2 are working on the extracts.

DB PIPE/PIPEX1

USERX1

DB PIPE/PIPE-X2

USERX2

DB PIPE/PIPE

USERA

Figure 2-1Example database and users



22/194


USERA creates a Pipe and flushes the database back to the owning database,

PIPE/PIPE. The results of various Q CLAIMLISTcommands by the three Users,

together with the extract control commands that they have to give to make thenew data available, are shown in the following diagram.

USERX1creates PIPE-100

EXTRACT FLUSH DB PIPE/PIPE

Q CLAIMLIST:none

Q CLAIMLIST OTHER:none

Q CLAIMLIST EXTRACT:/PIPE-100

USERA:

EXTRACT REFRESH DB PIPE/PIPE

Q CLAIMLIST:none

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

Q CLAIMLIST EXTRACT:

/PIPE-100

USERX2:

EXTRACT REFRESH DB PIPE/PIPE

Q CLAIMLIST:none

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

Q CLAIMLIST EXTRACT:none

Note that USERX2 must useQ CLAIMLIST OTHER(notQ CLAIMLIST EXTRACT) tosee the claim

Figure 2-2 Example Q CLAIMLIST commands


Version 11.6SP1


23/194


Note:

Q CLAIMLIST EXTRACT tells you what you can flushQ CLAIMLIST OTHERS tells you want you can't claim

A useful querying command when you are using extracts is:

Q DBNAME

This command will return the name of the database you are writing to.

You can query the extract claimlist for a named database. The database can be the

current one or its owner:

Q CLAIMLIST EXTRACT DB dbname

When you create an element, PDMS only sees it as a user claim, not an extract claim,until the element is flushed. It will then be reported as an extract claim (as well as a

user claim, if it has not been unclaimed).

Notethat a change in the claim status of an existing element will be shown by the

appropriate Q CLAIMLIST command as soon as appropriate updates take place, but a

user will have to GETWORK as usual to see the changes to the Design model data.

We recommend that:

Before you make a user or extract claim, you should do an EXTRACT REFRESH

and GETWORK.

If you need to claim many elements to an extract, it improves performance if the

elements are claimed in a single command, for example, by using a collection:

EXTRACT CLAIM ALL FROM !COLL

To query whether or not the PADD DB that you are using permits multiwrite access:

Q DBAC

where DBAC is a pseudo-attribute, which can have the text settings CONTROL,

UPDATE or MULTIWRITE.

To query the claim mode of the database, use:

Q DBCL

where DBCL is a pseudo-attribute, which can have the text settings EXPLICIT orIMPLICIT.

To query whether or not an element that you want to modify is currently claimed by

another user, navigate to that element and use:

Q LCLM

where LCLM is a pseudo-attribute with the logical settings True (element already

claimed) or False/Unset (element available for you to modify).

To produce a list of all elements currently claimed by your session:

Q CLAIMLIST



24/194


To produce a list of all elements currently claimed by other users who are accessing the

same DB:

Q CLAIMLIST OTHER

2.4 Comparing and Listing Database Changes

2.4.1 Comparing Database States at Different Times

You can report on database changes since a specified time using the DIFFERENCE

command. The types of change reported include:

The insertion and/or deletion of elements;

Changes to the attribute settings of elements

DIFFERENCE ALL SHEE FOR /DEPT_1 SINCE 21 JANUARY

DIFF ALL SHEE SINCE /STAMP_001

DIFF CE SINCE 10:00

- assumes current day.

DIFF /DRWG1

- compares current settings with those at your last SAVEWORK

command.

DIFF DRWG SINCE SESSION 66

- compares current settings with those at the end of an earlier

DRAFT session.

The output may be sent to a file by using the standardALPHA FILEorALPHA LOG

facilities (see Section 2.5.3).

You can also report on differences in extract databases compared with other extracts

higher in the extract hierarchy, as described in the next Section.

2.4.2 Listing Database Changes

You can output all changes to one or more specified elements since a given date, session,

or Stamp using the OUTPUTcommand. The output is in the form of a macro. You can

then run in the macro to recreate the elements and their attributes.

You can include only those elements whose settings have been changed since a specified

earlier time (i.e. those elements which would be listed by the DIFFERENCEcommand).


Version 11.6SP1


25/194


The output is generated in three stages:

1. Any elements that were originally locked are unlocked. Element deletions,name changes and type changes are output. Reordering or insertion of

elements in their owners members list is treated as deletion followed by

creation, so that Refno attribute settings may be changed.

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

3. Reference attribute settings and rules are output. Elements which were

originally locked are relocked and GADDcommands are included if any

elements were included in Groups.

Examples of the use of the OUTPUTcommand are:

OUTPUT /VIEW1-1Outputs all elements, whether or not they have ever been changed.

OUTPUT ALL SHEE FOR /DEPT-1 CHANGES SINCE 21 JANUARY

Outputs all changes to named element and its members since the given

date.

OUTPUT /VIEW1-1 CHANGES

Outputs all changes to named element and its members since last

SAVEWORK command.

OUTPUT /SHEET-1 CHANGES SINCE EXTRACT

In an extract database, outputs all changes since the extract was

created.

OUTPUT /SHEET-1 CHANGES SINCE LATEST EXTRACT

In an extract database, outputs all changes compared with the latest

version of the parent extract.

OUTPUT /SHEET-1 CHANGES SINCE EXTRACT 44

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

In an extract database, outputs all changes compared with the latest

version of the given extract, which must be higher in the extract

hierarchy.

OUTPUT /SHEET-1 CHANGES SINCE SESSION 77 EXTRACT 44

OUTPUT /SHEET-1 CHANGES SINCE OCT 2000 EXTRACT PIPE/PIPE-X1In an extract database, outputs all changes compared with the given

extract, which must be higher in the extract hierarchy, at the given

session or date.

OUTPUT /SHEET-1 CHANGES SINCE /STAMP_001

Outputs all changes to named element since the named Stamp.

The macro is sent to a file by using the standardALPHA FILEorALPHA LOGcommands

(see Section 2.5.3).

Corresponding versions of the DIFFERENCEcommand will output all differences. For

example:

OUTPUT /SHEET-1 DIFFERENCESS SINCE EXTRACT 44



26/194


2.5 Miscellaneous Facilities

2.5.1 Audible Error Trace

When a macro error occurs, there is an audible alarm at the workstation to signal that

the error has occurred. Occasionally, macro errors can be anticipated and no audible

warning is required. This command allows the audible warning to be switched on or off

either interactively or via a macro.

If the audible warning is ON, it will sound whenever an error alert is displayed.

ALARM ON - sets the audible tone to be on.

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

2.5.2 Switching Text Output Off (DEVICE TTY only)

The TRACEcommand is only relevant in TTY mode. It controls the automatic output of

the Current Element name. With TRACE set to ON, the name of an element is

displayed as it is accessed. With Trace set to OFF, the element name is not displayed.

When macros are being run, TRACE is always set to OFF automatically.

Examples:

TRACE OFF - stops the automatic name output.

TRACE ON - (default) restarts automatic output of Current Element

name.

2.5.3 Logging the Alpha Display

TheALPHA command allows you to log commands and responses displayed in the

Command Input & Output window. Examples of theALPHA LOGcommand are:

ALP LOG /LF1 - log displayed alpha information in file /LF1

ALP LOG /LF1 OVER - as above, but overwrite existing file /LF1

ALP LOG END - finish logging information

ALPHA FILEwill only record commands you give, not the system's responses.

2.5.4 Controlling Output of Warning Messages

The WARNINGScommand allows you to suppress the output of warning messages:

WARNINGS OFF - suppress the output of warnings

WARNINGS ON - enable the output of warnings (default).


Version 11.6SP1


27/194


Summary of Commands

Entering DRAFT...

DRAFT - enters DRAFT

Leaving DRAFT...

QUIT - leaves DRAFT without saving database changes.

QUITmodule_name - switches to named module, without saving database changes.

module_name - switches to named module, saving database changes.

Saving and Restoring the Current Display Status...

RECREATEname[OVERWRITE]

saves the display status in the named file. (OVERWRITE option

overwrites existing file of the same name)

RECREATE DISPLAYname[OVERWRITE]saves modal settings, e.g. changes from default pen configuration,

units, text quality etc. Read back in using $M/name.

INSTALL SETUPname

restores the display definition stored in the named file. (Refers to

file saved by RECREATE, not RECREATE DISPLAY.)

Saving and Getting Work...

SAVEWORK - saves the current DRAFT additions or modifications withoutleaving DRAFT

GETWORK - updates drawings with any changes made to the PADD

database by other users.

Audible Error Trace...

ALARM ON, ALARM OFF - turns audible error trace ON or OFF.



28/194


Finding the Current User Status...

STATUS - list current user status.

Finding the Current System Status...

SYSTAT - list current active status of project.

Listing Multiple-Database Information...

LIST option - lists most of the available project information held in the

System Database.

option= USERS, MDBS, DBS, TEAMS

Querying MDB Information...

QUERY USER - lists information about current user.

QUERY USER word - lists information about named user.

QUERY TEAM word - lists information about named team.

QUERY DB dbname - lists information about named DB.

QUERY MDBname - lists information about named MDB.

MDB mode...

M A - saves changes and enters MDB Mode

DB UPD TE MDB NOUPDATE enters

MDB Mode without saving changes.

In MDB mode you can give the following commands. See the

VANTAGE PDMS MONITOR Reference Manualfor more

information.

EXCHANGE alter the databases in the current list of the current MDBDEFERCURRENT

PROTECT temporarily alters your access rights to specified

databases.

USER changes the current user

PROJECT changes the current project

VAR allows you to set variables


Version 11.6SP1


29/194


QUERY allows you to query:

Users, including the number of active users,

Teams including the set (current) Team,Databases, including copied Databases,

MDBs, Macros and Variables

EXIT - leave MDB Mode.

Comparing and Listing Database Changes ...

OUTPUT selection [CHANGES] SINCE [date : session number]

List changes (optional) to selected part of database since (optional)

given date or session.

OUTPUT selection [CHANGES] SINCE [stamp]

List changes (optional) to selected part of database since given

Stamp.

OUTPUT selection [CHANGES] SINCE [LATEST] EXTRACT [date : session number]]

List changes (optional) to selected part of extract database since it

was created, or since given date or session in its parent extract.

OUTPUT selection [CHANGES] SINCE EXTRACT [ no. : name]

List changes (optional) to selected part of database compared with

the latest version of the given extract, which must be higher in the

extract hierarchy.

OUTPUT selection [CHANGES] [SINCE [date : session number] EXTRACT [ no. :

name]

List changes (optional) to selected part of database compared with

the given date or session in the given extract, which must be

higher in the extract hierarchy.

DIFF selection optionSINCE [date: session number]

Lists difference between selected part of database since (optional)

given date or session.

DIFF selection option SINCE [stamp]

Lists differences between selected part of database since given

Stamp.

DIFF selection [CHANGES] SINCE [LATEST] EXTRACT [date : session number]]

List differences (optional) to selected part of extract database since

it was created, or since given date or session in its parent extract.

DIFF selection [CHANGES] SINCE EXTRACT [ no. : name]

List differences (optional) to selected part of extract database



30/194


compared with the latest version of the given extract, which must

be higher in the extract hierarchy.

DIFF selection [CHANGES] [SINCE [date : session number] EXTRACT [ no. : name]

List differences (optional) to selected part of extract database

compared with the given date or session in the given extract, which

must be higher in the extract hierarchy.

Claiming in Standard Multiwrite Databases . . .

CLAIM selection[HIERARCHY]

Makes a user claim of selected element(s), optionally including all

elements under the named elements.

UNCLAIM[ALL | selection option][HIERARCHY]

Unclaims selected (or ALL) element(s).

Claiming in Extract Databases . . .

EXTRACT CLAIM selection[HIERARCHY]

Makes an extract claim of selected element(s), optionally including

all elements under the named elements.

EXTRACT FLUSH [DB dbname| selection[HIERARCHY]]

Writes changes back to the owning extract, optionally including all

elements under the named elements.

EXTRACT ISSUE [DB dbname| selection[HIERARCHY]]

Writes changes back to the owning extract, optionally including all

elements under the named elements, and releases the extract

claim.

EXTRACT RELEASE [DB dbname| selection[HIERARCHY]]

Releases the extract claim. The given elements must have beenflushed.

EXTRACT REFRESH

Refreshes the extract with changes made to the owning extract.

EXTRACT DROP [DB dbname| selection[HIERARCHY]]

Drops the changes made to the named elements.


Version 11.6SP1


31/194


Controlling and Logging the Alpha Display...

ALP LOG /LF1 - log displayed alpha information in file /LF2

ALP LOG /LF1 OVER - as above, but overwrite existing file /LF1

ALP LOG END - finish recording alpha information

Suppressing warning messages...

WARNINGs OFF - suppress the output of warnings

WARNINGs ON - enable the output of warnings (default).



32/194


33/194

3 Drawing the Design

This Section describes how to create an unannotated DRAFT picture. It describes the

part of the DRAFT database that stores the main administrative and graphical

elements, and how to create them. It then describes Views, which are the areas used to

display design elements, and how to define their contents.

Note: Throughout this manual,view(lower case letters) means an area view, alpha

view or plot view, whereasVIEW(upper-case letters) refers to the VIEW

database element. All other database elements are also named using fourupper-case letters (e.g. DRWG, SHEE, LIBY), but may also be referred to in

unabbreviated form with just a leading upper-case letter (e.g. Drawing instead

of DRWG).

3.1 Introducing the DRAFT Database

The top-level graphical elements in the DRAFT Database hierarchy are shown below.

DRAWING

SHEET

VIEW

Figure 3-1 The DRAFT Database Hierarchy - Principal Graphic Elements

The principal element is the Drawing (DRWG), which is the Database equivalent of the

traditional paper drawing. All the elements below DRWG in the hierarchy are used to

store the information required to completely define the Drawing.

A Drawing can own one or more Sheet (SHEE) elements, which correspond to the

sheets of a paper drawing (Sheet 1 of 3, Sheet 2 of 3 etc). A Drawing can consist of asingle Sheet. A Sheet is the highest-level element that may be displayed within a view.

A Sheet may own one or more VIEW elements. These are projections of parts of the

Design Database. A VIEW element has attributes that:

define the viewing parameters (looking direction, through point, scale, etc)

define the size, position and orientation of the region on the Sheet that the View

occupies

refer to another DRAFT database element that contains a list of the Design (or

Catalogue) elements that make up the VIEW picture.

The full DRAFT database hierarchy is illustrated in Appendix A.



34/194

Drawing the Design

3.2 Creating a Drawing, a Sheet and a View

The top-level element in a PDMS database is the World. Users cannot delete or create

the World. Starting with the World as the current element, you can create the hierarchy

under the World using a command sequence such as:

NEW DEPT /PIPESNEW REGI /PIPREGNEW DRWG /PD101NEW SHEET /SHEET1NEW VIEW /PLAN

You can omit all commands except for NEW DRWG and NEW VIEW if there is only

Department, one Registry and one Sheet on the Drawing. If the administrative elements

do not exist they will be created automatically.

Departments (DEPT) and Registries (REGI) are administrative elements.

Departments own Registries, as shown in the following diagram.

WORLD

DEPT

REGI

REPODRWG

LIBY

SHEE

DLLB

IDLI

ADDE REME

VIEW

IDLN

(or to a DESIGNdatabase element)

DESIGNDatabase

Note

different part of the Design model, or different views of the same part of the

model. See Section 3.5 for details of manipulating the contents of a VIEW.

Figure 3-2 The top part of the DRAFT Database Hierarchy

: You can have several VIEWs on a Sheet. Each VIEW can contain a picture of a


Version 11.6SP1


35/194

Drawing the Design

3.2.1 Defining the Contents of a View

There are two methods of specifying the contents of a VIEW:

3.3 ts Using the AUTO Command

ied design element to the View. For example:

This command carries out the following operations:

ent

to be displayed (/ZONE1 in our example).

corr

The such that the

defi

ote:

in a central picture storewithin the computer's memory.

ended. It will save

in the central picture

aving DRAFT by switching to another module will perform an implicit

SAVEWORK, and so graphics in the central picture store will be saved to picture

files.

Specifying the contents directly, by referencing a single Design database element.

See Section 3.3.

Specifying the contents indirectly, by referencing a DRAFT database element,

which can be set up so as to refer to a set of Design database elements. See Section

3.4.

Defining View Conten

TheAUTO command adds a specif

AUTO /ZONE1

The VIEWs IDLN (ID List Name) attribute is set to the name of the Design elem

The VIEWs THPO (Through Point) attribute is set to the Site coordinates

esponding to the centre of interest of the view.

VIEWs VSCA (VIEW Scale) attribute is set to a value calculated

ned picture will fit within the VIEW.

N AUTO only sets the IDLN attribute if it has not already been set. A second

AUTO command will not change the IDLN. TheAUTO command by itself will

use the existing IDLN setting.

The projection of the Design model must now be created before a picture can be

produced. This is done by typing;

UPDATE DESIGN

SAVEWORK

Notes: The UPDATE command creates the VIEW graphics

The SAVEWORKcommand is not necessary but it is recomm

the graphics in the central picture store to picture files in the picture file

directory. In a subsequent DRAFT session, the graphics will be read from the

picture file without the need for the UPDATEcommand.

If you leave DRAFT via a QUITcommand the graphics

store will not be saved and any existing picture files will not be updated.

Le



36/194

Drawing the Design

An UPDAT could take several minutes in complex cases. If you wish

to interrupt it (for example, you may realise there is another change you should have

made before giving the command), press Ctrl C(not NT).

sign operation will take a considerable time, you

3.4 ining VIEW Contents Using Id Lists

u of an Id List(IDLI

Starting at World level, the library part of the database is set up as in the following

example:

(See

(see

ypes

ry

The DLLB is used to group together Id List (IDLI) elements.

The Id List is constructed by usingADDand REMOVEcommands as in the following

ADD and R e line, for example:

NE1.EQUIP, /ZONE1.PIPES REMOVE /VESS1, BRAN 2 OF /PIPE3TheADDa ly create the Add Entry (ADDE) and

E DESIGNoperation

Where it is known that the Update De

may wish to initiate it as a Background Process (see 3.10).

Def

Yo can add many elements to a VIEW by displaying the contents

element). The Id List contains a list of the elements to be displayed. Id Lists are

contained within Drawing ListLibraries (DLLB elements).

NEW LIBY /LIB1NEW DLLB /DLB1NEW IDLI /ID1

the left-hand part of Figure 3-2)

Library (LIBY) elements can appear at four positions in the hierarchy

Appendix A). They are administrative elements used to group together several t

of sub-library. The type of sub-library of interest here is the Drawing List Libra

(DLLB).

example:

ADD /ZONE.PIPES2-1ADD /ZONE.EQUI2-1REMOVE /PIPE2-1-12REM /PUMP2-1-12

EMOVE may be combined on a singl

ADD /ZOnd REMOVEcommands automatical

Remove Entry (REME) elements shown in Figure 3-2, also setting those ADDE and

REME attributes which refer to (in this example) appropriate elements in the Design

database. Other Id Lists may be added or removed in the same way. For example:

NEW IDLI /LIST1ADD /ZONE1ADD /LIST2REM /LIST3


Version 11.6SP1


37/194

Drawing the Design

Note: When evaluated individually both /LIST2 and /LIST3 must define a set of

design elements which are then added to/removed from /LIST1, respectively. In

/BRAN2, /BRAN3

/BRAN2, /BRAN3

ries then the member list order is important. For an entry

een (implicitly) added previously. Hence a Remove Entry

should never be the first element in an Id List. Consider the command sequences:

ce 2

ADD /ZONE.PIPES ADD /ZONE.PIPES

d removes all branches owned by /PIPE1 - including

/PIPE1-1 which has been added by the second command (and implicitly by the first). In

Sequence 2 these commands have been reordered so that having removed all branches

in /PIPE1 (second command) the required Branch (/PIPE1-1) is added by the final

command.

IDLI /ID1or indirectly:

3.4.1 A

The DESADD ign

elements to a 3D view. The syntax is similar to theADDand REMOVEcommands

scr

This sequence of commands adds elements /ZONE.PIPES2-1 and /ZONE.EQUI2-1 to a

3D View, a by the

interface.

particular if /LIST3 is being used to remove a number of Branches (say) from/LIST1 then it should be defined as:

ADD /BRAN1,

and NOT as:

REM /BRAN1,

If an Id List has Remove ent

to be removed it must have b

Sequence 1 Sequen

ADD /PIPE1-1 REM /PIPE1REM /PIPE1 ADD /PIPE1-1

In Sequence 1 the final comman

Having created an Id List it can be used to define the contents of a VIEW by setting the

VIEW's IDLN attribute directly:

AUTO /ID1

as described in Section 3.3.

dding elements to 3D View

and DESREMOVE commands allow for the addition and removal of Des

de ibed above. For example:DESADD /ZONE.PIPES2-1DESADD /ZONE.EQUI2-1DESREMOVE /PIPE2-1-12DESREM /PUMP2-1-12

nd removes /PIPE2-1-12 and /PUMP2-1-12. This is normally activated



38/194

Drawing the Design

3.4.2 Selective Additions to the Id List

The PDMS Selection syntax can be used to generate Id Lists. For example:

AND TBOR LT 25 ) FOR /ZONE/PIPES

ADD ALL FROM !COLLECTION

t references.

at the

exam

eyword in these cases, otherwise the criterion will

These forms of the ADD and REMOVE commands set the CRIT attribute of the ADDE

and REM

In this case the RULEkeyword is not required.

S 000 U0

The first example would create a list of ADD entries, one for each significant element

that is in /Z e second example would

generate a list of ent in the current MDB

that overlaps the specified volume.

Note: If the spatial map is not up-to-date the list of elements generated may not be

correct. The method may produce very long Id Lists. These are

liable to become out-of-date as elements are added to, and removed from, the

ults may be yielded by setting the IDLIs LIMI

mary section at the end of this Section) to define

d ZONEs to the Id

ADD ALL EQUI FOR /SITE/99

REM ALL BRAN WITH ( HBOR LT 25

where !COLLECTION is a PDMS local variable containing a list of

Design elemen

In the above examples the Selection criteria are not stored in the database but

expanded, and the resulting list of elements stored. This can result in very long Id

Lists. You can define criteria, which are stored in the database, and only expanded

time of an UPDATE DESIGNcommand using the RULEkeyword. For

ple :

ADD RULEALL ZONE WITH ( FUNC EQ 'PIPING' )REM RULEALL BRAN WITH ( HBOR LT 25 AND TBOR LT 25 )

You must be sure to use the RULE k

be evaluated when the Rule is defined, and very many ADDEs and REMEs may be

created.

E elements. The CRIT attribute can also be set directly, for example:

NEW ADDECRIT ALL BRAN WITH ( PSPE EQ /RF300 )

3.4.3 The Spatial Map

TheADD ... WITHIN variation of theADDcommand uses the PDMS spatial map.The

spatial map is a simplified geometric representation of the design model. For example:

ADD /ZONE99 WITHIN E5000 N5000 U5000 TO W1000 1REMOVE WITHIN E2500 N1000 U500 TO E0 N0 U0

ONE99 and which overlaps the specified volume. Th

REMOVE entries, one for each significant elem

ADD ... WITHIN

Design databases. Better res

attribute (see Command Sum

the required volume and only ADD the relevant SITEs an

List.


Version 11.6SP1


39/194

Drawing the Design

3.4.4 Changing the Limits of the View Contents

The display of Design elements within a VIEW can be changed without affecting the IdList by changing the LIMI attribute of the IDLI element. This is done using the LIMITS

LIMITS E1000 N8000 U1000 TO E5000 N1000 U900

This ow rent position and deletes

3.4

QFOR /design_element_name At an IDLI, or at a VIEW.

specified, separated by spaces or commas

d List name/VIEW name is not required if the current element

is the Id List itself or a related VIEW.

IEW) outputs Id List members and limits.

Q

ands relating to Id Lists are:

Q MAP

Q mpassing volume of given element

nts in the given volume

command. For example:

Define limits explicitly.

LIMITS @ TO @

Set limits as 3D coordinates using the cursor.

LIMITS ID @ ID @

Set limits as 3D coordinates via Design elements selected with the

cursor.

3.4.5 Cleaning Up Id Lists

Id Lists may be purged of unknown references by the command:

DELETE NULL IDLIstmembers

command scans d n the database hierarchy from the cur

all ADDE and REME elements whose IDNM attribute is null or references an unknown

element.

.6 Querying Id Lists

Q IDLN FOR /design_element_name A series of Design element names may be

will output information on whether the named element is wholly included in the named

Id List (i.e. in the Id List and no member elements REMOVEd), partially included in the

named Id List (i.e. in the Id List but some member elements REMOVEd), or absent from

the named Id List. The I

QIDLN DESC (at a V

Note that querying the Id List in the usual way will list its ADDE and REME elements;

a more comprehensive output can be obtained by:

DESCRIPTION (at IDLI, ADDE or REME elements)

Other querying comm

Lists status of spatial maps in the current MDB

VOLUME identifier Gives enco

Q WINDOWvolume Lists significant eleme



40/194

Drawing the Design

3.5 Changing the Picture by Changing VIEW Attributes

explicitly in the usual way, and the effect on an elements attributes of giving the

LFRA controls the visibility of the VIEW frame. The frame will be drawn using the pen

defined by on 8 for a description of pens.

LFRA TRUE

turns the f

LFRA FF)

turns the fr

3.5.2 The Vi w S

SIZE is the paper size of the VIEW rectangle. Changing the size by a command such as

SIZE 00

e new VIEW frame.

e used to

resize and reposition the VIEW. For example:

O @

rs of VIEW defined by cursor

Centre of VIEW defined by cursor

y cursor:

BR bottom right

C centre

The default size is that of the owning Sheet. The VREGION command also affects the

XYPS attribute (see below).

The SIZE command can also be used at SHEE level to change the Sheet size.

This section describes the effects of changing the VIEW attributes. Attributes can be set

various DRAFT commands can be seen by giving a QUERY ATTRIBUTES command for

the element concerned.

3.5.1 The VIEW Frame

the Views NLPN attribute. See Secti

(or FRAME ON)

rame on,

FALSE (or FRAME O

ame off. The frame is OFF by default.

e ize

4 400

leaves the scale of the VIEW contents unaffected, but moves the point at the centre of

the picture to the centre of th

The SIZE attribute is also be changed by the VREGION command, which may b

VREGION FROM @ T

Opposite corne

VREG X100 Y100 TO X500 Y500

Opposite corners of VIEW defined explicitly

VREG AT @

VREG corner AT @

Specified corner of VIEW defined b

TL top left

TR top right

BL bottom left


Version 11.6SP1


41/194

Drawing the Design

3.5.3 The View Centre

XYPS controls the position of the centre of the VIEW on its owning Sheet. This attributetakes two numeric values, which are the coordinates of the centre of the VIEW relative

to the bottom left corner of the Sheet. The attribute can be set directly by commands

such as

AT @

Nominate new XYPS with cursor

XYPS 350 250

Change attribute directly

See Figure 3-3. The default XYPS is at the centre of the Sheet.

Figure 3-3

ONPOS is the position of the

Changing VIEW XYPS

centre of the VIEW contents, relative to the centre of the

e takes

See Figure 3-4. Changing ONPOS will make the existing VIEW graphics out-of-date, so

VIEW. VIEW contents are centred within the VIEW by default, so this attribut

the default values x0 y0. ONPOS is set directly, for example:

ONPO 45 -25

an UPDATE DESIGNcommand must be given.

ONPO ONPO

Figure 3-4Changing VIEW ONPOS



42/194

Drawing the Design

3.5.4 The View Scale

VSCA controls the scale of the VIEW contents. The scale will normally be setautomatically to a value which ensures that the VIEW contents fit comfortably wi

the VIEW boundary (see

thin

theAUTO command), but can be changed if necessary, e.g.

The larger the VSCA value, the larger are the displayed objects.

ple:

VRAT 1 TO 75

VRAT 1/16in TO 1ft

Two positive values have to be specified but the TO may be omitted. Setting VRAT will

cause the existing VIEW scale (VSCA attribute) to be recalculated. Setting VSCA

directly causes VRAT to be unset. The AUTO command calculates and sets VSCA

directly so this will also cause VRAT to be unset.

Care should be taken when changing VSCA, as it is easy to move the VIEW contents

over the VIEW frame. The AUTO command takes the ONPOS value into consideration

when it calculates the VSCALE.

3.5.5 Orientation of View Contents

ADEG controls the orientation of the VIEW contents. The attribute has a default value

le:

VSCA 0.05

VIEW scale may be expressed in terms of a ratio using theVRAT(VIEW Ratio)

attribute, for exam

of 0, and can be set to any angle. ADEG can be set directly or by using the TURN

command, for examp

TURN 60ADEG -120

A positive value results in an anticlockwise rotation. Figure 3-5illustrates the effect of

changing ADEG.


Version 11.6SP1


43/194

Drawing the Design

ADEG 0 ADEG 90

3-5Changing Orientation of VIEW Contents

Note that the degree of rotation produced is relative to an ADEG value of 0, not to the

last value o

rection of the top of the VIEW region relative to the top of the

tive) can be used to give a perspective projection, the value taken by the

arallel

, an

UPDATE D picture.

3.5.7 3D

.

an be added using the

DESADDcommand (see 3.4.1).

Throug

Figure

f ADEG.

(rotVarying RCOD ation code) produces a similar effect to varying ADEG, except that

the VIEW is rotated as well. RCOD may be set to UP, DOWN, LEFT or RIGHT,

corresponding to the di

screen. Default is UP.

3.5.6 PerspectivePERS (perspec

PERS attribute being related to the view angle. The default value of 0 gives a p

projection, which would be the normal setting for drawings. If PERS is changed

ESIGN command must be given to change the

View

A 3D View can be generated from a 2D View using the GENERATE MODELcommand

This view can be amended using the user interface. Elements c

3.5.8 Looking Direction

The Views line of sight is fully defined by any two of:

Looking direction

From point

h point



44/194

Drawing the Design

which are defined by the attributes DIR, THPO and FRPO. Setting one of these will

DIR (direction) specifies the looking direction, down by default. This attribute is set by

ISO3

e Design coordinates corresponding tocalculated automatically from the

VIEWs related Id List by the command.

explicitly by commands such as:

LOOK THROUGH N53426 W632764 U2125

Changing the DIRECTION, THROUGH point or FROM point will make the existingo this must be updated by typing

Query VIEWDIRection

or Down. This command gives an error when the

VIEW has Perspective or the current database position is not at or below a VIEW.

would give:

However, for a plan VIEW with RCODE LEFT, the result would be:

and for a plan VIEW with ADEG 120 (and RCODE UP) the result would be:

unset one of the other two, assuming they are both already set.

commands such as

LOOK ELOOK N45W

PLANELEVATION NDIR D

Note that the picture produced by changing the looking direction may not necessarily fit

into the VIEW frame.

The THPO (through point) attribute is set to ththe centre of interest of the view. These will be

AUTO

FRPO (the from point) is the position (in Design coordinates) at which the observer is

deemed to be.

The through point and from point may be set

LOOK FROM N53426 W632764 U2125FRPO N125671 E67342 U11254THPO N125671 E67342 U11254

VIEW graphics out of date, s

UPDATE DESIGN

before any change in the picture will be seen.

The 3D view directionequivalent to 2D Sheet direction may be queried using

where is Left, Right, Up

For example, in a plan VIEW with RCODE UP (the default), then the query

Q VIEWDIR LEFT

Viewdirection Left W

Viewdirection Left N

Viewdirection Left E 30 N


Version 11.6SP1


45/194

Drawing the Design

3.5.9 Representation Ruleset Reference

3.5.10 Hatching Ruleset Reference

The HRSF (Hatching Ruleset Reference) attribute refers to elements that control the

representation style to be used for hatching. See Section 4.3.

3.5.11 Change Ruleset Reference

The CRSF(Change Ruleset Reference) attribute refers to elements that control the

representation styles to be used for changed design items and annotations. See Section

10.

3.5.12 Arc Tolerance

TheATOL attribute controls the Arc Tolerance (the difference between the true and the

facetted representation of curves) of the graphical output for the VIEW, being set in

units of hundredths of a millimetre on the drawing. (Default value 15.)

3.5.13 View Gap

51774186 draft user guide part1

Documents