116 Gettingstarted

Getting Started with PDMS Version 11.6

pdms1160/Getting Started with PDMS issue 211004

PLEASE NOTE: AVEVA Solutions has a policy of continuing product development: therefore, the information contained in this document may be subject to change without notice. AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. While every effort has been made to verify the accuracy of this document, AVEVA Solutions shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance or use of this material. This manual provides documentation relating to products to which you may not have access or which may not be licensed to you. For further information on which Products are licensed to you please refer to your licence conditions.

© Copyright 1991 through 2004 AVEVA Solutions Limited All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of AVEVA Solutions. The software programs described in this document are confidential information and proprietary products of AVEVA Solutions or its licensors. For details of AVEVAʹs worldwide sales and support offices, see our website at http://www.aveva.com

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

Revision History Date

Version

October 2003 11.5

New manual at this PDMS version

Sept 2004

11.6

Updated to show new PDMS GUI features at this version. Cover page amended.

VANTAGE PDMS Version 11.6 Getting Started with PDMS

Notes

Revision History


Contents

Contents 1

The scope of this guide .................................................................... 1-1

1.1 1.2 1.3 1.4 1.5

What it includes ..................................................................................................................... 1‐1 What it excludes..................................................................................................................... 1‐1 Who it is meant for ................................................................................................................ 1‐1 1.3.1 Assumptions.............................................................................................................. 1‐2 How the manual is set out.................................................................................................... 1‐2 Text conventions .................................................................................................................... 1‐2

2

PDMS functions................................................................................ 2-1

2.1 2.2 2.3

PDMS and what it can do for you ....................................................................................... 2‐1 Using PDMS in the Plant Design process........................................................................... 2‐3 PDMS modules....................................................................................................................... 2‐3 2.3.1 Design modules ........................................................................................................ 2‐3 2.3.2 Drafting modules...................................................................................................... 2‐4 2.3.3 Catalogue and specification management modules............................................ 2‐6 2.3.4 Project administration modules ............................................................................. 2‐7

3

Finding out more – the user documentation and the online help .... 3-1

3.1

The User Documentation...................................................................................................... 3‐1 3.1.1 Accessing and using the documentation .............................................................. 3‐1 3.1.2 The content of the documentation ......................................................................... 3‐2 The online help....................................................................................................................... 3‐6 3.2.1 Accessing and using the help ................................................................................. 3‐6 3.2.2 The help icons ........................................................................................................... 3‐7

3.2

4

The PDMS databases........................................................................ 4-1

4.1 4.2

Introduction............................................................................................................................ 4‐1 The database types ................................................................................................................ 4‐1 4.2.1 The Project ................................................................................................................. 4‐1 4.2.2 DESIGN database ..................................................................................................... 4‐2 4.2.3 PADD database......................................................................................................... 4‐2 4.2.4 ISOD database........................................................................................................... 4‐3 4.2.5 CATALOGUE database........................................................................................... 4‐3 4.2.6 LEXICON database .................................................................................................. 4‐3 4.2.7 PROPERTIES database ............................................................................................ 4‐3 4.2.8 SYSTEM database ..................................................................................................... 4‐3 4.2.9 COMMS database..................................................................................................... 4‐4 4.2.10 MISC database .......................................................................................................... 4‐4 4.2.11 TRANSACTION database....................................................................................... 4‐4


contents-i

Contents

4.3 4.4 4.5

PDMS project structure......................................................................................................... 4‐4 4.3.1 Other projects ............................................................................................................ 4‐5 The relationships between databases ................................................................................. 4‐5 Multiple databases (MDBs) .................................................................................................. 4‐7

5

How PDMS data is stored................................................................. 5-1

5.1

5.3

The Design database element types .................................................................................... 5‐2 5.1.1 WORLD...................................................................................................................... 5‐2 5.1.2 SITE............................................................................................................................. 5‐2 5.1.3 ZONE ......................................................................................................................... 5‐2 5.1.4 EQUIPMENT (EQUI) ............................................................................................... 5‐2 5.1.5 SUB‐EQUIPMENT (SUBE) ...................................................................................... 5‐3 5.1.6 PRIMITIVES .............................................................................................................. 5‐4 5.1.7 STRUCTURES (STRU) ............................................................................................. 5‐4 5.1.8 FRAMEWORK (FRMW).......................................................................................... 5‐4 5.1.9 SUB‐FRAMEWORK (SBFR) .................................................................................... 5‐5 5.1.10 STRUCTURAL COMPONENTS ............................................................................ 5‐5 5.1.11 PIPE ............................................................................................................................ 5‐5 5.1.12 BRANCH (BRAN) .................................................................................................... 5‐6 5.1.13 PIPING COMPONENTS ......................................................................................... 5‐6 Attributes in PDMS ............................................................................................................... 5‐7 5.2.1 NAME ........................................................................................................................ 5‐8 5.2.2 TYPE ........................................................................................................................... 5‐8 5.2.3 LOCK.......................................................................................................................... 5‐8 5.2.4 OWNER ..................................................................................................................... 5‐8 5.2.5 POSITION.................................................................................................................. 5‐9 5.2.6 ORIENTATION ...................................................................................................... 5‐10 5.2.7 LEVEL ...................................................................................................................... 5‐10 5.2.8 OBSTRUCTION ...................................................................................................... 5‐10 5.2.9 HEIGHT ................................................................................................................... 5‐11 5.2.10 DIAMETER.............................................................................................................. 5‐11 UDAs (User Defined Attributes) ....................................................................................... 5‐11

6

Using PDMS...................................................................................... 6-1

6.1

6.2 6.3 6.4

Getting into PDMS................................................................................................................. 6‐1 6.1.1 Working in a module ............................................................................................... 6‐2 6.1.2 Changing to another module.................................................................................. 6‐2 Getting out of PDMS ............................................................................................................. 6‐3 Internationalisation ............................................................................................................... 6‐5 Customisation facilities; the programmable macro language......................................... 6‐6

7

Basic GUI features ........................................................................... 7-1

7.1 7.2

Using the mouse .................................................................................................................... 7‐1 Using forms ............................................................................................................................ 7‐1 7.2.1 Using text boxes........................................................................................................ 7‐2 7.2.2 Using drop‐down lists ............................................................................................. 7‐2

5.2

contents-ii


Contents

7.3 7.4 7.5 7.6

7.7 7.8 7.9

Using menus........................................................................................................................... 7‐2 Using the toolbars.................................................................................................................. 7‐3 Using the status bar ............................................................................................................... 7‐3 More on using forms ............................................................................................................. 7‐4 7.6.1 Using option buttons................................................................................................ 7‐4 7.6.2 Using check boxes .................................................................................................... 7‐4 7.6.3 Using scrollable lists................................................................................................. 7‐4 7.6.4 Using action buttons ................................................................................................ 7‐5 Responding to alert forms .................................................................................................... 7‐5 Dockable Windows, Menu Bars and Tool Bars ................................................................. 7‐6 Using commands ................................................................................................................... 7‐6 7.9.1 Why use command syntax? .................................................................................... 7‐6

8

Basic operations in PDMS ................................................................ 8-1

8.1 8.2 8.3

8.4

Querying ................................................................................................................................. 8‐1 Current element and current list position .......................................................................... 8‐2 Navigating to a given element............................................................................................. 8‐4 8.3.1 The Design Explorer................................................................................................. 8‐4 8.3.2 The Members List ..................................................................................................... 8‐5 8.3.3 Other Explorers......................................................................................................... 8‐6 8.3.4 My Data...................................................................................................................... 8‐6 Modifying the content of a database................................................................................... 8‐7

9

Interfaces to other systems............................................................. 9-1

9.1

VANTAGE Plant Enginerring (VPE) .................................................................................. 9‐1 9.1.1 VPE Workbench........................................................................................................ 9‐1 9.1.2 Introducing the VPE Workbench user interface .................................................. 9‐2 9.1.3 VPE P&ID .................................................................................................................. 9‐4 VANTAGE Plant Resource Management (VPRM) ........................................................... 9‐5 9.2.1 VPRM Interfaces ....................................................................................................... 9‐6 9.2.2 VPRM Facilities......................................................................................................... 9‐7 9.2.3 VPRM Architecture .................................................................................................. 9‐8 9.2.4 Introducing the VPRM user interface.................................................................... 9‐9 VPE and VPRM Interfaces ‐ Summary ............................................................................. 9‐10 VANTAGE Plant Design Model Management................................................................ 9‐10 9.4.1 The Model Management System core facilities.................................................. 9‐11 9.4.2 Introducing the Model Management System GUI ............................................ 9‐12 VANTAGE Enterprise NET (VNET)................................................................................. 9‐12 VANTAGE Plant Design Global........................................................................................ 9‐13 9.6.1 The Transaction database ...................................................................................... 9‐13 VANTAGE Plant Design Review ...................................................................................... 9‐13 The Data Exchange Interfaces ............................................................................................ 9‐14

