Hướng dẫn thiết kế AVEVA PDMS

Phần mềm thiết kế 3D PDMS – Plant Design Management System Các module chính của pdms : Design( Thiết kế ) 90% designer sử dụng trong quá trình thiết kế Equipment ( Thiết kế thiết bị ) Pipework ( Thiết kế đường ống ) Structure – ASL ( Thiết kế kết cấu ) HVAC ( Thiết kế thông gió ) Cable tray ( Máng cáp điện ) Draft( Gia công bản vẽ 2D ) Plotplan ( Bản vẽ bố trí mặt bằng thiết bị) GA ( Bản vẽ bố trí đường ống,bản vẽ lắp đặt ) Isodraft Xuất bản vẽ isometric ( bản vẽ chế tạo ) Ngoài ra một số module chính sử dụng cho người admin quản lý cao cấp phần mềm pdms là : Paragon, Specon, Admin …

Plant Design Management System

Training

CONTENTS

Introduction to PDMS 3

ADMIN 18

Equipment Application 33

Piping Application 43

Structural Application 56

Cable Trays 75

HVAC Designer 80

Isodraft 130

Draft 138

APPENDIX A 158

PDMS TRAINING

ANEWA

Introduction to PDMS

Introduction

PDMS is part of AVEVA’s VANTAGE suite of Plant Design products

What does PDMS offer?

1 Full size, 3-D modeling system

2 Design based on specification driven catalogues

3 Concurrent user accesses within a single project

4 Multi-discipline environment

5 On-line 3D Clash detection

6 Design consistency check

7 Automated Isometrics

8 Report generation

9 Drawing extraction & management

10 DXF and IGES drawing exchange

11 Programmable Macro Language

12 User Definable attributes

13 Interfaces to third party software

Modules of PDMS (Sorted Alphabetically)

PDMS is split into a number of modules which are used at different stages in the

plant design process

ADMIN : Used by Project coordinator or administrator to control /

monitor a Project in terms of areas, teams, users, modules and database

DESIGN : 3-D modeling module using which structures, Equipment,

Pipe work, Cable trays, HVAC components, can be modeled It also has a Pipe spooling applications and Hangers & Supports Application

MONITOR : This is an entry-level module, which monitors the entire

project, gives proper notification to users about their access rights as defined by the administrator As soon

as a user logs into PDMS, he enters MONITOR module This module controls the entry and exit of users from PDMS

PARAGON : Used to create or modify Catalogues and Specifications

for piping elements, structural elements, nozzles and hangers & supports Provides an user interface for creation of specifications also

PROPCON : Used to create or modify Properties DB, wherein the

properties used for stress analysis / any other engineering application can be stored These properties can be linked to the design elements using specifications

SPECON : Used to create specifications, but does not provide an

user interface

SPOOLER : This is the Pipe work Spooling module, it allow splitting

the pipe work design into logical sections (Spools) ready for fabrication

The PDMS databases

The overall purpose of PDMS is the controlled creation of a complete three–

dimensional process plant design model using computer–simulation techniques All information which exists about a PDMS design project, whether administrative

or technical, is stored in a series of hierarchical databases Use of the various

PDMS modules allows you to create, modify and extract information from these databases

The Database Types

The Project

A PDMS Project consists of the complete collection of information which relates to

a single design project This is identified by a three‐character name, allocated by the Project Administrator when the project is first initiated This name is used to identify the project to the system whenever you wish to work in the project using PDMS This allows access rights and use of system resources to be monitored and controlled

There are 10 different types of database which can go to make up a complete Project:

Design and Drawing Databases:

DESIGN database : It contains all information regarding the 3-D model being

developed This DB will have references to all other DB’s

to access information

PADD database : Stands for Production of Annotated and Dimensioned

Drawings

ISOD database : It contains all information of spool drawings produced by

SPOOLER It Supports Iso-draft Module

Reference Database:

Administration Databases:

Each PDMS module requires access to one or more specific database types, and entry to the module may be prevented if appropriate databases do not exist or if

you don’t have the appropriate access rights New databases can only be

created by the Project Administrator

CATALOGUE database :  Dimensional standards for nozzles, piping

components and structural profiles/fitting etc.,

 Details of connection types

 Bolting Data

 Specifications

