express

PDS Express Project Creation Quick Start Guide Document Number Version Date Pages DPDS3-PE-200016A PDS 7.1 April 2002 1-86 DPDS3-PE-200016B PDS 7.3 October 2004 Cover/Notice DPDS3-PE-200016C PDS 8.0 SE November 2005 Cover/Notice DPDS3-PE-200016D PDS 8.0 SE March 2007 Cover/Notice

Copyright Copyright © 1984-2007 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.

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 Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, 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.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartSketch, FrameWorks, INtools, MARIAN, ISOGEN, and IntelliShip are registered trademarks and SupportModeler and SupportManager are trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

If You Need Assistance________________

If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’sproducts, services, and direction. Our web address is: http://www.intergraph.com.

Support

For the lasest Support Services information, use a World Wide Web browser to connect tohttp://www.intergraph.com/ppo/services/support.asp.

If you are outside of the United States, please call your local Intergraph office. The most up-to-date list of international offices and distributors is available on the web athttp://www.intergraph.com.

Intergraph Directory

The following numbers are only valid in the United States unless otherwise indicated. If youare outside the United States, please call your local Intergraph office.

Intergraph General Information

All countries — 1-256-730-2000

Training Registration

1-800-766-7701 (U.S. Only)

1-256-730-5400 (Outside the U.S.)

Mailing Address

Intergraph Process, Power & Offshore300 Intergraph WayMadison, Alabama 35758U.S.A.

You can also reach us by electronic mail at [email protected].

3

________________

Documentation Contacts

We are constantly working on updates and improvements to the documents and othereducational media. If you have any suggestions on where we can improve the documentationor where you think more information is needed, let us know. You can reach us by:

Mail Intergraph Process, Power & OffshoreDocumentation Manager300 Intergraph WayMadison, AL 35758

4

Table of Contents________________

Table of Contents

If You Need Assistance ........................................................................................................ 3Intergraph Directory ............................................................................................................. 3

Preface ................................................................................................................................................. 7

Related Documents ............................................................................................................... 7What’s in This Document ..................................................................................................... 7

General Conventions .................................................................................................................... 9

Keyboard Conventions ......................................................................................................... 10Terminology ......................................................................................................................... 11

1. Getting Started ............................................................................................................................. 13

Project Setup Overview ........................................................................................................ 13Before You Begin ................................................................................................................. 14

Starting the Program .................................................................................................................... 14

2. Creating a Standard Project .......................................................................................................... 17

How to Use the New User Option ........................................................................................ 18

3. Creating a Customized Project ..................................................................................................... 27

How to Use the Advanced User Option ................................................................................ 27

4. Understanding the express.txt File ............................................................................................... 51

Seed Data .............................................................................................................................. 52Default File Locations .......................................................................................................... 54RDB Libraries ....................................................................................................................... 55Drawing Cell Libraries ......................................................................................................... 582D Reference Data ................................................................................................................ 58

Appendix A: The express.txt File .................................................................................................... 59

Appendix B: Sample Data ................................................................................................................ 77

Appendix C: Delivered SQL Scripts ................................................................................................ 79

Index .................................................................................................................................................... 81

5

PDS Express Project Creation Quick Start Guide — April 2002________________

6

Preface________________

Preface

Creating a new PDS project includes many distinct tasks that can be difficult toremember from one project to the next, particularly if you do not frequently create newprojects. With the 6.0 release of PDS, Intergraph is providing a new utility, ExpressProject Creation, which automates most of the steps needed to create a project. Thisdocument describes how to use Express Project Creation to set up both standard andcustomized projects.

This document provides only a general description of project setup. For example, adding3D project data to an existing 2D project or adding structural data to a project after it wascreated cannot be accomplished using Express Project Creation. Procedures of thisnature are described in the PDS Project Setup Technical Reference (Intergraph documentnumber DEA5067) and the PDS Project Administrator (PD_Project) Reference Guide(Intergraph document number DEA5027).

Related Documents

For more information on related topics, see the following documents:

Document Number________________ Document Title_____________

DEA5018 PDS 2D RDB Administrator User’s GuideDEA5027 Project Administrator (PD_Project) Reference GuideDEA5028 Reference Data Manager (PD_Data) Reference GuideDEA5050 Getting Started in PDS 2DDEA5065 PDS 2D RDB Administrator Reference GuideDEA5067 PDS Project Setup Technical Reference

What’s in This Document

This document contains the following chapters:

Chapter 1 — Getting Started.This chapter provides an overview of the workflow for setting up a project and describeshow 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 astandard directory structure.

Chapter 3 — Creating a Customized Project.This chapter describes how to use the Advanced User option to create a customizedproject.

7

PDS Express Project Creation Quick Start Guide — April 2002________________ Chapter 4 — Understanding the express.txt File.This chapter describes how to edit the express.txt file to further streamline your projectcreation 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.

8

Preface________________

General Conventions

This document contains many visual cues to help you understand the meaning of certainwords or phrases. The use of different fonts for different types of information allows you toscan the document for key concepts or commands. Symbols help abbreviate and identifycommonly used words, phrases, or groups of related information.

Typefaces

Italic Indicates a system response, which is an explanation of what the software isdoing. For example,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Commandpaths are shown using an arrow between command names. For example,

Choose File > Open to load a new file.

Sans serif Indicates a system prompt or message, which requires an action be taken bythe user. For example,

Select first segment of alignment

Bold TypewriterIndicates what you should literally type in. For example,

Key in original.dat to load the ASCII file.

Normal TypewriterIndicates an actual file or directory name. For example,

The ASCII report is stored in the layout.rpt file.

9


Symbols

This document uses the following symbols to represent mouse buttons and to identify specialinformation:

<C> Command button<D> Data button (usually the left mouse button)<R> Reset/reject button (usually the right mouse button)<T> Tentative button (usually the center mouse button)

Note — Important supplemental information.

Warning — Critical information that could cause the loss of data if not followed.

Technical tip or information — provides information on what the software isdoing or how it processes information.

Map or path — shows you how to get to a specific command or form.

More information — indicates there is additional or related information.

Need a hint — used with activities and labs, provides a tip or hint for doing theexercises.

Keyboard Conventions

The following list outlines the abbreviations this document uses for keyboard keys anddescribes how to use them in combination. You can make some menu selections through theuse of keyboard accelerators, which map menu selections to key combinations.

ALT Alternate keyCTRL Control keyDEL Delete keyENTER Enter keyESC Escape key

CTRL+z To hold down the Control key and press Z.ESC,k To press the Escape key, then K.

10

Preface________________

Terminology

Click To use a mouse or key combination to pick an item that begins anaction. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by pickingit with your cursor. Selecting does not initiate an action. Afterselecting an item, you click the action you want to affect the item. Forexample,

Select the file original.dat from the list box, then click Delete toremove it from the directory.

In addition, you would select items to define parameters, such asselecting toggle buttons. This also applies to selecting graphicelements from the design file. For example,

Select the line string to define the graphic template.

Tentative-select To place a tentative point on an existing graphic element in a designfile. If you are using the CLIX operating system, you tentative-selectby double-clicking with a mouse or pressing <T> on a hand-heldcursor. If you are using the Windows NT operating system, youtentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-heldcursor button twice in rapid succession. This term implies that you areclicking the data button (<D>) as part of a menu or dialog box action.For example,

Double-click on the file original.dat to load it into the newsurface.

Drag To press and hold the data button (<D>) while moving the mouse orhand-held cursor.

Type To key a character string into a text box.

Key in To type in data and press ENTER to enter the data and execute thedefault action.

In a dialog box, pressing TAB after keying in data willenter the data and move the cursor to the next field.

11


12

Gettin

g S

tarted

Getting Started________________

1. Getting Started

The Express Project Creation program is a new feature that enables you to easily createprojects using a predefined structure. Express Project Creation consists of two modes ofoperation — New User and Advanced User. The Advanced User mode allowscustomization of the directory structure and distribution of the project files acrossmultiple nodes.

Express Project Creation is available only on Windows NT-based computers. It cancreate projects on computers that operate on either Windows NT or CLIX.

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 ofthe information that is required to work in a PDS task. A project and all of itsaccompanying 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 requiresthat you have MicroStation, RIS, and a relational database set up. For informationon installing software, see the PDS Project Setup Technical Reference. Also referto the PD_Shell README.TXT file for information on product dependencies.

2. Configure the system. This step includes setting up domain logins and setting upthe networking environment. For information on system configuration, see thePDS Project Setup Technical Reference.

3. Create project databases. The PD_Shell product includes scripts that automatethe creation of the PDS databases for a number of database systems. These arelocated in the pdshell\sqls\ directory.

4. Create the project. Start the Express Project Creation, and follow the stepsoutlined in the following chapters of this document.

5. Define the reference data. Before you can begin working in your project, youmust set up the reference data. This involves loading ASCII files that definecomponents and specifications into the appropriate databases. These proceduresare described in the PDS Project Setup Technical Reference and the PDS ReferenceData Manager (PD_Data) Reference Guide.

