PID Manager User Guide

P&ID Manager
User Guide
AVEVA Solutions Ltd
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.
Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
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 AVEVA Solutions Ltd or its subsidiaries.
All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective licence agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
First published November 2007.
© AVEVA Solutions Ltd, and its subsidiaries.
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
P&ID Manager User Guide
Contents
Contents Page
P&ID Manager
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
AVEVA P&ID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Accessing P&ID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
LEXICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Pre-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Module Definition Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
UDA Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Mapping Set-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
GTYPE Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Attribute Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Page Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Attribute Derivation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
P&ID Manager Project Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Element Release Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3
Set Release Behaviour of Elements on Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3
Display Comments Dialog on Release to 3D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
Copying P&ID Manager Options from another Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6
Exporting P&ID Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
i 12.0
Contents
Importing P&ID Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7

Restore Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Import Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Viewing/Editing Import Destination SCGROUP Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Viewing/Editing Equipment and Off Line Instrument Positions . . . . . . . . . . . . . . . . . . . . . 3:10
Units Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:11
P&ID Manager User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Import Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Set Default Import Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Set Default Export Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Viewing/Editing Attribute Derivation Rules . . . . . . . . . . . . . . . . . . . 5:1

Selecting Rules to be Applied During Import . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Creating/Editing Rule Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4
Creating/Editing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5
Creating a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5
Rule Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9
Editing a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10
Moving Rules and Rule Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10
Deleting Rules and Rule Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10
Viewing/Editing Attribute Mappings . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Default Attribute Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:3
Creating Attribute Mapping Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:3
Creating Attribute Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5
XPath Expression Builder Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8
Source Dictionary Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:9
Shortcuts, XPath Operators and XPath Functions Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . 6:10
Expression Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12
Setting up Mappings Using the Xpath Expression Builder Dialog - Examples. . . . . . . . . . 6:12
Automatic Setting of Attribute Units and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:20
Accessing the Source Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:21
Editing, Moving and Deleting Mapping Groups and Mappings . . . . . . . . . . . . 6:22
Editing Mapping Groups and Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22
ii 12.0
Contents
Moving Mapping Groups and Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22

Deleting Mapping Groups and Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22
Viewing/Editing GTYPE Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Import Designations from File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3
Conflict Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4
Completing the Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:5
Setting up Rules for Automatic Completion of ISO 15926 Mappings . . . . . . . 7:5
Automatically Completing ISO 15926 Mappings . . . . . . . . . . . . . . . . . . . . . . . . 7:7
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7
Import Designations from other Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:8
Overwrite Mappings in Databases with Current Mappings . . . . . . . . . . . . . . . . 7:9
Configuring the Source Data Dictionary . . . . . . . . . . . . . . . . . . . . . 8:1

Accessing the Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Resetting the Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Populating or Updating the Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3
Previewing Diagrams before Import . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

Selecting Diagrams to Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
P&ID Manager Diagram Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3
Diagram Viewer Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4
Keyboard Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:5
Closing Diagrams and the Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:5
Importing Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1

Import Diagrams Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1
Diagram Set Import Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3
Creating Diagram Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:3
Entering Release Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:9
Importing Diagram Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:10
Closing the Diagram Set Editor without Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:11
Import Progress Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:11
Additional Import Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:12
Automatic Matching of Off-Page Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:13
Importing using PML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:14
Preliminaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:14
Importing Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:15
iii 12.0
Contents
Saving Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:18
P&ID Manager Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1

Opening the P&ID Manager Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
Element Hierarchy in the Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
Using the Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:5
Element Right-Click Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:5
Applying a Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:7
Viewing Element Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:7
Creating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:8
Deleting Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:9
Renaming Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:10
Moving Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:11
Viewing Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:11
Setting-up and Editing Off-Page Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:11
Releasing and Unreleasing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:12
Saving Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:13
Viewing Imported Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1

Selecting Diagrams to View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1
P&ID Manager Diagram Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:4
Highlighting and Selecting Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:4
Diagram Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:5
Other Viewer Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:6
Diagram Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1

Diagram Connector Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Selecting or Changing the Source Off-page Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Setting up a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3
Connection Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:5
Editing a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:6
Standard Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1

Using the Standard Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1
Search Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:2
P&ID Manager Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:1

P&ID Manager in LEXICON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1
Opening the LEXICON Module with P&ID Manager Installed. . . . . . . . . . . . . . 16:1
iv 12.0
Contents
Configuring UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1

UDA Catalogue Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:3
Viewing and Editing UDA Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:5
Viewing/Editing Attribute Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:5
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1
Appendix A: Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1
Alternation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1
Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:1
Quantification using Metacharacters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:2
Regular Expression Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:6
Appendix B: Releasing to 3D and the Schematic Database . . . . . . . . . . . . . . 17:8
Appendix C: XPath Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:9
Appendix D: Diagram Set File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:11
XML File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:11
Text File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17:13
v 12.0
Contents
vi 12.0
Introduction
1 Introduction
1.1 AVEVA P&ID Manager

AVEVA P&ID Manager is an add-in to PDMS 12.0 and is used to import P&ID data into
PDMS Schematic databases. The P&ID data is imported from an XML file, the content of
which complies with ISO 15926. The ISO 15926 data may be exported from AVEVA P&ID
Manager Gateway, AVEVA P&ID and from other supported P&ID systems.
AVEVA are committed to the use of open standards for the interchange of plant data
between AVEVA and 3rd party products. ISO 15926 is an open standard for the
representation of process plant life-cycle information. This representation is specified by a
generic, conceptual data model designed to be used in conjunction with reference data:
standard instances that represent information common to a number of users, process
plants, or both. For further information and for details of what P&ID systems can feed data
into the PDMS Schematic model through AVEVA P&ID Manager, contact your local AVEVA
sales office.
Once imported, P&ID data in the schematic database can be viewed and managed via a
hierarchical data explorer (P&ID Manager Explorer). This explorer includes facilities for
releasing selected schematic elements to the AVEVA Schematic 3D Integrator, for
integration with the 3D Design Model database. Facilities are also provided to view P&IDs,
both before and after import, using the Adobe SVG Viewer (Version 3.0.2). A set of standard
PDMS report templates which report against the schematic database are also included.
P&ID Manager facilities are available in both the DESIGN and LEXICON modules of PDMS.
For pre-configuration details, i.e. details of procedures that should be completed before
starting to use P&ID Manager, see Section 2: Pre-configuration.
1:1 12.0
Introduction
1.2 Accessing P&ID Manager
1.2.1 DESIGN
When P&ID Manager is installed, an additional option is displayed in the main DESIGN
menu bar:
The P&ID Manager menu consists of four main functional groups:

• The File sub-menu is used to view previews of the P&IDs available to be imported, and
to carry out imports. See Section 9: Previewing Diagrams before Import and Section
10: Importing Diagrams.
• The Tools sub-menu provides access to various dialogs, which are used to specify how
P&ID Manager operates.
See:
• Section 3: P&ID Manager Project Options.
1:2 12.0
Introduction
• Section 4: P&ID Manager User Options.

• Section 5: Viewing/Editing Attribute Derivation Rules.
• Section 6: Viewing/Editing Attribute Mappings.
• Section 7: Viewing/Editing GTYPE Mappings.
• Section 8: Configuring the Source Data Dictionary.
The Tools sub menu also provides access to the Diagram Connector, which is used to
manually connect page connectors between imported diagrams. See Section 13:
Diagram Connector.
• The Display sub-menu is used to view imported data in a hierarchical data Explorer,
and to view imported P&IDs. See Section 11: P&ID Manager Explorer and Section 12:
Viewing Imported Diagrams.
P&ID Manager adds a series of standard P&ID Searches to the saved searches section of
the PDMS Design Module Search Utility. See Section 14: Standard Searches.
A number of reports can be run on the Schematic Database. For further details, see Section
15: P&ID Manager Reports.
1.2.2 LEXICON
When P&ID Manager is installed, an additional option is displayed in the main LEXICON
menu bar:
• The UDA Catalogue option is used to specify which User Defined Attributes (UDAs) are
available in each schematic database with which P&ID Manager operates, and to
maintain the Attribute Mappings associated with the UDAs.
• The Attribute Mappings option is used to map system/project specific attributes from
the source files to schematic attributes or UDAs.
For details, refer to Section 16: P&ID Manager in LEXICON.
1:3 12.0
Introduction
1:4 12.0
Pre-configuration
2 Pre-configuration
2.1 Post Installation Tasks
2.1.1 Module Definition Configuration

In order to use P&ID Manager it must be possible to write to the Schematic databases from
within the DESIGN module. This can be configured by changing the module definition within
the PDMS ADMIN module as follows:
1. Open the ADMIN module.
2. Select Module definitions… from the Project menu.
3. Select the Design module and then click on Advanced Settings…
4. Set the Schematic database mode to Read/Write.
5. Click on Apply, close the dialog and select Save Work from the Admin menu.
2.1.2 Database Configuration

P&ID Manager requires at least one Schematic database in the MDB being used.
To make full use of the features available in P&ID Manager it is also recommended that a
Dictionary database is created for the definition of the default P&ID Manager UDAs.
2.1.3 UDA Creation

P&ID Manager makes use of UDAs to store additional attribution from the source ISO 15926
files. Of particular importance are the UDAs used to store information about page
connectivity and source system persistent identities. The UDAs should be added to the
MDB as follows:
1. Create a Dictionary database and ensure it is part of the MDB in use.
2. Open the LEXICON Module.
3. Select UDA Catalogue... from the P&ID Manager menu.
4. Select Apply from the UDA Catalogue dialogue.
5. Select Save Work from the LEXICON menu.
See Section 16.2: Configuring UDAs for further information on maintaining P&ID Manager
defined UDAs.
Creating the required UDAs in this way will automatically add the required attribute
mappings associated with the chosen UDAs.
2:1 12.0
Pre-configuration
When upgrading from a previous version of P&ID Manager you should re-run this activity
with the new version. This is to ensure that your schematic database contains any new
UDAs required by P&ID Manager.
2.2 Mapping Set-Up

AVEVA P&ID Manager includes a default set of GTYPE and attribute mappings. These are
intended to give a reasonable starting point for the use of P&ID Manager, but will need to be
assessed for each project, and amended or added to where appropriate. P&ID Manager
provides tools which help in this task. See Section 3.3: Import Configuration Tab.
2.2.1 GTYPE Mapping

The default GTYPE mappings map a commonly used set of ISO15926 classifications to
their corresponding GTYPE and SCSTYPE in the AVEVA P&ID schematic database.
The GTYPE mappings can be configured before importing any data, either manually or by
analysis of a set of source files, or may be configured after importing the data by analysing
the database(s). Once the mappings have been edited any data in the schematic databases
may have the mappings re-applied in order to update their attribution. Please see Section
3.3.1: Viewing/Editing Import Destination SCGROUP Elements.
The GTYPE and SCSTYPE attributes may also be set using the Attribute Mappings. Where
GTYPE and SCSTYPE are configured in AVEVA P&ID these will be loaded automatically
using the default attribute mappings without the GTYPE Mappings being configured.
GTYPEs and SCSTYPE attributes set by the attribute mappings or derivation rules will
override the GTYPE mappings.
2.2.2 Attribute Mapping

Attribute mappings should be configured before loading data as any changes to the
mappings will require the data to be updated (re-imported) in order for them to take effect.
Attribute mappings are crucial to the page matching process and must be correctly
configured for diagrams to be matched and merged.
If using the default UDAs then all of the core attributes from the source data should already
be populated, but system specific attributes stored within the GenericAttributes elements in
the import files will not be present. To configure your attribute mappings see Section 6:
Viewing/Editing Attribute Mappings.
The source data may use system specific attributes in order to specify how segments are
connected across diagrams. If the source data has been generated using AVEVA P&ID, and
the P&ID Manager default attribute mappings relating to the SCOPCI and SCOPCO
schematic database elements have not been amended, then additional cross-page
connectivity related attribute mappings will not be required. Attribute mappings for matching
page connections are provided pre-configured for this source tool.
However, if the source data was generated from an alternative gateway or tool, you may
need to configure cross-page connectivity attribute mapping to ensure that cross-page
connectivity is maintained. To do this:
1. First find the values of the AttributeName attributes on the CrossPageConnection XML
elements in your source data file.
2:2 12.0
Pre-configuration
2. Open the source data file in a tool capable of displaying XML files (you will not need to
edit the contents of the source file). Find the values of the AttributeName attributes on
the CrossPageConnection XML elements.
The following example shows the CrossPageConnection element in a data source
generated by AVEVA P&ID:
In this example the AttributeName attribute of the CrossPageConnection XML element

is "PipeId".
3. Make sure that your P&ID Manager source dictionary has been populated from a file or
files which match the source data structure you will be using to load P&ID's into your
project (see 8: Configuring the Source Data Dictionary).
4. Using the attribute mapping tool, create an attribute mapping which operates on the
SCOPCI and SCOPCO schematic database elements. You may wish to use the default
attribute mapping on these elements provided when you install P&ID Manager as a
basis for your custom attribute mapping.
5. The UDA :Pmgdfltmatch has been defined for storing diagram connection attribute
values where only one attribute is used for the connection. Set the database attribute
value of your attribute mapping to :Pmgdfltmatch:
6. You now need to map the correct source data attribute to the UDA :Pmgdfltmatch, to
ensure that page matching occurs.
2:3 12.0
Pre-configuration
To do this, click the ellipsis button to the right of the attribute mapping's Source Attribute
field. This will open the XPath expression builder:
7. Navigate to the attribute used in your source data file to store cross page connectivity
matching values.
The source data attribute PipeId is used in the AVEVA P&ID Manager Gateway. The
example above shows this source attribute and its associated mapping in the Source
Dictionary window of the P&ID Manager XPath Expression Builder:
8. You have now created a mapping from this source data file attribute to the UDA
:Pmgdfltmatch.
If cross page connectivity in your source data files is represented using more than one
attribute, then it will be necessary for you to create additional UDA's against the
SCOPCI and SCOPCO schematic database elements, and to then create additional
attribute mappings to ensure that these are populated during an import.
2.2.3 Page Matching

If you encounter issues with on and off page connectors not being correctly associated then
consult Section 2.2.2: Attribute Mapping.
2:4 12.0
Pre-configuration
2.3 Attribute Derivation Rules

When attributes are imported, the values of attributes may be automatically set according to
user-defined rules based on DB Expressions, known as Attribute Derivation Rules.
Default attribute derivation rules are not shipped with P&ID Manager.
It is recommended that attribute derivation rules are configured prior to importing data into
the schematic database. This is because attribute derivation rules cannot be applied to
existing elements in the schematic database, other than by re-importing existing schematic
data from the source import file or files.
A rule is set up by selecting the element type or types to which the attribute in question
belongs. The attribute itself is then selected. The list of attributes available for selection is
restricted to those common to all the selected element types.
The DB Expression to be applied to the attribute during processing is then entered.
If required, filters may be set up to restrict the instances of elements, based on the value of
one or more of their attributes, to which the rule is applied.
Rules are grouped into rule groups. Rule groups may contain both rules and other rule
groups. As required, individual rules or an entire rule group may be “switched off”, i.e. set
that they are not applied on import.
Please see Section 5: Viewing/Editing Attribute Derivation Rules for further information.
2:5 12.0
Pre-configuration
2:6 12.0
P&ID Manager Project Options
3 P&ID Manager Project Options
The Project Options dialog is used to set P&ID Manager project settings. To access the
dialog, select the Tools > Project Options... option from the P&ID Manager menu in the
DESIGN module.
3:1 12.0
The Options dialog is then displayed.
The Project Options dialog consists of four tabs, as described below.

To save changes to the options and exit the dialog, select the OK button.
To exit the dialog without saving, select the Cancel button.
3:2 12.0
3.1 Element Release Tab
Some elements in the schematic database may be accessed by AVEVA Integrator, for
integration into the PDMS DESIGN database. Access to such elements by AVEVA
Integrator is controlled by the schematic database release status of these elements.
The Element Release tab is used to specify:
• The element release status related actions carried out during the import of an
ISO15926 file into the schematic database.
• If the Release Comment dialogue box is displayed during release related activities,
either initiated during an import or from the P&ID Manager user interface, and whether
or not date and timestamps are automatically added to the beginning of release
comments.
3.1.1 Set Release Behaviour of Elements on Import

These options define the “release behaviour” of elements on import. Release behaviour is
the course of action taken during the P&ID import process for an element category, i.e.
whether or not elements within that category are imported and the release status they are
set to if they are.
Every imported element falls into one of three categories:
• Existing elements (i.e. elements imported before) that have been released
• Existing elements that have not been released
• New elements, i.e. elements not imported before
3:3 12.0
A different release behaviour can be specified for each category of element.
Existing Elements - Released
Select from the following options:

• 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 - The elements are imported and their release
status changed to not released.
• Import and keep existing status (ON) - The elements are imported and their release
status retained, i.e. set to released.
Existing Elements - Not Released

• Import and keep existing status (OFF) - The elements are imported and their release
status retained, i.e. set to not released. Default setting.
• Import and set release status to ON - The elements are imported and their release
status changed to released
New Elements