9.2

9.3 9.4

9.5 9.6 9.7 9.8


contents-iii

1

The scope of this guide

1.1

What it includes

This manual is designed to introduce you to PDMS as a system and how it fits into AVEVA’s VANTAGE product family. 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. See Chapter 3.

1.2

What it excludes

This manual does not include information about: •

• • •

1.3

Facilities which are related to the computer operating system from which PDMS is entered. For information about these, see your computer operating system manuals or ask your system administrator. Facilities which apply only to a small proportion of PDMS modules. For information about these, see the user documentation or online help for the relevant modules. Detailed information on any of the PDMS modules or databases Facilities needed to create macros and use the Programmable Macro Language (PML) to create ‘intelligent’ macros, new interfaces etc. You’ll find information on these topics in the VANTAGE Plant Design Software Customisation User Guide and Software Customisation Reference Manual.

Who it is meant for

The manual is written for a new user who is: • coming to a 3D Plant Design Management System (i.e. PDMS) for the first time or •

migrating from a similar 3D system


1-1


Both types of user will probably, but not necessarily, have attended a PDMS Basic Training course.

1.3.1

Assumptions

It is assumed that the reader: • •

1.4

is familiar with typical Intel PC hardware and Microsoft Windows 2000 and/or XP has a reasonable understanding of the principles and jargon of process plant design

How the manual is set out

The manual is organised as follows: • • • • • •

Chapter 2 introduces the basic steps to be taken to design a Process Plant using PDMS, and introduces the PDMS modules. Chapter 3 describes the User Documentation set and the online help Chapters 4 and 5 introduce the PDMS databases and the way data in PDMS is structured and how it is stored Chapters 6 to 8 describe how to get in to PDMS and use it perform simple operations. Chapter 9 introduces the other products in the VANTAGE suite, which PDMS can interface with. Appendix A is a glossary of PDMS terms and abbreviations.

Note that this guide does not always provide full details of menus and forms associated with these topics. For this information see the PDMS Design online help. Direct references may be made to topics within the online help, the following device being used to indicate such references: : The 3D View Window; Creating a 3D View Window

1.5

Text conventions

This guide uses the following text conventions: Serif

Bold

for the majority of the text. to highlight important information, and to introduce special terminology.

Serif italic

to denote internal cross references and citations.

Sans-serif

to denote keys on your keyboard.

1-2



Sans-serif bold

for menu names and options, and for the names of forms.

Typewriter

text output to the screen, including text that you enter yourself using the keyboard. Also for text within a form

Note that this manual may refer to the PDMS online help, but it will not always provide full details of menus and forms associated with specific help topics. For this information see the relevant online help. Direct references may be made to topics within the online help, the following device being used to indicate such references: : The Current Session Units form


1-3


1-4


2

PDMS functions

PDMS is part of AVEVA’s VANTAGE suite of Plant Design products. PDMS can interact with the other two principal members of the VANTAGE suite, VANTAGE Plant Engineering (VPE) and VANTAGE Project Resource Management (VPRM) (see Chapter 9). Chapter 6 introduces the principles of using PDMS.

2.1

PDMS and what it can do for you

PDMS (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.


2-1

PDMS functions

Figure 2‐1 Different types of output from PDMS 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 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 error‐ prone 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.

•

2-2

Annotation and dimensions obtained directly from the design database


PDMS functions

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

Using PDMS in the Plant Design process

The 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 and Specon modules). Design the various parts of the plant, referencing items from the catalogues (using the Design module). Check the design for errors and inconsistencies (Design). 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.3

PDMS modules

PDMS is split into a number of modules which are used at different stages in the plant design process. Chapter 3 contains details of the PDMS user documentation, which describes the PDMS modules and how to use them.

2.3.1

Design modules

Design Design is the main, graphically driven constructor module within PDMS. Design enables a full sized three‐dimensional plant model 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.


2-3

PDMS functions

Design 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 generation module, Isodraft).

Figure 2‐2 A typical Design 3D View

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

Drafting modules

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

2-4


PDMS functions

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.

Figure 2‐3 A typical Draft annotated and dimensioned drawing

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

PDMS functions

Figure 2‐4 A typical Isodraft piping isometric

2.3.3

Catalogue and specification management modules

Paragon 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, where 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-6


PDMS functions

Figure 2‐5 A typical Paragon catalogue component display

Specon Used 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 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.

2.3.4

Project administration modules

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


2-7

PDMS functions

