PDS 3DTHEORY.pdf

(1)

PDS 3D Theory

User’s Guide

Document Number

Version

Date

Pages

DPDS3-PB-200010A

PDS 7.1

April 2002

1-300

DPDS3-PB-200010B

PDS 7.3

October 2004

Cover/Notice

DPDS3-PB-200010C

PDS 8.0 SE

November 2005

Cover/Notice

(2)

Copyright

Copyright © 1984-2005 Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audiovisual displays; may be used pursuant to

applicable software license agreement; contains confidential and proprietary information

of Intergraph and/or third parties which is protected by copyright law, trade secret law,

and international treaty, and may not be provided or otherwise made available without

proper authorization.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in

subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS

252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software

Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the

License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial

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

Unpublished---rights reserved under the copyright laws of the United States.

Intergraph Corporation

Huntsville, Alabama 35894-0001

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth

in your purchase contract, and nothing stated in, or implied by, this document or its

contents shall be considered or deemed a modification or amendment of such warranties.

Intergraph believes the information in this publication is accurate as of its publication

date.

The information and the software discussed in this document are subject to change

without notice and are subject to applicable technical product descriptions. Intergraph

Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or

copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on

equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF

THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO

THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Trademarks

Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools,

MARIAN, and PDS are registered trademarks of Intergraph Corporation. Microsoft and

Windows are registered trademarks of Microsoft Corporation. MicroStation is a

registered trademark of Bentley Systems, Inc. ISOGEN is a registered trademark of Alias

Limited. Other brands and product names are trademarks of their respective owners.

(3)

If You Need Assistance

________________

If You Need Assistance

Intergraph Online

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

Support

For the lasest Support Services information, use a World Wide Web browser to connect to

http://www.intergraph.com/ppo/services/support.asp.

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

http://www.intergraph.com.

Intergraph Directory

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

Intergraph General Information

All countries — 1-256-730-2000

Training Registration

1-800-766-7701 (U.S. Only) 1-256-730-5400 (Outside the U.S.)

Mailing Address

Intergraph Process, Power & Offshore 300 Intergraph Way

Madison, Alabama 35758 U.S.A.

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

(4)

________________

Documentation Contacts

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

Mail Intergraph Process, Power & Offshore Documentation Manager

300 Intergraph Way Madison, AL 35758

(5)

Table of Contents

________________

1.5.1 Working Units ... 35

1.5.2 Recommended Working Units - English ... 36

1.5.3 Recommended Working Units - Metric ... 36

1.5.4 Reasoning ... 37

1.5.5 3D Coordinate Systems ... 38

1.5.5.1 Plant Coordinate System ... 38

1.5.6 Design Volume Coordinate System ... 43

1.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) ... 52

2.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 ... 58 2.3.1.2 Code-Listed Attributes ... 58

2.4 Database Definition Files ... 59

2.4.1 Project Control Database ... 59

2.4.2 Design Database ... 73

2.4.3 Reference Database ... 87

3. Reference Data ... 91

3.1 Piping Job Specification ... 94

3.1.1 Piping Materials Class Data ... 94

3.1.2 Piping Commodity Specification Data ... 96

3.1.2.1 Connect Point Data ... 96

3.1.3 Piping Specialty Specification Data ... 98

3.1.4 Instrument Component Specification Data ... 99

3.1.5 Tap Properties Data ... 100

3.1.6 Piping Commodity Size-Dependent Material Data ... 101

3.1.7 Piping Commodity Implied Material Data ... 102

(7)

Table of Contents

________________

3.2 Graphic Commodity Data and Physical Dimension Data ... 106

3.3 Material Description Data ... 107

3.4 Standard Note Library ... 109

3.5 Label Description Library ... 109

3.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 ... 115

4.1.2 Piping Materials Class Data ... 115

4.1.3 Piping Commodity Data ... 120

4.1.4 Table Access ... 124

4.1.5 Symbol Processors ... 126

4.1.6 Sub-Symbol Processor ... 127

4.1.7 Physical Data Definitions ... 128

4.1.8 Parametric Shape Definitions ... 132

4.1.9 Physical Data ... 135

4.1.9.1 Generic Tables ... 136

