PDS Express Project Creation

Plant Design System
Express Project Creation
Version 2011 (V12)

June 2011
DPDS3-PE-200016G
Copyright
Copyright 1984-2011 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement;
contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade
secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from
Intergraph Corporation.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of
the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless
the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed
license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use
of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives
licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement
and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for
resale or redistribution.
Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software
or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this
document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes
the information in this publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the
terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not
supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks
of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered
trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle
Corporation and/or its affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands
and product names are trademarks of their respective owners.
Contents
Preface .......................................................................................................................................................... 5
Getting Started ............................................................................................................................................. 7
Project Setup Overview .......................................................................................................................... 7
Before You Begin .................................................................................................................................... 7
Starting the Program ............................................................................................................................... 8
New User Mode ................................................................................................................................ 8
Advanced User Mode ....................................................................................................................... 9
Creating a Standard Project ..................................................................................................................... 11
How to Use the New User Option ......................................................................................................... 11
Creating a Customized Project ................................................................................................................ 19
How to Use the Advanced User Option ................................................................................................ 19
Understanding the express.txt File ......................................................................................................... 31
Seed Data ............................................................................................................................................. 32
Default File Locations ........................................................................................................................... 33
RDB Libraries ........................................................................................................................................ 34
Drawing Cell Libraries ........................................................................................................................... 36
2D Reference Data ............................................................................................................................... 36
The express.txt File ................................................................................................................................... 37
Sample Data ............................................................................................................................................... 71
Information in the Delivered Dataset..................................................................................................... 71
P&ID Assemblies .................................................................................................................................. 72
Delivered SQL Scripts ............................................................................................................................... 73
Project Options .......................................................................................................................................... 75
Define Project Data ............................................................................................................................... 76
Define System Units ............................................................................................................................. 76
Create Database Schemas ................................................................................................................... 76
Express Project Creation ...................................................................................................................... 77
Server Names & Drive Letters ........................................................................................................ 77
Define RDB File Locations ............................................................................................................. 77
Create FrameWorks Sub-Project .......................................................................................................... 78
Revise Working Units ............................................................................................................................ 78
Database Customization Options ......................................................................................................... 80
Database Structure Revision ................................................................................................................ 80
Define Location for New RDB ............................................................................................................... 82
Define 2D Reference Data Locations ................................................................................................... 82
Copy 3D RDB to New Project ............................................................................................................... 83
Copy Files to Project Directory ............................................................................................................. 83
Plant Design System Express Project Creation
Contents
Define Default Miscellaneous File Locations ........................................................................................ 84
Index ........................................................................................................................................................... 85
Preface
Creating a new PDS project includes many distinct tasks that can be difficult to remember from
one project to the next, particularly if you do not frequently create new projects. Intergraph
provides a utility called Express Project Creation, which automates most of the steps needed to
create a project. This document describes how to use Express Project Creation to set up both
standard and customized projects.
This document provides only a general description of project setup. For example, adding 3D
project data to an existing 2D project or adding structural data to a project after it was created
cannot be done using Express Project Creation. Procedures of this nature are described in the
PDS Project Setup Technical Reference and the PDS Project Administrator (PD_Project)
Reference Guide.
Related Documents
For more information on related topics, see the following documents:
PDS 2D RDB Administrator User's Guide
Project Administrator (PD_Project) Reference Guide
Reference Data Manager (PD_Data) Reference Guide
Getting Started in PDS 2D
PDS 2D RDB Administrator Reference Guide
PDS Project Setup Technical Reference
What's in This Document

This document contains the following chapters:
Chapter 1 - Getting Started -- This chapter provided an overview of the workflow for setting up
a project and describes how the Express Project Creation program fits into this workflow.
Chapter 2 - Creating a Standard Project -- This chapter describes how to use the New User
option to create a project that uses a standard directory structure.
Chapter 3 - Creating a Customized Project -- This chapter describes how to use the
Advanced User option to create a customized project.
Chapter 4 - Understanding the express.txt File -- This chapter describes how to edit the
express.txt file to further streamline your project creation workflow.
Appendix A - The express.txt File -- This appendix lists the complete express.txt file that is
delivered with the product.
Appendix B - Sample Data -- This appendix describes the sample data that is available with
the New User option.
Appendix C - Delivered SQL Scripts -- This appendix describes the SQL scripts that are
delivered with the PD_Shell product.
Preface
SECTION 1
Getting Started
The Express Project Creation program is a new feature that enables you to easily create
projects using a predefined structure. Express Project Creation consists of two modes of
operation --- New User and Advanced User. The Advanced User mode allows customization
of the directory structure and distribution of the project files across multiple nodes.
Express Project Creation is available only on Windows-based computers.
Project Setup Overview

A project is a convenient grouping of either all or part of the items that constitute a plant. The
project is the fundamental structure for working in PDS. Each project contains all of the
information that is required to work in a PDS task. A project and all of its accompanying files
must be defined before you can use any of the other PDS modules.
Setting up a project consists of the following steps:
1. Install the products. In addition to the operating system software, PDS requires that you
have MicroStation, RIS, and a relational database set up. For information on installing
software, see the PDS Project Setup Technical Reference. Also, refer to the PD_Shell
README.TXT file for information on product dependencies.
2. Configure the system. This step includes setting up domain logins and setting up the
networking environment. For information on system configuration, see the PDS Project
Setup Technical Reference.
3. Create project databases. The PD_Shell product includes scripts that automate the
creation of the PDS databases for a number of database systems. These are located in the
pdshell\sqls\ directory.
4. Create the project. Start the Express Project Creation, and follow the steps outlined in the
following chapters of this document.
5. Define the reference data. Before you can begin working in your project, you must set up
the reference data. This involves loading ASCII files that define components and
specifications into the appropriate databases. These procedures are described in the PDS
Project Setup Technical Reference and the PDS Reference Data Manager (PD_Data)
Reference Guide.
Before You Begin

Before you can create a project, you must have first configured your system and installed the
software. You will also need to create databases for each module of the PDS software to be
used by your project. For example, for a project that will use the piping and equipment modules,
you will need to create the project, design, and approved reference databases.
For Express Project Creation, you will need to have SmartPlant License Manager and PD_Shell
installed locally. (That is, they must be installed on the computer from which you plan to run the
Express Project Creation program.)
For New User mode, you will also need to have PD_Project, PD_Draw, PD_Data, PD_Eqp, and
RD_USRDB or RD_DINRDB installed locally on the same disk partition. (A local installation
means that the products are installed on the computer from which Express Project Creation is
Getting Started
being run.) If the project will include both 2D and 3D data, the PDS2D software will also need to
be installed locally. You will also need to install EE Raceway and FrameWorks Plus if your
project will include these disciplines.
If you are running Express Project Creation in Advanced User mode, you only need to have
SmartPlant License Manager and PD_Shell installed locally. You can specify remote nodes
where the other PDS modules have been loaded as a source location for the required libraries.
Starting the Program

To start the Express Project Creation program, double-click the Express Project Creation icon,
which is located in the PD_Shell program group.
The Project Options form is displayed.
Two modes are available for creating projects: New User and Advanced User.
New User Mode

With New User mode, you can set up a project that follows a standard directory and database
structure. The New User mode is ideal when your setup from one project to the next is
consistent. This mode is the fastest way to set up a project, offering only minimal interaction
once the process is started. The New User mode also provides an option to load sample data
(models and drawings) into the created project. For information on creating a project using the
New User option, see Creating a Standard Project (on page 11).
Use New User mode when any of the following conditions are true:
Your project does not require a unique directory structure.
You do not need to customize the relational data during project creation.
You want to create a test or pilot project.
Getting Started
You want to load a delivered sample dataset while creating the project.
Advanced User Mode

With Advanced User mode, you can customize the project as you are creating it. Not only can
you specify a unique directory structure for the project files, but you can also have complete
control over the structure of the data within the database. For information on creating a project
using the Advanced User option, see Creating a Customized Project (on page 19) .
Use Advanced User mode when any of the following conditions are true:
Your project requires a unique directory structure.
You need to customize the relational data.
You want the ability to review and possibly change the settings read from the express.txt
file.
Getting Started
10
SECTION 2
Creating a Standard Project

The New User option enables you to create a project that follows a relatively simple, standard
structure. Projects that are created using this option have the following directory structure:
The system creates all the directories and subdirectories; you do not need to create the
directory structure beforehand.
Each time you create a project, the express.txt file that was used to create the project is copied
to the project directory. This enables you to keep a record of the specific parameters used for
creating that project.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus and Raceway seed files after creating the projects, and before
creating models.
How to Use the New User Option

To create a project using the New User option, follow these steps:
1. On the Project Options form, set the User Level to New User.
You are prompted to specify whether you want to load sample data.
2. Select Option
Choose Yes to load sample project data (a small project that already contains plant items,
such as piping, equipment, and so forth) or click No to create a project that does not include
sample data. If you choose Yes, the system loads a set of models and drawings into the
created project. Refer to Appendix B for a description of the delivered sample data.
If you load sample data, your plant monument is automatically set to 0,0,0.
The available project disciplines are displayed.

3. Select Disciplines
11

Select the disciplines that apply to your project. The available disciplines depend on the
software you have loaded on the computer from which the Express Project Creation was
started. These modules must be installed locally. Furthermore, they must all be installed on
the same drive letter.
4. Accept or Select Other Discipline

After you have selected all required disciplines, choose Confirm to continue.
12

The Define Project Data form is displayed.
5. On the Define Project Data form, key in the project number, project name, company name,
job number, and plant name in the related fields. This information is stored in the Project
Database and can be used in reports and other project documents. Also specify a design file
in which project interferences are to be written. The default file name is your project name
with .dgn appended to it. If your project includes a 2D discipline, key in a site name. The
default site name is plant_name-project number. You can change the default name if
needed. Be sure to press return as you enter information in each field.
The project number determines the base directory name and the default schema
names.
6. Accept or Provide Project Data
After you have specified all of the project data, choose Confirm to continue.
13

The Define System Units form is displayed.
7. Select Option
On the Define System Units form, select the system of units --- English or Metric --- to be
used for measuring distances in the model.
You are prompted to specify the diameter units to be used for fittings and components.
8. Select Option
Select the Nominal Pipe Diameter (NPD) units --- English or Metric --- to be used for
specifying pipe and fitting diameters in the model.
If you chose to load sample data, the selections for system of units will determine the
sample dataset to be loaded.
You are prompted to specify whether or not you want to have plant monument information
included in your project.
9. Select Option
Choose Yes to include Easting, Northing, or Elevation coordinates for the plant monument
when the project is created. The plant monument is the center of the design volume for the
plant; this point corresponds to the MicroStation position 0,0,0.
Fields are displayed that enable you to specify the coordinates of the plant monument.
OR
Choose No to create the project without this information.
10. Accept or Select Option
14