• Set release status to OFF - The elements are imported and their release status set to
not released. Default setting
• Set release status to ON - The elements are imported and their release status set to
released.
3:4 12.0
3.1.2 Display Comments Dialog on Release to 3D

If the release comments are to be entered when data is released and unreleased to the
AVEVA Integrator, check the Enable Release Comments checkbox. If not, uncheck the
checkbox.
If the checkbox is checked, when data is released and unreleased using the P&ID Manager
Explorer, the Release Comments dialog is displayed, into which comments can be entered
(see Section 11: P&ID Manager Explorer).
Also, a Release Comments field is enabled or displayed when importing diagrams using the
UI (see Section 10: Importing Diagrams) for use when the release status of an element is
automatically changed when diagrams are imported.
To automatically add a date and timestamp to the beginning of release comment fields,
check the Add Date/Timestamp to Release Comment checkbox. This checkbox is
disabled if the Enable Release Comments checkbox is unchecked.
The date/timestamp format is as follows:
Date:[Date formatted using client regional settings]
[Hours:Mins]
Note: For further information on P&ID Manager release related behaviour, refer to Section
17.2: Appendix B: Releasing to 3D and the Schematic Database.
3.2 General Tab
The General tab is used to:
3:5 12.0
• 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.
Note: Copying settings from another project, importing setting from files, and resetting to
the default settings will change the Attribute mappings, GTYPE mappings, Attribute
derivation rules of the project, as well as the project options set up using this dialog.
3.2.1 Copying P&ID Manager Options from another Project

P&ID Manager option settings apply to the current project. P&ID Manager creates a record
of P&ID Manager related options of a project, which it stores locally. This is done when a
Project is opened in PDMS, with P&ID Manager installed, and the default P&ID Manager
Options are amended.
To copy project options from another project, press the Copy from Project button. The
Select Project dialog is then displayed and all Projects which have P&ID manager Options
defined will be displayed.
The Select Project dialog is then displayed.
The dialog lists all of the projects on the current PDMS installation for which P&ID Manager
options have been saved.
Press the OK button. The options are then copied from the selected project. A message is
displayed when the copy is complete.
3:6 12.0
3.2.2 Exporting P&ID Manager Options

P&ID Manager options can be exported to a file, which can then be imported by other PDMS
installations for use by other projects (see below).
Press the Export button. The Browse for Folder dialog is then displayed. Browse for the
location that the options file is to be exported to and press the OK button.
The options specified for the current database are then exported to that location into a file
with the default name of <Project>_Options.zip. A message is displayed when the
export is complete.
3.2.3 Importing P&ID Manager Options

As described above, the options settings of a project can be exported to a file. This file can
then be imported into another project. The options settings of that project are then changed
to those in the file.
Press the Import button. The Browse for Folder dialog is then displayed. Browse for the zip
file containing the options. The default file name of the export files is
<Project>_Options.zip.
Select the OK button. The import then takes place, and the existing options settings are
replaced by those in the import file. A message is displayed when the import is complete.
3:7 12.0
3.2.4 Restore Default Options

To restore the default P&ID Manager options, press the Reset Defaults button.
Note that this will reset all GTYPE Mappings, Attribute Mappings, Attribute Derivation Rules
and project options. A message requesting that the rest be confirmed is displayed:
A message is displayed when the restoration is complete.
3.3 Import Configuration Tab
The Import Configuration tab is used to:

• set default SCGROUP database elements to import diagrams, off-line instruments, off-
line equipment and pipelines into
• set the default coordinates of equipment and off-line instruments
3.3.1 Viewing/Editing Import Destination SCGROUP Elements

