TM-3542 AVEVA Plant (12.1) Schematic Model Manager (Administration) Rev 3.0

AVEVA Plant
(12.1)
TRAINING GUIDE
AVEVA Engineering
Schematic Model Manager
(Administration)
TM-3542
www.aveva.com
AVEVA Engineering (12.1)
Schematic Model Manager (Administration) TM-3542
www.aveva.com
© Copyright 1974 to current year. 2
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
Revision Log
Date Revision Description of Revision Author Reviewed Approved
31/10/2011 0.1 Issued for Review KI
06/11/2011 0.2 Reviewed KI HU
07/11/2011 1.0 Approved for Training 12.1 KI HU BT
18/11/2011 2.0 Issued with latest copyright KI HU BT
13/01/2012 3.0 Approved for Training 12.1.SP2 KI BT BT
Updates
All headings containing updated or new material will be highlighted.
Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers please report it to the AVEVA
Group Solutions Centre at gsc@aveva.com
This manual provides documentation relating to products to which you may not have access or which may
not be licensed to you. For further information on which products are licensed to you please refer to your
licence conditions.
Visit our website at http://www.aveva.com
Disclaimer
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
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
Printed by AVEVA Solutions on 17 April 2012
© AVEVA Solutions and its subsidiaries 2001 – 2012
AVEVA Solutions Ltd, 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
www.aveva.com
Contents
1 Introduction .............................................................................................................................................. 9
1.1 Aim..................................................................................................................................................... 9
1.2 Objectives ......................................................................................................................................... 9
1.3 Prerequisites .................................................................................................................................... 9
1.4 Course Structure .............................................................................................................................. 9
1.5 Using this guide ............................................................................................................................. 10
2 Administrative Settings ......................................................................................................................... 11
2.1 Environment Setup ........................................................................................................................ 11
2.2 Module Definition Configuration .................................................................................................. 11
2.3 Schematic Database Setup – Worked Example .......................................................................... 12
2.4 Dictionary Database Setup ........................................................................................................... 14
2.5 Multiple Database (MDB) Setup .................................................................................................... 15
2.6 Schematic Model Manager UDA’s Configuration – Worked Example ...................................... 15
Exercise 1 – Administrative Setup ............................................................................................................... 18
3 Schematic Model Manager Project and User Options Configuration .............................................. 19
3.1 Entering AVEVA Schematic Model Manager ............................................................................... 19
3.2 Project Options Setup ................................................................................................................... 21
3.2.1 Element Release Tab ............................................................................................................... 22
3.2.1.1 Updates to Existing Released Elements........................................................ 22
3.2.1.2 Updates to Existing not Released Elements ...................................................... 23
3.2.1.3 Setting Release Status for New Elements – Worked Example .......................... 23
3.2.1.4 Active Release Comment Dialogue Form .......................................................... 24
3.2.2 General Tab ............................................................................................................................. 24
3.2.2.1 Copy options settings from another Project ....................................................... 25
3.2.2.2 Exporting Schematic Model Manager Options folder ......................................... 26
3.2.2.3 Importing Schematic Model Manager Options File ............................................ 27
3.2.2.4 Restore Default Options Folder ......................................................................... 28
3.2.3 Import Configuration Tab ......................................................................................................... 28
3.2.3.1 Changing Default Import Destination Groups – Worked Example...................... 29
3.2.3.2 Graphics Settings .............................................................................................. 31
3.3 User Options Setup........................................................................................................................ 32
3.3.1 Data Export Default Location Setup – Worked Example ......................................................... 32
3.3.2 Data Import Default Location Setup – Worked Example ......................................................... 33
Exercise 2 – Project and User Options Configuration ............................................................................... 34
4 Configure the Source Data Dictionary ................................................................................................. 35
4.1 Populate / Reset the Source Data Dictionary .............................................................................. 35
4.1.1 Populate or Update the Source Dictionary – Worked Example ............................................... 36
4.1.2 Reset the Source Dictionary .................................................................................................... 37
Exercise 3 – Configuration of Source Data Dictionary .............................................................................. 38
5 Schematic Model Manager Attribute Mapping Configuration ........................................................... 39
5.1 Default Attribute Mapping ............................................................................................................. 39
5.2 Attribute Mapping Configuration for Imported P&ID Data ......................................................... 40
5.2.1 Creating Attribute Mappings Groups – Worked Example ........................................................ 40
5.2.2 Creating Attribute Mappings – Worked Example ..................................................................... 43
5.2.2.1 Testing XPath Expression – Work Example ...................................................... 48
Exercise 4 – Attribute Mapping Setup ......................................................................................................... 50
6 GTYPEs and SCSTYPEs Mapping Configuration ............................................................................... 51
6.1 GTYPE Mapping Setup – Worked Example ................................................................................. 52
6.1.1 Populate ISO 15926 Designation from File – Worked Example .............................................. 53
6.1.2 Automatic Completion of ISO 15926 Mappings – Worked Example ....................................... 57
6.1.3 Import Designation from other Database ................................................................................. 60
6.1.4 Overwrite Mapping in Database with Current mapping ........................................................... 61
Exercise 5 – GTYPE Mapping Setup ............................................................................................................ 62
7 Attribute Derivation Rules Configuration ........................................................................................... 63
7.1 Attribute Derivation Rules Setup – Worked Example ................................................................ 63
7.2 Adding Filters to Attribute Derivation Rules Setup – Worked Example................................... 66
www.aveva.com
Exercise 6 – Attribute Derivation Rule ........................................................................................................ 68
6
8 Line List Rules Configuration ............................................................................................................... 69

8.1 Line List Entry (LLENTRY) Configuration ................................................................................... 70
8.1.1 Creating LLENTRY Rule for SCPLINE –Worked Example ...................................................... 70
8.1.2 Creating LLENTRY Rule for SCBRANCH –Worked Example ................................................. 71
8.2 Line List From and To (LLFROM/LLTO) Configuration .............................................................. 72
8.2.1 Creating LLFROM /LLTO Rule for SCBRANCH –Worked Example ....................................... 73
8.3 Line List Diagram (LLDIAGRAMS) Configuration....................................................................... 74
8.3.1 Creating LLDIAGRAMs Rule – Worked Example .................................................................... 74
Exercise 7 – Line List Rules Configuration................................................................................................. 76
9 Schematic Model Viewer Icons Configuration .................................................................................... 77
9.1 Schematic Model Viewer Overview .............................................................................................. 77
9.2 Schematic Model Viewer Icons..................................................................................................... 77
Exercise 8 – Schematic Model Viewer Icon Configuration ....................................................................... 80
10 Highlight Changes Attributes Compare Configuration .................................................................. 81
10.1 Attribute Compare Configurations – Worked Example.............................................................. 82
10.2 Highlight Colour Configurations .................................................................................................. 84
10.2.1 Highlight Colour Configuration – Worked Example.................................................................. 84
Exercise 9 – Highlight Changes Attribute compare Configuration .......................................................... 86
11 Status Control Configuration For Schematic Elements ............................................................... 87
11.1 Status Control Configuration - Overview .................................................................................... 87
11.1.1 Status Control Setup for Schematic Diagrams – Worked Example ......................................... 88
11.1.1.1 Create Status Configuration World .................................................................... 88
11.1.1.2 Create Status Definition .................................................................................... 89
11.1.1.3 Create Status Value .......................................................................................... 91
11.1.1.4 Setting Status Value Transition ......................................................................... 93
Exercise 10 – Status Control Configuration .............................................................................................. 96
Appendix A ..................................................................................................................................................... 97
ISO 15926 Generic Types .......................................................................................................................... 97
Appendix B ..................................................................................................................................................... 99
Generic Types (Piping Components) ...................................................................................................... 99
Appendix C ................................................................................................................................................... 100
Schematic Model Manager UDA’s .......................................................................................................... 100
Appendix D ................................................................................................................................................... 102
XPath Expressions .................................................................................................................................. 102
www.aveva.com
www.aveva.com
CHAPTER 1
1 Introduction
The AVEVA Schematic Model Manager Administration training guide is for use with AVEVA Schematic
Model Manager Module.The training course will provide the trainee (Schematic Administrator) the necessary
skills to setup or create PDMS projects and all the required configuration for use with Schematic Model
Manager. This chapter outlines the objectives for this guide, details the knowledge required and what must
be in place before training starts, how to use this guide and the course structure.
1.1 Aim
Over the duration of the training participants will be given a basic understanding of how to administer
AVEVA Schematic Model Manager Project.
1.2 Objectives
To show how to setup or create PDMS project and other administrative functions necessary to
Schematic Model Manager in Administration Module.
To show how setup necessary configurations such as Attribute Mapping, Gtype Mapping e.t.c.
in AVEVA Schematic Model Manager application.
To show how to configure required UDA’s and other necessary settings in Lexicon Module.
1.3 Prerequisites
This training course requires;
PDMS and Schematic Model Manager to be installed correctly and working

MS Office Professional (incl. Visio 2007) to be installed (required by Schematic Model Viewer).
All necessary licenses to be valid & active.
Trainees to have a basic knowledge of the AVEVA Plant DESIGN user interface.
Please see Help file Schematic Model Manager – Post Installation Tasks
1.4 Course Structure
Training consists of oral and visual presentations, demonstrations and set tasks. Training is executed in the
PDMS SAM training project. Appropriate XML files from AVEVA P&ID are provided and form the basis of
this training course.
www.aveva.com
1.5 Using this guide
Certain text styles are used to indicate special situations throughout this document, here is a summary;
Menu pull downs and button press actions are indicated by bold dark turquoise text.
Information the user has to key-in will be red and in bold Italics.
Annotation for trainees benefit:
Additional information
Refer to other documentation
System prompts should be bold and italic in inverted commas i.e. 'Choose function'
Example files or inputs will be in the courier new font, colours and styles used as before.
www.aveva.com
CHAPTER 2
2 Administrative Settings
2.1 Environment Setup
When a new PDMS project is created or the setup of an existing project, 2 folders xxxDIA and xxxDFLTS
must be created. The two folders are necessary within the xxx project to store the SVG files created for
Schematic- 3D- Integrator and to store the configuration settings for Schematic- 3D Integrator.
The xxx project environment settings may need to be updated to locate and point to these additional project
folders should they not exist.
As an example here is a before and after indication of changes necessary to enable the SAM project to be
used with Schematic Model Manager and Schematic- 3D- Integrator;
Before
if exist %pp%\sam000 %set_project_evars% reset SAM NOMAIN 000:iso:mac:pic:dwg
After,
if exist %pp%\sam000 %set_project_evars% reset SAM NOMAIN 000:iso:mac:pic:dwg:dflts:dia
2.2 Module Definition Configuration
By default, access to Schematic database from the Schematic Model Manager module is set to read /
write.To use the Schematic Model Manager application it is necessary that this access remains as
read/write. This can be accessed by:
Open the ADMIN module.

