PDS Data Manager

695  Download (0)

Full text

(1)
(2)

Reference Data Manager

(PD_Data)

Reference Guide

Document Number

Version

Date

Pages

DPDS3-PB-200034A

PDS 7.1

April 2002

1-684

(3)

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.

The information and the software discussed in this document are subject to change without notice and should not be considered

commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility 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.

Trademarks

CLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DBACCESS, DesignReview, DIALOG, EE Raceway, FrameWorks, Project Engineer, and SEE are trademarks of Intergraph Corporation. All other brands and product names are trademarks of their respective owners.

Copyright

 1984-2002 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 and trade secret law 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 in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer

Software — Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished — rights reserved under the copyright laws of the United States. Intergraph Corporation

(4)

If You Need Assistance

________________

If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’s products, 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 to

http://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 at

http://www.intergraph.com.

Intergraph Directory

The following numbers are only valid in the United States unless otherwise indicated. If you are 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 & Offshore 300 Intergraph Way

Madison, Alabama 35758 U.S.A.

(5)

________________

Documentation Contacts

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

Mail Intergraph Process, Power & Offshore Documentation Manager

300 Intergraph Way Madison, AL 35758

(6)

Table of Contents

________________

Table of Contents

If You Need Assistance ... 3

Intergraph Directory ... 3 Preface ... 15 General Conventions ... 17 Keyboard Conventions ... 18 Terminology ... 19 1. Introduction ... 21 1.1 Project Organization ... 22

1.2 Reference Data Overview ... 23

1.2.1 Piping Job Specification Introduction ... 27

Graphic Commodity Data Introduction ... 27

Material Description Data Introduction ... 28

Standard Note Library Introduction ... 28

Label Description Library Introduction ... 29

Piping Assembly Library Introduction ... 29

1.3 Reference Database Introduction ... 30

1.4 Delivered Reference Data ... 31

1.5 Reference Data Setup ... 32

2. PDS Environment ... 33

PD Shell ... 34

PD_Shell Form Conventions ... 37

Common Tools on the PD Shell Forms ... 37

Batch Processes ... 40

Help ... 41

3. Reference Data Manager ... 43

3.1 Data Security ... 45

3.2 Reference Data Archival ... 46

4. Reference Data Location ... 47

4.1 Reference Database Management Data ... 48

(7)

Reference Data Manager Reference Guide — April 2002

________________

5. Piping Job Specification ... 55

5.1 Material Reference Database Structure ... 56

5.2 Neutral File Input ... 59

5.2.1 Piping Materials Class Data (201) ... 62

5.2.2 Piping Commodity Specification Data (202) ... 67

5.2.3 Piping Specialty Specification Data (203) ... 77

5.2.4 Instrument Component Specification Data (204) ... 81

5.2.5 Tap Properties Data (205) ... 85

5.2.6 Piping Commodity Size-Dependent Material Data (211) ... 88

5.2.7 Piping Commodity Implied Material Data (212) ... 91

5.2.8 Component Insulation Exclusion Data (231) ... 95

5.2.9 Flange Insulation Exclusion Data (232) ... 98

5.2.10 Piping Construction Tolerance Exclusion Data (233) ... 101

5.3 Spec Writer ... 103

5.3.1 RDB Options File ... 105

5.3.2 Piping Materials Class Data Command ... 113

5.3.2.1 Create/Revise Piping Materials Class Data ... 114

5.3.3 Piping Commodity Data Command ... 117

5.3.3.1 Create/Revise Piping Commodity Specification Data ... 119

5.3.3.2 Implied Data ... 126

5.3.3.3 Add Entry to Material Description Library ... 128

5.3.4 Piping Specialty Data Command ... 129

5.3.4.1 Create/Revise Piping Specialty Specification Data ... 130

5.3.5 Instrument Data Command ... 133

5.3.5.1 Create/Revise Instrument Specification Data ... 134

5.3.6 Tap Properties Data Command ... 137

5.3.6.1 Create/Revise Tap Properties Data ... 138

(8)

Table of Contents

________________

5.4.1 Load, Replace, and Replace Commodity Subset Options ... 148

5.4.2 Delete Option ... 151

5.4.3 Report Option ... 152

5.5 Piping Job Spec Report Manager ... 154

5.5.1 Using the Report Commands ... 155

5.5.2 Report Format Form ... 157

5.5.2.1 Format Creation/Revision Form ... 159

5.5.2.2 Format Deletion Form ... 161

5.5.3 Report Discrimination Data Form ... 163

5.5.3.1 Discrimination Data Creation Form ... 165

5.5.3.2 Search Criteria Form ... 167

5.5.3.3 Discrimination Data Revision Form ... 169

5.5.3.4 Discrimination Data Deletion Form ... 171

5.5.4 Report Form ... 173

5.5.4.1 Report Creation Form ... 175

5.5.4.2 Revise Report Form ... 178

5.5.4.3 Report Deletion Form ... 181

5.5.4.4 Report Approval Form ... 183

5.5.4.5 Report Multiple Submit Form ... 184

5.5.5 Report Management Defaults Form ... 186

6. Piping Job Specification Tables ... 189

6.1 PJS Tables and Functions ... 190

6.1.1 Temperature and Pressure Service Limits Table ... 191

6.1.2 Nominal Piping Diameters Table ... 194

6.1.3 Thickness Data Tables ... 197

6.1.4 Materials Data Table ... 200

6.1.5 Wall Thickness and Branch Reinforcement Equations ... 203

Delivered Equations ... 204

6.1.6 Branch Insertion Tables ... 208

6.1.7 Gasket Separation Table ... 212

6.1.8 Fluid Code Table ... 214

6.2 RDB Tables ... 215

6.2.1 Commodity Item Name Table (G02) ... 216

6.2.2 Bend Deflection Table (G04) ... 219

(9)

Reference Data Manager Reference Guide — April 2002

________________

6.2.4 Pipe Length Threshold Table (G07) ... 222

6.2.5 Preferred Bolt Length Table (G11) ... 223

6.2.6 Weld Type Table ... 226

6.2.7 Weld Clearance Table ... 228

6.2.8 Weld Graphics Dimensions Table ... 229

6.2.9 Bolt Commodity Code Table ... 230

6.2.10 Gasket Diameter Table ... 231

6.2.11 Field Fit Length Table ... 232

