Bentley AutoPlant Project Configuration V8i SS1 PDF

AutoPLANT Project Configuration
V8i (SELECTseries1)
Bentley Institute Course Guide
TRN012060-1/0002
Trademarks
AccuDraw, Bentley, the B Bentley logo, MDL, MicroStation and SmartLine are registered
trademarks; PopSet and Raster Manager are trademarks; Bentley SELECT is a service
mark of Bentley Systems, Incorporated or Bentley Software, Inc.
AutoCAD is a registered trademark of Autodesk, Inc.
All other brands and product names are the trademarks of their respective owners.
Patents
United States Patent Nos. 5,8.15,415 and 5,784,068 and 6,199,125.
Copyrights
2000-2010 Bentley Systems, Incorporated.
MicroStation 1998 Bentley Systems, Incorporated.
All rights reserved.
AutoPLANT Project Configuration
ii
Copyright 2010 Bentley Systems, Incorporated
Apr-10
Table of Contents
Course Overview ____________________________________ 1
Course Description ____________________________________1
Target Audience_______________________________________2
Prerequisites _________________________________________2
Course Objectives _____________________________________2
Modules Included _____________________________________2
System Requirements __________________________________3
AutoCAD or related Autodesk Products __________________4
ProjectWise Supported Versions__________________________4
Databases Supported __________________________________4
Program Software Loading Sequence ______________________4
Introductory Knowledge ________________________________6
Questions ________________________________________6
Answers __________________________________________7
Introduction to Project Setup __________________________ 9

Module Overview _____________________________________9
Module Prerequisites __________________________________9
Module Objectives_____________________________________9
Project Setup - Configuration Advantages __________________10
Project Success Formula - Software Implementation
Strategies_________________________________________10
Product Installation Overview ____________________________14
Project Setup Checklist _________________________________14
Initial Project Setup_________________________________14
Project Administrator _______________________________16
Data Manager _____________________________________16
Datasheets________________________________________17
Vision____________________________________________17
P&ID ____________________________________________17
Instrumentation and Wiring __________________________18
Piping____________________________________________18
Equipment ________________________________________19
Structural_________________________________________20
Walkthrough and Interference Detection _______________20
Isometrics and Isogen _______________________________21
Apr-10
iii
Bentley PLANT Training AutoPLANT Project Configuration

Table of Contents
Orthographics _____________________________________22
Bill of Material Reports ______________________________22
Document Management Application ______________________23
ProjectWise Application Server _______________________23
Types of Databases Supported ___________________________23
Types of Project Environments ___________________________25
Central Mode _____________________________________25
Multi-Project Mode_________________________________26
Distributed Mode __________________________________27
Module Review _______________________________________28
Questions ________________________________________28
Answers __________________________________________28
Project Information __________________________________ 29

Module Overview _____________________________________29
Create a New Project from Base __________________________30
Microsoft Access Project_____________________________30
SQL Server Projects _________________________________34
Oracle Projects ____________________________________40
Understanding the Project Directory Structure ______________44
Config Directory ___________________________________44
Datasheets Directory _______________________________45
Electrical Directory _________________________________46
Equip Directory ____________________________________46
Hookups Directory _________________________________47
Instrumentation Directory ___________________________47
Iso Directory ______________________________________48
P&ID Directory ____________________________________48
Piping Directory____________________________________49
Projdata Directory__________________________________49
Raceways Directory_________________________________50
Reports Directory __________________________________50
Standards Directory ________________________________51
Struct Directory ____________________________________51
Custom Directories _________________________________52
The ER Diagram ____________________________________52
Understanding the Directory Structure_____________________53
Local_Root Directory________________________________53
Network_Root Directory_____________________________53
Project_Root Directory ______________________________54
Custom_Root Directory _____________________________54
Local_Root Directories ______________________________55
Applications Accessing Project Data _______________________66
Core Applications __________________________________66
iv

Apr-10
Table of Contents
Bentley AutoPLANT 2D Applications____________________67

AutoPLANT 3D Applications __________________________69
Project Tools ______________________________________70
Tools ____________________________________________72
Module Review _______________________________________74
Questions ________________________________________74
Answers __________________________________________74
Configuring the Project Database ______________________ 75

Module Overview _____________________________________75
Overview of Project Administrator ________________________76
Archive___________________________________________76
Set as Startup Project __________________________________77
Revalidate Project __________________________________77
Project Properties __________________________________78
Adding a Database to the Current Project _______________80
Removing a Database from the Current Project __________81
Connecting to Password Protected Databases____________82
Manipulating the Databases _____________________________84
AT_VIEWS ___________________________________________95
Edit View _________________________________________95
Understanding the Edit View Dialog____________________96
Tag Types ____________________________________________102
Copy Tag Type Dialog _______________________________102
Tag Codes Button __________________________________105
Delimiters Tab _____________________________________107
Alternate Tag Codes for Tag Type Dialog ________________109
CATT Dialogs _________________________________________118
Mapping 2D and 3D Classes _____________________________128
Class Mapping _____________________________________128
Tag Type Mapping__________________________________129
Classes ___________________________________________129
Add or Remove Mappings____________________________130
Field Mapping Properties ____________________________135
Tag Type Mapping__________________________________136
Relationship Manager __________________________________137
Modifying Fields and Views in the SQL Project _______________139
New Field Restrictions and Definitions__________________143
Module Review _______________________________________146
Questions ________________________________________146
Answers __________________________________________146
Apr-10

Table of Contents
Managing Projects __________________________________ 147

Module Overview _____________________________________147
Interpreting the Project.ini files __________________________148
The SQL Server Project.ini File ________________________148
The Oracle Project.ini File ____________________________149
User Configurations ____________________________________150
Application Security____________________________________155
Assigning User Rights to CATT dialogs______________________156
Module Review _______________________________________159
Questions ________________________________________159
Answers __________________________________________159
Examining the Project Databases _______________________ 161

Module Overview _____________________________________161
Viewing the Projdata Tables _____________________________162
Specialized Data Tables______________________________164
Important Fields within the Data Tables ________________166
ER Diagram _______________________________________167
Viewing the Schema Tables ______________________________174
XXX_PICK Tables ___________________________________174
RebisDict Table ____________________________________175
RebisJoin Table ____________________________________175
RebisObject Table __________________________________176
RebisTable Table ___________________________________176
RebisView Table ___________________________________177
Tag_code, Tag_type and Tformat Tables ________________177
Viewing Project.mdb ___________________________________182
Module Review _______________________________________183
Questions ________________________________________183
Answers __________________________________________183
Project Utilities _____________________________________ 185

Module Overview _____________________________________185
Upgrading Existing Projects ______________________________186
Packaging a Project ____________________________________190
Split/Merge Utility ____________________________________199
Consistency Check Options ______________________________211
2D to 3D Consistency Reporter________________________211
Consistency Reporter Operations______________________213
2D to 3D CAD Interface and Consistency Checker _________218
vi

Apr-10
Table of Contents
Module Review _______________________________________221

Questions ________________________________________221
Answers __________________________________________221
Project Organization _________________________________ 223

Module Overview _____________________________________223
ProjectWise Navigator__________________________________224
GUIDS _______________________________________________233
Project GUIDS in AutoPLANT _________________________233
Document GUIDs in AutoPLANT _______________________234
Data Reuse ___________________________________________235
Drawing Exchange__________________________________235
Relationship Manager _______________________________235
PXF Files__________________________________________236
Briefcase Mode ____________________________________236
Module Review _______________________________________237
Questions ________________________________________237
Answers __________________________________________237
Data Manager Customization __________________________ 239

Module Overview _____________________________________239
Data Manager Interface ________________________________240
Overview of Database Terminology _______________________240
Brief Tour of the Data Manager Interface___________________241
Menus ___________________________________________241
Data Manager Toolbar ______________________________242
The Project Window ________________________________242
Examining the Original Database _________________________243
Understanding Views _______________________________244
Modifying a View ______________________________________246
Creating a New View ___________________________________254
Creating Reports ______________________________________257
Access Forms _________________________________________263
Module Review _______________________________________264
Questions ________________________________________264
Answers __________________________________________264
Datasheets Customization ____________________________ 265

Module Overview _____________________________________265
Apr-10
vii

Table of Contents
Understanding Datasheets Structure ______________________266

Database References ___________________________________267
Internal References ____________________________________267
Revision Control_______________________________________268
CurrentData_______________________________________268
Previous Data _____________________________________268
Revision List_______________________________________268
Creating a New Datasheet_______________________________269
Fully Mapped Datasheet Templates _______________________286
Datasheets Utilities ____________________________________289
Module Review _______________________________________293
Questions ________________________________________293
Answers __________________________________________293
Vision Customization ________________________________ 295

Module Overview _____________________________________295
Vision Overview _______________________________________296
Vision Interface _______________________________________297
Administrative Functions________________________________300
User Privileges and Settings _____________________________305
Revision Controls___________________________________305
Revision Marks ____________________________________306
Display Options ____________________________________308
Module Review _______________________________________310
Questions ________________________________________310
Answers __________________________________________310
Project Template Creation ____________________________ 311

Module Overview _____________________________________311
Template Project ______________________________________312
Module Review _______________________________________318
Questions ________________________________________318
Answers __________________________________________318
Appendix A ________________________________________ 319

AT.ini _______________________________________________319
SQL Project.ini ________________________________________342
Oracle Project.ini ______________________________________348
Access Project.ini ______________________________________356
viii

Apr-10
Table of Contents
Course Summary ____________________________________ 363

Course Summary ______________________________________363
Course Review ________________________________________364
Questions ________________________________________364
Answers __________________________________________366
Apr-10
ix


Apr-10
Course Overview
Course Description
AutoPLANT Project Configuration is a course designed for Project Administrators
who have been tasked with creating and/or modifying projects. It is our intent to
train you in-depth on project setup. You will be provided a set-up checklist to
insure that you consider all of the applications that will need to be registered for
your project. You will determine which type of database management system is
right for you. You learn the directory structure of the local directory files as well
as the network directory files.
You will be taught how to configure your project database by linking tables and
importing and exporting data. You will be instructed on tag types and views which
are integral to populating the databases. You will create new tag types, new fields
and new tables for your project.
You will learn to manage and organize your project. You will be taught the
administrator functions of archiving a project and creating a startup project. You
will be instructed on creating new users and setting the privileges of that user.
You will study at length the project databases and learn the intricate relationships
between the databases and how the specialized fields link the data together.
You will be introduced to the Project Utilities that will allow you to package your
project so that it can be sent to a vendor or satellite office. You will learn how to
split your project into two parts and then merge it together again.
Finally you will learn how to customize the Data Manager application to create
new views and reports. You will customize the Datasheet application to import
your current datasheets and the Vision application to add new third party
applications to your project.
Apr-10
1
Course Overview
Target Audience
Target Audience
This course is recommended for the following audience(s):
Project Administrators with experience in either our 2D applications or our 3D

applications or both.
Prerequisites
Completion of either the 2D or 3D Fundamentals courses
Working knowledge of databases
Working knowledge of Microsoft Access report writer
Course Objectives
After completing this course, you will be able to:
Setup a new project.
Configure a project.
Manage a project.
Package a project.
Create custom views and reports.
Import existing Datasheets.
Add new applications to a project.
Create a new custom project.
Modules Included
The following modules are included in this course:
Introduction to Project Setup Administrator
Project Information
Configuring the Project Database
Course Overview
Apr-10
System Requirements
Managing Projects
Examining the Project Databases
Project Utilities
Project Organization
Data Manager Customization
Datasheets Customization
Vision Customization
Custom Project
Project Template Creation
Appendix A
System Requirements
You must have a CD drive or Internet access for product installation. The
following prerequisites are required to run the modules included in AutoPLANT
Project Configuration:
Apr-10
Processor:
Intel Pentium 4 processor and AMD Athlon,

3.0 GHz or greater or Intel or AMD Dual Core
Processor, 2.0 GHz or greater
Operating System:
Microsoft Windows XP Professional SP2 or

later, Windows Vista 32 bit SP1
Microsoft Windows XP Professional SP1A or
later
Internet:
Microsoft Internet Explorer 6 SP1 or greater
Memory:
2GB or greater
Hard Disk:
2GB free hard disk space
Input Device:
Industry-standard input device supported by

Windows
Output Device:
Industry-standard input device supported by

Windows
Video Graphics Card:
Industry-standard video card/monitor
Processor:
Intel Pentium 4 processor and AMD Athlon,

3.0 GHz or greater or Intel or AMD Dual Core
Processor, 2.0 GHz or greater
Course Overview
AutoCAD or related Autodesk Products
AutoCAD or related Autodesk Products

AutoCAD:
2006, 2007, 2008 (32 bit only), 2009 (32 bit

only)
The latest applicable service packs must be used for all of the above products.
ProjectWise Supported Versions

Bentley ProjectWise V8 08.11.05
Databases Supported
Microsoft Access:
2003, 2007
SQLServer:
2005 Express Edition, 2005 Express Edition with

Advanced Services, 2005 Standard Edition and
2005 Enterprise Edition.
Oracle:
Oracle 9i Release 2, Oracle 10g Release 2,

Oracle 11g Release 1
Program Software Loading Sequence

This course will require the installation of the PLANT V8i Edition suite of software,
both 2D and 3D including Process and Instrumentation, P&ID and Plant Design.
Application
Size
Version
AutoPLANT P&ID
226 mb
V8i Edition
Bentley Process and Instrumentation
253 mb
V8i Edition
AutoPLANT Plant Design
490 mb
V8i Edition
Note: Please check Bentley Select Server for the most current version of the
software and any available updates for that software.
Course Overview
Apr-10
Program Software Loading Sequence
Installing Bentley PLANT software is typically a job best performed by the

administrator. The installer must have full administrative rights to the local system
(registry, etc). During installation, the installer will prompt for a variety of
information to control the destination of various components and whether or not
to install optional modules within each product group.
Apr-10
Course Overview
Introductory Knowledge
Before you begin this module, let's define what you already know.
Questions
1 When creating an AutoPLANT Project can you specify an Oracle, SQL, or
Access database type?
2 What are the different types of databases that Bentley software
supports?
3 Can a project be modified to meet the needs of the users?
4 How does the Bentley software propagate the tag data into the
databases?
5 Can you import your existing data into a Bentley project?
6 How does the software know which database source is being utilized for a
project?
7 Does the Supervisor login and password have to be used to log into a
project?
8 Where is the data stored for a project?
9 Is Project Packager a tool that packages a project into one zip file?
10 Why would you split a project into smaller projects?
11 What is a GUID?
12 Do you have to use the views and reports provided by Bentley Data
Manager?
13 What is a datasheet?
14 What is Bentley Vision?
15 What is the advantage of creating a custom template project?
Course Overview
Apr-10
Answers
1 Yes, when creating a project you will need to select a database type.
2 Bentley software supports, Access, SQL and Oracle databases.
3 Yes, Bentley software is designed to allow modifications to the base tables
to incorporate the data of the user.
4 Bentley software uses the tag type to propagate the tag information into
the databases.
5 Yes, existing data can be imported or linked to a Bentley project.
6 The PROJECT.ini file is read by the software and contains the type of
database being used by the project.
7 No, new logins and users can be created for each projects needs.
8 The data is stored in the projdata.mdb (or database equivalent) located in
the projects Projdata directory.
9 Yes, Project Packager rolls up the project including drawing files and the
database into one zip file.
10 You may want to split a project into smaller projecst so that they can be
sent to an outside vender for comments. The smaller projects can then be
merged back into the larger project and all comments and changes are
incorporated.
11 A GUID is a Globally Unique Identifier used by AutoPLANT.
12 No, you can customize the views and reports provided by Bentley Data
Manager to make them fit your needs.
13 A datasheet is a tool used by design engineers summarizing the
performance and other characteristics of a component.
14 Bentley Vision is an application for organizing both Bentley and NonBentley documents.
15 Creating a custom template project will prevent you from having to make
the same customization changes whenever you create a new project.
Apr-10
Course Overview
Course Overview
Apr-10
Introduction to Project Setup

Module Overview
This chapter will introduce you to project configurations and checklists which will
help you customize your project. You will be introduced to the types of databases
that are supported and the different project environments.
Module Prerequisites
Module Objectives
After completing this module, you will be able to:
Apr-10
Plan your project configuration.
9
Project Setup - Configuration Advantages

AutoPLANT configurations allow users the ability to segregate information or
formats for different clients or projects. In this section, you will be provided with
ideas on what and how to customize in your configurations, and reasons for
separating your customizations. You will also learn what is or is not available for
customization.
There are two types of configurations available, client-specific and projectspecific.
Client-specific: Some companies have multiple clients who have different

layering, text, border, etc., standards. These companies need to have a
configuration for their various clients.
Project-specific: A company may need to make a project-specific

configuration when, for example, the way they would put together a project
for client ABC's plant in Eastern USA is different from a project for client ABC's
plant in Western USA. Each plant's deliverable requirements may have
variations. For these reasons we will cover the Project Setup and the
ramifications of having different configurations before creating a custom
configuration.
AutoPLANT provides you with an easy-to-use interface to create configurations

quickly.
Project Success Formula - Software Implementation Strategies

Success takes planning and you need to plan for success. The following steps will
help you to formulate a plan.
1 Determine, and provide as needed, personnel training requirements.
Ensure that the designers and engineers are on the project team and
know how to use the software. Ensure the manager, project engineers
and lead designers know what to expect from the software and what its
limitations are.
2 Define and implement project CAD standards, such as coloring, layering,
annotations and line numbering formats.
3 Define and implement new components as quickly as possible.
4 Define and implement detailed design strategy and techniques, including
checking procedures and tools.
5 Define the project deliverables.
10
Apr-10
Personnel Selection and Training

There are three types of personnel involved with any project:
Actual users of the CAD and database software
Project engineers/managers who monitor the progress of the use of the

software
IS Department or Support Department, who need to understand and know

how to support the software
Training
For any realistic progress to be made in a short amount of time, the designers
and engineers will need to know the software before beginning the project.
The best method of insuring this is to provide formal training to enable your
users to learn how to properly use the software. Bentley is sure that you are
well aware of the pitfalls of trying to learn software "on the fly."
Selecting Users
The best designers are those people who are willing to learn new methods of
design and who have some experience or formal training in the field/industry
that they are working in. Therefore the best users are those people who have
a blend of experience in the field and/or industry and are comfortable with
computers in general.
Selecting Project Engineers and Managers

The best project engineers/managers are those who are willing to learn new
methods of implementing, monitoring, and statusing projects. Bentley has
seen many experienced personnel who have not experienced success with
projects because they try to implement the "old, tried and true" project
techniques instead of opening up to the shifting paradigm. Therefore the best
managers are those people comfortable with computers in general and
willing to look at alternate techniques to complete their projects.
Implement Project CAD Standards

Relevant questions to ask and determine prior to project start up:
Apr-10
Is this a large project or a small project?
How will the size of this project change our standards?
Does this project need to employ special AutoCAD techniques?
11
The implementation of CAD standards is a critical time-saving tool. Bentley

recommends that regular meetings be held to review the CAD standard content
and methodology to ensure that the information is still relevant. The current era
of computer hardware and CAD software development is changing so rapidly that
it is critical that the standards don't become dated.
Make sure that you analyze the needs of the current project against the CAD
standards. It is possible that the standards for one project will not work for
another project dependent upon such things as client requirements, project size,
and schedule.
Customization Needs and Execution

By addressing customization needs early in the project, you set the foundation
for an easy-flowing work environment for the users.
Determine whether the project needs new:
Component types.
Definition of deliverables - reports, templates, etc.
Components/symbols.
Annotation classes, i.e., line number methods, etc.
CAD standards - layers, linetypes, etc.
Data base fields.
Dialogs: Creating or modifying the dialogs that are used enhances

productivity by eliminating user error. User error usually comes from not
understanding or misinterpreting how the project information will be entered
in the dialog, if you use the same dialog for all projects.
Determine the need for and create any needed components that are not
currently available to the user. This will eliminate checking problems later in the
project.
Determine how and when to extract data for use on the project. This will help in
determining what information needs to be input to the database, which in turn
will dictate what database fields will be required.
Keep in mind that some customization is not backward-compatible. For instance,
if a component is changed in the middle of a project, every drawing containing
that component will have to be edited.
12
Apr-10
Install Order
Bentley Plant software applications need to be installed in order. For a full
AutoPLANT suite install, the following order is required:
1 Bentley ProjectWise
2 AutoCAD
3 AutoPLANT P&ID
4 Bentley Process and Instrumentation
5 AutoPLANT PDW
6 ProSteel
7 Bentley ProjectWise Navigator
Note: AutoCAD should be opened and closed once before installing
AutoPLANT to create the default profiles. Bentley Framework is not a

necessary installation but does contain up-to-date fixes for known Plant
issues. If you opt to install the latest version of Framework, install it
last. Partial installs are still run in the same order; simply omit the
modules not being installed.
Apr-10
13
Product Installation Overview
Product Installation Overview

Bentley Plant applications are designed to complement one another, making it
easier to share, build, and manage valuable project data. Using a central database
as a project repository, several applications can easily share the same data. You
can edit the data on a project-wide basis, drastically reducing the time it takes to
bring a data-intensive project to completion. In addition to the time-saving
benefits, managers will also appreciate the wealth of reports that can be
generated from a centralized system.
AutoPLANT software is designed to allow the project discipline teams to work in a
concurrent engineering environment for all aspects of functional, schematic, and
physical plant design. Many of these applications were developed to address the
common scenario of sending documents to off-site design offices and vendors,
and re-synchronizing the off-site design data with the central project database.
All applications are built on an open flexible database and standard Microsoft
tools like Microsoft Access and Microsoft Excel.
Project Setup Checklist

Initial Project Setup
Things to Decide
Determine applications to be utilized:
ProjectWise/Vision/Document Manager
AutoPLANT P&ID
Data Manager
Datasheets
Instrumentation and Wiring
Hookups
AutoPLANT P&ID Conversion Toolkit
AutoPLANT Piping/Equipment
Isometrics/Isogen
ProjectWise Navigator
14
Apr-10
Structural Modeler/Engineering/Detailing
Electrical
Determine hardware and software requirements (minimum and

recommended).
Determine the database type (Access, Oracle or SQL Server).
Select the network directory.
Determine the back-up schedule and responsibility.
Determine discipline partitioning (who owns whatProcess, Mechanical,

Instrumentation, Piping, etc.).
Determine shared vs. local standards and customization.
Identify deliverables (P&ID, PFD, Datasheets, Loops, Ortho's, Iso's, etc.).
Outline customization issues.
Verify Select agreement and set internal support strategies.
Establish the criteria and milestones for gauging the performance of your
implementation plan.
Training
Identify who gets trained and on which applications.
Set the training schedule.
Secure the training location.
Tasks
Apr-10
Prepare the file server as appropriate.
Install appropriate modules of AutoPLANT.
Create network project directory.
Create projects.
Assign administrator privileges.
Create user logins and assign access rights.
Create network project directory.
Define general database structure, server requirements for project

engineering/design, and long-term archiving.
Create additional fields for Detailed Design needs, i.e., work packages, etc.
Create additional DB views, search criteria, and reports.
15
Apply drawing setup decisions.
Review CAD drafting standards.
Review engineering standards.
Lifecycle Data Management (owner/operators)
Define EPC training requirements.
Define criteria to handle EPC requested customizations.
Define procedure for changing data structure during the project

(fields, supplemental tables).
Project Administrator
Tasks
Import data from external sources.
Create new database fields.
Establish tagging conventions.
Import new datasheets.
Create administrator privileges.
Create user logins and access rights.
Data Manager
Tasks
Create or modify views to accumulate data.
View formats
Read-only fields
Hidden fields
New database fields
Create or modify reports to view data.
Company logos
New database fields
Create user groups and logins if not already defined.
16
Apr-10
Divide users into groups.
Decide user rights.
Create logins for each group.
Datasheets
Tasks
Locate company logos.
Create/import datasheet templates.
Map datasheet cells.
Extended data
Vision
Tasks
Create administrative privileges if not already created.
Create user logins and access rights if not already created.
Establish viewer applications.
P&ID
Tasks
Apr-10
Define units for drawings (imperial, metric, mixed metric).
Create a custom directory if needed.
Creation/modification of dialogs.
Define title blocks.
Define custom layers, components, annotations.
Establish checking procedures.
17
Instrumentation and Wiring

Tasks
Establish tagging conventions.
Create new database fields.
Create or modify views to accumulate data.
View formats
Read-only fields
Hidden fields
New database fields
Create or modify reports to view data.
Company logos
New database fields
Create or modify loop templates.
Locate company logos.
Create or modify auto-generated templates.
Import user templates.
Piping
Things to Decide
Define tagging conventions.
What components are tagged?
How to delineate tag
Assign line numbers.
Dialog modifications
Identify custom (non-Bentley) components.
Specification definition
Miscellaneous items
Color by line number, size or spec?
Layer by line number or spec.
18
Apr-10
Tasks
Set Drawing Preferences.
Modify dialogs.
Create custom components and/or modify.
Specification Generation
Create new spec for project.
Identify default spec item for each nominal size: Valve Type, Elbows
and tees, and Flanges, gaskets and bolts.
Equipment
Things to Decide
Define tagging conventions.
Pumps
Vessels
Exchangers
Associated equipment (pump nozzles)
Identify common assemblies or custom components.
Identify location points.
Color and layer designations
Dialog modifications
Tasks
Apr-10
Modify dialogs.
Create common assemblies or custom components.
Create location points.
Color and layer designations
Specification generation
Create new spec.
Identify default spec for each component class.
19
Structural
Things to Decide
Define color and layer conventions.
Columns
Main Beams
Sub-members
Bracing
Define structure divisions (ex. Separate modules for each structure).
Detail connections - how much detail is required
Define import/export (stress) work flow methods.
Miscellaneous items
Tasks
Create AutoCAD Start-up Template Drawing file.
Define and create Work Frames.
Use Detail Center to create Styles.
Plans
Sections, Elevations
Details
Create Custom Shapes.
Create Template Types.
Base Plates, Bolting, etc.
Define Bentley Work Area Function Workaround.
Walkthrough and Interference Detection

Things to Decide
Basis for Interference runs (Steel vs Piping, Piping vs All.)
Partitions and Size of Interference runs
Is a formal walk through needed? (30%, 60%, 90% Design Reviews)
20
Apr-10
Who will need to be present?
Who will run the walk through?
When? Where? Who sets it up?
What part of models (all) will be walked through?
What type of walk through?
P&ID review
Construction review
Operations review
Maintenance review
Isometrics and Isogen

Things to Decide
How will isometrics be broken up? By line, by Spec, other?
Who has ownership of the isometric production?
What will the isometrics look like?
PCF output options (ISOGEN)
Title Block
Option switch settings (ISOGEN)
Annotation and Alternate text (ISOGEN)
Positioned text (ISOGEN)
Annotation and text
BOM options
Layering and Colors
Checking Procedures
Tasks
Apr-10
Develop an isometric production procedure.
Create/modify title block.
Enter Annotation and dimensions defaults.
Set Milestones in Deliverables .
21
Orthographics
Things to Decide
What plots/layouts are required?
Plans
Sections
Details
Drawing content
Equipment List
Nozzle Schedule
Cosmetics - how the drawing will look
Title Block
Dimensioning
Annotation: Line Numbers, elevations, general notes
Tasks
Develop a drawing production procedure.
Create/modify Title Blocks.
Enter annotation and dimension defaults.
Set Milestone in Deliverables.
Bill of Material Reports

Things to Decide
How often will BOM reports be extracted and for what purpose?
How will BOM reports be used?
Project status
Purchasing
Which database fields will be used and/or added?
Layout of columns
Do Specs need to be revised?
22
Apr-10
Document Management Application
Does the external drawing database need to be revised?
To what format will the BOM report be extracted?
Excel, Word, Access?
Tasks
Format the report look and arrange the layout of columns.
Document Management Application

Bentley is now providing document and data management applications. Below is
a brief description of the applications.
ProjectWise Application Server

ProjectWise is the backbone of a managed environment for your information.
ProjectWise is the company's flagship collaboration server, enabling highperformance multi-site collaboration among AEC project teams performing
distributed engineering. ProjectWise supports a managed environment for AEC
IT. In a managed environment, valuable AEC information is confidently shared,
synchronized, and secured; all data can be leveraged throughout an asset's
lifecycle and on future projects. Fast-track projects can be managed better by
ensuring that project teams can work on separate project tasks in parallel.
ProjectWise features include local caching and enhanced digital security, for fast
file access and secure workflows across distributed teams.
Types of Databases Supported

AutoPLANT Plant Design and P&IW applications support multiple types of
database environments. Below is a brief description of each database type. It is
recommended that you select the environment that best fits your company's
needs.
Microsoft ACCESS 2003, 2007

Microsoft Access is only recommended for very small projects because the
database does not support a multi-user environment.
Apr-10
23
Types of Databases Supported
SQL Server 2005 Express Edition, 2005 Express Edition

with Advanced Services, 2005 Standard Edition and 2005
Enterprise Edition
This database environment is recommended for large projects with multiple
users accessing the software at the same time. The projects can be set up as
individual databases or as a multi-project database.
Oracle Version 9i Release 2, 10g Release 2, 11g Release 1

This database environment is recommended for large projects with multiple
users accessing the software at the same time. The projects can be set up as
individual databases or as a multi-project database.
24
Apr-10
Types of Project Environments