13


Before You Begin

Before you can create a project, you must have first configured your system and installedthe software. You will also need to create databases for each module of the PDS softwareto be used by your project. For example, for a project that will use the piping andequipment modules, you will need to create the project, design, and approved referencedatabases.

For Express Project Creation, you will need to have PD_Lice and PD_Shell installedlocally. (That is, they must be installed on the computer from which you plan to run theExpress 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 whichExpress Project Creation is 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 installEE 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 tohave PD_Lice and PD_Shell installed locally. You can specify remote nodes where theother 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 Creationicon, which is located in the PD_Shell program group. The Project Options form isdisplayed.

14

Gettin

g S

tarted

Getting Started________________

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 anddatabase structure. The New User mode is ideal when your setup from one project to thenext is consistent. This mode is the fastest way to set up a project, offering only minimalinteraction once the process is started. The New User mode also provides an option toload sample data (models and drawings) into the created project. For information oncreating a project using the New User option, see Creating a Standard Project, page 17.

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.

You want to load a delivered sample dataset while creating the project.

15


Advanced User Mode

With Advanced User mode, you can customize the project as you are creating it. Notonly can you specify a unique directory structure for the project files, but you can alsohave complete control over the structure of the data within the database. For informationon creating a project using the Advanced User option, see Creating a CustomizedProject, page 27.

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 theexpress.txt file.

16

New

User

Creating a Standard Project________________

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 directorystructure:

The system creates all the directories and subdirectories; you do not need to create thedirectory structure beforehand.

17

PDS Express Project Creation Quick Start Guide — April 2002________________ Each time you create a project, the express.txt file that was used to create the project iscopied to the project directory. This enables you to keep a record of the specificparameters used for creating that project.

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 plantitems, such as piping, equipment, and so forth) or No to create a project thatdoesn’t include sample data. If you choose Yes, the system loads a set of modelsand drawings into the created project. Refer to Appendix B for a description of thedelivered sample data.

If you load sample data, your plant monument is automatically setto 0,0,0.

The available project disciplines are displayed.

3. Select Disciplines

Select the disciplines that apply to your project. The available disciplines dependon the software you have loaded on the computer from which the Express ProjectCreation was started. These modules must be installed locally. Furthermore, theymust all be installed on the same drive letter.

18

New

User


4. Accept or Select Other Discipline

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

The Define Project Data form is displayed.

19


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 informationis stored in the Project Database and can be used in reports and other projectdocuments. Also specify a design file in which project interferences are to bewritten. The default file name is your project name with .dgn appended to it. Ifyour project includes a 2D discipline, key in a site name. The default site name isplant_name-project number. You can change the default name if needed. Be sureto press return as you enter information in each field.

The project number determines the base directory name and thedefault schema names.

6. Accept or Provide Project Data

Once you have specified all of the project data, choose Confirm to continue.

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 andcomponents.

20

New

User


8. Select Option

Select the Nominal Pipe Diameter (NPD) units — English or Metric — to be usedfor specifying pipe and fitting diameters in the model.

If you chose to load sample data, the selections for system of unitswill determine the sample dataset to be loaded.

You are prompted to specify whether or not you want to have plant monumentinformation included in your project.

9. Select Option

Choose Yes to include Easting, Northing, or Elevation coordinates for the plantmonument when the project is created. The plant monument is the center of thedesign volume for the plant; this point corresponds to the MicroStation position0,0,0.

Fields are displayed that enable you to specify the coordinates of the plantmonument.

— OR —

Choose No to create the project without this information.

10. Accept or Select Option

Once you have provided the necessary information, choose Confirm to continue.

The Create Database Schemas form is displayed.

21


The selections that are available on this form vary depending on the disciplineschosen in Step 3.

11. Select Schemas

On the Create Database Schemas form, specify the schemas to be created for yourproject. All of the required schemas are automatically selected for you. With thepiping approved RDB schema and the EE RDB schema, you can choose to eithercreate 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 tospecify the existing project which contains reference data to share with the projectbeing created. Select the project from the displayed form, and choose Confirm tocontinue.

To create new schemas, select the Create New Schema option; then chooseConfirm.

The Create Project Control Schema form is displayed.

22

New

User


12. The Create Project Control Schema form enables you to specify the parametersneeded to build the schemas for your project. The information to be providedvaries depending on the relational database being used. For each field, provide thefollowing information:

Network Protocol — These fields indicate the types of network protocolsused to access the database. For most Intergraph networks, you will useXNS or TCP. RIS uses the protocol at the top of the list as its primaryprotocol.

Node Name or Address — Key in the address of the node (workstation orserver) to contain the database using the address format for the associatedprotocol (network address for XNS, internet address for TCP, and so forth).

If you are creating the database on the local workstation, you can select GetClient Address to fill in these values.

OS Type — Select the end of the field and select the type of operatingsystem for the database server: CLIX, VMS, or Windows NT.

OS Username and Password — For an Oracle database, key in theusername and password to access the project schema. This must be the sameusername/password specified using the grant resource function.

For a Sybase database, key in the username and password for a valid login tothe database server.

Database Username and Password — For an Oracle database, key in theusername and password to access the project schema. This must be the sameusername/password specified using the grant resource function.

For an Informix database, key in the username and password of the PDSaccount on the database server.

Database Name — For Oracle, this is the SID name for the Oracle database.The SID name is defined when the database is created.

23

PDS Express Project Creation Quick Start Guide — April 2002________________ For Informix, this is the same as the schema name as specified with theinfxcreate statement. For Informix Standard Engine, key in the fulldirectory path for the schema file (for example, c:\pdsproj\proj\pdproj).

For Sybase, this is the same as the schema name as specified by the SybaseCreate Database command.

Database Management System Location — Key in the directory path forthe home directory of the database product (for example, c:\oracle orc:\informix).

SQLEXEC — Informix only. This field tells Informix which engine to run.It can be left blank unless Informix Standard Engine and On-line Engine areloaded on the same machine.

DPTEMP — Informix only. This field defines a directory where you wantInformix to be create temporary files. The directory should be empty andmust be created before creating the RIS schema.

TBCONFIG — Informix only. This field is used only if you have multiplecopies of Informix running on the same system, each with its own tbconfigfile.

DSQUERY — Sybase only. This field defines the database query listener(Sybase server name).

SYBIFILE — Sybase only. This field defines the interface file name.

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 12. Otherwise,the Server Names & Drive Letters form is displayed.

24

New

User


13. On the Server Names & Drive Letters form, specify the node name of the fileserver on which the project is to reside. For Windows NT, key in the drive letteronly (for example, D, without the colon). Be sure to press return to enter the datainto each field.

If your server runs on Windows NT and you want to create theproject at a top-level drive (for example, c:\projname ore:\projname), you must first create a new share on the server forthat drive and specify just the drive letter as the new share name.This is because the default Windows NT shares for the drive lettersare available only to administrators.

If you are running Express Project Creation on a client and specifythat the project be located on a server, both the client and servernodes must be running the same version of Microstation. If theversions are different on the client and server, you will receive anError updating seed files at the end of setup.

14. Accept or Key in Data

Once you have entered all of the node name and drive letter information, chooseConfirm to continue.

If your project includes structural data, the Create FrameWorks Sub-Projectdisplays, and you continue to Step 15. Otherwise, the project is created, and theprogram exits.

25


15. Key in Sub-Project Data

On the Create FrameWorks Sub-Project form, specify the project number, theproject name, the node name of the system and the directory on that system inwhich 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 enterthe 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, notethat the directories for the structural sub-project are created suchthat the directory specified in the Sub-Project Number field iscreated as a subdirectory of the directory specified in the Sub-Project Path field.

16. Accept or Modify Sub-Project Data

Once you have specified all of the sub-project information, choose Confirm tocontinue.

A dialog box is displayed indicating that the project was successfully created, anda log file named express.log is written in the project directory. If there are severeerrors during the creation process, the system will try to clean up the database sothat you can re-create the project after resolving the errors.

No example specs are loaded for any of the sample projects. Youmust load specs in the specifications/material reference databasebefore you can work in the new project.

26

Ad

vanced

User

Creating a Customized Project________________

3. Creating a Customized Project

The Advanced User option enables you to create a project with a customized databaseand/or file structure. Not only does this option enable you to specify a unique directorystructure for all of the components that comprise a project, but it also enables you tocustomize working units, specify whether to use DBAcess for reporting, define uniquelocations for RDB data source files, and set up a project that shares or copies existingRDB data.

Like the New User mode, Advanced User mode automates much of the work involvedin setting up a project. But Advanced User mode differs from New User mode byallowing you to specify project creation parameters in the express.txt file. Furthermore,Advanced User mode enables you to confirm and modify these specificationsinteractively as the project is created. Advanced User combines the flexibility of theCreate Project option in the PD_Project component with the convenience of a scriptingfile.

For information on editing the express.txt file before starting the Advanced User mode,see Understanding the express.txt File, page 51.

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, set the User Level to Advanced User.