6.2.12 Component Mirror Table ... 233

6.2.13 Operator Mirror Table ... 234

6.2.14 Default End Preperation Table ... 236

6.2.15 MTO Tables and Functions ... 237

6.3 Piping Job Specification Tables Command ... 239

6.3.1 Options ... 240

6.3.2 Create Library ... 242

6.3.3 Compress Library ... 242

6.3.4 Unapproved ==> Approved ... 242

6.3.5 Create/Interactive Spec Tables ... 243

6.3.6 Create/Batch Spec Tables ... 244

6.3.7 Revise Spec Tables ... 245

6.3.8 Delete Spec Tables ... 247

6.3.9 Report on Spec Tables ... 248

6.3.10 List Spec Tables ... 250

6.3.11 Extract Spec Tables ... 251

7. Graphic Commodity Data ... 253

7.1 Graphic Commodity Library ... 254

7.1.1 Symbol Processors ... 256

7.1.2 Sub-Symbol Processor ... 258

7.1.3 Physical Data Definitions ... 259

7.1.4 Parametric Shape Definitions ... 263

7.2 Physical Data Tables ... 266

7.2.1 Data Retrieval from the Physical Data Library ... 267

7.2.2 Example of Physical Data Look-Up ... 268

(10)

Table of Contents

________________

7.4.1 Create Library ... 277

7.4.2 Compress ... 277

7.4.3 Unapproved ==> Approved ... 277

7.4.4 Create/Interactive Graphic Commodity Data ... 278

7.4.5 Create/Batch Graphic Commodity Data ... 279

7.4.6 Revise Graphic Commodity Data ... 281

7.4.7 Delete Graphic Commodity Data ... 283

7.4.8 Report Graphic Commodity Data ... 284

7.4.9 List Graphic Commodity Data ... 285

7.4.10 Extract Graphic Commodity Data ... 286

7.5 Physical Data Library Manager ... 287

7.5.1 Create Library ... 290

7.5.2 Compress ... 290

7.5.3 Unapproved ==> Approved ... 290

7.5.4 Create/Interactive Physical Commodity Data ... 291

7.5.5 Create/Batch Physical Commodity Data ... 292

7.5.6 Revise Physical Commodity Data ... 294

7.5.7 Delete Physical Commodity Data ... 296

7.5.8 Report Physical Commodity Data ... 297

7.5.9 List Physical Commodity Data ... 299

7.5.10 Extract Physical Commodity Data ... 300

8. Table Formats and Naming Conventions ... 303

8.1 Table Conventions ... 304 8.1.1 Table Names ... 304 8.1.2 Comments ... 304 8.1.3 Revision Markers ... 305 8.1.4 Component Tables ... 305 8.1.5 Units ... 306

8.1.6 Fields (Input/Output Columns) ... 308

8.1.7 NPD Values ... 309 8.1.8 Rating ... 309 8.1.9 Schedule/Thickness ... 310 8.1.10 Weight Tables ... 313 8.1.11 Abbreviations ... 314 8.2 Table Requirements ... 315

8.2.1 Tables Required for Piping Components ... 315

8.2.1.1 Fittings (6P2C, 6P3C, 6Q2C and 6Q3C) ... 316

8.2.1.2 Specialty Piping Components (6P6C and 6Q6C) ... 317

(11)

Reference Data Manager Reference Guide — April 2002

________________

8.3 Generic Tables ... 319

8.3.1 Variables for Generic Tables ... 320

8.3.2 Generic Table for Bolted Ends (G10) ... 324

8.3.3 Generic Table for Studs used in Bolted Connections (G12) ... 326

8.3.4 Generic Table for Studs in Bolted Connections w/ Term Type (G12T) ... 328

8.3.5 Generic Table for Male Ends (G20) ... 330

8.3.6 Generic Table for Female Ends (G30) ... 332

8.3.7 Generic Table for Weight and Thickness Data, Male Ends (G50) ... 333

8.4 Piping Component Tables ... 334

8.4.1 Variables for Specific Tables ... 336

8.4.2 Piping Component Table for GCP Data (P11A, P15A) ... 339

8.4.3 Piping Component Table GCP Overflow Data (P11B, P15B) ... 341

8.4.4 Piping Component Table Green and Red CP Data (P21A,P25A,P26A,P27A,P28A,P29A) ... 342

8.4.5 Piping Component Table Green and Red CP Overflow Data (P21B,P25B,P26B,P27B,P28B) ... 344

8.4.6 Piping Component Table for Operators and Actuators (P31A) ... 345

8.4.7 Piping Component Table for Operators and Actuators, Overflow Data (P31B) .... 347

8.4.8 Piping Component Table for Empty Weight based on GCP Data (P51,P52,P59) ... 348

8.4.9 Piping Component Table For Empty Weight of Valves (P60A) ... 350

8.4.10 Piping Component Table For Empty Weight of Valves, Overflow Data (P60B) ... 351

8.4.11 Piping Component Table for Empty Weight based on GCP and RCP Data (P61,P62,P63,P64,P65) ... 352

8.4.12 Piping Component Tables for Specialty Components ... 354

8.5 Instrument Component Tables ... 355

8.5.1 Instrument Body (I80 and P80) ... 355

8.5.2 Instrument Operator (I81 and P81) ... 358

9. Material Description Data ... 361

9.1 Material Data in the Material Reference Database ... 366

9.2 Short Material Description Library ... 367

9.3 Long Material Description Library ... 372

9.4 Specialty Material Description Library ... 374

(12)

Table of Contents

________________

10. Table Checker ... 385

10.1 Table Checker Form ... 389

10.1.1 Using the Report Commands ... 390

10.1.2 Report Format Form ... 392

10.1.2.1 Format Creation/Revision Form ... 394

10.1.2.2 Format Deletion Form ... 396

10.1.3 Discrimination Data Form ... 398

10.1.3.1 Discrimination Data Creation Form ... 400

10.1.3.2 Discrimination Data Revision Form ... 402

10.1.3.3 Discrimination Data Deletion Form ... 404

10.1.4 Report Form ... 406

10.1.4.1 Report Creation Form ... 408

10.1.4.2 Revise Report Form ... 411

10.1.4.3 Report Deletion Form ... 414

10.1.4.4 Report Approval Form ... 416

10.1.4.5 Report Multiple Submit Form ... 418