There are multiple project environments that apply to the manner in which
project data is managed by AutoPLANT Plant Design and P&IW applications.
Below is a brief description of each mode. Refer back to this section when
creating your new projects.
Central Mode
This is a full project mode, where all data from AutoPLANT 2D (P&ID and
Instrumentation data) and AutoPLANT 3D (Process piping and Equipment data) is
stored in a Central project database. The project data could be modified from
any application allowing quick 2D TO 3D consistency reporting.
The Central mode is available for Oracle, or SQL Server project databases. Bentley
strongly recommends the use of central mode for AutoPLANT projects.
Apr-10
25
Multi-Project Mode
This option will only be available if you have selected an SQL Server or Oracle
Database Type. It enables you to specify that the database used by this project
may also be used by other projects. For example, if you create an Oracle project,
you are required to specify the Oracle database connection information to create
the project. If you create this project using multi-mode, you will be able to create
subsequent projects that use this same Oracle database instance. You should
note that there is a reasonably significant performance penalty to supporting
multi-project mode. Enabling this functionality will effectively add a new ProjID
(project ID) column to every project table, which stores the project ID for that
database record. Every query on the project database must then include the
ProjID in order to filter the query so that it only returns records related to that
project. Oracle and SQL Server projects that were created using previous versions
of Bentley Plant software were automatically configured to support multi-project
mode.
Note: Multi-Project mode will be required for any project using ProjectWise.
26
Apr-10
Distributed Mode
This mode handles data in a manner that is most similar to that used in previous
AutoPLANT Plant Design versions (v2.01 and earlier). Component data is still
stored in the familiar PIPING, NOZZLE, and EQUIPMENT tables. Exceptions to this
include: Line Number, Service, Unit, Area, etc. data, which are now stored in the
project relationship tables.
Apr-10
27
Module Review
Module Review
Now that you have completed this module, let's measure what you have learned.
Questions
1 For a project to be successful, is proper training and knowledge critical?
2 Should your company's CAD standards be considered before creating your
project?
Answers
1 Yes, do not attempt to learn this software while working on a production
project without proper training.
2 Yes, your company's CAD Standards are an important consideration when
creating and configuring your project. Any customization made to a
project will not be retroactive. Changes will only affect data from that
point forward.
28
Apr-10
Project Information
Module Overview
In this section you will use the Bentley Project Administrator application to create
a new project in an Access format and will be shown how to create projects in an
SQL and Oracle format. You will complete an in-depth study of your project file
structure. You will be introduced to the applications accessing your project.
Module Objectives
Apr-10
Create a new project with different database environments.
Understand the project application directory structure.
Understand the project local and network directory structures.
Configure the applications accessing the project data.
29
Project Information
Create a New Project from Base

Project creation with other database types is shown in detail below and can be
used as a guide when creating your production project.
It is important to note that in most cases, the project will be located on a network
server with client workstations accessing the project from their workstations.
For training purposes, we will create an Access project.
Microsoft Access Project
Exercise 1: Create an Access Project

1 Select Programs > Bentley > Plant V8i > Project Tools > Project
Administrator from the Windows Start menu.
2 Highlight an existing folder.

3 Select File > Add Root.
The Browse For Folder dialog opens.
4 Browse to your C: drive.
5 Select Make New Folder.
Project Information
30
Apr-10
6 Rename New Folder to AutoPLANT_Admin_Training as shown below.
7 Press Enter.
8 Click OK.
9 Highlight AutoPLANT_Admin_Training in the Project Administrator
window.
10 Right-click.
11 Select New Project.
Note: Oracle is grayed out because Oracle is not installed on this workstation.
Use Multi Project Mode is only available for SQL and Oracle
databases.
12 Highlight Access.
Apr-10
31
Project Information
13 Click Next.
14 Select Standard Base Project from the Select the Base Schematic Project
Template.
15 Leave the Units set to Imperial.
16 Click Next.
17 Click Next.
The project paths are accepted. These may be modified later.
Project Information
32
Apr-10
18 Fill in dialog information as shown below.
19 Click Finish.
The project structure is now created. If the database format was not
Microsoft Access, the connection details would have been necessary
when the Projdata database started to create.
The new root directory and project are now shown in the Project
Administrator.
Apr-10
33
Project Information
SQL Server Projects

These exercises are for illustration only.
Exercise 1: Create an SQL Server Database

1 Launch SQL Server Management Studio.
2 Expand the Security node.
3 Select Login.
4 Right-click on Login.
5 Select New-Login.
6 Type PIW in the Login name field.

7 Set the SQL Server authentication check box.
8 Type pwuserin the Password field.
9 Clear the Enforce password policy check box.
10 Leave the Default database as master.
Project Information
34
Apr-10
11 Leave the Default language as English.
12 Click OK.
13 Right-click on the Database node.
14 Select New Database.
15 Type PIW in the Database name field.
Apr-10
35
Project Information
16 Select Browse in the Owner field.
17 Type PIW.
18 Click Check Names.
19 Click OK.
The New Database dialog is returned.
20 Click OK.
Project Information
36
Apr-10
Exercise 2: Create an SQL Database Project

1 In the Windows Start menu, select Programs > Bentley > Plant V8i >
Project Tools > Project Administrator.
Project Administrator opens. If prompted for a password, use supervisor.
2 Expand Bentley Plant V8i Projects.
The projects within the root folder are now visible.
3 Right-click on Bentley Plant V8i Projects.
4 Select New....
The Provider Type dialog opens.
5 Select SQL Server.
6 Click Next.
Warning: The option Use Multi Project Mode is available but not recommended for 2D
Projects.
7 Set Use Central Project Mode.

8 Click Next.
9 Click Next again.
The Project Paths are accepted.
Apr-10
37
Project Information
10 Complete the following dialog as shown.
11 Click Finish.
The project starts creating and the Data Link Properties dialog displays.
12 Select your server in the Select or enter a server name list.
13 Set the Use a specific user name and password check box.
14 Type PIW in the User name field.
15 Type pwuser in the Password field.
16 Set the Allow saving password check box.
17 Select the PIW database from your server as shown below.
18 Click Test Connection.
Project Information
38
Apr-10
To verify that the connection is working.

19 Click OK.
The finished project is listed in the Project Administrator.
20 Minimize the Project Administrator application.
Apr-10
39
Project Information
Oracle Projects
These exercises are for illustration only.
Exercise 1: Create a New Oracle User

Note: For first-time Oracle users, a User and Password must be created. For
existing Oracle users, the Login dialog will appear. Type your User
Name and Password into the dialog and click OK.
1 From the Windows Start menu, select Oracle > Application Development
> SQLPlus.
2 Type create user PIW identified by bbsi.
3 Click Enter.
4 Type /.
5 Click Enter.
User Created is returned.
6 Type grant connect, resource to PIW.
7 Click Enter.
8 Type /.
9 Click Enter.
Grant succeeded is returned.
The user and password have been created.
Exercise 2: Create a New Oracle Project

1 Maximize Project Administrator.
2 Expand Bentley Plant V8i Projects.
The projects within the root folder are now visible.
3 Right-click on Bentley Plant V8i Projects.
4 Select New.
The Provider Type dialog displays.
Project Information
40
Apr-10
5 Select Oracle.
6 Click Next.
7 Set the Use Central Project Mode check box.
8 Click Next.
9 Click Next.
The Project Paths are accepted.
Apr-10
41
Project Information
10 Complete the following dialog as shown.
11 Click Finish.
The Data Link Properties dialog displays.
12 Type your Data Source name in the Data Source field.
13 Set the Use a specific user name and password check box.
14 Type PIW in the User name field.
15 Type bbsi in the Password field.
16 Verify that Allow saving password is set.
The dialog should look similar to the one shown.
Project Information
42
Apr-10
18 Click OK.
19 Click OK on the Data Link Properties dialog.
The new project shows in the root folder.
Apr-10
43
Project Information
Understanding the Project Directory Structure

When creating a new project within Bentley Project Administrator, a directory
with the project's name will be created. This directory is typically located on a
network drive so that multiple users can access the project files. In the project
root directory, you will find three important files:
AT_PROJ.DBF: holds the list of projects that fall under this parent
directory
AT_PRODSV8i.DBF: holds the products that are registered on the

workstation
ACCESS.MDB: contains login information as well as application security

information
The project directory contains various files as well as a number of sub-directories.

Each project has a file in the root project directory called PROJECT.INI. This file
contains general project information, various default settings, and path settings
to various subdirectories. A sample PROJECT.INI and an explanation of the
individual sections and variables can be found in Appendix A.
Config Directory
The Config directory holds many of the delivered project configuration files
(.ini files), the border files for orthographic drawings and the delivered Isogen
format files.
Project Information
44
Apr-10
Datasheets Directory
The Datasheets directory contains all datasheets created for this project.
Within this directory are three sub-directories:
Equip: equipment datasheets. If you created a datasheet for Pump P100 called P-100DS.XLS, you would find this datasheet in the
Datasheets\Equip\ directory.
Instr: instrumentation datasheets. If you created a datasheet for

Clickure Indicator PI-100 called PI-100DS, you would find this
datasheet PI-100DS.XLS in the Datasheets\Instr\ directory.
Other: other asset datasheets
There is also a Specifications directory within the Datasheets directory, where

Specification Sheets are stored. It has a sub-directory structure similar to
Equip, Instr and Other.
P&IW allows you to create both specification sheets and datasheets for any
tagged item. Although the terms are occasionally used interchangeably, the
primary difference between specification sheets and datasheets is that a
specification sheet is what you want to obtain in the future and a datasheet is
what you physically have. For example, the design may specify the TDH for a
Pump must be twenty-four feet, but the Pump that was purchased tests to
twenty-five feet. The Specification Sheet would record 24', and the Datasheet
would record 25'.
Hint: The physical location of datasheets is controlled by the DATASHEETS key
under the [PATHS] section of the PROJECT.INI file. It is recommended

that this path be left as the default unless there is an overwhelming
reason that this must be changed.
Apr-10
45
Project Information
Electrical Directory
The Electrical directory contains a Drawings sub-directory in which electrical

drawings are stored.
Equip Directory
The Equip directory contains a Drawings sub-directory in which equipment

Project Information
46
Apr-10
Hookups Directory
Hookups are also referred to as installation details. The Hookups directory is

similar to the Datasheets directory in structure, with Hookup drawings
seprated into sub-directories Equip for equipment, Instr for instrumentation,
and Other for other types of assets.
Instrumentation Directory
The Instrumentation directory contains a Drawings sub-directory in which

loop diagrams are stored. For example, if you created a loop named F-101A,
you would find the F-101A.DWG drawing in the Instrumentation\Drawings
directory.
Apr-10
47
Project Information
Iso Directory
The Iso directory contains a Drawings sub-directory in which isometrics

P&ID Directory
The P&ID directory contains a Drawing sub-directory in which P&ID drawings

are stored. For example, if you created a P&ID drawing named AREA101A,
you would find the AREA101A.DWG drawing in the P&ID\Drawings directory.
Project Information
48
Apr-10
Piping Directory
The Piping directory contains a Drawings sub-directory in which piping

Projdata Directory
The Projdata directory typically contains three files:
Apr-10
Projdata.mdb: the project database, where project-specific data (e.g.

relationships, etc.) is stored. With a Central Mode project, this file is
contains all raw data for the project. Although documents associated
with the project are distributed into appropriately named directories,
all data for the project will reside in this file. With a Distributed Project
mode, each model or drawing file has its own database file.
49
Project Information
Project.mdb: contains the report and view definitions
Schema.mdb table: contains the table structures
Hint: Any customization to your project data storage (i.e., adding fields or
tables) will be done in the Projdata.mdb file.
Raceways Directory
The Raceways directory contains a Drawings sub-directory in which raceways

Reports Directory
Project Information
50
Apr-10
The Reports directory contains a Drawings sub-directory in which reports are

stored.
Standards Directory
The Standards directory has a number of sub-directories. The Datasheets,

Hookups, Instrumentation and P&ID directories hold templates for the
respective documents. The Rebcompdlgs.dll contains the CATT dialogs. The
Instrumentation directory contains symbols for AutoGen and Composite
drawings, electrical drawing templates and the projdata.mdb which is used to
store loop, panel and segment standard data.
Struct Directory
Apr-10
51
Project Information
The Struct directory contains a Drawings sub-directory in which structural

Custom Directories
Custom data structures and format changes are stored in the project
\Standards directory. For graphical elements utilized by P&ID,
customizations are stored in what is called the "custom" directory. This
directory location is specified by the APCUSTDIR key in the PROJECT.INI file.
Custom directories are discussed in depth later in this training course.
The ER Diagram
Relationships between the data tables within the projdata database are
displayed in the ER diagram on the local drive. To be most effective, this
diagram will need to be printed at a scale large enough to read individual
fields. Usually an E-sized sheet will suffice.
Project Information
52
Apr-10
Understanding the Directory Structure

There are four main directories installed with AutoPLANT: Local_Root,
Network_Root, Project_Root and Custom_Root. The Local_Root and
Network_Root directories should be installed locally on each workstation. The
Project_Root and Custom_Root directories should be installed on a network
server to allow sharing of files/data among different users.
All Bentley installs contain Local_Root and Network_Root files.
Files in the Local_Root and Network_Root directory are available only to the user
on that particular machine. If you make changes in these directories, no other
machine will be affected.
Project_Root and Custom_Root files, on the other hand, are shared by users on
any machine that accesses the network drive. If you make a change on
Network_Root or Custom_Root directories, all users accessing those files will see
the change.
Local_Root Directory
The Local_Root directory defaults to C:\Documents and Settings\All
Users\Application Data\Bentley\Plant V8i. This directory and its files must
reside on the local workstation. The Local_Root directory contains machinespecific files and settings.
Network_Root Directory
The Network_Root directory contains the files and settings needed to run the
software, including the program executables. Each workstation must have
access to these files if they intend to run the software. You can either install
the Network_Root files on each workstation or install the network files on the
network and then point each workstation to these files by modifying the
AT.INI.
Hint: Bentley recommends that network files be installed locally. This is
primarily because serving executables across a network taxes even

higher-bandwidth networks.
Apr-10
53
Project Information
Project_Root Directory
The Project_Root directory contains the data and documents created in the
project. Project specific customizations will be done in one of two ways. For
P&ID, you should first open Project.ini and add the following line within the
[PATHS] section
APCUSTDIR=c:\...\...\custom\ (where \...\...\ is the location of where you
want to put customized P&ID files. You do NOT need to call the directory
custom and may label it whatever you wish.
After doing this, the first time a P&ID file is created, the user will be prompted
whether or not they want this folder to be created. Selecting yes will create
the folder and copy to it most commonly modified P&ID files. If you wish to
modify any files not already copied here (%Project_Root%\...\Custom), copy
them from %Network_Root%\P&ID\...\...\ then place them in
%Project_Root%\...\...\custom\\...\ keeping the same file structure from
P&ID (%Network_Root%) and Custom (%Project_Root%).
For all other customization, either modify the files in
%Project_Root%\Config\. If the file you wish to modify, is not there, copy it
from %Network_Root%\modules\...\....\ keeping the same file structure from
Config (%Project_Root%) and Modules (%Network_Root%) downward. If the
file does not exist, place it in %Project_Root%\Config\...\...\ making sure to
put it in the most logical location.
Custom_Root Directory
The Custom_Root directory holds customizations other than those for P&ID
(which need to be added to each Project). This is where you would place any new
and/or customized files that are not Project Specific. As with customized files in
the %Project_Root%, you should keep a common folder structure to the location
for the same or similar files in the %Network_Root%. i.e. If you want to modify
BOLTS.EBS, which can be found in
%Network_Root%\Modules\Base\Piping\Draw\, you should copy it to
%Custom_Root%\Modules\Base\Piping\Draw\. The %Custom_Root% location
needs to be added to AT.INI in the [ALIAS] section.
The next section covers in more detail the various directories and some important
files that AutoPLANT creates when you install. This section is crucial in
understanding the fundamentals of how the software works.
Project Information
54
Apr-10
Local_Root Directories
C:\Documents and Settings\All Users\Application
Data\Plant V8i > CFG Directory
This configuration directory contains one file, at.ini, which is the major
configuration file used by the applications. In the at.ini configuration file a
"section" is marked by a heading in square brackets [ ], and the lines following
are called "keys".
A sample at.ini and an explanation of the individual sections and variables can
be found in Appendix A.

Data\Plant V8i > DataManager Directory
Apr-10
55
Project Information

Data\Plant V8i > I&W Directory
The I&W.mdb located in this directory is used for temporary storage of

project.mdb files while they are being modified in the I&W application. Once
a file is saved it is moved back to the project.mdb found in the Projdata
directory. An example would be modification of project reports.

Data\Plant V8i > P&ID Directory
This directory contains files related to the P&ID menus and toolbars.
Project Information
File
Description
PID.MNU
Compiled version of the P&ID and P&ID Tools menus
56
Apr-10
PIDBLK.MNU
Compiled version of the Block Manager menu
PID.DLL and
PIDBLK.DLL
DLL files containing the toolbar icon graphics

Data\Plant V8i > P&ID > Imperial, Metric or MMetric
Directory
These directories contain a file called nsize.txt, which is a list of available line
sizes for each unit's measurements.

Data\Plant V8i > Packager
The datatypes.V8il file found in this directory is a list of data types for each
platform.
Apr-10
57
Project Information

Data\Plant V8i > TemplateGen Directory
This directory contains the menu files (tmpl.mnc, tmpl.mnr, tmpl.msn, and
tmpl.mnu) and an auxiliary lisp file (tmpl-sup.lsp) used by Template
Generator.

Data\Plant V8i > Temp Directory
The Temp directory is used to generate reports.
Project Information
58
Apr-10

Data\Plant V8i > Tmpdir Directory
The TMPDIR directory creates a new temporary folder each time that a P&ID
is opened. This directory can get quite large and should be emptied on a
regular basis.
Apr-10
59
Project Information
Network_Root Directory
Not to be confused with Network drive, Bentley suggest you install this on all
the workstations running AutoPLANT software and by default, is installed
here: C:\Program Files\Bentley\Plant V8i\.
Note: The directory list below assumes a complete install of the Bentley
AutoPLANT Plant Design software.
Base Directory
This is where the seed files for new Projects reside. If, when creating a new
Project, you select Standard Base Project in the Select the Base Schematic
Template it will copy to the Project each of the folders within the
...\Base\Project\ folder. It also copies the \Base\Standards\ folder with all
its contents to the Project. If you wish to create a custom Schema, create a
folder within the \Base\Options\ folder. Copy the ..\Base\Project\ and
\Base\Standards\ folders to it, then modify the files within your new folder.
If you wish, you can also put a Custom folder in your new folder with any P&ID
customized files you want. This would be in lieu of what was discussed earlier.
Project Information
60
Apr-10
Bin Directory
This directory contains miscellaneous compiled code used by Bentley

applications, as well as program executables to launch Data Manager,
Document Manager, and Vision.
Language Directory
This directory contains databases that are used when a non-English version is
required.
Note: These files are not used on an English installation.
Apr-10
61
Project Information
P&ID > sym Directory
The SYM directory contains AutoCAD (.DWG) files, which are the graphics and
attributes used when placing an item into a P&ID drawing. For example, the
pmpcenv.dwg file located in this directory is the Centrifugal Vertical Pump
symbol that can be inserted on a P&ID drawing.
ProjectTools Directory
This directory contains program executables to launch the Convert Project,

Project Administrator, Project Packager and Split/Merge utilities.
Project Information
62
Apr-10
Specs > r1X > win Directory
This directory is used for storing specification files (optional) from the
different versions.
Support Directory
This directory contains various lisp (.lsp) programs, libraries and other files
needed by AutoPLANT and AutoCAD.
Note: This directory must be second in your AutoCAD search path for
AutoPLANT to function properly.
Apr-10
63
Project Information
Support_2D Directory
This directory contains additional minor files needed by P&ID and AutoCAD.
Note: This directory must be first in your AutoCAD search path for P&ID to
function properly.
SystemDoctor Directory
This directory is installed as part of the Core products and is for 3D application
use only.
Project Information
64
Apr-10
TemplateGen Directory
The Bentley Template Generator application enables you to create custom

(.dwg) templates and tokens that meet your company standards when
producing template-generated loop drawings within the Bentley
Instrumentation & Wiring application. This directory holds the files required
to create these loop templates in AutoCAD.
Tools Directory
This directory contains program executables to launch the Batch Print, Bulk
Datasheets Builder, Change Logo, and IWD editor utilities.
Apr-10
65
Project Information
Applications Accessing Project Data

Core Applications
Data Manager
Bentley Data Manager is a powerful relational database management tool for
storing, creating, and customizing project process instrumentation,
equipment, piping, and valve data. Developed by experienced
instrumentation engineers, Data Manager is the ideal tool for plant
engineering, maintenance, and operations departments.
Data Manager provides a fully-configurable user interface and database and
uses the industry-standard Microsoft Access format for easy linking to other
software tools. Bentley AutoPLANT Data Manager also supports Open
Database-Compliant (ODBC) data sources such as SQL Server, and Oracle.
Datasheets
Bentley Datasheets is an add-on module for Process and Instrumentation
applications that enables you to access and manage dynamically-passed
process and instrumentation data such as tag number, process data, vendor
data, etc. The Datasheets module utilizes Microsoft Excel as its native format
for data storage and customization.
Vision
Bentley Vision provides an easy-to-use environment to manage critical plant
data and documentation. The tree-like user interface allows you to quickly
navigate to a specific component to view operating data and associated
documentation. Vision and the Bentley applications share a common
relational database for storage of all plant data including process equipment,
lines, valves and instrumentation. Changes made to a P&ID are immediately
available through the Vision interface. By sharing a common relational
database, errors and data maintenance costs associated with duplicate data
are virtually eliminated.
Project Information
66
Apr-10
Document Manager
Bentley Document Manager enables you to organize, edit, and preview
project documents created with registered Bentley AutoPLANT applications.
Bentley AutoPLANT 2D Applications

Instrumentation & Wiring
Bentley Instrumentation & Wiring allows the user to define instruments,
loops, fieldbus segments, fieldbus panels, field panels, and card panels.
Because it uses the same engine as Data Manager, it provides users with a
familiar interface due to previous experience with modifying views, tables,
reports and forms.
Hookups
Bentley Hookups is an add-on module to Instrumentation & Wiring that
allows you to access and manage instrument installation detail drawings and
to generate parts lists and Bills of Materials. The Hookups module utilizes
Microsoft Excel as its native format for data storage and customization.
Layout Designer
Layout Designer uses the concept of layout drawings, a graphical, flexible
overview of instrumentation loops. A layout drawing may be defined for a
single loop if it is particularly complicated. Layout drawings may define an
area in a plant and all of the loop components associated with that area or all
of the loop components associated with a particular piece of equipment.
While in a layout drawing, users can create relationships between
components, and then proceed to define the connection details. Any
component on a layout drawing will have right-click context-sensitive menus
to reduce the amount of time it takes to perform detailed connections, tag
modifications or component definitions.
P&ID
AutoPLANT P&ID provides companies with an indispensable tool for creating
intelligent plant schematics. Utilizing the power of AutoCAD or with an
external relational database environment to create the intelligent plant
schematics, companies and engineers can now learn more about their plant
design in a fraction of the time that was needed to study hundreds of layout
drawings.
Apr-10
67
Project Information
P&ID provides a cost-efficient application for companies by reducing the

design and documentation time for capturing process information for system
design and plant studies (HAZOP studies, etc.), ensuring compliance to OSHA
1910 and ISO standards. Through its "scalable design," P&ID is suitable for
large, mid-sized and small engineering companies, as well as plant operators,
providing a key tool for the lifecycle design and documentation of process
plants.
P&ID Converter
Almost all companies have P&ID drawings in some form that represents the
schematic map of their process plants that need to be maintained.
Engineering consulting firms usually receive P&IDs from the client and are
requested to re-draw or use them as the basis for a plant project. Most of
these P&IDs were probably developed using native AutoCAD, without a third
party developer's software package, but using internally developed symbol
libraries to suit client/company standards. For those who did use a third-party
software application, this AutoPLANT utility can convert many of the drawings
generated by those systems as well.
The AutoPLANT P&ID Conversion Toolkit is essential to both the owner/
operator and the engineering contractor as it provides the ability to very
quickly convert these attribute/non-attribute, non-intelligent P&ID drawings
to intelligent AutoPLANT P&ID drawings. Attribute and text information in
these drawings can be extracted and stored in the AutoPLANT P&ID external
project database without the expense of redrawing all of the P&IDs.
Template Generator
The Bentley Template Generator application enables you to create custom
templates and tokens that meet your company standards when producing
template-generated loop drawings within the Bentley AutoPLANT
Instrumentation & Wiring application. The Template Generator module is
available from within Instrumentation when the edit option is chosen for
instrument templates. It requires AutoCAD or Microstation.
Project Information
68
Apr-10
AutoPLANT 3D Applications
AutoPLANT Piping
AutoPLANT Piping V8i Edition application is an object-based 3D piping system
design and modeling application. The software enables users to interactively
route and place piping components in a 3D environment. Piping can be used
to generate orthographic and isometric drawings and report quantities from
the 3D model.
AutoPLANT provides state-of-the-art 3D modeling capabilities previously
unavailable in any AutoCAD-based package. This capability is achieved
through ObjectARX technology, using 3D objects to represent plant
components. These custom objects provide superior representations from
any viewing perspective while using a fraction of the file size required using
standard AutoCAD shapes.
Piping utilizes a "spec driven" design approach, which maximizes quality by
ensuring compliance with applicable design criteria. Active database links
ensure correlation between the graphical and descriptive data in the model.
AutoPLANT Equipment
AutoPLANT Equipment module is a 3D parametric modeling application.
Equipment Modeler creates and edits mechanical equipment in a 3D
environment. Object-oriented features help you keep up with the inevitable
changes of a real world project. Updates to equipment dimensions are
instantly reflected in the 3D model.
The system comes with hundreds of mechanical equipment types commonly
used in building and plant design (such as pumps, tanks and heat exchangers).
A full selection of nozzle types also provides connectivity to the powerful
AutoPLANT Piping application.
AutoPLANT Raceways
AutoPLANT Raceways is an object-based 3D electrical system design and
modeling application. The software enables users to interactively route and
place commonly-used electrical and instrumentation components in a 3D
environment.
AutoPLANT Raceways provides state-of-the-art 3D modeling capabilities
previously unavailable in any AutoCAD-based package. This capability is
achieved through ObjectARX technology, using 3D objects to represent plant
components. These custom objects provide superior representations from
any viewing perspective while using a fraction of the file size required using
standard AutoCAD shapes.
Apr-10
69
Project Information
Raceways utilizes a "spec driven" design approach, which maximizes quality

by ensuring compliance with applicable design criteria. Active database links
ensure correlation between the graphical and descriptive data in the model.
Note: The AutoPLANT Piping, AutoPLANT Equipment, and AutoPLANT
Raceways systems are built on powerful object-oriented technology,

yet are easy to use and customize. They work seamlessly with other
Bentley design and information management technologies and can
integrate with your plant and business systems.
Bentley Isogen Interface

Isogen is an industry-standard automatic isometric generation program.
Fabrication, system, and erection isos can be automatically generated from a
3D piping model. Isogen offers a multitude of configuration features that
provide for a finished drawing to fit your requirements. Isogen is available as
an integral part of both applications with no additional licensing required.
AutoPLANT Isometrics
AutoPLANT Isometrics is an object-based isometric drawing application
allowing either direct "spec driven" isometric drafting or automatic extraction
from the 3D model. It contains the same powerful reporting features as the
AutoPLANT Piping application.
Direct isometric drawing creation allows designers to create piping isometrics
without first having to build a 3D model. The AutoISO feature automatically
produces piping isometric drawings from models creating using AutoPLANT
Piping.
Fully-dimensioned Isometric drawings can be used to generate a 3D Model
using our Plant Exchange Format (PXF). The combination of these techniques
ensures that piping designers have the right tool for all types and sizes of
projects.
Project Tools
2D to 3D Consistency Reporter
The AutoPLANT 2D to 3D Tools compares the components in the AutoPLANT
P&ID application with the equivalent components in AutoPLANT PIPING and
EQUIPMENT applications. In order for the 2D to 3D functionality to operate
you must have both AutoPLANT P&IDs and AutoPLANT Piping and Equipment
models.
Project Information
70
Apr-10
Configuration Editor
The Configuration Editor tool allows you to edit, copy and delete your
configurations to meet client or company standards.
Project Administrator
Project Administrator enables you to manage projects and edit database
configurations and tag types. It also provides control of system administration
functions for creating users, assigning users to groups, granting user/group
rights, and creating user/group functions and levels of access. Project
Administrator is available from within the Project Tools folder installed with
AutoPLANT Plant Design, P&ID and Instrumentation & Wiring.
Project Connectivity Reporter

The Project Connectivity reporter allows Users or System Administrators to
run Connectivity Checking outside the design files, on a project basis.
Project Packager
The Project Packager allows a project, including its structure, data and
documents, to be packaged for sending to another party. The packaged
project is included in a zip file. The other party can "un-package" the project
into the database type they are currently using. This module is available from
within the Project Tools folder installed with PIW.
Relationship Manager
Relationship Manager is an AutoPLANT Plant Design application, installed only
if the AutoPLANT Plant Design applications are installed. It cannot be used to
work with the AutoPLANT Process and Instrumentation applications. The
Relationship Manager provides a central location for an administrator to
manage AutoPLANT relationship values (e.g., LineNumber, Unit, Area, Service,
Spool, and Document).
Split/Merge Project
The Bentley Split/Merge Project utility is available from within the Project
Tools folder. It enables you to:
Apr-10
Split larger AutoPLANT projects into smaller, more manageable subprojects.
Merge the sub-projects back into the parent project.
Create a single project from multiple projects by merging the projects

together.
71
Project Information
Tools
Batch Print Utility
The Batch Print utility provides you with the capability to update and print
multiple documents associated with an AutoPLANT project.
Bulk Datasheets Builder

The Bulk Datasheets Builder utility assists PIW users in quickly creating
datasheets for multiple tags. Users are able to select tags by tag code or from
the tag register and assign templates to multiple tags. Once templates are
assigned, users are able to name and create the datasheets for all selected
tags. Bulk Datasheets Builder is available from within the Tools folder.
Change Logo Utility

The Change Logo utility enables you to quickly replace logos that appear on
Datasheets (*.XLS), AutoPLANT Specification Sheets (*.XLS), and Hookup
Drawings (*.XL) which utilize Microsoft Excel as the native format for data
storage and customization. It is available from within the Tools folder.
Class Editor
The AutoPLANT Class Editor (CE) provides an intuitive graphical user interface
to modify the information in a project's configuration files that defines the
PIPING/ISOMETRICS modules and their individual components. It also
provides direct access to the method script files, port definition, and
specification search criteria that are used by each component class.
Dialog Editor
Dialog Editor allows you to create and edit dialogs.
Drawing Flattener
Drawing Flattener produces a 2D flat file with hidden lines removed from a
predefined view in a 3D file or files. Flattened files can be output to different
scales and run as batch (multiple files) if desired.
IWD Editor
The IWD Editor allows for the modification of IWD templates and drawings
that are created by the Instrumentation application. These templates are
often used as borders for detailed connection drawings and for layout
drawings.
Project Information
72
Apr-10
Script Editor
The Script Editor is an interface that allows a user to write or edit the EBS files
used by the AutoPLANT Plant Design software.
Apr-10
73
Project Information
Module Review
Module Review
Questions
1 Which project type stores all the database data in the projdata.mdb file?
a) Central Project Mode
b) Distributed Project Mode
c) Standalone Project Mode
2 True or False: AutoPLANT supports many type of databases.
3 True or False: Data Manager provides an easy-to-use interface to the
database.
4 True or False: RelationShip Manager is a 2D and 3D administration tool.
Answers
1 The Central Project Mode stores all of the database data in the
projdata.mdb file.
2 True: AutoPLANT supports many type of databases, if the database
software is installed.
3 True: Data Manager can be used to create custom views and reports of
the database.
4 False: RelationShip Manager is a 3D administration tool only.
Project Information
74
Apr-10
Configuring the Project

