80524076-PDS-3dtheory

Users GuidePDS 3D Theory

May 1996

DEA506430SE**006 SE**151 SE**226 (06.00.00.00)

This is a new document, replacing DEA506420.

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 1996 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

Table of Contents________________

Table of Contents

Preface ................................................................................................................................................. vii

Related Products ................................................................................................................... viiDocument Organization ........................................................................................................ vii

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

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

1.1.1 Process Flow Diagram (PFD) ................................................................................. 21.1.2 Process & Instrumentation Diagram (P&ID) .......................................................... 21.1.3 Instruments and Instrument Loops .......................................................................... 3

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

1.2.1 Equipment Modeling (PD_EQP) ............................................................................ 41.2.2 FrameWorks Plus (FWP) ........................................................................................ 41.2.3 Piping Design Graphics (PD_Design) .................................................................... 51.2.4 Reference Data Manager (PD_Data) ....................................................................... 51.2.5 Drawing Manager (PD_Draw) ................................................................................ 61.2.6 PDS Stress Analysis Interface (PD_Stress) ............................................................ 61.2.7 Interference Checker/Manager (PD_Clash) ............................................................ 61.2.8 PDS Isometric Interface (PD_ISO, PD_ISOGEN) ................................................. 71.2.9 Report Manager (PD_Report) ................................................................................. 71.2.10 Project Engineer HVAC (PE-HVAC) ................................................................... 81.2.11 EE Raceway Modeling .......................................................................................... 81.2.12 Design Review Integrator (PD_Review) ............................................................... 9

1.3 Project Setup ....................................................................................................................... 10

1.3.1 System Setup ........................................................................................................... 101.3.2 2D Setup .................................................................................................................. 111.3.3 3D Setup .................................................................................................................. 121.3.4 About licensing ....................................................................................................... 12

1.4 Project Organization ............................................................................................................ 131.5 Working in Three Dimensions ............................................................................................ 15

1.5.1 Working Units ......................................................................................................... 191.5.2 Recommended Working Units - English ................................................................ 201.5.3 Recommended Working Units - Metric .................................................................. 201.5.4 Reasoning ................................................................................................................ 211.5.5 3D Coordinate Systems ........................................................................................... 22

i

PDS 3D Theory May 1996________________

1.5.5.1 Plant Coordinate System .......................................................................... 22

1.5.6 Design Volume Coordinate System ........................................................................ 271.5.7 Examples ................................................................................................................. 29

1.5.7.1 DVCS Oriented From Plant North ........................................................... 31

2. Database Overview ...................................................................................................................... 35

2.1 PDS and the Relational Interface System (RIS) ................................................................. 362.2 PDS System Configurations ................................................................................................ 38

2.2.1 Client/Server Relationship ...................................................................................... 38

2.3 PDS 3D Databases .............................................................................................................. 40

2.3.1 Database Information .............................................................................................. 41

2.3.1.1 Attribute Types ......................................................................................... 422.3.1.2 Code-Listed Attributes ............................................................................. 42

2.4 Database Definition Files .................................................................................................... 43

2.4.1 Project Control Database ......................................................................................... 432.4.2 Design Database ...................................................................................................... 572.4.3 Reference Database ................................................................................................. 71

3. Reference Data ............................................................................................................................. 75

3.1 Piping Job Specification ...................................................................................................... 78

3.1.1 Piping Materials Class Data .................................................................................... 783.1.2 Piping Commodity Specification Data ................................................................... 80

3.1.2.1 Connect Point Data .................................................................................. 80

3.1.3 Piping Specialty Specification Data ........................................................................ 823.1.4 Instrument Component Specification Data ............................................................. 833.1.5 Tap Properties Data ................................................................................................. 843.1.6 Piping Commodity Size-Dependent Material Data ................................................. 853.1.7 Piping Commodity Implied Material Data .............................................................. 863.1.8 PJS Tables and Functions ....................................................................................... 88

3.2 Graphic Commodity Data and Physical Dimension Data ................................................... 903.3 Material Description Data ................................................................................................... 913.4 Standard Note Library ......................................................................................................... 933.5 Label Description Library ................................................................................................... 933.6 Piping Assembly Library .................................................................................................... 94

ii


4. How PDS Works .......................................................................................................................... 97

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

4.1.1 Spec Access ............................................................................................................. 994.1.2 Piping Materials Class Data .................................................................................... 994.1.3 Piping Commodity Data .......................................................................................... 1044.1.4 Table Access ........................................................................................................... 1084.1.5 Symbol Processors .................................................................................................. 1104.1.6 Sub-Symbol Processor ............................................................................................ 1114.1.7 Physical Data Definitions ........................................................................................ 1124.1.8 Parametric Shape Definitions .................................................................................. 1164.1.9 Physical Data ........................................................................................................... 119

4.1.9.1 Generic Tables ......................................................................................... 1204.1.9.2 Specific Tables ......................................................................................... 121

4.2 Placing Components On Existing Segments ....................................................................... 122

