TM-1001 AVEVA Plant (12 Series) PDMS Foundations Rev 5.0.pdf

255  Download (0)

Full text

(1)

T

T

R

R

A

A

I

I

N

N

I

I

N

N

G

G

G

G

U

U

I

I

D

D

E

E

www.aveva.com

AVEVA Plant

(12 Series)

PDMS Foundations

TM-1001

(2)
(3)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

Revision Log

Date Revision Description of Revision Author Reviewed Approved

24/07/2009 2.1 Issued for Review NG

04/08/2009 2.2 Reviewed NG BT

06/08/2009 3.0 Approved for Training PDMS 12.0.SP4 NG BT RP

09/09/2009 3.1 Search Results Updated NG

10/09/2009 3.2 Search Results Reviewed NG BT

10/09/2009 4.0 Approved for Training PDMS 12.0.SP4 NG BT RP

16/10/2009 4.1 Issued for Review PDMS 12.0.SP5 NG

21/10/2009 4.2 Reviewed NG KB

25/11/2009 5.0 Approved for Training PDMS 12.0.SP5 NG KB RP

Updates

All headings containing updated or new material will be highlighted.

Suggestion / Problems

If you have a suggestion about this manual or the system to which it refers please report it to the AVEVA Group Solutions Centre at gsc@aveva.com

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

Information of a technical nature, and particulars of the product and its use, is given by AVEVA Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd. and its subsidiaries disclaim any and all

warranties and conditions, expressed or implied, to the fullest extent permitted by law.

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

Trademarks

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

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd 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, its name or logo belongs to its respective owner.

(4)

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 AVEVA Solutions Ltd. or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd 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 Disclaimer and Copyright notice 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 Ltd. The user may also not reverse engineer, decompile, copy or adapt the associated software. Neither the whole nor part of the product 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 or save as permitted by law. Any such unauthorised action is strictly prohibited and may give rise to civil liabilities and criminal prosecution.

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

Printed by AVEVA Solutions on 26 November 2009.

© AVEVA Solutions and its subsidiaries 2001 – 2009.

(5)

5

Contents

www.aveva.com

Introduction ... 11  1.1  Aim ... 11  1.2  Objectives ... 11  1.3  Prerequisites ... 11  1.4  Course Structure ... 11 

1.5  Using this guide ... 11 

AVEVA PDMS Fundamentals ... 13 

2.1  How PDMS can help you ... 13 

2.2  How PDMS is Structured ... 14  2.2.1  Design ... 14  2.2.2  Draft ... 15  2.2.3  Isodraft ... 16  2.2.4  Admin ... 16  2.2.5  Paragon ... 17  2.2.6  Propcon ... 17  2.2.7  Lexicon ... 17  2.3  PDMS Databases ... 18 

2.4  How data is stored in PDMS ... 19 

2.4.1  World (WORL) ... 20  2.4.2  Site (SITE) ... 20  2.4.3  Zone (ZONE) ... 20  2.4.4  Equipment (EQUI) ... 20  2.4.5  Sub-Equipment (SUBE) ... 20  2.4.6  Primitives ... 21 

2.4.7  Volume Model (VOLM) ... 21 

2.4.8  Sub-Volume Model (SVOLM) ... 21 

2.4.9  Structure (STRU)... 21  2.4.10  Framework (FRMW) ... 21  2.4.11  Sub-Framework (SBFR) ... 21  2.4.12  Structural Components ... 21  2.4.13  Pipe (PIPE) ... 21  2.4.14  Branch (BRAN)... 21  2.4.15  Piping Components ... 22  2.5  Element Names in PDMS ... 22  2.6  Units ... 22  2.7  Axis System ... 23 

User Interface Basics ... 25 

3.1  Accessing the Design Environment... 25 

3.2  Default Screen Layout ... 26 

3.3  Using the Mouse ... 26 

3.4  Using Menus ... 27 

3.4.1  Pull-Down Menus ... 27 

3.4.2  Sub-menus ... 28 

3.4.3  Context Pop-up menus ... 28 

3.5  Using Forms ... 29 

3.5.1  Tabs ... 29 

3.5.2  Radio Buttons ... 30 

3.5.3  Checkboxes ... 30 

3.5.4  Text Boxes ... 30 

3.5.5  Scrollable Lists (Options List) ... 30 

3.5.6  Buttons ... 31 

3.5.7  Link Labels ... 31 

3.5.8  Fold-up Panels ... 31 

3.5.9  Grids ... 31 

3.5.10  Form Menus ... 31 

3.5.11  Actioning Form Inputs ... 32 

3.5.12  Alert Forms ... 32 

(6)

www.aveva.com

3.6  Using Toolbars ... 36 

3.7  Command Window ... 36 

3.7.1  Entering Command Syntax ... 36 

3.7.2  Command Window Pop-up Menu ... 37 

3.8  Navigating the Databases ... 38 

3.8.1  Design Explorer ... 38 

3.8.2  Members List ... 42 

3.8.3  History Toolbar ... 43 

3.9  Deleting Elements from the Databases ... 43 

3.9.1  Deleting using Design Explorer ... 44 

3.9.2  Deleting using the Main Menu ... 44 

3.9.3  Deleting using the Default Toolbar ... 45 

3.9.4  Deleting using the Command Window ... 45 

3.10  Saving Changes to the Databases – Save Work ... 45 

3.11  Updating Databases to Show Other Changes – Get Work ... 46 

3.12  Undo and Redo ... 46 

3.13  On-line Help ... 46 

3.14  Leaving PDMS ... 47 

Exercise 1 ... 48 

Displaying Modelled Elements ... 53 

4.1  Building the Drawlist ... 53 

4.1.1  Populating the Drawlist Form ... 53 

4.1.2  Using the Drawlist Form ... 56 

4.1.3  Additional Drawlist Functions ... 59 

4.2  Setting the View Limits ... 61 

4.2.1  Using the View Control Buttons ... 61 

4.2.2  Using the View Menu ... 62 

4.2.3  Using the 3D View Pop-up Menu ... 63 

4.2.4  Using the Element Pop-up Menu ... 63 

4.3  Setting the View Direction ... 63 

4.3.1  Using the View Menu ... 63 

4.3.2  Using the 3D View Pop-up Menu ... 65 

Exercise 2 ... 66 

Working with 3D Views ... 69 

5.1  Modes of Operation in 3D Views ... 69 

5.2  Graphical Selections ... 69 

5.2.1  Selecting Items Individually ... 69 

5.2.2  Fence Selection... 70 

5.2.3  Clearing the Graphical Selection ... 70 

5.2.4  Reinstating the Previous Graphical Selection ... 71 

5.3  Navigate to Element Button ... 71 