You are prompted to specify the name and location of the setup configuration filethat 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 theproject, the node name of the computer on which the file is located, and the path tothe file. Be sure to press return to enter the information into each field.

The default file name is express.txt. The file is delivered to thepdshell\seedz directory.

The available project disciplines are displayed.

3. Select Disciplines

Select the disciplines that apply to your project. The available disciplines dependon the software you have loaded on the computer from which the Express ProjectCreation was started. (These modules do not necessarily have to reside on thecomputer; they can be installed in a client configuration.)

27


4. Accept or Select Other Discipline

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

The Define Project Data form is displayed.

28

Ad

vanced

User


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 adesign file in which project interferences are to be written. The default file name isyour project name with .dgn appended to it. If your project includes a 2Ddiscipline, key in a site name. The default site name is plant_name-projectnumber. You can change the default name if needed. Be sure to press return asyou enter information in each field.

The project number determines the base directory name and thedefault schema names.

6. Accept or Provide Project Data

Once you have specified all of the project data, choose Confirm to continue.

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 andcomponents.

29


8. Select Option

Select the Nominal Pipe Diameter (NPD) units — English or Metric — to be usedfor specifying pipe and fitting diameters in the model.

You are prompted to specify whether or not you want to have plant monumentinformation included in your project.

9. Select Option

Choose Yes to include Easting, Northing, or Elevation coordinates for the plantmonument when the project is created.

Fields are displayed that enable you to specify the coordinates of the plantmonument.

— 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, andElevation 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 unitsfor the piping and equipment models.

11. Select Option

Choose Yes if you want to modify the working units or No if you want to acceptthe default working units.

30

Ad

vanced

User



Choose Confirm to continue.

If you specified that you wanted to modify the working units, the Revise WorkingUnits 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 theavailable field. Then select the field name that you want reflected in your project.The default English working units are 2032 UORs per subunit. For Metricprojects, the default working units are 80 UORs per subunit. The field nameselections that are available depend on whether you specified English or Metricworking units.

The number of positional units per subunit should not be revised to beless than 635 PU per inch (English units) or 25 PU per mm (metricunits). The software updates the piping, equipment, and drawing seedfiles to reflect the change to the working units. The working units in thedrawing seed file will be updated to be 96 times the number of positionalunits per subunit that you specified for the models. All of the modelsthat will be referenced in the project (for example, structural,architectural, and so forth) will need to have the same working units asthe piping and equipment models.



31

PDS Express Project Creation Quick Start Guide — April 2002________________ The Create Database Schemas form is displayed.

15. On the Create Database Schemas form, specify the schemas to be created for yourproject. All of the required schemas are automatically selected for you. With thepiping approved RDB schema and the EE RDB schema, you can choose to eithercreate 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 specifythe existing project that contains reference data to share with the project beingcreated. Select the project from the displayed form, and choose Confirm tocontinue.

To create new schemas, select the Create New Schema option and then chooseConfirm.

The Create Project Control Schema form is displayed.

32

Ad

vanced

User


16. The Create Project Control Schema form enables you to specify the parametersneeded to build the schemas for your project. For each field, provide the followinginformation:

Network Protocol — These fields indicate the types of network protocolsused to access the database. For most Intergraph networks, you will useXNS or TCP. RIS uses the protocol at the top of the list as its primaryprotocol.

Node Name or Address — Key in the address of the node (workstation orserver) to contain the database using the address format for the associatedprotocol (network address for XNS, internet address for TCP, and so forth).

If you are creating the database on the local workstation, you can select GetClient Address to fill in these values.

OS Type — Select the end of the field and select the type of operatingsystem for the database server: CLIX, VMS, or Windows NT.

OS Username and Password — For an Oracle database, key in theusername and password to access the project schema. This must be the sameusername/password specified using the grant resource function.

For a Sybase database, key in the username and password for a valid login tothe database server.

Database Username and Password — For an Oracle database, key in theusername and password to access the project schema. This must be the sameusername/password specified using the grant resource function.

For an Informix database, key in the username and password of the PDSaccount on the database server.

Database Name — For Oracle, this is the SID name for the Oracle database.The SID name is defined when the database is created.

For Informix, this is the same as the schema name as specified with theinfxcreate statement. For Informix Standard Engine, key in the fulldirectory path for the schema file (for example, c:\pdsproj\proj\pdproj).

For Sybase, this is the same as the schema name as specified by the SybaseCreate Database command.

Database Management System Location — Key in the directory path forthe home directory of the database product (for example, c:\oracle orc:\informix).

SQLEXEC — Informix only. This field tells Informix which engine to run.It can be left blank unless Informix Standard Engine and On-line Engine areloaded on the same machine.

33

PDS Express Project Creation Quick Start Guide — April 2002________________ DPTEMP — Informix only. This field defines a directory where you wantInformix to be create temporary files. The directory should be empty andmust be created before creating the RIS schema.

TBCONFIG — Informix only. This field is used only if you have multiplecopies of Informix running on the same system, each with its own tbconfigfile.

DSQUERY — Sybase only. This field defines the database query listener(Sybase server name).

SYBIFILE — Sybase only. This field defines the interface file name.

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 enablesyou to specify whether or not you want to revise the piping design databasestructure.

17. Select Option

Choose Yes to modify the structure.

The Database Structure Revision form is displayed.

34

Ad

vanced

User


— 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 attributelengths, add user-defined attributes, define attributes to be displayed, or defineattributes to be case sensitive. Select the table to be modified from the display onthe 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 displayedrange to specify the length of the attribute.

35


20. You can select User Defined Attributes to add additional attributes to the selectedtable. If you cannot add additional attributes to the selected table, a warningmessage is displayed.

21. Enter Attribute Name

Key in the description for the new attribute. Be sure to press return to enter thedescription.

22. Select Attribute Type

Select the attribute type for the specified attribute: Decimal, Integer, ShortInteger, Alphanumeric, or Standard Note. If you select Alphanumeric, youmust also specify the number of characters. If you select Standard Note, you mustalso key in the number of the code list set.

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 theselected table to be displayed or not displayed for database operations.

36

Ad

vanced

User

Creating a Customized Project________________ The available fields redisplay 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 thedisplayed information.

The Database Structure Revision form is redisplayed.

28. You can select Attributes to be Case Insensitive to define the attributes within theselected table to be case insensitive for database operations. Attributes that areidentified as case insensitive are treated as uppercase regardless of the case enteredduring data input.

The available fields redisplay.

37


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 dataautomatically 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 assearch criteria for a database query.

Alphanumeric data that is to be transferred from the P&ID Database to the PipingDesign Database must be defined consistently in terms of case sensitivity for bothdatabases for successful data transfer and comparison.

Presently all alphanumeric data, with the following exceptions, is considered to becase sensitive. The following alphanumeric data is always considered to beuppercase and cannot be changed:

— Piping materials class.

— Schedule/thickness.

— Pressure rating.

38

Ad

vanced

User


— Commodity code.

Any attributes that are designated as case insensitive will have their data typechanged from character to upper_case in the design.ddl file in the projectdirectory.

If, after creating the project, you determine that an attribute was inadvertentlyselected or not selected for case insensitivity, you can edit the design.ddl filemanually to reverse the selection. However, this will not update any previouslycreated data.

30. Accept or Select Additional Attributes

Select additional attributes as needed. Then choose Confirm to accept thedisplayed information.

The Database Structure Revision form is redisplayed.

31. Once you have made all necessary database revisions, choose Confirm to continue.

The Database Customization Options form redisplays, and you are prompted tospecify 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.

39


33. Select Option