When diagrams (SCDIAG), off-line instruments (SCOINS), off-line equipment (SCEQUI)
and pipelines (SCPLIN) are imported, they are automatically placed in groups (SCGROU)
within the database hierarchy.
The groups these elements are placed in may be specified using attribute mappings (see 6:
Viewing/Editing Attribute Mappings for details).
Alternately, groups that these elements are placed in can be specified by the user using the
Import Destination Groups dialog, as described below.
If both an attribute mapping and the Import Destination Groups dialog have been used to
specify the destination group for an element, then the attribute mapping will be applied.
3:8 12.0
If neither of these methods is used, the elements are instead placed in default groups, which
are automatically created in the database as part of the import process (if they do not
already exist).
The default groups are named according to the following format:
<database name>/*/<name of element type>
For example:
To view or edit the groups into which diagrams, off-line equipment, equipment and pipelines
are imported into, press the View/Edit button on the Import Configuration tab. The Import
Destination Groups dialog is then displayed.
The Database field displays the name of the current Schematic database. To view/change
the import destination groups of another database, select it from the drop-down list. The list
consists of every Schematic database in the MDB.
The grid beneath the Database field lists the four element types and the names of the
groups into which they are imported.
3:9 12.0
To select a different group for an element type, select the ... button at the end of the row.
The Select Group dialog is then displayed:
Browse for the required group and select the OK button. Press the Cancel button to close
the dialog without making any changes.
Repeat as required for each of the four element types.
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.
3.3.2 Viewing/Editing Equipment and Off Line Instrument Positions

The attributes of imported equipment and off line instruments may not include a 3D position
for these items. Therefore a default position to be used when creating 3D elements may be
specified for use by such items.
The default position is entered in the Off Line Equipment & Instruments Default Position
field on the Import Configuration tab. For example:
For details of the format in which the coordinates must be entered, refer to PDMS 12.1
documentation.
3:10 12.0
3.4 Units Tab
Different diagrams may include measurements in different units of measure. For example,
on one diagram weight may be measured in Kilograms, on another it may be measured in
Pounds. On import, all such measurements are converted into the units of measure used in
the schematic database.
The Units tab is used to select the units of measure that measurements are to be converted
into. For example, the tab can be used to specify that all weight attributes values are to be
converted into Kilograms and all Volume attribute values are to be converted into Cubic
Metres.
In the Angle, Area, Pressure, Temperature, Volume and Weight fields, select the unit of
measure to be applied to values measured in these unit types.
Note that the value in the Distance field cannot be changed because all distances are
stored in millimetres in the database.
The default units of measure are as follows:
Unit Type Default Units of Measure

Angle Degrees
Area Square Metres
Distance Millimetres
Pressure Bar
Temperature Degree Celsius
Volume Cubic Metres
Weight Kilogram
3:11 12.0
Changing the unit of measure for a unit type will not update the units of measure for
instances of this unit type that have already been imported. Previously imported data must
be re-imported for the change to take effect.
The P&ID Manager default UDAs include attributes on the SCDIAG elements that store the
units of measure used when a diagram is loaded. If you need to determine the units for an
attribute value determine which diagram the element was last loaded from and view the
appropriate :Pmgunts attribute for the diagram.
3:12 12.0
P&ID Manager User Options
4 P&ID Manager User Options
The User Options dialog is used to set user specific P&ID Manager options. To access the
dialog, select the Tools > User Options... option from the P&ID Manager menu in the
DESIGN module.
The User Options dialog is then displayed.
To save changes to the options and exit the dialog, select the OK button.
4:1 12.0
P&ID Manager User Options
To exit the dialog without saving, select the Cancel button.
4.1 Import Options

If the Import Progress dialog (see 10.3: Import Progress Dialog) is to be closed
automatically when an import is complete, ensure that the Close Import Progress screen
on import completion checkbox is checked. The default setting is unchecked.
4.2 File Locations
4.2.1 Set Default Import Location

The default location which is accessed when browsing for files containing ISO15926 data to
import or view is displayed in the Default Location field of the Data Import row in the File
Locations grid.
To change the default folder, select the Data Import row, and press the Modify button. The
Browse for Folder dialog is then displayed.
Browse for the required folder and press the OK button. The new location is then displayed
in the Default Location field.
4.2.2 Set Default Export Location

The default location to which Options data is exported (see Section 3.3: Import
Configuration Tab), is specified in the Default Location field of the Data Export row in the
File Locations grid.
To change the default folder, select the Data Export row, and press the Modify button.
The Browse for Folder dialog is then displayed. Browse for the required folder and press the
OK button. The new location is then displayed in the Default Location field.
4:2 12.0
Viewing/Editing Attribute Derivation Rules
5 Viewing/Editing Attribute Derivation Rules
When diagrams are imported, the values of attributes may be automatically set according to
user-defined rules, known as Attribute Derivation Rules. There are no default rules shipped
with P&ID Manager.
To view or edit Attribute Derivation Rules, select the Tools > Attribute Derivation Rules...
option from the P&ID Manager menu in the DESIGN module.
5:1 12.0
The Attribute Derivation Rules dialog is then displayed.
Rules are grouped into rule groups. Rule groups may contain both rules and other rule
groups. The left-hand pane of the dialog displays all existing rules and rules groups. All rules
and groups are grouped under a node called Attribute Processing Rules.
5:2 12.0
The currently selected element is displayed in bold. Details of the currently selected element
are displayed in the right-hand pane.
Rules that are not selected to be applied during import are “greyed out” (see below).
Invalid rules are displayed in red text.
Press the OK button to close the dialog and save the changes that have been made. Press
the Cancel button to close the dialog without saving changes.
5.1 Selecting Rules to be Applied During Import

Each rule and rule group listed in the dialog has an “enabled” checkbox next to its name.
These are used to select which rules are to be applied during import.
5:3 12.0
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.
Unselected rules and groups are “greyed out”, i.e. displayed in grey, or pale red if invalid.
5.2 Creating/Editing Rule Groups

1. To create a new rule group, right-click on the Schematic Attribute Rules node, or the
node of an existing group, or on an existing rule, and select either Create > Group or
Insert > Group from the menu that is then displayed.
• If the Create option is selected, the new group is created within the currently
selected node, beneath any rules and groups already in that node.
• If the Insert option is selected, the new group is created above the currently
selected node, or at the top of the list of rules and group if the Attribute Processing
Rules node was selected.
5:4 12.0
The new group is created and given the default new group name (New Group):
2. Select the new group. Details of the new group are displayed in the right-hand pane:
3. Enter the name of the new group.

4. If the new rule group is to be processed, select “True” from the Enabled field.
Otherwise select “False”. The state of the checkbox against the rule group in the left-
hand pane will change to reflect the setting made here, and vice versa.
5. Click outside of the dialog to create the new group and close the dialog.
To edit an existing rule group, simply select it so that its details are displayed in the right-
hand pane and proceed as described above to edit them.
5.3 Creating/Editing Rules
5.3.1 Creating a Rule

1. To create a new rule, right-click on the Schematic Attribute Rules node, or the node of
rule group or a rule, and select either Create > Rule or Insert > Rule from the menu
that is then displayed.
• If the Create option is selected, the new rule is created within the currently selected
node, beneath any rules and groups already in that node.
• If the Insert option is selected, the new rule is created above the currently selected
node, or at the top of the list of rules and group if the Schematic Attribute Rules
node was selected.
The new rule is created and given the default new rule name (New Rule):
5:5 12.0
2. Select the new rule. Details of the new rule are displayed in the right-hand pane:
3. Enter the name of the new rule in the Name field. This is optional, as a name derived
from the properties of the rule will be assigned to the rule when it is created. The name
entered here will suffix this identifier (see below for details).
4. If the new rule is to be processed, select “True” from the Enabled field. Otherwise
select “False”. The state of the checkbox against the rule in the left-hand pane will
change to reflect the setting made here, and vice versa.
5. The number of attribute filters 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 field.
The Attribute Filters dialog is then displayed.
5:6 12.0
i. Enter a valid attribute in the displayed Attribute field, or select a attribute from the
drop down.
ii. In the Operator field, select the required operator from the drop-down list.
iii. The In List operator enables you to specify a list of values (separated by spaces)
for the specified attribute value - these can be numeric or non-numeric, depending
on the type of the attribute. For example, Attribute=AREA, Operator="In the List",
Value="0 1 3", would find items which have AREA attribute equal to either 0 or 1 or
3.
iv. In the Value field enter an appropriate value.
v. Multiple attribute filters can be applied. Click on the Add Filter option. A new row of
fields in which filter details can be entered is then displayed.
vi. To delete a filter or filters, select the row or rows they are displayed in and click on
the Delete Filter option.
vii. Once the required filters have been set up, press the OK button to close the dialog.
To close the dialog without saving any changes, press the Cancel button.
6. Select the attribute to which the rule is be applied from the Attribute field. The list
consists of the attributes shared by the selected Element Types, i.e. only attributes
which are common to all the selected Element Types are listed.
If the selected element types are changed, the list of valid attributes may also change.
If an attribute was selected that is now invalid, another attribute must be selected.
7. If a rule is a Name Clash Rule, select “True” in the NameClashRule field. Otherwise
leave this set to “False”.
The name attribute value of an element must be unique in the database. Due to the
application of a rule, the name of an element may be set to a value that is already in
use. This is called a "name clash".
5:7 12.0
Name Clash Rules are set up to prevent this. If a name clash is detected during an
import, the process will search for the Name Clash Rule of the element's element type
(if one exists), and apply that instead.
It is recommended that for each rule which attempts to set the Name attribute of one or
more elements, there should be a corresponding Name Clash Rule, which P&ID
Manager can apply to the Name attribute value of the same elements, in the event of a
name clash.
8. If the application of a Name Clash Rule still results in a clash, or if there is no Name
Clash Rule found for the element type(s), a default name is applied instead.
9. The value applied to the selected attribute is determined by a DB expression. To enter
this expression, select the ... button at the end of the DB Expression field. The Edit DB
Expression dialog is then displayed.
Enter the required DB Expression.

For information on DB Expressions, refer to 9. Expressions in the PDMS Database
Management Reference Manual.
Select the OK button. The entered Expression is then displayed in the DB Expression
field.
If the expression is valid a green tick will be displayed to the left of this field. If the
expression is invalid, or if no expression has been entered, a red cross is displayed.
Invalid expressions are displayed in red text.
Note: If DBExpression is left blank, or an invalid DBExpression is provided, the rule will be
shown in red in the Attribute Derivation Rules Explorer, and the rule will not be active
10. To select an element type or types to which the rule is to be applied, select the ... button
at the end of the Element Types field. The Select Values dialog is then displayed.
5:8 12.0
11. The Select Values dialog consists of two lists. The Available Values list lists the
Element Types which are available for selection. The Selected Values list lists the
Element Types that have been selected.
To select an Element Type, select it in the Available Values list and press the > button
to transfer it to the Selected Values list.
To de-select an Element Type, select it in the Selected Values list and press the <
button to transfer it back to the Available Values list.
Use the >> button to move all Element Types to the Selected Values list. Use the <<
button to move all Element Types to the Available Values list.
Elements may also be selected/deselected by double clicking.
Press the OK button once the required Element Types have been selected. The
selected Element Types are then displayed in the Element Types field of the Rule
Attribute dialog.
Press the Cancel button to close the dialog without saving any selections that have
been made.
5.3.2 Rule Names

Names of rules are in the following format:
Element Type/Attribute/Optional Rule Name
If more than one Element Type was selected, the name of the first Element Type is followed
by a comma and three full stops, i.e. “,...”.
For example, a rule with the following properties:
Elements: SCEQUI, SCNOZZ
Attribute: NAME
Rule Name: Rule 1
...will be called:
SCEQUI,…/NAME/Rule 1
A rule with the following properties:
5:9 12.0
Elements: SCEQUI
Attribute: NAME
Rule Name: (not defined)
...will be called:
SCEQUI/NAME
5.3.3 Editing a Rule

To edit an existing rule, simply select it so that its details are displayed in the right-hand
pane and proceed as described above to edit them.
5.4 Moving Rules and Rule Groups

Rules and rule groups can be moved to a different location in the hierarchy of rules and
groups by:
• Dragging and dropping
• Using the Ctrl+X (Cut) and Ctrl+V (Paste) keyboard commands
• Selecting the Cut and Paste options from the right-click menus of rules and groups.
If a rule group is moved, all rules and groups within that group are moved with it.
The Attribute Processing Rules node cannot be moved.
5.5 Deleting Rules and Rule Groups

To delete a rule or group, either select it and press the Delete key, or right-click and select
the Delete option. A message is then displayed, requesting that the deletion be confirmed.
Press Yes to continue with the deletion.
If a rule group is deleted, all rules and groups within that group are deleted with it.
The Attribute Processing Rules node cannot be deleted.
5:10 12.0
Viewing/Editing Attribute Mappings
6 Viewing/Editing Attribute Mappings
To map system/project specific attributes from the source files to schematic or user defined
database attributes, or to view existing mappings, use the Attribute Mapping dialog.
To access this dialog, select the Tools > Attribute Mappings... option from the P&ID
Manager menu in the DESIGN module or the Attribute Mapping option from the P&ID
Manager menu in the LEXICON module.
6:1 12.0
The Attribute Mapping dialog is then displayed:
The dialog can be used to 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.
The right-hand section displays the properties of the attribute mapping or mapping group
selected in the left-hand section, and is used to enter and edit these properties.
To close the dialog and save changes made to attribute mapping, press the OK button. To
close the dialog without saving changes, press the Cancel button.
Note: Changes made in the LEXICON module are not committed to the database until a
Save Work takes place.
6.1 Tree View

The tree view displays the hierarchy of attribute mapping groups and attribute mappings.
Attribute mapping groups may contain other attribute mapping groups as well as mappings.
All groups and mappings are grouped under a node called Attribute Mappings.
Attribute mapping groups are represented by folder icons. Attribute mappings are
represented by book icons.
In older versions of P&ID Manager, attribute mappings were not organised into groups. Any
mappings created using these older versions of P&ID Manager are automatically grouped
into an attribute mapping group called Default Mappings when P&ID Manager is upgraded.
Attribute mapping group nodes can be opened and closed using the + and - symbols.
6:2 12.0
6.2 Default Attribute Mappings

A number of default mappings are supplied with P&ID Manager. They are listed in the
Default Mappings attribute mapping group folder.
If required, these default mappings can be edited.

To edit an attribute mapping, select it in the tree view. The properties of the mapping are
then displayed in the right-hand section, and can be edited as described in 6.4: Creating
Attribute Mappings.
6.3 Creating Attribute Mapping Groups

To create a new attribute mapping group right-click on either the top-level Attribute
Mappings node, or on an existing attribute group node. From the menu that is then
displayed, select either the Create > Attribute Group option or the Insert > Attribute
Group option.
6:3 12.0
If the Create option is selected, the new attribute group node with the default name of New
Attribute Mappings is then created at the bottom of the hierarchy of groups and mappings
within the currently selected node.
If the Insert option is selected, the new attribute group is instead created directly above the
node that was selected when the option was selected. The Insert option is not available
from the top-level Attribute Mappings node.
The right-hand section of the dialog displays the properties of the new group.
Complete these properties to set up the attribute mapping group.

1. In the Name field, change the default name of the mapping as required. Alternatively,
double-click on the name in the tree-view and type in the name. A mapping name may
be up to 50 characters. The @ symbol may not be included.
2. The Element Types field displays the SCTYPEs to which the mappings in the group
can be applied.
If no SCTYPEs are specified in this field, all SCTYPEs may be selected for mappings in
the group.
To select the SCTYPEs, press the ... button at the end of the field. The Select Values
dialog is then displayed.
3. The Select Values dialog consists of two lists. The Available Values list lists the
SCTYPEs which are available for selection. The Selected Values list lists the
SCTYPEs that have been selected.
To select an SCTYPE, select it in the Available Values list and press the > button to
transfer it to the Selected Values list.
6:4 12.0
To de-select an SCTYPE, select it in the Selected Values list and press the < button to
transfer it back to the Available Values list.
Use the >> button to move all SCTYPEs to the Selected Values list. Use the << button
to move all SCTYPEs to the Available Values list.
Press the OK button once the required SCTYPEs have been selected. The selected
SCTYPEs are then displayed in the Element Types field.
Press the Cancel button to close the dialog without saving any selections that have
been made.
4. Whether or not the attribute mappings in the group are applied can be made
conditional. To enter the conditions, press the ... button at the end of the Condition
field and enter an XPath Expression using the XPath Expression Builder dialog. See
6.5: XPath Expression Builder Dialog for details
If an invalid expression is entered, “False” is displayed in the Condition field, indicating
that the mapping cannot be applied. If a valid expression is entered, “True” is
displayed.
“True” is also displayed if no conditions are entered. If no conditions are entered,
mappings are applied by default.
6.4 Creating Attribute Mappings

To create a new attribute mapping right-click on either the top-level Attribute Mappings
node, or on an attribute group node, or on an existing attribute mapping. From the menu that
is then displayed, select either the Create > Attribute Mapping option or the Insert >
Attribute Group option.
If the Create option is selected, a new attribute mapping with the default name of New
Attribute Mapping is then created at the bottom of the hierarchy of groups and mappings
within the current node.
If the Insert option is selected, the new attribute mapping is instead created directly above
the node that was selected when the option was selected.
6:5 12.0
The right-hand section of the dialog displays the default properties of the new mapping.
Complete these properties to set up the attribute mapping.

1. In the Name field, change the default name of the mapping as required. Alternatively,
double-click on the name in the tree-view and type in the name. A mapping name may
be up to 50 characters. The @ symbol may not be included.
2. The Element Types field displays the SCTYPEs to which the mapping is to be applied.
To select the SCTYPEs, press the ... button at the end of the field. The Select Values
Refer to 6.3: Creating Attribute Mapping Groups for details of this dialog.
The SCTYPES that are available for selection are limited to those specified for the
mapping group. If no SCTYPEs are specified for the group, any available SCTYPE
may be selected.
3. In the Database Attribute field select the UDAs/database attributes to which the
source file attribute is to be mapped to. The attributes that may be selected will be
those common to the SCTYPEs selected in the Element Types field.
4. Whether or not an attribute mapping is applied can be made conditional. To enter the
conditions, press the ... button at the end of the Condition field and enter an XPath
Expression using the XPath Expression Builder dialog. See 6.5: XPath Expression
Builder Dialog for details.
If an invalid expression is entered, “False” is displayed in the Condition field, indicating
that the mapping cannot be applied. If a valid expression is entered, “True” is
displayed.
“True” is also displayed if no conditions are entered. If no conditions are entered,
mappings are applied by default.
Note: Conditions may also be set up for the group as a whole. If conditions have been
setup for both the group and the mapping, both sets of conditions must be satisfied if
the mapping is to be applied.
6:6 12.0
5. In the Source Attribute field, either enter the name of the source file attribute.
Alternatively, press the ... button at the end of the field and enter an XPath Expression
using the XPath Expression Builder dialog. See 6.5: XPath Expression Builder Dialog
for details.
6. In the Attribute Units field, if applicable select the type of unit (e.g. weight, volume)
associated with the source file attribute from the drop-down list.
Alternatively, press the ... button at the end of the field and enter an XPath Expression
using the XPath Expression Builder dialog. See 6.5: XPath Expression Builder Dialog
for details.
This field may be automatically completed if the XPath Expression Builder dialog is
used to enter an XPath Expression in the Source Attribute field. See Automatic
Setting of Attribute Units and Types.
On import, the type of unit will be converted to the unit of measure (e.g. kilogram, cubic
metres) specified on the Units tab of the Options dialog. See 3.4: Units Tab.
7. In the Source Attribute Type field, enter the source attribute type, e.g. string, integer
etc. The default entry is “string”.
This field may be automatically completed if the XPath Expression Builder dialog is
used to enter an XPath Expression in the Source Attribute field. See Automatic
Setting of Attribute Units and Types.
8. In the File Format field, select the import source file format associated with the source
file attribute from the drop-down list. The default entry is “XMpLant”. Select * for all
formats.
9. The File Format Version field displays the versions of the source file format
associated with the source file attribute. The default entry is “*”, meaning all versions.
To select the versions, press the ... button at the end of the field. The Select Values
See 6.3: Creating Attribute Mapping Groups for details of this dialog.
6:7 12.0
6.5 XPath Expression Builder Dialog

The Xpath Expression Builder Dialog is accessed from the Condition, Source Attribute
and Source Attribute Units fields of the main Attribute Mapping dialog. It is used to
construct XPath expressions to populate these fields.
For more information on XPath expressions, see 17.3: Appendix C: XPath Expressions.
The dialog consists of three sections. The Source Dictionary pane section, the Shortcuts,
XPath Operators and XPath Functions tabs section and the Expression pane section.
An XPath expression may be constructed manually, by typing directly into the Expression
area of the dialogue. In addition, source file attributes for inclusion in the expression may be
selected from the Source dictionary, by navigating to the required element in the source
dictionary tree view and double clicking on the required attribute. This attribute will then be
added to the expression.
Additional elements for constructing an XPath expression are provided on the Shortcuts,
XPath Operators and XPath Functions tabs.
Once the required expression has been constructed, select the OK button to close the
dialog. The expression is then displayed in the relevant field in the main Attribute Mapping
dialog.
6:8 12.0
6.5.1 Source Dictionary Pane
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 Dictionary pane contains a tree-view that lists all the component classes in the
Source Data Dictionary that relate to the SCTYPEs selected in the Element Types field of
the main Attribute Mapping dialog, as described above.
The SCTYPEs/component classes are all listed against the top node of the tree view. This
node can be expanded to display the import file standards, for example XMpLant, of the
imported data.
Each import file standard node can be expanded to list the attributes which are common to
all of the selected SCTYPEs/component classes and that are of that import file standard.
Note: Nodes are expanded by pressing the + button on the keyboard.
If the required attributes are not displayed, or no attributes are displayed, the dictionary
must be populated by extracting attribute data from diagram import files. See 6.5.6:
Accessing the Source Data Dictionary.
Each of the attribute nodes can be expanded to display the following nodes, which display
attribute metadata.
Src - Xpath to the source of the attribute. This is the text that will be added to the
expression if the attribute is added to it.
SrcUnits - Xpath to the units of the attribute (if applicable).
6:9 12.0
Type - Storage type for the attribute (e.g. string, integer).

Has Content - Yes/No, indicates whether or not the attribute has been observed with
content at any time.
Min Cardinality - Displays the minimum observed cardinality of the attribute.
Max Cardinality - Displays the maximum observed cardinality of the attribute.
Of the above, Src and SrcUnits can be added to an expression. The other data is presented
for information only.
To add an attribute or attribute data to an expression, either drag and drop the data item
from the Source Dictionary pane into the Expression pane, or double-click on the data item.
If dragged and dropped, the data item is added to the expression where it is “dropped”. If
double-clicked the data item is added to the expression at the point that the cursor is
currently located in the Expression pane.
6.5.2 Shortcuts, XPath Operators and XPath Functions Tabs

The Shortcuts tab lists common XPath expression operations, for example for removing
spaces in strings and joining strings together.
The XPath Operators tab lists XPath expression operators, for use in constructing XPath
expression operations.
6:10 12.0
The XPath Functions tab lists XPath expression functions, for use in constructing XPath
expression operations.
Beneath the tabs, a description of the currently selected item is displayed.
To add an operation, operator, or function to an expression, either drag and drop it from the
tab into the Expression pane, or double-click on it.
If dragged and dropped, the item is added to the expression where it is “dropped”.
If double-clicked, operators are added to the expression at the point that the cursor is
currently located in the Expression pane.
If double-clicked, operations and functions are placed at the start of the expression, and the
expression is automatically enclosed in parenthesis following the item. If the Expression
pane is empty, the item is placed followed by empty parenthesis.
6:11 12.0
6.5.3 Expression Pane
As described above, items selected in the upper sections are copied into the Expression
pane. Multiple attributes, operations, etc can be selected to construct complex expressions.
XPath expressions, or parts of expressions, may also be typed directly into the pane.
Standard Cut, Copy and Paste text editing options are available on a right-click menu. The
right-click menu also includes a Clear Text option, which will clear the Expression pane.
6.5.4 Setting up Mappings Using the Xpath Expression Builder Dialog -

Examples
Mapping a URL Database Attribute

In this example, a mapping will be set up for the URL Database Attribute of a SCDIAG
(diagram) Database Attribute using the XPath Expression Builder.
This scenario assumes that the original intelligent P&ID Diagrams from which import files
are generated are subsequently stored in a SharePoint Portal site.
An attribute mapping will be constructed which uses an XPath expression to add both the
Sharepoint location and the correct file suffix to the import file’s diagram name Source
Attribute value. This is then written to the URL attribute of the corresponding SCDIAG
element, thereby providing a link from the schematic database directly to the original
intelligent P&ID file (in this example an AVEVA P&ID Diagram (.DWG)).
6:12 12.0
1. Using the Attribute Mapping dialog, create a new mapping and name it appropriately.
In the Element Types field, select the SCDIAGRAM (diagram) element.

From the Database Attribute field, select the URL attribute.
Leave the Condition field blank.
Refer 6.4: Creating Attribute Mappings for details.
2. Click on the ... button in the Source Attribute field.
The XPath Expression Builder dialog is then displayed, with the SCDIAGRAM element
listed in the Source Dictionary pane.
6:13 12.0
3. Double-click on the Concatenate operator on the Shortcuts tab.
The operator is then displayed in the Expression pane.
4. Between the first parenthesis and the comma in the concat operator, enter the URL of
the drawing location (excluding the file name) in double quotes.
6:14 12.0
5. Place the cursor after the comma and then double-click on the Name attribute of the
SCDIAGRAM element. The Name attribute is then placed into the expression.
6. After the second comma (which is added when the Name attribute is selected), enter
the file extension of the source drawing.
7. The expression is now complete. Select the OK button the save it and close the dialog.
The expression is displayed in the Source Attribute field of the main Attribute Mapping
dialog.
8. When SCDIAGRAM elements are imported into the database, their URL attributes are
automatically populated using the XPath expression.
6:15 12.0
Mapping an Owner Database Attribute

A mapping can be set up using an XPath expression so that when an element is imported its
Owner attribute is automatically set.
In this example a mapping will be set up which will result in the owner attributes of
equipment elements (SCEQUIPMENT) being set automatically on import. This will result in
equipment elements being assigned to the correct group (SCGROUP) within the database
hierarchy, rather than to the default group for equipment. If this group does not exist, it will
be created automatically.
Groups in this example are identified by single letters, which will be derived from the first
character of the name of the equipment (their Tag attributes).
6:16 12.0
1. Using the Attribute Mapping dialog, create a new mapping and name it appropriately.
In the Element Types field, select the SCEQUIPMENT element.

From the Database Attribute field, select the Owner attribute.
Leave the Condition field blank.
Refer 6.4: Creating Attribute Mappings for details.
2. Click on the ... button in the Source Attribute field.
The XPath Expression Builder dialog is then displayed, with the SCEQUIPMENT
element listed in the Source Dictionary pane.
6:17 12.0
3. Double-click on the Tag attribute of the SCEQUIPMENT element.
The attribute is then displayed in the Expression pane.
4. Place the cursor in the Expression pane in front of the Tag attribute:
Double-click on the substring function in the XPath Functions tab.
6:18 12.0
The substring function is then added to the expression, with the Tag attribute as its
subject.
5. After the first comma, enter the start position of the substring within the string (i.e.
within the Tag attribute), in this case 1. After the second comma, enter the length of the
substring, in this case also 1. This will result in the first character only of the Tag
attribute of equipment being selected.
6. The expression is now complete. Select the OK button the save it and close the dialog.
The expression is displayed in the Source Attribute field of the main Attribute Mapping
dialog.
7. From the Attribute Type field select dbelement, which indicates that the mapping will
generate new elements.
6:19 12.0
8. When an equipment element is imported, the mapping will refer to the name (Tag
attribute) of the equipment. It will take the first character of the equipment and create a
new group (if necessary), using that character as the group’s name, and will set the
Owner attribute of the equipment as that group.
6.5.5 Automatic Setting of Attribute Units and Types

When the OK button is pressed, the user may be prompted to automatically set the unit type
of an attribute to the default value if:
• The Expression Editor dialog was opened from the Source Attribute field.
• An attribute with units was selected, for example:
6:20 12.0
• The existing unit value in the Source Attribute Unit field is different from the default
value (or this field is blank).
If the Yes button is pressed, the user may also be asked if the attribute type should be
automatically set.
If the Yes button is pressed, both the Source Attribute Unit field and Attribute Type field
are automatically completed with the unit and attribute types of the selected attribute,
derived from the Source Data Dictionary.
6.5.6 Accessing the Source Data Dictionary

The Source Data Dictionary pane is populated with data from the Source Data Dictionary. To
populate, update or reset the dictionary, select the Manage Source Dictionary button.
The Source Dictionary Management dialog is then displayed. See 8: Configuring the Source
Data Dictionary for details.
6:21 12.0
6.6 Editing, Moving and Deleting Mapping Groups and

Mappings
6.6.1 Editing Mapping Groups and Mappings

To edit an attribute mapping group or attribute mapping, select it in the tree view. The
properties of the group or mapping are then displayed in the right-hand section, and can be
edited as described above. See 6.3: Creating Attribute Mapping Groups and 6.4: Creating
Attribute Mappings.
This method can also be used to rename the top level Attribute Mapping node.
6.6.2 Moving Mapping Groups and Mappings

Attribute mapping groups and attribute mappings can be moved (but not copied) from one
attribute group or another, or between an attribute group and the top level Attribute Mapping
node.
To move an attribute group or mapping, select it, and use the mouse to drag and drop it to
the required location in the tree view.
Alternatively, right-click on the group or mapping and select the Cut option from the menu.
Select the node in the hierarchy beneath which the group or mapping is to be placed, right-
click, and select the Paste option from the menu. The group or mapping is then moved to
the selected location. The Ctrl-X (cut) and Ctrl-V (paste) keyboard commands can also be
used.
The top level Attribute Mapping node cannot be moved.
6.6.3 Deleting Mapping Groups and Mappings

To delete a mapping group or mapping, either right-click on in the tree view and select the
Delete option, or select it and press the Delete keyboard key.
A message is then display requesting that the deletion be confirmed. Press the Yes button
to continue.
If a group is deleted, all mappings and groups within that group are also deleted.
The top level Attribute Mapping node cannot be deleted.
6:22 12.0
Viewing/Editing GTYPE Mappings
7 Viewing/Editing GTYPE Mappings
GTYPEs 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.
GTYPEs/SCSTYPEs are associated with schematic items by mapping them to the
ISO15926 designations of schematic items in the import files. Each ISO15926 designation
represents a component type in the schematic source.
The GTYPE value also affects the schematic database element created. 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 and SCTUB
schematic database elements will be created inside SCSEGMENT elements.
Note that not all schematic items have equivalents in the 3D database. Such items do not
need to have mappings set up against their ISO15926 designations.
To view or edit the mappings between ISO15926 designations and corresponding GTYPE/
SCSTYPE combinations, select the Tools > GTYPE Mappings... option from the P&ID
Manager menu in the DESIGN module.
7:1 12.0
The ISO15926 Mapping dialog is then displayed.
The grid displays any mappings that have already been set up. A limited set of default
mappings are supplied with P&ID Manager.
To add a new mapping, click on the blank row at the bottom of the grid enter the designation
of the schematic item type in the ISO 15926 Designation field.
Note: Lists of designations can be imported into these fields from a file, or from another
database (see below).
Complete the mapping by selecting a GTYPE, and if applicable, entering an SCSTYPE.
7:2 12.0
Note that mappings can be automatically completed in accordance with user-defined rules
(see below).
To delete existing mappings, select the rows containing the mappings and press the Delete
Selected Row(s) button.
To delete all mappings, press the Delete All button.
To close the dialog and save any changes, press the OK button.
To close the dialog without saving changes, press the Cancel button.
7.1 Import Designations from File

The ISO 15926 Designation fields can be completed by importing a list of designations
from a file.
If a file includes GTYPEs and STYPEs mapped to these designations, they are also
imported to complete the GTYPE and SCSTYPE fields.
To import designations from a file, press the Populate ISO 15926 Designations from File
button. The Import dialog is then displayed.
Browse for the XML file that contains the designations. Once the file is selected, press the
Open button. This button will not be active until an XML file has been selected.
7:3 12.0
7.1.1 Conflict Resolution

If the selected file does not contain any valid designations, an error message is displayed.
Otherwise, the Conflict resolution message is displayed:
The selected file may include GTYPE and STYPE mappings that conflict with those already
set up in the ISO15926 Mapping dialog.
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 STYPEs.
If such conflicts are detected, the following rules are applied to resolve them:
GTYPES
If a GTYPE conflict is detected, the following dialog is displayed during the import for each
conflict:
Select the preferred GTYPE to map to the designator from the list and press OK.
If the Yes button was 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 was selected, this GTYPE will not be included.
STYPES
If conflicting STYPE 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 STYPE will be
saved, overwriting any existing mappings.
A summary of the rules for conflict resolution is displayed by pressing the Help button.
7:4 12.0
7.1.2 Completing the Import

Imported GTYPEs are validated against a list of valid GTYPEs stored in the database. If an
imported GTYPE is not on this list it is invalid, and the associated designator is not imported.
A message is displayed to advise the user of this, e.g.:
If a designator in the import file is mapped to an STYPE 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:
The designations in the file are then copied into the ISO 15926 Designation fields.
The GTYPE and SCSTYPE fields are completed with the GTYPEs and STYPEs mapped to
the designations in the imported files.
7.2 Setting up Rules for Automatic Completion of ISO

15926 Mappings
ISO 15926 mappings can be automatically completed. The automatic completion is carried
out in accordance with rules set up by the user. For example, the user can specify that the
GTYPE of VALV is automatically mapped to the Control Valve designator.
To set up the rules for automatic completion, press the Configure Auto Complete button.
The Auto Complete Configuration dialog is then displayed.
7:5 12.0
To set up a rule:
1. In the Rule field enter a Regular Expression that is used to select which designators
are to be mapped using the rule.
For example, if the rule is to map Control Valves, enter CONTROL VALVE. If the rule is
to be used to map different sorts of valve, enter VALVE. All designators containing
"VALVE" would be mapped using this rule.
For guidance on using Regular Expressions see Section 17.1: Appendix A: Regular
Expressions.
2. In the GTYPE field, select the GTYPE that designators selected by the rule expression
are to be mapped to.
3. In the SCSTYPE field, if required, enter the SCSTYPE that designators are to be
mapped to.
4. 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.
7:6 12.0
If the Overwrite existing values checkbox is checked, existing mappings are overwritten
when rules are applied. If the checkbox is unchecked, existing mappings, either entered by
the user or set by a previous Auto Complete process, are not overwritten.
To delete existing rules, select the rows containing the rules and press the Delete Selected
Row(s) button.
To delete all rules, press the Delete All button.
To close the dialog and save any changes, press the OK button.
To close the dialog without saving changes, press the Cancel button.
7.3 Automatically Completing ISO 15926 Mappings

To automatically complete the ISO 15926 mappings using the rules set up using the Auto
Complete Configuration dialog (see above), press the Auto Complete button. The
mappings are then completed in line with the current rules.
7.3.1 Example
The list of designators is as displayed below:
7:7 12.0
The following rule is set up:
The Auto Complete button is pressed.

The mapping for the CHECK VALVE and CLOSED GENERAL VALVE designators are
automatically completed (they are mapped to the VALV GTYPE):
7.4 Import Designations from other Databases

The ISO 15926 Designation fields can be completed by importing designations from a
database or databases within the current MDB.
To import designations from other databases, press the Populate from Database(s) button.
The Select Database dialog is then displayed.
7:8 12.0
The dialog lists all the Schematic databases in the Master database (MDB).
To select the database(s) to import designations from, check the appropriate Apply
checkboxes.
Once the required selections have been made, press the OK button. The import then takes
place.
Press the Cancel button to close the dialog without proceeding with the import.
The designations in the selected databases are then copied into the ISO 15926
Designation fields. Note that designations already listed in these fields are not imported,
and therefore existing mappings will not be overwritten.
7.5 Overwrite Mappings in Databases with Current

Mappings
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 may
mean that elements already imported into the database have 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 is then displayed.
7:9 12.0
The dialog lists all the Schematic databases on the MDB. Select the required databases as
described above, and press the OK button.
7:10 12.0
Configuring the Source Data Dictionary
8 Configuring 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 - see 10:
Importing Diagrams).
This information is made available when configuring the attribute mappings using the XPath
Expression Builder dialog (see 6.5: XPath Expression Builder Dialog), in order to reduce the
need for a user to understand the source file format and XPath syntax.
The dictionary is populated automatically when diagram data is imported with attribute and
element metadata relating to the component classes in the diagram data import files. The
dictionary may also be populated manually if required.
During a project lifecycle, 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 to
the 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.
8.1 Accessing the Configuration Options

In order to populate, refresh or update the Source Data Dictionary, select the Tools >
Configure the Source Dictionary... option from the P&ID Manager menu in the DESIGN
module.
8:1 12.0
Alternatively, press the Manage Source Dictionary button on the XPath Expression Builder
dialog (see 6.5.6: Accessing the Source Data Dictionary).
The Source Dictionary Management dialog is then displayed.
For details on the configuration options, continue at:

• 8.2: Resetting the Dictionary
• 8.3: Populating or Updating the Dictionary
8.2 Resetting the Dictionary

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.
Select the Reset Source Dictionary button. The following message is then displayed:
The dictionary will then be reset to its default, empty state.
8:2 12.0
If the attribute mappings are to be edited before the next data import then it is recommended
that the dictionary is populated (see 8.3: Populating or Updating the Dictionary).
8.3 Populating or Updating the Dictionary

To add data to the dictionary without importing P&ID content into the database select the
Populate Dictionary from Source files… button.
The Open dialog is then displayed. Select the import file or files from which dictionary data is
to be extracted.
The following dialog is then displayed while the selected files are processed and information
about the elements and their attributes is added to the dictionary.
Data previously added to the dictionary is added to rather than replaced.
8:3 12.0
8:4 12.0
Previewing Diagrams before Import
9 Previewing Diagrams before Import
Note: For the procedure for viewing diagrams once they have been imported, see 12:
Viewing Imported Diagrams.
9.1 Selecting Diagrams to Preview

To view previews of diagrams that are available for import, select File > View... from the
P&ID Manager menu in the DESIGN module.
9:1 12.0
The Open dialog is then displayed:
Browse for and select the XML file or files of the diagrams to be previewed (each file
contains data for a single P&ID), and press the Open button. The default import file location
is specified on the User Options dialog (see Section 4.2: File Locations).
If all of the selected files are invalid, an error message is displayed, listing the invalid files.
No diagrams are displayed.
If some of the selected files are invalid, a warning message is displayed, listing the invalid
files. The message gives the user the option of continuing or cancelling. If the user chooses
to continue with the procedure, only diagrams associated with valid files are displayed.
9:2 12.0
9.2 P&ID Manager Diagram Viewer
The viewer displays the selected diagrams. Each diagram is displayed on a tab, labelled
with diagram file name.
Hover the mouse cursor over a tab to display the file name and location of the diagram file.
9:3 12.0
If multiple diagrams are being displayed, their tabs may not all fit in the viewer window. If this
is the case, next > and previous < buttons will be displayed in the bottom-right hand corner
of the window to enable these tabs to be displayed.
To close a diagram, right-click on the diagram or on the diagram tab, and select the Close
option from the menu that is then displayed.
9.2.1 Diagram Viewer Toolbar

The Diagram Viewer toolbar is automatically displayed.
It consists of the following buttons:
View Diagram - used to view diagrams that have been imported. See 12: Viewing
Imported Diagrams for details. Not used to preview unimported diagrams.
Zoom In
Zoom Out
Zoom to Selection - zooms to a selected area of the diagram. Select this button
then select the area by left-clicking on one corner of the area and then dragging the
cursor to the opposite corner of the area.
Zoom to Window - zooms out so that the entire diagram is visible.
This option is also available from the menu that is displayed by right-clicking on a
diagram.
Auto Zoom On External Selection - toggles the mode for auto-zoom.
Set Bookmark - saves the current view - saved views are known as bookmarks
Previous Bookmark - sets the view to the bookmark that was set before the
current bookmark
Next Bookmark - sets the view to the bookmark that was set after the current
bookmark
9:4 12.0
Delete Bookmark - deletes the current bookmark
Clear All Bookmarks - deletes all bookmarks
If the cursor is hovered over this button, a tooltip displaying information on keyboard
commands is displayed. See below.
Note: Bookmarks are not saved when the Diagram Viewer is closed.
9.2.2 Keyboard Commands

Useful keyboard commands include:
• To zoom into an area of a diagram, hold down the Ctrl key and left-click on one corner
of the area and then drag the cursor to the opposite corner of the area.
• Press Ctrl and click on the diagram to zoom in.
• Press Ctrl+Shift and click on the diagram to zoom out.
• To pan, hold down Alt and the left mouse button and drag the cursor in the required
direction.
9.2.3 Closing Diagrams and the Viewer

To close a diagram, right-click on the tab of the diagram and select the Close Tab option.
To close all diagrams, select the Close All Tabs option.

To close the viewer, select the X button in the top-right-corner of the window.
9:5 12.0
9:6 12.0
Importing Diagrams
10 Importing Diagrams
There are two import facilities available from the P&ID Manager menu in the DESIGN
module, the Import Diagrams facility (see 10.1: Import Diagrams Facility) and the Import
Diagram Set facility (see 10.2: Diagram Set Import Facility).
These two facilities are used to select the data to be imported. In the case of the Import
Diagram Set facility, these are predefined sets of diagrams, which once defined, can be
selected for import multiple times. In the case of the Import Diagrams facility, the diagram or
diagrams to be imported are selected at the time of import.
The import itself is then monitored using the Import Progress dialog (see 10.3: Import
Progress Dialog).
Diagram data can also be imported using the facilities available by using PML (see 10.4:
Importing using PML).
Whichever method is used, after data has been imported, it must be saved to the database
(see 10.5: Saving Imported Data).
10.1 Import Diagrams Facility

From the P&ID Manager menu, select File > Import Diagrams....
10:1 12.0
Importing Diagrams
Browse for and select the XML file or files of the diagrams to import, and press the Open
button. The default import file location is specified on the User Options dialog (see Section
4.2.1: Set Default Import Location).
As part of the import procedure, depending on the settings specified on the Project Options
dialog (see Section 3.1.1: Set Release Behaviour of Elements on Import), elements may be
automatically released.
10:2 12.0
Importing Diagrams
If this is the case, comments may be entered regarding the change in release status and
recorded against each released element in the schematic database in the Release
Comments dialog, which is automatically displayed.
Enter the comments and press the OK button. If the Cancel button is pressed, no release
comments are entered. This does not cancel the import.
Whether or not this dialog is displayed is also specified on the Project Options dialog.
The Import Progress dialog is then displayed. See 10.3: Import Progress Dialog.
10.2 Diagram Set Import Facility

A Diagram Set is a group of diagram XML files. By grouping these into Diagram Sets, the
same set of files can be recalled and re-imported as required.
The XML files themselves contain engineering item and graphical data. Each of these files
contains data for a single diagram. This data is exported from AutoCAD P&ID drawings
using the AVEVA P&ID Manager Gateway, from AVEVA P&ID, and other supported P&ID
systems. Contact your AVEVA Sales office for details.
File Sets are created and edited using the Diagram Set Editor. See 10.2.1: Creating
Diagram Sets.
Note: For guidance on creating or editing Diagram Sets using third party software, see
17.4: Appendix D: Diagram Set File Formats.
The Diagram Set Editor can also be used to initiate the import of Diagram Sets. Existing
Diagram Sets can also be selected for import via the File menu. See 10.2.3: Importing
Diagram Sets.
10.2.1 Creating Diagram Sets

From the P&ID Manager menu, select File > Diagram Set Editor.
10:3 12.0
Importing Diagrams
The Diagram Set Editor is then displayed:
This dialog used to create and edit Diagram Sets and initiate imports.
The title bar of the Diagram Set Editor will display the name of the current File Set, or “New
Diagram Set” if a new file set is in the process of being created. On entry, a new Diagram
Set is opened by default.
If an asterisk is displayed next to the title, this indicates that the current File Set has been
changed but not saved.
Creating a New Diagram Set

When the Diagram Set Editor is opened, a new “empty” Diagram Set is automatically
opened. If the editor is currently displaying a Diagram Set, select the New Diagram File Set
button to clear the screen:
If the current Diagram Set has not been saved, you will be prompted to save it, and if
required assign it a file name and specify its location.
To construct a new Diagram Set, the diagram XML files that are to comprise the Diagram
Set must be selected.
To add a single file or multiple files to a new Diagram Set, select the Add Diagrams button:
10:4 12.0
Importing Diagrams
Browse for and select the XML file or files of the diagrams to add to the Diagram Set, and
press the Open button. The default import file location is specified on the File Locations tab
of the Options dialog (see Section 4.2.1: Set Default Import Location).
The selected file or files is then displayed in the diagram list section of the Diagram Set
editor (see below for details of the diagram list section).
To add all the valid XML diagrams within a folder to the file set, select the Add All Files in a
Folder button:
10:5 12.0
Importing Diagrams
A folder browser is then displayed. Browse for the required folder and press OK.
All XML files in the folder that are in the correct format, plus all files listed in Diagram Sets
that are in that folder, are then added to the diagram list.
Notes:
• If an existing Diagram Set is selected or is in a selected folder, its files are added to the
current Diagram Set (its release comments are not included).
• If a text file containing a list of files is selected or is in a selected folder to process, all
the files listed will be added to the Diagram Set.
• If files cannot be added then the user is informed via a warning message, for example
if a file could not be found or is not valid.
• The Add All Files options does not include any subfolders within the selected folder,
only files.
• The diagram name attribute in the schematic database has a maximum length of 50
characters. Diagram names in the schematic database begin with a “/” character. If a
diagram name in an import file does not begin with a “/” character, then P&ID Manager
adds one to the beginning of the diagram name on import.
• Diagram names in import files may therefore be no more than 50 characters, if the
diagram name begins with a “/” character, or no more than 49 characters if the diagram
name does not begin with a “/” character. If these lengths are exceeded then the file will
not be added to the file set. A message will be displayed to inform the user of this.
10:6 12.0
Importing Diagrams
When all the required files have been selected, save the new Diagram Set by selecting the
Save Diagram Set button:
A File Save dialog is then displayed. Specify the name and location of the Diagram Set and
press Save.
Opening an Existing Diagram Set

To open an existing file set, select the Open Diagram Set button:
If there is a Diagram Set already open with unsaved changes, you will be prompted to save
it, and if required assign it a file name and specify its location.
An Open dialog is then displayed. Select the required Diagram Set and press Open. The
contents of the selected Diagram Set are then displayed in the diagram list section of the
Diagram Set Editor.
When opening an existing Diagram Sets, the files it consists of are validated. Any that no
longer exist or are invalid are greyed out in the diagram list section.
Adding and Deleting Files

To add further files to a Diagram Set, use the Add Files and Add All Files in a Folder buttons
are described above.
10:7 12.0
Importing Diagrams
To delete files from a Diagram Set, select the file or files in the diagram list and then select
the Remove Files button:
The selected files are then removed from the diagram list and the Diagram Set.
Save changes to the Diagram Set by using the Save Diagram Set button:
Diagram List
The diagram list section of the Diagram Set Editor lists the files that comprise the current
Diagram Set. It displays the file name and diagram name of each of these files.
It displays details of both new diagrams, i.e. diagrams that are not present in the database,
and existing diagrams, i.e. diagrams that are already present in the database.
Multiple files can be selected in the list using standard Windows methods. By default, the list
is sorted in ascending order of diagram name. Click on a different column heading to sort by
that column instead.
The list section also includes a DB Match field. The DB Match fields display the diagram
name of the diagrams in the database that the listed diagrams will update when the import
takes place.
Where a diagram was placed in this grid by the system, the Matched DB Diagram Name
field will be the same as the entry in the Diagram name. A different diagram can be selected
if required (see below).
To select a diagram name, press the button at the end of the field.
The Select Diagram dialog is then displayed:
10:8 12.0
Importing Diagrams
Browse for the required diagram and press the OK button.

The selected diagram name is then displayed in the DB Match field for the diagram.
10.2.2 Entering Release Comments

Comments field.
Whether or not this field is enabled is also specified on the Project Options dialog.
10:9 12.0
Importing Diagrams
10.2.3 Importing Diagram Sets

To import the diagram data files in a Diagram Set, open the Diagram Set in the Diagram Set
Editor and press the Import Now button. The Import Progress dialog is then displayed. See
10.3: Import Progress Dialog.
Alternatively, select File > Import Diagrams... from the P&ID Manager menu. The Open
Select the required Diagram Set and press the Open button.
Comments dialog, which is automatically displayed.
10:10 12.0
Importing Diagrams
Enter the comments and press the OK button. If the Cancel button is pressed, no release
comments are entered. This does not cancel the import.
Whether or not this dialog is displayed is also specified on the Project Options dialog.
The Import Progress dialog is then displayed. See 10.3: Import Progress Dialog.
10.2.4 Closing the Diagram Set Editor without Saving

If the Diagram set Editor is closed, and here are any unsaved changes to the current
Diagram Set, you will be prompted to save it, and if required assign it a file name and
specify its location.
10.3 Import Progress Dialog

The Import Progress dialog is displayed when diagrams are imported using any of the
facilities on the File menu.
The dialog displays:

• a progress bar for the import process as a whole,
• the number of diagrams already processed out of the total number to be processed,
• the name and status of the task being carried out.
If the dialog is to be closed automatically when the import is complete, check the Close on
import completion checkbox. The default settings of this checkbox is specified on the
Import Settings tab on the Project Options dialog (see Section 3.4: Units Tab).
To close the dialog once the import is finished, press the Dismiss button.
10:11 12.0
Importing Diagrams
10.3.1 Additional Import Details

To display more details of the import process, press the Details button (select the button
again to hide these details).
Tasks Tab
Each diagram is processed in turn. Once this has been completed, P&ID Manager attempts
to match any off-page connections in the imported diagrams with those of diagrams already
in the Schematic database (see 10.3.2: Automatic Matching of Off-Page Connectors). Each
of these tasks is listed in the Task column.
The status of each task is displayed in the Status column and indicated by an icon in the
first column:
Ready: Å
Cancelled: z
Running: Æ
Completed: 3
Completed with warnings: 3
Failed: ³
The Remaining column displays how many steps within task remain to be completed.
Summary and Errors Tabs

The Summary tab displays a textual description of the import as it happens.
10:12 12.0
Importing Diagrams
The Errors tab lists details of import errors as they are detected.
Note: After data has been imported it must be saved to the database. See 10.5: Saving
Imported Data.
10.3.2 Automatic Matching of Off-Page Connectors

As part of the import process, P&ID Manager attempts to automatically match any off-page
connectors (OPCs) in the imported diagrams with those of diagrams already in the
Schematic database.
In order for two OPCs to be matched:
• They must be of different types, i.e. one must be a SCOPCO (connector out) and the
other must be a SCOPCI (connector in).
• The data for each OPC includes a reference to a diagram that the other end of the
connection (the other OPC) is located on. This is known as the Match Diagram.
The Match Diagram of one OPC must be the diagram on which the other OPC is
located, and vice versa.
• The data for each OPC includes a reference to a Match Attribute. This is a reference to
an attribute of the other end of the connection. Each end of the connection must have
the same Match Attribute.
• The data for each OPC includes a Match Attribute Value. The Match Attribute Value for
one end of the connection must be the value of that attribute at the other end of the
connection, and vice versa.
• The match must be unique.
10:13 12.0
Importing Diagrams
For example, the OPCs with the following data would be matched automatically (assuming
the connection is unique):
OPC Type & Diagram SCOPCO on 905675 SCOPCI on 905677

Match Diagram 905677 905675
Match Attribute PersistentId PersistentId
Match Attribute Value 0123456 6543210
PersistentId 6543210 0123456
10.4 Importing using PML

It is possible to import P&IDs in non-graphics (tty) mode using PML. This enables batch
scripts to execute imports without user interaction. For example:
1. Create a folder called TestImport in your PDMS installation folder.
2. Create a file in the TestImport folder called import.bat with the following contents:
../pdms tty <project> <user>/<password> <mdb> $M/import.mac
3. Create a file in the TestImport folder called import.mac with the following contents:
design
!pid = object PIDManager()
!result = !pid.ImportFile('<P&ID filename and path>')
if (!result NE -1) then
savework
endif
finish
4. Run import.bat either from a command prompt or by double clicking on it from the file
explorer.
10.4.1 Preliminaries
All imports are executed using an instance of the PIDManager PML object. A PIDManager
object may be created as in the following example:
!pid=object PIDManager()
It is possible to see the methods available on this object by using the command:
10:14 12.0
Importing Diagrams
Q methods !pid
The first time the command line is used to import P&IDs after installing P&ID Manager the
user may need to execute the 'PML REHASH ALL' command to update the PML library
index file. If this hasn't been done then the following error message will be displayed:
10.4.2 Importing Diagrams

There are three ways of importing diagrams using the Command Window.
• Individually, by specifying the filename of a single diagram.
• Collectively, by specifying a folder containing diagram files - all valid diagrams in that
folder are imported.
• Collectively, by specifying a File Set - all valid diagrams in that file set are imported.
For a description of what File Sets are and how they are created see 10.2: Diagram Set
Import Facility.
Note: Once diagrams have been imported, a Save Work must take place to save changes
to the database. See 10.5: Saving Imported Data.
Importing Diagrams Individually

To import a single diagram enter the following:
!IMPORTFILE('File path and file name’)
If release comments are required, enter (refer to 10.2.2: Entering Release Comments):
!IMPORTFILE('File path and file name','Release Comment')
For example:
!IMPORTFILE('V:\P&ID Manager\TestData\905675.xml',
'Update to Diagram')
10:15 12.0
Importing Diagrams
The specified file is then imported. The Command Window displays progress, error and
warning messages as the import is carried out, for example:
If the specified file is invalid or missing, an error message “File Not Found” will be
displayed.
Importing Diagrams from a Folder

To import the diagrams in a folder enter the following:
!IMPORTFILESINDIR('Folder’)
If release comments are required, enter (refer to 10.2.2: Entering Release Comments):
!IMPORTFILESINDIR('Folder','Release Comment')
For example:
!IMPORTFILESINDIR('V:\P&ID Manager\TestData\','Update to
Diagrams')
The files in the specified folder are then imported. The Command Window displays
progress, error and warning messages as the import is carried out, for example:
If the specified folder is not found, an error message “Directory doesn’t exist” will be
displayed.
10:16 12.0
Importing Diagrams
If any of the files in the folder are invalid, an error message “File type not
recognised” will be displayed for each of them. The import procedure will then ignore the
invalid files.
Importing Diagrams from a Diagram Set

To import the diagrams in a Diagram Set enter the following:
!IMPORTFROMFILESET('Diagram Set’)
For example:
!IMPORTUSINGCONFIGFILE('V:\P&ID Manager\
ImportFileSet.xml')
The files in the specified Diagram Set are then imported. The Command Window displays
progress, error and warning messages as the import is carried out, for example:
Viewing Import Messages

Once an import has taken place, a return value is provided that indicates the success (or
otherwise) of the operation.
A value of type REAL is returned. The values and their meanings are as follows:
-1 = Error
0 = Success
1 = Imported with warnings.
All import messages, warnings and errors are written to a log file. This log file is available for
a period of 14 days, after which it is deleted. A new log file is created for every time P&ID
Manager is run, i.e. every time the DESIGN or LEXICON module is entered by a user.
There is a method on the PIDManager PML object that provides the full pathname of the
current logfile, in order to determine which log file relates to an import:
• !logfile = !pid.logFile()
Q !logfile
C:\AVEVA\Plant\PDMS12.0.SP4\P&ID Manager\Logs\
9fjvegnk.log
10:17 12.0
Importing Diagrams
10.5 Saving Imported Data

Imported data is not saved into the Schematic database until a Save Work takes place.
To save changes to the database using the user interface, either select the Save Work
toolbar button , or select the Save Work option from the Design menu.
To save changes to the database using the command line, enter 'savework' at the command
prompt.
10:18 12.0
P&ID Manager Explorer
11 P&ID Manager Explorer
Once imported into the Schematic database, P&ID data can be viewed in a hierarchical data
Explorer in the DESIGN module.
The Explorer can also be used to release the data in the Schematic database to the AVEVA
Schematic 3D Integrator.
11.1 Opening the P&ID Manager Explorer

To open the P&ID Manager Explorer, select Display > Explorer from the P&ID Manager
menu.
The P&ID Manager Explorer is then displayed.
11:1 12.0
11.2 Element Hierarchy in the Explorer

Each element in the Schematic database is assigned a element type (TYPE). Elements in
the Explorer are arranged by TYPE, in the following hierarchy:
Schematic Worl *
SCGROU (may contain further SCGROUs)
SCPLIN
SCBRAN
SCSEG
SCTUB
SCVALV
SCINST
SCFITT
SCOPCO
SCOPCI
SCPDES
SCDUCT
SCHVFI
TEXT
TEXT
SCHVAC
(same as under SCPLIN - see above)
SCEQUI
SCSUBE
SCNOZZ
SCELCO
TEXT
SCNOZZ
SCELCO
TEXT
SCOINS
TEXT
SCCAB
SCCORE
SCDIAG
SCTEMP
SCSTEN
Note: Element Types in italics cannot be imported into the database using P&ID Manager.
However, they can be created using other methods such as the Create menu options
(see below), or the command line, so they may appear in Explorer.
11:2 12.0
Schematic WORL *: The topmost level of the Schematic database hierarchy within which
all other elements exist. Cannot be moved, renamed or deleted.
SCGROU: Administrative elements containing groups of elements.
By default, groups for Diagrams, Instruments, Equipment and Pipelines are created
automatically when these elements are imported into the database. Other groups are
created as required by users (see Section 11.3.4: Creating Elements). The default groups
can be changed using the Options dialog (see Section 3.3.1: Viewing/Editing Import
Destination SCGROUP Elements), or by setting the OWNER attribute using the attribute
mapping facilities (see Section 6: Viewing/Editing Attribute Mappings).
Note: Groups may also contain other groups, which may in turn contain any of the
elements a higher level SCGROU may contain.
SCPLIN: Pipelines.
SCBRAN: Pipe branches.

TEXT: Text used to store information about the identity of items. This is provided for use by
the system and should not be deleted or renamed by users.
SCSEG: Page/pipe segments.
SCTUB: Tubing.
SCVALV: Valves.
11:3 12.0
SCINST: Inline Instruments.

SCFITT: Inline Fittings.
SCOPCI: Off-page connection (in).
SCOPCO: Off-page connection (out).
SCPDES: Pipe destination.
SCDUCT: Ducting.
SCHVFI: HVAC fitting.
SCHVAC: HVAC.
SCEQUI: Equipment.
SCSUBE: Sub-equipment.
SCNOZZ: Equipment nozzles.
SCELCO: Electrical connections.
SCOINS: Offline instruments.
SCCAB: Cables.
SCCORE: Cable cores.
11:4 12.0
SCDIAG: Diagram elements.
SCTEMP: Templates.
SCSTEN: Stencils.
11.3 Using the Explorer
11.3.1 Element Right-Click Menus

To perform actions on an element, right-click on it to display a right-click menu on which the
actions that can be carried out on the element are displayed, i.e.:
World Menu:
11:5 12.0
Group Menu:
Diagram Menu:
Other “Releasable” Elements Menu:
11:6 12.0
Off-page Connector Menu:
Other Elements Menu:
11.3.2 Applying a Filter

The displayed elements can be filtered so that only diagram elements and elements above
diagrams in the hierarchy are displayed.
To apply the filter, check the Filter checkbox.
The filter is then applied.
11.3.3 Viewing Element Attributes

To view the attributes of an element, right-click on the element and select the Attributes
option.
The Attributes Form is then displayed, on which the attributes of the selected, element are
displayed.
11:7 12.0
All data displayed on the form is read-only.

By default, the form is configured to automatically change to display the attributes of the
element currently selected (the current element or CE). To turn this functionality on or off,
right-click on the Attributes Form and choose the 'Track CE' option from the menu that is
then displayed.
11.3.4 Creating Elements

To create a diagram, right-click on the element in the hierarchy beneath which the new
element is to be created. For example, to create a SCBRAN element, right-click on the
SCPLIN element beneath which it is to be created, or to create a SCEQUI element, right-
click on the relevant SCGROU element.
Select the required element type from the Create menu.
11:8 12.0
The new element is created without a name and is placed beneath the selected element in
the element hierarchy.
Elements are shown in the P&ID Manager Explorer with their TYPE and element sequence
number (SEQU) combined.
Elements can be renamed if required (see below).
11.3.5 Deleting Elements

To delete elements other than diagrams, select the element, right-click, and select the
Delete option from the menu. The Confirm Delete dialog is displayed.
11:9 12.0
Note: If an element is deleted, all elements beneath it in the element hierarchy are also
deleted.
Press the OK button to complete the deletion.
Deleting Diagrams
To delete a diagram, select the diagram element, right-click, and select the Delete option
from the menu. The Delete Diagram dialog is then displayed.
The name of the selected diagram is displayed in the title bar of the dialog.
To delete only the diagram, leaving those elements associated with it (i.e. the items on the
diagram) in the database, select the Diagram Only option.
To delete both the diagram and associated elements, select the With Contents option. Note
that elements that are also associated with other diagrams are not deleted.
Press the OK button to complete the deletion.
11.3.6 Renaming Elements

To rename an element, select the element, right-click, and select the Rename option from
the menu. The Name dialog is displayed.
11:10 12.0
Enter the new name of the element and press the Apply button. Refer to PDMS Design
documentation for additional details of this dialog.
Enter the name of the new element. The following characters are not permitted in the name
of an element:
$ @ * ' '
A name may be a maximum of 50 characters.
It is not recommended that SCDIAG elements are renamed once loaded as it will affect the
ability of P&ID Manager to maintain the data associated with the diagram. Rather than
rename a diagram, it may be better to delete the diagram element and its related elements
from the database and re-import the diagram with the new name.
11.3.7 Moving Elements

Elements can be moved to different locations in the element hierarchy. To move an element,
select it, and use the mouse to drag and drop it to the required location.
Alternatively, right-click on the element and select the Cut option from the menu. Select the
element in the hierarchy beneath which the element is to be placed, right-click, and select
the Paste option from the menu. The element is then moved to the selected location.
Note: The selected location must be valid for the element type in the hierarchy. For
example, a diagram element can be placed beneath a group element, but not the
other way round.
11.3.8 Viewing Diagrams

To view a diagram, select the diagram element, right-click, and select the Show Diagram
option from the menu.
The diagram is then displayed in the P&ID Manager Diagram Viewer.
Note that when an item on an imported diagram is selected, it becomes the current element
(i.e. is selected) in the P&ID Manager Explorer.
See Section 12: Viewing Imported Diagrams for details.
11.3.9 Setting-up and Editing Off-Page Connections

To select or edit the source or target connector to which an off-page connector is connected,
right-click on the connector element (SCOPCI or SCOPCO) and select the Diagram
11:11 12.0
Connector option from the menu. The Diagram Connector dialog is then displayed. See
Section 13: Diagram Connector.
11.3.10 Releasing and Unreleasing Data
Releasing Data to the 3D Model

When an element is released (Release status set to “ON”) it is made available to the AVEVA
Schematic 3D Integrator i.e. the element in the Schematic database is made accessible to
the AVEVA Schematic 3D Integrator for integration with the 3D Design Model database.
The following types of element can be released:
SCDIAG
SCEQUI
SCOINS
SCPLIN
SCSEG
When an element is released, all its “child” elements (i.e. the elements beneath it in the
database, such as the nozzles of an equipment item) are released as well. Such elements
cannot be released independently of their parent elements.
When a diagram element is released, all elements that appear on that diagram are also
released.
To release an element and its child elements, right-click on it and select the Release to 3D
Status – ON option from the menu.
To release all the elements in a group that are eligible for release, right-click on the
SCGROU element in question and select the Release to 3D Status – ON option from the
menu.
To release all elements in the database that are eligible for release, right-click on the
WORL* element and select the Release to 3D Status – ON option from the menu.
The Comment dialog may then be displayed.
Whether or not this dialog is displayed is specified on the Element Release tab of the
Options dialog. See Section 3.1.2: Display Comments Dialog on Release to 3D.
Enter comments as required, and press the OK button to complete the release.
11:12 12.0
Unreleasing Data
To Unrelease an element, so that it is no longer available to the AVEVA Schematic 3D
Integrator right-click on the element and select the Release to 3D Status – OFF option from
the menu.
The Comment dialog may then be displayed as described above. Enter comments as
required, and press the OK button
The element and all its child elements are no longer accessible by the AVEVA Schematic 3D
Integrator.
11.3.11 Saving Changes

To save changes to the Schematic database, either select the Save Work toolbar button ,
or select the Save Work option from the Design menu.
Note: Changes made in the explorer are not saved into the database until a Save Work
takes place.
11:13 12.0
11:14 12.0
Viewing Imported Diagrams
12 Viewing Imported Diagrams
Note: For the procedure for previewing diagrams before they are imported, see 9:
Previewing Diagrams before Import.
12.1 Selecting Diagrams to View

To view an imported diagram, either:
• select a diagram or diagrams in the P&ID Manager Explorer, right-click, and select
Show Diagram from the menu that is then displayed:
• or select a diagram or diagrams in the P&ID Manager Explorer, and drag and drop
them into the Diagram Viewer.
• or select a diagram or diagrams in the P&ID Manager Explorer, and select Display >
Diagram Viewer from the P&ID Manager menu in the DESIGN module.
If no diagram is selected when the menu option is selected, the Diagram Viewer will
open without a diagram being displayed.
12:1 12.0
• or once the Diagram Viewer is open, use the View Diagram dialog to select and open a
diagram:
1. Select the View Diagram button from the Diagram Viewer toolbar: .
2. The View Diagram dialog is then displayed:
3. The Diagram Page window lists all the diagrams in the database.
4. To preview a diagram, check the Preview checkbox and select the diagram from
the Diagram Page list. The preview is then displayed in the left-hand window.
12:2 12.0
• To zoom into an area of a diagram preview, hold down the Ctrl key and left-click
on one corner of the area and then drag the cursor to the opposite corner of the
area.
• With the cursor over the diagram preview, press Ctrl and click on the diagram
preview to zoom in.
• With the cursor over the diagram preview, press Ctrl+Shift and click on the
diagram preview to zoom out.
• To pan, hold down Alt and the left mouse button and drag the cursor in the
required direction.
5. To reduce the number of diagrams listed in the Diagram Page window, or to search
for specific diagrams, use the Search For field and Search button.
Enter all or part of a diagram name in the Search For field and press the Search
button.
The list of diagrams is then restricted to those with names containing the search
criteria.
The following wildcards may be used in the search criteria:

• * - matches 0 or more characters
• + - matches 1 or more characters
• ? - matches only 1 character
• # - matches a digit
• [..] - matches 1 character against the given character set
To display all diagrams again, clear the Search For field and press the Search
button.
12:3 12.0
6. To open a diagram, select it from the list and press the OK button.
12.2 P&ID Manager Diagram Viewer
Each P&ID open is displayed on a tab, labelled with diagram name.
12.2.1 Highlighting and Selecting Items

Click an item in a diagram to highlight and select it. The item is displayed enclosed in a red
dashed line.
12:4 12.0
When an item is selected, it becomes the current element and is selected in the P&ID
Manager Explorer.
12.2.2 Diagram Connectors

To open the diagram that is the source or target of an off-sheet connector on the current
diagram, right-click on the connector and select the Go To Connected OPC option from the
menu that is then displayed.
The connected diagram is then opened in the viewer. If the option is disabled, no connection
exists. The connector is also highlighted and made the current element as described above.
To set up or edit a page connection, select the Diagram Connector option from the menu.
The Diagram Connector dialog is then displayed. See Section 13: Diagram Connector.
12:5 12.0
12.2.3 Other Viewer Functionality

For details of the diagram viewer toolbar and other general viewer functionality, refer to
Section 9.2: P&ID Manager Diagram Viewer.
12:6 12.0
Diagram Connector
13 Diagram Connector
Connections between Off-Page Connectors (OPCs) may be established automatically when

diagram data is imported (see 10.3.2: Automatic Matching of Off-Page Connectors). The
Diagram Connector is used to edit existing connections, and to set connections between
OPCs that were not established on import.
The Diagram Connector is opened by:
• Selecting the Tools > Diagram Connector... option from the P&ID Manager menu in
the DESIGN module.
• Right-clicking on an off-sheet connector element in the P&ID Manager Explorer and

selecting the Diagram Connector option.
The Diagram Connector dialog is then displayed.
13:1 12.0
Diagram Connector
13.1 Diagram Connector Dialog
When then dialog is opened, if the Current Element (CE) is an off-page connector, the
Source OPC field is automatically completed with that connector. This is always the case
when the dialog id opened from the P&ID Manager Explorer.
If there is already a connection set up for that off-page connector, the connected off-page
connector is displayed in the Target OPC field. Otherwise, the field will be blank.
If the dialog was opened from the P&ID Manager menu and the CE was not an off-page
connector, both fields will be blank. The source connector must therefore be selected.
Note: “Source” and “Target” is no indication of the type of off-page connector, i.e. “Source”
does not indicate that a connector is a SCOPCO (connector out) and “Target” does
not indicate that a connector is a SCOPCI (connector in).
In this context, the “Source” connector is the subject of this procedure, to which a
selected “Target” connector is connected.
13.1.1 Selecting or Changing the Source Off-page Connector

If the Source OPC field is blank, proceed as follows to select a source off-page connector.
If the Source OPC field is populated, use this procedure to select a different source off-page
connector.
An off-page source connector can be selected either by setting the current element as the
off-page source connector, or by selecting a connector from a list.
To set the current element as the source:
• select the required off-page connector (SCOPCO or SCOPCI) in the P&ID Manager
Explorer and the press the CE button next to the Source OPC field.
• Use PDMS Saved Searches (see Section 14: Standard Searches) to locate the
required off-page connector, right click on the search result and select the Navigate To
option from the menu that is then displayed.
Note: There are P&ID Manager saved searches that can be used for finding connected,
unconnected and manually connected OPCs.
• Select the OPC on a diagram in the Diagram Viewer (see Section 12.2.2: Diagram
Connectors).
13:2 12.0
Diagram Connector
To select the required off-page connector from a list, press the ... button next to the Source
OPC field. The OPC Browser dialog is then displayed.
The browser displays a list of all off-page connectors in the database.

The first column displays an indication of the quality of the match of the current connection
(if any) of each of the listed off-page connectors.
A green tick indicates the connection was made automatically on import, an orange tick
indicates that the connection was made manually using the Diagram Connector, while a red
cross indicates that the connector has no connection.
The names of each connector and the diagrams and lines on which they are located is
displayed. Connectors can be sorted by clicking on the column headings.
To select a connector, either double-click on it, or click on it once and press the OK button.
Once a connector is selected, the Source OPC field is populated with the name of the
selected connector. If there is an existing connection set up for this connector, the name of
the connected off-page connector is displayed in the Target OPC field.
13.1.2 Setting up a Connection

Once a source off-page connector has been selected, a connection can be established by
selecting a target off-page connector.
If a connection has already been established for the source off-page connector, it can be
edited (see 13.1.4: Editing a Connection).
To select a target off-page connector, proceed as described above for selecting a source off-
page connector, either by selecting the current element or choosing a connector from a list.
Target off-page connectors cannot be of the same type as the source off-page connector.
For example, if the source off-page connector is a SCOPCO, the target must be a SCOPCI.
The CE button is therefore only active if the correct type of off-page connector is selected in
the P&ID Manager Explorer, and the list of connectors in the OPC Browser dialog only
includes connectors of this type.
13:3 12.0
Diagram Connector
The list only includes connectors that are not currently connected (as indicated by the red
cross in the first column).
To select a connector, either double-click on it, or click on it once and press the OK button.
Once a connector is selected, the Target OPC field is populated with the name of the
selected connector.
To connect the source and target OPCs, press the Connect button.
If a user attempts to match two connectors that are not part of the same SCPLINE the
following warning message is displayed:
Select the OK button to set up the connection anyway, or the Cancel button to abort the
operation.
If the connection cannot be established, an error message is displayed indicating the
reason, for example:
If the connection is made successfully, the following message is displayed:
13:4 12.0
Diagram Connector
Once a connection is saved the Target OPC field is greyed out, the adjacent buttons
disabled and the Connect button replaced by a Disconnect button.
13.1.3 Connection Details

Details of the source and target connections are displayed in fields in the main part of the
dialog, under the headings of Source OPC and Target OPC.
The diagram (SCDIAG), line (SCPLINE), branch (SCBRANCH) and segment

(SCSEGMENT) on which the connections are located are displayed.
These elements can be made the current element, i.e. they will be selected in the P&ID
Manager Explorer, either by double-clicking on them, or right-clicking and selecting
Navigate to from the menu that is then displayed.
The Type fields displays the type of each connector, i.e. SCOPCO or SCOPCI.
The Match SCDIAG fields display the names of the diagrams that each connector connects
to.
The Match attribute fields display the names of the source data attribute used to match the
connectors to each other.
The Attribute match value fields display the values of the source data match attributes.
The bottom three fields indicate the quality of the match between the two connectors.
The SCDIAGs matched? field:
• If “Yes” is displayed in both fields and a green tick is displayed in the left-hand column,
this indicates that both connectors refer to the diagram that the other is located on.
In other words, the Match SCDIAG of the source connector is the diagram that the
target connector is located on and vice versa.
• If “Yes” is displayed in one field and “No” in the other, and an orange tick is displayed in
the left-hand column, this indicates that one of the connectors refers to the diagram that
the other is located on (the connector displaying “Yes”), but the other connector does
not.
13:5 12.0
Diagram Connector
In other words the Match SCDIAG of the source connector is the diagram that the
target connector is located on, but the Match SCDIAG of the target connector is not the
diagram that the source connector is located on, or vice versa.
• If “No” is displayed in both fields and a red cross is displayed in the left-hand column,
this indicates that the Match SCDIAG field of neither connector refers to the diagram
that the other is located on.
The SCPLINEs matched? field:
this indicates that both connectors are on the same SCPLINE.
this indicates that the connectors are on different SCPLINEs.
The Match attributes matched? field:
this indicates that both connectors have match attributes that satisfy the attribute
connection criteria.
• If “Yes” is displayed in one field and “No” in the other, and an orange tick is displayed in
the left-hand column, this indicates that one of the connections has a match attribute
that satisfies the connection criteria specified in the source data, but the other does not.
this indicates that neither connector has match attributes that satisfy the attribute
connection criteria.
See 10.3.2: Automatic Matching of Off-Page Connectors for an explanation of match
attributes.
13.1.4 Editing a Connection

To edit an existing connection, select the off-page connection at one end of the connection
in the Source OPC field as described above.
The Target OPC field is then populated with the off-page connection at the other end of the
connection. The field is greyed out and the adjacent buttons disabled.
Press the Disconnect button. The Target OPC field and adjacent buttons then become
active. Select another target off-page connection as described above.
13:6 12.0
Standard Searches
14 Standard Searches
P&ID Manager extends the search capability of the DESIGN module Search Utility by
adding a series of standard P&ID Searches to the saved searches section of the tool. The
screenshots below include the list of available searches at the time of writing but additional
ones may be added during this, or future, versions.
14.1 Using the Standard Searches

To access the Search Utility, if not already open, select Display > Search Utility from the
PDMS Main Menu.
From the Search Utility the P&ID Manager searches can be accessed by opening the Saved
Searches section at the bottom of the Utility then selecting P&ID Manager from the Select
dropdown list:
You can then load one of the searches using the next dropdown list and selecting the
Search button:
At this point the search has been run and the results shown in the Search Results window.
You will see the Search Utility has also been populated with the criteria used which can now
be modified and adjusted to further refine the search. It should be noted however that the
searches cannot be overwritten. If you wish to save a modified search you must do this by
saving it under a different name.
14:1 12.0
Standard Searches
14.2 Search Toolbar

The search toolbar, below, can also be used to run a standard search. Selecting P&ID
Manager from the Locations dropdown will enable you to then select the search you require.
Selecting the Search button will then display the search results in a results window.
14:2 12.0
P&ID Manager Reports
15 P&ID Manager Reports
Reports can be run on the Schematic database. The following report templates are provided
for this purpose:
Template Name Report Content

PIDManagerEquipmentList.tmp Equipment List
PIDManagerInstrumentIndex.tmp Instrument Index
PIDManagerLineList.tmp Line List
PIDManagerNotReleasedItems.tmp Items which have not been released
PIDManagerOffPageConnectors.tmp All Off Page Connectors (including
unconnected)
PIDManagerReleasedItems.tmp Items which have been released
PIDManagerUnconnectedOffPageConnectors.tmp Unconnected Off Page Connectors
PIDManagerValveList.tmp Valve List
To run a report
Select Utilities > Reports > Run from the main menu.
To view or modify a template
Select Utilities > Modify > Report.
To create a new template
Select Utilities > Reports > Create.
For further details
Refer to the Reporting Using PDMS manual.
15:1 12.0
P&ID Manager Reports
15:2 12.0
P&ID Manager in LEXICON
16 P&ID Manager in LEXICON
The P&ID Manager facilities in the LEXICON Module are used to:
• specify which User Defined Attributes (UDAs) are available in each schematic
database with which P&ID Manager operates,
• configure UDA properties,
• map UDA and other database attributes to attributes from the diagram data source
files.
16.1 Opening the LEXICON Module with P&ID Manager

Installed
If P&ID Manager is installed, the following message may be displayed when LEXICON is
opened:
To prevent this message from being displayed again, check the Don’t show this again
checkbox.
To configure UDAs, press the OK button. Continue at 16.2: Configuring UDAs. Otherwise
press Cancel.
16.2 Configuring UDAs

The UDA Catalogue dialog is used to specify which User Defined Attributes (UDAs) are
available in each schematic database with which P&ID Manager operates.
This dialog can be opened automatically when LEXICON is started (see above), or from the
UDA Catalogue option on the P&ID Manager menu.
Before this dialog is opened, the system checks the number of schematic databases that
the user can write to.
16:1 12.0
If the user has write access to more than one database, the following dialog is displayed,
listing these databases:
Select the dictionary database to store the UDA definitions and press OK. The UDA
Catalogue dialog then opens with information on the P&ID Manager UDAs.
If the user has write access to a single dictionary database, the UDA Catalogue dialog will
open with information on the P&ID Manager UDAs, and configures them in the dictionary
database that it has access to.
If the user does not have write access to any databases, UDA Catalogue dialog opens but a
message is displayed indicating that either there are no “writeable” databases, or that the
user does not have permission to write to them.
16:2 12.0
16.2.1 UDA Catalogue Dialog
16:3 12.0
If there are no “writeable” databases, or the user does not have write access to them, the
UDA catalogue is displayed, but the user can make no changes - all buttons and
checkboxes are disabled.
If the user does have write access to a dictionary database, the dialog lists the UDA
catalogue and indicates whether or not each UDA is in that database, and whether or not
attribute mapping has been set up for it.
The name and description of each UDA is displayed.
If a UDA is present in the schematic database, the following icon is displayed in the UDA
row: .
If a UDA is present in the schematic database and attribute mapping has been set up for it,
the following icon is also displayed in the UDA row: .
To add a UDA to the database, check the checkbox at the end of the row. To remove it,
uncheck the checkbox.
To check the checkboxes for all UDAs, press the Select All button.
To uncheck the checkboxes for all optional UDAs, press the Deselect All button.
To open the attributes dialog for a UDA, either double-click on it, or right-click and select the
Attributes option from the menu that is then displayed. See 16.2.2: Viewing and Editing
UDA Attributes.
To view the attribute mapping that is associated with a UDA right click on the UDA in the list
and select the Attribute Mapping… option. (see 6: Viewing/Editing Attribute Mappings).
To make a UDA the current element, right-click and select the Set as CE option from the
menu that is then displayed.
Press the Undo button to undo any changes made since the dialog was opened.
Press the Apply button to save changes.
If any UDAs have been removed from the database, a message is displayed requesting that
the deletion of these UDAs and associated attribute mappings be confirmed:
16:4 12.0
16.2.2 Viewing and Editing UDA Attributes

The attributes of UDAs and viewed and edited using the UDA Database Element dialog.
The dialog displays the attributes of the UDA currently selected in the UDA Catalogue
dialog. If the UDA is present in the dictionary database, the attributes displayed are those of
the UDA in that database, rather than the default catalogue attributes for the UDA.
Edit the attributes as required. Those attributes with values displayed in grey instead of
black text cannot be edited.
16.3 Viewing/Editing Attribute Mapping

To map system/project specific attributes from the source files to schematic or user defined
database attributes, or to view existing mappings, use the Attribute Mapping dialog.
For details see 6: Viewing/Editing Attribute Mappings.
16:5 12.0
16:6 12.0
Appendices
17 Appendices
17.1 Appendix A: Regular Expressions

This appendix explains how to use regular expressions to specify the GTYPE, and
optionally the SCSTYPE, that will be automatically mapped to an ISO15926 component
class when using the Auto Complete feature of the Options dialog (see 7.2: Setting up Rules
for Automatic Completion of ISO 15926 Mappings in 3.4.1 Viewing/Editing ISO 15926
Mappings). It is not intended as a comprehensive guide to Regular Expressions.
Regular Expressions are used to identify text containing characters, words, or patterns of
characters.
Regular Expressions are written in a formal language that can be interpreted to identify text
that matches the provided expression. Regular expression use metacharacters, which are
characters which have a special meaning, and literals, which are the string you wish to
match.
In this section all example Regular Expressions are shown in Courier New. All examples
of text that would match a Regular Expression used as an example are shown in Courier
New Bold.
The following operations are used to construct regular expressions.
17.1.1 Alternation
A vertical bar is used to separates alternatives. For example, CHECK|CHK will match both
CHECK and CHK.
17.1.2 Grouping
Parentheses are used to define the scope and precedence of the operators. For example:
analog|analogue
and…
analo(g|(gue))
These are equivalent, and would return positive matches on both analog and analogue.
Parentheses have other uses in Regular Expression construction which are beyond the
scope of this guide.
17:1 12.0
Appendices
17.1.3 Quantification using Metacharacters

A quantifier after a character or group defines how often the preceding element may occur.
The most commonly used quantifiers are ?, *, and +.
• ? The question mark indicates there is zero or one of the preceding element. For
example, too? matches both to and too.
• * The asterisk indicates there are zero or more of the preceding element. For example,
ab*c matches ac, abc, abbc, abbbc, and so on.
• + The plus sign indicates that there is one or more of the preceding element. For
example, ab+c matches abc, abbc, abbbc, and so on, but not ac.
The following table contains explanations of the meaning of some commonly used Regular
Expression metacharacters, and provides some simple examples of their use, to define how
P&ID Manager may automatically determine the GTYPE and optionally the SCSTYPE that
should be applied to an ISO15926 component class when executing the 'Auto Complete'
option.
Metacharacter Description Example

Example:
(3.*(WAY VALVE))
Matches any character What this expression means:
except a newline. If used Matches any component class which
. inside square brackets contains with any two characters
then the dot is treated as a (including space) followed by "WAY
literal. VALVE"
Example matches using expression:
3 WAY VALVE
Example:
((BLI..).(SP...))
What this expression means:
Groups a series of pattern Matches any component class which
( ) elements to a single contains BLI followed by any 2 characters
element followed by any 1 character followed by
SP followed by any three characters.
BLIND SPADE
Example:
(CLOSED.4+)
Matches the preceding
Matches any component class name
+ pattern element one or
which contains CLOSED followed by any
more times.
character followed by 4.
CLOSED 4 WAY VALVE
17:2 12.0
Appendices

Example:
(CLOSED.4?)
Matches the preceding Matches any component class name
? pattern element zero or which contains CLOSED followed by any
one times. character and optionally followed by 4.
CLOSED 4 WAY VALVE
CLOSED VALVE
Example:
(4.*WAY VALVE)
Matches the preceding Matches any component class name
* pattern element zero or which contains 4 followed by zero or one
more times. characters followed by WAY VALVE
4WAY VALVE
4 WAY VALVE
Example:
X{1,1}
Denotes the minimum M What this expression means:
{M,N} and the maximum N match Matches any component class name
count. which contains one and only one X
FLEXIBLE HOSE
Example:
[123]
Denotes a set of possible which contains 1,2 or 3
[...]
character matches.
1 WAY VALVE
2 WAY VALVE
DIAPHRAGM ACTUATED 3 WAY BALL
VALVE
17:3 12.0
Appendices

Example:
[1-3]
Matches a range of Matches any component class name
characters (alpha and which contains a character within the
[n1-n2] numeric), where n1 is the range 1 to 3
start of the range and n2
the end.
1 WAY VALVE
2 WAY VALVE
DIAPHRAGM ACTUATED 3 WAY BALL
VALVE
Example:
(SELF ACTING|AUTOMATIC)
Separates alternate
| which contains SELF ACTING or
possibilities.
AUTOMATIC
SELF ACTING GLOBE VALVE
AUTOMATIC GLOBE VALVE
Example:
(AP)\b
\b Matches a word boundary.
which contains a word ending in AP
FLAME TRAP
END CAP
Example:
\W
Matches a non-
\W which contains a non alphanumeric
alphanumeric character.
character such as a space
Any component class name which
contains a non alpha numeric character
17:4 12.0
Appendices

Example:
3\s
Matches a whitespace
which contains a 3 followed by a
\s character (space, tab,
whitespace character
newline, form feed)
3 WAY VALVE
DIAPHRAGM ACTUATED 3 WAY
VALVE
Example:
2\S
Matches anything BUT a
\S which contains a 2 followed by any non
whitespace.
whitespace character
2WAYVALVE
CLOSED2WAYVALVE
Example:
\d
Matches a digit, same as Matches any component class name
\d
[0-9]. which contains a single digit
PISTON ACTUATED 4 WAY VALVE
CLOSED 3 WAY VALVE
\D Matches a non-digit. Matches any component class name
which contains a non digit
Example:
^(PISTON)
Matches the beginning of a
^ which begins with PISTON
line or string.
PISTON ACTUATED 4 WAY VALVE
PISTON ACTUATED GENERAL
VALVE
17:5 12.0
Appendices

Example:
(FILTER)$
Matches the end of a line Matches any component class name
$
or string. which ends with FILTER
INLINE BASKET FILTER
INLINE FILTER
Matches the beginning of a For the purposes of component class
\A string (but not an internal mapping this is equivalent to ^
line).
Matches the end of a string For the purposes of component class
\Z
(but not an internal line). mapping this is equivalent to $
Matches every character What this expression means:
[^...] except the ones inside Allows a component class to be selected
brackets. based on a list of excluded characters.
17.1.4 Regular Expression Guidelines
Case
Regular Expressions are case sensitive, and capitalised metacharacters often have different
meanings to their lowercase equivalents.
By default regular expression matching is also case sensitive.
Component class names in an ISO15926 format import file are in Camel case. Camel case
is the practice of writing compound words or phrases, in which the words are joined without
spaces and are capitalised within the compound. For example:
BallValve
On importing an ISO15926 file, P&ID Manager converts component class names from
Camel case to upper proper case. The above example would be converted to:
BALL VALVE
All ISO 15926 Designator references made within P&ID Manager should be in upper proper
case.
All references made to ISO 15926 designators in auto complete rules, either in full, as in:
BALL VALVE
...or as part of a regular expression:
^BALL
Matching
To match a group of characters, surround the characters with parenthesis. For example:
(PINCH VALVE)
Will find a match wherever PINCH VALVE appears in a Component Class, such as:
17:6 12.0
Appendices
PISTON ACTUATED PINCH VALVE

PINCH VALVE
To exactly match a literal in a regular expression ensure that the expression begins with the
^ character and ends with the $ character. For example:
^(PINCH VALVE)$
This will match PINCH VALVE but will not match PISTON ACTUATED PINCH VALVE.
Escape Sequence
An escape sequence is a way of using a metacharacter as part of the search criteria of a
regular expression. This is done by placing the \ (backslash) character in front of the
quantifier.
For example the regular expression \* will find the * character in the component class name
BAG*FILTER.
17:7 12.0
Appendices
17.2 Appendix B: Releasing to 3D and the Schematic

Database
P&ID Manager release related behaviour is designed to provide a method of controlling
AVEVA Schematic 3D Integrator’s access to schematic data. AVEVA Schematic 3D
Integrator may only take data from the schematic database for inclusion in a PDMS 3D
Model, when that data has been released.
Elements of the following type may have release related behaviours applied to them:
• SCOINS
• SCEQUI
• SCSEG
Other element types are not displayed by the AVEVA Schematic 3D Integrator.
In addition, if the descendents of a schematic element may be of one or more of the above
types, then release related actions may be initiated from the parent (such as a Release or
Un-Release). In these cases release related actions will operate on the children (that can
be released) of the parent.
Schematic elements which may be parents are:
• Schematic WORL*
• SCGROU
• SCPLIN
In addition to these elements, release related actions may also be initiated from SCDIAG
elements. This carries out the release action on all elements (that can be released)
contained on the diagram which corresponds to the SCDIAG element.
Release related information about elements of the types SCOINS, SCEQUI and SCSEG is
stored in the following attributes of those elements:
RECOMM The release comment

REDATE The Date of the last release action
RESTAT The elements release status. 1 indicates that the element is released, 0
indicates that it is not.
REUSER The PDMS user name of the user who carried out the last release related
activity
17:8 12.0
Appendices
17.3 Appendix C: 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 6.5: 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:
Long form Short Form Description

child::MyElement MyElement MyElement child element of the current
context
attribute::MyAttribute @MyAttribute MyAttribute XML attribute of the current
context
child::* * all child elements of the current context
attribute::* @ all attributes of the current context
parent::* .. The parent element of the current context
ancestor::MyElement The MyElement element that the current
context is in
self ::* . The current context
/descendants::* //* all XML elements of the document
self::*// // all descendant XML element of the current
context
following-sibling::* The next XML element if one exists as a child
of the same parent element
preceding-sibling::* the previous element that is a child of the
same parent element as the current context
• Predicates can be added to each LocationPath in order to further constrain the

