PDMS Draft Part 1 Basic Drawing Creation & Output

pdms1151/man11/doc1issue 140403

PDMS DRAFTUser Guide

Part 1: Basic Drawing Creation & OutputVersion 11.5

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

PLEASE NOTE:AVEVA Solutions has a policy of continuing product development: therefore, theinformation contained in this document may be subject to change without notice.AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TOTHIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE.While every effort has been made to verify the accuracy of this document, AVEVASolutions shall not be liable for errors contained herein or direct, indirect, special,incidental or consequential damages in connection with the furnishing, performance oruse of this material.

This manual provides documentation relating to products to which you may not haveaccess or which may not be licensed to you. For further information on which Productsare licensed to you please refer to your licence conditions.

Copyright 1991 through 2003 AVEVA Solutions LimitedAll rights reserved. No part of this document may be reproduced, stored in a retrievalsystem 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 andproprietary products of AVEVA Solutions or its licensors.

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

http://www.aveva.com/engineeringit/world/

VANTAGE PDMS DRAFT User GuidePart 1: Basic Drawing Creation & OutputVersion 11.5

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

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

Contents

1 Introducing PDMS DRAFT ............................................................................ 1-11.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-12.1 Saving..........................................................................................................................2-1

2.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-62.3.4 How to Find Out What You Can Claim........................................................2-8

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-13.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 Selective Additions to the Id List .................................................................3-53.4.2 The Spatial Map ............................................................................................3-63.4.3 Changing the Limits of the View Contents..................................................3-6

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

Version 11.5

3.4.4 Cleaning Up Id Lists..................................................................................... 3-73.4.5 Querying Id Lists .......................................................................................... 3-7

3.5 Changing the Picture by Changing VIEW Attributes ............................................. 3-73.5.1 The VIEW Frame.......................................................................................... 3-73.5.2 The View Size................................................................................................ 3-83.5.3 The View Centre ........................................................................................... 3-83.5.4 The View Scale .............................................................................................. 3-93.5.5 Orientation of View Contents..................................................................... 3-103.5.6 Perspective .................................................................................................. 3-113.5.7 Looking Direction........................................................................................ 3-113.5.8 Representation Ruleset Reference ............................................................. 3-123.5.9 Hatching Ruleset Reference ....................................................................... 3-123.5.10 Change Ruleset Reference.......................................................................... 3-123.5.11 Arc Tolerance .............................................................................................. 3-123.5.12 View Gap Length ........................................................................................ 3-12

3.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-20

4 Graphical Representation ............................................................................ 4-14.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-94.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-15.1 Introduction................................................................................................................ 5-15.2 Creating and Using Planes........................................................................................ 5-3

5.2.1 Perpendicular Plane (PPLA) ........................................................................ 5-45.2.2 Flat Plane (FPLA)......................................................................................... 5-75.2.3 Stepped Plane (SPLA) .................................................................................. 5-8

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

Contents

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

6 Using the Cursor ........................................................................................... 6-16.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-17.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 File Header Options ......................................................................................7-37.2.4 Encoding of Multi-Byte Characters ..............................................................7-37.2.5 Scaling............................................................................................................7-4

7.3 Configurable DXF Output..........................................................................................7-47.3.1 Configuration Datasets .................................................................................7-47.3.2 Switches and BLOCK Rules to Control DXF Export...................................7-77.3.3 Limitations...................................................................................................7-13

7.4 Configurable DGN Output.......................................................................................7-137.4.1 Configuration Datasets ...............................................................................7-137.4.2 Common Features of Option Switches .......................................................7-167.4.3 File-Related and Miscellaneous Options....................................................7-177.4.4 Pen Related Options....................................................................................7-207.4.5 Font Related Options ..................................................................................7-227.4.6 Level-Related Options .................................................................................7-237.4.7 Group Related Options................................................................................7-247.4.8 Product Support Options.............................................................................7-267.4.9 Validation feature and options ...................................................................7-267.4.10 Summary of Switches and Rules to Control DGN Export.........................7-277.4.11 Limitations...................................................................................................7-29

8 Pens and Linestyles...................................................................................... 8-18.1 Introduction ................................................................................................................8-18.2 Colours ........................................................................................................................8-38.3 Line Representations .................................................................................................8-4

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

8.4 Marker Types............................................................................................................8-158.5 Hatch Patterns .........................................................................................................8-168.6 Defining Pen Settings ..............................................................................................8-21

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

Introducing PDMS DRAFT

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

Version 11.5

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-19.1 The Report.................................................................................................................. 9-19.2 The Circulation List................................................................................................... 9-29.3 Drawing Revisions ..................................................................................................... 9-3

10 Change Highlighting................................................................................... 10-110.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-1A.1 Basic Hierarchy..........................................................................................................A-1

B System Update Commands..........................................................................B-1B.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-1D.1 Introduction................................................................................................................D-1D.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-2D.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

Index

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

1 Introducing PDMS DRAFT

1.1 What does DRAFT do?

DRAFT produces fully annotated scale drawings showing selected parts of the designmodel 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 viewof a 3D model; for example, a plan view, a front elevation and an isometric view may bedisplayed 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 numberof drawings.

• Graphics providing annotation, including not only dimensioning and text but alsosuch 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 DRAFTdatabase does not contain information describing the geometry of the graphics thatmake up a drawing, but gives a description of how those graphics should be presentedon a drawing.From this database definition (together with the Design and Catalogue databases whichdescribe the appropriate 3D model) a drawing is generated which reflects the state ofthe design at that particular time. The drawing can be displayed on the screen andprocessed to produce a hard copy plotfile.


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

Version 11.5

1.3 Who Should Read This Manual

This is a command-level manual, written for people who are writing or customising theirown graphical user interface. It describes all the DRAFT commands, with workedexamples where appropriate. It is assumed that you are familiar with the normal way ofusing DRAFT, via the supplied Graphical User Interface (GUI).For an introduction to using DRAFT via the GUI, see Drawing Production UsingVANTAGE PDMS, and for further information, see the online help. For informationabout DRAFT System Administration, see the VANTAGE PDMS DRAFT AdministratorApplication User Guide.For general information about customising the graphical user interface, see theVANTAGE Plant Design Software Customisation Guide and VANTAGE Plant DesignSoftware 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 notrelate 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, that 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 mainadministrative and graphical elements and how to create them. It also describesViews, which are the areas used to display Design elements, and how to define theircontent.

• Chapter 4, Graphic Representation, describes how Design elements are defined anddrawn using Representation Rules. It describes how Representation Rules aredefined and describes the part of the DRAFT database that stores theRepresentation Rules. It also describes Hatching Rules, used for the automatichatching of faces of Design elements.

• Chapter 5, Section Planes, describes how you can construct sections through Designitems, using Planes in DRAFT, which can be displayed at VIEW level.


VANTAGE PDMS DRAFT User Guide Contents-1-3Part 1: Basic Drawing Creation & OutputVersion 11.5

• Chapter 6, Using the Cursor, describes how, with many DRAFT commands, you canuse the cursor to identify an element in the graphics window by using the IDcommand followed by an @:.

• Chapter 7, Plotting and Drawing Output, describes how you can generate, at anytime during the drawing process, a plotfile consisting of a single Sheet, View, or thecontent of an Area View.

• Chapter 8, Pens and Linestyles, defines the attributes that are associated with pensand describes how to set these attributes.

• Chapter 9, Reports, Circulation lists and Revisions, describes how to create thedrawing office administrative elements; reports and circulation lists. It alsodescribes 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 aDRAFT View. It describes how Change Rules are defined and describes the part ofthe DRAFT database that stores the Change Rules. It also describes the concept ofComparison Dates and how these are used to determine whether Design andAnnotation elements have been changed

• Appendix A, DRAFT Database Hierarchy, provides a graphical representation of theDRAFT database structure.

• Appendix B, System Update Commands, describes functions in DRAFT that can beused to minimise problems with cross-database referencing when Design databasesare deleted and rebuilt from macros. It also describes how the UPDATEINSTANCES command is used to update picture files that use the ‘instancing’mechanism.

• Appendix C, Picture File Naming Conventions, describes the structure of picture filenames.

• Appendix D, Guidelines for Importing DGN Files from DRAFT into MicroStation,describes how DRAFT drawings can be output as DGN files that can be importedinto a freshly installed version of microStation/J. It contains guidelines for ensuringthat fonts are translated correctly and how to improve other aspects of thetranslation.


2 General PDMS Commands

This Section describes some general PDMS commands, common to several PDMSmodules, 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/INSTALLfacility allows the display setup (including the full forms and menus set) to be saved, forrestoration 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, not RECREATE DISPLAY.)

NOTE: Forms resized or moved using the cursor will be INSTALLed to their originalsize.

2.1.2 Saving Work

The command:SAVEWORK

saves the current DRAFT additions or modifications without leaving DRAFT. It is goodpractice to use this command on a regular basis during a long DRAFT session to ensuremaximum data security.

General PDMS Commands


Version 11.5

2.1.3 Seeing Changes Made by Other Users

The commandGETWORK

updates the DRAFT database with the changes made by other users, if the database hasbeen opened in multi-write mode.

2.2 Accessing Multiple Database Information

The Multiple Database Access facilities allow you to list information about thedatabases you are using. It is also possible to change to another Multiple Database (seeSection 2.2.5), thus entering MDB Mode, from which further database-related activitiescan be performed.

2.2.1 Finding the Current User Status

The STATUS command gives you information about your current user status and that ofthe DBs to which you have access.For example, a typical response to the STATUS command 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, thathe is logged in to workstation PC378 as user 222f (a hexadecimal code), that he is amember 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 theteam which owns it), and MASTER/DRAFTAPP, MASTER/DRAFTLIB, MASTER/CATAand 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 SYSTAT command gives you information about the current active status of theproject within which you are working. It lists all users who are currently accessing the



project, the modules and databases which they are using, and whether they areexamining (Read-only status) or modifying (Read/Write status) the database. A typicalresponse to the SYSTAT command 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 isaccessing 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 tothe DB USER/USERB.

2.2.3 Listing Multiple-Database Information

The LIST command allows you to list most of the available project information held inthe 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 ADMINmodule of PDMS.A typical response to the LIST MDB command could be:

List of MDBS for project DRA==============================MDB: /USERACurrent DBS: 1 USER/USERA PADD EXCLUSIVE 2 MASTER/DRAFTAPP PADD UPDATE 3 MASTER/DRAFTLIB PADD UPDATE 4 MASTER/CATA CATA UPDATE 5 MASTER/DESI DESI UPDATEDeferred DBS:**NONE**

MDB: /USERBCurrent DBS: 1 USER/USERB PADD EXCLUSIVE 2 MASTER/DRAFTAPP PADD UPDATE 3 MASTER/DRAFTLIB PADD UPDATE 4 USER/DESIB DESI EXCLUSIVE 5 MASTER/CATA CATA UPDATE 6 MASTER/DESI DESI UPDATEDeferred DBS:**NONE**

A typical response to the LIST USERS command could be:



Version 11.5

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

GEN (GENERAL)TEAMS : TEST

The information generated by the LIST command will be displayed within the PDMSDRAFT REQUESTS window 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 USERQUERY USER wordQUERY TEAM wordQUERY DB dbnameQUERY 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. TheMDB command puts you into MDB Mode, where you can use a limited number ofMONITOR commands,You can either update the current MDB to save your changes before entering MDBMode, or ignore any changes made since your last SAVEWORK command (see Section2.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 VANTAGEPDMS MONITOR 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



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 multiwrite database, several users canwrite to it simultaneously, although they cannot change the same element.Multiwrite databases can either be Standard multiwrite databases, or Extractdatabases. In both types, an element must be claimed before it can be modified.Claiming an element prevents other users claiming (and modifying) the element; theelement must be unclaimed or released before another user can change it.Claiming can be either explicit, where the user must use the CLAIM command beforeattempting to modify the element, or implicit, where the claim is made automaticallywhen the user tries to modify the element. The claim mode is set when the DB iscreated. For full details see the VANTAGE PDMS ADMIN Command Reference Manual.

2.3.1 User Claims

In a Standard multiwrite database, you must claim an element before changing it. Thisis known as a user claim. If the claim mode is explicit (see below for details of how tocheck this), you must first claim each element that you want to modify using the CLAIMcommand. If the claim mode is implicit, the claim will be made automatically (althoughyou can still give explicit CLAIM commands if you want to prevent other users claimingspecific elements).Only primary elements can be claimed, that is:DEPT REGI DRWG LIBY SYLB ISOLB LALB SHLB BACK OVER SHEEYou 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, theprimary element above it in the hierarchy will be claimed.Examples of use of the CLAIM/UNCLAIM commands are:

CLAIM /SHEE1 /SHEE2 /SHEE3Claims named Sheets

CLAIM /DRWG HIERARCHYClaims named Drawing and all of its owned hierarchy



Version 11.5

CLAIM /VIEW2-1Claims Sheet which owns named View (since VIEW is not a primaryelement)

An element must be unclaimed before another user can claim it and change it. Userclaims are always unclaimed when you change modules or leaves PDMS, and you canalso unclaim elements at any time during a PDMS session using the UNCLAIMcommand.

UNCLAIM /SHEE2 /SHEE3Unclaims named Sheets

UNCLAIM ALLUnclaims all elements currently claimed

2.3.2 Notes on Standard Multiwrite DBs

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

• Elements cannot be unclaimed if there are updates outstanding. You must issue aSAVEWORK command first.

• You can insert/remove primary elements in a members list without claiming theowner. For example, you can add a Sheet into a Drawing without claiming theDrawing. Thus two users can add different Sheets to the same Drawing: anydiscrepancies will be resolved when a SAVEWORK is attempted.

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

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

• If two concurrent users allocate the same name to different elements, thesecond user to attempt a SAVEWORK will show up an error. The second usermust rename their element.

• If one user inserts a primary element into another element’s list, while aconcurrent user deletes the latter element, an attempt to SAVEWORK willshow up an error. Either the first user must delete or move the primaryelement, or the second user must QUIT without saving the deletion.

2.3.3 Extract Databases

Unlike standard multiwrite databases, extracts allow users to keep elements claimedwhen they exit from PDMS or change module. They can also be used, together with DataAccess Control, to manage workflow. See the VANTAGE PDMS ADMIN User Guide formore information.



An extract is created from an existing Database. When an Extract is created, it will beempty, with pointers back to the owing or master database. Extracts can only becreated from Multiwrite databases, and all extracts are themselves Multiwrite. Anextract can be worked on by one User at the same time as another user is working onthe master or another extract.When a user works on the extract, an extract claim is made as well as a user claim.If the claim mode is explicit, the extract claim will be made automatically when youmake a user claim using the CLAIM command. You can also claim to the extract onlyusing the EXTRACT CLAIM command.

• If an element is claimed to an extract, only users with write access to theextract 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 theelement, the element will be claimed both to the extract and then to theuser. If the element is already claimed to the extract, then the claim willonly be made to the user.

• If the databases are set up with explicit claim, then the user will need touse the CLAIM command before modifying the element.

• Once a user has made a user claim, no other users will be able to work onthe elements claimed, as in a normal multiwrite database.

• If a user unclaims an element, it will remain claimed to the extract untilthe extract claim is released or 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 changesmade to the extract can written back to the master, or dropped. Also, the extract can berefreshed with changes made to the master.

EXTRACT CLAIM /SHEE1 /SHEE2 /SHEE3Claims named Sheets to the extract

EXTRACT CLAIM /SHEE1 /SHEE2 /DEPT-PIPE HIERARCHYClaims the named elements, and all the elements in the hierarchy tothe extract

The HIERARCHY keyword must be the last on the command line. It will attempt to claimto the extract all members of the elements listed in the command which are not alreadyclaimed to the extract.

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

EXTRACT FLUSH /SHEE1 /SHEE2 /SHEE3Writes the changes to the named elements back to the owing extract.The Extract claim is maintained.

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



Version 11.5

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

EXTRACT ISSUE /SHEE1 /SHEE2 /SHEE3Writes the changes to the named Sheets back to the owning extractand releases the extract claim.

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

EXTRACT RELEASE /SHEE1 /SHEE2 /SHEE3Releases the extract claim: this command can only be given to releasechanges that have already been flushed.

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

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

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

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

2.3.4 How to Find Out What You Can Claim

Before you start work on an extract, you should do a GETWORK and an EXTRACT REFRESH,which will ensure that you have an up-to-date view of the database.This section explains what different users will see as a result of Q CLAIMLIST commands.For this example, take the case of a database PIPE/PIPE, accessed by USERA, with twoextracts. Users USERX1 and USERX2 are working on the extracts.



USERA creates a Pipe and flushes the database back to the owning database,PIPE/PIPE. The results of various Q CLAIMLIST commands by the three Users, togetherwith the extract control commands which they have to give to make the new dataavailable, are shown in the following diagram.

DB PIPE/PIPEX1

USERX1

DB PIPE/PIPE-X2

USERX2

DB PIPE/PIPEUSERA



Version 11.5

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 which you are actually writing to.You can query the extract claimlist for a named database. The database can be thecurrent one or its owner:

Q CLAIMLIST EXTRACT DB dbname

USERX1 creates PIPE-100EXTRACT FLUSH DB PIPE/PIPEQ CLAIMLIST:

none

Q CLAIMLIST OTHER:none

Q CLAIMLIST EXTRACT:/PIPE-100

USERA:EXTRACT REFRESH DB PIPE/PIPEQ CLAIMLIST:

none

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

Q CLAIMLIST EXTRACT:/PIPE-100

USERX2:EXTRACT REFRESH DB PIPE/PIPEQ CLAIMLIST:

none

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

Q CLAIMLIST EXTRACT:none

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



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 auser claim, if it has not been unclaimed).Note that a change in the claim status of an existing element will be shown by theappropriate Q CLAIMLIST command as soon as appropriate updates take place, but auser 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 which 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 DBCLwhere DBCL is a pseudo-attribute which can have the text settings EXPLICIT orIMPLICIT.To query whether or not an element which you want to modify is currently claimed byanother user, navigate to that element and use:

Q LCLMwhere LCLM is a pseudo-attribute with the logical settings True (element alreadyclaimed) or False/Unset (element available for you to modify).To produce a list of all elements currently claimed by yourself:

Q CLAIMLISTTo produce a list of all elements currently claimed by other users who are accessing thesame DB:

Q CLAIMLIST OTHER



Version 11.5

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 DIFFERENCEcommand. 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 standard ALPHA FILE or ALPHA LOGfacilities (see Section 2.5.3).You can also report on differences in extract databases comparred with other extractshigher 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 OUTPUT command. The output is in the form of a macro. You canthen run in the macro to recreate the elements and their attributes.You can include only those elements whose settings have been changed since a specifiedearlier time (i.e. those elements which would be listed by the DIFFERENCE command).



The output is generated in three stages:1. Any elements which were originally locked are unlocked. Element deletions, name

changes and type changes are output. Note that reordering or insertion of elementsin their owner’s members list is treated as deletion followed by creation, so thatRefno 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 GADD commands are included if any elements wereincluded in Groups.

Examples of the use of the OUTPUT command are:OUTPUT /VIEW1-1

Outputs 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 givendate.

OUTPUT /VIEW1-1 CHANGESOutputs all changes to named element and its members since lastSAVEWORK command.

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

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

OUTPUT /SHEET-1 CHANGES SINCE EXTRACT 44

OUTPUT /SHEET-1 CHANGES SINCE EXTRACT PIPE/PIPE-X1In an extract database, outputs all changes compared with the latestversion of the given extract, which must be higher in the extracthierarchy.

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 givenextract, which must be higher in the extract hierarchy, at the givensession or date.

OUTPUT /SHEET-1 CHANGES SINCE /STAMP_001Outputs all changes to named element since the named Stamp.

The macro is sent to a file by using the standard ALPHA FILE or ALPHA LOG commands(see Section 2.5.3).Corresponding versions of the DIFFERENCE command will output all differences. Forexample:

OUTPUT /SHEET-1 DIFFERENCESS SINCE EXTRACT 44



Version 11.5

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 thatthe error has occurred. Occasionally, macro errors can be anticipated and no audiblewarning is required. This command allows the audible warning to be switched on or offeither 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 TRACE command is only relevant in TTY mode. It controls the automatic output ofthe Current Element name. With TRACE set to ON, the name of an element isdisplayed 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

The ALPHA command allows you to log commands and responses displayed in theCommand Input & Output window. Examples of the ALPHA LOG command 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 informationALPHA FILE will only record commands you give, not the system's responses.

2.5.4 Controlling Output of Warning Messages

The WARNINGS command allows you to suppress the output of warning messages:

WARNINGS OFF - suppress the output of warnings

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



Summary of Commands

Entering DRAFT...

DRAFT - enters DRAFT

Leaving DRAFT...

QUIT - leaves DRAFT without saving database changes.

QUIT module_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...

RECREATE name [OVERWRITE]saves the display status in the named file. (OVERWRITE optionoverwrites existing file of the same name)

RECREATE DISPLAY name [OVERWRITE]saves modal settings, e.g. changes from default pen configuration,units, text quality etc. Read back in using $M/name.

INSTALL SETUP namerestores the display definition stored in the named file. (Refers tofile saved by RECREATE, not RECREATE DISPLAY.)

Saving and Getting Work...SAVEWORK - saves the current DRAFT additions or modifications without

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



Version 11.5

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 MDB name - lists information about named MDB.

MDB mode...MDB UPDATE - saves changes and enters MDB Mode MDB NOUPDATE enters

MDB Mode without saving changes.In MDB mode you can give the following commands. See theVANTAGE PDMS MONITOR Reference Manual for moreinformation.

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

PROTECT temporarily alters your access rights to specifieddatabases.

USER changes the current user

PROJECT changes the current project

VAR allows you to set variables



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

OUTPUT selection [CHANGES] SINCE [LATEST] EXTRACT [date : session number]]List changes (optional) to selected part of extract database since itwas 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 withthe latest version of the given extract, which must be higher in theextract hierarchy.