DICTIONARY database :  It contains Definitions for User Defined Attributes

PROPERTIES database : 1 It contains all Material property data normally used for

stress analysis

SYSTEM database :  It contains all Information about modules, databases,

users, teams etc

COMMS database :  It contains all information on current users - for the

STATUS and SYSTAT commands

MISC database : 2 It contains all data for user messages and

inter-db macros

TRANSACTION database : 3 To enable the System Administrator to monitor the

progress of Global commands, transaction messages are generated in the database each time the progress

of the command changes

The relationships between databases

In order that each user can see the required design components modeled 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

Multiple databases (MDBs)

When a PDMS project is set up by the Project Administrator, groups of databases are defined for particular purposes For example, the members of any design team will need access to those databases containing the parts of the design data for which that team is responsible plus some of the Catalogue and Drawing databases Such a group of databases is known as a Multiple Database or MDB There would usually be several MDBs for a project, each defining specific groups

of databases, for users with different tasks to perform

Design Database Hierarchy

The database is hierarchical, a tree like structure, as illustrated below

The PDMS Design Database Hierarchy

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

Now, let us use the computer,

Assuming PDMS has been correctly installed on your workstation, start PDMS by

selecting (for example) Start>Programs>AVEVA>VANTAGE PDMS 11.6>Run PDMS; two command windows and a ‘splash screen’ will appear

briefly The VANTAGE PDMS Login form that appears requires you to specify a number of details at the outset of your session

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

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

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

MDB is the multiple databases within the given Project that you wish to use Type

in, or select from the pull‐down list, pressing Enter in each case Make sure that you leave the Read Only box unchecked if you wish to modify the database as you

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

Use Load from to specify which setup files to load at startup You can choose either the application default settings (Load from Macro Files) or a customized setup saved during an earlier session (Load from Binary Files)

Click on the button to enter the PDMS module that you wish to use When PDMS has loaded, your screen looks like this:

As labeled above, the display comprises the following:

Title Bar

This shows the current PDMS module, and its sub-application if applicable

Main Menu Bar

This is the area you use to make menu selections

Main Tool Bar

This has a number of icon buttons and drop-down lists that offer shortcuts to a selection common PDMS operations and standard settings

Design Explorer This shows your current position in the PDMS database

hierarchy To move to a different point in the database, you click on the appropriate item in the list

Members List

As with the Design Explorer, the Members List displays the database elements

in the current MDB

There are a number of ways to navigate from one item to another The and arrows

at the top of the Members List allow navigation up and down the list at the level of the current element For example, if positioned at an EQUI element, selecting would move to the next EQUI element in the list Selecting would move back to the previous EQUI element

The Goto menu at the top of the form can also be used First select this menu, then select the Owner option, this will navigate to the owner of the CE

owner, i.e a ZONE If the current element were a nozzle (NOZZ) then Goto>Reference would allow navigation inside the catalogue database via the NOZZ’s Catref attribute

Command Window

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

To give a command, click in the Command> text entry box, type in the command,

and press Enter The scrollable list shows the command(s) entered and any

resulting output from PDMS (including error messages)

Command editing aids are available:

• Clicking on a line in the scrollable list area copies that line to the Command > box

• Command syntax in the Command> box can be edited using the Delete and

Backspace keys in the normal way

• Highlighting some or all of the text in the Command> box and pressing the right

mouse button gives useful Windows editing commands (Cut, Copy, Paste, Delete, Undo)

3D Graphical View This is the window in which you display the design model

graphically as you build it A pop-up menu (which you access with the right-hand mouse button) enables you to control how the model is represented This window also has its own tool bar

Status Bar This displays information about the current status of your operations

You can reposition or minimize these windows at any time using standard window management facilities

Draw list

To view the Draw List, select the option Display>Draw List from the main menu

bar You specify which elements of your design you wish to display, by adding them to or removing them from the draw list

The sample database associated with this exercise represents the whole of a simple building

Select Display>Draw List from the main menu bar You should see the Draw List

come up in a separate floating window If you wish, you can dock this window

Make sure that in the Design Explorer you have expanded any element to display

the Graphics below it

Pick the Selected element from the design element hierarchy, right-click the

mouse and select 3D View>Add This adds selected elements to the Draw List as well as to Graphical View window