4.1.9.2 Specific Tables ... 137

4.2 Placing Components On Existing Segments ... 138

4.2.1 Commodity Item Name Table ... 138

4.2.2 Bend Deflection Table ... 140

4.2.3 Branch Insertion Tables ... 140

4.2.4 Placement Examples ... 142

5. Creating 3D Models ... 145

5.1 Modeling Setup Requirements ... 145

5.1.1 Project Setup ... 145

5.1.2 Reference Data Setup ... 146

5.1.3 Seed Files ... 146

5.1.4 Model Files ... 147

5.1.5 Level Control and Graphical Symbology ... 147

5.1.6 Level and Symbology Defaults ... 148

5.2 Graphics Environment for PDS 3D ... 150

5.2.1 Working with the Graphical User Interface ... 151

5.2.2 Common Tools on Forms ... 157

5.2.2.1 Base Form ... 158

5.2.3 3D Seed Data ... 160

(8)

________________

5.3 Creating Equipment Models ... 164

5.3.1 Functions of PDS Equipment Modeling (PD_EQP) ... 164

5.3.2 About the Reference Database (RDB) ... 165

5.3.3 Equipment Model Seed Data ... 165

5.3.4 Equipment Modeling Environment ... 169

5.3.5 Equipment Modeling Concepts ... 171

5.3.6 Activating the Orientation Tee ... 173

5.4 Equipment Modeling Commands ... 174

5.4.1 Equipment Manipulation Commands ... 174

5.4.2 Component Manipulation Commands ... 174

5.4.3 Nozzle Manipulation ... 174

5.4.4 Review/Revise Commands ... 174

5.4.5 Define Commands ... 174

5.4.6 Miscellaneous Commands ... 174

5.4.7 Secondary Commands ... 175

5.5 Creating Piping Models ... 176

5.5.1 Piping Model Seed Data ... 178

5.5.2 Graphic Concepts for Piping Design ... 187

5.5.2.1 Piping Segments ... 187

5.5.2.2 Active Placement Point ... 188

5.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 ... 191

5.6.2 Revision Commands ... 192

5.6.3 Component Revision ... 192

5.6.4 Segment Vertex Commands ... 192

5.6.5 Piping Revision ... 192

5.6.6 Model Data ... 193

5.6.7 Review Data ... 193

5.6.8 Revise Data ... 193

5.6.9 Analyze Data ... 193

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

6.1 Database Requirements ... 195

6.2 P&ID Correlation Table ... 197

6.3 P&ID Graphical Data Transfer Setup ... 202

(9)

Table of Contents

________________

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

6.5.1 Update by Node Number ... 206

6.5.2 Transfer by Equipment Number and Nozzle Number ... 206

6.5.3 Update From Active P&I Drawing ... 207

6.6 P&ID Data ... 208

6.7 Name From P&ID ... 209

6.8 P&ID Data Comparison Options ... 210

7. Detecting and Managing Interferences ... 211

7.1 Interference Checking Process Overview ... 211

7.2 Project Organization ... 215

7.2.1 Understanding Design Areas and Volumes ... 216

7.3 Setting Up a System to Support Interference Detection ... 221

7.4 Understanding Interference Envelopes ... 223

7.4.1 Understanding Interference Checking ... 224

7.4.2 Understanding Interference Plotting ... 230

7.4.3 Understanding Interference Reporting ... 230

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

8.1 Reporting Process ... 231

8.2 Maintaining Report Definition Data ... 231

8.2.1 Understanding Report Files and Records ... 232

8.2.1.1 Format File ... 232

8.2.1.2 Discrimination Data File ... 232

8.2.1.3 Report Record ... 233

8.2.1.4 Report Output ... 234

8.3 Processing Reports ... 235

8.4 Report Types ... 235

8.5 Report Format File ... 237

8.5.1 Format File Syntax ... 237

8.5.2 Definitions ... 238

8.5.3 Output Fields ... 241

8.5.4 Sample Format Files ... 242

8.6 What Happens When I Report On a Component? ... 246

8.7 Material Takeoff Reporting (Report Manager) ... 252

8.8 Understanding Implied Items ... 256

(10)

________________

8.8.1 Mating Implied Items ... 256