If your project includes the EE Raceway discipline, you are prompted to specifywhether 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 CommandFile Name, as well as the Node Name and the Path (of the system on which theSQL and 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 specifywhether or not you want to have nonexisting directories created as needed.

40

Ad

vanced

User


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 bebuilt.

41


36. Select Option

Select one of the following options:

— Define Location for New RDB — Specifies the path names for the referencedata 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 youwant to create new libraries. This option enables you to build a new RDB orpoint to reference data that already exists on the file server, but which is notassociated with an existing project.

— Share RDB with Existing Project — Enables you to share reference data withan existing project. Like the Define Location for New RDB option, thisoption also updates the pdtable_102 entries without copying the libraries.However, it updates the entries to match those defined in an existing projectrather than reading the library locations from the express.txt file. When youselect this option, a list of existing projects is displayed for you to specify theproject with which RDB data is to be shared.

— Copy Existing RDB to New Project — Enables you to copy reference datafrom an existing project to the new project. This option updates thepdtable_102 entries for the libraries and also copies the files from the sourcedirectory to the specified output location. The source directory is defined bythe location of all the libraries in the existing project. When you select thisoption, a list of existing projects is displayed for you to specify the project fromwhich RDB data is to be copied.

42

Ad

vanced

User


— 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 thefiles from the source directory specified in the express.txt file to the specifiedoutput location.

You are prompted to specify whether or not you want to share reportformat/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 thereport 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 displayedfor you to specify how your 2D RDB data is to be built.

43


39. Select Option

Select one of the following options:

— Define Location for New RDB — Specifies the path names for the referencedata 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 fileserver, but which is not associated with an existing project.

— Share RDB with Existing Project — Enables you to share reference data withan existing project. When you select this option, a list of existing projects isdisplayed 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 datafrom an existing project to the new project. The source directory is defined bythe location of all the libraries in the existing project. When you select thisoption, a list of existing projects is displayed for you to specify the project fromwhich RDB data is to be copied.

— Copy Delivered RDB Data to New Project — Enables you to copy deliveredreference data to the new project.



If you chose the Define Location for New RDB option, the Define Location forNew RDB form is displayed. Go to Step 41.

44

Ad

vanced

User

Creating a Customized Project________________ If you chose the Copy RDB Data option, the Copy 3D RDB to New Project formis displayed. Go to Step 42.

If you chose Share RDB with Existing Project or Copy Existing RDB to NewProject, and your project includes any of the 2D disciplines, the Define 2DReference 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 thedisplayed data. The default nodes and paths are read from the express.txt file usedto create the project. To change the node name and path for one file, simply clickon 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 Tofield and keying in a new node name. The Substitute Root Paths From/To fieldsenable you to change groups of pathnames.

If you choose not to define a specific library, space through thefields for the file name, node, and path. Be sure to press Return ineach field.

Once you have defined the reference data to be used to create the reference data forthe new project, choose Confirm to continue.

If the program is unable to locate a specified file, a message box isdisplayed. When you close the message box, the file that caused theproblem is highlighted in red. Edit the data as necessary, andchoose Confirm to continue.

45

PDS Express Project Creation Quick Start Guide — April 2002________________ If your project includes any of the 2D disciplines, the Define 2D Reference DataLocation form is displayed, and you go to Step 43. Otherwise, the Copy Files toProject 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 thefiles copied from) and destination (where you want the files copied to) for thereference data. The default nodes and paths are read from the express.txt file usedto create the project.

Use the scroll bars to review the displayed data. To change the node name andpath for one file, simply click on the field you want to edit and key in the revisedinformation.

You can change all of the source node names by selecting the Change SourceNode Names To field and entering a new node name. The Substitute SourceRoot Paths From/To fields enable you to change groups of source pathnames.Similarly, the Change Destination Node Names To and Substitute DestinationRoot Paths From/To fields enable you to change groups of destination nodenames and pathnames for the new project.

Once you have defined the reference data to be used in the new project, chooseConfirm to continue.


46

Ad

vanced

User

Creating a Customized Project________________ 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 youwant the delivered files copied to) for the 2D reference data. The default nodes andpaths 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 andpath for one file, simply click on the field you want to edit and key in the revisedinformation.

You can change all of the node names by selecting the Change Node Names Tofield and entering a new node name. The Substitute Root Paths From/To fieldsenable you to change groups of pathnames.

Once you have defined the reference data to be used in the new project, chooseConfirm to continue.


The Copy Files to Project Directory form is displayed.


47


The Copy Files to Project Directory form displays a list of files to be copied toyour project. The File Description and File Name fields are not editable. The filedescriptions match the keywords in the express.txt file.

Use the scroll bars to review the displayed information. The Node and Pathcolumns reflect the values read from the express.txt file that was used to create theproject.

You can change the Node and Path specifications for an individual file by clickingon the field you want to change and entering the revised information. To changeall of the nodes, select the Change Node Names To field, and enter the new nodename. The Substitute Root Paths From/To fields enable you to quickly changegroups of pathnames.

Once you have defined the location of the project files to be used to create the newproject, choose Confirm to continue.


The Define Default Miscellaneous File Locations form is displayed.

48

Ad

vanced

User



The Define Default Miscellaneous File Locations form is much like the CopyFiles to Project Directory form. Instead of dealing primarily with seed, border,category, and configuration files, the Define Default Miscellaneous FileLocations form establishes the location for a variety of files that are specific tocertain 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 Pathcolumns reflect the values read from the express.txt file that was used to create theproject.

You can change the Node and Path specifications for an individual file by clickingon the field you want to change and entering the revised information. To changeall of the nodes, select the Change Node Names To field, and enter the new nodename. The Substitute Root Paths From/To fields enable you to quickly changegroups of pathnames.

Once you have defined the location of the project files to be used to create the newproject, choose Confirm to continue.

If the program is unable to locate a specified file, a message box isdisplayed. When you close the message box, the file that caused theproblem is highlighted in red. Edit the field as necessary, andchoose Confirm to continue.

49

PDS Express Project Creation Quick Start Guide — April 2002________________ If your project includes structural data, the Create FrameWorks Sub-Projectform 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, theproject name, the node name of the system, the directory in which the FrameWorksinformation is to be stored, the force units for the sub-project, and the name of thestandard section table. Be sure to press return to enter the information in eachfield.

When specifying the path, you must specify a full path name.Relative path names are not valid input for this field. Also, notethat the directories for the structural sub-project are created suchthat the directory specified in the Sub-Project Number field iscreated as a subdirectory of the directory specified in the Sub-Project Name field.

47. Accept or Modify Sub-Project Data

Once you have specified all of the sub-project information, choose Confirm tocontinue.

A dialog box is displayed indicating that the project was successfully created, anda log file named express.log is created in the project directory. If there are severeerrors during the creating process, the system will try to clean up the database sothat you can re-create the project after resolving the errors.

50

express.txt

Understanding the express.txt File________________

4. Understanding the express.txtFile

The express.txt file enables you to customize the way a project is created. This file isread whether you create a project using the New User mode or the Advanced Usermode. With Advanced User mode, you can modify the file settings as you create theproject; in New User mode, many of the settings in the express.txt file are inferred fromresponses 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 thedirectory 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 filescan only be used in Advanced User mode.

In the Advanced User mode, you can use a specific express.txt file. This file can belocated in any directory on any computer recognized through the network by yourcomputer. It can also have any file name. Its contents, however, must follow thestructure of the delivered express.txt file.

The express.txt file uses primary and secondary keywords to set variables needed tocreate a project. Primary keywords are on a line by themselves and are followed by acolon (:). You cannot edit primary keywords. Secondary keywords set the variable data.Secondary keywords are always followed by an equal sign (=). You can edit theinformation on the right side of the equal sign to be the value you want, but you cannotchange the keyword. That is, you can change the value for the keyword, but not thekeyword 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 acomment.

In New User mode, information in the file is replaced either by information that you keyin (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 thecomputer on which the PDS software resides. This text is replaced by the values readfrom the system registry. (This information is added to the system registry whenever youinstall software.) Other information, such as the value for file_server_node (thenode name of the computer on which the project data resides), is replaced by the nodename you enter on the Server Names & Drive Letters form.

For a complete printout of the delivered express.txt file, see Appendix A.

51

PDS Express Project Creation Quick Start Guide — April 2002________________ 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.

Seed Data

Piping_Seed_Model — Specifies the node name and directory of the seed filefor piping models .

Equipment_Seed_Model — Specifies the node name and directory of the seedfile for equipment models.

Raceway_Seed_Model — Specifies the node name and directory of the seedfile for raceway models.

Default_Seed_Drawing — Specifies the node name and directory of thedefault piping drawing seed file.

Alternate_Seed_Drawing — Specifies the node name and directory for thealternate drawing seed files. There is a separate entry for each drawing type.

Orthographic_Drawing_Plot_Size_Table — Specifies the node nameand directory of the plot size table for orthographic drawings (drawplotsize).

Drawing_Cell_Library — Specifies the node name and directory of thedrawing cell libraries (drawing.cel).

Drawing_Labels_per_Object_Type — Specifies the node name anddirectory of the drawing labels. There is a separate entry for each drawing type(labels.***, where *** is the drawing type number, such as 643 for EquipmentArrangements).

Instrument_Objects_for_Drawing_Annotation — Specifies the nodename and directory for the instrument objects that are used for annotating drawings(in_object.dwg).

Equipment_Objects_for_Drawing_Annotation — Specifies the nodename and directory for the equipment objects that are used for annotating drawings(eqp_object.dwg).

52

express.txt

Understanding the express.txt File________________ Label_Button_for_Drawing_Annotation — Specifies the node nameand directory for the ASCII file that defines the label placement form for theDrawing Mass Annotation command (lab_button.dwg).

Equipment_Centerline_Definitions_for_Drawings — Specifiesthe node name and directory for the equipment centerlines file (eqp_center.dwg).

Clash_Plot_Cell_Library — Specifies the node name and directory for thecell library to be used for clash reports (clash_plot.cel).

Clash_Plot_Border — Specifies the node name and directory for the borderfile to be used for clash reports (borderifc.dgn).

Clash_Plot_Settings — Specifies the node name and directory for thesettings file for plotting clashes (ifc.i).

Piping_Model_Category_Descriptions_by_NPD — Specifies the nodename and directory for the file that sorts piping category descriptions by nominalpipe diameter (pipecats1.txt).

Piping_Model_Category_Descriptions_by_Fluid_Code —Specifies the node name and directory for the file that sorts piping categorydescriptions by fluid code (pipecats2.txt).

Drawing_Category_Descriptions — Specifies the node name anddirectory of the drawing category descriptions file. (drwcats.txt).

FrameWorks_Category_Descriptions — Specifies the node name anddirectory of the FrameWorks category descriptions file (framewks.txt).

ModelDraft_Category_Descriptions — Specifies the node name anddirectory of the ModelDraft category descriptions file (symbology.sms).

Raceway_Configuration_File — Specifies the node name and directory ofthe Raceway configuration file (ee.cfg).

PID_to_Piping_NPD_Equivalent_Table — Specifies the node name anddirectory of the nominal pipe diameter equivalent table for P&ID-to-Piping datatransfer (pid_npd_equiv).

PID_to_Piping_Correlation_Table — Specifies the node name anddirectory 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 forthe queue descriptions file (queue_descript).

RDB_Option_File — Specifies the node name and directory of the referencedatabase options file used by the Interactive Spec Writer command (RDB_options).

53

PDS Express Project Creation Quick Start Guide — April 2002________________ Standard_Note_Maximum_Length_Table — Specifies the node name anddirectory of the maximum length table for standard notes (stnote_max_len).

Spec_Order_Maximum_Length_Table — Specifies the node name anddirectory of the file that contains the table of specification attribute orders and theirrelated maximum lengths (spec_order.max).

Default File Locations

PDS_Project_Directory — Specifies the node name and directory for thePDS project directory.

Raceway_Project_Directory — Specifies the node name and directory forthe raceway data.

Piping_Models — Specifies the node name and directory for the pipingmodels.

Equipment_Models — Specifies the node name and directory for theequipment models.

HVAC_Models — Specifies the node name and directory for the HVAC models.

Architectural_Models — Specifies the node name and directory for thearchitectural models.

Orthographic_Drawings_by_Drawing_Type — Specifies the node nameand directory for the orthographic drawings, ordered by drawing type. There is oneentry for each drawing type.

Drawing_Borders — Specifies the node name and directory for drawingborders.

Piping_Eden_Source — Specifies the default location (node name anddirectory) 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 anddirectory) for the neutral files to be used to load the Specification/MaterialReference Database and Material Description Libraries.