Alternatively, you can click the right or left mouse-button and drag-and-drop the

element into the 3D View

One of the Example Shown Below to explain the draw list

On the Draw List, click on the HVACFLOOR element You can now use the

controls in the Draw List to set the color from the popup palette Make the floor Black (See the online help for the Design Explorer for details of how to do this) Now pick the HVACWALLS Structure from the design element hierarchy and add it

to the draw list in the same way Set the color of the walls to aquamarine

Use the same method to add:

• HVACCOLS (columns) in green

• HVACBEAMS in blue

Do not add HVACROOF at this stage

Your building now looks like this:

Observe the effect of selecting different view directions from the Look and

Isometric menu options provided by the 3D View shortcut menu Revert to ISO>3

when you have finished

Manipulating the displayed view

You can manipulate the displayed model view in a number of ways The three view manipulation modes are:

• Rotate the view

• Pan the view across the display area

• Zoom in or out to magnify or reduce the view

The current manipulation mode is shown in the status line at the bottom of the 3D View window, and is currently set to Rotate, as shown in the previous illustration

To change the view manipulation mode, look at the Middle Button Drag options

on the 3D View shortcut menu By pressing and holding down the middle mouse button with the pointer within the 3D View, the view can manipulated in the selected way simply by moving the mouse The options of interest are Zoom Rectangle, Zoom In/Out, Pan and Rotate

Alternatively, you can change the manipulation mode by pressing one of the function keys, or by using the View Manipulation tool bar buttons, thus:

F2 or selects Zoom mode

F3 or selects Pan Mode

F5 or selects Rotate mode

(Try these selection options and observe the effect on the Middle Button Drag

shortcut menu; a tick appears against the selected option)

You can also choose the view manipulation mode from the options on the

View>Middle Button>Drag menu

Perform the operations while holding down the Ctrl key Note that the

Word Fast appears in the status line and that the rate of action is increased

Perform the operations while holding down first the Control key (to increase the action speed) and then the Shift key (to decrease the action speed)

In the 3D View tool bar, click on the Limits CE button, this adjusts the scale of the

view automatically such that it corresponds to a volume the right size to hold the chosen element(s);

To set an isometric view direction, position the cursor in the 3D View window and hold down the right-hand mouse button to display the pop-up menu Select

Isometric>Iso 3 from it

If the graphical view background colour is not already black, select

View>Settings>Black Background from the 3D View menu

It is good practice regularly to save your work This avoids the need to start all over again in the event of loss of work due to an unforeseen interruption, such as

Update the database to store changes to the design model so far by clicking on, or

selecting Design>Save Work

You should also save your current screen layout and display settings, so that next time you use the application you can easily pick up your design as it stands Do

this by selecting Display>Save>Forms & Display

You can now leave PDMS and return to the operating system Do this by selecting

Design>Exit

Ordinarily, if you had made any changes since your last Save Work operation, an

alert form would ask whether you want to save those changes; this time, you are just asked to confirm that you want to leave PDMS

Click OK

PDMS TRAINING

ANEWA

ADMIN

Introduction

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

of the PDMS Project into sections which:

• Are relevant to the needs of project reporting and control

• Form reasonable design subdivisions with sensible match lines and design

content

• Enable enough designers to work in parallel with simultaneous access to carry

out their design tasks

In much the same way as in a design office (with its section leader, draughts people, etc.), PDMS has Teams, the members of which are called Users These Teams can consist of any number of Users and can be organised by discipline or physical work areas

The main features are:

• Access Control (Teams and Users)

• Databases

• Multiple Databases (MDBs)

• Database management functionality

Admin includes a database integrity checking utility, used to check for inconsistencies in the contents of the databases and to derive statistical information about the use of the database storage capacity

Admin also allows the System Administrator to reconfigure a project This may be necessary:

• to compact databases at intervals, freeing disk space

• to upgrade PDMS projects when the database structure changes

• to compare the contents of two similar databases; for example, to create a modification record

To Create A New Project

A PDMS Project must be identified by a three-letter code The following steps

given below illustrate how to create the Project, say by name [XYZ] Before

proceeding to create the Project we shall make ourselves clear with the structure

of the Project Directory

XYZ000 The Project Directory The files under XYZ000 are:

XYZ001-XYZnnn Database files which contain the actual model data,

nnn has a maximum of 8188

XYZPIC The directory which stores picture files produced by DRAFT

XYZMAC The directory which stores inter-database connection macros

XYZISO The directory which stores files needed by ISODRAFT

XYZISO Contains four more sub-directories LIS, STD, SYS and UND

LIS To hold detail lists

STD To hold option files for standard isometrics

SYS To hold option files for system isometrics

UND To hold underlay files

DFLTS The PDMS defaults directory

CREATION OF PROJECT DIRECTORIES AND SUB-DIRECTORIES

We have to create the project directories 000, MAC, PIC & ISO which is preceded

by the three letters project name In this example, we have to create the

directories XYZ000, XYZMAC, XYZPIC & XYZISO, then under XYZISO we have

to create four more sub-directories LIS, SYS, UND & STD It is always

recommended to store all the projects under one directory say, D:\PROJECTS

D:\PROJECTS>MD XYZ

D:\PROJECTS>CD XYZ

D:\PROJECTS\XYZ>MD XYZ000 XYZPIC XYZMAC XYZISO

Above thing is for Windows NT Operating System

Above thing is for UNIX Operating System

After the Project Directory structure has been created change the access rights for the working directories to allow all PDMS Project users Read/Write access:

On Windows NT Operating System select each directory in turn (XYZ000, XYZPIC, XYZMAC and XYZISO) in Window NT Explorer For each one click the right mouse button and select Properties Select the security tab and check the

permissions are set correctly

On Unix Operating System the following procedure has to be

Performed

chmod ug+rw XYZ000

chmod ug+rw XYZPIC

chmod ug+rw XYZMAC

chmod ug+rw XYZISO

Set the Environment Variables for the Project

The system recognizes the projects available by referring to a set of environment variables These have to be set before proceeding any further Normally, we have

the file EVARS.BAT or cshrc.pdms in the home directory of the user in which

these variables are set

For Example on Windows NT Operating System:

D:\ AVEVA\Pdms11.6> EVARS.BAT EDIT

Add the following lines in the EVARS.BAT file

SET XYZ000=D: \PROJECTS\XYZ\XYZ000

SET XYZISO=D: \PROJECTS\XYZ\XYZISO

SET XYZMAC=D: \PROJECTS\XYZ\XYZMAC

SET XYZPIC=D: \PROJECTS\XYZ\XYZPIC

On Windows NT Operating System select Start > Settings > Control Panel > System, and select the ENVIRONMENT tab

Set the Variable name as XYZ000 and the value as D:\PROJECTS\XYZ\XYZ000 and then click on the SET button and similarly complete the procedure for the other variables XYZISO, XYZMAC and XYZPIC Then click on the APPLY button

and click OK Now the PDMS environment variables or set

Several macros and utilities are provided in the PDMSEXE directory i.e.,

D:\AVEVA\PDMS11.6 SP3 or wherever the directory PDMS11.6 SP3 is located

When PDMS is installed, a shortcut, Make PDMS Project, is created under the Start menu Make sure that the Project Directory Structure has been created and the Environment Variables are set as described above, and then proceed as follows:

Click on the Make PDMS Project shortcut This starts up the PDMS Project

Creator utility, which runs the file make.bat

Enter the Project name (the three-letter project code), here in this case it is XYZ

You will see an Asterisk * command prompt

Run the utility makemac.mac by typing:

$M /%PDMSEXE%/MAKEMAC.MAC

You will see the messages of the form:

Creating System Virgin Db

For each type of database, and finally a message:

Creating module definitions referencing %PDMSEXE%

Then type:

FINISH

to exit from the PDMS Project Creator

You can now enter PDMS by clicking on the start PDMS shortcut, and selecting

your new Project

A display obtained from the PDMS Project Creator window while actually creating

a new Project is shown below The display was obtained when the above

described procedure was followed Here the Project created is by the name XYZ SAMDSM =D:\AVEVA\pdms11.6 SP3\projectsampic

COMPREP =D:\AVEVA\pdms11.6 SP3\pdmsuser

OUTUFD =D:\AVEVA\pdms11.6 SP3\pdmsuser

This version of PDMS was issued to ANEWA ENGG PVT Ltd

