TRAINING GUIDE
AVEVA Plant
(12.1)
Project Drawing
Administration
TM-1302
Revision Log
Date Revision Description of Revision Author Reviewed Approved 13/03/2012 0.1 Issued for Review PDMS 12.1.SP2 SB/BT
25/03/2012 0.2 Reviewed SB/BT KB/SS
02/04/2012 1.0 Approved for Training PDMS 12.1.SP2 SB/BT KB/SS NG
Updates
All headings containing updated or new material will be highlighted.
Note: Highlighting will not be employed at Revision 1.0 due to significant alterations to training material warranted by release of PDMS 12.1.
Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers, please report it to AVEVA Training & Product Support (TPS) at [email protected]
This manual provides documentation relating to products to which you may not have access or which may not be licensed to you. For further information on which products are licensed to you please refer to your licence conditions.
Visit our website at http://www.aveva.com
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
www.aveva.com
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not be liable for any breach or infringement of a third party's intellectual property rights where such breach results from a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or logo belongs to its respective owner.
Contents
www.aveva.com
1 Introduction ... 11 1.1 Aim... 11 1.2 Objectives ... 11 1.3 Prerequisites ... 11 1.4 Course Structure ... 111.5 Using this guide ... 12
2 PDMS Draft Features ... 13
2.1 General ... 13
2.2 Automatic Drawing Production (ADP) ... 13
2.3 AutoDraft ... 14
2.4 Draft Administration ... 14
3 Project Drawing Administration Training Workflow ... 15
4 Getting started with PDMS Draft ... 21
4.1 Entering a Draft Session ... 21
4.2 Default Load Errors... 22
4.3 Draft Sample Data ... 23
4.4 Loading Draft Sample Data via Forms & Menus ... 24
4.5 Loading Draft Sample Data using the Command Line ... 24
4.6 Referencing Draft Sample Data ... 25
Exercise 1 Starting PDMS Draft ... 26
5 Administrative Rights ... 27
5.1 Draft Administrative Rights ... 27
5.2 Draft Defaults ... 27
5.3 Draft User Defaults (Training Setup) ... 28
5.4 Draft System Defaults ... 29
5.4.1 File Menu Options ... 29
5.4.2 Library Reference Pointers ... 30
5.4.3 Element Name Delimiters ... 31
5.4.4 Layer Purpose Definitions ... 31
5.4.6 Layer Creation Definitions – A Worked Example ... 34
5.4.7 Layer Purpose Filtering – A Worked Example ... 34
5.4.8 Sheet Sizes – A Worked Example ... 35
5.4.9 Naming Conventions ... 35
Exercise 2 Draft Administration Defaults ... 36
6 Drawlist Library ... 37
6.1 Entering Drawlist Library Administration Mode ... 37
6.2 Creating a Drawlist Library ... 38
6.3 Creating and modifying a Drawlist ... 38
6.3.1 Selecting a Drawlist Library & Drawlist ... 39
6.3.2 Creating a Drawlist ... 39
6.3.3 Deleting a Drawlist ... 40
6.3.4 Defining Drawlist Members ... 40
Exercise 3 Drawlist Library ... 41
7 Sheet Libraries ... 43
7.1 Entering Sheet Library Administration Mode ... 43
7.1.1 Creating a Sheet Library – A Worked Example ... 44
7.1.2 Creating a Backing Sheet & Content – A Worked Example ... 45
7.2 Restricting the Useable area of a Sheet – A Worked Example ... 48
7.3 Creating an Overlay & Content – A Worked Example ... 50
7.3.1 Drawlist & Drawlist Reference ... 51
7.3.2 Creating Views in Overs ... 51
7.3.3 Key Plan Design Areas ... 54
Exercise 4 Sheet Libraries ... 56
8 Symbol Libraries ... 57
8.1 Entering Symbol Library Administration Mode – A Worked Example ... 57
8.2 Creating a Symbol Library – A Worked Example ... 57
www.aveva.com
8.4 2D Symbolic Representation Administration ... 62
8.4.1 Project Structure and Distribution ... 62
8.4.2 Draft Symbol Sets – A Worked Example ... 62
8.4.3 Non-uniformly Scaled Design Symbols ... 65
8.4.4 Orientating Design Symbols ... 65
Exercise 5 Symbol Libraries ... 66
9 Label Library Administration ... 67
9.1 Entering Label Library Administration Mode ... 67
9.2 Creating a Label Library – A Worked Example ... 67
9.3 Creating Symbol Templates – A Worked Example ... 69
9.3.1 Adding Annotation via a Backing Sheet ... 70
9.4 Creating Text Templates – A Worked Example ... 71
9.5 Searching Label Libraries ... 72
Exercise 6 Label Libraries ... 73
10 Style Libraries ... 75
10.1 Entering Style Library Administration Mode ... 75
10.2 Creating a Style Library – A Worked Example ... 75
10.3 Creating and Deleting Styles ... 77
10.3.1 Creating a Style – A Worked Example ... 77
10.3.2 Deleting a Style ... 77
10.3.3 Listing Style Attributes ... 78
10.3.4 Setting Style Attributes ... 78
10.3.5 Draft Line Widths ... 80
10.4 Creating a Hatching Library – A Worked Example ... 80
10.5 Creating and Deleting Hatching Styles ... 81
10.5.1 Creating a Hatching Style ... 81
10.5.2 Deleting a Hatching Style ... 82
10.5.3 Setting Hatching Style Attributes ... 82
10.6 Creating a Change Style Library – A Worked Example... 86
10.7 Creating and Deleting Change Design Styles ... 87
10.7.1 Creating a Design Change Style – A Worked Example ... 87
10.7.2 Deleting a Change Design Style ... 88
10.7.3 Listing Change Design Style Attributes ... 88
10.7.4 Setting Change Design Style Attributes ... 88
10.8 Creating a Annotation Change Style Library – A Worked Example ... 89
10.9 Creating and Deleting Annotation Change Styles ... 90
10.9.1 Creating a Annotation Change Style – A Worked Example ... 90
10.9.2 Deleting a Annotation Change Style ... 91
10.9.3 Listing Style Attributes ... 91
10.9.4 Setting Change Style Attributes ... 91
Exercise 7 Style Libraries ... 93
11 Representation Rules ... 97
11.1 Entering Style Library Administration Mode ... 98
11.2 Creating a Representation Library – A Worked Example ... 98
11.3 Creating and Deleting Representation Rules ... 99
11.3.1 Creating a Rule ... 99
11.3.2 Deleting a Rule ... 100
11.3.3 Specifying the Elements to which Rules Apply ... 100
11.3.4 Associating Representation Rules with Styles ... 101
11.4 Creating a Hatching Library – A Worked Example ... 101
11.5 Creating and Deleting Hatching Rules – A Worked Example ... 102
11.5.1 Creating a Rule ... 102
11.5.2 Deleting a Rule ... 103
11.5.3 Specifying the Elements to which Rules Apply ... 103
11.5.4 Associating Hatching Representation Rules with Hatching Styles ... 104
11.6 Creating a Change Rule Library – A Worked Example ... 105
11.7 Creating and Deleting Change Rules – A Worked Example ... 106
11.7.1 Creating a Rule ... 106
11.7.2 Deleting a Rule ... 107
www.aveva.com
11.7.4 Specifying the Annotation to which Annotation Rules Apply ... 107
11.7.5 Applying Restrictions for Design Change Rules ... 107
11.7.6 Associating Change Representation Rules with Change Styles ... 108
Exercise 8 Representation Rules ... 109
12 Tag Rule Libraries ... 113
12.1 Entering Auto Tagging Administration Mode ... 113
12.2 Creating a Tag Rule Library – A Worked Example ... 113
12.3 Creating and Deleting Tag Rule Sets ... 114
12.3.1 Creating a Tag Rule Set – A Worked Example ... 114
12.3.2 Deleting a Tag Rule Set ... 115
12.4 Creating and Setting Up Tag Rules ... 115
12.4.1 Viewing Tag Rules ... 115
12.4.2 Specifying the Elements to which Rules Apply ... 115
12.4.3 Creating a Tag Rule – A Worked Example ... 116
12.4.4 Deleting a Tag Rule ... 116
12.4.5 Criteria for Tag Rule Application – A Worked Example ... 116
12.4.6 Associating a Label Template with a Tag Rule – A Worked Example ... 116
12.4.7 Associating a Drawlist with a Tag Rule ... 117
Exercise 9 Tag Rules ... 119
13 Database Updates ... 121
13.1 Updating Picture Files ... 121
13.2 Updating Template Instancing ... 121
13.3 Updating Cross-DB Reference Attributes ... 121
13.4 Updating Cross-DB Name Attributes ... 121
14 Plotting and Printing Options ... 123
14.1 AVEVA-Plot Service ... 124
14.3 PlotViewer ... 125
14.4 Plotting using Plot ... 125
14.4.2 Example HPGL2 soft driver with Pen Thickness Support ... 126
14.6 Other Output Formats... 127
14.7 Other Plotting Options ... 128
14.8 Saving Plot Options ... 128
14.9 Print ... 128
Exercise 10 Plot Options ... 128
15 Automatic Drawing Production (ADP) Administration ... 131
15.1 General ADP ... 131
15.2 Setting the ADP Defaults – A Worked Example ... 132
15.3 Type 1 Annotation (Pipe) – A Worked Example ... 133
15.3.1 General Settings... 134
15.3.2 Layer Purpose ... 135
15.3.3 Dimension Rules ... 135
15.3.4 Projection Line Text Settings ... 136
15.3.5 Checking Pipe Zone Settings for Type 1 Annotation ... 136
15.4 Type 2 Annotation (Equipment) – A Worked Example ... 137
15.4.1 General Settings... 138
15.4.2 Layer Purpose ... 138
15.4.3 Dimension Rules ... 138
15.4.4 Projection Line Text Rules ... 139
15.4.5 Checking Equipment Zone Settings for Type 2 Annotation ... 139
15.5 Type 3 Annotation (Gridlines) – A Worked Example ... 139
15.5.1 General Settings... 140
15.5.2 Layer Purposes ... 140
15.5.3 Dimension Rules ... 140
15.5.4 ‘X/Y–Axis’ Projection Line Text Rules ... 141
15.5.5 Checking Steelwork Settings for Type 3 Annotation ... 141
15.6 General ADP Defaults ... 141
15.6.1 Representation ... 142
15.6.2 Add / Remove Volume Drawlist Rules ... 143
15.7 Schedules ... 143
www.aveva.com
15.8.1 Changing the Tagging Rule Library ... 144
15.9 Creating a Tagging Library ... 144
15.10 Creating a Schedule Library – A Worked Example ... 145
15.10.1 Creating a New Schedule... 147
15.10.2 Creating a New Tagging Rule ... 149
15.10.3 Set and save the ADP Defaults ... 151
15.11 Backing Sheet Controls ... 152
15.11.1 Reference Drawings ... 152 15.11.2 Sheet Limits ... 153 15.11.3 Schedules ... 153 15.11.4 Keyplan... 154 15.11.5 Title ... 154 15.11.1 Logo ... 154 15.11.2 Frame ... 155 15.11.3 Summary ... 155
15.12 Steelwork Detailing ADP ... 155
15.13 SDA Options ... 156
Exercise 11 ADP Drawings ... 158
16 AutoDRAFT Administration ... 159
16.1 Updating the PDMS Batch File ... 160
16.2 Configuring AutoCAD for use with AutoDRAFT – A Worked Example ... 160
16.3 Accessing AutoDRAFT Administration ... 161
16.4 Starting the Symbol Editor - A Worked Example ... 161
16.5 Drawing Symbols in AutoCAD – A Worked Example ... 163
16.6 Starting the Frame Editor – A Worked Example ... 166
16.6.1 Backing Sheets in AutoCAD ... 167
16.7 Importing Symbols and Backing/Overlay Sheets – A Worked Example ... 167
Exercise 12 AutoDraft ... 169
17 Isometric Administration ... 171
17.1 Entering Style Library Administration Mode ... 171
17.2 Entering an Isodraft session ... 171
17.3 Isometric Option Files ... 172
17.3.1 Company Option Files ... 172
17.3.2 Project Option Files ... 173
17.4 Creating a Standard Isometric Project Option File – A Worked Example ... 173
17.5 Drawing sheet layout ... 175
17.6 Administrative Options – A Worked Example ... 176
17.6.2 Using True Type Fonts on Isodraft Output files ... 179
17.7 Sheet Layout Options – A Worked Example ... 181
17.7.1 Size/Stacking ... 181
17.7.2 Graphics ... 181
17.7.3 Specifications ... 183
17.7.4 Flow Arrows and Margins ... 183
17.7.5 Reserved Areas... 183
17.8 Dimensioning Options – A Worked Example ... 185
17.8.1 Units ... 185
17.8.2 Dimensions ... 186
17.8.3 Skew Box ... 187
17.8.4 Tapping Branches ... 188
17.9 Annotation Options – A Worked Example ... 189
17.9.1 Whitespace Search ... 190
17.9.2 Item Codes ... 190
17.9.3 Coordinates ... 190
17.9.4 Keys ... 190
17.10 Material List – A Worked Example ... 191
17.10.1 Options ... 191
17.10.2 Detail Texts ... 192
17.10.3 Item Codes ... 192
17.10.4 Bolting... 192
www.aveva.com
17.10.6 Material List File ... 193
17.11 Material Columns ... 193
17.12 Weld Numbering ... 195
17.13 Pipe / Spldrg Attribute Table – A Worked Example ... 196
17.14 Revision Table – A Worked Example ... 197
17.15 Bend Table and File ... 197
17.16 Reports and Symbol File ... 198
17.17 Title block... 199
17.18 Attribute Frame Texts ... 200
17.19 Standard Texts ... 201
17.19.1 Using True Type Fonts on Isodraft Output files ... 201
17.19.2 Typical Option File Including a Backing Sheet ... 202
17.20 Component Tags ... 202 17.21 Detail Plots ... 203 17.22 ... 205 17.23 Compipe Interface ... 206 17.24 Alternative Texts ... 206 17.25 IDF Processing ... 207 17.26 Change Highlighting ... 207
Exercise 13 IsoDraft Administration ... 209
18 IsoDraft Symbol Libraries ... 211
18.1 Entering Isometric Symbol Library Administration Mode ... 212
18.2 Creating an Isometric Symbol Library – A Worked Example ... 212
18.3 Creating IsoDraft Symbol Templates – A Worked Example ... 213
18.3.1 Drawing the Isometric Symbol ... 214
18.3.2 Exporting the ISODRAFT Symbol ... 214
18.3.3 Importing ISODRAFT Symbols ... 216
18.3.4 Typical Isodraft Symbol Definition File ... 217
Exercise 14 Isodraft Symbol Libraries ... 218
Appendix A Draft Defaults ... 219
www.aveva.com
CHAPTER 1
1
Introduction
PDMS Draft is the AVEVA Plant Drawing Production and Annotation Module. The Drawing created using PDMS Draft is populated with information taken directly from the Design or Draft Databases. This associated intelligence ensures the drawing accurately reflects the intended design and updates automatically to reflect any Design Changes.
This Training Course is designed for PDMS Administrators to understand the basics in administering Project Drawing Production and Isometric Production using PDMS.
1.1 Aim
In completing the Project Drawing Administration course, participants will learn the general principles of administration for customising the Draft working environment; enabling users to work more quickly and more effectively.
1.2 Objectives
Through the completion of the training, the Trainee will have sufficient knowledge to complete the following tasks:
To understand the different types of administrative libraries.
To be able to create and edit standard libraries.
To be able to create and edit symbolic and general labels.
To be able to create and edit backing sheets.
To be able to create and edit representation rule sets.
To be able to create and edit change highlighting rules.
To be able to configure and customise Automatic Drawing Production.
To be able to create transfer symbols and backing sheets using the AutoDRAFT / AutoCAD interface.
To be able to configure and customise Isometric Production and Symbols.
Chapter 3 provides a more detailed training outline, together with the training outputs expected of participants.
1.3 Prerequisites
Trainees must have attended the AVEVA Plant Drawing Production (Basic) and (Advanced) courses and be familiar with Microsoft Windows. It is preferable for the Trainee to have completed the Basic System Administration course or have an understanding of the Administration principles of PDMS.
1.4 Course Structure
Training will consist of oral and visual presentations, demonstrations and set exercises.
Each workstation will have a training project, populated with model objects. This will be used by the trainees to practice their methods, and complete the set exercises.
www.aveva.com
1.5 Using this guide
Certain text styles are used to indicate special situations throughout this document, here is a summary; Menu pull downs and button press actions are indicated by bold dark turquoise text.
Information the user has to key-in will be in bold red text.
Where additional information is presented, or reference is made to other documentation the following annotation will be used:
Additional information Refer to other documentation
System prompts will be bold, italicised, and presented in inverted commas i.e. 'Choose function'. Example files or inputs will be in the courier new font.
www.aveva.com
CHAPTER 2
2
PDMS Draft Features
The Draft module within PDMS allows the designer to generate fully annotated engineering drawings directly from data in the PDMS Design model. Furthermore, the Draft module allows drawings to be easily updated to reflect design model changes.
Chapter 2 outlines the facilities that may be utilised within Draft to produce drawings.
2.1 General
The Draft Graphical User Interface (GUI) has been designed to allow the User to generate and retrieve industry standard engineering drawings efficiently. The following features of Draft aid the drawing production process:
The designer can add dimensioning and other annotations with information taken directly from the design model.
The Draft drawing can be created with any view angle and the representation of the drawing graphics is controlled by representation rules that are pre-defined by the project administrator.
Various levels of wireline and hidden line removal views can be used. Sectional views can be generated by the creation of flat or stepped section planes.
The scale of the drawing can be selected from a set of Metric, Architectural and Engineering values, with the option of an automatic scale selection to use the largest appropriate scale.
A label can be attached to any design element and used to display any attribute of the design element. The format, content and appearance of the labels are controlled by the designer. Direct reference to the design data, combined with a simple update operation, ensures that the annotation always reflects the current state of the design model.
The ability to employ Autotagging is a quick solution for automatically generating labels that match a tagging rule. The rule determines the type of label and the design items the labels will be applied too.
A dimension is calculated directly from the design model, the Designer can control the format, content and appearance of the dimensions. As with labelling, direct reference to the design data ensures that the annotation always reflects the current state of the design model with a simple update operation.
2D drafting allows the designer to generate additional 2D annotation and graphics to form drawings. As with other Draft data, 2D annotation can be linked to design data and can be updated to follow the changes that occur in the design model.
For further information, refer to TM-1002 Drawing Production (Basic)
2.2 Automatic Drawing Production (ADP)
As the title of the application infers, this aspect of Draft enables the Designer to produce annotated drawings automatically. A set of rules determine how the annotation is generated. The drawings can be edited, if necessary, using the normal editing options in Draft. There are a number of ADP applications for different disciplines.
www.aveva.com
AVEVA PDMS Area Based Automatic Drawing Production enables standard production drawings, complete with annotation, to be automatically generated based on engineering disciplines and Plant areas. Refer to TM-1206 Drawing Production (Advanced)
Refer to TM-1209 Area Based Automatic Drawing Production
Refer to TM-1305 Area Based Automatic Drawing Production Administration
2.3 AutoDraft
This facility imports drawings directly from Draft into AutoCAD. However, it should be noted that once this action is done, the drawing in AutoCAD has no direct link to the design model or data – thereby not allowing drawing updates to occur from the PDMS design model.
Symbols and drawing frames can be exported from AutoCAD directly into Draft. Refer to TM-1206 Drawing Production (Advanced)
2.4 Draft Administration
The core part of this training relates to Draft Administration. Using this application, the Project Administrator is able to specify and customise the Draft environment. This includes setting default attribute values, creating drawing frames (commonly referred to as backing sheets), symbols and labels. The Administrator will also set the representation rules, labelling rules, naming conventions, line styles, hatch patterns and available symbols.
The Administration Option is only available to Free Users or Members of the DRAFTADMIN Team. To facilitate the above Administrative functions there are a number of administrative applications within Draft. These applications can be used to customise and configure the Draft environment to company or project standards. These applications are: General Administration.
Sheet Libraries: Contain Backing sheets and Overlays for use on a project.
Symbol libraries: Contain 2D symbols.
Isodraft Symbol Libraries: Contain symbols to be used on IsoDraft isometric drawings.
Label Libraries: Contain Symbolic and General Labels.
Style libraries: Contain drawing styles for use in conjunction with representation rule sets.
Representation Libraries: Contain Drawing representation rule sets.
Drawlist Libraries: Contain standard Drawlists.
Tagging Rules: Contains tag rules and tag rule sets.
Automatic Drawing Production.
AutoDraft – AutoCAD Interface.
In addition to the above, there are a number of default files, which are used to set the default attributes of Draft database elements and define the libraries available to the general user.
www.aveva.com
CHAPTER 3
3
Project Drawing Administration Training Workflow
Chapter 3 highlights the expected training outputs in undertaking the Project Drawing Administration training course and acts as a quick–reference guide to Draft Administration tasks.
The Training workflow will follow the Administrative workflow in creating the necessary ‘ingredients’ for Drawing production i.e. Backing Sheet creation through to Representation and Styles that may be utilised. The Drawing image presented at each workflow stage illustrates how each Administrative task may be reflected in the final produced drawing.
The course will also highlight Administrative tasks associated with Automatic Drawing Production and, the AutoDraft and IsoDraft applications.
3.1 Training Workflow Overview
1. Create Reference Drawlists
Drawlist Libraries (DLLB) contain a group of Drawlists (IDLI or ID Lists) which allow users to create lists of design elements to be drawn or sectioned.
The DLLBs and IDLIs can be assigned to design items according to design disciplines, project areas, or any other classifications appropriate to specific working practices.
Drawlist creation is regarded as the first administrative task in the training due to drawlist requirement for overlay / Keyplan creation. Refer to Chapter 6 for information on Drawlist Library creation.
WO
R
K
FL
O
W
www.aveva.com
2. Create a Sheet Library: Backing Sheet & Overlay
A key task for the Draft Administrator is to set up Sheet Libraries (SHLB) containing the Backing Sheets (BACK) and Overlay Sheets (OVER). These sheet libraries will be referenced by the general user on creation of Drawings and Views.
Refer to Chapter 7 for information on the creation of Sheet Libraries.
3. Create a Symbol Library
Symbol Libraries (SYLB) contains the Symbol Templates (SYTM) from which users can select 2D symbols to add to their drawings. Each SYTM may comprise any combination of 2D primitives, text primitives (TEXP) and existing symbol instances (SYMB).
Refer to Chapter 8 for information on Symbol Library creation.
WO
R
K
FL
O
W
www.aveva.com
4. Create a Label Library
A key administrative task is to set up Label Libraries (LALB) containing the Symbol Templates (SYTM) and Text Templates (TXTM) from which users can create symbolic (SLAB) or general (GLAB) labels respectively.
Refer to Chapter 9 for information on the creation of Label Libraries.
5. Create a Style Library & Representation Rules
WO
R
K
FL
O
W
www.aveva.com
It is required of the Draft Administrator to set up Styles (STYL) withinRepresentation Libraries (RPLB); these define the detailed representation the general user will use for various aspects of the drawing.
The Administrator will also be required to create the following:
Representation Rulesets (RRST) and Representation Rules (RRUL).
Hatching Rule Sets (HRST) and Hatching Rules (HRUL).
Change Rulesets (CRST), Design Change Rules (DCRULE) and
Annotation Change Rules (ACRULE).
Refer to Chapters 10 & 11 for information on the creation of Style Libraries and Representation Rules.
6. Create Tag Rules
Tag rules determine which items will be tagged in the View graphics, enabled by the Administrator defining Tag Rule Sets (TRST) and Tag Rules (TAGR) within Tag Rule Libraries (TRLB). When accessed during normal Draft drawing operations, each TAGR references a Tagging Template; this may be either a SYTM or a TXTM.
Refer to Chapter 12 for information on the creation of Tag Rules.
7. Database Update Administration
There are occasions when the Draft database is required to be updated specifically, as opposed to the routine updating that occurs from time to time in normal use. The Draft Administrator is able to undertake this task.
Refer to Chapter 13 for information on Database Update Administration.
WO
R
K
FL
O
W
www.aveva.com
8. Printing & Plotting Administration
The Administrator can enter or select operating system command strings that enable users to plot files in a variety of formats: PDMS supports output formats such as PDF, BMP and JPG.
Refer to Chapter 14 for information on Printing & Plotting Administration.
9. Automatic Drawing Production (ADP) Administration
The General ADP options create drawings from specified parts of the Design, and add annotation according to defaults set up by the System Administrator.
The ADP facility can also be used to produce Pipe, HVAC and Structural sketches.
Refer to Chapter 15 for detailed information on ADP Administration
E X A MP L E DR AW ING O UT P UT ADP DR AW ING O UT P UT
www.aveva.com
10. AutoDraft Administration
It is possible to transfer a Draft drawing directly across to AutoCAD, where some Designers prefer to perform final annotation before drawing issue. The transferred drawing maintains the exact style and representation as set within Draft.
Refer to Chapters 16 for detailed information on AutoDraft
11. IsoDraft Administration
IsoDraft, the Isometric drawing production module, uses a series of Option Files that describe how the Isometric should be drawn. It is necessary for the Draft Administrator to modify and create a Standard Isometric Project Option File and utilise a selection of options to configure Isodraft.
Symbol keys are used in Isodraft to represent piping symbols on the isometric plot. Isodraft Symbol Libraries (ISOLB) contain the Isometric Symbol Templates (ISOTM), thus allowing the Administrator to create and modify Isometric Symbol Keys.
Refer to Chapters 17 & 18 for detailed information on IsoDraft Administration AutoCAD AUT O DRAF T O UT P UT IS O DRAF T O UT P UT
www.aveva.com
CHAPTER 4
4
Getting started with PDMS Draft
Chapter 4 aims to introduce the Draft application in regards to access, the user interface and the Draft viewing and manipulations controls.
4.1 Entering a Draft Session
To start AVEVA PDMS and login to the Draft Module, the User must select the following:
& Or AVEVA Plant > Design > PDMS 12.1.SP2 > Draft from the Windows Start Menu.
The Trainer will provide user names and passwords; a typical example is shown below.
Project: Training
Username: A.DRAFTADMIN Password: A
MDB: A-PIPING
Click the Login button.
The User must be a member of the Draft administration team DRAFTADMIN and the PROJECT team to be able to customise existing backing sheets and symbols during the course. The Trainer has added A-DRAFTADMIN to these teams.On loading PDMS Draft, a default screen layout will be displayed comprising application menus / toolbars and a Draft Explorer. On entry to Draft, the General user application is selected by default.
www.aveva.com
Select Draft > Administration… from the main menu to enter the Administration application.The application pull-down is updated to include a number of Administration modules that may be used to perform specific Draft Administration tasks
Once in the Administration application, Draft > User Application… can be used to return to the Draft User Application.
4.2 Default Load Errors
Contrary to the Training Project, errors may be presented on entry to Draft where the MDB does not include the required Draft database i.e. MASTER/PADD, and/or does not reference a number of basic settings for pens, aids, etc. that are required by Draft.
If Draft initialises without errors the default files have loaded correctly. The utilised Training Project will enter without Load Errors.
This can be verified by selecting Display > Appware Load Errors… from the main menu to display the Default Load Errors form. As indicated below, the form will state that ‘No Errors Occurred During Load’ for the Training project.
www.aveva.com
Note the following typical errors that can occur with customer projects:
If load errors do occur, PDMS Draft will not load - only the command line will be displayed.4.3 Draft Sample Data
The AVEVA supplied Master Project (MAS) includes two databases that may be referenced from the project MDBs. The database MASTER/PADD contains the following AVEVA data:
General Admin
Master Library DEPT
AID information
User defined pen display
Backing sheets
Label and Symbol libraries
H&S ADP hierarchy
Structural detailing ADP hierarchy
Symbol templates.
The database MASTER/DICT contains the UDA definitions that are required within the Draft module. This database must be present in all Draft MDBs.
The AVEVA supplied Sample project (SAM) includes a database ADMIN/PADD which contains the following data:
Project Library
Drawing and sheet templates
ADP schedules
www.aveva.com
Representation Rulesets
Hatching rules
Styles
Overlays
General auto tagging Drawlists and circulation lists.
The database ADMIN/PADD has been copied to the Training Project and renamed PROJECT/PADD. It is normal practice to reference these databases but for completeness, and for the purpose of Training, they (macros) are included.4.4 Loading Draft Sample Data via Forms & Menus
If project default data is available, the Data File may be accessed by selecting Settings > Load Data
Files… from the General Administration main menu.
The Load Draft Data Files form is displayed:
The following Departments are available for selection within the Training Project:
Master Libraries (DEPT) loads all sample libraries supplied by AVEVA.
Project libraries (DEPT) loads all project specific libraries supplied by AVEVA.
There is also an option to load sample drawings but for the purposes of the training this option is not required.
Sample Project Drawings (DEPT) loads sample drawings for viewing.
4.5 Loading Draft Sample Data using the Command Line
A second option is available to load the sample data files into the Draft database. This can be undertaken where the project contains specific project data, but also requires AVEVA supplied data. If there is no default project data, it will be necessary to run the following macros in DEV TTY mode on the command line in Draft. The macros are located in the directory %PDMSUI%/DRA/DATA
MASTER.DAT PROJECT.DAT SAMPLE.DAT
Defaults must be loaded using the command line if the Draft forms and menus are not being displayed.As an example, the Administrator may enter the following on the command line:
$M/%PDMSUI%/DRA/DATA\MASTER.DAT $M/%PDMSUI%/DRA/DATA\PROJECT.DAT DRAFT
www.aveva.com
4.6 Referencing Draft Sample Data
As noted previously, AVEVA supply the Draft default data in two databases, one in the Master Project (MAS) called MASTER/PADD, and one in the Sample Project (SAM) called ADMIN/PADD.
MASTER/PADD should be included as a foreign database.
ADMIN/PADD should be copied into the project as a basis for project customisation.
Including and copying databases is covered by TM-1300 AVEVA Plant (12.1) System Administration(Basic).
www.aveva.com
Exercise 1
Starting PDMS Draft
Enter the Training Project (TRA) and navigate to the Draft Administration application as described within the Chapter.
Check the current MDB and ensure that the databases PROJECT/PADD and MASTER/PADD are available in the MDB. This can be done via the Command Window using the STATUS Command.
Become familiar with the application layout and available menus.
If the Training is being carried out on a non-AVEVA supplied project, ADMIN/PADD and MASTER/PADD must be included in the current MDB.www.aveva.com
CHAPTER 5
5
Administrative Rights
5.1 Draft Administrative Rights
To access the Administrator options within Draft, the User must be a member of a Draft Administration team with read/write access to the Draft database(s) that contain the relevant libraries.
The list of authorised Draft Admin teams is held within the file DRA-SETUP; located, in a standard installation, at: C:\AVEVA\Plant\Data12.1.SP2\pdmsui\DFLTS\dra-setup. The file may be modified to suit the team names being used. The standard Draft administration team referred to during this course will be DRAFTADMIN.
$* Set administration team global variable
$* If the user is a member of one of the teams specified
$* he/she is given access to the Draft Administrator Applications var !!CDSADMTEAM |MASTER DRAFTADMIN|
The value of the variable !!CDSADMTEAM can be modified as required.In addition, the DRA-SETUP file contains the location of the Draft default files. The Administrator should give consideration to the location of these default files. It is possible to have two arguments set for the environment variable %PDMSDFLTS%, to ensure that a subsequent AVEVA Plant installation does not overwrite these files. For example:
PDMSDFLTS = F:\company\pdmsui\DFLTS C:\AVEVA\Plant\Data12.1.SP2\pdmsui\DFLTS Read / Write access is required to this directory for the Draft Administrator but only Read access is required for general users.
5.2 Draft Defaults
As a Draft Administrator, the settings in the defaults files may be altered; if necessary creating a different defaults file for each of the company's drafting requirements. The defaults file accessed by an individual user is determined by the setting of the user's PDMSDFLTS environment variable.
Defaults can be set for the following:
Definitions of layers for use with views; defined in terms of their purpose and associated attribute groups.
Definitions of name delimiters; that is, the characters used to separate the component parts of an element's name.
Pointers to the libraries from which the different aspects of the Draft drawing functions obtain standard data, for example:
- 2D symbols and labels
- Backing sheets and overlay sheets
- Global representation rules and local styles - Circulation lists
www.aveva.com
- Tag rules and tag templates - DRWG and SHEE templates.
A list of default files used by the Draft applications can be found in Appendix A.5.3 Draft User Defaults (Training Setup)
When entering the Draft module, the file DRA-GEN-SYSTEM is read - defining the User Defaults required. The default system settings can be viewed and modified for the current session by the User. To display the User Defaults form select Settings > User Defaults… from the main menu.
Using the File option, Designers can load settings that have been pre-defined by the Draft Administrator. The defaults for the Training have been pre-defined by an Administrator (Trainer) and are applied by selecting File > Load Pre-Defined From... from the User Defaults form menu.
Navigate to: C:\AVEVA\Plant\Training12.1\Training\pdmsui\dflts (or as located by Trainer).
Select the file dra-gen-system to populate the User Defaults form as displayed above i.e. the setting of True Type Font specific defaults.
www.aveva.com
5.4 Draft System Defaults
To view and modify Draft System Defaults, the Administrator is able to prompt the Draft System Defaults form on selecting Settings > System Defaults… from the Administration main menu.
The current default file being used is displayed in the top area of the Draft System Defaults form. The form displays all the default settings for the current project:
5.4.1 File Menu Options
The options available to save and load from file, via the Draft System Defaults form, are as listed:
Save save changes to settings to displayed file.
Save As… save changes to settings to a specified file.
Load load defaults from current DRAFT defaults file.
www.aveva.com
For the Load and Load From options, the Draft Administrator can perform either a full or partial load by selecting the relevant option from the submenu: Full Load clears all existing default values from the forms before loading the new ones. A check is also completed, to ensure that the minimum numbers of default values are loaded to allow the application to run correctly.
Partial Load does not clear the existing form settings, allowing the Administrator to overwrite a subset of the defaults available.
Display Errors… displays the Default Load Errors form, which shows all errors that occurred during loading. Each error message shows the load file line number at which the error occurred and a brief description of the error.
Restore Backup restores default settings from back up file, i.e. DRA-GEN-SYSTEM.bak
The File DRA-GEN-SYSTEM may be read only.5.4.2 Library Reference Pointers
The Master Project Defaults and Local Project Defaults parts of the Draft System Defaults form display the library references used throughout the Draft applications.
To change the identified references, the user is able to navigate to the appropriate element in the Draft Explorer - as shown to the right of the CE button i.e. LIBY or SHLB, and click the CE button to transfer the name of the current element to the text field.
www.aveva.com
Alternatively the appropriate reference can be directly entered into the text field or imported using the File menu options.
The User Defaults form is initialised with the settings from the Draft System Defaults form after it has been loaded from file. Subsequent changes to the User Defaults form, override (but do not change) the settings on the Draft System Defaults form.5.4.3 Element Name Delimiters
By default, the individual parts of the PDMS element names are separated by a delimiting character ( / ) e.g. SHEETS/SHLB1/BACK1/SN1.
The Name Delimiters section of the Draft System Defaults form allows the Administrator to specify an alternative delimiter character to be used for Style names, Label Library names and/or Drawlist Library names.
5.4.4 Layer Purpose Definitions
Clicking the Layer Purpose Definitions… button on the Draft System Defaults form will display the Layer Purpose Definitions form.
The list gadget displays all the currently defined layers.
To create a new layer definition, a Layer Purpose to a maximum of three characters is entered, an attribute default setup file specified and the appropriate attributes selected - displayed when the layer is modified. Clicking the Insert button creates a definition after the currently selected definition in the list.
Layer Purpose: purpose value to be set on layer upon creation.
Setup File: default file to be executed upon creation of layer.
Delete / Insert: apply to currently selected settings in form.
Attributes: determines which attributes are displayed on the Layer Attributes form in the user application.
OK: applies the current values to the updated definition.
Layer Purpose
5.4.4.1
All layers have a PURP attribute, which is set to a four character keyword. This attribute identifies the purpose for which that layer is intended to be used. Layer Purposes cannot be duplicated under a single owning View. The Layer Purpose box on the form allows the Administrator to specify the purpose as a three character string. The fourth character is added automatically when setting the PURP, thereby allowing
www.aveva.com
The purpose keyword TAG is reserved for Autotagging layers. This is a requirement of the application and must always be defined in the layer defaults. If it is omitted, a TAG layer purpose definition will be appended automatically during default initialisation. The TAG layer purpose definition cannot be deleted.Setup File
5.4.4.2
The Setup File field is used to specify the (macro) file that will be executed to set the layer attributes after a layer has been created. This ensures that all users create layer annotation to a common standard. Nine layer default files are supplied as standard and are located in the %PDMSDFLTS% directory.
The copying and modification of these (macro) file(s) allow the Administrator to create company and/or project specific standards. New files can also be created for purpose types of an alternative, user specific definition.
Creating a Layer Setup / Defaults File – A Worked Example
5.4.4.3
The most efficient way to create a Layer Default File is to copy an existing file and customise it to suit the project requirements.
Default files are held in the directory pointed to by the environment variable %PDMSDFLTS%. Variables can be queried in PDMS using the Command Window (Display > Command Window…) and entering: Q EVAR PDMSDFLTS.
Using the given location as a reference, copy the file DRA-GEN-DIMLAY and rename to DRA-EQUIP-DIMLAY.
The default file can be copied in Windows and edited using a suitable editor. Editing the file as below modifies the Header and sets the dimension text size as 10mm:$p Equipment DIM Layer Defaults $* Layer general TEXT attributes FONT 11 $* Text font
TXCOLOUR 10 $* Text pen (colour) JUST LEFT $* Text justification $* Layer DIMENSION attributes
DIRE E $* Dimension direction
DLCOLOUR 10 DLSTYLE SOLID $* Dimension line pen DTERM ARROWS $* Dimension line terminator
FTERM DEFAULT $* Dimension line first terminator
PLCOLOUR 10 PLSTYLE SOLID $* Dimension projection line pen PJUST TOWARDS $* Dimension projection justification $* set unit dependent attributes
$* check units
if (!!isImperialLength('DIST')) then Tsize 3/8
CHEI 1/8in $* Text character height DOFF 1in $* Dimension offset
OSHT 1/8in $* Dimension projection overshoot PLCLE 0in $* Dimension projection clearance DMSP 0in $* Dimension spacing
else Tsize 10
www.aveva.com
DOFF 25mm $* Dimension offsetOSHT 2mm $* Dimension projection overshoot PLCLE 0mm $* Dimension projection clearance DMSP 0mm $* Dimension spacing
endif
$p Bottom Equipment DIM Layer Defaults return
A comment is included at the top and bottom of the file. Both will be output if the file has been successfully executed.Creating a New Layer Purpose – A Worked Example
5.4.4.4
As Draft will add a suffix letter, the Layer Purpose attribute can only be three Letters in length. In the following example a new layer purpose is created called EDI. This will be used for Equipment Dimensions i.e. will utilise the layer Defaults file DRA-EQUIP-DIMLAY created earlier.
Select DIM DRA-GEN-DIMLAY from the existing definitions list.
Using the Layer Purpose Definitions form, enter the following information within the fields:
Layer Purpose: EDI.
Setup File: DRA-EQUIP-DIMLAY. Click the Insert button and then click the OK button.
Attributes Group
5.4.4.5
The Dim, Note, Text, Lab and Symb checkboxes allow the Administrator to specify (by checking or un-checking each box) which attribute types will be displayed on the Layer Attributes form in the User application. The combination which applies to each of the currently defined layers is shown by the + (selected) and - (unselected) codes in the scrollable list.
www.aveva.com
5.4.6 Layer Creation Definitions – A Worked Example
The Layer Creation Definitions … button on the Draft System Defaults form displays the Layer Creation
Definitions form.
The form allows the Administrator to define a list of default layers that will be created each time a general user creates a View. The Administrator is required to specify a Layer Purpose and a Suffix to be appended to the View name, thereby setting the name of the new Layer.
In the example here, a new layer called USER_Equip_Dims has been defined using the created Layer Purpose EDI.
Click the Insert button and then click the OK button.
5.4.7 Layer Purpose Filtering – A Worked Example
When selecting a particular function, i.e. Dimensioning, the toolbar menu will change to display forms/menus which relate to that particular task.
This list is controlled by the settings of the Layer Purpose Filtering form. This form is opened by clicking the Layer Purpose Filtering… button on the Draft System Defaults form. The settings on this form will automatically be transferred to the list of layers that are shown.
Append EDI to the Dimensioning field.
Click the OK button.
Layer Purpose Filtering defines the Layers visible in the Layer Note drop-down list on the appropriate application menu bar.
As the defaults are stored in an external file, changes are only retained once a save has been performed on the Draft System Defaults Form.www.aveva.com
5.4.8 Sheet Sizes – A Worked Example
The default sheet sizes that are offered to the general user can be set via the Sheet Defaults form. This form is opened by clicking the Sheets Sizes… button on the Draft Systems Defaults form.
This form allows the Administrator to define the dimensions and display reference description for up to 15 standard sheet sizes. The description should be limited to ten characters, including spaces. Although more characters can be entered, only the first ten will be displayed on the list of possible sheet sizes offered to the user. The maximum allowable Imperial sheet size is 128.976”. The maximum metric sheet size is 3276 mm.
New Drawing Sizes can be added as required, for example add the following:
216.00mm 280.00mm Letter & 841.00mm 1189.00mm P0.
5.4.9 Naming Conventions
The Naming Convention form is displayed by clicking the Naming Conventions… button on the Draft System User form. The form is divided into two sections:
Mandatory Names
Mandatory names apply to those elements that must be named in order for the application to function correctly. As an example, drawing numbers are typically project related. Therefore any prefix should be entered in the Prefix box for the Drawing element.
For example 1234- or DEPT- and REGI-.
When any of these types of element are created, they will use the Mandatory name as part of the default name visible to the user.
Optional Names
Optional names apply to those lower–level database elements that do not need to be named for the application to function.
For each such element, the Named checkbox can be used to specify whether or not a default name is to be visible to the user.
www.aveva.com
Exercise 2
Draft Administration Defaults
Using Chapter 5 as a guide, perform the following tasks:
Edit file DRA-SETUP (typically C:\AVEVA\Plant\Data12.1.SP2\pdmsui\DFLTS) and check how many authorised Draft Admin Teams are present, typically:
$* Set administration team global variable
$* If the user is a member of one of the teams specified
$* he/she is given access to the Draft Administrator Applications
var !!CDSADMTEAM |MASTER DRAFTADMIN|
Locate and load pre-defined User Defaults from file DRA-GEN-SYSTEM within C:\AVEVA\Plant\Training12.1\Training\pdmsui\dflts.
Check the library pointer in the Draft System Defaults form name the correct elements in the hierarchy.
Try Saving and Loading the Defaults file.
With reference to the Chapter Worked Example and using the Draft User Application:
Set up and check the application of new default names for a DEPT (DEPT-) and REGI (REGI-). Create or Modify the Drawing Department: /DEPT-EQUIPMENT-AREA01.
This may already exist if Drawing Production courses have been completed.Create or Modify the Drawing Registry: /REGI-EQUIPMENT-AREA01.
This may already exist if Drawing Production courses have been completed.In each instance ensure that the following attributes are set:
Sheet Size: A0
Backing Sheet Reference: unset
All Units: Millimeters
Font: Arial Unicode MS
Note whether the new default standard sheet sizes are available on explicit creation of a Drawing (Create > Drawing > Explicitly…).
Name the Drawing: DRWG-DRAFT_ADMIN-EXAMPLE and the Sheet: DRWG-DRAFT_ADMIN-EXAMPLE/S1.
Confirm the extra layer setup file for dimensioning equipment is added on creation of a new unpopulated central View.
www.aveva.com
CHAPTER 6
6
Drawlist Library
Considering the eventual drawing to be produced, this chapter explains how to set up Drawlist Libraries (DLLB). Each library contains a group of Drawlists (IDLI or ID Lists) which allow users to create lists of design elements to be drawn or sectioned. The DLLBs and IDLIs can be assigned to design items according to design disciplines, project areas, or any other classification appropriate to specific working practices.
Each IDLI comprises a list of Design elements, in the usual format of an Add List and a Remove List, which can all be displayed in an area view simply by reference to the IDLI name.
The DEPT TT/Project_Libraries, supplied as part of the standard product, contains a LIBY named TT/DRA/PRJ/DRAWLISTS containing sample drawlist libraries.6.1 Entering Drawlist Library Administration Mode
To create or modify Drawlist Libraries, the Administrator is required to enter the Drawlist Administration application.
From the main menu select Draft > Drawlist Libraries….
Entry to the Drawlist Administration application can be verified at the top of the application.
All menu selections specified in the remainder of this chapter refer to this Drawlist Libraries menu unless otherwise stated.
www.aveva.com
6.2 Creating a Drawlist Library
To create a new Drawlist library (DLLB), the Administrator may navigate to an appropriate LIBY or create a new LIBY. The Drawlist Library can be owned by an existing LIBY.
Selecting Create > Library… from the main menu displays the Create LIBY form.
The Name field allows users to enter Library names i.e. /TT/AVEVA-DRAWLISTS.
Selecting Create > Drawlist Library… from the main menu displays the Create DLLB form.
The Name field allows users to enter Drawlist Library names i.e. /TT/AVEVA-DRAWLISTS/AVV.
6.3 Creating and modifying a Drawlist
Selecting Create > Drawlist… from the main menu displays the Create Drawlist form.
The Name field allows users to enter a Drawlist Name i.e. /TT/AVEVA-DRAWLISTS/AVV/EQUIP.
Clicking the OK button displays the Drawlist Management form with the created Drawlist Library and Drawlist referenced in the appropriate fields.
The Drawlist Management form may also be displayed by selecting Modify > Drawlist… from the main menu.
www.aveva.com
6.3.1 Selecting a Drawlist Library & Drawlist
With reference to the Drawlist Management form, the Drawlist Library pull-down menu allows the User to specify the Drawlist Library that owns the Drawlist (IDLI) to be modified. In turn, the Drawlist may be selected from the populated Drawlists list.
6.3.2 Creating a Drawlist
The Drawlist Management form may be utilised to create a Drawlist via the Create button; an action which displays the Create Drawlist form.
As described previously with Drawlist creation via the main menu, a Drawlist name is entered and confirmed on clicking the OK button.
Alternatively, selecting Create Copy will display the Create Drawlist form and, in turn, clicking the OK button displays the Copy Drawlist form.
The Drawlist to be copied is selected from the Drawlists list and the copy confirmed on clicking the OK button.
www.aveva.com
6.3.3 Deleting a Drawlist
To delete a Drawlist (IDLI) from the current Drawlist Library, the identified Drawlist is highlighted in the Drawlists list and the Delete button clicked.
6.3.4 Defining Drawlist Members
The lower part of the Drawlist Management form contains the gadgets that are used to build up the Add and Remove lists owned by each Drawlist.
Selecting the required elements from the Reference List Members list and clicking the Add button adds the selection to the drawlist. Similarly, to remove items from the Drawlist i.e. items that are not to be displayed on the drawing, elements are selected via the Reference List Members list and the Remove button clicked. The Reference List Members list can show either Design Database elements or alternative existing Drawlists. The former allows the User to pick design elements explicitly; the latter allows the User to identify design elements by their presence in other Drawlists. The Design Members/Drawlists pull-down list is used to choose which list is to be displayed.
Alternatively, elements can be added to the drawlist by defining a volume on clicking the Volume Defined button. All significant elements positioned partly or wholly within the current limits box will be added to the Drawlist. A Drawlist Limits form will be displayed where no volume limits are currently defined
To delete an entry from the Drawlist (Add entry or Remove entry), the relevant line in the Drawlist Members list highlighted and the Delete Entry button clicked.
www.aveva.com
Exercise 3
Drawlist Library
Using Chapter 6 as a guide, complete the following tasks:
Within DEPT TT/Project_Libraries, navigate to Library TT/DRA/PRJ/DRAWLISTS and create a Drawlist Library (DLLB) TT/DRA/PRJ/DRAWLISTS/AREA01.
Create a new Drawlist (IDLI): TT/DRA/PRJ/DRAWLISTS/AREA01/KEYPLAN.
The Drawlist contains design elements from the 3D Design Database: /ZONE-STRUCTURAL-AREA01, /ZONE-EQUIPMENT-AREA01 and /AREA_01_GRID.
The created Drawlist will be used later in the Training for the construction of a Drawing Keyplan.
The exercise above demonstrates the ability to add Plant Design grids (GRIDSYstem and FRIDAXiselements) to an IDLI. They are drawn using the Centreline Style/Colour with the GRIDLNs extending to the View boundary.
Ensure the Draft System Defaults reference the correct Library.
In the User Application, and using Sheet SHEE DRWG-DRAFT_ADMIN-EXAMPLE/S1 reference the new Drawlist within the central View.
www.aveva.com
CHAPTER 7
7
Sheet Libraries
Continuing the training in the context of the eventual drawing to be produced, this chapter explains how to set Sheet Libraries (SHLB) containing Backing Sheets (BACK) and Overlay Sheets (OVER). These Sheet Libraries will be referenced by the general user on creation of Drawings and Views.
The DEPT TT/Project_Libraries, supplied as part of the standard product, contains registries (REGIs) named TT/DRA/PRJ/TMP/<discipline>, where discipline is Piping, Equipment, etc... Each Registry contains Drawings, which own sample sheets with associated Libraries.
Within the DEPT TT/Project_Libraries, a Library named TT/DRA/PRJ/OVERS contains sample overlay sheets. Within the DEPT TT/Master_Libraries, also supplied as part of the standard product, a Library TT/DRA/MAS/BACKS contains sample backing sheets.
There is a duplicate set of these Libraries without the prefix /TT i.e./Project_Libraries and /Master_Libraries. These Departments have exactly the same information as described above but are configured using PDMS Fonts.7.1 Entering Sheet Library Administration Mode
To be able to create or modify Backing or Overlay Sheets the Administrator enters the Sheet Library application.