selected nodes. Predicates are enclosed inside ‘[‘ and ‘]’ characters. For example:
MyElement[@MyAttribute] selects MyElement XML elements that have
an attribute with the name MyAttribute
MyElement[@MyAttribute = ‘Motor’] selects the MyElement XML elements that
have an attribute with the name MyAttribute
that has a value of ‘Motor’
17:9 12.0
Appendices
MyElement[1] selects the first MyElement child of the current

context
MyElement[last()] selects the last MyElement child of the current
context
• Data can then be manipulated using functions such as:
normalize-space(MyElement) takes the textual contents from the MyElement
element and replaces all whitespace with a
single space character
translate(MyElement/@Tag,’-‘,’_’) replaces and ‘-‘ characters with a ‘_’ character
from the Tag attribute of MyElement
concat(MyElement[1],MyElement[2]) concatenates the results of MyElement[1] and
MyElement[2]
count(MyElement) The number of MyElement elements in the
current context
name(.) Name of the current element (including
namespace)
local-name(.) the local name of the current element
(excluding namespace)
• A Boolean expression is one that returns a value of True or False. This is usually
achieved using an equivalence or existence test such as:
@MyAttribute = ‘SomeValue’ MyAttribute has a value of SomeValue
@MyAttribute MyAttribute present on current context
Count(MyElement) = 1 1 element named MyElement in the current
context
17:10 12.0
Appendices
17.4 Appendix D: Diagram Set File Formats