10.1.5 Report Management Defaults Form ... 420

10.2 Sample Table Checker Output ... 422

11. Pipe Support Tutorial Definition Manager ... 437

11.1 Support Tutorial Definition Manager ... 438

11.1.1 Create Library ... 440 11.1.2 Compress ... 440 11.1.3 Unapproved ==> Approved ... 440 11.1.4 Create Data ... 441 11.1.5 Revise Data ... 442 11.1.6 Report Data ... 444 11.1.7 List Data ... 445 11.1.8 Delete Data ... 446 11.1.9 Extract Data ... 447

12. Standard Note Library ... 449

12.1 Standard Note Library Manager ... 453

12.1.1 Create Library ... 455

12.1.2 Compress ... 455

12.1.3 Unapproved ==> Approved ... 455

(13)

Reference Data Manager Reference Guide — April 2002

________________

12.1.5 Revise Standard Note Type ... 457

12.1.6 Report Standard Note Library Contents ... 459

12.1.7 List Standard Note Data ... 460

12.1.8 Delete Standard Note Data ... 461

12.1.9 Extract Standard Note Type ... 462

12.1.10 Load Database ... 463

13. Label Description Library ... 465

13.1 Label Types ... 466

13.1.1 Displayable Attribute Labels ... 466

13.1.2 Alphanumeric Labels ... 466

13.1.3 Displayable Attribute Message ... 466

13.1.4 Commodity Code Attribute Message ... 467

13.1.5 Isometric Drawing Labels ... 467

13.1.6 Report Labels ... 468

13.1.7 Clash Management Labels ... 468

13.2 Label Description Library Manager ... 471

13.2.1 Create Library ... 472

13.2.2 Compress Library ... 472

13.2.3 Unapproved ==> Approved ... 472

13.2.4 Create Label Data ... 473

13.2.4.1 Create Label Graphic Data ... 475

13.2.4.2 Create Label Attribute Data ... 478

13.2.4.3 Mass Annotation Options ... 484

13.2.5 Revise Label Data ... 485

13.2.6 Delete Label Data ... 487

13.2.7 Report Label Data ... 489

13.3 Label Library Merger ... 495

13.3.1 Label Library Merger Interface ... 495

13.3.1.1 File Menu ... 497

13.3.1.1.1 Open Source Label Library 1 ... 497

13.3.1.1.2 Open Source Label Library 2 ... 497

(14)

Table of Contents

________________

13.3.1.2.3 Invert Selection ... 499

13.3.1.2.4 Edit Label Number ... 499

13.3.1.2.5 Edit Label Description ... 499

13.3.1.2.6 Delete ... 499

13.3.1.2.7 Validate ... 499

13.3.1.2.8 Compress Destination Library ... 500

13.3.1.2.9 Copy to Destination ... 500

13.3.1.2.10 Clear Error Messages ... 500

13.3.1.3 Help Menu ... 501

13.3.1.3.1 Contents ... 501

13.3.1.3.2 About Library Merger ... 501

13.3.2 Workflow ... 502

14. Piping Assembly Library ... 505

14.1 Piping Assembly Language ... 506

14.1.1 PAL Keywords ... 506

14.1.2 Placing Taps in Assemblies ... 520

14.1.3 Sample Piping Assembly Files ... 521

14.2 Piping Assembly Library Manager ... 525

14.2.1 Options ... 525

14.2.2 Create Library ... 527

14.2.3 Compress ... 527

14.2.4 Unapproved ==> Approved ... 527

14.2.5 Create/Interactive Piping Assembly Data ... 528

14.2.6 Create/Batch Assembly Data ... 529

14.2.7 Revise Piping Assembly Data ... 530

14.2.8 Delete Piping Assembly Data ... 532

14.2.9 Report Assembly Data ... 533

14.2.10 List Assembly Data ... 534

14.2.11 Extract Assembly Data ... 535

15. Reference Database Revision Manager ... 537

15.1 Reference Data Conflict Report ... 540

15.2 Table Change Report ... 546

15.3 Reference Data Impact Report ... 551

15.3.1 Examples ... 551

15.4 Proposed RDB Changes Report ... 555

(15)

Reference Data Manager Reference Guide — April 2002

________________

Appendix A: Reference Data Manager Error Messages ... 565

Appendix B: Codelists ... 567

B.1 General Comments ... 569

B.2 Comments Specific to Units of Measure Codelist Sets ... 569

Glossary ... 667

(16)

Preface

________________

Preface

Document Purpose

This document is a reference guide for the Reference Data Manager module of the PDS 3D products. PDS 3D uses interactive graphics and database management techniques to integrate the engineering and design/drafting execution of plant design. The Reference Data Manager module is one part of the overall Plant Design System. It is specifically designed to define and modify the reference data for the PDS 3D modules. It enables you to control and standardize the PDS 3D tasks. You can also modify the reference data to reflect company practices and standards.

This document is designed as a reference; it is organized around the structure of the product rather than presenting a typical work flow. Use this guide when you need to look up a specific Reference Data Manager function.

Document Prerequisites / Audience

This document is intended for project managers who have a working knowledge of the PDS 3D Modules. Knowledge of relational database systems and basic file manipulations is recommended. You should also be familiar with a text editor, such as Notepad, vi, or EMACS.

Related Documents/Products

Intergraph Corporation’s Relational Interface System (RIS)TMis required to operate PDS 3D, along with a relational database management system (RDBMS) supported by RIS. Currently, these include Informix, Oracle, and Ingres. Information about RIS capabilities can be found in the following documents:

Relational Interface System (RIS) Reference Manual Relational Interface System (RIS) Operator Training Guide

For more information on related aspects of the PDS 3D products, consult the following documents:

Project Administrator Reference Guide Piping Design Graphics Reference Guide Equipment Modeling Reference Guide

(17)

Reference Data Manager Reference Guide — April 2002

________________

Report Manager Reference Guide

About this Document

This document contains front matter, numbered sections, appendices, a glossary, and an index. Much of this document is devoted to a description of the forms used to setup and maintain reference data.

Section 1 Provides an overview of the product. It describes general information, terms, and work flow.

Section 2 Describes the product environment. This includes information on accessing the product and common conventions for working in the PDS 3D modules.

Section 3 Describes the main Reference Data Manager form used to access the product.