and will only operate on hardware specified to AVEVA

PDMS Project Creator Mk11.6.3 (WINDOWS-NT 4.0) (9 Oct 2007 : 00:13) Copyright AVEVA 1974 to 2006

Issued to ANEWA ENGG PVT Ltd

Enter project name

XYZ

*$M /%PDMSEXE%/MAKEMAC.MAC

Creating System Virgin Db

Creating Comms Virgin Db

Creating Misc Virgin Db

Creating Design Virgin Db

Creating Catalogue Virgin Db

Creating Isodraft Virgin Db

Creating Properties Virgin Db

Creating Paddle Virgin Db

Creating Dictionary Virgin Db

Creating Comparator Virgin Db

Creating module definitions referencing %PDMSEXE%

*FINISH

Press any key to continue

For Example on UNIX Operating System:

/usr/people/pdmsproj/ is the path where the cshrc.pdms file is located

At the command prompt type jot cshrc.pdms and when the file opens add the

following lines

setenv XYZ000 /usr/sg/projects/XYZ/XYZ000

setenv XYZISO /usr/sg/projects/XYZ/XYZISO

setenv XYZMAC /usr/sg/projects/XYZ/XYZMAC

setenv XYZPIC /usr/sg/projects/XYZ/XYZPIC

Note: Environment Variables must be in UPPERCASE

On Unix Operating System the Project is created by running the makeS macro Several macros and utilities are provided in the PDMSEXE directory to create a

new project

makeS Is all you need to create the Project It calls the other scripts and

utilities as required

make Is a utility called by makeS

makemac.mac Creates the Project and loads the module definitions

automatically Note that MONITOR and ADMIN are already

defined in the supplied product

makmac.mac Sets up module definitions from ADMIN

modmac.mac Sets module definitions; automatically called from

makemac.mac and makmac.mac delmac.mac Deletes all module definitions from the Project

The Project can be created by any one of the two ways described below:

By running the makeS utility supplied in $PDMSEXE

By entering the individual command lines for each step

To create the Project XYZ, enter:

$PDMSEXE/makeS XYZ

makeS automatically does the following:

Checks that you have write access to the directory given by $PDMSWK

Checks that the Sitefile is correct

Checks that the Project does not already exist

Runs the make utility

Creates the virgin databases

Sets up the PDMS module definitions by running the modmac.mac

Sets the font directory

Finally, makeS checks that all the virgin databases are present These are

template files from which the different types of model database will be created

If the Project has to be created using the supplied utilities and macros individually, then enter:

$PDMSEXE/make Run the PDMS make executable

$M/%PDMSEXE%/makemac.mac Define the virgin DBs and

run the PDMS makemac macro

The Project XYZ has now been created To check what it consists of, type ls

$XYZ000 or open Windows NT Explorer and click on XYZ000

The directory should contain a SYSTEM database, a backup SYSTEM database,

a COMMS database, a MISC database and a virgin database, for each database type (SYSTEM, MISC, COMM, DESIGN, CATALOGUE, PADD, ISODRAFT, COMPARATOR, PROPERTIES and DICTIONARY)

To Replicate A Project

The Project > Replicate options can be used to replicate the whole Project which

already exists, including all the data, or just the structure of the Project

The Project Data option copies the Current Project to a new Project Before using

this option make sure that the Project directories and the environment variables are set for the Project being replicated Then enter the new Project Code on the

Replicate Project form

Note: A Project must not be replicated outside PDMS by copying the whole of the

Project directory to another Project directory This is because information about

the Project name is stored inside the DBs themselves

The Project Structure option creates a macro which can be run into PDMS to

replicate the structure of the Current Project No data is copied When this option

is selected, a file browser is displayed so that the pathname for the macro can be given

ADMIN scans the System database and outputs to the file all the commands

necessary to recreate the Project Structure, in the following order:

 Add DBs to MDBs and make them Current if appropriate

The Project XYZ created by using the makemac.mac utility is a Virgin Project Now we have to create and modify the main administration elements: TEAMs, USERs, DBs and MDBs

Start PDMS on the AVEVA PDMS Login form we can see choose the Project by

clicking on the button provided at the right end after the Project box After clicking,

the PDMS Login form and type the password for the user SYSTEM Then click on the Module scrolling list and select Admin module Then click on OK