Select Project > Module Definition… from the main window pull down.
From the Module Definition form, select Schematic Model Manager Module and then click on
the Advanced Settings. The form is then displayed.
www.aveva.com
2.3 Schematic Database Setup – Worked Example
A schematic (SCHE) database must exist within the project MDB to enable P&ID data to be imported.
The SAM MDB will be used for this AVEVA Schematic Model Manager training and must contain at least
one writable SCHE DB.
The system administrator can add several schematic DBs to the MDB if so desired. It is advisable to create
a new database for Schematic purposes e.g the DIAGRAMS database as used for demonstration.
This will usually be created by the system administrator in AVEVA PDMS 12.1 Admin Module.
To do this:
Start the AVEVA Tags application, Select All Programs >AVEVA Plant > Engineer >
Engineering 12.1 > Admin. Alternatively AVEVA Admin application could be accessed by double clicking
on AVEVA Engineer shortcut icon on the desktop.
AVEVA PDMS login box will then be displayed
In the Project field, select the pulldown

window and then select Sample from
the available list.
In the Username textbox Enter

SYSTEM
In the Password textbox Enter

XXXXXX in upper case.
MDB: None
AVEVA Admin module is displayed. Select Databases and Extracts from the Elements pull down to
display the available databases and extracts.
www.aveva.com
Then select the Create button as highlighted above.The Databases and Extracts dialog will then be
displayed.
Select the Create button as highlighted above.The Databases and Extracts dialog will be displayed.
Select the Master DB radio button and then click the OK button.The Create Database form will then be
displayed as shown:
From the Owning Team grid select <TEAM>SAMPLE
In the optional Description textbox enter

SCHEMATIC ARRANGEMENT
Name and Description are basic alpha-

numeric fields.
In Create SCGROU textbox enter

SAMPLE/DIAGRAMS
Entering a value in this field creates a

database element of the name supplied.If the
field is left unset no database element will be
created. This database element, will be visible
in the Schematic Explorer as a schematic
Group
“Create SCGROU” is displayed if Schematic

database is selected.
From the Database Type option list. Select

Schematic “SCHE”
www.aveva.com
After entering the necessary information,
Click the Apply button; this will complete the

creation of the new database.
Then click the Dismiss button to close the dialog.
The SCHE DB(s) must be writable.
2.4 Dictionary Database Setup
It is also necessary that a Dictionary database is created for the

definition of the default Schematic Model Manager User Defined
Attributes (UDA’s)
This will usually be created by the system administrator in

AVEVA Admin Module as shown:
www.aveva.com
2.5 Multiple Database (MDB) Setup
The newly created Schematic and Dictionary databases SAMPLE/DIAGRAM and SAM/DICT must be
added to a Multiple Database (MDB) in this case SAMPLE as shown.
At least one SCHE

DB and a Dictionary
DB must exist within
the project MDB to
enable P&ID data
importation.
2.6 Schematic Model Manager UDA’s Configuration – Worked Example
Schematic Model Manager uses User Defined Attributes (UDAs) to store additional attribute data from the
source ISO15926 files, such as information about page connectivity and source system persistent identities.
To configure the UDA’s required for use with Schematic Model Manager, start AVEVA Lexicon Application.
First select All Programs > AVEVA Plant > Engineer > Engineering 12.1 > Lexicon
Alternatively AVEVA Lexicon application could be access by double clicking on AVEVA Engineer shortcut
icon on the desktop as shown below:
www.aveva.com
AVEVA Lexicon login box will then be displayed as shown:

window and then select Sample from the
available list.
In the Username textbox Enter SYSTEM
In the Password textbox Enter XXXXXX in

upper case.
MDB: SAMPLE
If the defaut dictionary database (Master/Dict) is used, UDA configuration should be conducted
using Master Project.
Lexicon Module will be displayed as shown:
Enter Lexicon module, the user will be prompted to set up the Schematic Model Manager UDA’s. If it is the
user first time in lexicon and there is no configured UDA’s. Click the OK button to display the UDA
Catalogue.
The UDA Catalogue dialog is used to specify which User Defined Attributes (UDAs) are
available in each schematic database with which Schematic Model Manager operates.
www.aveva.com
Before the UDA Catalogue dialog is opened the system checks the number of schematic
database that the user can write to, If the user has access to more than one database, the
Select Database form will be displayed, prompting the user to select the require database.
UDA Catalogue can also be accessed by selecting from Lexicon Main Menu, Schematic Model Manager >
UDA Catalogue
All Schematic Model Manager UDA’s are prefixed

PMG e.g. Pmgtag
Click the Deselect All button - To uncheck the

checkboxes for all optional UDA
Click the Undo button - to undo any changes in the

UDA Catalogue
To configure all the UDA’s press the Select all button and then press the Apply button to save changes.
To configure required UDA’s, select the

checkbox of each UDA and then click the
Apply button to save the changes.
The greyed out UDA’s are mandatory for the

operation of Schematic Model Manager.
If the UDA is present in the schematic

database, icon is displayed in the UDA row.
If the UDA is present in the schemnatic

database and the attribute mapping has been
set up for the icon is displayed in the UDA
row.
The UDA configuration complete form will be displayed.
Click the Dismiss button and then the Savework

button from Lexicon Main Menu.
www.aveva.com
Exercise 1 – Administrative Setup
Create a Schematic Database to store imported P&ID data.
Create a Dictionary database for the definition of the default Schematic Model Manager User
Defined Attributes (UDA’s)
Add the newly created Schematic and Dictionary databases to a Sample Multiple Database
(MDB)
Configure the UDA’s required for use with Schematic Model Manager
www.aveva.com
CHAPTER 3
3 Schematic Model Manager Project and User Options Configuration
AVEVA Schematic Model Manager can be configured & setup to suit many projects requirements as
described below.
3.1 Entering AVEVA Schematic Model Manager
To start the AVEVA Schematic Model Manager application, Select All Programs > AVEVA Plant >
Engineer > Engineering 12.1 > Schematic Model Manager as shown:
Alternatively AVEVA Schematic Model Manager application could be access by double clicking on AVEVA
Engineer shortcut icon on the desktop as shown below:
www.aveva.com
AVEVA Schematic Model Manager login box will then be displayed as shown:

window and then select Sample from the
available list.
In the Username textbox Enter SYSTEM
In the Password textbox Enter XXXXXX in

upper case.
MDB: SAMPLE
A default screen layout will then be displayed
For further details on AVEVA Schematic Model Manager User interface, please refer to AVEVA
Schematic Model Training Guide (TM-3541).
www.aveva.com
3.2 Project Options Setup
Schematic Model Manager Project Options dialog is where user(s) configures the options which
determines how Schematic Model Manager project operates.The Project Options settings only apply to
current PDMS project.
To access the Project Options dialog
Select Tools > Project Options from the Schematic Model Manager menu.
The Project Options dialog will then be displayed.
The Project Options dialog consists of three tabs,
Element Release Tab

General Tab
Import Configuration
To save changes to the options and exit the dialog, select the OK button. And to exit the dialog without
saving, select the Cancel button.
www.aveva.com
3.2.1 Element Release Tab
Elements in the Schematic database have a Release Status (RESTAT) which determines whether AVEVA
Schematic 3D Integrator can access these elements for integration with the PDMS 3D Design items.
The Element Release tab access, by selecting Tools > Project Options from the Schematic Model
Manager main menu is used to specify:
Element release status related actions during the P&ID import process into the schematic
database.
If the Release Comments dialog is displayed during release related activities initiated during an
import.
All imported element falls into one of these categories as shown below and these options or categories
define the “release behaviour” of elements on import;
Note: only the following Schematic elements can be assigned a release state;
SCEQUI: Equipment
SCOINS: Instruments
SCPLIN: Pipelines
SCBRAN Pipe Branches
SCSEG: Page / Pipe segment
3.2.1.1 Updates to Existing Released Elements
Existing elements (i.e. elements imported before) that have been released may be updated by the user(s) if
required as shown.
Abort Diagram Import - If this option is selected, no elements will be imported from diagrams that include
released elements.
The release status of previously imported elements is retained. (Default setting).
Import and set release status to OFF – If this option is selected, the elements are imported and their
release status changed to not released (OFF).
www.aveva.com
Import and keep existing status (ON) - If this option is selected, the elements are imported and their
release status retained, i.e. set to Released.
If the ‘Abort Diagram Import’ option is selected, an error message will be displayed when
instances of existing ‘Released’ database items are being imported. The import of these elements
will be aborted.
3.2.1.2 Updates to Existing not Released Elements
Existing elements that have not been released may be updated by the user(s) if required as described.
Import and keep existing status (OFF) – If this option is selected, the elements are imported and their
release status retained, i.e. set to “Not Released” (Default setting).
Import and set release status to ON – If this option is selected, the elements are imported and their
release status changed to Released.
3.2.1.3 Setting Release Status for New Elements – Worked Example
Set release status to OFF - If this option is selected the elements are imported and their release status set
to “Not Released”. (Default setting)
www.aveva.com
Set release status to ON - If this option is selected the elements are imported and their release status set
to released.
3.2.1.4 Active Release Comment Dialogue Form
Enable Release Comments: - If checked Release Comment dialogue box is displayed during release
related activities, either initiated during an import, or from the Schematic Model Manager User interface.
Add Date/Timestamp to Release Comment: - If checked a Date & Time stamp value is included with the
Release Comment.
3.2.2 General Tab
Schematic Model Manager options settings apply to the current project. Schematic Model Manager creates
a record of Schematic Model Manager related options of a project,
which it stores locally.
The General tab is used to:
Copy options settings from another project associated with