After you have provided the necessary information, choose Confirm to continue.
The Create Database Schemas form is displayed.
The selections that are available on this form vary depending on the disciplines chosen in
Step 3.
11. Select Schemas
On the Create Database Schemas form, specify the schemas to be created for your project.
All of the required schemas are automatically selected for you. With the piping approved
RDB schema and the EE RDB schema, you can choose to either create a new schema for
your project or to attach to an existing schema.
If you choose Use Existing Schema, a dialog box displays, which allows you to specify the
existing project, which contains reference data to share with the project being created.
Select the project from the displayed form, and choose Confirm to continue.
To create new schemas, select the Create New Schema option; then choose Confirm.
15

The Create Project Control Schema form is displayed.
12. The Create Project Control Schema form enables you to specify the parameters needed to
build the schemas for your project. The information to be provided varies depending on the
relational database being used. For each field, provide the following information:
Network Protocol - These fields indicate the types of network protocols used to access
the database. For most networks, you will use TCP. RIS uses the protocol at the top of
the list as its primary protocol.
Node Name or Address - Key in the computer name where the database is hosted,
then click Get Client Address.
Database Username and Password - For an Oracle database, key in the username
and password to access the project schema. This must be the same
username/password specified using the grant resource function. For MSSQL
databases, enter the MSSQL database user name and user name's password.
OS Type - Select the Windows NT option.
OS Username and Password - For an Oracle database, key in the username and
password to access the project schema. This must be the same username/password
specified using the grant resource function. For MSSQL, enter an adminstrator login.
Database Name - For Oracle, this is the SID name for the Oracle database. The SID
name is defined when the database is created. For MSSQL, this is the actual database
name.
Database Management System Location - Key in the directory path for the home
directory of the database product (for example, c:\oracle).
SQLEXEC - This field is no longer used.
DPTEMP - This field is no longer used.
TBCONFIG - This field is no longer used.
DSQUERY - For MSSQL, if you are using a database instance, enter the instance name
here. The instance name is the name that is displayed in Server Management Studio.
This name is typically of the format <machine name>\<instance name>.
SYBIFILE - This field is no longer used.
After you have specified all of the required information, click Apply.
16

The Create Project Control Schema form is dismissed, and the schema is created. If
additional schemas are to be created, you are returned to Step 12. Otherwise, the Server
Names & Drive Letters form is displayed.
13. On the Server Names & Drive Letters form, specify the node name of the file server on
which the project is to reside. For Windows, key in the drive letter only (for example, D,
without the colon). Be sure to press return to enter the data into each field.
If your server runs on Windows and you want to create the project at a top-level drive
(for example, c:\projname or e:\projname), you must first create a new share on the
server for that drive and specify just the drive letter as the new share name. This is
because the default Windows shares for the drive letters are available only to
administrators.
If you are running Express Project Creation on a client and specify that the project be
located on a server, both the client and server nodes must be running the same version
of Microstation. If the versions are different on the client and server, you will receive an
Error updating seed files at the end of setup.
14. Accept or Key in Data
After you have entered all of the node name and drive letter information, choose Confirm to
continue.
17

If your project includes structural data, the Create FrameWorks Sub-Project displays, and
you continue to Step 15. Otherwise, the project is created, and the program exits.
15. Key in Sub-Project Data

On the Create FrameWorks Sub-Project form, specify the project number, the project name,
the node name of the system and the directory on that system in which the FrameWorks
information is to be stored, the force units for the sub-project, and the name of the standard
section table. Be sure to press return to enter the information in each field.
When specifying the path, you must specify a full path name. Relative path names
are not valid input for this field. Also, note that the directories for the structural sub-project
are created such that the directory specified in the Sub-Project Number field is created as
a subdirectory of the directory specified in the Sub-Project Path field.
16. Accept or Modify Sub-Project Data
After you have specified all of the sub-project information, click Confirm to continue.
A dialog box is displayed indicating that the project was successfully created, and a log file
named express.log is written in the project directory. If there are severe errors during the
creation process, the system will try to clean up the database so that you can re-create the
project after resolving the errors.
No example specs are loaded for any of the sample projects. You must load specs in
the specifications/material reference database before you can work in the new project.
18
SECTION 3
Creating a Customized Project

The Advanced User option enables you to create a project with a customized database and/or
file structure. Not only does this option enable you to specify a unique directory structure for all
of the components that comprise a project, but it also enables you to customize working units,
specify whether to use DBAcess for reporting, define unique locations for RDB data source files,
and set up a project that shares or copies existing RDB data.
Like the New User mode, Advanced User mode automates much of the work involved in
setting up a project. But Advanced User mode differs from New User mode by allowing you to
specify project creation parameters in the express.txt file. Furthermore, Advanced User mode
enables you to confirm and modify these specifications interactively as the project is created.
Advanced User combines the flexibility of the Create Project option in the PD_Project
component with the convenience of a scripting file.
For information on editing the express.txt file before starting the Advanced User mode, see
Understanding the express.txt File.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus and Raceway seed files after creating the projects, and before
creating models.
How to Use the Advanced User Option

To create a project using the Advanced User option, follow these steps:
1. On the Project Options form, select Advanced User.
You are prompted to specify the name and location of the setup configuration file that is to
be used to create the project.
2. Key in ASCII File Name, Node, and Path
Key in the name of the scripting file (usually express.txt) to be used to create the project, the
node name of the computer on which the file is located, and the path to the file. Be sure to
press Enter to enter the information into each field.
The default file name is express.txt. The file is delivered to the pdshell\seedz
directory.
The available project disciplines are displayed.

3. Select Disciplines
Select the disciplines that apply to your project. The available disciplines depend on the
software you have loaded on the computer from which the Express Project Creation was
started. (These modules do not necessarily have to reside on the computer; they can be
installed in a client configuration.)
4. Accept or Select Other Discipline
After you have selected all required disciplines, choose Confirm to continue.
19

The Define Project Data form is displayed.
5. On the Define Project Data form, key in the project number, project name, company name,
job number, and plant name in the related fields. Also specify a design file in which project
interferences are to be written. The default file name is your project name with .dgn
appended to it. If your project includes a 2D discipline, key in a site name. The default site
name is plant_name-project number. You can change the default name if needed. Be sure
to press return as you enter information in each field.
The project number determines the base directory name and the default schema
names.
6. Accept or Provide Project Data
After you have specified all of the project data, choose Confirm to continue.
20

The Define System Units form is displayed.
7. Select Option
On the Define System Units form, select the system of units --- English or Metric --- to be
used for measuring distances in the model.
You are prompted to specify the diameter units to be used for fittings and components.
8. Select Option
Select the Nominal Pipe Diameter (NPD) units --- English or Metric --- to be used for
specifying pipe and fitting diameters in the model.
You are prompted to specify whether or not you want to have plant monument information
included in your project.
9. Select Option
Choose Yes to include Easting, Northing, or Elevation coordinates for the plant monument
when the project is created.
Fields are displayed that enable you to specify the coordinates of the plant monument.
OR
Choose No to create the project without this information, and go to Step 11.
10. Key in coordinates for the plant monument in the Easting, Northing, and Elevation fields. Be
sure to press return as you enter information in each field.
You are prompted to specify whether you want to modify the project working units for the
piping and equipment models.
21

11. Select Option
Choose Yes if you want to modify the working units or No if you want to accept the default
working units.
Choose Confirm to continue.
If you specified that you wanted to modify the working units, the Revise Working Units form
is displayed. If you chose not to modify working units, go to Step 15.
13. On the Revise Working Units form, enter the UORs per subunit (SU) in the available field.
Then select the field name that you want reflected in your project. The default English
working units are 2032 UORs per subunit. For Metric projects, the default working units are
80 UORs per subunit. The field name selections that are available depend on whether you
specified English or Metric working units.
The number of positional units per subunit should not be revised to be less than
635 PU per inch (English units) or 25 PU per mm (metric units). The software updates the
piping, equipment, and drawing seed files to reflect the change to the working units.The
working units in the drawing seed file will be updated to be 96 times the number of positional
units per subunit that you specified for the models. All of the models that will be referenced
in the project (for example, structural, architectural, and so forth) will need to have the same
working units as the piping and equipment models.
The Create Database Schemas form is displayed.
15. On the Create Database Schemas form, specify the schemas to be created for your project.
All of the required schemas are automatically selected for you. With the piping approved
RDB schema and the EE RDB schema, you can choose to either create a new schema for
your project or to attach to an existing schema.
22

If you choose Use Existing Schema, a dialog box displays, allowing you to specify the
existing project that contains reference data to share with the project being created. Select
the project from the displayed form, and choose Confirm to continue.
To create new schemas, select the Create New Schema option and then choose Confirm.
The Create Project Control Schema form is displayed.
16. The Create Project Control Schema form enables you to specify the parameters needed to
build the schemas for your project. For each field, provide the following information:
Network Protocol --- These fields indicate the types of network protocols used to access
the database. For most networks, you will use TCP. RIS uses the protocol at the top of
the list as its primary protocol.
Node Name or Address --- Key in the address of the node (workstation or server) to
contain the database using the address format for the associated protocol (internet
address for TCP, and so forth).
If you are creating the database on the local workstation, you can select Get Client
Address to fill in these values.
OS Type --- Select the end of the field and select Windows.
OS Username and Password --- For an Oracle database, key in the username and
password to access the project schema. This must be the same username/password
specified using the grant resource function.
Database Username and Password --- For an Oracle database, key in the username
and password to access the project schema. This must be the same
username/password specified using the grant resource function.
Database Name --- For Oracle, this is the SID name for the Oracle database. The SID
name is defined when the database is created.
Database Management System Location --- Key in the directory path for the home
directory of the database product (for example, c:\oracle).
SQLEXEC --- This field is no longer used.
DPTEMP --- This field is no longer used.
TBCONFIG --- This field is no longer used.
DSQUERY --- This field is no longer used.
SYBIFILE --- This field is no longer used.
After you have specified all of the required information, choose Apply.
23

The Create Project Control Schema form is dismissed, and the schema is created. If
additional schemas are to be created, you are returned to Step 16. Otherwise, the Database
Customization Options form is displayed. The first field enables you to specify whether or
not you want to revise the piping design database structure.
17. Select Option
Choose Yes to modify the structure.
The Database Structure Revision form is displayed.

OR
Choose No to accept the default structure, and go to Step 32.
18. Identify Table for Modification
The Database Structure Revision form enables you to modify certain attribute lengths, add
user-defined attributes, define attributes to be displayed, or define attributes to be case
sensitive. Select the table to be modified from the display on the left side of the form.
The modifiable attributes for the selected table are displayed.