8.8.2 ’*’ Spec Implied Items ... 256

8.8.3 ’+’ Table Implied Items ... 257

8.9 Material Takeoff Options ... 259

8.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 ... 271

9.1.2 ASCII to Binary Conversion ... 272

9.1.3 ISOGEN ... 272

9.2 Batch Software Organization ... 273

9.2.1 The Batch Job Input File ... 273

9.2.2 Line Processing (pdsidf) ... 275

9.2.3 The ISOGEN Interface ... 275

9.2.4 ISOGEN ... 276

9.2.5 Plotting ... 276

10. Creating Orthographic Drawings ... 277

10.1 Drawing Manager Setup ... 279

10.2 Drawing Seed Data ... 284

10.3 Using Labels in Drawings ... 288

10.3.1 Label Types ... 288

10.3.2 Label Definition Data ... 290

10.3.3 Drawing View Specific Labels ... 290

10.3.4 Displayable Attribute Label ... 291

(11)

Preface

________________

Preface

This PDS 3D Theory Users Guide is designed as an aid for students attending the PDS 3D Theory Class presented by Intergraph Corporation Education Center and is a supplement to the standard product documentation. 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 describes information 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

(12)

________________

Chapter 7 - Detecting and Managing Interferences

Chapter 8 - Creating Material Takeoffs and Other Reports

Chapter 9 - Extracting Isometric Drawings

(13)

Preface

________________

General Conventions

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

Typefaces

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

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Command paths are shown using an arrow between command names. For example, Choose File > Open to load a new file.

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

Select first segment of alignment

Bold Typewriter

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

Normal Typewriter

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

(14)

________________

Symbols

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

<C> Command button

<D> Data button (usually the left mouse button)

<R> Reset/reject button (usually the right mouse button) <T> Tentative button (usually the center mouse button)

Note — Important supplemental information.

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

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

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

More information — indicates there is additional or related information.

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

Keyboard Conventions

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

ALT Alternate key

CTRL Control key

DEL Delete key

ENTER Enter key

ESC Escape key

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

(15)

Preface

________________

Terminology

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

Click Apply to save the changes.

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

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

example,

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

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

Select the line string to define the graphic template.

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

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

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

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

Type To key a character string into a text box.

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

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

(16)

(17)

1. PDS Overview

What is the Plant Design System?

________________

1. What is the Plant Design

System?

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

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

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

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

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

flow diagrams.

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

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

(18)

________________

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 build the plant. All of the needed data is stored in databases. These are relational databases which you 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 includes feasibility studies, cost estimates, and process simulations. Third-party process simulation packages such as ASPEN or SimSci allow engineers to perform preliminary calculations such as chemical equilibriums, reactions, heat and material balances and/or design pressures and temperatures. The data produced from these calculations are transferred to PDS where a process flow diagram (PFD) is developed.

1.1.2 Process & Instrumentation Diagram (P&ID)

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

The P&IDs display the overall process in much greater detail than the PFD. The P&ID shows all piping, instrumentation, and controls associated with a particular 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 and assigns tag numbers to each instrument item. The P&ID reflects the overall process control through either distributive control systems (DCS), programmable logic controllers (PLC), or stand-alone controller philosophy.

When doing propagation (taking graphic information from the drawing and writing it to the database), the drawing is checked for conformance to design rules and the drawing

(19)

1. PDS Overview

What are the 2D modules?

________________

1.1.3 Instruments and Instrument Loops

After the P&ID defines the process controls, the instruments must be defined with all of the individual data values. The Instrument Data Manager (IDM) is the database that maintains an entry for each instrument in a project.

(20)

________________

1.2 What are the 3D modules?

PDS 3D is used to create three-dimensional plant models, create equipment models, extract isometric drawings, and perform design interference checks and equipment clashes. As with the 2D modules, all of the needed data is stored in relational databases which can be queried or 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 to model the equipment defined in the P&ID.

Stylistic representations of equipment items are produced, with or without nozzles, by entering data from equipment data sheets noting dimensions and weights. Upon completion, the equipment item is placed in the 3D model.

Within PD_EQP, designers can create a physical envelope defining the space occupied by an equipment item along with space envelopes defining maintenance and access areas. This process is instrumental for interference checking later in the modeling process.