Piping_Assembly_Source — Specifies the default location (node name anddirectory) for the Piping Assembly Language source files.

Standard_Note_Library_Source — Specifies the default location (nodename and directory) for Standard Note (code list) source files.

54

express.txt

Understanding the express.txt File________________ Equipment_Eden_Source — Specifies the default location (node name anddirectory) for the Equipment Eden source files.

TDF_Table_Source — Specifies the default location (node name anddirectory) for Equipment table definition files.

Model_Builder_Source — Specifies the default location (node name anddirectory) for model builder language source files.

Design_Review_Model — Specifies the node name and directory forDesignReview models and tags.

Reports — Specifies the node name and directory for MTO reports.

Report_Formats — Specifies the node name and directory for report formatfiles.

Report_Discrimination_Data — Specifies the node name and directoryfor report discrimination data.

Report_Search_Criteria_Data — Specifies the node name and directoryfor report search criteria data.

Clash_Reports — Specifies the node name and directory for interference clashplot reports.

Clash_Plots — Specifies the node name and directory for interference designfiles.

Equipment_IForms — Specifies the node name and directory for the formsused by the PD_Eqp (Equipment) module.

RDB Libraries

A_Standard_Note_Library — Specifies the node name, directory, and filename for the approved standard note library.

U_Standard_Note_Library — Specifies the node name, directory, and filename for the unapproved standard note library.

A_Label_Description_Library — Specifies the node name, directory, andfile name for the approved label description library.

U_Label_Description_Library — Specifies the node name, directory, andfile name for the unapproved label description library.

A_Piping_Assembly_Library — Specifies the node name, directory, andfile name for the approved piping assembly library.

55

PDS Express Project Creation Quick Start Guide — April 2002________________ U_Piping_Assembly_Library — Specifies the node name, directory, andfile name for the unapproved piping assembly library.

A_Graphic_Commodity_Library — Specifies the node name, directory, andfile name for the approved graphic commodity library.

U_Graphic_Commodity_Library — Specifies the node name, directory, andfile 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, andfile name for the approved U.S. physical data library.

U_US_Physical_Data_Library — Specifies the node name, directory, andfile name for the unapproved U.S. physical data library.

A_DIN_Physical_Data_Library — Specifies the node name, directory, andfile name for the approved DIN physical data library.

U_DIN_Physical_Data_Library — Specifies the node name, directory, andfile name for the unapproved DIN physical data library.

A_British_Standard_Physical_Data_Library — Specifies the nodename, directory, and file name for the approved British standard physical datalibrary.

U_British_Standard_Physical_Data_Library — Specifies the nodename, directory, and file name for the unapproved British standard physical datalibrary.

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, andfile name for the approved JIS physical data library.

56

express.txt

Understanding the express.txt File________________ U_JIS_Physical_Data_Library — Specifies the node name, directory, andfile 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 nodename, directory, and file name for the approved International A physical datalibrary.

U_International_A_Physical_Data_Library — Specifies the nodename, directory, and file name for the unapproved International A physical datalibrary.

A_International_B_Physical_Data_Library — Specifies the nodename, directory, and file name for the approved International B physical datalibrary.

U_International_B_Physical_Data_Library — Specifies the nodename, directory, and file name for the unapproved International B physical datalibrary.

A_Company_Practice_Physical_Data_Library — Specifies the nodename, directory, and file name for the approved company practice physical datalibrary.

U_Company_Practice_Physical_Data_Library — Specifies the nodename, directory, and file name for the unapproved company practice physical datalibrary.

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 nodename, directory, and file name for the approved specialty material descriptionlibrary.

U_Specialty_Material_Description_Library — Specifies the nodename, directory, and file name for the unapproved specialty material descriptionlibrary.

57

PDS Express Project Creation Quick Start Guide — April 2002________________ A_Equipment_Graphic_Commodity_Library — Specifies the nodename, directory, and file name for the approved equipment graphic commoditylibrary.

U_Equipment_Graphic_Commodity_Library — Specifies the nodename, directory, and file name for the unapproved equipment graphic commoditylibrary.

A_Equipment_Tutorial_Definition_Library — Specifies the nodename, directory, and file name for the approved equipment tutorial definitionlibrary.

U_Equipment_Tutorial_Definition_Library — Specifies the nodename, directory, and file name for the unapproved equipment tutorial definitionlibrary.

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 filename for the approved equipment cell library.

U_Equipment_Cell_Library — Specifies the node name, directory, and filename 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 2Dreference data.

PID_Reference_Data — Specifies the node name and directory for the P&IDreference data.

PFD_Reference_Data — Specifies the node name and directory for the PFDreference data.

58

Ap

pen

dix A

Appendix A: The express.txt File________________

Appendix A 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’ == node name of location for PDS products! ’file_server_node’ == node name of file server for PDS project! ’design_review_node’ == 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’ == drive letter of location for PDS products! ’pds_project_data’ == drive letter of location for PDS project data! ’pds_model_data’ == drive letter of location for PDS model data! ’pds_dwg_data’ == drive letter of location for PDS drawing data! ’pds_3d_rdb_data’ == drive letter of location for PDS 3D reference data! ’pds_report_data’ == drive letter of location for PDS report data! ’pds_clash_data’ == drive letter of location for PDS clash data! ’pds_review_data’ == drive letter of location for DesignReview data! ’pds_2d_rdb_data’ == drive letter of location for PDS 2D reference data

!\! Source for Seed Data to be Copied to PDS Project Directory!/

Piping_Seed_Model:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\seedz

Equipment_Seed_Model:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\seedz

Raceway_Seed_Model:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\eerway\dgn\seed

Default_Seed_Drawing:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\seedz

Alternate_Seed_Drawing:! Foundation Location Drawings

Drawing_Type = 535Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\seedz

59

PDS Express Project Creation Quick Start Guide — April 2002________________ Alternate_Seed_Drawing:! Piling Drawings


Alternate_Seed_Drawing:! Structural Perspectives, Plans, Sections and Details


Alternate_Seed_Drawing:! Plot Plans


Alternate_Seed_Drawing:! Equipment Arrangement Drawings


Alternate_Seed_Drawing:! Piping Underground Drawings


Alternate_Seed_Drawing:! Equipment Orientations


Alternate_Seed_Drawing:! Piping One Line Drawings


Alternate_Seed_Drawing:! Piping Perspectives, Plans, Sections and Details


Alternate_Seed_Drawing:! Pipeline Alignment Drawings


Alternate_Seed_Drawing:! Instrument Location Plans


60

Ap

pen

dix A

Appendix A: The express.txt File________________ Alternate_Seed_Drawing:! Electrical Area Classification Drawings