19. Modify Lengths or Select Other Option
Select the attribute you want to change. Then key in a number within the displayed range to
specify the length of the attribute.
20. You can select User Defined Attributes to add additional attributes to the selected table. If
you cannot add additional attributes to the selected table, a warning message is displayed.
21. Enter Attribute Name
Key in the description for the new attribute. Be sure to press return to enter the description.
22. Select Attribute Type
Select the attribute type for the specified attribute: Decimal, Integer, Short Integer,
Alphanumeric, or Standard Note. If you select Alphanumeric, you must also specify the
number of characters. If you select Standard Note, you must also key in the number of the
code list set.
User defined attributes of attribute type Standard Note can be added to both
Equipment and Piping database tables.
23. Accept Attribute Data or Modify
Choose Confirm to post the newly defined attribute to the top part of the form.
24. Enter Attribute Name or Exit
Return to Step 21 to define another attribute.
OR
Choose Cancel to return to the Database Structure Revision form.
25. You can select Attributes to be Displayed to define the attributes within the selected table
to be displayed or not displayed for database operations.
The available fields re-display to list the attributes for the selected table.
26. Select Attributes to NOT be Displayed
From the list, select the attributes that you do not want to be displayed.
27. Accept or Select Additional Attributes
Select additional attributes as needed. Then choose Confirm to accept the displayed
information.
The Database Structure Revision form is re-displayed.
24

28. You can select Attributes to be Case Insensitive to define the attributes within the
selected table to be case insensitive for database operations. Attributes that are identified as
case insensitive are treated as uppercase regardless of the case entered during data input.
The available fields re-display.

29. Select Attributes to be CASE INSENSITIVE
From the displayed list of attributes, select one that you want to be case insensitive.
The selected attributes will have their alphanumeric data automatically converted to
uppercase in the following situations:
When a row is being created in the database.
When a row is being updated in the database.
When a value for such a column in a table is being used as search criteria for a
database query.
Alphanumeric data that is to be transferred from the P&ID Database to the Piping Design
Database must be defined consistently in terms of case sensitivity for both databases for
successful data transfer and comparison.
Presently all alphanumeric data, with the following exceptions, is considered to be case
sensitive. The following alphanumeric data is always considered to be uppercase and
cannot be changed:
Piping materials class.
Schedule/thickness.
Pressure rating.
Commodity code.
Any attributes that are designated as case insensitive will have their data type changed from
character to upper_case in the design.ddl file in the project directory.
If, after creating the project, you determine that an attribute was inadvertently selected or not
selected for case insensitivity, you can edit the design.ddl file manually to reverse the
selection. However, this will not update any previously created data.
information.
The Database Structure Revision form is redisplayed.

31. After you have made all necessary database revisions, choose Confirm to continue.
The Database Customization Options form redisplays, and you are prompted to specify
whether or not you want to use DBAccess for reporting.
32. Select Option
Select Yes to add the database structure necessary to support DBAccess reporting.
OR
Select No if you will be using some other reporting tool.
33. Select Option
If your project includes the EE Raceway discipline, you are prompted to specify whether or
not you want to customize the EE project database.
Choose Yes to customize the database.
Additional fields display for you to specify the SQL File Name and the Command File
Name, as well as the Node Name and the Path (of the system on which the SQL and
25

command files reside).
OR
Select No to continue without customizing the EE project database.
The .sql and .cmd files in the ~eerway\db directory are used to setup the database.
The Define RDB File Locations form is displayed. You are prompted to specify whether or
not you want to have nonexisting directories created as needed.
35. Select Option
Select Yes to allow the program to create directories as needed.
OR
Select No to use only existing directories.
Additional fields are displayed for you to specify how your 3D RDB data is to be built.
36. Select Option
Select one of the following options:
Define Location for New RDB --- Specifies the path names for the reference data
libraries, but does not copy any of the libraries to the specified directory. This option
updates the pdtable_102 entries; this is the option to use if you want to create new
libraries. This option enables you to build a new RDB or point to reference data that
already exists on the file server, but which is not associated with an existing project.
Share RDB with Existing Project --- Enables you to share reference data with an
existing project. Like the Define Location for New RDB option, this option also updates
the pdtable_102 entries without copying the libraries. However, it updates the entries to
match those defined in an existing project rather than reading the library locations from
the express.txt file. When you select this option, a list of existing projects is displayed for
you to specify the project with which RDB data is to be shared.
Copy Existing RDB to New Project --- Enables you to copy reference data from an
existing project to the new project. This option updates the pdtable_102 entries for the
libraries and also copies the files from the source directory to the specified output
location. The source directory is defined by the location of all the libraries in the existing
project. When you select this option, a list of existing projects is displayed for you to
specify the project from which RDB data is to be copied.
Copy RDB Data --- Enables you to copy reference data to the new project. This option
updates the pdtable_102 entries for the libraries and also copies the files from the
source directory specified in the express.txt file to the specified output location.
You are prompted to specify whether or not you want to share report format/search criteria
with an existing project.
37. Select Option
Choose Yes to use existing report format and search criteria.
A list of existing projects is displayed for you to to specify the project including the report
specifications to be shared.
OR
Choose No to use the delivered report specifications, and go to Step 39.
38. Double-click to select a project from the displayed list.
If your project includes any of the 2D disciplines, additional fields are displayed for you to
specify how your 2D RDB data is to be built.
26

39. Select Option
Select one of the following options:
Define Location for New RDB --- Specifies the path names for the reference data
libraries, but does not copy any of the libraries to the specified directory. This option
enables you to point to reference data that already exists on the file server, but which is
not associated with an existing project.
Share RDB with Existing Project --- Enables you to share reference data with an
existing project. When you select this option, a list of existing projects is displayed for
you to specify the project with which RDB data is to be shared.
Copy Existing RDB to New Project --- Enables you to copy reference data from an
existing project to the new project. The source directory is defined by the location of all
the libraries in the existing project. When you select this option, a list of existing projects
is displayed for you to specify the project from which RDB data is to be copied.
Copy Delivered RDB Data to New Project --- Enables you to copy delivered reference
data to the new project.
If you chose the Define Location for New RDB option, the Define Location for New RDB
form is displayed. Go to Step 41.
If you chose the Copy RDB Data option, the Copy 3D RDB to New Project form is
displayed. Go to Step 42.
If you chose Share RDB with Existing Project or Copy Existing RDB to New Project, and
your project includes any of the 2D disciplines, the Define 2D Reference Data Locations
form is displayed, and you go to Step 43. Otherwise, go to Step 44.
41. Accept or Update File Name, Node Name, and File Path
On the Define Location for New RDB form, use the scroll bars to review the displayed data.
The default nodes and paths are read from the express.txt file used to create the project. To
change the node name and path for one file, simply click on the field you want to edit and
key in revised information.
You can change all of the node names by selecting the Change Node Names To field and
keying in a new node name. The Substitute Root Paths From/To fields enable you to
change groups of pathnames.
If you choose not to define a specific library, space through the fields for the file
name, node, and path. Be sure to press Return in each field.
After you have defined the reference data to be used to create the reference data for the
new project, choose Confirm to continue.
If the program is unable to locate a specified file, a message box is displayed. When
you close the message box, the file that caused the problem is highlighted in red. Edit the
data as necessary, and choose Confirm to continue.
If your project includes any of the 2D disciplines, the Define 2D Reference Data Location
form is displayed, and you go to Step 43. Otherwise, the Copy Files to Project Directory
form is displayed, and you go to Step 44.
42. Accept or Update File Name, Node Name, and File Path
The Copy 3D RDB to New Project form displays the source (where you want the files copied
from) and destination (where you want the files copied to) for the reference data. The default
nodes and paths are read from the express.txt file used to create the project.
27

Use the scroll bars to review the displayed data. To change the node name and path for one
file, simply click on the field you want to edit and key in the revised information.
You can change all of the source node names by selecting the Change Source Node
Names To field and entering a new node name. The Substitute Source Root Paths
From/To fields enable you to change groups of source pathnames. Similarly, the Change
Destination Node Names To and Substitute Destination Root Paths From/To fields
enable you to change groups of destination node names and pathnames for the new project.
After you have defined the reference data to be used in the new project, choose Confirm to
continue.
The Copy Files to Project Directory form is displayed.

43. Accept or Update Node Name and File Path
The Define 2D Reference Data Location form displays the destination (where you want the
delivered files copied to) for the 2D reference data. The default nodes and paths are read
from the express.txt file used to create the project.
Use the scroll bars to review the displayed data. To change the node name and path for one
file, simply click on the field you want to edit and key in the revised information.
entering a new node name. The Substitute Root Paths From/To fields enable you to
change groups of pathnames.
After you have defined the reference data to be used in the new project, choose Confirm to
continue.
The Copy Files to Project Directory form is displayed.

The Copy Files to Project Directory form displays a list of files to be copied to your project.
The File Description and File Name fields are not editable. The file descriptions match the
keywords in the express.txt file.
Use the scroll bars to review the displayed information. The Node and Path columns reflect
the values read from the express.txt file that was used to create the project.
You can change the Node and Path specifications for an individual file by clicking on the
field you want to change and entering the revised information. To change all of the nodes,
select the Change Node Names To field, and enter the new node name. The Substitute
Root Paths From/To fields enable you to quickly change groups of pathnames.
After you have defined the location of the project files to be used to create the new project,
choose Confirm to continue.
The Define Default Miscellaneous File Locations form is displayed.

The Define Default Miscellaneous File Locations form is much like the Copy Files to Project
Directory form. Instead of dealing primarily with seed, border, category, and configuration
28

files, the Define Default Miscellaneous File Locations form establishes the location for a
variety of files that are specific to certain PDS modules. The File Description and File
Name fields are not editable. The file descriptions match the key words in the express.txt
file.
Use the scroll bars to review the displayed information. The Node and Path columns reflect
the values read from the express.txt file that was used to create the project.
You can change the Node and Path specifications for an individual file by clicking on the
field you want to change and entering the revised information. To change all of the nodes,
select the Change Node Names To field, and enter the new node name. The Substitute
Root Paths From/To fields enable you to quickly change groups of pathnames.
field as necessary, and choose Confirm to continue.
If your project includes structural data, the Create FrameWorks Sub-Project form is
displayed, and you continue to Step 40. Otherwise, the project is created, and the program
exits.
46. Key in Sub-Project Data
On the Create FrameWorks Sub-Project form, specify the project number, the project name,
the node name of the system, the directory in which the FrameWorks information is to be
stored, the force units for the sub-project, and the name of the standard section table. Be
sure to press return to enter the information in each field.
When specifying the path, you must specify a full path name. Relative path names
are not valid input for this field. Also, note that the directories for the structural sub-project
are created such that the directory specified in the Sub-Project Number field is created as
a subdirectory of the directory specified in the Sub-Project Name field.
47. Accept or Modify Sub-Project Data
After you have specified all of the sub-project information, choose Confirm to continue.
A dialog box is displayed indicating that the project was successfully created, and a log file
named express.log is created in the project directory. If there are severe errors during the
creating process, the system will try to clean up the database so that you can re-create the
project after resolving the errors.
29
30
SECTION 4
Understanding the express.txt File