Sections 4-16 Describe the individual libraries and managers which make up the Reference Data Manager including operating steps for each form within the manager.

Appendices Provide additional information related to the Reference Data Manager such as error messages, and file listings.

Additional Information

The following informational files are delivered with the software in the directory. File Name Contents

readme.txt Describes changes and additions to the product since the last version. For a fixes release, the fixes are appended to the top of the initial file to provide a history of all changes to the product. Includes Comments and Trouble Report numbers which describe what problems have been fixed. Provides special notices to the customer. Lists any exceptions made to the certification.

(18)

Preface

________________

General Conventions

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

Typefaces

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

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Command paths 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 by the user. For example,

Select first segment of alignment

Bold Typewriter

Indicates what you should literally type in. For example, Key in original.dat to load the ASCII file.

Normal Typewriter

Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rpt file.

(19)

Reference Data Manager Reference Guide — April 2002

________________

Symbols

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

<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 is doing 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 the exercises.

Keyboard Conventions

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

(20)

Preface

________________

Terminology

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

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by picking it with your cursor. Selecting does not initiate an action. After

selecting an item, you click the action you want to affect the item. For example,

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

In addition, you would select items to define parameters, such as selecting toggle buttons. This also applies to selecting graphic elements 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 design file. If you are using the CLIX operating system, you tentative-select by double-clicking with a mouse or pressing <T> on a hand-held cursor. If you are using the Windows NT operating system, you tentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-held cursor button twice in rapid succession. This term implies that you are clicking 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 new surface. Drag To press and hold the data button (<D>) while moving the mouse or

hand-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 the default action.

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

(21)

Reference Data Manager Reference Guide — April 2002

(22)

1. Introduction

Introduction

________________

1.

Introduction

Welcome to the Reference Data Manager (PD_Data) module of the Plant Design System of software.

Intergraph’s plant design software can be used to design any type of plant—from petrochemical plants, offshore platforms, chemical and pharmaceutical plants, consumer products (food, beverages, cosmetics, soap, paper, and so forth), to power plants, waste water treatment plants, and cogeneration facilities.

Specifically, the Plant Design System (PDS) integrates many discipline-specific software modules; these modules automate the many phases of a plant design project. Reference Data Manager (PD_Data) is one of these modules.

In PDS, placement of piping components is driven by the specification. The PDS reference data provides the selection criteria for the piping commodity items that are found in the piping job specification and the piping commodity libraries that are delivered with the product. This data is contained in the reference database (RDB) and can be used by other projects.

The Reference Data Manager (PD_Data) is specifically designed to define and modify the reference data for the PDS 3D modules. This reference data ensures consistency in the definition of piping specifications and

commodity libraries. It is used to control and standardize the PDS 3D modules to reflect company practices and standards.

(23)

Reference Data Manager Reference Guide — April 2002

________________

1.1

Project Organization

Since a process plant such as a refinery can be extremely large, PDS uses the following organization to break the plant into smaller pieces that can be handled more easily.

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 the

information required to work in a PDS task.

The Project Administrator controls the creation and modification of Piping projects. Each Piping project consists of a project control database, project design database, piping and equipment models, reference models (structural, HVAC, and electrical raceway), a set of drawings, and a collection of reference data. The reference data may be specific to one project or shared by more than one project.

A project and all of its accompanying files must be defined with the Project Administrator before you can use any of the other 3D PDS modules. Refer to the Project Administrator Reference Guide for more information on setting up a project.

(24)

1. Introduction

Reference Data Overview

________________

1.2

Reference Data Overview

The Reference Data Manager (PD_Data) enables you to define and modify the reference data for the PDS 3D modules. This reference data is used to ensure consistency in the definition of piping specifications and commodity libraries. It enables you to control and standardize the PDS 3D tasks. You can also modify the reference data to reflect company practices and standards.

The Reference Data for PDS 3D is composed of the following basic components:

Spec/Material Database

Table 201 - Piping Material Class Data

Table 202 - Piping Commodity Specification Data Table 203 - Piping Specialty Specification Data Table 204 - Instrument Component Specification Data Table 205 - Tap Properties Data

Table 211 - Piping Commodity Size-Dependent Material Data Table 212 - Piping Commodity Implied Material Data Table 231 - Component Insulation Exclusion Data Table 232 - Flange Insulation Exclusion Data

Practice Specific Reference Data

Physical Dimension Tables

Piping Job Specification Tables Short Material Descriptions Long Material Descriptions Specialty Material Descriptions

(25)

Reference Data Manager Reference Guide — April 2002

________________

Practice Independent Reference Data

Graphic Commodity Data

Standard Note Library Label Description Library Piping Assembly Library

The Reference Data Manager supports both approved and unapproved reference data for a project. The Project Control Database contains complete file management data for both an approved and unapproved version of each type of reference data such as the Piping Job Specification or the Graphic Commodity Library. This allows revisions to take place in unapproved files while other processes read the approved files. Once the information in the unapproved files has been verified, it can be posted to the approved reference data files. The following figure illustrates the various pieces of reference data required to place a 6" gate valve in a piping model and report on the placed component. It depicts how the various parts that make up PDS work together. Whenever possible, this placement example will be used throughout the rest of this document. For example, the discussion of the physical dimension tables will use the tables called to place the gate valve as examples.

(26)

1. Introduction

Reference Data Overview

(27)

Reference Data Manager Reference Guide — April 2002

(28)

1. Introduction

Piping Job Specification Introduction

________________

1.2.1

Piping Job Specification Introduction

The Piping Job Specification (PJS) provides selection criteria for piping commodity items, piping specialty items, and instruments. The information for the Piping Job Specification is contained in the following files:

Specification/Material Reference Database - database containing the definitions for piping materials classes, commodity items, specialty items, and tap properties tables. Spec Table Library - library containing the specification tables referenced in the PJS. The information in the Specification/Material Reference database and Spec Table Library tables is also delivered in the form of neutral files which you can extract and modify. The Piping Job Specification Manager enables you to create or revise the specificaton data in the Material Reference Database. You can use the interactive (forms-driven) specification writer or define/revise the data using ASCII neutral files.

The Piping Job Spec Tables command enables you to create, revise, and delete tables in the Spec Table Library.

Graphic Commodity Data Introduction