Alternate_Seed_Drawing:! Electrical Underground Drawings


Alternate_Seed_Drawing:! Lighting Perspectives, Plans, Sections and Details


Alternate_Seed_Drawing:! HVAC Perspectives, Plans, Sections and Details


Orthographic_Drawing_Plot_Size_Table:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\plot

Drawing_Cell_Library:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\cell

Drawing_Labels_per_Object_Type:! Foundation Location Drawings

Drawing_Type = 535Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddraw\sample

Drawing_Labels_per_Object_Type:! Piling Drawings


Drawing_Labels_per_Object_Type:! Structural Perspectives, Plans, Sections and Details


Drawing_Labels_per_Object_Type:! Plot Plans


Drawing_Labels_per_Object_Type:! Equipment Arrangement Drawings


61

PDS Express Project Creation Quick Start Guide — April 2002________________ Drawing_Labels_per_Object_Type:! Piping Underground Drawings


Drawing_Labels_per_Object_Type:! Equipment Orientations


Drawing_Labels_per_Object_Type:! Piping One Line Drawings


Drawing_Labels_per_Object_Type:! Piping Perspectives, Plans, Sections and Details


Drawing_Labels_per_Object_Type:! Pipeline Alignment Drawings


Drawing_Labels_per_Object_Type:! Instrument Location Plans


Drawing_Labels_per_Object_Type:! Electrical Area Classification Drawings


Drawing_Labels_per_Object_Type:! Electrical Underground Drawings


Drawing_Labels_per_Object_Type:! Lighting Perspectives, Plans, Sections and Details


Drawing_Labels_per_Object_Type:! HVAC Perspectives, Plans, Sections and Details


62

Ap

pen

dix A

Appendix A: The express.txt File________________ Instrument_Objects_for_Drawing_Annotation:

Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddraw\sample

Equipment_Objects_for_Drawing_Annotation:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddraw\sample

Label_Button_for_Drawing_Annotation:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddraw\sample

Equipment_Centerline_Definitions_for_Drawings:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddraw\sample

Clash_Plot_Cell_Library:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\cell

Clash_Plot_Border:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\border

Clash_Plot_Settings:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\plot

Piping_Model_Category_Descriptions_by_NPD:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\categ

Piping_Model_Category_Descriptions_by_Fluid_Code:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\categ

Drawing_Category_Descriptions:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\categ

FrameWorks_Category_Descriptions:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\categ

ModelDraft_Category_Descriptions:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\categ

Raceway_Configuration_File:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\eenuc

PID_to_Piping_NPD_Equivalent_Table:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\pid

PID_to_Piping_Correlation_Table:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\pid

63

PDS Express Project Creation Quick Start Guide — April 2002________________ Queue_Description_Library:

Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\plot

RDB_Option_File:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddata\sample\data

Standard_Note_Maximum_Length_Table:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\lib

Spec_Order_Maximum_Length_Table:! Copied to Piping_Spec_Source - not Project Directory

Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pddata\sample\format

!\! Default File Locations!/

PDS_Project_Directory:Node = file_server_nodePath = pds_project_data:\pds\project

Raceway_Project_Directory:Node = file_server_nodePath = pds_model_data:\pds\raceway

Piping_Models:Default_Node = file_server_nodeDefault_Path = pds_model_data:\pds\models\piping

Equipment_Models:Default_Node = file_server_nodeDefault_Path = pds_model_data:\pds\models\eqp

HVAC_Models:Default_Node = file_server_nodeDefault_Path = pds_model_data:\pds\models\hvac

Architectural_Models:Default_Node = file_server_nodeDefault_Path = pds_model_data:\pds\models\arch

Orthographic_Drawings_by_Drawing_Type:! Foundation Location Drawings

Drawing_Type = 535Default_Node = file_server_nodeDefault_Path = pds_dwg_data:\pds\dwg\535

Orthographic_Drawings_by_Drawing_Type:! Piling Drawings


Orthographic_Drawings_by_Drawing_Type:! Structural Perspectives, Plans, Sections and Details


64

Ap

pen

dix A

Appendix A: The express.txt File________________ Orthographic_Drawings_by_Drawing_Type:! Plot Plans


Orthographic_Drawings_by_Drawing_Type:! Equipment Arrangement Drawings


Orthographic_Drawings_by_Drawing_Type:! Piping Underground Drawings


Orthographic_Drawings_by_Drawing_Type:! Equipment Orientations


Orthographic_Drawings_by_Drawing_Type:! Piping One Line Drawings


Orthographic_Drawings_by_Drawing_Type:! Piping Perspectives, Plans, Sections and Details


Orthographic_Drawings_by_Drawing_Type:! Pipeline Alignment Drawings


Orthographic_Drawings_by_Drawing_Type:! Instrument Location Plans


Orthographic_Drawings_by_Drawing_Type:! Electrical Area Classification Drawings


Orthographic_Drawings_by_Drawing_Type:! Electrical Underground Drawings


65

PDS Express Project Creation Quick Start Guide — April 2002________________ Orthographic_Drawings_by_Drawing_Type:! Lighting Perspectives, Plans, Sections and Details


Orthographic_Drawings_by_Drawing_Type:! HVAC Perspectives, Plans, Sections and Details


Drawing_Borders:! PDS Drawing Borders will be copied into specified location for new users only

Node = file_server_nodePath = pds_dwg_data:\pds\dwg\border

Piping_Eden_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\eden_piping

Dimension_or_Spec_Table_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\table

Piping_Spec_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\spec

Piping_Assembly_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\assembly

Standard_Note_Library_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\std_note

Equipment_Eden_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\eden_eqp

TDF_Table_Source:Default_Node = file_server_nodeDefault_Path = pds_3d_rdb_data:\pds\rdb\source\eqp\tdf

Model_Builder_Source:Default_Node = file_server_nodeDefault_Path = pds_model_data:\pds\model_builder

Design_Review_Model:Destination_Node = design_review_nodeDestination_Path = pds_review_data:\pds\design_review

Reports:Default_Node = file_server_nodeDefault_Path = pds_report_data:\pds\report\mto

Report_Formats:Default_Node = file_server_nodeDefault_Path = pds_report_data:\pds\report\format

66

Ap

pen

dix A

Appendix A: The express.txt File________________ Report_Discrimination_Data:

Default_Node = file_server_nodeDefault_Path = pds_report_data:\pds\report\discrimination

Report_Search_Criteria_Data:Default_Node = file_server_nodeDefault_Path = pds_report_data:\pds\report\search

Clash_Reports:Destination_Node = file_server_nodeDestination_Path = pds_clash_data:\pds\clash\report

Clash_Plots:Destination_Node = file_server_nodeDestination_Path = pds_clash_data:\pds\clash\plot

Equipment_IForms:Source_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp

!\! Locations of Approved and Unapproved RDB Libraries!/

A_Standard_Note_Library:Source_File = std_note.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = std_note.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Standard_Note_Library:Source_File = std_note.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = std_note.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Label_Description_Library:Source_File = labels.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = labels.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Label_Description_Library:Source_File = labels.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = labels.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Piping_Assembly_Library:Source_File = assembly.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = assembly.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

67

PDS Express Project Creation Quick Start Guide — April 2002________________ U_Piping_Assembly_Library:

Source_File = assembly.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = assembly.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Graphic_Commodity_Library:Source_File = pip_gcom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = pip_gcom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Graphic_Commodity_Library:Source_File = pip_gcom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\libDestination_File = pip_gcom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Piping_Spec_Job_Table_Library:Source_File = us_pjstb.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_pjstb.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Piping_Spec_Job_Table_Library:Source_File = us_pjstb.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_pjstb.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_US_Physical_Data_Library:Source_File = us_pcdim.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_US_Physical_Data_Library:Source_File = us_pcdim.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_DIN_Physical_Data_Library:Source_File = din_pcdim.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rddinrdb\piping\libsDestination_File = din_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

68

Ap

pen

dix A

Appendix A: The express.txt File________________ U_DIN_Physical_Data_Library:

Source_File = din_pcdim.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rddinrdb\piping\libsDestination_File = din_pcdim.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_JIS_Physical_Data_Library:Source_File =Source_Node =Source_Path =Destination_File = jis_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

69

PDS Express Project Creation Quick Start Guide — April 2002________________ U_JIS_Physical_Data_Library:

Source_File =Source_Node =Source_Path =Destination_File = jis_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Australian_Physical_Data_Library:Source_File =Source_Node =Source_Path =Destination_File = aus_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Australian_Physical_Data_Library:Source_File =Source_Node =Source_Path =Destination_File = aus_pcdim.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_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.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

70

Ap

pen

dix A

Appendix A: The express.txt File________________ U_Company_Practice_Physical_Data_Library:

Source_File =Source_Node =Source_Path =Destination_File = cmp_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Short_Material_Description_Library:Source_File = us_shbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_shbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Short_Material_Description_Library:Source_File = us_shbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_shbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Long_Material_Description_Library:Source_File = us_lgbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_lgbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Long_Material_Description_Library:Source_File = us_lgbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_lgbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Specialty_Material_Description_Library:Source_File = us_spbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_spbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Specialty_Material_Description_Library:Source_File = us_spbom.lSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\rdusrdbDestination_File = us_spbom.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Equipment_Graphic_Commodity_Library:Source_File = zi_eqpms.libSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = zi_eqpms.libDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved

71

PDS Express Project Creation Quick Start Guide — April 2002________________ U_Equipment_Graphic_Commodity_Library:

Source_File = zi_eqpms.libSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = zi_eqpms.libDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved

A_Equipment_Tutorial_Definition_Library:Source_File = zi_tutlib.libSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = zi_tutlib.libDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved

U_Equipment_Tutorial_Definition_Library:Source_File = zi_tutlib.libSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = zi_tutlib.libDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved

A_Equipment_Physical_Data_Library:Source_File =Source_Node =Source_Path =Destination_File = us_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\approved

U_Equipment_Physical_Data_Library:Source_File =Source_Node =Source_Path =Destination_File = us_pcdim.lDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\lib\unapproved

A_Equipment_Cell_Library:Source_File = equip.celSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = equip.celDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\approved

U_Equipment_Cell_Library:Source_File = equip.celSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdeqp\datDestination_File = equip.celDestination_Node = file_server_nodeDestination_Path = pds_3d_rdb_data:\pds\rdb\eqp\unapproved

!\! Drawing Cell Libraries for each Drawing Type!/

72

Ap

pen

dix A

Appendix A: The express.txt File________________ Drawing_Cell_Library_by_Drawing_Type:! Foundation Location Drawings

Drawing_Type = 535Source_File = drawing.celSource_Node = software_nodeSource_Path = pds_product:\win32app\ingr\pdshell\cellDestination_File = dwg_535.celDestination_Node = file_server_nodeDestination_Path = pds_dwg_data:\pds\dwg\cell

Drawing_Cell_Library_by_Drawing_Type:! Piling Drawings


Drawing_Cell_Library_by_Drawing_Type:! Structural Perspectives, Plans, Sections and Details


Drawing_Cell_Library_by_Drawing_Type:! Plot Plans


Drawing_Cell_Library_by_Drawing_Type:! Equipment Arrangement Drawings


Drawing_Cell_Library_by_Drawing_Type:! Piping Underground Drawings


73

PDS Express Project Creation Quick Start Guide — April 2002________________ Drawing_Cell_Library_by_Drawing_Type:! Equipment Orientations


Drawing_Cell_Library_by_Drawing_Type:! Piping One Line Drawings


Drawing_Cell_Library_by_Drawing_Type:! Piping Perspectives, Plans, Sections and Details


Drawing_Cell_Library_by_Drawing_Type:! Pipeline Alignment Drawings


Drawing_Cell_Library_by_Drawing_Type:! Instrument Location Plans


Drawing_Cell_Library_by_Drawing_Type:! Electrical Area Classification Drawings


74

Ap

pen

dix A

Appendix A: The express.txt File________________ Drawing_Cell_Library_by_Drawing_Type:! Electrical Underground Drawings


Drawing_Cell_Library_by_Drawing_Type:! Lighting Perspectives, Plans, Sections and Details


Drawing_Cell_Library_by_Drawing_Type:! HVAC Perspectives, Plans, Sections and Details


!\! Reference Data Locations for All 2D Disciplines!/

PDS2D_Reference_Data:Node = file_server_nodePath = pds_2d_rdb_data:\pds\pds2d\rdb

PID_Reference_Data:Node = file_server_nodePath = pds_2d_rdb_data:\pds\pid\rdb

PFD_Reference_Data:Node = file_server_nodePath = 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 =

!! Notes:!

75

PDS Express Project Creation Quick Start Guide — April 2002________________ ! 1) The value for each drawing type, Drawing_Type = xxx, should be extracted! from CL2000 in the Standard Note Library.!

76

Ap

pen

dix B

Appendix B: Sample Data________________

Appendix B 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 EnglishRD_USRDB English Metric MixedRD_USRDB Metric Metric MetricRD_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 unlessyou have the RD_DINRDB product installed on your system. In that case, the DIN projectis loaded.

Information in the Delivered Dataset

Each dataset contains a file named sample_data.txt, which identifies the files to be loaded for thatdataset.

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.

77


No example specs are loaded for any of the sample projects. You must load specsin the specification /material reference database before you can work in the newproject.

P&ID Assemblies

In addition to the sample datasets, P&ID assemblies are also delivered to enable you to createP&IDs that correspond to the sample projects.

English/Mixed project — 38pi1.asm, 39pi1.asm, 40pi1.asm, 40pi1.asm, 40pi2.asm, and41pi1.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 createthe 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 theP&IDs. You can propagate the created drawings to load the information into the P&ID database.

78

Ap

pen

dix C

Appendix C: Delivered SQL Scripts________________

Appendix C 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 ofcreating the required database information before creating a new PDS project or to dropinformation from the database after deleting a PDS project.

These scripts have been provided as examples and should not be used until a databasemanager at your site has reviewed them to ensure that they will be usable in a specificdatabase environment.

Intergraph Corporation assumes no risks or responsibilities regarding the use of thesefiles. They are provided for use at your discretion.

These scripts require that the database engine has already been installed and configured to supportthe creation of new databases/users. Use a text editor to review the comments at the top of eachfile 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.

˜\pdshell\sql\sybsql\create.sql — Script to create all Sybase SQL databases for a PDSproject.

˜\pdshell\sql\sybsql\drop.sql — Script to drop all Sybase SQL databases for a PDS project.

79


80

Ind

ex

Index________________

Index 2D reference data 58

AA_Australian_Physical_Data_Library keyword 57A_British_Standard_Physical_Data_Library keyword

56A_Company_Practice_Physical_Data_Library

keyword 57additional resources

related documents 7A_DIN_Physical_Data_Library keyword 56Advanced User mode 16, 27

how to use 27A_Equipment_Cell_Library keyword 58A_Equipment_Graphic_Commodity_Library

keyword 58A_Equipment_Physical_Data_Library keyword 58A_Equipment_Tutorial_Definition_Library keyword

58A_European_A_Physical_Data_Library keyword 56A_European_B_Physical_Data_Library keyword 56A_Graphic_Commodity_Library keyword 56A_International_A_Physical_Data_Library keyword

57A_International_B_Physical_Data_Library keyword

57A_JIS_Physical_Data_Library keyword 56A_Label_Description_Library keyword 55A_Long_Material_Description_Library keyword 57Alternate_Seed_Drawing keyword 52A_Piping_Assembly_Library keyword 55A_Piping_Spec_Job_Table_Library keyword 56Architectural_Models keyword 54A_Short_Material_Description_Library keyword 57A_Specialty_Material_Description_Library keyword

57A_Standard_Note_Library keyword 55attributes 35

case sensitive 37displaying 36modifying 35

Attributes to be Case Insensitive option 37Attributes to be Displayed option 36A_US_Physical_Data_Library keyword 56

Bborderifc.dgn file 53

Ccase sensitive attributes 37cell libraries 58Clash_Plot_Border keyword 53clash_plot.cel file 53Clash_Plot_Cell_Library keyword 53Clash_Plots keyword 55Clash_Plot_Settings keyword 53Clash_Reports keyword 55contents of document 7Copy Delivered RDB Data to New Project option 44Copy Existing RDB to New Project option 42, 44Copy Files to Project Directory form 47Copy RDB Data option 43Create Database Schemas form 21, 32Create FrameWorks Sub-Project form 25, 50Create Project Control Schema form 22, 32customization 51customized projects 27

DDatabase Customization Options form 34Database Management System Location field 24, 33Database Name field 23, 33Database Structure Revision form 34Database Username field 23, 33DBAccess 39DBTEMP field 24, 34default directory structure 17default file locations 54Default_Seed_Drawing keyword 52Define Default Miscellaneous File Locations form

48Define Location for New RDB option 42, 44Define Project Data form 19, 28Define RDB File Locations form 40Define System Units form 20, 29Design_Review_Model keyword 55Dimension_or_Spec_Table_Source keyword 54directory structure

default 17document organization 7

81

PDS Express Project Creation Quick Start Guide — April 2002________________ document overview 7Drawing_Borders keyword 54Drawing_Category_Descriptions keyword 53drawing.cel file 52Drawing_Cell_Library keyword 52Drawing_Cell_Library_by_Drawing_Type keyword

58Drawing_Labels_per_Object_Type keyword 52drawplotsize file 52drwcats.txt file 53DSQUERY field 24, 34

Eee.cfg file 53eqp_center.dwg file 53eqp_object.dwg file 52Equipment_Centerline_Definitions_for_Drawings

keyword 53Equipment_Eden_Source keyword 55Equipment_IForms keyword 55Equipment_Models keyword 54Equipment_Objects_for_Drawing_Annotation

keyword 52Equipment_Seed_Model keyword 52express.txt file 18, 51