The express.txt file enables you to customize the way a project is created. This file is read
whether you create a project using the New User mode or the Advanced User mode. With
Advanced User mode, you can modify the file settings as you create the project; in New User
mode, many of the settings in the express.txt file are inferred from responses made to the
various prompts and fields displayed during the process.
In the New User mode, the express.txt file that is located in the \win32app\ingr\pdshell\seedz
directory is read, and the project is created using the directory structure specified. The
express.txt file is then copied to the project directory. You cannot edit this file. You can only edit
copies of this file, and these customized files can only be used in Advanced User mode.
In the Advanced User mode, you can use a specific express.txt file. This file can be located in
any directory on any computer recognized through the network by your computer. It can also
have any file name. Its contents, however, must follow the structure of the delivered express.txt
file.
The express.txt file uses primary and secondary keywords to set variables needed to create a
project. Primary keywords are on a line by themselves and are followed by a colon (:). You
cannot edit primary keywords. Secondary keywords set the variable data. Secondary keywords
are always followed by an equal sign (=). You can edit the information on the right side of the
equal sign to be the value you want, but you cannot change the keyword. That is, you can
change the value for the keyword, but not the keyword itself.
Comments --- information in the file added solely to help with the readability of the file --- are
also included; text that is on a line beginning with an exclamation point (!) is a comment.
In New User mode, information in the file is replaced either by information that you key in
(through the forms interface) or by information from the system registry. For example, the
delivered express.txt file uses software_node to describe the node name of the computer on
which the PDS software resides. This text is replaced by the values read from the system
registry. (This information is added to the system registry whenever you install software.) Other
information, such as the value for file_server_node (the node name of the computer on which
the project data resides), is replaced by the node name you enter on the Server Names & Drive
Letters form.
For a complete printout of the delivered express.txt file, see Appendix A.
The express.txt file contains the following major sections:
Specifications for seed data.
Specifications for default file locations.
Specifications for approved and unapproved RDB libraries.
Specifications for drawing cell libraries.
Specifications for the location of 2D reference data.
31
Seed Data
Piping_Seed_Model --- Specifies the node name and directory of the seed file for piping
models .
Equipment_Seed_Model --- Specifies the node name and directory of the seed file for
equipment models.
Raceway_Seed_Model --- Specifies the node name and directory of the seed file for raceway
models.
Default_Seed_Drawing --- Specifies the node name and directory of the default piping drawing
seed file.
Alternate_Seed_Drawing --- Specifies the node name and directory for the alternate drawing
seed files. There is a separate entry for each drawing type.
Orthographic_Drawing_Plot_Size_Table --- Specifies the node name and directory of the plot
size table for orthographic drawings (drawplotsize).
Drawing_Cell_Library --- Specifies the node name and directory of the drawing cell libraries
(drawing.cel).
Drawing_Labels_per_Object_Type --- Specifies the node name and directory of the drawing
labels. There is a separate entry for each drawing type (labels.***, where *** is the drawing
type number, such as 643 for Equipment Arrangements).
Instrument_Objects_for_Drawing_Annotation --- Specifies the node name and directory for
the instrument objects that are used for annotating drawings (in_object.dwg).
Equipment_Objects_for_Drawing_Annotation --- Specifies the node name and directory for
the equipment objects that are used for annotating drawings (eqp_object.dwg).
Label_Button_for_Drawing_Annotation --- Specifies the node name and directory for the
ASCII file that defines the label placement form for the Drawing Mass Annotation command
(lab_button.dwg).
Equipment_Centerline_Definitions_for_Drawings --- Specifies the node name and directory
for the equipment centerlines file (eqp_center.dwg).
Clash_Plot_Cell_Library --- Specifies the node name and directory for the cell library to be
used for clash reports (clash_plot.cel).
Clash_Plot_Border --- Specifies the node name and directory for the border file to be used for
clash reports (borderifc.dgn).
Clash_Plot_Settings --- Specifies the node name and directory for the settings file for plotting
clashes (ifc.i).
Piping_Model_Category_Descriptions_by_NPD --- Specifies the node name and directory for
the file that sorts piping category descriptions by nominal pipe diameter (pipecats1.txt).
Piping_Model_Category_Descriptions_by_Fluid_Code --- Specifies the node name and
directory for the file that sorts piping category descriptions by fluid code (pipecats2.txt).
Drawing_Category_Descriptions --- Specifies the node name and directory of the drawing
category descriptions file. (drwcats.txt).
FrameWorks_Category_Descriptions --- Specifies the node name and directory of the
FrameWorks category descriptions file (framewks.txt).
ModelDraft_Category_Descriptions --- Specifies the node name and directory of the
ModelDraft category descriptions file (symbology.sms).
Raceway_Configuration_File --- Specifies the node name and directory of the Raceway
configuration file (ee.cfg).
32

PID_to_Piping_NPD_Equivalent_Table --- Specifies the node name and directory of the
nominal pipe diameter equivalent table for P&ID-to-Piping data transfer (pid_npd_equiv).
PID_to_Piping_Correlation_Table --- Specifies the node name and directory of the correlation
table used for the P&ID-to-Piping data transfer (pid_to_piping).
Queue_Description_Library --- Specifies the node name and directory for the queue
descriptions file (queue_descript).
RDB_Option_File --- Specifies the node name and directory of the reference database options
file used by the Interactive Spec Writer command (RDB_options).
Standard_Note_Maximum_Length_Table --- Specifies the node name and directory of the
maximum length table for standard notes (stnote_max_len).
Spec_Order_Maximum_Length_Table --- Specifies the node name and directory of the file
that contains the table of specification attribute orders and their related maximum lengths
(spec_order.max).
Default File Locations

PDS_Project_Directory --- Specifies the node name and directory for the PDS project
directory.
Raceway_Project_Directory --- Specifies the node name and directory for the raceway data.
Piping_Models --- Specifies the node name and directory for the piping models.
Equipment_Models --- Specifies the node name and directory for the equipment models.
HVAC_Models --- Specifies the node name and directory for the HVAC models.
Architectural_Models --- Specifies the node name and directory for the architectural models.
Orthographic_Drawings_by_Drawing_Type --- Specifies the node name and directory for the
orthographic drawings, ordered by drawing type. There is one entry for each drawing type.
Drawing_Borders --- Specifies the node name and directory for drawing borders.
Piping_Eden_Source --- Specifies the default location (node name and directory) for the Eden
source files.
Dimension_or_Spec_Table_Source --- Specifies the default location (node name and
directory) for the Dimension Table and Spec Table source files.
Piping_Spec_Source --- Specifies the default location (node name and directory) for the
neutral files to be used to load the Specification/Material Reference Database and Material
Description Libraries.
Piping_Assembly_Source --- Specifies the default location (node name and directory) for the
Piping Assembly Language source files.
Standard_Note_Library_Source --- Specifies the default location (node name and directory)
for Standard Note (code list) source files.
Equipment_Eden_Source --- Specifies the default location (node name and directory) for the
Equipment Eden source files.
TDF_Table_Source --- Specifies the default location (node name and directory) for Equipment
table definition files.
Model_Builder_Source --- Specifies the default location (node name and directory) for model
builder language source files.
Design_Review_Model --- Specifies the node name and directory for DesignReview models
and tags.
Reports --- Specifies the node name and directory for MTO reports.
Report_Formats --- Specifies the node name and directory for report format files.
33

Report_Discrimination_Data --- Specifies the node name and directory for report
discrimination data.
Report_Search_Criteria_Data --- Specifies the node name and directory for report search
criteria data.
Clash_Reports --- Specifies the node name and directory for interference clash plot reports.
Clash_Plots --- Specifies the node name and directory for interference design files.
Equipment_IForms --- Specifies the node name and directory for the forms used by the
PD_Eqp (Equipment) module.
RDB Libraries
A_Standard_Note_Library --- Specifies the node name, directory, and file name for the
approved standard note library.
U_Standard_Note_Library --- Specifies the node name, directory, and file name for the
unapproved standard note library.
A_Label_Description_Library --- Specifies the node name, directory, and file name for the
approved label description library.
U_Label_Description_Library --- Specifies the node name, directory, and file name for the
unapproved label description library.
A_Piping_Assembly_Library --- Specifies the node name, directory, and file name for the
approved piping assembly library.
U_Piping_Assembly_Library --- Specifies the node name, directory, and file name for the
unapproved piping assembly library.
A_Graphic_Commodity_Library --- Specifies the node name, directory, and file name for the
approved graphic commodity library.
U_Graphic_Commodity_Library --- Specifies the node name, directory, and file name for the
unapproved graphic commodity library.
A_Piping_Spec_Job_Table_Library --- Specifies the node name, directory, and file name for
the approved piping specification job table library.
U_Piping_Spec_Job_Table_Library --- Specifies the node name, directory, and file name for
the unapproved piping specification job table library.
A_US_Physical_Data_Library --- Specifies the node name, directory, and file name for the
approved U.S. physical data library.
U_US_Physical_Data_Library --- Specifies the node name, directory, and file name for the
unapproved U.S. physical data library.
A_DIN_Physical_Data_Library --- Specifies the node name, directory, and file name for the
approved DIN physical data library.
U_DIN_Physical_Data_Library --- Specifies the node name, directory, and file name for the
unapproved DIN physical data library.
A_British_Standard_Physical_Data_Library --- Specifies the node name, directory, and file
name for the approved British standard physical data library.
U_British_Standard_Physical_Data_Library --- Specifies the node name, directory, and file
name for the unapproved British standard physical data library.
A_European_A_Physical_Data_Library --- Specifies the node name, directory, and file name
for the approved European A physical data library.
U_European_A_Physical_Data_Library --- Specifies the node name, directory, and file name
for the unapproved European A physical data library.
34