the same PDMS instance/Installation.
Import options settings from files exported from another

PDMS installation.
Export options settings to files for importing into other PDMS

installation.
Reset the project to the default installation settings.
www.aveva.com
3.2.2.1 Copy options settings from another Project
To copy project options from another project, select the Copy from Project… button from the General tab
dialog.
The Select Project dialog will be displayed and all Projects which have Schematic Model Manager options
defined will be displayed.
The dialog lists the entire project on the current PDMS

installation for which Schematic Model Manager options
have been saved.
Select the required project and then click OK button to copy options
from the selected project. A message is displayed when the copy is
completed.
If there are no project settings to copy in the PDMS installation, an error message will be displayed.
Copying settings from another project;

- Import setting from files
- Reset to the default settings such as change the Attribute mappings, GTYPE mappings, and
Attribute derivation rules of the project, as well as the project options set up using the
Project Options dialog.
www.aveva.com
3.2.2.2 Exporting Schematic Model Manager Options folder
The Schematic Model Manager Options files can be exported as a zipped folder, which can be imported by
other PDMS installation for use by other project.
To export Schematic Model Manager Options file. Select the Export button from the General
tab dialog. The Export Options form will then be displayed, click on the Yes button to continue as shown:
The Browse for folder dialog will be displayed.
Select the location that the option file is to be exported to

and click the OK button.
A message is displayed when the export is completed. The file is then exported to specified location with the
default naming convention <Project>_Option .Zip
www.aveva.com
The AttributeMapping XML file stores attribute mapping configuration

The ISO15926 stores / contains Gtype mapping configuration.
The Options XML stores Attribute derivation rules of the project as well as the project options setup
from Project Options dialog.
3.2.2.3 Importing Schematic Model Manager Options File
The exported “Options” file can be imported into another project which then automatically changes the
options setting of that project to those in the file.
To import the exported file:
Select the Import button from the General tab dialog.
The Browse for folder dialog will be displayed.
Then select the location that contain the Zip file

(<Project>_Option.Zip)
Select the OK button to import the file. And the

existing options settings are replaced by those in the
import file.
Message is displayed when the import is completed.
www.aveva.com
3.2.2.4 Restore Default Options Folder
The Reset button is used to restore the default Schematic Model Manager options. To do this;
Select the Reset Defaults button from the General tab dialog. A message requesting Reset
confirmation will be displayed as shown:
The Reset Default function will reset all Schematic Model Manager configuration back to
installation settings including GTYPE Mappings, Attribute Derivation Rules and project options
3.2.3 Import Configuration Tab
When P&IDs data are imported into Schematic database, the P&ID data are automatically placed in different
default Schematic groups (SCGROU) within the database presented in a hierarchical data explorer
(Schematic Explorer) as shown:
Default SCGROUP
Schematic diagrams (SCDIAG)
Schematic off-line instruments (SCOINS)
Schematic equipment (SCEQUI)
Schematic pipelines (SCPLINE)
Schematic loop (SCLOOP)
Schematic Actuator (SCACTUATOR)
Schematic Instrument Line (SCILINE)
www.aveva.com
3.2.3.1 Changing Default Import Destination Groups – Worked Example
The Schematic groups (SCGROU) elements are placed on import can be specified by the user using
Import Configuration option.
To specify required import Destination Schematic Groups, select the View/Edit button on the Import
configuration tab. The Import Destination Groups Dialog will be displayed as shown.
To reset or change the default Schematic groups, for example placing LOOP data into SCINSTRUMENT
group on import into Schematic database;
First to view or change the import destination groups of another database, select the required
database from the pull down list. In this case select “SAMPLE/CABLDIA” as shown.
The database pull down list consists of every

schematic database in the current MDB
The grid beneath the database field lists Allowable

element types and the names of the groups into
which they are imported.
www.aveva.com
In the grid beneath the Database field, click the browse button at the end of the required row. In this
example select the browse button at the end of SCLOOP row, the Select Group dialog will be displayed as
shown below.
In Select Group dialog, select required group, in this case “SCGROUP

SAMPLE/SCHDBTEST/*/Instruments” as higlighted above. Then select the OK button.
To cancel the changes, press the Cancel button to close the dialog without any changes.
The Import Destination Groups dialog will then be displayed. Select SCGROUP (SCGROUP
SAMPLE/SCHDBTEST/*/Instruments) path against SCLOOP as shown below;
Press the OK button to close the Import

Destination Groups dialog and save the
changes that have been made.
Press the Cancel button to close the dialog

without saving changes
www.aveva.com
Once the P&ID’s data are imported into the Schematics database, Instrument loop data will then be placed
in Schematic Instrument group (SCINSTRUMENT) as specified in Import Destination Groups dialog.
For further details on importing P&ID data into

schematic database, please refer to AVEVA
Schematic Model Training User Guide (TM-
3541).
3.2.3.2 Graphics Settings
When diagrams (PID’s) are imported into Schematic Model Manager, they are imported in colour.
This is the default setting and to ensure that the imported diagrams are in colour, Import diagrams in
colour checkbox must be checked.
If the Import diagrams in colour checkbox is not checked, all drawings are converted to black and white
when they are imported.
www.aveva.com
3.3 User Options Setup
The User options dialog is used to set user specific Schematic Model Manager options, which specify the
default folders for data imports and exports.
To access the dialog, select the Tools > User Options from the Schematic Model Manager module main
menu.
3.3.1 Data Export Default Location Setup – Worked Example
The Data Export default location option is use to specify the default folder for data export. If setup this is
where the Project Options zip file is output to.
To setup Data Export location, select the Data Export row, and press the Modify button.
www.aveva.com
The Browse for Folder dialog will then be displayed. Browse for the required folder and press the OK
button. The new location is then displayed in the Default Location field as shown
3.3.2 Data Import Default Location Setup – Worked Example
The Data Import default location option is use to specify the default folder for data Import.
To setup Data Export location, select the Data Export row, and press the Modify button
The Browse for Folder dialog will then be displayed. Browse for the required folder and press the OK
button.
The new location is then displayed in the Default Location field as shown
www.aveva.com
Exercise 2 – Project and User Options Configuration
1. Using the Project Options Form sets:
Release Status to “NO” for New elements that are imported into Schematic Database
Release Status to “OFF” for existing elements with Not Release Status in Schematic Database.
2. Using User Options Form sets:
Data Import default option to required location