4.2.1 Commodity Item Name Table ................................................................................. 1224.2.2 Bend Deflection Table ............................................................................................ 1244.2.3 Branch Insertion Tables .......................................................................................... 1244.2.4 Placement Examples ............................................................................................... 126

5. Creating 3D Models ..................................................................................................................... 129

5.1 Modeling Setup Requirements ............................................................................................ 129

5.1.1 Project Setup ........................................................................................................... 1295.1.2 Reference Data Setup .............................................................................................. 1305.1.3 Seed Files ................................................................................................................ 1305.1.4 Model Files ............................................................................................................. 1315.1.5 Level Control and Graphical Symbology ............................................................... 1315.1.6 Level and Symbology Defaults ............................................................................... 132

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

5.2.1 Working with the Graphical User Interface ............................................................ 1355.2.2 Common Tools on Forms ....................................................................................... 141

5.2.2.1 Base Form ................................................................................................ 142

5.2.3 3D Seed Data ........................................................................................................... 144

5.3 Creating Equipment Models ............................................................................................... 148

5.3.1 Functions of PDS Equipment Modeling (PD_EQP) ............................................... 1485.3.2 About the Reference Database (RDB) .................................................................... 1495.3.3 Equipment Model Seed Data .................................................................................. 1495.3.4 Equipment Modeling Environment ......................................................................... 153

iii

PDS 3D Theory May 1996________________

5.3.5 Equipment Modeling Concepts ............................................................................... 1555.3.6 Activating the Orientation Tee ................................................................................ 157

5.4 Equipment Modeling Commands ....................................................................................... 158

5.4.1 Equipment Manipulation Commands ..................................................................... 1585.4.2 Component Manipulation Commands .................................................................... 1585.4.3 Nozzle Manipulation ............................................................................................... 1585.4.4 Review/Revise Commands ..................................................................................... 1585.4.5 Define Commands ................................................................................................... 1585.4.6 Miscellaneous Commands ...................................................................................... 1585.4.7 Secondary Commands ............................................................................................. 159

5.5 Creating Piping Models ...................................................................................................... 160

5.5.1 Piping Model Seed Data .......................................................................................... 1625.5.2 Graphic Concepts for Piping Design ....................................................................... 171

5.5.2.1 Piping Segments ....................................................................................... 1715.5.2.2 Active Placement Point ............................................................................ 1725.5.2.3 Coordinate System Indicator and Orientation Tee ................................... 172

5.5.3 Orientation Tee ........................................................................................................ 173

5.5.3.1 Piping Connect Points .............................................................................. 174

5.6 Piping Design Commands ................................................................................................... 175

5.6.1 Placement Commands ............................................................................................. 1755.6.2 Revision Commands ............................................................................................... 1765.6.3 Component Revision ............................................................................................... 1765.6.4 Segment Vertex Commands .................................................................................... 1765.6.5 Piping Revision ....................................................................................................... 1765.6.6 Model Data .............................................................................................................. 1775.6.7 Review Data ............................................................................................................ 1775.6.8 Revise Data ............................................................................................................. 1775.6.9 Analyze Data ........................................................................................................... 177

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

6.1 Database Requirements ....................................................................................................... 1796.2 P&ID Correlation Table ...................................................................................................... 1816.3 P&ID Graphical Data Transfer Setup ................................................................................. 1866.4 P&ID Node Numbers .......................................................................................................... 1886.5 Update Segment Data from P&ID ...................................................................................... 189

6.5.1 Update by Node Number ........................................................................................ 1906.5.2 Transfer by Equipment Number and Nozzle Number ............................................ 1906.5.3 Update From Active P&I Drawing ......................................................................... 191

iv


6.6 P&ID Data ........................................................................................................................... 1926.7 Name From P&ID ............................................................................................................... 1936.8 P&ID Data Comparison Options ........................................................................................ 194

7. Detecting and Managing Interferences ........................................................................................ 195

7.1 Interference Checking Process Overview ........................................................................... 1957.2 Project Organization ............................................................................................................ 199

7.2.1 Understanding Design Areas and Volumes ............................................................ 200

7.3 Setting Up a System to Support Interference Detection ..................................................... 2057.4 Understanding Interference Envelopes ............................................................................... 207

7.4.1 Understanding Interference Checking ..................................................................... 2087.4.2 Understanding Interference Plotting ....................................................................... 2147.4.3 Understanding Interference Reporting .................................................................... 214

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

8.1 Reporting Process ................................................................................................................ 2158.2 Maintaining Report Definition Data ................................................................................... 215

8.2.1 Understanding Report Files and Records ................................................................ 216

8.2.1.1 Format File ............................................................................................... 2168.2.1.2 Discrimination Data File .......................................................................... 2168.2.1.3 Report Record .......................................................................................... 2178.2.1.4 Report Output ........................................................................................... 218

8.3 Processing Reports .............................................................................................................. 2198.4 Report Types ....................................................................................................................... 2198.5 Report Format File .............................................................................................................. 221

8.5.1 Format File Syntax .................................................................................................. 2218.5.2 Definitions ............................................................................................................... 2228.5.3 Output Fields ........................................................................................................... 2258.5.4 Sample Format Files ............................................................................................... 226