A_European_B_Physical_Data_Library --- Specifies the node name, directory, and file name
for the approved European B physical data library.
U_European_B_Physical_Data_Library --- Specifies the node name, directory, and file name
for the unapproved European B physical data library.
A_JIS_Physical_Data_Library --- Specifies the node name, directory, and file name for the
approved JIS physical data library.
U_JIS_Physical_Data_Library --- Specifies the node name, directory, and file name for the
unapproved JIS physical data library.
A_Australian_Physical_Data_Library --- Specifies the node name, directory, and file name for
the approved Australian physical data library.
U_Australian_Physical_Data_Library --- Specifies the node name, directory, and file name for
the unapproved Australian physical data library.
A_International_A_Physical_Data_Library --- Specifies the node name, directory, and file
name for the approved International A physical data library.
U_International_A_Physical_Data_Library --- Specifies the node name, directory, and file
name for the unapproved International A physical data library.
A_International_B_Physical_Data_Library --- Specifies the node name, directory, and file
name for the approved International B physical data library.
U_International_B_Physical_Data_Library --- Specifies the node name, directory, and file
name for the unapproved International B physical data library.
A_Company_Practice_Physical_Data_Library --- Specifies the node name, directory, and file
name for the approved company practice physical data library.
U_Company_Practice_Physical_Data_Library --- Specifies the node name, directory, and file
name for the unapproved company practice physical data library.
A_Short_Material_Description_Library --- Specifies the node name, directory, and file name
for the approved short material description library.
U_Short_Material_Description_Library --- Specifies the node name, directory, and file name
for the unapproved short material description library.
A_Long_Material_Description_Library --- Specifies the node name, directory, and file name
for the approved long material description library.
U_Long_Material_Description_Library --- Specifies the node name, directory, and file name
for the unapproved long material description library.
A_Specialty_Material_Description_Library --- Specifies the node name, directory, and file
name for the approved specialty material description library.
U_Specialty_Material_Description_Library --- Specifies the node name, directory, and file
name for the unapproved specialty material description library.
A_Equipment_Graphic_Commodity_Library --- Specifies the node name, directory, and file
name for the approved equipment graphic commodity library.
U_Equipment_Graphic_Commodity_Library --- Specifies the node name, directory, and file
name for the unapproved equipment graphic commodity library.
A_Equipment_Tutorial_Definition_Library --- Specifies the node name, directory, and file
name for the approved equipment tutorial definition library.
U_Equipment_Tutorial_Definition_Library --- Specifies the node name, directory, and file
name for the unapproved equipment tutorial definition library.
A_Equipment_Physical_Data_Library --- Specifies the node name, directory, and file name
for the approved equipment physical data library.
35

U_Equipment_Physical_Data_Library --- Specifies the node name, directory, and file name
for the unapproved equipment physical data library.
A_Equipment_Cell_Library --- Specifies the node name, directory, and file name for the
approved equipment cell library.
U_Equipment_Cell_Library --- Specifies the node name, directory, and file name for the
unapproved equipment cell library.
Drawing Cell Libraries

Drawing_Cell_Library_by_Drawing_Type --- Specifies the node name, directory, and file
name of the source and destination, ordered by drawing type. There is a separate entry for each
drawing type.
2D Reference Data
PDS2D_Reference_Data --- Specifies the node name and directory for the 2D reference data.
PID_Reference_Data --- Specifies the node name and directory for the P&ID reference data.
PFD_Reference_Data --- Specifies the node name and directory for the PFD reference data.
36
SECTION 5
The express.txt File

The following express.txt file is delivered as part of the Express Project Creation program:
! This is the default ASCII file used by Express Setup.
! Primary keywords must end with a 'colon' (:).
! Secondary keywords must include 'equals' ( = ), and are indented for
clarity.
! The following are 'logical node names' that have been used. In 'new user'
! mode, these logical names will be automatically replaced by inputs from
! the user.
! 'software_node'
! 'file_server_node'
! 'design_review_node'
==
==
==
node name of location for PDS products

node name of file server for PDS project
node name of DesignReview workstation
! The following are 'logical drive letters' that have been used. In 'new
user'
! mode, these logical names will be automatically replaced by inputs from
! the user. Likewise, the '\pds' root path will be automatically replaced
! by the project number.
! 'pds_product'
! 'pds_project_data'
! 'pds_model_data'
! 'pds_dwg_data'
! 'pds_3d_rdb_data'
data
! 'pds_report_data'
! 'pds_clash_data'
! 'pds_review_data'
Review data
! 'pds_2d_rdb_data'
data
== drive letter of location for PDS products

== drive letter of location for PDS project data
== drive letter of location for PDS model data
== drive letter of location for PDS drawing data
== drive letter of location for PDS 3D reference
== drive letter of location for PDS report data
== drive letter of location for PDS clash data
== drive letter of location for SmartPlant
==
drive letter of location for PDS 2D reference
!\
! Source for Seed Data to be Copied to PDS Project Directory
!/
Piping_Seed_Model:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
37

Equipment_Seed_Model:
Raceway_Seed_Model:
Source_Path = C:\win32app\ingr\eerway\dgn\seed\
Default_Seed_Drawing:
Alternate_Seed_Drawing:
! Foundation Location Drawings
Drawing_Type = 535
! Piling Drawings
Drawing_Type = 537
! Structural Perspectives, Plans, Sections and Details
Drawing_Type = 540
! Plot Plans
Drawing_Type = 641
! Equipment Arrangement Drawings
Drawing_Type = 643
! Piping Underground Drawings
Drawing_Type = 651
! Equipment Orientations
Drawing_Type = 661
38

! Piping One Line Drawings
Drawing_Type = 663
! Piping Perspectives, Plans, Sections and Details
Drawing_Type = 665
! Pipeline Alignment Drawings
Drawing_Type = 667
! Instrument Location Plans
Drawing_Type = 731
! Electrical Area Classification Drawings
Drawing_Type = 841
! Electrical Underground Drawings
Drawing_Type = 851
! Lighting Perspectives, Plans, Sections and Details
Drawing_Type = 865
! HVAC Perspectives, Plans, Sections and Details
Drawing_Type = 971
Orthographic_Drawing_Plot_Size_Table:
Source_Path = C:\win32app\ingr\pdshell\plot\
39

Drawing_Cell_Library:
Source_Path = C:\win32app\ingr\pdshell\cell\
Drawing_Labels_per_Object_Type:
Drawing_Type = 535
Source_Path = C:\win32app\ingr\pddraw\sample\
! Piling Drawings
Drawing_Type = 537
Drawing_Type = 540
! Plot Plans
Drawing_Type = 641
Drawing_Type = 643
Drawing_Type = 651
Drawing_Type = 661
Drawing_Type = 663
40

Drawing_Type = 665
Drawing_Type = 667
Drawing_Type = 731
Drawing_Type = 841
Drawing_Type = 851
Drawing_Type = 865
Drawing_Type = 971
Instrument_Objects_for_Drawing_Annotation:
Equipment_Objects_for_Drawing_Annotation:
Label_Button_for_Drawing_Annotation:
41

Equipment_Centerline_Definitions_for_Drawings:
Clash_Plot_Cell_Library:
Source_Path = C:\win32app\ingr\pdshell\cell\
Clash_Plot_Border:
Source_Path = C:\win32app\ingr\pdshell\border\
Clash_Plot_Settings:
Piping_Model_Category_Descriptions_by_NPD:
Source_Path = C:\win32app\ingr\pdshell\categ\
Piping_Model_Category_Descriptions_by_Fluid_Code:
Drawing_Category_Descriptions:
FrameWorks_Category_Descriptions:
ModelDraft_Category_Descriptions:
Raceway_Configuration_File:
Source_Path = C:\win32app\ingr\eenuc\
PID_to_Piping_NPD_Equivalent_Table:
Source_Path = C:\win32app\ingr\pdshell\pid\
PID_to_Piping_Correlation_Table:
Queue_Description_Library:
42

RDB_Option_File:
Source_Path = C:\win32app\ingr\pddata\sample\data\
Standard_Note_Maximum_Length_Table:
Source_Path = C:\win32app\ingr\pdshell\lib\
Spec_Order_Maximum_Length_Table:
!
Copied to Piping_Spec_Source - not Project Directory
Source_Path = C:\win32app\ingr\pddata\sample\format\
PDS_Project_Directory:
Node = minnow
Path = d:\proj1\project\
Raceway_Project_Directory:
Node = minnow
Path = d:\
Piping_Models:
Default_Node = minnow
Default_Path = d:\proj1\models\piping\
Equipment_Models:
Default_Path = d:\proj1\models\eqp\
HVAC_Models:
Default_Path = d:\proj1\models\hvac\
Architectural_Models:
Default_Path = d:\proj1\models\arch\
Drawing_Borders:
! PDS Drawing Borders will be copied into specified location for new users
only
Node = minnow
Path = d:\proj1\dwg\border\
Piping_Eden_Source:
Default_Path = d:\proj1\rdb\source\eden_piping\
Dimension_or_Spec_Table_Source:
Default_Path = d:\proj1\rdb\source\table\
Piping_Spec_Source:
Default_Path = d:\proj1\rdb\source\spec\
43

Piping_Assembly_Source:
Default_Path = d:\proj1\rdb\source\assembly\
Standard_Note_Library_Source:
Default_Path = d:\proj1\rdb\source\std_note\
Equipment_Eden_Source:
Default_Path = d:\proj1\rdb\source\eden_eqp\
TDF_Table_Source:
Default_Path = d:\proj1\rdb\source\eqp\tdf\
Model_Builder_Source:
Default_Path = d:\proj1\model_builder\
Design_Review_Model:
Destination_Node = minnow
Destination_Path = d:\proj1\design_review\
Reports:
Default_Path = d:\proj1\report\mto\
Report_Formats:
Default_Path = d:\proj1\report\format\
Report_Discrimination_Data:
Default_Path = d:\proj1\report\discrimination\
Report_Search_Criteria_Data:
Default_Path = d:\proj1\report\search\
Clash_Reports:
Destination_Path = d:\proj1\clash\report\
Clash_Plots:
Destination_Path = d:\proj1\clash\plot\
Equipment_IForms:
Source_Node =
Source_Path =
44

A_Standard_Note_Library:
Source_File = std_note.l
Destination_File = std_note.l
Destination_Path = d:\proj1\rdb\lib\approved\
U_Standard_Note_Library:
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Label_Description_Library:
Source_File = labels.l
Destination_File = labels.l
U_Label_Description_Library:
A_Piping_Assembly_Library:
Source_File = assembly.l
Destination_File = assembly.l
U_Piping_Assembly_Library:
45

A_Graphic_Commodity_Library:
Source_File = pip_gcom.l
Destination_File = pip_gcom.l
U_Graphic_Commodity_Library:
A_Piping_Spec_Job_Table_Library:
Source_File = us_pjstb.l
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_pjstb.l
U_Piping_Spec_Job_Table_Library:
A_US_Physical_Data_Library:
Source_File = us_pcdim.l
Destination_File = us_pcdim.l
U_US_Physical_Data_Library:
46