In much the same way as in a design office (with its section leader, draughts people, 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. Attributes defined in this way are held in a Lexicon (or dictionary) database and may then be assigned to elements in other databases as required. UDAs allow additional information to be stored in the databases and extracted into drawings and reports.

2-8


3

Finding out more – the user documentation and the online help

PDMS comes with an extensive set of user documents and online help files. This chapter explains how to access these resources and how to make the best use of them.

3.1 3.1.1

The User Documentation Accessing and using the documentation

The user documentation is provided as a set of Acrobat® .pdf files on the PDMS product CD. After installing PDMS, the user documentation may be found at (for example) C:\AVEVA\Pdms11.6\manuals\pdms116. This folder will contain a .pdf file called iindex.pdf, which is a contents list for the documentation set. Provided you have the Acrobat® Reader™ correctly installed on your workstation, double‐ clicking on the will give a display something like:

Using the mouse to point at one of the documents in the list and clicking the left‐hand mouse button will display the selected document in the Acrobat® Reader™ window. From here it can be read on‐screen, printed and searched through using the Acrobat® Reader™ facilities.


3-1


If you are unsure which document contains information on the topic you are interested in, button on the use the Acrobat® catalogue search facility. This is accessed from the ® ™ Acrobat Reader toolbar. Typing a keyword to search for will result in a (selectable) list of all the documents in the contents list which contain that keyword.

3.1.2

The content of the documentation

Broadly speaking, the supplied user documentation may be divided into three classes: • • •

Reference Manuals User Guides Others

Reference Manuals contain detailed information about the PDMS databases and facilities, usually at module level. User Guides (including Tutorial guides) tell you how to use PDMS to perform a particular task, and contain worked examples. Other manuals do not fit easily into either of the above classes, for example the PDMS User Bulletin. Also, there are manuals which, strictly speaking, are not PDMS‐specific but which are included in the PDMS user documentation set because they are still relevant to PDMS. In the order of the .pdf document contents list, the documents are: Title

Description

User Bulletin

Tells you about the new features and bug fixes in the current version of PDMS

Installation Guide

Tells you how to install the current version of PDMS

Structural Design Using PDMS

Tells you how to use PDMS to produce a connected steelwork structure; includes a hands‐on tutorial exercise.

Support Design Using PDMS

Tells you how to use PDMS to create pipe hangers and supports; includes a hands‐on tutorial exercise.

Pipework Design Using PDMS

Tells you how to use PDMS to create interconnected piping networks; includes a hands‐on tutorial exercise.

HVAC Design Using PDMS, Volume 1

Tells you how to use PDMS to create interconnected HVAC networks; includes a hands‐on tutorial exercise.

HVAC Design Using PDMS, Volume 2

Contains HVAC Design and Catalogue database reference material

Reporting from PDMS

Tells you how to use the reporting facilities in PDMS; includes a hands‐on tutorial exercise.

Monitor Reference Manual

Describes the command syntax available in the Monitor

3-2



Title

Description module. Useful if you wish to produce a customised interface, write macros or set up batch files.

Draft Administrator Application User Guide

Describes how to set up the Libraries used by the PDMS Draft applications. For System Administrators.

AutoDRAFT User Guide

Describes how to use the AutoDRAFT AutoCAD® application in conjunction with drawings produced by PDMS Draft and Isodraft.

Draft User Guide

The definitive Draft reference manual; mainly command syntax but with many illustrated examples; useful for those wishing to customise the interface or write macros.

Drawing Production Using Tells you how to use PDMS to create 2D drawings; includes a PDMS hands‐on tutorial exercise. Isodraft User Guide

Isodraft Reference Manual

Introduces Isodraft, PDMS’s isometric plotting facility. Explains the concepts underlying Isodraft and describes how to tailor the options to meet your own requirements. Describes the command syntax available to control the production of isometric drawings; useful for those wishing to customise the interface or write macros. Also shows the default symbol keys (SKEYs) that are used to plot the drawings, and gives examples of plotfiles. Aimed at experienced PDMS users and system administrators.

Paragon Reference Manual

Describes the command syntax available for designing catalogue components; useful for those wishing to customise the interface or write macros.

Plant Design Conventions for Catalogues and Specifications

Describes the conventions to be adhered to when constructing PDMS Catalogues and Specifications, if data inconsistencies within a project are to be avoided. Intended for specialists who are responsible for building up and maintaining the standard Catalogue databases within a PDMS project team.

Admin Command Reference Manual

Describes the PDMS Admin commands for Standard (non‐ Global) and Global projects. Written for System Administrators who are already experienced Admin users and who wish to write macros or use command input rather than the GUI.

Admin User Guide

Describes how (using the GUI) to set up and administer PDMS projects. Written for System Administrators.


3-3


Title

Description

SAINT Reference Manual

Describes, the PDMS Structural Analysis Interface module, an interface to the GTSTRUDL and STAAD‐III packages, used for the stress analysis of structural steelwork.

Access Stairs and Ladders User Guide

Tells you how to add access features to structural steelwork created using PDMS; includes a hands‐on tutorial exercise.

Data Access Routines User Guide

Describes the use of a set of FORTRAN 77 subroutines which may be incorporated into user‐written software for the purposes of navigating and manipulating the data held within a PDMS project. Can be used for the creation of interfaces to other software packages, e.g. material take‐off, pipe stress, isometrics, etc.

Plot User Guide

Explains how to use the Plot stand‐alone graphical plotting utility to interpret plotfiles in a range of pseudo‐code formats, as produced by a number of AVEVA (and third party) programs.

Data Checker Utility User Guide

Describes how to allow data consistency checking software written in AVEVA’s Programmable Macro Language (PML) to be added to PDMS Design.

Pipework Spooling Using PDMS

Tells you how to use PDMS to produce Pipework Spools from existing Pipework data; includes a hands‐on tutorial exercise.

Introduction to PDMS Design Templates

Tells you how to use the facilities provided in PDMS for the creation of Design Templates; includes a hands‐on tutorial exercise.

Design Graphical Model Manipulation User Guide

Introduces the graphical facilities available in both the Model Editor 3D View and the Model Editor itself.

Design Reference Manual Part 1

Describes general Design commands, which are used, for example, for setting up the display, and querying and navigating around the Design database. Useful for those who wish to write macros or use command input rather than the GUI.


Describes the commands for creating database elements and setting their attributes.


Contains details of all the elements which can be created in the Design database, their position in the database hierarchy and their attributes.

Design Reference Manual

Describes the Design Utilities for data consistency checking and clash detection, and for exporting Design data to

3-4



Title

Description

Part 4

programs such as Review.

Industrial Building Design Using PDMS

Tells you how to use PDMS to carry out the design and documentation of interconnected walls and floors; includes a hands‐on tutorial exercise.

Propcon Reference Manual

Describes the commands for creating and editing the Properties database.

Specon Reference Manual

Describes the commands for creating used to create or modify Specification (SPEC) elements in Catalogue Database.

Lexicon Reference Manual

Describes how to create user‐defined attributes (UDAs) for use in the Design, Draft and Catalogue databases.

Plant Design Software Customisation Guide

Describes how to use PML, AVEVA’s Programmable Macro Language. Should be used together with the Plant Design Software Customisation Reference Manual.

Plant Design Software Customisation Reference Manual

The Reference Manual for PML; intended for users who are already familiar with PML.


3-5


3.2

The online help

The online help exists to provide you with assistance with a particular feature of PDMS as you are using that feature, down to form level. (See Chapter 7 for more details of forms and menus.) The online help does not attempt to provide a structured narrative, although much reference material does exist within the help.

3.2.1

Accessing and using the help

Online help exists for all PDMS modules with a graphical user interface, namely Admin, Design, Draft, Isodraft, Monitor, Paragon and Spooler. Most bar menus end with a Help option, which gives you the following choices from its submenu: Help>Contents This displays the Help window with the Contents tab at the front, so that you can find the required topic from the hierarchical contents list. Help>Index This displays the Help window with the Index tab at the front, so that you can find all topics relevant to a selected keyword.

3-6



Help>Search This displays the Help window with the Search tab at the front, so that you can search for instances of a keyword across all the help topics. Help>About This displays information about the current operating system on your computer and about the versions of PDMS and its applications to which you have access. Pressing the F1 key at any time will display the help topic for the currently active window. The help attempts to provide you with information in a variety of ways: • • • •

‘How to’ help. Pick from a list of “how to’s”. The ‘how to’ will jump to a sequence of steps telling you how to perform the task you have selected. Context‐sensitive help. Provides help specific to the form you are using. Index search. Finds all topics relevant to a selected keyword. Keyword search. Finds all topics which contain a user‐specified word or phrase.

3.2.2

The help icons

Note: not all of the icons listed below will necessarily appear in all PDMS helps • •

• • • •

The symbol indicates a ‘book with own content’. This ‘book’ does not contain any help topics, but double‐clicking the icon will bring up the content of the book. The symbol indicates a ‘book with own content and topics’. Double‐clicking the icon will bring up the content of the book and a list of the help topics (and/or other ‘books’) contained within that book. The symbol is a ‘normal book’. Double‐clicking the icon will bring a list of the help topics (and/or other ‘books’) contained within the book. The symbol indicates an ‘ordered steps’ topic (typically a ‘How to’ topic). The symbol indicates a ‘reference topic’ giving supplementary information. The symbol indicates an ‘ordinary’ help topic


3-7

4

The PDMS databases

4.1

Introduction

The 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

4.2

The database types

4.2.1

The Project

A PDMS Project consists of the complete collection of information which relates to a single design project. This is identified by a three‐character 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 VANTAGE PDMS Admin 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 database ISOD database

Reference Databases: • • •

CATALOGUE database DICTIONARY database PROPERTIES database


4-1

The PDMS databases

Administration Databases: • • • •

SYSTEM database COMMS database MISC database TRANSACTION database

(See section 4.4 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 don’t have the appropriate access rights. New databases can only be created by the Project Administrator; see the PDMS Admin Reference Manual for details. The functions of each type of database are summarised in the following subsections.

4.2.2

DESIGN database

The Design databases contain all information needed to create a full‐scale three‐dimensional 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 database are described in the PDMS Design Reference Manual, Part 3.

4.2.3

PADD database

(PADD is an acronym for Production of Annotated and Dimensioned Drawings) This type of 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 PDMS Draft User Guide, Part 1.

4-2


The PDMS databases

4.2.4

ISOD database

The ISOD database holds pipework spool drawings generated by the Spooler module. See Pipework Spooling Using PDMS for more details of Spooler.

4.2.5

CATALOGUE database

This contains a catalogue of the standard components which you 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 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.

4.2.6

LEXICON database

The Lexicon (or Dictionary) database is a project–specific database which is used to hold the definitions of user‐defined attributes (UDAs). The UDAs are used to hold any information, not allowed for by the standard attributes, about elements which are themselves part of either a Design, Catalogue or Draft database. For further information, see the PDMS Lexicon Reference Manual.

4.2.7

PROPERTIES database

This 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 PDMS Propcon Reference Manual.

4.2.8

SYSTEM database

There is one, and 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


4-3

The PDMS databases

• •

4.2.9

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

COMMS database

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

4.2.10 MISC database The 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.

4.2.11 TRANSACTION database To 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 Chapter 9 and the PDMS Admin Reference Manual for details of Global.

4.3

PDMS project structure

A project is identified by a 3‐character name. For example, the sample project supplied with PDMS is project SAM. The structure of the project folder is shown below:

Figure 4‐1 Project SAM structure

4-4


The PDMS databases

sam000

The project directory. The files under sam000 are:

samsys

The SYSTEM database.

samcom

The COMMS database.

sammis

The MISC database.

samnnnn_sammmmm Database files which contain the actual model data. nnnn has a maximum value of 8188. samiso

The directory which stores files needed by Isodraft.

sampic

The directory which stores picture files produced by Draft.

sammac

The directory which stores inter‐database connection macros.

DFLTS

The PDMS defaults directory.

4.3.1

Other projects

Besides SAM, your PDMS install CD will include the MAS and IMP projects: •

•

4.4

MAS (Master) provides the sample project data in read‐only databases. This data should not be deleted or changed in any way, or the rest of the sample project will become unusable. IMP is an (empty) project set to use Imperial units

The relationships between databases

Although each type of database contains its own specific type of data, some of the data items in one database are derived from cross–references to data items in other databases. It is therefore sensible, and sometimes essential, to build up the various types of database in a logical order. In particular you should note the following points: •

•

•

A SYSTEM database must exist before you can access any other type of database in which you wish to work. It is created (using the MAKE macro) when a new project is set up; all other types of database are created using the ADMIN module. See the ADMIN Reference Manual for further details. DESIGN databases, particularly those containing piping or structural steelwork design data, derive information about the individual design components from the CATALOGUE databases. This information includes dimensional data, specifications for use, and connectivity data. A CATALOGUE database must therefore be built up before you try to work in a DESIGN database. PROPERTIES databases, if used, are referenced by CATALOGUE and DESIGN databases.


4-5

The PDMS databases

•

•

PADD databases normally incorporate references to parts of the design model, for graphical representation, as well as self–contained information for drawing annotation and administration. A DESIGN database, and hence a CATALOGUE database, should therefore exist before you try to work in a PADD database. LEXICON (DICTIONARY) databases hold definitions which are referenced from DESIGN, CATALOGUE or PADD databases.

Generally multi‐discipline projects are executed using discipline‐specific designers who will use specific applications in PDMS to construct the model components for their 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 are 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 collectively known as 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, or MDB. See section 4.5 for more details of Multiple Databases.

The cross‐references that exist between the various types of database (excluding the administration databases) are illustrated in Figure 4‐2.

4-6


The PDMS databases

PROPERTIES DB CATALOGUE DB DICTIONARY DB

DESIGN DB PADD DB ISOD DB

Figure 4‐2 Relationships between the database types

4.5

Multiple databases (MDBs)

When a PDMS project is set up by the Project Administrator, groups of databases are defined for particular purposes. For example, the members of any design team will need access to those databases containing the parts of the design data for which that team is responsible plus some of the Catalogue and Drawing databases. Such a group of databases is known as a Multiple Database or MDB. There would usually be several MDBs for a project, each defining specific groups of databases, for users with different tasks to perform. The way in which an MDB is set up, in terms of its constituent databases and access rights, is described in the PDMS ADMIN Reference Manual. Although an MDB may contain up to 1000 databases, only 300 of these may be accessed at any one time. These accessible databases are known as the current databases; all others within that MDB are said to be non‐current or deferred. Databases may be transferred between current and deferred status at any time. Many users can access the same MDB, but in most situations it is recommended that there is one MDB per user. This allows the database with write access to be placed at the start of the MDB. This is essential if new data is to be added to an empty database. An alternative approach is to have a single MDB for many users, and then use the Monitor module to move the required database to the front of the list.


4-7

5

How PDMS data is stored

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

Figure 5‐1 The PDMS Design database hierarchy 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.


5-1


5.1 5.1.1

The Design database element types WORLD

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

5.1.2

SITE

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

5.1.3

ZONE

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

5.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 5‐2.

5-2



Figure 5‐2 A Pump EQUI element

5.1.5

SUB-EQUIPMENT (SUBE)

A SUBE is an optional element to further sub‐divide an EQUI. The SUBE can also own primitive elements.

Figure 5‐3 A Vessel EQUI, with a SUBE


5-3


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

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

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

Figure 5‐4 A pipe rack FRMW element

5-4



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

5.1.10 STRUCTURAL COMPONENTS Structural 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.

5.1.11 PIPE Pipes 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.

Figure 5‐5 A Pipe element, showing Branches


5-5


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

5.1.13 PIPING COMPONENTS A 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. 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.

Figure 5‐6 A selection of piping components

5-6



5.2

Attributes in PDMS

Every 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:

Figure 5‐7 Cylinder and Box attributes 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

Default Value

Name

Name if specified or hierarchy description

Type

CYLI

Lock

false (the element is not locked)

Owner

the name of the owning element or its hierarchy description

Position

N 0mm E 0mm U 0mm (relative to its owner)


5-7


Attribute

Default Value

Orientation

Y is N and Z is U (relative to its owner)

Level

0 10 (this is a representation level setting)

Obstruction

2 (it is a solid hard element for clashing purposes)

Diameter

0 mm

Height

0 mm

These are all of the attributes of a cylinder, and all cylinders in the database will have precisely the same number of attributes.

5.2.1

NAME

Every 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 section 8.3). 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 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.

5.2.2

TYPE

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

5.2.3

LOCK

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

5.2.4

OWNER

The 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 EQUI’s members. 5-8



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:

Figure 5‐8 A simple ownership structure 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.

5.2.5

POSITION

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


5-9


Figure 5‐9 Point of Origin of a CYLI

5.2.6

ORIENTATION

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

5.2.7

LEVEL

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

5.2.8

OBSTRUCTION

The 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). 5-10



