Professional Documents
Culture Documents
PDS Express Project Creation PDF
PDS Express Project Creation PDF
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
Index ........................................................................................................................................................... 85
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
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.
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.
Two modes are available for creating projects: New User and Advanced User.
You want to load a delivered sample dataset while creating the project.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
30. Accept or Select Additional Attributes
Select additional attributes as needed. Then choose Confirm to accept the displayed
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
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.
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.
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.
You can change all of the node names by selecting the Change Node Names To field and
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.
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.
The Copy Files to Project Directory form is displayed.
44. Accept or Update Node Name and File Path
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.
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.
The Define Default Miscellaneous File Locations form is displayed.
45. Accept or Update Node Name and File Path
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
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.
After you have defined the location of the project files to be used to create 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
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.
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).
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.
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.
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.
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.
! 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.
! 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.
!\
! Source for Seed Data to be Copied to PDS Project Directory
!/
Piping_Seed_Model:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Equipment_Seed_Model:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Raceway_Seed_Model:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\eerway\dgn\seed\
Default_Seed_Drawing:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Foundation Location Drawings
Drawing_Type = 535
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Piling Drawings
Drawing_Type = 537
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Structural Perspectives, Plans, Sections and Details
Drawing_Type = 540
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Plot Plans
Drawing_Type = 641
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Equipment Arrangement Drawings
Drawing_Type = 643
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Piping Underground Drawings
Drawing_Type = 651
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Equipment Orientations
Drawing_Type = 661
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Piping One Line Drawings
Drawing_Type = 663
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Piping Perspectives, Plans, Sections and Details
Drawing_Type = 665
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Pipeline Alignment Drawings
Drawing_Type = 667
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Instrument Location Plans
Drawing_Type = 731
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Electrical Area Classification Drawings
Drawing_Type = 841
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Electrical Underground Drawings
Drawing_Type = 851
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! Lighting Perspectives, Plans, Sections and Details
Drawing_Type = 865
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Alternate_Seed_Drawing:
! HVAC Perspectives, Plans, Sections and Details
Drawing_Type = 971
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\seedz\
Orthographic_Drawing_Plot_Size_Table:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\plot\
Drawing_Cell_Library:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\cell\
Drawing_Labels_per_Object_Type:
! Foundation Location Drawings
Drawing_Type = 535
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Piling Drawings
Drawing_Type = 537
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Structural Perspectives, Plans, Sections and Details
Drawing_Type = 540
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Plot Plans
Drawing_Type = 641
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Equipment Arrangement Drawings
Drawing_Type = 643
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Piping Underground Drawings
Drawing_Type = 651
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Equipment Orientations
Drawing_Type = 661
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Piping One Line Drawings
Drawing_Type = 663
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Piping Perspectives, Plans, Sections and Details
Drawing_Type = 665
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Pipeline Alignment Drawings
Drawing_Type = 667
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Instrument Location Plans
Drawing_Type = 731
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Electrical Area Classification Drawings
Drawing_Type = 841
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Electrical Underground Drawings
Drawing_Type = 851
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! Lighting Perspectives, Plans, Sections and Details
Drawing_Type = 865
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Drawing_Labels_per_Object_Type:
! HVAC Perspectives, Plans, Sections and Details
Drawing_Type = 971
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Instrument_Objects_for_Drawing_Annotation:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Equipment_Objects_for_Drawing_Annotation:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Label_Button_for_Drawing_Annotation:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Equipment_Centerline_Definitions_for_Drawings:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddraw\sample\
Clash_Plot_Cell_Library:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\cell\
Clash_Plot_Border:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\border\
Clash_Plot_Settings:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\plot\
Piping_Model_Category_Descriptions_by_NPD:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\categ\
Piping_Model_Category_Descriptions_by_Fluid_Code:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\categ\
Drawing_Category_Descriptions:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\categ\
FrameWorks_Category_Descriptions:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\categ\
ModelDraft_Category_Descriptions:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\categ\
Raceway_Configuration_File:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\eenuc\
PID_to_Piping_NPD_Equivalent_Table:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\pid\
PID_to_Piping_Correlation_Table:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\pid\
Queue_Description_Library:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\plot\
RDB_Option_File:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pddata\sample\data\
Standard_Note_Maximum_Length_Table:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Spec_Order_Maximum_Length_Table:
! Copied to Piping_Spec_Source - not Project Directory
Source_Node = VMPDSJOENS
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_Node = minnow
Default_Path = d:\proj1\models\eqp\
HVAC_Models:
Default_Node = minnow
Default_Path = d:\proj1\models\hvac\
Architectural_Models:
Default_Node = minnow
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_Node = minnow
Default_Path = d:\proj1\rdb\source\eden_piping\
Dimension_or_Spec_Table_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\table\
Piping_Spec_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\spec\
Piping_Assembly_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\assembly\
Standard_Note_Library_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\std_note\
Equipment_Eden_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\eden_eqp\
TDF_Table_Source:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\eqp\tdf\
Model_Builder_Source:
Default_Node = minnow
Default_Path = d:\proj1\model_builder\
Design_Review_Model:
Destination_Node = minnow
Destination_Path = d:\proj1\design_review\
Reports:
Default_Node = minnow
Default_Path = d:\proj1\report\mto\
Report_Formats:
Default_Node = minnow
Default_Path = d:\proj1\report\format\
Report_Discrimination_Data:
Default_Node = minnow
Default_Path = d:\proj1\report\discrimination\
Report_Search_Criteria_Data:
Default_Node = minnow
Default_Path = d:\proj1\report\search\
Clash_Reports:
Destination_Node = minnow
Destination_Path = d:\proj1\clash\report\
Clash_Plots:
Destination_Node = minnow
Destination_Path = d:\proj1\clash\plot\
Equipment_IForms:
Source_Node =
Source_Path =
A_Standard_Note_Library:
Source_File = std_note.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = std_note.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Standard_Note_Library:
Source_File = std_note.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = std_note.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Label_Description_Library:
Source_File = labels.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = labels.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Label_Description_Library:
Source_File = labels.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = labels.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Piping_Assembly_Library:
Source_File = assembly.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = assembly.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Piping_Assembly_Library:
Source_File = assembly.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = assembly.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Graphic_Commodity_Library:
Source_File = pip_gcom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = pip_gcom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Graphic_Commodity_Library:
Source_File = pip_gcom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = pip_gcom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Piping_Spec_Job_Table_Library:
Source_File = us_pjstb.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_pjstb.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Piping_Spec_Job_Table_Library:
Source_File = us_pjstb.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_pjstb.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_US_Physical_Data_Library:
Source_File = us_pcdim.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_US_Physical_Data_Library:
Source_File = us_pcdim.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_DIN_Physical_Data_Library:
Source_File = din_pcdim.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rddinrdb\piping\libs\
Destination_File = din_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_DIN_Physical_Data_Library:
Source_File = din_pcdim.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rddinrdb\piping\libs\
Destination_File = din_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = bs_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = bs_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eura_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eura_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eurb_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eurb_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = jis_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = jis_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = aus_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = aus_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = inta_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = inta_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = intb_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = intb_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = cmp_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = cmp_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Short_Material_Description_Library:
Source_File = us_shbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_shbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Short_Material_Description_Library:
Source_File = us_shbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_shbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Long_Material_Description_Library:
Source_File = us_lgbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_lgbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Long_Material_Description_Library:
Source_File = us_lgbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_lgbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Specialty_Material_Description_Library:
Source_File = us_spbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_spbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Specialty_Material_Description_Library:
Source_File = us_spbom.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = us_spbom.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Equipment_Graphic_Commodity_Library:
Source_File = zi_eqpms.lib
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = zi_eqpms.lib
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\approved\
U_Equipment_Graphic_Commodity_Library:
Source_File = zi_eqpms.lib
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = zi_eqpms.lib
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\unapproved\
A_Equipment_Tutorial_Definition_Library:
Source_File = zi_tutlib.lib
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = zi_tutlib.lib
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\approved\
U_Equipment_Tutorial_Definition_Library:
Source_File = zi_tutlib.lib
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = zi_tutlib.lib
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\unapproved\
A_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = us_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = us_pcdim.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Equipment_Cell_Library:
Source_File = equip.cel
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = equip.cel
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\approved\
U_Equipment_Cell_Library:
Source_File = equip.cel
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdeqp\dat\
Destination_File = equip.cel
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\eqp\unapproved\
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
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = aisc
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Pipe_Support_Section_Table_Library:
Source_File = aisc
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\rdusrdb\
Destination_File = aisc
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
A_Pipe_Support_Tutorial_Definition_Library:
Source_File = ppsm_tlib.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = ppsm_tlib.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\approved\
U_Pipe_Support_Tutorial_Definition_Library:
Source_File = ppsm_tlib.l
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\lib\
Destination_File = ppsm_tlib.l
Destination_Node = minnow
Destination_Path = d:\proj1\rdb\lib\unapproved\
Pipe_Support_Drawing_Symbols:
Source_File =
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\PsmSymbols\
Destination_File =
Destination_Node = minnow
Destination_Path = d:\proj1\dwg\PsmSymbols\
Pipe_Support_Drawings_Base_Directory:
Default_Node = minnow
Default_Path = d:\proj1\dwg\psm\
Pipe_Support_Tdf_Directory:
Default_Node = minnow
Default_Path = d:\proj1\rdb\source\psm\tdf\
SPPID_to_Piping_Map_Database:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\pid\
SPPID_to_Piping_Transfer_Options:
Source_Node = VMPDSJOENS
Source_Path = C:\win32app\ingr\pdshell\pid\
Queue_Description_Library:
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\plot
RDB_Option_File:
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pddata\sample\data
Standard_Note_Maximum_Length_Table:
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Spec_Order_Maximum_Length_Table:
! Copied to Piping_Spec_Source - not Project Directory
Source_Node = software_node
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:
Node = file_server_node
Path = pds_model_data:\
Piping_Models:
Default_Node = file_server_node
Default_Path = pds_model_data:\pds\models\piping
Equipment_Models:
Default_Node = file_server_node
Default_Path = pds_model_data:\pds\models\eqp
HVAC_Models:
Default_Node = file_server_node
Default_Path = pds_model_data:\pds\models\hvac
Architectural_Models:
Default_Node = file_server_node
Default_Path = pds_model_data:\pds\models\arch
Orthographic_Drawings_by_Drawing_Type:
! Foundation Location Drawings
Drawing_Type = 535
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\535
Orthographic_Drawings_by_Drawing_Type:
! Piling Drawings
Drawing_Type = 537
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\537
Orthographic_Drawings_by_Drawing_Type:
! Structural Perspectives, Plans, Sections and Details
Drawing_Type = 540
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\540
Orthographic_Drawings_by_Drawing_Type:
! Plot Plans
Drawing_Type = 641
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\641
Orthographic_Drawings_by_Drawing_Type:
! Equipment Arrangement Drawings
Drawing_Type = 643
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\643
Orthographic_Drawings_by_Drawing_Type:
! Piping Underground Drawings
Drawing_Type = 651
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\651
Orthographic_Drawings_by_Drawing_Type:
! Equipment Orientations
Drawing_Type = 661
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\661
Orthographic_Drawings_by_Drawing_Type:
! Piping One Line Drawings
Drawing_Type = 663
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\663
Orthographic_Drawings_by_Drawing_Type:
! Piping Perspectives, Plans, Sections and Details
Drawing_Type = 665
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\665
Orthographic_Drawings_by_Drawing_Type:
! Pipeline Alignment Drawings
Drawing_Type = 667
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\667
Orthographic_Drawings_by_Drawing_Type:
! Instrument Location Plans
Drawing_Type = 731
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\731
Orthographic_Drawings_by_Drawing_Type:
! Electrical Area Classification Drawings
Drawing_Type = 841
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\841
Orthographic_Drawings_by_Drawing_Type:
! Electrical Underground Drawings
Drawing_Type = 851
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\851
Orthographic_Drawings_by_Drawing_Type:
! Lighting Perspectives, Plans, Sections and Details
Drawing_Type = 865
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\865
Orthographic_Drawings_by_Drawing_Type:
! HVAC Perspectives, Plans, Sections and Details
Drawing_Type = 971
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\971
Drawing_Borders:
! PDS Drawing Borders will be copied into specified location for new users
only
Node = file_server_node
Path = pds_dwg_data:\pds\dwg\border
Piping_Eden_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eden_piping
Dimension_or_Spec_Table_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\table
Piping_Spec_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\spec
Piping_Assembly_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\assembly
Standard_Note_Library_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\std_note
Equipment_Eden_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eden_eqp
TDF_Table_Source:
Default_Node = file_server_node
Default_Path = pds_3d_rdb_data:\pds\rdb\source\eqp\tdf
Model_Builder_Source:
Default_Node = file_server_node
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_Node = file_server_node
Default_Path = pds_report_data:\pds\report\mto
Report_Formats:
Default_Node = file_server_node
Default_Path = pds_report_data:\pds\report\format
Report_Discrimination_Data:
Default_Node = file_server_node
Default_Path = pds_report_data:\pds\report\discrimination
Report_Search_Criteria_Data:
Default_Node = file_server_node
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_Node = file_server_node
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:
Source_File = std_note.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = std_note.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Standard_Note_Library:
Source_File = std_note.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = std_note.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Label_Description_Library:
Source_File = labels.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = labels.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Label_Description_Library:
Source_File = labels.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = labels.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Piping_Assembly_Library:
Source_File = assembly.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = assembly.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Piping_Assembly_Library:
Source_File = assembly.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = assembly.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Graphic_Commodity_Library:
Source_File = pip_gcom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = pip_gcom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Graphic_Commodity_Library:
Source_File = pip_gcom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = pip_gcom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Piping_Spec_Job_Table_Library:
Source_File = us_pjstb.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_pjstb.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Piping_Spec_Job_Table_Library:
Source_File = us_pjstb.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_pjstb.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_US_Physical_Data_Library:
Source_File = us_pcdim.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_US_Physical_Data_Library:
Source_File = us_pcdim.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_DIN_Physical_Data_Library:
Source_File = din_pcdim.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rddinrdb\piping\libs
Destination_File = din_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_DIN_Physical_Data_Library:
Source_File = din_pcdim.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rddinrdb\piping\libs
Destination_File = din_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = bs_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_British_Standard_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = bs_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eura_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_European_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eura_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eurb_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_European_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = eurb_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = jis_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_JIS_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = jis_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = aus_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Australian_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = aus_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = inta_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_International_A_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = inta_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = intb_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_International_B_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = intb_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = cmp_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Company_Practice_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = cmp_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Short_Material_Description_Library:
Source_File = us_shbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_shbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Short_Material_Description_Library:
Source_File = us_shbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_shbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Long_Material_Description_Library:
Source_File = us_lgbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_lgbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Long_Material_Description_Library:
Source_File = us_lgbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_lgbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Specialty_Material_Description_Library:
Source_File = us_spbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_spbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Specialty_Material_Description_Library:
Source_File = us_spbom.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = us_spbom.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Equipment_Graphic_Commodity_Library:
Source_File = zi_eqpms.lib
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = zi_eqpms.lib
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved
U_Equipment_Graphic_Commodity_Library:
Source_File = zi_eqpms.lib
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = zi_eqpms.lib
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved
A_Equipment_Tutorial_Definition_Library:
Source_File = zi_tutlib.lib
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = zi_tutlib.lib
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved
U_Equipment_Tutorial_Definition_Library:
Source_File = zi_tutlib.lib
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = zi_tutlib.lib
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved
A_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = us_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Equipment_Physical_Data_Library:
Source_File =
Source_Node =
Source_Path =
Destination_File = us_pcdim.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Equipment_Cell_Library:
Source_File = equip.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = equip.cel
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved
U_Equipment_Cell_Library:
Source_File = equip.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdeqp\dat
Destination_File = equip.cel
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved
!\
! Drawing Cell Libraries for each Drawing Type
!/
Drawing_Cell_Library_by_Drawing_Type:
! Foundation Location Drawings
Drawing_Type = 535
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_535.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Piling Drawings
Drawing_Type = 537
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_537.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Structural Perspectives, Plans, Sections and Details
Drawing_Type = 540
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_540.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Plot Plans
Drawing_Type = 641
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_641.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Equipment Arrangement Drawings
Drawing_Type = 643
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_643.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Piping Underground Drawings
Drawing_Type = 651
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_651.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Equipment Orientations
Drawing_Type = 661
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_661.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Piping One Line Drawings
Drawing_Type = 663
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_663.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Piping Perspectives, Plans, Sections and Details
Drawing_Type = 665
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_665.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Pipeline Alignment Drawings
Drawing_Type = 667
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_667.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Instrument Location Plans
Drawing_Type = 731
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_731.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Electrical Area Classification Drawings
Drawing_Type = 841
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_841.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Electrical Underground Drawings
Drawing_Type = 851
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_851.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! Lighting Perspectives, Plans, Sections and Details
Drawing_Type = 865
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_865.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
Drawing_Cell_Library_by_Drawing_Type:
! HVAC Perspectives, Plans, Sections and Details
Drawing_Type = 971
Source_File = drawing.cel
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\cell
Destination_File = dwg_971.cel
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\cell
!\
! Reference Data Locations for All 2D Disciplines
!/
PDS2D_Reference_Data:
Node = file_server_node
Path = pds_2d_rdb_data:\pds\pds2d\rdb
PID_Reference_Data:
Node = file_server_node
Path = pds_2d_rdb_data:\pds\pid\rdb
PFD_Reference_Data:
Node = file_server_node
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
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = aisc
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Pipe_Support_Section_Table_Library:
Source_File = aisc
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\rdusrdb
Destination_File = aisc
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
A_Pipe_Support_Tutorial_Definition_Library:
Source_File = ppsm_tlib.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = ppsm_tlib.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved
U_Pipe_Support_Tutorial_Definition_Library:
Source_File = ppsm_tlib.l
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\lib
Destination_File = ppsm_tlib.l
Destination_Node = file_server_node
Destination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved
Pipe_Support_Drawing_Symbols:
Source_File =
Source_Node = software_node
Source_Path = pds_product:\win32app\ingr\pdshell\PsmSymbols
Destination_File =
Destination_Node = file_server_node
Destination_Path = pds_dwg_data:\pds\dwg\PsmSymbols
Pipe_Support_Drawings_Base_Directory:
Default_Node = file_server_node
Default_Path = pds_dwg_data:\pds\dwg\psm
Pipe_Support_Tdf_Directory:
Default_Node = file_server_node
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.
!
Sample Data
Four sample projects are available with the New User option. These projects are set up as
follows:
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.
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
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.
For more information, see:
Creating a Customized Project (on page 19).
File MU SU PU Area
Files MU SU PU Area
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.
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