Data Export default option to required location
www.aveva.com
CHAPTER 4
4 Configure the Source Data Dictionary
The Source Data Dictionary is a tool which helps in visualising and understanding the potential contents of
import files, in terms useful when creating attribute mappings.
The Source Data Dictionary consists of attribute and element metadata. This data is extracted from the
import files (the same files from diagram data is imported
This information is made available when configuring the attribute mappings using the XPath
Expression Builder dialog in order to reduce the need for a user to understand the source file
format and XPath syntax. Please refer to section 5.0 for more details.
4.1 Populate / Reset the Source Data Dictionary
To populate, refresh or update the Source Data Dictionary, select Tools > Source Dictionary Management
from the main menu to display the Source Dictionary Management window.
Alternatively, the Manage Source Dictionary Option may be accessed by select the Manage
Source Dictionary option on the XPath ExpressionBuilder dialog
The Source Dictionary Management form contains:
Reset the Dictionary – used if the dictionary is out of date because the GTYPE mappings or Attribute
Mappings relating to GTYPE have changed, then the dictionary should be reset.
Populate or Update the Dictionary - Used to add data to the dictionary without importing P&ID content into
the Schematic database.
www.aveva.com
4.1.1 Populate or Update the Source Dictionary – Worked Example
To add data to the dictionary without importing P&ID content into the database select the Populate
Dictionary from Source files … option.
The Open dialog is then displayed. Select the import file or files from which dictionary data is to be
extracted. Then click the Open button.
Then click the Open button, the selected

files are processed and information about
the elements and their attribute is added to
the dictionary.
The selected files are processed and the dictionary is populated automatically when diagram schematic data
is imported with attribute and element metadata relating to the component classes in the diagram data
import files
The imported attribute of the diagram can be

viewed on the XPath ExpressionBuilder dialog
The dictionary may also be populated manually if required. During a project life cycle, the Source Data
Dictionary may need to be populated or updated manually at the following times:
On creation of a project, for the purposes of configuring the attribute mappings,

prior tothe import of diagram files.
After editing the GTYPE mappings or attribute mappings in such a way that the element
types created in the database are affected.
On configuring attribute mappings for data from a new source system or file format.
www.aveva.com
4.1.2 Reset the Source Dictionary
If the dictionary is not current because the GTYPE mappings or Attribute Mappings relating to GTYPE have
changed, then the dictionary should be reset.
Select the Reset Source Dictionary … option.The following message is then displayed:
Click the Yes button the dictionary will then be reset to its default, empty state. If the attribute mappings are
to be edited before the next data import then it is recommended that the dictionary is populated
www.aveva.com
Exercise 3 – Configuration of Source Data Dictionary
1. Using the Source Dictionary Management form, populate the source data dictionary from the source files
(P&ID data) provided by the Trainer.
www.aveva.com
CHAPTER 5
5 Schematic Model Manager Attribute Mapping Configuration
In AVEVA Schematic Model Manager, prior to importing P&ID’s data, a review of the source data (P&ID
data) should take place so that all necessary mapping can be completed before import commences.
Source attributes will need to be mapped to Database attributes to ensure that attribute data is imported to
the correct location for the appropriate Schematic Type. The Attribute Mapping dialog is used for this task as
described in the following worked examples.
5.1 Default Attribute Mapping
A number of default mappings are supplied with Schematic Model Manager. They are listed in the Default
Group beneath the attribute mappings entry in the tree/explorer view accessed by select the Tools >
Attribute Mappings… option from the Schematic Model Manager Module main menu.
The “Attribute Mapping” option can also be accessed from LEXICON module. Changes made in
the LEXICON module are not committed to the database until a Save Work takes place.
The default Attribute Mapping folder location depends on where PDMS is installed; most often, it
is located in “C:\AVEVA\Plant\PDMS12.1.1\Schematic Model Manager\Defaults”
The Attribute Mappings dialog can be used to to view existing mappings and organise attribute mappings
into attribute mapping groups.
The dialog is divided into two sections. The left-hand section displays a tree-view of the current attribute
mapping groups and the attribute mappings they contain, and is used to create, move and delete mappings
and groups.
www.aveva.com
5.2 Attribute Mapping Configuration for Imported P&ID Data
The Attribute Mappings dialog is used to map system/project specific attributes from the source files (P&ID
data) to schematic or user-defined database attributes as described in the work example.
This is often used if specific project attributes mappings from the source files (P&ID data) to schematic or
user-defined database attributes that are not the default mappings is required.
5.2.1 Creating Attribute Mappings Groups – Worked Example
Attribute mapping groups are container for attribute mappings and may contain other attribute mapping
groups as well as mappings.
To create an attribute mapping group, right-click on the top-level entry (Attribute Mappings) of the explorer
explorer or existing attribute Group. Then select Create > Attribute Group or Insert > Attribute Group
option from the displayed menu
The right-hand panel section of the

dialog automatically displays the
properties of the newly created group.
Then complete the properties field to set up the attribute mapping:
Change the default Name of the

mapping either by clicking on the field
or on the name in the tree view and
enter PIPELINE NAME
www.aveva.com
In the Element Type field, select the element to which the mapping in the group can be applied the mapping
to, by clicking the browse… button at the end of the field to display the Select Values dialog
Select the required element type from the Available Values grid, and press the > button to move the element
to the Selected Values grid. In this case select SCPLINE as shown
The de-select; select the required SCPLINE from the selected Values grid and press the “<”
button to the element to Available grid
Press the >> button to move all elements to Selected Values grid. And Press << button to move all
elements from Selected Values grid to Available Value grid.
Select OK button form the Select Values form, once the required element (SCPLIN) have been selected.
www.aveva.com
In the Source System field, set the source of the P&ID from the drop down window to AVEVAPID
In File Format Field, select the file format “XMpLant” from the dropdown window as shown
In File Format Field Version field, click the browse … button at the end of the field to display the Select
Values dialog
Select 3.3.3 from the Available Values grid, and press the > button to move the element to the Selected
Values grid and click OK button
The File Format version field displays the versions of the source file format associated with source
file attribute. Schematic Model Manager supports XMplant 3.2.0 and 3.3.3 versions.
In this example the Condition Field should remain unset. This option is used to determine whether or not
the attribute mappings in the group are applied.
www.aveva.com
To enter the conditions, select the browse... option at the end of the Condition field and enter an XPath
Expression using the XPath Expression Builder
For further details on XPath Expression, please refer to section 5.2.2 and Appendix A.
5.2.2 Creating Attribute Mappings – Worked Example
To create a new attribute mapping, right-click on the attribute group;
Right-Click on the newly created “Attribute Group” in section 5.2.1 to display the right-click menu. Select
the Attribute Mapping option from the sub-list.
A new attribute mapping with a default name is created at the bottom of the hierarchy of group. The right-
hand section of the dialog automatically displays the properties of the new mappings, as shown:
Then complete the properties field to set up the

attribute mapping as shown:
In the Name Field, Enter a suitable

name.In this case SCPLIN NAME
In the Element Types Field, select

the appropriate element type in this
case SCPLINE to which the mapping
is to be applied from the Select
Value form as described in section
5.2.1
www.aveva.com
The schematic elements types that are available for selection are limited to those specified for the
mapping group.
In the Database Attribute Field, Select the appropriate attribute in this case NAME to which the source file
attribute is to be mapped, from the drop-down list.
The list of attributes available depends on the selected Schematic Element types.
In the Attribute Value field, enter the required Xpath expression as shown below, to map the source file
attribute (Bore Size) from the P&ID data to be imported to the value in the Database Attribute field in this
case “Name”.
concat( GenericAttributes/GenericAttribute[@Name='Size']/@Value,'-', translate(normalize-space(

@TagName ), ' ' , '' ))
The above XPath expression will map the source file attribute (Bore Size) to Database Attribute
(Name)
An XPath expression may be constructed manually, by typing directly into the Expression area of the dialog.
Alternatively using the element for constructing XPath expression provided on the Shortcuts, XPath
Operators and XPath Functions tabs as described below:
Display XPath Expression Builder Dialog by selecting the browse … button at the end of the
Source Attribute field.
In the Source Dictionary section of XPath Expression Builder, display available list of attributes
depends on the selected Schematic Element types
www.aveva.com
Place the cusor in the Expression Pane, and then double click on the “concat” function in the
XPath Functions tab. The “Concat” function will then be displayed in the Expression Pane.
“Cancat” function
appends one or more
strings onto a strings.
Users can populate Source Dictionary list by selecting Manage Source Dictionary option.
Please refer to section 4.0 for more details.
Select the required source file attribute in this case (Bore Size) to be included in the expression from
the Source dictionary by navigating to the required element in the source dictionary tree view.
Double clicking on the attribute. This attribute will then be added to the expression as shown in the
Expression Pane Section as shown
The source dictionary Source Dictionary pane shows the contents of the source dictionary that
relate to the Schematic Element type slected in the Element Type field of the main Attribute
Mapping dialog.
The source dictionary may be populated incrementally and automatically either during diagram
import or manually populated from one or more source files by clicking the Manage Source
Dictionary button from the Schematic Model manager XPath Expression Builder dialog.
www.aveva.com
Place the cusor in the Expression Pane in front of the “@Value” and add a delimiter if required as
shown:
Select “Remove all space” function from Shortcuts tab and drag to desired position in the
Expression Pane, in this case ahead of the delimiter or after the delimiter text ‘-‘.
The “Remove all space” function romoves all white space characters-“translate (normalize-space
(source data)”.
To add the source file attribute, (in this case “TagName”) to which the translate expression is to be
applied. Select the required element in the source dictionary tree view and drag to a desired
position in the Expression Pane as shown.
www.aveva.com
This attribute will then be added to the expression as shown in the Expression Pane section
When the required the XPath expression construction is completed, select the OK button from the XPath
Expression Builder Dialog. This will automatically update the Attribute Value as shown.
www.aveva.com
In Source Attribute Units Field, If the user selects a source attribute which has unit definition, the user may
be prompted to set the unit type for that attribute.
Imported files (XML) using both the SMM import and the
Excel Interface to work using the new Dabacon units
Once all the required fields have been setup. click the OK button from the Attribute Mapping dialog to close
the dialog or the Cancel button to close dialog without saving any changes.
When diagrams (P&IDs) are imported; the attributes values are automatically set according to user-defined
attributes mappings.
5.2.2.1 Testing XPath Expression – Work Example
XPath Expression may be tested if required using the “Preview tab”. The tab is used to test if an XPath
expression is valid and returns data which conforms to the mapped attribute of a Schematic element type
The tab is also used to preview the possible attribute values of database elements which are returned, after
XPath expressions have been applied on a selected P&ID.
To test the XPath expression constructed in section 5.2.2
Open XPath Expression Builder Dialog by selecting the browse …

button at the end of the Source Attribute field. And then Select the
Preview tab:
Set the “Source File” field, by selecting drawing against which the expression is to be tested:
www.aveva.com
The diagram file path, file format, file version and source system are displayed in the Source File field in the
format:
Press the Evaluate button and if the Expression is valid, the Preview Tab then display the result and Status
symbol display green tick indicates that the expression has been checked and is valid.
The source element type is displayed in the TYPE column,
The tag of the element in the drawing is displayed in the Tag field,
The attribute value resulting from the application of the XPath expression is displayed in the Result
field
If the expression is invalid, and error message is displayed The Status symbol, is then displayed as
a ‘red cross’ indicating that the expression has been checked and is not valid
www.aveva.com
Exercise 4 – Attribute Mapping Setup
1. Create an Attribute Mapping to
Set the Database attribute “Prefix” of Schematic Equipment element from source file (P&ID data) to
database attribute “Prefix” on import.
Set the Database attribute “:pmgdesc” of Schematic Equipment element from source file (P&ID
data) database attribute “Description” on import.
www.aveva.com
CHAPTER 6
6 GTYPEs and SCSTYPEs Mapping Configuration
GTYPE’s (Generic Type) identify the generic component types of the items that may be created in the 3D
database from the imported schematic items. SCSTYPEs (not to be confused with SCTYPEs) are GTYPE
sub-types, used to further identify GTYPEs
GTYPE’s & SCSTYPE’s are associated with schematic items by mapping them to the ISO15926
designations of schematic items present in the imported files (XML). Each ISO15926 designation represents
a component type in the schematic source data.
The GTYPE value also affects the schematic database element created. For example If the GTYPE
is set to ‘VALV’, ‘VTWA’ or ‘VFWA’ then an SCVALV schematic element is created.In the absence
of a GTYPE value of ‘VALV’, VTWA or VFWA only SCINST, SCTUB and SCFITT schematic
database elements will be created beneath an SCSEGMENT element hierarchy.
The choice and setting of the GTYPE value has implications in the schematic database in the following
aspects:
The element type is created on import.
Schematic 3D Integrator during Compare / Link / Build actions.
Downstream workflow (MTO and isometric production).
Not all schematic items have equivalents in the 3D database. Such items do not need to have
mappings set up against their ISO15926 designation.
To view or edit the mappings between ISO15926 designations and corresponding GTYPE/ SCSTYPE
combinations. Select the Tools > GTYPE Mappings option from the Schematic Model Manager main menu
www.aveva.com
6.1 GTYPE Mapping Setup – Worked Example
If the GTYPE (PDMS_Type) or SCSTYPE (PDMS_SubType) of a pipe component (e.g. PipeTee ) is unset
in the source file (ISO15926 XML File from AVEVA P&ID) as shown below, the attribute will remain unset in
Schematic Db if imported into Schematic Model Manager.
Schematic Explorer Attribute form
For further details on

Schmatic Explorer,
please refer to AVEVA
Schematic Model
Manager Training User
Guide (TM-3541).
To add new Gtype mapping to piping components in this case “PipeTee”
Open the the GTYPE mapping dialog by select the Tools > GTYPE Mappings as described in
section 6.0
Check if the required pipe component in this case PipeTee already exist in the ISO15926
designations field , and if not enter the required pipe component as shown
Click on the blank row at the bottom of the grid; enter the designation of the schematic item (PIPE
TEE) in the ISO 15926 Designation field. And then set GTYPE to the appropriate type in the case
Tee from the pull down list.
www.aveva.com
Select OK button from Schematic Model Manager Gtype Mapping dialog to save the settings.
To apply the newly created GTYPE

mapping, re-import the required diagram
If the required pipe component in this

case PipeTee already exist in the
ISO15926 designations field, complete
the mapping by selecting the appropriate
GTYPE if applicable, and enter a
relevant SCSTYPE.
If the GTYPE and SCSTYPE are set in the source file (e.g. AVEVA P&ID), Schematic Model
Manager will use these set values and override the GTYPE values configured in the GTYPE
mapping Form.
However if the GTYPE and SCSTYPE are unset in the source file XML file ( for example no values
configured in AVEVA P&ID) then Schematic Model Manager will use the values configured in the
GTYPE mapping form, If the designations (pipe component) already exist in the ISO15926
designations field.
6.1.1 Populate ISO 15926 Designation from File – Worked Example
The ISO 15926 Designation fields can be completed by importing a list of designations from a source file as
described in the example below:
www.aveva.com
To import designations from a source file:
Select the Populate ISO 15926 Designations from File button. And the Import dialog is then displayed
Locate the XML file that contains the designations you wish to load. Once the file is selected, press the
Open button. Imported GTYPEs are validated against a list of valid GTYPEs stored in the database.
If a GTYPE for import does not exist on this list, then it is classed as ‘Invalid’ and its associated
designator/component will not be imported. A message is displayed to advise the user as shown in this
example.
Select the OK button from the Schematic Model Manager form to continue.
www.aveva.com
The designations in the file are then copied into the ISO 15926 Designation fields. The GTYPE and
SCSTYPE fields are then completed with the GTYPEs and SCSTYPE from the source file mapped to the
designations in the imported files.
Designations already listed in these fields

are not re-imported; therefore existing
mappings will remain unaffected. If a
designator in the import file is mapped to an
SCSTYPE value but not a GTYPE value
then the designator will be treated as if it
has an invalid GTYPE and not imported.
When the import is completed successfully, the following

message is displayed:
If the selected file includes GTYPE (GenericType) and STYPE (SubType) mappings which conflicts with
those already set up in the ISO15926 Mapping dialog. A conflict resolution message will be displayed when
the OK button on the Schematic Model Manager form is selected.
Conflicts may also exist within the import file, i.e the
file may include multiple instances of the same
designator mapped to different GTYPEs or
SCSTYPE.
www.aveva.com
Select Yes button, from the ISO15926 Import-Conflict resolution form, if you wish to include the ISO15926
designation values in the resolution.
If the Yes button is selected on the

Conflict resolution message, the list
will include the GTYPE currently
mapped to the designator in the
ISO15926 Mapping dialog. If the No
button is selected, this GTYPE will
not be included.
Select the preferred GTYPE value to map to the designator from the list and press OK button. The GTYPE
field are automatically completed with the selected GTYPEs values as shown
If conflicting SCSTYPE values are found then the

assumption is made that no valid choice can be made
between them, either by the software or by the user,
and a blank SCSTYPE will be saved, overwriting any
existing mappings
www.aveva.com
6.1.2 Automatic Completion of ISO 15926 Mappings – Worked Example
This feature is provided to enable new projects to be setup with minimum effort. ISO 15926 mappings can
be automatically completed based on a pre-defined set of rules.
To set up the rules for automatic completion:
Select the Configure Auto Complete button to display Auto Complete Configuration dialog.
www.aveva.com
In Rule grid:
Enter a regular expression that is used to select which designators are to be mapped using the rule. In this
case enter PLUG VALVE. All designators containing Plug Valve would be mapped using this rule.
In the GTYPE grid, select the appropriate

GTYPE that designators selected by the rule
expression are to be mapped to.
For example GTYPE for valve is VALV. Then

enter the appropriate SCSTYPE if applicable.
The order in which rules are listed is the order in which they are processed. To change the position of a
rule in the list of rules, select the row containing the rule and press the up or down arrow button as
required.
Once a rule has been applied to an ISO15926 designator, the mapping it applies cannot be overwritten
during that process by another rule.
If the Overwritten existing values checkbox is checked, existing mapping are overwritten when the
rule are applied. If the checked box is unchecked, existing mappings are not overwritten.
To close the dialog and save any changes, press the OK button
www.aveva.com
To apply the setup rules to ISO 15926 Designation GTYPE Mapping, In the ISO 15926 Designation enter
PLUG VALVE.
Select Auto Complete button, the GTYPE field is automatically completed with pre-defined rule in this case
VALV
Rows that have been automatically

completed are identified by a pencil
symbol in the left hand column.
If undesired changes are made to the

ISO 15926 mappings then please
remember that you can cancel this
form & any changes will be
discarded.
www.aveva.com
6.1.3 Import Designation from other Database
The ISO 15926 Designation fields can be completed by importing designations from other database(s)
within the current MDB.
To import designations from other databases:
Select the Populate from Database(s) button.
The Select Database dialog will be displayed. The dialog lists all the Schematic databases in the
Master database (MDB).
Select the database(s) to import designations from, check the appropriate apply checkboxes
Once the required selections have been made, select the OK button. The import then takes
place. The designations in the selected databases are then copied into the ISO 15926
Designation fields.
Press the Cancel button to close the dialog without proceeding with the import.
Designations already listed in these fields are not imported, and therefore existing mappings will not
be overwritten. If a selected database does not contain any valid designations, an error message is
displayed.
www.aveva.com
6.1.4 Overwrite Mapping in Database with Current mapping
This option is used if designation/GTYPE mappings are changed after imports have already taken place.
For example if the name of a component type in the source diagrams is changed, this means that elements
already imported into the database having the wrong mappings.
To apply the current mappings to elements already imported into the Schematic database(s) in the current
MDB, or to apply the mapping to elements in another database.
Press the Re- apply to database(s) button. The Select Database dialog will be displayed
Select the required databases and then press the OK button to apply the current mappings to elements
already imported into the Schematic database(s).
www.aveva.com
Exercise 5 – GTYPE Mapping Setup
1. Populate Schematic Model Manager Gtype Mapping form a from a source file (A1-51-2009-1 –
provided by the trainer) using the “Populate ISO 15926 Designations from Files” options on GTYPE Mapping
Form.
2. Setup a Gtype Mapping for the following piping components
SAFETY VALVE
SIGHT FLOW INDICATOR
DUPLEX STRAINER
CARTRIDGE FILTER
FLAME ARRESTOR
BELLOWS
RUPTURE DISC
www.aveva.com
CHAPTER 7
7 Attribute Derivation Rules Configuration
The Attribute Derivation Rule features option allows user(s) to defined rules that will set or re-defined
schematic attributes values upon import according to the user-defined rules.
There is no default attribute derivation rules shipped with Schematic Model Manager.
7.1 Attribute Derivation Rules Setup – Worked Example
For example to create an attribute derivation rule to add the text ‘Test’ to SCEQUI Name upon import of the
P&ID to Schematic Database.
Select the Tools > Attribute Derivation Rules option from the Schematic Model Manager main toolbar as
shown:
Right-click on the schematic Attribute Rules nodes, or the node of an existing group, or an existing rule and
select Create > Group from the submenu.
Rules can be grouped as a means of

organising like rules, to do this users can by
create Groups for similar rule.
www.aveva.com
To edit an existing rule group, simply select the group, so that its details are displayed in the right-
hand pane and then modify the required entry.
The New group (Default name) is then created within the selected node.
To display the New group details,
Select the New group, the

details are then displayed in the
right-hand pane.
In the Name Field, Enter a

suitable Name; Equipment
Rule Group
In the Enable Field, If the new

rule group is to be processed,
select “True” from the pull
down window otherwise select
“False”
Select and right-click the required group, from the submenu select either Create > Rule or Insert > Rule.
The New rule (Default name) is then created within the selected node.
Each rule and rule group listed in the dialog has an “enabled” checkbox next to its name. These checkbox
are used to select which rules are to be applied during import.
If a rule group checkbox is unchecked, all the rules and rule groups within that group are
unselected, whether or not their checkboxes are checked.
If the Attribute Processing Rules checkbox is unchecked, all rules and rule groups are
unselected, whether or not their checkboxes are checked. Rules that are disabled are ‘Greyed’
out and invalid rules are shown in a red font
www.aveva.com
In the Name Field, enter a suitable Name:

SCEQUIP
Element Types field, select element type

the rule will apply to, in this case
SCEQUIPMENT
Database Attribute field, select the

database attribute that will be set in this
case NAME
Expression field enter database

expression that defines this rule for
example 'TEST’ + NAME
In Name Clash Rule field, Select False from the pull down window, these rules are only applied when there
is a name clash and also when the import process or Attribute Derivation rules attempt to create an element
with a name already in use.
If the expression is valid a green tick will be displayed to the left of the Expression field
For assitence with DB Expressions please refer to the PDMS ‘Database Management Reference
Manual
Once all the required field have been set up as shown above, select the OK button to close the dialog.
The defined rule(s) is then applied when diagrams are imported; the values of attributes are automatically
set according to user-defined rules which is in this case is add text ‘Test’ to SCEQUI Name
The Cancel button on the Attribute Rule Form is selected if required to close the dialog without
saving any changes.
For the rule to take effect, the diagram or P&ID must be re-imported to Schematic Model Manager,
if the diagram or P&ID already exists in schematic database.
www.aveva.com
7.2 Adding Filters to Attribute Derivation Rules Setup – Worked Example
Also the users can then apply any appropriate attribute Filters to this rule if required. Attribute filters can be
set up for the rule displayed in the Attribute filters field.
To add an attribute filter, click on the… button at the end of the Attribute Filters filters field to display the
Attribute Filters dialog.
Select Add Filter icon to create a row and complete the required fields.
– Select required attribute from

the pull down window in this
case DISTAG
– Select required operator from the

pull down list in this case Equals
www.aveva.com
– In the Value field enter an appropriate value to set the DISTAG attribute in this case P1502A
Once all the required filters have been set up, select the OK button to close the dialog.
This will force the attribute Derivation rule to only apply only to Scequipment with DISTAG attribute Value
equal P1502A upon import into schematic database. As shown below:
www.aveva.com
Exercise 6 – Attribute Derivation Rule
1. Setup an attribute Derivation rule to set the following database attribute (see below) for Schematic
Pipeline on import of the source file (A1-51-2009-1 – provided by the trainer) .
Design Tempareture Max (Dtmpmax) to 100degC

Design Tempareture Min (Dtmpmax) to 40degC
Operating Temparature Max (Otpmax) to 60degC
Operating Tempareture Min (Otpmin) to 50degC
www.aveva.com
CHAPTER 8
8 Line List Rules Configuration
Using the standard PDMS/Marine Search facility, users may retrieve and view the line list of the project,
derived from imported schematic data.
Before this can be done, additional configuration is required SCPLINE and SCBRANCH to specify;
Elements are to be included in the line list,

Setup rules for generating the text displayed in the line list for the From and To attributes, and
Setup rules for specifying how diagram names are displayed in the line list
To do this several pseudo attributes have been added to line and branch elements in the schematic
database.These attribute are;
This configuration is carried out using the Line List Configuration dialog. Access by Selecting the Line List
Options... option from Tools menu on Schematic Model Manager main toolbar.
www.aveva.com
The Line List configuration dialog consists of three sections. The left-hand pane displays a tree-view of the
configuration rule groups and the rules they contain, and is used to create and delete rules.
The rule nodes are; LLENTRY, LLFROM/LLTO and LLDIAGRAMS are pseudo attributes of the SCPLINE
and SCBRANCH elements that are used to configure line lists.
The Rule Properties section is used to define and display the properties of whichever rule or group is
currently selected in the tree view.
The Rule Filters section is used to create filter to apply the currently selected rule.
8.1 Line List Entry (LLENTRY) Configuration
Under the LLENTRY node in the hierarchy tree-view, there are five rule group nodes: SCPLINE, PIPE
SCBRANCH, BRANCH and Component Rules
In the SCPLINE Rules group, rules are set up to specify which

SCPLINEs are to be excluded from line lists and to be excluded
from use in a 2D/3D comparison of simplified piping network
structures
In the 3D PIPE Rules group, rules are set up to specify which PIPES are to be excluded from use in a
2D/3D comparison of a simplified piping network structure. (Mainly for design element “PIPE”)
In the SCBRANCH Rules group, rules are set up to specify which SCBRANCHs are to be excluded
from line lists and to be excluded from use in a 2D/3D comparison of simplified piping network
structures.
In the 3D BRANCH Rules group, rules are set up to specify which BRANCHs are to be excluded from
use in a 2D/3D comparison of simplified piping network structures. (Mainly for design element “Pipe
Branch”)
In the Component Rules group, rules are set up to specify which end components for a SCBRANCHs
are to result in SCBRANCHs with those end components (e.g. drains and end caps) being excluded
from line lists.
8.1.1 Creating LLENTRY Rule for SCPLINE –Worked Example
This is used to Used to set up rules which specifies SCPLINES to be excluded from line lists
to specify which SCPLINEs are to be excluded from line lists.
For example, if “trim pipes” are to be excluded from line lists, and in the project the element name attribute
identifies which SCPLINEs are trim pipes, the following rule could be set up as shown:
The Schematic Explorer containing Scpline with attribute

name “Trim”
www.aveva.com
To create the rule,
right-click on a rule group folder (SCPLINE Rules) and select the Create option from the sub-
menu.
A new rule with the default name of New Rule is

then created.
In the Name field Enter Exclude Trim Pipe
In the Attribute Filters section, add a filter by selecting Add filter and specify which attributes attribute
conditions required for Schematic branch (SCBRANCH) exclusions excluded.
In the Attribute Field from the dropdown list

select NAME
In the Operator, select the required operator

Starts with
in the Value field Enter /Trim
To close the dialog and save changes made to line list configuration, press the OK button
8.1.2 Creating LLENTRY Rule for SCBRANCH –Worked Example
In the SCBRANCH Rules group, rules are set up to specify which SCBRANCHs are to be excluded from line
lists. For example if the pipeline branches which are bypasses are to be excluded from the line list
www.aveva.com
To add the new rule, right-click on the SCBRANCH rule group folder Select the Create option from the menu
A new rule with the default name of New

Rule is then created.
In the Name field Enter Exclude Bypass

Pipes
In the Attribute Filters section, add a filter by selecting Add filter and specify which attributes are to result in a
SCBRANCH being excluded
Set Attribute to FUNC
Set Operator to Equals
Set Value to Bypass
To close the dialog and save changes made to line list configuration, press the OK button.
8.2 Line List From and To (LLFROM/LLTO) Configuration
Under the LLFROM/TO node in the tree-view, there are five rule group nodes: SCPLINE, PIPE
SCBRANCH, BRANCH and Component Rules
In the SCPLINE Rules group, rules are set up to specify which text is to
be used to identify the ‘From’ and ‘To’ attribute values
values of SCPLINEs in line lists.
www.aveva.com
In the PIPE Rules group, rules are set up to specify which text is to be used to identify the From and To
values of PIPE in line lists and comparisons.
In the SCBRANCH Rules group, rules are set up to specify which text is to be used to identify the
‘From’ and ‘To’ attribute values of SCBRANCHs in line lists
The SCBRANCH Rules are only applied to SCBRANCHs with no components, or if there are no
Component Rules.
In the BRANCH Rules group, rules are set up to specify which text is to be used to identify the From and To
values of BRANCHs in line lists and comparisons.
The BRANCH Rules are only applied to BRANCHs with no components, or if there are no
Component Rules.
In the Component Rules group, rules are set up to derive the text is to be used to identify the From and To
values of SCBRANCHs or BRANCHs from the attributes of the first/last components on branches.
8.2.1 Creating LLFROM /LLTO Rule for SCBRANCH –Worked Example
In the SCBRANCH Rules group, rules are set up to specify which text is to be used to identify the From and
To values of SCBRANCH in line lists as shown below:
In the Attribute field, select whether the rule will define the “From” text, the “To” text or both. In this case
select LLFROM and LLTO.
Enter the name of the rule in the Name field. In this case enter
Schematic Branch Rule
www.aveva.com
In the PML Expression field, enter a PML expression which will generate the SCBRANCH
Texts for the ‘From’ / ‘To’ attributes In this case enter Name
If the rule is only to be applied to SCBRANCHs with specific attribute values, a filter can be set up
in the Rule Filters section
To close the dialog and save changes made to line list configuration, press the OK button.
8.3 Line List Diagram (LLDIAGRAMS) Configuration
In the the LLDIAGRAMS Rules group, rules are set up to define how diagram names are presented in line
lists. The character that separates multiple diagram names in line lists may also be specified if required
8.3.1 Creating LLDIAGRAMs Rule – Worked Example
In the LLDIAGRAMS Rules group, rules are set up to specify which diagram names are presented in line
lists and character that separates multiple diagram names in line lists
To enter character that separates multiple diagram names in line lists. Select the LLDIAGRAMS node itself.
Enter the required character in the Separators field in the Rule Properties section
In the Separator Field enter

comma (,)
www.aveva.com
Enter the name of the rule in the Name field. In this case enter All Diagrams
In the PML Expression field, enter a PML expression which will generate the diagram names from the
attributes of the diagrams (SCDIAG elements). In this example enter NAME
If the rule is only to be applied to SCDIAGs with specific attribute values, a filter can be set up in the
Rule Filters section.
Using the standard PDMS/Marine Search facility, users may retrieve and view the line list of the project,
derived from imported schematic data using the user defined rules.
Supplied Rules
The following rules are supplied with the product:
Unset HREF/TREF Components: If a branch is unconnected and ends on a component, then

the DESC attribute is output as the LLFROM or LLTO attribute
Unset HREF/TREF SCTUBING: If a branch ends with an SCTUB, then the text 'Open Pipe' is
output for the LLFROM or LLTO attribute.
HREF/TREF Components: If a branch terminates at a component of another SCPLINE, then
the name of the SCPLINE is provided as the LLFROM or LLTO attribute value.
SCNOZZLEs: the name of the owning equipment is output with the nozzle name in brackets.
Equipment: the name of the Equipment is output with its DESC attribute in brackets.
Offline Instruments: The name of the instrument is output with the DESC attribute in brackets.
www.aveva.com
Exercise 7 – Line List Rules Configuration
Create LLENTRY Component rules to exclude SCBRANCHs from line lists based on piping
component “END CAP”.
www.aveva.com
CHAPTER 9
9 Schematic Model Viewer Icons Configuration
9.1 Schematic Model Viewer Overview
The Schematic Model Viewer provides the user with the ability to view and navigate the contents of the
schematic model database based on physical connections rather than logical connections (database
hierarchy) or diagram layout.
It provides a continuous navigable view of equipment items and the interconnecting piping networks,
independently of which system they belong to or which P&ID they have been drafted on.
The Schematic Model Viewer is implemented as a Common Application Framework (CAF) Add-In, meaning
that it can be hosted by different applications. The viewer requires access to a Schematic Database as part
of the current MDB.
9.2 Schematic Model Viewer Icons
The icons used to represent the equipment, generic branch points and inline fittings are determined by a set
of user configurable rules. These rules are stored in an XML file, called SchematicSymbols.xml which is
located in the PDMS installation directory
www.aveva.com
Below is an example of the .xml file. By editing this file the user can assign different icons based upon
element type and attribute value rules.
In the above example any equipment item not defined in the ‘attribute’ section will be assigned the
default Equip.png icon.
Icon files are stored in the %PMLLIB%\icons\SchematicModelViewer\directory
Users can add new icons, or modify the existing ones. For the creation of new icons, it is
recommended, it is recommended to follow the steps below:
– Review supplied icons to get an indication of size and format of icons.
– Save the newly created icons into %PMLLIB%\icons\SchematicModelViewer directory
www.aveva.com
Edit the SchematicSymbols.XMLfile file to make use of your new icons.
For example to assign the icon file COLM.PNG to the equipment type “COLUMN”
The following line shown in red colour below must be added to the SCEQUIPMENT section in the
SchematicSymbols.XMLfile.
As shown below:
<element type="SCEQUIPMENT">
<default-icon icon="Equip.png"/>
<Symbol attribute-name="Description" attribute-value="COLUMN"
icon="COLM.png" sten-name="" shape-name=""/>
For changes to be recognised PDMS must be restarted or Modules switched.
www.aveva.com
Exercise 8 – Schematic Model Viewer Icon Configuration
1. Log in to PDMS Disign and drag an equipment element into the 3D View, take a screen shot of the
equipment and then reduce the image size and save the image as a .png file
2. Modify /update the SchematicSymbols.XML file with the equipment details.
www.aveva.com
CHAPTER 10
10 Highlight Changes Attributes Compare Configuration
Attribute Compare Configurations contains default set of attribute mappings to be used for comparing
elements between specified sessions. The attribute configuration setting is accessed by selecting the
Attribute Configuration icon from Diagram Change Highlighting main toolbar. As shown highlighted:
“Default Settings” will be the only option available, unless a user specific or project specific
mapping has been saved using “Attribute Configuration” dialog.
The attribute configuration setting can also be accessed by selecting Diagram Change Highligting icon
from the Diagram Viewer main toolbar as shown.
www.aveva.com
10.1 Attribute Compare Configurations – Worked Example
Using Attribute Configurations dialog, setup an attribute compare Configurations mapping for element
type Schematic Pipeline (SCPLINE)
To do this;
First, click on the Attribute Configuration icon from

Diagram Change Highlighting toolbar to display the
Attribute Configuration dialog.
Click on the Element Type pull-down window and select desired element type, in this case SCPLINE from
the list as shown;
Select desired attributes name checkboxes, by clicking on corresponding attribute name check-box from the
“Include in Comparison” column as shown:
Alternatively selecting the checkbox in the

first row of “Include in Comparison” column
will select all the attributes checkboxes for the
selected element type. And click on the
checkbox again will de-select all the attributes
checkboxes for the selected element type,
www.aveva.com
To review only the selected attributes, click on the filter icon in

the first row of the“Include in Comparison” column to display
attributes as shown
Modified configuration needs to be saved as a “User Preference” or “Project Preference”, which will
become the default, in this example select “Save as a “User Preference”.
Save as a User Preference attribute configurations are stored in local settings and Save as a
Project Preference configurations are stored in project folder.
Click on the OK button as highlighted to

save the configuration settings
Selecting the OK button will automatically display the saved options option (in this case “User Settings”) in
the “Attribute Compare Configurations” drop down as highlighted below.
After changing the mappings, click on the Refresh button to redo the comparison using modified
mappings. This re-runs the diagram comparison, using the newly configured attribute settings.
www.aveva.com
Default Settings” will be the only option available, unless a user or project specific mapping has
been setup and saved.
10.2 Highlight Colour Configurations
Highlight changes option contains default set of colour settings used for indicating comparison results, by
highlighting affected elements (added / deleted / modified) on a compared diagram.
.
The Highlight Colour configuration dialog is accessed by selecting the Highlight Colour Configuration
icon from Diagram Change Highlighting main toolbar as highlighted below.
10.2.1 Highlight Colour Configuration – Worked Example
Using Highlight Colour Configuration dialog modify the default highlight colour setting for “items Deleted”
To do this;
First, click on Highlight Colour Configuration icon from Diagram Change Highlighting main toolbar as
shown in section 10.2 to display the Highlight Colour Configuration dialog.
www.aveva.com
Click on the Highlight Category Colour row, in this case “Items Deleted” Colour row to display “Colour
Selector” dialog.
Click on the desired colour in this example “Red” colour from the Colour Selector form
Then click on the Dismiss button to the close the Colour

Selector dialog.
The Highlight Colour Configuration dialog will automatically display the selected colour for highlighting
deleted items.
www.aveva.com
Exercise 9 – Highlight Changes Attribute compare Configuration
1. Using Attribute Configurations dialog, setup attribute compare Configurations mapping for element
type Schematic Branch (SCBRANCH), using the listed attributes shown below:
2. Using Highlight Colour Configuration dialog change the default colour setting for the entries listed
- New Items Added Colour to Blue.
- Items Modified Colour to Green.
www.aveva.com
CHAPTER 11
11 Status Control Configuration For Schematic Elements
Status Control enables the user to control and report on the status of individual model objects as they
progress through their lifecycles. It can be applied to any model objects, e.g. tagged items, catalogue
components, drawings.
For further details on Status Control, please refer to Status Control User Guide.
11.1 Status Control Configuration - Overview
P&IDs will typically go through several revision stages during its development. The example shown utilizes a
simplified lifecycle.
Although the example shown concerns the status control of a P&ID (Diagrams), however status definitions
can be created for any schematic element if required.
To create a Status Control for the revision stages of a P&ID as shown in the example workflow below, users
must first setup status control configuration in LEXICON module. Lexicon uses Status World, Status Definition
and status Value data types to define the status of an object.
www.aveva.com
11.1.1 Status Control Setup for Schematic Diagrams – Worked Example
To set up a status control definition for diagram shown in section 11.1, a number of procedures must first be
completed in LEXICON Module as listed below:
Creation of Status Configuration World
Creation of Status Definition
Creation of Status Value
The stated or procedures will be discussed in details and with work example in subsequent sections.
11.1.1.1 Create Status Configuration World
Right-click on the Dictionary World to display the right-click menu. Then select New Status Configuration
World from Create option sub-menu.
A new status world is then created and Current Element Editor dialog is also displayed as shown below.
www.aveva.com
In the Current Element Editor dialog, enter SchematicStatusManagement in the Name Field and enter
Status definitions for schematic data in the Description Field as shown:
The name field entered must not contain any space, but the description field can contain spaces
11.1.1.2 Create Status Definition
In the Explorer, select the newly created Status World “SchematicStatusManagement” right click and
select Status Definition from Create option sub-menu.
A new status Definition is then created and Current Element Editor dialog is also displayed as shown
www.aveva.com
In the Current Element Editor dialog shown
Enter PIDStatusManagement in the Name field
Enter Status Management for Reversion in the

Description field.
Then set the Controllable element types field that status definitions are to be applied. Select the browse
icon, to the display the Select Element Type dialog
In Select Element Type dialog enter SCDIAG in the Filter field, then select SCDIAGRAM and double click
on it . The Chosen Element Type section of the dialog is then automaticaly populated with the selected
element type.
www.aveva.com
From the Select Element Type dialog, click OK button to add the selected element type to the Controllable
element type field
The user can add other element types if the definition is required apply to multiply types of
elements.
11.1.1.3 Create Status Value
Select the newly created Status Definition “PIDStatusManagement” right click and select Status Value
from Create option sub-menu
A new status value is then created and Current Element Editor dialog is displayed as shown
www.aveva.com
In the Current Element Editor dialog,
Enter RevisionA in the Name field
Enter Issued to Engineer for check and comment in the Description field.
In the Numerical Value field enter 5,
Using the same process create additional Status Values using the listed information provided below.
Name Description Numerical Value
EquipmentReview Major Equipment items Review 30

ConnectivityReview Connectivity from P&ID to P&ID Checks 45
RevisionB Issued for Approval 55
ProcessFlowReview P&ID Process Flow Review 65
LineLabelReview Line numbers, insulation and tracing Specs Review 75
CommentReview Client's comment Review 95
Revision0 Approved for Design 100
The Entry of a numerical value is optional and may be a percentage or a simple value
The name of a Status value is only unique within its parent status definition. Users can use repeat
names such as Preliminary and Released in different deferent definitions.
www.aveva.com
11.1.1.4 Setting Status Value Transition
For each newly created Status Value, a valid transition route is required.
To setup the transition, select the require Status Value from the Dictionary Explorer in this case “RevisionA”
as shown:
In the Current Element Editor dialog, select Valid Status Transitions field. Click on the browse button
Select Valid Status Transitions window will be display.
Then Set the required valid transitions for the selected Status Value. In this example select
EquipmentReview for Status value RevisionA, and click the OK button as shown below
www.aveva.com
In the drop down selection for Promote select the appropriate values as shown below. The Demote Field
should remain unset.
Promote and demote are optional and simply denote a main route through the workflow, any valid
transitions not marked as promote or demote will still be available in the Status Controller.
Using the same process as described above and the information listed below, set valid transition, Promote
and Demote field for each Status Value create in section 9.1.1.3.
Status Value Valid Transitions Promote Demote
EquipmentReview ConnectivityReview & RevisionA ConnectivityReview RevisionA

ConnectivityReview RevisionA & RevisionB RevisionB RevisionA
RevisionB ProcessFlowReview & RevisionA ProcessFlowReview RevisionA
ProcessFlowReview LineLabelReview & RevisionB LineLabelReview RevisionB
LineLabelReview CommentReview & RevisionB CommentReview RevisionB
CommentReview Revision0 & RevisionB Revision0 RevisionB
Revision0 No transitions from Revision 0
It is assumed that the status management in this example ends at Revision0, therefore are no
transitions from Rev 0
www.aveva.com
Right-click on the defined Status definition or Status Value and select Graphical View from the right-click
menu .The Graphical View form is then displayed as shown
For further details on Graphical View, please refer to

Lexicon User Guide.
At the conclusion of the setup of ‘Valid Transitions’, the administrator needs to select Lexicon > Save Work,
a confirm form appears, click the Yes button to confirm.
www.aveva.com
Exercise 10 – Status Control Configuration
1. Using the diagram below create Status Control definition for Schematic Equipments
www.aveva.com
Appendix A
Appendix A
ISO 15926 Generic Types
Listed below is a sample list of ISO 15926 Item Types and the associated GTYPE / SCTYPE values.
ISO 15926 Description GTYPE SCTYPE

ACTIVATED CARBON FILTER FILT
ANGLE GLOBE VALVE VALV GLOB
ANGLE VALVE VALV
BAG FILTER FILT BAG
BALL VALVE VALV BALL
BASKET STRAINER FILT
BELLOWS PCOM EX
BLIND FLANGE FBLI
BUTTERFLY VALVE VALV BFLY
CAP CAP
CARTRIDGE FILTER FILT CART
CHECK VALVE VALV CHK
CLOSED GLOBE VALVE VALV GLOB
COLUMN
CONCENTRIC REDUCER REDU CONC
CONTROL VALVE INST CV
DIAPHRAGM ACTUATED BALL VALVE VALV CV
DIAPHRAGM ACTUATED GENERAL VALVE VALV CV
DIAPHRAGM VALVE VALV DIA
DIVERTER VALVE VALV DIV
DUPLEX STRAINER FILT
ECCENTRIC REDUCER REDU ECC
EXCESS FLOW VALVE VALV
EXPANSION JOINT PCOM EX
FILTER FILT
FLAME ARRESTOR PCOM FT
FLANGE FLAN
FLANGED NOZZLE
FOUR WAY VALVE VFWA
FUNNEL PCOM TU
GATE VALVE VALV GATE
GLOBE VALVE VALV GLOB
INSTRUMENT INDICATOR
LIFT CHECK VALVE VALV CHK
NEEDLE VALVE VALV
NOZZLE NOZZ
ORIFICE PLATE INST OP
PARALLEL SLIDE VALVE VALV SLIDE
PILOT OPERATED RELIEF VALVE VALV RV
PINCH VALVE VALV PINCH
PIPE CONNECTION FLAG (FORWARD)
PIPE CONNECTION FLAG (IN-BOUND)
PIPE CONNECTION FLAG (OUT-BOUND)
PIPE TEE TEE www.aveva.com
PLUG PCOM PL
PLUG VALVE VALV PLUG
PRESSURE RELIEF VALVE VALV RV
PRIMARY LINE SEGMENT
RELIEF VALVE VALV RV
ROTARY VALVE VALV ROTARY
RUPTURE DISC INST DR
SAFETY VALVE VALV
SIGHT FLOW INDICATOR PCOM SG
SIGHT GLASS PCOM SG
SPECTACLE BLIND PCOM SB
STEAM TRAP TRAP
STOP CHECK VALVE VALV CHK
STRAINER FILT
SWING CHECK VALVE VALV CHK
THREE WAY BALL VALVE VALV
THREE WAY VALVE VTWA
VACUUM RELIEF VALVE VALV RV
VALVE VALV
VERTICAL PUMP
For more information please refer to ISO 15926 or http://www.w3.org/ or http://www.iso.org/iso/
www.aveva.com
Appendix B
Appendix B
Generic Types (Piping Components)
GTYPE - a word attribute indicating the generic type of the PDMS Piping Component, selected from the
following list. Selected choice should consider 3D activities and output.
For more information please refer to the PDMS 12 Isodraft Admin Guide.
ATTA attachment
BEND pipe bend
CAP end cap
CLOS closure
COUP coupling
CROS cross piece
DUCT ducting
ELBO fitting elbow
FBLI blind flange
FILT filter
FLAN or FLG flange
FTUB fixed length tube
GASK gasket
HELE hanger element
INST instrument
INSU insulation
LJSE lap joint stub end
NOZZ nozzle
OLET weldolets
PCOM pipe component
REDU reducer
SHU standard hook-up
TEE fitting tee
TRAC tracing
TRAP steam trap
TUBE implied tube
UNIO union
VALV valve
VENT open-ended pipe or vent
VFWA four-way valve
VTWA three-way valve
WELD weld
www.aveva.com
Appendix C
Appendix C
Schematic Model Manager UDA’s
List Schematic Model Manager User Defined Attributes;
PMGID Source data ID attribute

PMGPersistentId1 Source system ID attribute
PMGPersistentIdCtxt1 Source system ID context
PMGDiscipline Discipline
PMGRating Rating
PMGStandard Standard
PMGISOSymbol ISO Symbol
PMGNozzleType Type of Nozzle
PMGHeight Height of Nozzle
PMGConnectionType Connection Type
PMGOperatorType Operator Type
PMGFabricationCategory Fabrication Category
PMGNominalDiameter Nominal Diameter
PMGNormalDesignPressure Normal Design Pressure
PMGMinimumDesignPressure Minimum Design Pressure
PMGMaximumDesignPressure Maximum Design Pressure
PMGNormalDesignTemperature Normal Design Temperature
PMGMaximumDesignTemperature Maximum Design Temperature
PMGMinimumDesignTemperature Minimum Design Temperature
PMGMinimumOperatingPressure Minimum Operating Pressure
PMGMaximumOperatingPressure Maximum Operating Pressure
PMGMinimumOperatingTemperature Minimum Operating Temperature
PMGMaximumOperatingTemperature Maximum Operating Temperature
PMGDescription Description
PMGComponentType Component Type
PMGRevision Revision
PMGTitle Title
PMGSize Size
PMGModTime Update Time
PMGFilename Filename
PMGDiagram Diagram Name
PMGStatus Status
PMGTag Tag
PMGSpecification Specification
PMGStockNumber Stocknum
PMGComponentClass Component Class
PMGComponentName Component Name
PMGTransactionType Last Transaction Type
PMGTransactionDate Last Transaction Date
PMGTransactionTime Last Transaction Time
PMGTransactionPerson Last Transaction Person www.aveva.com
© Copyright 1974 to current year.
AVEVA Solutions Limited and its subsidiaries. 100
PMGTransactionCompany Last Transaction Company

PMGSupplier Supplier
PMGManufacturer Manufacturer
PMGOutsideDiameter Outside Diameter
PMGStartDiameter Start Diameter
PMGNormalOperatingPressure Normal Operating Pressure
PMGNormalOperatingTemperature Normal Operating Temperature
PMGTestPressure Test Pressure
PMGWallThickness Wall Thickness
PMGWeight Weight
PMGMaterial Material
PMGMaterialDescription Material Description
PMGModelNumber Model Number
PMGDiameter Diameter
PMGInsideDiameter Inside Diameter
PMGPCDiagram Diagram Name of matching Connector
PMGPCAttribute Attribute Name for matching Connector
PMGPCValue Attribute value used to match Connector
PMGPCAttScope Scope qualifier for Pcattribute
PMGDefaultMatch Default placeholder for page matching values
www.aveva.com
Appendix D
Appendix D
XPath Expressions
XPath Expressions can be used when mapping system/project specific attributes from the source files to
schematic or user defined database attributes. See XPath Expression Builder Dialog.
This Appendix provides a brief guide to the use of XPath Expressions. For further information refer to:
http://www.w3.org/TR/xpath.
Within an Expression:
XML element names are represented in their simplest form as the tag name, e.g. <MyElement>
is represented as MyElement.
XML attribute names in their simplest form are prefixed with the @ character, e.g. the attribute
MyAttribute=”value” is represented as @MyAttribute
An expression is built up from a series of these LocationPaths separated by the ‘/’ character. For
example the attribute from <MyElement @MyAttribute /> may be obtained using
MyElement/@MyAttribute
More complex LocationPaths exist, such as:
www.aveva.com
© Copyright 1974 to current year.
AVEVA Solutions Limited and its subsidiaries. 102
Predicates can be added to each LocationPath in order to further constrain the selected nodes. Predicates
are enclosed inside ‘[‘ and ‘]’ characters. For example:
www.aveva.com

TM-3542 AVEVA Plant (12.1) Schematic Model Manager (Administration) Rev 3.0

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TM-3542 AVEVA Plant (12.1) Schematic Model Manager (Administration) Rev 3.0

Hochgeladen von

Copyright:

Verfügbare Formate

AVEVA Plant

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

Unauthorised or unlicensed use of the software is strictly prohibited.

Printed by AVEVA Solutions on 17 April 2012

© AVEVA Solutions and its subsidiaries 2001 – 2012

8 Line List Rules Configuration ............................................................................................................... 69

This training course requires;

PDMS and Schematic Model Manager to be installed correctly and working

1.4 Course Structure

1.5 Using this guide

2.1 Environment Setup

2.2 Module Definition Configuration

Open the ADMIN module.

2.3 Schematic Database Setup – Worked Example

AVEVA PDMS login box will then be displayed

In the Project field, select the pulldown

In the Username textbox Enter

In the Password textbox Enter

From the Owning Team grid select <TEAM>SAMPLE

In the optional Description textbox enter

Name and Description are basic alpha-

In Create SCGROU textbox enter

Entering a value in this field creates a

“Create SCGROU” is displayed if Schematic

From the Database Type option list. Select

After entering the necessary information,

Click the Apply button; this will complete the

Then click the Dismiss button to close the dialog.

The SCHE DB(s) must be writable.

2.4 Dictionary Database Setup

It is also necessary that a Dictionary database is created for the

This will usually be created by the system administrator in

2.5 Multiple Database (MDB) Setup

At least one SCHE

2.6 Schematic Model Manager UDA’s Configuration – Worked Example

AVEVA Lexicon login box will then be displayed as shown:

In the Project field, select the pulldown

In the Username textbox Enter SYSTEM

In the Password textbox Enter XXXXXX in

Lexicon Module will be displayed as shown:

All Schematic Model Manager UDA’s are prefixed

Click the Deselect All button - To uncheck the

Click the Undo button - to undo any changes in the

To configure required UDA’s, select the

The greyed out UDA’s are mandatory for the

If the UDA is present in the schematic

If the UDA is present in the schemnatic

The UDA configuration complete form will be displayed.

Click the Dismiss button and then the Savework

Exercise 1 – Administrative Setup

Create a Schematic Database to store imported P&ID data.

3 Schematic Model Manager Project and User Options Configuration

3.1 Entering AVEVA Schematic Model Manager

In the Project field, select the pulldown

In the Username textbox Enter SYSTEM

In the Password textbox Enter XXXXXX in

A default screen layout will then be displayed

3.2 Project Options Setup

To access the Project Options dialog

The Project Options dialog consists of three tabs,

Element Release Tab

3.2.1 Element Release Tab

3.2.1.1 Updates to Existing Released Elements

The release status of previously imported elements is retained. (Default setting).