Diagram sets can be created by third party systems along with the P&ID files in order for a
third party system to manage imports automatically via batch PML processing. A diagram
set can be defined either as an XML file or a text file and must conform to the following
format definitions.
17.4.1 XML File Format

All XML files representing a diagram set must conform to the XML Schema:
<PDMS Install directory>/P&ID Manager/Resources/ImportFileSet.xsd
<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.aveva.com/P&IDManager/ImportFileSet"
elementFormDefault="qualified" version="1.0">
<xsd:annotation>
<xsd:documentation>
Copyright (c) 1974 to 2009 AVEVA Solutions Ltd
</xsd:documentation>
<xsd:documentation>
P&ID Manager 12.0.4.0
</xsd:documentation>
</xsd:annotation>
<xsd:element name="ImportFileSet">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="File" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="FileName" type="xsd:string" use="required" />
<xsd:attribute name="FilePath" type="xsd:string" use="required" />
<xsd:attribute name="DiagramName" type="xsd:string" use="optional" />
<xsd:attribute name="MatchedSCDIAG" type="xsd:string" use="optional" />
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="Name" type="xsd:string" use="required" />
<xsd:attribute name="ReleaseComment" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="120"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>
17:11 12.0
Appendices
The data attributes in this file are defined as follows:
Element Attribute Description Example

