3DTHEORY

User’s GuidePDS 3D Theory

April 2002

DPDS3-PB-200010AFor PDS version 07.01.00.**

This document replaces DEA506440.

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 oramendment of such warranties.

The information and the software discussed in this document are subject to change without notice and should not beconsidered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for anyerror 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 accordancewith the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied byIntergraph or its affiliated companies.

TrademarksCLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DesignReview, DIALOG, EERaceway, FrameWorks, MicasPlus, ModelDraft, Project Engineer, and SEE are trademarks of IntergraphCorporation. All other brands and product names are trademarks of their respective owners.

Copyright 1984-2002 Intergraph CorporationAll Rights Reserved

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software licenseagreement; contains confidential and proprietary information of Intergraph and/or third parties which is protectedby copyright and trade secret law and may not be provided or otherwise made available without properauthorization.

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) ofThe 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 CorporationHuntsville, Alabama 35894-0001

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

Related Products ................................................................................................................... 11Document Organization ........................................................................................................ 11

General Conventions .................................................................................................................... 13

Keyboard Conventions ......................................................................................................... 14Terminology ......................................................................................................................... 15

1. What is the Plant Design System? ............................................................................................... 17

1.1 What are the 2D modules? .................................................................................................. 18

1.1.1 Process Flow Diagram (PFD) ................................................................................. 181.1.2 Process & Instrumentation Diagram (P&ID) .......................................................... 181.1.3 Instruments and Instrument Loops .......................................................................... 19

1.2 What are the 3D modules? .................................................................................................. 20

1.2.1 Equipment Modeling (PD_EQP) ............................................................................ 201.2.2 FrameWorks Plus (FWP) ........................................................................................ 201.2.3 Piping Design Graphics (PD_Design) .................................................................... 211.2.4 Reference Data Manager (PD_Data) ....................................................................... 211.2.5 Drawing Manager (PD_Draw) ................................................................................ 221.2.6 PDS Stress Analysis Interface (PD_Stress) ............................................................ 221.2.7 Interference Checker/Manager (PD_Clash) ............................................................ 221.2.8 PDS Isometric Interface (PD_ISO, PD_ISOGEN) ................................................. 231.2.9 Report Manager (PD_Report) ................................................................................. 231.2.10 Project Engineer HVAC (PE-HVAC) ................................................................... 241.2.11 EE Raceway Modeling .......................................................................................... 241.2.12 Design Review Integrator (PD_Review) ............................................................... 25

1.3 Project Setup ....................................................................................................................... 26

1.3.1 System Setup ........................................................................................................... 261.3.2 2D Setup .................................................................................................................. 271.3.3 3D Setup .................................................................................................................. 281.3.4 About licensing ....................................................................................................... 28

1.4 Project Organization ............................................................................................................ 291.5 Working in Three Dimensions ............................................................................................ 31

5

PDS 3D Theory — April 2002________________

1.5.1 Working Units ......................................................................................................... 351.5.2 Recommended Working Units - English ................................................................ 361.5.3 Recommended Working Units - Metric .................................................................. 361.5.4 Reasoning ................................................................................................................ 371.5.5 3D Coordinate Systems ........................................................................................... 38

1.5.5.1 Plant Coordinate System .......................................................................... 38

1.5.6 Design Volume Coordinate System ........................................................................ 431.5.7 Examples ................................................................................................................. 45

1.5.7.1 DVCS Oriented From Plant North ........................................................... 47

2. Database Overview ...................................................................................................................... 51

2.1 PDS and the Relational Interface System (RIS) ................................................................. 522.2 PDS System Configurations ................................................................................................ 54

2.2.1 Client/Server Relationship ...................................................................................... 54

2.3 PDS 3D Databases .............................................................................................................. 56

2.3.1 Database Information .............................................................................................. 57

2.3.1.1 Attribute Types ......................................................................................... 582.3.1.2 Code-Listed Attributes ............................................................................. 58

2.4 Database Definition Files .................................................................................................... 59

2.4.1 Project Control Database ......................................................................................... 592.4.2 Design Database ...................................................................................................... 732.4.3 Reference Database ................................................................................................. 87

3. Reference Data ............................................................................................................................. 91

3.1 Piping Job Specification ...................................................................................................... 94

3.1.1 Piping Materials Class Data .................................................................................... 943.1.2 Piping Commodity Specification Data ................................................................... 96

3.1.2.1 Connect Point Data .................................................................................. 96

3.1.3 Piping Specialty Specification Data ........................................................................ 983.1.4 Instrument Component Specification Data ............................................................. 993.1.5 Tap Properties Data ................................................................................................. 1003.1.6 Piping Commodity Size-Dependent Material Data ................................................. 1013.1.7 Piping Commodity Implied Material Data .............................................................. 1023.1.8 PJS Tables and Functions ....................................................................................... 104

6


3.2 Graphic Commodity Data and Physical Dimension Data ................................................... 1063.3 Material Description Data ................................................................................................... 1073.4 Standard Note Library ......................................................................................................... 1093.5 Label Description Library ................................................................................................... 1093.6 Piping Assembly Library .................................................................................................... 110

4. How PDS Works .......................................................................................................................... 113

4.1 What Happens When I Place a Component? ...................................................................... 113

4.1.1 Spec Access ............................................................................................................. 1154.1.2 Piping Materials Class Data .................................................................................... 1154.1.3 Piping Commodity Data .......................................................................................... 1204.1.4 Table Access ........................................................................................................... 1244.1.5 Symbol Processors .................................................................................................. 1264.1.6 Sub-Symbol Processor ............................................................................................ 1274.1.7 Physical Data Definitions ........................................................................................ 1284.1.8 Parametric Shape Definitions .................................................................................. 1324.1.9 Physical Data ........................................................................................................... 135

4.1.9.1 Generic Tables ......................................................................................... 1364.1.9.2 Specific Tables ......................................................................................... 137

4.2 Placing Components On Existing Segments ....................................................................... 138

4.2.1 Commodity Item Name Table ................................................................................. 1384.2.2 Bend Deflection Table ............................................................................................ 1404.2.3 Branch Insertion Tables .......................................................................................... 1404.2.4 Placement Examples ............................................................................................... 142

5. Creating 3D Models ..................................................................................................................... 145

5.1 Modeling Setup Requirements ............................................................................................ 145

5.1.1 Project Setup ........................................................................................................... 1455.1.2 Reference Data Setup .............................................................................................. 1465.1.3 Seed Files ................................................................................................................ 1465.1.4 Model Files ............................................................................................................. 1475.1.5 Level Control and Graphical Symbology ............................................................... 1475.1.6 Level and Symbology Defaults ............................................................................... 148

5.2 Graphics Environment for PDS 3D ..................................................................................... 150

5.2.1 Working with the Graphical User Interface ............................................................ 1515.2.2 Common Tools on Forms ....................................................................................... 157

5.2.2.1 Base Form ................................................................................................ 158

5.2.3 3D Seed Data ........................................................................................................... 160

7


5.3 Creating Equipment Models ............................................................................................... 164

5.3.1 Functions of PDS Equipment Modeling (PD_EQP) ............................................... 1645.3.2 About the Reference Database (RDB) .................................................................... 1655.3.3 Equipment Model Seed Data .................................................................................. 1655.3.4 Equipment Modeling Environment ......................................................................... 1695.3.5 Equipment Modeling Concepts ............................................................................... 1715.3.6 Activating the Orientation Tee ................................................................................ 173

5.4 Equipment Modeling Commands ....................................................................................... 174

5.4.1 Equipment Manipulation Commands ..................................................................... 1745.4.2 Component Manipulation Commands .................................................................... 1745.4.3 Nozzle Manipulation ............................................................................................... 1745.4.4 Review/Revise Commands ..................................................................................... 1745.4.5 Define Commands ................................................................................................... 1745.4.6 Miscellaneous Commands ...................................................................................... 1745.4.7 Secondary Commands ............................................................................................. 175

5.5 Creating Piping Models ...................................................................................................... 176

5.5.1 Piping Model Seed Data .......................................................................................... 1785.5.2 Graphic Concepts for Piping Design ....................................................................... 187

5.5.2.1 Piping Segments ....................................................................................... 1875.5.2.2 Active Placement Point ............................................................................ 1885.5.2.3 Coordinate System Indicator and Orientation Tee ................................... 188

5.5.3 Orientation Tee ........................................................................................................ 189

5.5.3.1 Piping Connect Points .............................................................................. 190

5.6 Piping Design Commands ................................................................................................... 191

5.6.1 Placement Commands ............................................................................................. 1915.6.2 Revision Commands ............................................................................................... 1925.6.3 Component Revision ............................................................................................... 1925.6.4 Segment Vertex Commands .................................................................................... 1925.6.5 Piping Revision ....................................................................................................... 1925.6.6 Model Data .............................................................................................................. 1935.6.7 Review Data ............................................................................................................ 1935.6.8 Revise Data ............................................................................................................. 1935.6.9 Analyze Data ........................................................................................................... 193

6. P&ID to Piping Data Transfer ...................................................................................................... 195

6.1 Database Requirements ....................................................................................................... 1956.2 P&ID Correlation Table ...................................................................................................... 1976.3 P&ID Graphical Data Transfer Setup ................................................................................. 2026.4 P&ID Node Numbers .......................................................................................................... 204

8


6.5 Update Segment Data from P&ID ...................................................................................... 205

6.5.1 Update by Node Number ........................................................................................ 2066.5.2 Transfer by Equipment Number and Nozzle Number ............................................ 2066.5.3 Update From Active P&I Drawing ......................................................................... 207

6.6 P&ID Data ........................................................................................................................... 2086.7 Name From P&ID ............................................................................................................... 2096.8 P&ID Data Comparison Options ........................................................................................ 210

7. Detecting and Managing Interferences ........................................................................................ 211

7.1 Interference Checking Process Overview ........................................................................... 2117.2 Project Organization ............................................................................................................ 215

7.2.1 Understanding Design Areas and Volumes ............................................................ 216

7.3 Setting Up a System to Support Interference Detection ..................................................... 2217.4 Understanding Interference Envelopes ............................................................................... 223

7.4.1 Understanding Interference Checking ..................................................................... 2247.4.2 Understanding Interference Plotting ....................................................................... 2307.4.3 Understanding Interference Reporting .................................................................... 230

8. Creating Material Takeoffs and Other Reports ............................................................................ 231

8.1 Reporting Process ................................................................................................................ 2318.2 Maintaining Report Definition Data ................................................................................... 231

8.2.1 Understanding Report Files and Records ................................................................ 232

8.2.1.1 Format File ............................................................................................... 2328.2.1.2 Discrimination Data File .......................................................................... 2328.2.1.3 Report Record .......................................................................................... 2338.2.1.4 Report Output ........................................................................................... 234

8.3 Processing Reports .............................................................................................................. 2358.4 Report Types ....................................................................................................................... 2358.5 Report Format File .............................................................................................................. 237

8.5.1 Format File Syntax .................................................................................................. 2378.5.2 Definitions ............................................................................................................... 2388.5.3 Output Fields ........................................................................................................... 2418.5.4 Sample Format Files ............................................................................................... 242

8.6 What Happens When I Report On a Component? .............................................................. 2468.7 Material Takeoff Reporting (Report Manager) ................................................................... 2528.8 Understanding Implied Items .............................................................................................. 256

9


8.8.1 Mating Implied Items .............................................................................................. 2568.8.2 ’*’ Spec Implied Items ............................................................................................ 2568.8.3 ’+’ Table Implied Items .......................................................................................... 257

8.9 Material Takeoff Options .................................................................................................... 2598.10 Labels in Material Descriptions ........................................................................................ 262

8.10.1 Create Label Attribute Data ................................................................................ 265

9. Extracting Isometric Drawings .................................................................................................... 269

9.1 Overview of Isometric Extraction ....................................................................................... 271

9.1.1 The Intergraph Interface to ISOGEN ...................................................................... 2719.1.2 ASCII to Binary Conversion ................................................................................... 2729.1.3 ISOGEN .................................................................................................................. 272

9.2 Batch Software Organization .............................................................................................. 273

9.2.1 The Batch Job Input File ......................................................................................... 2739.2.2 Line Processing (pdsidf) ......................................................................................... 2759.2.3 The ISOGEN Interface ............................................................................................ 2759.2.4 ISOGEN .................................................................................................................. 2769.2.5 Plotting .................................................................................................................... 276

10. Creating Orthographic Drawings ............................................................................................... 277

10.1 Drawing Manager Setup ................................................................................................. 27910.2 Drawing Seed Data ......................................................................................................... 28410.3 Using Labels in Drawings ............................................................................................... 288

10.3.1 Label Types ....................................................................................................... 28810.3.2 Label Definition Data ........................................................................................ 29010.3.3 Drawing View Specific Labels ......................................................................... 29010.3.4 Displayable Attribute Label .............................................................................. 291

Index .................................................................................................................................................... 293

10

Preface________________

Preface

This PDS 3D Theory Users Guide is designed as an aid for students attending the PDS 3D Theory Classpresented by Intergraph Corporation Education Center and is a supplement to the standard productdocumentation. It is structured according to the course outline and can be used as a study guide.

PDS 3D Theory describes basic conceptual information about the PDS 3D modules. It also describesinformation which should be considered before starting a PDS project.

Related Products

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

Project Administrator (PD_Project) Reference Guide (DEA5027)

Reference Data Manager (PD_Data) Reference Guide (DEA5028)

Piping Component Data Reference Guide (DEA5056)

Piping Design Graphics (PD_Design, PD_Model) Reference Guide (DEA5029)

PDS Equipment Modeling (PD_EQP) User’s Guide (DEA5017)

Interference Checker/Manager (PD_Clash) User’s Guide (DEA5030)

Drawing Manager (PD_Draw) User’s Guide (DEA5032)

PDS ISOGEN Reference Guide (DEA5040)

Document Organization

This document contains the following chapters:

Chapter 1 - Introduction

Chapter 2 - Database Overview

Chapter 3 - Reference Data

Chapter 4 - How PDS Works

Chapter 5 - Creating PDS Models

Chapter 6 - P&ID to Piping Data Transfer

11

PDS 3D Theory — April 2002________________ Chapter 7 - Detecting and Managing Interferences

Chapter 8 - Creating Material Takeoffs and Other Reports

Chapter 9 - Extracting Isometric Drawings

Chapter 10 - Creating Orthographic Drawings

12

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.

13


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.

14

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 new surface.

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.

15


16

1. PD

S O

verview

What is the Plant Design System?________________

1. What is the Plant DesignSystem?

Intergraph’s plant design software can be used to design any type of plant—frompetrochemical plants, offshore platforms, chemical and pharmaceutical plants, consumerproducts (food, beverages, cosmetics, soap, paper, and so forth), to power plants, waste watertreatment plants, and cogeneration facilities.

Specifically, the Plant Design System (PDS) integrates many discipline-specific softwaremodules; these modules automate the many phases of a plant design project. Instrument DataManager is one of these modules.

Designing a plant with the modular Intergraph-Zydex plant design software system comprisesfour phases:

1. Project Setup - 2D and 3D design files, project files, databases.

2. Preliminary Design - feasibility studies, cost estimates, general layouts and processflow diagrams.

3. Detailed Design - process, instrumentation, piping layouts, material control.

4. Design Review - 3D model walk-through.

17


1.1 What are the 2D modules?

PDS 2D is used to create schematic diagrams and to provide the associated reports and MTOs,and to define and purchase all equipment, instruments, pipe, and so forth, necessary to buildthe plant. All of the needed data is stored in databases. These are relational databases whichyou can query, add, delete, or edit information to suit your own or your client’s needs.

The PDS 2D modules are briefly discussed in the following sections.

1.1.1 Process Flow Diagram (PFD)

Conceptual design of a plant includesfeasibility studies, cost estimates, and processsimulations. Third-party process simulationpackages such as ASPEN or SimSci allowengineers to perform preliminary calculationssuch as chemical equilibriums, reactions, heatand material balances and/or design pressuresand temperatures. The data produced fromthese calculations are transferred to PDSwhere a process flow diagram (PFD) isdeveloped.

1.1.2 Process & Instrumentation Diagram (P&ID)

Equipment, instrumentation, and piping schematicsare drawn from process flow data using the Process &Instrumentation Diagrams (P&ID) product.

The P&IDs display the overall process in much greaterdetail than the PFD. The P&ID shows all piping,instrumentation, and controls associated with aparticular process area, as well as all process vessels,pumps, motors, and so forth.

The P&ID identifies the types of instrumentation and controls required by the process andassigns tag numbers to each instrument item. The P&ID reflects the overall process controlthrough either distributive control systems (DCS), programmable logic controllers (PLC), orstand-alone controller philosophy.

When doing propagation (taking graphic information from the drawing and writing it to thedatabase), the drawing is checked for conformance to design rules and the drawinginformation is loaded into a relational database.

18

1. PD

S O

verview

What are the 2D modules?________________

1.1.3 Instruments and Instrument Loops

After the P&ID defines the process controls, theinstruments must be defined with all of the individualdata values. The Instrument Data Manager (IDM) isthe database that maintains an entry for eachinstrument in a project.

19


1.2 What are the 3D modules?

PDS 3D is used to create three-dimensional plant models, create equipment models, extractisometric drawings, and perform design interference checks and equipment clashes. As withthe 2D modules, all of the needed data is stored in relational databases which can be queriedor edited. The PDS 3D modules are briefly discussed in the following sections.

1.2.1 Equipment Modeling (PD_EQP)

Equipment Modeling (PD_EQP) allows designers tomodel the equipment defined in the P&ID.

Stylistic representations of equipment items areproduced, with or without nozzles, by entering datafrom equipment data sheets noting dimensions andweights. Upon completion, the equipment item isplaced in the 3D model.

Within PD_EQP, designers can create a physicalenvelope defining the space occupied by an equipmentitem along with space envelopes defining maintenanceand access areas. This process is instrumental forinterference checking later in the modeling process.

1.2.2 FrameWorks Plus (FWP)

Structures must be designed to carry the loads frompiping, equipment, personnel and other factors to theground. FrameWorks Plus is used to layout structuralframes, foundations, slabs and walls. Piping designers,equipment modelers and structural designers, by sharingreference files, can see the location of each other’sobjects. The structural engineer referencing other modelscan place loads in the 3D model, and apply otheranalytical characteristics to use with a third-party analysissolver. After a design run, the new cross sectionproperties can be read back into the model toautomatically update all the associated symbolized 2Ddrawings.

Other outputs can be obtained from the data model suchas material lists, output to third-party steel detailingprograms, interference envelopes, and graphic and non-graphic data made available to the rendering and walk-through products such as DesignReview.

20

1. PD

S O

verview

What are the 3D modules?________________

1.2.3 Piping Design Graphics (PD_Design)

PD_Design allows designers to create a 3D model of thepiping and in-line instruments defined in the P&ID byrouting the pipelines through space.

When placing the instruments and valves, designers takeinto account pipeline flexibility, method of construction,and ease of access for maintenance and operations.Designers can route pipe in the 3D model as a centerlinerepresentation; moreover, a 3D shaded model can bedisplayed when necessary. The centerline is intelligent andcontains all the information relating to a pipeline, such asthe piping material class, nominal diameter, fluid code,insulation parameters, temperatures and pressures, and soforth.

The alphanumeric data required for each pipeline can beentered interactively or transferred from the P&ID. Thiscan be done during centerline routing, or it can beadded/revised later.

A pipeline can be connected to a specific nozzle or routed from a point in space. Componentssuch as valves, instruments and branches can be placed on the pipeline as it is routed. Valuesfor the alphanumeric data—such as line sequence number, nominal diameter, material class,temperatures and pressures—can be set during routing.

Interactive design checks are performed for each component placement. These checks ensurematching or compatible diameters, pressure ratings, end preparations, and other consistencycriteria. Pipe supports can be modeled giving either a detailed space envelope or a logicalrepresentation of the function of the support, such as an anchor, spring, or guide.

1.2.4 Reference Data Manager (PD_Data)

Placement of the piping components is specification-driven. The reference data provides theselection criteria for the piping commodity items found in the piping job specification andpiping commodity libraries delivered with the product. This data is contained in the RDB andcan be used by other projects.

The delivered reference data contains 140 piping materials classes, defining over 100,000different components for pressure ratings from 125-1500 pounds. It also contains anextensive set of catalog data including 2200 engineering tables.

Reference Data Manager (PD_Data) is specifically designed to define and modify thereference data for the PDS 3D modules. This reference data ensures consistency in thedefinition of piping specifications and commodity libraries. It is used to control andstandardize the PDS 3D modules to reflect company practices and standards.

21


1.2.5 Drawing Manager (PD_Draw)

Designers use the Drawing Manager (PD_Draw)product to create and/or revise orthographic productiondrawings. PD_Draw can be used with other PDS 3Dproducts to place annotation labels identifyingintelligent items and model coordinates, to plot thedrawings, and to produce reports for drawings andmodel data.

1.2.6 PDS Stress Analysis Interface (PD_Stress)

The stress analyst uses the PDS Stress Analysis Interface (PD_Stress)module to generate a neutral file from the 3D piping and equipmentmodels for stress analysis. PD_Stress interfaces to a number ofcommercial packages which accept ASCII format.

1.2.7 Interference Checker/Manager (PD_Clash)

Interference Checker/Manager (PD_Clash) creates envelope filesfor all models in the specified project, design area, or for individualmodels which have an envelope builder specific to each disciplinein the Interference Checker/Manager. It also collects envelope datafor the models that have envelope files which were previouslycreated by one of the other PDS modules. The checker/managerprocesses the specified design volume and identifies all of theinterference clashes.

22

1. PD

S O

verview

What are the 3D modules?________________ It then produces reports which allow the designer to review interferences and review and/orrevise the approval status of the interferences. The software places graphical markers for theproject, produces plots of clashes, and produces an interference report file.

1.2.8 PDS Isometric Interface (PD_ISO,PD_ISOGEN)

PDS Isometric Interface (PD_ISO,PD_ISOGEN) allows designers to extractisometric drawings from the plant model, eitherinteractively or through a batch process. Theinteractive extraction can be used for testing theinterface and verifying a specific pipeline. Batchgeneration of isometrics is used for generatingproduction drawings on a project. With eitherfunction, a bill of materials is automaticallygenerated and attached to the isometric drawing.An optional MTO file can be generated whichcan be printed or used as input to a materialcontrol system.

1.2.9 Report Manager (PD_Report)

Material take-off reports (MTOs) can begenerated on piping and equipment modelsthrough PD_Report. The MTO processgenerates reports by using the graphical data inthe specified models to refer to the DesignDatabase, Reference Database, Project Database,and Material Description Libraries for the dataon which to report. This data includes impliedmaterials, such as bolts, gaskets, and welds, thatare not represented in the model but arenecessary for the specified connectivity.

The Report Manager also maintains the data that defines the format, content, and approvalstatus of the reports.

23


1.2.10 Project Engineer HVAC (PE-HVAC)

PE-HVAC allows designers to place fittings anddevices while laying out duct routes. You can definethe active parameters for duct characteristics such aswidth, depth, shape, material, construction status, andservice.

1.2.11 EE Raceway Modeling

Electrical Engineer Raceway Modeling (EERWAY) isspecification-driven software which allows designers toextract data from the RDB and create 3D models of cabletrays, conduits, wire ways, underground duct banks, andcable trenches. These models can be created using thecenterline and/or 3-line component graphics. With these3D models, you can create interference envelopes and runinterference detection, produce MTOs, and extract racewaydrawings.

24

1. PD

S O

verview

Design Review Integrator (PD_Review)________________

1.2.12 Design Review Integrator (PD_Review)

The PD_Review interface provides an intelligent link to Intergraph’s DesignReview package.You can use DesignReview to walk through a PDS model—in full shaded mode—and reviewthe design and alphanumeric data.

Engineering data such as instrument numbers, equipment numbers, line numbers, and linesizes are available when walking through the model.

Comments are stored in a separate tag file and can be accessed later during the review session.On subsequent walk-throughs, the original comment can be reviewed along with theresponsible designer’s actions.

Also with DesignReview, the model can be used to train operations and maintenancepersonnel before or after the plant is constructed. DesignReview is not included in the PDSpackage and must be purchased separately.

25


1.3 Project Setup

Before work can begin on a project, extensive system setup needs to be completed. Thefollowing outlines the basic flow for initial system setup and project creation. This systemand project setup is usually done by the system manager. Once the project has been set up,other tasks are done by the designer.

1.3.1 System Setup

PDS can run either stand-alone on a workstation or configured in a server/client relationship.Due to the size and scope of PDS projects, most companies use a server/client relationship. APDS server can act as a database server, a file server, and/or a product server.

File and disk sharing systems such as NFS (Network File System) and DiskShare are used toaccess files on the server for processing on the client workstations.

PDS uses relational databases to store informational about virtually all aspects of the projectincluding:

Project data, such as file names and locations.

Reference data, such as piping commodity descriptions.

Design data, such as temperature and pressure values associated with graphic elements.

The PDS products attach to the relational databases through RIS. RIS supports popularRelational Database Management Systems, such as Informix, Oracle, and Ingres.

26

1. PD

S O

verview

Project Setup________________

1.3.2 2D Setup

The PDS2D product is the base platform loaded on each workstation that will be using PDS2D application software, such as PFD, P&ID, and IDM.

PDS2D is the interface to the PDS 2D application product line. It can be either loaded withthe client option to access software on a product server or installed locally. PDS2D allowsyou to perform project administrative functions such as establish and modify reference datafiles, projects, units and drawings.

A 2D project uses a minimum of two database schemas:

A project control database

A "task" (or design) database

The projcreate utility creates the schema information for the installed database. Once thedatabase files have been created, you can access the 2D environment to create units anddrawings for the project. Units are logical divisions of the schematic world of a plant.

27


1.3.3 3D Setup

The PD Shell product is loaded on each workstation that will be using the PDS 3D products.Other PDS 3D products can be either loaded on the workstation using the client option orinstalled locally.

A 3D project uses three database schemas:

A project control database,

A material/reference database,

A design database.

The 2D and 3D project share a common project control database. The ProjectAdministrator is used to create the database files, seed files, and project environment files.

A 3D project is divided into design areas by disciplines. Disciplines represent the various 3Dmodeling applications (such as Piping, Equipment, and HVAC). A design area represents aspecific portion of the project for a given discipline. Each design area comprises a set ofmodels that contains the actual design data.

1.3.4 About licensing

PD_LICE is client/server based; one or more central servers can be used to maintain licensinginformation for all PDS products in a network. Though the licensing information can be on asingle server, the licenses themselves float, that is, they can be used by any workstation in thenetwork. Both the client machine and license server must have PD_LICE installed. Anymachine can be a license server; the licensing has little impact on workstation/serverperformance.

PDS software is purchased or leased by the license. For example, if you purchased 30licenses, you are licensed for 30 processes to concurrently access the various PDS softwareapplications. PD_LICE keeps a running inventory of how many licenses are in use and howmany are available for use. When a PDS application module is started, the application sends arequest to run the software; this request is sent to one or more PDS license servers to obtain alicense to run. If not all licenses are in use, the server grants the license and the applicationstarts. If all licenses are in use when a batch job requests a license, PD_LICE waits until alicense is released (in other words, a user logs out), and processes the request to run. If alllicenses are in use when an interactive user requests a license, an error message displaysindicating that all PDS licenses are currently in use. You must wait until a license becomesavailable.

For more information on this topic, consult the PDS Licensing (PD_LICE) User’s Guide(DEA5071).

28

1. PD

S O

verview

Project Organization________________

1.4 Project Organization

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

A PDS project is comprised of the items that constitute a plant, or the portion of the plantbeing modified. The project is the fundamental structure for working in PDS. Each projectcontains all the information required to work in a PDS task.

A 3D project is divided into design areas by discipline. Disciplines represent the variouscategories of 3D modeling data such as Piping, Equipment, and Structural. A design arearepresents a specific volume or logical area of the project for a given discipline. Design areasare used to break up the project into smaller areas for interference checking and reporting.This speeds up processing when only a portion of the project has changed.

Each design area contains a set of models that correspond to a 3D design volume. Althoughthe illustration above shows only piping areas, each discipline is free to define its areasindependently of all other disciplines. The location of a model and the details of the DesignVolume Coordinate System are specified as seed data in the model definition. The model iscreated at full scale.

A model is a MicroStation design file that contains pipelines, equipment items, cable trays,conduit, structural steel and other items placed by the individual PDS applications such asPiping Design, Equipment Modeling, Raceway, FrameWorks Plus, respectively. Forexample, a piping model may contain only one pipeline or it may contain several pipelines.This is up to the discretion of the project team to satisfy the needs of a specific project.

Each model may be constructed with respect to a master point of reference, known as thePlant Monument (PM) or it may be constructed with respect to a local or auxiliary point ofreference, known as the Design Volume Monument (DVM). The use of the DVM in PDS isanalagous to the use of an Auxiliary Coordinate System (ACS) in MicroStation or a secondarycoordinate system in other CAD software systems.

29

PDS 3D Theory — April 2002________________ For most PDS projects, the PM corresponds to a survey benchmark or some well knownimmovable landmark at the plant site from which measurements can be made. The DVM mayalso correspond to a benchmark or well known point, but it usually differs from onecorresponding to the BM. For instance, if it is convenient to route piping in an out-buildingwith respect to the southwest corner of the building, then that corner of the building may bedesignated as the DVM so that specifying locations within the building during the designprocess may be more convenient. In either case, PDS always knows how to cross-convertfrom the two coordinate systems, so both systems may be used interchangeably for thepurposes of routing or for annotation of design documents.

Drawings are produced from the model. Although drawings can be created at different scales,they all reference the actual model graphics to avoid discrepancies with the model.

Each model represents a unique partition of the design database. This enables you to accessall the data for a single model (independently of the other project data) for the purpose ofcreating or modifying information. However, you can also perform interference checking andcreate reports based on the combined data from all the models in a project.

The Project Administrator module controls the creation and modification of the PDS 3Dprojects. Each project consists of a project control database, design database, piping andequipment models, reference models (structural, HVAC, and raceway), a set of drawings, anda collection of reference data. The reference data may be specific to one project or shared bymore than one project.

30

1. PD

S O

verview

Working in Three Dimensions________________

1.5 Working in Three Dimensions

All PDS models exist in three dimensions. Many design manipulations can be executed in a2D-like manner, but difficult routing situations and precise device placement require anunderstanding of working in a three dimensional environment. Any work done in PDS can beviewed in 3D from any angle.

PDS drawings are also created in three dimensions. However, all the graphics you draw lie ona single plane. Think of this plane as a sheet of drawing paper on a drafting board.Everything you draw on this sheet of paper is contained within one plane only (has onlyheight and width).

This single drawing plane in which you place 2D graphics can be located anywhere within the3D graphics system. When you place graphics in a plane other than this one, you create a 3Dfile. Therefore, a design file with graphics on only one plane is two dimensional; one withgraphics on more than one plane is three dimensional. The graphic components placed in aPDS model have designated height, depth, and width, making the design file a 3D file.

31

PDS 3D Theory — April 2002________________ All graphic elements must be placed in the design cube. The design cube is a volume ofthree-dimensional space you can think of as being inside the display terminal (as depicted bythe dashed lines in the figure below).

PDS has the tools to place graphics at any point in the design cube and to look at the designcube from any angle.

Imagine that a design cube actually does exist within your terminal. If that were so, youwould look into the 3D design cube from the terminal screen in the same way you would lookat a box from one side.

32

1. PD

S O

verview

Working in Three Dimensions________________ You normally think of looking at the design cube from one side or direction at a time.However, you can also look at more than one view, such as the top, front, right, and isometricviews at the same time. These views represent the cube from the corresponding sides.

Notice that the isometric view (also called the rotated view) shows the design cube from anapparent angle of 30°. Actually, the view is rotated 45° in two directions: the cube isdisplayed from the top front right.

33

PDS 3D Theory — April 2002________________ When a three-dimensional component is drawn or placed in the design cube, you are able tosee different sides of the component by looking at different sides of the design cube.

The cube is built around a Cartesian (or Rectangular) coordinate system with the view fromthe top such that the y axis is up, the x axis is to the right, and the z axis out (toward you), asshown below.

Design Cube Showing Cartesian Coordinate System

34

1. PD

S O

verview

Working Units________________

1.5.1 Working Units

The working units for a design volume define the extent of the design volume and theprecision of operations. You can revise the working units to be used for any model ordrawing files created in the project.

For interference checking and reference models to work properly, any changesto the working units should be made for all the 3D models for the project.

Each 3D design file is composed of over 4,000,000,000 units of resolution (UORs). Workingunits relate UORs to a measurement unit such as feet or meters and define how these units aredivided. The total units of resolution are divided into master units, sub units, and positionalunits (MU:SU:PU) which define the number of addressable points and thereby the precisionof operations. The following outlines the standard working unit definitions for PDS.

35


1.5.2 Recommended Working Units - English

File MU SU PU AreaModels (Piping, Equipment,Structural, Raceway, HVAC, Civil,Architecture, MicroStation)

1 FT 12 IN 2032 176138 FT

Drawing 1 FT 12 IN 195072 1834 FT

1.5.3 Recommended Working Units - Metric

File MU SU PU AreaModels 1 M 1000 MM 80 53687 M

Drawing 1 M 1000 MM 7680 536 M

36

1. PD

S O

verview

Working Units________________

1.5.4 Reasoning

The recommended PDS settings for English working units results in 24,384 UORs per foot(1x12x2032). Dividing this number into the available UORs in the design file yields an areaof coverage of 176,138.75 feet or 33.3 miles.

Working units establish the scale of the data. The actual SU and PU values do not matter aslong as the total UORs per master unit are the same. Therefore the English units can beconverted to metric units to create compatible models.

Dividing the total UORs per foot by the metric conversion factor provides the UORs permeter.

.304824384______ = 80000 UORs per meter

This value was used to assign the metric values 1:1000:80. Therefore, the values of1:12:2032 for English units and 1:1000:80 for metric units are compatible.

The recommended English (2032) and metric (80) values allow a file created using theEnglish system to be viewed and edited in metric mode without scaling or altering data.

The positional units for drawings should be defined so that the drawing has the sameresolution as the model. To maintain the same resolution, the smallest drawing view scale isused so that the PUs of the drawing file are no less than the maximum factor times the PUsused in the model.

For English units, the smallest drawing view scale for the delivered drawing seed files is 1/8"= 1’ (12"). This yields a factor of 96 to be applied to the model units to determine thedrawing units.

1/812____ = 96

2032 x 96 = 195072

For metric units, the factor is 100 (96 x 80 = 7680).

37


1.5.5 3D Coordinate Systems

The 3D coordinate systems used in PDS are Cartesian, or rectangular, coordinate systems,which define points within the space of the design cube by measuring distances along the x, y,and z axes.

Rather than use x, y, and z axes, which change according to the view alignment, PDS usesEasting, Northing, and Elevation axes.

1.5.5.1 Plant Coordinate System

The Plant Coordinate System (PCS) is defined in terms of a plant monument. The plantmonument defines the Easting, Northing, and Elevation coordinates to be assigned to thecenter of the MicroStation design volume. The following form, found in Project DataManager, is used to specify the Easting, Northing, and Elevation values of the plantmonument.

This must be done prior to any design file definition.

38

1. PD

S O

verview

3D Coordinate Systems________________

The plant monument is located at the MicroStation point designated as 0, 0, 0. The followingdiagram illustrates the Plant Coordinate system when accepting the default values (0, 0, 0) forthe plant monument and when the recommended working units are used:

39


As previously mentioned, the default working units yield an area of coverage of 176,138.75’(33.3 miles, or 53.58 Kilometers). Since the plant monument is always in the center of thedesign cube, you can divide 176,135.75’ by 2 to determine the extents of the Plant CoordinateSystem. The maximum Easting, Northing, and Westing, Southing, Up, or Down coordinate is88,069’ - 4.5"

Entering the Easting value of -5000 is the same as entering Westing 5000;Northing -20,000 is the same as Southing 20,000.

Do not modify the MicroStation Global Origin for piping or equipment seedfiles or models. In general, this is also not necessary for other disciplines’ seedor design files. Only if it appears that there will not be enough design plane tocontain all graphics (such as may be the case for large material-conveyingsystems spanning several miles) should you even consider a global originchange. It would always be a good idea to consult a PDS Support contactbefore making such a change.

If only positive Easting, Northing, and Westing values are entered, and the default plantmonument values were accepted, you are restricted to using only half of the available designvolume. To work within the contraints of positive Easting and Northing values and still usethe entire design cube, you must modify the Easting and Northing values of the plantmonument. For example, let us assume that the Plant monument is defined to be Easting88,069’ - 4.5", Northing 88,069’ - 4.5", and Elevation 0, as shown below.

40

1. PD

S O

verview

3D Coordinate Systems________________

With these settings, the Plant Coordinate System would be defined as follows:

The orientation of the plant coordinate system changes as you look at different views of thegraphic component, but it stays the same in relation to the component.

41

PDS 3D Theory — April 2002________________ The graphic below shows a plant model with preliminary piping and equipment. The front ofthe plant is seen in the front view, the top of the plant in the top view, and so forth. Thecoordinate system stays the same in relation to the design. Looking at each view, however,gives you a different perspective of the coordinate system.

42

1. PD

S O

verview

Design Volume Coordinate System________________

1.5.6 Design Volume Coordinate System

The Design Volume Coordinate System (DVCS) is a second coordinate system (in addition tothe Plant Coordinate System) that can be defined for an individual model. A DVCS is onlyrequired if different models need to have their coordinates referenced from a different point; itis analogous to the MicroStation Auxiliary Coordinate System.

The DVCS is defined in terms of a Design Volume Monument, which defines the Easting,Northing, and Elevation coordinates to be assigned to the center of the design volume of themodel.

You can select from two orientations (or use the Other button to select the preferred degreevalue) to define the plan view for the design volume, through the Project Data Manager.

↑North defines North at the top of the screen in a plan view.

North→ defines North at the right of the screen in a plan view.

Other allows you to define North as a keyed-in degree value.

43


The system uses the global coordinate system to maintain the relationship among the variousreference models attached to the working model.

44

1. PD

S O

verview

Examples________________

1.5.7 Examples

The following examples show various ways of modifying the Plant Coordinate System orDesign Volume Coordinate System for various working conditions.

45


46

1. PD

S O

verview

DVCS Oriented From Plant North________________

1.5.7.1 DVCS Oriented From Plant North

With values keyed into the Design Volume Corrdinate System Definition form as shownbelow, the design volume monument would be located at 350, 325, 0, and it would be rotated350 degrees (clockwise) from Plant North.

47

PDS 3D Theory — April 2002________________ If a plant consisted of 3 buildings within a 33.3-mile range, with each building at a differentangle than the other two, then the files might be defined as follows:

Note that, in the example, a unique design volume coordinate system has beendefined for each model.

While placing components in Building 1, the user might prefer to enter values relative to theSW corner of the building, rather than entering the large values associated with the PlantCoordinate system. To do this, the project administrator should create a model with a DesignVolume Monument located at the SW corner. In Plant Coordinate System, this coordinatewould be Easting -60,000 (Westing 60,000), Northing -75,000 (Southing 75,000), andElevation 0. In the Design Volume coordinate system, the location should be Easting 0,Northing 0, and Elevation 0.

When a Design Volume Coordinate System has been defined, the user has the choice ofviewing and entering coordinates using the Design Volume Coordinate System or the PlantCoordinate System.

This capability becomes even more valuable when placing components in buildings such asBuilding 2 and Building 3, which are rotated with respect to Plant North. Review thecoordinates for these buildings in the next three screen images.

48

1. PD

S O

verview

DVCS Oriented From Plant North________________

Building 1

Notice that the design volume is NOT ROTATED with respect to the PCS.

Building 2

Notice that the design volume is ROTATED 330 DEGREES with respect tothe PCS.

49


Building 3

Notice that the design volume is ROTATED 30 DEGREES with respect to thePCS.

50

2. Datab

ase O

verview

Database Overview________________

2. Database Overview

PDS uses relational databases to store information about virtually all aspects of the projectincluding:

Project data, such as file names and locations.

Reference data, such as piping commodity descriptions.

Design data, such as temperature and pressure values associated with graphic elements.

PDS provides a consistent interface for the maintenance of these databases.

All databases you create will be relational databases, meaning that they are based on arelational data model–a relation being a two-dimensional table made up of rows and columns.Most relational databases have a Structured Query Language (SQL) interface. The PDSproducts attach to the relational databases through Intergraph Corporation’s RelationalInterface System (RIS). RIS is a generic relational database interface that isolates the SQLinterface differences in specific vendors’ relational database management systems (RDBMSs).It provides a generic networked access to all databases generated with popular RDBMSssupported by RIS, including Informix (both Standard Engine and On-line), Oracle, andSybase.

51


2.1 PDS and the Relational InterfaceSystem (RIS)

PDS uses RIS to define information in an RDBMS. An RIS schema identifies a uniquedatabase/user combination in the commercial database system.

Users are established for different RDBMSs in different ways; in fact, the concept of adatabase differs greatly from one RDBMS to another. The various interfaces provided inPDS let you maintain databases through RIS efficiently, without requiring you to know thedifferences between RDBMSs or the syntax of the RIS create schema statement.

RIS works in conjunction with existing databases. You must have RIS implemented on yournetwork and also have one of the Relational Database Management Systems (RDBMSs)supported by RIS, such as Informix (SE or On-line), Oracle, or Ingres.

Intergraph Corporation recommends that database creation and manipulations be performed atthe System Manager level. The System Manager should be familiar with the theory andpractice of the Relational Interface System to be successful. See the Relational InterfaceSystem (RIS) Reference Manual for full information.

The database installation program involves significant decisions regarding the size of thedatabase to be created, the maximum number of users to be supported, the frequency ofautomatic backups, and other important issues. Intergraph Corporation recommends that asystem manager who has reviewed the database installation programs install and configure thedatabases.

3D RIS Overview

52

2. Datab

ase O

verview

Database Overview________________

2D RIS Overview

The Intergraph product numbers for the relational database products and the correspondingRIS products are documented in the latest ’workstation newsletter’. All ISS products (nucleussoftware) should also be up to date and compatible.

53


2.2 PDS System Configurations

This section describes the configuration options for PDS. PDS can be implemented on anetwork consisiting of file servers, database servers, and client nodes.

2.2.1 Client/Server Relationship

PDS is scalable and can be run on a single node or distributed across a number of client andserver nodes. Client nodes can be Intergraph Clipper workstations, or Intel workstationsrunning Windows NT workstation software.

Server nodes can be Intergraph Clipper servers or multi-processor type Intel servers runningWindows NT server software. Server nodes can be classified into three categories:

Database Server

This is the location of the Relational Databases. All databases will be created andstored on this machine.

Software Server

This is the location of the PDS application products. By using a software server, youcan load all of the PDS software in a central location and have individual workstationsaccess the software through the network.

54

2. Datab

ase O

verview

PDS System Configurations________________ File Server

This is the central location used to store the project files such as reference data libraries,seed files, model files, drawings, and reports.

Depending on system requirements you can designate one server to perform all of these dutiesor distribute them among multiple machines.

A client is a node which accesses data or performs a function on the remote resource (usuallya server). In most PDS configurations, the files reside on the server and processing takesplace on the client workstation.

55


2.3 PDS 3D Databases

A 3D project uses three database schemas as outlined in the following illustration.

56

2. Datab

ase O

verview

PDS 3D Databases________________ The 2D and 3D project share a common project control database.

The Project Administrator is used to create the database files, seed files, and projectenvironment files. A 3D project is divided into design areas by disciplines. Disciplinesrepresent the various 3D modeling applications (such as Piping, Equipment, and HVAC). Adesign area represents a specific volume of the project for a given discipline. Each designarea comprises a set of models which contain the actual design data.

2.3.1 Database Information

A database is a collection of formatted data which conforms to a set of predefined rules. ThePDS Databases are composed of a set of tables (entities) which represent categories of data.A table is a defined set of columns (attributes) which describe an item, such as the PipingCommodity Data table.

An attribute is a single type of information to be stored about an item, such as nominaldiameter or end preparation. Each attribute has a column number in the database table and aname which describes the piece of information to be stored. The actual information stored inthe database is referred to as the attribute value.

57


2.3.1.1 Attribute Types

The following conventions are used to designate the field type for database attributes.

character(n) alphanumeric field n characters in length

integer double word integer

short short integer

double real (floating point) value

standard note nnnn Standard Note Type for code-listed attribute

2.3.1.2 Code-Listed Attributes

A code-listed attribute is an attribute whose value must be defined using one of the selectionsfrom a particular code list in the Standard Note Library. In the database definition files,attributes which are code-listed are identified by a standard note number at the end of the linefollowing the field type description. For example, the line

6. fluid_code , character(6) , standard note 125

indicates that fluid_code is defined in terms of code list numbers belonging to Standard Note125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 forchlorine gas (GCL).

CL125, Fluid Code/Connector Type (999)

1 = [Blank]

11 = A [Air]14 = AC [Combustion air]17 = AE [Aeration air]20 = AI [Instrument air]

::

191 = G [Gas]194 = GCD [Carbon dioxide gas]197 = GCL [Chlorine gas]198 = GCN [Chlorination gas]200 = GF [Fuel gas]203 = GG [Flue gas]206 = GH [Hydrogen gas]209 = GHS [Hydrogen sulphide gas]

58

2. Datab

ase O

verview

Database Definition Files________________

2.4 Database Definition Files

This section lists the delivered database definition (ddl) files for Workstation PDS. Thesefiles are delivered with the PD_Shell product in the directory win32app\ingr\pdshell\ddl.When you create a project, the system copies these files to the project directory and uses themto create the database tables and columns.

2.4.1 Project Control Database

# Project Control Database

# Default Relational Database Definition

# The user must not revise this database definition other than to change# column names.

###################################################

# Project Description Data

table number = 101 , number of columns = 6

1 , system_unique_no , integer2 , project_no , character(15)3 , project_name , character(40)4 , job_no , character(40)5 , company_name , character(40)6 , plant_name , character(40)

###################################################

# Reference Database Management Data

table number = 102, number of columns = 9

1 , type_of_rdb_data , short2 , approval_status , short3 , rdb_file_spec , character(14)4 , path_name , character(36)5 , network_address , character(26)6 , lock_owner , character(10)7 , lock_status , short8 , lock_date , integer9 , revision_date , integer

###################################################

# Project Control Data


59

PDS 3D Theory — April 2002________________ 1 , product_version_no , short2 , report_path , character(36)3 , report_node , character(26)4 , report_format_path , character(36)5 , report_format_node , character(26)6 , report_filter_path , character(36)7 , report_filter_node , character(26)8 , piping_eden_path , character(36)9 , piping_eden_node , character(26)10, eden_table_path , character(36)11, eden_table_node , character(26)12, piping_spec_path , character(36)13, piping_spec_node , character(26)14, assembly_path , character(36)15, assembly_node , character(26)16, model_builder_path , character(36)17, model_builder_node , character(26)18, design_review_path , character(36)19, design_review_node , character(26)20, std_note_lib_path , character(36)21, std_note_lib_node , character(26)22, eqp_eden_path , character(36)23, eqp_eden_node , character(26)24, tdf_table_path , character(36)25, tdf_table_node , character(26)26, clash_report_path , character(36)27, clash_report_node , character(26)28, clash_plot_path , character(36)29, clash_plot_node , character(26)30, mdl_status_low_dr , short , standard note 160531, mdl_status_high_dr , short , standard note 160532, mdl_status_low_ic , short , standard note 160533, mdl_status_high_ic , short , standard note 160534, area_owner_opt_ic , short35, eqp_insul_opt_ic , short36, eqp_con_tol_opt_ic , short37, clash_rpt_index_no , integer38, report_search_path , character(36)39, report_search_node , character(26)

###################################################

# Project Archival Management Data


1 , archival_index_no , integer2 , archival_number , character(24)3 , archival_descript , character(40)4 , archival_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)7 , month_map , integer8 , day_of_week_map , integer9 , day_map , integer10, time_of_day , integer

###################################################

# Model Management Data

60

2. Datab

ase O

verview

Database Definition Files________________ # Engineering Discipline Data


1 , discipline_indx_no , short2 , discipline_name , character(20)3 , intra_disc_ifc_flg , short4 , discipline_mtrx_a, integer5 , discipline_mtrx_b, integer

# Design Area Data


1 , discipline_indx_no , short2 , area_index_no , short3 , area_name , character(10)4 , area_description , character(40)5 , volume_low_x , integer6 , volume_low_y , integer7 , volume_low_z , integer8 , volume_high_x , integer9 , volume_high_y , integer10, volume_high_z , integer11, interference_mode , short12, area_lock_owner , character(10)13, area_lock_status , short14, area_lock_date , integer15, clash_rpt_index_no , integer

# Model Data


1 , model_index_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , partition_no , short5 , model_no , character(10)6 , model_description , character(40)7 , model_file_spec , character(14)8 , path_name , character(36)9 , network_address , character(26)10, lock_owner , character(10)11, lock_status , short12, lock_date , integer13, verification_date , integer14, revision_date , integer15, responsible_disc , short16, model_type , short17, model_status , short , standard note 1605

# Piping Model Data


1 , partition_no , short2 , max_segment_number , integer3 , max_piping_number , integer

61

PDS 3D Theory — April 2002________________ 4 , max_pipe_number , integer5 , max_instr_number , integer6 , max_support_number , integer

# Model Setup Data


1 , discipline_indx_no , short2 , default_path_name , character(36)3 , default_node , character(26)4 , ref_mdl_symbology , short5 , symbology_display , short

#################################################### Structural Management Data

# Structural Sub-Project Control Data


1 , sub_project_ndx_no , short2 , sub_project_no , character(15)3 , sub_project_name , character(40)4 , sub_project_path , character(36)5 , sub_project_node , character(26)6 , sub_project_mount , character(50)

# Structural Design Area Per Sub-Project Data


1 , area_index_no , short2 , sub_project_ndx_no , short

###################################################

# Inspection Iso Data


1 , inspection_iso_id , character(24)2 , inspection_status , short3 , max_inspection_key , short

###################################################

###################################################

# Drawing Management Data

# Drawing Data

62

2. Datab

ase O

verview

Database Definition Files________________ table number = 121, number of columns = 24

1 , dwg_index_no , integer , index 12 , drawing_no , character(24) , index 23 , drawing_title , character(40)4 , default_scale , character(16)5 , approval_initials , character(4)6 , approval_date , integer7 , approval_status , short , standard note 358 , completion_status , short9 , drawing_size , short , standard note 120210, drawing_type , short , standard note 2000 , index 311, last_revision_no , character(2)12, drawing_file_spec , character(14)13, path_name , character(36)14, network_address , character(26)15, lock_owner , character(10)16, lock_status , short17, lock_date , integer18, revision_date , integer19, last_rev_index_no , short20, release_revision , character(2)21, release_date , integer22, checking_status , short , standard note 161023, standard_note_no_a , short , standard note 49924, standard_note_no_b , short , standard note 499

# Drawing View Data


1 , dwg_view_index_no , integer , index 12 , dwg_view_no , character(6) , index 23 , dwg_view_name , character(40)4 , dwg_view_scale , character(16)5 , dwg_index_no , integer6 , saved_view_name , character(6)7 , viewing_direction , short , standard note 16208 , composition_status , short , standard note 16309 , dwg_view_x_low , double10, dwg_view_y_low , double11, dwg_view_z_low , double12, dwg_view_x_high , double13, dwg_view_y_high , double14, dwg_view_z_high , double15, vhl_category_index , short16, drawing_view_type , short

# Drawing View Reference Model Data


1 , dwg_view_index_no , integer2 , model_index_no , integer

# Composite Drawing View Data


63

PDS 3D Theory — April 2002________________ 1 , comp_dwg_index_no , integer , index 12 , comp_dwg_view_no , character(6)3 , comp_dwg_view_name , character(40)4 , comp_dwg_v_scale , character(16)5 , dwg_index_no , integer6 , dwg_view_index_a , integer7 , dwg_view_index_b , integer8 , dwg_view_index_c , integer9 , dwg_view_index_d , integer10, dwg_view_index_e , integer11, dwg_view_index_f , integer12, dwg_view_index_g , integer13, dwg_view_index_h , integer14, dwg_view_index_i , integer15, dwg_view_index_j , integer

# Drawing Revision Data


1 , dwg_index_no , integer2 , revision_index_no , short3 , revision_no , character(2)4 , revision_date , integer5 , revision_by , character(4)6 , checked_by , character(4)7 , rev_description , character(40)

# Drawing Setup Data


1 , drawing_type , short , standard note 20002 , drawing_size , short , standard note 12023 , drawing_scale , character(16)4 , default_path_name , character(36)5 , default_node , character(26)6 , discipline_mask , short7 , alternate_seed_opt , short8 , cell_file_spec , character(14)9 , cell_path_name , character(36)10, cell_net_address , character(26)11, plot_catgy_mask_a , integer12, plot_catgy_mask_b , integer13, label_mask_a , integer14, label_mask_b , integer15, label_mask_c , integer16, label_mask_d , integer

# Reference Model Display Category Setup Data


1 , drawing_type , short , standard note 20002 , discipline_indx_no , short3 , category_mask_a , integer4 , category_mask_b , integer5 , category_mask_c , integer6 , category_mask_d , integer7 , vhl_category_msk_a , integer

64

2. Datab

ase O

verview

Database Definition Files________________ 8 , vhl_category_msk_b , integer9 , vhl_category_msk_c , integer10, vhl_category_msk_d , integer11, vhl_ref_symbology , short12, vhl_symbology , short

# Plotting Default Data


1 , iplot_index_no , integer2 , iplot_number , character(24)3 , iplot_description , character(40)4 , iplot_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)

###################################################

# Interference Management Data

# Clash Management Data


1 , system_unique_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , unique_sequence_no , integer5 , completion_date , integer6 , control_user_no , short7 , env_creation_date , integer8 , clash_check_option , short , standard note 12089 , volume_filter_opt , short , standard note 120910, volume_low_x , integer11, volume_low_y , integer12, volume_low_z , integer13, volume_high_x , integer14, volume_high_y , integer15, volume_high_z , integer

# Clash Data Per Project


1 , unique_clash_id , integer , index 12 , if_approval_status , short , standard note 12033 , comp_a_unique_id , integer4 , comp_b_unique_id , integer5 , model_index_no_a , integer6 , model_index_no_b , integer7 , discipline_index_a , short8 , discipline_index_b , short9 , recent_clash_type , short , standard note 120410, recent_plot_date , integer11, recent_review_date , integer , index 212, recent_sequence_no , integer

65

PDS 3D Theory — April 2002________________ 13, area_index_no , short14, action_discipline , short15, recent_seq_no_b , integer16, area_index_no_b , short

# Clash Data Per Job


1 , system_unique_no , integer , index 12 , unique_clash_id , integer , index 23 , unique_sequence_no , integer4 , clash_type , short , standard note 12045 , comp_a_range_x_lo , integer6 , comp_a_range_y_lo , integer7 , comp_a_range_z_lo , integer8 , comp_a_range_x_hi , integer9 , comp_a_range_y_hi , integer10, comp_a_range_z_hi , integer11, comp_b_range_x_lo , integer12, comp_b_range_y_lo , integer13, comp_b_range_z_lo , integer14, comp_b_range_x_hi , integer15, comp_b_range_y_hi , integer16, comp_b_range_z_hi , integer

# Component Clash Data Per Project


1 , unique_comp_id , integer , index 12 , comp_table_number , short3 , comp_row_number , integer4 , model_index_no , integer5 , primary_descript , character(20)6 , secondary_descript , character(40)7 , comp_model_status , short

# Clash Review History Information


1 , system_unique_no , integer , index 12 , unique_clash_id , integer , index 23 , review_date , integer4 , review_user_no , short5 , responsib_user_no , short6 , action , short , standard note 12057 , review_comment , character(100)8 , approval_method , short , standard note 1207

# Clash Plot History Information


1 , system_unique_no , integer , index 12 , unique_clash_id , integer3 , plot_date , integer

66

2. Datab

ase O

verview

Database Definition Files________________ 4 , plot_user_no , short

###################################################

# Report Management Data

# Report Data


1 , report_index_no , integer , index 12 , report_no , character(24) , index 23 , report_title , character(40)4 , approval_initials , character(4)5 , approval_date , integer6 , approval_status , short , standard note 357 , last_revision_no , character(2)8 , report_file_spec , character(14)9 , path_name , character(36)10, network_address , character(26)11, lock_owner , character(10)12, lock_status , short13, lock_date , integer14, revision_date , integer15, format_index_no , integer16, filter_index_no , integer17, last_rev_index_no , short18, report_source , short , standard note 131019, report_type , short , standard note 131220, search_index_no , integer

# Report Format Data


1 , format_index_no , integer , index 12 , format_number , character(24)3 , format_description , character(40)4 , format_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)7 , lock_owner , character(10)8 , lock_status , short9 , lock_date , integer10, revision_date , integer11, rpt_format_source , short , standard note 1310

# Report Descrimination Data


1 , filter_index_no , integer , index 12 , filter_number , character(24)3 , filter_description , character(40)4 , filter_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)7 , lock_owner , character(10)

67

PDS 3D Theory — April 2002________________ 8 , lock_status , short9 , lock_date , integer10, revision_date , integer11, rpt_filter_source , short , standard note 1310

# Report Revision Data


1 , report_index_no , integer2 , revision_index_no , short3 , revision_no , character(2)4 , revision_date , integer5 , revision_by , character(4)6 , checked_by , character(4)7 , rev_description , character(40)

# Report Search Criteria Data


1 , search_index_no , integer , index 12 , search_number , character(24)3 , search_description , character(40)4 , search_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)7 , lock_owner , character(10)8 , lock_status , short9 , lock_date , integer10, revision_date , integer11, rpt_search_source , short , standard note 1310

###################################################

# DesignReview Management Data


1 , review_index_no , integer , index 12 , review_no , character(24)3 , review_title , character(40)4 , review_type , short , standard note 14105 , control_file_spec , character(14)6 , control_path_name , character(36)7 , control_node , character(26)8 , control_lock_owner , character(10)9 , control_lock_stat , short10, control_lock_date , integer11, tag_file_spec , character(14)12, tag_path_name , character(36)13, tag_node , character(26)14, tag_lock_owner , character(10)15, tag_lock_status , short16, tag_lock_date , integer17, session_rev_date , integer

68

2. Datab

ase O

verview

Database Definition Files________________ 18, label_rev_date , integer19, label_file_spec , character(14)20, label_path_name , character(36)21, label_net_address , character(26)22, month_map , integer23, day_of_week_map , integer24, day_map , integer25, time_of_day , integer

###################################################

# Package/Release Management Data

# Package Data


1 , package_index_no , integer , index 12 , package_no , character(24)3 , package_title , character(40)4 , release_revision , character(2)5 , release_date , integer

# Document Data


1 , document_index_no , integer2 , package_index_no , integer3 , document_source , short , standard note 17104 , document_type , short , standard note 1720

###################################################

# Isometric Drawing Management Data

# Isometric Files Data


1 , isofile_indx_no , integer2 , isodflt_indx_no , integer3 , isofile_type , short4 , isofile_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)7 , iso_description , character(40)8 , lock_owner , character(10)9 , lock_status , short10, lock_date , integer11, revision_date , integer

# Project Options Data


69


1 , isoproj_indx_no , integer , index 12 , isoproj_task_opt , short3 , isoproj_name_opt , short4 , isoproj_dwg_opt , short5 , isodflt_indx_no , integer6 , reserved_1 , character(26)7 , reserved_2 , character(36)8 , reserved_3 , character(20)9 , batch_options , character(20)10, isoproj_name_label , short11, isoproj_dwg_label , short12, sub_directory_opt , short

# Defaults Set Data


1 , isodflt_indx_no , integer2 , isodflt_tag , character(12) , index 13 , isodflt_descr , character(40)4 , isodflt_rev_date , integer

# Isometric Design Area Definition Data


1 , iso_area_indx_no , integer2 , area_indx_no1 , short , index 13 , area_indx_no2 , short4 , area_indx_no3 , short5 , area_indx_no4 , short6 , area_indx_no5 , short7 , area_indx_no6 , short8 , selection_mode , short9 , iso_area_name , character(10)10, iso_area_desc , character(40)11, user_data_indx_no , integer12, isodflt_indx_no , integer13, cont_indx_no1 , short14, cont_indx_no2 , short15, cont_indx_no3 , short16, cont_indx_no4 , short17, cont_indx_no5 , short18, cont_indx_no6 , short19, cont_indx_no7 , short20, cont_indx_no8 , short21, cont_indx_no9 , short22, cont_indx_no10 , short

# Isometric User Data


1 , user_data_indx_no , integer2 , type_of_user_data , short3 , user_data_1 , character(40)4 , user_data_2 , character(40)5 , user_data_3 , character(40)

70

2. Datab

ase O

verview

Database Definition Files________________ 6 , user_data_4 , character(40)7 , user_data_5 , character(40)8 , user_data_6 , character(40)9 , user_data_7 , character(40)10, user_data_8 , character(40)11, user_data_9 , character(40)12, user_data_10 , character(40)

# Isometric Drawing Extraction Data


1 , drawing_indx_no , integer2 , iso_area_indx_no , integer , index 13 , lineid_1 , character(16) , index 24 , lineid_2 , character(16)5 , lineid_3 , character(16)6 , number_of_sections , short7 , drawing_number , character(20)8 , batch_ref_no , character(12)9 , iso_dgn_name , character(10)10, model_status_code , character(2)11, model_revised_date , integer12, lst_extraction_date, integer13, tot_no_extractions , short14, no_sheets_extract , short15, last_mto_date , integer16, mto_to_mtl_control , integer17, no_of_revisions , short18, user_data_indx_no , integer19, iso_type , short , index 3

# Isometric Drawing Revision Information


1 , draw_rev_indx_no , integer2 , draw_sht_indx_no , integer , index 13 , type_of_revision , short , index 24 , revision_number , short , index 35 , generated_by , character(3)6 , checked_by , character(3)7 , approved_by , character(3)8 , extraction_date , integer9 , extraction_no , short10, sheets_extracted , short11, rev_description , character(40)12, isodflt_indx_no , integer

# Isometric Last Used Occurrence Data


1 , table_no , integer2 , last_used , integer

# Isometric Sheet Extraction Data

71

PDS 3D Theory — April 2002________________ table number = 188 , number of columns = 7

1 , sheet_indx_no , integer2 , drawing_indx_no , integer , index 13 , sheet_no , integer , index 24 , last_extract_date , integer5 , tot_no_extractions , integer6 , last_mto_date , integer7 , no_of_revisions , integer

# Isometric Drawing Re-Extraction Data


1 , drawing_indx_no , integer , index 12 , section_no , short , index 23 , start_traversal_x , integer4 , start_traversal_y , integer5 , start_traversal_z , integer6 , start_entity , short7 , start_comp_occ , integer8 , start_seg_occ , integer

72

2. Datab

ase O

verview

Design Database________________

2.4.2 Design Database

# Piping Design Database


# The user must not revise this database definition other than to change# column names. Adding user-defined columns and changing lengths of# character data, where valid, must be performed in the Project Administrator# when the project is created.

# Piping Segment Data


1 , system_unique_no , integer , index 12 , line_number_label , character(40)3 , line_id , character(24)4 , unit_number , character(12)5 , unit_code , character(3)6 , module_no , character(16)7 , package_system_no , character(12)8 , train_number , character(2)9 , fluid_code , short , standard note 12510 , line_sequence_no , character(16)11 , nominal_piping_dia , short12 , piping_mater_class , character(16)13 , gasket_separation , character(8)14 , insulation_purpose , short , standard note 22015 , insulation_thick , double16 , insulation_density , double , standard note 1074 (units)17 , heat_tracing_reqmt , short , standard note 20018 , heat_tracing_media , short , standard note 21019 , heat_tracing_temp , double20 , construction_stat , short , standard note 13021 , hold_status , short , standard note 5022 , approval_status , short , standard note 3523 , schedule_override , character(8) , standard note 33224 , nor_oper_pres , double25 , nor_oper_temp , double26 , alt_oper_pres , double27 , alt_oper_temp , double28 , nor_dgn_pres , double29 , nor_dgn_temp , double30 , alt_dgn_pres , double31 , alt_dgn_temp , double32 , steam_outlet_temp , double33 , mater_of_construct , character(6)34 , safety_class , short , standard note 34035 , design_standard , short , standard note 57036 , design_area_number , character(10)37 , design_resp , short , standard note 16038 , construction_resp , short , standard note 16039 , supply_resp , short , standard note 16040 , coating_reqmts , short , standard note 19041 , cleaning_reqmts , short , standard note 23042 , fluid_category , character(4)43 , nor_op_pres_units , short , standard note 1064

73

PDS 3D Theory — April 2002________________ 44 , nor_op_temp_units , short , standard note 105645 , alt_op_pres_units , short , standard note 106446 , alt_op_temp_units , short , standard note 105647 , nor_dgn_pres_units , short , standard note 106448 , nor_dgn_temp_units , short , standard note 105649 , alt_dgn_pres_units , short , standard note 106450 , alt_dgn_temp_units , short , standard note 105651 , steam_temp_units , short , standard note 105652 , stress_system_no , character(12)53 , stress_reqmts , short , standard note 36054 , hyd_system_no , character(12)55 , hyd_reqmts , short , standard note 36056 , specific_gravity_a , double57 , specific_gravity_b , double58 , specific_gravity_c , double59 , viscosity , double60 , density , double61 , spec_heat_ratio , double62 , sonic_velocity , double63 , surface_roughness , double64 , test_system_no , character(6)65 , test_fluid , short , standard note 12566 , test_pressure , double67 , PID_id_part_a , character(4)68 , PID_id_part_b , character(4)69 , end_1_nozzle_id , integer70 , end_2_nozzle_id , integer71 , alpha_descript_id , character(12)72 , standard_note_no , short , standard note 49973 , pid_index_no , integer74 , color_code , character(8)75 , inspection_iso_id , character(24)76 , index_to_pi_dwg , integer

# Piping Component Data


1 , system_unique_no , integer , index 12 , piping_comp_no , character(20)3 , commodity_name , character(6)4 , model_code , character(6)5 , option_code , short , standard note 4006 , maximum_temp , double7 , sched_thick_basis , character(8) , standard note 3328 , commodity_code , character(16)9 , MTO_requirements , short , standard note 36510 , fabrication_cat , short , standard note 18011 , source_of_data , short , standard note 42012 , PDS_sort_code , character(6)13 , physical_data_id , character(8)14 , geometric_standard , short , standard note 57515 , weight_code , short , standard note 57816 , table_suffix_green , short , standard note 57617 , table_suffix_red , short , standard note 57718 , materials_grade , short , standard note 14519 , bend_radius , double20 , bend_angle , double21 , face_to_face_dim , double22 , dimension_a , double23 , dimension_b , double

74

2. Datab

ase O

verview

Design Database________________ 24 , dimension_c , double25 , surface_area , double , standard note 1010 (units)26 , empty_weight , double , standard note 1028 (units)27 , water_weight , double , standard note 1028 (units)28 , operator_weight , double29 , operator_sym_name , character(6)30 , chain_operator_no , short31 , opening_action , short , standard note 39032 , construction_stat , short , standard note 13033 , hold_status , short , standard note 5034 , heat_tracing_reqmt , short , standard note 20035 , heat_tracing_media , short , standard note 21036 , heat_tracing_temp , double37 , iso_dwg_index_no , integer38 , isometric_sheet_no , character(2)39 , piece_mark_no , character(10)40 , color_code , character(8)41 , stress_node_no , short42 , stress_intens_fact , double43 , head_loss_factor , double44 , piping_assembly , character(12)45 , component_group_no , short46 , remarks , character(50)47 , standard_note_no_a , short , standard note 49948 , standard_note_no_b , short , standard note 499

49 , cp_1_nom_pipe_diam , short50 , cp_1_outside_diam , double51 , cp_1_end_prep , short , standard note 33052 , cp_1_sch_thk , character(8) , standard note 33253 , cp_1_rating , character(8)54 , cp_1_face_to_ctr , double55 , cp_1_weld_no , character(8)56 , cp_1_weld_type , short , standard note 1100 / 400 (bolt option)57 , cp_1_gasket_gap , double58 , cp_1_gasket_option , short , standard note 40059 , cp_1_stress_node , short60 , cp_1_stress_factor , double61 , cp_1_head_loss , double


75 , cp_3_nom_pipe_diam , short76 , cp_3_outside_diam , double77 , cp_3_end_prep , short , standard note 33078 , cp_3_sch_thk , character(8) , standard note 33279 , cp_3_rating , character(8)80 , cp_3_face_to_ctr , double81 , cp_3_weld_no , character(8)82 , cp_3_weld_type , short , standard note 1100 / 400 (bolt option)

75

PDS 3D Theory — April 2002________________ 83 , cp_3_gasket_gap , double84 , cp_3_gasket_option , short , standard note 40085 , cp_3_stress_node , short86 , cp_3_stress_factor , double87 , cp_3_head_loss , double

88 , cp_4_nom_pipe_diam , short89 , cp_4_outside_diam , double90 , cp_4_end_prep , short , standard note 33091 , cp_4_sch_thk , character(8) , standard note 33292 , cp_4_rating , character(8)93 , cp_4_face_to_ctr , double94 , cp_4_weld_no , character(8)95 , cp_4_weld_type , short , standard note 1100 / 400 (bolt option)96 , cp_4_gasket_gap , double97 , cp_4_gasket_option , short , standard note 40098 , cp_4_stress_node , short99 , cp_4_stress_factor , double100, cp_4_head_loss , double

101, cp_5_nom_pipe_diam , short102, cp_5_outside_diam , double103, cp_5_end_prep , short , standard note 330104, cp_5_sch_thk , character(8) , standard note 332105, cp_5_rating , character(8)106, cp_5_face_to_ctr , double107, cp_5_weld_no , character(8)108, cp_5_weld_type , short , standard note 1100 / 400 (bolt option)109, cp_5_gasket_gap , double110, cp_5_gasket_option , short , standard note 400111, cp_5_stress_node , short112, cp_5_stress_factor , double113, cp_5_head_loss , double

114, unique_name , character(12)115, vlv_operator_dim_a , double116, vlv_operator_dim_b , double117, vlv_operator_dim_c , double118, vlv_operator_dim_d , double

119, last_placed_date , integer120, generic_comp_no , character(20)121, inspection_key , short122, cp_1_inspect_key , short123, cp_2_inspect_key , short124, cp_3_inspect_key , short125, cp_4_inspect_key , short126, cp_5_inspect_key , short

# Piping/Tubing Data


1 , system_unique_no , integer , index 12 , piping_comp_no , character(20)3 , commodity_name , character(6)4 , model_code , character(6)5 , option_code , short , standard note 4006 , maximum_temp , double7 , nominal_piping_dia , short8 , outside_diameter , double

76

2. Datab

ase O

verview

Design Database________________ 9 , schedule_thickness , character(8) , standard note 33210 , sched_thick_basis , character(8) , standard note 33211 , rating , character(8)12 , commodity_code , character(16)13 , MTO_requirements , short , standard note 36514 , fabrication_cat , short , standard note 18015 , source_of_data , short , standard note 42516 , PDS_sort_code , character(6)17 , geometric_standard , short , standard note 57518 , weight_code , short , standard note 57819 , table_suffix_green , short , standard note 57620 , table_suffix_red , short , standard note 57721 , materials_grade , short , standard note 14522 , pipe_length , double23 , surface_area , double , standard note 1010 (units)24 , empty_weight , double , standard note 1028 (units)25 , water_weight , double , standard note 1028 (units)26 , cold_spring_length , double27 , construction_stat , short , standard note 13028 , hold_status , short , standard note 5029 , heat_tracing_reqmt , short , standard note 20030 , heat_tracing_media , short , standard note 21031 , heat_tracing_temp , double32 , iso_dwg_index_no , integer33 , isometric_sheet_no , character(2)34 , piece_mark_no , character(10)35 , color_code , character(8)36 , piping_assembly , character(12)37 , component_group_no , short38 , remarks , character(50)39 , standard_note_no_a , short , standard note 49940 , standard_note_no_b , short , standard note 499

41 , end_1_end_prep , short , standard note 33042 , end_1_weld_no , character(8)43 , end_1_weld_type , short , standard note 1100 / 400 (bolt option)44 , end_1_gasket_gap , double45 , end_1_gasket_opt , short , standard note 40046 , end_1_stress_node , short47 , end_1_stres_int , double48 , end_1_head_loss , double

49 , end_2_end_prep , short , standard note 33050 , end_2_weld_no , character(8)51 , end_2_weld_type , short , standard note 1100 / 400 (bolt option)52 , end_2_gasket_gap , double53 , end_2_gasket_opt , short , standard note 40054 , end_2_stress_node , short55 , end_2_stres_int , double56 , end_2_head_loss , double57 , unique_name , character(12)

58 , last_placed_date , integer59 , inspection_key , short60 , end_1_inspect_key , short61 , end_2_inspect_key , short

# Instrument Component Data


1 , system_unique_no , integer , index 1

77

PDS 3D Theory — April 2002________________ 2 , instrument_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , sched_thick_basis , character(8) , standard note 3326 , MTO_requirements , short , standard note 3657 , fabrication_cat , short , standard note 1808 , source_of_data , short , standard note 4309 , PDS_sort_code , character(6)10 , physical_data_id , character(8)11 , geometric_standard , short , standard note 57512 , weight_code , short , standard note 57813 , table_suffix_green , short , standard note 57614 , table_suffix_red , short , standard note 57715 , materials_grade , short , standard note 14516 , face_to_face_dim , double17 , dimension_a , double18 , dimension_b , double19 , dimension_c , double20 , surface_area , double , standard note 1010 (units)21 , empty_weight , double , standard note 1028 (units)22 , water_weight , double , standard note 1028 (units)23 , operator_weight , double , standard note 1028 (units)24 , operator_type , double25 , operator_sym_name , character(6)26 , chain_operator_no , short27 , chain_length , double28 , opening_action , short , standard note 39029 , construction_stat , short , standard note 13030 , hold_status , short , standard note 5031 , design_resp , short , standard note 16032 , construction_resp , short , standard note 16033 , heat_tracing_reqmt , short , standard note 20034 , heat_tracing_media , short , standard note 21035 , heat_tracing_temp , double36 , insulation_purpose , short , standard note 22037 , insulation_thick , double38 , insulation_density , double , standard note 1074 (units)39 , cleaning_reqmts , short , standard note 23040 , safety_class , short , standard note 34041 , module_no , character(16)42 , package_system_no , character(12)43 , iso_dwg_index_no , integer44 , isometric_sheet_no , character(2)45 , piece_mark_no , character(10)46 , color_code , character(8)47 , stress_node_no , short48 , stress_intens_fact , double49 , head_loss_factor , double50 , piping_assembly , character(12)51 , component_group_no , short52 , remarks , character(50)53 , standard_note_no_a , short , standard note 49954 , standard_note_no_b , short , standard note 499

55 , cp_1_nom_pipe_diam , short56 , cp_1_outside_diam , double57 , cp_1_end_prep , short , standard note 33058 , cp_1_sch_thk , character(8) , standard note 33259 , cp_1_rating , character(8)60 , cp_1_face_to_ctr , double61 , cp_1_weld_no , character(8)62 , cp_1_weld_type , short , standard note 1100 / 400 (bolt option)

78

2. Datab

ase O

verview

Design Database________________ 63 , cp_1_gasket_gap , double64 , cp_1_gasket_option , short , standard note 40065 , cp_1_stress_node , short66 , cp_1_stress_factor , double67 , cp_1_head_loss , double



94 , cp_4_nom_pipe_diam , short95 , cp_4_outside_diam , double96 , cp_4_end_prep , short , standard note 33097 , cp_4_sch_thk , character(8) , standard note 33298 , cp_4_rating , character(8)99 , cp_4_face_to_ctr , double100, cp_4_weld_no , character(8)101, cp_4_weld_type , short , standard note 1100 / 400 (bolt option)102, cp_4_gasket_gap , double103, cp_4_gasket_option , short , standard note 400104, cp_4_stress_node , short105, cp_4_stress_factor , double106, cp_4_head_loss , double

107, cp_5_nom_pipe_diam , short108, cp_5_outside_diam , double109, cp_5_end_prep , short , standard note 330110, cp_5_sch_thk , character(8) , standard note 332111, cp_5_rating , character(8)112, cp_5_face_to_ctr , double113, cp_5_weld_no , character(8)114, cp_5_weld_type , short , standard note 1100 / 400 (bolt option)115, cp_5_gasket_gap , double116, cp_5_gasket_option , short , standard note 400117, cp_5_stress_node , short118, cp_5_stress_factor , double119, cp_5_head_loss , double

79

PDS 3D Theory — April 2002________________ 120, unique_name , character(12)121, bend_angle , double122, vlv_operator_dim_a , double123, vlv_operator_dim_b , double124, vlv_operator_dim_c , double125, vlv_operator_dim_d , double

126, last_placed_date , integer127, generic_comp_no , character(20)128, inspection_key , short129, cp_1_inspect_key , short130, cp_2_inspect_key , short131, cp_3_inspect_key , short132, cp_4_inspect_key , short133, cp_5_inspect_key , short

# Pipe Support Data


1 , system_unique_no , integer , index 12 , pipe_support_no , character(20)3 , model_code_phy , character(6)4 , model_code_log , character(6)5 , iso_support_type_a , short , standard note 3806 , iso_support_type_b , short , standard note 3807 , iso_support_type_c , short , standard note 3808 , iso_support_type_d , short , standard note 3809 , details_for_shop , character(50)10 , details_for_field , character(50)11 , fabrication_orient , character(20)12 , commodity_code , character(16)13 , MTO_requirements , short , standard note 36514 , fabrication_cat , short , standard note 18015 , weight , double , standard note 1028 (units)16 , construction_stat , short , standard note 13017 , hold_status , short , standard note 5018 , standard_note_no , short , standard note 49919 , iso_dwg_index_no , integer20 , isometric_sheet_no , character(2)21 , piece_mark_no , character(10)22 , color_code , character(8)23 , isometric_dim_a , double24 , isometric_dim_b , double25 , isometric_dim_c , double26 , isometric_dim_d , double27 , isometric_dim_e , double28 , trans_rigidity_x , double29 , trans_rigidity_y , double30 , trans_rigidity_z , double31 , rot_rigidity_x , double32 , rot_rigidity_y , double33 , rot_rigidity_z , double34 , spring_gap_length , double35 , sping_gap_direct , short36 , number_of_springs , short37 , last_placed_date , integer38 , inspection_key , short

# equip_group


80

2. Datab

ase O

verview

Design Database________________ 1 , equip_indx_no , integer2 , equip_no , character(30)3 , equip_descr_1 , character(40)4 , equip_descr_2 , character(40)5 , tutorial_no , character(6)6 , equip_class , character(2)7 , dry_weight , double8 , oper_weight_1 , double9 , oper_weight_2 , double10 , insulation_thk , double11 , construction_stat , short , standard note 13012 , equipment_division , short , standard note 6913 , approval_status , short , standard note 35

# equip_nozzle


1 , nozzle_indx_no , integer2 , nozzle_no , character(10)3 , equip_indx_no , integer4 , nominal_piping_dia , short5 , rating , character(8)6 , preparation , short , standard note 3307 , piping_mater_class , character(16)8 , unit_no , character(12)9 , fluid_code , short , standard note 12510 , unit_code , character(2)11 , line_sequence_no , character(6)12 , heat_tracing_reqmt , short , standard note 20013 , heat_tracing_media , short , standard note 21014 , insulation_purpose , short , standard note 22015 , insulation_thk , double16 , table_suffix , short , standard note 57617 , service , character(20)18 , schedule_thickness , character(8)19 , nor_therm_growth_X , double20 , nor_therm_growth_Y , double21 , nor_therm_growth_Z , double22 , alt_therm_growth_X , double23 , alt_therm_growth_Y , double24 , alt_therm_growth_Z , double25 , construction_stat , short , standard note 130

# equip_nozzle_extended


1 , nozzle_indx_no , integer2 , equip_indx_no , integer3 , parm_indx_no , integer4 , parm_noz_no , short5 , face_of_flange_x , double6 , face_of_flange_y , double7 , face_of_flange_z , double8 , face_flange_pri_1 , double9 , face_flange_pri_2 , double10 , face_flange_pri_3 , double11 , face_flange_sec_1 , double12 , face_flange_sec_2 , double13 , face_flange_sec_3 , double14 , face_flange_nor_1 , double

81

PDS 3D Theory — April 2002________________ 15 , face_flange_nor_2 , double16 , face_flange_nor_3 , double17 , nozzle_type , short18 , nozzle_length_1 , double19 , nozzle_length_2 , double20 , nozzle_radius , double21 , reference_item , character(11)22 , ref_loc_x , double23 , ref_loc_y , double24 , ref_loc_z , double25 , ref_loc_pri_1 , double26 , ref_loc_pri_2 , double27 , ref_loc_pri_3 , double28 , ref_loc_sec_1 , double29 , ref_loc_sec_2 , double30 , ref_loc_sec_3 , double31 , ref_loc_nor_1 , double32 , ref_loc_nor_2 , double33 , ref_loc_nor_3 , double34 , orientation_1 , double35 , orientation_2 , double36 , orientation_3 , double37 , orientation_4 , double38 , dimension_1 , double39 , dimension_2 , double40 , dimension_3 , double41 , dimension_4 , double42 , dimension_5 , double43 , dimension_6 , double44 , c_face_of_flange_x , character(41)45 , c_face_of_flange_y , character(41)46 , c_face_of_flange_z , character(41)47 , c_face_flange_pri , character(31)48 , c_face_flange_sec , character(31)49 , c_face_flange_nor , character(31)50 , c_nozzle_length_1 , character(31)51 , c_nozzle_length_2 , character(31)52 , c_nozzle_radius , character(31)53 , c_ref_loc_x , character(41)54 , c_ref_loc_y , character(41)55 , c_ref_loc_z , character(41)56 , c_ref_loc_pri , character(31)57 , c_ref_loc_sec , character(31)58 , c_ref_loc_nor , character(31)59 , c_orientation_1 , character(11)60 , c_orientation_2 , character(11)61 , c_orientation_3 , character(11)62 , c_orientation_4 , character(11)63 , c_dimension_1 , character(31)64 , c_dimension_2 , character(31)65 , c_dimension_3 , character(31)66 , c_dimension_4 , character(31)67 , c_dimension_5 , character(31)68 , c_dimension_6 , character(31)

#equip_datum_point


1 , equip_indx_no , integer2 , parm_indx_no , integer3 , point_type , short

82

2. Datab

ase O

verview

Design Database________________ 4 , point_indx_no , short5 , loc_x , double6 , loc_y , double7 , loc_z , double8 , loc_pri_1 , double9 , loc_pri_2 , double10 , loc_pri_3 , double11 , loc_sec_1 , double12 , loc_sec_2 , double13 , loc_sec_3 , double14 , loc_nor_1 , double15 , loc_nor_2 , double16 , loc_nor_3 , double17 , c_loc_x , character(41)18 , c_loc_y , character(41)19 , c_loc_z , character(41)20 , c_loc_pri , character(31)21 , c_loc_sec , character(31)22 , c_loc_nor , character(31)

# equip_primitive


1 , equip_indx_no , integer2 , prim_name , character(20)3 , place_pnt_no , short4 , place_by_x , double5 , place_by_y , double6 , place_by_z , double7 , place_by_pri_1 , double8 , place_by_pri_2 , double9 , place_by_pri_3 , double10 , place_by_sec_1 , double11 , place_by_sec_2 , double12 , place_by_sec_3 , double13 , place_by_nor_1 , double14 , place_by_nor_2 , double15 , place_by_nor_3 , double16 , category_type , short17 , dimension_a , double18 , dimension_b , double19 , dimension_c , double20 , dimension_d , double21 , dimension_e , double22 , c_place_by_x , character(41)23 , c_place_by_y , character(41)24 , c_place_by_z , character(41)25 , c_place_by_pri , character(31)26 , c_place_by_sec , character(31)27 , c_place_by_nor , character(31)28 , c_dimension_a , character(31)29 , c_dimension_b , character(31)30 , c_dimension_c , character(31)31 , c_dimension_d , character(31)32 , c_dimension_e , character(31)

# equip_primitive_usr_proj_shape


1 , equip_indx_no , integer

83

PDS 3D Theory — April 2002________________ 2 , prim_name , character(20)3 , place_point_no , short4 , place_by_pri_1 , double5 , place_by_pri_2 , double6 , place_by_pri_3 , double7 , place_by_sec_1 , double8 , place_by_sec_2 , double9 , place_by_sec_3 , double10 , place_by_nor_1 , double11 , place_by_nor_2 , double12 , place_by_nor_3 , double13 , category_type , short14 , number_vertices , short15 , projection , double16 , vertex_1_x , double17 , vertex_1_y , double18 , vertex_2_x , double19 , vertex_2_y , double20 , vertex_3_x , double21 , vertex_3_y , double22 , vertex_4_x , double23 , vertex_4_y , double24 , vertex_5_x , double25 , vertex_5_y , double26 , vertex_6_x , double27 , vertex_6_y , double28 , vertex_7_x , double29 , vertex_7_y , double30 , vertex_8_x , double31 , vertex_8_y , double32 , vertex_9_x , double33 , vertex_9_y , double34 , vertex_10_x , double35 , vertex_10_y , double36 , vertex_11_x , double37 , vertex_11_y , double38 , vertex_12_x , double39 , vertex_12_y , double40 , vertex_13_x , double41 , vertex_13_y , double42 , vertex_14_x , double43 , vertex_14_y , double44 , vertex_15_x , double45 , vertex_15_y , double46 , vertex_16_x , double47 , vertex_16_y , double48 , vertex_17_x , double49 , vertex_17_y , double50 , vertex_18_x , double51 , vertex_18_y , double52 , vertex_19_x , double53 , vertex_19_y , double54 , vertex_20_x , double55 , vertex_20_y , double56 , c_place_by_pri , character(31)57 , c_place_by_sec , character(31)58 , c_place_by_nor , character(31)59 , c_projection , character(31)60 , c_vertex_1_x , character(31)61 , c_vertex_1_y , character(31)62 , c_vertex_2_x , character(31)63 , c_vertex_2_y , character(31)

84

2. Datab

ase O

verview

Design Database________________ 64 , c_vertex_3_x , character(31)65 , c_vertex_3_y , character(31)66 , c_vertex_4_x , character(31)67 , c_vertex_4_y , character(31)68 , c_vertex_5_x , character(31)69 , c_vertex_5_y , character(31)70 , c_vertex_6_x , character(31)71 , c_vertex_6_y , character(31)72 , c_vertex_7_x , character(31)73 , c_vertex_7_y , character(31)74 , c_vertex_8_x , character(31)75 , c_vertex_8_y , character(31)76 , c_vertex_9_x , character(31)77 , c_vertex_9_y , character(31)78 , c_vertex_10_x , character(31)79 , c_vertex_10_y , character(31)80 , c_vertex_11_x , character(31)81 , c_vertex_11_y , character(31)82 , c_vertex_12_x , character(31)83 , c_vertex_12_y , character(31)84 , c_vertex_13_x , character(31)85 , c_vertex_13_y , character(31)86 , c_vertex_14_x , character(31)87 , c_vertex_14_y , character(31)88 , c_vertex_15_x , character(31)89 , c_vertex_15_y , character(31)90 , c_vertex_16_x , character(31)91 , c_vertex_16_y , character(31)92 , c_vertex_17_x , character(31)93 , c_vertex_17_y , character(31)94 , c_vertex_18_x , character(31)95 , c_vertex_18_y , character(31)96 , c_vertex_19_x , character(31)97 , c_vertex_19_y , character(31)98 , c_vertex_20_x , character(31)99 , c_vertex_20_y , character(31)

# equip_parametric


1 , equip_indx_no , integer2 , parm_indx_no , integer3 , symbol_name , character(10)4 , place_pnt_no , short5 , place_by_x , double6 , place_by_y , double7 , place_by_z , double8 , place_by_pri_1 , double9 , place_by_pri_2 , double10 , place_by_pri_3 , double11 , place_by_sec_1 , double12 , place_by_sec_2 , double13 , place_by_sec_3 , double14 , place_by_nor_1 , double15 , place_by_nor_2 , double16 , place_by_nor_3 , double17 , c_place_by_x , character(41)18 , c_place_by_y , character(41)19 , c_place_by_z , character(41)20 , c_place_by_pri , character(31)21 , c_place_by_sec , character(31)

85

PDS 3D Theory — April 2002________________ 22 , c_place_by_nor , character(31)

# equip_parametric_extended


1 , parm_indx_no , integer2 , form_indx_no , short3 , form_name , character(10)4 , form_fld , short5 , data_type , short6 , dimension_no , short7 , nozzle_fld , short8 , fld_attribute , short9 , fld_default , character(21)10 , fld_name , character(13)11 , value_real , double12 , value_char , character(41)

86

2. Datab

ase O

verview

Reference Database________________

2.4.3 Reference Database

# Specification/Material Reference Database


# The user must not revise this database definition other than to change# column names.

# Piping Materials Class Data


1 , system_unique_no , integer2 , piping_mater_class , character(16)3 , revision_no , character(2)4 , version_no , character(2)5 , revision_date , character(10)6 , fluid_code , character(6) , standard note 1257 , mater_of_construct , character(6)8 , corrosion_allow , double9 , mat_description , short , standard note 14810, service_lim_table , character(6)11, diameter_table , character(6)12, thickness_table , character(6)13, materials_table , character(6)14, thickness_equation , character(6)15, branch_table , character(6)16, tap_data_table , character(6)17, vent_drain_macro , character(6)18, gasket_separation , character(8)19, standard_note_no_a , short , standard note 49920, standard_note_no_b , short , standard note 49921, revision_mngt_date , integer22, bend_deflect_table , character(6)23, pipe_length_table , character(6)

# Piping Commodity Specification Data


1 , system_unique_no , integer2 , piping_mater_class , character(16) , index 13 , commodity_name , character(6)4 , option_code , short , standard note 4005 , maximum_temp , double6 , gcp_from_nom_diam , short7 , gcp_to_nom_diam , short8 , gcp_end_prep , short , standard note 3309 , gcp_rating , character(8)10, gcp_sch_thk , character(8)11, gcp_table_suffix , short , standard note 57612, rcp_from_nom_diam , short13, rcp_to_nom_diam , short14, rcp_end_prep , short , standard note 33015, rcp_rating , character(8)16, rcp_sch_thk , character(8)

87

PDS 3D Theory — April 2002________________ 17, rcp_table_suffix , short , standard note 57718, commodity_code , character(16)19, model_code , character(6)20, PDS_sort_code , character(6)21, modifier , double22, geometric_standard , short , standard note 57523, weight_code , short , standard note 57824, fabrication_cat , short , standard note 18025, materials_grade , short , standard note 14526, standard_note_no_a , short , standard note 49927, standard_note_no_b , short , standard note 49928, input_form_type , short , standard note 990

# Piping Specialty Specification Data


1 , system_unique_no , integer2 , piping_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , gcp_from_nom_diam , short6 , gcp_to_nom_diam , short7 , gcp_end_prep , short , standard note 3308 , gcp_rating , character(8)9 , gcp_sch_thk , character(8)10, gcp_table_suffix , short , standard note 57611, rcp_from_nom_diam , short12, rcp_to_nom_diam , short13, rcp_end_prep , short , standard note 33014, rcp_rating , character(8)15, rcp_sch_thk , character(8)16, rcp_table_suffix , short , standard note 57717, physical_data_id , character(8)18, PDS_sort_code , character(6)19, modifier , double20, geometric_standard , short , standard note 57521, weight_code , short , standard note 57822, fabrication_cat , short , standard note 18023, materials_grade , short , standard note 14524, standard_note_no_a , short , standard note 49925, standard_note_no_b , short , standard note 49926, input_form_type , short , standard note 990

# Instrument Component Specification Data


1 , system_unique_no , integer2 , instrument_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , gcp_from_nom_diam , short6 , gcp_to_nom_diam , short7 , gcp_end_prep , short , standard note 3308 , gcp_rating , character(8)9 , gcp_sch_thk , character(8)10, gcp_table_suffix , short , standard note 57611, rcp_from_nom_diam , short12, rcp_to_nom_diam , short

88

2. Datab

ase O

verview

Reference Database________________ 13, rcp_end_prep , short , standard note 33014, rcp_rating , character(8)15, rcp_sch_thk , character(8)16, rcp_table_suffix , short , standard note 57717, physical_data_id , character(8)18, PDS_sort_code , character(6)19, modifier , double20, geometric_standard , short , standard note 57521, weight_code , short , standard note 57822, fabrication_cat , short , standard note 18023, materials_grade , short , standard note 14524, standard_note_no_a , short , standard note 49925, standard_note_no_b , short , standard note 49926, input_form_type , short , standard note 990

# Tap Properties Data


1 , system_unique_no , integer2 , tap_table_name , character(6)3 , nominal_piping_dia , short4 , option_code , short , standard note 4005 , end_preparation , short , standard note 3306 , rating , character(8)7 , sched_thick , character(8)8 , tap_material_code , character(10)

# Piping Commodity Size-Dependent Material Data


1 , system_unique_no , integer2 , sys_commodity_code , character(16) , index 13 , gcp_nom_diam , short4 , rcp_nom_diam , short5 , gcp_sch_thk , character(8)6 , rcp_sch_thk , character(8)7 , commodity_code , character(16)8 , weld_weight , double9 , unit_price , double10, manhours , double

# Piping Commodity Implied Material Data


1 , system_unique_no , integer2 , sys_commodity_code , character(16) , index 13 , gcp_from_nom_diam , short4 , gcp_to_nom_diam , short5 , rcp_from_nom_diam , short6 , rcp_to_nom_diam , short7 , commodity_code , character(16)8 , quantity , double9 , fabrication_cat , short10, standard_note_no , short

89

PDS 3D Theory — April 2002________________ # Reference Database Revision Management Data


1 , specialty_rev_date , integer2 , instr_rev_date , integer3 , tap_data_rev_date , integer4 , size_data_rev_date , integer5 , implied_rev_date , integer6 , cmp_insul_rev_date , integer7 , flg_insul_rev_data , integer8 , con_tol_excl_data , integer

# Component Insulation Exclusion Data


1 , system_unique_no , integer2 , commodity_name , character(6)3 , model_code , character(6)4 , gcp_npd_from , short5 , gcp_npd_to , short6 , rcp_npd_from , short7 , rcp_npd_to , short8 , heat_tracing_from , short , standard note 2009 , heat_tracing_to , short , standard note 20010, insul_purpose_from , short , standard note 22011, insul_purpose_to , short , standard note 22012, nor_oper_temp_from , double13, nor_oper_temp_to , double

# Flange Insulation Exclusion Data


1 , system_unique_no , integer2 , bolted_npd_from , short3 , bolted_npd_to , short4 , heat_tracing_from , short , standard note 2005 , heat_tracing_to , short , standard note 2006 , insul_purpose_from , short , standard note 2207 , insul_purpose_to , short , standard note 2208 , nor_oper_temp_from , double9 , nor_oper_temp_to , double

# Piping Construction Tolerance Exclusion Data


1 , system_unique_no , integer2 , commodity_name , character(6)3 , model_code , character(6)4 , gcp_npd_from , short5 , gcp_npd_to , short6 , rcp_npd_from , short7 , rcp_npd_to , short

90

3. Referen

ce D

ata

Reference Data________________

3. Reference Data

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

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

Piping Job Specification

Graphic Commodity Data and Physical Dimension Data

Material Description Data

Standard Notes / Code Lists

Label Descriptions

Piping Assembly Definitions

The following illustrates the basic components of the Reference Data for PDS 3D.

91

PDS 3D Theory — April 2002________________ The Reference Data Manager supports both approved and unapproved reference data for aproject. The Project Control Database contains complete file management data for both anapproved and unapproved version of each type of reference data such as the Piping JobSpecification or the Graphic Commodity Library. This allows revisions to take place inunapproved files while other activities such as the Piping Designer read the approved files.Once the information in the unapproved files has been verified, it can be posted to theapproved reference data files.

Delivered Reference Data

The following reference data is delivered in the reference database products for thecorresponding practices (such as RDUSRDB for U.S. practice data or RDDINRDB for DINpractice data).

LibraryFile 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 thePD_Shell product in the win32app\ingr\pdshell\lib directory.


Graphic Commodity Library pip_gcom.l pip_gcom.l.t

Piping Assembly Library assembly.l assembly.l.t

Label Description Library labels.l -

Standard Note Library std_note.l std_note.l.t

The following reference data for Equipment Modeling is delivered in the PD_EQP product inthe win32app\ingr\pdeqp\dat directory.


Graphic Commodity Library zi_eqpms.lib -

92

3. Referen

ce D

ata

Reference Data________________ Tutorial Definition Library zi_tutlib.lib -

Cell Library equip.cel -

You should never point to the delivered files for your reference data since this could causepotential problems when you receive a new version of the software. Instead, you should copythe reference data files to a separate location. The script mkpdsdir.sh will copy the referencedata to the appropriate directories after creating the project directory files.

For each of the reference data libraries, you can copy the delivered libraries or create a new(empty) library to which you can load customized data.

93


3.1 Piping Job Specification

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

Specification/Material Reference Database - database containing the definitions forpiping 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 Librarytables is also delivered in the form of neutral files which you can extract and modify.

You can use the Piping Job Specification Manager to create or revise the PJS. The SpecManager enables you to define or revise the PJS data, and process neutral ASCII files todefine data in the PJS.

3.1.1 Piping Materials Class Data

A piping materials class defines a classification of components based on design data andservice limits. Much of the design data is stored in tables so that common information can beaccessed by more than one piping materials class.

The Piping Materials Class Data table contains 23 attributes.

1 , system_unique_no , integer2 , piping_mater_class , character(16)3 , revision_no , character(2)4 , version_no , character(2)5 , revision_date , character(10)6 , fluid_code , character(6) , standard note 1257 , mater_of_construct , character(6)8 , corrosion_allow , double9 , mat_description , short , standard note 14810, service_lim_table , character(6)11, diameter_table , character(6)12, thickness_table , character(6)13, materials_table , character(6)14, thickness_equation , character(6)15, branch_table , character(6)16, tap_data_table , character(6)17, vent_drain_macro , character(6)18, gasket_separation , character(8)19, standard_note_no_a , short , standard note 49920, standard_note_no_b , short , standard note 49921, revision_mngt_date , integer22, bend_deflect_table , character(6)23, pipe_length_table , character(6)

A sample neutral file for US practice is delivered in the filewin32app\ingr\rdusrdb\spec_data\classes.pmc. The following is a partial listing for thisneutral file. Entries in this table should be sorted alphanumerically by Piping Materials

94

3. Referen

ce D

ata

Piping Job Specification________________ Class.

95


3.1.2 Piping Commodity Specification Data

The Piping Commodity Specification Data defines all the components, pipes, bolts, andgaskets associated with a particular Piping Materials Class. It defines the standardcomponents found in a manufacturers catalog (commonly referred to as off-the-shelfcomponents). Because the Piping Commodity Specification Data is linked to the PipingMaterials Class, a separate set of commodity items must be defined for each Piping MaterialsClass database table.

3.1.2.1 Connect Point Data

Information for connect point data is defined in terms of two types of connect points known asgreen and red connect points. The following conventions are used to coordinate the two setsof data:

If data is only shown under the green connect point, it applies to all ends of thecomponent.

If a component has ends with different nominal diameters (regardless of other endproperties) the larger nominal diameter is designated as the green connect point.

If a component has ends with the same nominal diameter but other end properties whichdiffer, the following rules apply:

— If the ends have different termination types (regardless of the values forschedule/thickness) the end(s) whose end preparations have the lowest codelistnumber are designated as the green connect point.

— If the termination types are the same but the values for rating, schedule, or thicknessdiffer, the stronger end(s) is designated as the green connect point.

The Piping Commodity Specification Data table contains 28 attributes:

1 , system_unique_no , integer2 , piping_mater_class , character(16) , index 13 , commodity_name , character(6)4 , option_code , short , standard note 4005 , maximum_temp , double6 , gcp_from_nom_diam , short7 , gcp_to_nom_diam , short8 , gcp_end_prep , short , standard note 3309 , gcp_rating , character(8)10, gcp_sch_thk , character(8)11, gcp_table_suffix , short , standard note 576

96

3. Referen

ce D

ata

Piping Commodity Specification Data________________ 12, rcp_from_nom_diam , short13, rcp_to_nom_diam , short14, rcp_end_prep , short , standard note 33015, rcp_rating , character(8)16, rcp_sch_thk , character(8)17, rcp_table_suffix , short , standard note 57718, commodity_code , character(16)19, model_code , character(6)20, PDS_sort_code , character(6)21, modifier , double22, geometric_standard , short , standard note 57523, weight_code , short , standard note 57824, fabrication_cat , short , standard note 18025, materials_grade , short , standard note 14526, standard_note_no_a , short , standard note 49927, standard_note_no_b , short , standard note 49928, input_form_type , short , standard note 990

The following is a sample neutral file for the Piping Commodity Specification Data. Entriesin this table should be sorted alphanumerically by commodity_name.

A set of neutral files for US practice are delivered in the fileswin32app\ingr\rdusrdb\spec_data\*.pcd (one for each piping materials class specified in theclasses.pmc file).

A set of sample files depicting various options are delivered in thewin32app\ingr\pddata\sample\data directory.

bend_tbl.pcdequiv_npd.pcdfluid_code.pcd

fpipe.pcdgasket.pcdgskt_tbl.pcd

metric_npd.pcdpiplen_tbl.pcdthickness.pcd

97


3.1.3 Piping Specialty Specification Data

This database table contains data for a specific specialty item. It is used to define thosespecialty items which are used frequently by a particular company or installation. Thespecialty items are defined for the entire project, they are not partitioned by Piping MaterialsClass.

You can also place specialty items interactively in the model by defining thenecessary parameters at the time of placement. No entries in the MaterialReference Database are required for these interactive definitions.

The Piping Specialty Specification Data table contains 25 attributes.

1 , system_unique_no , integer2 , piping_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , gcp_from_nom_diam , short6 , gcp_to_nom_diam , short7 , gcp_end_prep , short , standard note 3308 , gcp_rating , character(8)9 , gcp_sch_thk , character(8)10, gcp_table_suffix , short , standard note 57611, rcp_from_nom_diam , short12, rcp_to_nom_diam , short13, rcp_end_prep , short , standard note 33014, rcp_rating , character(8)15, rcp_sch_thk , character(8)16, rcp_table_suffix , short , standard note 57717, physical_data_id , character(8)18, PDS_sort_code , character(6)19, modifier , double20, geometric_standard , short , standard note 57521, weight_code , short , standard note 57822, fabrication_cat , short , standard note 18023, materials_grade , short , standard note 14524, standard_note_no_a , short , standard note 49925, standard_note_no_b , short , standard note 499

A sample neutral file is delivered in the filewin32app\ingr\pddata\sample\data\specialty.data.

98

3. Referen

ce D

ata

Piping Commodity Specification Data________________

3.1.4 Instrument Component Specification Data

This table contains the data for a specific instrument item. It is used to define the instrumentswhich are used frequently by a particular company or installation. The instruments aredefined for the entire project, they are not partitioned by PMC.

You can also place instruments interactively in the model by defining thenecessary parameters at the time of placement. No entries in the MaterialReference Database are required for these interactive definitions.

1 , system_unique_no , integer2 , instrument_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , gcp_from_nom_diam , short6 , gcp_to_nom_diam , short7 , gcp_end_prep , short , standard note 3308 , gcp_rating , character(8)9 , gcp_sch_thk , character(8)10, gcp_table_suffix , short , standard note 57611, rcp_from_nom_diam , short12, rcp_to_nom_diam , short13, rcp_end_prep , short , standard note 33014, rcp_rating , character(8)15, rcp_sch_thk , character(8)16, rcp_table_suffix , short , standard note 57717, physical_data_id , character(8)18, PDS_sort_code , character(6)19, modifier , double20, geometric_standard , short , standard note 57521, weight_code , short , standard note 57822, fabrication_cat , short , standard note 18023, materials_grade , short , standard note 14524, standard_note_no_a , short , standard note 49925, standard_note_no_b , short , standard note 499

A sample neutral file is delivered in the filewin32app\ingr\pddata\sample\data\instrment.data.

99


3.1.5 Tap Properties Data

This table contains the tap properties data that is a function of the tap properties table nameand the nominal piping diameter. These tables define the piping taps which can be added toany of the components included in a piping materials class. The system uses the informationin these tables and the nominal diameter to provide values for rating, end preparation,schedule/thickness, and tap code. Tap tables do not allow a NPD range; there must be anindividual entry for each tap diameter.

1 , system_unique_no , integer2 , tap_table_name , character(6)3 , nominal_piping_dia , short4 , option_code , short , standard note 4005 , end_preparation , short , standard note 3306 , rating , character(8)7 , sched_thick , character(8)8 , tap_material_code , character(10)

A sample neutral file for US practice is delivered in the filewin32app\ingr\rdusrdb\spec_data\taps.data.

100

3. Referen

ce D

ata


Double_SpacingOrder= 2 3 5 4 6 7

! By=GJH Ckd By=RJW Rev=2 Date=12-May-1988

Table= C001! Description= SWE CL3000 default taps! Diam Opt Rating Prp Sc/Th Tap Code

0.375 691 - 591 NREQD E$37591XXX> 0.5 1 CL3000 421 NREQD E$50421064

0.5 691 - 591 NREQD E$50591XXX> 0.75 1 CL3000 421 NREQD E$75421064

0.75 691 - 591 NREQD E$75591XXX> 1 1 CL3000 421 NREQD E001421064

1 691 - 591 NREQD E001591XXX> 1.25 1 CL3000 421 NREQD E1$2421064

1.25 691 - 591 NREQD E1$2591XXX> 1.5 1 CL3000 421 NREQD E1$5421064

1.5 691 - 591 NREQD E1$5591XXX> 2 1 CL3000 421 NREQD E002421064

2 691 - 591 NREQD E002591XXX2.5 691 - 591 NREQD E2$5591XXX

> 3 1 CL3000 421 NREQD E0034210643 691 - 591 NREQD E003591XXX3.5 691 - 591 NREQD E3$5591XXX

> 4 1 CL3000 421 NREQD E0044210644 691 - 591 NREQD E004591XXX5 691 - 591 NREQD E005591XXX6 691 - 591 NREQD E006591XXX8 691 - 591 NREQD E008591XXX10 691 - 591 NREQD E010591XXX12 691 - 591 NREQD E012591XXX14 691 - 591 NREQD E014591XXX16 691 - 591 NREQD E016591XXX18 691 - 591 NREQD E018591XXX20 691 - 591 NREQD E020591XXX24 691 - 591 NREQD E024591XXX26 691 - 591 NREQD E026591XXX28 691 - 591 NREQD E028591XXX30 691 - 591 NREQD E030591XXX32 691 - 591 NREQD E032591XXX34 691 - 591 NREQD E034591XXX36 691 - 591 NREQD E036591XXX42 691 - 591 NREQD E042591XXX48 691 - 591 NREQD E048591XXX

3.1.6 Piping Commodity Size-Dependent MaterialData

The Size-Dependent Data table contains the data for a specific commodity item that isdependent on the commodity code, nominal piping diameter, and schedule/thickness.

This table is used for miscellaneous batch reporting, such as construction cost reports andrequisition orders, and interfaces to material control, stress analysis, and isometric drawingextraction.

101

PDS 3D Theory — April 2002________________ There are multiple occurrences for a specific commodity code and a specific pair of green andred nominal piping diameters in the Piping Commodity Size-Dependent Material Data tablebecause schedule/thickness is not included in the commodity code.

1 , system_unique_no , integer2 , sys_commodity_code , character(16)3 , gcp_nom_diam , short4 , rcp_nom_diam , short5 , gcp_sch_thk , character(8)6 , rcp_sch_thk , character(8)7 , commodity_code , character(16) , index 18 , weld_weight , double9 , unit_price , double10, manhours , double

A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\pcd_size.data.

3.1.7 Piping Commodity Implied Material Data

The Implied Material Data table contains the implied material data for a specific commodityitem that is dependent on both the piping commodity code and nominal piping diameter range.

This data is used strictly for generating implied material for MTO reporting and materialcontrol. It is not used for welds, bolts, nuts, or gaskets, but is reserved for other types ofimplied material, such as caps or stubs, for a specific commodity item. It is also used forreporting the implied components of a commodity item (for example, cap screws).

A unique commodity code must be defined for each commodity definition. For example, if acommodity code is defined for gate valves from 2" to 14", but you want a different descriptionfor a 12" gate valve, you must assign a new commodity code to the 12" valve.

1 , system_unique_no , integer2 , sys_commodity_code , character(16)3 , gcp_from_nom_diam , short4 , gcp_to_nom_diam , short5 , rcp_from_nom_diam , short6 , rcp_to_nom_diam , short7 , commodity_code , character(16) , index 18 , quantity , double9 , fabrication_cat , short10, standard_note_no , short

A sample neutral file for US practice is delivered in the filewin32app\ingr\rdusrdb\spec_data\implied.data.

102

3. Referen

ce D

ata


103


3.1.8 PJS Tables and Functions

The following tables, equations, and calculations are considered part of the Piping JobSpecification even though they are not stored in the Reference Database. The table/equationnames are defined in the Piping Materials Class Data. The actual tables and equations arestored in the Piping Job Specification Table Library.

Temperature and Pressure Service Limits table

This table includes the sets of temperatures and pressures that define the boundaries ofacceptability for a piping materials class.

Nominal Piping Diameter table

The NPD tables lists the diameters for piping and tubing which are valid within anypiping materials class which references this table.

Thickness Data table

Thickness data is determined as a function of the table name and nominal pipingdiameter. These tables include the minimum, retirement, thread, and preferredthicknesses required in the calculation of piping wall thickness. The tables provide theactual thickness; not a schedule. Therefore, there must be an individual entry for eachdiameter. You cannot use an NPD range.

Materials Data table

This table consists of the materials data that is a function of the table name, materialgrade, wall thickness range, and temperature. These tables include the properties whichare required for the calculation of piping wall thickness.

Piping Wall Thickness equation and Branch Reinforcement calculation

These tables define formulas for the calculation of piping wall thickness and branchreinforcement to resist positive pressure. The actual equations and their logic arehardcoded in the software.

Branch Insertion table

A branch insertion table defines the selection criteria for tee and lateral branches.Branch tables define the reinforcement to be used at tee and lateral branches as afunction of the acute angle of intersection and the nominal diameters for the intersectinglines.

The types of branch connections include reinforcing weld, coupling, threadolet,reducing tee, nipolet, reinforcing pad, sockolet, tee, weldolet, and so forth.

104

3. Referen

ce D

ata

PJS Tables and Functions________________ Gasket Separation table

These tables define the gasket gap to be used for a given nominal diameter andmaximum temperature. For each bolted end, the system uses the applicable table, theNPD of the end, and the maximum temperature for the gasket to be used to determinethe gap thickness to be used at the end. Lines in this table are sorted by NPD first andmaximum temperature second.

105


3.2 Graphic Commodity Data andPhysical Dimension Data

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

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

Graphic Commodity Library - contains the parametric definitions for the commodityitems. Entries in this library use the EDEN programming language.

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

The parametric descriptions and dimension tables are also delivered in the form of textlibraries which you can extract and modify using the Graphic Data Library Manager andPhysical Data Library Manager.

Refer to Chapter 4, How PDS Works, for examples of parametric definitions and dimensiontables.

106

3. Referen

ce D

ata

Material Description Data________________

3.3 Material Description Data

The Material Description Data is accessed for

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

Other miscellaneous reporting

Interfaces to material control systems

Stress analysis

Isometric drawing extraction.

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

Material Data in the Specification/Material Database - database tables containingdefinitions for commodity items, criteria for implied material, and weld data.

Short Material Description Library - contains the short material descriptions forcommodity items and taps.

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

Specialty Material Description Library - contains the material descriptions for specialtyitems.

The material descriptions are also delivered in the form of neutral files which you can modifyand post to the libraries. The following shows a portion of a neutral file for the short materialdescription library.

! DEFINE SHORT DESCRIPTIONS

! Date/Time: Wed Jul 7 14:38:03 1993

! Processed Library /usr/ip32/rdusrdb/us_shbom.l

!Cmdty Code ====================================Description========================================

CHAIN_1003 ’Chainwheel operator each with [422] of total chain length for [426] NPD valve with commodity code [400]’


DAABAXAABE ’Monitor, CL150 FFFE, ˆstation type, 4" CL150 in-let by 2.5" NHT stainless steel outlet w/stainless steel stem lock knobs

with 0.75" coupling in base, w/shapertip nozzle, Stang BB0309-21’

DBAAAXBAAB ’Fire hydrant, CL125 FFFE, ˆ5" size, counterclockwise open, 4.5" steamer nozzle, two 2.5" hose nozzles equipped w/caps

and chains, [428], American Darling B-50-B’

DCBGDXEADA ’Hose rack, 300#, FTE, ˆw/valve, wall mount, rt hand w/100 ft hose & fog nozzle, Powhatan 30-333’

DDAXCJDAAA ’Spray sprinkler, MTE, filled cone w/rupture disc, 304, Grinnell, Mulsifyre Projector S-1’

FAAAAAWAAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’

FAAAAAWWAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, cement lined, [409]|bore to match|’

FAAABADIIF ’Flange, CL150, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’

FAAADBDFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-XXS bore’

GEAAAZZADF ’Paddle spacer, CL150, FFTBE, ÂSTM-A516-70, Aitken Z1, [429]’

PAAAAACIIA ’Pipe, S-104, BE, ˆ’

PAAAAAJAAA ’Pipe, S-60, BE, ÂSTM-A53-B Type S’

PAAAAAWWXM ’Pipe, [401], BE, ÂSTM-A53-B Type S, cement lined, treated & wrapped’

PAAAABBAAE ’Pipe, S-STD, BE, ÂSTM-A106-B’

PADAABDGFD ’Pipe, S-XXS, PE, ÂSME-SA335-P11’

107

PDS 3D Theory — April 2002________________ PAFAAAWAAA ’Pipe bend, [403], BE, ˆ6 NPD rad, ASTM-A53-B Type S’

POAAAADIIA ’Nipple, BE, S-80S, 3" long, ÂSTM-A312-TP304 smls’

PRPAXZZAAA ’Reinforcing pad, [425], ASTM-A53-Bˆ’

PUBZZAWVAA ’Pipe, [401], SPE/BLE, ˆpush-on jt, 10 ft lay lngth, ASTM-A74 w/rubber gskt’

QAEZZAKTAB ’Reducing coupling, S-80, SE, ÂSTM-D2467’

SAAQZZZAAA ’Coupling, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

SCAQZZZAAA ’Cap, CL3000, SWE, ÂSTM-A105’

SHAQZZZABB ’Union, CL3000, SWE, ÂSTM-A350-LF2, MSS-SP-83’

SLAQZZZAAA ’90 deg elbow, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

SLAQZZZABB ’90 deg elbow, CL3000, SWE, ÂSTM-A350-LF2, ANSI-B16.11’

SLCQZZZAAA ’45 deg elbow, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

SLCQZZZABB ’45 deg elbow, CL3000, SWE, ÂSTM-A350-LF2, ANSI-B16.11’

STAQZZZAAA ’Tee, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

STBQZZZAAA ’Reducing branch tee, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

STLQZZZAAA ’Lateral, CL3000, SWE, ÂSTM-A105, ANSI-B16.11’

STMQZZZABB ’Reducing branch lateral, CL3000, SWE, ÂSTM-A350-LF2, ANSI-B16.11’

TPAZVZZAAA ’Plug, MTE, ÂSTM-A105, ANSI-B16.11’

UAAEGZZVBB ’1/4 bend, CL250, PE/MJBE, ÂWWA-C110, dbl thk cement lined w/gskt, glnd & blt’

URAEKZZVBB ’Concentric reducer, CL250, PLE/MJBSE, ÂWWA-C110, dbl thk cement lined w/gskt, glnd & blt’

VAAAUXJAAA ’Gate valve, CL150, FFFE, ˆBB, OS&Y, ASTM-A395, brnz trim, Stockham D-623’

VAAAUXJAGR ’Gate valve, CL150, FFFE, ˆBB, OS&Y, ASTM-A395, brnz trim, GO w/side handwheel, Stockham D-623’

VAABAHCCAA ’Gate valve, CL150, RFFE, ˆBB, OS&Y, ASTM-A216-WCB, trim 8, Crane 47’

VBABALCFAA ’Globe valve, CL150, RFFE, ˆBB, OS&Y, ASTM-A216-WCB, trim 12, Crane 143’

VBABALCFRE ’Globe valve, CL150, RFFE, ˆBB, OS&Y, ASTM-A216-WCB, NACE, trim 12, Crane 143’

VCAAUXJCAA ’Check valve, CL150, FFFE, ˆBC, swing, ASTM-A395, brnz trim, Stockham D-931’

VDABAUIBAA ’Ball valve, CL150, RFFE, ˆred. port, end entry, firesafe, ASTM-A216-WCB, plated CS ball, CS trim, Jamesbury 5150’

VEADAZEBAA ’Plug valve, CL150, RFFE, ˆlubricated, ASTM-A216-WCB, 125 Ra finish, Rockwell 1945’

VEADAZECGR ’Plug valve, CL150, RFFE, ˆlubricated, ASTM-A216-WCB, 125 Ra finish, GO w/side handwheel, Rockwell 4149’

VFLAUQRJGR ’Butterfly valve, CL125, FFFE, ÂSTM-A395, trim 316, EPT seat, GO w/side handwheel, Centerline Series 504’

VYFSAHEEAA ’Y globe valve, CL1500, SWE, ˆWB, OS&Y, ASTM-A105, trim 8, Rockwell/Edward 36124’

WAAAAAWAAA ’90 deg LR elbow, [403], BE, ÂSTM-A234-WPB, ANSI-B16.9’

WADAAAWABL ’45 deg LR elbow, [403], BE, ÂSTM-A420-WPL6, ANSI-B16.9’

WBAFBAWIKB ’Stub end, RFLFE/BE, ÂSTM-A403-WP304, ANSI-B16.9, [409]|bore to match|’

WCAAAAWAAA ’Cap, [403], BE, ÂSTM-A234-WPB, ANSI-B16.9’

WOAAAAWIFB ’Weldolet, [412], BE, ˆ|weldolet, |ASTM-A182-F304L’

WOBSABQAFA ’Sockolet, CL3000, BE/SWE, ˆ|sockolet, |ASTM-A105’

WOCTABQAFB ’Thredolet, CL3000, BE/FTE, ˆ|thredolet, |ASTM-A350-LF2’

WODAAAWAFA ’Elbolet, [412], BE, ˆ|elbolet, |ASTM-A105’

WOIAAAWAFA ’Latrolet, [412], BE, ˆ|latrolet, |ASTM-A105’

WOUSABQAFA ’Flatolet, CL3000, BE/SWE, ˆ|flatolet, |ASTM-A105’

WRAAAAWAAA ’Concentric reducer, [414], BE, ÂSTM-A234-WPB, ANSI-B16.9’

WRBAAAWAAA ’Eccentric reducer, [414], BE, ÂSTM-A234-WPB, ANSI-B16.9’

WTAAAAWFAL ’Tee, [403], BE, ÂSTM-A234-WP9, ANSI-B16.9’

WTBAAAWAAA ’Reducing branch tee, [416], BE, ÂSTM-A234-WPB, ANSI-B16.9’

WZBZZZZAZA ’Reinforcing weld, [423], carbon steelˆ’

XAAAAZZICC ’Gasket, CL150, ˆG52, 0.0625" thk comp sheet, org fiber/nitrile binder, full face, ANSI-B16.21’

XDAABZZQSG ’Gasket, CL150, ˆG653, 0.125" thk, 304 spiral wnd, graph filled, CS center ring, API-601’

YAJBPFCFFW ’Cap screws, ASTM-A193-B7,$0.625" diam x 1.5" lg’

YBJIPFKFFW ’Cap screws, ASTM-A193-B7,$1" diam x 3.5" lg’

YZZZHZZFFB ’B44, ASTM-A193-B8C Cl.1 studs w/ASTM-A194-8C hvy hex nuts’

YZZZMZZAAA ’B71, ASTM-A307-B machine bolts w/ASTM-A563-A hvy hex nuts’

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

Refer to Creating Material Takeoffs and Other Reports, page 231 for more information onmaterial descriptions.

108

3. Referen

ce D

ata

Standard Note Library________________

3.4 Standard Note Library

The text for code-listed attributes and standard notes is stored in the Standard Note Library.All attributes identified as code-listed are actually stored as integer values. The code list textassociated with the integer is stored in the Standard Note Library. Information in the StandardNote Library is identified by note number and note type. Output from the library consists offree-format text which forms the standard note.

3.5 Label Description Library

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

Drawing view specific labels

Drawing view identification labels

Drawing block labels

Alphanumeric labels

Displayable attribute messages

Material description attribute messages

Isometric drawing 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 alabel (such as level, line weight, and color code) and to define the format of the label (whatinformation comprises the label.)

109


3.6 Piping Assembly Library

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

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

The following shows a sample PAL file for a drain:

# Drain assemblyPAL ’DRAIN’!! This assembly will place a drain. The user needs to place a 1"! sockolet at the point the drain is desired.!

PLACE FITTING, 6Q3C88 , BY CP1!! The data from the component spec is read into the keywords.! TERM_TYPE_1 TO 5 gets the numeric value for end preparation (eg. 21)! PR_RATING_1 TO 5 gets the pressure rating! GEN_TYPE_1 TO 5 gets the textual value for end preparation (eg. MALE)!

LOAD_SPEC_DATA = ’6Q1C76’!! This ’IF’ statement determines if an optional flange is needed before! the gate valve is placed.!

IF ( GEN_TYPE_1 .EQ. BOLTED ) THENOPTION_RATING = PR_RATING_1OPTION_END_PREP = TERM_TYPE_1PLACE OPTIONAL , 6Q2C01 , BY CP2

ENDIF!! Places a gate valve. Notice in the spec that this type of gate valve! is different than a 6Q2C01.!

PLACE VALVE, 6Q1C76 , BY CP1IF ( GEN_TYPE_2 .EQ. BOLTED ) THEN

OPTION_RATING = PR_RATING_2OPTION_END_PREP = TERM_TYPE_2PLACE OPTIONAL , 6Q2C01 , BY CP1

ENDIF!! This command allows the user to pick which component to place. If the! option command is not used the s/w will choose option 1. In this instance,! without the OPTION_CODE command will cause an error because there are no! option 1 attributes available for 6Q2C16. Another possiblilty would be to! use OPTION_CODE = PROMPT. The user will be prompted for which component is! desired.!

OPTION_CODE = 163PLACE FITTING, 6Q2C16 , BY CP1

END

110

3. Referen

ce D

ata

Standard Note Library________________ The resulting graphics created by the PAL file look like this:

Graphics Placed by Drain Assembly

111


112

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

4. How PDS Works

This sections provides an overview of how the various parts of PDS are used to placecomponents in a model. It also outlines how the information in the model and theaccompanying engineering data in the Databases is used for material control.

All of the examples used in this chapter use the delivered reference data. This chapter isintended to illustrate how PDS uses the reference data rather than point out variouscustomizable features. Detailed customization information is provided in the Spec Writing forPDS 3D Course Guide and in the Reference Data Manager (PD_Data) Reference Guide.

4.1 What Happens When I Place aComponent?

This is a good starting point for a discussion of the various parts that make up PDS and howthese parts work together. The figure on the following page illustrates what happens whenyou place a Gate Valve in a piping model.

PDS makes extensive use of reference data to control the design process. Because PDS usesreference data to control placement operations, it is said to be specification-driven.

When you select a component for placement in the model, the system

uses the active parameters (such as piping materials class and nominal diameter) tosearch for the selected item name in the Specification Material Reference Database. Ifthe selected item is found in the RDB, the system reads the specification data for theparameters required to place the component. Included in this information is the modelcode (or specialty item number) for the selected component and the names of the spectables defined for the Piping Materials Class.

uses the model code (or specialty item number), derived from the RDB, to access theGraphic Commodity Library. The definitions in the Graphic Commodity Librarydetermine the physical tables required to place the component and call the tables in thePhysical Dimension Library.

places the symbol graphics in the model design file and writes the nongraphicinformation for the component in the database.

113


114

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

The Piping Designer provides a graphics environment for the creation and modification ofpiping and instrumentation. The graphics environment will be discussed in more detail inChapter 5.

The Place Component command activates a form used to control the placement operation.

4.1.1 Spec Access

The system uses the active parameters to access information in the Specification/MaterialReference Database. The active segment parameters define the data that will be used to placethe component.

4.1.2 Piping Materials Class Data

The Piping Materials Class setting defines a number of basic parameters. In this examplethe Piping Materials Class is set to 1C0031.

115


Piping Materials Class Code

The delivered reference data uses a 6 character code for the PMC based on the followingconvention.

F - Pressure RatingA - Material GroupXXXX - Sequence Number from Code List Set 148

Following this convention, 1C0031 is interpreted as

1 - CL150C - Carbon Steels0031 - CL150 RFFE, CS, Trim 8

Therefore, PMC 1C0031 equals 150# Carbon Steel, Standard Raised Face, with trim 8.

Refer to the listing of Code List Set 148 in the PDS Piping Component Data Reference Guidefor information on all the codes.

An alternate naming scheme is also described under Code List Set 148. Thisalternate scheme uses the convention:

A - Materials GroupB - Materials TypeC - Detail FeaturesD - Corrosion AllowanceE - ServiceF - Pressure Rating

Following this convention, CAC5C1 is interpreted as

C - Carbon SteelsA - CSC - Std RF. std trim5 - 0.063"C - Process. hot (-20 to 800° F)1 - CL150

You can use either of these conventions or use any standard character code upto 16 characters.

Temperature Pressure Table

This attribute identifies the table used to determine maximum pressure as a function oftemperature. This table includes the pressure and temperature sets that form the boundary forwhich the commodity items included in this piping materials class are suitable.

116

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

Table_Data_Definition ’L1001’

! Description= B16.5 CL150-1.1, -20 to 800! By=DCG Ckd By=DG Rev=0 Date=13-Feb-1987

No_Inputs 1 No_Outputs 1Input_Interpolation 1, Next_OneUnits= DF, PSIG

! Temperature Pressure-20 285100 285200 260300 230400 200500 170600 140650 125700 110750 95800 80END

Diameter Table

This attribute identifies the table used to determine the nominal piping diameter (NPD) valuesfor piping and tubing which are valid for this piping materials class. The following table willallow the placement of 1/2" to 36" piping:

Table_Data_Definition ’D036’

! Description= From 0.5 to 36! By=NP Ckd By=DG Rev=0 Date=22-Jan-1987

No_Inputs 1 No_Outputs 0Units= NPD_IN

! Diam0.50.7511.5234681012141618202224

117


262830323436END

Thickness Table

This attribute defines a table to be used for optional wall thickness and branch reinforcementcalculations. When the table is used, thickness data is determined as a function of nominalpiping diameter. The thickness table includes the minimum, retirement, thread, and preferredthicknesses required in the calculation of piping wall thickness. It provides the actualthickness; not a schedule. Therefore, there must be an individual entry for each diameter.

Table_Data_Definition ’TA501’

! Description= A,0.063CA,0.0071D<=24, 0.0075D>=26! By=DCG Ckd By=DG Rev=0 Date=31-Jan-1987

No_Inputs 1 No_Outputs 8Units= NPD_IN, IN, IN, IN, SC_TH_IN, SC_TH_IN, SC_TH_IN, SC_TH_IN, SC_TH_IN

! Diam Min Thick Ret Thick Thread Thick Preferred Schedules/Thicknesses0.5 .147 .06 - S-160 - - - -0.75 .154 .06 - S-XS - - - -1 .179 .06 - S-XS - - - -1.5 .2 .06 - S-XS - - - -2 .154 .06 - S-STD - - - -3 .216 .06 - S-STD - - - -4 .237 .07 - S-STD - - - -6 .28 .1 - S-STD - - - -8 .250 .1 - S-STD - - - -10 .250 .1 - S-STD - - - -12 .250 .1 - S-STD - - - -

Materials Table

This parameter defines a materials data table used to determine the material properties foroptional wall thickness calculations. The units of measure used in this table must beconsistent with those used in the corresponding Temperature-Pressure Table.

Table_Data_Definition ’ML01’

! Description= Materials per ANSI-B31.3b-1988! By=EPZ Ckd By=RSM Rev=3 Date=03-Oct-1989

No_Inputs 2 No_Outputs 6Input_Interpolation 2, Next_OneUnits= INT, DF, IN, IN, DEC, PSI, DEC, IN

118

4. Co

mp

on

ent

Placem

ent

How PDS Works________________ ! Mill Tolrnce! Mat Gr Temp Thick Range Y S % Value

116 -20 - - .4 20000 12.5 -116 100 - - .4 20000 12.5 -116 200 - - .4 20000 12.5 -116 300 - - .4 20000 12.5 -116 400 - - .4 20000 12.5 -116 500 - - .4 18900 12.5 -116 600 - - .4 17300 12.5 -116 650 - - .4 17000 12.5 -116 700 - - .4 16500 12.5 -116 750 - - .4 13000 12.5 -116 800 - - .4 10800 12.5 -142 -20 - - .4 20000 12.5 -142 100 - - .4 20000 12.5 -142 200 - - .4 20000 12.5 -142 300 - - .4 20000 12.5 -142 400 - - .4 20000 12.5 -142 500 - - .4 18900 12.5 -142 600 - - .4 17300 12.5 -142 650 - - .4 17000 12.5 -142 700 - - .4 16500 12.5 -142 750 - - .4 13000 12.5 -142 800 - - .4 10800 12.5 -162 -20 - - .4 20000 12.5 -162 100 - - .4 20000 12.5 -162 200 - - .4 20000 12.5 -162 300 - - .4 20000 12.5 -162 400 - - .4 20000 12.5 -162 500 - - .4 18900 12.5 -162 600 - - .4 17300 12.5 -162 650 - - .4 17000 12.5 -162 700 - - .4 16500 12.5 -162 750 - - .4 13000 12.5 -162 800 - - .4 10800 12.5 -

Thickness Equations

Thickness equations define formulas for the optional calculation of piping wall thickness andbranch reinforcement to resist positive pressure. The actual equations and their logic arehardcoded in the software.

EL01

Source - ANSI-B31.3c.1986 [Chemical Plant and Petroleum Refinery Piping]Thickness logic from paragraph 304.1, equation 3aReinforcement logic from paragraph 304.3.3 & Code - Appendix H

t =2(SE+PY)

PD_________

119

PDS 3D Theory — April 2002________________ where

P Design pressureD Pipe outside diameterS Allowable stress read from the Materials tableE Joint quality factor determined from the wall thickness attribute Cxxx where xxx is 100

times EY Coefficient Y read from the Materials tableA Additional Thickness (in inches or mm)

Gasket Gap / Table

This attribute defines either a single gasket gap value or a table used to determine the gasketgap based on nominal diameter and maximum temperature. If a table is specified, the systemuses the NPD of each bolted end and the maximum temperature for the gasket at that end todetermine the gap thickness.

In this example, the actual gap value (.125) is used rather than a table name.

4.1.3 Piping Commodity Data

The following shows the delivered commodity item data as defined in 1c0031.pcd.

The active segment parameters define the data that will be used to place the component.Continuing with our example, we will use the information for a 6 inch gate valve.

120

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

Item Name and Model Code

When you select the Gate option from the Place Component form, the system sets the Item Nameto 6Q1C01. This is the item name for a gate valve in the delivered reference data. Thecorresponding Model Code for this Item Name is GAT.

The item name is also called the AABBCC code because it is composed of a number of parameters.For example, the code 6Q1C01 breaks down as follows

AA 6Q Piping In-Line ComponentBB 1C ValvesCC 01 Gate Valve

Option Code

The option code is a code-listed value that tells the system to retrieve the primary commodity item,a secondary commodity item, or another special option from the Piping Commodity Data.

This parameter allows you to select from predefined options at placement. If no option is specified,the system defaults to option 1 (primary commodity item). Option 2 is reserved as the secondarycommodity item. The other options are determined by values for Code List Set 400.

Green and Red Connect Point Data

Since a standard gate valve has the same properties at both ends (connect points) only greenconnect point data is required.

! AABBCC - - - - - - Green CP - - - - - -! Code Opt From To Prp Rating Sc/Th TS

6Q1C01 1 3 12 21 CL150 NREQD 5

The From To values define the range of NPD values supported by this definition in this example3" to 12".

The End Preparation (Prp) is a code-listed attribute that identifies the end preparation for theconnect point. The system determines the termination type based on the range of values

2 - 199 bolted terminations300 - 399 male terminations400 - 599 female terminations

Using the values defined in Code List Set 330, the setting 21 indicates RFFE (Raised-Face FlangedEnd).

121

PDS 3D Theory — April 2002________________ The Rating identifies the pressure rating for the connect point. The setting CL150 refers to ANSIpressure rating CL150. The system interprets the first set of sequential numeric characters as thepressure rating value (150 in this example).

The Schedule Thickness (Sc/Th) exists as alphanumeric data. The value NREQD is used in caseswhere all of the following conditions apply:

The thickness value is not required in purchasing the component.

Empty weights are not significantly affected by actual thickness values.

Either stress analysis is not applicable or, if applicable, the component is to be consideredinfinitely rigid in stress analysis calculations.

The Table Suffix (TS) is a code-listed attribute (CL576) used to further reference the source of thegeneric dimensional data, such as flange data or piping outside diameter data.

For AMS standards, it represents the table suffix for the green connect point. The value 5 is thedefault for US practice. It represents the basis on which most US-practice generic piping tables fordimensional parameters is defined.

End Termination Type Basis for Table ValuesRaised-face flanged..........ANSI-B16.1, B16.5, API-605 or MSS-SP-42,

in this order of precedence

Commodity Code

The commodity code is a user-assigned code that together with the NPD and schedule/thicknessuniquely defines the component. It defines the customer’s commodity code (or part number). Thisattribute is the index into the Material Description Library.

Using the delivered reference data, the commodity code VAABAHCCAA represents

V - ValveA - Gate ValveA - CL150B - Raised Face Flanged EndsA - Carbon SteelH - Trim 8CC - Crane 47AA - Blank

For valves, the commodity code also defines the name of the dry weight table (required for stressanalysis). Refer to Appendix E in the PDS Piping Component Data Reference Guide for a listingof the delivered commodity codes.

122

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

Geometric Industry Standard

This code-listed attribute (CL575) identifies the source of the data (which is usually an industrystandard, such as ANSI, ISO, or DIN, or a company standard) from which the specific geometry ofthe commodity item can be deduced. This parameter represents the vendor or industry standard,and the material if either affects the dimensions of the commodity item.

Code list numbers 2-6999 are reserved for geometry standards that apply to US piping practices.The value 40 indicates

40 = ANSI-B16.10 [Dimensions of Ferrous Valves ||]

Modifier

This attribute has various uses depending on the type of commodity item. For a valve, it representsthe code list number from CL550 (operator/actuator type) which defines the symbol description andthe source of the physical data. If this value is a negative number (such as -3) the operator is notdisplayed when placing the component.

Reviewing CL550, the value 3 indicates a handwheel operator.

Materials Grade

This code-listed attribute (CL145) identifies the material code, specification, grade-temper, andjoint efficiency for the component. This data is used in wall thickness calculations. It can also beused to access physical data in the Graphic Commodity Library.

Reviewing CL145, the value 252 indicates A216-WCB.

Weight code

This code-listed attribute (CL578) defines the weight code for the component. It determines thetable to be used in finding the dry weight of the component. It is required for those cases wherematerial causes the dry weight data but not the dimensional data to differ for a specific geometricindustry standard.

Reviewing CL578, the value 52 indicates

52 = 490 pcf [Carbon steel, low Cr alloy steel, stainless steel]

123


Fabrication Category

This code-listed attribute (CL180) identifies the shop/field fabrication and purchase status of acomponent. It defines how the component was supplied and how the component was fabricated.The value 7 indicates Contractor supplied, field fabricated (CSFF).

4.1.4 Table Access

If all the required information is found in the Specification/Material Reference Database, thesystem performs table access to determine the geometry and dimensions of the component.

Using the Review Component Placement option of the Diagnostics command, you canreview the table access operations used to place the component.

The Place Component Error Data form displays the physical data libraries and Edenmodules that were accessed to place the component. The initial display lists the Edenmodules that were accessed. Indented lines indicate a module which was called from anothermodule. The system places an asterisk (*) beside the module name where Eden stoppedexecuting.

The system uses the model code (or specialty item number) to access the graphic commoditylibrary. The definitions in the graphic commodity library determine the physical tablesrequired to place the component and call the tables in the physical commodity library.

The Graphic Commodity Library (GCL) provides data for commodity items, engineereditems, and instruments. It is basically a catalog of component data which is accessed to

124

4. Co

mp

on

ent

Placem

ent

How PDS Works________________ determine physical data based on user specifications (such as NPD and end preparation)

assign connect point data from the Specification Material Reference Database

define the parametric shape for the model graphics.

PDS Piping uses the Eden Parametric Language to define and place components, specialtyitems, operators, and envelopes. Eden is a high- level programming language which usesinformation from the Material Reference Database and model to access parametric anddimensional data.

Eden is composed of three major types of modules

Symbol Processors

Physical Data Subroutines

Parametric Shape Definitions

These modules are designed to carry out two functions: data definition and graphicpresentation. The modular approach provides for efficient storage of information in theselibraries by enabling common information to be shared by different symbols.

125


Eden Module Relationships

4.1.5 Symbol Processors

A symbol processor is the controlling function or logic used to produce the graphics for acommodity item, piping specialty, instrument, pipe support, or interference envelope. Duringcomponent placement, the symbol processor

accesses the active component design parameters

assigns connect points

Calls the required physical data modules

126

4. Co

mp

on

ent

Placem

ent

How PDS Works________________ determines and calls the required parametric shape modules.

The system retrieves the active component parameters which are dependent upon a connectpoint from the RDB in terms of green, red, or tap connect point properties. The symboldefinition assigns the data corresponding to these connect point types (green, red, or tap) tothe physical connect point numbers (CP1, CP2, CP3, CP4 or CP5).

The first line of the Eden module defines the type of module and the module name. Thefollowing statement is used in the Eden modules to indicate a symbol processor module.

Symbol_Processor ’module name’

The module name is determined by the type of component being placed (commodity item orspecialty item). For a commodity item, the system searches for the Model Code of thecommodity item as the module name. If the Model Code is blank in the Piping CommoditySpecification Data, the system searches for the Item Name as the module name.

The following lists the symbol processor GAT which is used to control the placement of agate valve.

! REGULAR PATTERN, BOLTED OR MALE ENDS GATE VALVESymbol_Processor ’GAT’

Call Assign_Connect_Point ( GREEN, CP1 )Call Assign_Connect_Point ( RED, CP2 )

physical_data_source = ’V1’ // Standard_TypeCall Get_Physical_Data ( physical_data_source )

parametric_shape = ’V1’Call Draw_Parametric_Shape ( parametric_shape )

Valve_Operator = DABS ( Valve_Operator )If ( Valve_Operator .NE. 0 ) Then

If ( Valve_Operator .LT. 1000 ) ThenSubcomponent = ’OP’ // Valve_Operator

ElseSubcomponent = ’A’ // Valve_Operator

EndIfOperator_Orient = FALSE

EndIfStopEnd

Listing for Symbol Processor GAT

4.1.6 Sub-Symbol Processor

A subcomponent call in a symbol processor module indicates a sub-symbol processor.Subcomponents are additions to symbols such as an operator on a valve.

The first line of a sub-symbol processor module indicates the module type and the modulename.

127


Sub_Symbol_Processor ’module name’

The sub-symbol processor name for operators is a concatenation of the characters OP_ and themodifier value from the Piping Commodity Specification Data in the RDB. The value isexpressed as a code list number from CL550 (operator/actuator type). If the value is apositive number (such as 3) the operator is placed with the valve. If the value is a negativenumber (such as -3) the operator is not placed with the valve. (This is useful in segregatinglarge diameter valves which almost always have a valve operator from small diameter valveswhich frequently do not have an operator.)

The symbol processor for the gate valve calls a sub-symbol processor (Subcomponent =’OP’ // Valve_Operator) which places an operator on the valve. The followingdepicts the sub-symbol processor OP_3 which is used to control the placement of a handwheel operator on the valve.

! HANDWHEEL OPERATORSub_Symbol_Processor ’OP_3’

If ( Operator_Orient .EQ. TRUE ) Thenprompt = 1.0Call Prompt_to_Orient_Operator ( prompt )

EndIfphysical_data_source = ’OPERATOR_3’

Call Get_Physical_Data ( physical_data_source )parametric_shape = ’OP3’

Call Draw_Parametric_Shape ( parametric_shape )StopEnd

Listing for Sub-Symbol Processor OP_3

4.1.7 Physical Data Definitions

The system uses the physical data definitions to determine the dimension data, weight data,and surface area data using the active design parameters. Physical data modules are identifiedby the statement

Physical_Data_Definition ’module name’

as the first line in the Eden module.

The module name for a physical data module consists of a symbol type (such as V1, V2, andso forth for valves) and a generic type of geometric industry standard (such as AMS or DIN).You can define multiple physical data modules for the same symbol depending on the type ofstandard being referenced (for example, V1_AMS for American standards and V1_DIN forEuropean standards).

You can manage ten different sets of logic for table naming conventions for the followingindustry practices. The corresponding table suffix ranges and the suffix for the Piping Edenphysical data modules are indicated below.

128

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

Practice Range SuffixU.S. Practice 1-99 AMSEuropean - DIN 100-199 DINEuropean - British Standard 200-299 BRITISH_STDEuropean - Practice A 300-399 EURO_AEuropean - Practice B 400-499 EURO_BInternational - JIS 500-599 JISInternational - Australian 600-699 AUSInternational - Practice A 700-799 INT_AInternational - Practice B 800-899 INT_BCompany Practice 900-999 COMPANY

The geometric industry standard for a component is defined in the Piping Commodity Datatable of the Material Reference Database. Each component must be assigned a geometricindustry standard if it is to use physical data tables.

For most of the delivered symbols, the physical data modules are classified into twocategories: specific and generic. The specific physical data module is called by the symbolprocessor. This module then calls a generic physical data module.

Specific Physical Data Modules

The physical data module V1_AMS determines the specific dimensions (face-to-center andface-to-face) and other physical properties for a gate valve. This is the module called by thesymbol processor GAT

Physical_Data_Definition ’V1_AMS’physical_data_source = ’VALVE_2_AMS’

Call Get_Physical_Data ( physical_data_source )Call Read_Table ( Table_Name_A, input, output )

Surface_Area = Output_1Wet_Weight = Output_2F_to_C_Dim_1 = Output_3

If ( Term_Type_1 .EQ. Term_Type_2 ) ThenF_to_C_Dim_2 = F_to_C_Dim_1

ElseF_to_C_Dim_2 = Output_4

EndIfF_to_F_Dim = F_to_C_Dim_1 + F_to_C_Dim_2

If ( Valve_Operator .LE. 24.0 ) ThenCall Read_Table ( Table_Name_W, input, output )Dry_Weight = Output_1

EndIfReturnEnd

Listing for Physical Data Module V1_AMS

129


Generic Physical Data Modules

The generic modules contain information which is common to more than one symbol such asflange thickness, gasket separation, and outside diameter. The physical data moduleV1_AMS calls another physical data module VALVE_2_AMS which contains the genericdimension data for all valves with two connect points.

Physical_Data_Definition ’VALVE_2_AMS’Input_1 = Nom_Pipe_D_1

If ( Gen_Type_1 .EQ. BOLTED ) Thentable_name = ’BLT’ // Term_Type_1 // Pr_Rating_1 // Gen_Flag_GreenCall Read_Table ( table_name, input, output )Facing_OD_1 = Output_1Thickness_1 = Output_2Seat_Depth_1 = Output_3Thickness_1 = Thickness_1 - Seat_Depth_1CP_Offset_1 = Gasket_Sep_1If ( Symbology .EQ. MODEL ) Then

Thickness_1 = 0.0Depth_1 = 0.0Pipe_OD_1 = 0.0Body_OD_1 = Facing_OD_1

Elsetable_name = ’MAL_300_5’Depth_1 = Thickness_1Input_1 = Nom_Pipe_D_1Call Read_Table ( table_name, input, output )Pipe_OD_1 = Output_2Body_OD_1 = Pipe_OD_1

EndIfElse

If ( Gen_Type_1 .EQ. MALE ) Thentable_name = ’MAL’ // Term_Type_1 // Gen_Flag_GreenCall Read_Table ( table_name, input, output )Facing_OD_1 = Output_2Thickness_1 = 0.0Depth_1 = 0.0Seat_Depth_1 = 0.0CP_Offset_1 = 0.0Pipe_OD_1 = Facing_OD_1Body_OD_1 = Facing_OD_1

Elsetable_name = ’FEM’ // Term_Type_1 // Pr_Rating_1 // Gen_Flag_GreenCall Read_Table ( table_name, input, output )Facing_OD_1 = Output_1Depth_1 = Output_2Seat_Depth_1 = 0.0Thickness_1 = 0.0

If ( symbology .EQ. MODEL ) ThenDepth_1 = 0.0CP_Offset_1 = 0.0Pipe_OD_1 = 0.0Body_OD_1 = Facing_OD_1

ElseCP_Offset_1 = -Depth_1table_name = ’MAL_300_5’Call Read_Table ( table_name, input, output )Pipe_OD_1 = Output_2Body_OD_1 = Pipe_OD_1

130

4. Co

mp

on

ent

Placem

ent

How PDS Works________________

EndIfEndIf

EndIfIf ( Term_Type_2 .EQ. Term_Type_1 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 )

ThenFacing_OD_2 = Facing_OD_1Pipe_OD_2 = Pipe_OD_1Body_OD_2 = Body_OD_1Thickness_2 = Thickness_1Depth_2 = Depth_1Seat_depth_2 = Seat_Depth_1CP_Offset_2 = CP_Offset_1

ElseInput_1 = Nom_Pipe_D_2

If ( Gen_Type_2 .EQ. BOLTED ) Thentable_name = ’BLT’ // Term_Type_2 // Pr_Rating_2 // Gen_Flag_RedCall Read_Table ( table_name, input, output )Facing_OD_2 = Output_1Thickness_2 = Output_2Seat_Depth_2 = Output_3Thickness_2 = Thickness_2 - Seat_Depth_2CP_Offset_2 = Gasket_Sep_2If ( Symbology .EQ. MODEL ) Then

Thickness_2 = 0.0Depth_2 = 0.0Pipe_OD_2 = 0.0Body_OD_2 = Facing_OD_2

ElseDepth_2 = Thickness_2table_name = ’MAL_300_5’Input_1 = Nom_Pipe_D_2Call Read_Table ( table_name, input, output )Pipe_OD_2 = Output_2Body_OD_2 = Pipe_OD_2

EndIf

ElseIf ( Gen_Type_2 .EQ. MALE ) Then

table_name = ’MAL’ // Term_Type_2 // Gen_Flag_RedCall Read_Table ( table_name, input, output )Facing_OD_2 = Output_2Thickness_2 = 0.0Depth_2 = 0.0Seat_Depth_2 = 0.0CP_Offset_2 = 0.0Pipe_OD_2 = Facing_OD_2Body_OD_2 = Facing_OD_2

Elsetable_name = ’FEM’ // Term_Type_2 // Pr_Rating_2 // Gen_Flag_RedCall Read_Table ( table_name, input, output )Facing_OD_2 = Output_1Depth_2 = Output_2Seat_Depth_2 = 0.0Thickness_2 = 0.0If ( Symbology .EQ. MODEL ) Then

Depth_2 = 0.0CP_Offset_2 = 0.0Pipe_OD_2 = 0.0Body_OD_2 = Facing_OD_2

ElseCP_Offset_2 = -Depth_2table_name = ’MAL_300_5’

131


Input_1 = Nom_Pipe_D_2Call Read_Table ( table_name, input, output )Pipe_OD_2 = Output_2Body_OD_2 = Pipe_OD_2

EndIfEndIf

EndIfEndIf

Table_Name_A = Item_Name // Geo_Ind_Std // Term_Type_1Table_Name_W = Commodity_CodeInput_1 = Nom_Pipe_D_1Input_2 = Nom_Pipe_D_2

If ( Term_Type_1 .EQ. Term_Type_2 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 )Then

Table_Name_A = Table_Name_A // Pr_Rating_1 // ’A’Else

If ( Gen_Type_1 .EQ. Gen_Type_2 ) Then! Male X Male or Bolted X Bolted! or Female X Female

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //Pr_Rating_2 // ’A’

Else

If ( Gen_Type_1 .EQ. MALE ) Then! Male X Bolted and Male X Female

Table_Name_A = Table_Name_A // Term_Type_2 // Pr_Rating_2 // ’A’Else

If ( Gen_Type_2 .EQ. MALE ) Then! Bolted X Male and Female X Male

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //Else

! Bolted X Female and Female XBolted

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //Pr_Rating_2 // ’A’

EndIfEndIf

EndIfEndIf

ReturnEnd

Listing for Physical Data Module VALVE_2_AMS

4.1.8 Parametric Shape Definitions

The parametric shape definition describes the graphics symbol (such as bend, flange, or valvebody) which is placed for the component in the model.

Parametric shape definitions are used to place symbol graphics in the model or defineinterference envelopes. This involves the following major functions

defining connect point geometry

132

4. Co

mp

on

ent

Placem

ent

How PDS Works________________ placing connect points

moving the active location a specified distance

drawing a specific graphic shape

placing a center of gravity location.

Parametric shape definitions are divided into three basic types: model parametric shapes,detailed parametric shapes, and interference envelopes. The first line of the Eden moduleindicates the module type and the module name.

Model Parametric Shape Definitions

Model parametric shapes define the symbol graphics to be placed in the model. For example,the parametric shape module for a valve consist of a cylinder, two cones, and a cylinder(flange, valve body, flange).

The first line for these modules is of the form

Model_Parametric_Shape_Definition ’module name’

The module name for a parametric shape module consists of a symbol type (such as V1, V2,and so forth, for valves).

The parametric shape module V1 determines the model graphics for a valve. This is themodule called by the symbol processor GAT. The parametric shape module OP3 determinesthe model graphics for a hand wheel operator. This is the module called by the sub-symbolprocessor OP_3.

Model_Parametric_Shape_Definition ’V1’Call Define_Connect_Point_Geometry ( LINEAR )Call Place_Connect_Point ( CP1 )Call Move_By_Distance ( CP_Offset_1 )Call Draw_Cylinder_With_Capped_Ends ( Depth_1, Facing_OD_1 )

length = F_to_C_Dim_1 - Thickness_1diameter = 0.0

Call Draw_Cone ( length, Body_OD_1, diameter )Call Place_Connect_Point ( CP0 )Call Place_COG_Location ( DRY_COG )Call Place_COG_Location ( WET_COG )

length = F_to_C_Dim_2 - Thickness_2Call Draw_Cone ( length, diameter, Body_OD_2 )Call Draw_Cylinder_With_Capped_Ends ( Depth_2, Facing_OD_2 )Call Move_By_Distance ( CP_offset_2 )Call Place_Connect_Point ( CP2 )

ReturnEnd

Listing for Parametric Shape Module V1

133

PDS 3D Theory — April 2002________________ Model_Parametric_Shape_Definition ’OP3’

Call Define_Connect_Point_Geometry ( OPERATOR )Call Convert_NPD_to_Subunits ( Nom_Pipe_D_1, dia )

dist = dia + Min_Cyl_Dia * 0.5angle = 90.0radius = ( Dimension_2 - Min_Cyl_Dia ) * 0.5

Call Draw_Cylinder_With_Capped_Ends ( Dimension_1, Min_Cyl_Dia )Call Move_by_Distance ( -dist )Call Rotate_Orientation ( angle, Secondary )Call Rotate_Orientation ( angle, Normal )Call Move_Along_Axis ( -radius, Secondary )Call Draw_Torus ( radius, angle, Min_Cyl_Dia )Call Draw_Torus ( radius, angle, Min_Cyl_Dia )Call Draw_Torus ( radius, angle, Min_Cyl_Dia )Call Draw_Torus ( radius, angle, Min_Cyl_Dia )

ReturnEnd

Listing for Parametric Shape Module OP3

134

4. Co

mp

on

ent

Placem

ent

Physical Data________________

4.1.9 Physical Data

Selecting the Component Data option of the Place Component Error Data form displays thephysical data used to place the component.

To place a 6" gate valve, the system references the following tables.

135


4.1.9.1 Generic Tables

The spec access for a six-inch gate valve defines the end preparation at both connect points asRaised Face Flanged End (code list value 21) which is a bolted connection. As shown in thelisting for VALVE_2_AMS, the table name for a bolted connection on a two-connect pointvalve is

table_name= ’BLT’ // Term_Type_1 // Pr_Rating_1 //Gen_Flag_Green

Using the values from the Piping Job Specification (PMC=1C0031, Item Name=6Q1C01), theactual table name will be

BLT_20_150_5

This table returns the outside diameter, flange thickness, and the seating depth for each end ofthe valve. Note that the termination type (20) is used rather than the actual end preparationvalue (21).

You can use the Display Table option to display the contents of a table.

136

4. Co

mp

on

ent

Placem

ent

Specific Tables________________

4.1.9.2 Specific Tables

The specific tables are used to define the main body of the valve. Since the termination typeis the same at both ends of the valve (bolted), no red connect point data is required. Therequired tables are found by referring to the Bolted(G) termination type.

MC_GS_Term(G)_Rat(G)_A (P15A)

MC_GS_Term(G)_Rat(G)_B (P15B) - This table is only required if more than eightoutputs are necessary to define a commodity item.

Commodity Code (P59)

Using this information, the dimension tables for a 6" gate valve are:

GAT_40_20_150_A

This table returns the face-to-center dimension for the valve. Table P15B is notrequired for a gate valve.

VAABAHCCAA

This table returns the empty weight of the valve, including the weight of the operator.

If the end preparations were different at each end of the valve (such as female threaded bysocket welded) then a different set of tables would be required.

An additional table look-up is required to access the dimensional data for the valve operator.The following table is required to define the valve operator.

MC_Type(G)_Rat(G)_Op_A (P31A)

Using this table name format, the dimension table for a hand wheel operator on a 6" gatevalve is:

GAT_BLT_150_3_A

This table returns the stem length and the wheel diameter for the handwheel operator.

137


4.2 Placing Components On ExistingSegments

Piping segments are used to define the basic geometry of a pipeline and to carry commonattributes such as material class and NPD. All components placed in a piping model have anunderlying segment.

Segment data is stored in table 12 of the Design Database.

Data specific to a component is stored in table 34 of the Design Database.

When you place components on an existing piping segment (with Place Component orAutomated Placement), the system determines what type of component should be placedbased on the configuration and attributes of the segment(s) at the active placement point.

The Spec Table Library contains a set of tables which are used to determine the type ofcomponent to place and basic information about the components. Refer to the Reference DataManager Reference Guide for more information on these tables.

4.2.1 Commodity Item Name Table

The Piping Designer reads theCommodity Item Name table whenplacing a component at the vertex ofan existing piping segment. Thistable lists the Item Names of thecomponents to be used at differentsegment configurations (such asreduction, branching, or directionchanges). It enables you to relate thecomponent types hard-coded in thesoftware with the applicablecommodity item codes (item names).As the system processes the segmentfor component placement, it uses thederived item name from the table toreference the Piping CommoditySpecification Data table of theMaterial/Reference Database.

138

4. Co

mp

on

ent

Placem

ent

Placing Components On Existing Segments________________ When placing change of directioncomponents, this table is used inconjunction with the Bend DeflectionTable.

139


4.2.2 Bend Deflection Table

The bend deflection table is usedwhen placing components at thevertex of an existing piping segment.The system uses the bend angle at thesegment vertex to determine the typeof component to be placed.

This table defines which full size andreducing size component types willbe placed for a specified angle range.The angle is defined as the smallestangle that the continuation of onepipe run makes with the other run.The component types are defined inthe commodity item name table.

4.2.3 Branch Insertion Tables

Each Piping Materials Classreferences a set of branch tables: onefor 90-degree branches, one for 45-degree branches, and one for 45-to-90 degree branches.

Branch tables define thereinforcement to be used at tee andlateral branches as a function of theacute angle of intersection and thenominal diameters (first and secondsize) for the intersecting lines.

The system accesses the branch tablewhen placing a component at anintersection when no branchcomponent exists at that location.

The system uses the information inthe table and the first and second sizeto provide the item name of thecomponent to be used at theintersection. Typically, the codes arefrom one of the following types:

Reinforcing elements, such as reinforcing welds and pads.

140

4. Co

mp

on

ent

Placem

ent

Bend Deflection Table________________ Weld-on components reinforcing the intersection such as saddles and weldolets.

Weld-in components actually making the intersection such as laterals and tees.

During branch component placement, the comparison test of header segment data will includenominal piping diameter, override schedule/thickness and construction status.

141


4.2.4 Placement Examples

This section outlines the placement data for a bend, reducer, and tee placed on an existingsegment.

90 Degree Bend

142

4. Co

mp

on

ent

Placem

ent

Placement Examples________________

Reducer (6‘‘x4’’)

Branch (4‘‘x4’’)

143


144

5. Creatin

g 3D

M

od

els

Creating 3D Models________________

5. Creating 3D Models

This chapter describes the basics of 3D modeling using the Equipment Modeling and PipingDesigner Tasks.

5.1 Modeling Setup Requirements

The following operations must be completed before any modeling activities can take place.

5.1.1 Project Setup

A project and all of its accompanying files must be defined with the Project Administratorbefore you can use the Piping Designer or Equipment Modeling. Refer to the ProjectAdministrator 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 or Disk Sharing.

145


5.1.2 Reference Data Setup

Refer to the Reference Data Manager Reference Guide for information on defining thereference data for a project. This data must be defined before you can work in a model. Alsorefer to the Project Data Manager in the Project Administrator Reference Guide forinformation on selecting whether to use the approved or unapproved version of the referencedata for a model file.

5.1.3 Seed Files

When you create a project, the system copies a set of seed files from the PD_Shell directory tothe project directroy: drwsdz.dgn, eqpsdz.dgn, and mdlsdz.dgn. You can use the ProjectData Manager to modify the setting in these seed files. This data is often referred to as Type63 data because it is stored in the Type 63 elements of the design files.

This seed data is discussed throughout the remainder of this chapter. Before creating models,you should define the seed data to reflect your company practices so that all models will becreated with the same settings.

See chapter 6 of the Project Administrator (PD_Project) Reference Guide for detailedinformation on the Project Data Manager.

146

5. Creatin

g 3D

M

od

els

Creating 3D Models________________

5.1.4 Model Files

The Project Environment Manager is used to create, revise, or delete model files. Refer tothe Project Administrator Reference Guide for information on creating a piping model anddatabase files.

You can attach reference models defined in the other PDS 3D disciplines while working in apiping model. Refer to the following documents for information on creating and manipulatingmodels for the PDS 3D disciplines.

PDS Piping Design Graphics Reference Guide

PDS Equipment Modeling Reference Guide

FrameWorks Plus Reference Guide

PE HVAC Modeling Reference Guide

EE Raceway Modeling Reference Guide

5.1.5 Level Control and Graphical Symbology

The use of reference files provides for 63 display levels in the active design file plus 63 levelsfor each referenced discipline. The following example illustrates the levels for a piping modelwith attached reference models:

In this example, there are 63 active levels and 252 referenced levels which you can control(the two equipment models use the same levels and symbology). If a certain type of duct inthe HVAC model resides on Level 30 in that model, and all unapproved Instruments are to beplaced on Level 30 in the piping model, these are treated as two completely different levels.

147

PDS 3D Theory — April 2002________________ That is, you can turn off the display for the duct types on Level 30 in the HVAC model (viathe Reference Model controls) without effecting the display of unapproved instruments in theactive piping model.

All PDS users are encouraged to develop a logical, organized level control standard to manageinterdiscipline design files. The delivered seed file parameters for each application provide alogical, organized, and coordinated level designation and control scheme. You can customizethe delivered parameters, but it is highly recommended that careful thought be given to thecustom setup.

Once you develop a convention, whether it be the standard deliverable settings or anin-house standard, do not change the level or symbology settings after modelgraphics have been created. There is no easy way to propagate these changes to theexisting graphics in all the design files. The existing graphics will reflect the oldsettings and any new graphics will reflect the modified settings.

Since some applications rely on level assignments to perform basic functions (such asplacement of approved or unapproved items) which are transparent to the user, there isa very real chance of destroying the integrity of the project if a symbology change isinitiated after the project is under way.

For this reason, Intergraph recommends that you do not change the basic structure of thesymbology without careful thought. Attributes such as line weights, colors, and line types areopen to customization, but they should be established prior to project creation and should notchange throughout the life of the active design. Level assignments are also customizable;however, they should be established before any components are placed in the model files.

5.1.6 Level and Symbology Defaults

The following outlines the delivered symbology schemes and describes how you can accessthem for review and/or customization.

PDS 3D (Equipment, Piping, and Drawing)

Graphic symbology and level assignments are stored as Type 63 data in the project ormodel seed files. Changes in project seed data will be reflected in all subsequentmodels or drawings, while changes in a model or drawing file’s seed data will applyonly to that design file. The delivered settings are shown in Chapter 6 of the ProjectAdministrator (PD_Project) Reference Guide.

The seed data is accessed through the Project Data Manager function of the ProjectAdministrator. You can create a report of all Type 63 data at any time. Settings arechanged through a forms interface in the Project Data Manager session.

Structural (FrameWorks Plus)

The graphic symbology and level assignments are stored in an ASCII file in thedelivery directory of the FrameWorks Plus product, and are copied into the projectdirectory during project creation. There are both predefined and user-definablecategories (such as New and Existing).

148

5. Creatin

g 3D

M

od

els

Creating 3D Models________________ The default data can be changed using a text editor such as Notepad. The savedchanges are then adapted into the model. The file used for FrameWorks Plus models isframewks.txt

Electrical (EE Raceway)

The graphic symbology is delivered with all categories set to Level 1. This is the onlyapplication within Process & Power which leaves symbology definition totally up to theuser, and it is required prior to accessing a design file.

The default data is defined through a forms interface during project setup. Theprocedure is outlined in the EE Raceway Modeling Reference Guide.

PE-HVAC

Graphic symbology and level control is defined in an ASCII file named hvacSym.defein the project directory. The default data can be changed by editing the hvacSym.defeand hvacSym.defm files in the project directory.

149


5.2 Graphics Environment for PDS 3D

The PDS 3D products provide an interactive graphics environment (based on MicroStation)for the creation and manipulation of design elments. Like the other modules of PDS thesegraphics environments are accessed through PD_Shell. The following outlines the basic stepsto access the graphic environment for most PDS 3D products:

1. Select the project from the PD Shell form and select the product you wish to use.

2. Select the 3D design area for the model to be entered.

3. Select the model to be entered.

The system verifies that you have write access to the selected model. If so, it activatesthe graphical user interface for the selected model file.

150

5. Creatin

g 3D

M

od

els

Working with the Graphical User Interface________________

5.2.1 Working with the Graphical User Interface

The main method of communication between you and the software application is through thegraphical interface. This interface is organized into functional parts; menus, palettes, dialogboxes, view windows, and command menus.

Menus

Menus are your main source of interaction with the software application. It is from menusthat you access all other pieces of the application’s interface.

151


Palettes

Palettes are icon-based menus that provide access to dialog boxes or commands. Thesepalettes are organized into functional parts of the software, with each part represented by anicon on the main palette. An icon is a graphical depiction of a command name that appears ona menu.

Dialog Boxes

Dialog boxes are another type of menu available and represent the most detailed method ofinteraction between you and the software.

152

5. Creatin

g 3D

M

od

els


Dialog boxes contain fields or boxes, menu bars, and buttons that help you to easilycommunicate what you want to the software.

View Windows

Windows provide ways for you to change the way you look at your design. The number andname of each view appears in the title bar.

Window Manipulation Buttons - provide ways to manipulate windows.

Control Menu Box - displays a list of window actions. Double-clicking onthis button deletes the window. To choose an action from the menu, dragthe data button to move the cursor through the list, releasing when thecorrect item is selected.

— Restore - restores a minimized or maximized window to the previoussize and location.

— Move - moves a window around the workspace.

— Size - changes the height and width of the window in the directionindicated by the pointer.

— Minimize - collapses a window down to its smallest size. Clicking onthis icon once the window has been collapsed will restore it to itsoriginal size.

— Maximize - enlarges a window to its maximum size. If you choose thismenu entry on a window that is already at its maximum size, thewindow is restored to its previous size and location.

— Lower - moves a window to the bottom of the window hierarchy.

153


— Close - deletes a window.

Minimize - collapses a window.

Maximize - enlarges a window to its maximum size. If you choose themaximize button on a window that is already at its maximum size, thewindow is restored to its previous size and location.

Move Arrows - drag the data button on the title bar to move the window toa new location on the screen.

Vertical Arrows - appear when the cursor is over the top or bottom of theframe. Drag the data button to change the height of the window as youmove the cursor.

Horizontal Arrows - appear when the cursor is over the left or right side ofthe frame. Drag the data button to change the width of the window as youmove the cursor.

Diagonal Arrows - appear when the cursor is over the frame corners. Clickand drag the data button to change both the height and width of the windowwithout changing the position of the opposite corner.

MicroStation Command Window

The MicroStation Command Window contains the following fields that display systemmessages and your responses through keyboard input.

Control Menu Box - displays a list of window actions. Only the Lower and Sink actions areavailable for the command window. To choose an action, drag the data button through thelist, releasing when the correct item is selected.

Sink Box - moves the command window below views and other windows of its own type.

Menu Bar - displays MicroStation pull-down menus. To choose an item from a list, drag thedata button through the list, releasing when the correct item is selected.

Status Field - displays status messages concerning the system, such as locks and selectedelement information.

Command Field - displays the name of the current active command.

154

5. Creatin

g 3D

M

od

els

Working with the Graphical User Interface________________ Key-In Field - accepts alphanumeric values and key-in commands.

Message Field - displays system messages and prompts.

Prompt Field - displays a system prompt that directs you through a command.

Error Field - displays system error messages.

Forms

Many PDS 3D commands activate forms. Forms are used for a variety of purposes within thePDS environment. Most forms are activated when a command is selected and stay displayedas long as that command is active. When the command terminates, the form is erased.

The Create Drawing form from the Drawing Manager (PD_Draw) product is shown below.

Most forms contain the same basic features: buttons, fields, text, and other gadgets. Ingeneral, anything you find on a form is called a gadget.

Selecting Options

You move through the 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 gadgetand press <D>.

155

PDS 3D Theory — April 2002________________ For most of the forms with scrolling lists, you can double-click on a row to select and acceptthe data in that row. This performs the same action as selecting a row (which highlights) andthen selecting Confirm (√).

You will 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 will use in the environments:

Return — When keying in any data in a key-in field, press the <Return> key for thedata to be entered into the system. You can also press <Return> to move through a setof key-in fields.

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

Windows Editing — You can use standard Windows editing commands to edit key-infields.

156

5. Creatin

g 3D

M

od

els


5.2.2 Common Tools on Forms

There are many gadgets in the environments that are common to most or all of the forms.These tools and their functionality are described below.

The Help command activates on-line Help for the active form. Help remains active until youdelete the Help window.

The Cancel command is used to exit the active software, and return to the system prompt.

The Confirm (√) is used to accept a selection or operation. Depending on the active form oroption, the active form will remain active so that you can repeat a similar operation or controlreturns to the preceding form.

The Reset command with the curved arrow abandons the current form, returning to theimmediately preceding form in the hierarchy.

Scrolling List

Some screen menus have a scrolling list of projects or applications. You need to scroll a listonly if more options are available than can be displayed in the window. To scroll a list, selectthe arrow buttons on the side of the list. The list scrolls up or down depending on which arrowyou choose. To scroll one line at a time, select the smaller arrows. To scroll one window at atime, select the larger arrows.

You can also drag the slider up or down the bar by selecting it with the <D> button, keepingthe <D> button depressed, and moving the mouse up or down. The items scroll through thewindow as you move the button. The size and position of the slider on the scroll bar is anindication of the number of lines and the relative position within the list.

All commands which display a list of design areas or models will order the listalphanumerically by the design area number or model number in ascending order.

Key-in Fields

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

Key-in fields that appear on forms built with Form Builder accept EMACS editingcommands.

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

Microstation requires lowercase characters for the file specification and path name of alldesign files. Therefore, the system will automatically convert any input for the filespecification and path name of a design file (such as a model or drawing) to lowercase beforeloading into the Project Control Database.

157

PDS 3D Theory — April 2002________________ Display-list Boxes

A display-list box is located at the end of some key-in fields and lets you select data from alist instead of keying in information. For example, there is a display list associated with theAuthorization key-in field shown. At the end of the field, there is a small box with horizontaldashes. When you select this display list box with the screen cursor, an associated list of validinput values displays. Select the desired item from the list to input 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 textdisplay to the front of field; Shift Right moves the text display to the end of the field.

Toggle

A toggle field on a screen menu is used to select one of two possible choices, one of which isalways 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 adata point on the roll-through list to scroll through the available options. The optiondisplayed is active.

Standard Window Icons

If you press <D> along the edge of a form or any area not occupied by a button, key-in field,or other gadget, the box of icons shown at right displays. You can manipulate form windowsjust like any other workstation window.

The following list defines in order the available window icons.

Collapse/RestoreRepaint

Pop-to-bottomModify/Resize

Pop-to-topRestore Size

5.2.2.1 Base Form

When you enter the graphics environment, the system displays the base form. This formindicates the product creation date, software version number, active project number, and theactive model number.

158

5. Creatin

g 3D

M

od

els


You can also use this form to define the location on the screen to display all of the PipingDesign forms.

To revise the location of the form display,

Cancel any other forms. The base form should be the only form displayed.

Move the form to the desired location.

Select the File Design command to save the active form location. All subsequent formswill display in the saved location.

159


5.2.3 3D Seed Data

You can use the Project Data Manager to modify seed information for the project seed filesor for a specified model. These options affect all of the project seed files and the projectmarker file.

Select the option for the type of 3D data to be revised. The following report shows thedelivered seetings for the 3D data.

Plant Coordinate System Definition

Plant Coordinate System Description : Plant Coordinate System

Plant Coordinate System Monument :Easting : E 0’ 0" PlantNorthing : N 0’ 0" PlantElevation : El 0’ 0" Plant

Design Volume Coordinate System Definition

Design Volume Coordinate System Description : Design Volume Coordinate System

Design Volume Coordinate System Monument :Monument in Design Volume Coordinate System :

Easting : E 0’ 0" PlantNorthing : N 0’ 0" PlantElevation : El 0’ 0" Plant

Design Volume Monument in Plant Coordinate System :Easting : E 0’ 0" PlantNorthing : N 0’ 0" PlantElevation : El 0’ 0" Plant

160

5. Creatin

g 3D

M

od

els

3D Seed Data________________ Orientation of Design Volume Coordinate: East

Orientation of Design Volume Coordinate System as clockwise AngularOffset of Design Volume North from Plant North : 0.000000

Coordinate Label/Readout Descriptions

Coordinate System Label :Design Volume : SitePlant : PlantWorld : World

Coordinate System Readout :Design Volume :Plant : PlantWorld : World

Coordinate Axis Label :East : EastWest : WestNorth : NorthSouth : SouthElevation : Elev

Coordinate Axis Readout :East : EWest : WNorth : NSouth : SElevation : El

Dimensioning : English

Coordinate Label Prefix/Suffix

Match Line : Match LineCenter Line : CLTop Of Steel : TOSTop of Concrete : TOCBattery Limit : Battery LimitBottom of Pipe : BOPInvert Elevation : InvertPlatform Elevation :Face of Flange : F/FUser Define 1 :User Define 2 :User Define 3 :User Define 4 :User Define 5 :User Define 6 :User Define 7 :User Define 8 :User Define 9 :User Define 10 :User Define 11 :User Define 12 :User Define 13 :User Define 14 :User Define 15 :User Define 16 :User Define 17 :User Define 18 :

161

PDS 3D Theory — April 2002________________ User Define 19 :User Define 20 :

Coordinate Label/Readout Format

Coordinate Label Formats :10’ East Plant10’ Plant EastEast 10’ Plant (Active)East Plant 10’Plant 10’ EastPlant East 10’

Label Description On

Coordinate Readout :10’ E Plant10’ Plant EE 10’ Plant (Active)E Plant 10’Plant 10’ EPlant E 10’

Readout Description On

Coordinate Label/Readout Units

Label Units : Master Units and Subunits

Readout Units : Master Units and Subunits

Metric System of Units Label : Subunits Only

Label Descritions :Master Units Short Description : ’Subunits Short Description : "Master Units and Subunits Separator :Subunits and Fraction of Subunits Separator :

Readout Descriptions :Master Units Short Description : ’Subunits Short Description : "Master Units and Subunits Separator :Subunits and Fraction of Subunits Separator :

Secondary Units Descriptions :Master Units Short Description : MSubunits Short Description : MMMaster Units and Subunits Separator :Subunits and Fraction of Subunits Separator :

Coordinate Label/Readout Precision

Label Precision : Decimal to nearest 1/32

Label Alphanumeric Fraction

Readout Precision : Decimal to nearest 1/32

162

5. Creatin

g 3D

M

od

els

3D Seed Data________________ Secondary Precision : Decimal to nearest integer

Coordinate Label Symbology

Weight :Coordinate Labels : 1Witness Line and Terminator : 1

Color :Coordinate Labels : OrangeWitness Line and Terminator : Orange

Text Font :Coordinate Labels : 23Witness Line and Terminator : 125

Symbol for Line Terminator : 42

Plot Gap Size : 0.250000

Line Spacing : 0

Angular Label/Readout

Angular Label Decimal Degrees Accuracy : 1 Decimal Place

Angular Readout Decimal Degrees Accuracy : 1 Decimal Place

Angular Input is Clockwise from North

Slope Readout Accuracy : Number of Inches per Foot

163


5.3 Creating Equipment Models

The PDS Equipment Modeling (PD_EQP) product models equipment and equipment itemsfor later connection to PDS piping components created through the Piping Designer software.The Equipment Modeling product defines equipment volumes and positions nozzles on theequipment.

5.3.1 Functions of PDS Equipment Modeling(PD_EQP)

With PDS Equipment Modeling (PD_EQP), you can perform the following tasks:

Place basic three-dimensional building blocks such as cylinders, cones and boxes calledprimitives.

Place three-dimensional equipment and components called parametrics, which arepredefined and delivered in a library with the product.

Create complex parametrics using the EDEN language and add them to the ReferenceDatabase for future placement. Refer to the PDS Eden Interface Reference Guide fordetails.

Primitive Parametric

164

5. Creatin

g 3D

M

od

els

Creating Equipment Models________________

5.3.2 About the Reference Database (RDB)

The following libraries comprise the RDB and are used to define the equipment and make itcompatible with exisiting piping specs:

Graphic Commodity Library

Tutorial Definition Library

Piping Physical Data Library

Piping Design Standard Note Library

Piping Specification Tables Library.

5.3.3 Equipment Model Seed Data

The Project Data Manager is used to revise the seed data for a specified Equipment model orcreate a report of the RDB data. You can revise both 3D data and model data. The ReviseEquipment Data option is used to revise the model data for the selected equipment modelfile. The system activates the following form which provides access to the modificationoptions.

Select the option for the type of model data to be revised. The following report shows thedelivered settings for the Equipment Model Data.

165


Project Data Manager

Equipment Graphic Symbology

Primitives/Parametrics

Category Level Color Weight Symbology

Physical 10 9 2 SolidEqp Category 2 1 White 0 SolidEqp Category 3 1 White 0 SolidEqp Category 4 1 White 0 SolidEqp Category 5 1 White 0 SolidEqp Category 6 1 White 0 SolidEqp Category 7 1 White 0 SolidEqp Category 8 1 White 0 SolidEqp Category 9 1 White 0 SolidEqp Category 10 1 White 0 SolidEqp Category 11 1 White 0 SolidEqp Category 12 1 White 0 SolidEqp Category 13 1 White 0 SolidEqp Category 14 1 White 0 SolidEqp Category 15 1 White 0 SolidEqp Category 16 1 White 0 SolidEqp Category 17 1 White 0 SolidEqp Category 18 1 White 0 SolidEqp Category 19 1 White 0 SolidEqp Category 20 1 White 0 Solid

Nozzles


Nozzle Category Small 12 9 3 SolidNozzle Category Medium 12 9 3 SolidNozzle Category Large 12 9 3 Solid

Envelopes


Maintanence Envelope (Hard) 40 8 1 SolidMaintanence Envelope (Soft) 41 8 0 SolidAccess Envelope (Hard) 42 10 1 SolidAccess Envelope (Soft) 43 10 0 SolidSafety Envelope (Hard) 44 11 1 SolidSafety Envelope (Soft) 45 11 0 SolidConstruction Envelope (Hard) 46 12 1 SolidConstruction Envelope (Soft) 47 12 0 Solid

Equipment Graphic Symbology (continued)

Steel


Ladders 20 White 1 SolidPlatforms 21 White 1 SolidHandrails 22 White 1 SolidMiscellaneous Light Steel 23 White 1 Solid

166

5. Creatin

g 3D

M

od

els

Creating Equipment Models________________

Dumb Graphics


Dumb Category 1 30 White 0 SolidDumb Category 2 1 White 0 SolidDumb Category 3 1 White 0 SolidDumb Category 4 1 White 0 SolidDumb Category 5 1 White 0 SolidDumb Category 6 1 White 0 SolidDumb Category 7 1 White 0 SolidDumb Category 8 1 White 0 SolidDumb Category 9 1 White 0 SolidDumb Category 10 1 White 0 SolidDumb Category 11 1 White 0 SolidDumb Category 12 1 White 0 SolidDumb Category 13 1 White 0 SolidDumb Category 14 1 White 0 SolidDumb Category 15 1 White 0 Solid

Miscellaneous


Place Point 48 15 8 SolidDatum Point 50 13 10 SolidHole Elements 15 White 0 Solid2-D Shadows 12 9 3 Solid

Semi Intelligent Graphics


Semi-Intelligent Category 1 51 White 0 SolidSemi-Ingelligent Category 2 52 White 0 SolidSemi-Intelligent Category 3 53 White 0 SolidSemi-Intelligent Category 4 54 White 0 SolidSemi-Intelligent Category 5 55 White 0 Solid


Nozzle Default Placement Options

Nominal Piping Diameter

System of Units : English

Small is <= : 2INLarge is >= : 14IN

Table Name : D036

Define Table Suffix by End Type : Bolted - 5Female - 5Male - 5


Equipment Reference Database Management

167

PDS 3D Theory — April 2002________________ Graphic Commodity Library

Approved : wegl /usr/ip32/pdeqp/dat/ zi_eqpms.lib

Tutorial Definition LibraryApproved : wegl /usr/ip32/pdeqp/dat/ zi_tutlib.lib

Equipment Physical Data LibraryApproved :

Piping Physical Data LibraryApproved : wegl /usr/ip32/rdusrdb/ us_pcdim.l

Piping Design Standard Note LibraryApproved : wegl /usr/ip32/pdshell/lib/ std_note.l

Piping Job Specification Table LibraryApproved : wegl /usr/ip32/rdusrdb/ us_pjstb.l

Cell libraryApproved : wegl /usr/ip32/pdeqp/dat/ equip.cel

Forms Directory LocationApproved : wegl /usr/ip32/pdeqp/


Interference Envelope Emulation Data

Distance Between Two Planes for Clash Checking : 1"Number of Emulated Cylinders Per 90 Degree Torus : 4Length of Emulated Cylinders for Cone : 1"Length of Emulated Cylinders for Semi-Ellipsoid : 1"

168

5. Creatin

g 3D

M

od

els

Equipment Modeling Environment________________

5.3.4 Equipment Modeling Environment

The Equipment Modeling Interface is accessed through PD_Shell. This interface allows youto enter the Equipment Modeling graphics environment, create or modify Eden and TutorialDefinition files, print reports and define or edit filenames and locations for libraries.

Operating Sequence

1. At the Plant Design System form, select the Equipment Modeling option.

The system displays the Equipment Modeling Options form.

2. Select the Equipment Modeling option to enter the graphics environment.

The system displays the Equipment Modeling form listing the available design areanumbers and their corresponding descriptions.

169


3. Select Design Area

Select the 3D design area to modify and click Confirm.

The system lists the equipment models for the selected design area and theircorresponding descriptions.

4. Select Model

Select the Model Number to modify and click Confirm.

The system enters the graphics design file.

170

5. Creatin

g 3D

M

od

els

Equipment Modeling Concepts________________

5.3.5 Equipment Modeling Concepts

You can orient equipment items in a 3D design file using the refresh (orientation) tee and thecoordinate axis system. The refresh tee provides you with both the active point location andthe active orientation. The active point displays where the graphics will be placed while theactive orientation displays the graphic’s orientation.

The term refresh denotes graphics which are temporarily drawn on the screen and can bemoved dynamically. The refresh tee appears at the active place point when selectingplacement commands. It consists of two lines.

The primary axis originates at the active place point and is aligned with the equipmentitem center line.

The secondary axis is aligned perpendicular to the primary axis with its origin at thebisecting point with the primary axis. This axis is used to define the auxiliaryorientation.

When placing an equipment item with the refresh tee, you can adjust the orientation by one ofthe following methods:

Selecting the reset button (<R>) to adjust the orientation 90 ° around the active axis.

Keying in a specific angle.

Using the Refresh Manipulation commands via the coordinate axis system.

The coordinate axis system display consists of a refresh line originating at the active placepoint and pointing in one of six coordinate directions: North, East, Up, South, West andDown.

171


If the coordinate axis system display is turned on, the refresh tee appears at the active placepoint when you select a secondary command such as Absolute PDS XYZ or Delta PDSXYZ.

You can confirm the direction of the active axis by viewing the status field. The systemdisplays the directional information using a few simple symbols.

**P-IN S-

P - primary axisS - secondary axis** - indicating the active axis-IN or-OUT

- indicating the direction the active axis is pointing depending on the active view.In a specified view (other than Iso), IN points away from you when looking at amodel. OUT points toward you when looking at a model. For example whenlooking at a north view, IN points north (away from you) and OUT points south(toward you).

In the example above, the primary axis is the active axis and points IN toward the displayedview. The secondary axis is only visible in the displayed view. Since the primary axis isactive, it can be rotated by a Refresh Manipulation command.

The refresh tee cannot be displayed on a screen if it is located outside of thescreen view.

Also, a 3D representation of the orientation axes with their center located on the placementpoint appears in place of the orientation tee previous to its displacement. This axis is calledthe Coordinate Axis or the Coordinate System Indicator (CSI).

172

5. Creatin

g 3D

M

od

els

Equipment Modeling Concepts________________

5.3.6 Activating the Orientation Tee

When activating the orientation tee, the system displays the coordinate axis in its placeprevious to its displacement. The orientation tee can be manipulated only in the followinginstances:

It can be manipulated when the active point is defined using the ACTIVE POINTcommand. After selecting this command, you can use any of the pocket menu optionsto manipulate the tee. Angles of rotation cannot be entered with this command.

When placing equipment and components using a form or a parametric tutorial forequipment or component generation and manipulation. Angles of rotation can be keyedin, where positive angles are measured in the counterclockwise direction looking fromthe direction where the non-rotating axis is pointing. To change the axis to be rotated,select the CHANGE AXIS option.

When an equipment or component manipulation command (Move, Copy, Rotate,Mirror, etc.) is active. Angles of rotation for primary or secondary axis cannot beentered in this mode.

173


5.4 Equipment Modeling Commands

This section lists the Equipment Modeling commands that are available.

5.4.1 Equipment Manipulation Commands

These commands allow you to create, copy, move, delete, rotate and mirror entire pieces ofequipment defined either individually or by a fence. You can create equipment using userdefined primitives or parametrics.

5.4.2 Component Manipulation Commands

These commands allow you to add components or equipment items to existing pieces ofequipment and also copy, move, delete, rotate, mirror, and modify equipment items.

5.4.3 Nozzle Manipulation

This command allows you to place nozzles in reference to a datum point or another nozzle.The new nozzle will be added to the same equipment tag owning the referenced datum pointor nozzle.

5.4.4 Review/Revise Commands

These commands allow you to view or revise data associated with the current project ordrawing. This data includes project file data and equipment attributes.

5.4.5 Define Commands

These commands allow you to define the active placement point, the view orientation, anddisplay categories.

5.4.6 Miscellaneous Commands

These commands perform a variety of manipulations including envelope file generation,datum point manipulation, dimension checking, viewing specific equipment groups, attachinggraphics, controlling display categories, reviewing error messages, attaching referencemodels, and defining saved views.

174

5. Creatin

g 3D

M

od

els

Equipment Modeling Commands________________

5.4.7 Secondary Commands

These commands provide support for the primary commands. A Secondary Command willnot function unless a primary command is active. These commands are used to orient thescreen views, defines precision input, adjust the orientation of the refresh tee, or define thecoordinate system.

175


5.5 Creating Piping Models

The Piping Designer (PD_Design) is one module of PDS 3D products. It is specificallyintended for the creation and revision of 3D models in the design of the piping and in-lineinstrumentation within the plant. The resulting piping models can be used for checkinginterferences, extracting drawings, and generating bills of material.

The following illustration shows a typical piping model with reference models attached. Thepiping model contains fully dimensioned graphics for piping, piping components, instruments,piping specialties, and pipe supports. You can access coordinate points from the referencemodels and review database attributes.

Piping Model With Attached Reference Models

176

5. Creatin

g 3D

M

od

els

Creating Piping Models________________ Each component in a piping model is linked to a database record which contains non-graphicinformation about the component. When a component or segment is placed in the model, thesystem creates a row in the appropriate database table(s). A row represents one instance orrecord in the database.

Database Attributes Associated with Graphics

177


5.5.1 Piping Model Seed Data

The Revise Model Data option is used to revise the Model data in the project seed file or aspecific piping model. The system activates the following form which enables you to accessthe modification options.

Select the option for the type of model data to be revised. The following report shows thedelivered settings for the Piping Model Data.


Component Placement

Bend Deflection Table : BEND_DEFLECTION

Commodity Name Table : COMMODITY_ITEM_NAME

Pipe Length Threshold Table : PIPE_LENGTH

Segment Pipe Run Length Threshold Table : PIPE_RUN_LENGTH

Weld Type Table : WELD_TYPE_TABLE

Flange Data Module :

Reinforcing Weld Data Module :

Reinforcing Pad Data Module :

Pipe Commodity Name : PIPING

Tube Commodity Name : TUBE

Field Weld Symbol Name :

178

5. Creatin

g 3D

M

od

els

Piping Model Seed Data________________ Isometric Drawing Symbol Name :

Angular Tolerance (Automated Component) : 0.500000

Vicinity Tolerance : 4.000000


Piping Data Control

P&ID Component Name : Commodity Name

Fluid Code Update : Off

Weight Table : On

Branch Component Association for Isometric Drawings : Header

Copy Option : Append Prefix

Geometric Industry Standard : Expanded

Schedule Thickness Override Option : Larger of Override and Spec

System of Units for Nominal Piping Diameter : English

Field Name for Nominal Piping Diameter : IN


Physical Units Options

Insulation Density : lb/ftˆ3

Surface Area : ftˆ2

Dry/Wet Weights : lb

Maximum Temperature (Spec) : degF


Nozzle Data Transfer List

There are currently NO nozzle attributes selected for transferProject Data Manager

Graphic Symbology

Weights :Piping Commodity : 2Piping Specialty : 2Instrument : 2Piping/Tubing : 2Pipe Support : 2

Model Symbology : Simple

Color : Model Category


Graphic Symbology - Model Category

179

PDS 3D Theory — April 2002________________ Nominal Piping Diameter :

Small is <= 2INLarge is >= 14IN

Level ColorPiping Segment Not Approved Small 1 BluePiping Segment Not Approved Medium 11 BluePiping Segment Not Approved Large 21 BluePiping Segment Approved Small 31 BluePiping Segment Approved Medium 41 BluePiping Segment Approved Large 51 BluePiping/Tubing Not Approved Small 3 GreenPiping/Tubing Not Approved Medium 13 GreenPiping/Tubing Not Approved Large 23 GreenPiping/Tubing Approved Small 33 GreenPiping/Tubing Approved Medium 43 GreenPiping/Tubing Approved Large 53 GreenPiping Commodity Not Approved Small 2 GreenPiping Commodity Not Approved Medium 12 GreenPiping Commodity Not Approved Large 22 GreenPiping Commodity Approved Small 32 GreenPiping Commodity Approved Medium 42 GreenPiping Commodity Approved Large 52 GreenPiping Specialty Not Approved Small 4 OrangePiping Specialty Not Approved Medium 14 OrangePiping Specialty Not Approved Large 24 OrangePiping Specialty Approved Small 34 OrangePiping Specialty Approved Medium 44 OrangePiping Specialty Approved Large 54 OrangeInstrument Not Approved Small 5 OrangeInstrument Not Approved Medium 15 OrangeInstrument Not Approved Large 25 OrangeInstrument Approved Small 35 OrangeInstrument Approved Medium 45 OrangeInstrument Approved Large 55 OrangePipe Support - Logical Not Approved N/A 7 VioletPipe Support - Physical Not Approved N/A 10 WhitePipe Support - Logical Approved N/A 37 VioletPipe Support - Physical Approved N/A 40 WhiteMiscellaneous Graphics 58 RedDiagnostic Markers 59 RedAutomated Component/Pipe Placement Markers 62 RedModel Reconstruction Markers 63 Red


Symbology for Markers

Weights :Diagnostic Markers : 2Design Check Markers : 2Automated Placement Markers : 2Model Reconstruction Markers : 2Field Weld and Isometric Drawing Symbol : 2

Symbol Font Number : 125

Text Height : 6"

Text Width : 6"

Field Weld Symbol Name :

Isometric Drawing Symbol Name :Project Data Manager

Material Takeoff Options

180

5. Creatin

g 3D

M

od

els

Piping Model Seed Data________________ Commodity Code : Size Independent

Length Calculation : Almost Precise

Bolt Commodity Code : Piping Job Spec

Bolt Diameter Units : English

Bolt Length Units : English

Bolt Roundoff Option : Preferred Bolt Length Table

Alternate Gasket Search : Off

Field Fit Length : Off

Gasket Commodity Name : 6Q3C95Bolt Commodity Name : 6Q3C97Nut Commodity Name : 6Q3C98

Bolt Data Module : BOLT_DATAFlange Data Module : FLANGE_DATA_MTOBolt Length Table : BOLT_LENGTH


Design Review Label Option

Selected Labels :There are NO Design Review Labels Selected


Default Segment Parameters

unit_numberfluid_code Standard Note Number is Undefined <125,0>unit_codeline_sequence_nonominal_piping_dia 100-3/4INpiping_mater_classinsulation_purpose Standard Note Number is Undefined <220,0>insulation_thick 0’ 0"nor_oper_pres 0.000nor_op_pres_units Standard Note Number is Undefined <1064,0>nor_oper_temp 0.000nor_op_temp_units Standard Note Number is Undefined <1056,0>nor_dgn_pres 0.000nor_dgn_pres_units Standard Note Number is Undefined <1064,0>nor_dgn_temp 0.000nor_dgn_temp_units Standard Note Number is Undefined <1056,0>insulation_density 0 lb/ftˆ3heat_tracing_reqmt Standard Note Number is Undefined <200,0>heat_tracing_media Standard Note Number is Undefined <210,0>heat_tracing_temp 0 degFdesign_resp Standard Note Number is Undefined <160,0>supply_resp Standard Note Number is Undefined <160,0>construction_resp Standard Note Number is Undefined <160,0>construction_stat Standard Note Number is Undefined <130,0>hold_status Standard Note Number is Undefined <50,0>design_area_numberalt_oper_pres 0.000alt_op_pres_units Standard Note Number is Undefined <1064,0>alt_oper_temp 0.000alt_op_temp_units Standard Note Number is Undefined <1056,0>alt_dgn_pres 0.000alt_dgn_pres_units Standard Note Number is Undefined <1064,0>alt_dgn_temp 0.000alt_dgn_temp_units Standard Note Number is Undefined <1056,0>

181

PDS 3D Theory — April 2002________________ steam_outlet_temp 0.000steam_temp_units Standard Note Number is Undefined <1056,0>train_numbermater_of_constructsafety_class Standard Note Number is Undefined <340,0>design_standard Standard Note Number is Undefined <570,0>fluid_categorycoating_reqmts Standard Note Number is Undefined <190,0>cleaning_reqmts Standard Note Number is Undefined <230,0>package_system_no


Default Segment Parameters (continued)

module_nospecific_gravity_a 0.000specific_gravity_b 0.000specific_gravity_c 0.000viscosity 0.000density 0.000spec_heat_ratio 0.000sonic_velocity 0.000surface_roughness 0.000test_system_notest_fluid Standard Note Number is Undefined <125,0>test_pressure 0.000schedule_override


Design Consistency Checks

Data :Flow Direction : Hard CheckFlow Centerline : Hard CheckOutside Diameter : No CheckSchedule/Thickness : No CheckPiping Materials Class : Soft CheckMaterials of Construction Class : Soft CheckInsulation Thickness : Soft CheckInsulation Purpose : Soft Check

Tolerances :Flow Centerline Alighment : 0.500000Insulation Thickness : 1/4"


End Prep Compatibilities

Bolted End Preps

FFFE -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE FFTBCSEWG FFFTBE FFFTBEWG

FFFEWG -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE FFTBCSEWG FFFTBE FFFTBEWG

RFFE -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG

RFFEWG -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG

RJFE -RJFE RJLFE RJTBE MRJTBEWG RJTBCSE

182

5. Creatin

g 3D

M

od

els

Piping Model Seed Data________________ STFE -

SGFE SGLFE

LTFE -LGFE LGLFE

SMFE -SFFE SFLFE

LMFE -LFFE LFLFE

SGFE -STFE STLFE

LGFE -LTFE LTLFE

SFFE -SMFE SMLFE

LFFE -LMFE LMLFE

FFLFE -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG

RFLFE -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG

RJLFE -RJFE RJLFE RJTBE MRJTBEWG

STLFE -SGFE SGLFE

LTLFE -LGFE LGLFE

SMLFE -SFFE SFLFE

LMLFE -LFFE LFLFE

SGLFE -STFE STLFE



Bolted End Preps

LGLFE -LTFE LTLFE FFTBCSEWG

SFLFE -SMFE SMLFE

LFLFE -LMFE LMLFE

FFTBE -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE

FFTBEWG -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSEWG

183

PDS 3D Theory — April 2002________________ RFTBE -

FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE

RFTBEWG -FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSEWG

RJTBE -RJFE RJLFE RJTBE MRJTBEWG RJTBCSE

MRJTBEWG -RJFE RJLFE RJTBE

FFTBCSE -FFFE FFFEWG FFTBE

FFTBCSEWG -FFFE FFFEWG LGLFE FFTBEWG

RFTBCSE -RFFE RFFEWG RFTBE

RFTBCSEWG -RFFE RFFEWG RFTBEWG

RJTBCSE -RJFE RJTBE

FFFTBE -FFFE FFFEWG FFFTBE

FFFTBEWG -FFFE FFFEWG FFFTBEWG

MJE -MJE



Male End Preps

BE -BE TBE PE SE SWE HCE

TBE -BE TBE PE SWE HCE

MFE -MFE

MTE -FTE

MGE -FGE

MQCE -FQCE

MFRE -FFRE

MHE -FHE

SPE -BLE

184

5. Creatin

g 3D

M

od

els

Piping Model Seed Data________________ PE -

BE TBE PE SE SWE FTE HCE

3"FFPE -HCE



Female End Preps

SE -BE PE

SWE -BE TBE PE

FTE -MTE PE

FGE -MGE

FQCE -MQCE

FFRE -MFRE

FHE -MHE

BLE -SPE

HCE -BE TBE PE 3"FFPE

Project Data ManagerReference Database Management

Material/Specification Reference DatabaseApproved : ra_tcproj

Piping Job Specification Table LibraryApproved : wegl /usr/ip32/rdusrdb/ us_pjstb.l

Short Material Description LibraryApproved : wegl /usr/ip32/rdusrdb/ us_shbom.l

Long Material Description LibraryApproved : wegl /usr/ip32/rdusrdb/ us_lgbom.l

Specialty Material Description LibraryApproved : wegl /usr/ip32/rdusrdb/ us_spbom.l

Standard Note LibraryApproved : wegl /usr/ip32/pdshell/lib/ std_note.l

Label Description LibraryApproved : wegl /usr/ip32/pdshell/lib/ labels.l

Piping Assembly LibraryApproved : wegl /usr/ip32/pdshell/lib/ assembly.l

185

PDS 3D Theory — April 2002________________ Graphic Commodity Library

Approved : wegl /usr/ip32/pdshell/lib/ pip_gcom.l

Physical Data Library - U.S. PracticeApproved : wegl /usr/ip32/rdusrdb/ us_pcdim.l

Physical Data Library - DINApproved :

Physical Data Library - British StandardApproved :

Physical Data Library - European AApproved :

Physical Data Library - European BApproved :

Physical Data Library - JISApproved :

Physical Data Library - AustralianApproved :

Physical Data Library - International AApproved :

Physical Data Library - International BApproved :

186

5. Creatin

g 3D

M

od

els

Graphic Concepts for Piping Design________________

5.5.2 Graphic Concepts for Piping Design

The screen working area is used to display and manipulate graphic information. Thisinformation is managed by MicroStation; refer to the MicroStation documentation for details.

Refresh graphics are graphics which are temporarily drawn on the screen. Piping Designeruses refresh graphics to display placement aids such as the orientation tee and coordinatesystem indicator.

Graphics are frequently highlighted to provide visual feedback pertaining to the active input.Highlighting is normally followed by an Accept/Reject step allowing you to accept thehighlighted graphics as the desired input or to reject the highlighted graphics and selectanother graphic.

This following concepts and terms are common to the Piping Designer operations.

5.5.2.1 Piping Segments

The centerline routing within a model is represented by geographically connected pipingsegments. A piping segment defines the geometry of the pipeline and contains the non-graphical data associated with that pipeline. A single piping segment can define changes ofdirection, but an additional segment is created at a branch point or an attribute break, such as asize change or a spec break.

The following illustrates the terminology associated with a piping segment.

A pipeline consists of a set of graphically connected piping segments including all thebranches.

187


5.5.2.2 Active Placement Point

The term active placement point refers to the coordinate location used by the PlaceComponent command. It defines the point at which piping and instrumentation are placed.You can use Connect to Design to place a piping or instrument component at an existing,intelligent location in the model, such as a piping or instrumentation connect point, a nozzle,or a piping segment.

The system uses the orientation tee to indicate the location of the Active Placement Point.

5.5.2.3 Coordinate System Indicator and Orientation Tee

Coordinate System Indicator

The coordinate system indicator is a temporary display symbol which represents the sixorthogonal directions (North, South, East, West, Up, and Down) of the coordinate system.

Piping Designer uses the coordinate system indicator to indicate the active coordinatelocation when

defining or manipulating a piping segment

identifying a point on a piping segment

identifying a component center or connect point

188

5. Creatin

g 3D

M

od

els

Graphic Concepts for Piping Design________________ sketching a pipeline.

5.5.3 Orientation Tee

The orientation tee is a temporary display symbol which enables you to orient a componentbefore placement. The orientation tee is composed of two lines:

a primary axis representing the flow centerline

a secondary axis used to orient components which are not symmetrical about the flowcenterline (for example, a valve with an operator).

When the Place Component command is active, the system displays the orientation tee at theActive Placement Point and displays related information in the screen message fields.

P **S-OUT

The stars (**) indicate the active axis of rotation (the secondary in the above message). Wheneither axis is rotated such that its orientation is not in the plane of the view, the suffix IN orOUT is displayed next to P (primary) or S (secondary) indicating whether that axis is pointingin or out of that view. For example, when the secondary axis is perpendicular to the screenand oriented toward the designer, the message P S-OUT is displayed.

When placing a component with the orientation tee, you can adjust the orientation by pressing<R> or selecting one of the Orientation Control commands.

189


5.5.3.1 Piping Connect Points

Each component has a center and at least one connect point or pressurized end. A connectpoint is usually an end of a piping component to which another component or pipe (withcompatible properties) is connected. The connect point stores the description of thecomponent at that end. It indicates the flow centerline orientation, and properties such asdiameter, end preparation (flanged, welded,...), and rating.

The following rules (in order of priority) are used to determine the assignment of connectpoint numbers:

1. Connect Point 1 is always at the larger end (NPD).

2. If the ends have the same NPD, but different end preparations, then Connect Point 1 isassigned an end preparation in the following precedence: Bolted, Male, Female.

Refer to the PDS Piping Component Data Reference Guide for a detailed explanation ofconnect point assignments.

190

5. Creatin

g 3D

M

od

els

Piping Design Commands________________

5.6 Piping Design Commands

The following Piping Design commands are available..pE

5.6.1 Placement Commands

Placement commands enable you to place pipe, piping components, pipe supports, andinstrument components. You can also place assemblies (predefined sets of components).

These commands can be used at any time in the design process. In the process of creating apiping model you will use a combination of these commands depending on the desired result.A typical approach is to use

Sketch to route the layout of a pipeline and define the attribute data for the pipeline.The attribute data can be defined manually, copied from another segment, or updatedfrom information in the P&ID database.

Place Component to place components such as valves, instruments, or commodityoverrides along the segment pipeline.

Automated Placement to populate the pipeline with fittings and pipe.

The Copy Piping, Copy and Mirror Piping, and Copy and Rotate Piping commandsautomatically change the approval status of piping segments and piping components to notapproved during the copy operation.

You cannot make any of the following changes to approved piping.

Create a new piping segment in the Sketch command by connecting to previouslyplaced, approved piping.

Place new piping components, instrument components, piping, or tubing in the PlaceComponent command by connecting to previously placed, approved piping.

Place new pipe supports in the Place Pipe Support command by connecting topreviously placed, approved piping.

Place new pipe supports in the Place Logical Support command by connecting topreviously placed, approved piping.

191


5.6.2 Revision Commands

The Revision commands enable you to move, delete, and rotate existing piping. You canrevise individual components, piping segments, or all the elments on a pipeline or defined bya group operation.

These commands can be used at any time in the design process to move, modify, or delete acomponent, a piping segment, or a group of elments such as a pipeline.

Any rotation, addition, reconstruction, or deletion of PDS piping components and segmentsmust be done through these commands and not through MicroStation manipulations due to theinterdependence of graphic and database information.

5.6.3 Component Revision

These commands revise/append different positional and/or database information on PDSpiping components. Any rotation, addition, or reconstruction of PDS piping components mustbe done through these commands and not through MicroStation manipulations due to theinterdependence of graphic and database information. You cannot use MicroStationcommands to change piping as they will not update the user data associated with the pipingsegment or component.

5.6.4 Segment Vertex Commands

These commands enable you to revise piping segments in the active model. You can add,move, or delete an imbedded vertex for an existing piping segment. These command cannotbe used if the segment has been populated with pipes or components.

5.6.5 Piping Revision

These commands enable you to move, delete, rotate, and reconstruct existing piping. You canrevise a pipeline or those elements defined by an active group. The commands perform bothgraphical and database revisions.

192

5. Creatin

g 3D

M

od

els

Piping Design Commands________________

5.6.6 Model Data

These commands enable you to review or revise the model data stored in the Design Databaseand Project Control Database. Each component in a piping model is linked to a databaserecord which contains non-graphic information about the component. When a component orsegment is placed in the model, the system creates a row in the appropriate database table.

These commands can be used at any time in the design process to review or revise the modeldata stored in the Design Database.

5.6.7 Review Data

These commands enable you to review information in the Design Database or review existingreport files. You can only view the information you cannot make any changes. You canreveiw data for elements in the active model and attached reference models.

5.6.8 Revise Data

These commands enable you to revise information in the Design Database and defineadditional information for components. You can only revise information for items in theactive model.

5.6.9 Analyze Data

These commands enable you to review information related to the model analysis operations.You can also check for interferences within the active model file. Many of these commandare dependent on data from the Design Data Management commands.

Refer to the Chapter on Interference Detection for more information on detecting andreviewing interference clashes.

193


194

6. P&

ID D

ata T

ransfer

P&ID to Piping Data Transfer________________

6. P&ID to Piping Data Transfer

PDS provides cababilities for distributing data from one part of the design process to another.One aspect of this integration is the transfer and comparison of data between the P&ID taskand the Piping task. This section describes the conventions that apply to the loading,updating, and comparison of data between the P&ID Database and the piping model.

Features

Update segment data. You can transfer segment data from the P&ID to update theactive segment data, to define line attributes while sketching, or to revise a segmentattribute or set of attributes.

Review component names. You can select a component on the P&ID to define thecommodity item to be placed.

Compare data. You can compare data in the model against data in the P&ID to verifythat all the information is in agreement.

Graphical interface. The easiest way to transfer or review data is to use the graphicaldata transfer options. This allows you to display the P&ID drawing in a view whileworking in the model and select items directly from the drawing graphics.

PDS also supports transfer by line ID or by identifying an equipment nozzle as the startof a pipeline.

6.1 Database Requirements

For the P&ID Database to be linked to the Piping Design Database, the two applications mustshare the same Project Control Database schema. This can be achieved by using the sameproject number when creating the schematic project and the 3D project. Although the ProjectControl Database schema must be shared, the P&ID Database schema and the Piping DesignDatabase schema are otherwise independent.

Unit Number

The unit number attribute is used to locate the relevant P&ID data within the P&ID Task andMaster Database. The unti number should be set in the active segment data to match the UnitNumber setting within the P&ID database.

195


Propogated Drawings

Only those P&ID drawings which have been successfully propogated can be referenced forP&ID to Piping data transfer.

196

6. P&

ID D

ata T

ransfer

P&ID Correlation Table________________

6.2 P&ID Correlation Table

The P&ID Correlation Table is an ASCII file used to correlate a particular column or columnsin the P&ID segment table of the P&ID Database with a corresponding column in the pipingsegment table of the Piping Design Database.

The P&ID Correlation Table defines which database columns are to be transferred andcompared.

Any columns not specified in the Correlation Table will not be transferred.

The P&ID column numbers required in the Correlation table are from the relational databaseand are not the P&ID attribute numbers.

During the interactive loading of segment data, you can specify that either a complete orpartial set of data be considered. The Correlation Table specifies which columns are to beloaded, updated, or compared for both complete and partial data transfer.

The Correlation Table is expected to exist in the project directory for the applicable project,(the directory that includes the seed model, seed drawings, etc.) A default Correlation Tableis delivered in the PD_Shell product and is automatically copied to the project directory whena new project is created. You can edit the Correlation Table, if required, to add columns to ordelete columns from both the complete and partial data transfer processes. An asterisk (*)signifies that data transfer and comparison is applicable for that particular column. You canalso add user-defined columns of piping segment data to the Correlation Table.

The default Correlation Table is defined as follows:

# Segment Data Model P&ID Complete Partial#If you desire to default the ’non-partial’ attributes during a partial transfer of#data, in the partial column place a ’-’, skip at least one space, and define the#default value. The default value will be used whenever an interactive transfer#occurs, or if the toggle is set for the batch update. The complete,#partial and default values are supported ONLY in this section of the file.#example: attribute_one 99 100 * - default_valueunit_number 4 13unit_code 5 2 * *module_no 6 79 *package_system_no 7 81 *train_number 8 23 * *fluid_code 9 22 * *line_sequence_no 10 24 * *nominal_piping_dia 11 15 *npd_units -1 16piping_mater_class 12 25 * *insulation_purpose 14 26 * *insulation_thick 15 28 *insulation_thick_units -1 29insulation_density 16 30 * *insulation_density_units -1 31heat_tracing_reqmt 17 73 * *heat_tracing_media 18 74 * *heat_tracing_temp 19 75 * *heat_tracing_temp_units -1 76construction_stat 20 60 * *

197

PDS 3D Theory — April 2002________________ hold_status 21 83 * *schedule_override 23 66 *nor_oper_pres 24 39 *nor_oper_temp 25 41 *alt_oper_pres 26 43 *alt_oper_temp 27 45 *nor_dgn_pres 28 47 *nor_dgn_temp 29 49 *alt_dgn_pres 30 51 *alt_dgn_temp 31 53 *steam_outlet_temp 32 86 *mater_of_construct 33 61 *safety_class 34 59 *design_resp 37 69 *construction_resp 38 78 *supply_resp 39 71 *coating_reqmts 40 72 *cleaning_reqmts 41 77 *fluid_category 42 84 *nor_op_pres_units 43 40 *nor_op_temp_units 44 42 *alt_op_pres_units 45 44 *alt_op_temp_units 46 46 *nor_dgn_pres_units 47 48 *nor_dgn_temp_units 48 50 *alt_dgn_pres_units 49 52 *alt_dgn_temp_units 50 54 *steam_temp_units 51 87 *test_system_no 64 55 *test_fluid 65 56 *test_pressure 66 57 *

### Data extracted from the Piping Segment Table ( piping_seg, 112 ) of the P&ID Design Database:

# upstrm_node_nopid_node_number_a - 10

# dwnstrm_node_nopid_node_number_b - 11

flow_direction - 14

# line_no_labelline_number_label - 21

# dwg_occ_nodrawing_segment_index_no - 3

line_id - 12

# piping_thk_flagpiping_thickness_flag - 68

### Data extracted from the Equipment Table ( eq_group, 106 ) of the P&ID Design Database:

equipment_number - 7

### Data extracted from the Equipment Nozzle Table ( eq_nozz, 108 ) of the P&ID Design Database:

nozzle_number - 5

# pid_seg_occ_no

198

6. P&

ID D

ata T

ransfer

P&ID Correlation Table________________ nozzle_segment_index - 4

# eq_grp_occ_noequipment_nozzle_index - 2

# node_noequip_nozzle_node_no - 13

### Data extracted from the Piping Component Table ( piping_comp, 120 ) of the P&ID Design Database:

#piping_comp_table is the delimiter to signal the information below belongs to# P&ID’s piping_comp table and Piping’s pdtable_34_<partition_number>.# piping_comp_table signals that the following attributes belong to pdtable_34.piping_comp_table

piping_comp_number 2 6

aabbcc_code 3 9

commodity_code_flag - 28

cmdty_code 8 29

# opt attribute in P&ID is placed into the option_code attribute in Pipingcommodity_option_code 5 27

# pid_seg_occ_nocomp_segment_index_no - 3

# dwg_occ_nocomp_drawing_index_no - 2

# generic_tag_nospecialty_generic_tag_no - 44

#any attributes you desire to transfer (beyond those defined above) are listed# here. You determine which are transferred between P&ID piping_comp table# and piping pdtable_34. NOTE: Complete, partial and default do NOT# apply to these attributes.#attribute name (any thing) piping attr no p&id attr noconst_status 32 23heat_tracing_media 35 34heat_tracing_reqmts 34 33hold_status 33 41ht_tracing_media_temp 36 35opening_action 31 17remarks 46 20

### Data extracted from the Instrument Component Table ( instr_comp, 131 )of the P&ID Design Databas

#instr_comp_table is the delimiter to signal the information below belongs to# P&ID’s instr_comp table and Piping’s pdtable_67_<partition_number>.# instr_comp_table signals that the following attributes belong to pdtable_67.instr_comp_table

instrument_tag_number - 5

# pid_seg_occ_noinstr_segment_index_no - 4

# aabbcc_codeinstr_aabbcc_code - 10

199

PDS 3D Theory — April 2002________________ # dwg_occ_noinstr_drawing_index_no - 3

#generic_tag_noinstr_generic_tag_no - 80

#any attributes you desire to transfer (beyond those defined above) are listed# here. You determine which are transferred between P&ID instr_comp table# and piping pdtable_67. NOTE: Complete, partial and default do NOT# apply to these attributes.#attribute name (any thing) piping attr no p&id attr nocleaning_reqmts 39 60const_resp 32 35const_status 29 24dgn_resp 31 25fail_action_1 28 56heat_tracing_media 34 28heat_tracing_reqmts 33 27hold_status 30 40ht_tracing_media_temp 35 29insulation_purpose 36 31insulation_thick 37 33module_no 41 36package_system_no 42 38remark_2 52 22safety_classification 40 20

### Data extracted from the Drawing Table ( dwg, 102 ) of the P&ID Project Database:

drawing_number - 3

#unit_occ_nounit_index_number - 2

drawing_title - 16

network_address - 7

path_name - 8

file_specification - 5

propagation_status - 10

approval_initials - 21

approval_date - 22

revision_id - 27

for_comments_date - 29

for_design_date - 30

for_construct_date - 31task_name - 4

### Data extracted from the Unit Table ( unit, 101 ) of the P&ID Project Database:unit_number - 4unit_code - 3unit_name - 5

200

6. P&

ID D

ata T

ransfer

P&ID Correlation Table________________ ### Data extracted from the Task RDB Table ( task_rdb, 98 ) of the P&ID Project Database:pid_task_name - 2pid_task_rdb_node - 3pid_task_rdb_path - 4

### Data extracted from the PID Segment Table ( pid_seg, 110 ) of the P&ID Design Database:

# net_type_occ_nopiping_segment_index_no - 4

### Data extracted from the PID Drawing Revision Data Table ( dwg_rev_data,### 103 ) of the P&ID Design Database includes the following:dwg_occ_no - 2

### Data extracted from the Piping Connector Table (piping_connector, 124) of### the P&ID Design Database includes the following:connector_no - 4

#dwg_occ_no of the piping connector tableconnect_dwg_occ_no - 2

#pid_seg_occ_no of the piping connector tableconnect_pid_seg_occ_no - 3

#matching_criteria is the criteria to be used for matching the P&ID and Piping#segments together. Nodea (piping attribute 67) and Nodeb (piping attribute 68)#are the default criteria. The matching criteria is defined by listing the#piping attribute numbers separated by a space on the line below.matching_criteria 67 68

#search_mode is the method for searching for the matching criteria. The default#is ’FIRST’ – stop on the first match found. The other option is ’END’ which#means to search the entire database looking for a match. If more than one match#is found, the software evaluates all of the matches for an exact match of the#transfer data.search_mode FIRST

#exclusion_criteria has been a part of the submission process in the past. We#have added the capability to default this value. Values are ’YES’ for do not#check the transfer disabled segments and ’NO’ to check the transfer disabled#segments. This option can still be modified at submission.exclusion_criteria YES

201


6.3 P&ID Graphical Data Transfer Setup

You can select and view an active P&ID while working in a piping model. This enables thegraphical transfer of piping segment data by snapping to graphics in the active P&ID. Youcan also specify a component name for placement by selecting a component in the P&ID.

You can use the following options to select the active P&ID to be displayed. Only one P&IDcan be active for the purposes of data transfer.

You can select a drawing from a list of P&IDs extracted from the Project ControlDatabase. This list of drawings is limited to those P&IDs which have been propagatedfor the active unit number in the piping model. The applicable drawings are listed inalphanumeric order by drawing number.

Since the P&ID Database is unit dependent and the Piping Design Database is designarea dependent, one Piping design area may include data from different P&ID units.Therefore, you must specify the correct unit number in the active segment data prior torequesting a list of P&I drawings from the P&ID Database.

Select P&I Drawing by Line ID - You can specify a line ID by identifying piping inthe piping model or by accepting the active line id. The system determines the P&ID(or list of drawings) from the line id. It searches the Segment Table of the P&IDDatabase using the system unique number for the drawing and the line ID for thesegment.

Select P&I Drawing by Nozzle - You can specify an equipment number and nozzlenumber by locating a component connected to a nozzle, by keying in an equipmentnumber and nozzle number, or by snapping to a nozzle in an equipment model. Thesystem determines the P&ID from the equipment number and nozzle number and datain the P&ID Database.

202

6. P&

ID D

ata T

ransfer

P&ID Graphical Data Transfer Setup________________ You can use the Review P&I Drawing Details option to display information about a selectedP&I Drawing in the active unit.

Once you select a drawing by any of the described methods, the P&I drawing and thecorresponding drawing border are attached as reference files.

A selected screen view is used to display the P&ID. The system stores this view number inthe Type 63 data for the piping model.

203


6.4 P&ID Node Numbers

When piping segment data is transferred from the P&ID Database to the piping model, theP&ID node numbers derived from that database are reflected in the model as a form ofassociativity between the P&ID and the piping model. The following rules dictate how P&IDnode numbers are assigned during the creation of piping segments in the model.

Transferring piping segment data from the P&ID Database by any means results in theP&ID node numbers being stored with the piping segment that is to be created by eitherthe Place Component or Sketch command.

If you continue creating new piping segments in the model, either by explicitly placinga piping segment or by placing a component that results in the placement of a pipingsegment, the new piping segments continue to include the P&ID node numbers from theinitial piping segment.

If, at any time, you update the piping segment data manually with the Active SegmentData option, the P&ID node numbers for the subsequent piping segment is assigned asundefined (blank).

Using the First Size or Second Size option to place a reducing component will notresult in the P&ID node numbers being assigned as undefined unless you also use theActive Segment Data option.

If you place a component after specifying the active placement point with the Connectto Design option, the P&ID node numbers for the subsequent piping segment is derivedfrom those of the connected piping.

The P&ID node numbers are assigned as undefined when you connect to a nozzle,unless the active segment data is then updated from the P&ID Database.

If you place a component after specifying the active placement point with the Point inSpace option, the P&ID node numbers for the subsequent piping segment is assigned asundefined (blank).

If, in the Sketch command, you place a piping segment after specifying the activeplacement point with the Construct Point option, the P&ID node numbers for thesubsequent piping segment are assigned as undefined (blank).

204

6. P&

ID D

ata T

ransfer

Update Segment Data from P&ID________________

6.5 Update Segment Data from P&ID

You can update the active segment data by node number, by equipment/nozzle ID, or bysnapping to graphics in the active P&ID.

You can specify that the piping segment data transfer be complete or partial on the basis ofthe Correlation Table. The default mode is complete, and once the piping segment has beencreated in the model the active mode is restored to complete. In other words, the nextoperation will revert to complete data transfer, unless you explicitly select partial datatransfer.

A warning message is displayed if any one of the following conditions occurs in the processof loading the active data from the P&ID Database.

The piping materials class from the P&ID Database is undefined in the ReferenceDatabase

The nominal piping diameter from the P&ID Database is invalid for the pipingmaterials class from the P&ID Database on the basis of the NPD Table in the PipingSpecification Table Library

The active nominal piping diameter is invalid for the piping materials class from theP&ID Database on the basis of the NPD Table in the Piping Specification Table Libraryin partial data transfer, where nominal piping diameter is not loaded

The fluid code from the P&ID Database is invalid for the piping materials class fromthe P&ID Database on the basis of the Fluid Code Table in the Piping SpecificationTable Library for a piping materials class where a Fluid Code Table is applicable

205


6.5.1 Update by Node Number

You can update the active segment data by specifying two P&ID node numbers. This optionis provided in both the Place Component and Sketch commands. You can accept both oreither of the two active (previously specified) P&ID node numbers.

The P&ID Database is referenced using the P&ID project number. A single table is read fromthis database using unit number, P&ID node number ’A’, and P&ID node number ’B’. Sincethe P&ID Database is unit dependent and the Piping Design Database is design areadependent, one Piping design area may include data from different P&ID units, each unitbeing designated by a unique unit number.

The order of the P&ID node numbers, as specified by the user, determines the assignment offlow direction in the piping model. By convention, P&ID node number ’A’ is at the ActivePlacement Point. As a part of the data transfer process, the P&ID node numbers are stored inthe piping model for subsequent use and to retain the associativity between the segment in theP&ID Database and the segment(s) in the piping model. Likewise, the unique index into theP&ID segment table is stored in the piping model in order to enable the later comparison andupdate of P&ID node numbers from the P&ID Database into the piping model. It is possiblethat the P&ID node numbers may be changed by the P&ID propagation process for a specificsegment in the P&ID Database as a result of changes to the P&ID.

6.5.2 Transfer by Equipment Number and NozzleNumber

You can update the active segment data by specifying an equipment number and nozzlenumber. If you are actively connected to a nozzle in the model, this option automaticallysearches the P&ID Database using the ’active’ equipment number and nozzle number.Otherwise, you must either snap to the appropriate nozzle or key in the equipment number andnozzle number for the appropriate nozzle. This option is provided in both the PlaceComponent and Sketch commands.

The system accesses the P&ID Database using the P&ID project number. A single table isread from this database using the unit number, the equipment number, and the nozzle number.

The assignment of flow direction in the piping model is determined by the flow direction atthe nozzle end of the segment in the P&ID. As a part of the data transfer process, the P&IDnode numbers determined from reading the segment table in the P&ID Database are stored inthe piping model for subsequent use and to retain the associativity between the segment in theP&ID Database and the segment(s) in the piping model. Likewise, the unique index into theP&ID segment table is stored in the piping model in order to enable the later comparison andupdate of P&ID node numbers from the P&ID Database into the piping model. It is possiblethat the P&ID node numbers may be changed by the P&ID propagation process for a specificsegment in the P&ID Database as a result of changes to the P&ID.

206

6. P&

ID D

ata T

ransfer

Update by Node Number________________

6.5.3 Update From Active P&I Drawing

You can update the active segment data by snapping to graphics in the active P&ID. Thesystem reads a single table from the P&ID Database using the unit number and the attributelinkage from the segment in the P&ID.

If you identify a component in the P&ID that is associated with more than one segment, suchas a reducer, the active segment data is derived from the segment associated with the connectpoint nearest the identification point.

The order of the P&ID node numbers determines the assignment of flow direction in thepiping model. By convention, P&ID node number A is at the Active Placement Point. As apart of the data transfer process, the P&ID node numbers are stored in the piping model forsubsequent use and to retain the associativity between the segment in the P&ID Database andthe segment(s) in the piping model. The unique index into the P&ID Segment Table is alsostored in the piping model to enable the comparison and update of P&ID node numbers fromthe P&ID Database into the piping model. The P&ID node numbers may be changed by theP&ID propagation process for a specific segment in the P&ID Database as a result of changesto the P&I drawing.

207


6.6 P&ID Data

Revise Attributes

You can update the data for a previously placed piping segment using the Revise Attributescommand, by specifying two P&ID node numbers.

The order of the input of the two P&ID node numbers is used to control the assignment offlow direction in the piping model. P&ID node number ’A’ is associated with ’end 1’ of thesegment, while P&ID node number ’B’ will be associated with ’end 2’.

As with the previously described option, the piping segment data will be updated based uponthe Correlation Table. Likewise, the user has the option to specify that the piping segmentdata transfer is to be complete or partial on the basis of the Correlation Table. You can alsoupdate the data for a previously placed piping segment by snapping to graphics in the activeP&ID.

Attribute Break

You can load the piping segment data for an attribute break, using the Attribute Breakcommand, by specifying two P&ID node numbers.

The order of the input of the two P&ID node numbers is used to control the assignment offlow direction in the piping model. P&ID node number A is associated with the end of thepiping segment being placed at the attribute break’s location, while P&ID node number B isassociated with other end of the piping segment being placed.

Under user control, the revised piping segment will retain the existing piping segment data,including the P&ID node numbers. The new piping segment is created from the originalpiping segment with data being transferred from the P&ID Database using those P&ID nodenumbers specified by the user. This piping segment is created with the ’new’ P&ID nodenumbers.

As with the previously described option, the piping segment data is updated based upon theCorrelation Table. Likewise, the user has the option to specify that the piping segment datatransfer is to be complete or partial on the basis of the Correlation Table. You can also loadthe piping segment data for an attribute break by snapping to graphics in the active P&ID.

208

6. P&

ID D

ata T

ransfer

Name From P&ID________________

6.7 Name From P&ID

You can use the Name From P&ID option on the Place Component form to select the pipingor instrument component to be placed by identifying a component in the P&ID. It retrievesthe piping commodity name for a piping commodity, the piping component number for apiping specialty, or the instrument component number for an instrument for use in readingfrom the Reference Database. No other component data is read from the P&ID database.

209


6.8 P&ID Data Comparison Options

The P&ID Data Comparison Options command is provided as part of the Diagnosticscommand for the purpose of specifying the data comparison option for piping segments in themodel. You have two options with this command.

the ability to mark a piping segment to have segment data comparisons inhibited (orenabled) in the P&ID Data Comparison Report. This option is intended to assist theuser by not reporting extraneous piping segments which do not exist in the P&IDDatabase and have not been assigned P&ID node numbers in the piping model, i.e.segment data has not been transferred from the P&ID database. Note that the defaultmode for all piping segments created in the model is to have P&ID data comparisonsenabled. Thus it is not necessary for the user to take any action to enable P&ID datacomparisons, unless the user had previously and inadvertently designated that P&IDdata comparisons be inhibited for a particular piping segment.

a rules-based command for the purpose of automatically marking piping segmentscorresponding to vents, drains, and off-line instrument connections for being optionallyignored in P&ID data comparisons. The option is intended to assist the user by notreporting extraneous piping segments which may not exist in the P&ID Database andusually are not assigned P&ID node numbers in the piping model.

These piping segments representing vents, drains, and off-line instrument connections ismarked in the user data of the piping segment. Such designations will only have animpact, if the user chooses to have these piping segments excluded from the P&ID DataComparison Report.

The limit for the maximum number of vent/drain valves and instrument connectionsthat can be processed in one piping model is 200 for each (expanded from 100).

210

7. Interferen

ces

Detecting and Managing Interferences________________

7. Detecting and ManagingInterferences

This chapter provides information required to understand the terminology and philosophyinvolved with interference detection.

Interference Checker/Manager (PD_Clash) processes a specified design volume forinterference clashes. You can check for, review, and revise interferences at any stage of thedesign process.

The first section in this chapter is an overview of the interference management process; itbriefly covers the following topics:

Software setup

Interference envelope generation

Clash detection

Clash management and tracking

The second section is a review of project organization and the different units into which aplant/project can be broken for ease of manupulation.

The third section describes how to set up a system to support interference detection.

The fourth and final section is a general description of interference envelopes, the varioustypes of interferences (clashes) and what happens during interference detection andmanagement.

7.1 Interference Checking ProcessOverview

The following outlines the basic steps associated with interference detection and management.

Setup (outside the Interference Managermodule)

1. Define data with the Project Environment Manager.

Volume/Area definitions determine the extent of the project to process. Theextent may be physical by defining pre-defined volumes or logical by groupingmodels in a design area.

211

PDS 3D Theory — April 2002________________ To disable interference checking between certain disciplines, use the IntraDiscipline Interference Check toggle when defining the Discipline data.

2. Define interference data with the Project Data Manager.

The construction tolerance, the necessary space allocated beyond that which isnecessary for the component and its insulation, for each discipline is definedwith the Construction Tolerance form.

The action discipline is used to assign responsibility for a clash to a certaindiscipline. The action discipline is defined using the Select Action Disciplineoption on the Interference Check Data form.

The defined action discipline appears on plots and in the Action Discipline: fieldon the Interference Manager form in the Interference Checker/Managermodule.

Interference Envelopes:

3. The system accesses the model files to generate envelope files. The envelope files havea .env file extension. It is the envelope file and not the design file that is comparedduring interference detection.

4. The graphical volume for each component is defined by an interference envelopeparametric shape definition. This is an Eden module similar to the parametric shapemodule used to place the component in graphics.

Before performing interference detection on newly created or modified interferenceenvelope parametric shape definitions, use the Envelope Diagnostics option to generatea MicroStation-type graphic from the interference envelope. The graphics file is namedafter the envelope with a .til file extension.

5. Verify the consistency between the dates of envelope files and current design files usingthe Envelope Verification option. The results of the verification indicate whichenvelopes need to be updated.

Clash Detection:

6. Run the Interference Checker option to compare the envelope files for clashes withinthe specified area or volume.

7. A volume filter can be set for single runs of interference detection. Only the clashesfound within the specified volume are available for review after an interferencedetection run using this option.

8. For pre-defined volume design areas, the system checks all models within the pre-defined volume. This includes the portion of any model envelope file that encroacheswithin that volume regardless of its discipline.

212

7. Interferen

ces

Detecting and Managing Interferences________________

— OR —

For regular design areas, the system defines the volume as that which encompasses allmodel envelope files within the selected design area. This includes the portion of anymodel envelope file that encroaches within that volume regardless of its discipline ordesign area assignment.

9. For the specified area/volume, the system processes all of the portions of modelenvelopes or pairs of envelopes, for example:

Model A vs Model BModel A vs Model CModel A vs Model DModel B vs Model CModel B vs Model DModel C vs Model D

10. When a clash is detected, it is written to the database, and the graphics representing theclashing elements are written to the appropriate marker file. If you checked the entireproject, the clashes are written to the project marker file. If you checked a design area,the marker file is named after the design area with the extension which represents thediscipline:

Piping = 1Equipment = 2

Structural = 3HVAC = 4

Raceways = 5Architecture = 6

11. The Interference Report is created during the interference detection process and isnamed after the project or design area, depending on the option selected for interferencedetection, with a .int file extension. It contains only the unapproved clashes for thatrun.

Tracking and Managing:

12. Edit and review existing clashes, manipulate views, and approve exisiting clashes withthe Interference Manager option. This option displays and highlights clashes within agraphics environment, which can then be reviewed, edited or approved.

13. For unsuspected clashes, review envelopes in question using the Envelope Diagnosticscommand. This command generates a report with a .evd file extension. For example,this report contains instances such as when two or more groups of sub-components arecontained within one component but are not geometrically connected, in other words donot have overlapping ranges.

14. Clashes can be plotted any time after interference detection using the Interfence PlotManager option.

15. Aside from the Interferences Report, which is automatically generated duringinterference detection with the Interference Checker option, reporting on the ProjectControl Data is done using the Interference Report Manager. Discrimination data andformat files are used to generate specific types of reports. This sort of report might

213

PDS 3D Theory — April 2002________________ include a list of clashes involving the structural discipline, the approval status of thoseclashes, and the action discipline assigned to these clashes.

214

7. Interferen

ces

Project Organization________________

7.2 Project Organization

As discussed in Chapter 1, PDS uses the following organization to break the plant into smallerunits that can be handled more easily.

A project is a convenient grouping of all of the items that constitute a plant. The project is thefundamental structure for working in PDS. The project constitutes the entire volume of theproject.

A design area represents a specified volume or logical area of the project for a specificdiscipline. Design areas can be used to break up the project into smaller areas for interferencechecking or reporting. This speeds up processing when only a portion of the project haschanged. The models or model components that are not within the area/volume will not bechecked.

A design area pre-defined volume represents a pre-defined volume of the project for a specificdiscipline. The volume is defined by using the Project Environment Manager. Make surethat the pre-defined volume encompasses all the models that you want to be checked. Themodels or model components that are not within the volume will not be checked. The Pre-defined volume is used to encompass models and model components that might not have beengrouped together otherwise, or to define a design area that is smaller than usual.

A model is a 3D Microstation file that has a defined discipline and is located within thevolume of the project. A model represents a subdivision of the project based on workresponsibility, completion of schedules, and computer response time.

A volume filter can be used to decrease the volume of a project, area, or pre-defined volume tofurther decrease the processing time when only a sub-part requires checking or reporting.

215


7.2.1 Understanding Design Areas and Volumes

This section describes design areas and volumes and how they pertain to interferencechecking.

Running the Interference Checker for an entire project takes considerably longer than runningit for a design area. If the project workload is being shared, one of the design area optionswould be the most efficient. The design area options are less time consuming and createindividual sets of reports rather than one set of reports for the entire project. Adhere to usingeither the Project option or one of the Design Area options for the life of the project for themost consistent results.

Project

This option on the Interference Checker form performs clash checking for all of theenvelope files defined for the project and creates interference, difference, and batch queueerror reports. To specify a smaller volume for a single clash check, set the Volume Filtertoggle to On.

The dotted rectangle signifies the volume that is processed using the Project option.

Piping Design Area and Design Area

These options display a list of design areas for the specified discipline that are available forclash checking. After a design area has been selected, the system defines a volume thatencompasses all models within the selected design area. It then performs an interferencecheck on all models and parts of models, including models from all other disciplines, that arein the defined volume. To specify a smaller volume for a single interference check, set theVolume Filter toggle to On after selecting a design area.

216

7. Interferen

ces

Understanding Design Areas and Volumes________________ The dotted rectangle signifies the volume that is processed using the Design Area option.The name of the selected design area is DesA1.

Design Area and Piping Design Area Pre-defined Volume

These options display a list of design areas with pre-defined volumes available for clashchecking. After a design area has been selected, the system uses the pre-defined volume (asspecified through the Project Environment Manager). It then performs an interferencecheck on all models and parts of models, including models from all other disciplines, that arein the pre-defined volume.

The Interference Checker does not include models or parts of models that arein the selected design area that do not fall within the pre-defined volume.

The dotted rectangle signifies the volume that is processed using the Design Area Pre-defined Volume option. The name of the selected design area is DesAPreV1.

217


If you use Pre-defined Volumes as your method of checking, it is recommended thatyou run a project wide check at the end of the project to ensure that nothing wasmissed. However, you should not switch between Pre-defined Volume and Project ona consistent basis.

Volume Filter

This option creates a Volume Filter for one run of the Interference Checker. When set toVolume Filter On, you can define the low and high Easting, Northing, and Elevationcoordinates for one run of the Interference Checker in the following fields. When set toVolume Filter Off the system will use the default or pre-defined volume.

A volume filter can be used to decrease the volume of a project, area, or pre-defined volumeto further decrease the processing time when only a sub-part requires checking or reporting.The dotted rectangle signifies the volume that is processed when the Volume Filter has beenactivated and the volume to be checked has been specified.

218

7. Interferen

ces

Understanding Design Areas and Volumes________________

Single/Dual Ownership of Clashes

PD_Clash can be set up to allow single or dual ownership of clashes. This is very usefulwhen more than one design area needs to own, review, or approve a clash.

PD_Clash provides the capability for dual ownership–ownership available to each design areathat CONTAINS a component involved in a clash (when interference detection is run on thatarea) or single ownership–ownership assigned to the first design area to find the clash.

Dual ownership does not mean that ownership is automatically given to both design areaswhen a clash is found. It means that ownership is available to both design areas wheninterference detection is run on each.

Since clashes are stored in the database, reports can still be run on both designareas involved in a clash, even if interference detection has not been run onboth design areas. However, clashes are only written to the applicable designarea’s marker file during the interference detection process for each designarea. Therefore, clashes can only be reviewed and approved in design areas onwhich interference detection has been run.

This option does not define ownership assignments once clashes have been found. It acts afilter in the interference-detection process.

By default clash checking is done in Single (1) Design Area Ownership mode. In this mode,each clash belongs to the design area in which it was first found. When clash checking is donein this mode, clashes involving models that do not belong to the design area being checked arestill assigned to that design area.

219

PDS 3D Theory — April 2002________________ For instance, if design area C were checked for interferences in the Single (1) Design AreaOwnership mode, the system would compare all models that fall within the specified volumeincluding:

- all models against themselves- all design area A models against design area B models- all design area C models against design area A models- all design area C models against design area B models.

All of the clashes would belong to design area C.

In the Dual (2) Design Area Ownership mode, ownership is not based on the first designarea to find the clashes but on the design areas which own the components involved in a clash.

Interference checking is performed between models belonging to the design area beingchecked and all other models that fall within the volume of that design area. Clashes that donot involve at least one component from the design area being checked would not be found.

For instance, if design area C were checked for interferences in the Dual (2) Design AreaOwnership mode, the system would compare models in design area C with models fallingwithin the specified volume including:

- all design area C models against themselves- all design area C models against design area A models- all design area C models against design area B models.

The clashes found involving, for instance, design area C models against design area A modelswould be owned by design area C. Clashes could be reviewed and approved in design area Cand reports could be run on either design area C or design area A. You could not review orapprove clashes in design area A until you had run interference detection on it.

Clashes that do not involve at least one component from design area C models would not befound.

220

7. Interferen

ces

Setting Up a System to Support Interference Detection________________

7.3 Setting Up a System to SupportInterference Detection

The following project setup considerations are necessary to support interference checking.

1. Load software

All PDS servers and workstations must be loaded with the same release of PDS andnucleus software. The PDS software between servers and workstations must becompatible to run correctly. It is highly recommended that you read the Release Notesof the PD_CLASH README file when new releases are issued so that you will beinformed of any changes made to the product. The CAD Support person would mostlikely do this.

2. Set up plot queues.

The Interference Manager provides one default and four optional plot queues fordifferent types of plotters. The selection of the plot queue applies to all graphicinterference clash plots in a batch process. Multiple queues provide the flexibility insituations that arise which require different plotters for different paper types. This stepwould be completed by the CAD Support/System or Project Manager.

3. Define discipline responsibilities.

— The interference software uses area and model data to locate the models within aspecific design area for processing. This is done when the areas and model files arecreated. The location of the area marker file and model design file are stored by thesystem using data provided via the Project Environment Manager.

— Marker files are used by the software to place graphic markers for clashes that aredetected during interference checking.

4. Decide on Project or Area processing.

Interference checking can be done for the entire project or it can be divided into smallportions called design areas. The processing time for an entire project is much greaterthan for a design area. Also, it is often the case that only a certain design area or set ofdesign areas need to be checked.

Once you decide which method to use, either the Project option or thedesign area options, remain consistent. The more consistent you arewith your option selection, the more consistent the results will be. Forexample, you might select a design area option and receive the resultsfor one design area. You might correct a few of the interferences andthen run interference checking with the Project option. Remember, theinterference checker will only report new clashes, therefore, old clasheswould not be reported again although they may still exist in the designarea that was first checked. This step would be done by the InterferenceManager.

221


5. Define model graphics.

A set of model files for the project must be defined before you can use the InterferenceChecker/Manager.

222

7. Interferen

ces

Understanding Interference Envelopes________________

7.4 Understanding InterferenceEnvelopes

Envelope Builder

Piping, equipment, structural, raceway, and HVAC envelope files are created through the PDSInterference Manager module. All Architectural files will have their interference envelopefiles created within the Architecture product.

The envelope builder command performs the following tests to detect the situation where thegraphics for a model, that is not associated with the selected design area, encroaches into thevolume represented by that design area:

If the envelope file which corresponds to the model is Up-To-Date with respect to themodel, the envelope builder will not re-create the envelope file.

If the envelope file which corresponds to the model is Not-Up-To-Date with respect tothe model, but it has interference envelopes in the volume of the selected design area,then the envelope file for the model is re-created.

If the envelope file which corresponds to the model is Not-Up-To-Date with respect tothe model and it does not have any interference envelopes which fall within the volumeof the selected design area, then the envelope builder determines if the model has anycomponents which falls in the volume of the selected design area. If so, the envelopefile for that model is re-created.

Log files are batch queue error reports for the envelope builder data server that containinformation regarding any errors. These files have the extension .ebl and are created inthe \temp directory on the server or workstation from which the process was submitted.You should review this file.

Envelope Verification

The Envelope Verification command sorts the models being verified into one of thefollowing categories:

Up-To-Date: those interference envelopes that are consistent with respect to the model.

Not Up-To-Date: those interference envelopes that are inconsistent with respect to themodel and may require being re-created. This is because either the model has beenrevised since the interference envelopes were created, or the interference envelope fileis non-existent.

Not Mounted: an error occurred while mounting the file system where the modelresides.

223

PDS 3D Theory — April 2002________________ Any discrepancies found during this verification process indicate problems in the applicableEnvelope Builder and will be reported in a file in the \temp directory named after the projector design area with a .evd file extension.

Envelope Diagnostics

The Envelope Diagnostics command creates MicroStation graphics from the interferenceenvelopes for the model, in a file named <model name>.til. This file, placed in the samedirectory as the model, is used to view the interference envelopes interactively throughMicroStation to verify if the envelopes are correct.

7.4.1 Understanding Interference Checking

Once an interference philosophy has been determined, select the option to run the batchInterference Checker. Use your choice of either the Project option or any of the design areaoptions consistently throughout the interference checking process.

The Project option is the largest area of the project and encompasses every model file.

The Design Area options process a smaller division of a project with a limited numberof model files.

The Pre-Defined Volume option allows you to control the volume checked byspecifying specific volume coordinates. If not used, the system determines the volumebased on the volume of the envelope files in the area being checked (which can varyover the life of a project).

The Volume Filter toggle specifies a smaller volume of any of the options above.

Once the Interference Checker has been run, you can review the clashes interactively withthe Interference Manager.

The Piping Designer provides a command to check interferences interactivelywhile working in the piping design file. This option only checks one pipeline(or a group) against reference files that have a previously created envelope file.Unlike the Interference Checker, the Piping Design command does not writeclash information to the database. It is intended as a quick check for the pipingdesigner.

Interference Checker Input

The following are used as input by the PDS Interference Checker:

The data collected by the forms interface.

224

7. Interferen

ces

Understanding Interference Envelopes________________ Interference envelope files which correspond to model volumes or design areas.

Information in the Project Control Database. The approval status of each knowninterference is stored in the Project Control Database. When an interference isapproved, it is no longer be included in future interference reports. This allows allinterferences within a project to be resolved, either by changing the approval status ofthe interference to Approved or by revising the model.

Information in the Material Reference Database. The following database tables can beused to exclude items from interference checking.

— The Component Insulation Exclusion Data table (PDtable_231) allows you tocompletely or partially exclude the insulation of components that are on insulatedlines, during interference checking. If this table is not loaded, the insulationthickness is completely included in the component’s interference envelope.

— The Flange Insulation Exclusion Data table (PD_table 232) provides for partialexclusion of flange insulation thickness from the generation of interferenceenvelopes. This is an optional data table; if no data is defined for this table theinsulation thickness is completely included in the component’s interferenceenvelope.

Interference Checker Output

The following are generated by running the Interference Checker:

PDS Interference Report. This report contains all unapproved clashes, sorted first bymodel combinations then by the type of clash. For instance, all clashes detectedbetween model A and model B are grouped together. A synopsis of the clashes isincluded at the beginning of the report. This report also includes the model status ofany components involved in a clash for the piping, structural, HVAC, and equipmentdisciplines. This status is that of the model and not of the clash.

These reports are named after the project or design area with a .int file extension and arecreated each time the checker is run. The interference report is created at the locationspecified with the Interference Report Management Data option. The report beginswith a synopsis of all clashes found during interference processing and includes a reportof the clashing items within each of the design files represented in the synopsis.

PDS Interference Synopsis

mbpip2.env

Number of clashes = 14

PDS Interference Report

Date: 23-Jun-93 Time: 13:42:13

Model ’A’ Design File Name: mbpip2

Entire Design Volume Included In Report

225


PDS Interference Clashes

Hard/Hard Clashes

No Item Name Table Row X Coord Y Coord Z Coord

__ _________ _____ ___ _______ _______ _______

48 2CPINSTRUMENT 6 4194305 E 1’ 3 15/16" Plant N 2000’ 0" Plant El 0’ 0" Plant

meblabels-6IN-1C0031–0 "

Not approved

48 PIPE 5 4194306 E 40’ 2 3/16" Plant N 1999’ 10" Plant El 0’ 0" Plant

ifc’clash pipe’-1IN-1C0031–0 "

Not approved

49 3CPINSTRUMENT 6 4194306 E 8’ 4" Plant N 2000’ 0" Plant El 0’ 0" Plant


Not approved



Not approved

50 2CPSPECIALTY 3 4194306 E 13’ 4 1/8" Plant N 2000’ 0" Plant El 0’ 0" Plant


Not approved



Not approved

51 3CPSPECIALTY 3 4194307 E 18’ 4 1/4" Plant N 2000’ 0" Plant El 0’ 0" Plant


Not approved



Not approved

52 T 3 4194309 E 26’ 8 9/16" Plant N 2000’ 0" Plant El 0’ 0" Plant


Not approved



Not approved



Not approved



Not approved

54 pipesupport 8 4194305 E 31’ 2 3/16" Plant N 2000’ 6" Plant El -1’ 1 9/16" Plant


Not approved

54 PIPE 5 4194308 E 40’ 2 3/16" Plant N 1999’ 4" Plant El -6" Plant

ifcclash pipe-1IN-1C0031–0 "

Not approved



Not approved

55 CKS 3 4194321 E 22’ 6 1/16" Plant N 2000’ 0" Plant El 0’ 0" Plant

1construct-6IN-1C0031–0 "

Not approved

Interference Markers. All interferences within the project are graphically representedby markers and are used by the Interference Manager. Each time the InterferenceChecker detects an interference within the project, a marker is written to one of themarker design files. The project marker file is created in the project directory duringproject creation. It is named after the project database with a .dgn extension. Area

226

7. Interferen

ces

Understanding Interference Envelopes________________ marker files can be created as each piping or equipment design area is defined in theProject Control Database.

The interference markers are numbered in the .int report with a system-assignedsequential number starting with 1. Any previously approved markers (interferences)will not be replaced unless the corresponding model items have been graphicallymodified.

Error File. If an error is found while running the Interference Checker, the systemwrites the item name and an error code in a file named after either the project or designarea, depending on the option selected to run the Interference Checker, with a .icl fileextension. Runtime errors are written to a file with a .err extension.

Log files. Each batch job creates a log file which is placed in the \temp directory. Anyrun time errors will be listed in these log files.

Project Control Database Records. The following tables are updated by InterferenceChecking:

— Clash Management Data (131). A record is created each time InterferenceChecking is run.

— Interference Clash Data Per Project (132). A record is created for each clash inthe project. The unique_clash_id uniquely identifies a clash.

— Interference Clash Data Per Job (133). A record is created each time a clash isencountered.

— Component Clash Data Per Project (134). A record is created for each modelitem which is involved in one or more clashes.

These records are used by subsequent executions of the Interference Checker andInterference Manager.

Clash Plots. These files are named by the system as the marker number with theextension .plt and placed in the \temp directory (or you may use the Interference ClashPlot Manager to specify a different node and directory). The system automaticallygenerates the plots through the PDifc_plot queue.

Interference Manager

The interference manager is used to review all interferences in a project or area and revise theapproval status of a single interference marker or a group of interference markers.

227


Clash Categories

The Interference Manager and the reports created by the Interference Checker distinguishbetween three categories of interference clashes. See the graphics on the following page forexamples of clashes.

Hard. A clash which exists between actual physical components, equipment, orstructures.

Soft. A clash which exists between non-physical space envelopes, such as, insulation,maintenance accessways, or safety envelopes.

Construction. A clash or discrepancy which exists between the user-defined distanceand the actual distance of two components in specified disciplines defined usingPD_Project. For instance, if piping components are required to be at least 1" away fromall structural components but one is found closer, a Construction clash is reported.

Clash Precedence

The precedence for reporting clashes is Hard, Soft, and Construction. This results in theinterference clash being reported in one of the following categories. The report will containonly the category of clashes with the highest precedence in accordance with the followingprecedence table:

Hard - HardHard - SoftHard - ConstructionSoft - SoftSoft - ConstructionConstruction - Construction.

228

7. Interferen

ces

Understanding Interference Envelopes________________

Hard - Hard Example

The following example contains clashes between actual physical components. It would becategorized as a Hard - Hard clash.

Hard - Soft Example

The following example displays a clash between an actual component and space that has beenallocated for maintenance accessways. It would be categorized as a Hard - Soft clash.

229


7.4.2 Understanding Interference Plotting

The Interference Plot Manager option plots clashes generally by project or design area.Within these choices, you can plot clashes by:

The clash plot status.

The clash approval status.

The clash review status.

The clash category.

The group or individual clash selections from a list of clashes in marker file.

The Interference Clash Plot Management option defines a default node and path for futureclash plot files.

This is a required step in the Interference Checking Process. Problems could occurlater in the process if this step has not been completed.

7.4.3 Understanding Interference Reporting

The interferences report is generated automatically during interference detection with theInterference Checker option. You can create user-defined reports on the Project ControlData using the Interference Report Manager. Discrimination data and format files are usedto generate specific types of reports, such as a list of clashes involving the structuraldiscipline, the approval status of those clashes, and the action discipline assigned to theseclashes.

The interface and process for interfence reporting is similar to that used in the PDS ReportManager module.

230

8. Rep

ortin

g

Creating Material Takeoffs and Other Reports________________

8. Creating Material Takeoffs andOther Reports

8.1 Reporting Process

The following outlines the basic steps associated with the Material Take-Off process.

1. Pre-defined report data determines the discrimination data (such as which models toprocess) and the format (content and layout) of the report.

2. For the specified models (and using any additional discrimination data, such as linesize), the system scans the physical elements in the model.

3. The system determines the number of items present in the model by unique commoditycode. In addition to the physical elements, it determines any implied items based onconfiguration of mating components or designations in the Piping CommoditySpecification Data (PCD).

4. The system looks up the material descriptions for the located components and implieditems in the Material Description Library.

5. The system writes a report of the located and calculated items based on pre-definedreport format.

There are two main user tasks necessary for creating reports:

Maintaining the data that defines the format, content and approval status of the reports.

Processing reports by activating the interface to extract data from all of the PDSmodels, databases, and libraries that are involved in a project.

8.2 Maintaining Report Definition Data

The Report Manager uses both report definition files, such as discrimination data files andformat files, along with database records that represent these files to generate reports.

The two most important files that must be maintained in a report creation process are thediscrimination data file and the format file. The discrimination data file, which defines thesearch criteria for a report, is maintained interactively with the Report Manager. The formatfile is generated outside of the interface using an ASCII text editor. There are several sampleformat files that are delivered with the PDS 3D products. You can use these files as examplesfor creating format files to meet your specific needs.

231


8.2.1 Understanding Report Files and Records

The following definitions explain all of the files and records in the reporting process.

8.2.1.1 Format File

The format file is a user-defined, ASCII-text file which contains special indices identifyingwhat data appears in the report, how the data is sorted, and how the data is formatted in thereport. A set of basic format files are delivered for several types of reports. Using the ReportFormat option, you can create a database record for each format file so that it can be accessedfor report processing. Without the format record, the Report Manager is unable to accessformat files.

Format Record

The format record is a record in the Project Control Database used to name and locate aspecific format file. It is called a record to classify it as a block of data that is used for reportprocessing but, it is not an actual file. It is created interactively. There are five formatdefinitions in the format record:

Number — Defines a unique number to name the record with up to 24 characters in theProject Control Database. This number is a short name to identify the record of theformat file.

Description — Describes the format file with up to 40 characters in the Project ControlDatabase.

File Specification — Defines the file name of the ASCII format file. The systemverifies that the file does not already have a record in the project.

Path — Defines the disk location of the format file. This field retains the active setting.

Node — Defines the nodename where the format file is located. This field retains theactive setting.

8.2.1.2 Discrimination Data File

The discrimination data file defines the search criteria which is used to limit the report to onlythe specified database occurrences. It is an ASCII file that is created interactively using theReport Manager. You also create a uniquely-numbered record for each discrimination datafile so that it can be accessed for report processing.

232

8. Rep

ortin

g

Creating Material Takeoffs and Other Reports________________

Discrimination Data Record

The discrimination data record is a record in the Project Control Database used to name andlocate a specific discrimination data file. It is called a record to classify it as a block of datathat is used for report processing but is not an actual file. It is created using the ReportManager. There are five discrimination data definitions in the discrimination data record:

Number — Defines a unique number to name the record with up to 24 characters in theProject Control Database. This number is a short name to identify the record of thediscrimination data file.

Description — Describes the discrimination data file with up to 40 characters in theProject Control Database.

File Specification — Defines the file name of the discrimination data file to reference.

The system verifies that the file does not already have a record in the project.

Path — Defines the disk location of the discrimination data file. This field retains theactive setting.

Node — Defines the nodename where the discrimination data file is located. This fieldretains the active setting.

8.2.1.3 Report Record

The report record defines locations for all of the files that are necessary to generate a report,including the report output. (It is called a record to classify it as a block of data that is usedfor report processing but is not an actual file.) It is created using the Report Manager. Thereare seven report definitions in the report record:

Report Number — Creates a unique report number in the Project Control Databasethat acts as a name or identifier for a report record.

Report Title — Describes the report file. It is not the title in the actual report. Thattitle is specified in the format file.

Report File Spec — Defines the file name of the report output file. Each time a file isre-generated using the same report file, the report output file is overwritten. Changethis field to save the old report output file and generate a new one.

Report File Path — Defines the directory for the report output file.

Report Node — Specifies the nodename for the report output file.

Report Format File — Specifies the record number that contains the address of thereport format file to be used.

233

PDS 3D Theory — April 2002________________ Report Discrimination Data — Specifies the record number that contains the addressof the discrimination data to be used.

8.2.1.4 Report Output

The Report Manager creates a report using the specified format and discrimination data filesand places it in the directory specified.

234

8. Rep

ortin

g

Processing Reports________________

8.3 Processing Reports

Since there are reporting capabilities in various PDS modules, the format file, thediscrimination data file and the module where the report process is activated determine whattype of report is created.

For instance, you can create MTO reports with Report Manager and Drawing reports withthe report manager module of Drawing Manager. Depending on the definition data used andthe module that executes the process, you can create MTO reports, drawing reports, specreports, table checker reports, project reports, or interference reports.

The following section describes the various report types, how they are generated, and theircorresponding sample format files:

8.4 Report Types

Various modules in the PDS Suite generate reports. The following section describes thevarious report types, how they are generated, and their corresponding sample format files:

MTO Report (with implied materials) — Generates reports on PDS piping andequipment models involving data from the Design Database, Reference Database,Project Database, and Material Description Libraries. This type of report will alsoinclude implied mating data, such as bolts, gaskets, and welds by determining theconnectivity of the piping and equipment. Format files used in this type of reportprimarily use A and B prefixed indices. This report is generated using the ReportManager.

Drawing Report — Generates reports on PDS Piping and Equipment drawing viewsand drawing files. This report is the same type of report as the MTO report generatedby the Report Manager. Format files used in this type of report primarily use A and Bprefixed indices. This report is generated using the Drawing Manager.

Spec Report — Generates reports on the Reference Database and Material DescriptionLibraries. The spec report is used to report on data in the reference database. Formatfiles used to create this type of report primarily use C prefixed indices. This report isgenerated by the Reference Data Manager.

Table Checker Report — Generates reports on the Reference Database and MaterialDescription Libraries. The table checker report is used to test Eden modules and tablesthat would be executed by the Piping Commodity items within the Reference Database.Format files used to create this type of report primarily use C prefixed indices. Thisreport is generated by the Reference Data Manager.

Project Report — Generates reports on the Project Control Database. Format files usedin this type of report primarily use D prefixed indices. This report is generated using theProject Administrator.

235

PDS 3D Theory — April 2002________________ Interference Report — Generates reports on the project control database. clash area,clash type, and clash approval along with the search criteria specified in thediscrimination data define what interference data is reported. Format files used in thistype of report primarily use D prefixed indices. This report is generated using theInterference Manager/Checker.

236

8. Rep

ortin

g

Report Format File________________

8.5 Report Format File

The reporting process is driven by a format file that determines the contents and format of thereport. It must be created with a text editor prior to report processing.

The format file is a standard ASCII file which contains all the needed criteria for creating theactual report, such as text position, special indices for input into the report, and sortinginstructions for the indices.

8.5.1 Format File Syntax

The format file is based on fields. A field contains a complete description of a given piece ofdata to be placed in an ASCII report file.

Each line of the format file contains the entire description of one field. All fields areindependent of each other; if they have a common order in the report, you are responsible forplacing these fields in such a way that the orders match in the report. In other words, you areresponsible for defining your format file in such a way that your columns and headings willfall under one another.

Each line in the format file can contain the following data:

Field_Function,Row,Col,Field_Len,Data_Type,Field_Type,[Buffer],[Rows/Page],[Spacing]

(Brackets [ ] indicate data that is only used for certain field types; all other data is required inevery field type.)

Syntax Example

237


8.5.2 Definitions

Field_Function

0 Null Field — Used to send a data field (index) to sort on an unreported item.

1 Page Field - All Pages — Places the specified field once on every page of the report.

2 Page Field - First Page Only — Places the specified field once on the first page of thereport.

3 Page Field - Last Page Only — Places the specified field once on the last page of thereport.

4 Output Field — Places the specified field a variable number of times on every pageof the report based on rows/page and spacing.

5 New Page Marker — Forces a new page (form feed) after all the previous statementshave been processed. All the lines in the format file after this marker are placed on anew (repeated) page. In other words, this enables you to append a complete format fileto the previous format file and use the same data sources and sorting as the previouslines of the format file.

6 Continuous Page Marker — Forces everything after this marker in the format file upto a New Page Marker or the end of file to be continuously output as one page. Thespecified fields are continuously output without any page divisions. (This codeoverrides the value for Rows/Page)

This function can be used to generate an intermediate data file in a fixed form thatcontains only raw data (without headings and other annotation). This output can thenbe used as input to your own report generation software.

7 Turn On Output Field Appending Control — Forces all output fields after this markerin the format file to begin after the previous output field (above 7) is completed, that is,all output fields will initially begin at the last output fields finishing row.

8 Turn Off Output Field Appending Control — If 7 is in effect for an output field thiscode will turn the effect off making output fields normal.

9 Start of output field loop

10 End of output field loop — Repeats all output fields defined between codes 9 and10 until out of data or the maximum number of lines per output field has been exceededby the number of lines of data between the 9 and 10 codes. These options are used toprevent control sorts from breaking to a new page by using the remaining space on thepage before proceeding to a new page.

238

8. Rep

ortin

g


Row

Starting line number to be used in placing the field in the report. The maximum number ofrows in a report is 66.

Col

Starting column number to be used in placing the field within the specified row. Themaximum number of columns in a report is 132.

Field_Len

The maximum number of characters that a field can occupy for the active row. The startingcolumn plus the field length must not exceed 132. A negative value will truncate a fieldrather than wrap around a field (default). If the text being placed in the field exceeds the fieldlength, the text is continued on the next row indented one space (col + 1) until it is completedor the page ends.

Data_Type

Code used to determine the type of translation required to convert the data to text. (Refer tothe index listings to determine the applicable data type for a particular attribute.)

1 character or ’[Am]’, where m is the number of characters

2 single precision integer or ’[Im]’

3 double precision integer or ’[Im]’

where m is the number of characters for the integer field

4 single precision decimal (float) or ’[Fm.n]’

5 double precision decimal (float) or ’[Fm.n]’

where m is the total number of characters for the decimal value including the decimalpoint and n is the number of decimal places

Optional text can precede and/or follow the formatted data type within the quotation marks.

’optional text [Format] optional text’

[Format] can be any legal FORTRAN format statement that matches an expected output.

239


Field_Type

1 Text Field. Sets the buffer for hard-coded text.

2 Data Field. Sets the buffer for an index number or code used to generate the data tobe placed in the field.

3 Generate Date/Time. No buffer required. When the report is generated, the systemdate and time is placed at the designated row/col position.

4 Generate Page Number. No buffer required. When the report is generated, thesystem calculates the page number and places the number at the designated row/colposition.

5 Generate Date. No buffer required. When the report is generated, the system date isplaced at the designated row/col position.

A negative value will underline the generated output for the field. (This causes the report tobe in a stream line feed file, rather than a stream carriage return file. This may impact anexisting interface to a material control system.)

[Buffer] = Field Definition

The form of the buffer depends on the value for Field_Type.

Hard coded text is enclosed in single quotes (’).

For MTO reporting, the first character of the index is always A or B. Refer to thedescription of the indices for MTO Reporting (with implied materials).

For spec reporting, the first character of the index is always C. Refer to the descriptionof the indices for Spec Reporting. These indices are also used for the Table Checker.

For project and interference reporting, the first character of the index is always D.Refer to the description of the indices for Project and Interference Reporting.

[Rows/Page]

This setting is only required for output fields. It indicates the number of vertical spaces(lines) in which to repeat the field contents on a given page. For example, a setting of 20reserves 20 lines starting from a given row for use in placing the field contents (dependent onspacing).

This does not take into account the extended fields due to exceeded field length.

This is NOT the total number of times that the field is repeated (that value is based on numberof occurrences for the specified attribute); it is only the vertical space allotted for repeating thefield on a page.

240

8. Rep

ortin

g


[Spacing]

This setting is only required for output fields. It indicates how much space (in rows) isallowable between repeated fields. This is useful for reserving space for extended fields dueto exceeded field length.

(Rows/Page)/Spacing = the number of times an output field can appear on a page. Forexample, if Rows/Page=40 and Spacing = 2, 20 occurrences of the specified attribute areplaced on a page (until the number of occurrences is reached).

Optional Report Type Line

There is an optional line that will determine the type of report the format record creates. Itmust be the first line of the format file when used. This line contains an integer variable thatcorresponds to a name in the standard note type 1720 in the Standard Note Library. You canmodify the standard note type 1720 to add report types. For instance, the following linewould define the report type as Piping Components MTO Report:

report_type=689

8.5.3 Output Fields

Most report formats involve reporting multiple variables for a given component. This isaccomplished by using output fields (Field_Type = 2) with the necessary index numbers.

Each field is processed independently of the other fields on the report; there are no safeguardsto assure that information in different fields corresponds to the same item. Therefore, you areresponsible for placing these fields in such a way that the orders match in the report. Toensure that items match, you should make sure that the same number of common items arereported on each page. The Rows/Page divided by the Spacing determines the number oftimes an output field can appear on a page. Therefore, all the common fields should useidentical settings for Rows/Page and Spacing.

The Spacing enables you to reserve space for extended fields due to exceeded field length.For example, if you use a Field length of 20 for a field which may be up to 50 characters long,you should set the spacing at 3 to leave adequate space for any extended fields.

If there is no data for the specified output field(s) on a page, that page will notbe printed.

241


8.5.4 Sample Format Files

Different format files are used by the system to generated specific types of reports. Thefollowing sections explain all of the delivered sample format files, their delivery locations,and what type of report the generate. In some instances, report output is also included.

Sample MTO Report Format Files

The following files are provided in the product delivery in win32app\ingr\pdreport\sampledirectory.

segment.fmt — This report format includes piping segment data. It demonstrates’control’ sorting and output field ’looping’ (field functions 9 and 10).

This report format reports a list of piping segments grouped by the Model Builder’salphanumeric description id. The report includes all piping lines that are associatedwith a specific Model Builder alphanumeric input file.

(report type = 687)

piping_a.fmt — This report format includes data for piping components, pipes,instrument components, gaskets, bolts, nuts, and welds. It demonstrates the use of’standard’ output fields.

This report includes each category of data in a fixed area of a repeated report page using’normal sorting’ and ’standard output fields’ (field function 4).

(report type = 689)

piping_b.fmt — This report format includes data for piping components, pipes,instrument components, gaskets, bolts, nuts, and welds. It demonstrates the techniquefor grouping blocks of output fields on the same page of the report.

This report format reports data similar to ’piping_a.fmt’. It differs only in that itdemonstrates another method to format the data on the repeated page of the report.

(report type = 689)

piping_c.fmt — This report format includes data for piping components, pipes,instrument components, gaskets, bolts, nuts, welds, pipe supports, implied pipingcomponents, equipment, and nozzles. It demonstrates the use of different pages ofoutput within one report.

This report format reports data similar to ’piping_b.fmt’ with the addition ofpipe_supports, implied piping components, equipment, and nozzles. It uses ’page breakmarkers’ (field function 5) to break each category of data onto a different repeated pageof the report.

242

8. Rep

ortin

g

Sample Format Files________________ (report type = 689)

piping_d.fmt — This report format reports the material descriptions for pipingcomponents, pipes, instrument components, pipe supports, gaskets, and bolts.

This report format uses identical report indices to create two columns to continue dataon the same report page. It also uses page breaks to separate the different categories ofdata onto different repeated pages of the report.

(report type = 689)

piping_e.fmt — This report format reports data similar to ’piping_c.fmt’, but withoutany equipment and nozzle data.

This report format uses a ’continuous page marker’ (field function 6) to create a reportwith no page boundaries and continuous output (typically used for creating a neutral fileformat). It also demonstrates the use of report indices to create a summary of standardnotes used in the report.

report type = 689)

piping_f.fmt — This report format includes data for piping components, pipes,instrument components, gaskets, bolts, and pipe supports similar to ’piping_e.fmt’.

Each category of data is grouped (using ’global control sorting’) under a common linenumber label for each page of output. It uses ’output field appending’ (field functions 7and 8) to have the different categories of data reported on the same page and column ofoutput.

(report type = 689)

piping_g.fmt — This report format includes data for piping components, pipes,instrument components, gaskets, bolts, and pipe supports similar to ’piping_f.fmt’ withthe same line number grouping.

This report format uses ’output field looping’ (field functions 9 and 10) to utilize all ofthe report page space available. The report includes a line number followed by allcomponents that are associated with that line number label with one or more linenumber labels being reported per page, depending upon the amount of data and thespace available.

(report type = 689)

weight.fmt — This report format includes weight and center of gravity data for pipingcomponents, pipes, instrument components, gaskets, bolts, pipe supports, impliedpiping components, and equipment.

The output is similar in format to ’piping_e.fmt’ and demonstrates the weight and cogcalculation reporting indices.

243

PDS 3D Theory — April 2002________________ (report type = 689)

equip_a.fmt — This report format reports equipment data (including location data) andnozzle data (including location and orientation data). It demonstrates the full range ofequipment and nozzle reporting indices.

(report type = 661)

weldno.fmt — This format reports weld information, such as the weld number, typeand the first and second connect point NPD.

project_a.fmt — This format reports project information such as the client and projectlocation and uses information from the Drawing Management Data table and theDrawing Revision Data table for reporting.

Sample Spec Report Format Files

The following files are provided in the product delivered in thewin32app\pddata\sample\format directory.

piping_rdb.fmt — This report format includes piping material class data and pipingcommodity data from the Material Reference Database. It reports the ’partial’ (withoutembedded commodity code labels) material descriptions.

(report type = 601)

tbl_chk_1.fmt — This report format includes Table Checker data for one pipingmaterial class. It reports the piping commodities with the dimension tables and PipingEden modules used, including a list of all entries read in the dimension tables.

This report also includes a list of all dimension tables and Piping Eden modules thatwere required for those piping commodities, but not available in the ReferenceDatabase. This report format is a combination of the following report formatstbl_chk_2.fmt, tblk_chk_3.fmt, and tbl_chk_4.fmt. It provides full Table Checkeroutput for a specific piping materials class.

(report type = 601)

tbl_chk_2.fmt — This report format includes Table Checker data for one pipingmaterial class. It reports the dimension tables and Piping Eden modules used by eachpiping commodity in that piping materials class.

(report type = 601)

tbl_chk_3.fmt — This report format includes Table Checker data for one pipingmaterial class. It lists all entries read in dimension tables.

(report type = 601)

244

8. Rep

ortin

g

Sample Format Files________________ tbl_chk_4.fmt — This report format includes Table Checker data for one pipingmaterial class. It includes a list of all dimension tables and Piping Eden modules usedby the piping commodities in that piping materials class.

This report also includes a list of all dimension tables and Piping Eden modules thatwere required for those piping commodities, but not available in the ReferenceDatabase.

(report type = 601)

Sample Project Control Report Format Files

The following examples are delivered in the win32app\pdprojec\sample directory.

model_mgt.fmt — This format file reports model management data.

draw_mgt.fmt — This format file reports orthographic drawing management data.

iso_mgt.fmt — This format file reports isometric drawing management data.

iso_rev.fmt — This format file reports isometric drawing revision management data.

Sample Interference Report Format File

The following example is delivered in the win32app\pdclash\sample directory.

clash_mgt.fmt — This format file reports interference checker data.

Sample P&ID Consistency Check ReportFormat File

The following example is delivered in the win32app\pddesign\sample directory.

pid_cmprpt.fmt — This format file specifies the format of the title page and headingfor each page of the P&ID Consistency Check reports. The remainder of the report ispredefined by the product.

245


8.6 What Happens When I Report On aComponent?

When you place a component the system writes the engineering data for the component to thedesign database. For the gate valve placed in Chapter 4, the system writes information to thePiping Segment Data table and the Piping Component Data table. When you create a MaterialTake-Off (MTO) report using the Report Manager the system will use this data andinformation in the project reference data for reporting.

In addition to the engineering data in the design database, PDS3D uses the Material Description Library and the material datain the Material Reference Database to provide materialdescriptions for commodity items and specialty items.

Material Descriptions

The material description data is made up of four major parts:

1. Material Tables in the Material Reference Database - These database tables (211and 212) contain commodity definitions which enable you to further classify thecommodity items defined in the Piping Job Specification. This database informationtends to be customer-specific.

Piping Commodity Size-Dependent Material Data (211)

The Size-Dependent Data table contains the data for a specific commodity itemthat is dependent on the commodity code, nominal piping diameter, andschedule/thickness. It is used for miscellaneous reporting and interfaces tomaterial control, stress analysis, and isometric drawing extraction.

246

8. Rep

ortin

g

What Happens When I Report On a Component?________________ Piping Commodity Implied Material Data (212)

The Implied Material Data table contains the implied material data for a specificcommodity item that is dependent on both the commodity code and nominalpiping diameter range. This data is used for generating implied materials forMTO reporting and material control. It is not used for welds, bolts, nuts, orgaskets, but is reserved for other types of implied material, such as caps or stubs,for a specific commodity item. It is also used for reporting the impliedcomponents of a commodity item (such as cap screws).

2. Short Material Description Library - This library contains the short bill-of-material(BOM) descriptions for all piping commodity items and the description addenda fortaps. The short material descriptions can be up to 240 characters in length.

3. Long Material Description Library - This library contains the long bill-of-materialdescriptions for all piping commodity items. The long material descriptions can be upto 500 characters in length.

4. Specialty Material Description Library - This Library contains the materialdescriptions for any piping specialties, in-line instruments, or pipe supports which arereported by MTO or material control. These material descriptions are job specific andare accessed by the specialty item’s tag number. The specialty material descriptionscan be up to 240 characters in length.

The material description data in these files is used for reporting and material control and is notrequired for the interactive placement of symbols in the model. This data is normallyaccessed during a batch (non-interactive) process.

Commodity Codes

The system uses the commodity code as an index to access the descriptions in the materialdescription libraries. You can use the commodity code defined in the Piping CommoditySpecification Data table (Table 202 attribute 18) or a user-defined commodity code defined inthe Size-Dependent Material Data table (Table 211 attribute 7).

247


The source of the commodity code and other processing options for reporting are defined for amodel with the Material Takeoff Options form of the Project Data Manager.

The commodity code represents that set of parameters that completely describe a commodityitem, exclusive of nominal piping diameter and thickness. The character length for thecommodity code is determined from the character length of the commodity code in the SizeDependent Data table of the database, or from the character length of the commodity code inthe Piping Commodity Data table of the database, depending on which is being used to accessthe material descriptions.

The delivered commodity codes use a 10 character code to fully identify the item. The firstletter of the commodity code identifies the basic type of component, such as a valve or flange.The remaining characters provide a detailed description of the component. The first characterdesignations are:

248

8. Rep

ortin

g

What Happens When I Report On a Component?________________

B Flanged and Misc. Fittings Q Socket End FittingsD Fire and Safety Components R Tubing FittingsE Steam Specialties S Socketwelded FittingsF Flanges T Threaded FittingsG Flanged Specialties U Underground FittingsH Strainers V ValvesM Misc. Wetted Components W Welded FittingsN Misc. Non-Wetted Components X GasketsO Tubing and Hose Y BoltingP Pipe

Examples

1 2 3 4 5 6 7 8 9 0_____________________________

P A D A A B C A A E

P - PipeAD - Pipe, Plain EndsAA - SeamlessBC - X-Strong (s-xs)AAE - ASTM A106 Gr. B

V A A B A H C C A A

V - ValveA - Gate ValveA - CL150B - Raised Face Flanged EndsA - Carbon SteelH - Trim 8CC - Crane 47AA - Blank

Refer to the PDS Piping Component Data Reference Guide for a complete listing of thedelivered commodity codes.

You can use the delivered commodity codes or create your own naming scheme. Regardlessof the scheme used, all the codes must be unique and there must be an exact match betweenthe commodity code specified for an item in the Material Reference Database and commoditycodes used to define the material descriptions in the Material Description Library.

Implied Data

When the system creates a bill of materials for the elements in a model it lists both the itemsphysically defined in the model and any implied items which are associated with the physicalitems. Implied materials can be defined in any of the following ways.

249

PDS 3D Theory — April 2002________________ Mating Implied Data (gaskets, bolts, and welds)

During reporting, the system scans the components and their relationship to determineany mating implied material. The system uses a set of rules to determine the impliedmaterials based on the end conditions of mating components. These rules are describedin detail in the Report Manager (PD_Report) Reference Guide.

Item definitions for mating implication such as bolts and gaskets are defined in thePiping Commodity Specification Data Table (pdtable_202) of theSpecification/Material Reference Database.

Spec Implied Data

An asterix (*) in front of a commodity code in the Piping Commodity SpecificationData (PCD) indicates that there is another line item in the PCD for the impliedcomponent. For example, a lap joint flange and stub end. The lap joint flange is placedin the model but the stub end is not. However, the stub end will show up in reports.

This is a Parent/Child relationship with a one-to-one relation.

Parent = option numberChild = 5000 + parent option number

Table 212 Implied Data

A plus (+) in front of a commodity code in the PCD tells the software to look in table212 for that commodity code. This method indicates a primary component which hasone or more associated implied components.

This is a Parent/Child relationship with a one-to-many relation.

Commodity codes with neither an * or a + prefix in the PCD, indicate a commodityitem that has no associated implied components.

Report Output

The following is a sample report using the format file piping_a.fmt. It reports on a verysimple pipeline containing the component examples covered in Chapter 4 and the connectingpipes.

250

8. Rep

ortin

g

What Happens When I Report On a Component?________________

251


8.7 Material Takeoff Reporting (ReportManager)

Material Takeoff reporting (with implied materials) generates reports on PDS piping andequipment models involving data from the Design Database, Reference Database, ProjectDatabase, and Material Description Libraries. This type of report also includes impliedmating data, such as bolts, gaskets, and welds by determining the connectivity of the pipingand equipment. Format files used in this type of report primarily use A and B prefixedindices. This report is generated using Report Manager.

The active Piping Materials Class must be defined for a model for MTOprocessing to work. Before creating an MTO report for a model or set ofmodels, the Piping Materials Class should be set in the active segment data foreach model and the setting should be saved with File Design.

The sample format files for creating MTO reports are: segment.fmt, piping_a.fmt throughpiping_g.fmt, weight.fmt, equip_a.fmt, and weldno.fmt and are delivered in thewin32app\pdreport\sample directory.

Sample MTO Format (piping_g.fmt)

report_type=689 ! Piping Components MTO Report

1,1,1,-13,1,1,’Date/Time :’

1,1,14,-23,1,5

1,1,50,-40,1,1,’PDS MTO REPORT’

1,1,120,-6,1,1,’Page: ’

1,1,127,-3,2,4

2,3,10,-40,1,1,’Corporate Headquarters’

2,4,10,-40,1,1,’Intergraph Corporation’

2,5,10,-40,1,1,’Huntsville, Alabama 35894-0001’

2,6,10,-40,1,1,’(205)730-2000’

2,3,90,-20,1,2,B**Q5

2,3,110,-20,1,2,B**Q9

2,4,90,-20,1,2,B**Q6

2,5,90,-20,1,2,B**Q7

2,6,90,-20,1,2,B**Q8

1,8,1,-25,1,-1,’Commodity Code’

1,8,27,-16,1,-1,’Qty/Length’

1,8,45,-10,1,-1,’1st Size’

1,8,57,-10,1,-1,’2nd Size’

1,8,69,-63,1,-1,’Material Description’

9

4,10,55,-50,’LINE NUMBER: [A30]’,-2,BI2G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,BB2G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,BT1G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,BX1G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,B**K2G1,45,2

7

4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*S2G1,45,2

8

4,12,1,-25,1,2,BG8S2,45,2

4,12,27,-16,2,2,BS,45,2

4,12,45,-10,1,2,BN49S3,45,2

252

8. Rep

ortin

g

Material Takeoff Reporting (Report Manager)________________

4,12,57,-10,1,2,BN-49S4,45,2

4,12,69,63,1,2,BM1S5,45,2

7

4,12,1,-25,1,2,BA12S2,45,2

4,12,27,-16,1,2,BA22,45,2

4,12,45,-10,1,2,BA7S3,45,2

4,12,69,63,1,2,BF1S4,45,2

7

4,12,1,-25,1,2,B*G2S2,45,2

4,12,27,-16,2,2,B*O,45,2

4,12,45,-10,1,2,B*L55S3,45,2

4,12,57,-10,1,2,B*L-55S4,45,2

4,12,69,63,1,2,B*K1S5,45,2

7

4,12,1,-25,1,2,BT13S2,45,2

4,12,27,-16,2,2,BV,45,2

4,12,45,-10,1,2,BT2S3,45,2

4,12,57,-10,1,2,BT23,45,2

4,12,69,63,1,2,BT21S4,45,2

7

4,12,1,-25,1,2,BX12S2,45,2

4,12,27,-16,2,2,BZ,45,2

4,12,45,-10,1,2,BX4S3,45,2

4,12,57,-10,1,2,BX5S4,45,2

4,12,69,63,1,2,BX20S5,45,2

7

4,12,1,-25,1,2,B**J7S2,45,2

4,12,27,-16,1,2,B**O,45,2

4,12,69,63,1,2,B**M1S3,45,2

7

4,12,1,-25,1,2,B*P12S2,45,2

4,12,27,-16,2,2,B*R,45,2

4,12,45,-10,1,2,B*S11S3,45,2

4,12,69,63,1,2,B*U1S4,45,2

10

5

1,3,1,-13,1,1,’Date/Time :’

1,3,14,-23,1,5

1,3,50,-40,1,1,’PDS MTO REPORT’

1,3,120,-6,1,1,’Page: ’

1,3,127,-3,2,4

1,11,1,-34,1,-1,’GRAND TOTALS’

1,13,1,-15,1,-1,’Components’

1,13,20,-15,1,-1,’Pipes’

1,13,40,-15,1,-1,’Instruments’

1,13,60,-15,1,-1,’Gaskets’

1,13,80,-15,1,-1,’Bolts’

1,13,100,-15,1,-1,’Pipe Supports’

1,14,1,-15,2,2,BST

1,14,20,-15,2,2,BRT

1,14,40,-15,2,2,B*OT

1,14,60,-15,2,2,BVT

1,14,80,-15,2,2,BZT

1,14,100,-15,2,2,B*RT

Sample MTO Output

Date/Time : 15-Apr-93 PDS MTO REPORT Page: 1

Corporate Headquarters PDS Project tcproj

Intergraph Corporation tc101

Huntsville, Alabama 35894-0001 RoXXon Corp.

(205)730-2000 Nth Projector

Commodity Code Qty/Length 1st Size 2nd Size Material Description

______________ __________ ________ ________ ____________________

LINE NUMBER: P403-1/2IN-1C0031-N

________________________________

253


POCAAAOAAE 1 1/2IN 1/2IN Nipple, PE, S-160, 3" long, ASTM-A106-B

PPCAAAOAAE 1 1/2IN 1/2IN Nipple, PE, S-160, 6" long, ASTM-A106-B

VAUHAHGAAA 2 1/2IN 1/2IN Gate valve, CL800, SWE/FTE, BB, OS&Y, ASTM-A105, trim 8, Smith

800

LINE NUMBER: P403-3/4IN-1C0031-N

________________________________

POCAAAOAAE 9 3/4IN 3/4IN Nipple, PE, S-160, 3" long, ASTM-A106-B

TPAZVZZAAA 7 3/4IN - Plug, MTE, ASTM-A105, ANSI-B16.11

VAUHAHGAAA 9 3/4IN 3/4IN Gate valve, CL800, SWE/FTE, BB, OS&Y, ASTM-A105, trim 8, Smith

800

38-PI-6 1 3/4IN 3/4IN *

39-PI-9 1 3/4IN 3/4IN *

LINE NUMBER: P403-3IN-1C0031-N

______________________________

FAAABAWAAA 2 3IN 3IN Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore

XDAABZZQSG 1 3" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled,

CS center ring, API-601

YZZZHZZFFF 4 5/8" 3 3/4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts


______________________________

1 4IN 4IN *


VAABAHCCAA 1 4IN 4IN Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane

47

VBABAHCFAA 1 4IN 4IN Globe valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8,

Crane 143

WAAAAAWAAA 2 4IN 4IN 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9

WRBAAAWAAA 2 4IN 3IN Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,

ANSI-B16.9

WTAAAAWAAA 1 4IN 4IN Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9



______________ __________ ________ ________ ____________________


______________________________

PAAAAAWAAA 4’ 8 9/16" 4IN Pipe, S-STD, BE, ASTM-A53-B Type S



YZZZHZZFFF 32 5/8" 3 3/4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts

supp2 1 4IN *


______________________________


FGPBBAWAAA 2 6IN 6IN Orifice flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.36, WN, one

0.5" SWE tap, S-STD bore

GJGABZZADA 1 6IN 6IN Spectacle blank, CL150, RFTBE, ASTM-A516-70, API-590Z1, 0.75

thk

VAABAHCCAA 4 6IN 6IN Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane

47

VCABAHOBAA 2 6IN 6IN Check valve, CL150, RFFE, BC, swing, ASTM-A216-WCB, trim 8,

Pacific 180

WAAAAAWAAA 9 6IN 6IN 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9

254

8. Rep

ortin

g

Material Takeoff Reporting (Report Manager)________________

WADAAAWAAA 1 6IN 6IN 45 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9

WOAAAAWAFA 1 6IN 4IN Weldolet, S-STD x S-STD, BE, ASTM-A105

WOBSABQAFA 4 6IN 3/4IN Sockolet, CL3000, BE/SWE, ASTM-A105

WRAAAAWAAA 4 6IN 4IN Concentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,

ANSI-B16.9

WTAAAAWAAA 3 6IN 6IN Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9

PAAAAAWAAA 131’ 1 3/16" 6IN Pipe, S-STD, BE, ASTM-A53-B Type S



XDABBZZQSG 1 6" - Gasket, CL300, G653, 0.125" thk, 304 spiral wnd, graph filled,


YZZZHZZFFF 80 3/4" 4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts

YZZZHZZFFF 20 3/4" 5" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts

supp1 1 6IN *



______________ __________ ________ ________ ____________________


______________________________

supp3 1 6IN *


GRAND TOTALS

____________

Components Pipes Instruments Gaskets Bolts Pipe Supports

__________ _____ ___________ _______ _____ _____________

87 19 2 18 136 3

255


8.8 Understanding Implied Items

This section discusses the various types of implied items and a few miscellaneous items andhow they are reported. It also covers some of the features within the PDS suite of productsthat are outside of the Report Manager module.

When reporting on components, there are sometimes additional parts necessary to completethat component that are not represented graphically in the piping model or stored in the PipingDesign database. These additional components are mating, spec, or table implied items.

If an implied item is part of an implied connection, it is called a mating implied item.Otherwise, the naming conventions for implied items are defined by the location where theimplied item data is retrieved. The system retrieves these implied items from either the PipingComponent Specification Data Table (pdtable_202) or from Piping Commodity ImpliedMaterial Data Table (pdtable_212). The following sections explains the mating, spec, andtable implied items and how data is retrieved for each:

8.8.1 Mating Implied Items

Mating implied items are found by the system while scanning related mating components anddefining the items necessary to complete those connections. The following items termedmating implied.

Bolts

Gaskets

Nuts

Welds

The Material Takeoff Options form is part of the Project Administrator module, and itssetting greatly affect the way mating implied items are reported.

For more information on mating implied item reporting see the MaterialTakeoff Options section.

8.8.2 ’*’ Spec Implied Items

Commodity codes prefixed by an ’*’ in Material Description Code field in the Piping JobSpecification indicate a primary component that has one associated spec implied item.

The definition of the spec implied item has the same search parameters as the primarycomponent, except in the following instances:

256

8. Rep

ortin

g

Understanding Implied Items________________

– The value for the option attribute of the spec implied component is equal to 5000plus the option value for the primary component.

– The definition of the spec implied component can be divided into several NPDranges.

The output parameters of the spec implied component may differ from those of theprimary component in the following instances:

– Only the primary component is included in the model depiction; the spec impliedcomponent only appears in reports.

– Only the primary component is displayed on an isometric drawing; the spec impliedcomponent only appears in the materials list.

The commodity codes prefixed by an ’*’ are used to define:

– Stub-ends used in conjunction with lap, slip-on, and plate flanges.

– Jacketed components when the outer jackets are obtained independently of theinternal components.

’*’ Spec Implied Example

Both the primary component and the implied item in the following Piping Job Specificationexample would be reported:

! AABBCC ————Green CP———– ————Red CP————- Commodity Model Geo Mat Wt FF

! Code Opt From To Prp Rating Sc/Th TS From To Prp Rating Sc/Th TS code TMx Code Std Mod Grd Cd FC Nte lng

PIPING 1 2 6 301 - S-STD 5 - - - - - - *PAAAAAWAAA - PIPE 100 100 142 52 15 - 240

PIPING 5001 2 6 301 - S-STD 5 - - - - - - newcommcode - PIPE 100 100 142 52 15 - -

8.8.3 ’+’ Table Implied Items

Commodity codes prefixed by a ’+’ in the Commodity Code field in the Piping JobSpecification indicate the primary component has one or more associated table implied items.The system searches for the definition of the implied item in the Piping Commodity ImpliedMaterial Data (pdtable_212), which contains the commodity code of the primary component,the applicable NPD range, and the commodity code of the table implied components.

To use this option, pdtable_212 must be loaded.

The output parameters of the table implied item may differ from those of the primarycomponent in the following situations:

– If only the primary component is included in the model depiction, the table implieditems appear only in the report.

257


– If the primary component is displayed on an isometric drawing, The materials listonly includes the short description of the primary component. The descriptions ofthe table implied items are displayed as notes on the drawing, pointing to theprimary component. The text for these notes is derived from the short descriptionsof the applicable commodity codes. The short description can contain $ symbols toforce the text to a new line in the label.

The commodity codes prefixed by a ’+’ are used to define the following items:

– Cap screws for valves requiring caps.

– Safety covers for required components.

– Housings for required components.

’+’ Table Implied Example

First, notice the ’+’ indicating a table implied item in a line taken from the Piping JobSpecification.

6Q2C01 1 3 24 21 CL150 NREQD 5 - - 421 CL150 MATCH 5 +FAAABAWAAA - FWN 35 - 150 52 15 -

Secondly, notice the table entries that are related to the primary component,FAAABAWAAA, in pdtable_212. All of the related items, which include the first three itemsin the table would be reported:

! Implied data for table 212Single_SpacingSequence= 2 3 4 5 6 7 8 9 10!Comm Code GFr GTo RFr RTo Imp Code Qty FC Note!FAAABAWAAA 2 12 0 0 IMPFLG2A 1.5 7 -FAAABAWAAA 2 12 0 0 IMPFLG2B 0.5 7 -FAAABAWAAA 2 12 0 0 IMPFLG2C 1.0 7 -VAABAHCCAA 2 2 0 0 IMPVAL2A 0.5 7 -VAABAHCCAA 2 2 0 0 IMPVAL2B 2.5 7 -PAAAAAWAAA 2 2 0 0 IMPPIP2 1.0 7 -WAAAAAWAAA 2 2 0 0 IMPELB2 2.0 7 -WRAAAAWAAA 3 12 2 10 IMPRED 1.0 7 -

258

8. Rep

ortin

g

Material Takeoff Options________________

8.9 Material Takeoff Options

The Material Takeoff Options form of the Project Data Manager specifies the source ofcommodity information, units for bolt length and diameter, and specifies item names used toreference a commodity item in the Piping Job Specification and Graphic Commodity Library.These options are essential to material takeoff reporting.

Refer to the Project Administrator Reference Guide for more information on the Project DataManager. Refer to the Reference Data Manager Reference Guide for information on the studtable, bolt length calculations, and the bolt commodity code table.

Operating Sequence

1. Specify the bolt information.

Bolt Length Roundoff — Select the option for the means to determine the reportedbolt length.

— Preferred Bolt Length Table - the system uses the preferred bolt length table.

— Bolt Roundoff Factor - the system rounds up the calculated length by the specifiedfactor.

— No Roundoff - the exact length is used.

Length Calculation — Select the method to be used in calculating bolt length. Thebolt length is read from the stud table. The table name can be determined using therating and table suffix (Almost Precise) or using termination type, rating, and tablesuffix (Precise). This also affects bolt lengths for lap joint flanges.

259

PDS 3D Theory — April 2002________________ Bolt Commodity Code Select the method to be used in determining the commoditycode for bolts for use in material take-off. Piping Job Specification or BoltCommodity Code Table.

Bolt Diameter Units — Select the system of units for bolt diameter.

Bolt Length Units — Select the system of units for bolt length.

2. Gasket Search

Select this field to toggle the setting between Default or Alternate.

3. Field Fit Length

Select this field to toggle the setting between Off or On. If this field is On, the systemdisplays a field to input the Field Fit Length Table name.

4. Commodity Code

Select this field to toggle the setting between Size Independent or Size Dependent.

For a detailed description and graphical examples of how these optionswork, see the Size Dependent and Independent Reporting section.

When the Size Dependent option is enabled, thesystem provides two additional options.

Source of Implied Data This option specifies the source of the commodity code forreporting implied data from the Piping Commodity Implied Material Data Table.

The default option (System Commodity Code) tells the system to use the commoditycode defined in the Piping Commodity Specification Data Table (pdtable_202 attribute18).

The Size-Dependent Commodity Code option tells the system to use the commoditycode defined in the Piping Commodity Size-Dependent Material Data Table(pdtable_211 attribute 7).

Source of Material Description — This option specifies the source of the commoditycode for reporting a component’s material description.

The default option (System Commodity Code) tells the system to use the commoditycode defined in the Piping Commodity Specification Data Table (pdtable_202 attribute18). This option will result in a smaller Material Description Library.

260

8. Rep

ortin

g

Material Takeoff Options________________ The Size-Dependent Commodity Code option tells the system to use the commoditycode defined in the Piping Commodity Size-Dependent Material Data Table(pdtable_211 attribute 7). This option will result in a larger Material DescriptionLibrary.

5. Key in the commodity item names to be used for reporting mating implied materials.

Gasket Commodity NameBolt Commodity NameNut Commodity Name

6. Key in the Eden Module names.

Bolt Data Module — This field defines the name of the Eden Module whichdetermines the values for the bolt diameter, the number of bolts per mating, and the boltextension.

Flange Data Module — This field defines the name of the Eden Module which definesvalues for flange outside diameter, thickness, and seat depth.

7. Key in the bolt length values. The display of these fields is dependent on the setting forBolt Roundoff Option.

Bolt Length Table — This table defines the low and high range for calculated boltlengths and corresponding preferred or purchased lengths of the bolt. This field is onlyused if Preferred Bolt Length Table is the active Bolt Roundoff Option.

Bolt Length Roundoff Factor — This field defines the value for the bolt roundofffactor in subunits. This value is only used if Bolt Roundoff Factor is the active BoltRoundoff Option.

8. Select Confirm (√) to accept any changes to the Material Takeoff options.

261


8.10 Labels in Material Descriptions

The material descriptions for commodity items can be loaded in the Material Descriptionlibrary via neutral files. The neutral file includes a unique Commodity Code followed by atleast one space and a description enclosed in single quotes. It also contains the impliedmaterial descriptions associated with a commodity item.

The following shows a portion of the neutral file used to load the Short Material Descriptions.

! DEFINE SHORT DESCRIPTIONS

! Date/Time: Thu Apr 23 14:16:58 1992

! Processed Library /usr/newpipe/refdata/us_shbom.l

!Cmdty Code ====================================Description========================================



CHAIN_1251 ’Chainwheel operator each with [424] of total chain length for valve with tag no [402]’

DAABAXAABE ’Monitor, CL150 FFFE, ˆstation type, 4" CL150 in-let by 2.5" NHT stainless steel outlet w/stainless steel stem

lock knobs with 0.75" coupling in base, w/shapertip nozzle, Stang BB0309-21’

DAABAXAABF ’Monitor, CL150 FFFE, ˆstation type 4" CL150 in-let by 2.5" NHT stainless steel outlet w/stainless steel

stem lock knobs with 0.75" coupling in base, w/fog nozzle, Stang BB0309-21’

DACBAXABBC ’Monitor, CL150 FFFE, êlevated type, free standing, 4" CL150 in-let by 2.5" NHT stainless steel outlet, [427],

w/drain coupling, w/shapertip nozzle and two reaction supports, Stang BB2999-’

DACBAXABBD ’Monitor, CL300 FFFE, êlevated type, supported, 6" CL300 in-let by 2.5" NHT stainless steel outlet, [427],

w/drain coupling, w/shapertip nozzle, Stang BB3561’

DBAAAXBAAB ’Fire hydrant, CL125 FFFE, ˆ5" size, counterclockwise open, 4.5" steamer nozzle, two 2.5" hose nozzles

equipped w/caps and chains, [428], American Darling B-50-B’

DCBGDXEADA ’Hose rack, 300#, FTE, ˆw/valve, wall mount, rt hand w/100 ft hose & fog nozzle, Powhatan 30-333’

DDAXCJDAAA ’Spray sprinkler, MTE, filled cone w/rupture disc, 304, Grinnell, Mulsifyre Projector S-1’

FAAAAAWAAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’

FAAAAAWWAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, cement lined, [409]|bore to match|’

FAAABADIIA ’Flange, CL150, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’

FAAABADIIF ’Flange, CL150, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’

FAAABADNPF ’Flange, CL150, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, S-80S bore’

FAAABAOAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’

FAAABAOABB ’Flange, CL150, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, S-160 bore’

FAAABAOFFH ’Flange, CL150, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, S-160 bore’

FAAABAWAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWABB ’Flange, CL150, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWFFH ’Flange, CL150, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWFFL ’Flange, CL150, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWGFD ’Flange, CL150, RFFE/BE, ÂSME-SA182-F11, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWIIA ’Flange, CL150, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWIIF ’Flange, CL150, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|’

FAAABAWNPF ’Flange, CL150, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|’

FAAABBDAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-XXS bore’

FAAADAOAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’

FAAADAOFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’

FAAADAWAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAAADAWFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAAADBDFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-XXS bore’

FAABBADIIA ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’

FAABBADIIB ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304L, ANSI-B16.5, WN, S-80S bore’

FAABBADIIF ’Flange, CL300, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’

FAABBAOAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’

FAABBAOABB ’Flange, CL300, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, S-160 bore’

FAABBAOFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, S-160 bore’

FAABBAOFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, S-160 bore’

FAABBAWAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWABB ’Flange, CL300, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWFFL ’Flange, CL300, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWIIA ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWIIB ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304L, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWIIF ’Flange, CL300, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|’

FAABBAWNPF ’Flange, CL300, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|’

FAABBBDAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-XXS bore’

FAABDADIIJ ’Flange, CL300, RFFE/BE, ÂSTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, S-80S bore’

262

8. Rep

ortin

g

Labels in Material Descriptions________________ FAABDAOAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’

FAABDAOFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’

FAABDAWAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAABDAWFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAABDAWFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAABDAWIIJ ’Flange, CL300, RFFE/BE, ÂSTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’

FAADBADIIA ’Flange, CL600, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’

FAADBADIIF ’Flange, CL600, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’

FAADBAOAAA ’Flange, CL600, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’

FAADBAOABE ’Flange, CL600, RFFE/BE, ÂSME-SA105, ANSI-B16.5, WN, S-160 bore’

FAADBAWAAA ’Flange, CL600, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’

FAADBAWABE ’Flange, CL600, RFFE/BE, ÂSME-SA105, ANSI-B16.5, WN, [409]|bore to match|’

FAADBAWFFC ’Flange, CL600, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, [409]|bore to match|’

FAADBAWFFH ’Flange, CL600, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’

FAADBAWFFL ’Flange, CL600, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’

FAADBAWIIA ’Flange, CL600, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’

The following conventions are used to identify different types of information in the materialdescriptions:

ˆ All information to the left of the carat (ˆ) is used in MTO reporting and isometricextraction, but is excluded from Spec reporting.

| | Information appearing in |Pipes| indicates information for Spec descriptionsonly. This information is excluded from the descriptions for MTO reporting andisometric extraction.

[ ] Information appearing in [brackets] indicates a label type from the LabelDescription Library. The system uses the label format to determine theinformation to be included in the material description for MTO reporting andisometric extraction. The label information is never used in Spec reporting.

The following label types are provided in the product delivery:

Label No Data in Label Source of Data401 Piping sch/thk 1 Pipe403 Component Sch/thk 1 Component405 Component sch/thk 1 b Component407 Component sch/thk 2 Component409 Component sch/thk 2 b Component411 Component sch/thk 1 x 2 Component413 Component sch/thk 1 x 2 b Component415 Component sch/thk 1 x 3 Component417 Component sch/thk 1 x 3 b Component421 Bonnet length Component423 Reinforcing weld size Component425 Pad width x pad thick Component

Attributes for mating implied items, specifically bolts and gaskets, are not stored in theDesign Database (dd_projname) where attributes for independent components are stored. Youcan insert labels in Material Description Library for bolt and gasket entries, but these labelsmust be classified as Piping Component Data labels when they are created.

Although data for bolts and gaskets is not recorded in the Piping Component Data Table(pdtable_34_x) in the Piping Design Database (dd_projname), bolt and gasket labels areclassified as Piping Component Data labels. The system retrieves the bolt and gasketinformation for reporting using related attributes in the Piping Component Data Table(pdtable_202).

263

PDS 3D Theory — April 2002________________ Although all of the attributes for piping components are available when you define a bolt orgasket label using the Piping Component Data labels option, only the following attributescontain data that is pertinent to bolt and gasket reporting. The following list displays theform-attribute/table-attribute relationship which define what data is actually reported from thePiping Component Data Table (pdtable_202):

Form Attributes Related (pdtable_202) Attributescommodity_name commodity_nameoption_code option_codemaximum_temp maximum_tempcp_1_nom_pip_diam gcp_from_nom_diamcp_1_end_prep gcp_to_nom_diamcp_1_outside_diam gcp_end_prepcp_1_rating gcp_ratingcp_1_sch_thk gcp_sch_thktable_suffix_green gcp_table_suffixcp_2_nom_pipe_diam rcp_from_nom_diamcp_2_outside_diam rcp_to_nom_diamcp_2_end_prep rcp_end_prepcp_2_rating rcp_ratingcp_2_sch_thk rcp_sch_thktable_suffix_red rcp_table_suffixcommodity_code commodity_codemodel_code model_codePDS_sort_code PDS_sort_codebend_radius modifiergeometric_standard geometric_standardweight_code weight_codefabrication_cat fabrication_catmaterials_grade materials_gradestandard_note_no_a standard_note_no_astandard_note_no_b standard_note_no_b

A Label Description Library is delivered in win32app\pdshell\lib\labels.l and should be editedto suit the needs of your project.

264

8. Rep

ortin

g

Create Label Attribute Data________________

8.10.1 Create Label Attribute Data

The Label Description Library Manager is used to create and revise label data for the PDS3D modules. The Create Label Attribute Data form allows you to create and define a label.The Line and Item fields are used to define the attributes that make up the label and the orderof the attributes within the label.

Set the option at the upper left of the form.

Insert Data — used to add a line or item to the label description.

Delete Data — used to delete a selected line or item from the label description.

Edit Data — used to revise a selected line or item in the label description.

Insert Data

1. Set the option to Insert Data.

2. Set the toggle to Insert after or Insert before.

3. Select Line or Item to Insert Data

Select a line field to create a new line (before or after) the selected line.

— OR —

Select an item field to create a new item in the current line (before or after) the selecteditem.

265

PDS 3D Theory — April 2002________________ The system activates a form that displays the Attribute Data Types. The following formillustrates the display for a drawing view specific label.

4. Select Option

Select Piping Component Data to define the attribute data type for the bolt or gasketlabel.

The system displays the attributes for the selected data type.

266

8. Rep

ortin

g

Create Label Attribute Data________________

5. Enter Data

Select the attribute to be reported from the form. The system sets the Format Dataautomatically. You can modify the total length and the number of decimal places (ifapplicable).

All of the attributes that apply to gaskets and bolts are listed in the Labels in MaterialDescriptions section.

— OR —

For drawing view specific labels, you can select User Keyin Attribute to specify textto be entered by the user at label creation.

— OR —

Select Text Only and key in the text for a literal expression to be inserted in the label.

— OR —

Select Spacing Only and key in the number of spaces to define spacing betweenattributes.

6. Repeat the previous step to add additional attribute text information. This allows you tocombine attribute values and pre-formatted text.

You can only define one user-defined key-in in a specific label.

267


7. Select one of the Optional Data options to specify a modifier to the active format.Master Units = MicroStation master units, Sub Units = MicroStation sub units.

8. Select Confirm (√) to accept the specified attribute data.

Delete Data

1. Set the option to Delete Data.

2. Select the line or item to be deleted.

3. Select Confirm (√) to delete the highlighted line or item. When you select a line, thesystem deletes all the associated items.

Edit Data

1. Set the option to Edit Data.

2. Select Item to Edit

Select the item to be revised.

The system displays the attributes definition form for the selected item. The activesetting is highlighted or shown in the display fields.

3. Select an attribute from the form to change the type of data.

— OR —

Select the Format Data option. You can modify the total length and the number ofdecimal places (if applicable).

— OR —

For drawing view specific labels, you can select User Keyin Attribute to specify textto be entered by the user at label creation.

— OR —

Select Text Only and key in the text for a literal expression to be inserted in the label.

— OR —

Select Spacing Only and key in the number of spaces to define spacing betweenattributes.

4. Repeat the previous steps to edit additional items.

— THEN —

Select Confirm (√) to accept the edits.

9. Isom

etric E

xtraction

Extracting Isometric Drawings________________

9. Extracting Isometric Drawings

The PDS Isometric Extraction Software creates piping isometric drawings from 3D pipingmodels created by the Piping Designer.

269

PDS 3D Theory — April 2002________________ The software consists of two principal components:

Intergraph 3D software packages which create input for ISOGEN and perform otherfunctions necessary in final drawing creation.

ISOGEN, which draws the piping isometric and places it in a MicroStation design fileand

The software allows you to extract isometrics from a 3D plant model: single isometricsinteractively or multiple isometrics in a batch mode.

The ISOGEN software is designed to be flexible because drawing practices vary from onecompany to another. The following features of Intergraph’s isometric extraction packageallow you to specify drawing format:

User-controlled ISOGEN option switches

The capability to use an alternate or foreign text

A large set of Intergraph option switches

User-controlled attribute breaks shown on drawings

A flexible method for generating notes

Attribute-driven symbology (solid or dotted lines)

User-defined component symbology

User-controlled mapping of attributes to the title block.

In addition to the isometric drawing, the software also generates several nongraphic outputs,the most important of which is a completely user-definable MTO neutral file. This neutral fileis extremely useful for those who want to combine a material control system with Intergraph’s3D modeling software.

The above features are collectively referred to as software customization and are dealt with atlength in the PDS ISOGEN Interface Reference Guide.

270

9. Isom

etric E

xtraction

Overview of Isometric Extraction________________

9.1 Overview of Isometric Extraction

This section outlines the software components and how they are organized for interactivelyextracting isometrics.

9.1.1 The Intergraph Interface to ISOGEN

The core software module in isometric extraction (both interactive and batch) is the ISOGENinterface. This program reads data from the 3D model files and generates an input file forISOGEN. ISOGEN knows nothing of PDS or any of its files. It reads only the input filecreated for it by the ISOGEN interface. While ISOGEN is primarily responsible forgenerating the drawing graphics (including dimensioning) the ISOGEN interface isresponsible for most everything else — including note generation, recognition of attributechanges, defining which symbols to use and so on.

271

PDS 3D Theory — April 2002________________ The primary input to the ISOGEN interface is an ASCII file named pdsidf.dat. The interfacereads from this file the piping and equipment models involved, the output isometric file name,and identification of all of the pipelines in the drawing. The interface also reads in data fromthe options file.

The options file consists of a collection of switches, options and tables that gives you somecontrol over what the ISOGEN interface puts in its output file (called the intermediate datafile or idf) and therefore what appears in the final drawing.

Once this data is read in, the interface collects from the model files all of the components thatmake up the piping network. Data from the components is then used to form an internal datastructure which represents the network. Finally, this network is traversed (the software tracesa path through the piping network) and records are generated in the idf. The order of therecords in the idf is in the order of the network traversal. Drawing notes and other featuressuch as bill of material information are dealt with component by component as the network istraversed.

If the components in the piping models are not properly connected or other problems exist, theinternal data structure will not be properly built and isometric extraction will fail. The HITSreport can help you to find problems in the piping model and tell you when the interfacesoftware is not working properly.

9.1.2 ASCII to Binary Conversion

The Intergraph interface to ISOGEN creates an ASCII data file containing the input toISOGEN. Since ISOGEN requires the input data to be in binary format, a program namedISOA_BGEN is run to convert this ASCII data file to binary. ISOA_BGEN creates the binaryoutput file FOR036.# which IZOD2 uses to generate the isometric drawing.

9.1.3 ISOGEN

ISOGEN takes the binary input file and generates graphics in an 2D MicroStation design file.The graphics consist of the completed isometric drawing. ISOGEN can also generate severalnongraphic outputs, including:

An ISOGEN MTO neutral file

A parts list (bill of material)

A cut pipe report

A component VRS sheet number file

The parts list file contains the same bill of material that is shown on the isometric drawing. Itis possible to turn the drawing bill of material off and attach the printed ASCII file to thedrawing instead. The cut pipe report, which shows the length of each piece of pipe in the line,can be useful. The component VRS sheet number file is used by the batch extraction softwareand is discussed elsewhere.

272

9. Isom

etric E

xtraction

Batch Software Organization________________

9.2 Batch Software Organization

This section provides an overview of the batch extraction software components andorganization. The purpose of this section is to explain to software support personnel how thesoftware works so that problems can be tracked down and reported.

The batch extraction software is driven by an executable (pdsidf) and a script file (batch.sh).When you submit a batch job using the Schedule Batch Job form the batch extraction issubmitted to a batch queue named PDisocreate. This queue is created with a job limit of 1and a priority of 16. You can change these parameters as needed.

In order to run batch iso’s, a new file located in /usr/bin called pd_iso.sh must define locationsfor required software. This script is executed from the batch queue and allows the batchextraction process to run on a node other than the one from which it was submitted. Thefollowing four variables must be exported:

PD_SHELLPD_ISOPD_ISOGENRIS_PARAMETERS

The above variables have the following default settings after the product is installed.

PD_SHELL = /usr/ip32/pdshell/PD_ISO = /usr/ip32/pdiso/PD_ISOGEN = /usr/ip32/pdisogen/RIS_PARAMETERS = /usr/ip32/ris/parameters

If the locations for the above variables are different from the default locations. The file/usr/bin/pd_iso.sh must be edited so that it reflects the current variable location.

9.2.1 The Batch Job Input File

The input to the batch procedure is an ASCII data file generated by the Batch Environmentcalled the Batch Job Input File. This file is structured as shown.

273


Figure 9 - 1. Batch input file data structure

The first record in the file contains a file format version number and the name of the BatchData File from which the Batch Job Input file was generated. The software checks the versionnumber to see if it matches the software version number, and, if it does match, passes theBatch Data File name on to other software modules as needed.

The second record is called an option record. The option record contains all of the batchprocessing options and revision block data that was entered into the BATCH form. Eachoption is separated from the others by at least one space. This record contains an exclamationpoint (!) in column 1 which flags it as an option record.

The third record holds the name of the default set which was specified in the Create Batch JobInput form. This record also contains an exclamation point in column 1.

Subsequent records, which initially contain a space in column 1, hold the area and primaryline name for an isometric drawing which will be extracted. After the line is extracted, it ismarked by an asterisk (*) in column 1 to indicate that it has been processed.

The drawing records can be repeated any number of times in the batch job input file. Eachtime you select the Accept button from the Create Batch Job Input form, you write out a set ofdrawing records to the batch input file. An example batch job input file is shown below.

Figure 9 - 2. Example Batch Job Input File

When a batch iso job is submitted using the Schedule Batch Job form, the batch job input filename is passed to the pdsidf executable as a parameter. The system then reads the batch jobinput file and drawing creation begins.

274

9. Isom

etric E

xtraction

Batch Software Organization________________

9.2.2 Line Processing (pdsidf)

Given the options from the batch input file and the identification of the line, two files arecreated, seed.dat and pdsidf.dat. These are the same two files that are created duringinteractive extraction.

The Project database is accessed to obtain the list of model files, secondary pipeline names,the seed file names, the options file for the piping area, the output file directory, the iso designfile name and the extraction number for the drawing.

The two files produced are different from the ones produced for interactive extraction. Inpdsidf.dat, the first line name in the line name list is followed by a backslash and the pipingarea name. Following the line list is a record that contains the default set name. Next is arecord that contains batch processing options. The last record contains the extraction numberfor the drawing.

skiso5skiso4skiso6skiso7*skiso340eqp0140eqp00

pdssk:h:\proj\iso\isofiles\380105wc.i*380105\skiso\1

projN Y Y N * * Y * * 04-Aug-1998 *

131 0

In SEED.DAT, the seed iso design file name is followed by records containing the plotrequest file name, the output file directory, the output iso file name, extraction number andnumber of sections.

pdssk:h:\proj\iso\ref\isoc.defpdssk:h:\proj\iso\ref\isoc.sedpdssk:h:\proj\iso\ref\isoc_sml.ipdssk:h:\proj\iso\isofiles

380105131.fi

9.2.3 The ISOGEN Interface

The ISOGEN interface performs the same function in batch extraction as in interactiveextraction. It generates an Intermediate Data File (IDF), which is the input to ISOGEN. Inaddition to the IDF the interface may also produce an mto neutral file and three filescontaining text for the drawing title block.

275


9.2.4 ISOGEN

Isometrics generated by the batch software are always created one sheet to a design file. Theiso design file name is passed to the interface as name.i*. Therefore, the first sheet will be ina file with the extension .i01, the second in .i02 and so on.

When isometrics are created in batch, you must set Intergraph options block word 4 to 1. Thiscauses ISOGEN to create a file that identifies which sheet each component in the line isdrawn on. This file (called the sheet data file) is used downstream to split up the mto neutralfile by sheet and also to prepare the segment summary table for each isometric sheet.

9.2.5 Plotting

After drawings are created in batch they can be plotted with the IP_IPLOT plotting software.

To submit a plot, the batch software submits a job to the batch queue named PDisoplot. Thejob that runs in PDisoplot actually launches the plot.

Since the plot jobs are launched from a separate batch queue, you can accumulate the jobs inthe queue and release them at some later time. You might also hold the jobs in PDisoplot toprevent normal production plotting queues from getting loaded down with isometric plots.

276

10. Draw

ing

M

anag

emen

t

Creating Orthographic Drawings________________

10. Creating OrthographicDrawings

Designers use the Drawing Manager (PD_Draw) product to create and/or reviseorthographic production drawings. PD_Draw creates windows (drawing views) to the live 3DModels created with PD_Design and the other modeling products. PD_Draw is used to placeannotation labels identifying intelligent items and model coordinates, to plot the drawings,and to produce reports for drawings and model data.

The Drawing Manager is used to create and revise orthographic production drawings. It canbe used by any of the 3D disciplines within PDS for drawing management.

A drawing is a sheet or a plot used to describe the design of a model design volume (workarea). Many drawings can be created from one model to completely document a designvolume. A drawing can contain more than one drawing view of a model or models.

A drawing view is a view of a model or models. Each drawing view within a drawing canhave a different scale and each label within a drawing can have a different character size.

You can create a drawing during any stage of the design process. It consists of the referencemodel attachments for the model graphics used in the drawing and the graphics for thedrawing itself. The model graphics reside in the design file for that model. These modelgraphics are attached to the drawing as reference files through the use of drawing views.

277


Drawing Manager Features

The Drawing Manager can be used to:

Create a drawing for any of the PDS 3D disciplines, along with a key plan drawing.

Create multiple drawing views for a given drawing.

Revise definition information for existing drawings or drawing views.

Delete drawings and drawing views

Report on drawing information in the Project Control Database.

Report on model data in a specified drawing and drawing view(s).

Place drawing views graphically within a drawing border.

Revise drawing view characteristics, including clipping volume, orientation, referencefile attachments, and display categories.

Place annotation labels on a drawing to identify intelligent items and modelcoordinates.

Create hidden-line-removed model graphics.

Plot a drawing or set of drawings.

Create a key plan model for the project.

278

10. Draw

ing

M

anag

emen

t

Drawing Manager Setup________________

10.1 Drawing Manager Setup

Project Setup

A project and all of its accompanying files must be defined with the Project Administratorbefore you can use the Drawing Manager. Refer to the Project Administrator ReferenceGuide 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.

Model Files

A set of model files for the project must be defined before you can use the DrawingManager.

Refer to the following documents for information on creating and manipulating PDS 3DModels.

Piping Design Graphics Reference Guide

PDS Equipment Modeling Reference Guide

MicasPlus ModelDraft Reference Guide

PE HVAC Modeling Reference Guide

EE Raceway Modeling Reference Guide

Drawing Manager Setup

Complete the following operations before using the Drawing Manager.

Drawing Categories

When a project is created, the Project Administrator copies the default drawing categorynames to the project directory. The name of the copied file is drwcats.txt. You can edit thisfile to change the names that are displayed for drawing categories.

279


Although you can modify the drawing category names, the meaning of aspecific category will not be altered by this change.

Cells

The flow arrow symbol for drawing annotation is provided in the cell librarywin32app\pdshell\cell\drawing.cel. This cell library is copied to the project directory by theProject Administrator as a part of project creation. The Drawing Manager attaches thiscell library each time you select a drawing for the purpose of drawing annotation.

The drawing.cel library in the project directory must be used for any cells, other than the flowarrow, which you intend to use for drawing annotation.

Drawing Borders

The Drawing Manager uses the following guidelines to determine which drawing border toattach.

The directory and network address for the drawing border is defined in the RDBManagement Data with the Reference Data Manager. This setting is stored in theProject Control Database for access by the Drawing Manager.

The file specifications for the drawing borders is determined by the following namingconvention.

dwgbrd_<drawing_type>.<drawing_size>

drawing_type is the standard note number in Standard Note Type 2000 for drawingtypes.

drawing_size is the text for the standard note value corresponding to the drawing size inthe Standard Note Type 1202.

For example, the drawing border name for an ’A’ size piping drawing is dwgbrd_2.a.

Drawing Plot Size Table

This table is located in the drawplotsize file and is copied from the PD_Shell deliverydirectory at the time a project is created. It contains the drawing size standard notation, plotsize, the standard text for the size, and the four margins for the cutting edge. An example of adrawplotsize file and definitions of each field follows:

! Drawing Plot Size Table!!Drawing Size Cutting Edge Margins from Cutting Edge (Drawing Size)!Std Note Size X-l Y-t X-r Y-b!1 8.5"x11" 0.8125" 0.625" 2.125" 0.625 (A)

280

10. Draw

ing

M

anag

emen

t

Drawing Manager Setup________________ 2 11"x17" 1" 0.6875" 3" 0.6875" (B)3 17"x22" 1.1875" 0.75" 3.75" 0.75" (C)4 24"x36" 1.375" 0.8125" 5.4375" 0.8125" (D)5 34"x44" 1.5625" 0.875" 6.875" 0.875" (E)6 28"x40" 1.625" 0.9375" 5.625" 0.9375" (F)101 840mmx1189mm 56mm 35mm 198mm 35mm (A0)102 595mmx840mm 47mm 30mm 193mm 30mm (A1)103 420mmx595mm 38mm 27mm 190mm 27mm (A2)104 297mmx420mm 33mm 25mm 155mm 72mm (A3)105 210mmx297mm 28mm 24mm 65mm 24mm (A4)

Drawing Size Std Note is the standard note, which is referenced from the StandardNote Type 1202, for the drawing size selected.

Cutting Edge Size reflects the actual size of the cutting edge around the border that isassociated with the drawing size.

Margins from Cutting Edge

— X-l defines the horizontal distance from the left cutting edge for composition.

— X-t defines the horizontal distance from the right cutting edge for composition.

— Y-r defines the vertical distance from the top cutting edge for composition.

— Y-b defines the vertical distance from the bottom cutting edge for composition.

— Drawing Size is the standard note text for the drawing size.

Drawing Manager Database TableInformation

This section describes and includes the tables from the Default Relational DatabaseDefinition, which is stored in the project.ddl file, that are used during the drawing process.

These tables are dedicated to the Drawing Manager task. There is interaction between thesetables and other various tables in the Project Control Database (PDTABLE_112 Design AreaData, for example).

Project Control Database

This section describes and includes the tables from the Project Control Database that areaffected during the drawing process.

Do not edit database definitions except to modify column names.

# Drawing Data

281

PDS 3D Theory — April 2002________________ table number = 121, number of columns = 24

1 , dwg_index_no , integer , index 12 , drawing_no , character(24) , index 23 , drawing_title , character(40)4 , default_scale , character(16)5 , approval_initials , character(4)6 , approval_date , integer7 , approval_status , short , standard note 358 , completion_status , short9 , drawing_size , short , standard note 120210, drawing_type , short , standard note 2000 , index 311, last_revision_no , character(2)12, drawing_file_spec , character(14)13, path_name , character(36)14, network_address , character(26)15, lock_owner , character(10)16, lock_status , short17, lock_date , integer18, revision_date , integer19, last_rev_index_no , short20, release_revision , character(2)21, release_date , integer22, checking_status , short , standard note 161023, standard_note_no_a , short , standard note 49924, standard_note_no_b , short , standard note 499

# Drawing View Data


1 , dwg_view_index_no , integer , index 12 , dwg_view_no , character(6) , index 23 , dwg_view_name , character(40)4 , dwg_view_scale , character(16)5 , dwg_index_no , integer6 , saved_view_name , character(6)7 , viewing_direction , short , standard note 16208 , composition_status , short , standard note 16309 , dwg_view_x_low , double10, dwg_view_y_low , double11, dwg_view_z_low , double12, dwg_view_x_high , double13, dwg_view_y_high , double14, dwg_view_z_high , double15, vhl_category_index , short16, drawing_view_type , short

# Drawing View Reference Model Data


1 , dwg_view_index_no , integer2 , model_index_no , integer

# Composite Drawing View Data


1 , comp_dwg_index_no , integer , index 12 , comp_dwg_view_no , character(6)3 , comp_dwg_view_name , character(40)

282

10. Draw

ing

M

anag

emen

t

Drawing Manager Setup________________ 4 , comp_dwg_v_scale , character(16)5 , dwg_index_no , integer6 , dwg_view_index_a , integer7 , dwg_view_index_b , integer8 , dwg_view_index_c , integer9 , dwg_view_index_d , integer10, dwg_view_index_e , integer11, dwg_view_index_f , integer12, dwg_view_index_g , integer13, dwg_view_index_h , integer14, dwg_view_index_i , integer15, dwg_view_index_j , integer

# Drawing Revision Data


1 , dwg_index_no , integer2 , revision_index_no , short3 , revision_no , character(2)4 , revision_date , integer5 , revision_by , character(4)6 , checked_by , character(4)7 , rev_description , character(40)

# Drawing Setup Data


1 , drawing_type , short , standard note 20002 , drawing_size , short , standard note 12023 , drawing_scale , character(16)4 , default_path_name , character(36)5 , default_node , character(26)6 , discipline_mask , short7 , alternate_seed_opt , short

# Reference Model Display Category Setup Data


1 , drawing_type , short , standard note 20002 , discipline_indx_no , short3 , category_mask_a , integer4 , category_mask_b , integer5 , category_mask_c , integer6 , category_mask_d , integer

# Plotting Default Data


1 , iplot_index_no , integer2 , iplot_number , character(24)3 , iplot_description , character(40)4 , iplot_file_spec , character(14)5 , path_name , character(36)6 , network_address , character(26)

283


10.2 Drawing Seed Data

The Project Data Manager is used to revise the seed data for a specified drawing or create areport of the RDB data. You can revise both 3D data and drawing data.

The Revise Drawing option is used to revise the seed data for a selected drawing file. Thesystem activates the following form which provides access to the modification options.

Select the option for the type of drawing data to be revised. The following report shows thedelivered settings for the Drawing Data.

284

10. Draw

ing

M

anag

emen

t



Drawing Category Data

Level

Drawing View Specific Labels 4

Drawing View Indentification Labels 5

Coordinate Labels 7

Dimensioning 9

Revision Triangles and Revision Clouds 10

Hold Clouds 11

Reports 8

Miscellaneous Drawing Graphics 3

Non-Plotted Drawing Graphics 12

Battery Limits 36

Matchlines 37

Centerlines 38

Dumb Details 39

Leader Lines for Dumb Details 40

Extension Lines for Dumb Details 41

Dimensions for Dumb Details 42

Coordinates for Dumb Details 43

Like Line No Labels 44

Like Equipment No Labels 45

User-defined drawing annotation category 11 46










Hidden Line Category for View Number 1 21















Dashed Hidden Line Category for View Number 1 13
















Drawing Graphic Symbology

Weight Colors Name

Revision Cloud 0 White

Flow Arrow 0 White FLOARR

Report 0 White

Dimension White

Miscellaneous Violet

285


Field Name for Nominal Piping Diameter

Symbol Font 50

Character Size for Report Undefined,Undefined

Line Spacing Factor 0.500000

Maximum Blank Line 3


Drawing Label Sizes

Text Height Text Width

1/16" 1/16"

1/8" 1/8"

1/4" 1/4"

5/16" 5/16"

3/8" 3/8"

1/2" 1/2"

5/8" 5/8"

11/16" 11/16"

7/8" 7/8"

3/4" 3/4"


Drawing Annotation

Line

Line Text Spacing

Category Weight Symbology Color Terminator Text Size Font Factor

Battery Limits 0 Solid White 1/4", 1/4" 0 0.0000

Matchlines 0 Solid White 1/4", 1/4" 0 0.0000

Centerlines 0 Solid White 1/4", 1/4" 0 0.0000

Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000

Leader Lines for Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000

Extension Lines for Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000

Dimensions for Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000

Coordinates for Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000

Like Line No Labels 0 Solid White 1/4", 1/4" 0 0.0000

Like Equipment No Labels 0 Solid White 1/4", 1/4" 0 0.0000

User-defined drawing annotation category 11 0 Solid White 1/4", 1/4" 0 0.0000











Drawing Hidden Line Symbology

Use Default Weight

Use User Defined Symbology

Use Default Color

Drawing View Weight Symbology Color

286

10. Draw

ing

M

anag

emen

t


Drawing View Number 1 N/A Medium Dash N/A















287


10.3 Using Labels in Drawings

The Label Description Library contains the definitions for all the labels used in the PDS 3Dmodules. Labels can be placed in the drawing as intelligent graphics with linkages to thedesign database. You can update existing drawing view specific labels to reflect the latestdata in the database.

A Label Description Library is delivered in the file win32app\pdshell\lib\labels.l. You canuse the Label Description Library Manager to edit the labels to suit the needs of yourproject.

10.3.1 Label Types

The following label types are used for annotation in drawings.

Displayable Attribute Labels

Each type of displayable attribute label has a description in the Label Description Library.This description identifies the label characteristics such as level, color code, style, and font,and the attribute data associated with the label.

A displayable attribute label consists of the text and optionally, a leader line, a line terminator,and some label enclosure graphics. This label type is further divided into the followingcategories.

Drawing View Specific Label

displayable attribute labels for named model items which are placed in a drawing.

Drawing View Identification Label

labels with attribute linkages to the Drawing View Data (table 122) that reportinformation about the drawing view such as drawing view name and view scale

Drawing View Specific Labels are further divided into subcategories for Piping, SMS,HVAC, and Raceways. Drawing View Specific Labels for Piping and View IndependentLabels are divided into sub-ranges for system-defined labels and user labels.

Alphanumeric Labels

Alphanumeric labels are non-intelligent user-defined labels. Each type of alphanumeric labelhas a description in the Label Description Library. This description identifies the labelcharacteristics such as level, color code, style, and font. An alphanumeric label consists of thetext and optionally, a leader line, a line terminator, and some label enclosure graphics.

288

10. Draw

ing

M

anag

emen

t

Using Labels in Drawings________________

Displayable Attribute Message

Each type of displayable attribute message has a description in the Label Description Library.Unlike the other label types, the description of a displayable attribute message only containsthe attribute data. Therefore, you cannot define label description data such as color, weight,style, and text size for a displayable attribute message.

A displayable attribute message has all or part of its text derived from the alphanumeric datathat is linked to a specified named item in the model.

A displayable attribute message is displayed temporarily at the terminal either as anidentification message or as a reporting message. Some of these messages are displayed inthe terminal’s refresh message fields. Other messages are displayed temporarily in the model.The system does not place any graphics in the model for this type of label.

A displayable attribute message can also be used to create a value for another attribute, forexample, the Line Number Label attribute.

289


10.3.2 Label Definition Data

The Label Description Library Manager is part of the Reference Data Manager. Thefollowing forms show the label definition data used to define the line number label.

10.3.3 Drawing View Specific Labels

Label 001 defines the label definition data used to place a line number label in a drawingview.

290

10. Draw

ing

M

anag

emen

t

Label Definition Data________________

10.3.4 Displayable Attribute Label

Label 310 defines the structure of the line number label.

291


292

Ind

ex

Index________________

Index 3D

coordinate systems 31seed data 160

Aaccessing

spec data 115activate

orientation tee 173active

P&ID 207placement point 188

alphanumericlabels 288

analyzedata 193

ASCII to binary conversion 272attribute 57

data 193

Bbase

form 158batch

job input file 273software organization 273

batch job input file 273interface job creation (jobctl.exe) 275ISOGEN 276ISOGEN interface 275plotting 276

batch job 28bend

deflection table 140binary conversion 272bolts

commodity code 260Eden data module 261length 259, 261roundoff 259

bordersdrawing 280

branchinsertion tables 140reinforcement equations 119

Ccategories

drawing 279cells 280clash

categories 228checking

design areas 216design area ownership of 219ownership 219precedence 228

client/server relationship 54close windows 153code list 58, 109column 57commands

fields 154status field 154window 154

commoditycode 122, 247, 260data 120item name table 138options 121specification data 96

componentmanipulation commands 174placement

examples 142overview 113

revision 192selection 138

conceptspiping graphics 187

connectpoint 96, 190

construction clash category 228control menu box 153conventions

forms 155piping materials class code 116reporting 246

coordinatesystem

design volume 43indicator 188

293

PDS 3D Theory — April 2002________________ coordinate (continued)

system (continued)plant 38

createlabel

attribute data 265, 290creating

3D models 145creation

commands 191

Ddatabase

column 57definition 59information 51, 57linkage 177requirements 195schemas 56table 57

ddl files 59design 73project 59reference 87

defaultdisplay levels 148

definecommands 174

definition data 231delivered reference data 92design

area 216clash checking 216pre-defined volume 217

volumecoordinate system 43

Design Review Integrator (PD_Review) 25diagrams

processand instrumentation 18flow 18

discrimination datafile 232record 233

displaylevels 147

displayable attributelabels 288message 289

drawingannotation 288

drawing (continued)borders 280categories 279manager

setup 279orthographic 277plot size table 280seed data 284

drwcats.txt 279

EEden

bolt data module 261flange data module 261modules 125parametric language 125

EE RWAY 24end preparation 121envelope 223

builder 223diagnostics 224verication

errors 224verifications 223

environmentgraphics 150

equipmentinterface 169manipulation commands 174models 164number and nozzle number 206seed data 165

errorfield 155

examplescomponent placement 142

extractingisometric drawings 269

Ffabrication category 124features

drawing 278field

fit length 260flanges

Eden data module 261flow

diagram process 18format file 237

output fields 241

294

Ind

ex

Index________________ format file (continued)

syntax 237column 239data_type 239field_functions 238field_len 239field_type 240row 239

formsbase 158conventions 155

FrameWorks Plus 20FW+ 20

Ggadgets

conventions 155gaskets 260

commodity name 261gap 120

genericphysical data 130tables 136

geometricindustry standard 123

graphiccommodity

data 106library

parametric shape definitions 132physical data definitions 128sub-symbol processor 127symbol processors 126

commodity library 124symbology 147

graphics 187environment 150

working in 151green connect point 96, 121

Hhard clash category 228HITS 272

IIDF 272IDM 19IF_Check 22implied

data 249items 256

implied (continued)items (continued)

labels 262types 256

material data 102input 224instrument

component specification data 99loops 19

instrument data manager 19instrumentation

diagrams (P&ID) 18interface

equipment modeling 169interference

checkerdesign area 216

pre-defined volume 217input 224output 225piping

design area 216piping design area

pre-defined volume 217project 216

detection 211management

clash categories 228interference checker

input 224report 225units 215

intermediate data file 272introduction

project organization 29ISOA_BGEN 272ISOGEN 272, 276

interface 271, 275isometric

drawings 269extraction 271

item name 121

Jjob creation 275JOBCTL.EXE 275jobctl.exe 275

Kkey-in

fields 155

295

PDS 3D Theory — April 2002________________ Llabel

descriptiondata management

create attribute data 265, 290library 109

label types 288descriptions 288types 288

alphanumeric labels 288displayable attribute

labels 288message 289

labels 262level

control 147license 28licenses 28lower windows 153

Mmaintaining report definition data 231material

descriptions 107, 246, 262reference database

structureimplied data 102instrument 99piping commodity 96piping materials class 94piping specialty 98size-dependent data 101tap properties 100

takeoff 252options 259

materialsgrade 123table 118

matingimplied

items 256labels 262material descriptions 262

maximizingwindows 153

menubar 154

messagefield 155

MicroStationcommand window 154

minimize windows 153miscellaneous

commands 174model

data 193review 193revise 178, 193

revision 192component 192piping 192segment vertex 192

model code 121model files 222modeling 145

setup 145modifier 123MTO 231, 252

options 259

Nname from P&ID 209network

traversal 272node numbers 204nominal piping diameter 117nongraphic outputs 272NPD 117

Ooption

code 121record 274

optional report type line 241options file 272orientation

tee 189activating 173

orienting the refresh tee 171orthographic drawings 277output

fields 241overview

component placement 113interactive isometric extraction 271, 272

ASCII to binary conversion 272Intergraph interface 271

Pparametric shape definitions 132parametrics 164

296

Ind

ex

Index________________ PD_Clash 22PD_Data 21PD_Design 21PD_Draw 22PD_EQP 20PD_ISO 23PD_ISOGEN 23pdisoplot 276PD_LICE 28PD_Report 23PD_Review 25PDS

licenses 28placement theory 113

PDS reporting modules 235pdsidf.exe 275PD_Stress 22PE-HVAC 24physical

data 128dimension data 135

P&ID 18commodity name 209correlation table 197data 208data comparison options 210data transfer 195

by equipment number and nozzle number 206correlation table 197database requirements 195unit number 195, 196update by node number 206update segment data 205

graphical data transfer 202node numbers 204unit number 195, 196update segment data 205

pipingassembly

library 110commodity

implied material data 102size-dependent material data 101specification data 96, 120

connect point 190diameter 117job specification 94

tables and functions 104materials class data 94, 115models 176revision 192

piping (continued)segments 187specialty

specification data 98PJS 94

tables and functions 104place

point 188placement

commands 191placing

components on segments 138plant

coordinate system 38plot

sizes 280plotting

isos 276positional units 35precedence

clash 228pressure 116primary axis 189primitives 164process

and instrumentation diagrams (P&ID) 18flow diagram 18

processing reports 235project

data managerrevise drawing 284revise equipment model 165

network environment 54organization 29, 215setup 26, 221

prompt field 155

RRDBMS 51red connect point 96, 121reference

datadelivered 92equipment 165overview 91

graphic commodity data 106label description library 109material description data 107piping assembly library 110piping job specification 94standard note library 109

297

PDS 3D Theory — April 2002________________ refresh

teeorienting 171

refresh graphics 187relational interface system (ris) 51report

datareport record 233

definition data 231discrimination data

file 232record 233

files 232format file 232, 237

syntax 237format record 232interference 225output 234processing 235record 233records 232report type line 241types 235

reporting 231material takeoff 252process 246

reportsinterference 225

reviewdata 193

revisedata 193drawing data 284equipment data 165model

graphics 192model data 178

material takeoff options 259RIS 51, 52

Ssample

report format files 242secondary

commands 175secondary axis 189seed data 146

3D 160drawing 284equipment 165piping 178

segmentpiping 187vertex 192

selectingcomponents 138

server/client relationship 54setup 221

2D project 263D project 26drawing 279project 26

sink box 154size-dependent material data 101soft clash category 228software

lease 28purchase 28

specaccess 115implied

items 256specialty

specification data 98specific

physical data 129tables 137

standard notelibrary 109

statusfield 154

sub-symbol processor 127symbol processors 126syntax

format file 237column 239data_type 239field_functions 238field_len 239field_type 240row 239

systemconfigurations 54prompt field 155

Ttable

access 124database 57implied items 256, 257suffix 122

298

Ind

ex

Index________________ tables

bend deflection 140bolt length 261branch insertions 140commodity item name 138

tapproperties data 100

temperature 116transfer

from P&ID 195type 63 data 146type report line 241typefaces 13types

reports 235

Uunderstanding

envelopes 223interference checking 224interferences 211report data 232

updateby node number 206segment data

from P&ID 205, 207

Vvalve

operator 123view 153volume filter 218volumes

clash checking 216

Wwall thickness 118

equations 119weight code 123windows

close 153control menu box 153, 154lower 153manipulations 153maximize 153MicroStation command 154minimize 153move 153restore 153size 153view 153

workingunits 35

working ingraphics 151three dimensions 31

299


300

Date post:	07-Nov-2014
Category:	Documents
Upload:	mallela-sampath-kumar
View:	117 times
Download:	1 times

3DTHEORY

Documents