A_DIN_Physical_Data_Library:
Source_File = din_pcdim.l
Source_Path = C:\win32app\ingr\rddinrdb\piping\libs\
Destination_File = din_pcdim.l
U_DIN_Physical_Data_Library:
Source_Path = C:\win32app\ingr\rddinrdb\piping\libs\
A_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = bs_pcdim.l
U_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eura_pcdim.l
U_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
47

A_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eurb_pcdim.l
U_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = jis_pcdim.l
U_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = aus_pcdim.l
U_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
48

A_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = inta_pcdim.l
U_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = intb_pcdim.l
U_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = cmp_pcdim.l
U_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
49

A_Short_Material_Description_Library:
Source_File = us_shbom.l
Destination_File = us_shbom.l
U_Short_Material_Description_Library:
A_Long_Material_Description_Library:
Source_File = us_lgbom.l
Destination_File = us_lgbom.l
U_Long_Material_Description_Library:
A_Specialty_Material_Description_Library:
Source_File = us_spbom.l
Destination_File = us_spbom.l
U_Specialty_Material_Description_Library:
50

A_Equipment_Graphic_Commodity_Library:
Source_File = zi_eqpms.lib
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = zi_eqpms.lib
Destination_Path = d:\proj1\rdb\eqp\approved\
U_Equipment_Graphic_Commodity_Library:
Destination_Path = d:\proj1\rdb\eqp\unapproved\
A_Equipment_Tutorial_Definition_Library:
Source_File = zi_tutlib.lib
Destination_File = zi_tutlib.lib
U_Equipment_Tutorial_Definition_Library:
A_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
51

A_Equipment_Cell_Library:
Source_File = equip.cel
Destination_File = equip.cel
U_Equipment_Cell_Library:
PDS2D_Reference_Data:
Node = minnow
Path = pds_2d_rdb_data:\proj1\pds2d\rdb\
PID_Reference_Data:
Node = minnow
Path = pds_2d_rdb_data:\proj1\pid\rdb\
PFD_Reference_Data:
Node = minnow
Path = pds_2d_rdb_data:\proj1\pfd\rdb\
Copy_Report_Format_and_Search_Criteria_Data:
Source_Project_No =
Material_Reference_Database:
Source_Project_No =
Raceway_Reference_Database:
Source_Project_No =
A_Pipe_Support_Section_Table_Library:
Source_File = aisc
Destination_File = aisc
U_Pipe_Support_Section_Table_Library:
Source_File = aisc
52

A_Pipe_Support_Tutorial_Definition_Library:
Source_File = ppsm_tlib.l
Destination_File = ppsm_tlib.l
U_Pipe_Support_Tutorial_Definition_Library:
Pipe_Support_Drawing_Symbols:
Source_File =
Source_Path = C:\win32app\ingr\pdshell\PsmSymbols\
Destination_File =
Destination_Path = d:\proj1\dwg\PsmSymbols\
Pipe_Support_Drawings_Base_Directory:
Default_Path = d:\proj1\dwg\psm\
Pipe_Support_Tdf_Directory:
Default_Path = d:\proj1\rdb\source\psm\tdf\
SPPID_to_Piping_Map_Database:
SPPID_to_Piping_Transfer_Options:
Queue_Description_Library:
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\plot
RDB_Option_File:
Source_Path = pds_product:\win32app\ingr\pddata\sample\data
Standard_Note_Maximum_Length_Table:
Source_Path = pds_product:\win32app\ingr\pdshell\lib
53

Spec_Order_Maximum_Length_Table:
!
Copied to Piping_Spec_Source - not Project Directory
Source_Path = pds_product:\win32app\ingr\pddata\sample\format
!\
! Default File Locations
!/
PDS_Project_Directory:
Node = file_server_node
Path = pds_project_data:\pds\project
Raceway_Project_Directory:
Path = pds_model_data:\
Piping_Models:
Default_Node = file_server_node
Default_Path = pds_model_data:\pds\models\piping
Equipment_Models:
Default_Path = pds_model_data:\pds\models\eqp
HVAC_Models:
Default_Path = pds_model_data:\pds\models\hvac
Architectural_Models:
Default_Path = pds_model_data:\pds\models\arch
Orthographic_Drawings_by_Drawing_Type:
Drawing_Type = 535
Default_Path = pds_dwg_data:\pds\dwg\535
! Piling Drawings
Drawing_Type = 537
Drawing_Type = 540
54

! Plot Plans
Drawing_Type = 641
Drawing_Type = 643
Drawing_Type = 651
Drawing_Type = 661
Drawing_Type = 663
Drawing_Type = 665
Drawing_Type = 667
Drawing_Type = 731
Drawing_Type = 841
55

Drawing_Type = 851
Drawing_Type = 865
Drawing_Type = 971
Drawing_Borders:
! PDS Drawing Borders will be copied into specified location for new users
only
Path = pds_dwg_data:\pds\dwg\border
Piping_Eden_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eden_piping
Dimension_or_Spec_Table_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\table
Piping_Spec_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\spec
Piping_Assembly_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\assembly
Standard_Note_Library_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\std_note
Equipment_Eden_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eden_eqp
TDF_Table_Source:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eqp\tdf
56

Model_Builder_Source:
Default_Path = pds_model_data:\pds\model_builder
Design_Review_Model:
Destination_Node = design_review_node
Destination_Path = pds_review_data:\pds\design_review
Reports:
Default_Path = pds_report_data:\pds\report\mto
Report_Formats:
Default_Path = pds_report_data:\pds\report\format
Report_Discrimination_Data:
Default_Path = pds_report_data:\pds\report\discrimination
Report_Search_Criteria_Data:
Default_Path = pds_report_data:\pds\report\search
Clash_Reports:
Destination_Node = file_server_node
Destination_Path = pds_clash_data:\pds\clash\report
Clash_Plots:
Destination_Path = pds_clash_data:\pds\clash\plot
Equipment_IForms:
Source_Node =
Source_Path =
!\
! Locations of Approved and Unapproved RDB Libraries
!/
A_Standard_Note_Library:
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
57

U_Standard_Note_Library:
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Label_Description_Library:
U_Label_Description_Library:
A_Piping_Assembly_Library:
U_Piping_Assembly_Library:
A_Graphic_Commodity_Library:
58

U_Graphic_Commodity_Library:
A_Piping_Spec_Job_Table_Library:
Source_Path = pds_product:\win32app\ingr\rdusrdb
U_Piping_Spec_Job_Table_Library:
A_US_Physical_Data_Library:
U_US_Physical_Data_Library:
A_DIN_Physical_Data_Library:
Source_Path = pds_product:\win32app\ingr\rddinrdb\piping\libs
59

U_DIN_Physical_Data_Library:
Source_Path = pds_product:\win32app\ingr\rddinrdb\piping\libs
A_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
60

U_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
61

U_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Short_Material_Description_Library:
62

U_Short_Material_Description_Library:
A_Long_Material_Description_Library:
U_Long_Material_Description_Library:
A_Specialty_Material_Description_Library:
U_Specialty_Material_Description_Library:
A_Equipment_Graphic_Commodity_Library:
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved
63

U_Equipment_Graphic_Commodity_Library:
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved
A_Equipment_Tutorial_Definition_Library:
U_Equipment_Tutorial_Definition_Library:
A_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
U_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
A_Equipment_Cell_Library:
64

U_Equipment_Cell_Library:
!\
! Drawing Cell Libraries for each Drawing Type
!/
Drawing_Cell_Library_by_Drawing_Type:
Drawing_Type = 535
Source_File = drawing.cel
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_535.cel
Destination_Path = pds_dwg_data:\pds\dwg\cell
! Piling Drawings
Drawing_Type = 537
Drawing_Type = 540
! Plot Plans
Drawing_Type = 641
65

Drawing_Type = 643
Drawing_Type = 651
Drawing_Type = 661
Drawing_Type = 663
Drawing_Type = 665
66

Drawing_Type = 667
Drawing_Type = 731
Drawing_Type = 841
Drawing_Type = 851
Drawing_Type = 865
67

Drawing_Type = 971
!\
! Reference Data Locations for All 2D Disciplines
!/
PDS2D_Reference_Data:
Path = pds_2d_rdb_data:\pds\pds2d\rdb
PID_Reference_Data:
Path = pds_2d_rdb_data:\pds\pid\rdb
PFD_Reference_Data:
Path = pds_2d_rdb_data:\pds\pfd\rdb
!\
! Miscellaneous
!/
Copy_Report_Format_and_Search_Criteria_Data:
Source_Project_No =
Material_Reference_Database:
Source_Project_No =
Raceway_Reference_Database:
Source_Project_No =
!\
! Pipe Support Files
!/
A_Pipe_Support_Section_Table_Library:
Source_File = aisc
68

U_Pipe_Support_Section_Table_Library:
Source_File = aisc
A_Pipe_Support_Tutorial_Definition_Library:
U_Pipe_Support_Tutorial_Definition_Library:
Pipe_Support_Drawing_Symbols:
Source_File =
Source_Path = pds_product:\win32app\ingr\pdshell\PsmSymbols
Destination_File =
Destination_Path = pds_dwg_data:\pds\dwg\PsmSymbols
Pipe_Support_Drawings_Base_Directory:
Default_Path = pds_dwg_data:\pds\dwg\psm
Pipe_Support_Tdf_Directory:
Default_Path = pds_3d_rdb_data:\pds\rdb\source\psm\tdf
!
! Notes:
!
! 1) The value for each drawing type, Drawing_Type = xxx, should be extracted
! from CL2000 in the Standard Note Library.
!
69
70
SECTION 6
Sample Data
Four sample projects are available with the New User option. These projects are set up as
follows:
Product Loaded
NPD Units
Model Units
Sample Project
RD_USRDB
English
English
English
RD_USRDB
English
Metric
Mixed
RD_USRDB
Metric
Metric
Metric
RD_DINDB
Metric
Metric
DIN
Each of these projects contain models from the following disciplines: Piping, Equipment,
Structural (FrameWorks), and Raceway. These projects also include drawing.
The dataset that is loaded is determined based on the following criteria:
If you choose English NPD units and English model units, the English project is loaded.
If you choose English NPD units and Metric model units, the Mixed project is loaded.
If you choose Metric NPD units and Metric model units, the Metric project is used unless you
have the RD_DINRDB product installed on your system. In that case, the DIN project is
loaded.
Information in the Delivered Dataset