5.4  Multiple, Local and Clone Views ... 72 

5.4.1  Multiple Views ... 72 

5.4.2  Local Views ... 73 

5.4.3  Clone Views ... 74 

5.5  View Projection Mode ... 74 

5.6  Zoom, Pan, Rotate and Walk ... 76 

5.6.1  Setting the Middle Mouse Button Options ... 76 

5.6.2  Zoom ... 77 

5.6.3  Pan ... 77 

5.6.4  Rotate ... 77 

5.6.5  Walk ... 78 

5.6.6  Controlling the speed of middle mouse button operations ... 78 

5.7  Setting the View Centre ... 79 

5.8  Clipping ... 79 

5.9  More View Menu Options ... 82 

5.10  Graphics Settings ... 83 

5.10.1  Graphics Settings – 3D Views Tab ... 83 

5.10.2  Graphics Settings - Colour Tab ... 83 

5.10.3  Graphics Settings – Representation Tab ... 84 

(7)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

5.10.5  Graphics Settings – Plines and Ppoints Tab ... 86 

Exercise 3 ... 87 

Attributes, Positioning and Orientation... 93 

6.1  Element Attributes ... 93 

6.1.1  Pseudo Attributes ... 94 

6.1.2  User Defined Attributes ... 94 

6.1.3  Querying and Displaying Attributes ... 95 

6.1.4  Modifying Attributes ... 96 

6.2  Positioning ... 97 

6.2.1  The Positioning Control Toolbar ... 98 

6.2.2  Positioning Explicitly ... 100 

6.2.3  Positioning Relatively ... 101 

6.3  Orientation ... 102 

6.3.1  Display Axes on CE ... 103 

6.3.2  Setting Orientation using Axes ... 104 

6.3.3  Setting Orientation using Rotate ... 104 

Exercise 4 ... 107 

General Utilities ... 113 

7.1  Lists ... 113 

7.2  Groups ... 115 

7.2.1  Creating Group Worlds ... 116 

7.2.2  Creating Group Sets ... 116 

7.2.3  Managing Groups ... 116 

7.3  My Data ... 118 

7.4  Search Utility ... 120 

7.4.1  Specifying the Items to Search for ... 120 

7.4.2  Search Filters ... 121 

7.4.3  Attribute Filters ... 122 

7.4.4  Saved Searches ... 123 

7.4.5  Executing the Search from the Search form ... 124 

7.4.6  Search Results ... 125 

7.5  User Grid Systems ... 131 

7.5.1  Creating 3D Rectangular Grids ... 131 

7.5.2  Creating 3D Radial Grids ... 134 

7.5.3  Grid Display Options ... 136 

7.5.4  Modifying User Grid Systems ... 138 

7.5.5  Deleting User Grid Systems ... 138 

7.5.6  Displaying Picked Positions in Grid Coordinates ... 139 

7.6  Measuring ... 139 

7.6.1  Distance Measure ... 139 

7.6.2  Angle Measure ... 141 

7.7  Claimlists in Multiwrite Databases ... 144 

Exercise 5 ... 146 

Introduction to Model Editor ... 153 

8.1  Model Editor Mode ... 153 

8.1.1  The Locator Handle ... 153 

8.2  Overview of Model Editor Operations ... 154 

8.2.1  Movement ... 154 

8.2.2  Rotation ... 154 

8.2.3  Alignment ... 155 

8.2.4  Locator Handle as a Frame of Reference ... 155 

8.2.5  Feedback ... 155 

8.2.6  Unconstrained Positioning ... 155 

8.2.7  Undo and Redo ... 155 

8.2.8  Performance ... 156 

8.3  The Selection Menu ... 156 

8.4  Positioning and Orientation using the Locator Handle ... 157 

8.4.1  Aligning the Graphical Selection with points or lines on other displayed items ... 157 

8.4.2  Automatic Scrolling ... 157 

8.4.3  Linear Movement Handles ... 157 

(8)

www.aveva.com

8.4.5  Rotation Handles ... 161 

8.4.6  Dragging the Locator Handle Independently of the Graphical Selection ... 163 

8.5  Graphical Equipment Modification (GEM) ... 163 

8.5.1  Display Characteristics ... 163 

8.6  Positioning and Orientation Using the Edit Menu ... 164 

Exercise 6 ... 167 

Basic Equipment Modelling ... 173 

9.1  The Principles of Modelling Equipment ... 173 

9.1.1  User Defined Elements Types for Equipment ... 173 

9.1.2  The Equipment Hierarchy ... 174 

9.1.3  Primitives ... 174 

9.1.4  Equipment and Primitive Orientation ... 176 

9.1.5  Equipment, Sub-Equipment and Origin ... 176 

9.1.6  Naming Equipment ... 176 

9.2  The Equipment Application ... 176 

9.2.1  The Create Menu ... 177 

9.2.2  The Modify Menu... 180 

9.2.3  The Position Menu ... 184 

9.2.4  The Orientate Menu ... 187 

9.2.5  The Connect Menu ... 187 

9.2.6  The Equipment Toolbar ... 188 

9.3  Creating Equipment – A Worked Example ... 189 

9.3.1  Information and Decisions ... 191 

9.3.2  Creating the EQUI Element ... 192 

9.3.3  Creating the Primitives ... 193 

Exercise 7 ... 208 

Exercise 8 ... 211 

10  Equipment Modelling Using Templates ... 213 

10.1  Equipment Template Overview ... 213 

10.2  Creating Standard Equipment – A Worked Example ... 214 

10.2.1  Information ... 214 

10.2.2  Creating E1302B ... 216 

10.2.3  Creating E1302A using Copy Mirror ... 221 

10.3  Using Selection Tables ... 224 

Exercise 9 ... 225 

10.4  Creating Electrical Components ... 227 

10.4.1  Creating an Electrical Component – A Worked Example ... 229 

11  Equipment Utilities ... 231 

11.1  Import Equipment Utility ... 231 

11.1.1  Rules for the Content of Import XLS and CSV Files ... 233 

11.2  Equipment Report Utility ... 234 

11.2.1  Selecting Attributes to Output ... 235 

11.2.2  Outputting Attributes ... 236 

Exercise 10 ... 238 

12  Volume Modelling ... 239 

12.1  The Volume Model Hierarchy ... 239 

12.2  Creating VOLM and SVOLM Elements ... 239 

12.3  Creating Primitives ... 240 

12.4  Creating Volume and Sub Volume Models – A Worked Example ... 241 

12.4.1  Creating the Slab UDET ... 243 

12.4.2  Creating the Slab Primitive ... 244 

Exercise 11 ... 246 

APPENDIX A – AVEVA Equipment Primitives ... 249 

Box (BOX) ... 249 

Cylinder (CYLI) ... 249 