File FileName The filename of the P&IDfile.xml
file, excluding the
file path.
File FilePath The path of the file. Fully qualified:
C:\Data
Relative to the diagram
set:
.\Data
File DiagramName The name of the /A-different-name
P&ID Diagram if
different to that in
the P&ID file itself.
Note: The Diagram

name is
parsed from
the file but
may be
changed by
entering a
different
name in this
field.
File MatchedSCDIAG The database =16388/64238
reference of the
diagram already
loaded into the
database that this
file is to be matched.
ImportFileSet Name The filename of this Filename.xml
fileset
ImportFileSet ReleaseComment Any comments to be Revision A
used during import
when setting the
RELSTAT attributes.
17:12 12.0
Appendices
For example:
<?xml version="1.0" encoding="utf-8"?>

<ifs:ImportFileSet
xmlns:ifs="http://www.aveva.com/P&IDManager/ImportFileSet"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.aveva.com/P&IDManager/ImportFileSet ImportFile
Name="FileSetExample.xml"
ReleaseComment="Revision A">
<ifs:File
FileName="905680.xml"
FilePath=".\P&ID Data\" />
<ifs:File
FilePath=".\P&ID Data\"
MatchedSCDIAG="=16388/61274" />
<ifs:File
FilePath="C:\P&ID Data\"
DiagramName="/905676_A" />
</ifs:ImportFileSet>
17.4.2 Text File Format