The graphic commodity data is used to define commodity items, specialty items, and instruments. The Graphic Commodity Library contains the parametric symbol definitions required to place piping and instrument components in a 3D model. When you place a component the system uses the Piping Job Specification to select the appropriate component from the parametric symbol definition library which then accesses the component dimensional data.

The graphic commodity data is contained in the following object libraries:

Graphic Commodity Library - contains the parametric definitions for the commodity items.

Physical Dimension Libraries - contains dimension data for the commodity items. (A different Physical Dimension Library is required for each type of practice such as, U.S., DIN, or British Standard)

Spec Table Library - contains the specification tables referenced in the PJS. The parametric descriptions and dimension tables are also delivered in the form of text libraries which you can extract and modify using the Graphic Commodity Library

(29)

Reference Data Manager Reference Guide — April 2002

________________

Material Description Data Introduction

The Material Description Data is accessed for

Material Take-off (MTO) reporting from the Design Database Other miscellaneous reporting

Interfaces to the material control system Stress analysis

Isometric drawing extraction.

The Material Description Data consists of the commodity item data which is not stored in the Design Database, which is not required for the creation of graphic symbologies, and which is not part of the geometric data. This data is contained in the following files:

Material Data in the Specification/Material Database - database tables containing definitions for commodity items, criteria for implied material, and weld data. Short Material Description Library - contains the short material descriptions for commodity items and taps.

Long Material Description Library - contains the long material descriptions for commodity items.

Specialty Material Description Library - contains the material descriptions for specialty items.

The material descriptions are also delivered in the form of neutral files which you can modify and post to the libraries.

The Material Description Library Manager enables you to create, revise, and delete data in the Material Description Libraries. You can use the Piping Job Specification Manager to load the material data tables in the Specification/Material Database.

Standard Note Library Introduction

(30)

1. Introduction

Piping Job Specification Introduction

________________

Label Description Library Introduction

The Label Description Library contains the definitions for the following label types used in PDS 3D:

Orthographic drawing view specific labels Orthographic drawing view identification labels Orthagraphic drawing - user input

Displayable attribute messages Commodity code attribute messages Isometric drawing labels

Report labels

Clash management labels

These labels are intelligent graphics with links to the material database.

The Label Description Library Manager enables you to define the graphic parameters for a label (such as level, line weight, and color code) and to define the format of the label (what information comprises the label.)

Piping Assembly Library Introduction

The Piping Assembly Library contains the piping assembly definitions which define the parameters necessary to place a piping assembly (group of components) automatically in the model.

A Piping Assembly object library and text library which contain the definitions for basic assemblies are included in the product delivery.

(31)

Reference Data Manager Reference Guide — April 2002

________________

1.3

Reference Database Introduction

A database is a collection of formatted data which conforms to a set of predefined rules. The Specification/Material Reference Database is composed of a set of tables (entities) which represent categories of data. A table is a defined set of attributes which describe an item, such as the Piping Commodity Data table.

An attribute is a single type of information to be stored about an item, such as nominal diameter or end preparation. Each attribute has a column number in the database table and a name which describes the piece of information to be stored. The actual information stored in the database is referred to as the attribute value. This value is a fixed data type; it can be either numeric, alphanumeric, or code-listed.

numeric data types can be either real (decimal) or integer. These attributes are used for quantitative values such as pressure or temperature.

alphanumeric data types (also called character) are used for textual information such as component names or descriptions.

code-listed data types are a special integer values which help standardize and speed up data entry. A code list is a set of acceptable values for a particular attribute which can be referred to by an index number. A code-listed attribute is an attribute whose value is defined using one of the selections from a particular code list set.

(32)

1. Introduction

Delivered Reference Data

________________

1.4

Delivered Reference Data

The following reference data is delivered in the reference database products for the corresponding practices (such as RDUSRDB or RDDINRDB).

Library

File Description Object Text

Physical Dimension Table Library us_pcdim.l us_pcdim.l.t Piping Job Specification Table Library us_pjstb.l us_pjstb.l.t Short Material Description Library us_shbom.l

-Long Material Description Library us_lgbom.l -Specialty Material Description Library us_spbom.l -For the DIN RDB substitute din_ for us_ in the listed library file names.

The following reference data, which is not unique to any specific practice, is delivered in the PD Shell product in the \win32app\ingr\pdshell\lib directory.

Library

File Description Object Text

Graphic Commodity Library pip_gcom.l pip_gcom.l.t Piping Assembly Library assembly.l assembly.l.t Label Description Library labels.l

(33)

Reference Data Manager Reference Guide — April 2002

________________

1.5

Reference Data Setup

A project and all of its accompanying files must be defined with the Project Administrator before you can use the Reference Data Manager. Refer to the Project Administrator Reference Guide for information on

Loading PDS 3D products.

Editing the control script to identify the location of the project data. Setting up a project and creating the associated database schemas. Accessing the PDS 3D products remotely using NFS.

In addition to the information specified in the Project Administrator Reference Guide, you should complete the following steps before using the Reference Data Manager.

Load the appropriate Reference Data product (such as RDUSRDB for U.S. Practice or RDDINRDB for DIN Practice).

Edit the pds.cmd file to identify the text editor to be used when revising reference data through the Reference Data Manager forms. You can specify any text editor that has been loaded on the workstation. The default setting for Windows NT systems is

Notepad.

$ENV {’PD_EDITOR’} = ’<absolute path to preferred editor executable>’;

Edit the pds.cmd file to define PD_COMMIT_INTERVAL to control the commit interval for use in loading specification data into the Material Reference Database. This has the same impact as adjusting the -c option in a risload command line. The default commit value is 25. Increasing this variable may improve performance.

Identify the location of the Reference Data files as described in Reference Data Location, page 47.

(34)

2. Environment

PDS Environment

________________

2.

PDS Environment

The PDS 3D software supports a variety of applications. All the supported applications use a common interface that is controlled by the PD Shell program. This ensures consistency across applications and minimizes the amount of time required to learn the product. The PDS 3D modules provide a simple user interface through extensive use of forms. The modules also provide an on-line Help capability for easy access to information while working in the product.

The PDS 3D software uses available nucleus tools such as MicroStation and FORMS. It supports standard software such as NFS, NQS, and RIS required to set up data across a network. This design facilitates the use of non-PDS tools such as relational databases and third party software.

The PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraph’s Network Licensing System.

(35)

Reference Data Manager Reference Guide — April 2002