1.2.2 FrameWorks Plus (FWP)

Structures must be designed to carry the loads from piping, equipment, personnel and other factors to the ground. FrameWorks Plus is used to layout structural frames, foundations, slabs and walls. Piping designers, equipment modelers and structural designers, by sharing reference files, can see the location of each other’s objects. The structural engineer referencing other models can place loads in the 3D model, and apply other

analytical characteristics to use with a third-party analysis solver. After a design run, the new cross section

properties can be read back into the model to

automatically update all the associated symbolized 2D drawings.

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

(21)

1. PDS Overview

________________

1.2.3 Piping Design Graphics (PD_Design)

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

When placing the instruments and valves, designers take into account pipeline flexibility, method of construction, and ease of access for maintenance and operations. Designers can route pipe in the 3D model as a centerline representation; moreover, a 3D shaded model can be displayed when necessary. The centerline is intelligent and contains all the information relating to a pipeline, such as the piping material class, nominal diameter, fluid code, insulation parameters, temperatures and pressures, and so forth.

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

A pipeline can be connected to a specific nozzle or routed from a point in space. Components such as valves, instruments and branches can be placed on the pipeline as it is routed. Values for 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 ensure matching or compatible diameters, pressure ratings, end preparations, and other consistency criteria. Pipe supports can be modeled giving either a detailed space envelope or a logical representation 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 the selection criteria for the piping commodity items found in the piping job specification and piping commodity libraries delivered with the product. This data is contained in the RDB and can be used by other projects.

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

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

(22)

________________

1.2.5 Drawing Manager (PD_Draw)

Designers use the Drawing Manager (PD_Draw) product to create and/or revise orthographic production drawings. PD_Draw can be used with other PDS 3D products to place annotation labels identifying intelligent items and model coordinates, to plot the drawings, and to produce reports for drawings and model 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 equipment models for stress analysis. PD_Stress interfaces to a number of commercial packages which accept ASCII format.

1.2.7 Interference Checker/Manager (PD_Clash)

Interference Checker/Manager (PD_Clash) creates envelope files for all models in the specified project, design area, or for individual models which have an envelope builder specific to each discipline in the Interference Checker/Manager. It also collects envelope data for the models that have envelope files which were previously created by one of the other PDS modules. The checker/manager processes the specified design volume and identifies all of the interference clashes.

(23)

1. PDS Overview

________________

It then produces reports which allow the designer to review interferences and review and/or revise the approval status of the interferences. The software places graphical markers for the project, 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 extract isometric drawings from the plant model, either interactively or through a batch process. The interactive extraction can be used for testing the interface and verifying a specific pipeline. Batch generation of isometrics is used for generating production drawings on a project. With either function, a bill of materials is automatically generated and attached to the isometric drawing. An optional MTO file can be generated which can be printed or used as input to a material control system.

1.2.9 Report Manager (PD_Report)

Material take-off reports (MTOs) can be generated on piping and equipment models through PD_Report. The MTO process generates reports by using the graphical data in the specified models to refer to the Design Database, Reference Database, Project Database, and Material Description Libraries for the data on which to report. This data includes implied materials, such as bolts, gaskets, and welds, that are not represented in the model but are

necessary for the specified connectivity.

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

(24)

________________

1.2.10 Project Engineer HVAC (PE-HVAC)

PE-HVAC allows designers to place fittings and devices while laying out duct routes. You can define the active parameters for duct characteristics such as width, depth, shape, material, construction status, and service.

1.2.11 EE Raceway Modeling

Electrical Engineer Raceway Modeling (EERWAY) is specification-driven software which allows designers to extract data from the RDB and create 3D models of cable trays, conduits, wire ways, underground duct banks, and cable trenches. These models can be created using the centerline and/or 3-line component graphics. With these 3D models, you can create interference envelopes and run interference detection, produce MTOs, and extract raceway drawings.

(25)

1. PDS Overview

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 review the design and alphanumeric data.

Engineering data such as instrument numbers, equipment numbers, line numbers, and line sizes 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 the

responsible designer’s actions.

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

(26)

________________

1.3 Project Setup