Text files are interpreted as follows:
• A line that starts with '//' will be treated as a comment and ignored.
• All blank lines will be ignored
• All other lines are interpreted as a fully qualified or relative file path. If the text cannot
be interpreted as a file path the .txt file is considered invalid. File paths may be
enclosed in "" characters
Note: All P&ID files listed in a text file are expected to have a file extension.
Note: The user interface expects text files for diagram sets to have the file extension '.txt'.
For example:
// --------------------
//
// Date : 24/04/2009
// Time : 11:39::24
// System : Handwritten
//
// --------------------
// file in the same directory

905675.xml
// file in a sub directory
17:13 12.0
Appendices
.\P&ID Data\905680.xml
// fully qualified filename

C:\P&ID Data\905681.xml
// file paths may be specified in quotation characters

"C:\P&ID Data\905682.xml"
// end of file
17:14 12.0
Index
Index
A Project . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6
Creating
Abort Diagram Import . . . . . . . . . . . . . . . 3:4 Elements . . . . . . . . . . . . . . . . . . . . 11:8
Accessing P&ID Manager . . . . . . . . . . . . 1:2 Rule Groups . . . . . . . . . . . . . . . . . . . 5:4
Accessing the Configuration Options . . . 8:1 Rules . . . . . . . . . . . . . . . . . . . . . . . . 5:5
Add Date/Timestamp to Release Comment 3:5 Creating Diagram Sets . . . . . . . . . . . . . 10:3
ADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Alternation . . . . . . . . . . . . . . . . . . . . . . . 17:1
Attribute Mapping . . . . . . . . . . 6:1, 6:5, 16:5
D
Attribute Mapping Groups . . . . . . . . . . . . 6:3 Database Configuration . . . . . . . . . . . . . 2:1
Attribute Unit . . . . . . . . . . . . . . . . . . . . . . 6:7 Date/Timestamp . . . . . . . . . . . . . . . . . . . 3:5
Attributes DB Expression . . . . . . . . . . . . . . . . . . . . 5:8
Derivation Rules . . . . . . . . . 2:5, 5:1, 6:1 DB Match . . . . . . . . . . . . . . . . . . . . . . . 10:8
Filter . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Deleting
Mapping . . . . . . . . . . . . . . . . . . . . . . 2:2 Diagrams . . . . . . . . . . . . . . . . . . . 11:10
Viewing Element Attributes . . . . . . 11:7 Elements . . . . . . . . . . . . . . . . . . . . 11:9
Auto Complete . . . . . . . . . . . . . . . . . . . . 7:7 Rule Groups . . . . . . . . . . . . . . . . . . 5:10
Automatic Completion of ISO 15926 Mappings Rules . . . . . . . . . . . . . . . . . . . . . . . 5:10
7:5, 7:7 Deleting Mapping Groups and Mappings 6:22
Automatic Matching of Off-Page Connectors DESIGN . . . . . . . . . . . . . . . . . . . . . . 1:2, 1:3
10:13 Diagram Connectors . . . . . . . . . . . . . . 12:5
AVEVA P&ID . . . . . . . . . . . . . . . . . . . . . . 1:1 Diagram Set . 10:3, 10:4, 10:7, 10:10, 10:17
AVEVA P&ID Manager Gateway for AutoCAD Creating a Diagram Set . . . . . . . . . 10:4
P&ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Editing . . . . . . . . . . . . . . . . . . . . . . 10:7
Importing . . . . . . . . . . . . . . 10:10, 10:17
C Opening . . . . . . . . . . . . . . . . . . . . . 10:7
Diagram Set Editor . . . . . . . . . . . . . . . . 10:4
Closing Diagrams and the Viewer . . . . . . 9:5 Diagram Set File Formats . . . . . . . . . 17:11
Condition . . . . . . . . . . . . . . . . . . . . . 6:5, 6:6 Diagram Sets . . . . . . . . . . . . . . . 10:3, 17:11
Configure Auto Complete . . . . . . . . . . . . 7:5 Diagram Viewer
Configuring the Source Data Dictionary . 8:1 Closing Diagrams and the Viewer . . 9:5
Configuring UDAs . . . . . . . . . . . . . . . . . 16:1 Keyboard Commands . . . . . . . . . . . 9:5
Conflict Resolution . . . . . . . . . . . . . . . . . 7:4 Toolbar . . . . . . . . . . . . . . . . . . . . . . . 9:4
Copy from Project . . . . . . . . . . . . . . . . . . 3:6 Display Comments Dialog on Release to 3D 3:5
Copying P&ID Manager Options from another
Index page i 12.0