________________

PD Shell

The PD Shell program provides access to the various functions that are associated with the PDS 3D Modules. You can access the Plant Design System Environment form by

Double-clicking the PD_Shell icon on Windows NT workstations.

This executes a control script that defines all of the environment variables that are needed to run the product, and it identifies the location of the product files. These files can be located on the workstation or a server on the network. See pds.cmd in the Project Administrator Reference Guide for more information on this file. The script also activates the Plant Design

System Environment form.

This form identifies the active project(s) and provides access to all the PDS functions.

Options

Schematics Environment — Provides access to the PDS 2D modules that are used to

create and modify piping and instrumentation diagrams, process flow diagrams, and instrumentation database records.

(36)

2. Environment

PD Shell

________________

Piping Designer — Activates an interactive command environment that is used to

create piping and in-line instrumentation in the model; revise existing model graphics and database information; and verify the integrity of the data in the model.

Electrical Raceway Environment — Provides access to the Electrical Raceway

module, which provides an interactive environment that is used to create and revise raceway models and access raceway utilities.

Piping Design Data Manager — Provides access to a set of options that are used to

verify the integrity of the graphic and database information that is associated with a model.

Piping Model Builder — Enables you to create piping graphics from a nongraphics

environment. This module is used with PD_Design to create an accurate 3D model of the piping network.

Pipe Support Designer — Activates an interactive command environment that is used

to create pipe supports in the model, and revise existing pipe support model graphics and database information.

Pipe Stress Analysis — Activates a set of forms that are used to extract information

from piping models for input to third-party pipe stress analysis products.

Interference Manager — Activates a set of forms that are used to check for

interferences among project models and to control approved interferences.

Isometric Drawing Manager — Activates a set of forms that are used to extract

isometric drawings from piping models and to review or plot the created isometric drawings.

Drawing Manager — Activates a set of forms that are used to create and manipulate

drawings and drawing views; provide access to the interactive graphics environment for drawings; and provide access to a plot manager and vector hiddenline manager.

DesignReview Integrator — Activates a set of forms that are used to extract

information to form label files for use in DesignReview and to review data from a DesignReview session.

Report Manager — Activates a set of forms that are used to create and revise report

format files and report on information in a project including Material Take-Off reports.

Project Administrator — Provides access to a set of forms that are used to create a

project, create and revise project files, define project seed data, and control the project.

Reference Data Manager — Provides access to a set of forms that are used to control

the reference data for a project including Piping Job Specification data, Graphic Commodity Data, Alphanumeric Commodity Data, Standard Note Library, Label Description Library, and Piping Assembly Library.

(37)

Reference Data Manager Reference Guide — April 2002

________________

Other Fields

User ID — Used for access control. This field also sets the Review User ID for use in

the Interference Manager module.

If access control has been defined, you must key in a valid user ID as defined by your system manager to gain access to the projects. Refer to the Access Control Manger in the Project Administrator (PD_Project) Reference Guide, for more information on using access control.

If access control has not been defined, no entry is required for this field.

Password — Key in the password for the specified user ID.

Project List Field — Displays the defined projects for the network and allows you to

select the active project. The system lists all the defined PDS projects (2D-only, 3D-only, and 2D & 3D). An error is displayed if you select an option that is incompatible with the active project. For example, if the active project is a 2D-only project, you cannot access the the Interference Manager module.

If access control has been defined, only those projects for which you have some level of access are displayed.

Message Area — Displays prompts and messages that are associated with the active

(38)

2. Environment

PD_Shell Form Conventions

________________

PD_Shell Form Conventions

The following Conventions describe how to respond to the various buttons, lists, and prompts that make up the environments. The display size of forms and dialog boxes in the non-Microstation graphics environment are independent of the size of the workstation’s display system. Most forms contain the same basic features: buttons, fields, text, and other gadgets. In general, anything you find on a form is called a gadget.

Selecting Options

You move through the PD Shell forms by selecting function buttons or other gadgets from the form. Select means to place the screen cursor (which appears as an arrow) on top of a screen gadget and press <D>.

For most of the forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button.

You use the select action to select functions, access other forms, activate data fields, toggle buttons, select from lists, scroll through data displayed on the screen, and so on.

The following summarizes other basic actions you use in the environments:

Enter — When keying in any data in a key-in field, press the <ENTER> or <Tab> key for the data to be entered into the system. You can also press <ENTER> or <Tab> to move through a set of key-in fields.

Delete — If you make a mistake while keying in text, press the <Delete> key to erase character(s) to the left of the cursor.

Common Tools on the PD Shell Forms

There are many gadgets in the environments that are common to most or all of the forms. The following describes these tools.

Standard Commands

The PD Shell forms have a set of standard buttons in the upper right corner of most of the form windows. The available commands vary from form to form depending on the type of operation.

The Help button activates on-line Help for the active form. Help remains active until you delete the Help window.

(39)

Reference Data Manager Reference Guide — April 2002

________________

The Shell button exits the active form and returns control to the base manager that is associated with the active form. For most forms this returns to the Plant Design System

Environment form.

The Top button exits the active form and returns control to the top form of the active branch. The Cancel button cancels or exits from the active form. Control returns to the immediately preceding form in the hierarchy.

The Accept button accepts a selection or operation. Depending on the active form or option, the active form remains active so that you can repeat a similar operation or control returns to the preceding form.

The Restart button clears any key-in fields on the form that have values you can modify.

Scrolling List

Some screen menus have a scrolling list of projects or applications. You need to scroll a list only if more options are available than can be displayed in the window. To scroll a list, select the arrow buttons on the side of the list. The list scrolls up or down depending on which arrow you select.

The scrolling list has an arrow pointing up and an arrow pointing down. These arrows scroll lists line by line. There is a button that slides between these two arrows to indicate your position on the list. To page through the list, select the space above or below the sliding button. The list pages up or down

accordingly.

You can also select the slider and, while pressing <D>, slide the button up or down the bar. The items scroll through the window as you move the button. The size and position of the button on the scroll bar is an indication of the number of lines and the relative position within the list.

All commands that display a list of design areas or models order the list alphanumerically by the design area number or model number in ascending order.

In some forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button.

(40)

2. Environment

PD_Shell Form Conventions

________________