OUTPUT selection [CHANGES] [SINCE [date : session number] EXTRACT [ no. : name]List changes (optional) to selected part of database compared withthe given date or session in the given extract, which must behigher in the extract hierarchy.

DIFF selection option SINCE [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 givenStamp.

DIFF selection [CHANGES] SINCE [LATEST] EXTRACT [date : session number]]List differences (optional) to selected part of extract database sinceit 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 databasecompared with the latest version of the given extract, which must



Version 11.5

be higher in the extract hierarchy.

DIFF selection [CHANGES] [SINCE [date : session number] EXTRACT [ no. : name]List differences (optional) to selected part of extract databasecompared 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 allelements 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 includingall elements under the named elements.

EXTRACT FLUSH [ DB dbname | selection[HIERARCHY] ]Writes changes back to the owning extract, optionally including allelements under the named elements.

EXTRACT ISSUE [ DB dbname | selection[HIERARCHY] ]Writes changes back to the owning extract, optionally including allelements under the named elements, and releases the extractclaim.

EXTRACT RELEASE [ DB dbname | selection[HIERARCHY] ]Releases the extract claim. The given elements must have beenflushed.

EXTRACT REFRESHRefreshes the extract with changes made to the owning extract.

EXTRACT DROP [ DB dbname | selection[HIERARCHY] ]Drops the changes made to the named elements.

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


3 Drawing the Design

This Section describes how to create an unannotated DRAFT picture. It describes thepart of the DRAFT database which stores the main administrative and graphicalelements, and how to create them. It then describes Views, which are the areas used todisplay design elements, and how to define their contents.

Note: Throughout this manual, view (lower case letters) means an area view, alphaview or plot view, whereas VIEW (upper-case letters) refers to the VIEWdatabase element. All other database elements are also named using fourupper-case letters (eg DRWG, SHEE, LIBY), but may also be referred to inunabbreviated form with just a leading upper-case letter (eg Drawing insteadof DRWG).

3.1 Introducing the DRAFT DatabaseThe top-level graphical elements in the DRAFT Database hierarchy are shown below.

DRAWING

SHEET

VIEW

Figure 3-1 The DRAFT Database Hierarchy - Principal Graphic ElementsThe principal element is the Drawing (DRWG), which is the Database equivalent of thetraditional paper drawing. All the elements below DRWG in the hierarchy are used tostore the information required to completely define the Drawing.A Drawing can own one or more Sheet (SHEE) elements, which correspond to thesheets 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 theDesign Database. A VIEW element has attributes which:• 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 which contains a list of the Design (or

Catalogue) elements which make up the VIEW picture.

Drawing the Design


Version 11.5

The full DRAFT database hierarchy is illustrated in Appendix A.

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 createthe World. Starting with the World as the current element, you can create the hierarchyunder 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 onlyDepartment, one Registry and one Sheet on the Drawing. If the administrative elementsdo 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

LIBY

REPODRWG

SHEE

DLLB

IDLI

ADDE REME

VIEW

IDLN

(or to a DESIGNdatabase element)

DESIGNDatabase

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

Drawing the Design


Note: You can have several VIEWs on a Sheet. Each VIEW can contain a picture of adifferent part of the Design model, or different views of the same part of themodel. See Section 3.5 for details of manipulating the contents of a VIEW.

3.2.1 Defining the Contents of a View

There are two methods of specifying the contents of a VIEW:• Specifying the contents directly, by referencing a single Design database element.

See Section 3.3.

• Specifying the contents indirectly, by referencing a DRAFT database elementwhich can be set up so as to refer to a set of Design database elements. See Section3.4.

3.3 Defining View Contents Using the AUTO Command

The AUTO command adds a specified design element to the View. For example:AUTO /ZONE1

This command carries out the following operations:• The VIEW’s IDLN (ID List Name) attribute is set to the name of the Design element

to be displayed (/ZONE1 in our example).

• The VIEW’s THPO (Through Point) attribute is set to the Site coordinatescorresponding to the centre of interest of the view.

• The VIEW’s VSCA (VIEW Scale) attribute is set to a value calculated such that thedefined picture will fit within the VIEW.

Note that AUTO only sets the IDLN attribute if it has not already been set. A secondAUTO command will not change the IDLN. The AUTO command by itself will use theexisting IDLN setting.The projection of the Design model must now be created before a picture can beproduced. This is done by typing

UPDATE DESIGNSAVEWORK

Notes: The UPDATE command creates the VIEW graphics in a central picture storewithin the computer's memory.The SAVEWORK command is not necessary but it is recommended. It will savethe graphics in the central picture store to picture files in the picture filedirectory. In a subsequent DRAFT session, the graphics will be read from thepicture file without the need for the UPDATE command.

Drawing the Design


Version 11.5

If you leave DRAFT via a QUIT command the graphics in the central picturestore will not be saved and any existing picture files will not be updated.Leaving DRAFT by switching to another module will perform an implicitSAVEWORK, and so graphics in the central picture store will be saved to picturefiles.

An UPDATE DESIGN operation could take several minutes in complex cases. If you wishto interrupt it (for example, you may realise there is another change you should havemade before giving the command), press Ctrl C (not NT).

3.4 Defining VIEW Contents Using Id Lists

You can add many elements to a VIEW by displaying the contents of an Id List (IDLIelement). The Id List contains a list of the elements to be displayed. Id Lists arecontained within Drawing List Libraries (DLLB elements).Starting at World level, the library part of the database is set up as in the followingexample:

NEW LIBY /LIB1NEW DLLB /DLB1NEW IDLI /ID1

(See the left-hand part of Figure 3-2)• Library (LIBY) elements can appear at four positions in the hierarchy (see

Appendix A). They are administrative elements used to group together several typesof sub-library. The type of sub-library of interest here is the Drawing ListLibrary (DLLB).

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

The Id List is constructed by using ADD and REMOVE commands as in the followingexample:

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

ADD and REMOVE may be combined on a single line, for example:ADD /ZONE1.EQUIP, /ZONE1.PIPES REMOVE /VESS1, BRAN 2 OF /PIPE3

The ADD and REMOVE commands automatically create the Add Entry (ADDE) andRemove Entry (REME) elements shown in Figure 3-2, also setting those ADDE andREME attributes which refer to (in this example) appropriate elements in the Designdatabase. Other Id Lists may be added or removed in the same way. For example:

NEW IDLI /LIST1ADD /ZONE1ADD /LIST2REM /LIST3

Drawing the Design


Note that when evaluated individually both /LIST2 and /LIST3 must define a set ofdesign elements which are then added to/removed from /LIST1, respectively. Inparticular if /LIST3 is being used to remove a number of Branches (say) from /LIST1then it should be defined as:

ADD /BRAN1, /BRAN2, /BRAN3

and NOT as:REM /BRAN1, /BRAN2, /BRAN3

If an Id List has Remove entries then the member list order is important. For an entryto be removed it must have been (implicitly) added previously. Hence a Remove Entryshould never be the first element in an Id List. Consider the command sequences:

Sequence 1 Sequence 2ADD /ZONE.PIPES ADD /ZONE.PIPESADD /PIPE1-1 REM /PIPE1REM /PIPE1 ADD /PIPE1-1

In Sequence 1 the final command removes all branches owned by /PIPE1 - including/PIPE1-1 which has been added by the second command (and implicitly by the first). InSequence 2 these commands have been reordered so that having removed all branchesin /PIPE1 (second command) the required Branch (/PIPE1-1) is added by the finalcommand.Having created an Id List it can be used to define the contents of a VIEW by setting theVIEW's IDLN attribute directly:

IDLI /ID1

or indirectly:AUTO /ID1

as described in Section 3.3.

3.4.1 Selective Additions to the Id List

The PDMS Selection syntax can be used to generate Id Lists. For example:ADD ALL EQUI FOR /SITE/99

REM ALL BRAN WITH ( HBOR LT 25 AND TBOR LT 25 ) FOR /ZONE/PIPES

ADD ALL FROM !COLLECTIONwhere !COLLECTION is a PDMS local variable containing a list ofDesign element references.

• Note that in the above examples the Selection criteria are not stored in thedatabase but expanded, and the resulting list of elements stored. This can result invery long Id Lists. You can define criteria which are stored in the database, andonly expanded at the time of an UPDATE DESIGN command using the RULE keyword.For example :

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

Drawing the Design


Version 11.5

You must be sure to use the RULE keyword in these cases, otherwise the criterion willbe evaluated when the Rule is defined, and very many ADDEs and REMEs may becreated.These forms of the ADD and REMOVE commands set the CRIT attribute of the ADDEand REME elements. The CRIT attribute can also be set directly, for example:

NEW ADDECRIT ALL BRAN WITH ( PSPE EQ /RF300 )

In this case the RULE keyword is not required.

3.4.2 The Spatial Map

The ADD ... WITHIN variation of the ADD command uses the PDMS spatial map. Thespatial map is a simplified geometric representation of the design model. For example:

ADD /ZONE99 WITHIN E5000 N5000 U5000 TO W1000 S1000 U0REMOVE WITHIN E2500 N1000 U500 TO E0 N0 U0

The first example would create a list of ADD entries, one for each significant elementthat is in /ZONE99 and which overlaps the specified volume. The second example wouldgenerate a list of REMOVE entries, one for each significant element in the current MDBthat overlaps the specified volume.Note: If the spatial map is not up-to-date the list of elements generated may not be

correct. The ADD ... WITHIN method may produce very long Id Lists which areliable to become out-of-date as elements are added to and removed from theDesign databases. Better results may be yielded by setting the IDLI’s LIMIattribute (see Command Summary section at the end of this Section) to definethe required volume and only ADD the relevant SITEs and ZONEs to the IdList.

3.4.3 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 LIMITScommand. For example:

LIMITS E1000 N8000 U1000 TO E5000 N1000 U900Define 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 thecursor.

Drawing the Design


3.4.4 Cleaning Up Id Lists

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

This command scans down the database hierarchy from the current position and deletesall ADDE and REME elements whose IDNM attribute is null or references an unknownelement.

3.4.5 Querying Id Lists

Q FOR /design_element_name At an IDLI, or at a VIEW.

Q IDLN FOR /design_element_name A series of Design element names may bespecified, separated by spaces or commas

will output information on whether the named element is wholly included in the namedId List (i.e. in the Id List and no member elements REMOVEd), partially included in thenamed Id List (i.e. in the Id List but some member elements REMOVEd), or absent fromthe named Id List. The Id List name/VIEW name is not required if the current elementis the Id List itself or a related VIEW.

Q IDLN DESC (at a VIEW) outputs Id List members and limits.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:

Q DESCRIPTION (at IDLI, ADDE or REME elements)Other querying commands relating to Id Lists are:

Q MAP Lists status of spatial maps in the current MDBQ VOLUME identifier Gives encompassing volume of given elementQ WINDOW volume Lists significant elements in the given volume

3.5 Changing the Picture by Changing VIEW Attributes

This section describes the effects of changing the VIEW attributes. Attributes can be setexplicitly in the usual way, and the effect on an element’s attributes of giving thevarious DRAFT commands can be seen by giving a QUERY ATTRIBUTES command forthe element concerned.

3.5.1 The VIEW Frame

LFRA controls the visibility of the VIEW frame. The frame will be drawn using the pendefined by the View’s NLPN attribute. See Section 8 for a description of pens.

LFRA TRUE (or FRAME ON)turns the frame on,

Drawing the Design


Version 11.5

LFRA FALSE (or FRAME OFF)turns the frame off. The frame is OFF by default.

3.5.2 The View Size

SIZE is the ‘paper size’ of the VIEW rectangle. Changing the size by a command such asSIZE 400 400

leaves the scale of the VIEW contents unaffected, but moves the point at the centre ofthe picture to the centre of the new VIEW frame.The SIZE attribute is also be changed by the VREGION command, which may be used toresize and reposition the VIEW. For example:

VREGION FROM @ TO @Opposite corners of VIEW defined by cursor

VREG X100 Y100 TO X500 Y500Opposite corners of VIEW defined explicitly

VREG AT @Centre of VIEW defined by cursor

VREG corner AT @Specified corner of VIEW defined by cursor:

TL top leftTR top rightBL bottom leftBR bottom rightC centre

The default size is that of the owning Sheet. The VREGION command also affects theXYPS attribute (see below).The SIZE command can also be used at SHEE level to change the Sheet size.

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 relativeto the bottom left corner of the Sheet. The attribute can be set directly by a commandssuch as

AT @Nominate new XYPS with cursor

XYPS 350 250Change attribute directly

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

Drawing the Design


Figure 3-3 Changing VIEW XYPSONPOS is the position of the centre of the VIEW contents, relative to the centre of theVIEW. VIEW contents are centred within the VIEW by default, so this attribute takesthe default values x0 y0. ONPOS is set directly, for example:

ONPO 45 -25

See Figure 3-4. Changing ONPOS will make the existing VIEW graphics out-of-date, soan UPDATE DESIGN command must be given.

ONPO ONPO

Figure 3-4 Changing VIEW ONPOS

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 withinthe VIEW boundary (see the AUTO command), but can be changed if necessary, e.g.

VSCA 0.05

The larger the VSCA value, the larger are the displayed objects.VIEW scale may be expressed in terms of a ratio using the VRAT (VIEW Ratio)attribute, for example:

Drawing the Design


Version 11.5

VRAT 1 TO 75VRAT 1/16in TO 1ft

Two positive values have to be specified but the TO may be omitted. Setting VRAT willcause the existing VIEW scale (VSCA attribute) to be recalculated. Setting VSCAdirectly causes VRAT to be unset. The AUTO command calculates and sets VSCAdirectly so this will also cause VRAT to be unset.Care should be taken when changing VSCA, as it is easy to move the VIEW contentsover the VIEW frame. The AUTO command takes the ONPOS value into considerationwhen it calculates the VSCALE.

3.5.5 Orientation of View Contents

ADEG controls the orientation of the VIEW contents. The attribute has a default valueof 0, and can be set to any angle. ADEG can be set directly or by using the TURNcommand, for example:

TURN 60ADEG -120

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

ADEG 0 ADEG 90

Figure 3-5 Changing Orientation of VIEW ContentsNote that the degree of rotation produced is relative to an ADEG value of 0, not to thelast value of ADEG.Varying RCOD (rotation code) produces a similar effect to varying ADEG, except thatthe VIEW is rotated as well. RCOD may be set to UP, DOWN, LEFT or RIGHT,corresponding to the direction of the ‘top’ of the VIEW region relative to the top of thescreen. Default is UP.

Drawing the Design


3.5.6 Perspective

PERS (perspective) can be used to give a perspective projection, the value taken by thePERS attribute being related to the view angle. The default value of 0 gives a parallelprojection, which would be the normal setting for drawings. If PERS is changed, anUPDATE DESIGN command must be given to change the picture.

3.5.7 Looking Direction

The View’s line of sight is fully defined by any two of :• Looking direction• From point• Through point

which are defined by the attributes DIR, THPO and FRPO. Setting one of these willunset one of the other two, assuming they are both already set.DIR (direction) specifies the looking direction, down by default. This attribute is set bycommands such as

LOOK ELOOK N45WISO3PLANELEVATION NDIR D

Note that the picture produced by changing the looking direction may not necessarily fitinto the VIEW frame.The THPO (through point) attribute is set to the Design coordinates corresponding tothe centre of interest of the view. These will be calculated automatically from theVIEW’s related Id List by the AUTO command.FRPO (the from point) is the position (in Design coordinates) at which the observer isdeemed to be.The through point and from point may be set explicitly by commands such as:

LOOK THROUGH N53426 W632764 U2125LOOK FROM N53426 W632764 U2125FRPO N125671 E67342 U11254THPO N125671 E67342 U11254

Changing the DIRECTION, THROUGH point or FROM point will make the existingVIEW graphics out of date, so this must be updated by typing

UPDATE DESIGN

before any change in the picture will be seen.The 3D view direction equivalent to 2D Sheet direction may be queried using

Query VIEWDIRection <sheet-dir>

Drawing the Design


Version 11.5

where <sheet-dir>is Left, Right, Up or Down. This command gives an error when theVIEW has Perspective or the current database position is not at or below a VIEW.For example, in a plan VIEW with RCODE UP (the default), then the query

Q VIEWDIR LEFT

would give:Viewdirection Left W

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

and for a plan VIEW with ADEG 120 (and RCODE UP) the result would be:Viewdirection Left E 30 N

3.5.8 Representation Ruleset Reference

The RRSF (Representation Ruleset Reference) attribute refers to elements that controlthe representation style to be used. See Section 4.1.

3.5.9 Hatching Ruleset Reference

The HRSF (Hatching Ruleset Reference) attribute refers to elements that control therepresentation style to be used for hatching. See Section 4.3.

3.5.10 Change Ruleset Reference

The CRSF (Change Ruleset Reference) attribute refers to elements that control therepresentation styles to be used for changed design items and annotations. See Section10.

3.5.11 Arc Tolerance

The ATOL attribute controls the Arc Tolerance (the difference between the true and thefacetted representation of curves) of the graphical output for the VIEW, being set inunits of hundredths of a millimetre on the drawing. (Default value 15.)

3.5.12 View Gap Length

The VGAP attribute allows you to define the size of the gap that DRAFT inserts in Viewlines where they are crossed by non-solid primitives such as Plines, centrelines,DRAWIs, etc. The default value is 1.5mm.

Drawing the Design


3.6 More on the AUTO command

Previous sections have described the use of the AUTO command to add Design elementsto views. There are two other uses of AUTO:

AUTO LIMITS OF /idlist_name

Here the VIEW’s VSCA and THPO attributes are calculated using only the LIMIattribute of the referenced Id List, ignoring any Design items in the VIEW. If the Id Listname is omitted, the Id List relevant to the VIEW is assumed.

AUTO FROM position TO position

The VIEW’s VSCA and THPO attributes are calculated from the box defined by the two3D coordinates given. The position may be specified using the cursor (3D point orp-point), explicit p-point reference, origin of a named element, or an explicit 3Dcoordinate.

Drawing the Design


Version 11.5

3.7 Hidden Line Representation

The VTYP (view type) attribute controls the hidden-line representation of displayedpictures. Five possible VTYP setting are provided. These give progressively greatergraphical accuracy at the expense of increasing processing requirements. This facilityallows you to produce preliminary and intermediate drawings (where graphical accuracymay be of secondary importance) quickly, leaving only finished drawings to incur thegreatest processing overhead. The default VTYP setting is WIRELINE, which gives aconventional wireline picture as shown in Figure 3-6.

Figure 3-6 Typical Wireline Picture

Drawing the Design


Modelled Wireline representation gives slightly greater realism by blending theintersection of primitives, but without incurring the computational overheads ofremoving hidden lines. Figure 3-7 shows a modelled wireline display.

Figure 3-7 Typical Modelled Wireline picture

Drawing the Design


Version 11.5

Local Hidden Line representation gives a picture where hidden lines are removedfrom individual significant elements (EQUI, SUBS etc), but not from items hiddenbehind them. This gives a picture as shown in Figure 3-8.

Figure 3-8 Typical Local Hidden Lines Removed picture

Drawing the Design


Global Hidden Line representation gives a picture where all hidden lines are removed,giving a picture as shown in Figure 3-9.

Figure 3-9 Typical Global Hidden Lines Removed pictureAlternative methods of setting VTYP are as follows:

VTYP WIRE - wireline (default)

VTYP MWIR - modelled wireline

VTYP LOCAL - local hidden lines removed

VTYP GLOBAL - global hidden lines removed

VTYP UNIV - global hidden lines removed and intersection lines generated

Universal representation (see Figure 3-10) gives a picture where all hidden lines areremoved (as in Global HLR), but in addition intersection lines between clashingsignificant elements (e.g. EQUI and STRU or SUBS and SUBS) are generated. Whetheryou will need to use this View type will depend on the way in which you have createdthe model. The need for VTYP UNIVERSAL will be greater if the model is composed of alarge number of significant elements each with a small number of primitives, ratherthan vice versa. It is also more likely to be needed in non-orthogonal Views, wheremissing intersection line are most noticeable.

Drawing the Design


Version 11.5

Global hidden line Universal hidden line(each primitive must beowned by a differentsignificant element)

Figure 3-10 UNIVERSAL VIEW Type

3.8 Querying Commands

3.8.1 Querying View Contents

You can query which Design elements are are visible in a specified DRAFT View usingthe Q VSCAN command. You can:• Request a list of all significant elements that are visible in a View.

Q VSCAN SIGNIFicant IN view_idFor example:

Q VSCAN SIGNIF IN /VIEW-01

• Specify a significant design element and request a list of all its primitives that arevisible in a View.

Q VSCAN design_id IN view_idFor example:

Q VSCAN /PIPE100-B-1-B1

• Specify selection criteria to determine matching design elements visible in a View.Q VSCAN FOR selection_criteria IN view_id

For example:Q VSCAN FOR ALL ( VALVE VTWAY VFWAY ) WITH ( ABOR GE 50 )

Drawing the Design


In the above examples, design_id must refer to a Design significant element, that isEQUI, SUBE, STRU, SUBS, FRMW, SBFR, TMPL, BRAN, or HANG.The IN view_id may be omitted if your current database position is at or below a View.DRAFT determines whether design items are visible by scanning the data in the picture,not by scanning the IDList. Thus elements hidden by the hidden-line-removal processwill not be found. This command cannot determine how much of the element is visible.NOTE: A significant Design element will not be found in a View if it only owns other

significant elements. It must own visible primitives. This affects EQUI, STRUand FRMW elements; they will not be found unless they own visible primitives.

3.8.2 Querying Whether an Element Appears in a View

You can query whether low-level design elements and their owners appear in a givenView using the command:

Q FIND gid IN viewwhere gid is the general identifier of the element and view is the view identifier. Forexample:

Q FIND /BOX99 IN /SH1/V1Q FIND /VESS-05 IN VIEWQ FIND ILEAVE TUBE OF /VALVE-24 IN /VIEW/02

The view identifier can be omitted if it is the current element. For example:Q FIND /BRANCH-01

Possible answers are:FOUNDMISSINGINVALID ELEMENT

NOTE: A significant Design element will not be found in a View if it only owns othersignificant elements. It must own visible primitives. This affects EQUI, STRUand FRMW elements; they will not be found unless they own visible primitives.

3.8.3 Querying the Nearest Side to an Item

You can query the nearest side of a View to a given P-point, proportional distance alonga P-line, or origin of a Design element in the current View using the command:

Q VSIDE [ROTated] OF 3d_point_definitionFor example:

Q VSIDE OF /VESS-99Q VSIDE OF PPO2 OF /VALVE-100Q VSIDE OF PPLINE TOS OF /SCTN-101 STARTQ VSIDE OF PPLINE MEML OF /SCTN-101 PROP 0.5

Drawing the Design


Version 11.5

The ROTATION option allows the rotation (ie the VIEW’s RCOD attribute) to beconsidered if required.The response will be the nearest and next-nearest sides, and also whether the item isinside or outside the View. For example, Point 1 in Figure 3-11 will be LEFT UPOUTSIDE.

Point 1 View frame

Figure 3-11 Querying the nearest side to an item

3.9 Switching Between Databases

You can switch between the Design, Draft and Catalogue Databases using thecommand:

SWITCHIf the current element is in the Design database, SWITCH will make the element lastselected in the DRAFT database current. Similarly, giving the SWITCH command whenin the Draft database will return to the element last selected in the Design database.If the current element is a Catalogue Component, SWITCH will return to the last Designelement accessed. You can go directly to the Draft database or Design Database usingthe commands:

CONTEXT DRAWING

CONTEXT DESIGN

Drawing the Design


Summary of Commands

At Id List . . .

ADD design_element_identifier [design_element_identifier...]adds Design element to Id List.

REM design_element_identifier [design_element_identifier...]removes Design element from Id List

ADD ALL design_element_identifier FOR design_element_identifier

REM ALL design_element_identifier WITH ( selection_criteria ) FORdesign_element_identifier

LIMITS E value N value U value E value N value U valueremoves Design elements from ID List that are not wholly orpartially contained within defined limits box.

LIMITS @ TO @ set limits as 3D coords with the cursor

LIMITS ID @ ID @ set limits as 3D coords via Design elements using the cursor

DELETE ENTRY numberdelete either an ADDE or REME from the Id List members - thenumber is the member list number

DELETE ADD numberdelete an Add item, number corresponding to number of theelement out of the Adds only

DELETE REM numberdelete a Remove item, number corresponding to the number of theelement out of the Removes only

Drawing the Design


Version 11.5

At DRWG and below . . .

UPDATE DESIGN updates picture to latest VIEW and Design parameters

UPDATE DESIGN IGNOREas above, but deleted design elements (specified in Id List) ignored(and UPDATE process does not abort)

UPDATE ANNO updates Drawing annotation (including Backing Sheets) to latestDesign data and VIEW attributes

UPDATE BSHEETS updates Backing Sheets. Will ensure that the latest version of thereferenced BACK is used and will re-evaluate hash codewords on it(see Section 13).

UPDATE ALL updates annotation, tag rules and Design graphics (but only forthat part of the picture file determined by the level in thehierarchy at which the command is used).

UPDATE ALL IGNOREas above, but deleted design elements (specified in Id List) ignored(and UPDATE process does not abort)

(The above commands can be given from anywhere in the hierarchy if an appropriateelement identifier is inserted after the UPDATE keyword.)The UPDATE DESIGN, UPDATE ANNO and UPDATE ALL commands can be specifiedwith the option SHOW CHANGES, for example UPDATE DESIGN SHOW CHANGES.Database changes will be shown in the manner defined by the View's Change Ruleset.For more information see Section 10. This option is only valid at View elements orabove, it cannot be used for a Layer, say.

UPDATE PICTURE regenerates Sheet level picture. Updates annotation graphics (butnot Design graphics). Use only when the picture file is corrupted.DRAFT will prompt the user when this is necessary. Use at Sheetlevel or equivalent.)

Drawing the Design


At VIEW . . .

SIZE xvalue yvalue set VIEW size in mm with origin at default i.e. centre of Sheet.Min, Max, x,y values are 1 mm, 3276 mm respectively.

SIZE paper_size set VIEW size to a standard paper size, e.g. SIZE A2

VREGION @ set VIEW size and position using cursor

VREGION FROM X value Y value TO X value Y valueset VIEW size and position explicitly

VREGION corner move VIEW using specified corner to position:TL - top leftTR - top rightBL - bottom leftBR - bottom rightC - centre

VREGION VERTICAL directionset VIEW (vertical axis) orientation:

U - upD - downL - leftR - right

AT @ position VIEW origin in Sheet using cursor

AUTO design_element_identifierset VIEW Scale and Through Point throughdesign_element_identifier and scale to fit

AUTO idlist_name set VIEW Scale, Through Point and Id List reference. Ifidlist_name is omitted the IDLI relevant to the VIEW is assumed.

AUTO LIMITS OF /idlist_nameuse limits box of Id List to define VIEW

AUTO FROM position TO positionuse specified limits box to define view. The VIEW’s VSCA andTHPO attributes are calculated from the box defined by the two 3Dco-ordinates specified by position. (position includes cursorspecification of a 3D point or p-point, explicit p-point reference,origin of a named element, or an explicit 3D coord.)

VSCALE value set Scale of VIEW

Drawing the Design


Version 11.5

THPO E value N value U value(or LOOK THROUGH ...)

set Through Point of VIEW in 3D coords

THPO ID @(or LOOK THROUGH ...)

set Through Point as Design element p-point (converted to 3Dcoord)

FRPO E value N value U value(or LOOK FROM ...)

set From Point of VIEW in 3D coords

FRPO @(or LOOK FROM ...) set From Point in 3D coords with cursor

FRPO ID @(or LOOK FROM ...) set From Point as Design element p-point (converted to 3D coord)

ONPO xvalue yvalueposition the Through Point relative to the VIEW origin

ONPO @ position the Through Point relative to the VIEW origin using thecursor

TURN value(or ADEG value) rotate VIEW anticlockwise

VTYP option set VIEW type.Options: WIRE, MWIR, LOCAL, GLOB, UNIV

LOOK value(or DIR value) set VIEW direction (standard PDMS)

ISO value set isometric VIEW direction

PLAN set plan VIEW direction

ELEV option set elevation VIEW direction options: N, E, S and W

PERSPECTIVE angle set VIEW perspective

ATOL value set arc tolerance

RRSF name set reference to Representation Ruleset (RRST) element

RCOD option set rotation code.Options: UP, DOWN, LEFT or RIGHT (default UP)

Drawing the Design


Q VIEWDIR option query 3D view direction equivalent to 2D Sheet direction

LFRA option set visibility of VIEW frame

FRAME option Options: TRUE or FALSE (LFRA)ON or OFF (FRAME).

LVIS FALSE makes the VIEW invisible

LVIS TRUE makes the VIEW visible (default)

Q VLIMITS gives 3D limits of View (View must be orthogonal, with noperspective)

Anywhere . . .

SW switch Design/Drawing contexts

CONT DRAW switch to Drawing context

CONT DES switch to Design context

DELETE NULL IDLI deletes all ADDE and REME elements whose IDNM attribute isnull or which references an unknown element

Querying Contents of a ViewQ FIND gid IN view

queries whether a design element appears in a given View

Q VSCAN SIGNIFicant IN view_idOutputs a list of all significant elements that are visible in a View

Q VSCAN design_id IN view_idSpecify a significant design element and request a list of all its primitivesthat are visible in a View.

Q VSCAN FOR selection_criteria IN view_idSpecify selection criteria to determine matching design elements visible ina View

Q VSIDE [ROTated] OF 3d_point_definitionqueries the nearest side, next-nearest side, and whether the item is insideor outside the View. 3d_point_definition can be p-point, proportionaldistance along a p-line, or origin of a Design element in the current View.The ROTATED option allows the VIEW rotation (ie the VIEW’s RCODattribute) to be considered if required.


4 Graphical Representation

Representation Rules control how Design elements are drawn. Each Rule can specifya given type or types of element, or named elements. Representation Rules refer toStyles. The attributes of a Style define a series of pens, for example, frontface, backfaceand centreline pens, and whether items such as plines and obstruction volumes areshown. The pens define properties such as linestyle and colour. For more informationabout pens see Section 8.Representation Rules can be created in a Library and be referred to from a VIEW, orthey can be owned directly by a VIEW, in which case they are known as local rules.Local Rules override Library Rules. See Section 4.2.2 for more information about theorder in which Rules are applied.Representation Rules (RRUL) are stored in Representation Rulesets (RRST),which in turn are owned by Representation Libraries (RPLB).RPLBs are also used to store STYLs. The reference from an RRUL to a STYL is made bysetting the STYF attribute of the RRUL. When a View references a RRST, the referenceis made by setting the RRSF attribute of the View.

Figure 4-1 Representation Rules Database HierarchyThis Section also describes Hatching Rules, which are used for automatic hatching offaces of Design elements. See Section 4.3.

Library

VIEW

RPLB

RRUL

STYLRRST

RRUL

RRSF

STYF

STYF

Graphical Representation


Version 11.5

For details of how changes to design elements can be shown see Section 10 ChangeHighlighting.

4.1 Representation Styles

The Representation Style (STYL) defines the appearance of the elements specified by aRRUL that references it. The STYL attributes, with their defaults, are as follows:

Tube flag TUBEF OFFCentreline flag CLIN ONPiping Symbol flag PSYM ONObstruction flag OBSTF OFFInsulation flag INSU OFFProfile flag PRFG OFFP-line flag PLFG ONDrawing Level DLEV 0Frontface Pen FFPEN Pen 1Centreline Pen CLPN Pen 4Backface Pen BFPEN OFFObscured Pen OBPN OFFP-line Pen PLNP 5Member line Pen MLNP OFF

TUBEF, CLIN, PRFG, PLFG, PSYM, OBSTF and DLEV are standard PDMS displayrepresentation controls and are not described here. (See the PDMS DESIGN ReferenceManual for details.)If INSU is ON, Piping Component Insulation will be drawn using the frontface pen(FFPEN). The outline of the piping Components will be hidden by the insulation inhidden-line views. If insulation and Components are required to be displayed, twosimilar views (that use different Styles) will need to be defined and superimposed.The pen attributes allow different parts of chosen items to be drawn differently, and areused as follows:• Frontface Pen. In wireline VIEWs this attribute controls the pen to be used to

represent all edges. All edges are shown except for holes which will be drawn with adashed line of the same colour as the FFPN. Set directly, for example:

FFPEN 6 (or FFPN 6) Use pen 6 for the frontface

May be set to OFF to allow special effects.• Centreline Pen. This attribute controls the pen to be used for representing

centrelines. Also used for drawing LINE elements of Catalogue Components. Whendrawing pipework with TUBEF ON, CENTRELINE ON, the centreline will not beobscured by the piping Components. (Unlike FFPEN, it is not necessary tosuperimpose two VIEWs with different Styles.



DRAWI elements owned by EQUI, SUBE, STRU, SUBS, or PTRA will be drawn usingthe centreline pen of the STYL specified. For these DRAWIs the setting of the STYL’scentreline flag (CLFG) will be ignored even though the centreline pen is used; theLEVEL attribute should be used to control whether the DRAWI appears on the drawing.Set directly, e.g.

CLPN 2 - use pen 2 for centrelines.

• Backface Pen. In hidden line VIEWs, this attribute controls the pen to be used todraw the rear edges of items (set to OFF by default). Set directly, eg

BFPEN 3 (or BFPN 3) - use pen 3 for the backface

BFPEN would normally be set OFF for hidden line VIEWs, but if required can be usedto set the pen to be used for drawing the rear edges of items. This attribute has no effectin wireline views. See Figure 4-2 for an example of the use of the Backface Pen.

Figure 4-2 Use of Backface Pen (shown dotted)



Version 11.5

• Obscured Pen. In global hidden line VIEWs, this attribute controls the pen to beused to draw the front-facing edges of items that would otherwise be obscured byother objects (set to OFF by default). Set directly, eg

OBPEN 3 (or OBPN 3) - use pen 3 for obscured front facing edges

This attribute has no effect in wireline and local hidden line VIEWs. See Figure 4-3 foran example of the use of the Obscured Pen.

Figure 4-3 Use of the Obscured Pen (shown dotted)• P-line Pen. This attribute controls the pen to be used to draw p-lines. Set directly,

for example:PLNP 4 Use pen 4 for p-lines

PLNP may be set to OFF.• Member line Pen. This attribute controls the pen to be used to draw SCTN and

GENSEC member lines. Set directly, for example:MLNP 6 Use pen 6 for member lines

MLNP may be set to OFF.P-line pen and member line pen apply only to drawing steelwork Section elements. SeeSection 11 for a full discussion of of using DRAFT with structural steelwork.The pen settings control the colour and style of the lines drawn. See Section 18 for adescription of pens and linestyles.



4.2 Representation Rules

The Representation Ruleset owns a series of Representation Rules, each of whichcontains a reference to a different Representation Style. A Ruleset can therefore be usedto produce several graphical representations of the same VIEW. An example of thecommands for setting up a Ruleset is:

NEW RRST /RSET1 - create RulesetNEW RRUL /R11 - create RuleUSE /S2 FOR crit - set Style reference (STYF). /S2 must already exist;

crit= Design element name or selection criteriaWhen more than one Rule is created, the order of the command sequence is important.Consider the command sequences:

Sequence 1 Sequence 2NEW RRUL /R1 NEW RRUL /R1USE /S2 FOR ALL EQUIP USE /S2 FOR ALL NOZZNEW RRUL /R2 NEW RRUL /R2USE /S2 FOR ALL NOZZ USE /S1 FOR ALL EQUIP

Sequence 1 would result in Nozzles being drawn according to style /S1, sequence 2 wouldgive Nozzles in style /S2.You can also assign a style reference to an individual named Design element or a seriesof named elements, for example:

USE /S2 FOR /PUMP1-1 /VESS1

Note that the Design element must have a name: identifiers such as CE, FIRST EQUI,STRU 4 etc. cannot be used.Representation Rules can reference IDLIsts, using expressions if required. For example:

USE /STYLE1 FOR /LIST24 /LIST25

USE /STYLE2 FOR ALL IDLISTS WITH ( FUNC EQ 'STEAM' )

Once a Rule has been created, and a style set, the selection criteria can be changedwithout specifying the style by giving the command:

USE FOR crit

For example:USE FOR ALL BRAN WITH ( HBORE LE 80 )

Alternatively, the CRIT attribute can be set explicitly. For exampleCRIT ALL BRAN WITH ( HBORE LE 80 )

You can set up a rule to omit elements from a selection. For example, the followingRules (in the given order) will have the effect of drawing all Branches in Style S2 exceptsmall bore Branches, which will not be drawn at all:

NEW RRUL /SMALLBOREOMIT ALL BRAN WITH ( HBORE LE 80 AND TBORE LT 30 )



Version 11.5

NEW RRUL /BRANCHESUSE /S2 FOR ALL BRAN

Named elements can also be omitted. For example:OMIT /EQUIP99

The OMIT command sets the OMITFG attribute of the Rule, which automatically unsetsthe STYF of the Rule.DRAFT determines the style to use fr a particular element by scanning through the listof RRULs (in database order) until a selection criteria is matched. If DRAFT is unable tofind a relevant rule for a component the default style will be used. This is:

Tube OffCentreline OnProfile OffPline OnDrawing Level 0Ffpen 1Clpen 4Other pens Off

4.2.1 Selective Style Allocation

Style references may be applied selectively using PML expressions, for example:USE /S3 FOR ALL BRAN WITH (PSPE EQ /RF150 )USE /S4 FOR ALL BRAN WITH ((HBORE LE 50) OR (TBORE LE 50))USE /S5 FOR ALL BRAN WITH ((HBORE GT 80) AND (TBORE GT 80))USE /S6 FOR ALL BRAN WI ((PSPE EQ /RF200 ) AND ((HBOR GT 60) OR (TBOR GT60)))USE /S7 FOR ALL SCTN WI (CUTL GT 5000)USE /STYLE1 FOR ALL BRAN WI (ISPE EQ NULREF)

NOTE: For full details of using expressions in PDMS, see the VANTAGE PDMSDESIGN Reference Manual, Part 1 General Commands, or use the online helpand search for ‘‘expressions”.

The comparators available are: EQ, NE, LT, LE, GE, GT (although in some instancesonly EQ and NE are valid).• Each logical expression can be preceded by NOT, for example:

WI (PSPE EQ /RF300 AND NOT BUILT)

• The operands on either side of a comparator are interchangeable, for example:

WI (PSPE EQ /RF300 ) is equivalent to WI /RF300 EQ PSPEWI (ABORE GT 80) is equivalent to WI 80 LE ABORE

Note that it is possible to apply a selection criterion to a list of class types by enclosingthem in brackets, for example:

USE /ST1 FOR (ALL BRAN ALL SUBS) WI (ZONE EQ /ZONE.PIPES)



Without the brackets the selection criterion would only be applied to SUBS.Selection criteria should not be used unnecessarily. For example, if you wish to drawsmall-bore Branches in style /ST1 and the rest in style /ST2, it is only necessary to say:

USE /ST1 FOR ALL BRAN WI (HBOR LE 80 OR TBOR LE 80)USE /ST2 FOR ALL BRAN

As long as the criteria are defined in this order, all small-bore Branches will match thefirst criterion and the rest, having failed to match the first criterion, will match thesecond.

4.2.2 Local Rules

Local Rules may be set up as VIEW members in the same way as Library rules; theresulting graphical representation is determined as follows:• Local Rules always have priority over Rules within Rulesets in Libraries.• A Rule’s priority is determined by its position in the list; the higher in list the higher

its priority, but a Local Rule will still have a higher priority than the top RulesetRule.

This means that you should always place the more specific rules earlier in the list.

4.2.3 Setting the VIEW

Once the Rulesets and Styles have been set up, it is just a matter of setting the VIEWattribute RRSF to point to the Ruleset that you wish to use, and updating the design.

4.3 Automatic Hatching

Model faces created by section planes, and surfaces of specified Design primitives can behatched automatically by defining and applying Hatching Rules. The hatching iscarried out automatically as part of the Update Design process. For more information onSection planes see Section 1.The Hatching Rules (HRUL elements) define the faces to be hatched, and they referenceHatching Styles (HSTYL elements). Hatching Styles define the pens to be used todraw the hatching. Hatching Rules are stored in Hatching Rulesets (HRST elements).Hatching Rules and Rulesets are similar to Representation Rules and Rulesets.Hatching Styles and Rulesets are stored in RPLBs. Local Hatching Rules can be definedby creating HRULs owned directly by Views. The Local Hatching Rules directlyreference Hatching Styles (HSTYL).The hierarchy of database elements for hatching is similar to the Representation Rules,and allows you to impose company or project drawing standards.



Version 11.5

Hatched areas can be auto-blanked to allow annotation placed on top of them to belegible. See Section 2.2, Part 2, Drawing Annotation.

Figure 4-4 Hatching Rule Database Hierarchy

4.3.1 Hatching Rules

Each Hatching Rule references a Hatch Style element that defines the hatch pattern tobe applied. For each Hatch Rule you can specify:• Whether it applies to faces created by a section plane or to primitive surfaces.• The orientation of the faces to be considered for hatching. There are three options:

• All Directions, in which case the face will be hatched regardless of itsorientation.

• Perpendicular Direction, in which case the face will only be hatched if it isperpendicular to the viewing direction.

• Specified Direction, in which case the face will only be hatched if its normalmatches a specified value. The normal of a face is the vector perpendicular toit and pointing out of the solid primitive. Thus the normal of the uppermosthorizontal surface of a box is Up.

Library

VIEW

RPLB

HRUL

HSTYLHRST

HRUL

HRSF

HSTYF

HSTYF



4.3.2 Hatching Rules

The HRUL attributes, with their defaults, are as follows:Hatch Style Ref HSTYF reference to HSTYL, default nullFace Code FCODE Sectioned-FacesDirection Code DCODE All-DirectionsFace Normal NORM unsetSelection Criteria CRIT unset

Examples of setting attributes:HSTYF /HSTYL1

FCODE SECTionedfacesFCODE PRIMitivefaces

DCODE ALL DirectionsDCODE PERPendiculardirectionDCODE SPECifieddirection

NORM standard PDMS direction syntaxCRIT standard PDMS selection criteria syntax

As well as the usual NEW command, an HRUL can also be defined by:USE hstyl FOR criteria

which will set the HSTYF and CRIT attributes.

4.3.3 Which Elements can be Hatched

Significant elements (BRAN, EQUI, SUBS, FRMW, etc) are sectioned, not theirprimitives, and so a Hatch Rule that applies to Sectioned Faces must select onsignificant elements. If it selects on BOXes or VALVs (say) no hatching will be applied.For example, you could define three Hatching Rules for to a View to apply differenthatching patterns to concrete and steel items cut by a section plane, and a differenthatching pattern again to the top surfaces of panels representing an escape route.A Hatch Rule can only be applied to Sectioned Faces or Primitive Surfaces, not both.Only one Hatch Rule can be applied to a Design element. This means, for example, thatyou cannot hatch both types of face of a Design element, and it is not possible to hatchdifferently the three surfaces of a BOX element that are visible in an isometric View.

4.3.4 Hatching Styles

Each Hatching Style defines two pens, either of which may be set OFF. The Fill Pen(FPEN) defines the hatch pattern to be applied to the selected faces. The Outline pendefines the pen that is to be used to draw around the edges of the faces. For example, it



Version 11.5

is possible to emphasis an area by drawing a thick line around it without actuallyhatching it. For more information about pens and hatch-patterns see Section 18.The HSTYL attributes, with their defaults, are as follows:

Outline Pen OLPEN OffFill Pen FPEN Pen 1Pipe-end Symbol Flag PIPESYM TRUE

By default, when a length of implied tubing or a DUCT or STRT (ducting straight)element is cut and the resulting face is circular or rectangular, DRAFT will generate atypical sectioned symbol rather than just apply the hatch pattern to the face:

Figure 4-5 Typical Tubing ‘Sectioned Symbols’The PIPESYM attribute of Hatching Styles allows this functionality to be suppressedand replaced by normal hatching.

4.3.5 The Hatch Pattern

The hatch pattern is composed of either Solid Fill, or one or two sets of lines all the samecolour. The lines within a set are all parallel and equally spaced, and can only bestraight, solid, and of a single-pen thickness. Cross-hatching can be created using twosets of line that are not parallel. Double-line hatching can be created using two sets ofline that are parallel.The parameters that define each set of lines (that is, angle, separation, offset from sheetorigin) are absolute, that is, they are unaffected by factors such as Sheet size, Viewscale, or View orientation. For more information see Section 18.Note: Hatching in Isometric Views may not be entirely satisfactory. For example,

there is no way of altering the hatching parameters to suit the orientation of theface hatched, and so the faces created by a stepped section plane will all behatched at the same angle and separation for a given Design element. Thehatching of two connected faces will be continuous even though the faces willhave different orientations in 3D space.




4.4.1 Querying Rulesets and Styles

Q DESC - at Ruleset or RuleQ RRSF DESC - at VIEWQ STYF FOR /design_element identifier - at VIEW or Ruleset

The last example returns the Style used for the specified design element, irrespective ofthe element type specified at the RRUL. A list of design element identifiers may beentered, optionally separated by commas.

4.4.2 Querying Hatching Rulesets and Styles

The querying facilities are similar to those provided for RRULs. Thus at a HRUL:Q DESCription

will output a description for that HRUL with the format:USE hstyl FOR criteria

At a HRST:Q DESCription

will output an ordered list of descriptions – one for each of its HRULs.At a VIEW:

Q HRSF DESCriptionwill output an ordered list of descriptions starting with those of the HRULs it owns &then those of the HRST it references.At a VIEW or HRST:

Q HSTYF FOR design-idwill return the HRUL that is relevant for the specified design item. The <design-id>may be repeated if the HRULs for a list of design items are required.



Version 11.5

Summary of Commands

At Representation Rule . . .

USE stylename FOR crit

set drawing style for Design generic types, see above.

CRITeria crit set the CRIT attribute for the current rule

OMIT elements omits the elements specified, by name or type, which may be anexpression, from the representation

At Representation Style . . .

FFPN integer set pen number for drawing edges (modelled wireline VIEWs) orvisible(front face) edges (hidden-line VIEWs).

BFPN integer set pen number for drawing rear edges of items (no effect inmodelled wireline VIEWs).

OBPN integer set pen number for drawing front-facing edges of items that wouldOBPN OFF otherwise be obscured by other objects (global hidden-line VIEWs only).

CLPN integerCLPN OFF set pen number for drawing centrelines.

PLNP integerPLNP OFF set pen number for drawing p-lines

MLNP integerMLNP OFF set pen number for drawing member lines

PROFile ONPROFile OFF set profile flag

PLINes ONPLINes OFF set p-line flag



At Hatching Rule . . .

USE hstylename FOR critset hatching style for Design generic types, see above.

CRITeria crit set the CRIT attribute for the current HRUL.

FCODE SECTionedfacesSectioned faces will be hatched.

FCODE PRIMitivefacesPrimitive faces will be hatched.

DCODE ALLDirectionsAll faces will be hatched, regardless of direction

DCODE PERPendiculardirectionFaces perpendicular to the viewing direction will be hatched.

DCODE SPECifieddirectionFaces whose normals match the direction specified in the NORMattribute of the HRUL will be hatched. The normal of a face is thevector perpendicular to it and pointing out of the solid primitive.Thus the normal of the uppermost horizontal surface of a box isUp.

NORM direction Standard PDMS direction syntax

At Hatching Style . . .

OLPEN integer Set different pen number for drawing outline of selected faces.

OLPEN OFF Selected faces will not be outlined.

FPEN integer Set pen number for hatching selected faces.

PIPESYM TRUEPIPESYM FALSE Pipe end symbols (or HVAC duct end symbols) will be drawn

instead of hatching.

PIPESYM TRUEPIPESYM FALSE Pipe ends (or HVAC duct ends) will be hatched.


5 Section Planes

5.1 Introduction

DRAFT gives you the ability to construct sections through specified Design items, theresults of which can be displayed at VIEW level. All Planes are database items and cantherefore be used with more than one VIEW. There are three types of Plane elementwhich can be used to define four types of section plane, namely:• A Perpendicular Flat Plane passes through a specified point in the 3D design,

being oriented so as to be perpendicular to the current VIEW direction. The VIEWcontents which are discarded can be on either side of the plane. This type of planewould be used as either a section or a backing plane.

• A Flat Plane is similar to a perpendicular flat plane, but can be oriented to allowviews of the section from any angle.

• A Stepped Plane is a folded plane (i.e. a series of non-intersecting straight linespans) that extends to infinity in both directions along a specified axis. The shape isdefined by a series of points, the ends of the plane also extending to infinity. Thesimplest form of stepped plane would be defined by two points and would beequivalent to a Flat Plane. Any VIEW direction can be used and the VIEW contentson either side can be discarded. Note that the two end spans must not intersect eachother or an inner span. A stepped plane is illustrated in Figure 5-1.

• An Enclosed Plane. This is a particular form of stepped plane in which the firstand last points that define it coincide to form a ‘tube’ which is infinitely long alongits axis. Any VIEW direction can be used and either the inside or outside of the‘tube’ can be removed. An enclosed plane is illustrated in Figure 5-2.

Section Planes


Version 11.5

Figure 5-1 Stepped Plane

Figure 5-2 Enclosed Plane

All Planes have a standard ‘retain’ and ‘discard’ side, depending on how the Plane isdefined in the database. The Plane can be used in either ‘standard’ or ‘reverse’ modewhich effectively switches the Plane’s action without altering its definition. This allowsthe Plane to be used in different VIEWs both as a section or backing plane. Planes canonly be used with modelled VIEWs, that is not with basic wireline views.

Section Planes


5.2 Creating and Using Planes

All Planes are created and held within a Library structure, and are owned by a PlanesLibrary (PLLB) element. The part of the DRAFT database hierarchy relating to Planesis shown in Figure 5-3.

PLLB

FPLA SPLA

WPOS

LIBY

PLRF

VSEC

PPLA

VIEW

Figure 5-3 Database Hierarchy - Plane ElementsTo use a plane to produce a sectioned VIEW, you need to create a View Section (VSEC)element under a VIEW; VSEC attributes are:

• PLRF (Plane Reference) - the name of the plane to be used.

• IDLN - an Id List name for the section to operate on. If left undefined this willdefault to the World (i.e. /*). This means that all elements in the VIEW’s Id List willbe sectioned. A single Design item name can be used.

• PMOD - the mode in which the plane will be used to section the VIEW, i.e. the sideto be retained or discarded. The default is STANDARD, which is as the plane is set-up. REVERSE switches the side to be retained or discarded. OFF switches the planeoff.

• CLMO (centreline mode) By default this is set to ON, which has no effect onfunctionality. If it is set to OFF then the section will not be applied to line elementsof Piping Components. This allows you to remove Components and tubing by asection plane, but leave the centreline to show the path of the Branch. All other non-

Section Planes


Version 11.5

solid primitives are sectioned normally and are unaffected by the value of attributeCLMO.

• SMOD (a View attribute) - the section mode attribute, which defines how smallparts of piping components and implied tube that are cut by the front and backsectioning planes will be treated. This attribute only affects piping components andimplied tube in orthogonal, non-perspective Views.

If SMOD is set to STANDARD (the default), all elements will be sectioned in theusual way. If SMOD is set to OMIT FRACtional PCOMonents, the followingfunctionality will apply when the design graphics of the View are updated:

• All piping components whose origins (P0) lie outside the front and backsectioning planes will be removed from the drawlist. All other pipingcomponents will be drawn completely, even if they are cut by one of thesectioning planes.

• All lengths of implied tube that lie outside the front and back sectioning planeswill be removed from the drawlist. In this case the test for lying outside thesectioning planes will be based on the vector Parrive -> Pleave, and not on theactual volume occupied by the length of tube. Lengths of tube that lie within orcross the front or back sectioning planes will be drawn completely.

Where an IDList is defined by a set of piping components (for example, ADD/VALVE1 /VALVE2 /VALVE3) the functionality will not apply.The names of the items omitted can be output by the command

SMODE MESSAGES ONbut this will include all those piping components in the View’s IDList that falloutside the clipping box and would therefore not be drawn in any case.

Several VSEC elements can be used to produce as complex a section as you require, butthe larger the number the slower the operation will be.After setting up the VSEC it is just a matter of updating the design (with an UPDATEDESIGN command), remembering that sectioning will only take place if the VIEWattribute VTYPE is set for Local , Global or Universal hidden line removal, or Modelledwireline.

5.2.1 Perpendicular Plane (PPLA)

A PPLA has a single attribute POS which defines the 3D point through which the planepasses, the retained side being that towards which the VIEW direction points. Theorientation of the plane will always be perpendicular to the direction that you specify forthe VIEW. The basic command syntax for creating a PPLA is:

NEW PPLA- create a PPLA

Section Planes


POS @- set POS attribute to a 3D Design position or

POS ID @- set POS attribute to the 3D Design position of a Design element

POS IDP @- set POS attribute to the 3D Design position of a Design element p- point

NOTE: You can only input a 3D Design position on orthogonal VIEWs; the lookingdirection of such a VIEW will determine which coordinate is returned as zero.For example, a plan view will return U0 which you may need to alter to give therequired section.

Figure 5-4 illustrates the use of a perpendicular Plane, positioned at the pump coupling.

Section Planes


Version 11.5

Figure 5-4 Use of the Perpendicular Plane (PPLA)

Section Planes


5.2.2 Flat Plane (FPLA)

A FPLA has an attribute POS which defines a 3D point through which the plane passes,and an attribute NORM which defines the vector normal to the plane. The retained sideis that towards which the normal points. The basic command syntax for defining anFPLA is:

NEW FPLAPOS @NORM direction

The NORM direction can be any standard ‘PDMS direction’, e.g. N45W, ISO2, or can beby reference to a Design element p-point, in which case the result will be stored as a 3Dvector and the reference will be lost. Figure 5-5 illustrates the use of a flat Plane,positioned at the pump coupling and with a NORM direction of N45W.

Figure 5-5 Use of the Flat Plane (FPLA)

Section Planes


Version 11.5

5.2.3 Stepped Plane (SPLA)

A Stepped Plane can be ‘Open’ or ‘Closed’, the type being determined by the setting ofthe SPLA’s GTYP attribute. The default is GTYP OPEN. GTYP CLOSED defines anclosed Stepped Plane or Enclosed Plane. The only other attribute is DIR, whichdetermines the Plane’s extrusion direction.An SPLA owns WPOS elements, one per plane ‘step’, whose sole attribute is POS, thestep’s 3D Design position. Specifying a 3D position automatically creates a WPOSelement and sets the POS attribute.The order in which the points are defined plus the direction of the plane’s extrusiondetermines which side of the plane is retained. A ‘handy’ rule for determining the‘retain’ side (with PMODE STANDARD) is to hold the thumb, index finger and middlefinger of the left hand mutually at right angles; if the thumb points in the extrusiondirection and the index finger points towards the last step point then the middle fingerwill point towards the retain side - see Figure 5-6. A similar ‘rule’ applies for EnclosedPlanes.

Figure 5-6 Defining a Stepped Plane

Section Planes


The SPLA shown in Figure 5-6 would be created by a sequence of commands such as:NEW SPLADIR UGTYP OPENSTEP @ @ @ @ - Define a series of points through which an SPLA will be

constructedThe STEP command will invoke the cursor which will enable 3D positions or Design p-points to be identified, automatically creating WPOS elements. DRAFT imposes no limiton the number of steps, but in practice only four points can be defined by a single STEPcommand due to command line length restrictions. If a plane with more than four stepsis required, further STEP commands will enable additional points to be appended to theexisting member list. The minimum number of points required to define an SPLA is 2,which will have the effect of a Flat Plane.WPOS elements can be created explicitly by command sequences such as:

NEW WPOSPOS E120500 N236785 U0

If this syntax is used you must leave the list of WPOS elements in the correct order forthe SPLA to function. Figure 5-7 illustrates some examples of Stepped Planes.

Figure 5-7 Use of the Stepped Plane (SPLA)

Section Planes


Version 11.5

(The pictures in the left half of Figure 5-7 illustrate the use of the SKETCH PLANEfacility - see Section 5.4.)If the STEP command is used then once a series of points are entered a check is made toensure correct SPLANE definition; if satisfactory then a message of the form:

Splane /name is satisfactory

is output. If the plane is not satisfactory then the message will indicate what theproblem is. Generally, an SPLA will be incorrect if parts of the plane overlap even ifextruded to infinity at the ends; Figure 5-8 illustrates this situation.

.

Figure 5-8 Plane ErrorsIf you have defined a plane that is unsatisfactory then it will have to be manipulated. Inexamples A and B, the plane can be corrected by either reordering or repositioning oneof the points or by adding a new point. Alternatively the plane could be made anenclosing type. In example C the plane can only be corrected by either reordering thepoints or by repositioning one or more of them. How to move points is discussed in thenext Section.

5.3 Altering Planes

If you wish to change which side of a plane is retained or discarded, you can do this byreversing the plane’s orientation if it is an FPLA and by changing the DIR or reorderingthe WPOS points for a SPLA. The CHANGE ACTION command, for example:

Section Planes


CHANGE ACTION /PL2-5 - alter named Plane

CHANGE ACTION - alter current (Plane) element

will do this for you by altering either the DIR or NORM attributes depending on theplane type. A PPLA cannot have its action reversed since it does not have anorientation.Of course, changing the PMOD of the appropriate VSEC element would have the sameapparent effect as a CHANGE ACTION operation in this case, but whereas the formeroperation only changes the view section representation, the latter operation changes thePlane database element itself.The CHANGE ACTION command is valid at any Plane element, and at WPOS elementlevel in the case of a Stepped Plane.If you require a plane point to be moved, i.e. either a POS attribute for a PPLA or anFPLA, and the POS attribute of a WPOS element for an SPLA, the BY command can beused. For example:

BY N500

BY @ - Move by the difference between two cursor hits on the sameorthogonal VIEW

For an SPLA, the BY command will move the complete plane, i.e. the POS attribute willbe changed for all of the SPLA’s member WPOS elements.You can delete individual WPOS elements in the normal way but you can also deleteseveral at once using the command:

DELETE STEP number numberwhere the number arguments define the list position range of the points to be deleted.

5.4 Plane Querying

Once a plane has been created, it can be queried in the following ways:Q DESC - at Plane level (or at WPOS elements)

The plane referred to by the PLRF attribute of the VSEC can be queried by:Q PLRF DESC - at VSEC level

It is possible to query whether a given 3D point is on the retained or discarded side byusing the following:

Q SIDE @ - at plane levelQ SIDE /plane_identifier @ - from anywhereQ SIDE /plane_identifier E value N value U value - from anywhere

Section Planes


Version 11.5

In the latter case, only two coordinates need to be given dependent on which orthogonalview direction you are working on, e.g. for a Plan view only the Easting and Northingare required.You can make any plane visible in a suitable VIEW (i.e. one that is orthogonal to theaxis of the plane) by using the following commands:

SKETCH PLANE IN /view_identifier - at Plane level

SKETCH PLANE /plane_identifier - at VIEW level

SKETCH PLANE /plane_identifier IN /view_identifier - from anywhere

Figure 5-7 shows the SKETCH PLANE command in use. Once the plane has beenSketched then it will always be visible, irrespective of VIEW or area view manipulation.Only one plane at a time can be sketched. A plane can be erased by either of thefollowing commands:

ERASE PLANE - at VIEW level

ERASE PLANE IN /view_name - from anywhere

Note that the sketch facility is only a ‘drafting aid’ and is not part of the VIEWannotation. Any change made to a sketched Plane will not result in a correspondingchange to the displayed sketch - another SKETCH PLANE command will be needed.

Section Planes


Summary of Commands

Setting Plane Position . . .

POS @ - Set POS attribute to a 3D Design position

POS IDP @ - Set POS attribute to the 3D Design position of a design element p-point

NORM direction - Set an FPLA normal direction

For SPLAs . . .

DIR value - Set extrusion direction Use any PDMS direction syntax e.g. N45E

GTYP OPEN or CLOSED- Set GTYP. OPEN will define a stepped plane, CLOSED will define an enclosed plane

STEP @ @ @ . . . . - Define a series of points through which an SPLA will be constructed

Creating Section Plane points directly . . .

NEW WPOS - create WPOS element

POS E value N value U valueset position attribute

Switching retain/discard side . . .

CHANGE ACTION /plane gid- reverse the action of an FPLA or SPLA by reversing the direction of the NORM or DIR attributes respectively

Section Planes


Version 11.5

Moving Section Plane points . . .

BY N500 - Move the point in 3D Design World coordinates explicitly

BY @ - Move by the difference between two cursor hits on the same orthogonal view

Editing Section Plane points . . .

DELETE STEP value value- where value is the list position of the point to be deleted

Setting up the VIEW to accept Section Planes . . .

NEW VSEC - Create a VIEW Section element under a Layer

PLRF name - The reference name of the plane to be used

IDLN name - An Id list name for the section to operate on. If left undefined will default to the Id list specified by the VIEW. The Id list can only have Added items, any Removes will be ignored. A single Design item name can also be used.

PMOD [STANdard | REVerse | OFF]The Mode in which the plane will be used to section the view, i.e.which side will be retained or discarded. The default isSTANDARD which is as the plane is set up, or REVERSE whichswitches which side is retained or discarded. For a SPLA orFPLAthis has the same result as using the CHANGE ACTIONScommand.

Section Planes


Querying . . .Planes

Q DESC - At Plane level

Q PLRF DESC - At VSEC level Retained/Discarded side

Q SIDE @ - At plane level

Q SIDE /plane_name @- From anywhere

Q SIDE /plane_ name E value N value U value- From anywhere

Plane sketching . . .

SKETCH PLANE IN /view name- At Plane level

SKETCH PLANE /plane name- At VIEW level

SKETCH PLANE /plane name IN /view name- From anywhere

Plane erasing . . .

ERASE PLANE - At VIEW level

ERASE PLANE IN /view name- From anywhere


6 Using the Cursor

6.1 Identifying Elements Using the CursorWith many DRAFT commands, you can use the cursor to identify an element in thegraphics window by using the ID command followed by @:

ID @At this point, picking an element with the cursor will select and identify the displayedelement (the lowest-level element, i.e. a primitive, will be picked).Elements down to and including Design primitives or Catalogue piping components (e.g.FLANGES) may be accessed. Dimensions, Dimension Points and Labels may also beaccessed in this way.Other cursor identify commands are:

ID element_type @ - element_type is any Design, Catalogue or Drawing element (e.g. EQUI, SHEE)

ID VALV @ - select and identify valveID VALV VTWA @ - select and identify valve or VTWAID NOZZ @ - select and identify nozzle

You can specify up to 20 element types. For example:

ID VALV VFWA VTWA @See Sections 8, 9 and 14 for ID commands relating to Dimensions, Labels and 2Ddrafting respectively.The following command can only be used as part of a command:

IDP @ - select and identify p-point or structural node (PNOD or SNOD)

For example, ON IDP @.

You can restrict items picked to be either Design database elements or Draft databaseelements by using the commands:

ID DESEL @ID PADEL @ID DRAEL @

Picking an element with the cursor will make the item the current element (i.e. thecurrent position in the database will move to that item). If you select a Design element(e.g. a Cylinder primitive in a vessel) you will move to the Design database; if you selecta Drawing element (e.g. the edge of a Sheet) you will move to that element within theDRAFT database.

Using the Cursor


Version 11.5

6.2 Picking P-points and Nodes

P-points and structural node points (that is, PNODs and SNODs) may be picked by thecursor. The main uses are• for positioning annotation at a particular point on a primitive, for example the end

of a cylinder axis

• for identifying primitives below EQUI, STRU or SUBS elements.

A p-point or node may be identified usingQ IDP @

In addition, the p-point may be directly selected, for exampleON IDP @ - attach annotation to specified p-point or node

To identify a p-point, move the cursor across the VIEW display with the left-hand mousebutton held down (the cursor changes its appearance); as the cursor moves across (bydefault) a significant element its p-points will become visible.Moving the cursor over a p-point (with the left-hand mouse button still depressed) willcause the p-point identifier to be displayed in the Status Form; also, the appearance ofthe cursor will change.Selecting a p-point is achieved by releasing the mouse button with the cursor over therequired point. The identifier, direction and position of the point will appear in thePDMS DRAFT Command Input & Output form and the p-point display markers willdisappear.Releasing the left-hand mouse button without selecting a p-point will leave the currentset of p-points visible; you will be able to zoom or pan the view, or quit out of thecommand line by clicking on Cancel on the Status Form.Whether the p-points for the last significant element identified or for the last primitiveidentified are made visible is controlled by the PPOINTS command:

PPOINTS SIG - significant element p-points made visiblePPOINTS PRIM - Design primitive p-points made visibleQ PPOINTS - query current setting

In the latter case, identifying a length of implied tube will cause only the Branches Headand Tail p-points to be made visible. Lines generated by a section plane (see Section 5)are assigned to the significant element and not to the primitive sectioned; picking on oneof these lines will cause all the p-points of the significant element to be made visible -even when in ‘Design primitives’ mode. P-points which lie outside the view rectangle willnot be shown.

Using the Cursor


6.2.1 P-point Style

P-points will be drawn for Design elements in all VIEW types. They are shown asmarkers. You can change the marker type and scale, see Section 8.4. You can changethe colour using the SETFEEDBACK command, see Section 8.6.3.

6.3 Picking Structural Elements and P-lines

A p-line (or member line) may be identified by cursor hit using the commands:

IDPL @ - select and identify p-line

IDPE/ND @ - select and identify p-line start or endThis will return syntax to the command line in the following form:

PPLINE word OF element_identifier

The IDPE/ND command will generate text such as:Pline RTOS of /SCTN-98 startPline MEML of /SCTN-99 end

depending how far along the Pline the cursor hit was made. This may be used, forexample, to position annotation at the start or end points of Plines or to obtain the 3Dcoordinates of these points. For example:

NEW GLAB ON IDPE @will position a GLAB on the identified Pline at either its start or endpoint.

Q IDPE @will return the ENU position of the start or end point of the identifiedPline.

This syntax is used for querying and to identify a p-line for direction (note that it maynot appear at the beginning of a command line).The command

IDPDistance @

will return the proportional distance along the identified p-line. For example a GLABcan be positioned by either of:

ON IDPL @ON IDPD @

Examples of text returned by these commands could be (respectively):ON PPLINE BOS OF /SCTN.PN1_PN5

ON PPLINE BOS OF /SCTN.PN1_PN5 PROP 0.65

In the former case the default value for proportional distance will be used.

Using the Cursor


Version 11.5

6.4 Querying Position Data

There are two query commands which enable you to convert between 2D Sheet positionsand 3D design data positions.To derive a 3D position from 2D data use:

Q ENUPOSITION OF sheet_position (at/below a VIEW)where sheet_position is a position on the Sheet. This position (which must be within theVIEW rectangle) may be specified by cursor. This command returns the back-projectionof this position at Z=0 into the 3D world coordinate system of the current or specifiedVIEW, for example:

W 15500 N 10020 U 0

The specified VIEW must be axonometric without perspective.To derive a 2D position from 3D data use:

Q SHPOSITION OF position (at/below a VIEW)where position may be a 3D point or p-point, explicit p-point reference, origin of a namedelement, or an explicit 3D coordinate. This position or item may be specified by cursor.This command returns the projection of the explicit or implied 3D position onto theSheet for the current VIEW. For example,

X 574 Y 200

As with the ENUPOS query command, the specified VIEW must be axonometric withoutperspective and the specified position must lie within the VIEW rectangle.You can query the 3D origin in World coordinates of any Design element using thecommand:

Q IDORI @Q IDORI sheet_position (at/below a VIEW)

The response will be of the form:ID =123/456 ORIGIN W 0000mm N 0000mm U 0000mm

6.5 Snapping 2D Points to a Grid

Cursor commands which request 2D points will be rounded to the nearest point on theSNAP grid (if on). The grid is defined by the SNAP command, for example:

SNAP ON - turn the snap grid on

SNAP OFF - turn the snap grid off (the default)

SNAP ON 10 - define a square grid, 10mm in both X and Y directions

SNAP ON SPACING X25 Y40 - define a rectangular grid

Using the Cursor


When the SNAP grid is ON, all 2D cursor hits (including the BY @ command) will besnapped onto the nearest grid point. This does not affect graphics picking or pseudo-3Dcursor hits. Snapping only applies to cursor-generated positions; positions enteredexplicitly from the keyboard or via a macro are not snapped. Cursor hits will be snappedon any picture, whether or not the visible grid (see VGRID command below) isdisplayed.By default, the SNAP grid origin is positioned at the bottom left-hand corner of theSheet, and is drawn parallel to the X, Y axes of the Sheet. This origin may be changedby commands such as

SNAP AT X100 Y100 - define snap origin explicitly

SNAP AT @ - define snap origin with cursor

SNAP settings apply to all Sheets (and Symbol Libraries, Overlay Sheets etc) whenSNAP is ON. The initial setting (on entry to DRAFT) is a square grid at the Sheetorigin, with snapping switched off, i.e.

SNAP OFF AT X 0mm Y 0mm SPACING X 25mm Y 25mm

If the current PDMS units on module entry are INCH or FINCH, the initial SNAPspacing is one inch square.The snap grid may be queried using the command:

Q SNAP

The same information will also be output to file by a RECREATE DISPLAY command.Visible GridsThe snap grid is invisible unless it is turned on by the command

VGRID ON

Visible grids are not output to plotfiles.The VGRID command uses the current settings of the SNAP grid. A visible grid will beoutput on the current Sheet using some multiple (default 1) of the current SNAP grid.An element identifier may be specified as part of the command, for example:

VGRID /VIEW1-2 ON

This command would turn the visible grid on for the picture element (i.e. the SHEE,LALB, BACK, OVER, ISOLB or SYLB) owning the specified element.The visible grid is not maintained with changes in SNAP settings, so it is advisable toreset the grid (with another VGRID ON command) if the SNAP settings are changed.The spacing of the visible grid may be changed by commands such as

VGRID SNAP 2 - change visible grid spacing to twice that of snap grid

This command would give a less-cluttered grid display on the drawing. The defaultsetting may be returned to by giving the command

VGRID SNAP

Using the Cursor


Version 11.5

The following would cause a visible grid to be erased from the current Sheet (or aspecified Sheet), where sheet identifier identifies a picture element or an ownedelement.:

VGRID [sheet identifier] OFFERASE AIDS [IN sheet identifier]ERASE VGRID [IN sheet identifier]

The following causes all visible grids to be erased:Module switchingEntry to MDB mode

The snap multiple of the visible grid may be queried using the command:Q VGRID

Details of the VGRID snap multiple will also be output to file by a RECREATE DISPLAYcommand.It is also possible to query whether a specified Sheet currently has a visible griddisplayed, using

Q VGRID sheet_identifier

6.6 Highlighting Displayed Elements

Displayed elements can be highlighted (flashed) by using the HIGHLIGHT command. Theelements concerned may be Design elements (from significant element downwards,including implied Tubing and Rodding) or DRAFT annotation elements (i.e. Layers,Dimensions, Labels, 2D Drafting primitives). Overlay (OLAY) elements may also behighlighted. For example:

HIGHLIGHTHighlight current annotation element in all area views in which itappears

HIGHLIGHT IN /VIEW1-1Highlight current element (design or notation) in named VIEW

HIG IN ID VIEW @Highlight current element in cursor-identified VIEW

HIG /1501B IN ID VIEW @Highlight named design element in cursor-identified VIEW

HIG IARRIVE TUBE OF /VALVE1 IN /VIEW4HIG ILEAVE TUBE OF CE IN /PLAN_VIEWHIG HEAD TUBE OF /BRAN99 IN CEHIG TAIL TUBE OF CE IN /E_ELEVATION

Example commandsfor highlightingimplied tubing

Using the Cursor


HIG IN _f1_v1Highlight current element in named area view

HIG /1501BHighlight named Design element in all area views in which it appears

HIG /1501B IN _f1_v1Highlight named element in named area view only

Elements may also be highlighted simply by passing the cursor over them in the displaywith the left-hand button held down.NOTE: For the permanent highlighting of 2D Drafting primitives, see the ENHANCE

command in Section 9.4.4, Part 2, Drawing Annotation.

Using the Cursor


Version 11.5

Summary of Commands

Cursor Identification/Selection . . .

ID @ - select and identify any displayed element

ID element_type @ - select and identify any Design, Drawing or Catalogue element(e.g. EQUI, SHEE, PJOIN)

ID VALV @ - select and identify valve

ID VALV VTWA @ - select and identify valve or VTWA

ID BEND ELBOW @ - select and identify bends or elbows

ON IDP @ - attach annotation to specified p-point

ON IDPL @ - attach annotation to specified p-line

ID NOZZ @ - identify a Nozzle

The following can only be used as part of a command. For example, ON IDP @:

IDP @ - select and identify p-point

IDPL @ - select and identify p-line

IDPE/ND @ - select and identify p-line start or end

ID DESEL @ - select and identify any Design element

ID PADEL @ID DRAEL @ - select and identify any Draft element

Querying . . .

Q ENUPOSition OF sheet_positionderives a 3D position from 2D data

Q SHPOsition OF positionderives a 2D position from 3D data

You can query the 3D origin in World coordinates of any Design element using:

Q IDORI @Q IDORI sheet_position

(at/below a VIEW) returns the 3D origin in World coordinates of aDesign element

Using the Cursor


P-point Visibility . . .

PPOINTS SIG - significant element p-points made visible

PPOINTS PRIM - Design primitive p-points made visible

Highlighting Elements...

HIGHLIGHT - highlight current element in all area views in which it appears

HIG IN _f1_v1 - highlight current element in named area view

HIG /1501B - highlight named Design element in all area views in which it appears

HIG /1501B IN _f1_v1- highlight named element in named area view only

HIG /1501B IN ID VIEW @- highlight named Design element in VIEW picked bycursor

Snapping 2D Points to a Grid...

SNAP ON - turn snap grid on

SNAP ON 10 - define a square snap grid, 10mm in both X and Y directions

SNAP ON SPACING X25 Y40- define a rectangular snap grid

SNAP AT X100 Y100 - define snap grid origin explicitly

SNAP AT @ - define snap grid origin with cursor

VGRID ON - turn visible grid on

VGRID SNAP integer- change visible grid spacing to integer times that of snapgrid

VGRID SNAP - return to default visible grid spacing

Q SNAP - query snap grid

Q VGRI - query visible grid snap multiple


7 Plotting and Drawing Output

At any time during the drawing process, you can generate a plotfile that can consist of asingle Sheet, View or the contents of an Area View.

7.1 General

Plotfiles are produced by the PLOT command, which takes the following alternativeforms:

PLOT uuname filename [papersize] [OVERWRITE]

PLOT /sheet_name /filename [papersize] [OVERWRITE]

PLOT SHEE FILE /filename [papersize] [OVERWRITE]

PLOT VIEW FILE /filename [papersize] [OVERWRITE]

For example:PLOT /SHEET1 /SH1.PLTPLOT VIEW FILE /VW1.PLT A3

If the paper size is not specified then it will be taken as the same as the item beingplotted. Existing plotfiles will not be overwritten unless the OVERWRITE option is used.There are three additional options which may be specified between papersize andOVERWRITE:• CUTMARKS. By default the rectangular limit of the plotfile will be shown; this can

be suppressed by CUTMARKS OFF.

• The BORDER value option will cause a border to be left within the specified papersize. The image size of the item being plotted will be reduced accordingly.

• The FRAME option causes a frame to be drawn around the image; FRAME can onlybe used in concert with the BORDER option and marks the inside edge of theborder. It does not control the frame around the edge of the plotfile (see CUTMARKSabove).

An example of a PLOT command using its entire syntax is:PLOT SHEE FILE /S3.PLT A1 CUT OFF BORD 25 FRAME OVER

If required, plotfile pen definitions can be made different from those on the screen.Hence a line which appears as thin, solid, red on the screen could be made thick, dashed,black on plotfiles. See Section 8.6.2.

Plotting and Drawing Output


Version 11.5

You can query the size of a plotfile using the command:Query PLOTFile name SIZE

The response will be the size rectangle of the plot.

7.2 Standard DXF Output

7.2.1 Creating the DXF File

DXF format plotfiles (for use in AutoCAD) can be generated in a similar way to PDMSplotfiles simply by adding DXF to the command. For example:

PLOT SHEE DXF /SHEET1.DXFPLOT /SHT1/V1 DXF /VIEW1.DXF A3 OVER

It is recommended that the CUTMARKS OFF option be used when generating DXF files.

7.2.2 DXF File Contents

The DXF file created has a brief header section, followed by the TABLES section, whichdefines text styles and line types, and the ENTITIES section, which contains thedrawing data. The DXF BLOCK section is not used.The HEADER section contains two comments, giving file creator's name and thetime/date of creation. The only other variables set are $LIMMIN and $LIMMAX (thelimits of the drawing Sheet), $LTSCALE and $DIMSCALE. See also Section 7.2.3.The TABLES section defines all required text styles and line types. Two sets of textstyles are available corresponding to horizontal and vertical text (paths Right andDown), and both assume the existence of font files fnnnnnnnnnn (where nnnnnnnnnndenotes a ten-digit number) which correspond to the fonts used in a DRAFT session. Theline types are the standard DRAFT predefined set; they have been given names forAutoCAD use which are the DRAFT names prefixed by ‘GT’, e.g. GTSOLID, GTDOT etc.• Lines are passed as POLYLINE entities consisting of two or more points. The

available linestyles (with the names prefixed by ‘GT’) are illustrated in Figure .• Pen thicknesses are available. See Section 8.3.1.• Arcs/Circles are currently passed as POLYLINE entities with bulge factors.• All text strings are passed as TEXT entities in the appropriate font. For example,

text in Font 21 is output in style HTX21. The corresponding set of font files isdefined in the TABLES section of the DXF file. Text height and shear aresupported. All text is justified to the bottom-left corner of the text string. Note thatnon-zero character spacing is not supported in DXF output.

AutoCAD font files are provided as part of the AutoDRAFT software. Instructionsfor installing these can be found in the VANTAGE PDMS Installation Guide.



• Layers are assigned to entities according to their colour definition within DRAFT.These layers are named GT_n , where n is a number that corresponds to a PDMScolour.

• Colours are maintained according to Layer (i.e. BYLAYER in AutoCAD). Notethat the Layer colour for all DRAFT layers is white.

The ENTITIES section then follows, and is normally closed by the standard AutoCADEOF.

7.2.3 File Header Options

DXF files may have full AutoCAD headers, and Z-coordinates in the ENTITIES section.Example commands are:

PLOT SHEE DXF /SHEET1.DXF ACAD ZCOOR- include AutoCAD headers and Z-coordinates

PLOT SHEE DXF /SHEET1.DXF CADC ZCOOR- as above, but use Cadcentre header

If no header type is specified, the brief Cadcentre header is assumed. If the ACAD optionis used, then the DXF file produced will contain a header which is defined in fileacadxf.hdr in the PDMS executable directory (as defined by global variablePDMSEXE).File acadxf.hdr must contain, as a minimum, the following:• HEADER section• TABLES section• BLOCK section (optional)• ENTITIES section (optional) -UnterminatedIf the ZCOORD option is used, the DXF file produced will contain Z-coordinates of value0.000 (i.e. code 30 entries) in the $EXTMIN and $EXTMAX parameters in the headersection, and in polyline vertices and TEXT entities.

7.2.4 Encoding of Multi-Byte Characters

Multi-byte characters (e.g. Japanese) may be encoded in the DXF file in one of twoformats, namely Extended UNIX Code (EUC) and Shift-JIS. The format required willdepend upon the machine for which the DXF file is intended. The format should bespecified after the header and Z-coordinate requirements. For example:

PLOT SHEE DXF /SHEET1.DXF ACAD ZCOORD EUCPLOT SHEE DXF /SHEET1.DXF CADC ZCOORD SHI/FTJIS

If no encoding format is specified, EUC will be assumed. These options will have noeffect if only single-byte characters are output.

All terminated by anENDSEC keyword



Version 11.5

7.2.5 Scaling

The output written to the DXF file can be scaled using the SCALEUP command option. Ifrequired, the scaling value should be specified after the Z coordinate and characterencoding requirements. For example:

PLOT SHEE DXF /SHEET.DXF ACAD ZCOORD EUC SCALEUP 100

This will cause all values in the file to be increased by 100. Factors such as paper size,line thickness and character height will all be affected. This option allows the effects ofVIEW scaling to be reversed to some extent.

7.3 Configurable DXF Output

7.3.1 Configuration Datasets

It is possible to control the format of DXF output using configuration datasets. Theconfiguration dataset controls how the PDMS information is to be mapped into DXFformat. It does the following:• Controls how DRAFT graphics are to be grouped as DXF Block and Group

definitions.• Enables PDMS elements to be assigned to DXF layers.• Maps fonts, colours and linestyles between DRAFT and DXF.• Allows PDMS attribute information to be exported from DRAFT as DXF Block

attributes.The configurable DXF facility uses ‘loadable image’ (LI) applications, usable at Sheetlevel. The DXF export application can be executed using the LIEXEC command (whichalso loads the application if it has not already been loaded).The following example command uses the configuration data set ’MyConfigData’ tocontrol the export of DXF information:

LIEXEC /Draft_DXF_LI ’DXFOUTR13’ ConfigData ’MyConfigData’

Here ’DXFOUTR13’ is an application feature. At the current release of PDMS,DXFOUTR13 for producing AutoCAD Release 13 .DXF output is the only supportedfeature.This will create a DXF file with a name and format defined in the specified dataset forthe current picture element (e.g. SHEE, SYLB, etc.). Before giving the above command,the configuration dataset must have been defined in DRAFT by typing in theconfiguration data at the command line or by reading in a predefined macro file.Three example macro files are provided:default_dxf.mac Defines the default configuration settings.



full_dxf.mac Defines a sample set of configuration settings to produce fully -blocked, grouped and layered DXF files closely mapped to theDRAFT Sheet exported. Note that blocking commands for Designgraphics in this file are only intended as an example, and mayrequire modification to suit your own requirements.

graphics_dxf.mac Defines a configuration for graphics-only DXF files, minimal insize, which can be imported into systems which do not support fullAutoCAD Release 13 DXF file format. This provides compatibilitywith AutoCAD Release 12.

Other commands related to this facility are:LILIST Lists features of application(s) loaded by LILOAD/LIEXEC.DLICON Defines a named set of configuration options. For example:

DLICONconfiguration optionsEXIT

A DRAFT Configuration Dataset is made up of a series of switches and Blocking rules.The configuration options will contain the BLOCK and SWITCH syntax which controlthe content of the DXF file produced. See Section 7.3.2 for a full list of the switches andtheir permissible and default values.For example:

SWITCH GroupGLAB ONGroup GLABs into DXF groups

SWITCH HeaderFileName 'header.dxf'Specify the DXF header file name

The switch names are case-independent, but are shown as mixed case here to aidlegibility.Standard PDMS selection syntax is used to define Blocking Rules. These specify howPDMS design elements are to be organised into DXF Blocks. PDMS attributes can beincluded in block definitions. For example:BLOCK ALL STRU, INCLUDE NAME

BLOCK ALL BRAN WITH ( HBOR GE 100 OR TBOR GE 100 ) , INCLUDE NAME SPREF

Elements which can be blocked are:SITE, ZONE, STRU, SUBS, FRMW, SBFR, EQUI, SUBE, PIPE, BRAN, HVAC, REST

The configuration options may be overridden by LIEXEC command line options; inparticular the Outputfilename switch would normally be overridden by an LIEXECoption. For example:LIEXEC /Draft_DXF_LI 'DXFOUTR13' CONFIGDATA 'MyConfigData' OutputFileName '%PDMSUSER%/new.dxf'

It is also possible to omit the CONFIGDATA, in which case the default values of all theswitches will be assumed and no blocking will take place. However, in such a case a DXFheader file must be specified; for example:



Version 11.5

LIEXEC /Draft_DXF_LI 'DXFOUTR13' HeaderFileName 'header.dxf'

The datasets currently defined within DRAFT can be determined by:DLICON LIST

The definition of a specific dataset can be determined by:DLICON name DUMP

The value of a specific switch within a dataset can be determined by:DLICON name CHECK SWITCH switchname

Whether or not there is a blocking rule applicable to a specified Design element can bedetermined by:

DLICON name CHECK BLOCK element_identifier



7.3.2 Switches and BLOCK Rules to Control DXF Export

Switch name Value (default) DescriptionPrimitiveThickness [ ON ] Allows primitive thickness to be

represented by Polyline width inAutoCAD. The PlineWidthFactorswitch defines the scale of widthfactors used by DXF export.

OFF Prevents primitive thickness frombeing represented in AutoCAD. Allentities are generated using Lines,Arcs and Text with no Polylines.

PlineWidthFactor 0.1, [ 0.2 ], 0.3, …1.0

Defines the scaling of width factorstranslated from Draft to AutoCAD.Polyline width is defined by[( LTHICK - 1 ) * PlineWidthFactor].

ViewNumberPrefix ON Adds a unique numeric view prefixvalue to the beginning of eachAutoCAD Layer name created fromDraft views.

[ OFF ] Suppresses any numeric layer nameview prefix.

LayerZone ON Creates a unique layer for eachDesign ZONE and places all designinformation from that zone onto thelayer.

[ OFF ] Suppresses zone layering.LayerSite ON Creates a unique layer for each

Design SITE, and places all designinformation from that site onto thelayer.

[ OFF ] Suppresses site layering.LayerBack ON Creates a unique layer for the backing

sheet and places the backing sheetinformation on that layer inAutoCAD.

[ OFF ] Suppresses backing sheet layering.LayerOlay ON Creates a layer for each overlay and

places the overlay information on thatlayer in AutoCAD.



Version 11.5

Switch name Value (default) Description

[ OFF ] Suppresses overlay layering.LayerNote ON Creates a layer for each note and

places the note information on thatlayer in AutoCAD.

[ OFF ] Suppresses note layering.LayerLaye ON Creates an equivalent layer in

AutoCAD matching Draft annotationlayers and places information fromthe Draft layers onto subsequentAutoCAD layers.

[ OFF ] Suppresses Draft layer to AutoCADlayer mapping.

FontMapping [ ON ] Maps Draft text styles usingAutodraft equivalent AutoCAD fontstyles.

OFF Uses the standard AutoCAD“STANDARD” (txt) font style for allfonts in AutoCAD.

LinetypeMapping [ ON ] Maps Draft linepattern definitionsonto equivalent AutoCAD linetypedefinitions contained within the DXFheader.Unsupported or undefined linepatternnames are exported to AutoCAD usingan equivalent Draft style name, witha standard dashed representation.

OFF All Draft linepatterns are representedby the default “CONTINUOUS”linetype, mapped using “BYLAYER”in AutoCAD.

ColourMapping [ ON ] Draft pen colours 1 to 15 are mappedto equivalent AutoCAD colournumbers. Colour numbers above 15are mapped directly to AutoCADcolours in the range 1 to 254.

OFF Suppress colour mapping and assignall Draft pen colours to AutoCADcolour “BYLAYER”.

IncludeZCoordinates ON Uses explicit X,Y and Z co-ordinatevalues in the DXF export file.




[ OFF ] Uses explicit X and Y co-ordinatevalues in the DXF file, where Z isassumed to be 0. If Z is not equal to 0,it will be output explicitly.

GraphicsOnlyDXF ON Exports minimal DXF headerinformation and omits all R13 specificdata, including Objects, Handles,AcDb markers, dictionaries and tableinformation; Except :- Layers,Linetypes and Styles.This switch can be used to produceAutoCAD release 12 compatible DXFfiles and can be used to minimise DXFinformation in terms of file size andproduction time with the followingswitches set to OFF:LinetypeMapping,ColourMapping,IncludeZCoordinatesThe following switches are forced OFFwhen the GraphicsOnlyDXF switchis ON: EntityAcDbMarkers andIncludeDXFHeaderEntitiesAll Group switches are ignored whenthis option switch is used althoughblocking is permitted!

[ OFF ] Exports DXF information using a welldefined full AutoCAD release 13 DXFformat.

EntityAcDbMarkers ON Exports AutoCAD release 13 AcDbobject markers in all entities in theDXF file. This option may be requiredfor less tolerant DXF interpreters.

[ OFF ] Suppresses AutoCAD release 13AcDb object markers in all entities.Suppressing AcDb markers in theDXF file can significantly reduce theresulting DXF file size.

NestedBlocks ON Allows hierarchically related blocks tobe nested into a single block hierarchyin AutoCAD.



Version 11.5


[ OFF ] Prevents hierarchically related blocksfrom being nested together inAutoCAD. Block definitions thatcontain multiple sub-componentblocks will be represented by acollection of individual blocks asopposed to a single block definition.These individual, yet hierarchicallyrelated blocks can be grouped togetherusing the GroupBlocks switch.

BlockBack ON Creates a single Block definition forthe Draft backing sheet.

[ OFF ] Suppresses blocking of backingsheets.

BlockOlay [ ON ] Creates a single Block definition foreach Draft overlay sheet.

OFF Suppresses blocking of overlay sheets.BlockSymb ON Creates a single Block definition for

each instanced Draft symbol.

[ OFF ] Suppresses blocking of symbols.BlockFill [ ON ] Creates a single Block definition for

each Draft hatch/fill pattern.

OFF Suppresses blocking of hatchpatterns.

BlockGraphicFile ON Creates a single Block definition foreach occurrence of a plot spool fileused to represent backing sheets oroverlays.

[ OFF ] Suppresses blocking of Graphic plotspooled files.

GroupDims ON Groups dimensions into uniqueAutoCAD release 13 groups.

[ OFF ] Suppresses Grouping of dimensions.GroupNote ON Groups notes into unique AutoCAD

release 13 groups.

[ OFF ] Suppresses Grouping of notes.GroupVnot ON Groups view notes into unique

AutoCAD release 13 groups.




[ OFF ] Suppresses Grouping of view notes.GroupFrame ON Groups frames into unique AutoCAD

release 13 groups.

[ OFF ] Suppresses Grouping of frames.GroupGlab ON Groups GLAB labels into unique


[ OFF ] Suppresses Grouping of GLAB labels.GroupSlab ON Groups SLAB labels into unique


[ OFF ] Suppresses Grouping of SLAB labels.GroupBlocks ON Groups together hierarchically related

blocks, generated from blockingstructures and sub-structures or sub-frameworks. This switch should onlybe used when the NestedBlocksswitch is set to OFF.

[ OFF ] Suppresses Grouping of relatedBlocks

FontFilePath ‘/search/path/…’ Specifies the search path used tolocate Autodraft font shape files. Thisvalue is appended to the beginning ofall font style records created in theDXF file.

[ OFF ] If the search path is set to off, nodirectory path is appended to the startof font style records. This option canbe used if the relevant AutoCADshape files are located in the ACADsupport directory path.

UseShiftJISFonts ON Specifies font mapping should beapplied using the Shift JIS standard.

[ OFF ] Specifies font mapping should beapplied using the default EUCstandard.



Version 11.5

Switch name Value (default) DescriptionIncludeDXFHeaderEntities

ON Allows drawing information containedwithin the DXF header file to bemerged with the exported Draftdrawing information. Under normalexport circumstances, this switchshould be omitted or set to OFF.

[ OFF ] Ignores all DXF entities in theENTITIES section of the DXF headerfile.

HeaderFileName [‘%PDMSEXE%/draft_dxf_li.dxf’]

Specifies the DXF header file name,which will be read into Draft and usedas a backbone template for generatingthe DXF information. If a header filename is specified, it must be a validAutoCAD release 13 DXF file, basedon the default ‘draft_dxf_li.dxf’'

OutputFileName [‘output.dxf’] Specifies the output DXF file nameproduced when exporting DXF fileinformation.

IgnoreBlockRules [ ON ] Allows the DXF export application toignore all BLOCK rules in theconfiguration data-set, used to speedup processing of non-blocked DXFexport.

OFF Allows the DXF export application tosearch and compare configurationdata-set BLOCK rules againstdatabase information in order to blockcomponents in the DXF export file.

ScaleFactor Positive Real No.(default 1.0)

Scale Factor applied to entire DXFFile to enable Full scale Design unitsto be output in the DXF File

[ 1.0 ] Scale Factor 1.0 - DXF File inAnnotation units

Note: The default values specified in this table are those set up by the configurationmacro default_dxf.mac, as supplied with the product. The supplied defaultvalues will always be obtained when using the System Defaults for DXF Outputoption on the Configurable DXF Output form in the standard graphical userinterface.



7.3.3 Limitations

The following limitations apply:• DRAFT's intelligent blanking primitives are not exported to the DXF file as there

are no equivalent AutoCAD primitives to which to map them.• User-defined line patterns (see Section 18.3.2) are assigned to a fixed (dashed)

linetype definition in the DXF file using the DRAFT line pattern name as the DXFlinetype name. This definition can be redefined in AutoCAD to provide thelinestyle required.

• User-defined glyphs and line pictures(see Sections 8.3.4 and 8.3.5) are ignored.• Differentially scaled symbols are not supported.

7.4 Configurable DGN Output

7.4.1 Configuration Datasets

DGN files (for use in MicroStation/J) may also be created from DRAFT Sheets. DGN is abinary format.It is possible to control the format of DGN output using configuration datasets. Theconfiguration dataset controls how the PDMS information is to be mapped into DGNformat. It does the following:• Controls how DRAFT graphics are to be grouped as DGN Group definitions.• Enables PDMS elements to be assigned to DGN Levels.• Maps linestyles, colours and fonts between DRAFT and DGN.• Allows PDMS attribute information to be exported from DRAFT as DGN Group

attributes.The configurable DGN facility uses ‘loadable image’ (LI) applications, usable at Sheetlevel. The DGN export application can be executed using the LIEXEC command (whichalso loads the application if it has not already been loaded).The following example command uses the configuration dataset ’MyConfigData’ tocontrol the export of DGN information:

LIEXEC /Draft_DGN_LI ’DGNOUT’ ConfigData ’MyConfigData’

Here ’DGNOUT’ is an application feature.This will create a DGN file with a name and format defined in the specified dataset forthe current Sheet element. Before giving the above command, the configuration datasetmust have been defined in DRAFT. This may be done either by typing in theconfiguration data at the command line; by building up the required mappings using theDRAFT applicationware; or by reading in a predefined macro file.Other commands related to this facility are:



Version 11.5

LILIST Lists features of application(s) loaded by LILOAD/LIEXEC.DLICON name Defines a named set of configuration options. For example:

DLICON /myconfigconfiguration_optionsEXIT

A DRAFT Configuration Dataset is made up of a series of Switches, Group rules andLevel rules. The configuration_options will contain the GROUP, LEVEL and SWITCHsyntax that controls the content of the DGN file produced.For example:

SWITCH LevelDefault '63'Level 63 to be used by default

SWITCH SeedFileName 'seed.dgn'Specifies the DGN header file name

GROUP ALL EQUI, INCLUDE NAMEA group will be created for each equipment, which will be tagged withits name

LEVEL ALL NOTE, 'ON 32'Level 32 to be used for NOTE elements

Switch names are case-independent, but are shown as mixed case here to aid legibility.Switch values are PDMS text strings, and should be quoted.Rules for Groups and Levels use PML expressions, similar to those used inRepresentation rules. GROUP rules may be followed by the INCLUDE argument to tagthe group with attribute data; LEVEL rules should be followed by a text string definingthe level or range of levels to be used.NOTE: For full details of using expressions in PDMS, see the VANTAGE PDMS

DESIGN Reference Manual, Part 1, Section 2-3-11, or use the online help andsearch for ‘‘expressions”.

The configuration options may be overridden by LIEXEC command line options. Inparticular, the OutputFileName switch would normally be overridden by an LIEXECoption. For example:LIEXEC /Draft_DGN_LI 'DGNOUT' CONFIGDATA 'MyConfigData' OutputFileName '%PDMSUSER%/new.dgn'

It is also possible to omit the CONFIGDATA, in which case the default values of all theswitches will be assumed, the internal default seed will be used, and no grouping orlevelling will take place.The datasets currently defined within DRAFT can be determined by:

DLICON LISTThe definition of a specific dataset can be determined by:

DLICON name DUMPThe value of a specific switch within a dataset can be determined by:



DLICON name CHECK SWITCH switchnameFor example, to query the value of the UNITS switch in the configuration /myconfig:

DLICON /myconfig CHECK SWITCH Units

Whether there is a grouping or levelling rule applicable to a specified DESIGN orDRAFT element can be determined by:

DLICON name CHECK GROUP element_identifierDLICON name CHECK LEVEL element_identifier

For example, to query whether the configuration contains a level rule which applies to/PUMP1:

DLICON /myconfig CHECK LEVEL /PUMP1

7.4.1.1 Sample Configuration DatasetsSample configuration files are provided in the %PDMSDFLTS% directory as PML datafiles (pmldat). Further configuration files can be created using the DRAFT appware. Thesupplied configuration files include:dra-dgn-basic.pmldat Defines a restricted range of essential settings for

configured DGN output.dra-dgn-pdms.pmldat Defines a sample set of configuration settings to produce

fully-grouped and levelled DGN files closely mapped tothe DRAFT Sheet exported. Note that the grouping andlevelling commands for Design graphics in this file areonly intended as an example, and may requiremodification to suit your own requirements.

dra-dgn-imperial.pmldat Defines an equivalent set to dra-dgn-pdms.pmldat, inimperial-units

dra-dgn-nnnn.pmldat Defines a sample set of configuration settings that useslevelling by pen number, and uses text size to selectlevels for annotation (metric units)

dra-dgn-dddd.pmldat Defines a sample set of configuration settings that useslevelling by functional descriptions (imperial units)

Note: These configuration files may be converted to PDMS command-line macro filesfor batch creation of DGN files, using the PDMS appware as follows:

!dgn = object dgnout()!dgn.load( !!file( ‘%PDMSDFLTS%/name.pmldat’ ) )!dgn.save( !!file( ‘%PDMSUSER%/name.pmldat’ ) )

where name is one of the supplied configuration datasets. The macro file%PDMSUSER%/name.mac is created when the PML data file is saved.



Version 11.5

7.4.2 Common Features of Option Switches

7.4.2.1 General MappingsSeveral of the option switches map one set of values (DRAFT) to another (MicroStation).For example, DRAFT colour numbers may be mapped to MicroStation colour numbers,and DRAFT line-pattern names or numbers may be mapped to MicroStation numberedor customised line-styles. These mappings are all handled in the same way.Each mapping consists of one or more sub-mappings, separated by commas. Each sub-mapping has a left-hand (DRAFT) list and a right-hand (MicroStation) list separated bya colon.Each list can include elements that are numbers (non-negative integers or reals) orstrings (quoted or unquoted). Multiple elements are separated by a + character. Integersmay be separated by a '–' character to represent an inclusive range. A right-hand list ofintegers can include the characters 'R' (repeat) or 'D integer' (default).The following rules apply:• The left-hand list must not be empty.• If the right-hand list has a single element, all values in the left-hand list are mapped

to the same value.• If the right-hand list has the same number of elements as the left-hand list, each

element in the left list is mapped to the corresponding element in the right list.• If the right-hand list contains integers with an 'R' option, each element of the right-

hand list is used in turn, the elements being repeated as necessary.• If the right-hand list contains integers with a 'D' option, each element of the right-

hand list is used in turn once only, then the default value is used for all furthermappings as necessary.

For example:'CHAINED:pdmsChained, DASHED:pdmsDashed, DDOTTED:pdmsDdotted'

'1–11:15,12–20:33–41'

'1–20:26–30R' (maps 1:26, 2:27, 3:28, 4:29, 5:30, 6:26, 7:27, etc.)

'20–29:1–3D6' (maps 20:1, 21:2, 23:3, 24:6, 25:6, etc.)

7.4.2.2 Quoted StringsStrings within mappings may be quoted, if necessary, with ' or | characters. Forexample, some MicroStation custom line-styles have names which include a comma orcolon, such as dash, medium. In order to map to this MicroStation custom line-style,you must use an extra set of quotes to prevent the name being treated simply as dash.You need outer quotes to tell DRAFT where the option string ends, and inner ones to tellDraft_DGN_LI where each line-style name ends, thus:SWITCH MapLineStyle |DASHED:'dash, medium',LDASHED:'dash, long'|



A string must be quoted if any of the following apply:• It contains a comma, colon or plus character.• It starts or ends with a space or tab.• It starts with a minus, single quote or vertical bar.• It starts with a digit but is not a number (eg, 345P).

7.4.2.3 Continuing Long MappingsSome mappings may require string lengths longer than the permitted maximum (about100 characters). To achieve this, switches may be continued. Continuation switches havethe same name as the base switch, but extended by a single letter between A and Z.These must be used in alphabetic order. For example, the following long switch setting(all one line):

SWITCH MapLineStyle |CHAINED:pdmsChained, DDOTTED:pdmsDdotted,DASHED:' dash, medium ',LDASHED:' dash, long '|

could be split over the following switch settings:SWITCH MapLineStyle |CHAINED:pdmsChained|SWITCH MapLineStyleA |DDOTTED:pdmsDdotted|SWITCH MapLineStyleB |DASHED:' dash, medium '|SWITCH MapLineStyleC |LDASHED:' dash, long '|

Note: Continuation switches can be used in DLICON configuration syntax. They cannotbe used in the LIEXEC command syntax.

7.4.3 File-Related and Miscellaneous Options

Several switches in this section represent pathnames. These can include standardPDMS environment variable settings; for example:

SWITCH SeedFileName '%PDMSEXE%\dgndata\pdmsSeed2d.dgn'

A file name can include internal spaces without problems, but spaces at the start or endof the file name require additional quotes; for example:

SWITCH SeedFileName 'C:\Program Files\MicroStation\fromPDMS.dgn'SWITCH SeedFileName '| seed with leading spaces.dgn|'

7.4.3.1 OutputFileNameSpecifies the output DGN file name produced when exporting DGN file information. Forexample:

SWITCH OutputFileName '%PDMSUSER%\DGN_file_name.dgn'

7.4.3.2 SeedFileNameSpecifies the DGN seed file name to be used to create the output DGN file. If no seed filename is provided, an internal default seed will be used. The seed file must be a validMicroStation 2D seed file, and must not contain any inconsistent element data. Any tag-



Version 11.5

set definitions in the seed must not conflict with those created by Draft_DGN_LI. Forexample:

SWITCH SeedFileName '%PDMSEXE%\dgndata\pdmsSeed2d.dgn'

SWITCH SeedFileName 'mySeedFile.dgn'

The use of a seed file is optional.A sample seedfile pdmsSeed2d.dgn is supplied with Draft_DGN_LI. This contains acolour table which maps the default PDMS colours 1-16 into Microstation colours.Note: In configurations which use the supplied seedfile, the MapColour switch should

be set to ‘1-256:0-255’

7.4.3.3 UnitsMicroStation uses three levels of working units: Master Units, Sub-Units and PositionalUnits (or Units of Resolution).The seed file contains the size ratios of these three units, and may contain descriptions(max. two characters) of the master and sub-units, but there is no universal set ofdescriptions in use. The Units switch may be used to override the settings in the seedfile, and must contain the size of a master unit in millimetres (MASTMM):

Master Units Description MASTNAME, size in millimetres MASTMMSub-Units Description SUBNAME, ratio per master unit SUPositional Units Ratio per sub-unit PU

These keywords are not case-sensitive, but the values of MASTNAME and SUBNAMEare case-sensitive. The most common scenarios will be:• The working units are set up in the seed file. In this case, the Units switch just

contains the size of a master unit in mm. For example, with an imperial seed file,with master units inches, the Units switch should be:

SWITCH Units 'MASTMM:25.4'

• The working units in the configuration override those in the seed file: all Unitsoptions are needed. (A minor exception is that if the MASTNAME setting isrecognised as a common value, MASTMM may be omitted.) For example, to set boththe master and sub-unit names to millimetres, with one sub-unit per master unit,and 1270 positional units per sub-unit, the Units switch should be:SWITCH Units 'MASTNAME:mm,SUBNAME:mm,SU:1,PU:1270,MASTMM:1.0'

The MASTNAME and SUBNAME values cannot be quoted strings, but can includecharacters such as " (inches) and ' (feet). Only the first two characters of these values aresignificant, and it is not possible to include a space or comma in them. (If you wish touse a space or comma in MASTNAME and SUBNAME values, you must set up theworking units in the seed file, as in the first scenario.)Some more examples of Units settings, respectively for Master units in feet accurate to1/64th inch; and metres accurate to 0.01mm:

SWITCH Units |MASTNAME:',SUBNAME:",SU:12,PU:64,MASTMM:304.8|



SWITCH Units 'MASTNAME:m,SUBNAME:mm,SU:1000,PU:100,MASTMM:1000.0'

7.4.3.4 ScaleFactorA Scale Factor is applied to the entire DGN file to enable full-scale Design units to beoutput in the DGN file. The default value is 1.0.

7.4.3.5 ShiftXA horizontal shift is applied to everything written to the DGN file to position thedrawing at any required place on the Design Plane. The shift is measured inMicroStation Master Units, and the default value is 0.0.

7.4.3.6 ShiftYA vertical shift is applied to everything written to the DGN file to position the drawingat any required place on the Design Plane. The shift is measured in MicroStationMaster Units, and the default value is 0.0.

7.4.3.7 ExcludeBackIf this switch is set to On (the default is Off), any Backing Layer of the DRAFT drawingis not transferred to the DGN file.

7.4.3.8 ExcludeOlayIf this switch is set to On, (the default is Off), any Overlays on the DRAFT drawing arenot transferred to the DGN file.

7.4.3.9 ExcludeSheetFrameIf this switch is set to On, (the default is Off), the sheet frame on the DRAFT drawing isnot transferred to the DGN file.

7.4.3.10 ExcludeFillIf this switch is set to On, (the default is Off), no hatching (including solid fill) in theDRAFT drawing is transferred to the DGN file. This may be useful for good performancein MicroStation, since hatching is transferred as a set of lines.

7.4.3.11 ExcludeSolidFillIf this switch is set to On, (the default is Off), all solid fill is ignored and not transferredto the DGN file. However, other Hatching is still transferred.

7.4.3.12 ExcludeArrowFillIf this switch is set to On, (the default is Off), any solid fill for terminators on dimension-lines and label leader-lines is omitted from the transfer to the DGN file. Other solid filland hatching is transferred.



Version 11.5

Note: More than one of these switches to Exclude Fill may apply to the same entity. Ifany of these switches is true, then the entity will be excluded. For example,either ExcludeSolidFill or ExcludeArrowFill could be used to exclude the fill fordimension-line arrowheads. However, ExcludeArrowFill is more specific.

7.4.4 Pen Related Options

7.4.4.1 MapLineWeightsMicroStation has 32 line-weights (numbered 0-31); DRAFT has 11 line thicknesses(numbered 1-11). The links between them are controlled by the MapLineWeights option,for example:

SWITCH MapLineWeights '1:0,2:1,3:5,4-11:31'SWITCH MapLineWeights '1-11:0-10'

The second example is the default.

7.4.4.2 MapLineStyleMicroStation has seven numbered line-styles, and can also have named custom line-styles. MicroStation documentation recommends using named styles, but some drawingstandards specify numbered ones. DRAFT also uses a mixture of named and numberedline-patterns. The MapLineStyle option maps the DRAFT line-pattern to a MicroStationline-style, ignoring line picture and glyphs. (See Section 7.4.4.3 for how to map line-styles involving line pictures or glyphs.)A resource file pdms_lsty.rsc supplied with PDMS contains custom line-stylesequivalent to the default named PDMS line-patterns.• Any ScaleFactor (see Section 7.4.3.4) is applied to custom line-styles used in the

DGN file.• Any unmapped line-styles map to Solid lines.The following example maps DRAFT’s named line-styles to their nearest equivalents inMicroStation’s numbered styles. This is the default:

SWITCH MapLineStyle 'SOLID:0,DASHED:2,DOTTED:1,CHAINED:4,LDASHED:3,DDOTTED:6'

The next example maps DRAFT named line-styles to some custom line-styles providedas a MicroStation resource file:

SWITCH MapLineStyle'CHAINED:pdmsChained,DASHED:pdmsDashed,DDOTTED:pdmsDdotted,DOTTED:pdmsDotted,LDASHED:pdmsDashed,SOLID:0,TCHAINED:pdmsTChained'

Custom line-style names can include spaces and punctuation; for example, the defaultMicroStation/J installation includes styles -E- and Cable / Tele . See Section 7.4.2.2for details of when you must quote the style-names. As this mapping can get long, (thepreceding example is a single line mapping), you may need to use the continuationfacilities described in Section 7.4.2.3.



7.4.4.3 MapLineStyleByPenMore complex DRAFT line-styles can be set up by the combination of line-pattern, linepicture, line thickness and glyph. To map these combinations onto MicroStation line-styles, you must map them by Pen Number. (Note that this is the pen number as storedin the database, which is not the same as the pen number in the DRAFT AdministratorUser Defined Pen Settings form.)For example, you might have DRAFT pen numbers 217 and 222 set up as:

setpen 217 colour 4 solid lthick 2 lpic 4 glyph 1lpicture 22 mode 3 size 2 repeat 12 gap 4

setpen 222 colour 6 solid lthick 1 lpic 22 glyph 12

and wish to map these to the MicroStation custom line-styles Pneumatic and ‘Data link’respectively. For this you could use the switch setting:

SWITCH MapLineStyleByPen '217:Pneumatic,222:|Data link|'

Custom line-style names can include spaces and punctuation; for example, the defaultMicroStation/J installation includes styles -E- and Cable / Tele . See Section 7.4.2.2for details of when you must quote the style-names. As this mapping can get long, youmay need to use the continuation facilities described in Section 7.4.2.3.

7.4.4.4 MapColourBoth DRAFT and MicroStation use colour numbers, and the mapping between them iscontrolled by the MapColour switch. The interpretation of these colours by MicroStationdepends on the colour-table loaded (this can be included in the seed file). For example:SWITCH MapColour '1:11,2:1,3:6,4:2,5:3,6:4,7:5,8:37,9:33,10:0, 15:254'

SWITCH MapColour '1:96,2:51,3:22,4:52,5:50,6:15,7:49,8:64,9:51,10:0,11:96,12:13,13:63,14:197,15:25416:37'

The second example gives a fairly close fit in MicroStation to the PDMS colours used ifno seed-file is specified. This is the default mapping. Any unmapped colours are mappedto MicroStation colour 0.The sample seed-file pdmsSeed2d.dgn contains this mapping. The following mappingshould be used with this seed-file:

SWITCH MapColour ‘1-256:0-255’

The default mapping is 1-256:0-255. Any unmapped colours are mapped to MicroStationcolour 0. This mapping should be used when the supplied seedfile is used.

7.4.4.5 MarkerSizeThis option sets the size of a DRAFT marker in millimetres (at scale 1). The size of amarker in the DGN file will be the product of this size, the scale of the relevant DRAFTpen, and the overall ScaleFactor switch setting (see Section 7.4.3.4). The default is 1.0.



Version 11.5

7.4.5 Font Related Options

In addition to the font switches below, further work is required to import DRAFT textcorrectly into MicroStation. This is covered more fully in Appendix D Guidelines forImporting DGN Files from DRAFT into MicroStation. The following summarises therequirements:• PDMS DRAFT fonts must be set up in MicroStation using a fonts resource file. The

contents of this file are project-specific. A pdmsSamFont.rsc file is provided, based onthe fonts used in the SAM project supplied with PDMS.

• In order for the geometric data required to be exported to MicroStation, it is alsonecessary to use font geometry files during the transfer to the DGN file. Such filesfontnnn.dgn, where nnn is the Microstation font number, may be set up usingMicroStation. These files are provided in the dgndata directory below%PDMSEXE%. In order to use these files, it is necessary to set up an environmentvariable %OPENDGN_FONT_DIR% which points to this directory.

7.4.5.1 MapFontThis option maps from DRAFT's font numbers (11-16, 21-26, 31-36, 41-46) and thespecial SYMBOL to MicroStation font numbers. DRAFT font numbers 1 and 10 aretreated as equivalent to 11, 2 and 20 as equivalent to 21, 3 and 30 as equivalent to 31, 4and 40 as equivalent to 41. For example:

SWITCH MapFont '11-16:133,21-23:6,24-26:134,31-33:172, 34-36:177,41-43:173,44-46:181,SYMBOL:186'

It is possible to modify the MicroStation font size and position by fractions of theoriginal size; for example:

SWITCH MapFont '11-16:133w0.8h1.2u0.2'

This scales the font by a factor of 0.8 horizontally and a factor of 1.2 vertically, andshifts it up by 0.2 of a character height. The control codes include:

w Width Factorh Height Factoru Offset Upr Offset Rights Slope (in degrees)l Underline Separationp Adjustments for a PDMS font (this includes scaling of w1.25h1.25)m Adjustments for a MicroStation native font (default).

For example:SWITCH MapFont ‘11-13:133p,14-16:105m,21-23:6p,24-26:134p,31-33:172p,34-36:177p,41-43:173p,44-46:181p,SYMBOL:186p’

This font mapping maps PDMS fonts with a best fit for adjustment factors. For PDMSFont family 1, the bold font is mapped to a MicroStation native font.The default is:

SWITCH MapFont '11-46:105,SYMBOL:105'



Note that using the SYMBOL font will only produce good results if it is mapped to a fontcontaining suitable symbol-characters in the correct character positions. The SYMBOLfont is included in the MicroStation resource file pdmsSamFont.rsc supplied withPDMS. When using the supplied resource file, the following font mapping should beused:SWITCH MapFont ‘11-16:201p,21-23:202p,24-26:203p,31-33:204p,34-36:205p,41-43:206p,44-46:207p,SYMBOL:255p’

7.4.5.2 FontSlopesThis option controls whether DRAFT font slopes are translated into MicroStation textslants (default On) or are ignored (Off).

7.4.6 Level-Related Options

MicroStation/J supports a maximum of 63 levels (numbered 1–63). Each DGN graphicalelement is on one and only one level. MicroStation also offers names for levels, butDraft_DGN_LI always refers to levels by number.

7.4.6.1 LevelDefaultThis switch sets the default level: ie the level which will be used if no other switches orrules apply. The default value is 1. For example:

SWITCH LevelDefault '63'

7.4.6.2 LevelPenThis switch can set a mapping to DGN levels associated with DRAFT pen numbers. Thisallows fine control of which levels are used for which parts of the DRAFT drawing. (Notethat this is the pen-number as stored in the database, which is not the same as the pennumber in the DRAFT Administrator User Defined Pen Settings form.)For example:

SWITCH LevelPen '10-20:30-40,100-200:63'

This puts lines and text drawn with pen 10 onto level 30, pen 11 onto level 31 and so on,up to pen 20 onto level 40. DRAFT pens 100 to 200 are put onto level 63. Any other penshave no specific levels, and the default level is used.Note that levels set by LevelBack (see Section 7.4.6.3) or Level Rules (see Section7.4.6.4) take priority over this switch.

7.4.6.3 LevelBackThis switch can set the level number for the backing sheet and everything containedwithin it. The default is Off. If this option is switched On, then no other level switches orrules will apply to items within the backing sheet. For example:

SWITCH LevelBack '63'

This uses level 63 for the backing sheet and everything within it.



Version 11.5

7.4.6.4 Level RulesStandard PDMS selection syntax is used to define Level Rules. These specify how PDMSdesign elements are to be organised onto DGN Levels. For example:

LEVEL ALL STRU, 'ON 36'LEVEL ALL BRAN WITH ( HBOR GE 100 OR TBOR GE 100 ) , 'ON 40'LEVEL ALL EQUI WITH :purpose EQ HVAC, 'ON 44'LEVEL ( /C1101 ) , 'ON 55'LEVEL ALL LAYE WITH ( PURP EQ 'ADCA' ) , 'ON 21'LEVEL ALL LAYE WITH ( PURP EQ 'ADEA' ) , 'ON 22'LEVEL ALL LAYE WITH ( PURP EQ 'MATB' ) , 'ON 23'LEVEL ALL LAYE , 'ON 24'

Rules are applied in order; therefore, if a rule has already been applied for a givenelement, a later rule will not affect it. Using the order specified in the above examples, aLAYE with PURP ‘ADCA’ will be placed on level 21 not on level 24. However a LAYEwith PURP ‘XXXX’ would still be placed on level 24 even if there was a later rule whichapparently placed it elsewhere.Design elements which can have level rules include: SITE, ZONE, STRU, SUBS,FRMW, SBFR, EQUI, SUBE, PIPE, BRAN, HVAC, REST, GRDM, PTRA, BOUN,DRAWI (when owned by a SITE or ZONE) and all Piping Components.DRAFT elements which can have level rules include: LAYE, NOTE, OLAY, VNOT,GLAB, SLAB, ADIM, LDIM, PDIM and RDIM.These rules can operate with a level pool. This consists of one or more levels which areallocated as required. For example, a DRAFT Sheet may have several overlays, and youmay want each overlay on a separate DGN Level within the range 50 to 59 (the levelsassigned for overlays in your drawing standards).A level pool consists of one or more integers or integer ranges, separated by commas,with the optional characters ‘R’, meaning repeat the pool if necessary, and 'D integer' tospecify a default value when the pool is exhausted (see Section 7.4.2.1).For example, to use levels 3, 5, 6, and 7 for the first four sites, and then put any othersites on level 9, specify the switch setting:

LEVEL ALL SITE ,'POOL 3,5-7D9'

To use levels 6–10 for all sites, reusing them in turn as necessary, specify:LEVEL ALL SITE ,'POOL 6-10R '

To use levels 6–10 for the first four sites, then put any other sites on levels specified bywhatever other switches apply, do not use either a ‘D’ or an ‘R, thus:

LEVEL ALL SITE ,'POOL 6-10'

(Note that only the first rule that matches an element is ever considered.)

7.4.7 Group Related Options

MicroStation groups are also known as anonymous or orphan cells. They have a limitedcapacity. If a group reaches this limit, that group will be closed and a new group opened



(a message will be written to the log-file, if any, each time this occurs). Any tagsassociated with the group will be associated with the first group created.Note that the groups produced are never nested.

7.4.7.1 GroupSymbThe default for this switch is Off. If it is switched On, a single group is created for eachinstanced DRAFT symbol if no other group is active.

7.4.7.2 GroupFillThe default for this switch is Off. If it is switched On, a single group is created for eachDRAFT hatch/fill pattern if no other group is active.

7.4.7.3 GroupFrameThe default for this switch is Off. If it is switched On, a single group is created for eachDRAFT view frame if no other group is active. This option puts the line representing theframe itself, not the contents of the frame, into the group.

7.4.7.4 Group RulesStandard PDMS selection syntax is used to define Group Rules. These specify howPDMS design elements are to be organised into MicroStation groups. If PDMSattributes are included in group definitions, they will be attached to the groups asMicroStation tags. For example:

GROUP ALL STRU, INCLUDE NAMEGROUP ALL BRAN WITH ( HBOR GE 100 ) , INCLUDE NAME SPREF

Design elements which can have group rules include: SITE, ZONE, STRU, SUBS,FRMW, SBFR, EQUI, SUBE, PIPE, BRAN, HVAC, REST, GRDM, PTRA, BOUN,DRAWI (when owned by a SITE or ZONE) and all Piping Components.DRAFT elements which can have group rules include: LAYE, NOTE, OLAY, VNOT,GLAB, SLAB, ADIM, LDIM, PDIM and RDIM.Only the first Group rule that matches an element is ever considered. The order of therules is therefore important.Note that elements may be both grouped and levelled. Group rules specify that onegroup will be created for each occurrence of an element that fits a given rule. Level rulesspecify that all elements, which fit a given rule, will be placed on the same level or rangeof levels. For example:

GROUP ALL GLAB places each GLAB in a separate groupLEVEL ALL GLAB, ‘ON 25’ places the group for each GLAB on Level 25



Version 11.5

7.4.8 Product Support Options

7.4.8.1 LogFileNameThis switch sets the name used for the log file. The default value is‘%PDMSUSER%\Draft_DGN_LI_log.txt’. For example:

SWITCH LogFileName '%PDMSUSER%\example27.txt'

7.4.9 Validation feature and options

It is important to be able to syntax-check switches and rules. The Validate featurechecks the syntax of all switches in a supplied configuration. For example:

LIEXEC /Draft_DGN_LI 'VALIDATE' MapColour 1-256:0-255'

It also has extra switches, CheckLevelRule and CheckGroupRule, which check thatvalues are valid as the text string for a Level or Group rule, respectively. For example:

LIEXEC /Draft_DGN_LI 'VALIDATE' CHECKLEVELRULE 'POOL 3,5,8-10R'LIEXEC /Draft_DGN_LI 'VALIDATE' CHECKGROUPRULE 'INCLUDE NAME'

It is expected that the Validate feature will be used mainly by Appware and macrowriters.



7.4.10 Summary of Switches and Rules to Control DGN Export

Option name Value [default] DescriptionOutPutFileName [‘output.dgn’] Pathname for DGN export file.SeedFileName [internal default

seed file]Pathname for seed file used to createDGN export file.

Units Ratios of Master Units to Sub-Units andof Units of Resolution (Positional Units)to Sub-Units. Can also specifydescriptions (max. two characters) forMaster Units and Sub-Units.

ScaleFactor [1.0] Scaling factor applied to entire DGN file.ShiftX [0.0] Horizontal shift in Master Units applied

to the entire DGN file.ShiftY [0.0] Vertical shift in Master Units applied to

the entire DGN file.ExcludeBack On Suppresses transfer of DRAFT Backing

Layer to DGN file.

[Off] DRAFT Backing Layer transferred toDGN file.

ExcludeOlay On Suppresses transfer of DRAFT Overlaysto DGN file.

[Off] DRAFT Overlays transferred to DGN file.ExcludeSheetFrame On Suppresses transfer of DRAFT Sheet

Frame to DGN file.

[Off] DRAFT Sheet Frames transferred toDGN file.

ExcludeFill On Suppresses transfer of Hatching (including solid fill) to the DGN file

[Off] Hatching and solid fill transferred toDGN file.

ExcludeSolidFill On Suppresses transfer to the DGN file ofSolid fill

[Off] Solid fill transferred to DGN file.ExcludeArrowFill On Suppresses transfer to the DGN file of fill

for Dimension-line and Leader-lineterminators



Version 11.5

Option name Value [default] Description

[Off] Fill for Terminators transferred to DGNfile.

MapLineWeights [1–11:0–10] MicroStation has 32 line weights (0–31);DRAFT has 11 line weights (1–11).

MapLineStyle [Solid:0, Dashed:2, Dotted:1, Chained:4, LDashed:3 DDotted:6]

Maps DRAFT's line patterns to nearestequivalent MicroStation line style,ignoring line pictures and glyphs. Anyunmapped line styles default to Solidlines.

MapLineStyleByPen Maps DRAFT's pen numbers, which candefine combinations of line pattern, linethickness and glyphs, to MicroStationline styles.

MapColour Maps DRAFT colour numbers toMicroStation colour numbers.

MarkerSize [1.0] Sets size of a DRAFT marker in mm (atscale = 1).

MapFont [11–46:105,SYMBOL:105]

Maps DRAFT font numbers (11–16, 21–26, 31–36, 41–46, SYMBOL) toMicroStation font numbers.

FontSlopes [On] Translates DRAFT font slopes toMicroStation text slants.

Off Ignores DRAFT font slopes.LevelDefault [1] Sets default level to be used by

MicroStation if no other switches or rulesapply.

LevelPen Map items associated with specificDRAFT pen numbers to MicroStationlevels.

LevelBack Sets MicroStation level to be used forbacking sheet (and items within it).

Level Rules A set of rules that assign specified PDMSelement types to MicroStation levels. Canuse R (repeat) and D (default) syntax toset up level pools.

GroupSymb On Creates single MicroStation group foreach DRAFT symbol if no other group isactive.



Option name Value [default] Description

[Off] Does not automatically create group forDRAFT symbols.

GroupFill On Creates single MicroStation group foreach DRAFT hatch/fill pattern if no othergroup is active.

[Off] Does not automatically create group forDRAFT hatch/fill patterns.

GroupFrame On Creates single MicroStation group foreach DRAFT view frame if no othergroup is active. (Group will contain frameline, but not frame content.)

[Off] Does not automatically create group forDRAFT view frame.

Group Rules A set of rules which assign specifiedPDMS element types to MicroStationgroups. Any PDMS attributes included ingroup definitions will be attached togroups as MicroStation tags.

LogFile On Creates log file to record error messagesgenerated during creation of DGN file.

[Off] Log file is not created.LogFileName [%PDMSUSER%

\DRAFT_DGN_LI_log.txt]

Pathname for log file (if LogFile is set toOn).

7.4.11 Limitations

The following limitations apply:• DRAFT's intelligent blanking primitives are not exported to the DGN file.• User-defined glyphs and line pictures (see Sections 8.3.4 and 8.3.5) are ignored.

However, it is possible to specify a MicroStation custom line-style for a givenDRAFT pen number.

• Differentially scaled symbols are not supported.• Hatching (fill) is exported as a set of poly-lines.• Dimensions are not exported as MicroStation dimensions. However, they may be

grouped.• Multi-byte fonts are not supported with MicroStation/J.


8 Pens and Linestyles

8.1 Introduction

Every graphics primitive in DRAFT is drawn in a specific line pen. Each pen has a pennumber in the range 1-255.Each numbered pen can be defined to have some or all of the following attributes:• A colour.• A line representation. This applies to all drawn lines. Each representation itself

has the following attributes:• A thickness - 11 widths.• A pattern - solid, dashed, dotted etc; a choice of 10 predefined patterns is

available; you can also define your own.• A glyph (optional) - a symbol used in the definition of a line picture (see

below). A choice of 20 glyphs is available; you can also define your own.• A line picture (optional) - defining the size of the glyphs, their spacing and

the length of gap (if any) made for them in the line path. A choice of 20predefined line pictures is available; you can also define your own.

• A marker type. A choice of five marker types (drawn at a user-definable scale) isavailable.

• A hatch pattern (used only for closed polyline graphics primitives, e.g. circles(CIRC), rectangles (RECT) etc). A choice of 20 predefined line pictures is available;you can also define your own.

Each of the above attributes is discussed in detail in sections 8.2 - 8.5. How to set up a(numbered) pen with the above attributes is defined in section 8.6. Having set up a pen,the pen number can then be assigned to a number of pen attributes possessed by variousDRAFT elements. These elements and their relevant attributes are referred tothroughout this manual, but a few general rules are given in section 8.7.The term linestyle is used here and elsewhere in this document to describe the overallappearance of a line in terms of its thickness, pattern and picture.

Pens and Linestyles


Version 11.5

Figure 8-1 shows some of the possibilities.

Figure 8-1 Miscellaneous Line Patterns/Thicknesses, Fill Patterns

Pens and Linestyles


8.2 Colours

You may define colour numbers 1 to 128. The COLOUR command is used to define theRed-Green-Blue mixfor a colour nimber or to assign a predefined colour mix by name.For example:

COLOUR 3 GREENCOL 4 WHITESMOKECOL 128 MIX RED 80 GREEN 50 BLUE 50COL 100 MIX RED 50 GRE 50 BLU 0

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

Colour numbers 1 to 16 are assigned by default to the following predefined colours:Colour 1 GREY Colour 9 BROWNColour 2 RED Colour 10 WHITEColour 3 ORANGE Colour 11 PINKColour 4 YELLOW Colour 12 MAUVEColour 5 GREEN Colour 13 TURQUOISEColour 6 CYAN Colour 14 INDIGOColour 7 BLUE Colour 15 BLACKColour 8 VIOLET Colour 16 MAGENTA

The complete set of (50) predefined colours which you may specify by name is:MIXTURECOLOUR

Red Green Blueblack 0 0 0white 100 100 100whitesmoke 96 96 96ivory 93 93 88grey 66 66 66lightgrey 75 75 75darkgrey 32 55 55darkslate 18 31 31red 80 0 0brightred 100 0 0coralred 80 36 27tomato 100 39 28plum 55 40 55deeppink 93 7 54

(continued)

Pens and Linestyles


Version 11.5

MIXTURECOLOURRed Green Blue

pink 80 57 62salmon 98 50 44orange 93 60 0brightorange 100 65 0orangered 100 50 0maroon 6 14 42yellow 80 80 0gold 93 79 20lightyellow 93 93 82lightgold 93 91 67yellowgreen 60 80 20springgreen 0 100 50green 0 80 0forestgreen 14 56 14darkgreen 18 31 18cyan 0 93 93turquoise 0 75 80aquamarine 46 93 78blue 0 0 80royalblue 28 46 100navyblue 0 0 50powderblue 69 88 90midnight 18 18 31steelblue 28 51 71indigo 20 0 40mauve 40 0 60violet 93 51 93magenta 87 0 87beige 96 96 86wheat 96 87 70tan 86 58 44sandybrown 96 65 37brown 80 17 17khaki 62 62 37chocolate 93 46 13darkbrown 55 27 8

How to assign a colour to a pen number is described in Section 8.6.

8.3 Line Representations

Lines may have some or all of the representation attributes listed in Section 8.1.Examples of the available options are illustrated in the following sections.

Pens and Linestyles


8.3.1 Line Thicknesses

Line Pen can be defined as having a thickness index in the range 1 to 11, definedusing the LTHICKNESS keyword. Increasing the thickness index by 1 will increase theline thickness by approx 0.2mm.

LTHICK 1 gives the thinnest line (single stroke)LTHICK 11 gives the thickest (approx 2mm)

Predefined settings are THIN and THICK.THIN corresponds to LTHICK 1THICK corresponds to LTHICK 3

See section 8.6.2 for examples of using the SETPEN command to set line thickness to apen number.

8.3.2 Line Patterns

A choice of 10 predefined line patterns is available (see Figure 8-2); you may also defineyour own.SOLID

DASHED

DOTTED

CHAINED

LDASHED

DDASHED

DDOTTED

FDOTTED

DCHAINED

TCHAINED

Figure 8-2 Line PatternsLine Pattern is defined in terms of two parameters:Pattern description: a sequence of dashes and gaps each with an integer

specifying their relative lengths.Pattern repeat distance: the approximate distance at which the pattern is repeated

and to which the sum of the lengths of all the dashes andgaps are scaled. If not specified a repeat distance of 25mm(1in) is assumed.

Pens and Linestyles


Version 11.5

The two parameters are defined by the LPATTERN command, which takes the generalform:

LPATTERN int [TEMplate [int |name] | REPeat distance ][ [ REPeat distance ] pattern_description ]

The pattern_description is specified by a series of DASH and GAP keywords and relativelengths (given in integers). For example, a chained pattern description could be given as:

DASH 20 GAP 5 DASH 5 GAP 5

A pattern description must start with a dash and it is recommended that it should endwith one as well so that lines do not end with a gap but are drawn to their full length. Itwould therefore be better if the previous example was defined as:

DASH 10 GAP 5 DASH 5 GAP 5 DASH 10

If the TEMPLATE option is used then DRAFT will take the Line Pattern specified by thetemplate name or number as the starting point for the definition of the new LinePattern. In order to change the repeat distance of an existing user-defined Line Patternit should be specified as the template. It is not possible to change the definition of the 10predefined Line Patterns. The LPATTERN and TEMPLATE numbers must be in therange 1 - 100.The definitions of the 10 predefined Line Patterns are:

Pattern Name REPEATdistance

DASH GAP DASH GAP DASH GAP DASH

SOLID - - - - - - - -DASHED 12 4 4 4 - - - -DOTTED 6 8 44 8 - - - -CHAINED 24 80 32 16 32 80 - -LDASHED 18 72 36 72 - - - -DDASHED 22 25 25 50 24 2 24 25DDOTTED 16 25 24 2 24 2 24 25FDOTTED 3 1 23 1 - - - -DCHAINED 30 60 25 25 25 25 25 60TCHAINED 45 100 25 25 25 25 25

2525

100

The Repeat distances are in millimetres, the DASH and GAP values are relative sizes.See section 8.6.2 for examples of using the SETPEN command to set line pattern to apen number.Note that the appearance of a pattern on a screen will not be identical to that obtainedin plotfiles and DXF files. In particular, the size of the marks and spaces will not beaffected by zooming in or out.

Pens and Linestyles


8.3.3 Glyphs

A choice of 20 predefined line glyphs is available, see Figure 8-3, and you can also defineyour own, see Section 8.3.4. The actual size and spacing of the glyph will depend uponthe line picture with which it is used.

Pens and Linestyles


Version 11.5

Glyph 1 Double slash

Glyph 2 L

Glyph 3 Cross

Glyph 4 Zigzag 1

Glyph 5 Zigzag 2

Glyph 6 Break symbol

Glyph 7 Transverse bar

Glyph 8 Arrowhead, forward pointing, unfilled

Glyph 9 Arrowhead, backward pointing, unfilled

Glyph 10 Open arrowhead, forward pointing

Glyph 11 Open arrowhead, backward pointing

Glyph 12 Circle, unfilled

Glyph 13 Square, unfilled

Glyph 14 Hexagon, unfilled

Glyph 15 Diamond, unfilled

Glyph 16 Arrowhead, forward pointing, filled

Glyph 17 Arrowhead, backward pointing, filled

Glyph 18 Circle, filled

Glyph 19 Star

Glyph 20 Thick bar

Figure 8-3 Predefined Glyphs 1 to 20

Pens and Linestyles


8.3.4 User-defined Glyphs

User-defined glyphs are created by defining a series of spans which can be straight linesor circular arcs. The ends of the spans are defined by pairs of coordinates. Arcdefinitions must specify the subtended angle, which must lie between –180 and +180. Apositive angle defines a counter-clockwise arc, a negative angle a clockwise one. APolyline may have up to 49 spans and a Polyarc up to 19.Glyphs can include breaks and solid-filled areas, and new glyphs can be created fromexisting ones by inverting or adding spans to them.The actual size of a glyph is not defined until it is used in conjunction with a Line-Picture. The size is then determined by mapping the EXTENT value of the glyph ontothe SIZE attribute of the Line-Picture. Thus if a glyph with EXTENT 2000 consisting of acircle of diameter 1000 is used in conjunction with a Line-Picture with SIZE 6mm andREPEAT 20mm the final line will have 3mm circles drawn every 20mm. Except for verysimple glyph designs it is recommended that an EXTENT of 2000 is used.Each glyph must have a number in the range 1 - 100. The predefined glyphs supplied inDRAFT are numbered 1 to 20.The general forms of the command are:

LGLYPH glyph_no STArt EXTent value polyspan polyspan . . .Defines a glyph starting from an empty glyph

LGLYPH glyph_no ADD polyspanAdds additional polyspans to the definition of an existing glyph

LGLYPH glyph_no TEMplate glyph_no . . . options. . . ADD polyspanDefines a glyph starting from the current definition of another glyph. Theinitial definition may be filled, or inverted about the X or Y axis (or both)before optional polyspans are added to it. Note that in this case an EXTENTof 2000 will be assumed.

The FILL option specifies that the following lines and arcs are to be considered asoutlines bounding a solidly-filled area. Each succeeding BREAK causes the precedingoutline to be closed by a straight line span. The NOFILL option causes the area boundedby the outlines since the last fill to be treated as the multiple boundary of an area whichis solidly filled. Further lines or arcs are no longer treated as outlines until the nextFILL. FILL and NOFILL both imply BREAK. Outlines may be either outer boundaries orholes: by convention, outlines are specified in a sense that keeps the filled area on theleft – counter-clockwise around outer boundaries, clockwise around holes – but this isnot mandatory.A straight line will be automatically generated between consecutive PLINEs and PARCsunless a BREAK, FILL, or NOFILL option is specified.

Pens and Linestyles


Version 11.5

ExamplesThe following examples define the standard glyphs supplied, which are illustrated inFigure 8-3.Glyph 1: Double slash

LGLYPH 1 START EXTENT 20 PLINE 5 10 -15 -10 BREAK PLI -5 -10 15 10

Glyph 2: L SymbolLGLYPH 2 STA EXT 20 PLI 0 10 0 -10 10 -10

Glyph 3: CrossLGLYPH 3 STA EXT 20 PLI -10 -10 10 10 BRE PLI -10 10 10 -10

Glyph 4: Zigzag 1LGLYPH 4 STA EXT 20 PLI -10 0 -10 10 10 -10 10 0

Glyph 5: Zigzag 2LGLYPH 5 STA EXT 20 PLI -20 0 -10 10 10 -10 20 0

Glyph 6: Line-break symbol:LGLYPH 6 STA EXT 34 PLI -17 0 10 34 -10 -34 17 0

Glyph 7: Transverse bar:LGLYPH 7 STA EXT 20 PLI 0 10 0 -10

Glyph 8: Arrow head (in path direction):LGLYPH 8 STA EXT 20 PLI 10 0 -10 5 -10 -5 10 0

Glyph 9: Arrow head (in anti-path direction):LGLYPH 9 TEMPLATE 8 XINVERT

Glyph 10: Open Arrow head (in path direction):LGLYPH 10 STA EXT 20 PLI 0 10 10 0 0 -10

Glyph 11: Open Arrow head (in anti-path direction):LGLYPH 11 TEM 10 XIN

Glyph 12: Circle:LGLYPH 12 STA EXT 20 PARC 10 0 180 -10 0 180 10 0

Glyph 13: Square:LGLYPH 13 STA EXT 20 PLI 10 10 -10 10 -10 -10 10 -10 10 10

Pens and Linestyles


Glyph 14: Hexagon:LGLYPH 14 STA EXT 2000 PLI 1000 0 500 866 -500 866

LGLYPH 14 ADD PLI -1000 0 -500 -866 500 -866 1000 0

Glyph 15: Diamond:LGLYPH 15 STA EXT 20 PLI -10 0 0 10 10 0 0 -10 -10 0

Glyph 16: Filled Arrow head (in path direction):LGLYPH 16 TEM 8 FILL

Glyph 17: Filled Arrow head (in anti-path direction):LGLYPH 17 TEM 16 XIN

Glyph 18: Filled circle:LGLYPH 18 TEM 12 FILL

Glyph 19: Star:LGLYPH 19 STA EXT 2000 PLI 924 383 -924 -383 BRE PLI 383 924 -383 -924

LGLYPH 19 ADD BRE PLI -383 924 383 -924 BRE PLI -924 383 924 -383

Glyph 20: Thick bar:LGLYPH 20 STA EXT 20 FIL PLI -20 -1 0 -1 PARC 0 –1 180 0 1 PLI -20 1 -20 -1

8.3.5 Line Pictures

A predefined set of line pictures is provided; it is also possible for you to define your own.Line Picture is defined in terms of four parameters:Mode: A code number (1 - 6) to signify how the glyphs are to be

distributed. If a value is not specified, 3 is assumed.The MODE number is interpreted as follows:

Mode MeaningNumber

1-3 Glyphs spaced along the line. Mode = 3 is recommended to give the best overall results.Mode = 1 or 2 may give untidy effects at the ends of spans.

4 One glyph at end of line.5 One glyph at beginning of line, with axes reversed.6 A glyph at each end of line, the first having axes

reversed.

Pens and Linestyles


Version 11.5

Glyph size: The SIZE to which the glyph reference size is scaled. Thisvalue must be specified.

Glyph repeat distance: The approximate frequency of the glyphs. The first glyphhas its origin at half the REPEAT distance from the start ofthe line. With Mode = 2 or 3 DRAFT will adjust the specifiedrepeat distance so as to give an integer number of repeats.For Mode = 4, 5 or 6 the glyphs will be placed with theirorigins at half the repeat distance from the appropriateends. With Mode = 4, 5 or 6 the repeat distance may be 0 orunspecified, otherwise it must be specified and be greaterthan 0.All DRAFT’s predefined glyphs (except numbers 10, 11, and20) have their origins at their centres and thus a repeatdistance of 0 with Mode = 4, 5 or 6 will cause them to becentred upon the end(s) of the primitive. This is generallysatisfactory for balloons, dots, etc but with arrowheads itwill cause the primitive to appear longer than specified. Toavoid this, the repeat distance should be equal to the SIZEvalue. This will cause the origin of each glyph to bepositioned at half the repeat distance from the end.

Gap length: The length of each GAP in the path. This may be 0 if no gapsare required. If it exceeds the repeat distance then the pathitself is completely omitted - only the glyphs will be drawn.If not specified then 0 is assumed.

In addition, the template option, if used, causes DRAFT to take the Line Picturespecified by the template number as the starting point for the definition of the new LinePicture. In order to change the definition of an existing Line Picture it should bespecified as the template. The TEMPLATE number must be in the range 1-100.Predefined Line PicturesThe line is drawn in the current thickness and pattern (i.e. dashed, chained etc). Thereare 400 possible line picture/glyph combinations. Figure 8-4 shows the 20 line picturescombined with one glyph (glyph 15).Line pictures 1-9 produce small glyphs which will generally fit neatly in a 2mm gap inthe line. Line pictures 10-14 produce glyphs that are twice as big, and so most will fitinto a 4mm gap.

Pens and Linestyles


Actual definitions are:Line Picture TEMPLATE MODE SIZE REPEAT distance GAP

1 3 2 12 22 1 2 25 23 1 2 50 24 3 2 12 05 4 2 25 06 4 2 50 07 3 2 12 500008 7 2 25 500009 7 2 50 50000

10 3 4 25 411 10 4 50 412 10 4 75 413 3 4 50 5000014 13 4 75 50000

Where gaps are marked ‘50000’ the line itself is omitted, i.e. only the glyphs are drawn.This style could be used, for example, to draw a series of arrowheads to denote flowdirection in pipework without drawing the centreline of the pipework. It is for thisreason that the set of glyphs includes backward-pointing arrowheads.Line pictures 15-20 put the glyph at the end(s) of the line. Line pictures 15 and 16produce small (2mm) glyphs, line-pictures 17 and 18 are larger (4mm), and 19 and 20are much larger (generally equivalent to 12mm diameter). Actual definitions are:

Line Picture TEMPLATE MODE SIZE REPEAT distance GAP15 4 2 0 016 15 6 2 017 4 4 4 018 17 6 4 019 4 12 0 1220 19 6 12 12

All distances quoted (i.e. SIZE, REP, and GAP values) are in millimetres.

Pens and Linestyles


Version 11.5

When a glyph is omitted from the definition of a pen, the line picture will be drawn withany gaps that the line picture defines. When a line picture is omitted from thedefinition, any glyph assigned to the pen will be ignored. Glyphs and line pictures maybe removed from the definition of a pen by the GLYPH OFF and LPICTURE OFF syntax,see section 8.6.

LPIC 1

LPIC 2

LPIC 3

LPIC 4

LPIC 5

LPIC 6

LPIC 7

LPIC 8

LPIC 9

LPIC 10

LPIC 11

LPIC 12

LPIC 13

LPIC 14

LPIC 15

LPIC 16

LPIC 17

LPIC 18

LPIC 19

LPIC 20

Figure 8-4 Predefined Line Pictures

Pens and Linestyles


User-Defined Line PicturesThe four parameters are defined by the LPICTURE command, which takes the generalform:LPICTURE int [TEMplate int] | MODE int | SIZE distance | REPeat distance |GAP distanceFor example

LPICTURE 22 MODE 3 SIZE 4 REP 25 GAP 10

If the TEMPLATE option is used then DRAFT will take the Line Picture specified by thetemplate number as the starting point for the definition of the new Line Picture. Inorder to change the definition of an existing Line Picture it should be specified as thetemplate. The LPICTURE and TEMPLATE numbers must be in the range 1-100.Users should note that line picture parameters are affected by scale. This means, forinstance, that if a Symbol Template is defined using a pen with line picture assigned,then when that template is instanced to define a Symbol the size and frequency of theglyphs will be affected by the scale of the Symbol.This also means that if a pen with Line Picture assigned is used to draw 3D designgraphics then the size and frequency of the glyphs will be reduced by the view scale.

8.4 Marker Types

The marker type attribute is used to define the symbol to be used to represent p-pointsand MRKP primitives. A choice of five marker types (drawn at a user-definable scale) isavailable.

. (STOP) x (CROSS)+ (PLUS) * (STAR) o (RING)

Figure 8-5 P-Point Marker Types

Pens and Linestyles


Version 11.5

8.5 Hatch Patterns

A predefined set of hatch patterns is provided; it is also possible for you to define yourown. Hatch Pattern is defined in terms of three parameters:Angle: the slope of the hatch lines in degrees measured in a

counter-clockwise direction from the horizontal. The valuespecified must lie in the range -360 to 360. If not specified avalue of 30 will be assumed.

Separation: the spacing between the hatch lines. If 0 then a solid fill isachieved. The specified value will always be used in plotfiles; on terminals the spacing will be device-dependent butit will be related to the specified value. If no value is given, 4mm will be assumed.

Offset: this is the offset of the hatch-pattern from the bottom left-hand corner of the picture. It is only of real use when twohatch-patterns with the same angle and separation arecombined together in a single pen. If they have differentoffsets double-line hatching can be achieved. If no value isgiven 0 is assumed.

In addition, the template option, if used, causes DRAFT to take the Hatch Patternspecified by the template number as the starting point for the definition of the newHatch Pattern. In order to change the definition of an existing Hatch Pattern it shouldbe specified as the template. The TEMPLATE number must be in the range 1-100.Predefined Hatch PatternsTwenty predefined hatch patterns plus a solid-fill capability are provided. Hatchpatterns 1-10 are shown (within square RECT primitives) in Figure 8-6. These providetwo separations (2mm and 4mm) and six angles (30, -30, 45, -45, 0, 90). The offset valuefor all of these settings is 0mm. Patterns 11-20 are similar except that they have adifferent offset value. The offset for the 4mm separated patterns is 0.5mm and that forthe 2mm separated patterns is 1mm.For all hatch patterns, the (optional) solid-fill colour will be that of the pen to which thehatch pattern number is assigned. (See section 8.6.2 for an example command.)It is possible to assign two hatch patterns to a single pen. This enables you to createmore complicated hatching styles. By combining two 4mm-separated patterns that differonly in offset value (e.g. patterns 4 and 14), you can obtain a double-hatching style.Combining two 2mm-gapped patterns that differ only in offset value (e.g. patterns 8 and18) will produce hatching with a 1mm gap. These combination patterns are shown inFigure 8-7. Other combinations will generally produce cross-hatching; examples ofpossible permutations are shown in Figure 8-8.Actual definitions are:

HatchPattern

TEMPLATE ANGLE SEPARATION OFFSET

Pens and Linestyles


HatchPattern

TEMPLATE ANGLE SEPARATION OFFSET

1 30 4 02 1 -30 4 03 1 45 4 04 1 -45 4 05 1 0 2 06 1 90 2 07 1 30 2 08 2 -30 2 09 3 45 2 0

10 4 -45 2 011 1 30 4 0.512 2 -30 4 0.513 3 45 4 0.514 4 -45 4 0.515 5 0 2 116 6 90 2 117 7 30 2 118 8 -30 2 119 9 45 2 120 10 -45 2 1

All distances quoted (SEPARATION and OFFSET) are in millimetres.User-Defined Hatch PatternsThe four parameters are defined by the HPATTERN command, which takes the generalform:HPATTERN int [[TEMplate int] | ANGLe int | SEParation distance | OFFset distance]For example:

HPATTERN 22 TEM 3 SEP 6

If the TEMPLATE option is used then DRAFT will take the Hatch Pattern specified bythe template number as the starting point for the definition of the new Hatch Pattern.In order to change the definition of an existing Hatch Pattern it should be specified asthe template. The HPATTERN and TEMPLATE numbers must be in the range 1-100.

Pens and Linestyles


Version 11.5

HPATTERN 1

Gap 4mmAngle 30°

HPATTERN 2

Gap 4mmAngle -30°

HPATTERN 3

Gap 4mmAngle 45°

HPATTERN 4

Gap 4mmAngle -45°

HPATTERN 5

Gap 2mmAngle 0°

HPATTERN 6

Gap 2mmAngle 90°

HPATTERN 7

Gap 2mmAngle 30°

HPATTERN 8

Gap 2mmAngle -30°

HPATTERN 9

Gap 2mmAngle 45°

HPATTERN 10

Gap 2mmAngle -45°

Figure 8-6 Hatch Patterns 1-10

Pens and Linestyles


HPATTERN 1 +HPATTERN 11










Figure 8-7 Combined Hatch Patterns (Parallel)

Pens and Linestyles


Version 11.5











Figure 8-8 Combined Hatch Patterns (Cross-Hatching)

Pens and Linestyles


8.6 Defining Pen Settings

8.6.1 Defaults

By default, pens 1-120 are predefined as follows:

PenNumber

ColourNumber

Line Pattern

LineThickness

Hatch PatternNumber

MarkerType

MarkerScale

1 1 SOLID THIN 1 STOP 12 1 DASH THIN 2 PLUS 13 1 DOT THIN 3 STAR 14 1 CHAIN THIN 4 RING 15 1 LDASH THIN 5 CROSS 16 1 SOLID THICK 6 STOP 47 1 DASH THICK 7 PLUS 48 1 DOT THICK 8 STAR 49 1 CHAIN THICK 9 RING 4

10 1 LDASH THICK 10 CROSS 411 2 SOLID THIN 1 STOP 1: : : : : : :

20 2 LDASH THICK 10 CROSS 4: Increments Repeats Alternates Repeats Repeats Alternates: by 1 every every every every every every: 10 pens 5 pens 5 pens 10 pens 5 pens 5 pens

111 12 SOLID THIN 1 STOP 1: : : : : : :

120 12 LDASH THICK 10 CROSS 4

Notes: Hatch patterns 11 to 20 and solid fill are not assigned to pens by default.

Glyphs and line pictures are not assigned to pens by default, but a macro(linestyles.mac) is supplied which, when run, will define pens 201 to 220 tohave the line picture/glyph combinations shown in Figure 8-9.

Pens and Linestyles


Version 11.5

PEN 201glyph 15 lpic 1PEN 202glyph 4 lpic 2

PEN 203glyph 8 lpic 3


















Figure 8-9 Line-Pattern/Glyph Combinations Assigned (by macro) to Pens 201-220

Pens and Linestyles


8.6.2 User-Definable Pens

All pen settings can be changed from those set by default by the SETPEN command,which (using its full functionality) takes the form:

SETPEN [int[int]:ALL] | COLOUR [int:col_name] | line_width | LTHICK int | line_pattern | LPATTint | LPIC [int:OFF] | GLYPH [int:OFF] | HPATT [int[int]] | FILL | marker_type | SCALE int

Where: int = integer;col_name = predefined colour name as listed in Section 8.2;line_width = THICK or THIN;line_pattern = predefined pattern name as listed in Section 8.3.2;marker_type = predefined marker name as listed in Section 8.4.

Any or all of the eight pen attributes may be set (in any order). For example:SETPEN 23 THICK DASHED COLOUR 7

SETPEN 99 THIN DCHAINED COL STEELBLUE

SETPEN 207 COL 1 LTHICK 6 SOLID LPIC 9 GLYPH 16 HPATT 7 17

SETPEN 50 THICK LPATTERN 14 COL 7 SCA 4 PLUS GLY OFF LPI OFF

The syntax allows a range of pens to be defined with one command. For example:SETP 1 TO 100 LTHI 4

assigns Lthickness 4 to pens 1-100 (the 'TO' is optional)SETPEN 42 44 HPATT FILL COL 6

assigns solid fill, in colour 6, to pens 42, 43, and 44SETP ALL SOLID

assigns linestyle SOLID to all pens ( 1-255)SETPEN DEF

sets pens 1-255 to their default settingsThe SETPEN command sets both the display pen and the plotter pen. These can be setindependently by the DEVPEN and PLOTPEN commands (respectively), which take thesame syntax. For example:

PLOTPEN ALL THINset all plotter pens as THIN

DEVPEN 11 20 COL 2 THINsets display device pens 11-20 as colour 2 and THIN

Pen settings for marker types are defined by commands such as:SETP 24 RING SCALE 4

redefines pen 24 on both device and plotfileDEVP 11 15 SCA 8 CROSS

redefines pens 11-15 on device onlyPLOTP ALL SCA 5

redefines scale value only on all plotfile pens

Pens and Linestyles


Version 11.5

Colour number must be an integer in the range 1-128 (except when used with thePLOTPEN command, see below); marker scale must be an integer in the range 1-8. Theinteger used to define line picture, glyph and hatch pattern(s) must be in the range1-100. OFF is another option for the first two of these, for example:

SETP 99 LPIC OFF GLY OFFremoves line picture/glyph definition from pen 99

When using the PLOTPEN command to define the plotter pen the colour number can bein the range 1-255. This number is written to PDMS plotfiles as the pen number or asthe layer number (as GT_n) in standard DXF format files. If the SETPEN command isused with a colour number in the range 129-255, only the plotter colour number ischanged.Note that if a colour name is specified rather than a number when using the SETPENsyntax the colour number, written to the plotfile as the pen number or the layer numberin DXF files, will be defined by PDMS and will be in the range 206-255. Thus:

SETP 100 COL 2 THIN DASHEDwill cause 2D graphical primitives (drawn in DRAFT pen 100) to be assignedpen 2 in PDMS plotfiles and to layer GT_2 in DXF files.

However:SETP 100 COL RED THIN DASHED

will cause 2D graphical primitives (drawn in DRAFT pen 100) to be assignedpen 214 in PDMS plotfiles and to layer GT_214 in DXF files. (As 214 is thePDMS system colour for RED.)

8.6.3 Graphical Feedback

The cursor size/resize commands (e.g. VREGION, DEFINE, DIAMETER etc) incorporate a‘rubber banding’ feature - keeping the left-hand mouse button held down enables anappropriate shape to be dragged out to the required extent.The colour of this ‘graphical feedback’ feature is magenta by default, but can be changedby the SETFEEDBACK command. For example:

SETFEED COL 15Set rubber banding colour to colour 15.

SETFEED COL BRIGHTORANGE

SETFEED COL DEFSet rubber banding colour to magenta

The SETFEEDBACK command also controls the appearance of displayed p-points. Bydefault, when p-points are displayed (see Section 6) they appear as ‘star’ markers, scale2, in the current feedback colour. The marker type and scale can be changed by:

SETFEEDBACK PPOINTS marker_type [SCALE int]

For example,SETFEED PPO PLUS

Set p-point symbol to ‘+’

Pens and Linestyles


SETFEED PPO RING SCALE 3Set p-point symbol to ‘o’, scale 3

8.6.4 Querying Pen Settings

The colour, line representation, marker style and hatch pattern of a pen may be queriedby commands such as:

Q SETPEN 25 LINEQuery line representation assigned to pen 25

Q SETPEN 64 FILLQuery hatch pattern assigned to pen 64

Q SETPEN 5Query all attribute settings of pen 5

DEVPEN and PLOTPEN may be queried separately in the same way.Q SETFEED PPO

Query setting of p-points pen

8.7 DRAFT Element Pen Attributes

Having set up a pen definition, an element will be drawn in that style by assigning thepen number to the appropriate element attribute. For example (at a 2D draftingprimitive):

SETPEN 33 COL 4Assign colour 4 to pen 33

NLPN 33Set the element’s NLPN (note line pen) attribute to pen 33. The element willbe drawn in colour 4.

NLPN (note line pen) is an attribute of all 2D drafting primitives (STRA, RECT, CIRCetc, see Section 14). Note that NLPN may be set to OFF, which enables filled 2Dprimitives with no ‘edge’ to be drawn.The DRAFT element pen attributes are too numerous to list here, but a general rule isthat they all end in ‘PEN’ or ‘PN’. Most are used to draw lines, and as such may haveany or all of the representation attributes (except hatch pattern and marker type/scale)detailed in this Section assigned to them. Exceptions to this rule are:• FPEN (fill pen), an attribute of closed polyline 2D drafting primitives. Only colour

and hatch pattern definition are relevant to this attribute.For example:

SETPEN 200 COL 7 HPATT 6

FPEN 200Primitive will be filled with hatch pattern 6 in colour 7

Pens and Linestyles


Version 11.5

SETPEN 200 HPATT FILL

FPEN 200Primitive will be solid-filled with colour 7

• TPEN (text pen), DTPN (dimension text pen) and PTPN (projection text pen).These are text pens and as such only colour is relevant.


9 Reports, Circulation Lists and Revisions

This Section describes how to create the drawing office administrative elements ofreports and circulation lists, and how DRAFT handles revision numbers.

9.1 The Report

The Report (REPO) element may be used to contain brief textual information relatingto a full report (which would exist outside PDMS) on the owning drawing registry. Therelevant part of the DRAFT database is shown in Figure 9-1.

REGI

REPO

TEXT

Figure 9-1 Report Database Hierarchy

A Report has the attributes:• Circulation List Reference (CLRF) A reference to a circulation list element.

See Section 9.2.• Date. The report creation date• Source. The name of the macro which generated the report• Originator (ORNA. Text to describe the originator of the report• Filename (FLEN). The name of the file containing the report, as a text string• Title (TITL). A description of the report• Revision (RVSN). The revision number of the report

Reports, Circulation Lists and Revisions


Version 11.5

A typical creation sequence for a REPO might be:NEW REPOTITL ’REPORT ON VALVES IN ZONE 2’FLEN ’/REP-A-V’CLRF /PURCHASING

9.2 The Circulation List

DRAFT gives you the ability to store Drawing Circulation Lists. The relevant part of theDRAFT database is shown in Figure 9-2.

Library

CLLB

RECICIRL

RECI

DRWG

CLRF

CIRL

REPO

CLRF

Figure 9-2 Circulation List Database HierarchyThe Circulation List Library (CLLB) is an administrative element used to grouptogether Circulation Lists (CIRL), each of which is referred to from the CLRF(Circulation List Reference) attribute of a Drawing (or Report) element. Each CIRL maycontain other CIRL elements and/or Recipient (RECI) elements. A RECI has theattributes:• Recipient Name (RNAM)• Location (LOCA)• Number of Copies (COPI)



An example of setting up a Circulation List hierarchy might be:NEW CLLB

Create Circulation List Library (at Library level)NEW CIRL /CL1

Create Circulation ListNEW RECI /RC1

Create RecipientsRNAM ’Tom’

LOCA ’Room F21’

NEW RECI /RC2

RNAM ’Dick’

LOCA ’Room G24’

COPI 2

/DRWG DR1Set Circulation List Reference

CLRF /CL1

9.3 Drawing Revisions

The Revision (REVI) element enables you to store drawing revision data. A REVI maybe a member of a Drawing element or of a Sheet element, see Figure 9-3.

DRWG

SHEE REVI

REVI

CIRL

C LRF

Figure 9-3 The Revision Element

A REVI has the attributes:• Approver (APPR)



Version 11.5

• Date of Approval (APDT)• Revision (RVSN)• Revision text (STEXT)• Date of Revision (RVDT)• Revision Author (RVAU)• Circulation List Reference (CLRF)RVSN, RVDT and RVAU are all automatically set on REVI creation, but they can thenbe edited. The format of the date assigned to RVDT is controlled by the value of theDATEFOrmat attribute of the relevant DEPT.Pseudo reference array attributes SREVAY and DREVAY are available to return a listof the reference of all the REVI elements owned by a Sheet or Drawing. The maximumarray size is 50. The attributes are valid at any element of or below a Sheet or Drawingrespectively. They have been created primarily for use with hash codewords to generaterevision data on drawings, see Section 5.4, Part 2, Drawing Annotation.



Summary of Commands

At Circulation List . . .

RNAM text - set name of recipient

LOCA text - set location of recipient

COPI integer - set number of copies

At Revision . . .

APPR text - set name of approver

APDT text - set approval date

RVSN [text] - revision letter. Automatically set, but may be overridden

RVAU [text] - revision author. Automatically set, but may be overridden

CLRF name - set Circulation List (CIRL) reference


10 Change Highlighting

Change Rules control how Design and Annotation elements that have been changedare drawn on a DRAFT View and are similar to Representation Rules. Each ChangeRule can be specific to a given type or types of element, or named elements. ChangeRules refer to Change Styles, either Design Change Styles or Annotation ChangeStyles, depending on whether the changed element is a Design element or anAnnotation element. The attributes of the Change Styles define the way in whichchanged elements will be drawn. Generally this will be by altering the pen(s) used.Pieces of text may also have their font changed, be underlined, or be enclosed within aspecified style of parentheses. For more information about pens see Chapter 8. Forinformation about Representation Rules see Section 4.In order to determine whether Design and Annotation elements have changed, it isnecessary to compare the relevant databases at two points in time. One of these twopoints is always the current time. The other point used is a Comparison Date. Theconcept of Comparison Dates is discussed in Section 10.5.Design Change Rules (DCRULE) and Annotation Change Rules (ACRULE) arestored in Change Rulesets (CRST), which in turn are owned by RepresentationLibraries (RPLB).RPLBs are also used to store Design Change Styles (DCSTYL) and AnnotationChange Styles (ACSTYL). The reference from a DCRULE to a DCSTYL is made by itsDCSTYF attribute, and the reference from an ACRULE to an ACSTYL is made by itsACSTYF attribute. When a VIEW references a CRST, the reference is made by its CRSFattribute.

dcstyf

VIEW

RPLB

CRST

ACRULE DCRULE

RPLB

DCSTYLcrsf

acstyf

ACSTYL

Figure 10-1 Change Rules Database Hierarchy

Change Highlighting


Version 11.5

The hierarchy of database elements for Change Highlighting is similar to that forRepresentation and Auto-hatching and allows company or project standards to beimposed. However, unlike Representation and Hatching Rules, Change Rules cannot beowned directly by a VIEW and there are therefore no local change rules.Once the Rulesets and Styles have been set up, it is just a matter of setting the VIEWattribute CRSF to point to the Ruleset that you wish to use, defining a ComparisonDate, and issuing an UPDATE command with the SHOW CHAnges option (see Section10.6).

10.1 Design Change Styles

The Design Change Style (DCSTYL) defines the appearance of changed designelements specified by a DCRULE that references it. Each DCSTYL defines eight pensthat will be used to draw changed design elements. These eight pens are equivalent tothe six pens of a Representation Style plus the two pens of a Hatching Style. All eightpens may be set to; a pen number from 1 to 255, to OFF, or to UNCHANGED. If set toUNCHANGED, the relevant Representation or Hatching Style pen value will be used.Note that if any of the Representation or Hatching pens are set to OFF they will not beoverridden by the Design Change Style pen.The DCSTYL attributes, with their defaults, are as follows:

Frontface Pen FFPN Pen 76Backface Pen BFPN Pen 78Obscured Line Pen OBPN Pen 80Centreline Pen CLPN Pen 79P-line Pen PLNP Pen 77Member Line Pen MLNP Pen 79Fill Pen FPEN Pen 71Outline Pen OLPEN Pen 76

Note that DCSTYLs are not exact equivalents of Representation Styles, they do not haveTubing Flag (TUBEF), Drawing Level (DLEV), etc. attributes. The values of theseattributes are determined from the relevant Representation Styles. The DCSTYL onlydefines which, if any, of the standard pen values should be overridden in order thatchanged Design elements are marked.Design elements that have no DCSTYL assigned to them will not have any changes thatare made to them marked. Within a VIEW, it is therefore possible to mark changesmade to pipework, for example, but ignore changes made to steelwork.

Change Highlighting


10.2 Annotation Change Styles

An Annotation Change Style (ACSTYL) defines the appearance of changedannotation elements (Label, Dimension or 2D Primitives) specified by an ACRULE thatreferences it. Each ACSTYL defines three pens, a font, and two other attributes that willbe used to draw changed annotation elements. The three pens are used for drawing text,linear graphics and hatched areas of annotations. All three pens may be set to; a pennumber from 1 to 255, or to UNCHANGED. The font attribute may be set to a standardfont number or to UNCHANGED. If any of these four attributes are set toUNCHANGED, the relevant Label/Dimension/2D Primitives attribute will be used. Thetwo other attributes define whether changed text is to be underlined or enclosed inbrackets.The ACSTYL attributes, with their defaults, are as follows:

Text Pen TPEN Pen 71Line Pen NLPN Pen 71Fill Pen FPEN Pen 71Font Number FONT UNCHANGEDBrackets BRACKE NONEUnderline UNDERL OFF

Alternative values for BRACKE are; ROUnd, CURly, SQUare, ANGle.

10.3 Change Rules

The Change Ruleset (CRST) owns both Design Change Rules (DCRULEs) andAnnotation Change Rules (ACRULEs). Design Change Rules reference Design ChangeStyles and Annotation Change Rules reference Annotation Change Styles.

10.3.1 Design Change Rules

Design Change Rules use Selection Criteria to define the changed design elements towhich the rule is to apply, in a similar manner to Representation and Hatching Rules.The manner in which each changed design element is marked is defined by thereferenced Design Change Style. It is therefore possible to mark different types ofelements in different ways, or not at all.The DCRULE attributes, with their defaults, are as follows:

Design Change StyleReference

DCSTYF unset

Selection Criterion CRIT unset

Change Highlighting


Version 11.5

For more information on using Selection Criteria refer to Section 2.3.11 of theVANTAGE PDMS DESIGN Reference Manual, Part 1 General Commands.For changes to be highlighted properly the Selection Criterion should use one of thefunctions that make use of the current Comparison Date. These are; CREATED andMODIFIED. For example:

CRIT ALL BRAN MEM WITH (MODIFIED (GEOM))

CRIT ALL SCTN WITH (MODIFIED (LENGTH))

CRIT ALL EQUI WITH (CREATED ())

CRIT ALL WITH (CREATED ())

For more information on the CREATED() and MODIFIED() functions and their use inPDMS expressions refer to Section 2.3.11 of the VANTAGE PDMS DESIGN ReferenceManual, Part 1 General Commands.Note that a third function associated with the Comparison Date, DELETED(), is notrelevant here, deleted design elements will not be shown on DRAFT drawings and hencecannot be highlighted.

10.3.2 Annotation Change Rules

Changes to annotation graphics are treated in a simpler manner than changes to designgraphics. Annotation Change Rules have an attribute to determine whether they shouldbe applied to Changed Annotations, Added Annotations, or both.For Changed Annotations, only changes in expanded text strings will be marked. Forexample, a repositioned GLAB with BTEX '#NAME' that has moved because itsreferenced design element has moved will not be marked as changed. However, if itsBTEX was '#NAME at #POS' then the text string would be marked as changed. Thewhole expanded text string would be drawn in accordance with the referenced ACSTYL.Associated leader lines, dimension lines, projection lines, or any other graphic elements,would not be marked as changed.For Added Annotations, all elements associated with the annotation will be marked,that is, the expanded text string and all graphic elements.The ACRULE attributes, with their defaults, are as follows:

Annotation Change StyleReference

ACSTYF unset

Annotation Code ASCODE Changed

Each CRST therefore only needs to reference one or two ACRULES, one applicable toChanged Annotations, one applicable to Added Annotations. If more than one ACRULEis referenced for a type of changed annotation, only the first, in database order, will beapplied.

Change Highlighting


The syntax for the Annotation Change Rule Application attribute is:ASCODE ADDedanno, CHANgedanno, ADDed AND CHANged

10.4 Attribute Setting

The attributes FFPN, BFPN, CLPN, OBPN, PLNP, MLNP, FPEN, OLPEN, TPEN,NLPN and FONT all have the option of UNChanged. This is valid at DCSTYL andACSTYL elements only. Assigning UNChanged to these attributes at any other elementwill generate the following error message:

64,275: UNCHANGED is not valid at <type> elements

The syntax for the Change Highlighting Referencing attributes is:

DCSTYF UNSET or any DCSTYL

ACSTYF UNSET or any ACSTYL

CRSF UNSET or any CRST

Change Rules can also be defined with the USE command. For example:USE /anno-change-style-01 FOR CHANGEDANNO

USE /anno-change-style-04 FOR ADDEDANNO

USE /des-change-style-A FOR ALL EQUI WITH MODIFIED (GEOM HIER)

USE /des-change-style-B FOR ALL WITH MODIFIED()

For full details of using expressions in PDMS refer to Section 2.3.11 of the VANTAGEPDMS DESIGN Reference Manual, Part 1 General Commands.

10.5 The Comparison Date

It is only by comparing a drawing at two states or sessions that it is possible todetermine what has changed. Using the current state of the drawing as one state wemust then reference an earlier state in order to make the comparison. We do this byspecifying a Comparison Date (COMPDATE), that is, the drawing state at a time thatwe wish to use as a baseline or datum.The Comparison Date can be set in one of two ways:

• By specifying an actual time and date.

• By referencing a Stamp.

Change Highlighting


Version 11.5

For example:SETCOMPDATE 31 March 2002

SETCOMPDATE STAMP /Prelim-Milestone

The current Comparison Date can be queried by:Q COMPDATE DATE

Q COMPDATE STAMP

A Stamp is a way of referencing combinations of databases and sessions at specifiedinstances. Stamps are created by the PDMS Administrator. For more information onStamps and how they are created and used refer to the VANTAGE PDMS ADMINCommand Reference Manual and the VANTAGE PDMS ADMIN User Guide.The Comparison Date can be used in queries on any attributes, using the syntax OLD.For example:

Q OLD XLEN

will output the value of attribute XLEN of the current element at the Comparison Date.Q OLD REF OF /OLDPIPE

will output the reference of deleted element /OLDPIPE at the Comparison Date.For more information on the Comparison Date functionality refer to the VANTAGEPDMS ADMIN User Guide.

10.6 UPDATE Command, SHOW CHANGES Option andError Messages

The commands UPDATE DESIgn, UPDATE ANNOtation and UPDATE ALL have theoption SHOW CHAnges. In each case this option will update the picture to the latestrelevant data and VIEW attributes, including changes. This option is only valid at Viewelements or above. If no changes are found on the View, a message will be output toreassure the user that the SHOW CHAnges option has been properly evaluated.The following error conditions may be encountered when using the SHOW CHAngesoption:

• If the SHOW CHAnges option is given below View level, updating will proceed andthe following error message will be displayed:

64,444: The SHOW CHANGES option will be ignored when issuedbelow a View

• If no Comparison Date or Stamp is specified, updating will be abandoned and thefollowing error message will be displayed:

64,446: No current Comparison Date or Stamp defined. UPDATE SHOWCHANGES abandoned.

Change Highlighting


• If the View's CRSF attribute is unset, it is assumed that default Design andAnnotation Change Rules are to be applied. These are equivalent to the following:

USE /default-design-change-style FOR ALL WITH (MODIFIED())

USE /default-anno-change-style FOR ADDED AND CHANGED ANNO

where the defaults are equivalent to the following:

DEFAULT DESIGNCHANGE STYLE

DEFAULT ANNOTATIONCHANGE STYLE

FFPN 76 TPEN 71

BFPN 78 NLPN 71

OBPN 80 FPEN 71

CLPN 79 FONT Unchanged

PLNP 77 BRACKETS None

MLNP 79 UNDERLINE Off

FPEN 71

OLPEN 76

• If the View's CRSF attribute is invalid, updating will be abandoned and the followingerror message will be displayed:

64,64: <view-name>:CRSF attribute value is invalid

followed by the error message:64,153: <view-name>:Generation of Design (or Annotation or All)graphics abandoned

• If the CRSF references a CRST that contains no rules, updating will be abandoned and theollowing error message will be displayed:

64,445: <CRST-name>: No DCRULEs (or ACRULEs or Change Rules)defined


• If the CRSF references a CRST that contains no DCRULEs (with reference to anUPDATE DESI command), or no ACRULEs (with reference to an UPDATE ANNOcommand), updating will be abandoned and the following error message will bedisplayed:

64,445: <CRST-name>: No DCRULEs (or ACRULEs) defined

followed by the error message:

Change Highlighting


Version 11.5

64,153: <view-name>:Generation of Design (or Annotation or All)graphics abandoned

In this case if the command was UPDATE ALL and the CRST contains ACRULES butno DCRULEs (for example), then it is assumed that the user wants to produce adrawing on which only annotation changes are marked.• If the DCSTYF or ACSTYF attribute of a Change Rule is unset or invalid, updating

will be abandoned and one of the following error messages will be displayed:64,64: <rule-name>:DCSTYF (or ACSTYF) attribute value is invalid

64,65: <rule-name>:DCSTYF (or ACSTYF) attribute value unset


• If the CRIT attribute of a DCRULE is unset (with reference to an UPDATE DESI andan UPDATE ALL command), the following error message will be displayed:

64,296: Warning: <rule-name>: is invalid and will be ignored


10.7.1 Querying Change Rulesets and Design or Annotation Styles

The querying facilities are similar to those provided for RRULs. Thus, at a DCRULE oran ACRULE:

Q DESCriptionwill output a description for that rule with the format:

USE desi-change-style FOR criteriaUSE anno-change-style FOR ascode-value

At a CRST:Q DESCription

will output an ordered list of descriptions – one for each of its DCRULEs and ACRULEs.At a VIEW:

Q CRSF DESCriptionwill output an ordered list of rule descriptions , one for each owned by its referencedCRST.At a VIEW or CRST:

Q DCSTYF FOR design-id

Change Highlighting


will return the DCRULE that is relevant for the specified design item.

Change Highlighting


Version 11.5

Summary of Commands

At Design Change Rule . . .

USE stylename FOR crit - Set drawing style for Design generic types.

CRITeria crit - Set the CRIT attribute for the current rule.

At Design Change Style . . .

FFPN integerFFPN OFFFFPN UNCHANGED - Set pen number for drawing front face edges.

BFPN integerBFPN OFFBFPN UNCHANGED - Set pen number for drawing rear face edges.

OBPN integerOBPN OFFOBPN UNCHANGED - Set pen number for drawing front-facing edges of

Items that would otherwise be obscured by other objects.

CLPN integerCLPN OFFCLPN UNCHANGED - Set pen number for drawing centrelines.

PLNP integerPLNP OFFPLNP UNCHANGED - Set pen number for drawing p-lines.

MLNP integerMLNP OFFMLNP UNCHANGED - Set pen number for drawing member lines.

FPEN integerFPEN OFFFPEN UNCHANGED - Set pen number for hatching selected faces.

OLPEN integerOLPEN OFFOLPEN UNCHANGED - Set different pen number for drawing outline of

selected faces.

Change Highlighting


At Annotation Change Rule . . .

USE stylename FOR ADDED - Set drawing style for changed Annotations.

At Annotation Change Style . . .

TPEN integerTPEN UNCHANGED - Set pen number for annotation text.

NLPN integerNLPN UNCHANGED - Set pen number for drawing annotation linear graphics.

FPEN integerFPEN UNCHANGED - Set pen number for drawing annotation hatched areas.

FONT integerFONT UNCHANGED - Set annotation font.

BRACKE SQUAREBRACKE NONE - Set bracket style for enclosing text.

UNDERL ON - Set Underline ON for annotation text.

VANTAGE PDMS DRAFT User Guide A-1Part 1: Basic Drawing Creation & OutputVersion 11.5

A DRAFT Database Hierarchy

A.1 Basic Hierarchy

WORLD

LIBY DEPT

REGI

LIBY

REPO DRWG

TEXT

SHEE REVI

TEXT

NOTE VIEW

LAYE RRUL VSEC

HRUL

ADIM LDIM VNOT GLAB SLAB

:

:

(see overleaf)

(see overleaf)

(see overleaf)

(see overleaf)

REVIOLAY

TAGRPDIM RDIM

HRUL

NOTE: Automatically created `system' elements are not shown.

DRAFT Database Hierarchy

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

Version 11.5

Note: Automatically created system elements are not shown.

VANTAGE PDMS DRAFT User Guide B-1Part 1: Basic Drawing Creation & OutputVersion 11.5

B System Update Commands

B.1 Cross-Database Referencing

The functionality described in this appendix exists in order to minimise problems ofcross-database referencing when Design databases are deleted and rebuilt from macros.All DRAFT elements with DDNM, IDLN, or IDNM reference attributes also have‘system’ text attributes DDNX, IDLX, and IDNX respectively. These three attributes canbe queried but not set by the user.DRAFT will always use the DDNM, IDLN and IDNM attributes; values in DDNX, IDLXand IDNX will be ignored. Setting a DDNM, IDLN or IDNM attribute will also causethe associated ‘system’ text attribute (i.e. DDNX, IDLX and IDNX respectively) to be setto the name of the Design element referenced, so long as it is named.The following UPDATE commands exist to aid updating of a DRAFT database followingrebuilding of an associated Design database:

UPDATE element_identifier REFSUPDATE element_identifier NAMES

The first of these will change the DDNM, IDLN, and IDNM attributes ofelement_identifier, and all elements below it in the DRAFT database hierarchy, to matchthe values obtained from the associated text attributes. This means that if a Designdatabase is deleted and rebuilt then, so long as those elements referenced from DRAFTdatabases are all named, references in DRAFT databases can easily be kept up to date.The second command will change the DDNX, IDLX, and IDNX attributes to match thevalues obtained from the associated reference attributes. This option has been includedprimarily to allow a full set of these new text attributes to be generated for existingDRAFT databases. In each case no change will occur if a value cannot be obtainedfrom the name/reference encoding/decoding process. The element_identifier can beomitted, in which case the current element will be assumed.During the updating process warning messages will be output whenever an attribute ischanged or when DRAFT attempts to change an attribute but is unable to generate therequired name or reference to do so. These messages will be of the form:

VSEC 2 of /VIEW2: IDLN attribute updated to /ZONE1.PIPES

GLAB 1 of /D1/S1/V1/LAYER1: unable to update DDNX attribute

System Update Commands

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

Version 11.5

B.2 Updating Symbol Instances

The commandUPDATE INSTANCES

(valid at SHEE, BACK, OVER, SYLB, LALB or above) scans the database hierarchy andupdates all those parts of picture files which use the graphics ‘instancing’ mechanism.For example, a SYMB is an ‘instance’ of a SYTM. OLAY and BACK elements are in thesame category.

VANTAGE PDMS DRAFT User Guide C-1Part 1: Basic Drawing Creation & OutputVersion 11.5

C Picture File Naming Conventions

Picture file names incorporate the database reference and version number (PVNOattribute) of the picture element. Picture file names have the form:

M46-2107-20-13

where the first two numbers are the database reference of the picture element. The thirdnumber is the value of the EXFI attribute (which is normally the database/extract filenumber at the time the picture was saved). The final number is the picture versionnumber (PVNO attribute). This is incremented every time the picture is modified.Only those picture elements that may include design graphics (that is SHEEs andOVERs) have picture files. The graphics for other picture elements (LALBs, BACKs etc.)are created when required.The picture file name may be queried at the picture element (SHEE, OVER) using thecommand:

Q PICFilename

This returns the picture directory and file name, for example:%ABCPIC%/M46-2107-20-13

VANTAGE PDMS DRAFT User Guide D-1Part 1: Basic Drawing Creation & OutputVersion 11.5

D Guidelines for Importing DGN files fromDRAFT into MicroStation

D.1 Introduction

DRAFT drawings can be passed into MicroStation as DGN files. Various switches andrules are available in DRAFT to allow the DGN output to be configured as required.These notes refer only to MicroStation/J and the DGN files produced from DRAFT.A configuration can be defined which allows DRAFT DGN files to be imported into afreshly installed version of MicroStation/J with correct geometry, colours and styles.However, the fonts are not likely to be correct. These notes contain guidelines on how toproduce DGN drawings from DRAFT with the correct fonts, and how to improve otheraspects of the translation.

D.2 Exporting DRAFT drawings containing PDMS Fonts

PDMS is issued with a very large number of font files that have been assembled over along period from the public domain, in-house and the user community. They have allbeen translated to the AutoCAD standard and take the form of pairs of source (.shp) andcompiled (.shx) files.These notes discuss how to install these fonts into MicroStation in line with the originalDRAFT drawing. Experienced MicroStation users may know alternative ways of doingthis.Two alternative approaches are:• Use AVEVA’s Fontconverter utilities to create PDMS-compatible versions from

.shp versions of the fonts you wish to use in MicroStation

• Use MicroStation standard fonts similar to the PDMS fonts, and accept somedifferences in text output.

If you use DRAFT’s alternative character set for characters such as ¥ © ¼ or Ω you willneed to install AVEVA’s symbol font.It is not possible to install a 16 bit font (.SHX) fileinto Microstation/J or earlier.The set of PDMS fonts required in MicroStation is project dependent. The supplied fontresource file pdmsSamFont.rsc uses the PDMS fonts associated with the SAM project.Individual projects may have different fonts in use, so will require a different fontresource file. See section D.3.1 for instructions on how to create such resource files.

Guidelines for Importing DGN Files from DRAFT into MicroStation

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

Version 11.5

Font resource files should be installed alongside the corresponding MicroStation fontresource files, typically in

... \bentley\workspace\system\symb

pdmsSamFont.rsc uses particular MicroStation font numbers (201 to 207 for text fontsand 255 for the symbol font). These are mapped to DRAFT fonts using the MapFontswitch in DRAFT. It is possible that these font numbers may clash with fonts in otherfont resource files in use. If this happens, see section D.3.6 for instructions on how tomodify MicroStation font numbers.When you install additional fonts into MicroStation DRAFT needs additionalinformation on the font geometry to export the drawing. This is supplied as a set of fontgeometry files, fontNNN.dgn (where NNN is a MicroStation font number referred to inthe font resources file).These fontNNN.dgn files must be in either the current directory, or a directory accessedby the environment variable OPENDGN_FONT_DIR. This variableOPENDGN_FONT_DIR should be set to %PDMSEXE%\dgndata or wherever the fontgeometry files have been installed.Font geometry files are supplied for the fonts used in the SAM project. These correspondto pdmsSamFont.rsc and are supplied in the directory PDMSEXE%\dgndata. SectionD.3.7 contains instructions as to how to create further fontNNN.dgn files for other fonts.Section D.4 discusses how PDMS font numbers are mapped onto font file names. AllAVEVA fonts are supplied in the %PDMSEXE%\autodraftfonts directory, in AutoCADformat as .shx files.

D.3 Installing PDMS Fonts into MicroStation

To keep them separate the required fonts should be installed into a new font resourcelibrary called, for example, myfont.rsc, which should be placed with the supplied fontresource libraries, typically in the directory:


MicroStation refers to fonts by a number not by the name. PDMS fonts are supplied asAutoCAD .shx files as part of AutoDRAFT. These are supplied in the directory%PDMSEXE%\autodraftfonts (or another location).

Once fonts have been installed, they may be checked using the element/text menu. Thenewly installed fonts should be visible together with the font numbers assigned byMicroStation to the new fonts. If necessary, font numbers may be modified (see sectionD.3.6.).The font installation should follow the step-by-step procedure:

D.3.1 Creating a new Font resource library

(This step may be skipped if using an existing resource library)



Menu: Utilities>Install FontsButton: New (Rightmost window)

Navigate to the default font library areaEnter required library file name - e.g. myfont.rsc

Button: OK

D.3.2 Selecting .shx files to add to resource library

Button: Open (Leftmost window)Set Type to .shxNavigate to a AutoCAD .shx file areaSelect the required .shx files

Button: AddButton: Done

D.3.3 Selecting the library destination

Button: Open (Rightmost window)Navigate to default font library area (typically... \bentley\workspace\system\symb)

Select the required font resource library (.rsc file)

Button: OK

D.3.4 Copying the fonts into the library

In the leftmost window, select the required source files. Font details shouldappear.

Button: CopyButton: Done

D.3.5 Checking The Installation

Menu: Element>TextUse drop down or View to locate the font name



Version 11.5

The font number assigned by MicroStation is also visibleSelect to use for text

D.3.6 Changing MicroStation font numbers

Menu: Utilities>Install FontsButton: Open (rightmost window)

Navigate to the default font library area

D.3.7 Select the required .rsc library

Button: OKSelect the font name in the rightmost windowFont details appearThe font number and the description may be edited here.Font geometry files fontNNN.dgn must then be created to match the fontnumbers in the resource file.

D.3.8 Creating a new Font Geometry File

Font geometry files (or “magic font-files”) are used by DRAFT to export font geometryand alignment correctly to MicroStation. One of these files is required for each fontused. The MicroStation font number NNN is included in the name of these files. Thesefiles contain a set of instructions and various other text data. These files should not bemodified other than as described below, since the data in these files is required forDRAFT DGN output to work correctly.In order to create a font geometry file for a new font, open an existing font geometry file(a set of these is supplied in %PDMSEXE%\dgndata) and follow the instructions displayedthere. This involves using the MicroStation EDG utility to change the font used. (TheEDG utility is installed alongside MicroStation, for example in…\Bentley\Program\Edg\edg.exe.) The instructions in the fontNNN.dgn files arerepeated here.

To create an external font do the following:• Make sure you have made a copy of this design file.



• The new name must start with 'font' appended with the font number. (e.g.font186.dgn for MicroStation font number 186)

• Open this file in EDG first and type 'modify font=<n> whole' where <n> is thenew font number.

• Open this file in MicroStation and type 'mdl load fixrange' (Use Keyinoption).

• Compress and close the design file. (Use Compress on File menu)

• Place the file in a directory where it can be found by the OpenDGNkernel (which is used by DRAFT DGN output). Either this is either the currentdirectory or a directory accessed by means of an environment variable called'OPENDGN_FONT_DIR'.

We recommended that these fonts are placed in %PDMSEXE%\dgndata. If you needdifferent font resource libraries for different projects we suggest that you create sub-directories and point OPENDGN_FONT_DIR to the appropriate one for the project.

D.4 Mapping the Installed Fonts

PDMS fonts normally need the DRAFT export to use a font adjustment factor of 1.25,and a special adjustment when aligning text to the top of the body. This may beachieved by using the code p when mapping the fonts, e.g.

MAPFONT ‘11-16:201p’

For further details, see Section 7.4.

D.5 PDMS font file names

PDMS font file names follow a naming convention. This is described fully in AVEVA’sfont-building utilities, but is briefly summarised here.PDMS font families are defined by their IR (International Registration) number andStyle number in the system database. Font file names are of the form marrrtswuu,where m=0; a is the alphabet; rrr is the encoding; ts is the type and sub-type; w is theweight; and uu is a serial number. PDMS fonts are exported to AutoCAD as either filled(prefix f), or open (prefix of). All font-files have an 8-character equivalent short name:

Name IR Number Encoding(marrr)

Short code

Latin-1 1 01001 L1



Version 11.5

Latin-2 2 01002 L2

UK 4 01004 LB

Latin-Cyrillic 5 09998 CL

US 6 08901

(or 01006)

81

(or LA)

Greek 7 02018 GG

Cyrillic 8 03537 CR

SYMBOL - 09999 OP

Name PDMS Stylenumber

Font type(tswuu)

Bold Font type(tswuu)

Line 1 11901 -

Block 2 Outline 11203 Filled 11203

Serif 3 21191 21291

Italic 4 22191 22291

Script 5 31191 31291

Typewriter 6 21902 -

Uniform width 7 16901 -

Generally, PDMS uses the 8-bit Latin fonts (08901) instead of US fonts (01006), sincethese include US characters. Thus IR number 6 Style number 1 is font of0890111901(short name O8111901) ; IR number 4 Style number 3 is of0100421191 (short nameOLB21191), bold version of0100421291 (OLB21291).The fonts available in DRAFT are organised into four font families. Each font familyuses up to two font files to set up a range of six font numbers. For example, font family 3contains two font files to set up fonts 31-33 (normal, forward and back-slant) and theequivalent bold font 34-36.In addition, DRAFT uses a Symbol font for special characters (e.g. ~D gives the degreessymbol). The AVEVA SYMBOL font is of0999911901.shx (shortname OOP11901). Theequivalent filled font is f0999911901.shx (shortname FOP11901).To determine the font families used in a PDMS project, the following ADMIN commandshould be used:

Q FONTFamily

In typical Cadcentre projects, font family 1 is a line font; font family 2 is a block font;font family 3 is a serifed font and font family 4 an italic or typewriter font. Different



projects will use different fonts. The following font files are used in the SAM project andare set up in pdmsSamFont.rsc:

Font numbersin Project SAM

MicroStationFont Number(FontNNN.dgn)

Shortname Longname Description

11-16 201 O8111901.shx of0890111901.shx US Line

21-23 202 OLB11203.shx of0100411203.shx UK Block(Outline)

24-26 203 FLB11203.shx f0100411203.shx UK Block(Filled)

31-33 204 OLB21191.shx of0100421191.shx UK Serif

34-36 205 OLB21291.shx of0100421291.shx UK Serif (Bold)

41-43 206 OLB22191.shx of0100422191.shx UK HersheyComplex Italic

44-46 207 OLB22291.shx of0100422291.shx UKHersheyTriplexitalic

SYMBOL 255 FOP11901.shx f0999911901.shx PDMS Symbols

D.6 Colours

We supply a MicroStation colour table pdms_col.tbl, which contains colour definitionsmatching DRAFT’s default settings for Pens 1 to 16, and also for the other namedDRAFT colours. This may be installed in the MicroStation data directory alongside theBentley-supplied colour tables, typically at:

... \bentley\workspace\system\tablesYou may, if you wish, attach this colour table to a seed file or design file and set asuitable colour mapping, if you wish to match DRAFT colours as closely as possible.

D.7 Line Styles

AVEVA supplies a line style resource file containing definitions of MicroStation customline styles matching the proportions of DRAFT’s named line patterns. This may beinstalled in the MicroStation font directory alongside Bentley-supplied font resourcefiles, typically at:


VANTAGE PDMS DRAFT User Guide index-iPart 1: Basic Drawing Creation & OutputVersion 11.5

Index3D view direction, ............................. 3-11ADD command, .......................... 3-4, 3-20ADEG attribute,.................................. 3-9ALARM command,................... 2-14, 2-16ALPHA command, ............................ 2-14Arc tolerance, .................................... 3-12Arc tolerance (ATOL) attribute,....... 3-12AUTOSCALE command, .........................

.................. 3-2, 3-3, 3-5, 3-9, 3-12, 3-22BY command, ........................... 5-11, 5-14CHANGE ACTION command, 5-10, 5-13CLMO (Centreline Mode) attribute, .. 5-4Colours, default,.................................. 8-3CRIT command, ............4-12, 4-13, 10-10Databases

current status of, ............................. 2-2switching between, ........................ 3-19

DDNM attribute, ................................... 1DDNX system attribute,........................ 1DELETE command, ............................ 3-6DELETE NULL IDLI command, ............

................................................. 3-6, 3-24DELETE STEP command, ...... 5-11, 5-14Design elements

hatching, .......................................... 4-7DEVPEN command, ......................... 8-23DGN Output,..................................... 7-13DIR attribute,.................................... 3-10Direction

of View,........................................... 3-10

Displaypreserving

recovering, ...........................2-1, 2-16DLLB (Id List Library) element, ........3-4DRAFT

entering, .........................................2-16DRAFT command,.............................2-16Drawing (DRWG) element,.................3-1DTPN (Dimension Text Pen) attribute,8-

26DXF output

scaling,..............................................7-4Enclosed planes, ..................................5-1ERASE command, ....................5-12, 5-15Explicit mode

multiwrite DBs,................................2-5Extracts, ..............................................2-7

master,..............................................2-7Flat Plane (FPLA) element,.........5-1, 5-7FPEN (fill pen) attribute, .................8-25FPLA element,.....................................5-7FRPO (From Point) VIEW attribute, ......

........................................................3-11GETWORK command, ...............2-2, 2-16Global hidden line views,..................3-16Glyphs,.................................8-1, 8-7, 8-12Grid

snapping to, ......................................6-4GTYP attribute,..........................5-8, 5-13Hatch pattern, ............................8-1, 8-16

in automatic hatching,...................4-10

Index

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

Version 11.5

Hatch Patternspredefined,......................................8-16user-defined,...................................8-17

Hatchingautomatic,.........................................4-7

Hatching Rules, ...................................4-8Hidden lines,......................................3-13HIGHLIGHT command, .....................6-6HPATTERN command,.....................8-17Id List

cleaning up, ......................................3-6querying,...........................................3-7

Id List Library (DLLB) element, ........3-4Id List Name (IDLN) attribute,...3-3, 5-3Id lists

querying,...........................................3-7IDLI (Id List) elements, ......................3-4IDLN attribute, ...................................... 1IDLX system attribute, .......................... 1IDNM attribute, ..................................... 1IDNX system attribute, ......................... 1Implicit mode

multiwrite DBs,................................2-5INSTALL SETUP command,.....2-1, 2-16Interrupt key, ......................................3-3LFRA attribute,...................................3-7Limits

of view,..............................................3-6Line colour, ..........................................8-1Line pattern,.................................8-1, 8-5Line picture, ........................................8-1Line pictures

predefined,......................................8-12

user-defined, ...................................8-15Line thickness,............................. 8-1, 8-5Linestyles, ............................................8-1LIST command, ......................... 2-3, 2-17Local hidden lines,.............................3-15Local Rules,..........................................4-7Looking direction, ..............................3-10

controlling,......................................3-10LTHICKNESS keyword, .....................8-5LVIS (Layer Visibility) attribute, .....3-24Marker type, .............................. 8-1, 8-15Master database

of extract, ..........................................2-7MDB command, .................................2-17MDB mode, ..........................................2-4MLNP (Member line pen) attribute,...4-4Modelled wireline view,.....................3-14Multiple database,...............................2-4NLPN (note line pen) attribute,........8-25NORM attribute, .............. 5-7, 5-11, 5-13Omitting, ..............................................4-5ON command, ......................................6-3Orientation

view contents, ...................................3-9Pen attributes

use of to define representation style, ...............................4-2, 10-2, 10-3, 10-4

Pen numbers, .......................................8-1Pen settings

querying, .........................................8-25Perpendicular Flat Plane (PPLA)

element, .................................... 5-1, 5-4PERS attribute, .................................3-10Perspective, ........................................3-10

Index

VANTAGE PDMS DRAFT User Guide index-iiiPart 1: Basic Drawing Creation & OutputVersion 11.5

controlling, ..................................... 3-10Picture files, ........................................... 1Plane editing, ........................... 5-11, 5-14Plane querying, ................................. 5-15Plane retained/discarded side

determining,................................... 5-15switching, ....................................... 5-13

Plane sketching,....................... 5-12, 5-15Planes Library (PLLB) element, ........ 5-3Planes, erasing,........................ 5-12, 5-15PLLB element, .................................... 5-3PLMP (P-line pen) attribute, ............. 4-4PLOT command, ................................. 7-1Plotfiles

size,................................................... 7-2PLOTPEN command, ....................... 8-23PLRF (Plane Reference) attribute, .........

........................................5-3, 5-11, 5-14PMOD (Plane Mode) attribute, . 5-3, 5-14POS attribute, .... 5-4, 5-7, 5-8, 5-11, 5-13Position

converting 2D/3D,............................ 6-4PPLINE command, ............................. 6-3PPOINTS command,........................... 6-2Project, current status of, ................... 2-3PTPN (Projection Text Pen) attribute, ...

........................................................ 8-26Querying

Id Lists, ............................................ 3-7spatial map, ..................................... 3-7view contents, ................................ 3-18view direction,................................ 3-11

QUIT command,................................ 2-16RCOD (rotation code) attribute,....... 3-10

Recipient (RECI) element, ..................9-2Recipient name (RNAM) attribute, .........

...................................................9-2, 9-5RECREATE command, ..............2-1, 2-16Registry (REGI) element, ...................3-2REMOVE command, ..................3-4, 3-20Remove Entry (REME) element, ........3-4Report (REPO) element, .....................9-1Representation Rules

Querying,........................................4-11Setting up, ...............................4-5, 10-3

Representation Ruleset Reference(RRSF) attribute, . 3-11, 3-23, 4-7, 10-2

Representation Styleassigning,.................................4-5, 10-3

Representation Style (STYL) element, ....................................................4-2, 10-2

Revision element, ................................9-3Rubber banding, ................................8-24Rubber banding colour,.....................8-24Rules

in defining IDLists, ..........................3-5SAVEWORK command,.............2-1, 2-16Scale, of view, ......................................3-9Selective styles, ...................................4-6SETFEEDBACK command, .............8-24SETPEN command, ..........................8-23Sheet (SHEE) element, .......................3-1SIZE attribute, ....................................3-8SKETCH command, .................5-12, 5-15SMOD (Section Mode) attribute, ........5-4SNAP command, .................................6-4Spatial map

use of by ADD WITHIN command,.3-6

Index

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

Version 11.5

SPLA element,.....................................5-8STATUS command,....................2-2, 2-17STEP command, ............... 5-9, 5-10, 5-13Stepped Plane (SPLA) element, ..5-1, 5-8Styles, selective allocation, .................4-6SWITCH command, ..........................3-19SYSTAT command, ....................2-3, 2-17THPO (Through Point) VIEW attribute,

........................................................3-10TPEN (Text Pen) attribute, ..............8-26TRACE command, .............................2-14Universal representation, .................3-16UPDATE ALL command,..................3-21UPDATE ANNO command,..............3-21UPDATE DESIGN command, .................

....................................... 3-3, 3-11, 3-21UPDATE INSTANCES command, ........ 2UPDATE NAMES command, ................ 1UPDATE PICTURE command, ........3-21UPDATE REFS command, .................... 1USE command,....................................4-6Users

current status of,..............................2-2VGRID command, ...............................6-5VIEW

orientation of on Sheet,..................3-10View centre, .........................................3-8

View contentsquerying, .........................................3-17

View contents orientation, ..................3-9View direction, ...................................3-11View frame, ..........................................3-7View Gap (VGAP) attribute, .............3-12View gap length, ................................3-12View limits, ..........................................3-6View ratio,............................................3-9View scale,............................................3-9View Section (VSEC) element,.. 5-3, 5-11View size, .............................................3-8View type,...........................................3-13Views

querying, .........................................3-18VRAT attribute, ...................................3-9VREGION command, ................ 3-8, 3-22VSCALE attribute, ..............................3-9VTYP (View type) attribute, .............3-13Warning Messages,............................2-14Wireline views, ..................................3-13WPOS element,..........5-8, 5-9, 5-11, 5-13XYPS attribute, ...................................3-8Z-coordinates

in DXF files,......................................7-3

PDMS Draft Part 1 Basic Drawing Creation & Output

Documents

Transcript of PDMS Draft Part 1 Basic Drawing Creation & Output