Database
Module Overview
In this chapter you will learn to use tools and utilities such as the Project
Administrator application to make modifications to the project.
Module Objectives
Apr-10
Review Project Administrator properties.
Modify the database properties.
Modify the AT_Views.
Modify tag types.
Understand mapping.
Modifying CATT dialogs.
Understand the project objects' properties.
Modify fields and views in an SQL project.
75
Overview of Project Administrator
Overview of Project Administrator

In this section you will become familiar with the Project Administrator interface.
The Project Administrator is part of the AutoPLANT V8i Edition installations.
Archive
The Archive command enables you to create a backup, or archived, copy of the
selected project. A project may be archived in the following manner:
Exercise 1: Create an Archive folder

1 Select Bentley > Plant V8i > Project Tools > Project Administrator from
the Windows Start menu.
2 Select the AP_Sample project folder.
3 Select File > Archive from the menu or right-click on the project folder in
the navigation tree.
The following dialog opens, prompting you to specify the destination
directory for the archive.
4 Browse to the drive of your choice.

5 Click Make New Folder.
A New Folder directory is created below the currently selected drive. New
Folder is highlighted.
6 Type Archive.
76
Apr-10
Set as Startup Project
Exercise 2: Restoring a Project

1 Expand Recycled Projects.
2 Right-click on the Project.
3 Select Restore.

This command enables you to select the default startup project for other
AutoPLANT applications.
To use:
1 Select File > Set as Startup Project from the menu or right-click on the
project folder in the navigation tree.
2 Select Set as Startup in the context menu.
Revalidate Project
This command will validate a project that has been restored so that it may be
edited.
A project may be revalidated using this method:
1 Select the restored project in the navigation tree.
Apr-10
77
2 Select File > Revalidate Project from the menu or right-click on the
restored project in the navigation tree.
3 Select Revalidate Project.
Alternatively, you can set up automatic validation upon project selection in the
navigation tree by doing the following:
1 Select Edit > Preferences.
2 Select the General tab.
3 Set the Validate Tree on Load option from the Tree View Settings group
box shown below.
Project Properties
When a new project is created, the Project Administrator builds a PROJECT.INI file
in the project directory, which contains general project and database
configuration data.
The Project Administrator dialog enables you to view/modify the information
stored in the [GENERAL] and [Paths] configuration groups in PROJECT.INI. To
access the dialog:
1 Expand the Project node.
78
Apr-10
2 Select Properties.
Select a few different properties and note that the value from the
project.ini is shown and can be changed in the Selected Value field.
[GENERAL]
APPLICATIONS=DOCMANAGER;PIPING;ISOMETRICS;ELECTRICAL;EQUIP;2DPIPIN
G;FLATTENER;VISION;NAVIGATOR;DATAMANAGER;HOOKUPS;I&W;INSTRUMENTATI
ON;DATASHEETS;TEMPLATEGEN;P&ID;STRUCTURAL;
DeleteTagNumbers=Yes
TagNumPrefix=000
ProjectName=
ProjectNumber=1
ProjectDescript=
ClientName=AutoPLANT Sample Project
ClientNumber=A1
ClientLoc=Bentley,Exton
ContractorName=
ContractorNumber=
ContractorLoc=
Remove tags on document deletion=Yes
Apr-10
79
Adding a Database to the Current Project

By expanding the Database node and selecting Databases, you can Edit, Add,
Modify, or Remove a database entry to the Project Databases list. This dialog has
these options:
Edit Tables: allows you to modify the tables within the database.
Add: allows you to add a new database to the project.
Modify and Remove: can only be executed on custom user databases

that have been added to the project (e.g., system databases
PROJDATA and SCHEMA may not be modified or removed).
To add a database to the current project:

1 Click Add.
80
Apr-10
The Data Link Properties dialog opens.
From this dialog you will modify the properties that were set for the user
database when it was previously added to the project.
2 Select the desired database provider type (Microsoft Jet 4.0 OLE DB
Provider for Access databases).
3 Click Next.
4 Select the Connection tab.
5 Select an existing database.
Note: If you wish to use a new one, you first need to create it using Access.
6 Add any user/passwords needed to access this database.

7 Click Cancel.
This exits the dialog without creating a new project database.
Removing a Database from the Current Project

1 Select Database > Databases properties page from the navigation tree.
2 Select a non-system database from the Project Databases list.
3 Click Remove.
Warning: System databases (e.g., PROJDATA and SCHEMA) cannot be removed from a
project.
Apr-10
81
Connecting to Password Protected Databases

Database systems such as Oracle or SQL Server require an additional user login
from the AutoPLANT software. If this login information is not included in the
configuration, you will be prompted to log into the database upon application
initialization. If this is undesirable, the connection string can be modified to
include this information, thereby bypassing this additional login requirement. For
example, the standard connect string found in the project's PROJECT.INI file will
only include the DSN value. Optionally, you can include the UID and PWD values
required by your database system on the Connection tab of the Data Link
Properties dialog.
Add the following definition to your AT.INI file.
[Databases]
Projdata=dsn=AutoPlant Oracle; uid=<oracle username>; pwd=<oracle
password>
In addition, if the AutoPLANT application must access a password-protected
database system, these values must also be included in the AT.INI file as shown
below:
[AT_ASI]
user=<oracle username>
password=<oracle password>
Import-Export
This is used for the Plant Design software. It gives you the ability to set the switch
so that when a .jsm or .pxf file is exported, it will be recorded in the doc_reg
table. You have the ability to set the path to be used to store the files by setting
the switch to publish.
System
This folder is used by the Plant Design software for setting defaults for file
locations, slop tolerances and default values.
Model
Plant Design uses this folder for AutoCAD settings such as north orientation and
display options.
82
Apr-10
Piping
Plant Design uses this folder for pathing, color codes for nodes, preset copy
values to be made available for changing, and preset update options for globally
updating the model.
Isometrics
Used by the Plant Design software for setting the paths for the Isometric
application, north orientation, display, node colors and dimensioning style.
Equipment
Plant Design uses this folder for storing paths to the equipment module and
display.
Isogen
This folder is used by the Plant Design software for the automatically generated
isometric created by Isogen. Pathing, display and automatic attribute extraction
can be set here.
Reports
This folder contains a list of available fields for the Bill of Materials reports.
Apr-10
83
Manipulating the Databases
Exercise 1: Edit a Table in the Current Project Database

1 Access the Database > Databases properties page from the navigation
tree.
2 Select the Projdata database from the list.
3 Click Edit Tables.
4 Select the Area3D table from the list.

5 Click Edit.
The following table describes the Edit Table fields:

Table Design
Used to launch Microstation Access for modifications to the table structure
Physical Name
This read-only field displays the physical name of the current table in the
underlying database.
Description
Description of the current table
Registered
Applications
Enables you to indicate the registered applications whose database(s) will

be affected by the current database table. Select the button to the right of
this field to display the Registered Applications dialog, which shows a list of
registered applications.
84
Apr-10
Relationships
Type
Enables the user to associate components with records in database tables
Attributes
These check boxes enable you to change the field properties of the current
database table.
6 Review the dialog.

7 Click OK.
Exercise 2: Add and Remove a Field from a Table

1 Select the PIPING table from the list of available tables.
2 Click Edit.
Note: The Table Design option allows you to add, modify and remove columns
from the PIPING table.

3 Click Table Design.
The PIPING table opens in Microsoft Access Design View.
Apr-10
85
4 Scroll to the MANU_FACT field in the Field Name section.

5 Right-click on it.
6 Select Delete Rows from the context menu.
The MANU_FACT field is removed. The column is deleted from the Piping
table.
Warning: Any data existing in a data field that is deleted will be permanently lost, even if the
administrator adds the column back again later.
7 Set the curser below the last row defined in the grid.
8 Type COMMODITY in the Field Name.
9 Set the Data Type to Text.
10 Set the Field Size to 24.
11 Select File > Save.
12 Exit the table.
13 Click OK.
The Edit Table dialog closes.
14 Click Close.
Project Administrator returns.
86
Apr-10
Exercise 3: Link an External Database Table to the Project

1 Launch Microsoft Access.
2 Create a new database entitled FLOWS.
3 Save the FLOWS database to the project's Projdata directory.
4 In the FLOWS database, create a table called FlowRate.
5 Add a new field called FlowNum.
6 Select Text from the Data Type field list.
7 Type 3 in the Field Size field.
8 Add a new field called FlowDesc.
9 Select Text from the Data Type field list.
10 Type 50 in the Field Size field.
11 Set FlowNum as the Primary Key.
12 Add information into the FlowRate table, as below:
13 Save the table.

14 Close Access.
16 Expand the AP_Sample project.
17 Access the Database > Databases properties page from the navigation
tree.
18 Select PROJDATA from the Project Databases list.
19 Click Add.
Apr-10
87
The Data Links Provider dialog displays.

20 Select Microsoft Jet 4.0 DB Provider.
21 Click Next >>.
22 Browse to \AP_Sample\Projdata.
23 Select Flows.mdb from the Select Access Database dialog.
24 Click Open.
88
Apr-10
You will receive verification that the database has been connected to the
project.
26 Click OK.
The Data Links dialog is returned.
27 Click OK.
Note: The database is inserted as Data1.
28 While highlighted, rename to FLOWS.

29 Select FLOWS.
The Tables in FLOWS dialog opens.
31 Click Add.
32 Select FlowRate.
33 Click OK.
34 Highlight FlowRate.
35 Click Edit.
The Edit Table dialog opens.
Apr-10
89
36 Select the browse button next to the Register Applications field.
37 Set DataManager, Project Administrator and AutoPLANT P&ID.

38 Click OK.
The applications are registered and the dialog closes.
39 Click OK.
The Edit Table closes.
40 Click Close.
The Tables in FLOWS dialog closes and Project Administrator returns.
Exercise 4: Modify the Project.ini file

1 Browse to \AP_Sample directory.
2 Open the Project.ini file in Notepad.
3 Search for the [Data Sources] section.
[DATA SOURCES]
Projdata =DSN=MS Access for AutoPLANT;DBQ=%s
Schema
=DSN=MS Access for AutoPLANT;DBQ=%s
ModelDB
=Dsn=MS Access for AutoPLANT;DBQ=%s
SpecDB
Report
FLOWS
=DSN=MS Access for AutoPLANT;DBQ=%s;PWD=""
4 Modify the flows statement to remove :PWD="" as shown below.

FLOW=DSN=MS Access for AutoPLANT;DBQ=%s. (??should this say FLOWS?)
5 Search for the [Databases] section.

[DATABASES]
90
Apr-10
Projdata=%ProjPath%\PROJDATA\PROJDATA.MDB
;For SQL Server
;Projdata =DATABASE=%s;DRIVER={SQL Server};UID=;PWD=;SERVER=%s
Schema=%ProjPath%\PROJDATA\SCHEMA.MDB
FLOWS=User ID=Admin;Data
Source=C:\sarnia\dale_ron\Projdata\FLOWS.mdb;Mode=Share Deny
None;Extended Properties="";Jet OLEDB:System database="";Jet
OLEDB:Registry Path="";Jet OLEDB:Database Password="";Jet
OLEDB:Engine Type=5;Jet OLEDB:Database Locking Mode=1;Jet
OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk
Transactions=1;Jet OLEDB:New Database Password="";Jet OLEDB:Create
System Database=False;Jet OLEDB:Encrypt Database=False;Jet
OLEDB:Don't Copy Locale on Compact=False;Jet OLEDB:Compact Without
Replica Repair=False;Jet OLEDB:SFP=False.
6 The flows statement is so long it has to be modified to match the

statement below.
FLOW= C:\sarnia\dale_ron\Projdata\FLOWS.mdb.
Note: The statement will vary based on your configuration.
Exercise 5: Join the New Table with Existing Tables

1 Select Database > AT_Views.
AT_Views (system views) displays within the project.
2 Select the AT_PIPERUN view.
3 Click Edit.
The Edit View dialog displays.
4 Select the Joins tab as shown below.
5 Select Pipe_run in the window.
Apr-10
91
6 Select FlowRate in the Project Tables group box.

7 Click Add.
8 In the Join Expression group box, select Pflow in the Pipe_run field.
9 Select FlowNum in the FlowRate field as shown in the following figure.
One to many
relationship
If set, toggles the association of the primary key for a selected field value.
System
If set, defines the current field as a system field.
Primary Key
This list enables you to associate a primary key (i.e.,Tag_Type, Tag_No, etc.)
with a selected field value in the current join expression. Select the
appropriate field value within the left pane of the dialog, set the One to
many relationship check box, and then select the appropriate list entry.
10 Select the Fields tab.

11 Highlight the FlowRate table.
12 In the FlowRate Fields group box, set FlowDesc.
13 Click Save.
Note: From within Data Manager, if you have existing pipe runs in the project,
you will be able to input a value (for example 1, 2, or 3 in the Pflow

field).
14 Click Refresh View.
To see that the FlowRate field is populated.
Exercise 6: Add Fields to the Database Tables

92
Apr-10
3 Expand Database > Databases.

4 Select the Projdata database.
6 Scroll to the Equip table.
7 Click Edit.
8 Clear the Protected attribute in the following dialog.
9 Click Table Design.

Microsoft Access opens.
10 Scroll to the bottom of the list of fields.
11 Type EDT in the first blank field.
12 Set the Data Type to Text.
13 Set the Field Size to 20.
14 Repeat steps 11-13, typing EDP in the next blank field.
Apr-10
93
The table should now appear as below.
15 Click Save.
16 Close Microsoft Access.
17 Re-set the Protected attribute.
18 Click OK.
19 Click Close.
The Project Administrator returns.
Note: This method is used for Access only; it will not work in SQL or Oracle.
94
Apr-10
AT_VIEWS
AT_VIEWS
A view is defined in AutoPLANT P&ID as a collection of data fields. Each tag type
may have one or more views associated with it. One view is designated as the
default view, which is used during the creation, import, and export of tagged
components in the drawings. Therefore, in order for a tagged component to be
placed in a drawing, it must have a view associated with its tag type.
When you CATT on a component in P&ID, if multiple views are associated with
the selected component's tag type, a dialog will display listing the views. The view
selected controls the data displayed in the CATT dialog.
P&ID has its own view definitions that are separate and independent of any other
application working within the project environment. The application's views can
be modified or created on the AT_Views property page that resides under the
Database branch in the project's navigation tree.
Edit View
Editing a view from the AT_Views property page displays the Edit View dialog.
1 Select the AT_CVALVE view.
2 Click Edit.
The Edit View dialog enables you to design the view definition. You can customize
descriptive information, join expressions, project tables, fields, and field
properties associated with the current view.
Apr-10
95
AT_VIEWS
Understanding the Edit View Dialog

Creating and modifying views are one of the key features of Bentley software.
The views contained within Project Administrator are known as P&ID views.
These are the views that link the actual P&ID components to the databases.
The Edit View dialog has three tabs: Views, Joins, and Fields.
Views Tab
The Views tab has multiple fields that describe the view.
The following table describes the fields in the View tab.

Form Name
The name of the CATT dialog to be used with this view
Join Name
The name of a join that multiple views can belong to. For example the
Equipment join contains all of the AT_EQXXX views. Therefore if you make a
change in one of these views, it could affect all of the views within that join
name.
Tag Type
The name of the tag type of the component that uses this view.
Show only
records of this
tag_type
Controls the display of tags (as selected in the Tag Type list) to display in the
current view.
Default View
If set, makes the view the default for the tag type.
96
Apr-10
AT_VIEWS
System View
If set, makes this a view that cannot be deleted because it is used within the
code.
Setup Field
Security
Opens the following dialog and allows each field to be selected for security:
Joins Tab
The Joins tab has multiple sections for completing the tasks involved in making or
modifying a view.
The following table describes the fields in the Joins tab.

Window
The Window shows the parent table with each of its children. Each child
table can also have children of its own.
Join Expression
The Join Expression group box is the interface an administrator would use to
define the relationship between two tables.
The parent and child lists define the fields used to relate the tables together.
The join is either going to be a One to Many Relationship or should be left
blank to indicate a one-to-one relationship.
The Primary Key: the field within the table that has been designated as the
primary key.
Project Tables
Apr-10
Shows the tables that are available within the database structure to be
joined together
97
AT_VIEWS
To use:
1 Select the appropriate parent table from within the window.
2 Add the table which will be joined as a child.
3 Go back to the Join Expression.
4 Enter the field names which will join the tables.
Fields Tab
The Fields tab is used to activate certain fields within the view. Each table can
have fields that are active or non-active.
Window
Shows the join tree which lists all of the tables within the view and their
relationship to each other
Instr_a Fields
This list shows which fields from the selected table are active in the view.
Edit: opens the Edit Field Properties dialog, which provides information
about a field if a field name is used more than once and the field must be
aliased.
Select All: selects all fields in the view.
Clear All: clears all fields in the view.
Field Properties
This group box activates if a field is selected. It shows the field name
description, the Alias (if it has one) and any properties that were created
within the Edit Field Properties dialog.
5 Click Cancel.
The dialog closes.
98
Apr-10
AT_VIEWS
Exercise 1: Create a New View

1 Highlight AT_INST_ in the Common Tag Type View Definitions window.
2 Click New.
3 Set From current View AT_INST_.

4 Click OK.
5 Type AT_INST_XMTR in the Name field.
6 Type Instrument Transmitter View in the Description field.
7 Click OK.
Exercise 2: Edit the New AT_INSTR_XMTR View

1 Select the newly-created AT_INST_XMTR view at the bottom of the list.
2 Click Edit.
3 Select the Joins tab.
4 Highlight Instr_a.
5 In the Project Tables group box, scroll down and highlight the Loop table.
6 Click Add.
7 Select Loop_ID from Instr_a Field in the Join Expression group box.
Apr-10
99
AT_VIEWS
8 Select Keytag from Loop Field.

10 Highlight the Loop table.
11 Check the Service field in the Loop Fields list.
12 Click Save.
13 Close the view.
The Warning dialog appears but is not of any concern.
14 Click OK.
You will now re-edit the AT_INST_XMTR view.
16 Highlight the Loop table.
17 Highlight Service.
18 Click Edit.
19 Type Loop Service in the Description field.
100
Apr-10
AT_VIEWS
20 Type LOOP SERVICE in the Field Alias field.
21 Click OK.
22 Click Save.
Exercise 3: Add Fields to the View

1 Scroll down to find the AT_EQUIP view.
2 Click Edit.
4 Ensure that the Equip table is highlighted.
5 Scroll to the bottom of the fields list.
6 Set Edt and Edp as shown below.
7 Click Save.
8 Click Close.
Project Administrator closes.
Apr-10
101
Tag Types
Tag Types
In this section you will become familiar with tag types. You will learn how the tag
types are used to populate the data tables via the view definitions. You will create
a new tag type and then create the view that is associated with it.
A tag type is analogous to a component class. For example, some projects may
have an overall tag type for equipment, while another project may have separate
tag types for pumps, vessels, exchangers, etc. The decisions involved in
establishing tag types are often determined by tag naming (tag formats) or by
required deliverables like reports. The application is shipped with a standard
selection of tag types, but these can be deleted, modified, or expanded. The Tag
Types option below the Database branch in the navigation tree of Project
Administrator enables you to create, edit and delete the tag number format and
tables from which tab number data is read for the current project.
Copy Tag Type Dialog

To copy a Tag Type in the Project Administrator:
1 Access a project's Database > Tag Types property page.
2 Select a Tag Type from the property page list.
3 Click Copy.
The Copy Tag Type dialog displays, enabling you to create a new tag
numbering format for the current project using an existing Tag Type as a
template.
102
Apr-10
Tag Types
Tag Tab
The Tag tab enables creating a new tag numbering format to be used by the
current project.
Apr-10
Tag Type
The name of the tag type currently selected
Description
Description of the tag type
Tag Code
The combination of fields and delimiters of which the tag is composed
Code Prefix
Used to distinguish fields that may be in multiple tables. For example, if

there is an ETYP and an ITYP field then the code prefix would be either E or I
depending on if the type value is for a piece of equipment or for an
instrument.
Required Fields:
The number of fields in the tag code. This number must match the number
of tag codes for the tag to work in P&ID.
Unique Tag
If set, this tag is to be unique in the project.
Remove data
from database
upon deletion
If set, removes the tag from the database upon deletion in either Data
Manager or P&ID. This field is grayed out unless the Delete tags from
Database option is set to No in the project properties. Checking this box
would then allow this tag type to be deleted and override the project
properties.
Disable Tag
Number field
If set , disables the Tag Number field in the Enter Tag Number dialog for this
tag type. This will force the user to define the tag number in the individual
fields provided for that tag type in the Enter Tag Number dialog. This option
is provided to support clients that do not use delimiters (e.g., hyphen,
underscore, etc.) in their tag numbers, and have no other method to define
the separation between the tag fields (specific length, alpha or numeric
format, etc.).
Tag Codes and

Delimiters
Shows the fields and delimiters that are available to build a tag code.
103
Tag Types
Tables Tab
The Tables tab assigns the database links to be used by a new tag numbering
format. The following table describes the fields in the Tables tab:
Tag Register
Selects the table where the current tag number format is to be stored from
this list
Source Table
Selects the source table to which the current tag type is to be linked from
this list
Supplemental
Tables
Enter the name of any supplemental table(s) into which data will be stored
when using the new tag type in this field. This field requires that commas be
used for multiple tables, and no spaces should be used (i.e.,
FTDATA,FVDATA).
Link Table
Selects the table to which the current tag type is to be linked from this list
Pick Table
Enables the display of pre-defined values to assist in the building of a tag

using the current tag number format. The pick tables are stored in the
Schema.mdb. For example, the eqp_pick table contains the values E, P, V
and X for the field ETYP. So during the creation of the tag, these values are
available from within the TYP list of the tag dialog.
Tag Group
Associates the current tag type to a group by typing the name of the tag
group in this field.
104
Apr-10
Tag Types
To use the Tables tab:

1 Select the appropriate list entries.
2 Click OK.
The new tag type is saved.
3 Click Cancel to exit the dialog without saving the new tag type.
Tag Codes Button

The Tag Codes button opens the Edit Tag Format dialog shown below. This
enables you to create custom fields and delimiters to be used in defining a
custom tag number format.
Fields Tab
Apr-10
105
Tag Types
The Fields tab enables you to create, edit, and delete field values which can be
used in defining a custom tag number format.
To create a new field value:
1 Type the appropriate values in the Field and Code fields.
2 Click Add.
To change an existing field value:
1 Select the appropriate list entry.
2 Type over the information in the appropriate field.
3 Click Set.
To delete a field value:
2 Click Remove.
Click Close to exit the dialog.
Exercise 1: Add a New Field

1 Select AT_Process from the list of Tag Types.
2 Click Edit.
3 Click Tag Codes
4 Type SERV in the Field: field.
5 Type F in the Code: field..
6 Click Add.
7 Click Close.
106
Apr-10
Tag Types
Delimiters Tab
The Delimiters tab enables you to create, edit, and delete delimiter (separator)
values which can be used in defining a custom tag number format.
To create a new delimiter value:
1 Type the appropriate values in the Delimiter and Code fields.
2 Click Add.
To change an existing delimiter value:
2 Type over the information in the appropriate field.
3 Click Set.
To delete a delimiter value:
2 Click Remove.
Click Close to exit the dialog. The delimiters are described below.
Delimiter
Code
Description
Will break the tag when it finds a hyphen (A-T-N or 100-FT-100)
"
Will break the tag when it finds a backslash (A/T-N or 100/FCV100)
Will break the tag when it finds an underscore

(A_T_N or 100_FCV_100)
'
Apr-10
Will break the tag when it changes from a number to a character