Key-in Fields

Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark gray. You can select a key-in field and key in a new value. A bar cursor appears in the active key-in field. Key in your input, and press <Return>. To change a field, reselect the field and key in the new information. Key-in fields have a maximum number of characters depending on the item that is being defined.

If you select a key-in field for a code-listed attribute, the system activates a form that lists the code list values for the selected field.

MicroStation requires lowercase characters for the file specification and path name of all design files. Therefore, the system automatically converts any input for the file specification and path name of a design file (such as a model or drawing) to lowercase before loading into the Project Control Database.

Display-List Boxes

A display-list box is located at the end of some key-in fields. It lets you select data from a list instead of keying in information. For example, there is a display list associated with the Authorization key-in field shown. At the end of the field, there is a small box with horizontal dashes. When you select this display list box with the screen cursor, an associated list of valid input values displays. Select an item from the list to enter its value into the field.

Shift Left and Shift Right buttons

At the bottom of some key-in and display fields, there are two buttons marked with arrows. These buttons are called shift left and shift right buttons.

Often, you can key in more characters than a field display shows. Shift Left moves the text display to the front of the field; Shift Right moves the text display to the end of the field.

Toggle

A toggle field on a screen menu enables you to select one of two possible choices, one of which is always displayed. Place a data point on the toggle field to toggle between the two choices.

Roll-Through List

A roll-through list shows one choice at a time of a list that can be several items long. Place a data point on the roll-through list to scroll through the available options. The option displayed is active.

(41)

Reference Data Manager Reference Guide — April 2002

________________

Standard Window Icons

When using this software in the CLIX environment, you can press <D> along the edge of a form or any area not occupied by a button, key-in field, or other gadget, to display a box of icons. You can manipulate form windows just like any other workstation window. The following list defines the available window icons.

Collapse/Restore Repaint Pop-to-bottom Modify/Resize Pop-to-top Restore Size

Batch Processes

When you install the PDS 3D applications, the system creates the necessary batch queues for that application. Refer to Loading PDS Products in the Project Administrator Reference Guide for a listing of the batch queues.

PDS 3D uses these batch queues to allow you to continue working in the environment while the system processes a request. Many of the batch processes can be delayed for submission at a specified time.

When you submit a batch process the system sends an electronic mail message to the mail path of the default login reporting the jobs completion status. The mail message also includes any error log information.

(42)

2. Environment

Help

________________

Help

On-line Help is a special feature of your application software. Help provides instant access to information from the application reference documents, such as command descriptions and explanations, prompt sequences, and much more.

There are several avenues you can take to find information about a command or subject. For instance, Help provides

A table of contents that lists subjects by topic and subtopic (in a hierarchy).

An alphabetized index of every command or subject that has been documented for the software.

A glossary to help you become familiar with product-specific terms.

The ability to move up, down, back, and forth through Help by using cross-references and links to primary and secondary commands.

The ability to quickly search through Help for information on a specific subject or command.

When you first select Help, the Help Table of Contents is displayed in a pop-up window. Select a topic from this list or select a command from the menu to display an article in the pop-up window.

Whenever possible, PDS Help is context sensitive. For example, if you select the help icon for a given form, Help that is specific to that form is displayed.

The Help window has buttons that you can use to manipulate either Help or the window itself as follows:

(43)

Reference Data Manager Reference Guide — April 2002

________________

Scroll Bar — Moves up or down in an article that is displayed in the Help window. Help Command Buttons — Enable you to move around in the Help file.

Cancel or File > Exit — exits Help and closes the Help window.

Operating Sequence

1. Select the Help button from the command window or form.

If you select Help while using a command, help on the active command is displayed. If no command is active, the table of contents is displayed.

2. Use the command buttons or scroll bar to move around in Help. — OR —

(44)

3. Reference

Data Manager

Reference Data Manager

________________

3.

Reference Data Manager

The Reference Data Manager provides access to the various functions associated with the PDS 3D Reference Database. Select the Reference Data Manager option from the PD Shell form.

Select the option to be performed.

Spec Writer — Used to create, modify, and delete information in the Material

Reference Database using a forms interface. See Spec Writer, page 103.

Piping Job Specification Manager — Used to create, modify, and delete information

in the Material Reference Database using neutral files. See Piping Job Specification, page 55 and Piping Job Specification Manager, page 145.

Piping Job Specification Tables — Used to create, modify, and delete information in

the Piping Job Spec Table Library. See Piping Job Specification Tables, page 189 and Piping Job Specification Tables Command, page 239.

Piping Job Spec Report Manager — Used to define and generate reports of data in

the Material Reference Database. See Piping Job Spec Report Manager, page 154.

Graphic Commodity Library Manager — Used to create, modify, and delete graphic

commodity library data (Eden modules). See Graphic Commodity Library, page 254 and Graphic Commodity Library Manager, page 275.

Physical Data Library Manager — Used to create, modify, and delete physical data

(dimension tables) in object and text libraries. See Physical Data Tables, page 266 and Physical Data Library Manager, page 287.

(45)

Reference Data Manager Reference Guide — April 2002

________________

Material Description Library Manager — Used to create and modify alphanumeric

commodity data. See Material Description Data, page 361 and Material Description Library Manager, page 376.

Support Tutorial Definition Manager — Used to create, revise, and delete data in the

Tutorial Definition Library. See Pipe Support Tutorial Definition Manager, page 437.

Standard Note Library Manager — Used to create, revise, and report the code lists

and standard notes associated with the PDS 3D modules. See Standard Note Library, page 449 and Standard Note Library Manager, page 453.

Label Description Library Manager — Used to define the graphic parameters for a

label (such as level, line weight, and color code) and to define the format of the label (what information comprises the label). See Label Description Library, page 465 and Label Description Library Manager, page 471.

Piping Assembly Library Manager — Used to create, revise, and delete piping

assembly definitions in the Piping Assembly Library. The Piping Assembly Language (PAL) enables you to define the parameters necessary to place a piping assembly (group of components) automatically in the model. See Piping Assembly Library, page 505 and Piping Assembly Library Manager, page 525.

Table Checker — Used to verify that all the commodity spec tables, entries, and Eden

modules for a piping materials class exist in the graphic data libraries for the project. See Table Checker Form, page 389.

Reference Database Revision Manager — Used to create a set of reports for

coordinating revisions in the Reference Database and the implied changes which are required in the model. See Reference Database Revision Manager, page 537.