The AVEVA PDMS Login form disappears and the AVEVA PDMS Admin form

appears This form has already been illustrated in the Project Replication topic above

The main ADMIN menu bar is seen across on the top of the screen The options

on this menu bar provide access to all PDMS Project administration tools The

ADMIN Elements form is also seen, through which the ADMIN elements of

Teams, Users, Databases and MDBs can be created, copied, modified and deleted

The ADMIN Elements form has four states, corresponding to the main ADMIN elements (Team, User, Database and MDB) The element type can be changed

by selecting from the Elements option button The scrolling list on the form will

display all the elements of the given type in the Project, and the Create, Copy,

Modify and Delete buttons will allow creating copy, modifying and deleting elements of the appropriate type

Once the ADMIN elements needed have been decided, the recommended

sequence is as follows:

 Create users

 Create teams and users to them

 Create DBs

 Create MDBs and add databases to them

The Teams and Users can be created in any order If the Teams are created first,

then the Users can be added as they are created using the Create User form

Alternatively the Users can be created first and then added to the Teams using the

Create Team form

Creating Teams

To create a Team, set the Element option button on the ADMIN Elements form to Team, and then press Create The Create Team form will be displayed

To create a Team, enter a Name, and optionally a Description Press Apply, and

the Team will be created

On the left of the form there is a list of the existing Users in the Project If a Users

have already been created, they can be added to the Team by selecting the element in the left hand list, and selecting the right arrow button The User will be added to the Team, and the User’s Name will appear in the right hand list

Note: Users can also be added to Teams on the Create User form

Creating Users

To create a User, set the Element option button on the ADMIN Elements form to User, and then press Create The Create User form will be displayed

Enter a name and password, and set the Security option button to Free if a FREE

user is to be created A Description can also be entered if required

Press Create, and the User will be added to the Membership scrolling list

The User can be added to the existing Team using the User Membership scrolling lists All the Teams in the Project are shown in the Project Teams list The Membership list shows the members of the Team selected in the Project Teams list Add the member being created to a Team by selecting the Team and

pressing the right hand arrow A member can be removed from a Team by

selecting the user in the Membership list and pressing the left hand arrow

Note: Users can also be added to the Teams on the Create Team form

Creating Databases

To create a Database, set the Element option button to the Admin Elements form

to Database, and then press Create The Create Database form will be displayed

The Database name is shown at the top of the form Database names are in the format:

TeamName/DatabaseName where TeamName is the name of the Team which owns a Database, and which

therefore has write access to it If there is no Current Team, the Database name

will be shown as unset/unset If there is a Current Team, the Team Name will be

shown as the first part of the Database Name The Owning Team is selected from the scrollable list

Enter the DatabaseName in the Name text box

Select the Database Type from the option button

Select the Access Mode, if Multiwrite is chosen, then the Claim Mode should be

selected from the next option button

The Area number, DB number and File number are normally set by the System, as shown by the word System entered in the text boxes It may sometimes be necessary to set them manually

The Area number is used if it is needed to store the databases in a different

directory

The DB number is used internally by PDMS to identify the Database When a

Database is copied, the copy keeps the same DB number There cannot be more than one DB with the same DB number in the same MDB

The File number is used in generating the filename of the Database For e.g., A Database in the Project XYZ with file number 12 will be stored in the file named XYZ012

Press Create, and the Database will be created

The attributes of Databases can be modified using a similar form very similar to

the Create form To display the Modify form, select the element to be changed in the Admin Elements form and then either:

Press Modify on the Admin Elements form which will display the Modify form,

or

Select Modify from the Create/Modify option button on the Create form, if it is

displayed, and the mode will change to Modify

The Name, Description, Access Mode and Area Number of a Database can be

changed, whereas the Type, DB Number and File Number cannot be changed Note: If you try to change a Database name to a name that already exists, you will

be prompted to confirm that you want to overwrite the Database

 Copying Databases

 Copied Databases can be used for:

 Copy a template Project

 Merging Projects

 Copying included Databases for archiving

Databases can be copied by selecting Database from the Element option button

on the Admin Elements form, selecting the element you want to copy from the scrolling list, and then pressing the Copy button The Copy Database from will be

displayed