Index
E H
Editing Highlighting . . . . . . . . . . . . . . . . . . . . . 12:4
Rule Groups . . . . . . . . . . . . . . . . . . . 5:4
Rules . . . . . . . . . . . . . . . . . . . . . . . . 5:5 I
Editing Diagram Sets . . . . . . . . . . . . . . 10:7
Editing Mapping Groups and Mappings 6:22 Import
Element Designations from File . . . . . . . . . . . 7:3
Attributes . . . . . . . . . . . . . . . . . . . . 11:7 Designations from other Databases 7:8
Filter . . . . . . . . . . . . . . . . . . . . . . . . 11:7 Destination Groups . . . . . . . . . . . . . 3:9
Hierarchy . . . . . . . . . . . . . . . . . . . . 11:2 Diagram Sets . . . . . . . . . . . . . . . . . 10:3
Right-Click Menus . . . . . . . . . . . . . 11:5 Diagrams . . . . . . . . . . . . . . . 10:1, 10:15
Types . . . . . . . . . . . . . . . . . . . . . . . . 5:8 ISO 15926 Designations . . . . . . 7:3, 7:8
Element Release Tab . . . . . . . . . . . . . . . 3:3 Location . . . . . . . . . . . . . . . . . . . . . . 4:2
Display Comments Dialog on Release to 3D Options . . . . . . . . . . . . . . . . . . . . . . 3:7
3:5 P&ID Manager Options . . . . . . . . . . 3:7
Set Release Behaviour of Elements on Im- Progress . . . . . . . . . . . . . . . . . . . 10:11
port . . . . . . . . . . . . . . . . . . . 3:3 Starting . . . . . . . . . . . . . . . . . . . . 10:10
Element types . . . . . . . . . . . . . . . . . 6:4, 6:6 Import and keep existing status (OFF) . . 3:4
Enable Release Comments . . . . . . . . . . 3:5 Import and keep existing status (ON) . . . 3:4
Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11:1 Import and set release status to OFF . . . 3:4
Element Hierarchy . . . . . . . . . . . . . 11:2 Import and set release status to ON . . . 3:4
Opening the P&ID Manager Explorer 11:1 Import Diagrams Facility . . . . . . . . . . . 10:1
Using the Explorer . . . . . . . . . . . . . 11:5 Import Tab . . . . . . . . . . . . . . . . . . . . . . . 3:8
Export Viewing/Editing Equipment and Off Line In-
Location . . . . . . . . . . . . . . . . . . . . . . 4:2 strument Positions . . . . . . 3:10
Options . . . . . . . . . . . . . . . . . . . . . . . 3:7 Viewing/Editing Import Destination SC-
Exporting P&ID Manager Options . . . . . . 3:7 GROUP Elements . . . . . . . . 3:8
Importing Diagram Sets . . . . . . 10:10, 10:17
F Importing using PML . . . . . . . . . . . . . 10:14
Introduction . . . . . . . . . . . . . . . . . . . . . . 1:1
File Format . . . . . . . . . . . . . . . . . . . . . . . 6:7 ISO 15926 . . . . . . . . . . . . . . . . . . . . 1:1, 7:1
File Format Version . . . . . . . . . . . . . . . . . 6:7 ISO 15926 Designation . . . . . . . . . . 7:2, 7:8
File Locations Tab ISO 15926 Mappings . . . . . . . . . . . . 7:5, 7:7
Set Default Export Location . . . . . . . 4:2
Set Default Import Location . . . . . . . 4:2 K
Filter
Attribute . . . . . . . . . . . . . . . . . . . . . . 5:6 Keyboard Commands . . . . . . . . . . . . . . 9:5
Element . . . . . . . . . . . . . . . . . . . . . 11:7
L
G
LEXICON . . . . . . . . . . . . . . . . . . . . 2:1, 16:1
General Tab . . . . . . . . . . . . . . . . . . . . . . 3:5
Copying P&ID Manager Options from anoth- M
er Project . . . . . . . . . . . . . . . 3:6
Exporting P&ID Manager Options . . 3:7 Mapping Groups and Mappings
Importing P&ID Manager Options . . 3:7 Deleting . . . . . . . . . . . . . . . . . . . . . 6:22
Restore Default Options . . . . . . . . . . 3:8 Editing . . . . . . . . . . . . . . . . . . . . . . 6:22
Grouping . . . . . . . . . . . . . . . . . . . . . . . . 17:1 Moving . . . . . . . . . . . . . . . . . . . . . . 6:22
GTYPE . . . . . . . . . . . . . . . . . . . . . . 2:2, 7:1 Mapping Set-Up . . . . . . . . . . . . . . . . . . . 2:2
GTYPE Mappings . . . . . . . . . . . . . . . . . . 2:2 Attribute Mapping . . . . . . . . . . . . . . . 2:2
GTYPE Mapping . . . . . . . . . . . . . . . 2:2
Page Matching . . . . . . . . . . . . . . . . . 2:4
Matching Off-Page Connectors . 10:13, 13:1
Index page ii 12.0

Index
Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2 R
Display Menu . . . . . . . . . . . . . . . . . . 1:3
File Menu . . . . . . . . . . . . . . . . . . . . . 1:2 Re-apply to databases(s) . . . . . . . . . . . . 7:9
Tools Menu . . . . . . . . . . . . . . . . . . . . 1:2 Regular Expressions . . . . . . . . . . . . . . 17:1
Module Definition Configuration . . . . . . . 2:1 Alternation . . . . . . . . . . . . . . . . . . . 17:1
Moving Elements . . . . . . . . . . . . . . . . 11:11 Grouping . . . . . . . . . . . . . . . . . . . . 17:1
Moving Mapping Groups and Mappings 6:22 Guidelines . . . . . . . . . . . . . . . . . . . 17:6
Moving Rules and Rule Groups . . . . . . 5:10 Quantification using Metacharacters 17:2
Releasing Data . . . . . . . . . . 3:3, 11:12, 17:8
Release Behaviour . . . . . . . . . 3:3, 17:8
N Existing Elements - Not Released 3:4
NameClashRule . . . . . . . . . . . . . . . . . . . 5:7 Existing Elements - Released . . 3:4
New Elements . . . . . . . . . . . . . . 3:4
Release Comments . . . 3:5, 10:9, 10:15
O
Unreleasing Data . . . . . . . . . . . . . 11:13
Off Line Equipment and Instrument Default Posi- Renaming Elements . . . . . . . . . . . . . . 11:10
tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10 Reports . . . . . . . . . . . . . . . . . . . . . . . . . 15:1
Off-Page Connectors . . . . . . . . . . . . . . 13:1 Reset Defaults . . . . . . . . . . . . . . . . . . . . 3:8
OPCs . . . . . . . . . . . . . . . . . . . . 10:13, 13:1 Resetting the Dictionary . . . . . . . . . . . . . 8:2
Opening an Existing Diagram Set . . . . . 10:7 Restore Default Options . . . . . . . . . . . . . 3:8
Opening the P&ID Manager Explorer . . 11:1 Rule Groups . . . . . . . . . . . . . . . . . . . . . . 5:1
Options Dialog Rule Names . . . . . . . . . . . . . . . . . . . . . . 5:9
Element Release Tab . . . . . . . . . . . . 3:3 Rules . . . . . . . . . . . . . . . . . . . . . . . . 5:1, 5:2
General Tab . . . . . . . . . . . . . . . . . . . 3:5
Import Tab . . . . . . . . . . . . . . . . . . . . 3:8 S
Units Tab . . . . . . . . . . . . . . . . . . . . 3:11
Overwrite Mappings in Databases with Current Saving Changes . . . . . . . . . . . . . . . . . 11:13
Mappings . . . . . . . . . . . . . . . . . . . . . . . . 7:9 Saving Imported Data . . . . . . . . . . . . 10:18
SCDIAG . . . . . . . . . . . . . . . . . . . . . . . . 11:5
SCGROU . . . . . . . . . . . . . . . . . . . . 3:8, 11:3
P
Schematic WORL * . . . . . . . . . . . . . . . 11:3
P&ID Manager Diagram Viewer . . 9:3, 12:4 SCSTYPE . . . . . . . . . . . . . . . . . . . . 2:2, 7:1
P&ID Manager Explorer . . . . . . . . . . . . 11:1 SCTYPE . . . . . . . . . . . . . . . . . . . . . . 6:4, 6:6
P&ID Manager Options . . . . . . . . . . . . . . 3:1 Search Toolbar . . . . . . . . . . . . . . . . . . . 14:2
P&ID Manager Reports . . . . . . . . . . . . . 15:1 Searches . . . . . . . . . . . . . . . . . . . . . . . 14:1
P&ID Manager User Options . . . . . . . . . 4:1 Selecting Diagrams
Page Matching . . . . . . . . . . . . . . . . . . . . 2:4 to Preview . . . . . . . . . . . . . . . . . . . . 9:1
PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 to View . . . . . . . . . . . . . . . . . . . . . . 12:1
PML . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:14 Selecting Rules to be Applied During Import 5:3
Populate from Database(s) . . . . . . . . . . . 7:8 Set Default
Populate ISO 15926 Designations from File 7:3 Export Location . . . . . . . . . . . . . . . . 4:2
Populating or Updating the Dictionary . . 8:3 Import Location . . . . . . . . . . . . . . . . 4:2
Post Installation Tasks . . . . . . . . . . . . . . 2:1 Set Release Behaviour of Elements on Import
Database Configuration . . . . . . . . . . 2:1 3:3
Module Definition Configuration . . . . 2:1 Set release status to OFF . . . . . . . . . . . 3:4
UDA Creation . . . . . . . . . . . . . . . . . . 2:1 Set release status to ON . . . . . . . . . . . . 3:4
Pre-configuration . . . . . . . . . . . . . . . . . . . 2:1 Setting up Rules for Automatic Completion of
Previewing Diagrams before Import . . . . 9:1 ISO 15926 Mappings . . . . . . . . . . . . . . . 7:5
Project Options Dialog . . . . . . . . . . . . . . 3:1 Source Attribute Name . . . . . . . . . . . . . . 6:7
Source Attribute Type . . . . . . . . . . . . . . 6:7
Q Source Data Dictionary . . . . . . . . . . . . . 8:1
Source OPC . . . . . . . . . . . . . . . . . . . . . 13:2
Quantification using Metacharacters . . . 17:2 Standard Searches . . . . . . . . . . . . . . . 14:1
Index page iii 12.0

Index
T 7:8
Overwrite Mappings in Databases with Cur-
Target OPC . . . . . . . . . . . . . . . . . . . . . . 13:2 rent Mappings . . . . . . . . . . . 7:9
The Diagram Connector . . . . . . . . . . . . 13:1 Setting up Rules for Automatic Completion
Tree View . . . . . . . . . . . . . . . . . . . . . . . . 6:2 of ISO 15926 Mappings . . . 7:5
TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
X
U
XPath Expression Builer Dialog . . . . . . . 6:8
UDA . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1 XPath Expressions . . . . . . . . . . . . . . . . 17:9
UDA Attributes . . . . . . . . . . . . . . . . . . . 16:5
UDA Catalogue . . . . . . . . . . . . . . . . . . . 16:3
UDA Creation . . . . . . . . . . . . . . . . . . . . . 2:1
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7
Units Tab . . . . . . . . . . . . . . . . . . . . . . . . 3:11
Unreleasing Data . . . . . . . . . . . . . . . . 11:13
User Defined Attributes . . . . . . . . . . . . . 16:1
User Options Dialog . . . . . . . . . . . . . . . . 4:1
Using the Explorer . . . . . . . . . . . . . . . . 11:5
Applying a Filter . . . . . . . . . . . . . . . 11:7
Creating Elements . . . . . . . . . . . . . 11:8
Deleting Elements . . . . . . . . . . . . . 11:9
Element Right-Click Menus . . . . . . 11:5
Moving Elements . . . . . . . . . . . . . 11:11
Releasing and Unreleasing Data . 11:12
Renaming Elements . . . . . . . . . . . 11:10
Saving Changes . . . . . . . . . . . . . . 11:13
Viewing Diagrams . . . . . . . . . . . . 11:11
Viewing Element Attributes . . . . . . 11:7
V
Version . . . . . . . . . . . . . . . . . . . . . . . . . . 6:7
Viewing Diagrams . . . . . . . . . . . . . 9:1, 12:1
Viewing Element Attributes . . . . . . . . . . 11:7
Viewing Imported Diagrams . . . . . . . . . 12:1
Viewing/Editing Attribute Derivation Rules 5:1
Creating/Editing Rule Groups . . . . . . 5:4
Creating/Editing Rules . . . . . . . . . . . 5:5
Deleting Rules and Rule Groups . . 5:10
Moving Rules and Rule Groups . . . 5:10
Selecting Rules to be Applied During Import
5:3
Viewing/Editing Attribute Mappings . . . . 6:1
Viewing/Editing Equipment and Off Line Instru-
ment Positions . . . . . . . . . . . . . . . . . . . 3:10
Viewing/Editing GTYPE Mappings . . . . . 7:1
Viewing/Editing Import Destination SCGROUP
Elements . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
Viewing/Editing ISO 15926 Mappings
Automatically Completing ISO 15926 Map-
pings . . . . . . . . . . . . . . . . . . 7:7
Import Designations from File . . . . . 7:3
Import Designations from other Databases
Index page iv 12.0

PID Manager User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PID Manager User Guide

Uploaded by

Copyright:

Available Formats

P&ID Manager

First published November 2007.

© AVEVA Solutions Ltd, and its subsidiaries.

P&ID Manager User Guide

P&ID Manager Project Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Importing P&ID Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7

P&ID Manager User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

Viewing/Editing Attribute Derivation Rules . . . . . . . . . . . . . . . . . . . 5:1

Viewing/Editing Attribute Mappings . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

Moving Mapping Groups and Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22

Viewing/Editing GTYPE Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1

Configuring the Source Data Dictionary . . . . . . . . . . . . . . . . . . . . . 8:1

Previewing Diagrams before Import . . . . . . . . . . . . . . . . . . . . . . . . . 9:1

Importing Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1

Saving Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:18

P&ID Manager Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1

Viewing Imported Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1

Diagram Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1

Standard Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14:1

P&ID Manager Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15:1

Configuring UDAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16:1

1.1 AVEVA P&ID Manager

1.2 Accessing P&ID Manager

The P&ID Manager menu consists of four main functional groups:

• Section 4: P&ID Manager User Options.

2.1 Post Installation Tasks

2.1.1 Module Definition Configuration

2.1.2 Database Configuration

2.1.3 UDA Creation

2.2 Mapping Set-Up

2.2.1 GTYPE Mapping

2.2.2 Attribute Mapping

In this example the AttributeName attribute of the CrossPageConnection XML element

2.2.3 Page Matching

2.3 Attribute Derivation Rules

3 P&ID Manager Project Options

The Options dialog is then displayed.

The Project Options dialog consists of four tabs, as described below.

3.1 Element Release Tab

3.1.1 Set Release Behaviour of Elements on Import

A different release behaviour can be specified for each category of element.

Existing Elements - Released

Select from the following options:

Existing Elements - Not Released

Select from the following options:

Select from the following options:

3.1.2 Display Comments Dialog on Release to 3D

3.2 General Tab

The General tab is used to:

3.2.1 Copying P&ID Manager Options from another Project

3.2.2 Exporting P&ID Manager Options

3.2.3 Importing P&ID Manager Options

3.2.4 Restore Default Options

A message is displayed when the restoration is complete.

3.3 Import Configuration Tab

The Import Configuration tab is used to:

3.3.1 Viewing/Editing Import Destination SCGROUP Elements

3.3.2 Viewing/Editing Equipment and Off Line Instrument Positions

3.4 Units Tab

Unit Type Default Units of Measure

4 P&ID Manager User Options

The User Options dialog is then displayed.

To exit the dialog without saving, select the Cancel button.

4.1 Import Options