Reference Database Management Data — Used to define the filenames for Reference

Database Files, graphic commodity data, dimension tables, and spec tables. You can define both approved or unapproved RDB data for each item. See Reference Database Management Data, page 48.

Default Project Control Data — Used to define the default location for the source

files used to load the RDB files (such as neutral files, program files, and report files). See Default Project Control Data, page 53.

(46)

3. Reference

Data Manager

Data Security

________________

3.1

Data Security

The Reference Data Manager provides data security features for the following reference data libraries in the event of accidents such as, electrical power surges and network failures. These features also protect the libraries in the event that a library is being shared by multiple projects, and different users in different projects mistakenly attempt to revise one of the libraries simultaneously.

Graphic Commodity Library Physical Data Library

Piping Job Specification Table Library Short Material Description Library Long Material Description Library Specialty Material Description Library Standard Note Library

Label Description Library Piping Assembly Library

When you enter the Reference Data Manager to create, revise, or delete data in any of the these libraries, the system creates a temporary file for that library. This temporary file is named <library_specification>.c and will be created in the same directory location as the object libary. Once you successfully exit the applicable library manager, the system deletes the temporary file. If a PDS user is unable to exit the Reference Data Manager for any reason (such as a power failure), the system displays a dialog box when the next user enters the Reference Data Manager to revise that library. You must decide which of the following situations applies and respond accordingly.

If you are certain that the warning results from a previous unusual exit, make one of the following decisions.

— If a corrupted library (including the corresponding source library and revision library) has been restored from a backup, select the accept option.

— If you are concerned with the integrity of the library for any reason, select the exit option. Then restore the library, the corresponding source library, and the corresponding revision library to their previous state (before the last revisions). If you are aware that a different user may be revising that library within a different project, select the exit option.

This feature requires that PDS users have write access to the directory in which the libraries reside. The Reference Data Manager will display an error

message, if the user does not have privileges for write access to the applicable directory and the user will not be able to revise that library.

When a PDS user exits a data creation or revision session, the Reference Data Manager verifies the integrity of the binary tree structure within the library. The system displays an error if the Reference Data Manager determines that an error exists in the binary tree structure. In this event, you should contact Intergraph immediately for assistance in repairing the library.

(47)

Reference Data Manager Reference Guide — April 2002

________________

3.2

Reference Data Archival

PDS includes a Project Archival Manager to provide archival and retrieval facilities for projects, including reference data. For more information about the Project Archival

Manager, see Project Archival Manager in the Project Administrator Reference Guide. For

specific information about archiving reference data, see Reference Data in the Project Administrator Reference Guide.

(48)

4. Reference

Data Location

Reference Data Location

________________

4.

Reference Data Location

This section describes the options used to define the location of the Reference Data files on the network.

Reference Database Management Data — Defines the location for Reference

Database Files, graphic commodity data, dimension tables, and spec tables. You can define both approved or unapproved RDB data for each item. See page 48.

Default Project Control Data — Defines the default location for the source files used

to load the RDB files (such as neutral files, language files, and report files). See page 53.

(49)

Reference Data Manager Reference Guide — April 2002

________________

4.1

Reference Database Management

Data

This option activates the Reference Database Management Data form used to define the filenames for Reference Database Files, graphic commodity data, dimension tables, and spec tables. You can define both approved or unapproved RDB data for each item.

Operating Sequence

1. Select Reference Database Management Data from the Reference Data Manager form.

2. Select RDB File Type

Select the RDB file from the list of files. You can use the scroll arrows to scroll through the listed files.

The system identifies the file for the selected field in the fields at the bottom of the form. There are no default settings for these files; you must define the applicable file

(50)

4. Reference

Data Location

Reference Database Management Data

________________

Short Material Description Library

— This field identifies the library which contains the short bill-of-material description for all piping commodity items and the BOM description addenda for taps.

Long Material Description Library

— This field identifies the library which contains the long BOM description for all piping commodity items. The long BOM description is only used for requisitions.

Specialty Material Description Library — This field identifies the library

which contains the BOM description for engineered items, in-line instruments, and pipe supports. This library tends to be customer-specific.

Standard Note Library — This field identifies the location of the standard

note library.

Label Description Library — This field identifies the location for the label

description library.

Piping Assembly Library — This field identifies the location for the Piping

Assembly library. This library contains the symbol definitions for assemblies.

Graphic Commodity Library — This field identifies the library which

contains the Eden modules used to place components in the model.

Physical Data Library — These fields identify the library files which contain

the physical data tables for a range of geometric industry standards.

Commodity Synonym Library — This field identifies the user-defined library

which contains the map for translating the default piping commodity names used in the P&ID Task to names specified by the user in the Piping Job Specification.

Orthographic Drawing Borders — This field identifies the drawing border files

to be used when creating drawings. A set of border files are delivered to the directory win32app\ingr\pddraw\border. You must specify which style of borders is to be used.

3. Key in any changes to the selected RDB files. Refer to Delivered Reference Data, page 31, for a listing of the delivered reference data files.

If you specify an unapproved file, the system will use the unapproved file for all

Reference Data Manager operations (such as revising entries in a library.)

Refer to the Project Data Manager in the Project Administrator Reference Guide for information on setting the choice of data for a model file or drawing.

4. You can select Approved –> Not Approved to copy the approved definition of the selected RDB file to the Not Approved fields. Select confirm to update the information.

(51)

Reference Data Manager Reference Guide — April 2002

________________

Refer to the individual managers for information on posting the unapproved information to the approved files.

5. You can select Default All Library Locations to define a default location for all approved and all unapproved library files.

6. You can select Copy All Standard Libraries to copy the delivered library files to a specified location.

7. Select Accept following each change to the reference data to accept the specified file location.

— THEN — Select Cancel to exit the form.

Options

Default All Library Locations

This option assigns a default network address, pathname, and file specification to the various Reference Database libraries for both the approved and unapproved libraries. You can override any of these default specifications by selecting the appropriate library and keying in the file information.

Specify Default Nodename

Key in a default network address and pathname to be used for all approved Reference Database libraries and a network address and pathname to be used for all unapproved libraries.

The file specifications for all libraries are determined automatically on the basis of the industry practice and the following naming convention.

When copying the Not Approved library to the Approved library, the copy will not occur if the approved library is the most recent or has the same date as the

Figure

Updating...

References