(A'T#N or 35FT100)
107
Tag Types
Will break the tag when it changes from a character to a number

(A'T#N or 35FT100)
1,2,3
Will break the tag after the number of characters. For example, if
the type is FCV and the number is 100345, the tag code T3N will be
FCV100
Note: The codes for delimiters are in lower case, to differentiate them from
field codes.
108
Apr-10
Tag Types
Alternate Tag Codes for Tag Type Dialog
The Alternate Tag Codes for Tag Type dialog enables you to create a new tag
numbering format, which can be used as an alternate for the current tag type.
To access the dialog, click Alternates in either the Copy Tag Type or Edit Tag Type
dialog.
To create a unique alternate tag type:
1 Type the appropriate information in the fields provided, or use the
available list.
2 Click Add to save the new tag type.
To edit an alternate tag type:
1 Select the appropriate tag type from the list.
2 Type the appropriate information in the fields provided, or use the
available lists.
3 Click Update.
To delete an alternate tag type:
1 Select the appropriate tag type from the list.
2 Click Remove.
Note: The user will not be forced to use an alternate tag format. For example,
if an alternate tag format is created with a suffix, it would still be

possible for the user to include the suffix value along with the value in
Apr-10
109
Tag Types
the previous field in the primary tag format. Training is the key for
consistency when options are established.
Description
Assigns a unique description to the alternate tag type in this field.
Tag Code
A list providing pre-defined tag numbering formats. You can also build a
unique tag format in this field by selecting the appropriate values from the
Fields and Delimiters list entries within the Tag Codes and Delimiters group
box.
Required Fields
The total number of fields that must be filled when using the alternate tag
type.
Code Prefix
Used to type any prefix to precede the alternate tag format.
Unique Tag
If set, this tag is to be unique to the project.
Tag Codes and

Delimiters
Provides a list of pre-defined values to be used in building the alternate tag

number format (the value string displays in the Tag Code field).
Exercise 2: Add a New Alternate Tag Code

1 Type Area-Service-Number in the Description: field.
2 Select AREA from the Fields list.
3 Select "-" from the Delimiters list.
4 Select the newly added field SERV from the Fields list.
5 Select "-" from the Delimiters list.
6 Select NUM from the Fields list.
7 Type 3 in the Required Fields field.
8 Click Add.
110
Apr-10
Tag Types
9 Click OK.
Exercise 3: Make the Alternate Tag Code the Default

1 Select the Tag tab in the Copy Tag Type dialog.
2 Select A-F-N in the Tag Code list.
3 Click OK.
The dialog closes.
Exercise 4: Create a New Tag Type

1 Highlight AP_Sample > Database > Tag Types in the navigation tree.
2 Select AT_INST_ from the display of Tag Types.
3 Click Copy.
4 Type AT_INST_XMTR in the Tag Type field.

5 Type Instrument Transmitter Tag in the Description field.
6 Click OK.
Exercise 5: Change the Tag Code

1 Select AT_INST_XMTR.
2 Select Edit.
3 Highlight and remove any data in the Tag Code field.
The items in steps 4-10 below are selected in the Tag Codes and Delimiters
group box.
4 Select AREA from the Fields list.
Apr-10
111
Tag Types
5 Select ' (single quote) from the Delimiters list.

6 Select TYP from the Fields list.
7 Select # (pound sign) from the Delimiters list.
8 Select NUM from the Fields list.
9 Select the - (dash sign) from the Delimiters list.
10 Select SUFFIX from the Fields list.
11 Type 4 in the Required Fields field.
The tag code appears as shown.
12 Select the Tables tab.

Note the table and schema information, but do not change the
information.
13 Click OK.
The tag code changes are saved.
112
Apr-10
Tag Types
Exercise 6: Make a New Pick Table

2 Select Database > Databases.
3 Select SCHEMA.
5 Click Add.
Apr-10
113
Tag Types
6 Click OK.
7 Click Create New.

Microsoft Access opens.
8 Add the following fields and criteria.
VAR
VALUE
DESCRIPT
Data Type
Text
Text
Text
Field Size
10
50
50
Required
Yes
No
No
Allow Zero Length
No
No
No
Indexed
No
No
No
Unicode Compression
Yes
Yes
Yes
IME Mode
No Control
No Control
No Control
IME Sentence Mode
None
None
None
114
Apr-10
Tag Types
9 Close Microsoft Access.

10 Click Yes.
To save.
11 Type Proc_Pick.
12 Click OK.
13 Click No.
The Add Available Tables to Database dialog returns.
14 Select Proc_Pick.
15 Click OK.
The table has now been added to the SCHEMA database tables.
16 Click Edit.
17 Type Process Pick Table in the Description field.
Apr-10
115
Tag Types
18 Set Data Manager, Project Administrator and AutoPLANT P&ID in the

Registered Applications list.
19 Click OK
The applications are registered.
20 Click OK.
21 Click Close.
Exercise 7: Add Data to the Proc_Pick table

1 Browse to C:\AutoPLANT_Admin_Training\AP_Sample\Projdata.
2 Open Schema.mdb in Microsoft Access.
3 Open the Proc_Pick table.
4 Add the data as shown.
5 Close Microsoft Access and save the changes.
Exercise 8: Use the Proc_Pick Table

1 If Project Administrator is not already open, select Bentley > Plant V8i >
Project Tools > Project Administrator from the Windows Start menu.
2 Select Database > Tag Types.
3 Scroll down and select AT_PROCESS.
4 Click Edit.
116
Apr-10
Tag Types
5 Select the Tables tab.

6 Select Proc_Pick from the Pick Table list.
7 Click OK.
A new process is placed, and the Tag dialog provides the following list.
Apr-10
117
CATT Dialogs
CATT Dialogs
In this lesson you will learn to edit the CATT dialogs. Many companies require
database fields on the CATT dialogs that Data Manager does not provide out-ofthe-box. This lesson will introduce you to the procedure to modify the dialogs to
meet your needs.
Exercise 1: Edit the Visual Basic Dialogs

Note: You will need Microsoft Visual Basic ver. 5.0 or 6.0 Professional Edition
to customize the dialogs.

1 Create a new folder in the C:\Program Files\Bentley\Plant V8i\P&ID
directory called Propdlgs.
2 Locate the Propdlgs.zip file in the \P&ID directory.
3 Unzip the file into the new Propdlgs directory.
4 Copy the RebisComponentDialogs.vbp.
5 Rename it RebisComponentDialogs-org.vbp.
This will give you a working backup of the original file.
6 Start Visual Basic.
7 Select the Existing tab.
8 Browse to the file C:\Program Files\Bentley\Plant

V8i\P&ID\Propdlgs\RebisComponentDialogs.vbp.
9 Click Open.
118
Apr-10
CATT Dialogs
Exercise 2: Open the Form

1 In the Project window, double-click on the Forms folder.
All the Visual Basic forms available for P&I Workgroups display.
2 Scroll down the list until you find the form AT_EqPmp.
3 Double-click.
The Pump Data form opens in the design environment.
Apr-10
119
CATT Dialogs
Exercise 3: Modify the Form

1 Click on the very top of the form to activate the overall grip points.
2 Stretch the entire dialog downwards as shown below to add space to the
bottom of the form.
3 Highlight the three command buttons OK, Cancel, and Help.

4 Drag them towards the bottom of the dialog.
5 Select the Pump Data tab.
6 Grab a grip point and drag down to make space for two new text boxes.
Your form should now look like the one in the following figure.
120
Apr-10
CATT Dialogs
7 Select the Text Box on the General toolbar shown below.
8 Click and drag Text Box under the Manufacturer field.

A new text box called Text1 is created.
9 Select Text Box again.
10 Click and drag Text Box under the Model No. field.
A new text box called Text is created.
11 Select Label on the General toolbar.
12 Click and drag to the left of the first text box.
By default it will be called Label23.
13 Select Label on the General toolbar again.
14 Click and drag to the left of the second text box.
By default it will be called Label24.
15 Select Label23.
Label23 is highlighted.
16 In the Properties dialog scroll to the Caption section.
17 Change the text to Design Press.
18 Repeat this for Label24 except enter the Caption text Design Temp.
19 Select the text box Text1.

20 In the Properties dialog, select the (Name) field.
21 Change the name to EDP.
22 Scroll down to the Text field.
Apr-10
121
CATT Dialogs
23 Delete the value so that the text box is blank.

24 Repeat these steps for text box Text2 except enter EDT for the (Name).
The form should now look like the one in the following figure.
The (Name) value has to match the name of the field we added to the table
EQUIP in the earlier exercise. Therefore any data typed into this text box will
be written to this field.
Now you must change the Tab Index value for the text boxes. The Tab Index is
the order in which the text boxes and buttons are made active when selecting
the Tab key.
25 Select the Manufacturer text box.
26 In the Properties dialog scroll down to the Tab Index field.
It should read 10.
27 Select the Design Press text box.
28 Change the Tab Index value to 11.
29 Select the Design Temp text box.
30 Change the Tab Index value to 18.
The re-numbering propagates through the entire form.
122
Apr-10
CATT Dialogs
Exercise 4: Save the File

1 Click Save.
You now need to make the dll that will be copied to our project.
2 Select File > Make Rebcompdlgs.dll.
Visual Basic will now compile and write the new DLL.
3 Make sure that the new DLL is written into the C:\Program
Files\Bentley\Plant V8i\P&ID\Propdlgs\ folder.
The status bar at the top of the Visual Basic window displays the progress
of the compiling DLL.
4 Close Visual Basic.
5 Save the changes.
6 Copy the file REBCOMPDLGS.DLL from C:\Program Files\Bentley\Plant
V8i\P&ID\Propdlgs\ to the ...\STANDARDS\ directory for your project.
7 From the Windows Start menu, select Programs > Bentley > Plant V8i >
Data Manager.
8 Open the EQUIPMENT LIST view.
9 Add a new filter to the project.
10 Select Tag Properties.
You can now add Design Pressure and Design Temperature data to the
filter.
11 Open a P&ID.
12 Insert a pump using the same tag number.
13 CATT on the filter and see the Design Pressure and Design Temperature
data from the P&ID.
14 Select the Tag Number field in the CATT dialog.
15 Tab through the fields to make sure that the Tab Index is correct for the
dialog.
Exercise 5: Make a New Form

1 Close Data Manager.
2 Start Microsoft Visual Basic.
3 Open the Visual Basic Project RebisComponentDialogs.vbp that is
residing in C:\Program Files\Bentley\Plant V8i\P&ID\Propdlgs\.
Apr-10
123
CATT Dialogs
4 Expand the Forms folder in the Project Window.

5 Double-click on the form AT_Inst_.
To create the new form you need to perform a 'save as' on this form.
6 Select File > Save Instrument.frm As.
7 Name the new form Instrument_XMTR.frm.
8 Save it into the folder C:\Program Files\Bentley\Plant
V8i\P&ID\Propdlgs.
9 From the Properties window change the Name for this new form from
AT_Inst_ to AT_Inst_XMTR.
10 Change the Caption property from Instrument Data to Transmitter Data.
The new form AT_Inst_XMTR is now added to the Visual Basic project.
However, the original form AT_Inst_ has been removed by the Saveas
command.
Before you continue you should add the Instrument form back into the
project.
11 In the Project window right-click on any form.
12 From the pop-up menu select Add > Add File
13 Select the Existing tab.
14 Select Instrument.frm.
15 Click Open.
The Instrument form is added back into the project.
124
Apr-10
CATT Dialogs
To enable the new transmitter form AT_Inst_XMTR to work correctly you

must now edit the Class Module ComponentDialogs and also the Module
CattUtil.
16 From the Project window close the Forms folder.
17 Expand the Modules folder.
18 Double-click on the Module CattUtil(catutil.bas).
CattUtil(catutil.bas) opens in the main VB code window.
19 Scroll down in the RebisComponentDialogs - CattUtil (Code) window until

you find the section shown below.
20 Copy and paste the following lines:

Case Is = "AT_Inst_"
Apr-10
125
CATT Dialogs
Set frmCurrentForm = AT_Inst_
21 Change them to:

Case Is = "AT_Inst_XMTR"
Set frmCurrentForm = AT_Inst_XMTR
The modified section should look like this. Note case sensitivity applies.
22 Close the RebisComponentDialogs - CattUtil (Code) window.

23 Expand the Class Modules folder from the Property window.
24 Double-click on ComponentDialogs (ComponentDialogs.cls).
This will now open in a new code window.
25 Modify the Public Function LoadAllForms() section.
26 Copy the line Load At_Inst_ and paste it back in.
27 Modify the line to read At_Inst_XMTR as shown below.
126
Apr-10
CATT Dialogs
All the modifications to the Visual Basic project are now complete.
28 Click Save.
To apply these changes to your project you must re-create the
RebisComponentDialogs.dll.
29 Select File > Make RebCompDlgs.dll.
The Make Project dialog opens.
30 Ensure that you have browsed the folder C:\Program Files\Bentley\Plant
V8i\P&ID\.
31 Click OK.
You will get a warning that this file already exists and asking if you want to
replace the existing file.
32 Click Yes.
The DLL is compiled.
33 Close Visual Basic.
34 Click Yes.
The Visual Basic Project is saved.
35 Copy the newly created DLL into
C:\AutoPLANT_Admin_Training\AP_Sample\Standards.
36 Open Data Manager.
37 Select Tag Properties > Information for a transmitter tag.
Apr-10
127
Mapping 2D and 3D Classes
Class Mappings: a tree view listing of the Equipment and Piping

mappings between 2D and 3D classes. The mapping information
displayed is read from EQUIPCLASSMAP and BASECLASSMAP,
respectively. You have the option to add or remove any mappings
using the corresponding buttons.
Field Mapping Properties: a flex grid view that displays mappings

between 2D and 3D fields, as stored in the FIELDMAP2D3D table. The
user will have the option to add new mappings and update existing
ones.
Tag Type Mapping: a read-only view of all of the tag_type mappings in

Plant Design and P&ID.
Class Mapping
The 2D to 3D mapping tables located in the project database are a non-user
interface part of the system in which users would be interested. These tables
allow the user to customize the mapping of 2D items to 3D items according to
his/her specific needs. An interface is provided in the Project Administrator
application to manage these mapping definitions.
128
Apr-10
Tag Type Mapping

The tag types are read from the tag_types table in Schema.mdb, which can be
found under %PROJECT_ROOT%\Projdata. Tags defined with the cod_prefix 'V', 'I'
or 'P' are displayed under the Piping node. Those with cod_prefix 'E' and 'N' are
displayed under Equipment.
Classes
The PDW class information under the Piping node is read from BASECLASSMAP
table while the Equipment class information is read from the EQUIPCLASSMAP
table. Both tables are located in the %PROJECT_ROOT\Projdata\Projdata.mdb.
Apr-10
129
BASECLASSMAP Table
EQUIPCLASSMAP Table
The P&ID classes are read from settings.dbf (and dinset.dbf, in case of Metric and
Mixed Metric projects).
Add or Remove Mappings

The user has the option to add or remove any mappings using the corresponding
buttons.
To add a new mapping, click Add:
130
Apr-10
This allows you to map any P&ID class to a PDW class. The P&ID classes can be
filtered by Tag Type while the PDW classes can be filtered by Class Module.
The Remove button removes the selected mapping from the database. You are
only able to remove one mapping at a time. Because of this, Remove is disabled
when a tag type or the grouped class is selected.
Exercise 1: Piping Class Mapping

1 In the Class Mappings page, expand the Piping node.
2 Click Add.
In this case, we are adding a mapping between PID class CANG and PDW class
AT_VALVE_CNTL.
3 Select AT_VALVE in PID classes.
Apr-10
131
4 Highlight CANG.
5 Select Base Piping Module in PDW Classes.
6 Select AT_VALVE_CNTL.
7 Click Add.
The mapping definition is created.
8 Click Cancel.
The dialog closes.
9 Set P&ID Classes in the Group By section.
10 Expand CANG.
You will see the addition of the 3D Class AT_VALVE_CNTL mapped to the
2D Class CANG.
11 Enable PDW Classes in the Group By section.

12 Expand AT_VALVE_CNTL.
You will see the addition of the 2D Class CANG mapped to the 3D Class
AT_VALVE_CNTL.
Note: The mappings need to be added in this order (i.e., define the Tag_Type
of the 3D class first and then define mapping between the 2D and 3D
class).
132
Apr-10
Exercise 2: Equipment Class Mapping

1 Set P&ID Classes.
2 In the Class Mappings page, expand the Equipment node.
3 Click Add.
4 Select the PID class CONV.

5 Select VERTV.
6 Click Add.
The mapping definition is created and the dialog closes.
7 Expand CONV.
Apr-10
133
You will see the addition of the 3D Class VERTV mapped to the 2D Class
CONV.
8 Set PDW Classes in the Group By section.

9 Expand VERTV.
You will see the addition of the 2D Class CONV mapped to the 3D Class
VERTV.
The navigation tree is updated to include the new mapping.
Note: The mappings need to be added in this order (i.e., define the Tag_Type
of the 3D class first and then define mapping between the 2D and 3D
class).
134
Apr-10
Field Mapping Properties

This property page contains a flex grid view that displays mappings between 2D
and 3D fields stored in the FIELDMAP2D3D table. You can add new mappings and
update or remove existing ones.
The Add button displays the following dialog to add a new mapping:
The 2D Field list and 3D Field list is populated according to the class category
chosen.
The 2D Field list is populated from Schema.RebisDict.
The 3D Field list is populated according to:
Apr-10
135
Fields of the 3D tables (i.e. Equip3D for class category 'Equipment'

etc.)
System objects defined in the ObjectType table
Component Preferences from CompPref.ini where the Resulttype is

string.
The Remove button removes the selected mapping from the database.
The Update button gives you the option to update the selected entry - in this case
the category, P&ID field and the PDW fields cannot be modified since they form
the primary key for the record.
Tag Type Mapping

This page provides the user with a view of all P&ID and PDW classes along with
their description and tag_types.
136
Apr-10
This data is read up from the settings.dbf file for P&ID classes and from
ValueMap2d3d table in Projdata for PDW classes.
The Relationship Manager is an AutoPLANT 3D Plant Design application. This tool
is only available if the AutoPLANT 3D applications are installed. It cannot be used
to work with the Process & Instrumentation applications. The Relationship
Manager provides a central location for an administrator to manage AutoPLANT
3D relationship values (e.g., LineNumber, Unit, Area, Service, Spool, and
Document).
The workflow for the AutoPLANT 3D application is designed for a Project
Administrator to create all of the relationship values for a project or configuration
at the start of the project outside of AutoCAD. This workflow gives an
administrator control over the values used for these properties on a project.
Designers can then select from the provided list of values to create models.
Note: The capability to add new relationship values is also available within
AutoPLANT 3D applications through the Component Preferences

control. This option is provided as an alternate workflow.
Administrators can make this capability available on a project basis by
Apr-10
137
setting the Read-only Relationships option on the Relationship

properties page in the Project Administrator.
The Relationship Manager is also used to delete, rename, add, import, and export
documents in a project environment. Deleting a document deletes its associated
component records and relationships from the project.
138
Apr-10
Modifying Fields and Views in the SQL Project

In this section you will learn how to modify and create new fields for the SQL
Project. You will also customize the view to include the newly-created field.
Note: These exercises are for demonstration purposes only. SQL Server tables
are also editable from within Project Administrator.
Exercise 1: Modify Existing Fields in the Data Tables

1 From the windows Start menu, select Programs > Microsoft SQL Server >
Server Manager Studio.
The Server Manager Studio opens to the Console Root as shown below.
2 Expand Microsoft SQL Server.

3 Expand SQL Server Group.
4 Expand the Local (or Windows NT depending on your setup) server group,
Databases.
Apr-10
139
5 Expand PIW.
6 Double-click on the Tables node.

All of the tables in the project are displayed.
7 Scroll down the tables until you find Instr.

8 Right-click on Instr.
140
Apr-10
9 Select Modify from the context menu.
The Instr table opens in the Design view.

10 Scroll down until you find the Descript field.
11 Change the Length field from 40 to 100.

12 Close the table.
13 Click Yes.
The changes to the table are saved.
Apr-10
141
Exercise 2: Add a New Field to the INSTR Table

1 Highlight the Instr table.
2 Select Modify.
3 Scroll to the bottom of the Column Name list.
4 Place your cursor in the first blank row.
5 Type MYFIELD in the Column Name.
6 Set the Data Type as varchar.
7 Set the Length as 50 as shown below.
8 Close the table.

9 Click Yes.
The changes in the table are saved.
142
Apr-10
New Field Restrictions and Definitions

There are a few restrictions when creating your new field. They are listed below
as a reference.
Column Name
The Column Name or Field cannot contain the words ID or TAG. These are system
field identifiers that are used by the software. Using these fields will result in
read-only fields within the views.
Data Types
The software has the capacity to use several data types when creating a new
field. Listed in the table below are each data type and whether its use is
recommended.
Column Name
Recommended
Description
Char
YES
This data type can be used for such items as cost codes
where the data contained within the field is of a specific
length. The data base will allocate memory to the field
whether the field is populated or not.
Varchar/
Varchar2
YES
This data type can be used for any item. The data base
will only allocate memory to the actual field size that is
populated.
Invarchar/
Invarchar2
YES
This data type is used for Unicode fields. An example

would be foreign languages such as Japanese or Russian
where the characters need to be 2 bits instead of 1 bit.
Blobs/Globs
NO
These data types are not recommended.
Binary/
Varbinary
NO
These data types are not recommended.
Ntext
NO
This data type is not recommended.
Allow Nulls
If left unchecked the field must be populated or the record will not be saved. The
application does not allow Nulls for items such as KEYTAG and TAG fields.
Close Enterprise Manager.
Apr-10
143
Exercise 3: Modify an SQL View

There are several words that SQL has reserved for their use. You can find a list
at the following link http://msdn.microsoft.com/en-us/library/
bb208875.aspx.
Data Manager.
2 Logon as Supervisor if not already logged in.
3 Expand the Views node.
4 Close the Equipment List.
5 Select the Process Instrument List.
6 Right-click.
7 Select Edit.
8 Click Design.
The Design View - Process Instrument List dialog opens.

9 Verify that the INSTR table is highlighted in the Source Tables list.
144
Apr-10
10 Scroll down in the Fields window until you find the new field MYFIELD as
shown below.
11 Click the ADD arrow.

MYFIELD is added to the Selected Fields window.
12 Click OK.
13 Refresh the Process Instrument List.
14 Scroll to the far right.

Your field has been added to the view and is available to be populated
with data.
Apr-10
145
Module Review
Module Review
Questions
1 Name the three different types of 2D to 3D mapping.
2 How do you make a backup of a project?
3 What is used to separate the fields of a custom tag type?
4 What are the AT_Views?
5 What third-party software is required to modify the CATT dialogs?
6 What is the name of the file which contains the property dialog
definitions?
Answers
7 The three types of mapping available are: Class, Type and Field.
8 To make a backup of a project create an Archive folder using Project
Administrator.
9 A delimiter is used to separate the fields of a custom tag.
10 The AT_Views are a collection of data fields.
11 Microsoft Visual Basic ver. 5.0 or 6.0 Professional Edition is required to
make changes to the CATT dialogs.
12 The RebisComponentDialogs.vbp file contains the property dialog
definitions.
146
Apr-10
Managing Projects
Module Overview
In this section you will study in-depth the ini files associated with the project. You
will learn how to set the user and group security.
Module Objectives
Apr-10
Understand the Project.ini files.
Set the user privileges.
147
Managing Projects
Interpreting the Project.ini files

The SQL Server Project.ini File
A generic project.ini file can be found in Appendix A of this manual. Review the
file. The sections that we are interested in are shown below. The sections not
covered here are the same no matter what database the project is created with.
The [PROVIDERS] section shows that the projdata is in an SQLOLEDB format.
[PROVIDERS]
Projdata=SQLOLEDB.1
Schema=Microsoft.Jet.OLEDB.4.0
The [DATA SOURCES] section is not used by the 2D applications, it is provided for
the 3D applications.
[DATA SOURCES]
Projdata =DRIVER={SQL Server};SERVER=%s;UID=%s;PWD=%s;DATABASE=%s
Schema
ModelDB
SpecDB
Report
The [DATABASES] section provides the connectivity information for the specified
data source location. For example, a project will contain multiple databases. For
each defined database, a connection string must be provided. This section should
not be altered, unless the data has to be moved from one location to another.
[DATABASES]
Projdata=Password=bsi;Persist Security Info=True;User
ID=PIW;Initial Catalog=PIW;Data Source=SHEPG15214COV
;For SQL Server
Schema=%Projpath%\PROJDATA\SCHEMA.MDB
Managing Projects
148
Apr-10
The Oracle Project.ini File

A generic project.ini file can be found in Appendix A of this manual. Review the
file. The sections that we are interested in are shown below. The sections not
covered here are the same no matter what database the project is created with.
The [PROVIDERS] section shows that the projdata is in an ORAOLEDB.Oracle.1
format.
[PROVIDERS]
Projdata=ORAOLEDB.Oracle.1
The [DATA SOURCES] section is not used by the 2D applications, it is provided for
the 3D applications.
[DATA SOURCES]
Projdata =DRIVER={Oracle ODBC Driver};DBQ=%s;UID=%s;PWD=%s
Schema
ModelDB
SpecDB
Report
The [DATABASES] section provides the connectivity information for the specified
data source location. For example, a project will contain multiple databases. For
each defined database, a connection string must be provided. This section should
not be altered, unless the data has to be moved from one location to another.
[DATABASES]
Projdata=Password=bbsi;Persist Security Info=True;User ID=PIW;Data
Source=plantdev.bentley.com
;For SQL Server
Schema=%Projpath%\PROJDATA\SCHEMA.MDB
Apr-10
149
Managing Projects
User Configurations
User Configurations
Exercise 1: Add a User to the Current Project

Administrator from your Windows Start menu.
2 Expand the C:\AutoPLANT_Admin_Training folder.
4 Expand Project > Main.
5 Select User Configuration in the Security group.
6 Click Add.
The Create User dialog displays.
7 Type Review in the Login Name field.
8 Type Reviewers in the User Name field.
9 Select Guest in the Member of Group list.

10 Type the new user Login password, check, in the Password field.
11 Duplicate this field entry in the Confirm Password field.
12 Click OK.
The new user is added to the current project.
Managing Projects
150
Apr-10
User Configurations
Exercise 2: Remove a User from the Current Project

1 Select Admin from the list.
2 Click Remove.
The User dialog is displayed.
3 Click Yes to confirm deletion.
Exercise 3: Edit User Access Privileges

1 Select Review from the list.
2 Click Edit.
The Edit User dialog displays.
3 Type Checker in the Login Name field.
4 Click OK.
The changes are saved.
5 Click Close.
Exercise 4: Add a Group to the Current Project

1 Select User Configuration.
2 Select the Groups tab.
Apr-10
151
Managing Projects
User Configurations
3 Click Add.
4 Type Accounting in the Group Name field.

5 Clear all but Engineering in the Function window.
6 Clear all but Administration in the Level window.
7 Select Read Only from the Group Default Access Type.
8 Click OK.
The new group is added to the current project.
Exercise 5: Remove a Group from the Current Project

1 Select Operators from the list.
2 Click Remove.
The User dialog displays.
3 Click Yes.
Operators is deleted.
Managing Projects
152
Apr-10
User Configurations
Exercise 6: Edit Group Access Privileges

1 Select Designers from the list.
2 Click Edit.
The Edit Group dialog displays.
3 Type Drafters in the Group Name field.
4 Select Instrumentation and Piping in the Function list.
5 Select Designer and Draftsman in the Level list.
6 Select User from the Group Default Access Type list.
7 Click OK.
8 Click Close.
Project Administrator is returned.
Exercise 7: Create a Group-Level Access Category

1 Select User Configuration.
The User Configuration dialog displays.
2 Select the Advanced tab.
3 Type Finance in an empty cell below the Function column heading.
4 Type Accountant in the adjacent cell below the Level column heading.
5 Click Update..
Apr-10
153
Managing Projects
User Configurations
Exercise 8: Edit a Group-Level Access Category

1 Type over Finance with Accounting.
2 Click Update.
Exercise 9: Remove a Group-Level Access Category

1 Delete Accounting from the Function column.
2 Click Update.
3 Click Close.
Managing Projects
154
Apr-10
Application Security
Application Security
Exercise 1: Set Application Security

1 Click Application Security.
2 Select Data Manager from the Application list if not already selected.
3 Select Create/Edit/Delete Tags from the Program Actions window.
4 Set PIPING in the Function window.
5 Clear MAINTENANCE in the Level window.
6 Click OK.
Note: The result of this change is that every function and level that was
checked enables those users to create, edit or delete tags. If a function

or level was not enabled, those users will not be able to create, edit or
delete tags.
Apr-10
155
Managing Projects
Assigning User Rights to CATT dialogs
Exercise 1: Field Access Configuration for AT_Views

1 Expand the project nodes and navigate to AP_Sample > Database > AT_
Views.
2 Select the view AT_INST_.
3 Click Edit.
The Edit View dialog opens.
4 Click Setup Field Security.
5 Select INSTR_A.INST_DESC, INSTR_A.MANUFACT and INSTR_A.MODEL.

6 Set INSTRUMENTATION in the Function window.
Managing Projects
156
Apr-10
7 Set DESIGNER in the Level window.
8 Select INSTR_A.ISERV and INSTR_A.REQ_NO.

9 Set INSTRUMENTATION in the Function window.
10 Set ENGINEER in the Level window.
11 Click OK.
12 Click Save.
Apr-10
157
Managing Projects
The following dialog is available to the Instrument Designer.
The following dialog is available to the Instrument Engineer.
User access rights have now been assigned to both Data Manager and
P&ID views to prevent the wrong user editing the project data.
Managing Projects
158
Apr-10
Module Review
Module Review
Questions
1 Can you restrict some users from being able to edit data in your project?
2 Which section of the Project.ini file contains the database information?
3 Is there a different Project.ini file for each database type?
Answers
1 Yes, you can assign individuals to user groups which do not have editing
capabilities in the project.
2 The [Providers] section contains the type of database being used in the
project.
3 No, there is only one Project.ini file. The information contained in the
[Providers] section changes depending on the database type being used.
Apr-10
159
Managing Projects
Module Review
Managing Projects
160
Apr-10
Examining the Project

Databases
Module Overview
In this chapter you will examine the project database tables. You will learn how
the tables are related. You will learn the function of the field Keytag and study the
Schema tables.
Module Objectives
Apr-10
View the data tables.
Add a component.
Track the component through the tables.
Open the schema tables.
Locate a table in the database.
Copy a SQL string from an existing view.
161
Viewing the Projdata Tables

In this section you will view the project tables and learn how they relate to the
project. SQL Server projects will contain an .adp file instead of an .mdb file. Oracle
projects will not have either file in the Projdata directory because their tables are
located on the Oracle server and must be manipulated using Oracle tools such as
Enterprise Manager.
.MDB files: MS ACCESS file type that contains data tables, queries and
reports.
.ADP files: MS ACCESS file type that contains queries and reports, but
connects to a SQL Server server for its data tables.
Exercise 1: View the Data Tables

1 In Windows Explorer, browse to
C:\AutoPLANT_Admin_Training\AP_Sample\Projdata.
This directory contains the PROJDATA.mdb, the Project.mdb and the
Schema.mdb..
Note: The Flows.mdb was added in a previous chapter and is not part of the
project databases.
You will first examine the PROJDATA.mdb file.
2 Open MS Access.
162
Apr-10
3 Select File > Open.

5 Select PROJDATA.mdb.
6 Click Open.
7 Select the TAG_REG table.
8 Double-click.
Apr-10
163
The TAG_REG table opens indicating that no data has been added to the
project.
Specialized Data Tables

Within the database there are several specialized tables that do not hold data,
but contain the fields necessary to link the data tables together.
Key_Link
The KEY_LINK table is the most important of the P&ID tables, holding all of the
KEYTAGS generated by the software and its complementary LINK_ID. When
trouble-shooting a corrupt project, this table is the first to be opened to start
tracking the broken links.
164
Apr-10
XXXX_Lnk
There are multiple link tables within the database that contain system fields that
cross-reference data to other data tables. The EQP_LNK table, for example, is
used to link all of the equipment data to its corresponding drawing.
Last_ID
The LAST_ID table is used as a counter. It contains a counter for the project's
Keytags, the unique identifier defined for every component in the project as well
as the last-used values for the linking fields. The software reads this table and
assigns the next available values to the entity being added. The DS_ID and
PROP_ID KEY_TYPES contain values used by the fully-mapped datasheets installed
with every project.
Apr-10
165
Note: The records will be automatically added to the LAST_ID table as
different key types are needed. If your project has no mapped

datasheets, for example, you would not have the records shown above.
Extended Data Tables

There is a relationship between the Last_ID table and the EXTDATAPROP table the PROP_ID and DS_ID fields are contained within both. The Extended Data
Tables are primary used for Data Sheets.
Important Fields within the Data Tables

In this section you will become familiar with some of the important fields within
the data tables. The fields are either hidden within the interface or are read-only.
If the tables are opened outside of the Bentley environment, they are unprotected and it needs to be noted that they should not be modified.
PROJ_ID
The PROJ_ID field is added to the data tables in either the SQL Server or
Oracle environment if the Multi-Project Mode had been selected during the
creation of the project.
Warning: It is not recommended that 2D projects be created in Multi-Project
Mode.
KEYTAG
The KEYTAG field is a Bentley system field which is imperative in linking the
multiple data tables together. This field is populated by the software and
should not be altered in any way.
XXXX_ID
There are multiple _ID fields contained within the data tables which are
used for linking the tables together. These fields are populated by the
software and should not be altered in any way.
166
Apr-10
ER Diagram
The Bentley suite of applications is built on relational databases. The Entity
Relationship graphically depicts all of the links between the Projdata tables. The
diagram (Bentley Plant 08.11.05.xx ERD.pdf) is available from C:\Program
Files\Bentley\Plant V8i\Help.
Apr-10
167
1 Open the file and zoom in to the Valve table.
When a valve is placed on a drawing, the tag is written to the TAG_REG table and
linked via the keytag back to the VALVE table. This is illustrated by the arrow
leading from the VALVE.Keytag to the TAG_REG.Keytag. The keytag from the
VALVE table is also linked to the RUN_CONN table providing the link between the
valve and the process run information.
2 Scroll down to the INSTR table.
Note: Although the keytag field is connected to several tables, it is not
connected to the TAG_REG table. Therefore the INSTR table contains all
of the instrument tags.
3 Follow the arrows from the Manufacturer and Model fields of the INSTR
table to the INSTYPE table.
This link makes it possible to create a list of available manufacturers and models
based on the type of instrument being used.
168
Apr-10
The following exercises will illustrate the two conditions just explained.
Exercise 2: Add an Instrument to the Database

Data Manager.
Since the AP_Sample was selected in the previous exercise as the startup
project, Data Manager will open to the correct project.
3 Double-click on Process Instrument List.
The view opens but does not contain any data.
4 Select Tools > New Tag.
The Select Type dialog will open requesting that you choose a tag type for
your instrument.
5 Select AT_INST_.
6 Click OK.
7 Type 100-FT-100 in the Tag Number field.
Apr-10
169
8 Click OK.
The Process Instrument List opens containing the new instrument.
Exercise 3: Add a Valve to the Database

1 Close the Process Instrument List.
2 Open the Valve List.
The New Tag dialog opens.
4 Type V-1 in the Tag Number field.
170
Apr-10
5 Click OK.
The Valve List opens containing the new valve.

Exercise 4: Trace the Components in the Data Tables

1 Open MS Access.
3 Select PROJDATA.mdb.
4 Click Open.
Apr-10
171
The Last_ID table opens. Here you can see if the counters have been
changed.
As seen in the above figure, the KEYTAG counter has gone up by two. The
KEY_ID is 0000000002; this will be important as we track the instrument.
5 Close the Last_ID table.
6 Open the Instr table.
Note: One record has been added to the Instr table, the instrument added
through Data Manager. The KEYTAG value indicates that it was the first
entity added.
The Instr table performs the same function for instruments that the TAG_REG
table does for every other component. Therefore, to track any component
other than an instrument, the Tag_Reg table must be included.
172
Apr-10
Exercise 5: Trace a Valve Component

1 Open the TAG_REG table.
A record has been added. According to the KEYTAG it is the second entity
in the project
2 Close the TAG_REG table.
3 Open the Valve table.
The valve was recorded in two locations using the KEYTAG field as a link.
With the linkage in place, the TAG_REG table will only hold the tagging
information and the Valve table will hold all of the valve data.
Apr-10
173
Viewing the Schema Tables

In this section you will learn how these tables are used as the backbone of the
project.
Exercise 1: Open the Schema Tables

1 In Windows Explorer, browse to
C:\AutoPLANT_Admin_Training\AP_Sample\Projdata.
2 Open MS Access.
5 Select Schema.mdb.
6 Click Open.
XXX_PICK Tables
These tables are used for the dialog lists.
174
Apr-10
RebisDict Table
The RebisDict table contains the definitions of the fields used in each of the
system AT_XXX views. The table also shows any aliases of field names as well as
the rights level set on each field.
RebisJoin Table
The items in the RebisJoin table allow component types to be linked to like/
different component types. It also allows for grouping of items and Parent/Child
associations. These views are specific to AutoPLANT P&ID only.
Apr-10
175
RebisObject Table
The RebisObject table stores the report definitions and the application to which it
is registered. The Instrument and drawing template information is also stored
here.
RebisTable Table
The Rebistable table shows all of the tables within the project database, where
they reside and which application they are registered to.
176
Apr-10
RebisView Table
The RebisView table and the RebisDict table work together to define all of the
project views. RebisView contains SQLStrings that are used by all applications.
Tag_code, Tag_type and Tformat Tables

These three tables work together to define tag coding which is the center-piece
of the component tags.
The Tag_code table contains the tag codes for each tag type.
Apr-10
177
The Tag_type table holds the default formats for all of the different tag types.
The Tformat table contains the definitions for the individual tag codes.
178
Apr-10
Exercise 2: Locate a Table

1 Open the RebisTable table in MS Access.
2 Scroll down until you find the INS_LOC table.
Note: The INS_LOC table is found in the Schema database and is registered
only to the P&ID application.

3 Close the RebisTable table.
Exercise 3: Copy an SQL Statement from an Existing View

1 Open the RebisView table.
2 Scroll down until you find the View_Name AT_INST_.
3 Highlight the record.
Apr-10
179
4 Scroll to the right until you reach the SQL_String field.
5 Place your cursor in the SQL_String field for AT_INST_.

6 Press Shift+F2.
The entire text is now available in a Zoom dialog ready to be cut and pasted.
7 Press Ctrl+C to copy.
8 Open Notepad.
180
Apr-10
9 Press Ctrl+V to paste.
10 Select File > Save As.

11 Type SQL.txt in the File Name field.
12 Click Save.
13 Close Notepad.
14 Close the RebisView table.
15 Close MSAccess.
You can now modify and paste this string to create a new view based on the
AT_INST_ view.
Apr-10
181
Viewing Project.mdb
Viewing Project.mdb
In this exercise you will learn how the queries from the Project.mdb are used.
Exercise 1: Open PROJECT.mdb

1 Open MS Access.
4 Select PROJECT.mdb.
5 Click Open.
This database is a repository for views and reports. There are no tables defined
within the database, so these queries and reports cannot be opened directly from
the mdb.
When the I&W or Data Manager applications are opened, the software does the
following:
1 It looks to the Schema.mdb and opens the RebisObject table to determine
which views are assigned to the application being opened.
2 It downloads the views to either the C:\Documents and Settings\All
Users\Application Data\Bentley\Plant V8i\I&W\I&W.mdb or
C:\Documents and Settings\All Users\Application Data\Bentley\Plant
V8i\DataManager\DataManager.mdb.
3 It copies the views from the Project.mdb to the appropriate
DataManager.mdb or I&W.mdb.
182
Apr-10
Module Review
Module Review
Questions
1 What is the unique identified for each tag or component added to the
database?
2 Which database in the Projdata directory contains the definitions of the
views and reports?
3 Are control valves and valves stored in the same table?
4 Does the Tag_Reg table contain the keytags for all components in a
project?
Answers
1 The keytag is a unique identifier assigned to each tag or component.
2 The Schema database contains the tables which hold the definitions of the
views and reports.
3 No, a control valve is considered an instrument and is stored in the INSTR
table while a valve is stored in the VALVE table.
4 No, the Tag_Reg table does not contain any instrument tags. The INSTR
table acts as the tag register for instruments.
Apr-10
183
Module Review
184
Apr-10
Project Utilities
Module Overview
In this chapter you will learn to use the Project Utilities. You will package your
project and then un-package it into a different database type. You will use the
Split/Merge utility to make a child project, and then merge the child back into the
parent project. You will be instructed on how to use the Consistency Checker
Reporter. Finally you will place 2D components into a 3D drawing.
Module Objectives
Apr-10
Upgrade a project.
Package a project.
Split and merge a project.
Run consistency checker.
185
Project Utilities
Upgrading Existing Projects
Exercise 1: Upgrade an Existing Project

2 Expand the C:\Bentley Plant V8i Projects root directory.
4 Select the Integrity Check tab.
Project Utilities
186
Apr-10
5 Select the following options as shown below.
Note: When the Integrity Check is set and a project is selected in Project
Administrator a series of tests will be run on the project. This produces

a report that appears in the Integrity Check section on the right side of
the Project Administrator window. It is always a good idea to review the
Integrity Report before upgrading the project from the Integrity Check
Results.
6 Click Apply.
7 Click OK.
8 Select the Sample_Imperial project in Project Administrator.
The following dialog illustrates the progression of the database check.
The Integrity Check completes.

9 Right-click on the Sample_Imperial project.
Apr-10
187
Project Utilities
10 Select Upgrade > From Integrity Check Results.
The upgrade procedure starts. The Project Database Upgrade dialog

opens, showing the status of the upgrade. During this process the
software compares the current project's database with the BASE project's
database. Any differences found are updated from the BASE project. This
can include items such as missing tables, columns, fields, indexes, etc.
Once the update has finished you can review the Integrity Check Report to
show any outstanding differences. A link to this file is found on the right
side of the Project Administrator window.
Project Utilities
188
Apr-10
11 Click on the link for the IntegrityUpgradeLog.V8il file.

The IntegrityUpgradeLog.V8il file opens, with all major outstanding
differences that could not be changed shown in red. The most likely
reason for this is database constraints. The user must make the suggested
changes manually.
Turning off Integrity Checker.

13 Clear the Enable Integrity Check Engine Globally check box.
14 Clear the Skip Integrity Upgrade Errors check box.
Note: This must be turned off before closing Project Administrator.
Apr-10
189
Project Utilities
Packaging a Project
Packaging a Project
In this section you will learn to package your project to send to another location.
You will also learn to unpack the project using the same format. Finally, you will
take the packaged project and un-package it into a different database format.
Exercise 1: Pack a Project

1 Select Programs > Bentley > Plant V8i > Project Tools > Project Packager
from the Windows Start menu.
2 Set Package Project.

3 Click Next.
4 Click Select Project.
Project Utilities
190
Apr-10
Packaging a Project
5 The following dialog opens showing the project in the current root
directory.
6 Select AP_Sample.
7 Click OK.
The Login dialog may open if the Save Password was not checked in
previous occurrences.
8 Type Supervisor in the password.
9 Click OK.
The Project Packager dialog is populated with the AP_Sample information.
10 Click Next.
The Project Packager is now requesting information for the location of the
packaged project.
Apr-10
191
Project Utilities
Packaging a Project
11 Select browse.
12 Browse to your desktop if you are not already there.

13 Type AP_SampleProject.zip in the File name field.
14 Click Open.
The Project Packager is populated with the location.
Note: If you set the Package the Project for Handover option, the following
dialog displays.
Project Utilities
192
Apr-10
Packaging a Project
Note: Enabling this option will package the project for EPC to Owner project
transfer. The transfer process allows the owner to incorporate new

copies of an external project. It is not intended to synchronize
documents created by the EPC and documents created by the Owner
Operator.
15 Click Next.
The Project Packager confirms that all steps have been taken.
16 Click Next.
The packaging process begins.
The application now begins the process of packaging the project. A series
of dialogs with progress bars will open.
Apr-10
193
Project Utilities
Packaging a Project
Project Package re-opens indicating that the process has been successful.
17 Click Finish.
Exercise 2: Unpack the Project to a Different Root Directory
In this exercise you will unpack the previous project into a different root
directory. The project was created in Access and will be unpackaged into an
MSDE Server database.
Note: If you do not have MSDE installed, please watch the instructor's
demonstration of this exercise.

1 Select Programs > Bentley > Plant V8i > Project Tools > Project Packager
from the Windows Start menu.
The Project Packager wizard opens.
2 Set the UnPackage Project check box.
3 Click Next.
The Project Packager requests the name of the zipped project and its
location.
4 Click browse.
Project Utilities
194
Apr-10
Packaging a Project
5 Navigate to the AP_SampleProject.zip project.
6 Select AP_SampleProject.zip.
7 Click Open.
The Project Packager re-opens with the project path inserted into the
Select package zip file field as shown below.
8 Click browse to Select location.

Note: It should be noted that the project cannot be unpackaged into the same
root directory as the original project. If you want to overwrite or update
Apr-10
195
Project Utilities
Packaging a Project
an existing project, you should select the Select an existing project to

replace option.
9 Select the drive where the new project will be located.

10 Click Make New Folder.
11 Rename the New Folder to Training Projects.
12 Click OK.
Project Packager returns. The new root directory is created, and its
directory location is listed in the Select location field.
13 Click Next.
Project Packager is now ready to un-package your project.
Project Utilities
196
Apr-10
Packaging a Project
14 Click Next.
The project begins to unpack and you are presented with the Project
Database Type dialog requesting you to select the type of database to
unpack the project into.
15 Select Access.
16 Click OK.
Apr-10
197
Project Utilities
Packaging a Project
The project continues to unpack itself into the new database location. When the
process is complete the Project Packager wizard returns to indicate that the
Project was unpackaged successfully.
The AP_Sample project will now be available for use.

17 Browse to C:\Training Projects\AP_Sample\Projdata.
Note: The Projdata database now has an extension of .adp indicating that the
project is in an MSDE format.
Project Utilities
198
Apr-10
Split/Merge Utility
Split/Merge Utility
In this lesson you will split the Training project into a parent and a child. After the
split is complete, you will modify the child project. Finally you will merge the child
project back into the parent project. A new Projdata directory has been provided
for the following exercises.
Exercise 1: Install the Training Project

1 Make sure all AutoPLANT applications are closed.
2 Download the file Training.exe.
3 Save the file to your desktop.
4 Double-click on the file Training.exe.
5 Click Unzip to begin the extraction to the root directory of the C drive
(C:\).
6 Click Close.
8 Select File > Add Root.
The Browse for Folder dialog displays.
Note: Because you cannot create a project root directory under a project
directory, you must select something at the primary root level of the
navigation tree in order for this option to be available in the File menu.
9 In the Browse For Folder directory, select C:\Bentley Training Project.
10 Click OK.
Apr-10
199
Project Utilities
Split/Merge Utility
Exercise 2: Split a Project

1 Select Programs > Bentley > Plant V8i > Project Tools > Split or Merge
Project from the Windows Start menu.
The Split/Merge Project dialog opens so that you can select the
appropriate Parent Project. It will default to the last project that was
opened.
2 Select File > Open Parent Project.

The Open Project dialog displays.
3 Select Bentley Training Project > Training.
4 Click OK.
5 Select Child Projects > Create New Child.
Warning: With SQL or Oracle, the user must have the ability to create a new table; otherwise
an error will appear and the function will be stopped.
Project Utilities
200
Apr-10
Split/Merge Utility
The New Project - Details dialog opens.

6 Type Training_Child in the Project Name field.
7 Click Finish.
8 Click No in the Upgrade Project dialog.
The project begins creating. The progress bar indicates that the parent
and child projects are being compared.
When the comparison stops, the Child Project Synchronization dialog
shows that only the parent project has documents and data.
9 Select the PID-01.

We will now populate the child project with data.
Apr-10
201
Project Utilities
Split/Merge Utility
10 Click Update Child.
The program opens the following dialog indicating that there are
additional documents which were not selected, but are associated to tags
located on the P&ID.
11 Click Select All.

12 Click OK.
Project Utilities
202
Apr-10
Split/Merge Utility
The Child Project Synchronization dialog is now populated with the

documents and tags from both the Parent and Child projects.
13 Click Close.
14 Close the Split/Merge dialog.
Exercise 3: Modify the Child Project

Data Manager.
Data Manager opens the Training project.
2 Open the Equipment List View.
3 Select Tools > Filter > Count Filtered Rows.
Note: There are 53 records in the Equipment List View.
4 Click OK.
The Equipment List View closes.
5 Select File > Open Project.
The child project Training_Child is now present.
6 Highlight Training_Child.
Apr-10
203
Project Utilities
Split/Merge Utility
7 Click OK.
The child project now opens.

8 Select Tools > Filter > Count Filtered Rows.
Note: There are now 29 records in the Equipment List view.
9 Click OK to close.
Exercise 4: Modify the Child Project with an Imported Datasheet

1 Close the My Instrument list.
3 Double-click on the Process Instrument list.
The Process Instrument list opens.
4 Scroll down the list until you find 100-TT-100.
5 Select Applications > Data Sheet Editor.
6 Select File > New.
The Data Sheet Wizard opens.
7 Set Standards if not already set.
8 Click Next.
9 Select f1_flow_element_pressure_type.
10 Click Next.
11 Type 100TT100 in the Document Number field.
12 Click Next.
13 Highlight 100-TT-100 from the Available Tags window.
Project Utilities
204
Apr-10
Split/Merge Utility
14 Click Add Tag Number.

15 Click Next.
16 Click Finish.
The Datasheet opens.
17 Type Oil Temperature in the Service Description field (D13).
18 Click Save and Exit.
19 Click OK.
20 Click Return to Data Manager.
The Datasheet application closes.
Note: The datasheet was created in the child and the database was updated
with the new information.
Exercise 5: Modify the Child Project with New Tags.

2 Select AT_INST_ from the Select Type dialog.
3 Click OK.
4 Type 100-PT-110 in the Tag Number field.
5 Click OK.
Apr-10
205
Project Utilities
Split/Merge Utility
6 Scroll down the Process Instrument list until you find the tag 1-PT-110.
Note: The Keytag for this instrument has increased by 20 million. This is to
eliminate duplicate tags when the child is merged back into the project.
Exercise 6: Modify the Child Project by Deleting an Existing Tag

1 In the Process Instrument list, select Tools > Find > Find Tag.
2 Type 100-LT-200 in the Tag Numbers that Contain field.
3 Click OK.
4 Select 100-LT-200.
5 Click OK.
The tag is now in the first row of the view.
6 Select Tools > Delete Tag.
The Data Manager presents a dialog confirming that you want to delete
the tag.
7 Click Yes.
The instrument is now deleted from the database.
Exercise 7: Modify the Parent Project

1 Select File > Open Project.
2 Open the parent project Training.
Project Utilities
206
Apr-10
Split/Merge Utility
3 Close the My Instrument list.

4 Open the Process Instrument list.
Note: The instrument tag 100-LT-200 is still a part of the parent project.
5 Select Tools > Find > Find Tag.

6 Find the tag 100-LT-200.
7 Select Tools > Edit Tag.
The Edit Tag dialog opens.
8 Change the tag to 100-LT-202.
9 Click OK.
Exercise 8: Modify the Parent Project by Adding a New Tag

2 Select AT_INST_ from the Select Type dialog.
3 Click OK.
4 Type 100-FI-110 in the Tag Number field.
5 Click OK.
6 Scroll down the Process Instrument list until you find the tag 100-FI-110.
Apr-10
207
Project Utilities
Split/Merge Utility
Exercise 9: Modify the Parent Project by Deleting an Existing Tag

1 In the Process Instrument list, select Tools > Find > Find Tag.
2 Type 100-LG-100 in the Tag Numbers that Contain field.
3 Click OK.
4 Select 100-LG-100.
5 Click OK.
The tag is now in the first row of the view.
6 Select Tools > Delete Tag.
The Data Manager dialog opens again to confirm deletion of tag,
7 Click Yes.
The instrument is now deleted from the database.
Exercise 10: Update the Parent and Child Projects

1 Select Programs > Bentley > Plant V8i > Project Tools > Split or Merge
Project from the Windows Start menu.
2 Select File > Open Parent Project.
3 Select Child Projects > Synchronize with Child.
Project Utilities
208
Apr-10
Split/Merge Utility
The program runs through each of the projects and notes the changes.
4 Scroll down in the Document View.
Your new datasheet is marked as a new document.
The synchronization shows the new tags that were generated in the child
project.
Exercise 11: Update the Parent Project

1 Highlight the newer tags in the Child Project.
2 Click Update Parent.
Apr-10
209
Project Utilities
Split/Merge Utility
The program notes that there were a few documents that were not
included in the selection set and asks if you want them to be included in
the update.
3 Click OK.
The Synchronization window appears.
4 Scroll to the bottom of the Tag View.
The new tags have been added to the parent project.
Project Utilities
210
Apr-10
Consistency Check Options

2D to 3D Consistency Reporter
Process Overview
In order for the 2D to 3D functionality to operate, you must have access to an
AutoPLANT 2D project. The 2D to 3D functionality provided in PIPING and
EQUIPMENT is accomplished by a series of mappings defined in external text files.
These mappings enable the system to accurately map an AutoPLANT P&ID
component to its AutoPLANT PIPING equivalent. If you are familiar with the
customization of the P&ID system, you will understand what this functionality
accomplishes. On the most general level, it is a mapping of a P&ID components
key to a PIPING components class.
In order to facilitate the performance of consistency checks, supporting database
tables are provided in the projects database which allow mapping between the
2D (P&ID) and 3D systems (Piping and Equipment).
The Consistency Reporter user interface is comprised of the following views:
tree view of all 2D and 3D line numbers and valves for the selected
project
tree view of all 2D and 3D equipment and nozzles for the selected
project
grid listing the mapped property value consistency results related to

the selected item in the Line Numbers or Equipment tree view
The following provides a description of the mapping tables and how they are
used.
Apr-10
211
Project Utilities
Views of the 2D and 3D Drawings
A component item in the Line Numbers or Equipment grid marked with a green
check mark indicates that the item exists in both 2D and 3D with no
inconsistencies.
A line number or equipment item marked with a curving down arrow indicates
that the item is present in 2D and 3D but one or more of its child items have an
inconsistency. Child items of line numbers are valves. Child items of equipment
are nozzles.
A component item in the Line Numbers or Equipment grid marked with a red 2
indicates that the item is present in 3D but missing in 2D. A red 3 indicates that
the item is present in 2D but missing in 3D. If the item is present in 2D but missing
in 3D, each entry in the 3D columns will be marked *Missing*. If the item is
present in 3D but missing in 2D, each entry in the 2D columns will be marked
*Missing*.
A component item in the Line Numbers or Equipment grid marked with a red
check mark indicates that the item exists in both 2D and 3D but has field value
inconsistencies. These inconsistencies will be listed in the Consistency Status grid.
A mapped properties item in the Consistency Status grid marked with a green
check mark indicates that the properties of the selected item in the Line Numbers
or Equipment grid are properly matched between 2D and 3D.
Project Utilities
212
Apr-10
A mapped properties item in the Consistency Status grid marked with a red check
mark indicates that a mismatch exists between the 2D and 3D properties of the
selected item in the Line Numbers or Equipment grid.
Consistency Reporter Operations

Opening a Project
Open a new project by selecting File > Open.
Refreshing the Drawing Views

Refresh drawing views by selecting File > Refresh.
Running Consistency Checks

To run a consistency check, select Run Check from the right-click context menu or
select Check > Run. Consistency checks may only be performed in these locations:
at the root node of the Line Numbers and Equipment tree views
on a line number node in the Line Numbers tree view
on an equipment tag node in the Equipment tree view
Purging Obsolete Consistency Results

If there are old and obsolete line numbers or valves that no longer exist in 2D and
3D, but still exist in the consistency results, these may be removed by selecting
Check > Purge.
Note: Performing a full consistency check (the preferred method of updating
consistency check results) will automatically purge these items.
Resetting Consistency Results

Select Check > Reset to reset the consistency results in the currently selected Line
Numbers or Equipment tree view.
Ignoring Inconsistencies
When the check box is set in the Ignore column in the Line Numbers tree view,
Equipment tree view, or Consistency Status grid, any inconsistencies are ignored.
Apr-10
213
Project Utilities
This option is also available from the right-click pop-up menu and from the Check
menu.
Viewing 2D and 3D Drawings

The 2D and 3D drawings for a selected item may be viewed by selecting:
View > 2D Drawing
View > 3D Drawing
View > Zoom in 2D Drawing
View > Zoom in 3D Drawing
Alternatively, the same options may be selected from the right-click context
menu.
The Zoom options will zoom into the drawing view centered on the selected item.
Other View Options

Other options available in the View menu include:
Project Utilities
Status Bar: toggles viewing the status bar
Toolbar: currently not available
Line Numbers: toggles viewing the Line Numbers tree view
Equipment: toggles viewing the Equipment tree view
214
Apr-10
Consistency Status: toggles viewing the Consistency Status view
Reports
The following options are available under the Reports menu:
Preview: allows the user to preview a selected report
Print: allows the user to print a selected report
Edit: allows the user to edit a selected report
All reports are Microsoft Access reports in the current project's

ConsistencyReports.mdb Microsoft Access database.
Exercise 1: Perform a Consistency Check

2 Log into the project.
Apr-10
215
Project Utilities
3 Select Tools > 2D to 3D Consistency Reporter.
The following dialog displays.
4 Select Check > Run.
Project Utilities
216
Apr-10
Now you are able to investigate the items with a red check mark, which
means that there is a discrepancy between the P&ID and the 3D Model. In this
case, a valve is not in the 3D model on line number L1001. You could choose
to ignore this discrepancy or you can choose another course of action, which
may include the removal or addition of the component.
If you are unsure of the problem, you may investigate further by selecting the
component in question. Then, from the View menu, choose the drawing type
that requires further review.
5 The drawing will be displayed in the lowest dialog window, as shown

below:
Apr-10
217
Project Utilities
You may pan or zoom into the window by right-clicking within the drawing and
selecting an option from the context menu.
2D to 3D CAD Interface and Consistency Checker

The 2D/3D interface is a convenient way to view the P&ID and associated data
such as pipes/valves or equipment/nozzles while in the 3D design environment.
This functionality is available from the main menu for both the EQUIPMENT and
PIPING applications.
Since this application is launched inside Piping or Equipment, it will not be
discussed in detail here. Below are typical graphical interfaces the user will see.
Browse Piping and Valves - Showing Data Values
Project Utilities
218
Apr-10
Browse Piping and Valves - Showing View Pane Containing

P&ID Graphics
Browse Equipment and Nozzle, Values/View Pane Closed
Apr-10
219
Project Utilities
Consistency Checker in 2D Browser, View Pane Closed
These features will enhance modeling productivity by allowing access to current

data from the P&ID, Equipment data sheets etc. When values are changed, the
consistency checker will highlight any inconsistent data between the 3D model
and the P&ID.
Project Utilities
220
Apr-10
Module Review
Module Review
Questions
1 Discuss why items were locked in the parent project while the child
project was split out.
2 Discuss the updated items in the parent project.
3 What does enabling the "Packing the project for Handover" option
provide?
4 Briefly state what the 2D to 3D Consistency Checker utility does.
Answers
1 Items were locked in the parent project so that users could not make
changes to the items while the child project was being worked on. This
action allows the project to be synchronized when the child project is
brought back into the parent project.
2 Once the child project is merged back into the parent project, all items in
the parent project are updated with the most current information from
the child project, and any new items from the child project are added to
the parent project.
3 The Packing the project for Handover option allows a project from EPCs to
be brought into the Owner Operator projects as a new project, without
synchronizing with the Owner's existing projects.
4 The 2D to 3D Consistency Checker utility provides an interface which
verifies that components in a 2D drawing are also in a 3D drawing.
Apr-10
221
Project Utilities
Module Review
Project Utilities
222
Apr-10
Module Overview
This section is designed to introduce you to ProjectWise Navigator and how it is
used to interface with various documents.
Module Objectives
Apr-10
Use ProjectWise Navigator.
223
ProjectWise Navigator delivers visual technologies to support design and
construction management processes and to manage assets in real time. These
technologies can be used to satisfy five key business and project requirements.
Highlights include the ability to:
Assemble 2D/3D content from hundreds of applications and file

stores.
Review designs and models in an immersive and homogenous

environment.
Enrich content, add comments, link docs/data sets, add materials for
visualization.
Analyze and simulate construction schedules, detect clashes and

lighting options.
Produce portable and intelligent work packages for downstream

activities.
Provide Visual Collaboration.
You need to first create i-models, which can then be open using ProjectWise
Navigator
Project information from different applications often must be shared. An i-model
is used to exchange project information from different applications and products.
For example, an i-model allows you to share Bentley data along with third-party
product information. An i-model shows a design at a precise state, facilitating the
review and management of the design. Because it is a snapshot of the design, it
can be used in many different types of workflows.
The ProjectWise i-model Composer

ProjectWise i-model Composer is a desktop application used for creating i-models
from data generated by design applications. It supports the creation and
publication of i-models from a wide range of file formats generated by Bentley
and third-party design applications in the Plant, Building, Civil and GeoSpatial
industries.
If you wish to create a series of i-models (maybe all of your Equipment models)
you should first create a composite model with all the models referenced in.
224
Apr-10
Exercise 1: Create an i-model

1 Select Start > All Programs > Bentley > ProjectWise i-model Composer >
ProjectWise i-model Composer.
2 Select examples in the User list.

3 Select AutoPlant in the Project list.
4 Select default in the Interface list.
5 Select Main.dwg in the file name list.
6 Click Open.
The system loads the Main.dwg design file and each X'ref attached to the
file.
7 Select Publish-i-model.
To create the Published Files.
Apr-10
225
Exercise 2: Read 3D Component Indexing

1 Select ProjectWise Navigator Start > Programs > Bentley > ProjectWise
Navigator V8i > ProjectWise Navigator V8i Edition.

5 Select Main.dwg.i.dgn in the file name list.
6 Click Open.
The system loads the Main.dwg design file and each X'ref attached to the
file.
7 Select Component Indexing File > Navigate > Components.
8 Select the Components tab (if needed).
226
Apr-10
9 Select View Components.
The system retrieves the component data.
10 Expand AUTOPLANT_LINENUMBER.
11 Select 0314.
12 Right-click.
13 Select Zoom.
14 Expand line 0314.
Apr-10
227
15 Select PIPE, SCH 40.
The system reads the component data in the model. Properties are readonly.
228
Apr-10
Exercise 2: Read 2D Component Indexing

1 Select Start > All Programs > Bentley > ProjectWise i-model Composer >
ProjectWise i-model Composer.
5 Select PID02.dwg in the file name list.
6 Click Open.
7 Select Publish-i-model.
8 Select ProjectWise Navigator Start > Programs > Bentley > ProjectWise
Navigator V8i > ProjectWise Navigator V8i Edition.

10 Select AutoPlantPIW in the Project list.
12 Select PID02.dwg.i.dgn in the file name list.
13 Click Open.
14 Select Component Indexing File > Navigate > Components.
15 Select the Components tab (if needed).
Apr-10
229
16 Select View Components.
The system prompts you to select the project folder the P&ID file resides
in.
17 Select the folder shown below.
18 Click OK.
19 Select the project.
20 Click OK.
230
Apr-10
The system is now able to read the project database.
21 Click OK.
The system retrieves the component data.
22 Select AutoPLANT P&ID > PIDP02.DWG.i.dgn > Process.

23 Select 0204.
Apr-10
231
24 Right-click.
25 Select Zoom.
The system reads the component data in the model. Properties are readonly.
232
Apr-10
GUIDS
GUIDS
A Globally Unique Identifier (or GUID) is a special type of identifier used in
software applications in order to provide a reference number which is unique in
any context (hence, "Globally"). A GUID is used, for example, in defining the
internal reference for a type of access point in a software application, or for
creating unique keys in a database. While each generated GUID is not guaranteed
to be unique, the total number of unique keys (2128 or 3.41038) is so large that
the probability of the same number being generated twice is very small.
Project GUIDS in AutoPLANT

An AutoPLANT Project is uniquely defined by a project root and project
number. In some cases this uniqueness is not enough. An example of this is
when you are enabling the AutoPLANT project into ProjectWise. To improve
this, a Project GUID has been added to the Project.ini.
Apr-10
233
GUIDS
Document GUIDs in AutoPLANT

Document GUIDs are created when Project Packager is used to package a project.
The user must set Add ProjectWise Synchronization Support. This option is used
primarily for handover projects. An example of this is when an EPC wants to hand
over a project to their client.
Note: To create Document GUIDs:
1 Set Project Packager (with "Add ProjectWise Synchronization Support")

2 CreateGUID utility.
234
Apr-10
Data Reuse
Data Reuse
In this section you will become familiar with techniques to reuse AutoPLANT
design data.
One rule of thumb with AutoPLANT design software is that you shouldn't have to
re-draw or re-model a design. The software provides various methods of coping
data, models and drawings.
Note: The design file units (Imperial/Metric) need to be the same when coping
from one file to another, or from project to project.
Drawing Exchange
Drawing Exchange enables you to export an AutoPLANT P&ID to an exchange
drawing embedded with its associated database data. An exchange drawing
can be used to:
Move the current drawing from a stand-alone version to a project

version.
Move or copy the current drawing from one project to another.
Combine or split projects.
Archive a drawing at the end of a project to ensure that data remains

with the associated drawing.
The Relationship Manager is an AutoPLANT Plant Design application. This tool
is only available if the AutoPLANT applications are installed. It cannot be used
to work with PLANT's Process and Instrumentation applications. The
Relationship Manager provides a central location for an administrator to
manage relationship values (e.g. LineNumber, Unit, Area, Service, Spool, and
Document).
The workflow for AutoPLANT Plant Design allows the Project Administrator to
create all of the relationship values for a project or configuration at the start
of the project outside of AutoCAD. This workflow gives an administrator
control of the property values used on a project. Designers can then select
from the provided list of values to create the models.
Apr-10
235
Data Reuse
The Relationship Manager is also used to delete, rename, add, import, and
export documents in a project environment. Deleting a document deletes the
associated component records and relationships from the project.
PXF Files
This utility is included in the AutoPLANT Plant Design application and used
primarily to copy 3D piping components from one file to another, or from one
project to another. This functionality is covered in the AutoPLANT Plant
Design training manual.
Briefcase Mode
Briefcase mode replaces the former Standalone mode supported in
AutoPLANT Plant Design 2004 Edition. Briefcase drawings are associated with
configurations instead of projects. This mode consolidates all of the data into
the drawing file. It does not require a project, knowledge of a database, or
any other extraneous information.
236
Apr-10
Module Review
Module Review
Questions
1 What is ProjectWise Navigator?
2 What are the three forms of Data Reuse?
Answers
1 ProjectWise Navigator delivers visual technologies to support design and
construction management processes and to manage assets in real time.
2 The three forms of data reuse are Drawing Exchange files, PXF files and
Briefcase Mode.
Apr-10
237
Module Review
238
Apr-10

Module Overview
In this chapter you will learn to customize the views and reports provided in the
Bentley Data Manager application.
Module Objectives
Apr-10
Customize a Data Manager view.
Create a new view.
Customize a Data Manager report.
Create a new report.
239
Data Manager Interface
Data Manager Interface

Data Manager is a core application for interfacing with the database that
underlies all Process and Instrumentation and AutoPLANT Plant Design
applications. Changes made here can affect the working of the other application.
Thus, one must be careful to make only prudent, well thought-out changes to the
data structure.
There are two primary methods for interfacing with the data in Data Manager:
Views and Reports. This chapter will cover how to set up views and reports using
Data Manager, with a minor discussion on modifying the database.
For this chapter, we are going to proceed with Microsoft Access format
databases. The discussion could be directly extended to other database options.
Overview of Database Terminology
Tables: fundamental structure of a relational database, typically an object

that stores data in records (rows) and fields (columns)
Records: rows of data in a table
Fields: columns of data in a table
Views (also called queries): operations that retrieve data from one or more
tables and display the results in a grid format where you can update the
records (with some restrictions).
240
Apr-10
Brief Tour of the Data Manager Interface

This section provides a general introduction to the Data Manager interface.
Take some time to familiarize yourself with the main features of the interface as
described below
Menus
File
The File Menu provides commands to:

Create a new project.
Open an existing project.
Edit and manage descriptive, database, directory, and path information
associated with the current project.
Log into the current project as a different user.
Launch the AutoPLANT Project Editor module.
Import and export table data.
Launch the AutoPLANT Batch Print module.
Exit the Data Manager application.
Edit
The Edit Menu commands provide shortcut methods to traditionally timeconsuming keyboard actions.
View
The View Menu provides commands to:

Toggle the Project Window.
Toggle the Properties Window.
Refresh the current view.
Display the current project equipment list, motor list, and instrument list.
Tools
The Tools Menu provides commands to:

Quickly create, edit, and delete tag numbers.
View/modify detailed database data associated with a selected tag number.
Search/replace a tag or text string.
Filter and sort the data in the current view.
Use Database utilities and tools.
Applications
The Applications Menu provides commands to launch other AutoPLANT

products such as Datasheets, Specification Sheets, Hookups, and P&ID.
Window
The Window Menu provides commands to:

Toggle between multiple open Data Manager windows.
Arrange all open windows.
Help
The Help Menu commands display:

on-line help for AutoPLANT Data Manager
product version information for AutoPLANT Data Manager
Apr-10
241
Data Manager Toolbar

The Data Manager toolbar provides the fastest access to application commands.
After initial startup, it is docked in the upper portion of the screen. To view the
name of the command that will be executed by any tool, position the cursor over
it and pause. A tool tip will display describing that item.
The Project Window

The Project window contains these sections:
Views: enables viewing, creating, editing, and deleting views defined

in the current project standards
Reports: enables previewing, creating, editing, deleting, and revising

reports defined in the current project standards
Macros: enables running, creating, editing, and deleting macros

defined in the current project standards
Tables: enables opening an existing table within the current project
242
Apr-10
Examining the Original Database

When creating a project, you choose to copy the "Base" project. (Or, some
existing project whose creation can be traced back to some point of copying the
Base project.) The database for the Base project was one of the items copied in
creating your project. The Base version is found in the C:\Program
Files\Bentley\Plant V8i\Base\Project directory.
When creating an Access project, the project.mdb in Base\Project directory is
copied into the project's directory Projdata. When an MSDE project is created, a
file called project.mdf is created in addition to the Access file project.mdb. When
an Oracle or SQL project is created, the project database is on the Oracle or SQL
server.
To see these tables and the raw data from within Data Manager, expand the
Table node in the Project Window.
Apr-10
243
Understanding Views
Views are a filtered look into a table or tables in the database. They are the same
as queries in Microsoft Access. For example, if you wanted to look at the data for
specific components, and you only want to view the Tag number, manufacturer
and model number, you would create a view that displays these three attributes.
There are two types of views in AutoPLANT:
Traditional Microsoft Access views are created using Microsoft Access

tools and techniques. These views are good for viewing data, and for
generating filters for a report. (Reports will be covered later in this
chapter.)
AutoPLANT (AT_XXX) views have been moved to Project Administrator

and were discussed earlier.
The views are not saved in the same file with the raw data; instead they are in a
separate database file found in the project directory. In particular, the views are
saved in the schema.mdb file found in the Project's Projdata directory. The
reports are also saved in this directory in both the schema.mdb and the
project.mdb. For example:
1 Open schema.mdb.
2 Open the table REBISVIEW.
3 In this table, locate EQUIPMENT LIST.
4 Note that in the Equipment List record, the view is defined as an SQL
Query.
If you are proficient with SQL, you could create new views from inside this table.
However, most people prefer to create views through the Data Manager
244
Apr-10
interface, which you will do next. Opening the Equipment List view in Data
Manager should show the same view defined in the SQL query of Schema.mdb.
Note: Keep in mind that no raw data is held in Schema.mdb; it holds only the
definitions of views and reports and other project objects.
Apr-10
245
Modifying a View
Modifying a View
AutoPLANT Views can also be used to highlight specific information to suit the
current user requirements.
The Design View interface allows for:
Simplified Field selection.
Text font and color control.
Simple Field access control (ability to make fields read-only or hidden).
Ability to have fields read from a list.
In addition, selecting Design with Access can access all functionality available in
Microsoft Access. (i.e., selecting Design with Access will launch the Microsoft
Access view design interface.)
Note: During the next several exercises you will be learning how to modify and
edit views. It is now necessary to have data in your project so that you
can see the results of your modifications.
Exercise 1: Highlight Fields
Warning: Please note that you cannot add a field with the characters "ID" or "TAG" in the
field name, nor should you edit any of the existing fields with these characters.
They are considered system fields and are used for internal purposes only.
Data Manager.
2 Open the C:\Bentley_Training_Project\Training project.
3 In the Project Window, select the Equipment List view.
4 Right-click.
246
Apr-10
Modifying a View
5 Select Edit.
The Edit View screen contains these options:
Design: allows the view to be designed
System: cannot be modified by the user and indicates a system view
Protected: indicates a view that cannot be modified by a normal user
Read Only: indicates that the views contents are read only
Short List: allows system views to be hidden quickly
6 Click Design.
7 In the Selected Fields list highlight OP PRESS.

The Field property changes to EOPP.
Apr-10
247
Modifying a View
8 Click the browse next to the Color field.
9 Select a green color.

10 Click OK.
The word OP PRESS in the Color field shows as green.
11 Repeat steps 4 through 10 to change the OP TEMP field to green.
12 Click OK.
The Design View dialog closes and Data Manager is returned.
13 Scroll over to the OP Press and OP Temp fields, which are now displayed
in green.
Exercise 2: Make a Field Usable to Everyone

1 Select the Equipment List view.
2 Right-click.
3 Select Edit.
4 Select the PIPING DRG field.
248
Apr-10
Modifying a View
5 Clear the Read Only check box.
6 Click OK.
Data Manager is returned.
7 Scroll over to the PIPING DRG field.
The Font and Color background change to black and white.
Apr-10
249
Modifying a View
Exercise 3: Make the Manufacturer Field a Picklist in Equipment List View

1 Close Data Manager and any other AutoPLANT application.
2 Browse to C:\Bentley_Training_Project\Training\Projdata.
3 Open Projdata.mdb.
4 Create a new Table in design view having three fields, EQPTYPE,
MANUFACTURER and DESCRIPTION:
5 Set all three Data Type fields to Text.

6 Save the table with the name Manufacturer.
7 Open Manufacturer in Datasheet view.
250
Apr-10
Modifying a View
8 Enter the following data.
9 Save and close Projdata.mdb.

11 Expand Database.
12 Select the Databases node.
13 Select PROJDATA from Project Databases.
Apr-10
251
Modifying a View
15 Click Add.
16 Select Manufacturer.
17 Click OK.
18 Click Close.
19 Close Project Administrator.
Data Manager.
21 Select the Equipment List view.
252
Apr-10
Modifying a View
22 Click Design.
The Design View dialog opens.
23 Move the MANUFACTURER field up between MATERIAL and OP PRESS
fields.
24 Set Pick List.
25 Type Select DISTINCT MANUFACTURER from MANUFACTURER where
EQPTYPE = '<<TAG_TYPE>>' in the Pick List entry window.
26 Click OK.
The MANUFACTURER list displays manufacturer names with respect to

Equipment Tag Type.
Apr-10
253
Creating a New View
Creating a New View
Exercise 1: Create a New View

1 Select the Equipment List in the Project Window.
2 Right-click.
3 Select New.
Starting from Scratch: creating a view from scratch. This option

requires knowledge of the AutoPLANT table structure and Microsoft
Access Query building.
From Other Project: allows views to be migrated from other projects.
From current View: allows the current view to be used as a baseline for
the new view.
4 Set From current View.

5 Click OK
6 Type My Equipment List in the Name field.

7 Type Exchanger List in the Description field.
8 Set the Short List check box.
9 Click Design.
The Design View dialog displays.
10 Click Design with Access.
254
Apr-10
Creating a New View
Microsoft Access is loaded with the view displayed in the query builder.
Note: AutoPLANT Data Manager uses Microsoft Access to design queries and
reports. This provides an established interface and allows queries and

reports from user applications to be easily migrated. For further
information concerning Access queries and reports, refer to Access online help.
11 Select the ETYP field.
12 Type E in the Criteria cell.
13 Press ENTER.
14 Close the Access Query Design View.
A prompt is displayed to save the changes.
15 Click Yes.
The Design View - My Equipment List dialog is displayed.
16 Click OK.
The Design View dialog closes and Data Manager is returned.
Apr-10
255
Creating a New View
The My Equipment List view displays in the Project Window.
Exercise 2: Display the Short List Views

1 Set Short List on the Project Window.
The Project Window closes all of the nodes.
Only the Short List views are displayed.
256
Apr-10
Creating Reports
3 Open My Equipment List.
Only the Exchangers are displayed.
Creating Reports
Data Manager utilizes Microsoft Access for report writing; therefore, the greater
your Microsoft Access skills, the easier it is for you to create and customize
reports. It is not the purpose of this class to teach you the full capabilities of
Microsoft Access reporting. However, we will now cover a few examples to show
the possibilities.
Exercise 1: Creating a Filtered View for Pumps

1 Select the Equipment List.
2 Right-click.
3 Select New.
The New View dialog displays.
4 Set From current view.
5 Click OK.
6 Type Pump Report View in the Name field.
7 Type PUMPS ONLY in the Description field.
Apr-10
257
Creating Reports
8 Click Design.
9 Click Design with Access.
10 Place your cursor in the Criteria field in the column that reports the
TAG_TYPE from the TAG_REG table.
11 Right-click.
12 Select Build.
13 Type AT_EQPMP.
Expression Builder closes.
14 Click OK.
15 Save and close Microsoft Access.
16 Click OK.
258
Apr-10
Creating Reports
17 Double-click on Pump Report View in Data Manager.
Note: Only pumps are listed.
Exercise 2: Build a Report from the Filtered Pump View

1 Expand the Reports node.
2 Select the Equipment List report.
3 Right-click.
4 Select New.
5 Set From Current Report.
The New Report dialog opens.
6 Type PUMP LIST in the Name field.
7 Type PUMPS ONLY in the Description field.
8 Click Design.
The Pump List report is modified.
9 Select Properties or right-click in the gray space.
Apr-10
259
Creating Reports
10 Select the ALL tab.
11 Select Pump Report View.

12 Type Pump List in the Caption field.
Pump List will show in the report header.
13 Close the Report dialog.
14 Save and close to the view.
15 Open the Pump List report.
260
Apr-10
Creating Reports
Exercise 3: Make the Report Filter

1 Make a copy of Equipment List report as was done in the previous
examples.
2 Name it Pump List Too.
3 Type Another Pump List in the Description field.
4 Click Design.
The Report Design view displays.
5 Right-click in the gray space.
6 Select Build Event.
7 Select Code Builder.
8 Modify the code so that (after the option section) it reads:
Private Sub Report_Open(Cancel As Integer)
DoCmd.ApplyFilter , "TAG_TYPE = 'AT_EQPMP'"
End Sub
9 Save and close the Code Builder.

10 Save and close Microsoft Access.
11 Open the Pump List Too report.
Exercise 4: User Input Report - Case 1

1 Make a copy of the Equipment List report.
2 Name it User Pick Equip.
Apr-10
261
Creating Reports
3 Click Design.
The report design view displays.
7 Click OK.
DoCmd.ApplyFilter , "TAG_TYPE = ENTER_TAG_TYPE"
End Sub
9 Save and close the report.

10 Open the User Pick Equip report.
11 Type AT_EQDRM.
12 Click OK.
The report opens showing only the equipment drum tags.
Exercise 5: User Input Report - Case 2

1 Make a copy of the Equipment List report.
2 Name it Equip List PID.
3 Click Design.
The report design view displays.
7 Click OK.
DoCmd.ApplyFilter , "PID_DRAWING_NO"
End Sub
262
Apr-10
Access Forms
9 Save and close the report.

10 Open the Equip List PID.
The Enter Parameter Value dialog opens, prompting the user to enter a
P&ID drawing number.
11 Enter PID01.
12 Click OK.
The report opens showing the equipment on PID01.
Access Forms
If you want to automate the report generation using an Microsoft Access Form,
you can do it by enabling the Forms visibility in the at.ini file. For more
information on the Forms, refer to Microsoft Access help.
[Data Manager]
Userforms=1
Apr-10
263
Module Review
Module Review
Questions
1 What is the name of the interface which allows you to change the color of
a field name?
2 Can you add your own company logo to a Bentley report?
3 How would you filter a report to show only transmitters?
Answers
1 The Design View interface allows you to change the color of a field name.
2 Yes, your company logo can be added to a Bentley report.
3 In the Microsoft Access Design view, you would type "FT" in the criteria
field of the ITYP field.
264
Apr-10
Module Overview
In this chapter you will learn to use the Bentley Datasheets application to create
datasheets, add tokens, and generate a datasheet. You will also use the
Datasheets Utilities to create and update the data.
Module Objectives
Apr-10
Create a new datasheet.
Understand mapped datasheets.
Add a property to a datasheet.
Export a datasheet.
265
Understanding Datasheets Structure
Understanding Datasheets Structure

Bentley Datasheets provides you with three control buttons within the current
physical datasheet (.XLS).
Save and Exit: saves all changes made to the current datasheet (.XLS),
and returns to the Bentley Datasheets interface.
Cancel and Exit: cancels all changes made to the current datasheet
(.XLS), and returns to the Bentley Datasheets interface.
Show Database Fields: displays a list of the available database fields

that can be linked in the current datasheet. Click the adjacent Expand
button to display the individual fields from a specific table.
Exercise 1: Link a Field to the Datasheet

Linking fields to datasheets provides the best way to keep data current. It also
allows update of the database should the datasheet be imported into the
project.
1 Select a pump tag in Data Manager.
2 Launch Datasheets.
The datasheet file opens.
4 Place your cursor in the appropriate cell.
5 Select the appropriate field from the Database Fields list.
6 Click Set Field Link within the Database Fields list.
7 Click Save and Exit (located above the Microsoft Excel menu).
Datasheets returns.
8 Select File > Exit.
Data Manager returns.
266
Apr-10
Database References
Database References
A cell name can refer to a single cell or to a range of cells:
Single cell names: bind data in the spreadsheet cell to the first tag
allocated to the datasheet. Data transfer may be bi-directional. Data
transfer is uni-directional from database to datasheet if the database
view or view field is marked read-only.
Range cell names: bind data in the spreadsheet cell range to each tag
allocated to the datasheet. Multi-cell ranges will expand as tags are
allocated to the datasheet. Typically they are used for lists of tags and
tag descriptions; for example where 10 identical limit switches are
allocated to a datasheet. Data transfer is always uni-directional from
database to datasheet.
Internal References
Single cell names contain the latest revision information. These names will also be
used when a batch update of revisions is done.
Rev: revision number
RevDate: revision date
RevBy: name of the person who did the last revision
RevStatus: revision status
Range cell names that contain a summary of the revision history. These ranges
are defined as a single column with multiple rows, where the first row contains
the heading. It differs from the previous multi-cell names where the system will
only use the amount of rows that is marked and will not expand it. If there are
already five revisions for this datasheet, but the range is only three rows high, it
will only use the latest two revisions in the RevList.
RevListNo: revision numbers
RevListDate: revision dates
RevListStatus: revision statuses
RevListBy: list of persons who did the latest revisions
Note: Before designing the datasheet, mark the normal printable page by
selecting all the cells in that area and defining the selection as
Apr-10
267
Revision Control
PrintArea. This will help to space all the datasheet items correctly. It
can also be used when you want to put some comments on the
worksheet, but don't want to display them on the printout.
Revision Control
Revision control will mark any changes made while working with the datasheet.
This is possible if the following cell names are defined: CurrentData, PreviousData
and RevList. The following describes how to create these cell names.
CurrentData
1 Select the columns and rows where the user normally types the datasheet
information.
2 Define the selected area as CurrentData.
Note: It is a good practice to reserve a column next to this block for the
revision numbers and name the heading Rev.

The system updates the Rev column with a "rev marker" wherever it finds
differences between the CurrentData with PreviousData. When revisions
are updated, the rev marker is replaced with the revision number.
Previous Data
1 Copy the current data to the clipboard.
2 Create a new worksheet.
3 Name the new worksheet Previous Data.
4 Paste the copy of current data from the clipboard onto cell A1.
5 Define the cell as PreviousData.
Revision List
1 Create another worksheet.
2 Name it Previous Revisions.
3 From cell A1 select 4 columns and 2 rows.
268
Apr-10
Creating a New Datasheet
4 Define the selection as RevList.

5 Name the four column headers, in this order: Rev, Date, Status, By.
The revision list includes all revisions created by the Datasheets model
and expands and contracts as revisions are added or removed.

Bentley Datasheets is not a stand-alone application; it is launched from either the
Instrumentation & Wiring or the Data Manager application. A key concept in
Datasheets is that of standard vs. actual datasheets.
A standard can be considered a template. When you create a datasheet for a
particular item, you will create it from the standard. The standard holds the
mapping to the database for the different cells on the datasheet.
A datasheet, on the other hand, is simply an Excel spreadsheet. If the standard
was configured correctly, this Excel spreadsheet will read values from the
database. When you assign a tag to the datasheet, it looks in that particular tag's
record for database values to fill out the datasheet.
After you create a datasheet, you can change the values on it. But then you may
have for instance, the Area field equal to 51 on the datasheet but equal to 45 in
the Database. When you save, the software will prompt you to pick which one
you really want to use, and you will decide if the database or the datasheet has
the most current value.
Apr-10
269
Exercise 1: Create a New Datasheet

This exercise demonstrates concepts and is not meant to show the complete
creation of an entire datasheet.
1 Open a new spreadsheet in Microsoft Excel.
2 Save the new spreadsheet as MYPUMPDS.XLS
3 Modify the spreadsheet to look like the one shown in the following figure.
Note: So far you have just entered simple text - it has no intelligence.
The way you make a cell intelligent in Excel is to name it. Each cell has a name
of its row and column, displayed in the upper left. For example, Pump No. is
A3, Description is A5, and the cell to the right of Description is B5.
We will now link the cells to the database.
4 Place your cursor in cell B5.
5 Select Insert > Name > Define.
270
Apr-10
6 Type _EDESC in the Names in workbook field.

Note: EDESC is the field in the EQUIP table that holds the description. The
underscore ("_") before EDESC is a link telling Microsoft Excel that this
cell is to be read from a database.
7 Click Add.
8 Click OK.
B5 is now named _EDESC.
9 Repeat steps 4 through 8 for fields B6 through B11, refering to the
following table for the database field names.
Description
Database Field
Pump No
_Tag_NO
Service
_ESERV
Material
_EMATL
Operating
Pressure
_EOPP
Operating
Temperature
_EOPT
Power
_EPOW
Type
_ETYP
Note: You can only use a particular name once per Microsoft Excel sheet. For
example, you cannot rename both B4 and B5 _EDESC. However, you

can name one cell and have another cell refer to it. For example, name
B4 as _EDESC and set B5 equal to B4.
We will now name the datasheets.
10 Double-click datasheet tab Sheet1.
11 Type Current Data.
13 Type Previous Data.
15 Type Previous Revisions.
Apr-10
271
16 Add fields Rev, Status, By and Date on datasheet cells D2, D3, D4 and D5
as shown:
17 Click in cell E2.

The Define Name dialog displays.
19 Type Rev in the Names in workbook field.
20 Click Add.
21 Click OK.
22 Repeat steps 14 through 18 to add RevBy to cell E3.
23 Repeat steps 14 through 18 to add RevDate to cell E4.
24 Select the Previous Revisions tab.
272
Apr-10
25 Add the following fields:
26 Select cells A1 to D2.

The name RevList is defined to the selection.
28 Select the Current Data tab.
Apr-10
273
29 Copy all the cells and paste them to the Previous Data tab:
30 Select the Current Data tab.

31 Save MYPUMPDS.xls.
32 Exit MYPUMPDS.xls.
274
Apr-10
Exercise 2: Import Your Datasheet into the Project

2 Expand [+] the Training project.
3 Expand [+] Datasheets.
Apr-10
275
The right-hand window shows the datasheet for the project listed by tag
type.
We will now add a new datasheet to the project.

4 Select Edit Datasheet.
276
Apr-10
The window on the right changes.
5 Select AT_EQPMP from the Select Tag Type list.

6 Click Add.
7 Set Other Standards.
Apr-10
277
8 Click OK.
9 Select MYPUMPDS.xls.
10 Click Open.
The datasheet is now shown in the right-hand side of the Project
Administrator dialog.
11 Type My Pump Datasheet into the Description field.
278
Apr-10
12 Click Save.
This datasheet is now available in Data Manager for use with tags
containing the tag type AT_EQPMP.
13 Click Properties.
14 Click Add.
Extended Data Property is added to the datasheet.
15 Type User1 in the Property field.
16 Type User Defined Field 1 in the Description field.
17 Select <NONE> in Unit Type field.
18 Click Save.
19 Close the dialog.
20 Select Datasheets from the navigation tree.
Apr-10
279
The datasheet has been added to the project.

22 Close Project Administrator.
280
Apr-10
Exercise 3: Test Your New Datasheet

Data Manager.
2 Open the Equipment List view.
4 Select Tag Type AT_EQPMP.
5 Click OK.
6 Tag the pump P-313.
7 Click OK.
8 Manually enter information into the fields as shown in the table below.
Note: TAG_NO and ETYP should already have values.
Database Field
Data Value
Description
My Pump
Service
Glycol Pump
Material
Steel
Operating
Pressure
200 PSI
Operating
Temperature
175 F
Power
15 HP
Apr-10
281
Exercise 4: Create the Datasheet

1 Create a new datasheet by selecting File > New.
2 Set Standards.
3 Click Next.
4 Select MYPUMPDS.
5 Click Next.
6 Type 1234 in the Document Number field.
7 Click Next.
8 Select P-313 from Available Tags.
9 Add to the Allocated Tags window.
10 Click Next.
11 Set Open Document in Excel.
282
Apr-10
12 Click Finish.
The datasheet opens in Microsoft Excel, filled out with data from P-313.
This datasheet is now stored in your project's
\Standards\Datasheet\Equip directory.
13 Select Show Database Fields from the Datasheet toolbar.
14 Expand the node for EXT-DATA.

Note: User1 is available for mapping.
15 Select User1 from Database Fields.

16 Select cell B12.
17 Click Set Field Link.
Apr-10
283
A dialog appears confirming the mapping of Database Field with

Datasheet cell.
18 Click OK.
19 Click Save and Exit.
Data Manager returns.
Note: The overall idea is to create datasheets from a standard. Once a
standard is created, it will not change during datasheet creation. You

can make as many (or as few) datasheets from a standard as desired.
Each datasheet will become a separate Microsoft Excel spreadsheet.
Exercise 5: Saving the Datasheet as a Project Standard

1 Select P-313.
3 Select File > Save As.
4 Type MyPumpDatasheet in the Datasheet - Standard Name field.

5 Click OK.
The datasheet is stored as a project standard.
Exercise 6: Locking Datasheet Cells

Datasheet 1234.xls launches.
2 Select cell B5.
284
Apr-10
3 Select Data > Validation from the Microsoft Excel menu.

4 Select List from the Allow field.
5 Clear In-cell dropdown.
6 Click the button at the end of the Source field.

7 Select any cell on the sheet out of the CurrentData range.
8 Click Data Validation.
The Data Validation dialog re-opens.

9 Select the Error Alert tab.
10 Type This field cannot be modified manually. The update must be passed
from the AutoPLANT project database in the Error Message field.
11 Click OK.
Now when the field is selected the error message will appear.
Apr-10
285
Fully Mapped Datasheet Templates

Bentley Datasheets provides fully mapped datasheet templates which are stored
in the System Library. The templates can be imported into the project and used
immediately without the need for users to map individual fields to tables in the
project database. The templates are based on client and accepted industry
standards.
Users can utilize their own templates but will have to import them into the
project. Once the templates are imported the user can create properties and map
them.
The token structure for the datasheet import is: ::FieldName::Field Description.
Exercise 1: Importing Mapped Tokens

1 Open the user datasheet CV Control Valves provided in the dataset.
2 Select cell K13.
3 Type ::SvrConFloRate::Service Condition Flow Rate in cell K13.
4 Save and close Microsoft Excel.
286
Apr-10
The text ::SvrConFloRate::Service Condition Flow Rate is in token format and will
be automatically added to the extended data table upon import of this datasheet
into the project.
Exercise 2: Import a Mapped Datasheet into a Project
Users will be able to import new or existing datasheet templates directly into the
project environment without having to create and then map every property
needed to support the template. Users can type tokens into the cells to be
mapped and these will be automatically converted into mapped cells, properties
and property descriptions associated with the template and any component
assigned to the template. Minimal impact will be felt because the import routines
are built into the Project Administrator interface. When a user adds or imports a
datasheet into a project the routine is launched and begins searching for and
converting tokens.
Note: Once a datasheet template is imported, the tokens will be replaced with
mapped fields and will no longer be necessary.

1 Open Project Administrator.
2 Expand the PIW Sample project.
3 Expand Datasheets.
4 Select Edit Datasheets.
5 Select AT_CVALVE from the Select Tag Type field.
6 Click Add.
The Select From dialog displays.
7 Set Other Standards.
8 Browse to the CV Control Valve datasheet.
9 Click Open.
The datasheet is imported into the PIW Sample project.
Apr-10
287
10 Type Imported Control Valve Datasheet in the Description field.
11 Click Save.
12 Click Properties.
Note that the token has been added to the Extended Data tables.
288
Apr-10
Datasheets Utilities
The Export Sheet feature in Batch Print and Update allows the creation of a single
Microsoft Excel file compiled from multiple datasheets.
Exercise 1: Create an Export Sheet

1 Launch Batch Print Utility.
2 Select all the TT datasheets.

3 Select File > Create Export Sheet.
The Export Sheet Wizard opens.
4 Click Browse.
The New Export Sheet Name dialog displays.
5 Name the export sheet TTexport.XLS.
6 Save it in the \PIW_Admin_Training\PIW Sample\ directory.
7 Click Save.
Step one of the wizard returns.
8 Click Next.
9 Select which tokens you would like on your export sheet.
Note: TAG_NO and DOC_Name are required fields.
Apr-10
289
10 Using the right arrow, select _ElmntManufact, _ElmntModel, and

_P_order.
11 Click Next.
12 Leave Open this Export Sheet set.
13 Click Finish.
Microsoft Excel opens with the export sheet.
The export sheet shows the summary of the selected field values by tag
number. The idea is to update values in the export sheet, and then reimport these values into the datasheets and database.
Warning: Do not use export sheets to change tag numbers, document name or doc_ID. If you
are sending this export file to another for data entry, you may want to investigate
protecting these critical cells as well as the column headings using built-in
Microsoft Excel functions.
290
Apr-10
Exercise 2: Update from an Export Sheet

1 Type ABC Transmitters in the _ElmntManufac field.
2 Type 1234XYZ in the _ElmntModel field.
3 Type 43A345 in the _P_Order field.
4 Save the xls file.

5 Exit Microsoft Excel.
6 In Batch Print Utility, select File > Update from Export Sheet.
This will update both the datasheet and the database to the values
entered in the export sheet.
7 Open Data Manager.
8 Select an instrument that has been updated.
9 Select View > Extended Data.
The updates to the database are displayed.
10 Open a datasheet and note the same thing.
Apr-10
291
Exercise 3: Other Bulk Update Features

You can select File > Freshen Export sheet to re-dump to the export sheet
from the same datasheets.
You can also select File > Update to use Batch Print Utility to update a
selection of datasheets from the database or vice versa.
1 In Data Manager, open the Process Instrument List.
2 Select the ITYP of TT.
3 Right-click.
4 Select Filter > Quick Filter.
5 Change the Purchase Order field of all the TT tags to 98Z890.
6 In Batch Print and Update, highlight 1 of the TT datasheets.
7 Select File > Update.
Warning: This dialog may be confusing. You need to select what you wish to change.
8 Select Database.
9 Click OK.
10 Click REFRESH in Data Manager.
Note: This will verify that the Purchase Order field in the database has been
replaced by the current data on the datasheet for the selected

datasheets.
Note: If you had selected Document in the update direction dialog, the
Purchase Order value in the datasheet would have changed. The

automatic feature will compare data/time stamps for the database and
datasheet. If the document timestamp is older or the same as the
DOC_REG.LASTUPDATE database timestamp, the document will
update. Otherwise, this option will update the database.
292
Apr-10
Module Review
Module Review
Questions
1 What are Range cells?
2 How do you associate a field to a cell in a Microsoft Excel spreadsheet?
3 What is a fully mapped datasheet?
4 What is the advantage of importing and exporting datasheets?
Answers
1 Range cell names bind data in the spreadsheet cell range to each tag
allocated to the datasheet.
2 To associate a field name to a cell use the command Insert > Name >
Define and type the field name in the Define Name dialog.
3 A fully mapped datasheet is a user datasheet which has been imported
into the project and the fields on the datasheet modified to contain
tokens that map the existing information to the databases.
4 Datasheets can be imported from or exported to a third party. The data
modified by the third party will then be incorporated into the project
database.
Apr-10
293
Module Review
294
Apr-10
Module Overview
In this chapter you will learn about the Bentley Vision application, a document
management system for organizing your documents.
Module Objectives
Apr-10
Use the Vision application.
295
Vision Overview
Vision Overview
Vision is a Bentley application for organizing documents. These documents can be
Bentley documents like P&IDs or Datasheets or PIPING Models. They can also be
non-Bentley documents such native AutoCAD files, Microsoft Word documents,
or Adobe Acrobat PDF files. The term "document" should be taken to mean any
electronic file.
The Bentley Vision application is similar to Windows "My Computer" or
"Windows Explorer". These Windows applications are a way of displaying files
that are on your computer and include some options on how to display the files
and sort the displayed information. Vision is similar but has a few differences:
Vision does not show you all of the existing files on your computer. You must
tell Vision what files to display. This is useful, because you only want to see
documents related to the current project.
Vision is organized by projects, allowing you to have different "work areas"

for different projects. You do not have to keep your documents separate for
different Projects - Vision will take care of that for you.
Vision lets you group your documents in a number of ways. You can group
them by type, as marked by the file extension. For example, all Microsoft
Word documents (doc) could be in one folder, all Microsoft Excel documents
in another (xls), all bitmaps in another (bmp), and so forth. You could also
group the documents to accommodate your company's file structure or you
can group documents based on the related AutoPLANT application.
296
Apr-10
Vision Interface
Vision Interface
Exercise 1: Launch Vision

1 Select Programs > Bentley > Plant V8i > Vision from the Windows Start
menu.
If this is the first time you have opened Vision, the Login dialog displays.
2 Leave Supervisor in the User Name.

3 Type Supervisor in the Password field.
4 Set Save Password.
Note: This feature allows you to automatically be logged in as Supervisor
when opening projects in this project folder.

Vision opens by default into the last open project.
In the Vision interface, the titlebar indicates the current project. Below the
titlebar are menu options and an icon bar. The commands behind the icons
duplicate some of the menu picks.
5 Hover over the icon bar with your mouse.
A tool tip displays indicating each icon's function.
Apr-10
297
Vision Interface
Exercise 2: Explore the Vision Interface

On the left side of the Vision interface are two tabs above the Tagged Item
Tree:
Area tab: displays data contained in the current project, filtered or

sorted by areas.
Document tab: displays documents contained in the current project,

sorted by the application to which the document is associated.
On the right pane of the Vision interface are two tabs, Properties and
Document View, which display information on a selected (highlighted)
document. If no document is currently highlighted, the fields in the two tabs
will be blank.
Properties tab: displays information specific to the tag number or

document selected within the Tagged Item tree.
Document View tab: enables you to display the current document

selected in the Tagged Item tree in a preview window.
1 Select the Area tab.

The Area tab shows the different types of components that can be found
on the drawings.
2 Expand the Instrumentation node.
The different types of instruments are presented.
3 Expand the Flow Element node.
4 Select 100-TT-100.
298
Apr-10
Vision Interface
The Properties tab displays the properties of the transmitter. Any

document associated to the tags, for instance a loop or datasheet,
displays in the Associated Documents window.
The Document tab shows the applications and the documents that are used in
each application.
5 Expand the AutoPLANT P&ID node.
6 Select PID-01.
The Properties tab is now populated with the document's data.
7 Select the Document View tab.
A preview of the selected drawing displays in the window.
Apr-10
299
Administrative Functions
Exercise 1: Add a Non-Installed Application to a Folder

1 Select File > Application Setup.
The Applications dialog displays.
2 Type ProPipe Documents in the Description field.
3 Type /CD: \PRO1313\PIPEADS\R13 in the AutoCAD Cmd field.
Note: /CD: \PRO1313\PIPEADS\R13 is the profile to be used to launch
AutoCAD.
4 Type AT_PROPIPE in the Reg App field.
Note: This is the AT.INI variable to be associated with the application
AT_PROPIPE.
5 In the Picture field, locate and assign the application a unique image
(.BMP or .ICO files only) to be displayed in the Document tab.
6 Click Add.
7 Click Apply.
8 Scroll down to view the newly added application Propipe.
Note: The App Type field has been populated by the software.
9 Click Close.
The dialog closes.
300
Apr-10
The current Vision session is closed.

11 Open C:\Documents and Settings\All Users\Application
Data\Bentley\Plant V8i\CFG\AT.INI in a text editor.
12 In the [GENERAL] group, add the new application ProPipe Documents to
the APPLICATIONS keyword, followed by a semi-colon.
13 Scroll down to the bottom of the AT.INI configuration file.
14 Type the new application name within brackets, as it appears within the
APPLICATIONS keyword [ProPipe Documents].
15 Type the executable file to be used to launch the application CADAPP=
C:\Program Files\AutoCAD 2008\acad.exe.
Note: This location may change depending on where you installed AutoCAD.
16 Type the keyword to be associated with the application

REGAPP=AT_PROPIPE.
17 Select File > Save.
The AT.INI configuration file is closed.
Exercise 2: Associate a Document

1 Select the Area tab.
2 Use the Find Tag function to locate tag 100-FE-100.
Apr-10
301
3 Select Utilities > Associate Document(s).
4 Select 1234.
5 Click Add Link.
6 Click OK.
Note: The document has been associated with tag 1000-TT-003 as displayed
within the Associated Documents group box.
Exercise 3: Associate a Document Type with an Application

1 Select File > Viewer and File Type Setup.
The Configure dialog displays.
2 Select the File Types tab.
302
Apr-10
3 Type the extension of the file type WMF in the Extension field.
4 Click Add.
5 Click Apply.
6 Select the Viewers tab.

7 Select WMF from the Extension list.
8 Browse the Viewer field to find the executable file and path to be used to
launch the current file type.
9 Click Add.
10 Click Apply.
Apr-10
303
The new viewer is now visible in the list of Viewers.
11 Click Close.
304
Apr-10
User Privileges and Settings

Revision Controls
Exercise 1: Set up Revision Controls

1 Select File > Revision Control Security.
The Revision Control Security dialog displays.
2 Select AutoPLANT P&ID from the Applications list.
3 Select Check In-Out/Edit.
4 Click Edit.
5 Leave the Functions as is.

6 Clear Engineer in the Level window.
7 Clear Administration in the Level window.
8 Click OK.
9 Click Close.
Vision is returned.
Note: With this setting, Engineers or Administrators of any discipline would
not be able to check in or check out or edit any AutoPLANT P&ID.
Apr-10
305
Revision Marks
Exercise 1: Create a Revision Mark

Note: A document must be opened before revision marks can be made.
1 Launch Vision if not already open.

2 Select the Document Tab.
3 Expand the AutoPlant P&ID.
4 Highlight PID-01.
5 Right-click.
6 Select Edit.
The file opens.

7 Select Documents > Revision Marks.
8 Click in the Number window.
306
Apr-10
9 Click Edit.
10 Type A in the Number field.

11 Type Revision A in the Title field.
12 Click Add.
13 Click Close.
14 Exit the PID file.
Apr-10
307
Display Options
The Display > Options command displays the Display Options dialog shown
below, which allows you to customize both the Vision interface and selected
Vision controls.
Hide Keytags in Properties: enables you to toggle the display of the

Internal Keytag property associated with an individual tag number.
This property is displayed within the Properties tab.
Hide Check In and Out Status: enables you to toggle the display of the
Status dialog when performing document check-in/check-out
functions.
Display Document Menu on Right Mouse Click: enables you to control

the display of the Documents menu commands via right-click. If this
check box is set, all commands within the Documents menu will
display within a pop-up menu. This pop-up menu also includes select
main menu short-cuts available near the bottom of the pop-up menu.
If this check box is cleared, select main menu shortcuts will display
within a pop-up menu. The Display menu commands will also display
within this pop-up menu embedded within the main menu short-cuts.
Minimize on Document Edit: If set, you can control the minimization of

Vision upon editing a document.
Enable Property Editing: Setting this check box allows you to edit the
properties of a selected tag number or document displayed within the
Properties tab.
Maximum Nodes per Branch: enables you to adjust the number of

records to display beneath each branch of the Vision tree. This setting
applies to all tabs displayed in the Vision tree.
308
Apr-10
Apr-10
Document Grouping: enables you to control how documents are

grouped within the Vision interface.
Font: displays the Font dialog which enables you to control your
default font, font style, and font size display. This font will apply to
virtually all dialogs, the Document Tree, etc.
309
Module Review
Module Review
Questions
1 If you wanted to see the check-in status of a document, what would have
to be done?
2 How would you keep an instrumentation CAD operator from deleting a
tag on a P&ID?
3 Can you associate a component with a document?
Answers
1 To see the check-in status of a document you would have to open the
Display Options and clear Hide Check In and Out Status.
2 To keep an instrumentation CAD operator from deleting a tag you would
open Revision Control Security, select AutoPLANT P&ID in the
Applications list, select Delete in the Action list, click Edit, clear
Instrumentation, clear Cad, and click OK. MKM???? check this w/Gale,
since I modified it so much.
3 Yes, once the component is selected, any document can be associated to
it.
310
Apr-10

Module Overview
In this lesson you will learn to create a project template that can be selected
when creating a new project. This template will contain the customization
changes that were completed during this course.
Module Objectives
Apr-10
Create new projects without having to customize each one.
311
Template Project
Template Project
Customizations were made to the AP_Sample project throughout the course. You
will now make the AP_Sample project a template to be used over and over again.
Exercise 1: Create a Template Directory

4 Browse to C:\Program Files\Bentley\Plant V8i\Base\Options with
Windows Explorer.
5 Create a new folder entitled ABC Corporate (any name can be used here).
6 Open the ABC Corporate folder.

7 Create two new folders, Project and Standards.
8 Browse to C:\AutoPLANT_Admin_Training\AP_Sample.
312
Apr-10
Template Project
9 Copy the Project.ini file.

10 Paste it into the ABC Corporate\Project directory.
11 Copy the Projdata directory.
12 Paste it into the ABC Corporate\Project directory.
13 Browse to C:\AutoPLANT_Admin_Training\AP_Sample\Standards.
14 Copy all of the directories and files from the AP_Sample\Standards
directory to the ABC Corporate\Standards directory.
Apr-10
313
Template Project
Exercise 2: Create a New Configuration

2 Expand the Standard Configurations node.
3 Right-click on Standard Configurations.

4 Select New.
5 Type ABC_Corporation in the Configuration Name field.
6 Click OK.
7 Using Windows Explorer, browse to C:\Program Files\Bentley\Plant
V8i\Config.
314
Apr-10
Template Project
8 Open the Configs.ini file in Notepad.
Note: A new section for ABC_Corporation has been added.
9 Modify State=userdefined to State=protected.
10 Remove the line Parent=Imperial.

11 Browse to C:\AutoPLANT_Admin_Training\AP_Sample\Config.
Apr-10
315
Template Project
12 Copy all folders and files.

13 Paste the items into C:\Program Files\Bentley\Plant
V8i\Config\ABC_Corporation.
14 Browse to C:\Program Files\Bentley\Plant
V8i\Config\ABC_Corporation\isogen.
15 Modify the path in the isogen.fls file for each style directory:
Note: This allows the software to set the proper path to be assigned when it
builds the new project.

17 Create a new access project.
18 Select the ABC Corporation template from the Select the Base Schematic
Template list.
19 Click Next >.

20 Click Next >.
21 Name the project XYZ.
22 Click Finish.
316
Apr-10
Template Project
The XYZ project contains all of the customization created throughout this
course.
Apr-10
317
Module Review
Module Review
Questions
1 Why did you change the path in the isogen.fls file?
Answers
1 The variable <iso_path> was added to the isogen.fls file so that during
during creation of the project the file would inherit the correct project
path.
318
Apr-10
Appendix A
AT.ini
[EQUIP]
DESCRIPTION=AutoPlant Equipment
COMP_PREF_INI_FILE=COMPPref
CP_BLOCK_TYPE=0
LOCALDIR=%LOCAL_ROOT%\equip
MENU_SELECTABLE=1
PROGRAMDIR=%NETWORK_ROOT%\equip
REGAPP=AT_EQP
STARTUP_FILE=at_eqp.lsp
STARTUP_FUNC=at_eqp_startup
SYS_PREF_INI_FILE=SYSPref
USER_PREF_INI_FILE=UserPref
CADAPP=C:\Program Files\AutoCAD 2008\acad.exe
AcadCmdLine=/p "C:\Documents and Settings\All Users\Application
Data\Bentley\Plant V8i\AutoPLANT_PDW811ACAD_6001_409.arg" /b loadequip
[HELP]
GENERAL=%NETWORK_ROOT%\HELP\ATPLANT.CHM
Apr-10
319
Appendix A
AT.ini
COMMON-HELP=%NETWORK_ROOT%\HELP\ATCOMM.CHM
MODULE SETUP=%NETWORK_ROOT%\HELP\ATMODULES.CHM
BASE=%NETWORK_ROOT%\HELP\ATBASE.CHM
ISOMETRICS=%NETWORK_ROOT%\HELP\ATISO.CHM
APSYSTEMDOCTOR=%NETWORK_ROOT%\HELP\atsysdoctor.CHM
AUTO-ISO=%NETWORK_ROOT%\HELP\ATAISO.CHM
INSTR=%NETWORK_ROOT%\HELP\ATINSTR.CHM
DWGPROD=%NETWORK_ROOT%\HELP\ATDPROD.CHM
DRAFT_TLS=%NETWORK_ROOT%\HELP\ATDRAFTTLS.CHM
ANNO=%NETWORK_ROOT%\HELP\ATANNO.CHM
SELEC=%NETWORK_ROOT%\HELP\ATSELEC.CHM
Report Writer=%NETWORK_ROOT%\HELP\ATRPT.CHM
FLATTENER=%NETWORK_ROOT%\HELP\atdwgflattener.chm
2D3D=%NETWORK_ROOT%\HELP\AT2D3D.CHM
ATDB=%NETWORK_ROOT%\HELP\ATDB.CHM
TOOLS=%NETWORK_ROOT%\HELP\attools.chm
PREFSELECT=%NETWORK_ROOT%\HELP\ATPREFSELECTOR.CHM
PRJEDT=%NETWORK_ROOT%\HELP\ProjAdmin.CHM
PROJUPGRADE=%NETWORK_ROOT%\HELP\atprojupgrade.CHM
PROJCONV=%NETWORK_ROOT%\HELP\atprojtypeconv.CHM
PROJCOMM3=%NETWORK_ROOT%\HELP\ATPROJCOMM3.CHM
PROJEXPORT=%NETWORK_ROOT%\HELP\atprojexport.chm
Appendix A
320
Apr-10
AT.ini
PROJIMPORT=%NETWORK_ROOT%\HELP\atprojimport.chm
PROJOBJMNT=%NETWORK_ROOT%\HELP\ATPROJOBJMAINT.CHM
PROJOBJEXP=%NETWORK_ROOT%\HELP\ATPROJOBJEXP.CHM
PROJOBJECT=%NETWORK_ROOT%\HELP\ATPROJOBJECT.CHM
CABLETRAY=%NETWORK_ROOT%\HELP\ATCBLTR.CHM
CONDUIT=%NETWORK_ROOT%\HELP\ATCOND.CHM
DUCTILE=%NETWORK_ROOT%\HELP\ATPDUC.CHM
HIGHPURITY=%NETWORK_ROOT%\HELP\ATPTRIC.CHM
LINEDPIPE=%NETWORK_ROOT%\HELP\ATPLINE.CHM
HVAC=%NETWORK_ROOT%\HELP\ATHVAC.CHM
PLASTIC=%NETWORK_ROOT%\HELP\ATPLA.CHM
TUBING=%NETWORK_ROOT%\HELP\ATPSWGL.CHM
VICTAULIC=%NETWORK_ROOT%\HELP\ATPVIC.CHM
Refrigeration=%NETWORK_ROOT%\HELP\atrefrig.chm
SPECGEN=%NETWORK_ROOT%\HELP\SPECGEN.CHM
SPECUNITCONVERTER=%NETWORK_ROOT%\HELP\specgenunitconverter.chm
RELMGR=%NETWORK_ROOT%\HELP\ATRELATIONSHIPMGR.CHM
ProjConTool=%NETWORK_ROOT%\HELP\approjectconnectivitytool.chm
TRANSLATOR=%NETWORK_ROOT%\HELP\ATXCHG.CHM
PIPING=%NETWORK_ROOT%\HELP\ATPIPE.CHM
ELECTRICAL=%NETWORK_ROOT%\HELP\ATRACEWAYS.CHM
EQUIP=%NETWORK_ROOT%\HELP\ATEQP.CHM
Apr-10
321
Appendix A
AT.ini
[Hookups]
REGAPP=HKUPS
AcadCmdLine=
DESCRIPTION=Hookups
[Vision]
FloatingAssocDwgDisplay=1
LastReportSelected=Cable Schedule Electrical
dialogLeft=3795
dialogTop=630
dialogWidth=11250
dialogHeight=14160
PaneWidth=11130
PaneHeight=12730
LeftPane=930
RightPane=5970
TopPane=8385
BottomPane=2130
TopTab=0
LastTreeTab=2
LastFindType=1
AreaDisplay=1
UnitDisplay=0
Appendix A
322
Apr-10
AT.ini
DocDisplay=1
UserDisplay=0
AssocDoc1=2167.37
AssocDoc2=2167.37
AssocDoc3=2167.37
AssocDocsplitValue=0
AlwaysUseBentleyView=1
AlwaysUseVoloView=0
LastDocumentOpened=
LastFolderOpened=
ZoomToTop=0
ZoomToLeft=0
FloatingDwgDisplayTop=9480
FloatingDwgDisplayLeft=5572
FloatingDwgDisplayWidth=5000
FloatingDwgDisplayHeight=4000
AppDetails=0
MinimizeOnEdit=0
FloatingDwgDisplay=0
[TemplateGen]
Apr-10
323
Appendix A
AT.ini

Data\Bentley\Plant
V8i\PlantCmp128PID.B4D07ED6_F64A_4E1D_8972_58D047FEEB61ACAD_6001_
409.arg"
CADMODE=DWG
STARTUP_FILE=ap.lsp
PROGRAMDIR=%NETWORK_ROOT%
STARTUP_FUNC=c:start
DESCRIPTION=AutoPLANT Template Generator
REGAPP=AT_TMPL
MENU_SELECTABLE=1
HELP_FILE=%NETWORK_ROOT%\Help\TempGen.chm
BASE_MENU=acad.mnu
APP_MENU_POS=10
SHOWCFG=TRUE
DefaultBlockSpacing=0
[DataManager]
REGAPP=DMGR
[Datasheets]
REGAPP=DSHEET
AcadCmdLine=
DESCRIPTION=Data Sheets
[ALIAS]
Appendix A
324
Apr-10
AT.ini
NETWORK_ROOT=C:\Program Files\Bentley\Plant V8i

CUSTOM_ROOT_ORIG=C:\Bentley Plant V8i Configurations\
CUSTOM_ROOT=C:\TEMP\
LOCAL_ROOT=C:\Documents and Settings\All Users\Application
Data\Bentley\Plant V8i
[GENERAL]
AP=%NETWORK_ROOT%
APWS=%LOCAL_ROOT%
AT_BIN_DIR=%NETWORK_ROOT%\bin
APP_RELOAD_FLAG=0
APPLICATIONS=DocManager;PIPING;ISOMETRICS;ELECTRICAL;EQUIP;2DPIPING;Fl
attener;Vision;Navigator;DataManager;Instrumentation;P&ID;STRUCTURAL;NEW
;TEST;ORTP;COMP-DRAW;PROCAD;
APTMP=C:\Documents and Settings\All Users\Application Data\Bentley\Plant
V8i\Tmpdir\
APPROJDB=C:\Program Files\Bentley\Plant V8i\Base\
ProjectDetailsForLogin=0
LastUser=supervisor
SavedUserPW=supervisor|~~1D0415151312061618134741434D5651
CurProject=0001
EXPERT=1
ShowModeSelectionGUI=0
[Report Writer]
Apr-10
325
Appendix A
AT.ini
PROGRAMDIR=%NETWORK_ROOT%\reports
LOCALDIR=%LOCAL_ROOT%\Reports
DESCRIPTION=AutoPLANT Report Writer
REPORT_INI_FILE=Reports
REPORT_INI_DEFFILE=RptType
REPORT_LISP_NAME=AT_Rpt
REGAPP=at_rpt
MENU_SELECTABLE=0
[HelpDocs]
DocMgr=%NETWORK_ROOT%\Help\CustDocMgr.htm
Navigator=%NETWORK_ROOT%\Help\CustNavigator.htm
DataMgr=%NETWORK_ROOT%\Help\CustDataMgr.htm
Vision=%NETWORK_ROOT%\Help\CustVision.htm
SpecSht=%NETWORK_ROOT%\Help\CustSpecSht.htm
ProjEd=%NETWORK_ROOT%\Help\CustTProjEd.htm
ChgLogo=%NETWORK_ROOT%\Help\CustChgLogo.htm
CvrtProj=%NETWORK_ROOT%\Help\CustCnvrtPrj.htm
BatchPrint=%NETWORK_ROOT%\Help\CustBatchPrint.htm
BlkDataSht=%NETWORK_ROOT%\Help\CustBlkDataSht.htm
LayoutDsg=%NETWORK_ROOT%\Help\CustLayoutDsg.htm
SplitMergeProj=%NETWORK_ROOT%\Help\CustSplitMergeProj.htm
Hookup=%NETWORK_ROOT%\Help\CustHookup.htm
Appendix A
326
Apr-10
AT.ini
InstWir=%NETWORK_ROOT%\Help\CustInstWir.htm
DataSht=%NETWORK_ROOT%\Help\CustDatasht.htm
PID=%NETWORK_ROOT%\Help\CustPID.htm
[Navigator]
dialogLeft=576
dialogTop=300
dialogWidth=10824
dialogHeight=8064
PaneWidth=10728
PaneHeight=6784
LeftPane=900
RightPane=5616
TopPane=3300
BottomPane=1284
TopTab=0
LastTreeTab=2
LastFindType=1
AreaDisplay=1
UnitDisplay=0
DocDisplay=1
UserDisplay=0
AssocDoc1=2167.37
Apr-10
327
Appendix A
AT.ini
AssocDoc2=2167.37
AssocDoc3=2167.37
FloatingDwgDisplayTop=5700
FloatingDwgDisplayLeft=8676
FloatingDwgDisplayWidth=3516
FloatingDwgDisplayHeight=2964
MinimizeOnEdit=0
[MSDE]
INSTANCE_LOGIN=sa|*1>V9@1!:
[Packager]
DataTypes=%Local_Root%\Packager\Datatypes.xml
Logfiles=%Local_Root%\Packager\LogFiles
[Project Administrator]
PROGRAMDIR=%NETWORK_ROOT%\Bin
STARTUP_FILE=ProjectAdministrator.exe
REGAPP=PA
[GENERAL_2D]
HELP_FILE=%NETWORK_ROOT%\Help\aplant2d.chm
[DocViewer]
FILETYPES=DWG;DGN;TXT;DOC;XLS;PDF;JPG;GIF;BMP;EBS;
Appendix A
328
Apr-10
AT.ini
Default-Viewer=INTERNAL
[I&W]
AutoGenPDF=0
REGAPP=I&W
AcadCmdLine=
DESCRIPTION=Instrumentation & Wiring
[P&ID]
STARTUP_FILE=ap.lsp
DESCRIPTION=AutoPLANT P&ID
REGAPP=AT_PID
MENU_SELECTABLE=1
HELP_FILE=%NETWORK_ROOT%\Help\at_pid.chm
BASE_MENU=acad.mnu
APP_MENU_POS=10
CONTEXTMENU=%LOCAL_ROOT%\P&ID\context.mnu
CONVERSIONMENU=T
SymbolManager=1
SymbolManDoubleClick=1
Apr-10
329
Appendix A
AT.ini

Data\Bentley\Plant V8i\AutoPLANT_PID811ACAD_6001_409.arg"
MENUMODE=1
ValveSpecMode=1
ValveSpecSelectBefore=1
ValveSpecPath=C:\Bentley Training Project\Training\Specs
VALVESPECCONF=specconf.ini
VALVESPECCONFPATH=
ValveTagVisible=1
[Electrics]
STARTUP_FILE=ap.lsp
DESCRIPTION=AutoPLANT Electrics
REGAPP=AT_ELC
BASE_MENU=acad.mnu
APP_MENU_POS=10
CONTEXTMENU=%LOCAL_ROOT%\P&ID\context.mnu
Data\Bentley\Plant V8i\AutoPLANT_PID811ACAD_6001_409.arg"
[P&ID Assembly Manager]
Mode=Default
Appendix A
330
Apr-10
AT.ini
INSTRUMENTS=0:0
AT_INST_=0:0
EQUIPMENT=0:0
AT_EQDRM=0:0
AT_EQEXC=0:0
AT_EQPMP=0:0
AT_EQTNK=0:0
AT_CVALVE=0:0
PROCESS=0:0
AT_PROCESS=0:0
VALVES=0:0
AT_HVALVE=0:0
MISCELLANEOUS=0:0*
AT_PID_NOZZLE=0:0
DocPrefix=
DocSuffix=
tv:LastNode=Training Level Gauge
tvProj:LastNode=JUNKASSY1
AT_EQTWR=0:0
AT_INST_ORF=0:0
AT_INST_FLO=0:0
AT_PSV=0:0
Apr-10
331
Appendix A
AT.ini
[AT_ASI_CONTEXT_MENUS]
AT_TIEIN=AT_TIEIN
AT_SPEC_ITEM=AT_SPEC_ITEM
AT_PID_NOZZLE=AT_PID_NOZZLE
[AssocDocFilters]
Key1=Doc_name like "PID*"
Key2=Doc_type = "DWG"
Key3=Owner like "Supervisor"
Key4=Doc_name like "PID*" or Doc_name like "A*"
LastFilter=Doc_name like "PID*"
[PIPING]
DESCRIPTION=AutoPlant Piping
LOCALDIR=%LOCAL_ROOT%\PIPING
MENU_SELECTABLE=1
PROGRAMDIR=%NETWORK_ROOT%\PIPING
REGAPP=AT_PIPE
STARTUP_FILE=at_pipe.lsp
STARTUP_FUNC=at_pipe_startup
UNLOAD_FUNC=at_pipe_unload
Appendix A
332
Apr-10
AT.ini

Data\Bentley\Plant V8i\AutoPLANT_PDW811ACAD_6001_409.arg" /b loadpiping
[ISOMETRICS]
DESCRIPTION=AutoPlant Isometrics
LOCALDIR=%LOCAL_ROOT%\iso
MENU_SELECTABLE=1
PROGRAMDIR=%NETWORK_ROOT%\iso
REGAPP=AT_ISO
STARTUP_FILE=at_iso.lsp
STARTUP_FUNC=at_iso_startup
UNLOAD_FUNC=at_iso_unload
Data\Bentley\Plant V8i\AutoPLANT_PDWISO811ACAD_6001_409.arg" /b loadiso
[AUTO-ISO]
DESCRIPTION=Auto-Iso
LOCALDIR=%LOCAL_ROOT%\iso
MENU_SELECTABLE=1
Apr-10
333
Appendix A
AT.ini
PROGRAMDIR=%NETWORK_ROOT%\iso
REGAPP=at_aiso
STARTUP_FILE=at_aiso.lsp
STARTUP_FUNC=at_aiso_startup
UNLOAD_FUNC=at_aiso_unload
[CE]
PROGRAMDIR=%NETWORK_ROOT%\Bin
SCRIPTEDITOR=C:\Program Files\Bentley\Plant V8i\BIN\ebs_edit.exe
SCRIPTEDITORPARMS=%s
STARTUP_FILE=APClassEditor.exe
[MODELREVIEW]
PROGRAMDIR=%NETWORK_ROOT%\Support
STARTUP_FILE=bmodrev.lsp
STARTUP_FUNC=bmodrev_startup
DESCRIPTION=Bentley Model Review
[TRANSLATOR]
DESCRIPTION=Translator
LOCALDIR=%LOCAL_ROOT%\XCHG
MENU_SELECTABLE=1
PROGRAMDIR=%NETWORK_ROOT%\XCHG
Appendix A
334
Apr-10
AT.ini
REGAPP=at_xchg
STARTUP_FILE=at_xchg.lsp
STARTUP_FUNC=at_xchg_startup
UNLOAD_FUNC=at_xchg_unload
USER_PREF_INI_FILE=userPref
[ELECTRICAL]
DESCRIPTION=Raceways
LOCALDIR=%LOCAL_ROOT%\elect
MENU_SELECTABLE=1
PROGRAMDIR=%NETWORK_ROOT%\elect
REGAPP=AT_ELECT
STARTUP_FILE=at_elect.lsp
STARTUP_FUNC=at_elect_startup
UNLOAD_FUNC=at_elect_unload
Data\Bentley\Plant V8i\AutoPLANT_PDW811ACAD_6001_409.arg" /b
loadraceways
[2DPIPING]
Apr-10
335
Appendix A
AT.ini
[Document Manager]
dialogLeft=-60
dialogTop=-60
dialogWidth=21720
dialogHeight=13170
PaneWidth=21600
PaneHeight=11740
LeftPane=2415
RightPane=14955
TopPane=7605
BottomPane=1920
TopTab=0
LastTreeTab=2
LastFindType=2
AreaDisplay=1
UnitDisplay=0
DocDisplay=1
UserDisplay=0
AssocDoc1=2167.37
AssocDoc2=2167.37
AssocDoc3=2167.37
Appendix A
336
Apr-10
AT.ini
LastDocumentOpened=
LastFolderOpened=
MinimizeOnEdit=0
FloatingDwgDisplay=0
[TOOLS]
REGAPP=AT_TOOLS
AcadCmdLine=
DESCRIPTION=Knowledge Manager
[PDF]
REGAPP=PDF
AcadCmdLine=
DESCRIPTION=Generated PDF Report
[APIPE]
REGAPP=APIPE
AcadCmdLine=
DESCRIPTION=AutoPIPE
[JSM]
REGAPP=JSM
AcadCmdLine=
DESCRIPTION=JSpace Model Files
[PSPID]
Apr-10
337
Appendix A
AT.ini
REGAPP=PSPID
AcadCmdLine=
DESCRIPTION=PlantSpace P&ID
[PSPIPE]
REGAPP=PSPIPE
AcadCmdLine=
DESCRIPTION=PlantSpace Pipe
[PSEQP]
REGAPP=PSEQP
AcadCmdLine=
DESCRIPTION=PlantSpace Equipment
[UNKNOWN]
REGAPP=AT_UNKNOWN
AcadCmdLine=
DESCRIPTION=AT_UNKNOWN
[COMP-DRAW]
REGAPP=COMP-DRAW
Data\Bentley\Plant V8i\AutoPLANT_PDW811ACAD_6001_409.arg" /b loadequip
loadpiping
DESCRIPTION=Composite Drawing
[ToolTipDisplay]
Delimiter=-
Appendix A
338
Apr-10
AT.ini
EQUIP=TAG_NO,EDESC
PROCESS=TAG_NO
Brackets=[]
[NEW]
REGAPP=AT_NEW
DESCRIPTION=Junk
[TEST]
REGAPP=AT_TEST
DESCRIPTION=junk1
[ProjectDB]
MSGBOXDEBUG=0
[DOCUMENTSELECTION]
ALL_COLUMNS=DOC_ID;TAG_TYPE;TAG_CODE;DOC_NAME;DOC_DESC;DOC_FN
AME;ALT_NAME;LOCATION;AREA;SHEET_NO;OF_SHEET;APPROVEDBY;DOC_TYP
E;TEMPLATE;REGAPP;DWG_STAT;REGEN_FLAG;LASTUPDATE;AUTOTAG_ON;JOIN
KEYTAG;JOINPARAM;OWNER;ARCHIVENUMBER;USERDEFINED1;USERDEFINED2;
USERDEFINED3;USERDEFINED4;USERDEFINED5;TITLE1;TITLE2;TITLE3;LOCKED;NO
TES;FOLDER;PREV_TAG;PROJ_STAT;CREATE_TM;LAST_MOD;TAGINSERT;REV;CO
MP_ID;DCM_ID;PWV_ID;DOC_IDCODE;SKETCH;
SELECTED_COLUMNS=DOC_ID;DOC_NAME;LOCATION
[HKUPS]
REGAPP=HKUPS
Apr-10
339
Appendix A
AT.ini
AcadCmdLine=
DESCRIPTION=Hookups
[ORTP]
REGAPP=AT_ORTP
DESCRIPTION=Ortho Drawings
[TagBrowse]
Key1='PID*'
Key2='PID-1'
Key3='*1*'
LastFilter='PID*'
[PIDANNO-AT_PIPERUN]
ANNO0=(STRCAT PSZ_NOM "-" PSPEC_NOM "-" POPT "-" POPP )
ANNO1=
ANNO2=
ANNO3=
ANNO4=
[P&IDEquipNoz]
AT_EQPMP=1
[UPDATE]
AP_UPDATE_LAST=rebis
Appendix A
340
Apr-10
AT.ini
[PROCAD]
REGAPP=PROCAD
Data\Bentley\Plant V8i\AutoPLANT_PDW811ACAD_6001_409.arg"
DESCRIPTION=ProCAD
[DSHEET]
REGAPP=DSHEET
AcadCmdLine=
DESCRIPTION=Data Sheets
[ProjectAdministrator]
DS_IMPORT_RANGE=A1:AZ300
[DOCKSETTINGSR17]
APPrefSelectAN17.ComponentPreferences=1
Apr-10
341
Appendix A
SQL Project.ini
SQL Project.ini
[GENERAL]
APPLICATIONS=DOCMANAGER;PIPING;ISOMETRICS;ELECTRICAL;EQUIP;2DPIPING
;FLATTENER;VISION;NAVIGATOR;DATAMANAGER;HOOKUPS;I&W;INSTRUMENTA
TION;DATASHEETS;TEMPLATEGEN;P&ID;STRUCTURAL;
TagNumPrefix=000
ProjectName=Intel_project
ProjectNumber=
ProjectDescript=Intel_project
ClientName=
ClientNumber=
ClientLoc=
ContractorName=
ContractorNumber=
ContractorLoc=
ProjectID=0001
ProjectGUID={2113AD14-F31D-4407-8BFF-FF2F50AEA143}
SharedSchema=0
SharedStandards=0
[PATHS]
Appendix A
342
Apr-10
SQL Project.ini
Standards=j:\Common_Directories\Standards\
Reports=Reports\
APCUSTDIR=j:\Common_Directories\APCUSTDIR\
EleDrawings=EleDrawings\
EleSymbols=Standards\Electrical\Symbols\
InsDrawings=InsDrawings\
InsSymbols=Standards\Instrumentation\Symbols\
CardSymbols=Standards\Instrumentation\Symbols\
TermSymbols=Standards\Instrumentation\Symbols\TermDWG\
ELECT_DWG=ELECT_DWG\
DataSheets=DataSheets\
Specifications=Specifications\
Hookups=Hookups\
P&ID_Assemblies=Standards\P&ID\Assemblies\
PID_DWG=PID_DWG\
PIPE_DWG=PIPE_DWG\
ISO_DWG=ISO_DWG\
EQP_DWG=EQP_DWG\
STRUCT_DWG=STRUCT_DWG\
[PROVIDERS]
Projdata=SQLOLEDB.1
Apr-10
343
Appendix A
SQL Project.ini
Schema=SQLOLEDB.1
[DATA SOURCES]
Projdata =DRIVER={SQL Server};SERVER=%s;UID=%s;PWD=%s;DATABASE=%s
Schema =DRIVER={SQL Server};SERVER=%s;UID=%s;PWD=%s;DATABASE=%s
ModelDB =Dsn=MS Access for AutoPLANT;DBQ=%s
SpecDB =Dsn=MS Access for AutoPLANT;DBQ=%s
Report =Dsn=MS Access for AutoPLANT;DBQ=%s
[DATABASES]
Projdata=Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=Intel_project;Data Source=.
;For SQL Server
Schema=Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=Intel_project;Data Source=.
[Modeller]
WorkDBExtension
EscalateDelay
=0
MaxConnections
Appendix A
= MDB
= 50
CleanState
= 10
WorkDir
= DbWork
344
Apr-10
SQL Project.ini
CompactDir
= DbCompact
CompactExt
= MDX
[Templates]
CABFLL_M=22.50
CABFLL_I=0.9
CABFLW_M=5.00
CABFLW_I=0.20
Standard=METRIC
USEDIALOG=FALSE
CoreLinetype = SOLID
CableLineweight_Imperial = 0.125
CableLineweight_Metric = 0.125
JumperLinetype = SOLID
JumperLineweight_Imperial = 0.125
JumperLineweight_Metric = 0.125
JumperLineSpacing_X_Imperial = 0.041
JumperLineSpacing_Y_Imperial = 0.041
JumperLineSpacing_X_Metric = 0.041
JumperLineSpacing_Y_Metric = 0.041
JumperLineSpacingxl_X = 5
Apr-10
345
Appendix A
SQL Project.ini
JumperLineSpacingxl_Y = 5
ShowJumpers=1
dwgtemplatedirection= NORMAL
ShowJumperLabels=FALSE
CableOffset_Termcon_Imperial = 0.25
CableOffset_Termcon_Metric = 0.25
CableOffset_LoopCon_Imperial = 0.25
CableOffset_LoopCon_Metric = 0.25
coreOffset_Termcon_Imperial= 0.75
coreOffset_Termcon_Metric = 0.75
coreOffset_LoopCon_Imperial = 0.75
coreOffset_LoopCon_Metric = 0.75
MakeSingleInstrBlock =FALSE
ForceAlign=TRUE
TraverseOppositeSide=TRUE
HeaderGap = 2
HideDuplicateCableHeaders=TRUE
[DCW_Settings]
CableLineweight = 1
Appendix A
346
Apr-10
SQL Project.ini
JumperLineweight = 1
JumperLineSpacing_X = 90
JumperLineSpacing_Y = 90
ShowJumpers=1
cableoffset = 400
coreoffset=800
HideDuplicateCableHeaders=TRUE
[IWUISETTINGS]
CARDEDITDEFFIELDS
=IOLIST_ID,TERMSET,IO_TYPE,CHNL,ADDRESS,TAG_NO,DESCRIPT
cardeditcurrfields
=IOLIST_ID,TERMSET,IO_TYPE,CHNL,ADDRESS,TAG_NO,DESCRIPT,REV
JSETTINGS=LL1=1;LL2=-1;LL3=-1;LL4=-1;LL5=-1;LL6=1;RL1=1;RL2=1;RL3=1;RL4=1;RL5=1;RL6=-1
DefaultTermSymbol ="Tstrip1.dwg"
[DATASHEETS]
RevisionControl=1
TagFilterList=TRUS200-E-*;**;*;_________________________;
DocFilterList=XD900E01.XLS;*.XLS;*.XLS;*.*;_________________________;
Apr-10
347
Appendix A
Oracle Project.ini
Oracle Project.ini
[GENERAL]
TagNumPrefix=000
ProjectName=APPROJ22
ProjectNumber=12345
ProjectDescript=APPROJ22
ClientName=
ClientNumber=
ClientLoc=
ContractorName=
ContractorNumber=
ContractorLoc=
ProjectID=0001
ProjectGUID={210D3428-70CC-40BB-AEDF-82E8CBDDEB69}
SharedSchema=0
SharedStandards=0
IsProjectVersion893=1
IWUSELASTIDONLY=0
Appendix A
348
Apr-10
Oracle Project.ini
[PATHS]
Standards=Standards\
Reports=Reports\
EleDrawings=Electrical\Drawings\
InsDrawings=Instrumentation\Drawings\
ELECT_DWG=Raceways\Drawings\
Specifications=DataSheets\Specifications\
Hookups=Hookups\
PID_DWG=P&ID\Drawings\
PIPE_DWG=Piping\Drawings\
ISO_DWG=Iso\Drawings\
EQP_DWG=Equip\Drawings\
STRUCT_DWG=Struct\Drawings\
[PROVIDERS]
Apr-10
349
Appendix A
Oracle Project.ini
Projdata=OraOLEDB.Oracle.1
[DATA SOURCES]
Projdata =DRIVER={Oracle ODBC Driver};DBQ=%s;UID=%s;PWD=%s
Schema =DSN=MS Access for AutoPLANT;DBQ=%s
[DATABASES]
Projdata=Password=bentley;Persist Security Info=True;User ID=approj22;Data
Source=appw
;For SQL Server
[Modeller]
WorkDBExtension
EscalateDelay
MaxConnections
CleanState
Appendix A
= MDB
=0
= 50
= 10
350
Apr-10
Oracle Project.ini
WorkDir
= DbWork
CompactDir
= DbCompact
CompactExt
= MDX
[Templates]
CABFLL_M=22.50
CABFLL_I=0.9
CABFLW_M=5.00
CABFLW_I=0.20
Standard=METRIC
USEDIALOG=FALSE
Apr-10
351
Appendix A
Oracle Project.ini
ShowJumpers=1
ForceAlign=TRUE
HeaderGap = 2
HideDuplicateCableHeaders=FALSE
BlocksPlacementOrderFromTop=TRUE
COMPOSITEDRAWINGTAGTYPES=AT_MUX_TSTRIP
COMPOSITEDRAWINGSYMBOLTOKENNAME=INSPOINT
Appendix A
352
Apr-10
Oracle Project.ini
[DCW_Settings]
CableLineweight = 1
ShowJumpers=1
cableoffset = 0.05
coreoffset=0.9
ShowFerrule=FALSE
BlocksPlacementOrderFromTop=TRUE
[IWUISETTINGS]
CARDEDITDEFFIELDS
cardeditcurrfields
Apr-10
353
Appendix A
Oracle Project.ini
MAXFFInstrLimit=255
ALL_SORTCOL=0
ALL_SORTORDERDESC=FALSE
TSTRIP_SORTCOL=0
TSTRIP_SORTORDERDESC=FALSE
DOC_REG_SORTCOL=0
DOC_REG_SORTORDERDESC=FALSE
LLabel=1
RLabel=1
CARDSORTFIELD=CHNL
CARD_SORTCOL=0
CARD_SORTORDERDESC=FALSE
CABLE_SORTCOL=0
CABLE_SORTORDERDESC=FALSE
AllocateLoopNumberExpression=
INSTR_SORTCOL=0
INSTR_SORTORDERDESC=FALSE
CARDPORTEDITDEFFIELDS=PORT_ID,TERMSET,IO_TYPE,PORT_NO,IP_ADDRESS,C
OMMENTS,REV,NODE,NETWORK
Appendix A
354
Apr-10
Oracle Project.ini
cardporteditcurrfields=PORT_ID,TERMSET,IO_TYPE,PORT_NO,IP_ADDRESS,COM
MENTS,REV,NODE,NETWORK
CARDPORTSORTFIELD=PORT_NO
LOOP_SORTCOL=0
LOOP_SORTORDERDESC=FALSE
[SplitMerge]
Triggers=True
[Vision]
ArchiveSwitch=0
[DATASHEETS]
RevisionControl=1
Apr-10
355
Appendix A
Access Project.ini
Access Project.ini
[GENERAL]
TagNumPrefix=000
ProjectName=Training
ProjectNumber=159
ProjectDescript=Imperial Training Project
ClientName=Bentley
ClientNumber=1
ClientLoc=Exton, PA
ContractorName=
ContractorNumber=
ContractorLoc=
ProjectID=0001
ProjectGUID={680DEE8C-B74F-4D87-A05A-C722C923C094}
SharedSchema=0
SharedStandards=0
[PATHS]
Appendix A
356
Apr-10
Access Project.ini
Standards=Standards\
Reports=Reports\
EleDrawings=Electrical\Drawings\
InsDrawings=Instrumentation\Drawings\
ELECT_DWG=Raceways\Drawings\
Specifications=DataSheets\Specifications\
Hookups=Hookups\
PID_DWG=P&ID\Drawings\
PIPE_DWG=Piping\Drawings\
ISO_DWG=Iso\Drawings\
EQP_DWG=Equip\Drawings\
STRUCT_DWG=Struct\Drawings\
ALIAS0=%LOCAL_ROOT%\Reports\
REFPATH1=C:\Bentley Training Project\Training\Supplemental\
DSHEET_0=Datasheets\Instr\
Apr-10
357
Appendix A
Access Project.ini
[PROVIDERS]
Projdata=Microsoft.Jet.OLEDB.4.0
[DATA SOURCES]
Projdata =DSN=MS Access for AutoPLANT;DBQ=%s
Schema =DSN=MS Access for AutoPLANT;DBQ=%s
[DATABASES]
Projdata=%ProjPath%\PROJDATA\PROJDATA.MDB
;For SQL Server
[Modeller]
WorkDBExtension
EscalateDelay
MaxConnections
CleanState
Appendix A
= MDB
=0
= 50
= 10
358
Apr-10
Access Project.ini
WorkDir
= DbWork
CompactDir
= DbCompact
CompactExt
= MDX
[Templates]
CABFLL_M=22.50
CABFLL_I=0.9
CABFLW_M=5.00
CABFLW_I=0.20
Standard=METRIC
USEDIALOG=FALSE
Apr-10
359
Appendix A
Access Project.ini
ShowJumpers=1
ForceAlign=TRUE
HeaderGap = 2
[DCW_Settings]
CableLineweight = 1
Appendix A
360
Apr-10
Access Project.ini
ShowJumpers=1
cableoffset = 400
coreoffset=800
[IWUISETTINGS]
CARDEDITDEFFIELDS
cardeditcurrfields
MAXFFInstrLimit=255
[Vision]
Apr-10
361
Appendix A
Access Project.ini
ArchiveSwitch=0
[DATASHEETS]
RevisionControl=1
TagFilterList=P-*;*P*;*;_________________________;
DocFilterList=;P*.XLS;*.XLS;*.*;_________________________;
Appendix A
362
Apr-10
Course Summary
Course Summary
You have now completed an extensive course on the Bentley 2D and 3D software.
You should now be able to determine what type of project database will fit your
needs, how to customize the tables and view of that project, and how to use the
tools provided to manipulate your project.
Now you will be able to:
Apr-10
Setup a new project.
Configure a project.
Manage a project.
Package a project.
Create custom views and reports.
Import existing Datasheets.
Add new applications to a project.
363
Course Summary
Course Review
Course Review
Now that you have completed this course, lets measure what you have learned.
Questions
2 In what order must the software be installed?
3 List a few things that should be considered before starting a project.
4 What is the difference between the project's local and network
directories?
5 The Central Project Mode was designed for which database type?
6 Which project mode does Bentley recommend using?
7 Name the three types of 2D to 3D mappings available and give a
description of each.
8 True or False: The RebisPropertyDialog.vbp file contains the property
dialog.
9 Which application would be used to add a user to the current project?
10 In the Project.ini files, which section shows the database type being
utilized for the project?
11 What is the name of the document which shows the relationships of the
database tables?
12 Why are instruments and equipment tags stored in separate locations?
13 Which database table holds the view definitions and in which database
does this table reside?
14 Why would you package a working project?
15 Why would you split a project?
16 Which tool would you use if you needed to compare the 2D documents
and 3D documents of a project?
17 Which application is used to update a Bentley report?
18 Can you use your existing company datasheets in a Bentley project?
19 How does the software determine what information has been modified
on a datasheet?
20 Can you associate an external document to a component?
Course Summary
364
Apr-10
Course Review
21 Can you modify the software so that it will open file types that are not
standard within the Bentley file structure?
Apr-10
365
Course Summary
Course Review
Answers
1 The software must be installed in the following order: AutoPLANT P&ID,
Bentley Process and Instrumentation and Bentley Plant Design.
2 Three things which should be considered before starting a project are:
personnel training, CAD standards, and customization needs. You should
also consider which software, type of installation, and type of project
database you will need.
3 Local directories are located in C:\Documents and Settings\All
Users\Application Data\Bentley\Plant V8i and contain machine-specific
files. The Network directories contain the executables needed to run the
software and must be accessible by each workstation.
4 The Central Project Mode was designed for the Access database type but
is available for MSDE, SQL and Oracle.
5 Bentley strongly recommends using the Central Project Mode.
6 The three types of mapping available are: Class mapping, Tag Type
mapping and Field mappings. Class mapping uses the XXCLASSMAP tables
for 3D items and the settings.dbf for 2D items. Tag Type mapping uses the
ValueMap2D3D table and the settings.dbf to compare tag types within the
two applications. The Field mapping compares the data stored in the
Fieldmap2d3d table.
7 False: The file containing the property dialog definitions is called the
RebisComponentDialogs.vbp.
8 The Project Administrator project tool would be used to add a user to the
current project.
9 The [Providers] section of the Project.ini file will list the database type
being utilized.
10 The ER Diagram is the document which graphically shows the
relationships between the database tables.
11 The instruments utilize the INSTR table with a self-contained keytag to
store tag numbers, while the equipment tags are stored in the TAG_REG
table and linked by the keytag to the EQUIP table.
12 The RebisView table contains the view definitions. It is found in the
Schema database.
13 You would package a working project if you needed to move its location
from one server to another, or if you needed to send the project to a third
party.
Course Summary
366
Apr-10
Course Review
14 You would split a project if you want a third party to work on a section of
the project, but not the entire project. Utilizing this tool would allow you
to send the third party the affected documents. They could be updated
and additional documents added and brought back into the parent
project. All of the modified or new tags will be added to the project
database.
15 To compare 2D and 3D documents you would use the 2D to 3D
Consistency Checker.
16 Bentley reports can be updated with the Access report writer.
17 Yes, you can use your existing company datasheets in a Bentley project by
mapping the cells of the datasheet and then importing it into the project.
18 When a datasheet is closed, the Resolve Differences dialog will open
showing the changes between the datasheet and the database. At that
time, you can select which data is correct and save.
19 Yes, using the Vision application you can associate any document to a
component.
20 Yes, you can add external file types to your project structure.
Apr-10
367
Course Summary
Course Review
Course Summary
368
Apr-10

Bentley AutoPlant Project Configuration V8i SS1 PDF

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Bentley AutoPlant Project Configuration V8i SS1 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

AutoPLANT Project Configuration

Bentley Institute Course Guide

AutoPLANT Project Configuration

Copyright 2010 Bentley Systems, Incorporated

Introduction to Project Setup __________________________ 9

Bentley PLANT Training AutoPLANT Project Configuration

Project Information __________________________________ 29

Bentley PLANT Training AutoPLANT Project Configuration

Bentley AutoPLANT 2D Applications____________________67

Configuring the Project Database ______________________ 75

Bentley PLANT Training AutoPLANT Project Configuration

Managing Projects __________________________________ 147

Examining the Project Databases _______________________ 161

Project Utilities _____________________________________ 185

Bentley PLANT Training AutoPLANT Project Configuration

Module Review _______________________________________221

Project Organization _________________________________ 223

Data Manager Customization __________________________ 239

Datasheets Customization ____________________________ 265

Bentley PLANT Training AutoPLANT Project Configuration

Understanding Datasheets Structure ______________________266

Vision Customization ________________________________ 295

Project Template Creation ____________________________ 311

Appendix A ________________________________________ 319

Bentley PLANT Training AutoPLANT Project Configuration

Course Summary ____________________________________ 363

Bentley PLANT Training AutoPLANT Project Configuration

Bentley PLANT Training AutoPLANT Project Configuration

Project Administrators with experience in either our 2D applications or our 3D

Completion of either the 2D or 3D Fundamentals courses

Working knowledge of databases

Working knowledge of Microsoft Access report writer

Setup a new project.

Create custom views and reports.

Import existing Datasheets.

Add new applications to a project.

Create a new custom project.

Introduction to Project Setup Administrator

Configuring the Project Database

Copyright 2010 Bentley Systems, Incorporated

Examining the Project Databases

Data Manager Customization

Project Template Creation

Intel Pentium 4 processor and AMD Athlon,

Microsoft Windows XP Professional SP2 or

Microsoft Internet Explorer 6 SP1 or greater

2GB free hard disk space

Industry-standard input device supported by

Industry-standard input device supported by

Video Graphics Card:

Industry-standard video card/monitor

Intel Pentium 4 processor and AMD Athlon,

Copyright 2010 Bentley Systems, Incorporated

AutoCAD or related Autodesk Products

AutoCAD or related Autodesk Products

2006, 2007, 2008 (32 bit only), 2009 (32 bit

ProjectWise Supported Versions

2005 Express Edition, 2005 Express Edition with

Oracle 9i Release 2, Oracle 10g Release 2,

Program Software Loading Sequence

Bentley Process and Instrumentation

AutoPLANT Plant Design