Before work can begin on a project, extensive system setup needs to be completed. The following outlines the basic flow for initial system setup and project creation. This system and 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. A PDS 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 to access files on the server for processing on the client workstations.

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

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 popular Relational Database Management Systems, such as Informix, Oracle, and Ingres.

(27)

1. PDS Overview

Project Setup

________________

1.3.2 2D Setup

The PDS2D product is the base platform loaded on each workstation that will be using PDS 2D 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 with the client option to access software on a product server or installed locally. PDS2D allows you to perform project administrative functions such as establish and modify reference data files, 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 the database files have been created, you can access the 2D environment to create units and

drawings for the project. Units are logical divisions of the schematic world of a plant.

(28)

________________

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 or installed 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 Project

Administrator 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 3D modeling applications (such as Piping, Equipment, and HVAC). A design area represents a specific portion of the project for a given discipline. Each design area comprises a set of models 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 licensing information for all PDS products in a network. Though the licensing information can be on a single server, the licenses themselves float, that is, they can be used by any workstation in the network. Both the client machine and license server must have PD_LICE installed. Any machine can be a license server; the licensing has little impact on workstation/server performance.

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

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

(29)

1. PDS Overview

Project Organization

________________

1.4 Project Organization

Since a process plant such as a refinery can be extremely large, PDS uses the following organization to break the plant into smaller pieces that can be handled more easily. A PDS project is comprised of the items that constitute a plant, or the portion of the plant being modified. The project is the fundamental structure for working in PDS. Each project contains all the information required to work in a PDS task.

A 3D project is divided into design areas by discipline. Disciplines represent the various categories of 3D modeling data such as Piping, Equipment, and Structural. A design area represents a specific volume or logical area of the project for a given discipline. Design areas are 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. Although the illustration above shows only piping areas, each discipline is free to define its areas independently of all other disciplines. The location of a model and the details of the Design Volume Coordinate System are specified as seed data in the model definition. The model is created 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 as Piping Design, Equipment Modeling, Raceway, FrameWorks Plus, respectively. For example, 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 the Plant Monument (PM) or it may be constructed with respect to a local or auxiliary point of reference, known as the Design Volume Monument (DVM). The use of the DVM in PDS is analagous to the use of an Auxiliary Coordinate System (ACS) in MicroStation or a secondary coordinate system in other CAD software systems.

(30)

________________

For most PDS projects, the PM corresponds to a survey benchmark or some well known immovable landmark at the plant site from which measurements can be made. The DVM may also correspond to a benchmark or well known point, but it usually differs from one

corresponding to the BM. For instance, if it is convenient to route piping in an out-building with respect to the southwest corner of the building, then that corner of the building may be designated as the DVM so that specifying locations within the building during the design process may be more convenient. In either case, PDS always knows how to cross-convert from the two coordinate systems, so both systems may be used interchangeably for the purposes 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 access all the data for a single model (independently of the other project data) for the purpose of creating or modifying information. However, you can also perform interference checking and create 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 3D projects. Each project consists of a project control database, design database, piping and equipment models, reference models (structural, HVAC, and raceway), a set of drawings, and a collection of reference data. The reference data may be specific to one project or shared by more than one project.

(31)

1. PDS Overview

Working in Three Dimensions

________________

1.5 Working in Three Dimensions

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

PDS drawings are also created in three dimensions. However, all the graphics you draw lie on a 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 only height and width).

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

(32)

________________

All graphic elements must be placed in the design cube. The design cube is a volume of three-dimensional space you can think of as being inside the display terminal (as depicted by the 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 design cube from any angle.

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

(33)

1. PDS Overview

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 isometric views 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 an apparent angle of 30°. Actually, the view is rotated 45° in two directions: the cube is displayed from the top front right.

(34)

________________

When a three-dimensional component is drawn or placed in the design cube, you are able to see 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 from the top such that the y axis is up, the x axis is to the right, and the z axis out (toward you), as shown below.

(35)

1. PDS Overview

Working Units

________________

1.5.1 Working Units

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

For interference checking and reference models to work properly, any changes to 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). Working units relate UORs to a measurement unit such as feet or meters and define how these units are divided. The total units of resolution are divided into master units, sub units, and positional units (MU:SU:PU) which define the number of addressable points and thereby the precision of operations. The following outlines the standard working unit definitions for PDS.

