05_Getting Started With PDMS

Getting Started With PDMS

AVEVA Solutions Ltd

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

CopyrightCopyright 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 Ltd. 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 Ltd, 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 license agreements, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited. First published September 2007 AVEVA Solutions Ltd, and its subsidiaries AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. 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, trade mark rights, or other intellectual property rights in any other product, its name or logo belongs to its respective owner.



Contents

Page

Getting StartedScope of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1What it Includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

How the Manual is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

PDMS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Using PDMS in the Plant Design Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2 PDMS Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3DESIGN Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drafting Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catalogue and Specification Management Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Project Administration Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3 2:4 2:6 2:7

PDMS Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 Database Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Project .............................................................. DESIGN Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PADD Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISOD Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CATALOGUE Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DICTIONARY Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PROPERTIES Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1 3:2 3:2 3:2 3:2 3:3 3:3

i

12.0


SYSTEM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COMMS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MISC Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANSACTION Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3:3 3:3 3:3 3:4

How PDMS Data is Stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1DESIGN Database Element Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2WORLD .............................................................. SITE .............................................................. ZONE .............................................................. EQUIPMENT (EQUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SUB-EQUIPMENT (SUBE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PRIMITIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STRUCTURES (STRU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FRAMEWORK (FRMW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SUB-FRAMEWORK (SBFR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STRUCTURAL COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIPE .............................................................. BRANCH (BRAN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIPING COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 4:2 4:2 4:2 4:3 4:4 4:4 4:4 4:4 4:5 4:5 4:5 4:5

Attributes in PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:7 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8 POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 ORIENTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9 OBSTRUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 HEIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 DIAMETER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10

UDAs (User Defined Attributes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Pseudo-Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10 Attributes Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:10

Using PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Logging into PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2

ii

12.0


Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDB .............................................................. Module .............................................................. Read Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5:3 5:3 5:4 5:5 5:5

Exit out of PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5 Internationalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Customisation Facilities; The Programmable Macro Language (PML). . . . . . . 5:7

Basic GUI Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Using Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Text Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop-down Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Option Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scrollable Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2 6:2 6:2 6:3 6:3 6:3

Menus

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4

Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:4 Respond to Alert Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Dockable Forms, Toolbars and Menu Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Menu Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6

Using Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10Why use Command Syntax? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10 Command Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10 Note on Filenames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11

Basic Operations in PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Querying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Current Element and Current List Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 Navigate to a Given Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3Design Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4 Members List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:5

iii

12.0


Other Explorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6 My Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7

Modify the Content of a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8 Drawlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:87:10 7:11 7:11 7:11 7:19 7:20 7:20 7:20 7:20 7:22 7:24 7:24 7:26 7:27 7:27 7:28 7:28 7:28 7:30 7:30 7:32 Change the Visual Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display of Graphical Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display of Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Drawlist Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saved Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Saved Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete a Saved Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explorer Bar Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Search Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality on the Search Output Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Move around the Grid using the Keyboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grid Splitting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pin Rows and Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Row and Column Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Column Re-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Column Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Column Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Numeric Data Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Group Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Grid Data Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PDMS Search Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:14

GUI Grid Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:24

Reference List Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:32Which Elements will be displayed in the Reference List? . . . . . . . . . . . . . . . . . . . . . . . . . 7:33 Using the Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:33

Product Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1

Glossary of Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . 9:1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:5

iv

12.0


Core Filters for Explorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1

v

12.0


vi

12.0

Getting Started With PDMSScope of this Manual

11.1

Scope of this ManualWhat it IncludesThis manual provides an introduction to PDMS as a system and describes some functions which are common to several disciplines. The manual gives an introduction to what PDMS does and how it does it, including introductions to: the PDMS modules and what they do the PDMS databases the PDMS user interface.

More detailed information, particularly on the PDMS modules and the databases they use, can be found elsewhere in the PDMS user documentation set.

1.2

Who Should Use this ManualThe manual is written for a new user who is: or migrating from a similar 3D system. Both types of user will probably, but not necessarily, have attended a PDMS Basic Training course. coming to a 3D Plant Design Management System (i.e. PDMS) for the first time

1.2.1

AssumptionsIt is assumed that the user: is familiar with Microsoft Windows 2000 and/or XP has a reasonable understanding of the principles and jargon of process plant design.

1:1

12.0

Getting Started With PDMSScope of this Manual

1.3

How the Manual is OrganisedThe manual is organised as follows: PDMS Functions PDMS Databases and How PDMS Data is Stored Using PDMS, Basic GUI Features and Basic Operations in PDMS Product Range Glossary of Terms and Abbreviations introduces the basic steps to be taken to design a Plant using PDMS, and introduces the PDMS modules. introduce the PDMS databases and the way data in PDMS is structured and how it is stored. describe how to get in to PDMS and use it perform simple operations. shows the AVEVA product ranges. is a glossary of PDMS terms and abbreviations.

1:2

12.0

Getting Started With PDMSPDMS Functions

2

PDMS FunctionsPDMS (the Plant Design Management System) enables you to design a 3D computer model of a process plant. PDMS allows you to see a full colour-shaded representation of the plant model as your design progresses, adding an extremely impressive level of realism to traditional drawing office techniques. 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 passed on. These range from reports on data stored in the databases, fully annotated and dimensioned engineering drawings, to full colour-shaded 3D walk-through capabilities which allow you to visualise the complete design model.

Even with the advanced features of PDMS, the main form of communication between the plant designer and the fabricator remains the drawings. Without engineering drawings the task of building a plant would be almost impossible. To meet this requirement, PDMS can

2:1

12.0


produce numerous types of drawing, ranging from complex 3D illustrations to fully annotated and dimensioned arrangement drawings and piping isometrics. All the data in a PDMS design would be of little value without the ability to ensure the quality of the design information. PDMS contributes to the quality of the design in the following ways: Ensures consistent and reliable component data In a design environment which uses only 2D drawing techniques, the size of each fitting must be decided before it can be drawn. This is a time-consuming and errorprone process, where often the design errors 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. 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, Hangers and Supports, HVAC, Cable trays and Steelwork all use specifications to assist 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 drawing 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. Potential problems can thus be resolved 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.1

Using PDMS in the Plant Design ProcessThe sequence of operations (greatly simplified) in a new plant design project would be: Create the project and set up administrative controls (using the PDMS ADMIN module). Create the Catalogue and Specification data from which standard design Components can be selected (using the PARAGON module). Design the various parts of the plant, referencing items from the catalogues (using the DESIGN module). Check the design for errors and inconsistencies (DESIGN module).

2:2

12.0


Document the design in the form of drawings (general arrangement, construction, assembly, and isometric), reports and material lists (DRAFT and ISODRAFT modules).

You may also wish to transfer design data to or from other systems at various stages.

2.2

PDMS ModulesPDMS is split into a number of modules which are used at different stages in the plant design process.

2.2.1

DESIGN ModulesDESIGN DESIGN is the main, graphically driven constructor module. It enables a full sized threedimensional plantmodel to be defined in the design database, with selected views of the current state of the design shown on the graphics screen as the design progresses. All parts of the design (including equipment, and piping and structural steelwork layouts) can be created. Component selection is provided through Specifications that dictate which Catalogue Components can be used. Each part of the design model can be displayed in colour-shaded solid colour-coded representations for ease of interpretation. The DESIGN module can check for interferences (clashes) between items created in the design. There is a very flexible reporting capability that can be used to produce a wide variety of design documents - from bulk Material Take Off to detailed nozzle schedules. Piping isometrics can be previewed in DESIGN (without having to switch to the Isometric drawing generation module, ISODRAFT).

2:3

12.0


SPOOLER SPOOLER is used for pipework spooling. It allows the designer to split the pipework design into logical sections (spools) ready for fabrication. The spool data can then be output as isometric drawings using ISODRAFT (see below).

2.2.2

Drafting ModulesDRAFT DRAFT enables dimensioned and annotated scale drawings of selected parts of the design model to be produced. All information needed to create the drawing is accessible via a single drawing database, which extracts data to be used for dimensioning directly from the DESIGN database. Annotation can be in the form of labels attached to DESIGN elements, or 2D annotation such as drawing notes, or 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 recalculated automatically every time the drawing is updated. A design model 3D view can be previewed in DRAFT to aid assembly of a drawing in the 2D view.

2:4

12.0


Diagrams Diagrams supports the creation of cabling diagrams. The application is based on the AVEVA Design Platform GUI and diagram layouts are created using an embedded Microsoft Office Visio drawing control. All relevant data entered through the application is stored into the Schematic Database. Schematic Model Manager Schematic Model Manager is used to import P&ID data into Schematic databases and have the ability to view and manage the data. The P&ID data is imported from a XML file, the content of which complies to ISO15926. ISODRAFT ISODRAFT produces automatically annotated and dimensioned piping isometric drawings, with associated material lists, of specified sections of the plant pipework. The content and style of the drawings can be chosen to suit the needs of pipe fabricators and/or erectors and can include a wide range of optional features to suit local requirements. Other facilities include: Full material lists. Automatic spool identification. Automatic splitting of complex drawings. User-defined drawing sheets.

2:5

12.0


2.2.3

Catalogue and Specification Management ModulesPARAGON Used to generate and modify catalogues, with facilities for catalogue component construction with visual control (including 3D colour-shaded representations of the item being designed). 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 steelwork, piping, and HVAC and cable tray components. 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. SPECON Used by the administrator to create or modify the component specifications within the catalogue database. Specifications define the suitability of catalogue components for particular types of use. PROPCON Used by the administrator to create or modify the properties database, which holds details of those properties of the components and materials which may be needed for stress analysis or safety auditing of all or part of a design. It also includes data such as the material

2:6

12.0


densities needed by the DESIGN module structural applications for calculating weights and centre of gravity of steelwork items.

2.2.4

Project Administration ModulesADMIN Large plants designed using PDMS will usually be broken down into individual areas (either physical areas or design areas), depending on the physical 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. The main features are: Access Control (Teams and Users) Databases Multiple Databases (MDBs) Database management functionality

ADMIN includes a database integrity checking utility, used to check for inconsistencies in the contents of the databases and to derive statistical information about the use of the database storage capacity. ADMIN also allows the System Administrator to reconfigure a project. This may be necessary: to compact databases at intervals, freeing disk space to upgrade PDMS projects when the database structure changes to compare the contents of two similar databases; for example, to create a modification record

LEXICON Used by the System Administrator to set up user defined attributes (UDA) and user defined defined element types (UDET). Both are defined in a DICTIONARY database. User defined element types allow objects in a database to be given a user defined name to replace the generic name, for example an EQUI element can be called a :PUMP or :VESSEL. Additional information can be stored in user defined attributes assigned to database elements and extracted into drawings and reports. MONITOR Module The MONITOR Module is commonly used to query the status of a projects users and access rights. MONITOR allows basic querying of database information which normally can only be obtained using the ADMIN Module (which can only be accessed by a Free user). MONITOR can also be used to quickly change a password of the currently logged in user or completely switch to another user (if the user credentials are known).

2:7

12.0


Depending on the user type (Free or General), MONITOR can be used to change access rights and defer databases. Batch processing and simply messaging can also be achieved. If there is a problem with a project that inhibits another PDMS module from loading, then the software will automatically load the MONITOR Module allowing simple diagnostics to be conducted via its command line interface. For a detailed explanation of the MONITOR Module refer to MONITOR Reference Manual.

2:8

12.0

Getting Started With PDMSPDMS Databases

33.1

PDMS DatabasesIntroductionThe overall purpose of PDMS is the controlled creation of a complete three-dimensional process plant design model using computer-simulation techniques. All information which exists about a PDMS design project, whether administrative or technical, is stored in a series of hierarchical databases. Use of the various PDMS modules allows you to create, modify and extract information from these databases. This chapter describes The purpose of each type of database How the detailed project information is held in each How the separate databases are related to each other

3.23.2.1

Database TypesProjectA PDMS Project consists of the complete collection of information which relates to a single design project. This is identified by a name, allocated by the Project Administrator when the project is first initiated. This name is used to identify the project to the system whenever you wish to work in the project using PDMS. This allows access rights and use of system resources to be monitored and controlled. For further details of these functions, see the Administrator User Guide and Monitor Reference Manuals. There are 10 different types of database which can go to make up a complete Project: Design and Drawing Databases: DESIGN database PADD (DRAFT) database ISOD (Spooler) database

Reference Databases: CATALOGUE database LEXICON (Dictionary) PROPERTIES database

Administration Databases: SYSTEM database COMMS database

3:1

12.0


MISC database TRANSACTION database

(Refer to the Administrator User Guide for more background information on Reference databases). Each PDMS module requires access to one or more specific database types, and entry to the module may be prevented if appropriate databases do not exist or if you dont have the appropriate access rights. New databases can only be created by the Project Administrator; see the Administrator User Guide for details. The functions of each type of database are summarised in the following subsections.

3.2.2

DESIGN DatabaseThe DESIGN databases contain all information needed to create a full-scale threedimensional representation of the plant. Each user is normally allowed to modify the DESIGN databases which relate to his function in the plant design team, and will often have permission to look at other DESIGN databases so that his work is compatible with that of other designers. Typical design functions, each of which may use a different DESIGN database, include: Equipment design (process vessels, storage vessels, pumps, heat exchangers etc.) Pipework design (the interconnecting pipes between the various equipment items) Structural design (the columns, beams, walls, stairways etc. which support and give access to the operational equipment and pipework) Hangers and Supports (specialised pipe support structures)

The compositions of the principal types of DESIGN element are described in the Data Model Reference Manual.

3.2.3

PADD DatabaseThe Production of Annotated and Dimensioned Drawings (PADD) database holds data about both the pictorial content of drawings and about their annotation and dimensional information. It therefore holds a complete specification of the contents of a drawing. Its use is specific to the interactive drawing module DRAFT. For further information, see the Draft User Guide.

3.2.4

ISOD DatabaseThe ISOD database holds pipework spool drawings generated by the SPOOLER module. See Pipework Design User Guide for more details of SPOOLER.

3.2.5

CATALOGUE DatabaseThe CATALOGUE database contains a catalogue of the standard components which the user may select when designing pipework, ducting, hangers and supports or structural steelwork. It includes: Dimensional details for each component Details of permissible connections between different components and of the bolts needed to assemble flanged components

3:2

12.0


Specifications of the components, which define the conditions of use for each type (maximum pressure, temperature etc.)

A CATALOGUE database may contain a single universal catalogue, but it will more commonly contain a general catalogue plus one or more specialised catalogues specific to particular design functions. For further information, see the Catalogues and Specifications User Guide.

3.2.6

DICTIONARY DatabaseThe DICTIONARY database holds the definitions of user defined attributes (UDA) and user defined element types (UDET). User defined elements types allow objects in a database to be given a user defined name to replace the generic name, for example an EQUI element can be called a :PUMP or :VESSEL. Additional information can be stored in user defined attributes assigned to database elements and extracted into drawings and reports.

3.2.7

PROPERTIES DatabaseThe PROPERTIES is available for storing data about material properties, which may be needed to supplement Catalogue and Specification data for some design functions such as stress analysis. Its use is specialised and will not be described further in this manual. For further information, see the PROPCON chapter in the Catalogues and Specifications Reference Manual.

3.2.8

SYSTEM DatabaseThere is only one SYSTEM database in each Project Folder. It holds administrative information about the composition and use of the project, including the following: A list of databases of all categories which are usable in the project A list of all users, identified by name and password, who can legally access the databases, and the operating team(s) to which they are assigned A list of PDMS modules available for use in the project Access control data, which defines those databases which are accessible to any specific user and whether he may modify them or only look at them

3.2.9

COMMS DatabaseThe COMMS database stores the information about who is using which module and which databases are current. Each user has a separate area of the COMMS database, which can be accessed in write mode, and so can record module changes etc. Each user has read access to the other users areas, and so can find out about other users in the project.

3.2.10

MISC DatabaseThe MISC database is used to store inter-user messages, and inter-database macros. This database can only be opened in write mode by one user at a time, but many users can read from it. All users need to be able to write to this database, but only when they are sending messages or writing inter-database macros, or deleting messages and macros. All users can read from the database at any time.

3:3

12.0


3.2.11

TRANSACTION DatabaseTo enable the System Administrator to monitor the progress of Global commands, PDMS Global stores details of issued commands in a TRANSACTION database. Transaction messages are generated in the database each time the progress of the command changes. Transaction databases are only present when PDMS incorporates the Global product. See Administrator Command Reference Manual for details of Global.

3:4

12.0

Getting Started With PDMSHow PDMS Data is Stored

4

How PDMS Data is StoredDespite the huge power and potential of PDMS, the database is structured in a very simple and logical form. The database is hierarchical, a tree like structure, as illustrated below. Note: The hierarchy below illustrates the (simplified) DESIGN database hierarchy, but the CATALOGUE, PADD, ISOD, LEXICON and PROPERTIES databases also have a hierarchical structure.

In this hierarchical structure all the database 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.

4:1

12.0


4.14.1.1

DESIGN Database Element TypesWORLDWhen the database is first built, it is empty except for a single element named the WORLD. Every database has its own WORLD element as the first element in the hierarchy.

4.1.2

SITEBelow the WORLD, the second level of the hierarchy is the 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. There can be as many SITEs within a PDMS project as required for data organisation.

4.1.3

ZONEThe next level below a SITE is a ZONE. Again, a ZONE is not necessarily used to define a physical area, it is more likely to store similar types of item for easy reference, such as a piping system in one ZONE, related equipment in another, and so on. There can be as many ZONEs owned by a site as required for data organisation. Below ZONE level the hierarchy is discipline dependent, i.e. the elements depend on which discipline you are modelling.

4.1.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 to form the item. The primitives may be owned directly by the EQUI element or by a Sub-Equipment element. An Equipment would typically be a Pump, or a Vessel. The Box and Cylinder primitives are clearly visible in the Pump Equipment shown in figure below.

4:2

12.0


4.1.5

SUB-EQUIPMENT (SUBE)A SUBE is an optional element to further sub-divide an EQUI. The SUBE can also own primitive elements.

4:3

12.0


4.1.6

PRIMITIVESPrimitives are the basic building blocks of PDMS. They are used by other disciplines to create catalogue components. There are many types of primitive, each with its own features, which when combined with other primitives can represent complex shapes. Examples of primitives are nozzle (NOZZ), box (BOX), cylinders (CYLI) and pyramids (PYRA).

4.1.7

STRUCTURES (STRU)STRU elements are administrative elements, i.e. they exist to own FRAMEWORK elements, and allow the plant structures to be separated for ease of modelling and reporting.

4.1.8

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. Structural components may also be owned by a Sub-Framework element.

4.1.9

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

4:4

12.0


4.1.10

STRUCTURAL COMPONENTSStructural profiles are represented in PDMS by section (SCTN) elements. I-section profile sizes are selected using a Section Specification that references standard catalogue data for section sizes complying with various national standards. Plates are represented by panel (PANE) elements and curved profiles are modelled using a general section (GENSEC) component.

4.1.11

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

4.1.12

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.

4.1.13

PIPING COMPONENTSA BRAN can own a wide variety of components such as gaskets (GASK), flanges (FLAN), tees (TEE), valves (VALV), elbows (ELBO), etc. These form the shape and geometry of the BRAN and ultimately the pipeline itself.

4:5

12.0


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 this remains constant no matter how many 100mm bore elbows are used in the design.

4.2

Attributes in PDMSEvery element in a PDMS database has a fixed set of properties known as its attributes. Some attributes are common throughout the range of elements while others differ according to the type of element involved. For example, a cylinder (CYLI) has HEIGHT and DIAMETER attributes whilst the size of a box (BOX) is determined by XLENGTH, YLENGTH and ZLENGTH attributes, as illustrated below:

4:6

12.0


When you create an element, a set of appropriate attributes are entered into the database. The attributes will vary according to the type of element but essentially the process is the same. For example, a cylinder has the following attributes: Attribute NAME TYPE LOCK OWNER POSITION ORIENTATION LEVEL OBSTRUCTION DIAMETER HEIGHT Default Value Name if specified or hierarchy description CYLI false (the element is not locked) the name of the owning element or its hierarchy description N 0mm E 0mm U 0mm (relative to its owner) Y is N and Z is U (relative to its owner) 0 10 (this is a representation level setting) 2 (it is a solid hard element for clashing purposes) 0 mm 0 mm

4.2.1

NAMEEvery element in PDMS can be named. Whether named or not every element will have a unique system-generated reference number. If a name is not specified, then a hierarchy description will be displayed in the Design Explorer or Members List (see Navigate to a Given Element). Internally PDMS uses the reference number since this cannot change. A table of names against reference numbers is maintained for this purpose. All PDMS names begin with a forward slash character (/), which is considered to be part of the name. In order to save you the effort of typing this, all of the forms you encounter will

4:7

12.0


add the forward slash for you when you press the Enter key after typing a name. The forward slash character is not shown in the Design Explorer or Members List. The WORLD has a special name in PDMS, /*. Names cannot contain spaces and are case sensitive. For example, /E1302A is a different name from /E1302a or /e1302A. Elements in a PDMS database are unique, i.e. they cannot have the same name or reference number.

4.2.2

TYPEThis attribute refers to the specific type of element it is, e.g. EQUI is an Equipment type.

4.2.3

LOCKThe LOCK attribute determines if an element may be changed or not. If an element is locked, its LOCK attribute is set to the value TRUE, preventing it from being modified until unlocked. By default, LOCK is false.

4.2.4

OWNERThe different levels in the hierarchy are maintained by an Owner-Member relationship. An EQUI will have ZONE as its owner, while a CYLI might well be one of the EQUIs members. The owner is that element which is directly related to the current element at the next level up in the hierarchy, as shown in the diagram below:

4:8

12.0


The element on the upper level is the Owner of those elements directly below it, e.g. the equipment (EQUI) owns the primitive (CYLI). The lower level elements are Members of the owning element, e.g. the EQUI is a member of the ZONE.

4.2.5

POSITIONMany items in a database have a POSITION attribute which is the position of the element in relation to its owner. All primitives have a position attribute which relates to its point of origin. As each primitive has a different Point of Origin changing the position attribute will have the effect of moving the cylinder to some other position with its point of origin positioned on the new co-ordinates.

4.2.6

ORIENTATIONBy default, a cylinder is created in a vertical direction; that is, with one of its ends facing up. The orientation attribute allows this to be changed to any angle on any axis.

4.2.7

LEVELPDMS can produce different representations of an item, depending on how it has been modelled and the representation levels used. The default level is 0 to 10 but levels can be set beyond this range if needed. For example, steelwork profiles can be represented by centreline (stick representation) only or by the full detail of the section profile. By manipulating level settings it is, therefore, possible to have simple or complex representation of elements for DESIGN display or DRAFT drawings.

4:9

12.0


4.2.8

OBSTRUCTIONThe OBSTRUCTION attribute is used to declare whether an element is solid or not. Obstructions can be declared as Hard, Soft or No Obstruction, depending on the value of the OBSTRUCTION attribute. The default value of 2 results in a Hard obstruction, 1 results in a Soft obstruction (used for walkways, maintenance access etc.) and 0 is for No Obstruction (used to save computing time when elements are enclosed in another element which acts as an overall obstruction).

4.2.9

HEIGHTThe height of the cylinder.

4.2.10

DIAMETERThe diameter of the cylinder.

4.3

UDAs (User Defined Attributes)This type of attribute is defined and assigned to elements using the LEXICON module by the System or Project Administrator. A UDA is just like any other attribute but may be specific to the company or the particular project. The setting of the UDA is up to the user, although it may have been set to a default value. Changing this is the same as with all other attributes. Their current values may be found by querying the items attributes. A UDA can be recognised by the colon placed in front of it: :COLOUR :HEIGHT (User Defined Attribute) (Normal Attribute)

4.4

Pseudo-AttributesThese are attributes that are set by the system for a specific purpose, and cannot be changed by the user.

4.5

Attributes FormThe Attributes Form displays all the attributes that have been specified for a database element. The form is accessed by selecting Display>Attributes Utility from the Design main menu bar:

4:10

12.0


The left hand column shows the names of the attributes, the right hand column shows the values. A brief description of the attribute is provided at the bottom of the form. All data in the form is read-only; it is not possible to add or delete attributes, or to change their values. Invisible attributes are not shown on the form (these are set by the system or Project Administrator using the LEXICON module). Attributes are grouped according to the categorisations; these are also set in LEXICON. The form above shows three attribute categorisations: Construction, General and Misc. If an attribute does not have a categorisation, then it is assigned an appropriate draft categorisation in the Attribute Form. The form can be docked, floating and resized. Icons at the top of the form determine how the attributes are listed:

4:11

12.0


When the left icon is selected, the attributes are grouped by Category or by Data Type, as determined by selecting the appropriate options from the right-click menu (described below). When the middle icon is selected, all the attributes are listed alphabetically, regardless of Category or Data Type. Right-clicking anywhere on the form displays a pop-up menu with the following options:

Track CE - By default the form will track the current element. That is, if the current element is changed in the Design Explorer or 3D View, the forms content will change to display the attributes of the new current element. This menu option toggles tracking on or off. Groups by Category - The attributes are grouped according to Category (which are set in LEXICON). The Category icon at the top of the form also needs to be selected. Group by Data Type - The attributes are grouped according to their data type, i.e. Boolean, Double, Element, Hyperlink, Integer, Orientation, Position, String and Word. The Data Type icon also needs to be selected. Show Description - Used to hide/show the description field at the bottom of the form. Collapse All Nodes - Collapses all nodes in the list - equivalent to clicking on all the - icons on the left hand side of the form. Expand All Nodes - Expands all nodes in the list - equivalent to clicking on all the + icons on the left hand side of the form. Open Document - For an attribute of data type hyperlink, the pathname of a referenced document will be displayed in the Value field. Selecting this option opens the referenced document. It will be opened outside PDMS; PDMS does not control access rights to the document. Array attributes are shown with each member of the array listed separately, using a space as the separator, as shown in the following example:

4:12

12.0


4:13

12.0


4:14

12.0

Getting Started With PDMSUsing PDMS

55.1

Using PDMSLogging into PDMSAssuming PDMS has been correctly installed on your workstation, start PDMS by selecting Start>Programs>AVEVA>Plant 12.0>Run Plant; two command windows and a splash screen will appear briefly. The Login form that appears requires you to specify a number of details at the outset of your session.

To enter PDMS, you must first click on the Login form to make it active. The form should be populated in the following order.

5.1.1

ProjectIn the Project field enter a three letter project code. Alternatively a long project identifier can be entered if one has been created by the System Administrator. Clicking on to the right of the field will open the following PDMS Projects form.

5:1

12.0


This form lists all available PDMS Projects. Clicking on the Sort by pull down allows the sorting of the list of available projects. The following selections can be made. Project Project Code Name Description

A filter may also be applied to the list of available projects by entering a criteria in the Filter field; an asterisk may be used as a wildcard. Note: The Filter field only applies to the Project column of the list of available projects. Clicking on a project will result in the PDMS Projects form closing and the selected project will be populated in the Project field of the Login form.

5.1.2

UsernameA username will have been allocated to you by the System Administrator. Clicking on to the right of the Username field will open the Select User form.

Click on the Sort by pull down allows the sorting of the list of available users in a project. The following selections can be made.

5:2

12.0


Name Description

A filter may also be applied to the list of available projects by entering a criteria in the Filter field; an asterisk may be used as a wildcard. Note: The Filter field only applies to the Name column of the list of available users. Clicking on a user will result in the Select User form closing and the selected user will be populated in the Username field of the Login form.

5.1.3

PasswordA password will have been allocated to you by the System Administrator. Passwords are case sensitive, be sure to enter correctly. Clicking on the Change button to the right of the password field will allow the user to change the password for the selected user. You will be prompted to enter your current password, a new password and to confirm the new password.

5.1.4

MDBNote: Before attempting to enter a value for the MDB field make sure that a valid username and password has been entered. You will not be able to proceed if not the case. In the MDB field enter the name of a Multiple Database you wish to use. Clicking on to the right of the field will open the Select MDB form.

5:3

12.0


Clicking on the Sort by pull down allows the sorting of the lists of available Multiple Databases. The following selections can be made: Name Description

A filter may also be applied to the list of available projects by entering a criteria in the Filter field; an asterisk may be used as a wildcard. Note: The Filter field only applies to the Name column of the list of available MDBs. Clicking on a MDB will result in the Select MDB form closing and the selected MDB will be populated in the MDB field of the Login form.

5.1.5

ModuleFrom this pull down select the PDMS Module to launch, the following options are available. MONITOR DESIGN DIAGRAMS SCHEMATIC MODEL MANAGER SPOOLER DRAFT ISODRAFT PARAGON SPECON PROPCON LEXICON ADMIN

5:4

12.0


5.1.6

Read OnlyTo modify the database as you work, leave the Read Only check box unchecked. Only select this option to view the project in the Read Only mode. Click on the OK button to enter the selected module.

5.1.7

Restore ViewsThis Restore views check box is only available when DRAFT is selected in the Module pulldown. Restore views effectively restores the layout of all forms and re-opens the last known project at the point where it was left when the Draft application was exited from a previous session. If the Restore views box is checked then the following will take place immediately when the Draft module is loaded: Re-position all forms to the locations they were left in the last open session. Automatically conduct a Get Work operation. Position the current element in the Draft Explorer to the selected element in the last session.

5.2

Exit out of PDMSYou will normally leave PDMS directly from the application module in which you are working. You may either save all work done in the current module before leaving or you may quit directly without updating any databases. Select Design>Exit: All the modules have an Exit menu selection; the one shown below being for DESIGN: If you have made changes prior to selecting Exit and have not carried out a SAVEWORK operation, you will be asked if you first wish to save your changes to the appropriate database:

Clicking YES at this point would be the equivalent of doing a SAVEWORK (and then a QUIT). If you have done a SAVEWORK (and made no subsequent changes), or if you have made no changes at all during your Design session, then Exit will display a message asking you to confirm that you wish to leave DESIGN:

5:5

12.0


In every case, when you leave PDMS you will be returned to the operating system at the point from which you entered PDMS.

5.3

InternationalisationMicrosoft produces many localised variants of Windows. AVEVA products are designed to work in English on all of these, though they do not currently support the use of all the local languages. At the time of writing, AVEVA provides limited facilities that vary somewhat between products. Users of PDMS need to enter data (text and names) using their local language and output the same onto deliverables such as drawings, reports etc. In some cases, there is also a need to localise or translate the user interface. The same data are also required in other products such as AVEVA Plant Design Review. By default, your PDMS project can use any language whose characters are contained within the Latin-1 character set, comprising: Danish Finnish Spanish Swedish Dutch French German Italian English Icelandic Norwegian Faroese Irish Portuguese

PDMS can also support the following groups of languages: Far Eastern, comprising: Japanese Korean Simplified Chinese Traditional Chinese

Latin-2, comprising: Albanian Hungarian Serbo-Croatian Czech Polish Slovak English Rumanian Slovene German

5:6

12.0


Latin-Cyrillic, comprising: Bulgarian Macedonian Byelorussian Serbo-Croatian English Ukrainian Russian

PDMS does not support any other character set/language, nor does it support the mixing of any of the above except the mixing of one Far Eastern language with English. PDMS must know if you are using a non-Latin-1 language in order to display characters correctly on drawings. To use an alternative character set/language: You must use an appropriate version of Windows and a suitable keyboard. You must select the appropriate options from the Windows Options. , Regional

For further details, see the PDMS and Associated Products Installation Guide, also the Administrator User Guide for details of font families.

5.4

Customisation Facilities; The Programmable Macro Language (PML)Most PDMS modules make use of a Graphical User Interface (GUI) to drive the software. The interfaces provided with PDMS are designed to apply to a wide range of situations and business needs. However, as you become more experienced with PDMS you may wish to design an interface which is more closely related to your requirements. You do this using AVEVAs Programmable Macro Language (PML). For full details of PML, refer to the Software Customisation Guide and the Software Customisation Reference Manual. Before you begin customising a GUI, you must have a good working knowledge of the command syntax for the module you are working with. The commands are described in detail in the reference manuals for the modules. The ability to customise individual Applications to suit your own specific needs gives you great flexibility in the ways in which you use your system. But it also introduces the risk that your modified macros may not be compatible with future versions of the software, since they are no longer under AVEVAs control. Your own Applications may diverge from future standard versions and may not take advantage of product enhancements incorporated into the standard product. To minimise this risk, it is most important that your in-house customisation policies constrain any changes which you make to the Applications so that they retain maximum compatibility with the standard product at all times. Remember that AVEVA can give you full technical support only for products over which it has control. It cannot guarantee to solve problems caused by software which you have written yourself.

5:7

12.0


5:8

12.0

Getting Started With PDMSBasic GUI Features

6

Basic GUI FeaturesPDMS uses a Graphical User Interface (GUI) using forms (dialogue boxes) and menus with which Microsoft Windows users should be familiar. This chapter describes those GUI features which are specific to PDMS.

6.1

Using the MouseYou use the mouse to steer the pointer around the screen and to select or pick items by using the mouse buttons. The buttons perform different tasks depending on the type of window, and the position within the window, where the pointer is positioned. The appearance of the pointer changes according to the type of display item that is underneath it. The left-hand mouse button has three functions: On a graphical view, clicking the left-hand button with the pointer over a design element results in that element becoming the current element (that is, the design item on which you want to carry out the next operation). In a sequence of menus, dragging with the left-hand button activates the command represented by the highlighted menu option when the button is released. On a form, the effect varies according to what you select.

The middle mouse button is used primarily to manipulate a graphical view. The right-hand button is used to access the menu options specific to the graphical view window, or items listed on a form.

6.2

Using FormsForms are used both to display information and to let you enter new data. Forms typically comprise an arrangement of buttons of various types, text-boxes, and scrollable lists. Input to a form is usually via a combination of mouse and keyboard. While you have access to a form, you can change a setting, return to the initial values, accept and act on the current data, or cancel the form without applying any changes, according to the nature of the form. Forms can include any of the following: text boxes drop-down lists option buttons check boxes scrollable lists

6:1

12.0


action buttons.

6.2.1

Text Boxes

Text boxes are the areas where you type in alphanumeric data such as names or dimensions. A text box will usually have a label to tell you what to enter. When you first open a form which contains text boxes, the first text-box on the form is current and a text editing cursor (a vertical bar) is displayed in the box. A text-box often contains a default entry (such as unset) when first displayed. Some text boxes accept only text or only numeric data, and entries with the wrong type of data are not accepted. To enter data into a text box: Click in the box to insert the text editing cursor. Type in the required data, editing any existing entry as necessary. (You may need to delete the existing entry first.) When you have finished, confirm the entry by pressing the Enter (or Return) key. Any text box with an unconfirmed setting is highlighted by a yellow background.

6.2.2

Drop-down ListsDrop-down lists let you choose one option from a multiple selection. The list will usually have a label to tell you what you are setting and will show the current selection. They typically have the following appearance:

To change the setting, click on the down arrow or button face to reveal the full list of available options, then pick the required option.

6.2.3

Option ButtonsOption buttons are used to select one option, from a group of options. The selection is mutually exclusive, so that selecting one option deselects others in that group automatically. They typically have the following appearance: Option selected Option not selected To change the selected option button in a group, click the required button.

6:2

12.0


6.2.4

Check BoxesCheck boxes are used to switch an option between two states, typically set and unset. Unlike option buttons, they do not interact, so that you can set any combination of check boxes at the same time. They typically have the following appearance: Set Unset

6.2.5

Scrollable Lists

A scrollable list is displayed as a vertical list of options within a form, with vertical and horizontal scroll bars along its sides. To select an option, click on the line you want. The selected line is highlighted. Some scrollable lists let you make only a single selection, so that selecting any option deselects all others automatically. Other lists let you make multiple selections, with all selected options highlighted simultaneously. You can deselect a highlighted option in a multiple-choice list, by clicking on it again (repeated clicks toggle a selection).

6.2.6

Action ButtonsMost forms include one or more action buttons. You use these to tell PDMS what to do with the details you have entered in the form. The common action buttons are: Tells the system to accept the current form settings, and closes the form. Cancels any changes you have made to the form, and closes the form. Tells the system to accept the current form settings, and leaves the form displayed for further use. Cancels any changes you have made to the form, and leaves the form displayed for further use. Closes the form, keeping the current settings.

6:3

12.0


Some forms contain more specific types of control button which carry out particular command options. The action is indicated by the name of the button (such Add or Remove).

6.3

MenusMenu options in pull-down or pop-up menus can be in any of three formats: Standalone options initiate an action immediately. Options followed by three dots display a form.

Options followed by a pointer, display a subsidiary menu that offers a further range of options. Throughout this guide, related selections from menus are abbreviated form using the > symbol as a separator. For example: Select Position>At>Explicit means: 1. Select Position from the bar menu. 2. Select At from the resulting pull-down menu 3. Move the pointer to the right and select Explicit from the resultant submenu.

6.4

Toolbars

Toolbars are displayed immediately below the main menu bar in the application window. Some modules are provided with several toolbars. Toolbars contain a number of icon buttons which let you carry out common tasks without searching for the options in the menus. If you hover the cursor over a button, a tool-tip pop-up box will remind you of the function of the button. To activate a button click on it. Note: Toolbars can be switched on or off by right-clicking on a toolbar or the menu bar. The names of all the toolbars available for the module will then be listed. Toolbars currently displayed will have a tick next to their names. Click on the name of a toolbar to add or remove it from the display as required.

6.5

Status Bar

The status bar displays messages telling you what actions the application is carrying out. You should look at it frequently, especially if the system appears to be waiting for you to do

6:4

12.0


something, since it will always prompt you for any input or action which is required to carry out the next step of your current activity. If the prompt lets you repeat a task an unspecified number of times, such as picking a selection of items using the cursor, you must press the Esc key when you have finished to indicate that you are ready to move to the next operation.

6.6

Respond to Alert Forms

Alert forms are used to display information such as error messages, prompts and requests for confirmation of changes. You should respond by carrying out the task prompted for, or by clicking on the control buttons on the form usually an OK or Cancel button.

6.7

Dockable Forms, Toolbars and Menu BarsCertain key forms, for example Design Explorer and My Data, and all menu bars and toolbars are provided with dockable functionality. This gives you considerable control over the layout of forms and other aspects of the graphical interface. The layout that you set up is saved when you end a design session and restored when you begin a new session. As much as possible, layouts are also maintained when switching between modules. Forms, menu bars and toolbars may be docked to any edge of the application window; forms and toolbars may be set to 'float' at any position on the screen.

6.7.1

ToolbarsTo float a toolbar, either double left-click on its move handle or circle the move handle and drag the toolbar away from the side of the main application window it is docked at. Once a toolbar is floating it will be displayed with a title bar. You can then drag the title bar to move the toolbar to a new location. To dock a floating toolbar, drag its title bar to the top, bottom, left or right side of the application window. Alternatively, double-click its title bar; the toolbar will return to its previous docked position.

6.7.2

Menu BarsMenu bars can be docked at any of the four sides of the application window, but they cannot be floated. To deck a menu bar at a new position, click the move handle menu bar to another side of the application window until it snaps into place. and drag the

6:5

12.0


6.7.3

FormsPDMS allows you to choose where to put a form by using the mouse to drag it to a new position. The following options are available: Floating on its own, in which case it can be resized to any size. Attached to any side of the main application window. Attached to any side of another form that is already docked. Attached in the same place as another docked form; tabs are used to switch between the forms. AutoHide support, to maintain an uncluttered screen.

To undock a form (i.e. floating), select the title bar and drag it to a new position within the application window. To dock a form that is floating, or to re-locate a docked form to another side of the application window, select and drag the title bar of the form. As the form is dragged the Docking Tool will be displayed:

The Docking Tool indicates the positions where the form can be docked. While still holding down the left mouse button, as the mouse pointer is moved over one of the allowable positions, a translucent coloured rectangle is drawn to show the eventual position of the form when the mouse button is released.

When moving the mouse pointer over a window that is already docked, the same Docking Tool is displayed to allow docking on any side of that window:

6:6

12.0


If the mouse button is released while the mouse pointer is over the central part of the Docking Tool, the form will be attached to the first one, with the same size and position. Each form that is attached in this way will have a tab located at the bottom of the combined form, to allow switching between the forms. The figure below shows the Design Explorer from being docked in this way to the My Data form:

6:7

12.0


When docking is complete, the display will be as shown below:

6:8

12.0


The tabbed form can be positioned and docked as for a normal (untabbed) form. An AutoHide function is available for docked forms (including tabbed forms as described above). To save space on the screen, a docked form can be unpinned (hidden) by clicking the AutoHide icon on the title bar. The form is replaced by a tab, as shown below:

When the tab is clicked the form is displayed again.

6:9

12.0


6.86.8.1

Using CommandsWhy use Command Syntax?For most purposes you will want to use PDMS via the GUI. However, by using commands you may be able to streamline your methods of working and save you time on repeated tasks. In particular, you may want to: Create macros to automate repetitive procedures (see the Software Customisation Guide and Software Customisation Reference Manual) Design and create new forms and menus for your graphical user interface that match your working needs precisely (see the Software Customisation Guide and Software Customisation Reference Manual)

In some cases it can be slightly quicker to use commands rather than the GUI for simple operations. For example: Q MEM Q ATT - list the members of the current element - list the attributes of the current element

Note: that you should always use the GUI to create elements.

6.8.2

Command WindowThe Command Window is used to type is commands instead of using forms and menus. To display the Command Window, select Display>Command Line from the main menu:

Type your command in the Command Window text box and press Enter to enter the command. The scrollable list shows the previous commands entered and any resulting output. The list will maintain approximately the last 1000 lines of output. The keyboard Up and Down arrow keys can also be used to scroll through the history of entered commands. Any line in the command window can be double-clicked to copy it as the active line.

6:10

12.0


Clicking the right mouse button in the window displays a pop-up menu: Copy Paste Copies highlighted text in the command window. Pastes copied text into the command window. Macro text, which has been copied from any source, can be submitted for processing by pasting it into the Command Window. This paste option will execute each line of the copied text as a separate command as if they had been typed into the Command Window. This option first creates a temporary file containing the copied macro commands and executes this as a macro. For a large number of commands this gives better performance. Allows you to select the font size for the text in the Command Window. The choices are Large, Medium and Small. Clears the Command Window.

Paste as Macro

Font Size

Clear

Note: Macro files can also be dragged into the command window from their location in Windows Explorer.

6.8.3

Note on FilenamesPDMS filenames can be up to 1024 characters long, and can include spaces. For example, the following command can be used within PDMS: SLIST C:\Program files\Aveva\a temporary file.txt.

6:11

12.0


6:12

12.0

Getting Started With PDMSBasic Operations in PDMS

7

Basic Operations in PDMSWork in any PDMS module is mostly about manipulating the elements and their attributes in one or more databases; either to add, change, read or delete data. You must therefore be able to tell PDMS: which database(s) you want to access. which elements in the database hierarchy you want to access. what changes, if any, you want to make to the databases contents.

This chapter tells you how to do these things.

7.1

QueryingYou will often find, when working in PDMS, that you need to check existing information about some aspect of the programs operations. For example, you may need to find out about any of the following: The current usage of the program in terms of users, modules and databases. The unique code which identifies the process you are running and the station you are running it from (useful for generating unique work file names). The current setting of a command option. The contents of part of a particular database; for example, the current setting of an attribute or the list of member elements owned by a specific element. The elements which match specific selection criteria entered by you.

Each module incorporates a Query pull-down menu which allows you to ask about some of these topics, the scope of the facility being dependent upon the particular module which you are using. For example, the Query pull-down menu for DESIGN is:

7:1

12.0


Not all of the querying operations available from PDMS can be accessed using the GUI. For these other (general) options, the QUERY command must be used.

7.2

Current Element and Current List PositionHow PDMS Data is Stored explained the principles of database structures and the concept of owners and members. This section introduces two new concepts which apply to all aspects of database navigation when you are using a constructor module. When you are working in any database, PDMS always considers you to be located at a specific element in that database. This element is known as the Current Element. The Member List of any element comprises a list of pointers to those elements directly below it in the database hierarchy; that is, to those elements which it owns. These pointers have a definite order, identified by numbered positions in the list. In addition to being notionally at the Current Element, PDMS also considers you to be at a specific pointer. This position is known as the Current List Position.

Current Element

Pointer to Current List Position

Members of Current Element 1 2 3 4

List Position in Member List

As you move about within a database, the Current Element and Current List Position are continuously updated so that PDMS always knows where you are. As soon as you access a new element, this becomes the Current Element.

7:2

12.0


To view the Current Element and its Member List (in numeric order) at any time, simply click the box next to the desired current element in the Design Explorer (see Design Explorer). The members of the current element will be shown. For example:

Alternatively, give the commands: Q CE Q MEM to display the current element to display the members list of the current element

7.3

Navigate to a Given ElementThe user normally navigates to an element by means of the Design Explorer or the Members List.

7:3

12.0


7.3.1

Design Explorer

The Design Explorer provides an easy-to-use, graphical method of exploring the Design Database. It has the following features: A Tree View display of DESIGN database elements (which can be expanded and contracted by clicking the or icons) in the current MDB. The icons in the tree view represent the different DESIGN database element types. navigation to database elements in DESIGN databases the ability to manage items in the display using the Drawlist (a separate window listing the displayed items) the ability to query the attributes of, rename, delete, copy and paste DESIGN database elements.

The current element can be identified in the Design Explorer as the highlighted item in the tree view and is displayed in the History list in the main menu bar. The History list contains a list of recently visited items.

Design Explorer replaces most of the functions of the Members List in PDMS DESIGN. The Members List is still available from the Display menu. The Design Explorer will be displayed on entry to DESIGN. If you dismiss it, it can be reinstated by selecting Display>Design Explorer from the main menu bar.

7:4

12.0


7.3.2

Members List

As with the Design Explorer, the Members List displays the database elements in the current MDB. There are a number of ways to navigate from one item to another. The and arrows at the top of the Members List allow navigation up and down the list at the level of the current element. For example, if positioned at an EQUI element, selecting next EQUI element in the list. Selecting would move to the

would move back to the previous EQUI element.

The Goto menu at the top of the form can also be used. First select this menu, then select the Owner option, this will navigate to the owner of the CE. Choosing the Goto>Reference option will give a list of further options depending on the Current Element. Goto>Reference at EQUI level will only navigate to its owner, i.e. a ZONE. If the current element were a nozzle (NOZZ) then Goto>Reference would allow navigation inside the catalogue database via the NOZZs Catref attribute.

7:5

12.0


PDMS databases may contain many thousands of elements, however, only one element can be accessed at a time. As all elements, with the exception of the WORLD, are owned by another element, deleting, say, a ZONE would cause everything owned by that ZONE to be deleted as well.

7.3.3

Other ExplorersBesides the Design Explorer (to navigate the DESIGN database), there are similar explorers in DRAFT (to navigate the DRAFT database), SPOOLER and ISODRAFT (to navigate the ISOD (spool drawings)) database and PARAGON (to navigate Paragon, Design and Properties databases). Explorer Filters A predefined set of database filters are available to reduce the amount of information presented in the Explorers. These are made up of a collection of core filters. Filters can be selected and turned on and off from each Explorer. When filtering is off the complete Database hierarchy is displayed in the Explorer. Only one system filter can be active at any given time for each Explorer. Additional preset filters are available via the Explorer Settings window for special case elements. Select Setting > Explorer from the main menu bar to display the window. These filters can be toggled on/off regardless of whether the system filters have been set. The filters are composed of the following parts: Shows- Element types to display, along with ancestors Show Descendants- Element types to display along with descendents and ancestors Skips- Element types to skip (skips only that element, ancestors and descendents still appear) Hides- Element types to hide along with descendents Hide Below- Element types to hide descendents Show Show descendents Skip Hide below Hide Shows elements relevant to piping, refer to Core Filters for Explorers. Shows elements relevant to Structural, refer to Core Filters for Explorers. Shows elements relevant to Equipment, refer to Core Filters for Explorers.

Precedence (lowest to highest)

Piping Structural Equipment

Administrator Shows elements relevant to Administration, refer to Core Filters for Explorers. Hangers and Shows elements relevant to Hangers & Supports, refer to Core Filters for Supports Explorers.

7:6

12.0


7.3.4

My Data

The My Data window is used to group data into collections. You can then carry out operations on all the items in a collection in one action. The My Data window is accessed by selecting My Data from the Display menu. Using the window, you can generate collections of database elements which you may need to work on. Each time you access the My Data window in any of the modules that use it (DRAFT, DESIGN, SPOOLER, etc), the data collections generated will be displayed. This enables elements to be easily transferred between these modules. The contents of My Data persists between applications and module switching, as well as between design sessions. The data stored is per user, per project in the PDMSUSER directory. This means that, for example, in DESIGN you could add elements to My Data and then switch to DRAFT to use the same data. Note that is the PDMSUSER directory is shared between users, those users will see the same data.

7:7

12.0


7.4

Modify the Content of a DatabaseYou would normally create, modify or delete elements using the GUI, by means of the Create, Modify and Delete pull-down menus. The options available depend on the module that you are in and the appl

Documents

05_Getting Started With PDMS