Each dataset contains a file named sample_data.txt, which identifies the files to be loaded for
that dataset.
English --- Piping models: pipealm1, pipealm2, and pipealm3; Equipment model:
eqpalm1; Raceway model: rwayalm1; Structural subproject: fw1; Orthographic drawings:
aircool, htexchg, pumps, tank, overall001, overall002, piping001, pipin002, cable.
Mixed --- Piping models: pipealm1, pipealm2, pipealm3; Equipment model: eqpalm1;
Raceway model: rwayalm1; Structural subproject: sametric; Orthographic drawing:
EXAMPLE.
Metric --- Piping models: pipealm1, pipealm2, pipealm3; Equipment model: eqpa1;
Raceway model: rway1a1; Structural subproject: sametric; Orthographic drawing:
EXAMPLE.
DIN --- Piping models: pipmod1, pipmod2, pipmod3, pipmod4; Equipment models:
eqpmod1, eqpmod2; Structural subproject: frm1; Orthographic drawings: fundament,
produktion, tanklager, rohr_prod1, rohr_prod2, rohr_tank.
No example specs are loaded for any of the sample projects. You must load specs in the
specification /material reference database before you can work in the new project.
71
Sample Data
P&ID Assemblies
In addition to the sample datasets, P&ID assemblies are also delivered to enable you to create
P&IDs that correspond to the sample projects.
English/Mixed project --- 38pi1.asm, 39pi1.asm, 40pi1.asm, 40pi1.asm, 40pi2.asm, and
41pi1.asm.
Metric project --- 39m1.asm, 39m1.asm, 40m1.asm, and 41m1.asm.
DIN project --- prod01.asm, and tank01.asm.
The system does not automatically load the assemblies into the created project. You should
create the necessary units and drawings (one drawing for each assembly) in the PDS2D
environment. Then use the Place Assembly command within the P&ID environment to place
the graphics for the P&IDs. You can propagate the created drawings to load the information into
the P&ID database.
72
SECTION 7
Delivered SQL Scripts

The following SQL scripts are delivered with the PD_Shell product in the
~win32app\ingr\pdshell\sql\ directory. You can use these scripts to simplify the process of
creating the required database information before creating a new PDS project or to drop
information from the database after deleting a PDS project.
These scripts have been provided as examples and should not be used until a
database manager at your site has reviewed them to ensure that they will be usable in a specific
database environment. Intergraph Corporation assumes no risks or responsibilities regarding
the use of these files. They are provided for use at your discretion.
These scripts require that the database engine has already been installed and configured to
support the creation of new databases/users. Use a text editor to review the comments at the
top of each file for information to be edited and information on how to run the scripts.
~\pdshell\sql\mssql\create.sql --- Script to create all MS SQL Databases for a PDS project.
~\pdshell\sql\mssql\drop.sql --- Script to drop all MS SQL databases for a PDS project.
~\pdshell\sql\oracle\create.sql --- Script to create all Oracle users for a PDS project.
~\pdshell\sql\oracle\drop.sql --- Script to drop all Oracle users for a PDS project.
73
Delivered SQL Scripts
74
SECTION 8
Project Options
The Project Options form is displayed when you double-click the Express Project Creation
icon. It enables you to specify basic project creation parameters; it contains the following
options:
User Level --- Select either New User or Advanced User. New User enables you to create
a basic project that follows a predefined directory structure and that uses default settings for
many of the project creation options. Advanced User enables you to create a customized
project.
For more information, see:

Creating a Standard Project (on page 11)
Creating a Customized Project (on page 19)
If you choose Advanced User, additional fields are displayed enabling you to provide the file
name and location of the express.txt file to be used as a guide for creating the project.
Sample Data --- This option is available only in New User mode. Select Yes to load a small
project that already contains plant items, such as piping, equipment, and so forth. Select No
to create the project without this data.
Select Disciplines --- Select the disciplines that apply to your project. The available
disciplines depend on the software you have loaded on the computer from which Express
Project Creation was started. (These modules do not necessarily have to reside on the
machine; they can be installed in a client configuration.)
In This Section
Define Project Data ........................................................................76
Define System Units .......................................................................76
Create Database Schemas ............................................................76
Express Project Creation ................................................................77
Create FrameWorks Sub-Project ...................................................78
Revise Working Units .....................................................................78
Database Customization Options ...................................................80
Database Structure Revision ..........................................................80
Define Location for New RDB.........................................................82
Define 2D Reference Data Locations .............................................82
Copy 3D RDB to New Project.........................................................83
Copy Files to Project Directory .......................................................83
Define Default Miscellaneous File Locations ..................................84
75
Project Options
Define Project Data

The Define Project Data form is displayed during project creation using either New User mode
or Advanced User mode. In the fields provided, key in the project number, project name,
company name, job number, and plant name. Then choose Confirm to continue, or Cancel to
return to the previous form.

Define System Units

The Define System Units is displayed during project creation using either New User mode or
Advanced User mode. Options on this form enable you to specify whether the project will be
using metric or English units for the basis of measurement and for the basis of pipe and fitting
sizes. An option is also provided enabling you to specify the coordinates of the plant monument
if one is to be included in your project.
If you are creating a project in Advanced User mode, an option is provide enabling you to
revise the working units. If you select Yes, an additional form, is included in the project creation
workflow.

After you have specified all required parameters, choose Confirm to continue or Cancel to
Create Database Schemas

The Create Database Schemas form is displayed during the project creation workflow for either
New User or Advanced User. This form enables you to specify the schema configuration for
your project. All of the required schemas are automatically selected for you. With the piping
approved RDB schema and the EERDB schema, you can choose to either create a unique
schema for your project or to share the schema with an existing project.
If you choose Use Existing Schemas, a form displays, which enables you to specify the project
with which you want to share the schema. Select the project from the displayed form, and
To create new schemas, select the Create New Schema option and then choose Confirm.

Once you have specified all required parameters, choose Confirm to continue or Cancel to
76
Project Options
Express Project Creation

If you are accessing this form in New User mode, see Server Names & Drive Letters (on page
77). If you are accessing this form in Advanced User mode, see Define RDB File Locations (on
page 77).
Server Names & Drive Letters

The Server Names & Drive Letters form is displayed as part of the project creation workflow
using New User mode. This form enables you to specify a file server where the project is to
reside and drive letters on that server for each of the modules of the project.
For more information, see Creating a Standard Project (on page 11).
Define RDB File Locations

The Define RDB File Locations form is displayed as part of the project creation workflow for
Advanced User mode. This form enables you to specify whether or not you want the system to
create directories as needed during project creation. This form also provides options that enable
you to control how RDB data is set up for the project. The following options are available:
Define Location for New RDB --- Specifies the path names for the reference data libraries, but
does not copy any of the libraries to the specified directory. This option updates the pdtable_102
entries; this is the option to use if you want to create new libraries. This option enables you to
build a new RDB or point to reference data that already exists on the file server, but which is not
associated with an existing project.
Share RDB with Existing Project --- Enables you to share reference data with an existing
project. Like the Define Location for New RDB option, this option also updates the
pdtable_102 entries without copying the libraries. However, it updates the entries to match those
defined in an existing project rather than reading the library locations from the express.txt file.
When you select this option, a list of existing projects is displayed for you to specify the project
with which RDB data is to be shared.
Copy Existing RDB to New Project --- Enables you to copy reference data from an existing
project to the new project. This option updates the pdtable_102 entries for the libraries and also
copies the files from the source directory to the specified output location. The source directory is
defined by the location of all the libraries in the existing project. When you select this option, a
list of existing projects is displayed for you to specify the project from which RDB data is to be
copied.
Copy RDB Data --- Enables you to copy reference data to the new project. This option updates
the pdtable_102 entries for the libraries and also copies the files from the source directory
specified in the express.txt file to the specified output location.
If your project includes any of the 2D disciplines, the Define RDB File Locations also provides
options that enable you to control how RDB data is set up for the project. The following options
are available:
Define Location for New RDB --- Specifies the path names for the reference data libraries, but
does not copy any of the libraries to the specified directory. This option enables you to build a
new RDB or point to reference data that already exists on the file server, but which is not
associated with an existing project.
77
Project Options
Share RDB with Existing Project --- Enables you to share reference data with an existing
project. When you select this option, a list of existing projects is displayed for you to specify the
project with which RDB data is to be shared.
Copy Existing RDB to New Project --- Enables you to copy reference data from an existing
project to the new project. The source directory is defined by the location of all the libraries in
the existing project. When you select this option, a list of existing projects is displayed for you to
specify the project from which RDB data is to be copied.
Copy Delivered RDB Data to New Project --- Enables you to copy delivered reference data to
the new project.

Creating a Customized Project (on page 19).
Create FrameWorks Sub-Project

The Create FrameWorks Sub-Project form is displayed as part of the project creation workflow
for New User mode or Advanced User mode for projects that include a structural component.
This form enables you to specify the project number, the project name, and the node name of
the system and the directory on that system in which the structural information is to be stored.

Revise Working Units

This option enables you to revise the working units to be used for any model or drawing files
created in the project.
Each 3D design file is composed of over 4,000,000,000 units of resolution (UORs). Working
units relate UORs to a measurement unit such as feet or meters and define how these units are
divided. The total units of resolution are divided into master units, subunits, and positional units
(MU:SU:PU) which define the number of addressable points and thereby the precision of
operations. The following outlines the standard working unit definitions for PDS.
Recommended Working Units - English
78
File
MU
SU
Models
1 FT
12 IN
PU
2032
Area
176138 FT
Drawings 1 FT
12 IN
195072
Recommended Working Units - Metric
1834 FT
Files
MU
SU
PU
Area
Models
1M
1000 MM
80
53687 M
Drawings
1M
1000 MM
7680
559 M
Project Options
The recommended PDS setting for English working units results in 24,384 UORs per foot
(1x12x2032). Dividing this number into the available UORs in the design file yields an area of
coverage of 176,138.75 FT or 33.3 miles.
Working units establish the scale of the data. The actual SU and PU values do not matter as
long as the total UORs per master unit are the same. Therefore, the English units can be
converted to metric units to create compatible models.
Dividing the total UORs per foot by the metric conversion factor provides the UORs per meter.
(24384/0.3048) = 80000 uors per meter
This value was used to assign the metric values 1:1000:80. Therefore, the values of 1:12:2032
for English units and 1:1000:80 for metric units are compatible.
The recommended English (2032) and metric (80) values allow a file created using the English
system to be viewed and edited in metric mode without scaling or altering data. This allows work
in a mixed unit project (metric lengths with English NPD).
For interference checking to work properly, the working units must be the same for all the
3D models for the project. This includes raceway and structural models and any other
disciplines to be used, not just piping and equipment models.
The positional units for drawings should be defined so that the drawing has the same resolution
as the model. To maintain the same resolution, the smallest drawing view scale is used so that
the PUs of the drawing file are no less than the maximum factor times the PUs used in the
model.
The smallest drawing view scale for the delivered drawing seed files is 1/8" = 1' (12"). This yields
a factor of 96 to be applied to the model units to determine the drawing units.
12/(1/8) = 96
2032 x 96 = 195072
80 x 96 = 7680
For metric units, the factor is also 96 (96 x 80 = 7680).
The following form reflects the display for a project using English units. The form will vary slightly
if you are using metric units.
1. Working Units
Key in the value for the number of UORs (units of resolution) per subunit. The default is
2032 for English units and 80 for metric units.
2. Field Names
For English units, master units will always be in feet and subunits will always be in inches.
Select the button for the names to be used for master units and subunits. These names will
appear in forms and on reports.
For metric units, you can specify master units in either meters or millimeters; subunits are
always in millimeters.
3. Choose the Confirm button to accept the specified working units and to return to the Create
Project form.
OR
Choose the Cancel button to exit the form without changing the working units for the project.
79
Project Options
Database Customization Options