(36)

________________

1.5.2 Recommended Working Units - English

File MU SU PU Area

Models (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 Area

Models 1 M 1000 MM 80 53687 M

(37)

1. PDS Overview

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 area of 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 as long as the total UORs per master unit are the same. Therefore the English units can be converted to metric units to create compatible models.

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

.3048

24384

______ = 80000 UORs per meter

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

The recommended English (2032) and metric (80) values allow a file created using the English system to be viewed and edited in metric mode without scaling or altering data. The positional units for drawings should be defined so that the drawing has the same resolution as the model. To maintain the same resolution, the smallest drawing view scale is used so that the PUs of the drawing file are no less than the maximum factor times the PUs used in the model.

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 the drawing units.

1/8 12 ____ = 96 2032 x 96 = 195072

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

(38)

________________

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 uses Easting, 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 plant monument defines the Easting, Northing, and Elevation coordinates to be assigned to the center of the MicroStation design volume. The following form, found in Project Data

Manager, is used to specify the Easting, Northing, and Elevation values of the plant

monument.

(39)

1. PDS Overview

3D Coordinate Systems

________________

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

(40)

________________

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 the design cube, you can divide 176,135.75’ by 2 to determine the extents of the Plant Coordinate System. The maximum Easting, Northing, and Westing, Southing, Up, or Down coordinate is 88,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 seed files or models. In general, this is also not necessary for other disciplines’ seed or design files. Only if it appears that there will not be enough design plane to contain all graphics (such as may be the case for large material-conveying systems spanning several miles) should you even consider a global origin change. It would always be a good idea to consult a PDS Support contact before making such a change.

If only positive Easting, Northing, and Westing values are entered, and the default plant monument values were accepted, you are restricted to using only half of the available design volume. To work within the contraints of positive Easting and Northing values and still use the entire design cube, you must modify the Easting and Northing values of the plant

(41)

1. PDS Overview

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 the graphic component, but it stays the same in relation to the component.

(42)

________________

The graphic below shows a plant model with preliminary piping and equipment. The front of the plant is seen in the front view, the top of the plant in the top view, and so forth. The coordinate system stays the same in relation to the design. Looking at each view, however, gives you a different perspective of the coordinate system.

(43)

1. PDS Overview

Design Volume Coordinate System

________________

1.5.6 Design Volume Coordinate System

The Design Volume Coordinate System (DVCS) is a second coordinate system (in addition to the Plant Coordinate System) that can be defined for an individual model. A DVCS is only required if different models need to have their coordinates referenced from a different point; it is 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 the model.

You can select from two orientations (or use the Other button to select the preferred degree value) 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.

(44)

________________

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

(45)

1. PDS Overview

Examples

________________

1.5.7 Examples

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

(46)

(47)

1. PDS Overview

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 shown below, the design volume monument would be located at 350, 325, 0, and it would be rotated 350 degrees (clockwise) from Plant North.

(48)

________________

If a plant consisted of 3 buildings within a 33.3-mile range, with each building at a different angle than the other two, then the files might be defined as follows:

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

While placing components in Building 1, the user might prefer to enter values relative to the SW corner of the building, rather than entering the large values associated with the Plant Coordinate system. To do this, the project administrator should create a model with a Design Volume Monument located at the SW corner. In Plant Coordinate System, this coordinate would be Easting -60,000 (Westing 60,000), Northing -75,000 (Southing 75,000), and Elevation 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 of viewing and entering coordinates using the Design Volume Coordinate System or the Plant Coordinate System.

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

(49)

1. PDS Overview

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 to the PCS.

(50)

________________

Building 3

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

(51)

2. Database

Overview

Database Overview

________________

2. Database Overview

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

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 a relational 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 PDS products attach to the relational databases through Intergraph Corporation’s Relational Interface System (RIS). RIS is a generic relational database interface that isolates the SQL interface differences in specific vendors’ relational database management systems (RDBMSs). It provides a generic networked access to all databases generated with popular RDBMSs supported by RIS, including Informix (both Standard Engine and On-line), Oracle, and Sybase.

(52)

________________

2.1 PDS and the Relational Interface

System (RIS)

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

Users are established for different RDBMSs in different ways; in fact, the concept of a

database differs greatly from one RDBMS to another. The various interfaces provided in

PDS let you maintain databases through RIS efficiently, without requiring you to know the differences between RDBMSs or the syntax of the RIS create schema statement.

RIS works in conjunction with existing databases. You must have RIS implemented on your network 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 at the System Manager level. The System Manager should be familiar with the theory and practice of the Relational Interface System to be successful. See the Relational Interface

System (RIS) Reference Manual for full information.

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

(53)

2. Database

Overview

Database Overview

________________

2D RIS Overview

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

(54)

________________

2.2 PDS System Configurations

This section describes the configuration options for PDS. PDS can be implemented on a network 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 and server nodes. Client nodes can be Intergraph Clipper workstations, or Intel workstations running Windows NT workstation software.

Server nodes can be Intergraph Clipper servers or multi-processor type Intel servers running Windows 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 and stored on this machine.

Software Server

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

(55)

2. Database

Overview

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 duties or distribute them among multiple machines.

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

(56)

________________

2.3 PDS 3D Databases

(57)

2. Database

Overview

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 project environment files. A 3D project is divided into design areas by disciplines. Disciplines represent the various 3D modeling applications (such as Piping, Equipment, and HVAC). A design area represents a specific volume of the project for a given discipline. Each design area 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. The PDS 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 Piping Commodity Data table.

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

(58)

________________

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 selections from 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 line following 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 Note 125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 for chlorine 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]