Cone (CONE) ... 250 

Snout (SNOU) ... 250 

Pyramid (PYRA) ... 251 

Circular Torus (CTOR) ... 251 

Rectangular Torus (RTOR) ... 252 

(9)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

Sloped Cylinder (SLCY) ... 253 

Extrusion (EXTR) ... 253 

Solid of Revolution (REVO) ... 254 

(10)
(11)

www.aveva.com

CHAPTER 1

1 Introduction

AVEVA PDMS is a complex program with different applications that enables discipline designers to create a 3D model of a plant design. These applications use common features within the Design module that

designers need to be familiar with before embarking on discipline specific application training. 1.1 Aim

The aim of this training module is to provide the basic knowledge of the common features that provide the ‘foundations’ for PDMS Design.

1.2 Objectives

ƒ Explain how PDMS can assist in Plant design

ƒ Familiarise trainees with the basics of the User Interface

ƒ Explain how to manipulate the model in 3D

ƒ Explain Element Attributes, Positioning and Orientation of Elements

ƒ Introduce the Model Editor for graphical model manipulation

ƒ Explain how to create Equipment in PDMS

ƒ Explain how to create Volume Models in PDMS 1.3 Prerequisites

ƒ Keyboard Skills

ƒ Familiarisation with Microsoft Windows

ƒ Knowledge of Plant Design 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.

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.

Annotation for trainees benefit:

L

Additional information

Refer to other documentation

System prompts will be bold and italic in inverted commas i.e. 'Choose function' Example files or inputs will be in the courier new font, colours and styles used as before.

(12)
(13)

www.aveva.com

CHAPTER 2

2 AVEVA PDMS Fundamentals

The AVEVA Plant Design Management System (PDMS) is a multi-discipline 3D modelling system that allows you to simulate a detailed, full size model of all the significant parts of a process plant.

PDMS allows you to see a full colour shaded representation of the plant model as your design progresses, adding an unprecedented level of realism to design office techniques.

2.1 How PDMS can help you

In the model you can store huge amounts of data referring to position, size, part numbers and geometric relationships for the various parts of the plant. This model becomes a single source of engineering data for all of the sections and disciplines involved in a design project.

All this information is stored in databases. There are many different output channels from the databases through which information can be disseminated including textual reports, fully annotated and dimensioned arrangement and detailed drawings, piping and HVAC isometrics and interfaces to a variety of stressing, analysis, detailing and visualisation products.

Different types of output from PDMS

All the data in a PDMS design would be of little value without the ability to ensure the quality of the design information. Indeed, it would be pointless to develop such a large software system if it could not improve on existing techniques.

PDMS contributes to the quality of the design in the following ways: • Ensures consistent and reliable component data

In a conventional design environment, using 2D drawing techniques, the size of each fitting must be decided before it can be drawn. This is a time consuming process that often leads to expensive errors, which are only found during the erection stage of the project. With PDMS, all piping component sizes and geometry are predefined and stored in a catalogue, which cannot be changed by the designer. This ensures that all items are true to size and are consistent throughout the design, no matter how many users there are on the project.

(14)

www.aveva.com

• Adheres to definable engineering specifications

Piping specifications and steelwork catalogues stating precisely the components to be used are compiled for the purpose of ensuring consistent, safe and economic design. Design applications for piping, HVAC, cable trays and steelwork all use specifications to control component selection. • Ensures correct geometry and connectivity

There are many different ways of making design errors, such as incorrect fitting lengths, incompatible flange ratings, or simple alignment errors. PDMS can check all of these using data consistency procedures built into the system to check all or individual parts of the design model.

• Avoids component interferences

Despite a wealth of skill and experience in plant design, traditional design office techniques are still subject to human error. Laying out complex pipe runs, and general arrangements in confined areas using conventional 2D methods, inevitably leads to clashes between elements, which are trying to share the same physical space. PDMS enables you to avoid such problems in two ways:

1. By viewing the design interactively during the design process, allowing visual checks on the model from different viewpoints and resolves any potential problems as they arise.

2. By using the powerful clash checking facility within PDMS, which will detect clashes anywhere in the plant, this can be done interactively or retrospectively.

• Annotation and dimensions obtained directly from the Design database

Extracted information from the PDMS database, such as arrangement drawings, piping isometrics and reports, will always be the latest available as it is stored only in one source. Through the course of a project, information is constantly changing and drawings need to be reissued. When this happens, drawings, reports etc can be updated and reissued with the minimum of effort.

2.2 How PDMS is Structured

PDMS is divided into a number of functional modules which access the databases for a different purposes. The main modules and their purpose are listed below.

• Design 3D Model Design

• Draft 2D Drawing Production • Isodraft Isometric Drawing Production • Admin Project/User Administration

• Paragon Catalogue and Specification Construction • Propcon Properties Construction

• Lexicon User Defined Attributes and User Defined Element Type creation 2.2.1 Design

Design is the graphically driven data input module for the 3D model in PDMS. In this module the plant model is built and the data stored in one or more databases. The databases contain a three-dimensional

description of all items in the plant. Component selection is provided through specifications that dictate which catalogue components can be used.

The main features are:

(15)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

• Modification of existing design elements.

• Viewing of the design model interactively by graphical manipulation.

• Creation of reports, e.g. MTO, weight, C of G, project pricing, project timing, etc. • Clash detection to find interferences between design elements.

The Design module has a number of discipline applications and sub-applications to assist discipline designers in building models efficiently. These applications are:

• General • Equipment • Pipework • Cable Trays • HVAC Designer • Structures • Cabling System 2.2.2 Draft

Draft is used to create annotated, dimensioned arrangement and detail drawings. The annotation can be in the form of labels attached to design elements or 2D annotation such as drawing notes, drawing frames, tables, lines, etc.

Annotation attached to a design data element on the drawing will move if the 3D position of the element changes. Dimensions are projected distances between connecting points (P-Point) in the 3D design. The dimension itself is calculated automatically and is recalculated every time the drawing is updated. The design database can be interrogated through the drawing database, but it cannot be changed from within the Draft module.

(16)

www.aveva.com

2.2.3 Isodraft

Isodraft produces dimensioned symbolic piping and HVAC isometrics for construction and erection purposes in various formats.

Isodraft facilities include: • Full material lists.

• Automatic spool identification.

• Automatic splitting of complex drawings. • User-defined drawing sheets.

Example ISODRAFT output 2.2.4 Admin

Large plants designed using PDMS are usually broken down into individual areas (either physical areas or design areas), depending on the size, complexity and configuration of the plant. On a large project, the System Administrator will first agree with Project and Design Management the breakdown of the PDMS project into sections which:

• Are relevant to the needs of project reporting and control.