On this form, you can specify the owning team by selecting one from the list of all the teams in the Project You can copy a Name, Description and Area Number Note that you cannot change the Database number of the copied Database This will be the same as the original You cannot have more than one Database with the Same Database number in the same MDB

Note: To avoid the risk of Database corruption, all copying of Databases (i.e., the files inside the Project directory) must be done from The ADMIN module and not

be using operating system utilities or commands

Copied Databases can be changed or deleted

Including and Copying Foreign Databases

Databases can be copied from other Projects They 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 from the second Project set

When creating a Project that is going to share Database from other Projects, there are two important considerations:

 Teams must exist for all Databases that are to be 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: Foreign Databases are marked with * in the database list

To include a Foreign Database, set the Element option gadget on the Admin

 Foreign Projects lists the other Projects available

 Access Project as You must enter a Username and Password for a free user in the Foreign Project

 Foreign DBs list the Databases in the Foreign Project

Select the Databases you require and press Apply You will be prompted to create

the owning Team if it does not already exist in the Current Project You cannot

include a Database which has the same Teamid/DBName as an existing

Database in the Current Project

You can exclude Foreign Databases by pressing the Exclude Db button on the Admin Element Form The Exclude Db form will be displayed

To copy a Foreign Database, Set the Element option gadget on the Admin Elements form to Database, and press the Copy Foreign Db button The Copy Foreign Db form will be displayed

The Copy Foreign Db form is displayed when you press Copy Foreign Db on the Admin Elements form This button is only available when the Element option gadget on the Admin Elements form is set to Database

Foreign Projects Lists the other Projects available

Access Project as You must enter a Username and Password for a Free User in

the Foreign Project

Foreign DBs lists the databases in the foreign project

Target Database name is set as follows: pick the Team which will

Own the Database from the list, and enter the Database name

Press Apply You cannot include a Database which has the same Teamid/DBName as an existing Database in the Current Project

Deleting Databases

Databases can be deleted by selecting the element from the scrolling list on the

Admin Elements form and then pressing Delete

Note: To avoid the risk of Database corruption, all deletion of Databases (i.e the files inside the Project directory) must be done from ADMIN and not by using

operating system utilities or commands

Creating MDBs

Multiple Databases are in short called as MDBs To create an MDB, set the Element option button on the Admin Elements form to MDB, and press Create

The Create Multiple Database form will be displayed

The Create Multiple Database form allows you to give the MDB a Name and Description

The Multiple Database Definition scrolling lists are used to define the Databases

in the MDB, and whether they are current or deferred

An MDB may contain up to 1000 Databases However, only 300 of these (known

as the current Databases) can be accessed at any one time The other

Databases are deferred Databases can be transferred between current and

deferred status at any time, so that a user can replace a current Database by a

non-current one to access a particular part of the design The Project Databases list shows all the Databases in the Project which are not in the MDB The arrow buttons are used to add and remove Databases from the MDB, either as current or deferred, and to change a Database between the current and deferred lists The Insert option button is used to position the Databases in a specified order in the list

of current Databases The order is important

Note: An MDB can only contain one database with a given DBNO Two databases

will have the same DBNO if one has been created as a copy

Modifying MDBs

The attributes of MDBs can be modified using a form very similar to the Create

form To display the Modify form, select the element you want to change in the Admin Elements form and then either:

 Press Modify on the Admin Elements form which will display the Modify

form, or

 Select Modify from the Create/Modify option button on the Create form, if

it is displayed, and the mode will change to Modify

You can change the Name, Description, Access Mode and Area Number of a Database The Type, DB number and File number cannot be changed

PDMS TRAINING

ANEWA

Equipment Application

EQUIPMENT APPLICATION

Equipment items consist of a collection of PDMS primitives, arranged in such a way that they physically model the real life object When we build equipment, we need to decide how we want to model the object, just as we would if we were building a plastic model The only difference in PDMS terms is that we model the object at full size rather than working to a scale

PDMS modeling elements

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

Equipment Application in PDMS has the following primitives

Solid Primitives Negative Primitives

Circular Torus Rectangular Torus

Rectangular Torus Pyramid

Sloped Cylinder

What is a P-point?

P-points are identifiable primitive points in any PDMS primitive A BOX has got seven primitive points (P-points) We can query a lot of information from P-points Any element can be moved, rotated, positioned, connected, measured using P-points