(59)

2. Database

Overview

Database Definition Files

________________

2.4 Database Definition Files

This section lists the delivered database definition (ddl) files for Workstation PDS. These files 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 them to 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 , integer 2 , 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 , short 2 , approval_status , short 3 , rdb_file_spec , character(14) 4 , path_name , character(36) 5 , network_address , character(26) 6 , lock_owner , character(10) 7 , lock_status , short 8 , lock_date , integer 9 , revision_date , integer ################################################### # Project Control Data

table number = 103 , number of columns = 39

(60)

________________

1 , product_version_no , short 2 , 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 1605 31, mdl_status_high_dr , short , standard note 1605 32, mdl_status_low_ic , short , standard note 1605 33, mdl_status_high_ic , short , standard note 1605 34, area_owner_opt_ic , short 35, eqp_insul_opt_ic , short 36, eqp_con_tol_opt_ic , short 37, clash_rpt_index_no , integer 38, report_search_path , character(36) 39, report_search_node , character(26) ################################################### # Project Archival Management Data

table number = 104, number of columns = 10 1 , archival_index_no , integer 2 , 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 , integer 8 , day_of_week_map , integer 9 , day_map , integer 10, time_of_day , integer ################################################### # Model Management Data

(61)

2. Database

Overview

Database Definition Files

________________

# Engineering Discipline Data

table number = 111 , number of columns = 5 1 , discipline_indx_no , short

2 , discipline_name , character(20) 3 , intra_disc_ifc_flg , short

4 , discipline_mtrx_a, integer 5 , discipline_mtrx_b, integer # Design Area Data

table number = 112 , number of columns = 15 1 , discipline_indx_no , short 2 , area_index_no , short 3 , area_name , character(10) 4 , area_description , character(40) 5 , volume_low_x , integer 6 , volume_low_y , integer 7 , volume_low_z , integer 8 , volume_high_x , integer 9 , volume_high_y , integer 10, volume_high_z , integer 11, interference_mode , short 12, area_lock_owner , character(10) 13, area_lock_status , short 14, area_lock_date , integer 15, clash_rpt_index_no , integer # Model Data

table number = 113 , number of columns = 17

1 , model_index_no , integer , index 1 2 , discipline_indx_no , short 3 , area_index_no , short 4 , partition_no , short 5 , 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 , short 12, lock_date , integer 13, verification_date , integer 14, revision_date , integer 15, responsible_disc , short 16, model_type , short

17, model_status , short , standard note 1605 # Piping Model Data

table number = 114 , number of columns = 6 1 , partition_no , short

2 , max_segment_number , integer 3 , max_piping_number , integer