2D reference data 58cell libraries 58default file locations 54RDB libraries 55seed files 52syntax 51

Ffiles

2D reference data 58borderifc.dgn 53cell libraries 58clash_plot.cel 53default locations 54drawing.cel 52drawplotsize 52drwcats.txt 53ee.cfg 53eqp_center.dwg 53eqp_object.dwg 52express.txt 18, 51framewks.txt 53ifc.i 53in_object.dwg 52lab_button.dwg 53pid_npd_equiv 53

files (continued)pid_to_piping 53pipecats2.txt 53pipecats.txt 53queue_descript 53RDB libraries 55RDB_options 53spec_order.max 54stnote_max_len 54symbology.sms 53

formsCopy Files to Project Directory 47Create Database Schemas 21, 32Create FrameWorks Sub-Project 25, 50Create Project Control Schema 22, 32Database Customization Options 34Database Structure Revision 34Define Default Miscellaneous File Locations 48Define Project Data 19, 28Define RDB File Locations 40Define System Units 20, 29Revise Working Units 31Server Names & Drive Letters 24

framewks.txt file 53FrameWorks_Category_Descriptions keyword 53

HHVAC_Models keyword 54

Iifc.i file 53in_object.dwg file 52Instrument_Objects_for_Drawing_Annotation

keyword 52introduction 13

Kkeyword

Label_Button_for_Drawing_Annotation 53keywords

A_Australian_Physical_Data_Library 57A_British_Standard_Physical_Data_Library 56A_Company_Practice_Physical_Data_Library 57A_DIN_Physical_Data_Library 56A_Equipment_Cell_Library 58A_Equipment_Graphic_Commodity_Library 58A_Equipment_Physical_Data_Library 58A_Equipment_Tutorial_Definition_Library 58A_European_A_Physical_Data_Library 56A_European_B_Physical_Data_Library 56A_Graphic_Commodity_Library 56

82

Ind

ex

Index________________ keywords (continued)

A_International_A_Physical_Data_Library 57A_International_B_Physical_Data_Library 57A_JIS_Physical_Data_Library 56A_Label_Description_Library 55A_Long_Material_Description_Library 57Alternate_Seed_Drawing 52A_Piping_Assembly_Library 55A_Piping_Spec_Job_Table_Library 56Architectural_Models 54A_Short_Material_Description_Library 57A_Specialty_Material_Description_Library 57A_Standard_Note_Library 55A_US_Physical_Data_Library 56Clash_Plot_Border 53Clash_Plot_Cell_Library 53Clash_Plots 55Clash_Plot_Settings 53Clash_Reports 55Default_Seed_Drawing 52Design_Review_Model 55Dimension_or_Spec_Table_Source 54Drawing_Borders 54Drawing_Category_Descriptions 53Drawing_Cell_Library 52Drawing_Cell_Library_by_Drawing_Type 58Drawing_Labels_per_Object_Type 52Equipment_Centerline_Definitions_for_Drawings

53Equipment_Eden_Source 55Equipment_IForms 55Equipment_Models 54Equipment_Objects_for_Drawing_Annotation 52Equipment_Seed_Model 52FrameWorks_Category_Descriptions 53HVAC_Models 54Instrument_Objects_for_Drawing_Annotation 52Model_Builder_Source 55ModelDraft_Category_Descriptions 53Orthographic_Drawing_Plot_Size_Table 52Orthographic_Drawings_by_Drawing_Type 54PDS2D_Reference_Data 58PDS_Project_Directory 54PFD_Reference_Data 58PID_Reference_Data 58PID_to_Piping_Correlation_Table 53PID_to_Piping_NPD_Equivalent_Table 53Piping_Assembly_Source 54Piping_Eden_Source 54Piping_Model_Category_Descriptions_by_Fluid_Code

53

keywords (continued)Piping_Model_Category_Descriptions_by_NPD

53Piping_Models 54Piping_Seed_Model 52Piping_Spec_Source 54Queue_Description_Library 53Raceway_Configuration_File 53Raceway_Project_Directory 54Raceway_Seed_Model 52RDB_Option_File 53Report_Discrimination_Data 55Report_Formats 55Reports 55Report_Search_Criteria_Data 55Spec_Order_Maximum_Length_Table 54Standard_Note_Library_Source 54Standard_Note_Maximum_Length_Table 54TDF_Table_Source 55U_Australian_Physical_Data_Library 57U_British_Standard_Physical_Data_Library 56U_Company_Practice_Physical_Data_Library 57U_DIN_Physical_Data_Library 56U_Equipment_Cell_Library 58U_Equipment_Graphic_Commodity_Library 58U_Equipment_Physical_Data_Library 58U_Equipment_Tutorial_Definition_Library 58U_European_A_Physical_Data_Library 56U_European_B_Physical_Data_Library 56U_Graphic_Commodity_Library 56U_International_A_Physical_Data_Library 57U_International_B_Physical_Data_Library 57U_JIS_Physical_Data_Library 57U_Label_Description_Library 55U_Long_Material_Description_Library 57U_Piping_Assembly_Library 56U_Piping_Spec_Job_Table_Library 56U_Short_Material_Description_Library 57U_Specialty_Material_Description_Library 57U_Standard_Note_Library 55U_US_Physical_Data_Library 56

Llab_button.dwg file 53Label_Button_for_Drawing_Annotation keyword 53

MModel_Builder_Source keyword 55ModelDraft_Category_Descriptions keyword 53modifying attributes 35

83

PDS Express Project Creation Quick Start Guide — April 2002________________ NNetwork Protocol field 23, 33New User mode 15, 17

how to use 18Node Name or Address field 23, 33

OOrthographic_Drawing_Plot_Size_Table keyword

52Orthographic_Drawings_by_Drawing_Type keyword

54OS Type field 23, 33OS Username field 23, 33overview 7

project setup 13

PPassword field 23, 33PDS2D_Reference_Data keyword 58PDS_Project_Directory keyword 54PFD_Reference_Data keyword 58pid_npd_equiv file 53PID_Reference_Data keyword 58pid_to_piping file 53PID_to_Piping_Correlation_Table keyword 53PID_to_Piping_NPD_Equivalent_Table keyword 53pipecats1.txt file 53pipecats2.txt file 53Piping_Assembly_Source keyword 54Piping_Eden_Source keyword 54Piping_Model_Category_Descriptions_by_Fluid_Code

keyword 53Piping_Model_Category_Descriptions_by_NPD

keyword 53Piping_Models keyword 54Piping_Seed_Model keyword 52Piping_Spec_Source keyword 54plant monument

entering coordinates 21plant monument coordinates 30preface 7prerequisites 14project schemas 32project setup overview 13project setup steps 13

Qqueue_descript file 53Queue_Description_Library keyword 53

RRaceway_Configuration_File keyword 53Raceway_Project_Directory keyword 54Raceway_Seed_Model keyword 52RDB libraries 55RDB_Option_File keyword 53RDB_options file 53related documents 7Report_Discrimination_Data keyword 55Report_Formats keyword 55reporting options 39Reports keyword 55Report_Search_Criteria_Data keyword 55Revise Working Units form 31

Sschemas 32seed files 52Server Names & Drive Letters form 24Share RDB with Existing Project option 42, 44spec_order.max file 54Spec_Order_Maximum_Length_Table keyword 54SQLEXEC field 24, 33Standard_Note_Library_Source keyword 54Standard_Note_Maximum_Length_Table keyword

54starting the program 14stnote_max_len file 54SYBIFILE field 24, 34symbology.sms file 53

TTBCONFIG field 24, 34TDF_Table_Source keyword 55typefaces 9

UU_Australian_Physical_Data_Library keyword 57U_British_Standard_Physical_Data_Library keyword

56U_Company_Practice_Physical_Data_Library

keyword 57U_DIN_Physical_Data_Library keyword 56U_Equipment_Cell_Library keyword 58U_Equipment_Graphic_Commodity_Library

keyword 58U_Equipment_Physical_Data_Library keyword 58U_Equipment_Tutorial_Definition_Library keyword

58U_European_A_Physical_Data_Library keyword 56

84

Ind

ex

Index________________ U_European_B_Physical_Data_Library keyword 56U_Graphic_Commodity_Library keyword 56U_International_A_Physical_Data_Library keyword

57U_International_B_Physical_Data_Library keyword

57U_JIS_Physical_Data_Library keyword 57U_Label_Description_Library keyword 55U_Long_Material_Description_Library keyword 57U_Piping_Assembly_Library keyword 56U_Piping_Spec_Job_Table_Library keyword 56User Defined Attributes option 36U_Short_Material_Description_Library keyword 57using Advanced User mode 27using the New User option 18U_Specialty_Material_Description_Library keyword

57U_Standard_Note_Library keyword 55U_US_Physical_Data_Library keyword 56

Wworking units 30

85


86

express

Documents

trademarks intergraph

assistance intergraph

intergraph logo

restricted computer

reliability of software

unpublished rights

covernotice dpds3pe

copyright laws