The Database Customization Options form is displayed as part of the project creation workflow
for Advanced User. This form enables you to revise the structure of the piping design database.
If you choose to modify the database structure, the Database Structure Revision form is
displayed with a series of fields and options that enable you to change parts of the database
structure.
The Database Customization Options form also enables you to specify whether or not your
project will be using DBAcess for reporting.
If your project includes the EE Raceway discipline, additional fields are displayed for you to
specify whether or not you want to customize the EE database.
For more information, see Creating a Customized Project (on page 19).
Database Structure Revision

The Database Structure Revision form is displayed as part of the project creation workflow for
Advanced User mode. This form enables you to modify certain attribute lengths, add
user-defined attributes, define attributes to be displayed, or define attributes to be case
sensitive.
1. Identify Table for Modification
Select the table to be modified from the display on the left side of the form.
The modifiable attributes for the selected table are displayed.

2. Modify Lengths or Select Other Option
Select the attribute you want to change, and then key in a number within the displayed
range to specify the length of the attribute.
3. You can select User Defined Attributes to add additional attributes to the selected table. If
you cannot add additional attributes to the selected table, a warning message is displayed.
The available fields update to enable you to add attributes. The number of the next available
attribute is also displayed.
4. Enter Attribute Name
Key in the description for the new attribute. Be sure to press return to enter the description.
5. Select Attribute Type
Select the attribute type for the specified attribute: Decimal, Integer, Short Integer,
Alphanumeric, or Standard Note. If you select Alphanumeric, you must also specify the
number of characters. If you select Standard Note, you must also key in the number of the
code list set.
User defined attributes of attribute type Standard Note can be added to both
Equipment and Piping database tables.
6. Accept Attribute Data or Modify
Choose Confirm to post the newly defined attribute to the top part of the form.
7. Enter Attribute Name or Exit
Return to Step 4 to define another attribute.
OR
80
Project Options
Choose Cancel to return to the Database Structure Revision form.
8. You can select Attributes to be Displayed to define the attributes within the selected table to
be displayed or not displayed for database operations.
The form fields update to list the available attributes for the selected table.
9. Select Attributes to NOT be Displayed
From the list, select the attributes that you do not want to be displayed.
information.

11. You can select Attributes to be Case Insensitive to define the attributes within the selected
table to be case insensitive for database operations. Attributes that are identified as case
insensitive are treated as uppercase regardless of the case entered during data input.
12. Select Attributes to be CASE INSENSITIVE
From the displayed list of attributes, select one that you want to be case insensitive.
The selected attributes will have their alphanumeric data automatically converted to
uppercase in the following situations:
a. When a row is being created in the database.
b. When a row is being updated in the database.
c. When a value for such a column in a table is being used as search criteria for a
database query.
Alphanumeric data that is to be transferred from the P&ID Database to the Piping Design
Database must be defined consistently in terms of case sensitivity for both databases for
successful data transfer and comparison.
Presently all alphanumeric data, with the following exceptions, is considered to be case
sensitive. The following alphanumeric data is always considered to be uppercase and
cannot be changed:
Piping materials class
Schedule/thickness
Pressure rating
Commodity code
Any attributes that are designated as case insensitive will have their data type changed from
character to upper_case in the design.ddl file in the project directory.
If, after creating the project, you determine that an attribute was inadvertently selected or not
selected for case insensitivity, you can edit the design.ddl file manually to reverse the
selection. However, this will not update any previously created data.
information.

14. After you have made all necessary database revisions, choose Confirm to continue.
The Database Customization Options form redisplays.

For more information, see Creating a Customized Project (on page 19).
81
Project Options
Define Location for New RDB

The Define Location for New RDB form is displayed as part of the project creation workflow for
Advanced User mode. This form enables you to specify a unique directory structure for the
RDB data. The default nodes and paths are read from the express.txt file used to create the
project.
Use the scroll bars to review the displayed data. To change the node name and path for one file,
simply click on the field you want to edit and key in revised information.
keying in a new node name. The Substitute Root Paths From/To fields enable you to change
groups of path names.
After you have specified the reference data files and the structure for the new project, choose
Confirm to continue. Choose Cancel to return to the previous form.
If the program is unable to locate a specified file, a message box is displayed. When you
close the message box, the file that caused the problem is highlighted in red. Edit the data as
necessary, and choose Confirm to continue.

Define 2D Reference Data Locations

The Define 2D Reference Data Locations form is displayed as part of the project creation
workflow for Advanced User mode. This form enables you to specify a unique directory structure
for the 2D RDB data. The default nodes and paths are read from the express.txt file used to
create the project.
simply click on the field you want to edit and key in revised information.
keying in a new node name. The Substitute Root Paths From/To fields enable you to change
groups of path names.
After you have specified the reference data files and the structure for the new project, choose
Confirm to continue. Choose Cancel to return to the previous form.

82
Project Options
Copy 3D RDB to New Project

The Copy 3D RDB to New Project form is displayed as part of the project creation workflow for
Advanced User mode. This form displays the source (where you want the files copies from)
and the destination (where you want the files copied to) for the reference data. The default
nodes and paths are read from the express.txt file used to create the project.
simply click on the field you want to edit and key in the revised information.
You can change all of the source node names by selecting the Change Source Node Names
To fields and entering a new node name. The Substitute Source Root Paths From/To fields
enable you to change groups of source path names. Similarly, the Change Destination Node
Names To and Substitute Destination Root Paths From/To fields enable you to change
groups of destination node names and path names for the new project.
Once you have specified the reference data to be used to create the reference data for the new
project, choose Confirm to continue.

Copy Files to Project Directory

The Copy Files to Project Directory is displayed as part of the project creation workflow for
Advanced User mode. This form displays a list of files to be copied to your project. The File
Description and File Name fields are not editable. The file descriptions match the keywords in
the express.txt file.
Use the scroll bars to review the displayed information. The Node and Path columns reflect the
values read from the express.txt file that was used to create the project.
You can change the Node and Path specifications for an individual file by clicking on the field
you want to change and entering the revised information. To change all of the nodes, select the
Change Node Names To field, and enter the new node name. The Substitute Root Paths
From/To fields enable you to quickly change groups of path names.

83
Project Options
Define Default Miscellaneous File Locations

The Define Default Miscellaneous File Locations form is displayed during the project creation
workflow for Advanced User mode.This form establishes the location for a variety of files that
are specific to certain PDS modules. The File Description and File Name fields are not
editable. The file descriptions match the keywords in the express.txt file.
Use the scroll bars to review the displayed information. The Node and Path columns reflect the
values read from the express.txt file that was used to create the project.
You can change the Node and Path specifications for an individual file by clicking on the field
you want to change and entering the revised information. To change all of the nodes, select the
Change Node Names To field, and enter the new node name. The Substitute Root Paths
From/To fields enable you to quickly change groups of path names.
Once you have defined the location of the project files to be used to create the new project,

84
Index
C
Copy 3D RDB to New Project 83
Copy Files to Project Directory 83
Create Database Schemas 76
Create FrameWorks Sub-Project 78
Creating a Customized Project 19
Creating a Standard Project 11
D
Database Customization Options 80
Database Structure Revision 80
Define 2D Reference Data Locations 82
Define Default Miscellaneous File Locations
84
Define Location for New RDB 82
Define Project Data 76
Define RDB File Locations 77
Define System Units 76
Delivered SQL Scripts 73
E
Express Project Creation 77
G
Getting Started 7
P
Preface 5
Project Options 75
R
Revise Working Units 78
S
Sample Data 71
Server Names & Drive Letters 77
T
The express.txt File 37
U
Understanding the express.txt File 31
85

PDS Express Project Creation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDS Express Project Creation

Uploaded by

Copyright:

Available Formats

Plant Design System

Express Project Creation

Version 2011 (V12)

U.S. Government Restricted Rights Legend

Warranties and Liabilities

Plant Design System Express Project Creation

Plant Design System Express Project Creation

What's in This Document

Plant Design System Express Project Creation

Plant Design System Express Project Creation

Project Setup Overview

Before You Begin

Plant Design System Express Project Creation

Starting the Program

The Project Options form is displayed.

New User Mode

Plant Design System Express Project Creation

Advanced User Mode

Plant Design System Express Project Creation

Plant Design System Express Project Creation

Creating a Standard Project

How to Use the New User Option

The available project disciplines are displayed.

Plant Design System Express Project Creation

Creating a Standard Project

4. Accept or Select Other Discipline

Plant Design System Express Project Creation

Creating a Standard Project

Plant Design System Express Project Creation

Creating a Standard Project

Plant Design System Express Project Creation

Creating a Standard Project

The Create Database Schemas form is displayed.

Plant Design System Express Project Creation

Creating a Standard Project

Plant Design System Express Project Creation

Creating a Standard Project

Plant Design System Express Project Creation

Creating a Standard Project

15. Key in Sub-Project Data

Plant Design System Express Project Creation

Creating a Customized Project

How to Use the Advanced User Option

The available project disciplines are displayed.

Plant Design System Express Project Creation

Creating a Customized Project

Plant Design System Express Project Creation

Creating a Customized Project

Plant Design System Express Project Creation

Creating a Customized Project

The Create Database Schemas form is displayed.

Plant Design System Express Project Creation

Creating a Customized Project

The Create Project Control Schema form is displayed.

Plant Design System Express Project Creation

Creating a Customized Project

The Database Structure Revision form is displayed.

The modifiable attributes for the selected table are displayed.

The Database Structure Revision form is re-displayed.

Plant Design System Express Project Creation

Creating a Customized Project

The available fields re-display.

The Database Structure Revision form is redisplayed.

Creating a Customized Project