• Form reasonable design subdivisions with sensible match-lines and design content.

• Enable enough designers to work in parallel with simultaneous access to carry out their design tasks. In much the same way as in a design office (with its section leader, draftspeople, etc.), PDMS has Teams, the members of which are called Users. These Teams can consist of any number of Users and can be organised by discipline or physical work areas.

(17)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

The main features of the Admin module are:

• Access Control (Teams and Users) • Databases (DB’s)

• Multiple Databases (MDBs)

• Database management functionality 2.2.5 Paragon

Paragon is used to create and modify the component catalogue and specifications stored in the Catalogue database. The catalogues in PDMS serve a similar purpose to the manufacturers’ catalogues, which you would refer to when using conventional design methods. The PDMS component catalogue is used to specify the geometry, connection information, obstruction and detailing data of piping, structural, HVAC and cable tray components.

Paragon is used to construct the component catalogue just as Design is used to construct the design data. It should be noted that, whereas the design data is specific to a particular design, catalogues and

specifications may be specific to a company but general to a number of projects in that company. For example, the same catalogue component may also appear in other designs proceeding at the same time. 2.2.6 Propcon

Propcon is used to input and edit data within the Properties database.

The database contains data for materials, e.g. density, Young’s Modulus, expansion coefficients, etc., as well as component data, e.g. component weight, corrosion allowance, wall thickness, etc.

2.2.7 Lexicon

Lexicon enables the definition of User Definable Attributes (UDA) that may be assigned to PDMS elements so that additional information may be stored in the databases and extracted into drawings and reports. In addition, User Defined Element Types (UDET) may be defined to enhance the engineering terminology in the project and differentiate between types of the base element. For example, an EQUI element may be designated as an element type of, say, :PUMP or :EXCHANGER

(18)

www.aveva.com

2.3 PDMS Databases

The heart of PDMS consists of a set of hierarchical databases that store the model data. The database system is called Dabacon and is exclusive to AVEVA. There are several different database types, structured specifically for plant design data storage and each type of database stores different data.

Generally, multi-discipline projects are executed using discipline specific designers who will use specific applications in PDMS to construct the model components for their specific discipline. A project, therefore, may consist of a number of Design databases for each discipline.

When constructing the model, references are made to catalogue; property and user defined attribute data that is held in different types of databases. As this data is common to all users of each discipline, each user will refer to a common set of data for the project. These databases are called Reference databases. In order that each user can see the required design components modelled by other users and refer to the common catalogue, property and user defined attribute data, the Design and Reference databases are grouped together into a Multiple Database (MDB).

There may be several MDBs for a project, each defining specific groups of databases, for users with different tasks to perform.

Databases can be of two types, i.e. Update or Multiwrite and an MDB may contain each type.

Update databases allow only one user at a time to work in the database, creating or modifying data held within it. This set-up is easy to administer but on a large project will require a large number of databases. In addition, as only one user at a time can modify the data this may cause a bottleneck on busy project schedules.

Simplified scenario using Update databases

Multiwrite databases allow any number of users to work in the database simultaneously, creating and modifying data within it. In order to control the modification of the data, a ‘claim list’ concept is used to avoid

(19)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

a ‘last saved’ scenario for element modification to occur. Claim lists are discussed in more detail later in the Training Guide.

Simplified scenario using Multiwrite databases 2.4 How data is stored in PDMS

Each hierarchical database is a ‘tree’ like structure similar to the hierarchy of directories and sub-directories used to contain the files on a computer. The topmost data level in all databases is called the WORLD, below which all other data exists.

The PDMS Design Database Hierarchy (part)

Each identifiable item of data is known as a PDMS element. Each element has a number of associated pieces of information that, together, completely define its properties. These are known as attributes.

(20)

www.aveva.com

In this hierarchical structure all elements are owned by other elements, with the exception of the WORLD. Elements that are owned by another element, e.g. a ZONE is owned by a SITE, are said to be members of the owning element, e.g. The ZONE is a member of the SITE.

The vertical link between two elements on adjacent levels of the database hierarchy is defined as an owner-member relationship. The element on the upper level is the owner of those elements directly below it. The lower level elements are members of their owning element, e.g. a SITE is the owner of a ZONE and the ZONE is a member of a SITE.

Each element can have many members, but it can only have one owner. All elements are owned by another element with the exception of the WORLD.

Each element may only exist in its correct position in the hierarchy, e.g. a ZONE may not be directly owned by the WORLD, it must be owned by a site.

Every element is identified within the database structure by an automatically allocated reference number and, optionally, by a user-specified name.

The following sections give descriptions of the main element types in a PDMS Design database. Most of the element types are abbreviated, usually to the first four letters of the full name, when they are displayed in the user interface. The abbreviations are shown in parenthesis.

2.4.1 World (WORL)

When the database is first built, it is empty except for a single element named the WORLD. Each database has its own WORLD element as the first element in the hierarchy. The World cannot be deleted or re-named.

2.4.2 Site (SITE)

Below the WORLD, the second level of the hierarchy is SITE. A SITE may be considered as a significant collection of plant, whose size is not necessarily determined by physical area, but by practical

considerations. It may, for example be the whole project, or one part of a large project. You can have as many SITEs within a PDMS project as required for data organisation.

2.4.3 Zone (ZONE)

The next level below a SITE is a ZONE. As with a SITE, a ZONE is not necessarily used to define a physical area, it is more likely to store similar types of items for easy reference, such as a piping system in one ZONE, related equipment in another, and so on. You can have as many ZONEs owned by a site as required for data organisation.

SITE and ZONE elements are common to all disciplines. Below ZONE level the hierarchy is discipline dependent, i.e. the elements depend on which discipline you are modelling.

2.4.4 Equipment (EQUI)

Equipment items are built up in PDMS using elements known as primitives. Each piece of equipment can comprise any number of primitive shapes positioned in space to represent the equipment item. The primitives may be owned directly by the EQUI element or by a Sub-Equipment element.

2.4.5 Sub-Equipment (SUBE)

(21)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

2.4.6 Primitives

Primitives are the basic building blocks of PDMS. They are used by other disciplines to create catalogue components. There are many types of primitives; each with its own features which when combined with other primitives can represent complex shapes.

Examples of primitives are nozzle (NOZZ), box (BOX), cylinder (CYLI), pyramid (PYRA), cone (CONE) and dish (DISH).

2.4.7 Volume Model (VOLM)

A VOLM is a ‘simplified’ version of an EQUI element. This allows volumes to be modelled without them being called Equipment items. A VOLM may directly own any primitive except a NOZZ.

2.4.8 Sub-Volume Model (SVOLM)

A SVOLM is an optional element, similar to a SUBE, to sub-divide a VOLM. A SVOLM may own any primitive except a NOZZ.