5.2.9

HEIGHT

The height of the cylinder.

5.2.10 DIAMETER The diameter of the cylinder.

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

(User Defined Attribute)

HEIGHT

(Normal Attribute)


5-11


5-12


6

Using PDMS

6.1

Getting into PDMS

Assuming PDMS has been correctly installed on your workstation, start PDMS by selecting (for example) Start>Programs>AVEVA>VANTAGE PDMS 11.6>Run PDMS; two command windows and a ‘splashscreen’ will appear briefly. The VANTAGE PDMS 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 PDMS Login form to make it active.

Project is the project you will be working on (for example, SAM). Type in, or select from the pull‐down list, pressing Enter in each case.

Username will have been allocated to you by your System Administrator. Type in, or select from the pull‐down list, pressing Enter in each case.

Password will have been allocated to you by your System Administrator; type in. MDB

is the multiple database within the given Project that you wish to use. Type in, or select from the pull‐down list, pressing Enter in each case. Make sure that you leave the Read Only box unchecked if you wish to modify the database as you work.

Module is the PDMS module that you wish to use. Type in, or select from the pull‐down list, pressing Enter in each case.


6-1

Using PDMS

Use Load from to specify which setup files to load at startup. You can choose either the application default settings (Load from Macro Files) or a customised setup saved during an earlier session (Load from Binary Files). The example below shows that user STRUC has entered PDMS to access MDB STRUC from the Design module, loading the initial setup from in‐built macro files.

Click on the

6.1.1

button to enter the Design module.

Working in a module

Once you have entered a module you can carry out any valid operations (normally reading, adding to or modifying the data stored in the current databases; see Chapter 8) by using the GUI (see Chapter 7) or by using the command syntax for that module as described in the relevant Reference Manual. You can usually change the databases to which the module has access from within the module. You can transfer data from PDMS to parts of your computer network which are not part of the PDMS database, such as external files or hardware devices, and you can also give non‐PDMS commands directly the computer operating system, as described in section 7.9. You can update your writeable databases at any time, so as to reflect any design changes you’ve made while working in the current module.

6.1.2

Changing to another module

Each PDMS module has a Modules submenu enabling you to switch to any other module to which you have access rights. For example, for the Design module:

6-2


Using PDMS

An option form will be displayed asking you whether you wish to save the changes you have made in the current module before entering another one.

6.2

Getting out of PDMS

You 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. All the modules have an Exit menu selection; the one shown below being for Design:


6-3

Using PDMS

