AVEVA Plant

(12.1)

TRAINING GUIDE
PDMS Hands-On
Overview

TM-1000

www.aveva.com
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 2
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Revision Log
Date Revision Description of Revision Author Reviewed Approved
03/01/2012 0.1 Issued for Review PDMS 12.1.SP2 GE
02/03/2012 0.2 Reviewed GE SB / KB
09/03/2012 1.0 Approved for Training PDMS 12.1.SP2 GE SB / KB NG

Updates
All headings containing updated or new material will be highlighted.

Note: Highlighting will not be employed at Revision 1.0 due to significant alterations to training material
warranted by release of PDMS 12.1.

Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers, please report it to AVEVA
Training & Product Support (TPS) at [email protected]

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

Visit our website at http://www.aveva.com

Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free
from viruses.

1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar
losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of
data or information; any special, indirect, consequential or pure economic loss, costs, damages,
charges or expenses which may be suffered by the user, including any loss suffered by the user
resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of
whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence)
or otherwise.

1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with
the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year
in which the user's claim is brought.

1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.

1.5 In the event of any conflict between the above clauses and the analogous clauses in the software
licence under which the AVEVA software was purchased, the clauses in the software licence shall
take precedence.

www.aveva.com
© Copyright 1974 to Current Year 3
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part
of it (including source code, object code, any data contained in it, the manual and any other documentation
supplied with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.

All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this
document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or
transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is
granted, it expressly requires that this copyright notice, and the above disclaimer, is prominently displayed at
the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in
this publication may be incorporated into any third-party software, product, machine, or system without the
prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised
action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.

The AVEVA software described in this guide is to be installed and operated strictly in accordance with the
terms and conditions of the respective software licences, and in accordance with the relevant User
Documentation.

Unauthorised or unlicensed use of the software is strictly prohibited.

Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA
shall not be liable for any breach or infringement of a third party's intellectual property rights where such
breach results from a user's modification of the AVEVA software or associated documentation.

AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

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

AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trademark rights, or other intellectual property rights in any other product or software, its
name or logo belongs to its respective owner.

www.aveva.com
© Copyright 1974 to Current Year 4
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Contents

1 Introduction .............................................................................................................................................. 7
1.1 Aim..................................................................................................................................................... 7
1.2 Objectives ......................................................................................................................................... 7
1.3 Prerequisites .................................................................................................................................... 7
1.4 Course Structure .............................................................................................................................. 7
1.5 Using this guide ............................................................................................................................... 7
2 PDMS Fundamentals ............................................................................................................................... 9
2.2 Installation ...................................................................................................................................... 10
2.3 Logging into PDMS ........................................................................................................................ 11
2.4 How PDMS is structured ............................................................................................................... 12
2.4.1 Admin ....................................................................................................................................... 12
2.4.2 Paragon .................................................................................................................................... 12
2.4.3 Propcon .................................................................................................................................... 13
2.4.4 Lexicon ..................................................................................................................................... 13
2.4.5 Design ...................................................................................................................................... 13
2.4.6 Isodraft ..................................................................................................................................... 14
2.4.7 Draft .......................................................................................................................................... 15
2.4.8 Review ...................................................................................................................................... 15
3 PDMS Administration ............................................................................................................................ 17
3.1 Introduction to Administration ..................................................................................................... 17
3.1.1 Projects .................................................................................................................................... 17
3.1.2 Teams ...................................................................................................................................... 17
3.1.3 Users ........................................................................................................................................ 17
3.1.4 PDMS Databases ..................................................................................................................... 18
3.1.5 Including and Copying Foreign Databases .............................................................................. 20
3.1.6 Multiple Databases (MDBs) ..................................................................................................... 20
3.1.7 References between Databases .............................................................................................. 20
3.2 Creating a New Project – A Worked Example ............................................................................. 21
3.3 Using PDMS Admin – A Worked Example ................................................................................... 21
3.3.1 Creating a New Team .............................................................................................................. 22
3.3.2 Creating a New User ................................................................................................................ 23
3.3.3 Creating a New Database ........................................................................................................ 23
3.3.4 Adding Foreign Databases ....................................................................................................... 24
3.3.5 Creating an MDB ...................................................................................................................... 25
Exercise 1 PDMS Administration ............................................................................................................ 27
4 PDMS Paragon ....................................................................................................................................... 29
4.1 Introduction to Paragon ................................................................................................................ 29
4.1.1 Creating the Paragon Hierarchy............................................................................................... 30
4.1.2 Creating the Component Category Element ............................................................................ 32
4.1.3 Creating a Component Copy .................................................................................................... 33
4.1.4 Adding the Parameter Values .................................................................................................. 34
4.1.5 Constructing the Pointset ......................................................................................................... 34
4.1.6 Constructing the Geometry Set ................................................................................................ 37
Exercise 2 PDMS Paragon – Component Creation ................................................................................ 40
5 PDMS Design .......................................................................................................................................... 41
5.1 Introduction to Design ................................................................................................................... 41
5.1.1 World (WORL) .......................................................................................................................... 42
5.1.2 Site (SITE) ................................................................................................................................ 42
5.1.3 Zone (ZONE) ............................................................................................................................ 42
5.1.4 Equipment (EQUI) .................................................................................................................... 42
5.1.5 Sub-Equipment (SUBE) ........................................................................................................... 42
5.1.6 Primitives .................................................................................................................................. 43
5.1.7 Structure (STRU)...................................................................................................................... 43
5.1.8 Framework (FRMW) ................................................................................................................. 43
5.1.9 Sub-Framework (SBFR) ........................................................................................................... 43
5.1.10 Structural Components ............................................................................................................ 43
5.1.11 Pipe (PIPE) ...............................................................................................................................
www.aveva.com 43
5.1.12 Branch (BRAN)......................................................................................................................... 43
© Copyright 1974 to current year. 5
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.1.13 Piping Components .................................................................................................................. 43

5.2 The Design Window ....................................................................................................................... 43
5.3 Using the Mouse ............................................................................................................................ 44
5.4 Key Tools within Design ............................................................................................................... 45
5.4.1 The Model Editor ...................................................................................................................... 45
5.4.2 Application Specific Toolbars ................................................................................................... 46
5.5 Equipment Creation – A Worked Example .................................................................................. 47
5.5.1 Creating Equipment from Primitives......................................................................................... 47
5.5.2 Creating Equipment from a Template ...................................................................................... 50
5.6 Structure Creation – A Worked Example ..................................................................................... 52
5.6.1 Setup ........................................................................................................................................ 52
5.6.2 Creating the Columns .............................................................................................................. 53
5.6.3 Creating the Beams ................................................................................................................. 54
5.6.4 Creating a Panel....................................................................................................................... 55
5.7 Piping Creation – A Worked Example .......................................................................................... 57
5.7.1 Pipe Creation............................................................................................................................ 58
5.7.2 Branch Definition ...................................................................................................................... 59
5.7.3 Component Creation ................................................................................................................ 60
Exercise 3 PDMS Design – Pipe Creation............................................................................................... 62
6 PDMS ISODRAFT ................................................................................................................................... 65
6.1 Introduction to Isodraft ................................................................................................................. 65
6.2 Accessing Isodraft ......................................................................................................................... 65
6.3 Producing an Isometric ................................................................................................................. 66
7 PDMS Draft ............................................................................................................................................. 69
7.1 Introduction to Draft ...................................................................................................................... 69
7.1.1 General ..................................................................................................................................... 69
7.1.2 Auto Drawing Production ......................................................................................................... 69
7.1.3 AutoDRAFT .............................................................................................................................. 69
7.2 Creating a Draft Drawing ............................................................................................................... 70
7.3 Creating a Draft Sheet ................................................................................................................... 72
7.4 Creating a Draft View ..................................................................................................................... 72
7.4.1 Populating Views ...................................................................................................................... 74
Exercise 4 PDMS Draft – Create a Drawing ............................................................................................ 76
7.5 Annotating a Drawing .................................................................................................................... 78
7.5.1 Dimensioning............................................................................................................................ 78
7.5.2 Labelling ................................................................................................................................... 79
Exercise 5 PDMS Draft – Labelling .......................................................................................................... 81
8 Exporting to AVEVA Review ................................................................................................................. 82
8.1 Exporting Model Data .................................................................................................................... 82
APPENDIX A – AVEVA Equipment Primitives ............................................................................................ 86
Box (BOX) ................................................................................................................................................... 86
Cylinder (CYLI) ........................................................................................................................................... 86
Cone (CONE) .............................................................................................................................................. 87
Snout (SNOU) ............................................................................................................................................. 87
Pyramid (PYRA) ......................................................................................................................................... 88
Circular Torus (CTOR)............................................................................................................................... 88
Rectangular Torus (RTOR) ....................................................................................................................... 89
Dish (DISH) ................................................................................................................................................. 89
Sloped Cylinder (SLCY) ............................................................................................................................ 90
Extrusion (EXTR) ....................................................................................................................................... 90
Solid of Revolution (REVO) ...................................................................................................................... 91
Nozzle (NOZZ) ............................................................................................................................................ 92

www.aveva.com
© Copyright 1974 to Current Year 6
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 1

1 Introduction

AVEVA PDMS is a complex program with different applications designed to simplify and unify the process of
creating large industrial models. One of the greatest strengths of PDMS is its flexibility, as it allows the users
to setup and configure a project to meet very exact and detailed requirements.

1.1 Aim

The aim of this training guide is to provide a basic working knowledge of how the various modules within
PDMS work, and how they would be utilised in a project scenario.

1.2 Objectives

 Learn how a PDMS Project is created and setup

 Learn how catalogue components are created
 Learn how a basic PDMS model is built
 Learn how pipe isometrics are setup and created
 Learn how general arrangement drawings are setup and created
 Learn how a PDMS model can be exported to Review

1.3 Prerequisites

 Keyboard skills
 Familiarisation with Microsoft Windows

1.4 Course Structure

Training will consist of oral and visual presentations, demonstrations and set exercises. Each workstation
will have a training project, populated with model objects. This will be used by the trainees to practice their
methods, and complete the set exercises.

1.5 Using this guide

Certain text styles are used to indicate special situations throughout this document.

Menu pull downs and button press actions are indicated by bold dark turquoise text.

Information the user has to Key-in will be bold red text.

Additional information notes and references to other documentation will be indicated in the styles below.

 Additional information
 Refer to other documentation

System prompts will be bold and italic in inverted commas i.e. 'Choose function'.

Example files or inputs will be in the courier new font. If users are required to enter information as part of
an example, appropriate fonts and styles previously outlined will be used.
www.aveva.com
© Copyright 1974 to Current Year 7
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 8
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 2

2 PDMS Fundamentals

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

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

2.1 How PDMS can help you

The model can store an extremely large amount 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 plant design project.

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

Different types of output from PDMS

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

PDMS contributes to the quality of the design in the following ways:

 Ensures consistent and reliable component data

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

www.aveva.com
© Copyright 1974 to Current Year 9
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

 Adheres to definable engineering specifications

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

 Ensures correct geometry and connectivity

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

 Avoids component interferences

Despite a wealth of skill and experience in plant design, traditional design office techniques are still
subject to human error. Laying out complex pipe runs, and general arrangements in confined areas
using conventional 2D methods, inevitably leads to clashes between elements, which are trying to
share the same physical space. PDMS enables the user to avoid such problems in two ways:
1. By viewing the design interactively during the design process, allowing visual checks on the
model from different viewpoints and resolves any potential problems as they arise.
2. By using the powerful clash checking facility within PDMS, which will detect clashes anywhere in
the plant, this can be done interactively or retrospectively.

 Annotation and dimensions obtained directly from the Design database

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

2.2 Installation

During the installation sequence, a choice between two levels of installation will be given.

 Full installation Installs all available product components (recommended for new installation
unless there are good reasons for restricting the options available to end
users)

 Custom installation Gives a list of all available product components from which it is possible to
select those to be installed

It is recommended that the default settings are used for folder paths etc. unless there are good reasons for
doing otherwise.

The installation requires at least 750MB of free disk space for the full set of components. Extra capacity will
be required if projects are to be stored on the workstation itself. InstallShield checks that there is enough
space available before it starts, and warns you if there is not.

Before PDMS can be started, the FLEXMAN program needs to be installed. FLEXMAN is based on FLEXlm,
the de-facto standard license manager system. The FLEXMAN product is supplied on all standard DVDs
that contain a full product release. Any hardware or software specific requirements are clearly indicated
where necessary.

www.aveva.com
© Copyright 1974 to Current Year 10
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

2.3 Logging into PDMS

PDMS is started by using one of a set of three desktop icons which are labelled Plant Design, Plant
Engineer and Plant Manage. These can also be accessed using Start > Programs > AVEVA Plant.

Selecting Plant Design 12.1 will display the PDMS version folder (e.g. PDMS 12.1). Opening this folder
displays a list of shortcuts to PDMS modules and utilities.

With the start menu icons there is a

’help’ documentation shortcut which
enables the user to search or browse
through topics.

The PDMS Design module may be accessed by clicking the Design shortcut.

Following the initial splash screen, the Design login

form is displayed.

The user first selects the Project from a drop down

menu. The Project selection will determine the
available entries for Username and MDB.

The Username and MDB may then be selected from

the drop-down menu, or alternatively the appropriate
name may be entered directly into the text box.

www.aveva.com
© Copyright 1974 to Current Year 11
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

When a Password is entered the Login button

becomes active.

Providing the Password is valid, clicking the Login

button enters the PDMS Design module in the selected
project and using the selected MDB.

Clicking the Cancel button aborts the login.

2.4 How PDMS is structured

PDMS is divided into a number of functional modules which access the databases for different purposes.

The main modules and their purpose are listed below.

 Admin Project/User Administration

 Paragon Catalogue and Specification Construction
 Propcon Properties Construction
 Lexicon User Defined Attributes and User Defined Element Type creation
 Design 3D Model Design
 Isodraft Isometric Drawing Production
 Draft 2D Drawing Production

PDMS models can also be visually enhanced using AVEVA’s Review package (this is a standalone
package).

 Review 3D visualisation

2.4.1 Admin

Large plants designed using PDMS are usually broken down into individual areas (either physical areas or
design areas), depending on the size, complexity and configuration of the plant. On a large project, the
System Administrator will first agree with Project and Design Management the breakdown of the PDMS
project into sections which:
 Are relevant to the needs of project reporting and control.
 Form reasonable design subdivisions with sensible match-lines and design content.
 Enable enough designers to work in parallel with simultaneous access to carry out their design tasks.

In much the same way as in a design office (with its section leader, drafts 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 of the Admin module include:
 Access Control (Teams and Users)
 Databases (DB’s)
 Multiple Databases (MDBs)
 Database management functionality

2.4.2 Paragon

Paragon is used to create and modify the component catalogue and specifications stored in a Catalogue
database. The catalogues in PDMS serve a similar purpose to the manufacturers’ catalogues, which a user
would refer to when using conventional design methods. The PDMS component catalogue www.aveva.com
is used to

© Copyright 1974 to Current Year 12

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

specify the geometry, connection information, obstruction and detailing data of piping, structural, HVAC and
cable tray components.

Paragon is used to construct the component catalogue just as Design is used to construct the design data.
It should be noted that, whereas the design data is specific to a particular design, catalogues and
specifications may be specific to a company but general to a number of projects in that company. For
example, the same catalogue component may also appear in other designs proceeding at the same time.

2.4.3 Propcon

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

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

2.4.4 Lexicon

Lexicon enables the definition of User Definable Attributes (UDA) that may be assigned to PDMS elements
so that additional information may be stored in the databases and extracted into drawings and reports.

Lexicon also enables the definition of User Defined Element Types (UDET) that may be defined to enhance
the engineering terminology in the project and differentiate between types of the base element. For
example, an EQUI element may be designated as an element type of, say, :PUMP or :EXCHANGER.

In addition, Lexicon enables the definition of Status elements for use with Status Controller and Database
Views for use with Report Designer.

2.4.5 Design

Design is the graphically driven data input module for the 3D model in PDMS. In this module the plant
model is built and the data stored in one or more databases. The databases contain a three-dimensional
description of all items in the plant. Component selection is provided through specifications that dictate
which catalogue components can be used.

The main features are:

 Creation of new design elements.
 Modification of existing design elements.
 Viewing of the design model interactively by graphical manipulation.
 Creation of reports, e.g. MTO, weight, C of G, project pricing, project timing, etc.
 Clash detection to find interferences between design elements.

The Design module has a number of discipline applications and sub-applications to assist discipline
designers in building models efficiently. These applications are:
 General
 Equipment
 Pipework
 Cable Trays
 HVAC Designer
 Structures
 Cabling System
 Additional Design applications are available if they have been installed, e.g. Multi Discipline Supports
and Nuclear. These applications are separately licensed.
www.aveva.com
© Copyright 1974 to Current Year 13
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Example 3D model in PDMS Design

2.4.6 Isodraft

Isodraft produces dimensioned, symbolic piping and HVAC isometrics for fabrication and construction
purposes.

Isodraft facilities include:

 Full material lists

 Automatic spool
identification

 Automatic splitting
of complex
drawings

 User-defined
drawing sheets

www.aveva.com
© Copyright 1974 to Current Year 14
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

2.4.7 Draft

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

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

2.4.8 Review

Review is AVEVA’s standalone 3D visualisation package that can be used to create realistic images and
video clips of a plant model. It allows the user to add custom textures, such as stainless steel for piping, or
brickwork for walls. It also has the option to add backgrounds and lighting, as well as creating paths for
cameras or objects to move along. This guide will look at how PDMS design data can be exported to
Review.

Review is not included in the PDMS suite, and must be purchased separately.

www.aveva.com
© Copyright 1974 to Current Year 15
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 16
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 3

3 PDMS Administration

3.1 Introduction to Administration

The Admin module would not normally be used by the engineers, designers or drafters. It is a tool for
designing and managing the structure of a PDMS project, and is usually the responsibility of one person, or
on larger projects, a small group of people.

The function of the PDMS Administrator is similar to that of an Administrator for any other multi-user system.
The Administrator will be responsible for creating new Users and Teams, as well creating new databases, or
including/copying databases from existing projects. They can control what Users and Teams can access,
and whether they can write to certain databases, or just read them.

These options allow a certain level of security to be added to a project, as well as facilitating project
maintenance and troubleshooting.

3.1.1 Projects

If you enter your projects folder (by default C:\AVEVA\plant\PDMS12.0\project) you will see the project
folders. A project is identified by a three-character code. For example, the sample project supplied with the
product is SAM. Each project will own at least four folders e.g. sam000, samMAC, samISO and samPIC.

 sam000 is the project directory. It will contain database files which store the actual model data
 samISO is the directory which stores files needed by ISODRAFT
 samMAC is the directory which stores inter-database connection macros
 samPIC is the directory which stores picture files produced by DRAFT

To access the projects environment, variables must be set to the project directories. For the sample project,
the environment variables are set in the supplied evars.bat file.

For example, the file will contain the following line to define the location of the database files:

Set SAM000=c:\AVEVA\plant\PDMS12.0\project\sam000

3.1.2 Teams

Teams are, in essence, the top level of the hierarchy in Admin. Each database belongs to one Team only.
Ownership of a database is established by the naming convention and has the format
TeamName/databaseName.

3.1.3 Users

Users are defined by name and password, which they enter when first starting PDMS. Users are normally
member of Teams. Any User belonging to a Team will have write access to the databases owned by the
Team. Most users will have a Privilege setting of General, restricting access to certain Administrative
elements of PDMS.

www.aveva.com
© Copyright 1974 to Current Year 17
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

3.1.4 PDMS Databases

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

A PDMS project can contain the following types of databases:

Administration Databases:

 The SYSTEM database itself, which holds the access control data for the model data and modules.

 The COMMS database, which stores information about who is using which module and which model
databases are available.

 The MISC database, which stores inter-user messages and inter-database macros.

Model Databases:

 DESIGN databases which contain all the design information for the project.

 CATALOGUE databases which contain the project catalogue and specifications.

 PADD databases which contain data about drawings produced by DRAFT.

 ISOD databases which contain spool drawings produced by SPOOLER.

 PROPERTIES databases which can contain material properties, and can be referenced by the
catalogue.

 DICTIONARY databases which contain the definitions of user-defined attributes (UDAs), as set up in
LEXICON.

 COMPARATOR databases which are used by Design Manager (this requires a separate license,
which if not held, means this type of database will never be used).

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

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

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

www.aveva.com
© Copyright 1974 to Current Year 18
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

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

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

Simplified scenario using Update databases

Multiwrite databases allow any number of users to work in the database simultaneously, creating and
modifying data within it. In order to control the modification of the data, a ‘claim list’ concept is used to avoid
a ‘last saved’ scenario for element modification to occur. Claim lists are discussed in more detail later in the
Training Guide.

Simplified scenario using Multiwrite databases

www.aveva.com
© Copyright 1974 to Current Year 19
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

3.1.5 Including and Copying Foreign Databases

You can copy Databases from other projects. Databases can also be shared between projects, which saves
disk space and eliminates errors which could be caused by copying. Catalogue databases are often shared
in this way.

Databases included from a second project are also known as foreign databases. The second project must
be available: that is, you must be able to read from the second project directory, and have the environment
variables for the second project set.

When you create a project that is going to share databases from other projects, there are two important
considerations:

 Teams must exist for all databases that are shared.

 Databases in the source project that will be shared must NOT be given a database number that will
clash with a database number that already exists in the destination project.

Note that Foreign Databases are marked with a * in the database list.

3.1.6 Multiple Databases (MDBs)

To control what data a user can see, databases are grouped into Multiple Databases (MDBs). A project will
contain at least one MDB. A database may be a member of any number of MDBs.

An MDB must contain all the data that the user need to access. For example, for a DESIGN user, the MDB
must contain a Catalogue database and the Design database that the user is going to work on. In addition,
the MDB should contain all other Design databases with data in the same physical volume, which will ensure
the accuracy of clash checking, and all other Design databases which will have connections to the user’s
design area.

3.1.7 References between Databases

When you create a Branch (e.g. a branch of a pipe), PDMS sets a Head Reference (HREF) and/or a Tail
Reference (TREF) for that Branch to the items it is connected to, for example a Nozzle or a Tee name.

It also sets the Connection Reference (CREF) of that item to point at the Branch that has been connected.

If you have write access to the connected component it just connects and sets the relevant connection
references. If you don’t have write access, an Inter-Database connection macro is created. Users that have
write access to that item will then receive a message via PDMS telling them that a macro has been created.
They can then run the macro to complete the creation of the connection references.

www.aveva.com
© Copyright 1974 to Current Year 20
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

3.2 Creating a New Project – A Worked Example

Creating a new Project is done from outside of the main PDMS interface. In version 12, a Project Creation
Wizard has been introduced. This can be found in Start > All Programs > AVEVA Plant > Design >
PDMS 12.1.SP2 > Project Creation Wizard.

Running the Project Creation

Wizard will display the wizard
form.

The Project textbox can have an

eight character alpha-numeric
name.

The Code is restricted to three

alphabetical characters. This
Code will also define the names
of the directories that are created.

The Address will default to the project directory in the PDMS installation, but can be changed. Often the
location of a project will be on a network drive.

Clicking Project Variables allows you to add additional directories or project areas.

Clicking Existing Projects will show you a list of the projects currently available.

Clicking Details allows you to enter further text information about the project such as an extended name or
description.

Once sufficient information has been entered, the Create… button will become active, and clicking it will
create the skeleton of the new project.

Create a new project named Training with the project code TRA.

Leave the remaining settings as default and click the Create… button.

The Project Creation Wizard window will now close and PDMS will create the project files required.

3.3 Using PDMS Admin – A Worked Example

PDMS Admin can be accessed via the start menu:

AVEVA Plant > Design > PDMS 12.1 > Admin.

Alternatively the Admin module can be accessed

using the desktop shortcut as described previously.

When a project is first created, there is only one user named SYSTEM. The SYSTEM user is a Free user,
meaning the user has unrestricted access to the PDMS modules. As previously mentioned, the majority of
users within a project will not be Free users, and have a Privilege setting of General. This will prevent them
from accessing the Admin module.

Login to PDMS Admin using the following details: Project: TRAINING

User: SYSTEM
Password: XXXXXX
MDB: <blank www.aveva.com
© Copyright 1974 to Current Year 21
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

3.3.1 Creating a New Team

To create a new Team, ensure that Teams has been selected from the Elements pull -down list.

Click the Create button to prompt the Create Team form as shown below.

From here the user is able to define a Team name and Description into the appropriate textboxes. If Users
have already been created, these could be added as Team Members at this point.

Enter the team name DESIGNA and Description Design Team A.

Once the information has been input, click Apply to complete the creation.

www.aveva.com
© Copyright 1974 to Current Year 22
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

3.3.2 Creating a New User

Selecting Users from the Elements pull down, and then clicking Create will bring up the Create User form
as shown on the following page.

For a User a Name and Password are required to be entered. In addition, a Description may be entered,
and a Security type can be selected (Free or General).

Create a new User called USERA and press the Return key. Click the Set Password button and set this to
A. A description can be entered, for example A User.

Make the new User a member of <TEAM> DESIGNA by highlighting the team and clicking the black arrow
icon to move it across from Project Teams to Team Membership as shown.

As before, clicking the Apply button completes the creation.

3.3.3 Creating a New Database

Select Databases and Extracts from the Elements pull-down menu

and click the Create… button. The prompted form offers the User an
option of creating either a Master DB or Extract of a DB.

Select the Master Database option. Extract Databases will not be discussed in this guide.
www.aveva.com
© Copyright 1974 to Current Year 23
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Clicking OK will open up the Create Database form as shown below.

The Owning Team must be selected. Select the

team DESIGNA that was previously created.

Name and Description are basic alpha-numeric

fields.

Enter the name NEWPIPE and type a description

in the text box below.

Database Type specifies what type of information

will be held in the Database, such as Catalogue
information, Design information, Drawings etc.
For this example select Catalogue from the drop
down list to make NEWPIPE a catalogue
database.

Create SITE defines a name for a new site that is

created along with the Database. As it is not
required in this instance, leave the text box as
unset.

Access Mode controls how the Database is

accessed. The choices are either Multiwrite or
Update, and Implicit Claim and Explicit Claim.
These determine how and when a User can write
information.

Select Multiwrite and Implicit claim from the

drop down boxes.

Area, DB and File Number are reference

numbers primary for internal use. System
denotes that PDMS will manage the numbering
which is suitable for this database.

After entering the necessary information, click Apply to complete the creation of the new database.

3.3.4 Adding Foreign Databases

For the Databases and Extracts Element, the following options are available at the bottom of the screen:

Both the Include… and Copy Foreign functions work in the same way, however with Copy Foreign the
databases have to copied one by one, whereas Include… allows a selection to be included in one click.

Selecting Include… will open the screen shown on the next page. At the top of form is a list of the Projects
from which databases can be included. The bottom half of the form list all the databases available for
inclusion within the project. Multiple databases can be selected by using the Shift or Ctrl keys.

www.aveva.com
© Copyright 1974 to Current Year 24
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

In this example, all of the databases from the MASTER project will be added to the Training project as
foreign databases.

Click the Include… button while on

the Databases and Extracts
element screen to display the
Include Foreign Database form.

First, select the Master database

from the Foreign Projects part of
the form.

In order to include a foreign

database, a valid Username and
Password is required for the
Foreign Project, which must be
entered on the form.

In this case, enter the Username

SYSTEM together with the
password XXXXXX.

Select all the MASTER/ databases

from the foreign databases list by
Shift-Clicking on the databases.

Once the required Databases have

been selected, and a valid
Username and Password entered,
click Apply to include the
databases in the new project.

3.3.5 Creating an MDB

To create a Multiple Database, select MDB from the Elements pull down menu and then click Create…

The Create Multiple Database form will then be displayed, as shown below.

To create a Multiple Database, a Name must first be entered.

In this case Name the MDB TRAINA. The description can be left as unset.

Databases can be moved between the Project Databases and Current Databases lists using the arrow
icons. If there are one or more databases already in the Current Databases list, then the Insert pull down
allows you to specify whether the next database added will be placed Before or After the currently selected
Database.

Add all the available databases to the TRAINA MDB by highlighting them and clicking the down arrow to
place them into the Current Databases list. Ensure that newly created Master Databases are at the top of
the Current Databases list.

To reorder databases, they may be moved across to Deferred Databases and back again.

www.aveva.com
© Copyright 1974 to Current Year 25
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

It is good practice to put the databases that are going to be used most frequently at the top of the list.

www.aveva.com
© Copyright 1974 to Current Year 26
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Exercise 1 PDMS Administration

Using Chapter 3 as a guide, complete the following tasks.

1. Create an additional team called ADMIN.

2. Make USERA a member of the ADMIN team

3. Create three additional Master Databases, all with Owning Team set to:

- NEWDESI (Type: Design).

- NEWISO (Type: Isodraft).
- NEWDRAFT (Type: Draft).

All have owning Team, DESIGNA and have the same Access Mode (and Number def.) as
NEWPIPE.

4. Include the foreign database ADMIN/PADD from the Sample project.

5. Add ADMIN/PADD to the created MDB

6. Check that the tasks have been completed as required by exiting PDMS Admin and logging into the
PDMS Paragon Module using the new User, Password and MDB credentials.

www.aveva.com
© Copyright 1974 to Current Year 27
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 28
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 4

4 PDMS Paragon

4.1 Introduction to Paragon

PARAGON enables PDMS Catalogue databases to be built by creating or modifying both Piping
Components and Steelwork Components (Profile, Joints and Fittings) using an intuitive graphical user
interface.

The catalogues in PDMS serve a similar purpose to the manufacturers’ catalogues, which would be referred
to when using traditional design methods. The PDMS component catalogue is used to specify the
geometry, connection information, obstruction and detailing data of piping, structural, HVAC and cable tray
components.

Paragon is used to construct the component catalogue just as Design is used to construct the design data.
It should be noted that, whereas the design data is specific to a particular design, catalogues and
specifications may be specific to a company but general to a number of projects in that company. For
example, the same catalogue component may also appear in other designs proceeding at the same time.

The hierarchy within Paragon is represented by the diagram below:

The Catalogue World sits beneath the WORLD element that all PDMS projects and modules contain. Below
is a brief description of the eight elements that can sit beneath the Catalogue World.

 PRTWLD – Part World

A Part World owns Part Families. These consist of a number of Parts containing reference attributes.
The main purpose of the Part Families is to allow a component to be fully described without the need for
an associated Piping Specification,

 TABWLD – Spec Table World

Tables are used widely to define and configure a range of attributes and key items of information.

A Size Range Table allows a range of nominal bore sizes to be set that are allowed in a specification
that references the table.

A Branch Table performs a similar function, allowing combinations of branch and header sizes to be
defined.

A Reducer Table allows the combinations of large and small end sizes for Reducers to be defined.

 NBRWLD – Nominal Bore World

Similar to a Spec Table World, the Nominal Bore World defines a range of bores that a specification
referencing it can use.

 SPWL – Specification World

This is where Pipe Specifications are created either using PARAGON or SPECON (Specification
Constructor), although the latter only accepts input in a tabular format.

www.aveva.com
© Copyright 1974 to Current Year 29
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

 CCTA – Connection Tables

Connection Tables are a coding system for defining which pairs of connection types are compatible with
one another. These connection types can be created and edited by the user. A likely example might be
pairing the BWD (Butt Weld) connection type with the FBD (Flange facing, Raised Face, 300lb rated)
connection type, as this would be a common combination in practice.

 CATA – Catalogue
The Catalogue is where the sections are created. These could be profiles of steel beams or columns, or
different piping components such as Valves, Tees or Elbows.

 BLTA – Bolt Tables

The Bolt Table contains information describing the nature of the bolted connections of Piping
Components, such as the number of bolts required for a given flange diameter, their length and diameter,
or information about nuts and washers. The Bolt Tables are designed for the exclusive use of Isodraft.
This is to allow Isometrics to be produced with detailed enough information to give the fabricators
everything they need.

 UNITS – Unit Types

Paragon enables unit types to be set up which will then be linked to attributes of various elements that
appear throughout the PDMS database. The most common units (and also the defaults) are millimetres,
inches, or feet and inches, which are usually assigned to bore and distance measurements.

This training and the associated exercises will focus on the creation of Piping Components rather than
steelwork or specifications.

The first part is a step-by-step exercise to create an Elbow. The exercise requires trainee to follow the same
procedure to create a Flange, Tee and Gasket from a basic diagram and table of measurements.

4.1.1 Creating the Paragon Hierarchy

On loading PDMS Paragon using the newly created login credentials, the Catalogue Explorer is displayed.
The explorer lists Catalogue, Design, Draft and Property Worlds. Expanding the Catalogue World should
result in the following view.

The first item under the Catalogue World is the

newly created /NEWPIPE database. The DESIGNA
tag denotes that it is owned by the DESIGNA team,
of which USERA is a member.

This database will be used to hold the new

components.

Paragon has a number of sub-modules that relate to the different fields of component creation. By default
this is set to General. From the main Paragon menu, change the sub-module to the required Pipework…
www.aveva.com
© Copyright 1974 to Current Year 30
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

In order to ensure that a coherent and sensible naming structure is used, go to Settings > Naming… and
tick the Auto Naming On/Off checkbox.

The first element to be created is the Catalogue (CATA): select Create > Catalogue… The Create
Catalogue form is displayed. From here a Name and Purpose must be specified, in this case
TRAIN.CATA and PIPE respectively. Click the OK button to create the Catalogue.

The next element to be created is the Section (SECT): select Create > Section… This usually the point at
which different component types are defined e.g. valves or elbows. The Create Section form is displayed.
As found with the Catalogue form, a Name and Purpose must be entered.

For this example, enter the Name ELBO-TRA and set the Purpose to PIPE.

The final element to be created is the Category: select Create > Category… The Create Category form is
displayed. The Category Name is often given using an industry coding system that defines key
characteristics of the component. In this case the Category Name will be TRA-SPEC to aid understanding
and again, the Purpose set to PIPE.

Once the Category has been created, the Model View form will be displayed automatically.

www.aveva.com
© Copyright 1974 to Current Year 31
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

4.1.2 Creating the Component Category Element

When the Model View form first appears, it should look like the example below.

The first task is to

input the required
parameter names for
the Element in the
Parameter
Definitions list.
Nominal Bore is
always there by default
for Piping
Components.

To add additional
parameters, click New,
type the name in the
Desc: box and click
the Apply button.

Add the parameters shown here.

www.aveva.com
© Copyright 1974 to Current Year 32
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

The next task is to rename the component and add a description and Generic Type. To do this, first select
Component in the Model References pane, as shown below.

The bottom of the Model View form will update to display References.

Change the name to /TRA-SPEC-100, the Description to 100mm Elbow and the Generic Type to ELBO.

Click Apply to confirm these changes.

4.1.3 Creating a Component Copy

As the description suggests, the first component is a 100mm bore Elbow, but a 150mm and 200mm version
are also required. In order to do achieve this variation, copies of the first component will be created and
modified.

Select Category in the Model References pane.

At the bottom of the form, the first component created, /TRA_SPEC-100, will be shown in a table. Select
this component and click the Copy button twice to create two additional components.

www.aveva.com
By clicking on the Name, the copies can be renamed to /TRA-SPEC-150 and /TRA-SPEC-200.

© Copyright 1974 to Current Year 33

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

4.1.4 Adding the Parameter Values

By clicking in the boxes for PA1 to PA5 for

each component, a value can be entered.

Fill these in using the values shown on the

right.

 Note: The parameters can also be changed from References area at the bottom the Element pane, but
the parameters are not numbered, and they only relate to the element that was last selected at the
bottom of the Category pane.

By selecting the 150mm and 200mm versions of the elbow from the Category pane table, and then
switching to the Component pane, the descriptions of these two elements can be updated to reflect the
different bore size.

4.1.5 Constructing the Pointset

The Pointset (PTSE) is a definition of the axis system, and creates a series of Ppoints that can be used to
help define geometry and viable connections. The Ppoints are created on an XYZ axis system with the
component origin, or P0, being set to 0, 0, 0.

To switch to the Pointset creation options, select Point Set: from the Model References pane.

In order to make the process slightly easier, first tick the Axes checkbox at the top of the Model View form
to display a set of axes in the 3D View window.

Next, click the Representation button to the right of the P-Lines tick box to display the following form.

Tick the Display and Numbers boxes under the Ppoints heading to display and number the Ppoints as they
are created, thereby making them easier to identify on the screen.

www.aveva.com
© Copyright 1974 to Current Year 34
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

The Model View form should now look like the example shown below.

To create a new Ppoint, one of the Ppoint types must be selected from the New pull down at the bottom of
the form. For these exercises, only the Axial P-Point type will be required.

Select Axial P-Point from the pull down and the form will be updated to reflect the selection.

A new Ppoint has a number of data fields that can be entered. A number of these fields can be expressed in
relation to the Parameter previously defined.

 P-point Number – each Ppoint must have a different number.

 Connection Type – this will be taken from the Parameters.
 Bore – this will be taken from the Parameters.
 Axis Direction – as well as a position, a Ppoint has a direction, and this is defined here.
 Distance – this is the distance to the Ppoint from the origin (P0).
www.aveva.com
© Copyright 1974 to Current Year 35
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Start by defining Ppoint 1 using the parameters shown below.

Click Apply to create the Ppoint.

Next create Ppoint 2 using the next set of parameters shown below.

Again, click Apply to create the Ppoint.

The end result should look like the example below.

www.aveva.com
© Copyright 1974 to Current Year 36
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

4.1.6 Constructing the Geometry Set

The Geometry Set is the obvious part of the catalogue, since this is the visible item seen by everyone
connected to a project.

The component will be constructed from a series of basic primitives, such as cylinders, boxes and cones.
The Ppoints created in the Pointset and the parameters created earlier will be used to help position the
primitives. It is important to have a mental image of the component to be created and how it will be
orientated about the axis system.

Start by selecting Geometry from the Model References pane.

The bottom of the form will be updated to show the Geometry References pane.

To represent the Elbow, select a Positive SCTO (Circular Torus) primitive from the pull down menu and tick
the Show Geometry Plot box. This tick box will display a plot showing the different parameters for the
primitive graphically, as shown below.

www.aveva.com
© Copyright 1974 to Current Year 37
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

In the case of the Elbow, the A Axis can be set to P1 (Ppoint 1) and the B Axis to P2. The PDIA can be set
to PARAM 2, so that is corresponds to the Outside Diameter parameter set earlier.

To complete the primitive definition, set:

Representation (or Repr) to Piping Detail – allows the component detail to be switched off in favour of
other views

Drawing Level to 0 to 10 – can be used as a filter to adjust which components are visible

Obstruction to Hard – tells PDMS that this component is solid so that if anything else overlaps, it will flag as
a Clash

Tube Flag to On – displays the outline of the elbow

Click Apply to create the primitive. Untick the Show Geometry Plot checkbox to view the component.

To complete the component, a Centre Line needs to be created along with two spheres to represent the
welds at each end.

The centre line parameters are as shown:

www.aveva.com
© Copyright 1974 to Current Year 38
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

The first sphere parameters are as shown here:

The second sphere has identical parameters to the first, except for the Direction which should be set to Y.

Changing the Repr. pull down menu, located at the

top right of the Model View form to Piping Centre
Line will show the centreline of the elbow along with
a representation of the welds.

www.aveva.com
© Copyright 1974 to Current Year 39
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Exercise 2 PDMS Paragon – Component Creation

Go through the same process as with the Elbow, starting from the creation of the Section under the
TRAIN.CATA Catalogue and create the following two components. The P-Point Configuration diagram
provides information on the P-Point positions and directions relative to one another.

A Concentric Reducer – Primitive: LSNO

P-Point Configuration

Connection BWD

Nominal Size Value ‘A’ Value ‘B’ Value ‘C’

200x150 219 mm 168 mm 152 mm
200x100 219 mm 114 mm 152 mm
150x100 168 mm 114 mm 140 mm

A Tee – Primitives: 2 x LCYL

D
P-Point Configuration
C

Connection BWD
B

A A

Nominal Size Value ‘A’ Value ‘B’ Value ‘C’ Value ‘D’
100x100 105 mm 114 mm 105 mm 114 mm
150x150 143 mm 168 mm 143 mm 168 mm
200x200 178 mm 219 mm 178 mm 219 mm
200x100 178 mm 219 mm 156 mm 114 mm
www.aveva.com
© Copyright 1974 to Current Year 40
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 5

5 PDMS Design

5.1 Introduction to Design

Design is the main, graphically driven constructor module within PDMS. In this module the plant model is
built and the data stored in one or more databases. The databases contain a three-dimensional description
of all items in the plant. Component selection is provided through specifications that dictate which catalogue
components can be used.

The main features are:

 Create new design elements

 Modify existing design elements

 Interrogate and View the design model interactively by graphical manipulation

 Create Reports to detail project pricing, project timing, material lists, customisation of user defined
requirements etc.

 Run a Clash detection application to check interference between design elements

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

The PDMS Design Database Hierarchy

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

www.aveva.com
© Copyright 1974 to Current Year 41
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

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

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

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

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

Every element is identified within the database structure by an automatically allocated reference number
and, optionally, by a user-specified name.
The following sections give descriptions of the main element types in a PDMS Design database. Most of the
element types are abbreviated, usually to the first four letters of the full name, when they are displayed in the
user interface.

5.1.1 World (WORL)

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

5.1.2 Site (SITE)

Below the WORLD, the second level of the hierarchy is SITE. A SITE may be considered as a significant
collection of plant, whose size is not necessarily determined by physical area, but by practical
considerations. It may, for example be the whole project, or one part of a large project. You can have as
many SITEs within a PDMS project as required for data organisation.

5.1.3 Zone (ZONE)

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

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

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 in space to represent the equipment item. The
primitives may be owned directly by the EQUI element or by a Sub-Equipment element.

5.1.5 Sub-Equipment (SUBE)

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

www.aveva.com
© Copyright 1974 to Current Year 42
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

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 primitives; each with its own features which when combined with
other primitives can represent complex shapes.

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

5.1.7 Structure (STRU)

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

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.

5.1.9 Sub-Framework (SBFR)

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

5.1.10 Structural Components

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

5.1.11 Pipe (PIPE)

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

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 Branch may own a wide variety of components such as Gaskets (GASK), Flanges (FLAN), Elbow (ELBO),
Tees (TEE), Valves (VALV), etc. These form the shape and geometry of the Branch and ultimately the Pipe
itself.

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

5.2 The Design Window

When entering PDMS Design, the main window is displayed.

www.aveva.com
© Copyright 1974 to Current Year 43
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

 Main Menu – contains application command menus

 3D View Window – the window in which the design model will be displayed. This window has horizontal
and vertical toolbars

 Prompt Area – the main prompts are displayed here (measurements etc.)

 Status Area – displays viewing parameter status information. Prompts are displayed here when
graphical interaction is required.

The main window can be repositioned or minimised at any

time by using the standard Windows buttons. Many of the
forms and toolbars, such as the Design Explorer can be
moved and/or docked to create a customised layout. This is
done by clicking and dragging on either the dotted line
marking the end of a toolbar, or the title bar of a form, and
then moving it to the required position. If docking is available,
a set of docking icons will appear (as shown below), and
moving the cursor of the icon will preview where the form will
be docked.

5.3 Using the Mouse

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

The mouse steers the graphics pointer around the screen and is also used to select or ‘pick’ items by using
the mouse buttons. The buttons perform different tasks depending on the type of window, and the position
within the window, where the pointer is positioned. The appearance of the pointer will change according to
the type of display item that is underneath it. www.aveva.com
© Copyright 1974 to Current Year 44
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

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

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

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

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

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

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

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

5.4 Key Tools within Design

There are a number of functions and tools within the Design modules aimed at making common tasks
quicker and easier.

5.4.1 The Model Editor

The Model Editor can be used to position and rotate items in the PDMS database. To enter
the Model Editor Mode select the Model Editor icon, shown below.

Items selected in the 3D View Window whilst in Model Editor

Mode will be displayed with a set of handles that can be
clicked and dragged to move or rotate the item.

Right clicking on a handle will bring up a menu with additional positioning options, such as Align with
Feature… or Snap to Point… These can make positioning an item very quick and easy if it needs to be
aligned with or joined to an existing point.

www.aveva.com
© Copyright 1974 to Current Year 45
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.4.2 Application Specific Toolbars

When switching to one of the specialist module within Design, e.g. Pipework, HVAC, Structures, or to sub-
modules within those, toolbars specific to that discipline are loaded, providing shortcut buttons to many of
the key tasks.

The pictures below show the toolbars for Equipment, Pipework and Structures. Examples of the functions
offered on the Pipework Toolbar are Pipe Creation, Pipe Modification, Component Creation, and
Component Selection.

www.aveva.com
© Copyright 1974 to Current Year 46
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.5 Equipment Creation – A Worked Example

There are two ways that items of equipment can be created within PDMS. One is by building an item using
primitives to construct the geometry. The other is to use a predefined equipment template.

To begin the Worked Example, ensure that Equipment mode is currently selected from the Design tab on
the main menu. Next select the World (WORL) level in the Design Explorer, and then select Create > Site…
from the main menu. This will display the Create Site form, where /TRAINING-SITE should be entered as
the name. Press Enter to confirm the name.

Click OK on the form to create the SITE element. Notice that the new element appears in the Design
Explorer as the current element.

Next create two ZONEs using the Create > Zone... option from the main menu and call them /EQUIP and
/CIVIL.

5.5.1 Creating Equipment from Primitives

The first item to be created is a base for the subsequent elements to sit on. This will be modelled as an
Equipment component, using a Box, in the CIVIL zone.

 See Appendix A for details of PDMS Primitives.

Start by selecting the /CIVIL zone in the Design Explorer. Next

create an EQUI element by selecting Create > Equipment…
from the main menu, and name it SLAB. The Equipment
Creation form also has the option to position the EQUI element
with respect to (wrt) either the World or any other existing
element. Enter the position as East 0, North 0, Down 100 wrt
World.

www.aveva.com
© Copyright 1974 to Current Year 47
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Next select Create > Primitives… from the main menu, pick the Box
from the Primitives form and click Create Primitives. The Primitives
form will change to show the Box properties.

The origin of the Box (in the very centre) will be placed at the origin of
the EQUI element, as previously defined.

Enter the X Length as 10000, the Y Length as 10000 and the Z

Length as 200. As the Equipment origin is currently set to Down 100
with respect to the World, and the origin of a box is at its centre, a Z
Length of 200 will put the top surface of the Box at 0 on the Z axis.

Click Create to complete the process. Dismiss the form using the Next
button.

To check the position of the top of the Box, select Query > General…
from the main menu and set the drop down boxes to Position, P3 and
World. The result in the pane below should give a Position of E 0mm N
0mm U 0mm.

Next create another EQUI element, but this time under the /EQUIP zone and name it TANK. Enter the
position as West 2000, North 2000, Up 1500 wrt World.

Next select Create > Primitives… from the main menu, pick the Cylinder from the Primitives form and
click Create Primitives.

The origin of the Cylinder (in the very centre) will be placed at the origin of the EQUI element, as previously
defined.

Enter the Height as 3000 and the Diameter as 2500 and click Create. The bottom of the Cylinder should be
sitting directly on the top of the /SLAB.

To verify this visually, view a side elevation of the equipment by right clicking anywhere in the 3D view
window then selecting Look> North. Then switch to a wire line view of the model by pressing the F8 key and
inspect.

www.aveva.com
© Copyright 1974 to Current Year 48
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

To add a top to the tank, create a Dish with the same Diameter as the
Cylinder, a Radius of 75 and a Height of 250, and then click Create. The
Dish will initially be placed at the origin of the EQUI, and so will be sitting
in the middle of the Cylinder.

Once the Create button has been clicked, additional modification options
appear on the form, one of which allows the position of the primitive to be
adjusted.

Type 1500 into the Up box and press Enter. The Dish should now be
sitting on top of the Cylinder.

To complete the Tank, two Nozzles

will be created using the Create >
Nozzles… option from the main
menu.

Enter the name as /TANK-N1 and

then click Nozzle Type… and set it
to #300.R.F., Ansi Flanged,
100(mm). Click Apply to return to the
Create Nozzle form.

Complete the rest of the form using

the information in the example of the
next page. This should create a
Nozzle coming out from the centre of
the tank, facing to the East.

www.aveva.com
© Copyright 1974 to Current Year 49
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Create a second Nozzle called /TANK-N2 with the same Nozzle Type
and parameters as the first, except this time set the Up parameter to
500. The end result should look like the image below.

In order to make the nozzle holes visible, the Holes Drawn tick box
must be checked in the Representation tab in the Settings >
Graphics form.

5.5.2 Creating Equipment from a Template

First reselect the /EQUIP zone in the Design Explorer.

To create an item of equipment from a template, select Create > Standard Equipment from the main menu.
The Create Equipment form will then be displayed.

www.aveva.com
© Copyright 1974 to Current Year 50
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Enter the name as /PUMP.

Click the Specification radio button and set the drop

down menu to AVEVA Standard Equipment.

From the bottom list select:

“Standard” Standard Pumps
“Centrifugal” Pumps
“Centreline” Mounted Centrifugal Pumps
“PUMP 005” Centre Line Mounted, Tangential
Offset

A preview of the selected pump will then be displayed

in the bottom window.

Clicking the Properties… button will bring up a

Modify Properties window. This allows certain
parameters of the equipment to be changed.

Change the Baseplate Length to 1200 and the

Baseplate Width the 500. Click OK to confirm the
changes.

Once the Apply button is clicked to create the Pump,

a prompt will appear in the Prompt Area at the top left
of the 3D View stating, ‘Position Equipment Origin
(Snap) Snap’.

As PDMS is now requesting a position, the Positioning Control Toolbar will be displayed in the Toolbar
Menu.

There are a variety of options for positioning, but in this instance the pump will be positioned explicitly using
the Explicit Position icon . Set the position to East 2000, South 2000, Up 3360 and click Apply.

The pump should be sitting elevated over the base.

The final modification to make is to the Nozzles on the Pump. In the hierarchy expand the EQUI PUMP
element, and then expand the TMPL 1 element beneath it.

www.aveva.com
© Copyright 1974 to Current Year 51
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Select NOZZ 1 and then select Modify > Nozzle

Specification… from the main menu. Set the
Nozzle to #300.R.F, Ansi_flanged, 100(mm) and
click Apply.

Change NOZZ 2 to #300.R.F., Ansi_flanged,

50(mm).

5.6 Structure Creation – A Worked Example

Basic structures are created using Beams, Columns, Panels and Plates. For this worked example, a stand is
going to be created to support the pump.

5.6.1 Setup

First switch to the Beams and Columns sub-module by selecting Design > Structures… > Beams and
Columns… from the main menu. The Beams and Columns Toolbar should then appear somewhere in the
Toolbar Menu.

Section Specification Section Storage Area Node Storage Area

Next create a ZONE and Structure (STRU) under /TRAINING-SITE in

the same manner as before, and name them /STRUC and /STAND
respectively. Under /STAND create a Framework (FRMW) and name it
/STEEL.

Before starting to create the structure, the Pick Filters and Section Specification need to be set.

To set the Pick Filters go to Settings > Pick Filters > Plines… and set the Rule to Normal. This rule acts
as a filter, determining how connections are made and where sections will run to and from.

www.aveva.com
© Copyright 1974 to Current Year 52
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

To set the Section Specification, click the Set

Default Profile Specification icon on the
Beams and Columns Toolbar, and set it to British
Standard, Universal Columns, 203x203x46kg/m,
and the Justification to NA (Neutral Axis).

Next set the Section Storage Area and Node Storage Area. To do this, select the /STEEL Framework in
the Design Explorer and click the icons left of the text area in the Beams and Columns Toolbar, as
indicated by the arrows on the example above.

5.6.2 Creating the Columns

To begin creating sections select Create > Sections > Straight… from the main menu, and the following
menu will appear.
First tick the Confirm box in the Verification section.

Next click the Explicit Position button .

Set the position to East 1000, South 3500, Up 0 and then click OK. The
Start point for the column will now be displayed in the 3D View.

To set the end point, click the Define Section End button , set the
Direction to U WRT /* and enter 3000 in the Distance box. Click the OK
and then Accept button to create the first column.

To create the other three columns of the stand, select Create > Copy > Offset… from the main menu and
set the Y Offset to 2000 as shown below:

www.aveva.com
© Copyright 1974 to Current Year 53
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Click Apply and then Yes to the ‘Retain created

copies?’ dialogue.

The Copy with Offset form should still be

visible. Change the Object pull down to Pick,
change the Y Offset back to 0, and change the
X Offset to 2000.

Once the Apply button has been clicked an

‘Identify items to copy’ prompt appears at the
bottom left of the PDMS window. Click on the
two existing columns in the 3D View to select
them (they should turn red), and then press the
Esc key to exit the selection process.

A Confirm dialogue should appear:

Click Yes and then Yes again to the ‘Retain created copies?’
dialogue. There should now be four evenly spaced columns
sitting on top of the base.

5.6.3 Creating the Beams

To create the beams, first change the Section Specification to British Standard, Universal Beams,
203x133x25kg/m and the Justification to TOS (Top of Steel).

Select Create > Sections > Straight… and again click the Confirm tick box. The Positioning Control
Toolbar should have appeared again. This time select Element and Snap from the pull downs.

To create a beam, click on the top of one of the columns and select the top of an adjacent column, and then
click the Accept button. Place the other three beams in the same way to create the platform.

www.aveva.com
© Copyright 1974 to Current Year 54
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.6.4 Creating a Panel

The next part of the example is creating a panel on top of the stand for the pump to sit on.

First, switch to the Panels and Plates sub-module by selecting Design > Structures > Panels and Plates…
from the main menu.

Next create a new Framework (FRMW) under the /STAND Structure called /PANEL, and set the Panel
Storage Area and Panel Linear Joint Storage Area to this Framework in the same way as the Section and
Node Storage Areas were with the steelwork.

Select Create > Panel… from the main menu and the following menu will appear:

Set the Thickness to 10 and the Justification to

Top.

Make sure the Pline Rule is still set to Normal in

the Pick Filters.

Next select the Derive points from graphic picks button in the Create Methods section of the
form. Set the Positioning Control Toolbar to PPoint and Snap.

Zoom in to the top of one of the columns and click and hold the left mouse button anywhere on the column.
Move the mouse pointer to the outside corner of the column until a small white crosshair appears, and then
let go of the mouse button. An Origin label should appear next to this point, denoting that this is the start
point for the panel.

www.aveva.com
© Copyright 1974 to Current Year 55
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Do the same again for one of the adjacent columns and a Last Vertex label should appear.

Repeat this procedure for the next two columns and a square panel covering the top of the stand should
evolve to complete the structure. It is important that the vertices are created going either clockwise or anti-
clockwise around the columns, and not diagonally, otherwise the panel will not be created correctly.

www.aveva.com
© Copyright 1974 to Current Year 56
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.7 Piping Creation – A Worked Example

To start creating Pipework, select Design > Pipework… from the main menu. This will activate the
Pipework Toolbar.

The Pipework Toolbar is used to manipulate Pipes, Branches and Branch Components. The buttons
associated with the toolbar are summarised in this section.

The default Piping Specification can be reset using this Icon. Default Pipe Specification is shown in this text
box.

Used for the Creation and Modification of Pipes.

Display Piping Components Creation Form

Used for reselecting Piping Components.

A range of Piping Components can be deleted using this icon.

Used to Align components.

Used to Orientate Components.

First create a new ZONE called /PIPES under the /TRAINING-SITE.

www.aveva.com
© Copyright 1974 to Current Year 57
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.7.1 Pipe Creation

Click the Pipe Creation Form button from the Pipework Toolbar to load the Create Pipe form.

Name the pipe PIPE_1.

Set the Pipe Specification to A3B

Set the Bore to 100mm.

Click Apply to create the PIPE element in the hierarchy.

www.aveva.com
© Copyright 1974 to Current Year 58
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.7.2 Branch Definition

Clicking the Apply button on the previous form will automatically load the Modify Pipe form. The form can
also be accessed by selecting the Pipe Modification button from the Pipework toolbar.

To set the start and end points for the pipe, first click the Change
button under the Head Connection heading. The form will
change to allow a point to be selected. Click the Pick button;
select the larger of the two nozzles on the pump (NOZZ 1) and the
click Connect to confirm the selection.

Next click the Change button under the Tail Connection heading.
Click the Pick button, select the upper of the two nozzles on the
tank and click Connect to confirm the selection.

A dotted line should have appeared showing the shortest route between the two nozzles.

It is important to check that the Connection Type for both the head and tail are set to FBD. If they appear as
anything else, then the Nozzle Specification is incorrect and will cause problems when the pipes are
created.

 See sections 5.5.1 and 5.5.2 for information on the correct Nozzles Specifications and how to modify
them.

www.aveva.com
© Copyright 1974 to Current Year 59
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

5.7.3 Component Creation

Next select the Pipe Component Creation button from the toolbar to load to Component Creation form.

Click on Flange from the component list and then select WN

(Weld Neck) from the list of Flange types.

Check to make sure that With Flow and Auto Create Adjacent
are selected at the bottom of the form.

With Flow tells PDMS to create the components from the Head and work forward. Switching to Against
Flow will set the component creation to start from the tail and work backwards.

Auto Create automatically adds any essential components. In the case of a Flange, a Gasket will be placed
in front of it.

Click the Connect button to create the gasket and flange attached to the pump.

www.aveva.com
© Copyright 1974 to Current Year 60
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Next click Set Branch to return to the component creation form

and create an Elbow (EL90), making sure that the Flange is the
current element in the Design Explorer.

Using the Model Editor , position the Elbow to line up with

the tail nozzle on the tank, by right clicking on the X Axis
handle and using the Align with Feature... function. Once
Align with Feature… has been selected, position the mouse
over the centre of the tank nozzle to snap to the position, and
click to confirm. A length of pipe will automatically be created
between the flange and the elbow.

Next rotate the Elbow so that the open end is facing down.

Create a second Elbow; rotate it so that the open end is facing the nozzle.

Click the Align Selection/Component icon which will move the elbow downwards to align with the
nozzle. A length of pipe will be created automatically once the elbow is aligned with the nozzle at the tail of
the branch.

To add a Flange and Gasket to the nozzle on the tank, first select the Branch (PIPE1/B1) in the Design
Explorer and create a Weld Neck (WN) Flange with the Against Flow button selected.
www.aveva.com
© Copyright 1974 to Current Year 61
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Exercise 3 PDMS Design – Pipe Creation

Using Chapter 5 as a guide, create PIPE_2. Instead of using the Change button under Head Connection,
use the Change button under Head Detail, and set the parameters to be the same as the example below.

This should position the Head of the pipe in open space at the East side of the site.

The tail should be connected to the open nozzle on the pump.

The pipe must have a Gasket and Flange attached the pump nozzle at the tail. Add a single Elbow (one of
the ELBOW LR ANSI variations such as EL90) to line up the head and tale.

In order to get the pipe to appear between the Head of the Branch and the Elbow, first open the Command
Window from the Display menu.

Select the Pipe Branch (BRAN) in the Design Explorer, and in the Command Window type in SEL HSTU.
This will automatically set the relevant attribute completing the Pipe.

 When a pipe starts with the Head positioned in space and the Connection set to OPEN, as might be the
case with a feed pipe coming from off-site, no Head Tube Specification (HSTUBE) attribute is set by
default. In the example above, the Head Tube Specification attribute was automatically selected by
entering the SEL HSTU command. This must be performed using the Command Line.

www.aveva.com
© Copyright 1974 to Current Year 62
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Create PIPE3 with the Head connected to the open nozzle on the tank. Create the tail in the same way as
the head of PIPE2 using the parameters below.

PIPE3 must start with a Gasket and Flange, and be followed by an Elbow (one of the ELBOW LR ANSI
variations). The Elbow should be aligned with ELBO 2 of PIPE1, with the leave direction set to North.

Next add a Gate Valve (VALVE GATE ANSI with FLANGE WN ANSI), followed by an additional elbow of
the same type as the previous one. Position the Elbow so that the leave direction is set to East, and it is
aligned with the Tail of the Branch. A pipe should now connect the Elbow to the Tail of the Branch.

Next add an 80mm Reducing Tee (80 TEE ANSI) and using the Model Editor position it 200mm from the
Elbow.

The final part of the exercise is to create a second branch in PIPE3. To do this click the Pipe Modification
Form button from the Pipework Toolbar and then click the New Branch button on the Pipe Modification
Form:

This will bring up a blank set of Head and Tail Detail and Head and Tail Connection information.
www.aveva.com
© Copyright 1974 to Current Year 63
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Using the same method as before, set the Head Connection of the branch to be the open end of the Tee,
and set the Tail Detail using the following information:

Place a Gate Valve (VALVE GATE ANSI with FLANGE WN ANSI) after the tee connection, and rotate this
to point North using Model Editor.

Next add an Elbow (same type as used in Branch 1), and align it with the Tail of the Branch. Note that a
pipe has not automatically connected the Elbow to the Tail, because the Pipe Bore (80mm) and the Tail
Bore (100mm) do not match.

Finally add an 80x100mm Concentric Reducer (100 REDU CONC ANSI) and position it 500mm from the
Elbow.

The end result should look like the example below.

www.aveva.com
© Copyright 1974 to Current Year 64
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 6

6 PDMS ISODRAFT

6.1 Introduction to Isodraft

From the Pipes and Branches produced in the Design module, fabrication, erection, system and trim
isometric drawings can be produced. Isodraft, the Isometric Drawing Production module, uses a series of
option files to produce these differing isometrics.

To begin with, the Training project doesn’t have any options files in it to define these Isometric drawings, so
the first task is to copy a few of these files from another project.

First navigate to the C:\AVEVA\Plant\Projects12.1.SP2\Sample\samiso\std directory.

Copy all four files and paste them into the C:\AVEVA\Plant\PDMS12.1.SP2\Project \TRAINING\traiso\std
directory.

6.2 Accessing Isodraft

Before Isometrics would normally be produced, all pipes and/or branches would be checked using a tool
within the Design module called Data Consistency Checker. This ensures that all the components have the
correct references, are correctly aligned and not overlapping.

From the Design module, Isodraft can be accessed selecting Design > Modules > Isodraft… from the Main
Menu.

Once in Isodraft, open the Members List by clicking (shown below) showing the contents of the Design
Database and a graphical window, similar to that in Design.

www.aveva.com
© Copyright 1974 to Current Year 65
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

6.3 Producing an Isometric

Isodraft has a number of options to control the appearance, content and type of isometric.

The four files copied earlier will provide two alternative isometrics, each with an option to produce metric or
imperial data output, thus giving four options files altogether. An Isodraft Administrator can create/modify
options files to set the appearance and content of the isometric.

Before accessing one of these options files, using the Isodraft Members form, navigate to PIPE1 in the
/TRAINING-SITE.

From the Main Menu on the graphical window, select Isometrics > Standard…

The Standard Isometric form will be displayed, as shown below:

At the top of the form, the current element (CE) is

shown. If the current element needs to be changed,
then the new pipe should be selected in the Isodraft
Members form, and then the CE button must be
pressed.

In the Isodraft Members form, select PIPE_1. Then in

the Standard Isometrics form, click the CE button.

The Options pull-down defines where the Options files

are located. Select Project if it is not already active, to
display the available files which were copied earlier in
the exercise in the middle of the form.

In the Standard Iso Options section of the form, select

the BASIC.MET options file.

The Detail pull-down allows either the Current

Element, or a Detail List to be defined (this is used for
Bolt Reports).

The Produce pull-down gives options to either create

Isometrics, Transfer files (to interface with other
systems), Batch Macro (to generate a large quantity of
Isometrics), or a Bolt Report (generates a report of
bolts for pipes and branches in the Detail List).

When all the options have been chosen, click Apply to generate an Isometric in a new graphical viewing
area.

www.aveva.com
© Copyright 1974 to Current Year 66
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

An example of an Isometric using PIPE 3 is shown below.

Experiment with creating some Isometrics from the three pipes in the /TRAINING-SITE.

In the event of a pipe that still has data inconsistencies, the Isometric will not be produced and a text output
detailing the error will be displayed.

www.aveva.com
© Copyright 1974 to Current Year 67
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 68
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 7

7 PDMS Draft

7.1 Introduction to Draft

Draft is the drawing production module of PDMS. It allows engineering drawings to be generated, fully
annotated, directly from data in the PDMS Design model. Drawings can be easily updated to reflect changes
in the Design model.

Within Draft there are three applications that are used for specific functions associated with the production of
drawings. These applications are called:

 General
 Auto Drawing Production
 AutoDRAFT

7.1.1 General

The Draft Graphical User Interface has been designed to allow industry standard engineering drawings to be
generated and retrieved quickly and efficiently. Dimensioning and other annotations can then be added. It is
not necessary to perform any calculations or input any data, as all annotation information comes directly
from the Design model.

7.1.2 Auto Drawing Production

The Automatic Drawing Production application enables annotated drawings to be produced automatically.
Rules can be set that determine how the annotation is produced. The drawings can then be edited, if
necessary, using the normal drawing editing options in Draft.

The application contains three separate utilities, which are used for different disciplines. The utilities are:

 General ADP
 Steelwork Detailing
 Hangers and Supports ADP

7.1.3 AutoDRAFT

This application is the Draft two-way interface to AutoCAD.

Note: PDMS drawings created using Draft have a unique format and cannot be read using other software
packages. However, there is a facility to export drawings under a different format.

It is possible to transfer a Draft drawing directly across to AutoCAD, where some users prefer to perform
final annotation before drawing issue. The transferred drawing maintains the exact style and representation
as set from Draft. This is done by using an option called DXF CE under the Utilities menu.

The user can develop symbol libraries and drawing frames in AutoCAD and import these directly for use in
Draft prior to returning the drawing from AutoCAD to Draft.

www.aveva.com
© Copyright 1974 to Current Year 69
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

7.2 Creating a Draft Drawing

Like all other areas of PDMS, Draft also has a strict hierarchy that needs to be followed.

The first element to create is a Department. This must sit under the World level, and is created from the
Create > Department… option in the Main Menu.

Enter the name as /Training_Library and click

OK.

Once the OK button has been clicked, the Department Information form is displayed. This form shows the
name of the DEPT and provides an opportunity to automatically create the next element, a Registry, and/or
set up attributes of the Department.

Click the Attributes button to load the Department Attributes form.

Change the paper size to A1 on the pull down menu. Under the Backing Sheet heading, select the
Reference radio button, and then select /DRA/MAS/BACKS/MET/A1 from the pull down menu. Any
drawing created in this Department will now use this Backing Sheet as the default unless otherwise
specified.

Click Apply and then Dismiss to return to the Department Information form, and then click OK to create
the Department.

www.aveva.com
© Copyright 1974 to Current Year 70
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

If the Create Registry box was ticked on the Department Information form, then the Create REGI form will
be displayed. Alternatively, this form can be accessed from Create > Registry… in the Main Menu.

Enter the name as /Training_Registry and click

OK.

Once the OK button has been clicked, the Registry Information form is displayed. This form shows the
name of the REGI and provides an opportunity to automatically create the next element, a Drawing, and/or
set up attributes of the Registry. As the attributes have already been defined for the Department, it is not
necessary to do the same for the Registry.

Leave the Create Drawing box ticked.

Templates will not be used in this project, so select the

Explicitly radio button and then click OK to create the
Drawing.

The Create DRWG form will then be displayed. Leave the name as /DR1 and click OK.

The Drawing Definitions form will then be displayed, allowing additional information such as a drawing title
to be entered.

Enter the Title as Training Drawing 1, click Apply and

then Dismiss.

The drawing has now been created and setup.

www.aveva.com
© Copyright 1974 to Current Year 71
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

7.3 Creating a Draft Sheet

Now that the drawing has been created, a sheet must also be created.

Select Create > Sheet > Explicitly… from the Main Menu, and the Create SHEE form will appear.

Leave the name as DR1/S1 and click OK.

The Sheet Definition form will then be displayed.

Enter the Title as Site Overview and

click Apply then Dismiss.

7.4 Creating a Draft View

Views are essentially windows within a Sheet in which the model data can be displayed. There are a number
of different ways in which Views can be created and setup.

Limits-defined – this allows views to be created by specifying corner

points on the sheet

User defined – this allows views to be created and the size and
position to be setup using cursor clicks in the sheet area

Detail – this allows detailed views to be created by selecting an

element and then setting up the size and position

Predefined Frame – this gives a range of predefined view setups,

where the view positions are fixed, and the view directions can be
specified

www.aveva.com
© Copyright 1974 to Current Year 72
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

From the Main Menu, select Create > View > Predefined Frame… to load the View Configuration form.

The various view layouts are represented by the dotted lines

in the preview pane.

Selecting a setup activates the pull down menus that relate to

that configuration, from where View Directions can be defined.

Select the third radio button from the top, and set the upper
left view to North, the lower left view to Down and the right
view to Iso 3.

Adjust the View Spacing to 15mm. This alters the gap

between the frames when they are created.

Click OK to create the three Views.

The main display window should now look something like this:

www.aveva.com
© Copyright 1974 to Current Year 73
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

7.4.1 Populating Views

As in Design, a Drawlist must be populated, determining which items are displayed within the View.

First select one of the Views, either by clicking on the frame in the main display, or by selecting it from the
Draft Explorer. From the Main Menu select Modify > View > User-defined… to load the User-Defined
View form.

From the menu at the top, select Graphics > Drawlist… to load the Drawlist Management form.

In the Reference List Members

section, select TRAINING-SITE
and then click the Add button at
the bottom.

This will move the whole of the

Training Site over to the Drawlist
Members list.

Click Dismiss to close the form

and return to the User-Defined
View form.

www.aveva.com
© Copyright 1974 to Current Year 74
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

In the General tab of the User-Defined View form, set the View Type to Global Hidden Line.

In the Scale tab, first click the Auto Scale button. This will calculate the largest scale that will allow the
entire Drawlist to fit within the View. Click the Nearest button to set the scale to the closest standardised
scale.

Finally, under the Update Design on Apply? heading, select the Update Design option, and then click the
Apply button.

A view of the site should now have appeared in that View window.

www.aveva.com
© Copyright 1974 to Current Year 75
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Exercise 4 PDMS Draft – Create a Drawing

Set up the remaining two views in the same manner as the first. If possible, keep the Scale of all views the
same.

Next create a second sheet with the Title set as Pump. Use the Predefined Frames option to create a single
view, facing west. Modify the View so that only the Pump appears in Wireline Hidden Line mode.

www.aveva.com
© Copyright 1974 to Current Year 76
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

www.aveva.com
© Copyright 1974 to Current Year 77
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

7.5 Annotating a Drawing

The two main types of annotation are dimensioning and labelling.

In the Draft Explorer, under the VIEW element are a series of LAYE (Layer) elements where Labels and
Dimensions can be stored.

7.5.1 Dimensioning

Select the _Dims layer under DR1/S1/V1.

From the Main Menu select Create > Dimension > Dimension Linear… to load the Create Linear
Dimension form.

In this case the settings can be left as they are, so click OK to load the Linear/Angular Dimensions form.

The tick box with the loop icon to the right of the Create
button enables chains of dimension points to be
created. Tick this box.

The list on the left selects how the points are selected.

www.aveva.com
© Copyright 1974 to Current Year 78
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Select Before from the list, and then click Create. A prompt will appear in the Status Area asking for an item
to be selected for dimensioning.

First click on the box that forms the base, and then select the Tank element. A dimension should appear
giving the distance from the left hand side of the base to the left hand side of the tank. Further selections will
add additional dimensions using the Before criteria.

Press the Escape (Esc) key to exit the dimension creation.

Close the Linear/Angular Dimension form and create a new dimension in exactly the same way as before,
but this time select After from the list.

The result should look something like the example below.

7.5.2 Labelling

As with Dimensioning, the correct layer must first be selected. Select the _Labs layer under DR1/S1/V3 in
the Draft Explorer and then select Create > Label > General/Symbolic… from the Main Menu to load the
Labels form (seen on the next page). For this exercise, General Labels will be created.

Selecting the Create NEW button brings up a prompt to identify an element. Select the Tank element from
one of the views. More than one item can be selected to be labelled at the same time. Press the Escape
(Esc) key to end the selection

Selecting one of the options under the Attributes pull down menu will bring up the appropriate modification
form.

www.aveva.com
© Copyright 1974 to Current Year 79
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Select text Contents… from the pull down to load the Modify Text form.

The Intelligent Texts… button provides a list of possible

references for text.

Either by typing or using the Intelligent Texts button,

change the text field to #OWNE(C2:) and then click
Apply.

A label with the text TANK should now be visible on the

Tank element in the Iso 3 view.

Selecting one of the options from the Position pull down

allows the user to move the label.

The Text Setting… option under Attributes has the

ability to increase the text size if necessary.

www.aveva.com
© Copyright 1974 to Current Year 80
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Exercise 5 PDMS Draft – Labelling

Label the Pump and steel sections on the Site Overview drawing. For the steel sections use the SPRE
attribute instead of NAME to display the section specification.

Resize and/or reposition the labels so that the drawing is clear and neat. This can be done by using the
Model Editor.

Dimension the Pump drawing to show some of the main dimensions of the Pump.

www.aveva.com
© Copyright 1974 to Current Year 81
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 CHAPTER 8

8 Exporting to AVEVA Review

8.1 Exporting Model Data

To Export model data for Review, first switch to the Design module.

Once in the Design module, select Utilities > Export > Create… from the Main Menu.

Enter tra_site.rvm into the Output File box, and then select the binary radio button.

Select the TRAINING-SITE from the Design Explorer and click the Add button below the Include list.

Click the Export button to create the Review file. By default this will be created in the
C:\AVEVA\plant\Data12.1.1\pdmsuser directory.

Open Review 12.1.1.1 if installed and select File> Open then navigate to the newly created .rvm file.

Upon opening the new file in Review, a blank ‘observer’ view will be displayed. An explorer window will also
be displayed by default which contains a hierarchy similar to that in PDMS (if the explorer is not displayed,
navigate to View > Explorer). Open the hierarchy select the training site and drag this onto the observer
view. As no materials have been selected for the components in the model, they will be black in appearance.

www.aveva.com
© Copyright 1974 to Current Year 82
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Open the Materials Definition window using View >

Materials Definition and click a predefined material. The
material will be displayed in the Material Definition fold up
menu.

Click the Material Painter link and then select one or

several components on the training model within the
observer window to give the components a material. The
material definition box can also be used to change the colour
of the predefined material.

The Material Properties fold up menu allows attributes such

as roughness and transparency of the material to be
adjusted using sliders.

When the material properties or definition are changed, all

components which mate use of that material can be updated
by clicking Apply Changes.

The backdrop may be changed as per the screenshot on the

following page by clicking Edit > Image Quality… and then
changing Camera Backdrop to Sky and Land using the
drop down menu.

The model lighting and shadows can be adjusted using the

light definition form which is accessed from View >
Lighting Control or clicking the view lighting control icon:

The light sources may be switched on and off by clicking the

light bulb icon:

The user can control the colour and intensity of the ambient
light source. Sources 1-7 allow the user to select from
various types of lighting, control their intensity, colour, type
of shadowing and position.

www.aveva.com
© Copyright 1974 to Current Year 83
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Above is simple example of the model from the Training project with some textures, scenery and shadows
added.

Navigation within Review is different to PDMS Design navigation; these are the controls when the user is in

walkthrough/flythrough mode:

Use the left mouse button to select components. Pressing and holding down
the left mouse button causes the name and model coordinates of the
element under the pointer to appear in the status line.

www.aveva.com
© Copyright 1974 to Current Year 84
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Click the central wheel to centre the view on that point.

Scrolling the central wheel moves the observer forward and backwards.

Click and drag the central wheel in order to rotate the view about the
observer.

Click and drag the right mouse button in order to pan across the model.

7 8 9
In In

The number pad may be used to navigate, acting in a similar way to using
4 5 6
the central wheel of the mouse. The arrow keys rotate about the observer;
Pg Up and Pg Dn move the observer forward or backwards.
1 2 3
Out Out 7 8 9
In In

Numeric Keypad keys 2, 4, 6, 8 pan in 4 5 6

directions shown by half view width.

The arrow keys pan about the model.
1 2 3
Keys 7 and 9 zoom in Out Out

Keys 1 and 3 zoom out

Arrow keys pan in Numeric Keypad keys 2, 4, 6, 8 pan in
directions shown directions shown by half view width.
Keys 7 and 9 zoom in
Keys 1 and 3 zoom out

www.aveva.com
© Copyright 1974 to Current Year 85
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 APPENDIX A

APPENDIX A – AVEVA Equipment Primitives

Please note that some P-points have been removed from selected images to maintain display clarity.

Box (BOX)

Specific geometric attributes:

Xlength Length parallel to X axis
Ylength Length parallel to Y axis
Zlength Length parallel to Z axis

Cylinder (CYLI)

Specific geometric attributes:

Diameter Diameter of cylinder
Height Length parallel to Z axis

www.aveva.com
© Copyright 1974 to Current Year 86
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Cone (CONE)

Specific geometric attributes:

Dtop Diameter at top of cone
Dbottom Diameter at bottom of cone
Height Length parallel to Z axis

Snout (SNOU)

Specific geometric attributes:

Dtop Diameter at top of snout
Dbottom Diameter at bottom of snout
Xoffset Offset of centre of top from centre of bottom on X axis
Yoffest Offset of centre of top from centre of bottom on Y axis
Height Length parallel to Z axis
 Only an Xoffset is show in this example, however, both Yoffset and Xoffset may be set.
www.aveva.com
© Copyright 1974 to Current Year 87
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Pyramid (PYRA)

Specific geometric attributes:

Xbottom Length of bottom of pyramid parallel to X axis
Ybottom Length of bottom of pyramid parallel to Y axis
Xtop Length of top of pyramid parallel to X axis
Ytop Length of top of pyramid parallel to Y axis
Height Length parallel to Z axis
Xoffset Offset of centre of top from centre of bottom on X axis
Yoffset Offset of centre of top from centre of bottom on Y axis
 Only a Yoffset is show in this example, however, both Yoffset and Xoffset may be set.

Circular Torus (CTOR)

Specific geometric attributes:

Rinside Inside radius in XY plane
Routside Outside radius in XY plane
Angle Subtended angle (maximum 180°)

www.aveva.com
© Copyright 1974 to Current Year 88
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Rectangular Torus (RTOR)

Specific geometric attributes:

Rinside Inside radius in XY plane
Routside Outside radius in XY plane
Height Length parallel to Z axis
Angle Subtended angle (maximum 180°)

Dish (DISH)

Specific geometric attributes:

Diameter Diameter of dish in XY plane.
Height Height of dish parallel to Z axis
Radius Knuckle radius

 If the knuckle radius is 0 then the dish is represented as a segment of a sphere. If the knuckle radius
is greater than 0 then the dish is represented as a partial ellipsoid, generally used to represent a
torispherical end to a vessel.

www.aveva.com
© Copyright 1974 to Current Year 89
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Sloped Cylinder (SLCY)

Specific geometric attributes:

Diameter Diameter of sloped cylinder
Height Length in Z axis from bottom centre to top centre
Xtshear Inclination of top of cylinder in the XZ axis (in degrees)
Ytshear Inclination of top of cylinder in the YZ axis (in degrees)
Xbshear Inclination of bottom of cylinder in the XZ axis (in degrees)
Ybshear Inclination of top of cylinder in the YZ axis (in degrees)

 Only an Xtshear and Ybshear are shown in this example, however, Xtshear, Ytshear, Xbshear and
Ybshear may be set in any combination to obtain the required results. The values for these attributes
may be +ve or –ve.

Extrusion (EXTR)

Specific geometric attributes:

Height Height of extrusion in Z axis

www.aveva.com
© Copyright 1974 to Current Year 90
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Solid of Revolution (REVO)

Specific geometric attributes:

Angle Rotation angle around X axis (selected rotation line)

 A solid of revolution is a 2D shape, defined by a series of vertices at each change in direction, rotated
through a specified angle around a specified rotation axis. The primitive consists of three element
types, i.e. REVO, LOOP and VERTs.

www.aveva.com
© Copyright 1974 to Current Year 91
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 AVEVA Plant (12.1)
PDMS Hands-On Overview TM-1000

Nozzle (NOZZ)

Although a nozzle is classed as a primitive, it is unlike the other primitives in that its geometry is determined
in Paragon as part of a catalogue component. Nozzles of different types and geometry may be constructed
in Paragon to suit the requirements of the Piping Specification.

The specific nozzle type is referenced from Paragon using the Spref (Specification Reference) attribute.

Specific geometric attributes:

Height Height between nozzle face and end, i.e. from P1 to P2.

Special Attributes:
RINSIDE Inside radius
ROUTSIDE Outside radius
HEIGHT Height between top and bottom surfaces
ANGLE Subtended angle (not allowed to be greater than 180 degrees)

The origin of the rectangular torus is at the centre of the arcs of radii RINSIDE and ROUTSIDE, and is
defined in the X-Y plane

www.aveva.com
© Copyright 1974 to Current Year 92
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.