2.4.9 Structure (STRU)

STRU elements are administrative elements, i.e. they exist to own FRAMEWORK elements, and allow the plant structures to be sub-divided for ease of modelling and reporting.

2.4.10 Framework (FRMW)

FRMW elements are used to store structural components in the model. A complex structure can be divided into logical frameworks. Dividing the structure in this way allows structural modelling, and also reporting, to be done more efficiently, e.g. by copying a complete FRMW.

2.4.11 Sub-Framework (SBFR)

A SBFR is an optional element that can own structural components. They are used to further sub-divide complex projects or for modelling sub-assemblies within a framework.

2.4.12 Structural Components

Structural profiles are represented in PDMS by section (SCTN) elements. Profile sizes are selected using a section specification that references standard catalogue data for section sizes complying with various national standards or company standards. Plate elements are represented by Panel (PANE) elements and curved profiles are modelled using a Generic Section (GENSEC) component.

2.4.13 Pipe (PIPE)

Pipes may be considered like lines on a flow sheet. They may run between several end connection points and are usually grouped by a common specification and process.

2.4.14 Branch (BRAN)

Branch elements are sections of a pipe, which have known start and finish points. In PDMS the start and finish points are called the Head and Tail. Heads and tails may be connected to Nozzles, Tees or other Heads and Tails, depending on the configuration of the pipe, or left open ended.

(22)

www.aveva.com

2.4.15 Piping Components

A Branch may own a wide variety of components such as Gaskets (GASK), Flanges (FLAN), Elbow (ELBO), Tees (TEE), Valves (VALV), etc. These form the shape and geometry of the Branch and ultimately the Pipe itself.

Piping components are selected using Piping Specifications that reference standard catalogue data. For example, each time you want to use a 100mm bore elbow, PDMS always accesses the data for it from the component catalogue. The data for these elements remains constant no matter how many 100mm bore elbows are used in the design.

2.5 Element Names in PDMS