If you have made changes prior to selecting Exit (and if you 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 which merely asks you to confirm that you wish to leave Design:

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

6-4


Using PDMS

6.3

Internationalisation

Microsoft produces many localised variants of Windows. VANTAGE 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 VANTAGE Plant Design Review. By default, your PDMS project can use any language whose characters are contained within the Latin-1 character set, comprising: Danish

Dutch

English

Faroese

Finnish

French

Icelandic

Irish

Spanish

German

Norwegian

Portuguese

Swedish

Italian

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

Traditional Chinese

Latin-2, comprising: Albanian

Hungarian

Polish

Serbo‐Croatian

Czech

English

German

Rumanian

Slovak

Slovene

Latin-Cyrillic, comprising: Bulgarian

Byelorussian

English

Macedonian

Serbo‐Croatian 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.


6-5

Using PDMS

•

You must select the appropriate options from the Windows Regional Options.

,

For further details, see the PDMS Installation Guide, also the PDMS Admin User Guide for details of font families.

6.4

Customisation facilities; the programmable macro language

Most PDMS modules make use of a 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 AVEVA’s programmable macro language (PML). There are two versions of PML, the older one, known as PML 1, and the newer one, known as PML 2. PML 2 has been specifically designed for writing and customising the Forms and Menus of PDMS and other AVEVA products. Almost all the facilities available in PML 1 and the older Forms and Menus facilities are present in PML2. 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. PML 2 has not completely replaced PML 1, and there are some tasks which are carried out more efficiently using PML 1 facilities. In particular, the PML 1 expressions package, which is used within PDMS for writing rules and defining report templates. 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 AVEVA’s 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. For full details of PML, refer to the VANTAGE Plant Design Software Customisation Guide and the Plant Design Software Customisation Reference Manual. If you need a full description of PML 1, for example if you are maintaining old code, you will need to refer to previous versions of the Plant Design Software Customisation Guide. The last one to describe PML 1 fully was dated October 1995.

6-6


7

Basic GUI features

PDMS uses a GUI using forms (dialog boxes) and menus with which Microsoft Windows users should not be unfamiliar. This chapter describes those GUI features which are specific to PDMS.

7.1

Using the mouse

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

7.2

Using forms

Forms can include any of the following: • • • • • •

text boxes drop‐down lists option buttons check boxes scrollable lists action buttons.

Text boxes and drop‐down lists are explained below; the remainder are explained later in this chapter.


7-1

Basic GUI features

7.2.1

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

•

7.2.2

Using drop-down lists

Drop‐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.

7.3

Using menus

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

7-2

Options followed by a pointer, display a subsidiary menu that offers a further range of options.


Basic GUI features

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 men. 2. Select At from the resulting pull‐down menu 3. Move the pointer to the right and select Explicit from the resultant submenu.

7.4

Using the 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. The actions of the buttons are explained in the online help. 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, you click on it. Note: Toolbars can be switched on or off by right‐clicking on a tool bar 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.

7.5

Using the 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 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.


7-3

Basic GUI features

7.6

More on using forms

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

7.6.1

Using option buttons

Option buttons (sometimes referred to as radio buttons) are used to select one, and only one, 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.

7.6.2

Using check boxes

Check 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

7.6.3

Using scrollable lists

7-4


Basic GUI features

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

7.6.4

Using action buttons

Most 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 PDMS to accept the current form settings, and closes the form. Cancels any changes you have made to the form, and closes the form.

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

7.7

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


7-5

Basic GUI features

7.8

Dockable Windows, Menu Bars and Tool Bars

PDMS uses a number of Microsoft “.NET forms” where windows are “dockable” and “undockable”, and where other window manipulation facilities are available. For full details of these facilities see the PDMS online help (for the “graphical” modules), Dockable Windows, Menu Bars and Tool Bars help topic.

7.9

Using commands

PDMS commands can be typed in when using PDMS via the Display>Command Line… menu selection, which gives the Command Window:

To give a command, click in the Command> text entry box, type in the command, and press Enter. The scrollable list shows the command(s) entered and any resulting output from PDMS (including error messages). Command editing aids are available: • • •

7.9.1

Clicking on a line in the scrollable list area copies that line to the Command > box. Command syntax in the Command> box can be edited using the Delete and Backspace keys in the normal way. Highlighting some or all of the text in the Command> box and pressing the right mouse button gives useful Windows editing commands (Cut, Copy, Paste, Delete, Undo).

Why 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: •

7-6

Create macros to automate repetitive procedures (see the Plant Design Software Customisation Guide and Reference Manual) VANTAGE PDMS Version 11.6 Getting Started with PDMS

Basic GUI features

•

Design and create new forms and menus for your graphical user interface that match your working needs precisely (see the Plant Design Software Customisation Guide and Reference Manual)

In some cases it can be slightly quicker to use commands rather than the GUI for simple operations. For example:

Q MEM

‐ list the members of the current element

Q ATT

‐ list the attributes of the current element

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


7-7

Basic GUI features

7-8


8

Basic operations in PDMS

Work 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 database’s contents This chapter tells you how to do these things

8.1

Querying

You will often find, when working in PDMS, that you need to check existing information about some aspect of the program’s 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 workfile 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:


8-1


The querying operations available from the GUI are fully explained by the online help for the module in question. 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. See the PDMS Design Reference Manual Part 1 for details.

8.2

Current element and current list position

Chapter 5 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 (see Figure 8‐1). 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. Pointer to Current List Position

Current Element

Members of Current Element 1

2

3

4

List Position in Member List

Figure 8‐1 Current Element, Member List and Current List Position 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. To check 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. The members of the current element will be show. For example:

8-2



Alternatively, give the commands: Q CE

‐ to display the current element

Q MEM

‐ to display the members list of the current element


8-3


8.3

Navigating to a given element

You would normally navigate to an element by means of the Explorer or the Members list.

8.3.1

The 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 Draw List (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.

8-4



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.

8.3.2

The 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 NOZZ’s Catref attribute.

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. Full details of these forms and how to use them are given in the online help.


8-5


8.3.3

Other Explorers

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

8.3.4 My Data

My Data provides a ‘scratchpad’ facility, enabling you to assemble collections of data and transfer them from one module to another.

8-6



8.4

Modifying the content of a database

You 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 application that is loaded. For example, for the Design module, General application:

Full details of these menus and how to use them are given in the online help.


8-7

9

Interfaces to other systems

PDMS is a member of AVEVA’s VANTAGE Plant Design family of products, the others being VANTAGE Plant Engineering (VPE), VANTAGE Project Resource Management (VPRM), and VANTAGE Enterprise Net (VNET). This chapter introduces these products and gives an overview of the ways in which PDMS interfaces with them.

9.1

VANTAGE Plant Enginerring (VPE)

The VPE products store and manage the engineering data for a plant design project. There are two VPE Products: • •

9.1.1

VPE Workbench VPE P&ID

VPE Workbench

VPE Workbench is a project data store based around an Oracle database. The database is capable of storing all the engineering data required to design, build and commission a process plant. VPE Workbench interfaces with a wide range of applications including PDMS, VPE P&ID and VPRM. Together with these applications, VPE Workbench can be used from the start of plant conceptual design all the way through to plant operation. VANTAGE PDMS Version 11.6 Getting Started with PDMS

9-1


One of the greatest strengths of VPE Workbench is its data management capabilities. These include access control, security, issue control, validation, change monitoring and the audit trail. VPE Workbench can be used to produce a range of deliverables including datasheets (specifications) and schedules. If VPE Utilities and Business Objects are used with VPE Workbench, this range of deliverables can be extended to include diagrams and all manner of ad hoc reports. VPE Workbench maintains a log of deliverables that it produces but does not control these outside of itself. Clients are able to receive deliverables in electronic format and there are various tools available such as Data Mapper that can take client data and import it into VPE Workbench. Using VPE Workbench: •

• • • • •

• • • • • •

Provides controlled, multi‐user access to managed engineering data resulting in improved data accuracy and less time spent waiting for data or looking for the latest release; Results in less rework, because up‐to‐date data is always available; Leads to improved data accuracy and validation with in built expertise; Enables comprehensive audit trails to be maintained which record the time that changes were made and by whom; Provides electronic deliverables and flexible reporting output; Enables a common system to be established in every office, permitting multi‐office project execution with global working across a wide area network, and enabling efficient transfer of engineers between offices with minimal re‐training; Enables rapid start up of new projects, as data held in a database for an existing project can be copied to a new project; Automatically highlights data changes; Provides advanced query facilities; Facilitates implementation of STEP standards for data exchange; Presents the user with an interface common with other Windows software already in use and hence reduces learning times. Quick and easy reporting of UDA data from PDMS.

VPE Workbench is made up of modules, five of which are based on engineering disciplines. They are Process, Instrumentation, Mechanical, Electrical and Piping. The user interface for each of these modules is tailored to suit the user’s role and normal work activities. The structure of the underlying data store remains completely hidden. There is one further module, the Administration module, which is used to set up data for all the modules.

9.1.2

Introducing the VPE Workbench user interface

The VPE Workbench entry screen is as shown below:

9-2



You access data via forms. Regardless of the number of users concurrently accessing the system, VPE Workbench ensures that data duplication is eliminated, and that the full data history is preserved. VPE Workbench automatically tracks and highlights all data changes and provides an effective mechanism for configuring the controlled approval and release of data, and associated change notification. A typical VPE/Oracle form is:


9-3


9.1.3

VPE P&ID

VPE P&ID is a 2D‐drafting system, optimised for producing Process and Instrumentation diagrams (P&IDs). VPE P&ID is an application that can be combined with either AutoCAD or Microstation, to draw intelligent P&IDs quickly and accurately. The intelligence of each P&ID consists of the data, provided by the user that is associated with the drawing symbols (AutoCAD blocks or Microstation cells). This data, together with the graphical information of the drawing, can be transferred to VPE Workbench. Data from VPE Workbench can also be imported into VPE P&ID. VPE P&ID can also be used to build ʹschematic onlyʹ or ʹfirst passʹ flow diagrams quickly without the necessity to enter project data, which may not be available at the time. VPE P&ID uses the data on P&IDs to generate lists of process information that can then be used to automatically create documents via an interface with a data management system. Typical documents are drawing lists, equipment lists, piping line lists, instrument indexes, valve lists and lists of special piping items. Specific data interfaces exist between VPE P&ID and VPE Workbench. The P&ID Loader is one such interface, which enables a set of files, containing various categories of engineering data, to be loaded and reloaded whenever necessary. Also, the two‐way transfer of information between VPE P&ID and VPE Workbench enables loop numbers, I/O information, and selected equipment design information to be automatically included in a P&ID.

9-4



Information is validated online as it is entered into VPE P&ID by a conformance check against validation lists. The data may then be exported to separate files outside of AutoCAD or Microstation. These files can then be imported by a database and manipulated, as required. The VPE P&ID user interface comprises customised menus, toolbars and, in the case of Microstation, a command window, which integrates with the AutoCAD or Microstation display and software. The interface also incorporates dialogue or list boxes, pulldown menus and, optionally, tablet (digitiser) menus.

9.2

VANTAGE Plant Resource Management (VPRM)

The VPRM Workbench product provides Project Control and Resource Management facilities covering the key Project Variables of: • • • •

Materials Documents Progress Costs


9-5


VPRM enables Project Management to identify and access information relating to the above variables, enabling timely decisions to be made.

9.2.1

VPRM Interfaces

VPRM interfaces with general office systems, such as MS Excel and Word, and with other strategic systems, for example:

9-6

•

VANTAGE Plant Engineering (VPE). VPRM imports engineering design data from VPE, and to ensure the compatibility of this transfer, VPE imports reference data from VPRM.

•

PDMS and PDS 3D Modelling Systems These systems can import VPRM Specification Data for use in the production of isometric drawings. MTO details are derived from these drawings and imported into VPRM.

•

GPI (Global Procurement Information) System VPRM provides GPI with details of globally strategic vendors, materials, bids received and purchase orders placed, to enable GPI to be a source of information on world‐wide best prices and availability of equipment and materials. GPI provides VPRM with a standard for categorising materials, known as GMC (Global Material Category).

•

EDM (Enterprise Document Management) System EDM and VPRM operate in conjunction to manage documentation. EDM covers the document storage and distribution, and VPRM covers the organisation of document numbering, registering, progressing etc. EDMʹs search and retrieval facilities are available from within VPRM.

•

KMS Management System Interfaces between KMS and VPRM enable users of KMS to utilise VPRM for material management activities, while continuing to use the functionality of KMS for other purposes.

•

PRIMAVERA Planning System PRIMAVERA provides VPRM with activity and milestone details and planned dates. VPRM provides PRIMAVERA with forecast and actual completion dates.

•

Financial Systems (e.g. PENTA) VPRM provides a financial system such as PENTA with budget, cost and commitment values and information on vendors and the materials received from them. The financial system provides VPRM with information on expenditure and actual hours worked.

•

ICARUS Estimating System ICARUS provides VPRM with original budget data for a project. VPRM provides ICARUS with historical data on which to base estimates. VANTAGE PDMS Version 11.6 Getting Started with PDMS


Extensive interfaces between these systems ensure that data, once created, is continuously available for ongoing related processes.

9.2.2

VPRM Facilities

Once installed in an office, VPRM can be used to control many projects. To support operation of the projects, VPRM provides ʹCorporateʹ facilities, consisting of a material catalogue, a vendor database and an estimating database. The support of projects by corporate facilities ensures consistent referencing and identification of materials and vendors, within and between projects. The facilities provided by VPRM are summarised below: •

Data Security To safeguard the held data, VPRM incorporates an access control facility. This involves allocation of passwords to the various VPRM ʹSystem Usersʹ and, depending on the functional role of the particular user, the allocation of access rights to screens and reports presented by VPRM.

•

Project Management VPRM presents a high‐level view of the status and overall health of each project. The presented information covers costs, progress, materials and documents. Critical data is highlighted.

•

Cost Management VPRM presents budget, expenditure and commitment values and other data for the management of project costs. The information is presented as ʹto‐dateʹ and for specified periods. To highlight potential management problems, variances between forecast and budget values, and between expenditure to date and commitment values, are displayed.

•

Progress Measurement VPRM presents information on the budgets, progress, productivity and scheduling of work carried in the “home office” for each project. Progress of individual design documents is included. Overall project man‐hour requirements for the duration of the project are computed.

•

Document Control VPRM provides facilities for controlling documents produced for the design and construction of the project (Design Documents) and documents that support the purchased items and materials (Vendor Documents). VPRM interrelates with EDM for handling of the actual documents.

•

Engineering and Materials Management For the control of all major equipment, tagged items and bulk materials (summarised here as materials) throughout the life of the project, VPRM provides facilities for:


9-7


• • • • • • • •

Specifying which materials are permitted for use, Systematically analysing the project design information with regard to the materials required for construction (Material Take Off), Requisitioning the materials in a logical and controlled manner, Sending enquiries to potential vendors, analysing the resultant bids, and then placing purchase orders, Expediting and organising inspection of materials prior to despatch from vendors, Organising the transit of consignments from vendors to site, Recording receipt of materials at site, and maintaining records of them when in stores, Planning and scheduling construction work, taking into account the availability of the required materials and, where appropriate, assigning them to subcontractors.

•

Material Catalogue The VPRM material catalogue facilitates the logical identification of materials and purchasable items and is the source of all standard VPRM descriptions and references for them. In addition to the standard versions, the material catalogue can provide descriptions in other languages, and reference numbers specified by a particular client or defined by the user.

•

Vendor Database The VPRM vendor database is a single source of information on vendors and sub‐ contractors. Vendors are identified as supplying materials of particular categories, and data is available regarding past bid and purchase order performance, and quality assurance and quality control performance.

•

Estimating Database The VPRM estimating database contains bulk material price information for use in the production of estimates for future VPRM projects. In future, the database will also provide facilities to produce the estimates themselves and will also contain standard costs for construction activities.

9.2.3

VPRM Architecture

VPRM uses an Oracle 3‐tier architecture, consisting of: • • •

9-8

An Oracle Database server, which contains the data and some of the application logic. An Oracle Internet Application server (iAS). This communicates with the Database server and contains the bulk of the application logic as well as the iAS aspects. A Client tier that provides the user interface, via PCs, with the server‐side tiers. It communicates with the iAS by direct socket connection. The PCs run Web browsers.



9.2.4

Introducing the VPRM user interface

VPRM uses a standard MS Windows “forms and menus” user interface. All VPRM sessions are displayed in a standard browser window. The main menu bar, with a typical selection, is shown below. Note the toolbar.

The data entry screens within VPRM are produced using a number of database items. These items form a structure in which data can be queried, inserted, modified or deleted. A typical screen (Identity Code Details) is shown below:


9-9


9.3

VPE and VPRM Interfaces - Summary

The interfaces between AVEVA’s VANTAGE Plant Engineering and VANTAGE Plant Resource Management packages can be summarised by the diagram below:

Bulk Material Control and Procurement MTO data

PDMS

Engineering Data

Spec data

VPRM

Tray Access and E&I position data

VPE

The PDMS → VPRM interface takes place from the PDMS Isodraft module. See the user documentation for Isodraft, and the online guides for the VPE and VPRM products for more details. The VANTAGE Plant Design Model Management product constitutes a much more extensive set of interfaces between the above (and other) products. See below.

9.4

VANTAGE Plant Design Model Management

Model Management (which requires PDMS and VPE to be present) integrates PDMS and VPE into the Model Management product. The Model Management System provides facilities for controlling data related to engineering objects designed in 3D using PDMS. The facilities encompass creating and maintaining the PDMS data from 2D engineering data for lines, equipment and instruments, as input using VPE Workbench. This structure ensures

9-10



that there is consistency between the specified engineering data, the 2D P&IDs, and the 3D design model. Model Management also includes the Model Object Manager, Connectivity Manager and Clash Manager products. Bespoke products can also be provided as part of the Model Management System, namely VPD Deliverable Manager, Area‐Based Automatic Drawing Production and Multi‐Discipline Supports. The Data Storage area of VPE is the central repository for 2D objects and associated data. The 2D objects can be created by importing data from a P&ID, by direct entry into VPE, or by mapping the data from a spreadsheet. VPE data storage also holds the 3D data for 3D objects that correspond to every controlled design object in PDMS. This enables a comparison of the data to be made between the engineering data and design data within VPE itself, and associated reports to be produced. The PDMS Design database is the central storage point for 3D design objects and associated attribute data. The 3D design objects are created and managed during a PDMS session. The status of each controlled object is managed through VPD Model Management.

9.4.1

The Model Management System core facilities

Model Object Manager manages the build and attribute comparison of 3D objects against the 2D data content in VPE Workbench. Model Object Manager provides facilities for controlling data for all engineering objects designed in 3D using PDMS, maintaining records of 3D objects that mirror those in PDMS, mainly for reporting purposes and drawing control facilities. Facilities are available for viewing the lists of engineering data, and certain attributes that affect the 3D design, and for creating design data based on engineering data, comparing design data with engineering data, and modifying design data to bring it into line with engineering data. Clash Manager manages the resolution of clashes in the 3D model. Clash Manager can be used to process the 3D data and generate clash data when two or more items that are not connected occupy the same 3D space. The system provides reports on clashes and enables a status, history and responsible discipline to be allocated to each one. This enables the PDMS user to prioritise, control and monitor the work involved in the resolution of all clashes. Connectivity Manager manages the connectivity comparison of pipelines in the 3D model with the counterpart 2D P&ID lines, and also provides facilities for building 3D pipelines and components from 2D data. Connectivity Manager ensures that the pipes, components and equipment of the designed process plant are represented consistently by the P&IDs and the 3D model in PDMS. The Connectivity Manager GUI displays information on the occurrences of connectivity mismatches, and can graphically display the physical positions of them.


9-11


9.4.2

Introducing the Model Management System GUI

The Model Management System uses a ‘forms and menus’ GUI like other VPD Products. An example Connectivity Manager screen is shown below.

9.5

VANTAGE Enterprise NET (VNET)

VANTAGE Enterprise NET (VNET) is an application‐independent, web‐enabled platform for collaboration and mark‐up of engineering information. Through VNET, 3D models, schematics, documents and data from any application can be browsed in context and with full intelligence, giving the most comprehensive profile of plant data. For its users, it is the ʹwindow on the worldʹ for projects or plants, irrespective of tasks or discipline.

9-12



9.6

VANTAGE Plant Design Global

Global is an optional PDMS facility which is used to synchronise the databases between different sites (which may be at different locations and in different time zones) working on the same project. You can split a project so that its data is distributed across a number of locations by making the project into a Global project. The PDMS users in the different locations access the same PDMS project. The project’s distributed nature is largely invisible to the users. Each location has its own local copy of the PDMS product, and local copies of PDMS databases. To ensure the integrity of data, the project databases are automatically checked and incremental updates are issued across all project sites. Global is a System Management product rather than a “user” product. In a PDMS installation that incorporates the Global product, Global takes the form of extra forms and menus in the Admin module.

9.6.1

The Transaction database

In standard PDMS, commands are processed one at a time so that the next command cannot begin until the previous one has finished. In principle, the state of the system is therefore always known. In Global, remote commands are processed in parallel and so the next command may be initiated before the previous one has finished. The advantage of this mode of operation in Global is to prevent a slow long‐transaction command from blocking the user. Its disadvantage is that the user needs to work in a new way to exploit this parallel nature of Global. If a remote command traversing the Global network becomes held up at a particular location (for example due to a comms line fault) then, for most commands, the command is placed in a transaction database at that location for later processing. A small number of commands, known as ‘kernel’ commands, bypass the transaction database and are stored in a pending file for later processing. The use of the transaction database and the pending file means that commands are guaranteed to complete, but some commands may not succeed. Some may roll back, while others may just fail.

9.7

VANTAGE Plant Design Review

Plant design model files created using PDMS Design can be exported to VANTAGE Plant Design Review for visualisation. It is important to realise that Review is a visualisation product, you cannot design things in Review. The visualisation facilities in Review include:


9-13


•

• • • •

View control. The position that the observer is looking from, the point through which the observer is looking, the orientation of the model with respect to the viewer, and the viewing angle can all be controlled. Material definition. Selected model elements can be given ‘material’ display properties such as shininess, smoothness and texture. Lighting facilities allow the positions, colours and intensities of light sources to be controlled. Animations can be defined by setting up a progressive sequence of views, giving a ‘walkthrough’ effect. Sea and Sky backgrounds can be included, giving even greater realism.

A typical Review picture is shown below (courtesy of Paragon Engineering Services Inc.).

9.8

The Data Exchange Interfaces

A variety of VANTAGE Plant Design interface products exist as separate ‘add‐on’ packages to PDMS:

9-14



Product Name

Function

OpenSteel

Provides a bi‐directional interface between PDMS and leading steel detailing packages such as StruCAD, SteelCad and X‐Steel using the SDNF file format.

ImPLANT‐I

Enables design data in the Intergraph Standard File Format (ISFF) or MicroStation DGN and DRV formats to be imported into PDMS and Review products.

ImPLANT‐STL

Imports STL‐format data from third party mechanical CAD packages into PDMS Design.

ExPLANT‐I

Enables geometry data from PDMS to be exported into the 3D geometry DGN format.

RetroView

Enables the PDMS model to be adjusted to as‐built status by comparison with photogrammetric data from Offset’s Magan product.

STRESS‐C

Exports piping information to Coade’s Caesar II pipe‐stress program

STRESS‐T

Exports piping information to AAA Technology’s Triflex pipe‐ stress program

PDMS to CABSYS

Exports PDMS model data to the CABSYS Cable routing package

PDMS to STAAD III

Exports PDMS model data to the STAAD III stress analysis package

For more details of these products, see the AVEVA website www.aveva.com/engineeringit/world/


9-15

Appendix A Glossary of terms and abbreviations A.1

Introduction

This glossary comprises: • •

Technical terms relevant to PDMS, with brief explanations of their meanings. Abbreviations and acronyms used throughout the PDMS documentation, with expansions to their full derivations. It does not list general process engineering terms, with which you are assumed to be familiar.

A.2

Definitions

Add‐in ‐ An add‐in provides a means of adding functionality. An add‐in application appears on the applications menu, which provides a method of switching to it. Algebraic Notation ‐ The form of syntax used in current versions of PDMS for entering values and operators into numerical calculations. Algebraic syntax conforms closely to the way in which the expression to be calculated would be written as an ordinary mathematical function. Application Macro ‐ A predefined macro which allows you to enter sequences of commands which simplify specific types of design work. Applicationware (‘Appware’) – A suite of forms and macros designed for use with a specific design task, for example pipework design. Attribute ‐ A specific item of data which defines one of the properties of an element in a database. An element is fully specified by combining all its attributes. Batch Mode ‐ A method of running a computer program without user intervention; for example, overnight. The command inputs are stored in a file and then read sequentially into the computer. The opposite is Interactive Mode. Command ‐ An instruction to the computer program to carry out a specific action. A command may comprise a single instruction, or a list of instructions combined into a single input line. A command word often requires a qualifying argument. Crosshairs ‐ A crosshair cursor. A horizontal and a vertical line on a display screen whose intersection represents the cursor position. Current Element ‐ The element in a database at which you are notionally situated at a given stage of database navigation.


A-1

Glossary of terms and abbreviations

Database ‐ A related set of data stored in a logically‐accessible format in a computer system. Any single item of data can be retrieved by defining a unique route to its location. Default ‐ An option selected automatically if you do not specify any particular choice from an available range of commands or attribute settings. Device Driver ‐ An interface which translates the output from a computer into a form which can be input to another device (e.g. a printer, plotter or terminal). Docking/Dockable ‐ This describes forms and menu bars that can be attached in appropriate places to the frame of the main PDMS window. Drag‐and‐drop ‐ Select with mouse and then drag (holding the mouse button down) to a different place. Element ‐ A discrete item of data held in a database; identified by number and/or name and defined by its attributes. Expression ‐ A mathematical or logical definition, the calculated result of which is to be used as a command argument. File ‐ An identifiable part of the computerʹs memory used to store data. Data may be added to and removed from a file, or may be manipulated as a whole by operations on the complete file. Filename ‐ The name of a file in the computerʹs operating system. When referenced from within PDMS the filename must be preceded by a / symbol; this symbol is not part of the filename as defined by the computerʹs operating system. Folder (also referred to as a Directory) ‐ An administrative grouping of files in the computerʹs memory to make logical access to any individual file easier. Form (also referred to as a Dialog Box) ‐ That part of a graphical user interface screen into which you may enter the settings of parameters or command arguments, usually with prompting text which shows you what to enter at each location. Graphics File ‐ see Plotfile. GROUP ‐ A collective element which can be used to form temporary links between otherwise unrelated elements in a database. Head ‐ The input end of a BRANCH (under normal flow conditions). Hit Radius ‐ The maximum acceptable error in identifying a point on a screen using a graphics pointer. If the distance from the pointer position to the intended location is larger than the hit radius, the location will not be identified. Interactive Mode ‐ The method of operation whereby you perform an operation using the mouse and/or keyboard and wait for PDMS to interpret and act upon it before you perform the next operation. The opposite is Batch Mode.

A-2



Level (drawing) ‐ An attribute of an element in a Design database which defines whether or not the corresponding item is to be shown when a drawing is plotted. The levels to be drawn are specified as part of the plotting command. Level (hierarchic) ‐ The vertical position at which a given type of element is situated in a database structure; analogous to a generation in a family tree. Macro ‐ A sequence of commands stored as a text file. When the macro is called from within PDMS, the command processor reads each line of the file in turn and behaves as if the commands were being directly entered. Member (of an Element List) ‐ A lower‐level element linked immediately below another element (its owner) in a database hierarchy. A Group Member is an exception in that it is linked only indirectly to the GROUP, which is a parent but not its owner. Member (of a Team) ‐ A named PDMS user who is linked with other users (as a team) who share common access rights to one or more databases. Menu ‐ A predefined list of options displayed as part of the Graphical User Interface. Module ‐ A subdivision of the overall PDMS program which is used to carry out a particular type of operation on the databases. Each module has its own name within the program suite. Mouse ‐ A device for positioning the pointer on a workstation screen. Multiple Database (MDB) ‐ A group of databases linked together administratively for a specific purpose. You can only access a database if you have access rights to an MDB which contains it. My Data – a storage area for remembering PDMS data for future use. Typically used to copy collections of elements from one module to another. Name ‐ A name in PDMS is an element identifier which you allocate to it. It is an alphanumeric string prefixed by a / symbol. This identifier is always additional to the elementʹs reference number, which is allocated automatically by PDMS. Offspring ‐ A lower‐level element linked anywhere below another element (one of its parents) in a database hierarchy. A member is a special case of an offspring. Owner ‐ One higher‐level element linked directly above another element (one of its members) in a database hierarchy. Parameter ‐ A ‐variable item of information (value, text etc.) which must be defined before a command can be executed unambiguously. Parent ‐ A higher‐level element linked anywhere above another element (one of its offspring) in a database hierarchy. An owner is a special case of a parent. PIPE ‐ An element, comprising an assembly of BRANCHes, which defines part of a complex piping system. The term has a specific meaning in PDMS which may not correspond with its usual engineering meaning.


A-3


Plotfile ‐ A file which contains encoded graphics data. The fileʹs contents can be unspooled to a plotter or graphics screen when the corresponding drawing is to be generated. Pointer (1) ‐ An indicator (also referred to as the cursor) on a display screen which identifies one of two types of location: • •

An alpha pointer (e.g. a flashing block or bar) shows where the next input character will appear. A graphics pointer (e.g. an arrowhead) identifies a location or an element in the depicted part of the design model.

Pointer (2) ‐ A link between elements or attributes, indicating the path by which information is transferred logically between the various parts of the databases. P‐point (Principal Point) ‐ An imaginary location and direction used to manipulate and interconnect elements which represent physical entities in the design model. A P‐line is a p‐ point extruded in a specific direction. Primitive ‐ A fundamental design shape (box, cylinder etc.) used to build up the design of a physical entity in the design model or component catalogue. Read‐only ‐ An access category that allows you to look at the contents of a database or file but not to modify them. Read/Write ‐ An access category that allows you to look at the contents of a database or file and to modify them. Enter (key) ‐ The carriage return key on the keyboard. Used to end each typed command line and send its contents to the command processor. Also referred to as the Return key. Selection – A selection of objects defined using the 3D graphical view. Shortcut Menu – a context‐sensitive menu activated by the secondary (usually right‐hand) mouse button. Syntax (Of Commands) ‐ the rules which define precisely how a command line must be entered so that PDMS can interpret your instructions unambiguously. Syntax is usually specified by using diagrams to show the valid command sequences. Tail ‐ The output end of a BRANCH (under normal flow conditions). Team ‐ An administrative grouping of PDMS users who share common access rights to one or more databases. Textual Expression – An expression which manipulates text simply as strings of alphanumeric characters without regard to their overall meaning. Title bar – The top of a window, containing its title. Toolbar – A collection of GUI icons, used to trigger the GUI actions.

A-4



Unspooler – A translation program which allows graphical output files (plotfiles) produced by a computer program to be input to an offline plotter. Each combination of output format and plotter type requires a specific unspooler. User‐Defined Attribute – A database attribute whose name and type of content are defined by the user rather than by the default PDMS structure. Window – A part of a display which is allocated a specific area of the screen. The position and (unless the window is non‐resizable) of the window may be redefined interactively. WORLD – The highest level element in any database; always allocated the symbol /* as its PDMS name.

A.3

Abbreviations and Acronyms

Abbreviations which are thought to be self‐explanatory, particularly those which are simply the first few letters of an obvious word, are not listed. ADE

ASCII Decimal Equivalent

ASCII

American Standard Code for Information Interchange

CATREF

Catalogue Reference

CE

Current Element

CL

Centreline

COCO

Connection Compatibility

CPU

Central Processor Unit

CREF

Connection Reference

CTORU

Circular (cross‐section) Torus

DABACON

Database Constructor

DB

Database

DDL

Data Definition Language

DXF

Drawing Exchange Format (as used by AutoCAD®)

GTYP

Generic Type

GUI

Graphical User Interface

HPGL

Hewlett Packard Graphics Language

I/O

Input/Output

IGES

International Graphics Exchange Specification

LJSE

Lap Joint Stub End


A-5


MDB

Multiple Database

OS

Operating System

Pn

P‐point n (where n is an integer)

PA

P‐Arrive or Arrive P‐point

PDMS

Plant Design Management System

PH

Pipe Head

P&ID

Piping and Instrumentation Diagram

PID

Piping and Instrumentation Diagram

PL

P‐Leave or Leave P‐point

PML

Programmable Macro Language

POHED

Polyhedron

PT

Pipe Tail

PTRANS

Percent (%) Variable Translator

PVOL

Preferred Volume or Penalty Volume

Q

Query

Refno

Reference Number (of an element in a database)

RTORU

Rectangular (cross‐section) Torus

SHU

Standard Hookup

SKEY

Symbol Key

SPCOM

Specification Component

SPREF

Specification Reference

STYP

Symbol Type

UDA

User‐Defined Attribute

VDM

View Definition Matrix

WN

Weld Neck

2D or 3D

Two‐ or Three‐dimensional

@

Crosshair cursor location

A-6


116 Gettingstarted

Recommend Documents