Equipment Modeling Hierarchy

The different levels in the hierarchy are maintained by an Owner-Member relationship An EQUI will have ZONE as its owner, while a CYLI might well be one of the EQUI’s members

The owner is that element which is directly related to the current element at the next level up in the hierarchy, as shown in the diagram below:

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

Creation of Standard Equipment

A SUBEQUIPMENT is an optional element to further sub-divide EQUIPMENT The SUBEQUIPMENT can also own primitive elements

Let us consider a pump given below and try to model it using the Standard

equipment creation menu Select Create>Standard from the main menu From

the equipment creation form select the Pumps sub-classification and select the

Centre-Line Mounted, Vertical nozzles pump

A Pump EQUI element

Fill in the various parameters from the drawing Do not worry about the position of the equipment We will be discussing it later in this session

Origin of Equipment

The equipment will be positioned based on its Origin The origin of the equipment will be as indicated in the standard equipment creation form If we want to know the origin of the equipment

E Navigate to any primitive belonging to the equipment

F Type ‘AXES AT CE’ in the command window

If we want to modify the origin of any equipment, we can do so by selecting

Modify>Equipment Origin>ID P-point from the main menu Please note that if

the origin of the standard equipment is altered, it becomes difficult to modify the equipment later on

Positioning the Equipment

By default, equipment will be positioned with respect to the owner, (i.e a zone) However if we want the equipment to be positioned with respect to any other

PDMS entity we can do so Let us look at the Position>Explicitly AT and

Position>Relatively BY menus

Altering the Orientation of Equipment

Orientation of equipment is also with respect to the Owner Equipment can be

oriented any time as per our choice When we type ‘Q ORI’ at the command

window, we normally get

Orientation Y is N and Z is U

Attributes in PDMS

Every element in a PDMS database has a fixed set of properties known as its attributes Some attributes are common throughout the range of elements while others differ according to the type of element involved For example, a cylinder (CYLI) has Height and Diameter attributes whilst the size of a box (BOX) is determined by Xlength, Ylength and Zlength attributes, as illustrated below:

Cylinder and Box attributes

Let us try this on BOX primitive BOX having attributes

XLEN, YLEN and ZLEN

Let us try to correlate these two The Y direction of the BOX is towards the North

of the Plant and Z direction of the BOX is towards the Upward Direction of the Plant We can always rotate the box along any axis

First let us try it out on the command line If we type in the command 'ORI Y is E

and Z is U’, we will have the Y direction of the BOX towards the East Direction of

the plant and Z direction of the BOX will be towards the Upward Direction still Now, we will try to do the same operation using the menu - which is more user

friendly and in more lay man terms Select Orientate>Rotate from the main menu

Creation of non-standard Equipment:

When you create an element, a set of appropriate attributes are entered into the database The attributes will vary according to the type of element but essentially the process is the same For example, a cylinder has the following attributes:

Attribute Default Value

Name Name if specified or hierarchy description

Lock false ( the element is not locked)

Owner The name of the owning element or its hierarchy

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

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

Level 0 10 (this is representation level setting)

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

Let us model the equipment (STABILIZER REFLUX DRUM 1201) given in the drawings without using the menus The listing of commands is given below This listing does not contain the commands for creating nozzles We will be using the menus to create the nozzles However, we will be positioning the nozzles using the command line only We will see about creating nozzles also without using the menus later

Naming of Nozzles

Normally, the nozzle names should be prefixed by the equipment name for ease of identification We can prefix the name of any element to anything by following these steps:

G Navigate to the element whose name has to become the prefix (Assume the name as /E1101)

H Type ‘SET’ in the command window

I Navigate to any element (preferably a nozzle) to which this name has to

be prefixed Type ‘NAME */A1’ in the command window The name of the nozzle will become ‘/E1101/A1’

Renaming of Nozzles

This is needed, when equipment is renamed The names of the nozzles remain the same with the earlier name still prefixed To overcome such a situation navigate to the equipment, whose name is to be changed (let us say /E1101 to

/E1201) type ‘RENAME ALL /E1101 /E1201’

This command can be used for any such similar situations, not only limiting to the nozzles

Sub-Equipment

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