Any element in a PDMS database may be given an explicit name. Names enable you to identify elements and to produce meaningful reports from the database. Which elements you name is a matter of choice, however, in general ‘significant elements’, e.g. SITE, ZONE, EQUI, SUBE, PIPE, BRAN, STRU, FRMW, SBFR, etc. would be named. It is not usual for primitives to be named. The WORLD is named /* and cannot be renamed.

Element names in PDMS must comply with the following rules:

• Element names begin with a forward slash, e.g. /MY_MODEL. Generally, most design items give you the opportunity to name them from the element creation form. You do not have to enter the forward slash on such forms as it is added automatically when the Return (Enter) key is pressed.

• Element names must be unique across all databases in the MDB.

• Element names are case sensitive, e.g. /P1001A, /P1001a, /p1001A and /p1001a are all valid, and different, names.

• Element names must not contain spaces. Any character such as forward slash (/), Underscore (_), hyphen (-), asterisk (*), etc. may be used as separators.

• Element names must be no longer than 50 characters.

If an element is not explicitly named it receives a system name, e.g. CYLI 2 of EQUI 1 of ZONE 2 of SITE /MY-MODEL. Internally PDMS does not use names to identify elements but a unique database reference number so that an element may be re-named at any time. These reference numbers are never re-used if an element is deleted and are, therefore, remain unique throughout the life of the project. On some forms the reference number is used in place of the system name and will look something like =23584/2152.

2.6 Units

Internally PDMS works in millimetres; however, the current session units may be set to metric or imperial for data input and output. The units may be changed at any time during the session.

For metric units the number of decimal places for the output may be specified and for imperial units different output styles are available, i.e.

• Inches – part units expressed as fractions, e.g. 39.3/8 • Feet & Inches – e.g. 3'- 3.3/8

• Feet & Inches – e.g. 3'- 3.3/8" • Feet & Inches – e.g. 3ft 3 3/8in

(23)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

2.7 Axis System

PDMS uses the right hand rule to express the co-ordinate system and rotation:

In Design, the WORLD has a world co-ordinate system whose origin is at X 0, Y 0 and Z 0.

PDMS assigns cardinal directions to the X, Y and Z axes, i.e. • X is East

• Y is North • Z is Up

Many elements in PDMS have position and rotation attributes. Such elements have there own axis system, conforming to the right hand rule, and the position and orientation are expressed with respect to their owner.

Refer to Chapter 6, Attributes, Positioning and Orientation, for information on the Position and

(24)
(25)

www.aveva.com

CHAPTER 3

3 User Interface Basics

This Chapter describes the basics of the user interface including accessing the Design environment, the use of the mouse, menus, forms and toolbars and the Design Explorer.

3.1 Accessing the Design Environment

PDMS may be started by selecting Start>All Programs>AVEVA>PDMS 12.0>Run PDMS from the task bar or from a pre-defined desktop icon. Starting PDMS displays the AVEVA PDMS Login form:

The AVEVA PDMS Login form controls access to PDMS. The available entries for Username are determined by the Project selected and the available entries for MDB are determined by the Username selected.

The Project, Username and MDB may be selected via the option arrows adjacent to each textbox.

Each arrow will display an appropriate form from which the selection may be made. Alternatively, the entries may be keyed in with the Return (Enter) key being pressed after each entry.

When a valid Password has been entered the Change button on the AVEVA PDMS Login form is activated which enables the Password to be changed directly by the user. Clicking the button displays the Change Password form where the new password may be entered and confirmed

The required PDMS Module, i.e. Design, Draft, Paragon, etc., may be selected from the pull-down menu.

The Restore Views checkbox becomes active once a module has been previously entered. Checking this box will restore the screen layout, including forms and views.

(26)

www.aveva.com

3.2 Default Screen Layout

The first entry into the Design module displays the default screen layout:

This default layout may be modified to suit individual preferences, e.g. additional forms may added to the layout, forms may be moved and ‘docked’, forms may be pinned/unpinned as required, toolbars may be moved or docked around the edges of the screen. Some of these features are described later in this Chapter.

After exiting PDMS or changing to a different module, a subsequent return to the Design module will restore the screen layout as it was left in the previous session.

3.3 Using the Mouse

L

A three button mouse, preferably with a scroll wheel middle button, is required for PDMS.

The mouse steers the graphics pointer around the screen and is also used to select or ‘pick’ items by using the mouse buttons. The buttons perform different tasks depending on the type of window, and the position of the mouse pointer in the window. The appearance of the pointer will change according to the type of display item that is underneath it.

There are two techniques used when operating the mouse buttons, Clicking and Dragging:

• Clicking - the pointer is positioned over a specific point on the screen. Clicking and releasing a mouse button ‘picks’ whatever is displayed at that point on the screen. This technique is generally used for selecting items in graphical views, operating gadgets on forms and for selecting lines in scrollable lists. • Dragging - the pointer is positioned over a specific point on the screen, the mouse button is clicked and

held down whilst dragging the pointer to another position on the screen. To complete the operation the button is released at the second position. This technique is mainly used for manipulating the design model in graphical views, moving forms/toolbars around the screen and for operating sub-menus.

(27)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

The functions of each of the three mouse buttons are described below:

• Left Mouse Button - The left mouse button is the main button for selecting items. On a graphical view clicking the left mouse button with the pointer over a design element selects the element. In a sequence of menus, dragging with the left mouse button activates the command represented by the highlighted menu option when the button is released. On a form, the effect depends on the type of selections that are being made, e.g. buttons, radio buttons, check boxes, scrollable lists, fold-up panels, etc.

• Middle Mouse Button - The principal use of the middle mouse button in the Design module is to manipulate the model in the 3D graphical view.

• Right Mouse Button - Clicking the right mouse button displays context pop-up menus, where available.

See Chapter 4, Displaying Modelled Elements, for details of using the mouse to manipulate the model in

graphical views.

3.4 Using Menus

There are three types of menu in PDMS, Pull-down Menus, Sub-menus and context Pop-up menus. 3.4.1 Pull-Down Menus

Clicking an item on the menu bar with the left mouse button displays the pull-down menu items:

As the pointer is passed over the menu items they are highlighted in turn. Each menu item has one of three options that result in different actions when the option is selected:

Options followed by a triangular pointer:

Placing the cursor over this type of menu entry displays a sub-menu. Option followed by three dots:

When this type of option is highlighted, clicking the left mouse button will require some user input, i.e. selecting an item, entering data in a form, confirming a message, etc.

Option shown as plain text:

When this type of option is highlighted, clicking the left mouse button will directly perform the action described in the menu item.

L

If, after displaying a pull-down menu, no menu item is required, clicking the left mouse button in a 3D

(28)

www.aveva.com

Some plain text menu items are toggles, i.e. they turn the

selection On or Off.

If such a menu option is turned on, a subsequent opening of the menu will display a checkmark next to the item. The checkmark is not displayed if the menu option is Off.

Some toggles also have separate buttons on a toolbar which are ‘pressed’ when the menu option is selected:

3.4.2 Sub-menus

Highlighting a menu item that is followed by a triangular pointer displays a sub-menu.

Sub-menus may contain any of the three menu options described above, e.g. it is possible to have a Sub-menu of a Sub-menu.

If none of the menu items are required, highlighting another option on the pull-down menu will dismiss the Sub-menu. Alternatively, clicking the left mouse button in a 3D View will dismiss the Pull-down as well as the Sub-menu.

3.4.3 Context Pop-up menus

Context Pop-up menus are context sensitive and are accessed by clicking the right mouse button. The menu options depend on where the pointer is located at the time of the mouse click. Context Pop-up menus are available from the 3D Views, Explorers and forms:

(29)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

3.5 Using Forms

Forms are used to display information, enter data and to modify data.

Forms typically comprise an arrangement of Tabs, Buttons, Text Boxes, Radio Buttons, Checkboxes, Scrollable Lists, Link Labels, Grids and Fold-up Panels, sometimes collectively referred to as gadgets.

Input to a form is usually via a combination of mouse and keyboard, the mouse being used to select the appropriate controls and the keyboard to enter the data.

When a form is displayed, settings may be changed, reset to initial values, accepted or cancelled without applying any changes, depending on the design of the form.

3.5.1 Tabs

Tabs are used to change to a new ‘page’ of the form. The current tab is highlighted with a yellow strip along the top of the tab label.

(30)

www.aveva.com

3.5.2 Radio Buttons

Radio buttons are combined in groups and only permit one selection of the group to be set ON, i.e. the radio button with the filled dot in the centre.

To set a radio button ON move the pointer over the radio button or associated text and click the left mouse button. Turning a radio button on will automatically turn the other radio button(s) in the group OFF.

3.5.3 Checkboxes

A checkbox may be either ON, i.e. a checkmark (tick) is displayed in the box, or OFF, i.e. the box has no checkmark displayed. Checkboxes are not mutually exclusive so any combination of check boxes on a form may be ON or OFF.

To change the status of a check box, i.e. to set it ON or OFF, move the pointer over the check box or associated text and click the left mouse button.

3.5.4 Text Boxes

Text boxes enable alphanumeric data, e.g. names, dimensions, values, etc., to be entered. A text box will generally have a label describing, or qualifying, the data required adjacent to it.

To enter data into a text box, move the pointer into the box and click the left mouse button. Key in the required data using the keyboard or edit any existing entry as necessary. The Backspace key will clear the box of any content. When complete, acceptance of the input is confirmed the by pressing the Return (or Enter) key.

When first displaying a form containing text boxes, the first text box on the form will be current and a text pointer (a vertical bar) will be displayed in the box. A text box often contains a default entry when first displayed. Some text boxes will accept only text or only numeric data, and entries with the wrong type of data will not be accepted.

3.5.5 Scrollable Lists (Options List)

A scrollable list, sometimes referred to as an options list) is displays a vertical list of options within a form.

If required for the length of the list, a vertical scroll bar is displayed on the right hand side of the list.

A horizontal scroll bar may also be displayed along the bottom of the list.

To select an option from a scrollable list, click with the left mouse button on the list or the down arrow to display the list items.

Moving the pointer up and down the list highlights each list item in turn. To select a list item click the required selection with the left mouse button.

Some scrollable lists allow only a single selection, i.e. selecting any option deselects all others

automatically. Other lists allow multiple selections, with all selected options highlighted simultaneously. Multiple selections, where applicable, are made using standard Windows selection functionality, i.e. the Ctrl and Shift keys. To de-select a highlighted option on a multi-item list, click on it again. Repeated clicks toggle a selection on and off.

(31)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

3.5.6 Buttons

Buttons may be any size and have either a text label, a sketch (picture) or a solid colour (swatch) within it that conveys the purpose of the button. Each button usually carries a Tooltip to describe the purpose of the button.

The button may take direct action when activated, display a form or toggle a setting. When a toggle button is ON it is shown as ‘pressed’. How this is shown depends on the Appearance settings of the Windows Display Properties.

Buttons are used by moving the pointer over the button and clicking the left mouse button. 3.5.7 Link Labels

Link Labels are text that links one form to another. Link Labels may be active, i.e. the text is underlined when the pointer is moved over it, or inactive, i.e. it is not underlined when the pointer is moved over it. Link labels are used by moving the pointer over an active label and clicking the left mouse button.

3.5.8 Fold-up Panels

Fold-up Panels are used to ‘extend’, i.e. reveal more options, large forms.

When a Fold-up Panel is hidden it displays a circle button with two ‘down’ arrows on the right hand side of the panel header.

Clicking the button opens the panel to reveal the options contained within it. These options may be any of the other gadgets.

Once unfolded the circle button on the panel header changes to show two ‘up’ arrows.

Clicking the button will fold-up the panel, hiding its contents.

3.5.9 Grids

Grid gadgets appear on forms where data is displayed in rows and columns, similar to a spreadsheet. The grid gadget has the capability of column grouping, column sorting and column filtering; however, the functionality differs between forms that contain these gadgets. The functionality will be explained in detail when encountered in the training guides.

3.5.10 Form Menus

Some forms contain a menu across the top of the form. Form menus have the same functionality and options as described previously for menus.

(32)

www.aveva.com

3.5.11 Actioning Form Inputs

Most forms include at least one control button which is used to either: • Enter the command option represented by the current form setting. • Cancel any changes made to the form since initially opened. • Close the form.

The OK and Apply buttons enter the current form settings as command inputs, however, the OK button also closes the form whereas the Apply button leaves the form displayed further input.

The Cancel and Reset buttons cancel any changes made to the settings of the form. Cancel also closes the form.

The Dismiss button simply closes the form.

Some forms contain more specific types of control buttons, which carry out particular command options (extensions of the Apply concept); e.g. the Goto, Add and Remove buttons.

Where a form does not contain a Dismiss button a Control form menu item is usually provided. This pull-down menu will contain a close option which dismisses the form.

Where neither a Dismiss button or Control pull-down menu are provided the form may be dismissed by clicking the Close button on the top right hand side of the form with the left mouse button. This should only be where no other option to dismiss the form is provided.

3.5.12 Alert Forms

An Alert form is used to display information such as error messages, prompts and requests for confirmation of changes. The form will usually have to be acknowledged using an OK button before proceeding.

(33)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

3.5.13 Dockable Forms

Some forms are dockable, i.e. they can be fixed in a particular place on the display. When dockable forms are initially displayed they will dock at their default position.

This position may be changed by dragging the form’s banner with the left mouse button. As the form is moved, docking icons are displayed to aid the docking process.

When the form is dragged over one of the docking aids, the docking tool previews the docking position using a shaded area of the display.

(34)

www.aveva.com

Once the required docking position has been achieved, releasing the left mouse button will dock the form in the selected position.

If a dockable form is dragged over a previously docked form, additional docking aids for docking the new form over the previous form are displayed. The additional docking aids work in the same way as previously described.

(35)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

If the central Tab button of the docking aids is used, the form being docked will form a tabbed form with the form(s) it is being dragged over.

To separate the forms, the tabbed group must be undocked first and then separated by dragging the tab away from the group.

Once a dockable form has been docked, it may also be pinned and unpinned, i.e. hidden or displayed:

Clicking the Pin (tooltip Auto Hide) button on the form header ‘hides’ the form under the tab in the adjacent edge of the display.

Passing the cursor over the tab displays the form which may be used in the normal way. Clicking the Pin button removes the tab and displays the form.

If the screen layout has been modified selecting Settings>Reset Windows Layout from the main menu will restore the screen to the previous layout in that session.

(36)

www.aveva.com

3.6 Using Toolbars

Toolbars group together gadgets, e.g. buttons, scrollable list and text boxes, for a particular set of

commands or commands related to common functionality. The gadgets on the toolbars operate in the same way as described previously for forms.

Some toolbars, usually those containing common functionality, are displayed by default, whilst others, usually containing more specialised functionality, are displayed as and when required.

Toolbars may be selected for display by clicking the right mouse button in the ‘blank’ area adjacent to the main menu to display a list of the available toolbars.

The currently displayed toolbars are indicated by the checkbox icon adjacent to the toolbar name. Selecting a toolbar from this list will toggle its display on or off, i.e. add or remove the checkbox icon.

Toolbars such as the Equipment Toolbar, Pipework Toolbar, HVAC Designer Toolbar, etc, are displayed when the appropriate application is entered. These toolbars may be displayed at other times but the gadgets contained in them will be inactive. Toolbars such as the Positioning

Control toolbar, which is common to all applications, is displayed only when an operation that may use this functionality is selected.

All toolbars may be moved by dragging with the left mouse button as per standard Windows functionality. The toolbars may be docked around any edge of the main window and in any configuration.

Most toolbars may be dragged from the main window border into another area of the screen layout to form a standalone toolbar. In this mode, the shape and configuration of the toolbar may be modified by dragging its edges.

L

Toolbars may be customised and new toolbars created, however, this functionality is outside the

scope of this training guide.

3.7 Command Window

The Command Window enables the user to directly interact with the database(s) by entering valid command syntax to manipulate, create, modify and query any database element. Reports may also be output to the Command Window.

The Command Window is a dockable form and is displayed by selecting Display>Command Line… from the main menu.

3.7.1 Entering Command Syntax

After clicking in the Command Window with the left mouse button, valid command line syntax may be entered on to the active line. Command line syntax is executed by pressing the Return (Enter) key.

There is no definitive list of command line syntax, however, the Design Reference Manuals, supplied

with PDMS, is a useful reference for Command Syntax.

Previously entered commands may be recalled to the active line by double-clicking the left mouse button on the required line in the Command Window or by using the up and down arrow cursor keys to step through previous syntax entries until the appropriate line is found. The active line may be edited before executing the command(s). Command line syntax is not case sensitive, except for names.

(37)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

3.7.2 Command Window Pop-up Menu

Clicking the right mouse button in the Command Window displays a pop-up menu with the following options:

Copy – this option allows a single highlighted line or multiple highlighted lines to be copied from the Command Window to the clipboard.

Paste – this option enables single or multiple lines of text, which has been copied to the clipboard from any source, to be submitted for processing in the Command Window. This option will execute each line of the text as a separate command, as if they had been typed into the Command Window. The last line will not be executed but becomes the active line and must be executed manually by pressing the Return key. • Paste as Macro – this option first creates a temporary file containing the copied macro commands and

executes this as a macro. This option enables macro syntax, such as error handling to be used. For a large number of commands this option gives better performance, e.g. graphics will only be updated at the end of the macro rather than after each command.

Font Size – this option has a sub-menu that allows the font size in the Command Window to be set to Small, Medium or Large:

Clear – this option clears the Command Window of all text.

L

Care should be taken when using the Command Window as all commands entered act directly on

the database elements. Some operations available from the forms and menus cannot be replicated in the Command Window. Conversely, some operations in PDMS can only be performed via the

(38)

www.aveva.com

3.8 Navigating the Databases

Being able to navigate around the databases and the database hierarchy is an essential part of successfully working with PDMS. The user interface provides several tools to facilitate navigation.

3.8.1 Design Explorer

The Design Explorer is a dockable form that provides a ‘tree’ view of the database elements in the current MDB.

Each element’s type is shown, i.e. SITE, ZONE, EQUI, etc., together with its name. Where elements have been explicitly named the name is displayed without the leading forward slash. Elements that have not been explicitly named, e.g. primitives, are displayed with their system generated name.

The tree can be expanded and collapsed by using the and icons adjacent to the database elements. The icons are only displayed where the elements own other elements.

One element in the Design Explorer will always be highlighted. This is referred to as the Current Element, often abbreviated to CE in forms, menus and documentation.

There may only be one Current Element at any one time and most commands, either via the forms and menus or the Command Window act on the CE.

Functionality for commands to act on more than one

element at a time is explained later in this training guide.

Elements that have been created or modified in a Multiwrite database with an explicit claim, or elements that are explicitly claimed, are displayed in bold text in Design Explorer until they are unclaimed.

Elements in Update databases are not displayed in bold text.

See section 7.6 – Claimlists in Multiwrite Databases for

(39)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

3.8.1.1 Design Explorer Filtering

As the databases in the current MDB may contain many thousands of elements, the Design Explorer has a filter that, when activated, restricts the display of elements for other disciplines.

For example, the current user may be a Piping Designer routing and modelling pipes.

By selecting the Piping option from the pull-down at the top of the Design Explorer and activating the filter by checking the Filter

checkbox, the Piping elements are left unaffected; however, other discipline elements are restricted.

The Equipment elements only display the Nozzle (NOZZ) primitives, if any, that they own, as the pipe may need to connect to these elements. All other primitives owned by the equipment are not displayed.

For Structural elements, no elements below the Framework (FRMW) level are displayed.

The other filter options, e.g. Hangers&Supports, Equipment and Structural function in a similar way. The filters cannot be extended or edited.

3.8.1.2 Design Explorer Pop-up Menu

Clicking any element in the Design Explorer with the right mouse button displays a pop-up menu with the following options:

3D View - this option has a sub-menu and enables elements to be displayed or removed from the 3D View.

This functionality is covered in Chapter 4, Displaying

Modelled Elements.

Show Attributes – this option displays the Attribute form for the Current Element.

See Chapter 6 for details of querying, displaying and

modifying attributes.

(40)

www.aveva.com

The element name may be modified by entering a new name in the Name text box and clicking the Apply button.

The pull-down menu options are: • Only – renames only the CE

Re-name all – renames the CE members, if any, that have derivative names of the CE. • Un-name – un-names the CE so that its Name

attribute is unset. Delete – this option deletes the Current Element.

A confirmation message is displayed before deletion.

Clicking the Yes button permanently deletes the CE from the database. Clicking the No button retains the CE.

Add To My Data – This option adds the Current Element to a My Data collection.

Refer to Chapter 7 General Utilities, for details of the My Data functionality.

New Explorer – This option creates a new Explorer for the Current Element and below, i.e. all elements owned by the Current Element.

(41)

AVEVA Plant (12 Series) PDMS Foundations TM-1001

www.aveva.com

The New Explorer option has a context sensitive sub-menu, i.e. its options depend on the element type of the current element. The CE and its owner will always be two of the options, however, significant attributes will also be available, depending on the element.

Copy – this option copies the Current Element to the clipboard.

Paste – this option copies a valid element from the clipboard to the current location in the Design Explorer, providing it is within the same database, i.e. elements cannot be copied across databases using this functionality.

If the element is named, the pasted element is named Copy-of-nnnn, where nnnn is the name of the Current Element. Where more than one copy of a named element is pasted the second and subsequent elements will contain a sequential copy number, e.g. Copy-(2)-of-nnnn, Copy-(3)-of-nnnn, etc. If the element is unnamed, the pasted element is allocated a system name.

L

It is possible to copy and paste an element in Design Explorer using Drag & Drop functionality. Holding

down the Ctrl key and the left mouse button on the CE and moving the pointer, a line is displayed showing the potential location of the copy. Releasing the left mouse button creates a copy of the CE. The same naming conventions apply as described above.

3.8.1.3 Explorer Settings

Selecting Settings>Explorer… from the main menu displays the Explorer Settings form.

The form contain check boxes that toggle the following settings: • Auto Collapse Tree – If selected, whenever the user changes CE,

any expanded node not containing the selected CE is automatically collapsed. This applies to all active explorers. This option is

disabled if Expand to CE is not selected.

Expand to CE – If selected, this option automatically expands the tree when the CE changes (if not already expanded).

Hide non-writable Template Worlds – If selected, this option hides all non-writable Template Worlds in Design Explorer. • Show TUBI/ROD – If selected, this option displays all TUBI and

ROD elements in Design Explorer.

L

TUBI and ROD elements are Piping and Cable Tray

components respectively. These elements are discussed in the appropriate discipline training guide.

The Draft Explorer section of this form is outside the scope of this training guide. See TM-1002 Drawing

(42)

www.aveva.com

3.8.2 Members List

The Members list was the pre-cursor to Design Explorer in previous versions of PDMS. Although lacking much of the functionality of Design Explorer it remains a valuable part of the PDMS user interface for database navigation.

The Members list is a re-sizeable form that displays the database elements in the current MDB. Unlike Design Explorer, only the CE members and owners are displayed.

Clicking on an element in the Members list makes it the CE and the display changes accordingly. The CE is identified by highlighting, blue when selected and grey otherwise (depending on the Windows Settings). An element name may be entered in the text box at the top of the form. Pressing the Return key navigates to the element, if found, and makes it the CE.

If the element name is invalid and/or not found a Cannot access element “nnnn” error message is displayed, where “nnnn” is the entered name.

The left and right arrows either side of the text box enable up (left arrow) and down (right arrow) navigation from the CE at the same element level, i.e. with an EQUI element as the CE, clicking the right arrow would go to the next EQUI element, if it exists, in the owning ZONE and make it the CE. Clicking the left arrow would go to the previous EQUI element, if it exists, in the owning zone and make it the CE.

If there is no previous or next element of the same type a List exhausted for nnnn error message is displayed, where nnnn is the name of the owning element.

Selecting the GoTo>Reference… option on the form menu displays the GoTo Reference form:

The contents of the form depend on the element type. For some elements, e.g. ZONE, EQUI, etc., limited attributes are displayed. For other elements, e.g. NOZZ, PIPE, BRAN, etc., more attributes are displayed.

For elements with Catalogue or Specification References, clicking these attributes with the left mouse button will navigate to them in the GoTo Reference form and the Members list, thus enabling navigation within reference databases.

Figure

Updating...

References

Updating...