8.6 What Happens When I Report On a Component? .............................................................. 2308.7 Material Takeoff Reporting (Report Manager) ................................................................... 2368.8 Understanding Implied Items .............................................................................................. 240

8.8.1 Mating Implied Items .............................................................................................. 2408.8.2 * Spec Implied Items ............................................................................................ 2408.8.3 + Table Implied Items .......................................................................................... 241

8.9 Material Takeoff Options .................................................................................................... 2438.10 Labels in Material Descriptions ........................................................................................ 246

v

PDS 3D Theory May 1996________________

8.10.1 Create Label Attribute Data ................................................................................ 249

9. Extracting Isometric Drawings .................................................................................................... 253

9.1 Overview of Isometric Extraction ....................................................................................... 255

9.1.1 The Intergraph Interface to ISOGEN ...................................................................... 2559.1.2 ASCII to Binary Conversion ................................................................................... 2569.1.3 ISOGEN .................................................................................................................. 256

9.2 Batch Software Organization .............................................................................................. 257

9.2.1 The Batch Job Input File ......................................................................................... 2579.2.2 Line Processing (pdsidf) ......................................................................................... 2599.2.3 The ISOGEN Interface ............................................................................................ 2609.2.4 ISOGEN .................................................................................................................. 2609.2.5 Plotting .................................................................................................................... 260

10. Creating Orthographic Drawings ............................................................................................... 261

10.1 Drawing Manager Setup ................................................................................................. 26310.2 Drawing Seed Data ......................................................................................................... 26810.3 Using Labels in Drawings ............................................................................................... 272

10.3.1 Label Types ....................................................................................................... 27210.3.2 Label Definition Data ........................................................................................ 27410.3.3 Drawing View Specific Labels ......................................................................... 27410.3.4 Displayable Attribute Label .............................................................................. 275

Index .................................................................................................................................................... 277

vi

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) Users Guide (DEA5017)

Interference Checker/Manager (PD_Clash) Users Guide (DEA5030)

Drawing Manager (PD_Draw) Users 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

vii

PDS 3D Theory May 1996________________

Chapter 7 - Detecting and Managing Interferences

Chapter 8 - Creating Material Takeoffs and Other Reports

Chapter 9 - Extracting Isometric Drawings

Chapter 10 - Creating Orthographic Drawings

viii

1. PDS Overview

What is the Plant Design System?________________

1. What is the Plant DesignSystem?

Intergraphs plant design software can be used to design any type of plantfrompetrochemical 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.

1

PDS 3D Theory May 1996________________

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

2

1. PDS Overview

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.

3

PDS 3D Theory May 1996________________

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

4

1. PDS Overview


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 datasuch as line sequence number, nominal diameter, material class,temperatures and pressurescan 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.

5

PDS 3D Theory May 1996________________

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.

6

1. PDS Overview


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.

7

PDS 3D Theory May 1996________________

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.

8

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 Intergraphs DesignReview package.You can use DesignReview to walk through a PDS modelin full shaded modeand 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 designers 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.

9

PDS 3D Theory May 1996________________

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.

10

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

11

PDS 3D Theory May 1996________________

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. The PDS license server can be a CLIX or a Windows NT machine.

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) Users Guide(DEA5071).

12

1. PDS Overview

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.

13

PDS 3D Theory May 1996________________

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.

14

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

15

PDS 3D Theory May 1996________________

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.

16

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

17

PDS 3D Theory May 1996________________

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

18

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

19

PDS 3D Theory May 1996________________

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

20

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

21

PDS 3D Theory May 1996________________

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.

22

1. PDS Overview

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:

23

PDS 3D Theory May 1996________________

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.

24

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

25

PDS 3D Theory May 1996________________

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.

26

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

27

PDS 3D Theory May 1996________________

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

28

1. PDS Overview

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.

29

PDS 3D Theory May 1996________________

30

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

31

PDS 3D Theory May 1996________________

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.

32

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 tothe PCS.

33

PDS 3D Theory May 1996________________

Building 3

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

34

2. Database

Overview

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 modela 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 Corporations 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.

35

PDS 3D Theory May 1996________________

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

36

2. Database

Overview

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.

37

PDS 3D Theory May 1996________________

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.

38

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

39

PDS 3D Theory May 1996________________

2.3 PDS 3D Databases

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

40

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

41

PDS 3D Theory May 1996________________

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]

42

2. Database

Overview

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


43

PDS 3D Theory May 1996________________

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

44

2. Database

Overview


# 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

45

PDS 3D Theory May 1996________________

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

46

2. Database

Overview



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


47

PDS 3D Theory May 1996________________

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

48

2. Database

Overview


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

49

PDS 3D Theory May 1996________________

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

50

2. Database

Overview


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)

51

PDS 3D Theory May 1996________________

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

52

2. Database

Overview


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


53

PDS 3D Theory May 1996________________

1 , isoproj_indx_no , integer , index 12 , isoproj_task_opt , short3 , isoproj_name_opt , short4

80524076-PDS-3dtheory

Documents

Transcript of 80524076-PDS-3dtheory