PDS 3D Theory Guide

Plant Design System 3D Theory

Versio n 2009 (V10)

Febru ary 2009

DPDS3-PB-200010E DPDS3-PB-200010E

Copyright Copyright © 1984-2009 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 from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense expense and is "restricted "restricted computer software" submitted submitted with restricted restricted rights rights in accordance accordance with with subparagraphs subparagraphs (a) through through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Street address: 170 Graphics Drive, Madison, AL 35758

Terms of Use Use of this software product is subject to the End User License Agreement and Limited Product Warranty ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable reasonable number number of copies copies of the documentatio documentation n as defined defined in the applicable applicable license license agreement agreement and delivered with with the software software product for licensee's internal, non-comme non-commercial rcial use. The The documentation documentation may may not be printed printed for resale resale or redistribution. redistribution.

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, 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 publication is accurate accurate as of its publication 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. descriptions. Intergraph Intergraph Corporation Corporation is not not responsible responsible for any error error that may appear in this this document. 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. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are trademarks of their respective owners.

Preface PDS ............................................................................................................................................... vii What is the Plant Design System? ............................................................................................................. 1

What are the 2D modules? ..................................................................................................................... 2 Process Flow Diagram (PFD) .......................................................................................................... 2 Process & Instrumentation Diagram (P&ID) .................................................................................. 3 Instruments and Instrument Loops .................................................................................................. 3 What are the 3D modules? ..................................................................................................................... 4 Equipment Modeling (PD_EQP) ..................................................................................................... 4 FrameWorks Plus (FWP) ................................................................................................................. 4 Piping Design Graphics (PD_Design) ............................................................................................. 5 Reference Data Manager (PD_Data) ............................................................................................... 6 Drawing Manager (PD_Draw) ........................................................................................................ 7 PDS Stress Analysis Interface (PD_Stress) ..................................................................................... 7 Interference Checker/Manager (PD_Clash)..................................................................................... 8 PDS Isometric Interface (PD_ISO, PD_ISOGEN) .......................................................................... 9 Report Manager (PD_Report)........................................................................................................ 10 Project Engineer HVAC (PE-HVAC) ........................................................................................... 10 EE Raceway Modeling .................................................................................................................. 11 Design Review Integrator (PD_Review) ....................................................................................... 11 Project Setup ........................................................................................................................................ 12 System Setup ................................................................................................................................. 12 2DSetup ......................................................................................................................................... 13 3D Setup ........................................................................................................................................ 14 About licensing .............................................................................................................................. 14 Project Organization ............................................................................................................................. 15 Working in Three Dimensions ............................................................................................................. 16 Working Units ............................................................................................................................... 19 Recommended Working Units - English ....................................................................................... 20 Recommended Working Units - Metric ........................................................................................ 21 Reasoning ...................................................................................................................................... 22 3D Coordinate Systems ................................................................................................................. 22 Plant Coordinate System ............................................................................................................... 23 Design Volume Coordinate System ............................................................................................... 28 Examples ....................................................................................................................................... 30 Database Overview ................................................................................................................................... 35

PDS and the Relational Interface System (RIS) ................................................................................... 36 PDS System Configurations ................................................................................................................. 37 Client/Server Relationship ............................................................................................................. 38 PDS 3D Databases ............................................................................................................................... 39 Database Information .................................................................................................................... 40


i

Database Definition Files ..................................................................................................................... Project Control Database ............................................................................................................... Design Database ............................................................................................................................ Reference Database .......................................................................................................................

41 41 57 69

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

Delivered Reference Data .................................................................................................................... 76 Piping Job Specification ....................................................................................................................... 77 Piping Materials Class Data........................................................................................................... 77 Piping Commodity Specification Data .......................................................................................... 78 Piping Specialty Specification Data .............................................................................................. 80 Instrument Component Specification Data .................................................................................... 81 Tap Properties Data ....................................................................................................................... 82 Piping Commodity Size-Dependent Material Data ....................................................................... 83 Piping Commodity Implied Material Data .................................................................................... 84 PJS Tables and Functions .............................................................................................................. 86 Graphic Commodity Data and Physical Dimension Data ................................. ................ ................................... .................................. ................ 87 Material Description Data .................................................................................................................... 87 Standard Note Library .......................................................................................................................... 89 Label Description Library .................................................................................................................... 89 Piping Assembly Library ..................................................................................................................... 90 How PDS Works ....................................................................................................................................... 91

What Happens When I Place a Component? ....................................................................................... 91 Example of Piping Software ................................................................................................................ 92 Place Component Command ................................................................................................................ 94 Spec Access ................................................................................................................................... 94 Piping Materials Class Data........................................................................................................... 94 Piping Commodity Data .............................................................................................................. 100 Table Access ................................................................................................................................ 103 Symbol Processors ....................................................................................................................... 105 Sub-Symbol Processor ................................................................................................................. 106 Physical Data Definitions ............................................................................................................ 107 Specific Physical Data Modules .................................................................................................. 108 Parametric Shape Definitions ...................................................................................................... 111 Physical Data ............................................................................................................................... 113 Placing Components On Existing Segments ...................................................................................... 116 Commodity Item Name Table ..................................................................................................... 116 Bend Deflection Table ................................................................................................................. 117 Branch Insertion Tables ............................................................................................................... 117 Placement Examples .................................................................................................................... 118 Creating 3D Models ................................................................................................................................ 121

Modeling Setup Requirements ........................................................................................................... 122 Project Setup ................................................................................................................................ 122 Reference Data Setup .................................................................................................................. 122 Seed Files ..................................................................................................................................... 122 Model Files .................................................................................................................................. 123 ii


Level Control and Graphical Symbology .................................................................................... 124 Level and Symbology Defaults ................................................................................................... 125 Graphics Environment for PDS 3D .................................................................................................... 126 Working with the Graphical User Interface ................................................................................. 126 Common Tools on Forms ............................................................................................................ 132 3D Seed Data ............................................................................................................................... 135 Creating Equipment Models .............................................................................................................. 138 Functions of PDS Equipment Modeling (PD_EQP).................................................................... 139 About the Reference Database (RDB) ......................................................................................... 139 Equipment Model Seed Data ....................................................................................................... 140 Equipment Modeling Environment ............................................................................................. 143 Equipment Modeling Concepts ................................................................................................... 145 Activating the Orientation Tee .................................................................................................... 147 Equipment Modeling Commands....................................................................................................... 148 Equipment Manipulation Commands .......................................................................................... 148 Component Manipulation Commands ......................................................................................... 148 Nozzle Manipulation Manipulation ................... ............................ .................. .................. .................. .................. .................. .................. .................. .................. .................. ............... ...... 148 Review/Revise Commands .......................................................................................................... 148 Define Commands ....................................................................................................................... 148 Miscellaneous Commands ........................................................................................................... 148 Secondary Commands ................................................................................................................. 149 Creating Piping Models...................................................................................................................... Models ...................................................................................................................... 149 Piping Model Seed Data .............................................................................................................. 151 Graphic Concepts for Piping Design ........................................................................................... 160 Orientation Tee ............................................................................................................................ 162 Piping Design Commands .................................................................................................................. 163 Placement Commands ................................................................................................................. 163 Revision Commands .................................................................................................................... 164 Component Revision ................................................................................................................... 164 Segment Vertex Commands ........................................................................................................ 164 Piping Revision ............................................................................................................................ 165 Model Data .................................................................................................................................. 165 Review Data ................................................................................................................................ 165 Revise Data .................................................................................................................................. 165 Analyze Data ............................................................................................................................... 165 P&ID to Piping Data Transfer .............................................................................................................. 167

Database Requirements ...................................................................................................................... 168 P&ID Correlation Table ..................................................................................................................... 168 P&ID Graphical Data Transfer Setup ................................................................................................ 174 P&ID Node Numbers ......................................................................................................................... 176 Update Segment Data from P&ID ..................................................................................................... 177 Update by Node Number ............................................................................................................. 178 Transfer by Equipment Number and Nozzle Number ................................................................. 178 Update From Active P&I Drawing .............................................................................................. 179 P&ID Data .......................................................................................................................................... 180 Name From P&ID ................. ........................... ................... .................. .................. .................. .................. .................. .................. .................. .................. .................. .................. ......... 180 P&ID Data Comparison Options........................................................................................................ 181


iii

SmartPlant P&ID to PDS Piping Data Transfer ................................................................................. 183

Transferring Piping Data .................................................................................................................... 185 Installation .......................................................................................................................................... 187 Install Oracle ................................................................................................................................ 187 Install SmartPlant Engineering Manager ..................................................................................... 188 Install SmartPlant P&ID .............................................................................................................. 189 Test the SmartPlant Connection .................................................................................................. 189 Creating and Maintaining Links ......................................................................................................... 191 Establish a SmartPlant/PDS Link ................................................................................................ 194 Revising Linked Models .............................................................................................................. 195 Mapping Attributes ............................................................................................................................ 197 Map an Ignored Attribute ............................................................................................................ 198 Map an Unmapped Attribute ....................................................................................................... 198 Segment Data Comparison Report ..................................................................................................... 199 Choosing Data Transfer Options ........................................................................................................ 201 Load From P&ID Options .................................................................................................................. 203 Graphical P&ID Setup Command ...................................................................................................... 205 Select P&ID by Line ID Command ................................................................................................... 207 Select P&ID Drawing by Nozzle Command ...................................................................................... 209 Review P&ID Drawing Details Command ........................................................................................ 211 P&ID Drawing Display Categories Command .................................................................................. 213 Restore View of Piping Model Command ......................................................................................... 215 Disable Display of P&ID Drawing Command ................................................................................... 217 Name from P&ID P&ID Option................. .......................... .................. ................... ................... .................. .................. .................. .................. .................. .................. ................ ....... 219 Named Component Component Existence Report Report Command Command.................. ........................... .................. .................. .................. .................. .................. ................ ....... 221 Appendix A: Troubleshooting ............................................................................................................ 223 Detecting and Managing Interferences ................................................................................................. 227

Interference Checking Process Overview .......................................................................................... 227 Project Organization ........................................................................................................................... 229 Understanding Design Areas and Volumes ................................................................................. 230 Setting Up a System to Support Interference Detection..................................................................... 235 Understanding Interference Envelopes .............................................................................................. 236 Understanding Interference Checking ......................................................................................... 237 Understanding Interference Plotting ............................................................................................ 242 Understanding Interference Reporting ........................................................................................ 243 Creating Material Takeoffs and Other Reports .................................................................................. 245

Reporting Process............................................................................................................................... 245 Maintaining Report Definition Data .................................................................................................. 246 Understanding Report Files and Records .................................................................................... 246 Processing Reports ............................................................................................................................. 248 Report Types ...................................................................................................................................... 248 Report Format File ............................................................................................................................. 249 Format File Syntax ...................................................................................................................... 249 Definitions ................................................................................................................................... 250 Output Fields ............................................................................................................................... 253 Sample Format Files .................................................................................................................... 254 iv


What Happens When I Report On a Component? ............................................................................. 258 Material Descriptions .................................................................................................................. 258 Commodity Codes ....................................................................................................................... 260 Examples ..................................................................................................................................... 261 Implied Data ................................................................................................................................ 262 Report Output .............................................................................................................................. 263 Material Takeoff Reporting (Report Manager) .................................................................................. 263 Sample MTO Format (piping_g.fmt) .......................................................................................... 264 Sample MTO Output ................................................................................................................... 266 Understanding Implied Items ............................................................................................................. 268 Mating Implied Items .................................................................................................................. 268 '*' Spec Implied Items .................................................................................................................. 268 '+' Table Implied Items ................................................................................................................ 269 Material Takeoff Options ................................................................................................................... 270 Labels in Material Descriptions ......................................................................................................... 273 Create Label Attribute Data ......................................................................................................... 278 Material Data Publisher ...................................................................................................................... 281 Extracting Isometric Drawings ............................................................................................................. 283

Overview of Isometric Extraction ...................................................................................................... 285 The Intergraph Interface to ISOGEN .......................................................................................... 286 ASCII to Binary Conversion ....................................................................................................... 286 ISOGEN....................................................................................................................................... 286 Batch Software Organization ............................................................................................................. 287 The Batch Job Input File ............................................................................................................. 288 Line Processing (pdsidf) .............................................................................................................. 289 The ISOGEN Interface ................................................................................................................ 289 ISOGEN....................................................................................................................................... 290 Plotting......................................................................................................................................... 290 Creating Orthographic Drawings ......................................................................................................... 291

Drawing Manager Features ................................................................................................................ 292 Drawing Manager Setup .................................................................................................................... 292 Project Setup ................................................................................................................................ 292 Model Files .................................................................................................................................. 293 Drawing Manager Setup .............................................................................................................. 293 Drawing Categories ..................................................................................................................... 293 Cells ............................................................................................................................................. 293 Drawing Borders .......................................................................................................................... 293 Drawing Plot Size Table .............................................................................................................. 294 Drawing Manager Database Table Information .......................................................................... 295 Project Control Database ............................................................................................................. 295 Drawing Seed Data ............................................................................................................................ 297 Using Labels in Drawing ................................................................................................................... 301 LabelTypes .................................................................................................................................. 301 Label Definition Data .................................................................................................................. 302 Drawing View Specific Labels .................................................................................................... 303 Displayable Attribute Label ......................................................................................................... 304


v

Index ........................................................................................................................................................ 305

vi


This document provides command reference information and procedural instructions for the Plant Design System 3D Theory Guide task.

List of PDS Documentation 

DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide



DPDS3-PB-200004 - Drawing Manager (PD_Draw) User's Guide DPDS3-PB-200005 - EE Raceway Modeling Reference Guide

  

DPDS3-PB-200006 - Interference Checker/Manager (PD_Clash) User's Guide DPDS3-PB-200010 - PDS 3D Theory User's Guide



DPDS3-PB-200013 - PDS EDEN Interface Reference Guide Volume I : Piping DPDS3-PB-200015 - PDS Equipment Modeling (PD_EQP ) User's Guide DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1



DPDS3-PB-200022 - PDS Piping Component Data Reference Guide



DPDS3-PB-200023 DPDS3-PB-200025 DPDS3-PB-200026 DPDS3-PB-200028

- PDS Project Setup Technical Reference - PDS Stress Analysis Interface (PD_Stress) User's Guide - Pipe Supports Modeler Reference Guide - Piping Design Gr aphics (PD_Design) Reference Guide

DPDS3-PB-200030 DPDS3-PB-200033 DPDS3-PB-200034 DPDS3-PB-200035

- Pr oject Administrator (PD_Project) Reference Guide - Project Engineer HVAC (PE-HVAC) Reference Guide - Reference Data Mana ger (PD_Data) Reference Guide - Report Manager (PD_Report) User's Guide

 

                  

DPDS3-PB-200041 - PDS EDEN Interface Reference Guide Volume 2 : Equipment DPDS3-PB-200042 - PDS EDEN Interface Reference Guide Volume 3 : Pipe Supports DPDS3-PE-200016 - PDS Express P roject Crea tion Quick Start Guide DPDS3-PE-200052 - PDS Ortho Draw User's Guide DPDS3-PE-200029 - Piping Model Builder (PD_Model) Reference Guide DPDS3-PE-200031 - Project Engineer HVAC Getting Started Guide DPDS3-PE-200032 - Project Engineer HVAC Overview DPDS3-PE-200045 - PDS Label Library Merger Utility DPDS3-PE-200047 DPDS3-PE-200048 DPDS3-PE-200050 DPDS3-PE-200051


- PDS Reference Data Auditing Tool - Pipe Supports Explorer Utility - Batch Services Quick Start Guide - Batch Services User's Guide

vii

Preface PDS

viii


SECTION 1

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

2D and 3D design files, project files, databases. feasibility studies, cost estimates, general layouts and process flow diagrams.

3. 4.

process, instrumentation, piping layouts, material control. 3D model walk-through.


1

What is the Plant Design System?

What are the 2D modules?............................................................. What are the 3D modules?............................................................. Project Setup .................................................................................. Project Organization ...................................................................... Working in Three Dimensions.......................................................

2 3 12 14 16

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.

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.

2



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 information is loaded into a relational database.

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.


3


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.

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.

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.

4


What is the Plant Design System? 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 nongraphic data made available to the rendering and walk- through products such as SmartPlant Review.

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 Plant Design System 3D Theory

5

What is the Plant Design System? 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.

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.

6



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.

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.


7


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

8



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.


9


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.

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.

10



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.

The PD_Review interface provides an intelligent link to Intergraph's SmartPlant Review. You can use SmartPlant Review to walk through a PDS model—in full shaded mode—and review the design and alphanumeric data.


11

What is the Plant Design System? 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 SmartPlant Review, the model can be used to train operations and maintenance personnel before or after the plant is constructed. SmartPlant Review is not included in the PDS package and must be purchased separately.

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 .

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. PDS uses relational databases to store informational about virtually all aspects of the project including: 

, such as file names and locations. , such as piping commodity descriptions.



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



12


What is the Plant Design System? The PDS products attach to the relational databases through RIS. RIS supports popular Relational Database Management Systems, such as Oracle and MS SQL.

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


13


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 used to create the database files, seed files, and project environment files.

is

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.

SmartPlant License Manager 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 SmartPlant License Manager 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. SmartPlant License Manager 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, SmartPlant License Manager 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 SmartPlant License Manager User's Guide .

14



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 or it may be constructed with respect to a local or auxiliary point of reference, known as the Design Volume Monument . 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. 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 Plant Design System 3D Theory

15

What is the Plant Design System? 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.

All PDS models exist in three dimensions. Many design manipulations can be executed in a 2Dlike 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).

16


What is the Plant Design System? 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.

All graphic elements must be placed in the design cube . The design cube is a volume of threedimensional 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.


17

What is the Plant Design System? 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.

18


What is the Plant Design System? 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.

Design Cube Showing Cartesian Coordinate System

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.


19

What is the Plant Design System? 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.

20

File

MU

SU

PU

Area

Models (Piping, Equipment,

1 FT

12 IN

2032

176138 FT


What is the Plant Design System? Structural, Raceway, HVAC, Civil, Architecture, MicroStation) Drawing

1 FT

12 IN

File

MU

SU

PU

Area

Models

1M

1000 MM

80

53687 M

Drawing

1M

1000 MM

7680

536 M


195072

1834 FT

21


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.

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.

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

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.

22



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. This must be done prior to any design file definition.


23

What is the Plant Design System? 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:

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

24


What is the Plant Design System? entire design cube, you must modify the Easting and Northing values of the plant monument. For example, let us assume that the Plant monument is defined to be Easting 88,069’ - 4.5", Northing 88,069’ - 4.5", and Elevation 0, as shown below.

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


25


26


What is the Plant Design System? 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.


27

What is the Plant Design System? 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.

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.

28


What is the Plant Design 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 button to select the preferred degree value) to define the plan view for the design volume, through the . 

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.

The system uses the global coordinate system to maintain the relationship among the various reference models attached to the working model. Plant Design System 3D Theory

29


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

30



DVCS Oriente d From Plant North With values keyed into the 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.


31

What is the Plant Design System? 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.

32


What is the Plant Design System? Notice that the design volume is NOT ROTATED with respect to the PCS.

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


33


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

34


SECTION 2

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

, such as file names and locations. , such as piping commodity descriptions.



, 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 Oracle and MS SQL.


35

Database Overview

PDS and the Relational Interface System (RIS) ............................ PDS System Configurations .......................................................... PDS 3D Databases ......................................................................... Database Definition Files ..............................................................

36 37 39 41

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 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 Oracle or MS SQL. 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.

36


Database Overview 3D RIS 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.

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


37

Database Overview

PDS is scalable and can be run on a single node or distributed across a number of client and server nodes. Client nodes are Intel workstations running Windows. Server nodes are multi-processor type Intel servers running Windows 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. 

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.

38


Database Overview

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

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

The

is used to create the database files, seed files, and project

environment files. A 3D project is divided into design ar eas by disciplines . Disciplines represent the various 3D modeling applications (such as Piping, Equipment, and HVAC). A design area


39

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

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.

Attribu te Type s The following conventions are used to designate the field type for database attributes. character(n)

alphanumeric field n characters in length

i nt eger

double word integer

shor t

short integer

doubl e

real (floating point) value

st andar d not e nnnn

Standard Note Type for code-listed attribute

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. f l ui d_code

, char act er ( 6)

, st andar d not e 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, Fl ui d Code/ Connect or Type ( 999) 1 = [ B l ank ]

11 = A

[Ai r]

14 = AC

[ Comusti on ai r]

17 = AE

[ Aerati on ai r]

20 = AI

[ I nst rument ai r]

: :

40


Database Overview 191 = G 194 = GCD

[ Gas] [ Carbon di oxi de gas]

197 = GCL

[ Chl ori ne gas]

198 = GCN

[C

200 = GF

[ Fue

o r i na t i o n ga s]

203 = GG

[ F ue gas]

206 = GH

[ Hydrogen gas]

209 = GHS

[ Hy r o gen s u p i e gas ]

gas]

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.

# Proj ect Cont rol Database # Defaul t Rel ati onal Database Defi nit i on # T e us er mus t not r evi s e t i s

at a as e

e i ni t i on ot er t an

# t o change col umn names. #

Proj ect Descri pti on Data

ta

e num e r

= 101

, num e r o

c o umns

= 7

1

, system_uni que_no

, i nteger

2

, pr o j e ct _ no

, c ar ac t er 15

3

, proj ect_name

, char acter( 40)

4

, j o _no

, c ar act er 40

5

, company_name

, c aracter 40

6

, pl ant _name

, char acter( 40)

7

, si t e_ i

, c ar act er 10

#

Re erence Data ase Management Data

t abl e number

= 102, number of col umns

1

, t ype_ o _r

2

, appr o va _ s t at u s

, s or t

3

, rdb_f i l e_spec

, character (14)

4

, pat _ name

, c ar ac t er 36

5

, net work_address

, char acter( 26)

6

,

oc _ owner

, c ar ac t er 10

7

,

oc _ st at us

, s or t

8

, l ock_date

, i nteger

9

, r e vi s i on_ at e

, i nt e ger

#

_ at a

= 9

Pr o j e ct Cont r o

t abl e number

= 103

, s or t

Dat a , number of col umns


= 41

41

Database Overview 1

, pr o uc t _ ver s i on_ no

2

, r epor t _ pat

, c ar ac t er 36

3

, repor t _node

, char acter( 26)

4

, r epor t _ or mat _ pat

, c ar ac t er 36

5

, report _f ormat_node

, char acter( 26)

6

, r epor t _ i t er _pat

, c ar act er 36

7

,

,

8

, pi pi ng_eden_pat h

, char acter( 36)

9

, pi pi ng_ e en_ no e

, c ar ac t er 26

repor t _ i t er _no e

10, e en_t a

, s or t

c ar act er 26

e_pat

, c ar act er 36

11, eden_t abl e_node

, char acter( 26)

12, pi pi ng_ spec _pat

, c ar ac t er 36

13, pi pi ng_ spec _no e

, c ar ac t er 26

14, assembl y_pat h

, char acter( 36)

15, as sem y_ no e

, c ar ac t er 26

16, model _bui l der_ pat h

, character ( 36)

17, mo e _ ui

, c ar act er 26

18,

er _no e

es i g n_ r evi ew_ pat

19, desi gn_r evi ew_node

, c ar ac t er 36 , character( 26)

20, st _ not e_ i _pat

, c ar act er 36

21, st _ not e_ i _no e

, c ar act er 26

22, eqp_eden_path

, char acter( 36)

23, eqp_ e en_ no e

, c ar ac t er 26

24, t df _t abl e_path

, character (36)

25, t df _t abl e_node

, character (26)

26, c as _ r epor t _ pat

, c ar act er 36

27, cl ash_r eport _node

, char acter( 26)

28, c as _ p ot _pat

, c ar act er 36

29, cl ash_pl ot_node

, character (26)

30, mdl _st atus_l ow_dr

, shor t

31, m _ st at us _ i g _ r

, s or t

32, mdl _st atus_l ow_i c 33, m _ st at us _ i g _ i c

, shor t , s or t

34, area_owner_opt_i c

, s ort

35, eqp_i nsul_ opt_ i c

, short

36, eqp_ c on_ t o _ opt _ i c

, s or t

37, c as _ r pt _ i n ex_ no

, i nt e ger

38, report _search_path

, character ( 36)

39, r epor t _ sear c _ no e

, c ar act er 26

40, sup_t df_t abl e_path

, character( 36)

41, sup_ t

, c ar act er 26

_t a

e_ no e

# Proj ect Arc i va

42

, st andard not e

1605

, st an ar

not e

1605

, st andard not e

1605

, st an ar

1605

not e

Management Data


Database Overview ta

e num e r

= 1 04, num e r o

c o umns

= 11

1

, ar c i va _ i n ex_ no

, i nt e ger

2

, archi val _number

, char acter( 24)

3

, ar c i v a _ escr i pt

, c ar act er 40

4

, ar c h i v a l _ f i l e _s pe c

5

, pat _ name

6

, net wor _ a

7

, month_ map

, i nt eger

8

,

ay_o _wee _map

, i nteger

9

,

ay_map

, i nteger

, char a c t e r ( 1 4) , c ar ac t er 36

r ess

, c ar act er 26

10, t i me_of_day

, i nteger

11, s c e u e_ t ype

, s or t

# Sit e Descri pti on Data t abl e number


= 13

1

, si t e_ i

, c ar act er 10

2

, s i t e _ de sc r i pt i o n

, c har a c t e r ( 4 0)

3

, mi n_mo e _range

, i nteger

4

, max_mo e _range

, i nteger

5

, mi n_dwg_r ange

, i nteger

6

, max_ wg_range

, i nteger

7

, mi n_ wg_vi ew_r ange , i nteger

8

, max_dwg_vi ew_r ange

9

, mi n_pi p_parti ti on

, i nteger , i nteger

10, max_pi p_part i t i on

, i nteger

11, mi n_eqp_part i t i on

, i nteger

12, max_eqp_part i t i on

, i nteger

13, master_f l ag

, short

# Mo e

Management Data

# Engineeri ng Di sci pli ne Data t abl e number

= 111

, number of col umns

1

,

i s ci p i n e_ i n x_ no

2

, di sci pl i ne_name

3

, i nt r a_ i s c_ i c_

4

,

5

, di sci pl i ne_mt rx_b, i nt eger

= 5

, s or t , character (20)

g

, s or t

i s c i p i ne_ mt r x _ a, i nt e ger

# Desi gn Area Data t abl e number

= 112



= 15

1

,

, s or t

2

, ar e a_ i n ex_ no

, s or t

3

, area_name

, char acter ( 10)

4

, ar ea_ es cr i pt i on

, c ar ac t er 40

5

, vol ume_l ow_x

, i nteger


43

Database Overview 6

, vo ume_ ow_y

, i nteger

7

, vo ume_ ow_z

, i nteger

8

, vol ume_hi gh_x

, i nteger

9

, vo ume_ i g _ y

, i nt e ger

10, vol ume_hi gh_z

, i nteger

11, i nt e r er e nc e_ mo e

, s or t

12, ar ea_ oc _ owner

, c ar ac t er 10

13, area_l ock_status

, short

14, ar ea_ oc _ at e

, i nt e ger

15, c as _ r pt _ i n ex_ no

, i nt e ger

# Model Data ta

e num e r

= 113

, num e r o

c o umns

= 17

1

, mo e _ i n ex_ no

, i nt e ger

2

, di s c i pl i ne_ i ndx _ no

3


, s or t

4

, pa r t i t i on_ no

, s hor t

5

, mo e _ no

, c ar act er 10

6

, mo e _ es cr i p t i on

, c ar act er 40

7

, model _f i l e_spec

, character (14)

8

, pat _ name

, c ar ac t er 36

9

, net wor _ a

, i n ex

1

, s hor t

r ess

, c ar act er 26

10, l ock_owner

, char acter( 10)

11,

, s or t

oc _ st a t us

12, l ock_date

, i nteger

13, v er i f i c at i on_ dat e

, i nt e ge r

14, r e vi s i on_ at e

, i nt e ger

15, responsi bl e_di sc

, short

16, mo e _ t ype

, s or t

17, model _st atus

, shor t

, st andard not e

1605

# Pi pi ng Model Data ta

e num e r

= 114

, num e r o

c o umns

= 6

1

, pa r t i t i on_ no

, s hor t

2

, max_segment _numer

3

, max_pi pi ng_num er

, i nteger

4

, max_pi pe_number

, i nteger

5

, max_i nstr _num er

, i nteger

6

, max_support _num er

, i nteger

, i nteger

306

# Model Setup Dat a ta 1

e num e r ,

44

= 115

, num e r o


c o umns

= 5

, s or t


Database Overview 2

,

e au t _ pat _ name

, c ar ac t er 36

3

,

e au t _no e

, c ar act er 26

4

, ref _mdl _symbol ogy

, shor t

5

, sym o ogy_ i s p ay

, s or t

# Str uctur al Management Data # St r uc t ur a ta

Su - P r oj ec t Cont r o

Dat a

= 1 16, num e r o

c o umns

e num e r

= 6

1

, sub_proj ect_ndx_no

, short

2

, s u _ pr oj ect _ no

, c ar ac t er 15

3

, s u _ pr o j e ct _ n ame

, c ar a ct e r 40

4

, sub_proj ect _pat h

, character (36)

5

, s u _ pr oj ect _ no e

, c ar ac t er 26

6

, s u _ pr oj ec t _ mount

, c ar ac t er 50

# Str uctural Desi gn Ar ea Per Sub- Proj ect Data ta

e num e r

= 1 17, num e r o

1

, area_i ndex_no

2

, s u _ pr oj ec t _ n x_ no

c o umns

= 2 , shor t

, s or t

# I nspecti on I so Data t abl e number


= 3

1

, i ns pect i on_ i s o_ i

, c ar ac t er 24

2

, i ns pec t i on_ s t at u s

, s or t

3

, max_i nspecti on_key

# Mo e

, short

Owner s i p Dat a

t abl e number


= 2

1

, model _i ndex_no

, i nteger

2

, si t e_ i

, c ar act er 10

, i ndex

1

# Dr awi ng Management Dat a # Dr awi ng Data t abl e number


= 34

1

, dwg_i ndex_no

, i nteger

, i ndex

1

2

,

r a wi ng_ no

, c ar ac t er 24

, i n ex

2

3

, drawi ng_ti t l e

, character (40)

4

,

e au t _sca e

, c ar act er 16

5

, appr ova _ i ni t i a s

, c ar act er 4

6

, approval _date

, i nteger

7


, s or t

8

, c omp et i on_ s t at u s

, s or t

9

, drawi ng_si ze

, shor t

, st andard not e

1202

r a wi ng_ t y pe

, s or t

, stan ar

2000 ,

10,

i ndex

, s t an ar

not e

not e

35

3

11,

as t _ r evi s i o n_ no

, c ar ac t er 2

12,

r awi ng_ i e_ spec

, c ar ac t er 14


45

Database Overview 13, pat _ name

, c ar ac t er 36

14, net wor _ a

r es s

, c ar act er 26

15, l ock_owner

, char acter( 10)

16,

, s or t

oc _ st a t us

17, l ock_date

, i nteger


, i nt e ger

19,

, s or t

as t _ r e v_ i n ex _no

20, rel ease_revi si on

, character (2)

21, r e eas e_ at e

, i nt e ger

22, c ec i ng_ st at us

, s or t

23, st andard_not e_no_a

, short

, st andard not e

499

24, s t an ar _ not e _no_

, s or t

, s t an ar

not e

499

not e

1620 opt i ona

25, c us t o m_ 1

, c ar a ct e r 40

26, custom_2

, char acter( 40)

27, c us t o m_ 3

, c ar a ct e r 16

28, custom_4

, char acter( 16)

29, c us t o m_ 5

, c ar a ct e r 16

30, c us t o m_ 6

, c ar a ct e r 16

31, custom_7

, char acter( 16)

32, c us t o m_ 8

, c ar a ct e r 16

33, custom_9

, i nteger

34, cust om_10

, i nteger

# Drawi ng Vi ew Data t abl e number


= 16

1

, dwg_vi ew_i ndex_no

, i nteger

, i ndex

1

2

,

wg_ vi ew_ no

, c ar a ct e r 24

, i n ex

2

3

, dwg_vi ew_name

, char acter ( 40)

4

,

, c ar ac t er 16

5

, dwg_i ndex_no

, i nteger

6

, saved_vi ew_name

, char acter ( 6)

7

, vi ewi ng_ i r ec t i on

, s or t

8

, composi t i on_st atus

9

,

wg_ vi ew_ sc a e

, shor t

, st andard not e

wg_vi ew_ x_ ow

10,

, s t an ar

wg_ vi ew_y_ ow

,

ou e

,

ou

e

11, dwg_ vi ew_z_l ow

, doubl e

12,

wg_ vi ew_ x_ i g

,

ou

e

13,

wg_ vi ew_ y_ i g

,

ou

e

14, dwg_vi ew_z_ hi gh 15, v

_ cat egor y_ i n ex

, doubl e , s or t

16, drawi ng_vi ew_t ype # Drawi ng Vi ew Re erence Mo e ta

46

e num e r

1630

= 1 23, num e r o

, shor t Data c o umns

= 2


Database Overview 1

,

wg_vi ew_i n ex_no

2

, mo e _ i n ex _no

, i nteger , i nt e ger

# Composi t e Dr awi ng Vi ew Data ta

e num e r

= 1 24, num e r o

c o umns

= 15

1

, comp_dwg_i ndex_no

, i nteger

2

, c omp_ wg_ v i e w_ no

, c ar a c t e r 24

3

, comp_ wg_vi ew_name

4

, comp_dwg_v_scal e

, char acter ( 16)

5

,

wg_i n ex_no

, i nteger

6

,

wg_vi ew_i n ex_a

, i nteger

7

, dwg_vi ew_i ndex_b

, i nteger

8

,

wg_vi ew_i n ex_c

, i nteger

9

,

wg_ v i e w_ i n e x_

, i nt e ge r

10, dwg_vi ew_i ndex_e

, i nteger

11,

, i nt e ge r

, i ndex

1

, c aracter 40

wg_ v i e w_ i n ex _

12, dwg_vi ew_i ndex_g

, i nteger

13,


, i nt e ge r

14,

wg_vi ew_i n ex_i

, i nteger

15, dwg_vi ew_i ndex_j

, i nteger

# Dr awi ng Revi si on Data ta

e num e r

= 1 25, num e r o

c o umns

= 16

1

, dwg_i ndex_no

, i nteger

2

, r evi s i o n_ i n ex_ no

, s or t

3

, revi si on_no

, character (2)

4

, revi si on_date

, i nteger

5

, r evi s i o n_ y

, c ar act er 4

6

, checked_by

, char acter( 4)

7

, r ev_ es cr i pt i on

, c ar ac t er 40

8

, appr_by_1

, char acter( 4)

9

, appr_by_2

, char acter( 4)

10, appr _ y_ 3

, c ar ac t er 4

11, appr_by_4

, char acter( 4)

12, appr _ y_ 1_ at e

, i nt e ger

13, appr _ y_ 2_ at e

, i nt e ger

14, appr_by_3_dat e

, i nteger

15, appr _ y_ 4_ at e

, i nt e ger

16, c ec e _ at e

, i n t eger

# Dr awi ng Setup Dat a ta

e num e r

= 1 26, num e r o

c o umns

= 26

1

, drawi ng_t ype

, shor t

, st andard not e

2000

2

,

r a wi ng_ s i z e

, s or t

, s t an ar

1202

3

,

r a wi ng_ sc a e

, c ar ac t er 16


not e

47

Database Overview 4

,

e au t _ pat _ name

, c ar ac t er 36

5

,

e au t _no e

, c ar act er 26

6

, di sci pl i ne_mask

7

,

8

, c el l _ f i l e _s pe c

, c har a c t e r ( 1 4)

9

, ce

, c ar act er 36

a t e r nat e _s ee _ opt

10, ce

, short , s or t

_ pat _ name _net _a

r ess

, c ar act er 26

11, pl ot_cat gy_mask_a

, i nteger

12, p ot _ c at g y_ mas _

, i nt e ger

13,

a e _ mas _ a

, i nt e ger

14, l abel _mask_b

, i nteger

15,

a e _ mas _ c

, i nt e ger

16,

a e _ mas _

, i nt eger

17, custom_1

, char acter( 40)

18, c us t o m_ 2

, c ar a ct e r 40

19, custom_3

, char acter( 16)

20, c us t o m_ 4

, c ar a ct e r 16

21, c us t o m_ 5

, c ar a ct e r 16

22, custom_6

, char acter( 16)

23, c us t o m_ 7

, c ar a ct e r 16

24, c us t o m_ 8

, c ar a ct e r 16

25, custom_9

, i nteger

26, cust om_10

, i nteger

# Re erence Mo e ta

e num e r

Di sp ay Category Setup Data

= 1 27, num e r o

c o umns

= 12

1

, drawi ng_t ype

2

,

3

, categor y_mask_a

, i nteger

4

, c at e gor y _ ma s _

, i nt e ge r

5

, cat egory_mas _c

, i nteger

6

, categor y_mask_d

, i nteger

7

, v

_ c at e gor y _ ms _ a

, i nt e ger

8

, vhl _categor y_msk_b

, i nteger

9

, vhl _categor y_msk_c

, i nteger

10, v


_ cat e gor y _ms _

, shor t

, st andard not e

2000

, s or t

, i n t eger

11, vhl _r ef_ symbol ogy

, shor t

12, v

, s or t

_ sym o ogy

# P ot t i ng De au t Dat a t abl e number


= 6

1

, i p ot _ i n ex_ no

, i nt e ger

2

, i pl ot_number

, char acter( 24)

3

, i p ot _ es cr i p t i on

, c ar act er 40

48


Database Overview 4

, i p ot _ i e_ spec

, c ar act er 14

5

, pat _ name

, c ar ac t er 36

6

, net work_address

, char acter( 26)

# Drawi ng Owners i p Data t abl e number 1

,

2

, si t e_ i


wg_ i n ex _ no

= 2 , i nt e ge r

, i n ex

1

, i ndex

1

, c ar act er 10

# I nter f erence Management Data # C as ta

Management Dat a

e num e r

= 1 31, num e r o

c o umns

= 15

1

, system_uni que_no

2

,

3


4

, uni que_sequence_no

5

, c omp et i o n_ a t e

, i nt e ge r

6

, control _user_no

, short

7

, env _ cr e at i o n_ a t e

, i nt e ge r

8

, c as _ c ec _ opt i on

9

, vol ume_fi l t er_opt


, i nteger , s or t , s or t , i nteger

, s or t

, s t an ar , shor t

10, vo ume_ ow_x

, i nteger

11, vo ume_ ow_y

, i nteger

12, vol ume_l ow_z

, i nteger

13, v o ume_ i g _ x

, i nt e ger

14, vol ume_hi gh_y

, i nteger

15, vol ume_hi gh_z

, i nteger

# C as

not e

1208

, st andard not e

1209

Dat a Per P r oj ec t

t abl e number


= 16

1

, uni que_ c as _ i

, i nt eger

2

, i f _approval _st atus

3

, comp_a_uni que_i d

, i nteger

4

, c omp_ _ uni que _i

, i nt e ge r

5

, model _i ndex_no_a

, i nteger

6

, mo e _ i n ex_ no_

, i nt e ger

7

,

i s ci p i n e_ i n ex_ a

, s or t

8

, di s c i pl i ne_ i nde x_ b

, s hor t

9

, r ec ent _ c as _ t ype

, shor t

, s or t

10, r e cent _ p ot _ at e

, i n ex

1

, st andard not e

1203

, s t an ar

1204

not e

, i nt e ger

11, r ecent_r evi ew_dat e

, i nteger

12, r ecent_sequence_no

, i nteger

, i ndex

13, area_i ndex_no

, shor t

14, act i on_ i s ci p i n e

, s or t

15, recent _seq_no_

, i nteger


2

49

Database Overview 16, ar ea_ i n ex_ no_ # C as

, s or t

Dat a Per J o

t abl e number


= 17

1

, system_uni que_no

, i nteger

, i n ex

1

2

, uni que_cl ash_i d

, i nteger

, i ndex

2

3

, uni que_sequence_no

4

, c as _ t ype

, s or t

, s t an ar

not e

1204

5

, comp_a_r ange_x_l o

, i nteger

6

, comp_a_r ange_y_ o

, i nteger

7

, comp_a_r ange_z_ o

, i nteger

8

, comp_a_r ange_x_hi

, i nteger

9

, comp_a_range_y_ i

, i nteger

not e

1204

, s t an ar

not e

1205

not e

1207

, i nteger

10, comp_a_range_z_ i

, i nteger

11, comp_b_r ange_x_l o

, i nteger

12, comp_ _range_y_ o

, i nteger

13, comp_b_r ange_z_l o

, i nteger

14, c omp_ _ r a nge _x _ i

, i nt e ge r

15, c omp_ _ r a nge _y _ i

, i nt e ge r

16, comp_b_r ange_z_hi

, i nteger

17, e nv _ pa i r _ t y pe

, s or t

, stan ar

, i n ex

1

# Component C as t abl e number

Data Per Proj ect


= 7

1

, uni que_ c omp_ i

, i nt e ge r

2

, comp_t abl e_number

, short

3

, comp_r ow_number

, i nt eger

4

, mo e _ i n ex _no

, i nt e ger

5

, pri mary_descri pt

, character (20)

6

, s ec on ar y_ es cr i pt

7

, comp_model _st atus

, c ar ac t er 40 , short

# Cl ash Revi ew Hi story I nformati on ta

e num e r

= 1 35, num e r o

c o umns

= 8

1

, system_uni que_no

, i nteger

, i ndex

1

2

, uni que_ c as _ i

, i nt eger

, i n ex

2

3

, r e vi e w_ a t e

, i nt e ge r

4

, revi ew_user _no

, shor t

5

, r e spons i _ us er _ no

, s or t

6

, ac t i on

, s or t

7

, r evi ew_comment

, char acter ( 100)

8

, appr ova _ met o

, s or t

, s t an ar

, i nteger

, i n ex

# Cl ash Pl ot Hi story I nf ormati on ta 1

e num e r

= 1 36, num e r o

, system_uni que_no

50

c o umns

= 4 1


Database Overview 2

, uni que_ c as _ i

, i nt eger

3

, p ot _ at e

, i nt e ger

4

, pl ot_user_no

, short

#

Repor t Management Dat a

# Report Data ta

e num e r

= 1 41, num e r o

c o umns

= 20

1

, r e por t _ i n ex_ no

, i nt e ger

, i n ex

1

2

, report _no

, character (24)

, i ndex

2

3

, r epor t _ t i t e

, c ar act er 40

4

, appr ova _ i ni t i a s

, c ar act er 4

5

, approval _date

, i nteger

6


, s or t

7

,

, c ar ac t er 2

8

, r e por t _ f i l e _s pe c

, c har a c t e r ( 1 4)

9

, pat _ name

, c ar ac t er 36


10, net work_address

, char acter( 26)

11,

oc _ owner

, c ar ac t er 10

12,

oc _ st a t us

, s or t

13, l ock_date

, i nteger


, i nt e ger

15,

ormat_i n ex_no

, i nteger

16, f i l t e r _ i ndex _ no

, i nt e ge r

17,

, s or t

as t _ r e v_ i n ex _no

, s t an ar

not e

35

18, r eport _source

, shor t

, st andard not e

1310

19, r eport _t ype

, shor t

, st andard not e

1312

20, s ear c _ i n ex _no

, i nt e ger

# Report Format Data ta

e num e r

= 1 42, num e r o

c o umns

= 11

1

, f ormat_i ndex_no

, i nteger

2

, f ormat_ number

, char acter ( 24)

3

,

4

, f ormat_f i l e_spec

, character (14)

5

, pat _ name

, c ar ac t er 36

6

, net wor _ a

7

, l ock_owner

, char acter( 10)

8

,

oc _ st at us

, s or t

9

,

oc _ at e

, i nt eger

or mat _ es cr i pt i on

, i ndex

1

, c ar ac t er 40

r ess

, c ar act er 26

10, revi si on_dat e

, i nteger

11, r p t _ or mat _ s our c e

, s or t

, s t an ar

not e

1310

# Report Di scr i mi nat i on Data ta 1

e num e r ,

= 1 43, num e r o

c o umns

i t e r _i n ex_ no


= 11 , i nt e ger

, i n ex

1

51

Database Overview 2

,

i t er _ num er

, c ar act er 24

3

,

i t er _ escr i pt i on

4

, f i l t e r _ f i l e_ s pec

, c har a ct e r ( 1 4)

5

, pat _ name

, c ar ac t er 36

6

, net work_address

, char acter( 26)

7

,

oc _ owner

, c ar ac t er 10

8

,

oc _ st at us

, s or t

9

, l ock_date

, i nteger


, i nt e ger

11, r pt _ i t e r _s our c e

, s or t

, c ar act er 40

, s t an ar

not e

1310

, st andard not e

1310

# Report Revi si on Data ta

e num e r

= 1 44, num e r o

c o umns

= 7

1

, r e por t _ i n e x_ no

, i nt e ge r

2

, revi si on_i ndex_no

, short

3

, r evi s i on_ no

, c ar ac t er 2

4

, revi si on_date

, i nteger

5

, r evi s i o n_ y

, c ar act er 4

6

, c ec e _ y

, c ar act er 4

7

, rev_descri pti on

, character (40)

# Repor t Sea r c ta

e num e r

Cr i t e r i a Da t a = 1 45, num e r o

c o umns

= 11

1

, search_i ndex_no

, i nteger

2

, s ear c _ num er

, c ar ac t er 24

3

, search_descri pt i on , character( 40)

4

, search_fi l e_spec

, character (14)

5

, pat _ name

, c ar ac t er 36

6

, net work_address

, char acter( 26)

7

,

, c ar ac t er 10

8

, l o ck _ st a t u s

, s hor t

9

, l ock_date

, i nteger


, i nt e ger

11, r pt_search_source

, shor t

#

oc _ owner

, i ndex

1

Desi gnRevi ew Management Dat a

ta

e num e r

= 1 51, num e r o

c o umns

= 25

1

, revi ew_i ndex_no

, i nteger

2

, r evi ew_ no

, c ar ac t er 24

3

, r evi e w_ t i t e

, c ar act er 40

4

, revi ew_t ype

, shor t

5

, cont r o _ i e_ spec

, c ar act er 14

6

, cont r ol _pat h_name

, char acter( 36)

7

, cont r o _ no e

, c ar act er 26

8

, cont r o _ oc _ owner

52

, i ndex

1

, st andard not e

1410

, c ar ac t er 10


Database Overview 9

, cont r o _ oc _ st at

, s or t

10, c ont r o _ oc _ at e

, i nt eger

11, t ag_f i l e_spec

, character (14)

12, t a g_ pat _ name

, c ar a ct e r 36

13, t ag_node

, char acter( 26)

14, t ag_ oc _ owner

, c ar ac t er 10

15, t ag_ oc _ st at us

, s or t

16, t ag_l ock_date

, i nteger

17, s es s i o n_ r e v_ a t e

, i nt e ge r

18,

, i nt e ger

a e _ r ev_ at e

19, l abe l _ f i l e _s pe c

, c har a c t e r ( 1 4)

20,

a e _ pat _ name

, c ar ac t er 36

21,

a e _ net _a

, c ar act er 26

r ess

22, month_ map

, i nt eger

23,

, i nteger

ay_o _wee _map

24, day_map

, i nteger

25, t i me_ o _ ay

, i nt e ger

#

Pac age/ Re ease Management Data

#

Package Dat a

ta

e num e r

= 1 61, num e r o

c o umns

= 5

1

, pac age_ i n ex _no

, i nt e ger

2

, package_no

, char acter( 24)

3

, pac age_ t i t e

, c ar act er 40

4

, rel ease_revi si on

, character (2)

5

, rel ease_date

, i nteger

#

, i n ex

1

Document Dat a

t abl e number


ocument_ i n ex_no

= 4

1

,

, i nteger

2

, package_i ndex_no

, i nteger

3

, document _source

, short

, st andar d not e

1710

4

,

, s or t

, stan ar

1720

o cument _ t y pe

not e

# Pi pe Support Dr awi ng Management Dat a ta

e num e r

= 1 70, num e r o

c o umns

= 16

1

, support _uni que_no

, i nteger

2

, ganged_i d

, i nteger

3

, gr o upe _ i

, i nt e ger

4


, s or t

5

, model _i ndex_no

, shor t

6

,

, c ar act er 40

7

, drawi ng_fi l e_spec

, character (40)

8

, pat _ name

, c ar ac t er 40

9

, net wor _ a

r awi ng_ t i t e

r ess


, c ar act er 40

53

Database Overview 10, s uppor t _ i nei

, c ar act er 40

11, mat er i a _ i n ex

, c ar ac t er 20

12, revi si on_no , short 13, r e vi s i on_ at e

, i nt e ger

14, drawi ng_st atus

, shor t

15, s eet _ no

, s or t

16, s eet _ t ot a

, s or t

t abl e number


1, we

_i

2, we

_ i _ at a

= 3

, c ar act er 80 , c ar act er 40

3, l ast_modi f i ed_dat e

, i nteger

# I somet r i c Dr awi ng Management Data # I s ome t r i c F i e s Da t a t abl e number


= 11

1

, i s o i e_ i n x_ no

, i nt eger

2

, i s odf l t _ i ndx _ no

, i nt e ge r

3

, i s o i e_t ype

, s or t

4

, i s o i e_spec

, c ar act er 14

5

, pat h_name

, char acter ( 36)

6

, net wor _ a

r ess

, c ar act er 26

7

, i s o_ es cr i pt i on

, c ar ac t er 40

8

, l ock_owner

, char acter( 10)

9

,

, s or t

oc _ st at us

10, l ock_date

, i nteger

11, revi si on_dat e

, i nteger

# Proj ect Opti ons Data t abl e number


= 12

1

, i s opr o j _ i n x_ no

, i nt e ger

2

, i s opr o j _ t a s k_ opt

, s hor t

3

, i sopr oj _name_opt

, shor t

4

, i s opr oj _ wg_ opt

, s or t

5

, i s odf l t _ i ndx _ no

, i nt e ge r

6

, r es er ve _ 1

, c ar ac t er 26

7

, r es er ve _ 2

, c ar ac t er 36

8

, reserved_3

, char acter( 20)

9

,

, c ar ac t er 20

at c _ opt i ons

10, i s opr oj _ name_ a e

, i n ex

1

, s or t

11, i soproj _dwg_l abel

, short

12, s u _ i r ect or y_ opt

, s or t

# Defaul t s Set Data ta 1

e num e r , iso

54

= 1 82, num e r o

t _i n x_ no

c o umns

= 4 , i nt eger


Database Overview 2

, iso

t _t ag

, c ar act er 12

3

, i so

t _ escr

, c ar act er 40

4

, i s odf l t _ r ev _ dat e

, i n ex

1

, i n ex

1

, i nt e ge r

# I sometr i c Desi gn Area De i nit i on Data t abl e number


= 32

1

, i s o_ ar e a_ i n x _ no

, i nt e ge r

2

, ar e a_ i n x_ no1

, s or t

3

, area_i ndx_no2

, shor t

4

, ar e a_ i n x _no3

, s or t

5


, s or t

6

, area_i ndx_no5

, shor t

7


, s or t

8

, s e ec t i on_ mo e

, s or t

9

, i so_area_name

, char acter( 10)

10, i s o_ ar ea_ es c

, c ar ac t er 40

11, user _dat a_i ndx_no

, i nteger

12, i so

, i n t eger

t _ i n x_ no

13, c ont _ i n x_ no1

, s or t

14, cont _i ndx_no2

, shor t


, s or t


, s or t

17, cont _i ndx_no5

, shor t


, s or t

19, cont _i ndx_no7

, shor t

20, cont _i ndx_no8

, shor t


, s or t

22, cont _i ndx_no10

, shor t

23, c ont _ i n x_ no11

, s or t


, shor t


, shor t

26, c ont _ i n x_ no14

, s or t


, shor t

28, c ont _ i n x_ no16

, s or t

29, c ont _ i n x_ no17

, s or t


, shor t

31, c ont _ i n x_ no19

, s or t

32, c ont _ i n x_ no20

, s or t

# I sometr i c User Data ta

e num e r

= 1 84, num e r o

c o umns

= 12

1

, user_ dat a_i ndx_no

, i nteger

2

, t y pe_ o _ us er _ at a

, s or t

3

, us er _ at a_ 1

, c ar ac t er 40


55

Database Overview 4

, us er _ at a_ 2

, c ar ac t er 40

5

, us er _ at a_ 3

, c ar ac t er 40

6

, user_ dat a_4

, char acter( 40)

7

, us er _ at a_ 5

, c ar ac t er 40

8

, user_ dat a_6

, char acter( 40)

9

, us er _ at a_ 7

, c ar ac t er 40

10, us er _ at a_ 8

, c ar ac t er 40

11, user _dat a_9

, char acter( 40)

12, us er _ at a _10

, c ar ac t er 40

# I sometr i c Dr awi ng Ext r acti on Data t abl e number

= 185


r a wi ng_ i n x _ no

= 19

1

,

, i nt e ge r

2

, i s o_ ar e a_ i n x _no

, i nt e ger

, i n ex

1

3

, l i nei d_1

, character (24)

, i ndex

2

4

,

, c ar act er 24

5

, l i nei d_ 3

6

, num e r _ o _ sec t i ons

7

,

8

, batch_ref_no

, character (12)

9

, i s o_ gn_ name

, c ar ac t er 24

10, mo e _ st at us _c o e

, c ar ac t er 2

, i ndex

3

i nei _ 2

, c har a c t e r ( 2 4)

r a wi ng_ num e r

, c ar a ct e r 24

11, model _r evi sed_dat e 12,

, s or t

, i nteger

s t _ e xt r ac t i on_ at e , i nt e ge r

13, tot_ no_extr act i ons

, short

14, no_sheets_extr act

, short

15,

, i nt e ge r

as t _ mt o _ at e

16, mto_t o_mtl _control

, i nt eger

17, no_ o _ r evi s i o ns

, s or t

18, user _dat a_i ndx_no

, i nteger

19, i so_type

, short

# I sometr i c Drawi ng Revi si on I n ormati on t abl e number

= 186


= 12

1

,

r a w_ r e v_ i n x _ no

, i nt e ge r

2

,

r a w_ s t _ i n x_ no

, i nt e ger

, i n ex

1

3

, type_of_r evi si on

, short

, i ndex

2

4

, r evi s i o n_ num e r

, s or t

, i n ex

3

5

, gener at e _ y

, c ar act er 3

6

, checked_by

, char acter( 3)

7

, appr ove _ y

, c ar act er 3

8

, ext racti on_date

, i nteger

9

, ex t r a ct i on_ no

, s or t

10, s eet s _ext r act e

56

, s or t


Database Overview 11, r ev_ es cr i pt i on

, c ar ac t er 60

12, i so

, i n t eger

t _ i n x_ no

# I somet r i c Last Used Occurr ence Data ta

e num e r

= 187

, num e r o

c o umns

1

, tabl e_no

, i nteger

2

,

, i nt e ger

as t _ us e

= 2

# I s ome t r i c S ee t E xt r ac t i o n Da t a t abl e number

= 188


= 7

1

, s eet _ i n x_ no

, i nt e ger

2

,

, i nt e ge r

, i n ex

1

3

, sheet_no

, i nteger

, i ndex

2

4

,

, i nt e ger

5

, tot _no_extr acti ons

6

, l ast_mt o_date

, i nteger

7

, no _ o _ r e vi s i o ns

, i nt e ge r

, i nt e ge r

, i n ex

1

, i ndex

2


as t _ ex t r ac t _ at e , i nteger

# I sometr i c Dr awi ng Re-Extr acti on Data ta

e num e r

= 189

, num e r o

c o umns


= 8

1

,

2

, secti on_no

, short

3

, s t a r t _ t r a ver s a _ x

, i nt e ger

4

, s t a r t _ t r a ver s a _ y

, i nt e ger

5

, s t a r t _ t r a ve r s al _ z

, i nt e ge r

6

, s t ar t _ ent i t y

, s or t

7

, st art _comp_occ

, i nteger

8

, start _seg_occ

, i nteger

# Pi pi ng Desi gn Database # Defaul t Rel ati onal Database Defi nit i on # T e us er mus t not r evi s e t i s

at a as e

e i ni t i on ot er t an t o

# change col umn names. Addi ng user - defi ned col umns and changi ng # l engths of character dat a, wher e val i d, must be perf ormed i n # t e Pr oj ec t A mi ni s t r at o r w en t e pr oj ec t i s cr eat e . # Pi pi ng Segment Data ta

e num e r

= 12

, num e r o

c o umns

= 79

1 , system_uni que_no

, i nteger

2 , l i ne_number_l abel

, character( 40)

3 ,

i ne_i

, c ar act er 24

4 , uni t _ num e r

, c ar ac t er 12

5 , uni t _code

, character( 3)

6 , mo u e_ no

, c ar ac t er 16


, i n ex

1

57

Database Overview 7 , pac age_ s ys t em_ no

, c ar a ct e r 12

8 , t r ai n_ num er

, c ar ac t er 2

9 , f l ui d_code

, shor t

10

,

, c ar a c t e r 16

11

, nomi nal _pi pi ng_di a

, short

12

, pi pi ng_ mat e r _ c as s

, c ar a ct e r 16

13

, gas et _ s epar at i on

14

, i nsul ati on_pur pose

15

, i nsu at i on_t i c

16

, i ns u at i on_ ens i t y

,

17

, heat_t raci ng_r eqmt

18

,

eat _ t r a ci ng_ me i a

19

,

e at _ t r a c i n g_ t e mp

20

, const r ucti on_st at

21

,

22

, st andard not e

125

, st andard not e

220

1074

, short

, s t an ar not e ( u ni t s ) , st andard not e

, s or t

, s t an ar

not e

210

, shor t

, st andard not e

130

, s or t

, s t an ar

not e

50

, approval _st atus

, shor t

, st andard not e

35

23

, s c e u e_ over r i e

, c ar act er 8

, st an ar

not e

332

24

, no r _ oper _ p r e s

,

25

, nor_oper_t emp

, doubl e

26

, a t _ oper _ pr es

,

ou

e

27

, a t _ o per _ t e mp

,

ou

e

28

, nor_dgn_pr es

, doubl e

29

, nor _ gn_ t e mp

,

30

, al t _dgn_pr es

, doubl e

31

, al t _dgn_t emp

, doubl e

32

, s t e am_ out et _ t emp

,

33

, mater_of_constr uct

34

, s a et y _c as s

, s or t

, s t an ar

not e

340

35

, desi gn_st andar d

, shor t

, st andard not e

570

, s or t

, s t an ar

not e

160

i ne _s eque nc e_ no

o

, c ar ac t er 8 , short , ou

e

e

,

_ st at us

36 , desi gn_ar ea_number

ou

ou

ou

ou

ou

200

e

e

e

e

, charact er(6)

, charact er( 10)

37

,

38

, const r ucti on_r esp

, shor t

, st andard not e

160

39

, s upp y _r e sp

, s or t

, s t an ar

not e

160

40

, c oat i ng_ r e qmt s

, s or t

, stan ar

no t e

190

41

, cl eani ng_r eqmt s

, shor t

, st andard not e

230

42

,

, c ar ac t er 4

43

, no r _ op_ pr e s _ uni t s

, s or t

, stan ar

no t e

1064

44

, nor_op_t emp_uni t s

, short

, st andar d note

1056

45

, a t _ o p_ pr e s_ uni t s

, s or t

, s t an ar

not e

1064

46

, al t _op_t emp_uni t s

, shor t

, st andard not e

1056

47

, nor _ gn_ pr e s_ uni t s

, s or t

, s t an ar

not e

1064

48

, no r _ gn_ t e mp_ uni t s

, s ort

, stan ar

no t e

1056

58

es i gn_ r es p

ui _ cat egor y


Database Overview 49

, a t _ gn_ pr es _uni t s

, s or t

, s t an ar

not e

1064

50

, a t _ gn_ t e mp_ uni t s

, s or t

, s t an ar

not e

1056

51

, st eam_t emp_uni t s

, short

, st andar d note

1056

52

, s t r e s s_ s ys t e m_ no

, c ar a ct e r 12

53

, st ress_r eqmt s

, shor t

, st andard not e

360

54

,

y _ sys t em_ no

, c ar ac t er 12

55

,

y _ r e qmt s

, s or t

, s t an ar

not e

360

, st an ar

not e

125

, st andard not e

499

56 , speci f i c_gravi ty_a

, doubl e

57

, s peci i c _gr avi t y_

,

ou

e

58

, s pec i i c _gr avi t y _c

,

ou

e

59

, vi scosi t y

, double

60

,

,

ou

e

61

, s pec _ eat _ r at i o

,

ou

e

62

, soni c_vel oci ty

, double

63

, s ur ac e_ r oug nes s

,

64

, t est_s ystem_no

, char acter( 6)

65

, t est _

, s or t

66

, t e s t _ pr e ss ur e

,

67

, PI D_i d_part_ a

, character( 4)

68

, PI D_ i _par t _

, c ar act er 4

69

, en _ 1_ noz z e_ i

, i nt e ger

70

, end_2_nozzle_i d

, i nteger

71

, a p a_ escr i pt _i

, c ar act er 12

72

, st andard_not e_no

, shor t

73

, pi d_i ndex_no

, i nteger

74

, co or _co e

, c ar act er 8

75

, i nspecti on_i so_i d

, character( 24)

76

, i n ex_ t o _pi _ wg

, i nt e ger

77

, wel d_i d

, character( 80)

ens i t y

ui

78 , sppi d_pi perun_gui d

, charact er( 32)

79

, c ar act er 32

,

sppi _ r awi n g_ gui

ou

ou

e

e

# Pi pi ng Component Dat a ta

e num e r

= 34

, num e r o

c o umns

= 126


, i nteger

2 , pi pi ng_comp_no

, char acter( 20)

3 , c ommo i t y _ name

, c ar a ct e r 6

4 , mo e _ co e

, c ar act er 6

5 , opt i on_code

, shor t

6 , maxi mum_t emp

,

7 , sched_thi ck_basi s

, char acter( 8)

8 , c ommo i t y _c o e

, c ar ac t er 16

9 , MTO_requi rements

, s ort


ou

, i n ex

1

, st andard not e

400

, st andard not e

332

, stan ar

365

e

note

59


,

11

, s or t

, s t an ar

not e

180

, s our c e_ o _ at a

, s or t

, s t an ar

not e

420

12

, PDS_sort _code

, char acter( 6)

13

, p ysi c a _ at a_ i

, c ar act er 8

14

, geometr i c_st andard

, st andard not e

575

15

, wei g t _ c o e

, s t an ar

not e

578

16

, ta

, s t an ar

not e

576

17

, t abl e_suf f i x_red

, short

, standard note

577

18

, mat e r i a s _gr a e

, s or t

, s t an ar

145

19

,

,

20

, bend_angl e

, doubl e

21

,

ace_t o_ ace_ i m

,

ou

e

22

,

i me ns i o n_ a

,

ou

e

23

, di mensi on_b

, doubl e

24

,

,

25

, surf ace_area

, doubl e

26

, empt y _ wei g t

,

ou

e

27

, wat e r _ wei g t

,

ou

e

28

, operator _wei ght

, doubl e

29

, operator_sym_name

, c aracter 6

30

, c ai n_ oper a t or _ no

, s or t

31

, openi ng_acti on

, shor t

, st andard not e

390

32

, c ons t r u ct i on_ s t at

, s or t

, s t an ar

130

33

, hol d_stat us

, shor t

, st andard not e

50

34


, short

, st andard not e

200

35

,

, s or t

, s t an ar

not e

210

36

, heat_t raci ng_t emp

, doubl e

37

, i s o_ wg_ i n e x_ no

, i nt e ge r

38

, i sometri c_sheet_ no

39

, pi ece_mark_no

, char acter( 60)

40

, co or _co e

, c ar act er 8

41

, st ress_node_no

, shor t

42

, s t r es s_ i n t ens _ ac t

43

,

44

, pi pi ng_assembl y

45

, component_group_no

46

, r emar s

47

, st andard_not e_no_a

, short

, st andard not e

499

48

, s t an ar _ not e _no_

, s or t

, s t an ar

not e

499

49

, cp_1_nom_pi pe_di am , short

50

, cp_1_out si e_ i am

,

51

, c p_ 1_ en _ pr e p

, s or t

, s t an ar

not e

330

60

a r i c at i on_ cat

e_ su

i x_ gr een

, short , s or t , s or t

en _r a i us

i me ns i o n_ c


ou

ou

not e

e

e , st andar d note ( u ni t s ) , s t an ar not e ( u ni t s ) , s t an ar not e ( u ni t s )

not e

1010 1028 1028

, charact er(2)

,

ou

ea _ oss_ act or

e ,

ou

e

, char acter( 12) , s ort , c ar ac t er 50

ou

e



, cp_ 1_ sc _ t

, c ar act er 8

53

, c p_ 1_ r at i ng

, c ar ac t er 8

54

, cp_1_face_t o_ctr

, double

55

, c p_ 1_ we

, c ar ac t er 8

56

, cp_1_wel d_type

_ no

, shor t

, st an ar

not e

332

, st andard not e 400

1100

, st andard not e

400

/

o t opt i on 57

, c p_ 1_ gas et _ gap

,

ou

e

58

, cp_1_gasket_opti on

59

, c p_ 1_ s t r e ss _ no e

60

, c p_ 1_ st r e ss _ ac t or

61

, cp_1_head_l oss

62

, c p_ 2_ nom_ pi pe_ i am , s o r t

63


,

64

, cp_2_end_prep

, short

, st andar d note

330

65

, cp_ 2_ sc _ t

, c ar act er 8

, st an ar

332

66

, cp_2_rati ng

, character( 8)

67

, c p_ 2_ ac e_ t o_ ct r

,

68

, c p_ 2_ we

, c ar ac t er 8

69

, cp_2_wel d_type

, short , s or t ,

ou

e , doubl e

_ no

ou

ou

e

not e

e

, shor t


1100

, st andard not e

400

/

o t opt i on 70


71


72


73 , cp_2_str ess_f act or

,

ou

e

, short , s or t , doubl e

74

, cp_2_head_l oss

, doubl e

75


76

, cp_3_out si de_di am

, doubl e

77

, c p_ 3_ en _ pr e p

, s or t

, s t an ar

not e

330

78

, cp_3_sch_thk

, char acter( 8)

, st andard not e

332

79

, cp_3_rati ng

, character( 8)

80


,

81

, cp_3_wel d_no

, char acter( 8)

82

, c p_ 3_ we

, s or t

, s t an ar 400

not e

1100

, s t an ar

not e

400

, s t an ar

not e

330

_ t y pe

ou

e

/

o t opt i on 83

, cp_3_gasket_ gap

84

, c p_ 3_ gas et _ o pt i on

85



, doubl e , s or t , s or t , doubl e

87

, cp_3_ ea _ oss

,

ou

e

88

, cp_4_nom_pi pe_di am , short

89


,

ou

e

90

, c p_ 4_ en _ pr e p

, s or t


61


, cp_ 4_ sc _ t

, c ar act er 8

92

, c p_ 4_ r at i ng

, c ar ac t er 8

93

, cp_4_face_t o_ctr

, double

94

, c p_ 4_ we

, c ar ac t er 8

95

, cp_4_wel d_type

_ no

, shor t

, st an ar

not e

332


1100

, st andard not e

400

/

o t opt i on 96


97


98


99


,

ou

e

, short , s or t ,

ou

e

100, cp_4_head_l oss

, doubl e

101, c p_ 5_ no m_ pi pe _ i a m , s or t 102, cp_ 5_ out si e_ i am

,

103, cp_5_end_prep

, short

, st andar d note

330

104, cp_ 5_ sc _ t

, c ar act er 8

, st an ar

332

105, cp_5_rati ng

, character( 8)

106, c p_ 5_ ac e_ t o _c t r

,

107, cp_ 5_ we

, c ar ac t er 8

_ no

108, cp_5_wel d_t ype

ou

ou

e

not e

e

, short

, st andar d note 400

1100

, st andard not e

400

/

o t opt i on 109, c p_ 5_ ga s et _ g ap

,

110, cp_5_gasket _opt i on

e

, shor t

111, c p_ 5_ s t r e ss _ no e 112, cp_5_st ress_f actor

ou

, s or t , doubl e


, doubl e

114, uni que_ na me

, c ar a c t e r 12

115, vl v_operator _di m_a

, doubl e

116, v v_ oper at or _ i m_

,

117, vl v_operator _di m_c

, doubl e

118, vl v_operator _di m_d

, doubl e

119,

ou

e

as t _ p ac e _ at e

, i nt e ger

120, gener i c_comp_no

, char acter ( 20)

121, i ns pec t i on_ ey

, s or t

122, c p_ 1_ i ns pec t _ ey

, s or t

123, cp_2_i nspect_key

, shor t

124, c p_ 3_ i ns pec t _ ey

, s or t

125, c p_ 4_ i ns pec t _ ey

, s or t


, shor t

# P i p i ng/ T u i ng Da t a t abl e number

= 50


= 61


, i nteger

2 , pi pi ng_ c omp_ no

, c ar a c t e r 20

62

, i n ex

1


Database Overview 3 , c ommo i t y _ name

, c ar a ct e r 6

4 , mo e _ co e

, c ar act er 6

5 , opt i on_code

, shor t

6 , maxi mum_t emp

,

ou

e

,

ou

e

7 , nomi nal _pi pi ng_di a

400

, st an ar

not e

332

, st andard not e

332

, short

8 , out s i e_ i amet er 9 , sc e u e_t i c ness

, st andard not e

, c ar act er 8

10

, sched_thi ck_basi s

, char acter( 8)

11

, r at i ng

, c ar ac t er 8

12

, c ommo i t y _c o e

, c ar ac t er 16

13

, MTO_r equi r ement s

, short

, st andar d note

365

14

,

, s or t

, s t an ar

not e

180

15

, s our c e_ o _ at a

, s or t

, s t an ar

not e

425

16

, PDS_sort _code

, char acter( 6)

17

, geomet r i c _s t an ar

, s t an ar

not e

575

18

, wei ght _code

, st andar d note

578

19

, ta

e_ su

i x_ gr een

, s t an ar

not e

576

20

, ta

e_ su

i x _r e

, s or t

, st an ar

not e

577

21

, materi al s_grade

, shor t

, st andard not e

145

22

, pi pe_ engt

,

ou

e

23

, s ur ac e_ ar e a

,

ou

e

1010

24

, empty_wei ght

, doubl e

25

, wat e r _ wei g t

,

, s t an ar not e ( u ni t s ) , st andar d note ( u ni t s ) , s t an ar not e ( u ni t s )

26

, col d_spri ng_l ength

27


, shor t

, st andard not e

130

28

,

, s or t

, s t an ar

50

29


, short

, st andard not e

200

30

,

, s or t

, s t an ar

not e

210

31


, doubl e

32

, i so_dwg_i ndex_no

, i nteger

33

,

34

, pi ece_mark_no

, char acter( 60)

35

, co or _co e

, c ar act er 8

36

, pi pi ng_ as sem y

, c ar ac t er 12

37

, component_ group_no

38

, r emar s

39

, s t an ar _ not e _no_ a

, s or t

, s t an ar

not e

499

40

, st andard_not e_no_b

, short

, st andard not e

499

41

, en _ 1_ en _ pr ep

, s or t

, s t an ar

not e

330

42

, end_1_wel d_no

, char acter( 8)

43

, en _ 1_ we

, s or t

, s t an ar 400

not e

1100


o

, s or t , short , s or t

i s omet r i c _s eet _ no

e

1028

, doubl e

_ st at us


ou

1028

not e

, c ar ac t er 2

, short , c ar ac t er 50

_ t ype

/

o t opt i on


63


, en _ 1_ gas et _ gap

,

45

, en _ 1_ gas et _ opt

, s or t

46

, end_1_st ress_node

, shor t

47

, en _ 1_ st r e s_ i n t

,

48

, end_1_head_l oss

, doubl e

49

, en _ 2_ en _ pr ep

, s or t

50

, en _ 2_ we

, c ar act er 8

51

, end_2_wel d_t ype

_ no

ou

ou

e , s t an ar

not e

400

, s t an ar

not e

330

e

, short

, st andar d note 400

1100

, st andar d note

400

/

o t opt i on 52

, en _ 2_ gas et _ gap

,

ou

53

, end_2_gasket _opt

, short

54

, en _ 2_ st r e ss _no e

, s or t

55

, en _ 2_ st r e s_ i n t

,

56

, end_2_head_l oss

, doubl e

57

, uni que _name

, c ar a c t e r 12

58

, l ast_pl aced_date

, i nteger

59

, i ns pec t i on_ ey

, s or t

60

, en _ 1_ i n spec t _ ey

, s or t

61

, end_2_i nspect_key

, shor t

ou

e

e

# I nst r ument Component Data ta

e num e r

= 67

, num e r o

c o umns

1 , syst em_uni que_no 2 , i ns t r ume nt _ c o mp_ no

= 133 , i nteger

, i ndex

1

, c a r ac t e r 20

3 , model _code

, char acter( 6)

4 , opt i on_code

, shor t

, st andard not e

400

5 , sc e _ t i c _ asi s

, c ar act er 8

, st an ar

not e

332

6 , MTO_r equi r ement s

, short

, st andar d note

365

7 ,

, s or t

, s t an ar

not e

180

8 , sour ce_of _dat a

, shor t

, st andard not e

430

9 , PDS_sort _code

, char acter( 6)

10

, p ysi c a _ at a_ i

, c ar act er 8

11

, geometr i c_st andard

, st andard not e

575

12

, wei g t _ c o e

, s t an ar

not e

578

13

, ta

, s t an ar

not e

576

14

, t abl e_suf f i x_red

, short

, standard note

577

15

, mat e r i a s _gr a e

, s or t

, s t an ar

not e

145

16

,

,

17

, di mensi on_a

, doubl e

18

,

,

19

, di mensi on_c

, doubl e

20

, s ur ac e_ ar e a

,

ou

e

not e

1010

21

, empt y _ wei g t

,

ou

e

, s t an ar ( u ni t s ) , s t an ar ( u ni t s )

not e

1028

64


e_ su

i x_ gr een

ace_t o_ ace_ i m

i mens i o n_

, short , s or t , s or t

ou

ou

e

e



, wat e r _ wei g t

,

ou

e

, s t an ar ( u ni t s ) , s t an ar ( u ni t s )

not e

1028

23

, oper a t or _ wei g t

,

ou

e

not e

1028

24

, operator _t ype

, doubl e

25

, operator_sym_name

, c aracter 6

26

, chai n_oper ator_ no

, shor t

27

, c ai n_ engt

,

28

, o peni ng_ ac t i on

, s or t

, stan ar

no t e

390

29


, shor t

, st andard not e

130

30

,

o

_ st at us

, s or t

, s t an ar

not e

50

31

,

es i gn_ r es p

, s or t

, s t an ar

not e

160

32

, const r ucti on_r esp

, shor t

, st andard not e

160

33

,

e at _ t r a c i n g_ r e qmt

, s ort

, stan ar

no t e

200

34

,


, s or t

, s t an ar

not e

210

35


36

, i ns u at i on_ pur p os e

, s t an ar

not e

220

37

, i nsulat i on_t hi ck

38

, i ns u at i on_ ens i t y

not e

1074

39

, c eani ng_ r eqmt s

, s or t

, s t an ar ( u ni t s ) , s t an ar

not e

230

40

, safet y_cl ass

, shor t

, st andard not e

340

41

, mo u e_ no

, c ar ac t er 16

42

, pa c age_ s ys t e m_ no

, c ar a c t e r 12

43

, i so_dwg_i ndex_no

, i nteger

44

,

45

, pi ece_mark_no

, char acter( 60)

46

, color_ code

, character( 8)

47

, s t r e s s_ no e_ no

, s or t


48 , str ess_i nt ens_f act

ou

e

, doubl e , s or t , double ,

ou

e

, c ar ac t er 2

, doubl e

49

,

ea _ oss_ act or

,

ou

e

50

, pi pi ng_assembl y

51

, component_ group_no

52

, r emar s

53

, st andard_not e_no_a

, short

, st andard not e

499

54

, s t an ar _ not e _no_

, s or t

, s t an ar

not e

499

55


56


, doubl e

57

, c p_ 1_ en _ pr e p

, s or t

, s t an ar

not e

330

58

, cp_ 1_ sc _ t

, c ar act er 8

, st an ar

not e

332

59

, cp_1_rati ng

, character( 8)

60


,

61

, cp_1_wel d_no

, char acter( 8)

62

, c p_ 1_ we

, s or t

, s t an ar 400

not e

1100

, char acter( 12) , short , c ar ac t er 50

_ t y pe

ou

e

/

o t opt i on


65



,

64

, c p_ 1_ gas et _ o pt i on

65

, cp_1_st r ess_node

66


67

, cp_1_head_l oss

68


69


,

70

, cp_2_end_prep

71

ou

e

, s or t

, s t an ar

not e

400

, short

, st andar d note

330

, cp_ 2_ sc _ t

, c ar act er 8

, st an ar

not e

332

72

, c p_ 2_ r at i ng

, c ar ac t er 8

73

, cp_2_face_t o_ctr

, double

74

, c p_ 2_ we

_ no

, c ar ac t er 8

75

, c p_ 2_ we

_ t y pe

, s or t

, s t an ar 400

not e

1100

, shor t ,

ou

e , doubl e

ou

e

/

( b ol t o pt i on) 76


,

77


78


79


80

, cp_2_head_l oss

81


82


,

83

, cp_3_end_prep

84

ou

e

, short

, st andard not e

400

, short

, st andar d note

330

, cp_ 3_ sc _ t

, c ar act er 8

, st an ar

332

85

, cp_3_rati ng

, character( 8)

86

, cp_3_face_t o_ctr

, double

87

, c p_ 3_ we

, c ar ac t er 8

88

, cp_3_wel d_type

, s or t ,

ou

e , doubl e

_ no

ou

e

, shor t

not e


1100

, st andard not e

400

/

o t opt i on 89

, cp_3_gasket_ gap

90


91



, doubl e , short , s or t , doubl e

93

, cp_3_ ea _ oss

,

ou

94


95


, doubl e

96

, c p_ 4_ en _ pr e p

, s or t

, s t an ar

not e

330

97

, cp_ 4_ sc _ t

, c ar act er 8

, st an ar

not e

332

98

, cp_4_rati ng

, character( 8)

99


,

, s t an ar 400

not e

1100

ou

e

e

100, cp_4_wel d_no

, char acter( 8)

101, c p_ 4_ we

, s or t

_ t y pe

/

o t opt i on

66


Database Overview 102, c p_ 4_ ga s et _ g ap

,

103, c p_ 4_ gas et _ o pt i on

e

, s or t

, s t an ar

104, cp_4_st ress_node 105, c p_ 4_ s t r e ss _ ac t or

ou

not e

400

, shor t ,

ou

e


, doubl e

107, c p_ 5_ no m_ pi pe _ i a m , s or t 108, cp_ 5_ out si e_ i am

,

ou

e

109, cp_5_end_prep

, short

, st andar d note

330

110, cp_ 5_ sc _ t

, c ar act er 8

, st an ar

not e

332

111, c p_ 5_ r at i ng

, c ar ac t er 8

112, cp_5_f ace_t o_ctr

, doubl e

113, cp_ 5_ we

_ no

, c ar ac t er 8

114, c p_ 5_ we

_ t y pe

, s or t

, s t an ar 400

not e

1100

/

( b ol t o pt i on) 115, c p_ 5_ ga s et _ g ap

,

116, cp_5_gasket _opt i on

e

, shor t

, st andard not e

117, c p_ 5_ s t r e ss _ no e 118, c p_ 5_ s t r e ss _ ac t or

ou

, s or t ,

ou

e


, doubl e

120, uni que_ na me

, c ar a c t e r 12

121,

,

en _ ang e

122, vl v_operator _di m_a

, doubl e

123, v v_ oper at or _ i m_

,

124, vl v_operator _di m_c

, doubl e

125, vl v_operator _di m_d

, doubl e

126,

400

ou

ou

e

e

as t _ p ac e _ at e

, i nt e ger

127, gener i c_comp_no

, char acter ( 20)

128, i ns pec t i on_ ey

, s or t


, shor t


, shor t

131, c p_ 3_ i ns pec t _ ey

, s or t


, shor t

133, c p_ 5_ i ns pec t _ ey

, s or t

# Pi pe Support Data t abl e number

= 80


= 50


, i nteger

2 , pi pe_ s uppor t _ no

, c ar a ct e r 20

3 , model _code_phy

, char acter( 6)

4 , mo e _ co e_ og

, c ar act er 6

, i n ex

1

5 , i so_suppor t _t ype_a

, short

, st andard not e

380

6 , i s o_ s uppor t _ t y pe_

, s or t

, s t an ar

not e

380

7 , i s o_ s uppor t _ t y pe_ c

, s or t

, s t an ar

not e

380


67

Database Overview 8 , i s o_ s uppor t _ t y pe_ 9 ,

, s or t

et ai s_ or _s op

, s t an ar

not e

380

, c ar act er 50

10

, de t ai l s _ f o r _ f i el d

11

,

12

, commodi t y_code

, char acter ( 16)

13

, MTO_requi rements

, s ort

, stan ar

note

365

14

,

, s or t

, s t an ar

not e

180

15

, wei ght

, doubl e

1028

16

, c ons t r u ct i on_ s t at

, s or t

, st andar d note ( u ni t s ) , s t an ar not e

17

,

_ st at us

, s or t

, s t an ar

50

18

, st andard_not e_no

, shor t

, st andard not e

499

19

, i s o_ wg_ i n e x_ no

, i nt e ge r

20

,

21

, pi ece_mark_no

, char acter( 60)

22

, co or _co e

, c ar act er 8

23

, i sometr i c_di m_a

, doubl e

24

, i s omet r i c_ i m_

,

ou

e

25

, i s omet r i c _ i m_ c

,

ou

e

26

, i sometr i c_di m_d

, doubl e

27

, i s omet r i c _ i m_ e

,

ou

e

28

, t r ans_ r i gi i t y_ x

,

ou

e

29

, t r ans _ r i gi di t y _ y

, do ubl e

30

, t r ans_ r i gi i t y_ z

,

31

, r o t _ r i gi di t y _ x

, do ubl e

32

, r o t _ r i gi di t y _ y

, do ubl e

33

, r ot _r i gi i t y _z

,

34

, spri ng_gap_l ength

, doubl e

35

, s pi ng_ gap_ i r ec t

, s or t

36

, number _of_ spri ngs

, shor t

37

, l ast_pl aced_date

, i nteger

38

, i ns pec t i on_ ey

, s or t

39

, mark_number

, char acter ( 80)

40

, gr o up_ i

, i nt e ger

41

, ga ng_ i

, i nt e ge r

42

, materi al _grade

, shor t

, st andard not e

145

43

, we

, s or t

44

, mat er i a _ i n ex

, c ar ac t er 16

45

, operati ng_l oad

, doubl e

46

, i nst a

,

47

, hydrostat i c_l oad

, double

48

, t o t a _ movement _ 1

,

a r i c at i on_ or i ent

, c har a c t e r ( 5 0) , c ar act er 20


o


_co e

e _ oa

130

not e

, c ar ac t er 2

ou

ou

ou

ou

e

e

e

e

, i n s u uni t s

--

i s t a nc e

at t r i ut e

68



, t o t a _ movement _ 2

,

ou

e

, i n s u uni t s

, doubl e

, i n subuni t s

--

i s t a nc e

at t r i ut e 50

, r od_di ameter

# Spec i i c at i on/ Mat e r i a # De au t Re at i ona

Re er e nc e Dat a as e

Dat a as e De i ni t i on

# The user must not r evi se thi s dat abase def i ni t i on other t han t o # c ange co umn names. # Pi ping Materi al s Cl ass Data t abl e number


= 23

1

, system_uni que_no

, i nteger

2

, pi ping_mater_cl ass

3

, r evi s i on_ no

, c ar ac t er 2

4

, ver s i on_ no

, c ar ac t er 2

5

, revi si on_date

, character( 10)

6

,

, c ar act er 6

7

, mat e r _o _ cons t r uc t

8

, cor r osi on_al l ow

, doubl e

9

, mat _ es cr i pt i on

, s or t

, character( 16)

ui _ co e

, character( 6)

11,

, c ar act er 6

e

12, t i c ness_ t a

not e

125

, s t an ar

not e

148

, c ar ac t er 6

10, servi ce_l i m_t abl e i a met er _ t a

, s t an ar

e

, c ar act er 6

13, materi al s_tabl e

, character( 6)

14, t i c nes s_ equat i on

, c ar act er 6

15, branch_t abl e

, character( 6)

16, t ap_data_t abl e

, character( 6)

17, vent _ r ai n_ mac r o

, c ar ac t er 6

18, gasket_separ ati on

, char acter( 8)


, short

, st andar d not e

499


, s or t

, s t an ar

not e

499

21, revi si on_mngt _dat e

, i nteger

22,

, c ar act er 6

, st andar d not e

400

en _ e

ect _t a

e

23, pipe_l engt h_t abl e

, character( 6)

# Pi pi ng Commodi t y Speci f i cati on Data ta

e num e r

= 2 02, num e r o

c o umns

= 28

1

, system_uni que_no

, i nteger

2

, pi pi ng_ mat e r _c as s

3

, c ommo i t y _ name

, c ar a c t e r 6

4

, opt i on_code

, shor t

5

, maxi mum_t emp

,

, c ar ac t er 16


, i n ex

ou

1

e

69

Database Overview 6

, gcp_ rom_ nom_ i am

, s or t

7

, gcp_t o_ nom_ i am

, s or t

8

, gcp_end_prep

, short

9

, gc p_ r at i ng

, c ar ac t er 8

10, gcp_sch_thk 11, gcp_ t a

e_ su

ix

, s or t , s or t

13, r cp_ t o_nom_di am

, shor t

14, r c p_ en _ pr e p

, s or t

15, r c p_ r at i ng

, c ar ac t er 8

16, rcp_sch_t hk

, character( 8)

e_ su

330

, s t an ar

not e

576

, s t a n ar

not e

330

, s t an ar

not e

577

, s t an ar

not e

575

, char acter( 8)

12, r cp_ rom_nom_ i am

17, r cp_ t a

, st andar d not e

ix

, s or t

18, c ommo i t y _c o e

, c ar ac t er 16

19, model _code

, char acter( 6)

20, PDS_ sor t _ c o e

, c ar ac t er 6

21, modi f i er

, doubl e

22, geomet r i c _s t an ar

, s or t

23, wei g t _ c o e

, s or t

, s t an ar

not e

578

24, f abri cat i on_cat

, short

, standard note

180

25, mat e r i a s _gr a e

, s or t

, s t an ar

not e

145

26, s t an ar _ not e _no_ a

, s or t

, s t an ar

not e

499

27, st andard_not e_no_b

, short

, st andar d not e

499

, s t a n ar

not e

990

, st andar d not e

400

, st andar d not e

330

, st andar d not e

576

, st andar d not e

330

, s t an ar

577

28, i nput _ or m_ t y pe

, s or t

# Pi ping Speci al ty Speci f i cat i on Data t abl e number


= 26

1

, system_uni que_no

, i nteger

2

, pi pi ng_comp_no

, char acter( 20)

3

, mo e _co e

, c ar act er 6

4

, opt i on_code

, shor t

5

, gcp_f r om_ nom_ di am

, shor t

6


, s or t

7

, gcp_end_prep

, short

8

, gc p_ r at i ng

, c ar ac t er 8

9

, gcp_sc _t

, c ar act er 8

10, gcp_t abl e_suf f i x

, shor t

11, r cp_ rom_nom_ i am

, s or t

12, r cp_ t o_nom_ i am

, s or t

13, r cp_end_prep

, shor t

14, r c p_ r at i ng

, c ar ac t er 8

15, rcp_sch_t hk

, character( 8)

16, r cp_ t a

e_ su

ix

17, p ysi c a _ at a_ i

70

, s or t

not e

, c ar act er 8


Database Overview 18, PDS_ sor t _ c o e

, c ar ac t er 6

19, mo i i er

,

20, geometr i c_st andard

ou

e

, short

, st andar d not e

575

21, wei g t _ c o e

, s or t

, s t an ar

not e

578

22, f abri cat i on_cat

, short

, standard note

180


, s or t

, s t an ar

not e

145


, s or t

, s t an ar

not e

499

25, st andard_not e_no_b

, short

, st andar d not e

499

, s t a n ar

not e

990

, s t an ar

not e

400

, s t a n ar

not e

330

, s t an ar

not e

576

, st andar d not e

330

, standard note

577

, s t an ar

not e

575


, s or t

# I nstr ument Component Speci i cati on Data t abl e number


= 26

1

, system_uni que_no

2

, i ns t r ument _ c o mp_ no

3

, model _code

, char acter( 6)

4

, opt i on_ co e

, s or t

5


, shor t

6


, s or t

7

, gc p_ en _ pr e p

, s or t

8

, gcp_rat i ng

, character( 8)

9

, gcp_sc _t

, c ar act er 8

10, gcp_ t a

e_ su

, i nteger , c ar a c t e r 20

ix

, s or t

11, r cp_ f r om_nom_di am

, shor t

12, r cp_ t o_nom_ i am

, s or t

13, r cp_end_prep

, shor t

14, rcp_rati ng

, character( 8)

15, r cp_ sc _ t

, c ar act er 8

16, rcp_tabl e_suf f i x

, short

17, p ysi c a _ at a_ i

, c ar act er 8

18, PDS_sort _code

, char acter( 6)

19, modi f i er

, doubl e

20, geomet r i c _s t an ar

, s or t

21, wei ght _code

, short

, st andar d not e

578

22,


, s or t

, s t an ar

not e

180


, s or t

, s t an ar

not e

145


, short

, st andar d not e

499


, s or t

, s t an ar

not e

499

, s t a n ar

not e

990


, s or t

# Tap Pr opert i es Data ta

e num e r

= 2 05, num e r o

c o umns

= 8

1

, system_uni que_no

, i nteger

2

, t ap_ t a

, c ar ac t er 6

3

,

e_ name

nomi na _ pi pi ng_ i a

, s or t


71

Database Overview 4

, opt i on_ co e

, s or t

, s t an ar

not e

400

5

, en _ pr e par a t i on

, s or t

, s t a n ar

not e

330

6

, r a t i ng

, c har a c t e r ( 8 )

7

, sc e _t i c

, c ar act er 8

8

, t ap_materi al _code

, char acter( 10)

# Pi ping Commo i ty Si ze-Depen ent Materi a ta

e num e r

= 2 11, num e r o

c o umns

Data

= 10

1

, system_uni que_no

, i nteger

2

, s ys _c ommo i t y _c o e

3

, gcp_nom_ i am

, s or t

4

, r cp_nom_di am

, shor t

5

, gcp_sc _t

, c ar act er 8

6

, r cp_sc _t

, c ar act er 8

7

, commodi t y_code

, char acter ( 16)

8

, we

,

9

, uni t_ pri ce

, c ar ac t er 16

_ wei g t

1

, i n ex

1

e

, double

10, man our s

,

# P i p i ng Commo i t y I mp i e t abl e number

ou

, i n ex

Ma t er i a

ou

e

Dat a


= 10

1

, system_uni que_no

, i nteger

2

, s ys _c ommo i t y _c o e

3


, shor t

4


, s or t

5

, r cp_f r om_ nom_ di am

, shor t

6

, r cp_t o_ nom_ di am

, shor t

7

, c ommo i t y _c o e

, c ar ac t er 16

8

, quant i t y

, double

9

,

a r i cat i on_ cat

, s or t

10, st andard_not e_no

, shor t

, c ar ac t er 16

# Ref er ence Dat abase Revi si on Management Dat a ta

e num e r

= 2 21, num e r o

c o umns

= 8

1

, speci al ty_r ev_dat e

, i nteger

2

, i ns t r _ r e v_ at e

, i nt e ger

3

, t a p_ at a _ r ev_ at e

, i nt e ger

4

, si ze_data_rev_dat e

5

, i mp i e _ r ev_ at e

6

, c mp_ i ns u _ r e v_ at e

, i nt e ge r

7

, f l g_ i ns ul _ r e v_ dat a

, i n t e ge r

8

, c on_ t o _ exc _ at a

, i nteger , i nt e ger

, i nt e ger

# Component I nsul ati on Excl usi on Data ta 1

e num e r

= 2 31, num e r o

, system_uni que_no

72

c o umns

= 13 , i nteger


Database Overview 2


, c ar a c t e r 6

3

, mo e _co e

, c ar act er 6

4

, gcp_npd_f r om

, shor t

5

, gc p_ np _ t o

, s or t

6

, r cp_npd_f r om

, shor t

7

, r c p_ np _ t o

, s or t

8

,

, s or t

, st an ar

not e

200

9

, heat_t r aci ng_t o

, shor t

, st andar d not e

200

, s t an ar

not e

220

, s t a n ar

not e

220

eat _ t r aci ng_ r om

10, i ns u _ pur pos e_ r om , s or t 11, i ns u _ pur p os e_ t o

, s or t

12, nor _oper_t emp_fr om , doubl e 13, nor_ oper_t emp_t o

,

ou

e

# F a nge I ns u at i o n Ex c us i on Dat a t abl e number


= 9

1

, system_uni que_no

, i nteger

2

, bol t ed_ npd_ f r om

, shor t

3

,

o t e _ np _ t o

, s or t

4

,

eat _ t r aci ng_ r om

, s or t

, st an ar

not e

200

5

, heat_t r aci ng_t o

, shor t

, st andar d not e

200

6

, i ns u _ pur pos e_ r om , s or t

, s t an ar

not e

220

7

, i ns u _ pur p os e_ t o

, s t a n ar

not e

220

8

, nor_oper_ t emp_fr om , doubl e

9

, no r _ ope r _ t e mp_ t o

, s or t

,

ou

e

# Pi pi ng Const ruct i on Tol erance Excl usi on Data t abl e number


= 7

1

, system_uni que_no

, i nteger

2

, commodi t y_name

, char acter ( 6)

3

, mo e _co e

, c ar act er 6

4

, gcp_npd_f r om

, shor t

5

, gcp_npd_to

, shor t

6

, r cp_np _ r om

, s or t

7

, rcp_npd_to

, short

# Pi pi ng Support Group ta

e num e r

= 2 40, num e r o

c o umns

= 3

1

, system_uni que_no

, i nteger

2

, s uppor t _ gr o up

, c ar a ct e r 6

3

, gr oup_ es cr

, c ar ac t er 40

# Pi pi ng Support Commodi t y Ref er ence Dat a ta

e num e r

= 2 41, num e r o

c o umns

= 11

1

, system_uni que_no

, i nteger

2

, s uppor t _ gr o up

, c ar a ct e r 6

3


, c ar a c t e r 6


73

Database Overview 4

, np _ r om

, s or t

5

, np _ t o , s or t

6

, t df_t abl e_name

, char acter( 8)

7

, t emp_ t a

, c ar act er 8

8

, sched_t abl e

, character( 8)

9

, at t ac ment _ t y pe

, s or t

e

10, mo e _ co e

, c ar act er 6

11, materi al _desr

, character( 50)

# Pi ping Support Materi a ta

e num e r

Re erence Data

= 2 42, num e r o

c o umns

= 10

1

, system_uni que_no

, i nteger

2


, c ar a c t e r 6

3

, np _ r om

, s or t

4

, npd_to , short

5

, geomet r i c _s t an ar

6

, materi al _i ndex

, character( 16)

7

,

, c ar ac t er 16

8

, i t em_ ey0

, c ar ac t er 2

9

, i t em_key1

, char acter( 2)

10

, s or t

, s t an ar

r awi ng_ see

, i t em_ ey2

not e

575

, c ar ac t er 2

# Pi pi ng Support Descri pti on Data t abl e number


= 7

1

, system_uni que_no

, i nteger

2

, materi al _i ndex

, character( 16)

3

, sequence_number

, shor t

4

, quant i t y

, s or t

5

, di mensi on_att _no

, shor t

6

, i mp i e _ st at us

, s or t

7

, materi al _descr

, character( 80)

74


SECTION 3

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

Graphic Commodity Data and Physical Dimension Data



Material Description Data Standard Notes / Code Lists

  

Label Descriptions Piping Assembly Definitions

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

The supports both approved and unapproved reference data for a project. The Project Control Database contains complete file management data for both an approved and unapproved version of each type of reference data such as the Piping Job Specification or the Graphic Commodity Library. This allows revisions to take place in unapproved files while other activities such as the read the approved files. Once the information in the unapproved files has been verified, it can be posted to the approved reference data files.


75

Reference Data

Delivered Reference Data .............................................................. 76 Piping Job Specification ................................................................ 77 Graphic Commodity Data and Physical Dimension Data............. 87 Material Description Data.............................................................. 87 Standard Note Library ................................................................... 89 Label Description Library .............................................................. 89 Piping Assembly Library ............................................................... 89

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

File Description

Object

Text

Physical Dimension Table Library

us_pcdim.l

us_pcdim.l.t

Piping Job Specification Table Library

us_pjstb.l

us_pjstb.l.t

Short Material Description Library

us_shbom.l

-

Long Material Description Library

us_lgbom.l

-

Specialty Material Description us_spbom.l Library For the DIN RDB substitute din_ for us_ in the listed library file names. The following reference data, which is not unique to any specific practice, is delivered in the PD_Shell product in the win32app\ingr\pdshell\lib directory. Library

File Description

Object

Text

Graphic Commodity Library

pip_gcom.l

pip_gcom.l.t

Piping Assembly Library

assembly.l

assembly.l.t

Label Description Library

labels.l

-

Standard Note Library std_note.l std_note.l.t The following reference data for Equipment Modeling is delivered in the PD_EQP product in the win32app\ingr\pdeqp\dat directory. Library

76


Reference Data File Description

Object

Text


zi_eqpms.li b

Tutorial Definition Library

zi_tutlib.lib -

Cell Library equip.cel You should never point to the delivered files for your reference data since this could cause potential problems when you receive a new version of the software. Instead, you should copy the reference data files to a separate location. The script mkpdsdir.sh will copy the reference data to the appropriate directories after creating the project directory files. For each of the reference data libraries, you can copy the delivered libraries or create a new (empty) library to which you can load customized data.

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

Specification/Material Reference Database - database containing the definitions for piping

materials classes, commodity items, specialty items, and tap properties tables. 

Spec Table Library - library containing the specification tables referenced in the PJS.

The information in the Specification/Material Reference database and Spec Table Library tables is also delivered in the form of neutral files which you can extract and modify. You can use the to create or revise the PJS. The Spec Manager enables you to define or revise the PJS data, and process neutral ASCII files to define data in the PJS.

A piping materials class defines a classification of components based on design data and service limits. Much of the design data is stored in tables so that common information can be accessed by more than one piping materials class. The Piping Materials Class Data table contains 23 attributes. 1 , system_uni que_no , i nteger 2 , pi ping_mater_cl ass , charact er(16) 3 , revi si on_no , charact er( 2) 4 , versi on_no , charact er( 2) 5 , revi si on_dat e , charact er( 10) 6 , f l ui d_code , charact er( 6) , st andar d 7 , mater_of_constr uct , charact er(6) 8 , cor r osi on_ al l ow , doubl e 9 , mat_descri pti on , shor t , st andar d 10, servi ce_l i m_t abl e , character( 6) 11, di ameter_t abl e , character( 6) 12, t hickness_t abl e , character( 6) 13, materi al s_t abl e , character( 6) 14, thi ckness_equat i on , character( 6) 15, branch_tabl e , charact er( 6) 16, tap_data_t abl e , character( 6) 17, vent_drai n_macro , char acter( 6) 18, gasket _separati on , char acter( 8) 19, st andard_note_no_a , short , 20, st andar d_not e_no_b , short , 21, revi si on_mngt _dat e , i nteger


not e

125

not e

148

st andar d not e st andar d not e

499 499

77

Reference Data 22, ben bend_d d_defl efl ect_t abl abl e 23, pi pe_l eng engt h_tabl h_tabl e

, character( character( 6) , charac character( ter( 6)

A sample neutral file for US practice is delivered in the file win32app\ingr\rdusrdb\spec_data\classes.pmc . The following is a partial listing for this neutral file.

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

Conne ct Po int Data Data

Information for connect point data is defined in terms ter ms of two types of connect points known as conventions are used to coordinate the two sets of green and red connect points. The following conventions data: 

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

If a component has ends with different nominal diameters (regardless of other end properties) the larger nominal diameter diameter is designated as the green connect connect point.  If a component has ends with the same nominal diameter but other end properties which differ, the following rules apply: 

78


Reference Data 

If the ends have different termination types (regardless of the values for schedule/thickness) schedule/thickness) the end(s) whose end preparations have the lowest codelist number are designated as the green connect c onnect point.



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

The Piping Commodity Specification Data table contains 28 attributes: 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 10, 11, 11, 12, 12, 13, 13, 14, 14, 15, 16, 17, 18, 18, 19, 19, 20, 20, 21, 21, 22, 22, 23, 23, 24, 25, 25, 26, 26, 27, 27, 28, 28,

system_uni _uni que_n que_no o , i nteger nteger pi pi ng_mater_cl ass , charac charactt er(16) er(16) , i ndex ndex 1 commodi odi t y_name , charact er( 6) opt opt i on_cod on_code e , short short , st anda andard rd not not e 400 400 maxi mum_t emp , doubl doubl e gcp_f gcp_f r om_nom_di am , short gcp_t gcp_t o_nom o_nom_di am , shor shor t gcp_end gcp_end_pr _pr ep , short , st anda andarr d not not e 330 330 gcp_rat cp_rat i ng , charac charactt er( 8) gcp_sch_thk gcp_sch_thk , charact charact er( 8) gcp_t gcp_t abl abl e_suf e_suf f i x , shor shor t , st anda andarr d not not e 576 576 rcp_f r om_nom _nom_di am, short short rcp_t o_nom o_nom_di am, short short r cp_end_prep cp_end_prep , short , st anda andarr d not not e 330 330 rcp_rati ng , charac character( ter( 8) rcp_sch_t rcp_sch_t hk , charac charactt er(8) rcp_tabl rcp_tabl e_suf e_suf f i x , short short , standard standard note note 57 577 commodi odi t y_code , char char acter ( 16) 16) model odel _code _code , char char acter( 6) PDS_sort S_sort _code _code , character ( 6) modi odi f i er , doub doubll e geom geometr i c_st anda andarr d , shor shor t , st anda andarr d note note 575 wei ght ght _code _code , short short , st anda andard rd note 578 578 f abri abri cat cat i on_ca on_catt , short short , st and andard note note 180 180 materi al s_grade , short short , st anda andard rd not not e 145 145 st anda andarr d_not d_not e_no_a e_no_a , short , st anda andarr d not not e 499 499 st anda andarr d_not d_not e_no_b e_no_b , s hor hor t , st anda andarr d not not e 499 499 i nput_f nput_f orm_t ype ype , short short , st anda andard rd not not e 990 990

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

A set of neutral files for US practice are delivered in the files win32app\ingr\rdusrdb\spec_data\*.pcd (one for each piping materials class specified in the classes.pmc file). A set of sample files depicting various options are delivered in the win32app\ingr\pddata\sample\data directory. bend_tbl.pcd

fpipe.pcd

metric_npd.pcd

equiv_npd.pcd gasket.pcd

piplen_tbl.pcd

fluid_code.pcd gskt_tbl.pcd

thickness.pcd


79

Reference Data

This database table contains data for a specific specialty item. It is used to define those specialty items which are used frequently by a particular company or installation. The specialty items are defined for the entire project, they are not partitioned by Piping Materials Class. You can also place specialty items interactively in the model by defining the necessary parameters at the time of placement. placement. No entries in the Material Reference Reference Database are required required for these interactive definitions. The Piping Specialty Specification Data table contains 25 attributes. 1,

system_uni _uni que_n que_no o

, i nteger nteger

2,

pi pi ng_ c om omp_ no no

, c a r ac ac t e r 20

3,

mo e _ c o e

, c ar ac ac t er er 6

4,

opt opt i on_cod on_code e

, short short

5,

gc p_ r om_ nom_ i am

, s or t

6,

gc g c p_ t o_ nom_ i am

, s or t

7,

gcp_end gcp_end_pr _pr ep

, short

8,

gc p_ r at at i ng


9,

gcp_sc gcp_sch h_t hk

, charac charactt er(8)

10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20 , 21 , 22 , 23 , 24 , 25 ,

gc p_ t a

, st anda andarr d

not not e

400 400

, st anda andarr d

not not e

330 330

, s t an an ar

not e

576

, s t an an ar

not e

330

, s t an an ar

not e

577

, st anda andarr d

not not e

575 575

, s or t

, s t an an ar

not e

578

a r i c at at i on_ ca cat

, s or t

, s t an an ar

not e

180

materi al s_grade

, short short

, st anda andarr d

not not e

145 145

e_ su su

ix

, s or t

r c p_ r om_ nom_ i am

, s or t

r c p_ t o_ nom_ di am

, s hor t

r c p_ p_ en en _ pr pr ep ep

, s or t

r c p_ p_ r at at i ng


rcp_sch_t rcp_sch_t hk


r cp cp_ t a

e_ su su

ix

, s or t

p ys i c a _ at a_ a_ i


PDS_sort _code _code

, charact charact er( 6)

mo i i er er

,

geom geometr i c_st anda andard rd

ou

, short short

wei g t _ co co e

e

s t an an ar _ no not e _n _no_ a

, s or t

, s t an an ar

not e

499

s t an an ar _ no not e_ e_ no no_

, s or t

, s t an an ar

not e

499

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

80


Reference Data

This table contains the data for a specific instrument item. It is used to define the instruments which are used frequently by a particular company or installation. The instruments are defined for the entire project, they are not partitioned by PMC. You can also place instruments interactively in the model by defining the necessary parameters at the time of placement. placement. No entries in the Material Reference Reference Database are required required for these interactive definitions. 1

, system_uni _uni que_n que_no o

2

, i nstr ument ent _comp_no , charact charact er( 20) 20)

3

, model odel _code _code

, charact charact er( 6)

4

, opt i on_ co co e

, s or t

5

, gc p_ f r om_ nom_ di am

, s hor t

6

, gc p_ t o_ nom_ i am

, s or t

7

, gc p_ p_ en en _ pr pr e p

, s or t

8

, gcp_rati gcp_rati ng


9

, gc p_ s c _ t


10, gc p_ t a

e_ su su

, i nteger nteger

ix

, s or t

11, r c p_ f r om_ nom_ di am

, s hor t

12, r c p_ t o_ nom_ i am

, s or t

13, 13, r cp_end_prep cp_end_prep

, short

14, r c p_ p_ r at at i ng


15, r cp cp_ s c _ t


16, rcp_tabl rcp_tabl e_suf e_suf f i x

, short short

17, p ys i c a _ at a_ a_ i


18, PDS_ so sor t _ c o e


19, 19, modi odi f i er

, doub doubll e

20, geomet r i c _s _s t an an ar

, s or t

, s t an an ar

not e

400

, s t an an ar

not e

330

, s t an an ar

not e

576

, st anda andarr d not not e

330 330

, standard standard note

577

, s t an an ar

not e

575

21, wei g t _ c o e

, s or t

, s t an an ar

not e

578

22, f abri abri cat cat i on_ca on_catt

, short short

, standard standard note

180

23, mat e r i a s _g _gr a e

, s or t

, s t an an ar

not e

145

24, 24, st anda andarr d_not d_not e_no_a e_no_a

, short

, st anda andarr d not not e

499 499

25, s t an an ar _ no not e _n _no_

, s or t

, s t an an ar

499


not e

81

Reference Data A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\instrment.data .

This table contains the tap properties data that is a function of the tap properties table name and the nominal piping diameter. These tables define the piping taps which can be added to any of the components included in a piping materials class. The system uses the information in these tables and the nominal diameter to provide values for rating, end preparation, schedule/thickness, and tap code. Tap tables do not allow a NPD range; there must be an individual entry for each tap diameter. 1 2 3 4 5 6 7 8

, , , , , , , ,

system_uni _uni que_n que_no o , t ap_t ap_t abl abl e_nam e_name , nom nomi nal _pi ping_di ping_di a , opt opt i on_cod on_code e , end_p end_prr eparati eparati on , r a t i ng , sched sched_t _t hick , t ap_m ap_materi al _code _code ,

i nteger nteger char char acter( 6) short short shor shor t , st anda andarr d not not e 400 400 shor shor t , st anda andarr d not not e 330 330 c ha har a c t e r ( 8 ) charac charactt er(8) char char acter( 10) 10)

A sample neutral file for US practice is delivered in the file win32app\ingr\rdusrdb\spec_data\taps.data . Doubl oubl e_Spaci ng !

Or de der = 2 By=GJ H Dat e=12e=12- May- 1988 Tabl e=

! ! >

>

82

3

5

4 6 Ckd By=RJ W

7 Rev=2

C001 C001 Descr i pti on= on= SWE CL3000 L3000

Di am 0. 375

Opt 691

0. 5

1

0. 5

691

0. 75

1

0. 75

691

Rat i ng

Pr p 591

Sc / T h NREQD

Tap Code E$37591XXX E$37591XXX

CL 30 3000

421

NREQD

E$50421064

591

NREQD

E$50591XXX E$50591XXX

421

NREQD

E$75421064

591

NREQD

E$75591XXX E$75591XXX

-

CL 30 3000 -

def def aul aul t

t aps aps


Reference Data >

1

1

1

691

>

1. 25

1

1. 25 1. 5

691 1

-

>

1. 5 2

691 1

-

>

2

691

-

2. 5 3

691 1

-

3

691

-

3. 5 4

691 1

-

4

691

5

>

>

CL 30 3000

421

NREQD

E001421064

591

NREQ NREQD D

E001591XXX

CL 30 3000

421

NREQD

E1

$2, 421, 064

CL 30 3000

591 421

NREQD NREQD

E1 E1

$2591XXX $2591XXX $5, 4 21 21, 0 64 64

CL 30 3000

591 421

NREQD NREQD

E1 $5591XXX $5591XXX E002421064

591

NREQ NREQD D

E002591XXX

591 421

NREQD NREQD

E2 $5591XXX $5591XXX E003421064

591

NREQ NREQD D

E003591XXX

591 421

NREQD NREQD

E3 $5591XXX $5591XXX E004421064

-

591

NREQ NREQD D

E004591XXX

691

-

591

NREQ NREQD D

E005591XXX

6

691

-

591

NREQ NREQD D

E006591XXX

8

691

-

591

NREQ NREQD D

E008591XXX

10

691

-

591

NREQ NREQD D

E010591XXX

12

691

-

591

NREQ NREQD D

E012591XXX

14

691

-

591

NREQ NREQD D

E014591XXX

16

691

-

591

NREQ NREQD D

E016591XXX

18

691

-

591

NREQ NREQD D

E018591XXX

20

691

-

591

NREQ NREQD D

E020591XXX

24

691

-

591

NREQ NREQD D

E024591XXX

26

691

-

591

NREQ NREQD D

E026591XXX

28

691

-

591

NREQ NREQD D

E028591XXX

30

691

-

591

NREQ NREQD D

E030591XXX

32

691

-

591

NREQ NREQD D

E032591XXX

34

691

-

591

NREQ NREQD D

E034591XXX

36

691

-

591

NREQ NREQD D

E036591XXX

42

691

-

591

NREQ NREQD D

E042591XXX

48

691

-

591

NREQ NREQD D

E048591XXX

-

CL 30 3000

CL 30 3000

The Size-Dependent Data table contains the data for a specific commodity item that is dependent on the commodity code, nominal piping diameter, and schedule/thickness. This table is used for miscellaneous batch reporting, such as construction cost reports and requisition orders, and interfaces to material control, stress analysis, and isometric drawing extraction. There are multiple occurrences for a specific commodity code and a specific pair of green and red nominal piping diameters in the Piping Commodity Size-Dependent Material Data table because schedule/thickness schedule/thickness is not not included in the commodity code. 1 2 3

, , ,

syst em_uni que_no que_no , sys_ commodi odi t y_code y_code , gc gc p_ nom_ di am ,


i nt eger char char act er( 16) s hor t

83

Reference Data 4 5 6 7 8 9 10, 10,

, r cp c p_ nom_ di am , gcp_sch cp_sch_t _t hk , , r cp_sch cp_sch_t _t hk , , commodi t y_code y_ code , wel d_w _we ei ght , , uni t _pr _pr i ce , manho anhour ur s , doub doubll

, s hor t character character ( 8) cha char act er ( 8) , cha char act er ( 16) doub oubl e doubl e e

,

i ndex 1

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

The Implied Material Data table contains the implied material data for a specific commodity item that is dependent on both the piping commodity code and nominal piping diameter range. This data is used strictly for generating implied material for MTO reporting and material control. It is not used for welds, bolts, nuts, or gaskets, but is reserved for other types of implied material, such as caps or stubs, for a specific commodity item. It is also used for f or reporting the implied components of a commodity item (for example, cap screws). A unique commodity code must be defined for each commodity definition. definition. For example, if a commodity code is defined for gate valves from 2" to 14", but you want a different description for a 12" gate valve, you must assign a new commodity c ommodity code to the 12" valve.

84

1

, system_uni _uni que_n que_no o

, i nteger nteger

2

, s ys ys _c _c om ommo i t y _c _c o e


3

, gc p_ f r om_ nom_ di am

, s hor t

4

, gc p_ t o_ nom_ i am

, s or t

5

, r c p_ ro r om_ nom_ i am

, s or t

6

, r c p_ t o_ nom_ di am

, s hor t

7

, c om ommo i t y_ y _ co co e


8

, quant i t y

,

9

, f abr i c at at i o n_ n_ c at at

, s ho ho r t

10, s t an an ar _ no not e _n _no

, s or t

ou

, i n ex

1

e


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


85

Reference Data

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

Temperature and Pressure Service Limits table

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

Nominal Piping Diameter table

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

Thickness Data table Thickness data is determined as a function of the table name and nominal piping diameter. These tables include the minimum, retirement, thread, and preferred thicknesses required in the calculation of piping wall thickness. The tables provide the actual thickness; not a schedule. Therefore, there must be an individual entry for each e ach diameter. You cannot use an NPD range.



Materials Data table This table consists of the materials data that is a function of the table name, material grade, wall thickness range, and temperature. These tables include the properties which are r equired for the calculation of piping wall thickness.



Piping Wall Thickness equation and Branch Reinforcement calculation These tables define formulas for the calculation of piping wall thickness and branch reinforcement to resist positive pressure. The actual equations and their logic are hardcoded in the software.



Branch Insertion table A branch insertion table defines the selection criteria for tee and lateral branches. Branch tables define the reinforcement to be used at tee and lateral branches as a function of the acute angle of intersection and the nominal diameters for the intersecting lines. The types of branch connections include reinforcing weld, coupling, threadolet, reducing tee, nipolet, reinforcing pad, sockolet, tee, weldolet, and so forth.



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

86


Reference Data

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

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

Entries in this library use the EDEN programming language. 

Physical Dimension Dimension Librar ies - contains dimension data for the commodity items. (A

different Physical Dimension Library is required for each type of practice such as, U.S., DIN, or British Standard) The parametric descriptions and dimension tables are also delivered in the form f orm of text libraries which you can extract and modify using the and . Refer to Chapter 4, How PDS Works , for examples of parametric definitions and dimension tables.

The Material Description Data is accessed for 

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



Interfaces to material control systems



Stress analysis Isometric drawing extraction.



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

Material Data in the Specification/Material Database - database tables containing



definitions for commodity items, criteria for implied material, and weld data. Short Material Description Library - contains the short material descriptions for commodity items and taps.



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

items. 

Specialty Specialty Mater Material ial Description Libra Libra ry - contains the material descriptions for specialty

items.


87

Reference Data The material descriptions are also delivered in the form of neutral files which you can modify and post to the libraries. The following shows a portion of a neutral file ffor or the short material description library. ! DEFI NE SHO SHORT DESCRI ESCRI PTI ONS ! Dat e/ Ti me: Wed J ul 7 14: 14: 38: 03 1993 1993 ! Process Processed ed Li brary \ . . \ wi n32a n32app pp\\ i ngr\ rdusrdb rdusrdb\\ us_shbom s_shbom. l ! Cmdt y Co Code ====================================Des Des c r i pt i on======================================== CHAI N_1003 _1003 ' Chai hai nwheel heel ope operr ator each wi t h [ 422] 422] of t otal chai n l ength ength f or [ 426] 426] NPD val ve wi t h commodi odi t y code [ 4 00 00] ' CHAI N_1005 _1005 ' Chai hai nwheel heel ope operr ator each wi t h [ 422] 422] of t otal chai n l ength ength f or [ 426] 426] NPD val ve wi t h commodi odi t y code [ 4 00 00] ' DAABAXAABE ' Moni oni t or, CL1 CL150 50 FFFE, FFFE, st ati on t ype, ype, 4" CL150 L150 i n-l et by 2.5" NHT st ai nl ess st eel eel outl outl et w/ st ai nl ess steel stem l ock ock knob knobs s wi t h 0. 0. 75" 75" coupl coupl i ng i n base base,, w/ shape shapert rt i p nozzl nozzl e, Stang Stang BB BB0309 0309-- 21' 21' DBAAA BAAAXB XBAA AAB B ' Fi r e hydr hydr ant, CL12 CL125 5 FFFE, FFFE, 5" si ze, count count ercl ockwi se open open,, 4. 5" st eamer nozzl nozzl e, t wo 2. 5" hose hose nozzl nozzl es equi equi pped pped w/ caps caps and and chai chai ns, [ 428], 428], Ameri can Darl i ng B- 5050- B' DCBG CBGDXEAD XEADA ' Hose r ack, 300# 300#, FTE, FTE, w/ val ve, wal l mount ount , rt hand hand w/ 100 f t hose & f og nozzl e, Pow Powhatan 30-333' DDAXCJ DAAA ' Spray spri spri nkl nkl er, MTE, TE, f i l l ed cone cone w/ rupt rupt ure disc, 30 304, Gri nnel nnel l , Mul si f yre Proj ector ector S- 1' FAAAA FAAAAAW AWAAA AAA ' Fl ange, ange, CL150, L150, FFFE/ BE, BE, ASTM ASTM- A105, A105, ANSI - B16. B16. 5, WN, [ 409] 409] | bore t o mat ch| ' FAAAA FAAAAAW AWWAA ' Fl ange, ange, CL150, L150, FFFE/ BE, BE, ASTM ASTM- A105, A105, ANSI - B16. B16. 5, WN, cement l i ned, ned, [ 409] 409] | bore t o mat ch| ' FAA FAAABAD ABADI I F ' Fl ange ange,, CL150, L150, RFFE/ FFE/ BE, BE, ASTM ASTM- A182 A182-- F316, F316, ANSI - B16. 16. 5, WN, S-80S bor bor e' FAAAD FAAADBDFFC ' Fl ange, ange, CL150, L150, RFFE/ BE, BE, ASTM ASTM- A182-F11, A182-F11, ANSI - B16. B16. 5, WN, 125 Ra f i ni sh, S- XXS XXS bore' GEAAA EAAAZZ ZZAD ADF ' Paddl Paddl e spacer , CL150, L150, FFTBE, FFTBE, ASTM ASTM- A516-70, A516-70, Ai t ken Z1, Z1, [ 429] 429] ' PAA PAAAAACI I A ' Pi pe, pe, S-104, S-104, BE, ' PAAA PAAAAA AAJJ AAA AAA ' Pi pe, S- 60, BE, BE, ASTM ASTM- A53A53- B Type S' PAAAAAWWXM ' Pi pe , [ 401] , BE, ASTM- A 53 53- B Ty Ty pe pe S, S, c em eme nt nt l i ne d, d, t r e at at e d & wr a pp ppe d' d' PAAA PAAAAB ABBA BAAE AE ' Pi pe, S- STD, BE, BE, ASTM ASTM- A106-B' A106-B' PAD PADAABD AABDGFD ' Pi pe, S- XXS, XXS, PE, ASM ASME- SA335 SA335-- P11' P11' PAFAA PAFAAAW AWAAA AAA ' Pi pe bend, bend, [ 403] 403] , BE, BE, 6 NPD r ad, ASTM ASTM- A53A53- B Type S' POAAAAD AAADI I A ' Ni ppl ppl e, BE, S-80S, 3" l ong, ong, ASTM STM- A312 A312-- TP304 TP304 sml s' PRPA PRPAX XZZAA ZZAAA A ' Rei nfor ci ng pad, pad, [ 425], 425], ASTM ASTM- A53-B A53-B ' PUB PUBZZAW ZZAWVAA VAA ' Pi pe, pe, [ 401], 401], SPE/ SPE/ BLE, pushpush- on j t , 10 f t l ay l ngt ngt h, ASTM STM- A74 A74 w/ r ubbe ubberr gskt' QAEZZ AEZZAK AKTA TAB B ' Reduci educi ng coupl i ng, S- 80, SE, ASTM ASTM- D2467' 2467' SAAQ SAAQZZZA ZZZAAA AA ' Coupl oupl i ng, CL3000 CL3000,, SWE, ASTM ASTM- A105, A105, ANSI - B16. B16. 11' SCAQ SCAQZZZAAA ZZZAAA ' Cap, CL3000, SWE, ASTM- A105' SHAQ SHAQZZZA ZZZABB BB ' Uni on, CL3000, CL3000, SWE, ASTM- A350A350- LF2, MSS- SP- 83' SLAQZZZA ZZZAAA AA ' 90 deg el bow, CL3000, CL3000, SWE, ASTM- A105, A105, ANSI - B16. B16. 11' SLAQZZZA ZZZABB BB ' 90 deg el bow, CL3000, CL3000, SWE, ASTM- A350A350- LF2, ANSI - B16. B16. 11' SLCQZZZA ZZZAAA AA ' 45 deg el bow, CL3000, CL3000, SWE, ASTM- A105, A105, ANSI - B16. B16. 11' SLCQZZZA ZZZABB BB ' 45 deg el bow, CL3000, CL3000, SWE, ASTM- A350A350- LF2, ANSI - B16. B16. 11' STAQ STAQZZZA ZZZAAA AA ' Tee, CL3000, CL3000, SWE, ASTM- A105, A105, ANSI - B16. B16. 11' STBQ STBQZZZA ZZZAAA AA ' Reduci educi ng br anch t ee, CL3000, L3000, SWE, ASTM ASTM- A105, A105, ANSI - B16. B16. 11' STLQZZZA ZZZAAA AA ' Lat er al , CL3000 CL3000,, SWE, ASTM ASTM- A105, A105, ANSI - B16. B16. 11' STMQZZZA ZZZABB BB ' Reduci educi ng br anch l at er al , CL3000, L3000, SWE, ASTM ASTM- A350-LF2, A350-LF2, ANSI - B16. B16. 11' TPAZVZ TPAZVZZA ZAAA AA ' Pl ug, MTE, ASTM ASTM- A105, A105, ANSI - B16. B16. 11' UAAEG AAEGZZVB ZZVBB B ' 1/ 4 bend, bend, CL250, CL250, PE/ MJ BE, BE, AWWA-C110, A-C110, dbl t hk cement l i ned w/ gskt , gl nd & bl t ' URAEKZZ EKZZVB VBB B ' Concentr oncentr i c r educer, educer, CL25 CL250, 0, PLE/ PLE/ MJ BSE, BSE, AWWA-C110 A-C110,, dbl dbl t hk cement l i ned ned w/ gskt, gl nd & bl t ' VAAA VAAAU UXJ AAA AAA ' Gat e val ve, CL150, CL150, FFFE, BB, BB, OS&Y, ASTM ASTM- A395, A395, brnz t r i m, St ockhamD- 623' 623' VAAA VAAAU UXJ AGR ' Gat e val ve, CL150, CL150, FFFE, BB, BB, OS&Y, ASTM ASTM- A395, A395, brnz t r i m, GO w/ si de handw handwheel heel , St ockhamD- 623' 623' VAAB VAABAH AHCCAA CAA ' Gat e val ve, CL150, CL150, RFFE, BB, BB, OS&Y, ASTM ASTM- A216-W A216-WCB, CB, t r i m 8, Crane 47' VBAB VBABALC ALCFAA FAA ' Gl obe val ve, CL150, L150, RFFE, RFFE, BB, BB, OS&Y, ASTM ASTM- A216-W A216-WCB, t r i m 12, Crane 143' 143' VBAB VBABALC ALCFR FRE E ' Gl obe val ve, CL150, L150, RFFE, RFFE, BB, BB, OS&Y, ASTM ASTM- A216-W A216-WCB, NACE, ACE, t r i m 12, Cr ane 143' 143' VCAAUXJ CAA ' Check heck val ve, CL150, L150, FFFE, FFFE, BC, BC, swi swi ng, ng, ASTM ASTM- A395, 395, brnz t r i m, StockhamDStockhamD- 931' 931' VDABAUI BAA ' Bal l val val ve, ve, CL1 CL150 50,, RFFE RFFE,, red. red. port port , end end ent ent r y, f i resaf e, ASTM STM- A216-W 216-WCB, pl pl ated CS bal bal l , CS CS t r i m, J amesbur y 5150' 5150' VEAD EADAZEBA ZEBAA A ' Pl ug val ve, CL150, L150, RFFE, FFE, l ubr ubr i cated, ASTM ASTM- A216-W 216-WCB, 125 125 Ra f i ni sh, Rockwel l 1945 1945'' VEAD VEADAZEC AZECG GR ' Pl ug val ve, CL150, CL150, RFFE, l ubri cat ed, ASTM ASTM- A216-W A216-WCB, CB, 125 Ra f i ni sh, GO w/ si de handw handwheel , Rockw Rockwel el l 4149 4149'' VFLAU FLAUQRJ GR ' Butt erf l y val ve, CL125, L125, FFFE, FFFE, ASTM STM- A395 A395,, t r i m 316, 316, EPT EPT seat, GO w/ si de hand handw wheel heel , Cent ent erl i ne Seri Seri es 504' 504' VYFSA VYFSAH HEEAA EEAA ' Y gl obe val ve, CL1500, L1500, SWE, WB, OS&Y, ASTM ASTM- A105, A105, t r i m 8, Rockwel ockwel l / Edwar d 36124' 36124' WAAAA AAAAAW AWAAA AAA ' 90 deg LR el bow, [ 403], BE, ASTM ASTM- A234A234- WPB, ANSI ANSI - B16. B16. 9' WADAAAW AAAWABL ABL ' 45 deg LR el bow, [ 403], BE, ASTM ASTM- A420A420- WPL6, ANSI - B16. B16. 9' WBAFBA BAFBAW WI KB ' St ub end, end, RFLFE/ RFLFE/ BE, BE, ASTM ASTM- A403-W A403-WP304, P304, ANSI - B16. B16. 9, [ 409] 409] | bore t o mat ch| ' WCAAA CAAAAW AWAAA AAA ' Cap, Cap, [ 403], BE, ASTM- A234A234- WPB, ANSI - B16. B16. 9' WOAAAAW AAAWI FB ' Wel dol dol et, [ 412], 412], BE, | wel dol dol et, | ASTM ASTM- A182-F304 182-F304L' L' WOBSAB BSABQ QAFA ' Sockol et , CL3000 CL3000,, BE/ BE/ SWE, | sockol et , | ASTM ASTM- A105' A105' WOCTABQ TABQAFB AFB ' Thr Thr edol edol et, CL3000 L3000,, BE/ FTE, FTE, | t hredol et, | ASTM STM- A350-LF2' 350-LF2' WODAAAW AAAWAFA AFA ' El bol bol et, [ 412], 412], BE, BE, | el bol bol et , | ASTM ASTM- A105' 105' WOI AAAWAFA ' Latr ol et, [ 412], 412], BE, | l atr ol et, | ASTM STM- A105' 105' WOUSABQ SABQAFA AFA ' Fl atol et, CL3000 L3000,, BE/ BE/ SWE, | f l atol et, | ASTM STM- A105 A105'' WRAAA RAAAAW AWAAA AAA ' Concent oncent r i c r educer educer , [ 414] 414] , BE, BE, ASTM ASTM- A234-W A234-WPB, PB, ANSI - B16. B16. 9' WRBAA RBAAAW AWAAA AAA ' Eccentr i c r educer educer , [ 414] 414] , BE, BE, ASTM ASTM- A234-W A234-WPB, PB, ANSI - B16. B16. 9' WTAAA TAAAAW AWFAL ' Tee, [ 403] 403] , BE, BE, ASTM ASTM- A234-W A234-WP9, ANSI - B16. B16. 9' WTBAA TBAAAW AWAAA AAA ' Reduci educi ng br anch t ee, [ 416] 416] , BE, BE, ASTM ASTM- A234-W A234-WPB, ANSI - B16. B16. 9' WZBZZ ZBZZZZ ZZAZ AZA A ' Rei nfor ci ng wel d, [ 423], 423], carbon st eel ' XAAAAZZI CC ' Gasket asket , CL150, L150, G52, 52, 0.0625" 0.0625" t hk comp sheet, sheet, org f i ber ber / ni t ri l e bi nder, nder, f ul l f ace, ace, ANSI - B16. 16. 21' 21' XDAABZZ ABZZQ QSG ' Gasket, CL150, L150, G653, 653, 0. 125" 125" t hk, 304 304 spi r al wnd, nd, graph f i l l ed, ed, CS cent cent er r i ng, ng, API - 601' 601' YAJ BPFCFFW BPFCFFW ' Cap sc r ews, ASTM- A193A193- B7, $0. 625" di am x 1. 5" l g' YBJ I PFKFFW ' Cap sc r ews, ASTM- A193A193- B7, $1" di am x 3. 5" l g' YZZZH YZZZHZZFFB ZZFFB ' B44, B44, ASTM- A193A193- B8C Cl . 1 st uds w/ ASTM ASTM- A194A194- 8C hvy hex nut s' YZZZM YZZZMZZAA ZZAAA A ' B71, B71, ASTM- A307A307- B machi ne bol t s w/ ASTM- A563A563- A hvy hex nut s'

88


Reference Data The enables you to create, revise, and delete data in the Material Description Libraries. You can use the to load the material data tables in the Specification/Material Database. Refer to Creating Material Takeoffs and Other Reports , page 231 for more information on material descriptions.

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

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

Drawing view specific labels



Drawing view identification labels Drawing block labels

    

Alphanumeric labels Displayable attribute messages Material description attribute messages Isometric drawing labels.

These labels are intelligent graphics with links to the material database. The enables you to define the graphic parameters for a label (such as level, line weight, and color code) and to define the format of the label (what information comprises the label.)


89

Reference Data

The Piping Assembly Library (PAL) contains the piping assembly definitions which define the parameters necessary to place a piping assembly (group of components) automatically in the model. A Piping Assembly object library and text library which contain the definitions for basic assemblies are included in the product delivery. # Dr ai n assembl y PAL ' DRAI N' ! ! Thi s assembl y wi l l pl ace a drai n. The user needs t o pl ace a 1" ! sockol et at t he poi nt the drai n i s desi red. ! PLACE FI TTI NG, 6Q3C88 , BY CP1 ! ! The dat a f r omt he component spec i s r ead i nto t he keywords. ! TERM_TYPE_1 TO 5 gets t he numeri c val ue f or end preparat i on ( eg. 21) ! PR_RATI NG_1 TO 5 gets t he pressur e r ati ng ! GEN_TYPE_1 TO 5 get s t he t extual val ue f or end preparat i on (eg. MALE) ! LOAD_SPEC_DATA = ' 6Q1C76' ! ! Thi s ' I F' st atement det ermi nes i f an opt i onal f l ange i s needed bef ore ! the gat e val ve i s placed. ! I F ( GEN_TYPE_ 1 . EQ. BOLTED ) THEN OPTI ON_RATI NG = PR_RATI NG_1 OPTI ON_ END_ PREP = TERM_ TYPE_ 1 PLACE OPTI ONAL , 6Q2C01 , BY CP2 ENDI F ! ! Pl aces a gat e val ve. Noti ce i n t he spec t hat t hi s t ype of gat e val ve ! i s di f f erent t han a 6Q2C01. ! PLACE VALVE, 6Q1C76 , BY CP1 I F ( GEN_TYPE_ 2 . EQ. BOLTED ) THEN OPTI ON_RATI NG = PR_RATI NG_2 OPTI ON_ END_ PREP = TERM_ TYPE_ 2 PLACE OPTI ONAL , 6Q2C01 , BY CP1 ENDI F ! ! Thi s command al l ows t he user t o pi ck whi ch component t o pl ace. I f t he ! opt i on command i s not used t he s/ w wi l l choose opt i on 1. I n t hi s i nstance, ! wi t hout t he OPTI ON_CODE command wi l l cause an er r or because t here ar e no ! opt i on 1 att r i but es avai l abl e f or 6Q2C16. Anot her possi bl i l t y woul d be t o ! use OPTI ON_CODE = PROMPT. The user wi l l be prompt ed f or whi ch component i s ! d es i r e d. ! OPTI ON_CODE = 163 PLACE FI TTI NG, 6Q2C16 , BY CP1 END

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

90


SECTION 4

This section provides an overview of how the various parts of PDS are used to place components in a model. It also outlines how the information in the model and the accompanying engineering data in the Databases are used for material control. All of the examples used in this chapter use the delivered reference data. This chapter is intended to illustrate how PDS uses the reference data rather than point out various customizable features. Detailed customization information is provided in the Spec Writing for PDS 3D Course Guide and in the Reference Data Manager (PD_Data ) Reference Guide .

This is a good starting point for a discussion of the various parts that make up PDS and how these parts work together. The figure on the following page illustrates what happens when you place a Gate Valve in a piping model. PDS makes extensive use of reference data to control the design process. Because PDS uses reference data to control placement operations, it is said to be specification-driven. When you select a component for placement in the model, the system 





uses the active parameters (such as piping materials class and nominal diameter) to search for the selected item name in the Specification Material Reference Database. If the selected item is found in the RDB, the system reads the specification data for the parameters required to place the component. Included in this information is the model code (or specialty item number) for the selected component and the names of the spec tables defined for the Piping Materials Class. uses the model code (or specialty item number), derived from the RDB, to access the Graphic Commodity Library. The definitions in the Graphic Commodity Library determine the physical tables required to place the component and call the tables in the Physical Dimension Library. places the symbol graphics in the model design file and writes the nongraphic information for the component in the database.


91

How PDS Works

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

92


How PDS Works


93

How PDS Works

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

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

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

94


How PDS Works

Piping Materials Clas s Code The delivered reference data uses a 6 character code for the PMC based on the following convention. F

- Pressure Rating

A

- Material Group

XXXX - Sequence Number from Code List Set 148 Following this convention, 1C003 1 is interpreted as 1

-CL150

C

- Carbon Steels

0031

- CL150 RFFE, CS, Trim 8

Therefore, PMC 1C003 1 equals 150# Carbon Steel, Standard Raised Face, with trim 8. Refer to the listing of Code List Set 148 in the PDS Piping Component Data Reference Guide for information on all the codes. An alternate naming scheme is also described under Code List Set 148. This alternate scheme uses the convention: A - Materials Group B - Materials Type C - Detail Features D - Corrosion Allowance E

- Service

F

- Pressure Rating

Following this convention, CAC5C1 is interpreted as C - Carbon Steels A -CS C - Std RF. std trim 5

- 0.063"

C - Process. hot (-20 to 800° F) 1

-CL150

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


95

How PDS Works

Temp erature Pres s ure Table This attribute identifies the table used to determine maximum pressure as a function of temperature. This table includes the pressure and temperature sets that form the boundary for which the commodity items included in this piping materials class are suitable.

Tabl e _Dat a _Def i ni t i on ' L1001' ! Descr i pt i on= B16. 5 CL150- 1. 1, - 20 t o 800 ! By=DCG Ckd By=DG Rev=0 Dat e=13- Feb- 1987 No_I nput s 1 No_Out put s 1 I nput _I nt er pol at i on 1, Next_ One Uni t s= DF, PSI G ! Temper at ur e Pr essur e - 20 285 100 285 200 260 300 230 400 200 500 170 600 140 650 125 700 110 750 95 800 80 END

Diam ete r Table This attribute identifies the table used to determine the nominal piping diameter (NPD) values for piping and tubing which are valid for this piping materials class. The following table will allow the placement of 1/2" to 36"piping:

Tabl e_Dat a_Def i ni t i on ' D036' ! Descr i pt i on= From 0. 5 t o 36 ! By=NP Ckd By=DG Rev=0 Dat e=22- J an- 1987 No_I nput s 1 No_Out put s 0 Uni t s= NPD_I N ! Di am 0. 5 0. 75 1 1. 5 2 3 4

96


How PDS Works 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 END

Thickness Table This attribute defines a table to be used for optional wall thickness and branch reinforcement calculations. When the table is used, thickness data is determined as a function of nominal piping diameter. The thickness table includes the minimum, retirement, thread, and preferred thicknesses required in the calculation of piping wall thickness. It provides the actual thickness; not a schedule. Therefore, there must be an individual entry for each diameter.

Tabl e _Dat a _Def i ni t i on ' TA501' ! Descr i pt i on= A, 0. 063CA, 0. 0071D<=24, 0. 0075D>=26 ! By=DCG Ckd By=DG Rev=0 Dat e=31- J an- 1987 No_I nput s 1 No_Out put s 8 Uni t s= NPD _I N, I N, I N, I N, SC _TH _I N, SC _TH _I N, SC _TH _I N, SC _TH _ I N, SC _TH _I N ! Di am Mi n Thi ck Ret Thi ck Thr ead Thi ck Pr ef er r ed Schedul es/ Thi cknesses 0. 5 . 147 . 06 S- 160 0. 75 . 154 . 06 S- XS 1 . 179 . 06 S- XS 1. 5 . 2 . 06 S- XS 2 . 154 . 06 S- STD 3 . 216 . 06 S- STD 4 . 237 . 07 S- STD 6 . 28 .1 S- STD 8 . 250 . 1 S- STD 10 . 250 . 1 S- STD 12 . 250 . 1 S- STD -


97

How PDS Works

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

Tabl e_Data_ Def i ni t i on ' ML01' ! Descri pti on= Materi al s per ANSI - B31. 3b- 1988 ! By =EPZ Ck d By=RSM Rev=3 Dat e =03- Oc t - 1 989 No_I nput s 2 No_Out puts 6 I nput_I nterpol ati on 2, Next _One Unit s= I NT, DF, I N, I N, DEC, PSI , DEC, I N ! ! Mat Gr Temp Thi ck Range Y S 116 - 20 .4 20000 116 100 .4 20000 116 200 .4 20000 116 300 .4 20000 116 400 .4 20000 116 500 .4 18900 116 600 .4 17300 116 650 .4 17000 116 700 .4 16500 116 750 .4 13000 116 800 .4 10800 142 - 20 .4 20000 142 100 .4 20000 142 200 .4 20000 142 300 .4 20000 142 400 .4 20000 142 500 .4 18900 142 600 .4 17300 142 650 .4 17000 142 700 .4 16500 142 750 .4 13000 142 800 .4 10800 162 - 20 .4 20000 162 100 .4 20000 162 200 .4 20000 162 300 .4 20000 162 400 .4 20000 162 500 .4 18900 162 600 .4 17300 162 650 .4 17000 162 700 .4 16500 162 750 .4 13000 162 800 .4 10800

Mi l l % 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5 12. 5

To l r nc e Val ue -

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

EL01 Source - ANSI-B 31 .3c. 1986 [Chemical Plant and Petroleum Refinery Piping] Thickness logic from paragraph 304.1, equation 3a

98


How PDS Works Reinforcement logic from paragraph 304.3.3 & Code - Appendix H

where P Design pressure D Pipe outside diameter S Allowable stress read from the Materials table E Joint quality factor determined from the wall thickness attribute Cxxx where xxx is 100

times E Y Coefficient Y read from the Materials table A Additional Thickness (in inches or mm)

Gas ket Gap / Tab le This attribute defines either a single gasket gap value or a table used to determine the gasket gap based on nominal diameter and maximum temperature. If a table is specified, the system uses the NPD of each bolted end and the maximum temperature for the gasket at that end to determine the gap thickness. In this example, the actual gap value (.125) is used rather than a table name.


99

How PDS Works

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

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

Item Name an d Mode l Code When you select the option from the Place Component form, the system sets the Item Name to 6Q1C01. This is the item name for a gate valve in the delivered reference data. The corresponding Model Code for this Item Name is GAT.

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

100

AA 6Q

Piping In-Line Component

BB 1C

Valves

CC 01

Gate Valve


How PDS Works

Option Cod e The option code is a code-listed value that tells the system to retrieve the primary commodity item, a secondary commodity item, or another special option from the Piping Commodity Data. This parameter allows you to select from predefined options at placement. If no option is specified, the system defaults to option 1 (primary commodity item). Option 2 is reserved as the secondary commodity item. The other options are determined by values for Code List Set 400.

Green and Red Conne ct Point Data Since a standard gate valve has the same properties at both ends (connect points) only green connect point data is required. ! AABBCC Gr een CP ! Code Opt Fr om To 6Q1C01 1 3 12

The 3" to 12".

Pr p Rat i ng Sc/ Th TS 21 CL150 NREQD 5

values define the range of NPD values supported by this definition in this example

The (Prp) is a code-listed attribute that identifies the end preparation for the connect point. The system determines the termination type based on the range of values 2 - 199 bolted terminations 300 - 399 male terminations 400 - 599 female terminations Using the values defined in Code List Set 330, the setting 21 indicates RFFE (Raised-Face Flanged End). The identifies the pressure rating for the connect point. The setting CL 150 refers to ANSI pressure rating CL 150. The system interprets the first set of sequential numeric characters as the pressure rating value (150 in this example). The (Sc/Th) exists as alphanumeric data. The value NREQD is used in cases where all of the following conditions apply:   

The thickness value is not required in purchasing the component. Empty weights are not significantly affected by actual thickness values. Either stress analysis is not applicable or, if applicable, the component is to be considered infinitely rigid in stress analysis calculations.

The (TS) is a code-listed attribute (CL576) used to further r eference the source of the generic dimensional data, such as flange data or piping outside diameter data. For AMS standards, it represents the table suffix for the green connect point. The value 5 is the default for US practice. It represents the basis on which most US-practice generic piping tables for dimensional parameters is defined. End Ter mi nat i on Type Rai sed- f ace f l anged


Basi s f or Tabl e Val ues ANSI - B16. 1, B16. 5, API - 605 or MSS- SP- 42, i n t hi s order of pr ecedence

101

How PDS Works

Commodity Code The commodity code is a user-assigned code that together with the NPD and schedule/thickness uniquely defines the component. It defines the customer's commodity code (or part number). This attribute is the index into the Material Description Library. Using the delivered reference data, the commodity code VAABAHCCAA represents V - Valve A - Gate Valve A -CL150 B - Raised Face Flanged Ends A - Carbon Steel H - Trim 8 CC - Crane 47 AA - Blank For valves, the commodity code also defines the name of the dry weight table (required for stress analysis). Refer to Appendix E in the PDS Piping Component Data Reference Guide for a listing of the delivered commodity codes.

Geom etric Ind us try Stan da rd This code-listed attribute (CL575) identifies the source of the data (which is usually an industry standard, such as ANSI, ISO, or DIN, or a company standard) from which the specific geometry of the commodity item can be deduced. This parameter represents the vendor or industry standard, and the material if either affects the dimensions of the commodity item. Code list numbers 2-6999 are reserved for geometry standards that apply to US piping practices. The value 40 indicates 40 = ANSI - B16. 10 [ Di mensi ons of Fer r ous Val ves | | ]

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

102


How PDS Works

Mate rials Grade This code-listed attribute (CL145) identifies the material code, specification, grade-temper, and joint efficiency for the component. This data is used in wall thickness calculations. It can also be used to access physical data in the Graphic Commodity Library. Reviewing CL145, the value 252 indicates A216-WCB.

Weight cod e This code-listed attribute (CL578) defines the weight code for the component. It determines the table to be used in finding the dry weight of the component. It is required for those cases where material causes the dry weight data but not the dimensional data to differ for a specific geometric industry standard. Reviewing CL578, the value 52 indicates 52 = 490 pcf [ Car bon st eel , l ow Cr al l oy steel , st ai nl ess st eel ]

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

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


103

How PDS Works Using the option of the the table access operations used to place the component.

command, you can review

The form displays the physical data libraries and Eden modules that were accessed to place the component. The initial display lists the Eden modules that were accessed. Indented lines indicate a module which was called from another module. The system places an asterisk (*) beside the module name where Eden stopped executing. The system uses the model code (or specialty item number) to access the graphic commodity library. The definitions in the graphic commodity library determine the physical tables required to place the component and call the tables in the physical commodity library. The Graphic Commodity Library (GCL) provides data for commodity items, engineered items, and instruments. It is basically a catalog of component data which is accessed to 

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



assign connect point data from the Specification Material Reference Database define the parametric shape for the model graphics.



PDS Piping uses the Eden Parametric Language to define and place components, specialty items, operators, and envelopes. Eden is a high- level programming language which uses information from the Material Reference Database and model to access parametric and dimensional data. Eden is composed of three major types of modules   

104

Symbol Processors Physical Data Subroutines Parametric Shape Definitions


How PDS Works These modules are designed to carry out two functions: data definition and graphic presentation. The modular approach provides for efficient storage of information in these libraries by enabling common information to be shared by different symbols.

Eden Module Relationships

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



accesses the active component design parameters assigns connect points Calls the required physical data modules



determines and calls the required parametric shape modules.

 

The system retrieves the active component parameters which are dependent upon a connect point from the RDB in terms of green, red, or tap connect point properties. The symbol definition


105

How PDS Works assigns the data corresponding to these connect point types (green, red, or tap) to the physical connect point numbers (CP1, CP2, CP3, CP4 or CP5). The first line of the Eden module defines the type of module and the module name. The following statement is used in the Eden modules to indicate a symbol processor module. Symbol _Pr ocessor ' modul e name'

The module name is determined by the type of component being placed (commodity item or specialty item). For a commodity item, the system searches for the Model Code of the commodity item as the module name. If the Model Code is blank in the Piping Commodity Specification Data, the system searches for the Item Name as the module name. The following lists the symbol processor GAT which is used to control the placement of a gate valve. ! REGULAR PATT ERN, BOLTED OR MALE ENDS GATE VALVE Symbol _Pr ocessor ’ GAT’ Cal l Assi gn_Connect _Poi nt ( GREEN, CP1 ) Cal l Assi gn_Connect _Poi nt ( RED, CP2 ) physi cal _dat a_sour ce = ’ V1’ / / Standar d_Type Cal l Get_Physi cal _Data ( physi cal _dat a_source ) parametr i c_shape = ’ V1’ Cal l Dr aw_Parametr i c_Shape ( par ametr i c_shape ) Val ve_Oper at or = DABS ( Val ve_Oper ator ) I f ( Val ve_Operat or . NE. 0 ) Then I f ( Val ve_Oper ator . LT. 1000 ) Then Subcomponent = ’ OP’ / / Val ve_Oper ator Else Subcomponent = ’ A’ / / Val ve_Oper ator EndIf Operat or_Or i ent = FALSE EndI f Stop End

Listing for Symbol Processor GAT

A subcomponent call in a symbol processor module indicates a sub-symbol processor. Subcomponents are additions to symbols such as an operator on a valve. The first line of a sub-symbol processor module indicates the module type and the module name. Sub _Symbol _Pr ocessor ' modul e name'

The sub-symbol processor name for operators is a concatenation of the characters OP_ and the modifier value from the Piping Commodity Specification Data in the RDB. The value is expressed as a code list number from CL550 (operator/actuator type). If the value is a positive number (such as 3) the operator is placed with the valve. If the value is a negative number (such as -3) the operator is not placed with the valve. (This is useful in segregating large diameter valves which almost always have a valve operator from small diameter valves which frequently do not have an operator.) The symbol processor for the gate valve calls a sub-symbol processor ( Subcomponent = ' OP' / / Val ve_Oper at or ) which places an operator on the valve. The following depicts the subsymbol processor OP_3 which is used to control the placement of a hand wheel operator on the valve. ! HANDWHEEL OPERATOR Sub _Symbol _Pr ocessor ' OP_3' I f ( Oper at or_ Or i ent . EQ. TRUE ) Then pr ompt = 1. 0

106


How PDS Works Cal l Prompt _t o_Or i ent _Oper at or ( pr ompt ) EndI f physi cal _dat a_s our ce = ' OPERATOR_3' Cal l Get _Physi cal _Dat a ( physi cal _dat a_sour ce ) par amet r i c_ shape = ' OP3' Cal l Dr aw_Par amet r i c_Shape ( par amet r i c_s hape ) St op End Listing for Sub-Symbol Processor OP_3

The system uses the physical data definitions to determine the dimension data, weight data, and surface area data using the active design parameters. Physical data modules are identified by the statement Physi cal _Dat a_Def i ni t i on ' modul e name' as the first line in the Eden module.

The module name for a physical data module consists of a symbol type (such as V1, V2, and so forth for valves) and a generic type of geometric industry standard (such as AMS or DIN). You can define multiple physical data modules for the same symbol depending on the type of standard being referenced (for example, V1_AMS for American standards and V 1_DIN for European standards). You can manage ten different sets of logic for table naming conventions for the following industry practices. The corresponding table suffix ranges and the suffix for the Piping Eden physical data modules are indicated below. Practice

Range

Suffix

U.S. Practice

1-99

AMS

European - DIN

100-199

DIN

European - British Standard

200-299

BRITISH_STD

European - Practice A

300-399

EURO_A

European - Practice B

400-499

EURO_B

International - JIS

500-599

JIS

International - Australian

600-699

AUS

International - Practice A

700-799

INT_A

International - Practice B

800-899

INT_B

Company Practice 900-999 COMPANY The geometric industry standard for a component is defined in the Piping Commodity Data table of the Material Reference Database. Each component must be assigned a geometric industry standard if it is to use physical data tables. For most of the delivered symbols, the physical data modules are classified into two categories: specific and generic. The specific physical data module is called by the symbol processor. This module then calls a generic physical data module. Plant Design System 3D Theory

107

How PDS Works

The physical data module V1_AMS determines the specific dimensions (face-to-center and faceto-face) and other physical properties for a gate valve. This is the module called by the symbol processor GAT Physi cal _Data_Def i ni t i on ' V1_AMS' physi cal _dat a_s our ce = ' VALVE_2_AMS' Cal l Get _Physi cal _Dat a ( physi cal _data_sour ce ) Cal l Read_Tabl e ( Tabl e_Name_A, i nput , out put ) Sur f ace_Ar ea = Out put _1 Wet _Wei ght = Out put _2 F_ t o_C_Di m_1 = Out put _3 I f ( Ter m_Type_1 . EQ. Ter m_ Type_2 ) Then F _t o _C _Di m _2 = F _t o _C _Di m _1 El se F_ t o_C_Di m_2 = Out put _4 EndI f F _t o _F _Di m = F _t o _C _Di m _1+ F _t o _C _Di m _2 I f ( Val ve_Oper at or . LE. 24. 0 ) Then Cal l Read_Tabl e ( Tabl e _Name _W, i nput , out put ) Dr y _Wei ght = Out put _1 EndI f Ret ur n End

Listing for Physical Data Module V1_AMS

Gene ric P hys ica l Data Modu les The generic modules contain information which is common to more than one symbol such as flange thickness, gasket separation, and outside diameter. The physical data module V1_AMS calls another physical data module VALVE_2_AMS which contains the generic dimension data for all valves with two connect points. Physi cal _Dat a_Def i ni t i on ’ VALVE_2_AMS’ I nput _1 = Nom_Pi pe_D_1 I f ( Gen_Type_1 . EQ. BOLTED ) Then t abl e_name = ’ BLT’ / / Ter m_Type_1 / / Pr_ Rat i ng_1 / / Gen_Fl ag_Gr een Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_OD_ 1 = Out put _ 1 Thi ckness _ 1 = Out put _ 2 Seat _Dept h_1 = Out put _3 Thi ckness _ 1 = Thi ckness _1 - Seat _Dept h_1 CP_Of f set _ 1 = Gasket _ Sep_1 I f ( Symbol ogy . EQ. MODEL ) Then Thi ckness _1 = 0. 0 Dept h_1 = 0. 0 Pi pe_OD_1 = 0. 0 Body_OD_1 = Fac i ng_OD_1 El se t abl e_name = ’ MAL_ 300_5’

108


How PDS Works Dept h_1 = Thi ckness_ 1 I nput _1 = Nom_ Pi pe_D_1 Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Pi pe_OD_1 = Out put _2 Body_OD_1 = Pi pe_OD_ 1 EndI f El se I f ( Gen_Type_1 . EQ. MALE ) Then t abl e_name = ’ MAL’ / / Ter m_Type_ 1 / / Gen_Fl ag_Gr een Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_OD_1 = Out put _2 Thi ckness _1 = 0. 0 Dept h_1 = 0. 0 Seat _Dept h_1 = 0. 0 CP_Of f set _1 = 0. 0 Pi pe_OD_ 1 = Faci ng_OD_1 Body_OD_ 1 = Fac i ng_OD_1 El se t abl e_name = ’ FEM’ / / Ter m_Type_1 / / Pr_ Rat i ng_1 / / Gen_Fl ag_Gr een Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_OD_1 = Out put _1 Dept h_1 = Out put _2 Seat _ Dept h_1 = 0. 0 Thi ckness _ 1 = 0. 0 I f ( symbol ogy . EQ. MODEL ) Then Dept h_1 = 0. 0 CP_Of f set _1 = 0. 0 Pi pe_OD_1 = 0. 0 Body_OD_1 = Faci ng_OD_ 1 El se CP_Of f set _1 = - Dept h_1 t abl e_name = ’ MAL_ 300_5’ Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Pi pe_OD_ 1 = Out put _2 Body_OD_ 1 = Pi pe_OD_1 EndI f EndI f EndI f I f ( Ter m_Type_2 . EQ. Ter m_Type_1 . AND. Nom_ Pi pe_D_1 . EQ. Nom_Pi pe_D_2 ) Then Faci ng_OD_2 = Faci ng_ OD_1 Pi pe_OD_2 = Pi pe_OD_1 Body_OD_2 = Body_ OD_1 Thi ckness _2 = Thi ckness _1 Dept h_2 = Dept h_1 Seat _dept h_2 = Seat _Dept h_1 CP_Of f set _2 = CP_Of f set _1 El se I nput _1 = Nom_Pi pe_D_2 I f ( Gen_Type_2 . EQ. BOLTED ) Then t abl e_name = ’ BLT’ / / Ter m_Type_2 / / Pr_ Rat i ng_2 / / Gen_Fl ag_Red


109

How PDS Works Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_ OD_2 = Out put _1 Thi ckness _2 = Out put _2 Seat _Dept h_2 = Out put _3 Thi ckness _2 = Thi ckness _ 2 - Seat _Dept h_2 CP_Of f set _2 = Gasket _Sep_2 I f ( Symbol ogy . EQ. MODEL ) Then Thi ckness _2 = 0. 0 Dept h_2 = 0. 0 Pi pe_OD_2 = 0. 0 Body_OD_2 = Faci ng_OD_2 El se Dept h_2 = Thi ckness_ 2 t abl e_name = ’ MAL_ 300_5’ I nput _1 = Nom_Pi pe_D_2 Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Pi pe_OD_2 = Out put _2 Body_OD_2 = Pi pe_OD_2 EndI f El se I f ( Gen_Type_2 . EQ. MALE ) Then t abl e_name = ’ MAL’ / / Ter m_Type_2 / / Gen_Fl ag_Red Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_OD_2 = Out put _2 Thi ckness _2 = 0. 0 Dept h_2 = 0. 0 Seat _Dept h_2 = 0. 0 CP_Of f set _2 = 0. 0 Pi pe_OD_2 = Faci ng_OD_2 Body_OD_ 2 = Fac i ng_OD_2 El se t abl e_name = ’ FEM’ / / Ter m_Type_2 / / Pr_ Rat i ng_2 / / Gen_Fl ag_Red Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Faci ng_OD_2 = Out put _ 1 Dept h_2 = Out put _ 2 Seat _Dept h_2 = 0. 0 Thi ckness _2 = 0. 0 I f ( Symbol ogy . EQ. MODEL ) Then Dept h_2 = 0. 0 CP_Of f set _2 = 0. 0 Pi pe_OD_2 = 0. 0 Body_OD_2 = Faci ng_OD_2 El se CP_Of f set _2 = - Dept h_2 t abl e_name = ’ MAL_ 300_5’ I nput _1 = Nom_Pi pe_D_2 Cal l Read_Tabl e ( t abl e_name, i nput , out put ) Pi pe_OD_2 = Out put _2 Body_OD_2 = Pi pe_OD_2 EndI f EndI f

110


How PDS Works EndI f EndI f Tabl e_Name_A = I t em_Name / / Geo_I nd_St d / / Ter m_Type_1 Tabl e_Name_W = Commodi t y_ Code I nput _1 = Nom_Pi pe_D_1 I nput _2 = Nom_Pi pe_D_2 I f ( Ter m_Type_1 . EQ. Ter m_ Type_2 . AND. Nom_ Pi pe_ D_1 . EQ. Nom_Pi pe_D_2 ) Then Tabl e_Name_A = Tabl e_Name_A / / Pr _Rat i ng_1 / / ’ A’ El se I f ( Gen_Type_1 . EQ. Gen_Type_2 ) Then ! Mal e X Mal e or Bol t ed X Bol t ed ! or Femal e X Femal e Tabl e_Name_A = Tabl e_Name_A / / Pr _Rat i ng_1 / / Ter m_Type_2 / / Pr _ Rat i ng_ 2 / / ’ A’ El se I f ( Gen_Type_1 . EQ. MALE ) Then ! Mal e X Bol t ed and Mal e X Femal e Tabl e_Name_A = Tabl e_Name_A / / Ter m_ Type_ 2 / / Pr _Rat i ng_2 / / ’ A’ El se I f ( Gen_Type_2 . EQ. MALE ) Then ! Bol t ed X Mal e and Femal e X Mal e Tabl e_Name_A = Tabl e_Name_A / / Pr_ Rat i ng_1 / / Ter m_Type_2 / / El se ! Bol t ed X Femal e and Femal e X Bol t ed Tabl e_Name_A = Tabl e_Name_A / / Pr_ Rat i ng_1 / / Ter m_Type_2 / / Pr _ Rat i ng_ 2 / / ’ A’ EndI f EndI f EndI f EndI f Ret ur n End Listing for Physical Data Module VALVE_2_AMS

The parametric shape definition describes the graphics symbol (such as bend, flange, or valve body) which is placed for the component in the model. Parametric shape definitions are used to place symbol graphics in the model or define interference envelopes. This involves the following major functions defining connect point geometry  placing connect points  moving the active location a specified distance  drawing a specific graphic shape 


111

How PDS Works 

placing a center of gravity location.

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

Mod el Para me tric Sh ap e Definition s Model parametric shapes define the symbol graphics to be placed in the model. For example, the parametric shape module for a valve consists of a cylinder, two cones, and a cylinder (flange, valve body, flange). The first line for these modules is of the form Model _Par amet r i c_ Shape_Def i ni t i on ' modul e name'

The module name for a parametric shape module consists of a symbol type (such as V1, V2, and so forth, for valves). The parametric shape module V1 determines the model graphics for a valve. This is the module called by the symbol processor GAT. The parametric shape module OP3 determines the model graphics for a hand wheel operator. This is the module called by the sub-symbol processor OP_3. Model _Par amet r i c _Shape _Def i ni t i on ' V1' Cal l Def i ne_Connect _Poi nt _Geomet r y ( LI NEAR ) Cal l Pl ace_Connect _Poi nt ( CP1 ) Cal l Move_By_Di st ance ( CP_Of f set _1 ) Cal l Dr aw_Cyl i nder _Wi t h_Capped_Ends ( Dept h_1, Faci ng_OD_1 ) l engt h = F_t o_C_Di m_1 - Thi ckness_1 di amet er = 0. 0 Cal l Dr aw_Cone ( l engt h, Body_OD_1, di amet er ) Cal l Pl ace_Connect _Poi nt ( CP0 ) Cal l Pl ace_COG_ Locat i on ( DRY_COG ) Cal l Pl ace_COG_ Locat i on ( WET_COG ) Cal l Pl ace_Connect _Poi nt ( CP2 ) Ret ur n End Listing for Para metric Shape Module V1

Model _Par amet r i c _ Shape _Def i ni t i on ' OP3' Cal l Def i ne_Connect _ Poi nt _ Geomet r y ( OPERATOR ) Cal l Conver t _NPD_t o_Subuni t s ( Nom_Pi pe_D_1, di a ) di st = di a + Mi n_Cyl _Di a * 0. 5 angl e = 90. 0 r adi us = ( Di mensi on_2 - Mi n_Cyl _Di a ) * 0. 5

112


How PDS Works Cal l Dr aw_Cyl i nder_ Wi t h_Capped_Ends ( Di mensi on _1, Mi n_Cyl _Di a ) Cal l Move_by_Di st ance ( - di st ) Cal l Rot ate_Or i ent at i on ( angl e, Secondar y ) Cal l Rot ate_Or i ent at i on ( angl e, Nor mal ) Cal l Move_Al ong_Axi s ( - r adi us, Secondary ) Cal l Dr aw_Tor us ( r adi us, angl e, Mi n_Cyl _Di a ) Cal l Dr aw_Tor us ( r adi us, angl e, Mi n_Cyl _Di a ) Cal l Dr aw_Tor us ( r adi us, angl e, Mi n_Cyl _Di a ) Cal l Dr aw_Tor us ( r adi us, angl e, Mi n_Cyl _Di a ) Ret ur n End Listing for Pa ra metric Shape Module OP3

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


113

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

Gene ric Tab les The spec access for a six-inch gate valve defines the end preparation at both connect points as Raised Face Flanged End (code list value 21) which is a bolted connection. As shown in the listing for VALVE_2_AMS, the table name for a bolted connection on a two-connect point valve is t abl e_name= ' BLT' / / Ter m_Type_1 / / Pr _Rat i ng_1 / / Gen_Fl ag_Gr een

Using the values from the Piping Job Specification (PMC=1C003 1, Item Name=6Q1C01), the actual table name will be BLT _20 _150 _5

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

114


How PDS Works You can use the

option to display the contents of a table.

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

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



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



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

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



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

If the end preparations were different at each end of the valve (such as female threaded by socket welded) then a different set of tables would be required. An additional table look-up is required to access the dimensional data for the valve operator. The following table is required to define the valve operator. MC_Type(G)_Rat(G)_Op_A (P3 1A) Using this table name format, the dimension table for a hand wheel operator on a 6" gate valve is: Plant Design System 3D Theory

115

How PDS Works GAT_BLT_150_3_A This table returns the stem length and the wheel diameter for the handwheel operator.

Piping segments are used to define the basic geometry of a pipeline and to carry common attributes such as material class and NPD. All components placed in a piping model have an underlying segment. Segment data is stored in table 12 of the Design Database. Data specific to a component is stored in table 34 of the Design Database. When you place components on an existing piping segment (with or ), the system determines what type of component should be placed based on the configuration and attributes of the segment(s) at the active placement point.

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

The reads the Commodity Item Name table when placing a component at the vertex of an existing piping segment. This table lists the Item Names of the components to be used at different segment configurations (such as reduction, branching, or direction changes). It enables you to relate the component types hard-coded in the software with the applicable commodity item codes (item names). As the system processes the segment for component placement, it uses the derived item name from the table to reference the Piping Commodity Specification Data table of the Material/Reference Database.

116


How PDS Works When placing change of direction components, this table is used in conjunction with the Bend Deflection Table.

The bend deflection table is used when placing components at the vertex of an existing piping segment. The system uses the bend angle at the segment vertex to determine the type of component to be placed. This table defines which full size and reducing size component types will be placed for a specified angle range. The angle is defined as the smallest angle that the continuation of one pipe run makes with the other run. The component types are defined in the commodity item name table.

Each Piping Materials Class references a set of branch tables: one for 90-degree branches, one for 45- degree branches, and one for 45-to90 degree branches. Branch tables define the reinforcement to be used at tee and lateral branches as a function of the acute angle of intersection and the nominal diameters (first and second size) for the intersecting lines. The system accesses the branch table when placing a component at an intersection when no branch component exists at that location.


117

How PDS Works The system uses the information in the table and the first and second size to provide the item name of the component to be used at the intersection. Typically, the codes are from one of the following types:

  

Reinforcing elements, such as reinforcing welds and pads. Weld-on components reinforcing the intersection such as saddles and weldolets. Weld-in components actually making the intersection such as laterals and tees.

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

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

118


How PDS Works


119

How PDS Works

120


SECTION 5

This chapter describes the basics of 3D modeling using the Tasks.

Modeling Setup Requirements....................................................... Graphics Environment for PDS 3D ............................................... Creating Equipment Models .......................................................... Equipment Modeling Commands .................................................. Creating Piping Models ................................................................. Piping Design Commands .............................................................


and

121 125 138 147 149 163

121

Creating 3D Models

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

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

Loading PDS 3D products. Editing the control script to identify the location of the project data.



Setting up a project and creating the associated database schemas.



Accessing the PDS 3D products remotely.



 

Becky: should the last bullet item be removed?

Refer to the Reference Data Manager Reference Guide for information on defining the reference data for a project. This data must be defined before you can work in a model. Also refer to the in the Pr oject Administrator Reference Guide for information on selecting whether to use the approved or unapproved version of the reference data for a model file.

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

122


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

See chapter 6 of the Project Administrator (PD_Pr oject) Reference Guide for detailed information on the .

The

is used to create, revise, or delete model files. Refer to the Pr oject Administrator Reference Guide for information on creating a piping model and database files. You can attach reference models defined in the other PDS 3D disciplines while working in a piping model. Refer to the following documents for information on creating and manipulating models for the PDS 3D disciplines. 

PDS Piping Design Gra phics Reference Guide



PDS Equipment Modeling Reference Guide



Frame Works Plus Reference Guide



PE HVAC Modeling Reference Guide



EE Raceway Modeling Reference Guide


123

Creating 3D Models

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

In this example, there are 63 active levels and 252 referenced levels which you can control (the two equipment models use the same levels and symbology). If a certain type of duct in the HVAC model resides on Level 30 in that model, and all unapproved Instruments are to be placed on Level 30 in the piping model, these are treated as two completely different levels. That is, you can turn off the display for the duct types on Level 30 in the HVAC model (via the Reference Model controls) without affecting the display of unapproved instruments in the active piping model. All PDS users are encouraged to develop a logical, organized level control standard to manage interdiscipline design files. The delivered seed file parameters for each application provide a logical, organized, and coordinated level designation and control scheme. You can customize the delivered parameters, but it is highly recommended that careful thought be given to the custom setup. Once you develop a convention, whether it be the standard deliverable settings or an inhouse standard, . There is no easy way to propagate these changes to the existing graphics in all the design files. The existing graphics will reflect the old settings and any new graphics will reflect the modified settings. Since some applications rely on level assignments to perform basic functions (such as placement of approved or unapproved items) which are transparent to the user, there is a very real chance of destroying the integrity of the project if a symbology change is initiated after the project is under way. For this reason, Intergraph recommends that you do not change the basic structure of the symbology without careful thought. Attributes such as line weights, colors, and line types are 124


Creating 3D Models open to customization, but they should be established prior to project creation and should not change throughout the life of the active design. Level assignments are also customizable; however, they should be established before any components are placed in the model files.

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

PDS 3D (Equipment, Piping, and Drawing) Graphic symbology and level assignments are stored as Type 63 data in the project or model seed files. Changes in project seed data will be reflected in all subsequent models or drawings, while changes in a model or drawing file's seed data will apply only to that design file. The delivered settings are shown in Chapter 6 of the Project Administrator (PD_Project) Reference Guide . The seed data is accessed through the function of the . You can create a report of all Type 63 data at any time. Settings are changed through a forms interface in the Project Data Manager session.



Structural (FrameWorks Plus) The graphic symbology and level assignments are stored in an ASCII file in the delivery directory of the FrameWorks Plus product, and are copied into the project directory during project creation. There are both predefined and user-definable categories (such as New and Existing). The default data can be changed using a text editor such as Notepad. The saved changes are then adapted into the model. The file used for FrameWorks Plus models is framewks. txt



Electrical (EE Raceway) The graphic symbology is delivered with all categories set to Level 1. This is the only application within Process & Power which leaves symbology definition totally up to the user, and it is required prior to accessing a design file. The default data is defined through a forms interface during project setup. The procedure is outlined in the EE Raceway Modeling Reference Guide .



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


125

Creating 3D Models

The PDS 3D products provide an interactive graphics environment (based on MicroStation) for the creation and manipulation of design elements. Like the other modules of PDS these graphics environments are accessed through PD_Shell. The following outlines the basic steps to access the graphic environment for most PDS 3D products: 1. Select the project from the PD Shell form and select the product you wish to use. 2. Select the 3D design area for the model to be entered. 3. Select the model to be entered. The system verifies that you have write access to the selected model. If so, it activates the gra phical user interface for the selected modelfile.

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

126


Creating 3D Models

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


127

Creating 3D Models

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

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

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

128


Creating 3D Models

View Wind ows

displays a list of window actions. Double-clicking on this button deletes the window. To choose an action from the menu, drag the data button to move the cursor through the list, releasing when the correct item is selected. •

restores a minimized or maximized window to the previous size and location. moves a window around the workspace.

• •

changes the height and width of the window in the direction indicated by the pointer.

•

collapses a window down to its smallest size. Clicking on this icon once the window has been collapsed will restore it to its original size.

•

enlarges a window to its maximum size. If you choose this menu entry on a window that is already at its maximum size, the window is restored to its previous size and location.

• •


moves a window to the bottom of the window hierarchy. deletes a window.

129

Creating 3D Models collapses a window. enlarges a window to its maximum size. If you choose the maximize button on a window that is already at its maximum size, the window is restored to its previous size and location. allows you to drag the view to the left or right in the window. allows you to drag the view up or down in the window.

drag the data button on the title bar to move the window to a new location on the screen. appear when the cursor is over the top or bottom of the frame. Drag the data button to change the height of the window as you move the cursor. appear when the cursor is over the left or right side of the frame. Drag the data button to change the width of the window as you move the cursor. appear when the cursor is over the frame corners. Click and drag the data button to change both the height and width of the window without changing the position of the opposite corner.

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

130


Creating 3D Models The

form from the

product is shown below.

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

Se lec ting Options You move through the forms by selecting function buttons or other gadgets from the form. Select means to place the screen cursor (which appears as an arrow) on top of a screen gadget and press . For most of the forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting  . You will use the select action to select functions, access other forms, activate data fields, toggle buttons, select from lists, scroll through data displayed on the screen, and so on. The following summarizes other basic actions you will use in the environments: 

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



— If you make a mistake while keying in text, press the key to erase character(s) to the left of the cursor. Windows Editing — You can use standard Windows editing commands to edit key-in fields.




131

Creating 3D Models

There are many gadgets in the environments that are common to most or all of the forms. These tools and their functionality are described below. The command activates on-line Help for the active form. Help remains active until you delete the Help window. The

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

The  is used to accept a selection or operation. Depending on the active form or option, the active form will remain active so that you can repeat a similar operation or control returns to the preceding form. The command with the curved arrow abandons the current form, returning to the immediately preceding form in the hierarchy.

Some screen menus have a scrolling list of projects or applications. You need to scroll a list only if more options are available than can be displayed in the window. To scroll a list, select the arrow buttons on the side of the list. The list scrolls up or down depending on which arrow you choose. To scroll one line at a time, select the smaller arrows. To scroll one window at a time, select the larger arrows. You can also drag the slider up or down the bar by selecting it with the button, keeping the button depressed, and moving the mouse up or down. The items scroll through the window as you move the button. The size and position of the slider on the scroll bar is an indication of the number of lines and the relative position within the list. All commands which display a list of design areas or models will order the list alphanumerically by the design area number or model number in ascending order.

132


Creating 3D Models

Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark gray. You can select a key-in field and key in a new value. A bar cursor appears in the active key-in field. Key in your input and press . To change afield, reselect the field and key in the desired information. Key-in fields have a maximum number of characters depending on the item being defined. Key-in fields that appear on forms built with Form Builder accept EMACS editing commands. If you select a key-in field for a code-listed attribute, the system activates a form which lists the code list values for the selected field. Microstation requires lowercase characters for the file specification and path name of all dlistesign files. Therefore, the system will automatically convert any input for the file specification and path name of a design file (such as a model or drawing) to lowercase before loading into the Project Control Database.

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

At the bottom of some key-in and display fields, there are two buttons marked with arrows. These buttons are called shift left and shift right buttons. Often, you can key in more characters than a field display shows. Shift Left moves the text display to the front of field; Shift Right moves the text display to the end of the field.

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


133

Creating 3D Models

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

If you press along the edge of a form or any area not occupied by a button, key-in field, or other gadget, the box of icons shown at right displays. You can manipulate form windows just like any other workstation window. The following list defines in order the available window icons.

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

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

134

To revise the location of the form display, Cancel any other forms. The base form should be the only form displayed. Move the form to the desired location.


Creating 3D Models 

Select the command to save the active form location. All subsequent forms will display in the saved location.

You can use the to modify seed information for the project seed files or for a specified model. These options affect all of the project seed files and the project marker file.

Select the option for the type of 3D data to be revised. The following report shows the delivered settings for the 3D data. Pl ant Coor di nat e Syst em Def i ni t i on Pl ant Coor di nat e System Descr i pt i on : Pl ant Coor di nate Syst em Pl ant Coor di nat e Syst em Monument : East i ng : E 0’ 0" Pl ant Nor t hi ng : N 0’ 0" Pl ant El evat i on : El 0’ 0" Pl ant Desi gn Vol ume Coor di nat e Syst em Def i ni t i on Desi gn Vol ume Coor di nat e Syst em Descr i pt i on : Desi gn Vol ume Coor di nat e Syst em Desi gn Vol ume Coor di nat e Syst em Monument : Monument i n Desi gn Vol ume Coor di nat e Syst em : East i ng : E 0’ 0" Pl ant Nor t hi ng : N 0’ 0" Pl ant El evat i on : El 0’ 0" Pl ant


135

Creating 3D Models Desi gn Vol ume Monument i n Pl ant Coor di nat e Syst em : East i ng : E 0’ 0" Pl ant Nor t hi ng : N 0’ 0" Pl ant El evat i on : El 0’ 0" Pl ant Or i ent at i on of Desi gn Vol ume Coor di nat e: East Or i ent at i on of Desi gn Vol ume Coor di nat e Syst em as cl ockwi se Angul ar Of f set of Desi gn Vol ume Nort h f r om Pl ant Nort h : 0. 000000 Coor di nat e Label / Readout Descr i pt i ons Coor di nat e System Label : Desi gn Vol ume : Si t e Pl ant : Pl ant Wor l d : Wor l d Coor di nat e Syst em Readout : Desi gn Vol ume : Pl ant : Pl ant Wor l d : Wor l d Coor di nat e Axi s Label : East : East West : West Nort h : Nort h Sout h : Sout h El evat i on : El ev Coor di nat e Axi s Readout : East : E West : W Nor t h : N Sout h : S El evat i on : El Di mensi oni ng : Engl i sh Coor di nat e Label Pr ef i x/ Suf f i x Mat ch Li ne : Mat ch Li ne Cent er Li ne : CL Top Of St eel : TOS Top of Concr et e : TOC Bat t er y Li mi t : Bat t er y Li mi t Bot t om of Pi pe : BOP I nver t El evat i on : I nver t Pl at f or m El evat i on : Face of Fl ange : F/ F User Def i ne 1 : User Def i ne 2 : User Def i ne 3 : User Def i ne 4 : User Def i ne 5 : User Def i ne 6 : User Def i ne 7 : User Def i ne 8 : User Def i ne 9 : User Def i ne 10 : User Def i ne 11 : User Def i ne 12 : User Def i ne 13 : User Def i ne 14 : User Def i ne 15 :

136


Creating 3D Models User Def i ne 16 : User Def i ne 17 : User Def i ne 18 : User Def i ne 19 : User Def i ne 20 : Coor di nat e Label / Readout For mat Coor di nat e Label For mat s : 10’ East Pl ant 10’ Pl ant East East 10’ Pl ant ( Act i ve) East Pl ant 10’ Pl ant 10’ East Pl ant East 10’ Label Descr i pt i on On Coor di nat e Readout : 10’ E Pl ant 10’ Pl ant E E 10’ Pl ant ( Act i ve) E Pl ant 10’ Pl ant 10’ E Pl ant E 10’ Readout Descr i pt i on On Coor di nat e Label / Readout Uni t s Label Uni t s : Mast er Uni t s and Subuni t s Readout Uni t s : Mast er Uni t s and Subuni t s Met r i c Syst em of Uni t s Label : Subuni t s Onl y Label Descri t i ons : Mast er Uni t s Shor t Descri pt i on : ’ Subuni t s Shor t Descr i pt i on : " Mast er Uni t s and Subuni t s Separat or : Subuni t s and Fr act i on of Subuni t s Separat or : Readout Descr i pt i ons : Mast er Uni t s Shor t Descri pt i on : ’ Subuni t s Shor t Descr i pt i on : " Mast er Uni t s and Subuni t s Separat or : Subuni t s and Fr act i on of Subuni t s Separat or : Secondary Uni t s Descr i pt i ons : Mast er Uni t s Shor t Descr i pt i on : M Subuni t s Short Descr i pt i on : MM Mast er Uni t s and Subuni t s Separat or : Subuni t s and Fr act i on of Subuni t s Separat or : Coor di nat e Label / Readout Preci si on Label Pr eci si on : Deci mal t o near est 1/ 32 Label Al phanumeri c Fr act i on Readout Preci si on : Deci mal t o nearest 1/ 32 Secondary Preci si on : Deci mal t o nearest i nt eger Coor di nat e Label Symbol ogy Wei ght : Coor di nat e Label s : 1 Wi t ness Li ne and Ter mi nat or : 1 Col or : Coor di nat e Label s : Or ange Wi t ness Li ne and Ter mi nat or : Or ange


137

Creating 3D Models Text Font : Coor di nat e Label s : 23 Wi t ness Li ne and Ter mi nat or : 125 Symbol f or Li ne Ter mi nat or : 42 Pl ot Gap Si ze : Li ne Spaci ng : Angul ar Label / Readout Angul ar Label Deci mal Degr ees Accur acy : 1 Deci mal Angul ar Readout Deci mal Degr ees Accur acy : 1 Deci mal Angul ar I nput i s Cl ockwi se f r om Nor t h Sl ope Readout Accur acy : Number of I nches per Foot

0. 250000 0 Pl ace Pl ace

The PDS Equipment Modeling (PD_EQP) product models equipment and equipment items for later connection to PDS piping components created through the Piping Designer software. The Equipment Modeling product defines equipment volumes and positions nozzles on the equipment.

138


Creating 3D Models

With PDS Equipment Modeling (PD_EQP), you can perform the following tasks: Place basic three-dimensional building blocks such as cylinders, cones and boxes called primitives.  Place three-dimensional equipment and components called parametrics , which are predefined and delivered in a library with the product.  Create complex parametrics using the EDEN language and add them to the Reference Database for future placement. Refer to the PDS Eden Interface Reference Guide for details. 

The following libraries comprise the RDB and are used to define the equipment and make it compatible with existing piping specs: 




Tutorial Definition Library



Piping Physical Data Library Piping Design Standard Note Library Piping Specification Tables Library.

 


139

Creating 3D Models

The is used to revise the seed data for a specified Equipment model or create a report of the RDB data. You can revise both 3D data and model data. The option is used to revise the model data for the selected equipment model file. The system activates the following form which provides access to the modification options.

Select the option for the type of model data to be revised. The following report shows the delivered settings for the Equipment Model Data. P r oj e ct Dat a Manager Equi pment Grap i c Symbol ogy Pr i mi t i v es / Parametr i cs Cat egory

140

Level

Col or

Wei ght

Symbol ogy

P ysi c a

10

9

2

So i

Eqp Cat egory 2

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 3

1

Wi te

0

So i

Eqp Ca t ego r y 4

1

Wi te

0

So i

Eqp Cat egory 5

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 6

1

Wi te

0

So i

Eqp Ca t ego r y 7

1

Wi te

0

So i

Eqp Cat egory 8

1

Whi t e

0

Sol i d


Creating 3D Models Eqp Ca t ego r y 9

1

Wi te

0

So i

Eqp Ca t ego r y 10

1

Wi te

0

So i

Eqp Cat egory 11

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 12

1

Wi te

0

So i

Eqp Cat egory 13

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 14

1

Wi te

0

So i

Eqp Ca t ego r y 15

1

Wi te

0

So i

Eqp Cat egory 16

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 17

1

Wi te

0

So i

Eqp Ca t ego r y 18

1

Wi te

0

So i

Eqp Cat egory 19

1

Whi t e

0

Sol i d

Eqp Ca t ego r y 20

1

Wi te

0

So i

Cat egory

Level

Col or

Wei ght

Symbol ogy

Noz z e Cat e gor y

Sma

12

9

3

So i

Nozzl e Cat egor y

Medi um

12

9

3

Sol i d

Nozz e Category

Large

12

9

3

So i

Level

Col or

Wei ght

Symbol ogy

40

8

1

So i

41

8

0

So i

42

10

1

Sol i d

43

10

0

So i

44

11

1

Sol i d

45

11

0

Sol i d

46

12

1

So i

47

12

0

Sol i d

No zz e s

Enve opes Cat egory Mai nt anence Envel ope (Har d) Mai nt anence Envel ope ( Sof t ) Access Envel ope ( Hard) Access Enve ope (Soft) Saf ety Envel ope ( Hard) Saf ety Envel ope (Soft) Const r ucti on Envel ope (Har d) Const r ucti on Envel ope ( Sof t ) Equi pment Grap i c Symbol ogy St eel Cat egory

cont i nue d)

Level

Col or

Wei ght

Symbol ogy

20

Wite

1

So i

Pl atf orms

21

Whi t e

1

Sol i d

Han r ai s

22

Wite

1

So i

Mi s c e a ne ous Li ght St eel 166

23

Wi te

1

So i

La

er s

Cr eat i ng Equi pment Mo e s Dumb Gr aphi cs Ca t ego r y

L ev e

Co or

We i g t

Sy m o o gy

Dumb Categor y 1

30

Whi t e

0

Sol i d

Dum Cat e gor y 2

1

Wi te

0

So i

Dum Cat e gor y 3

1

Wi te

0

So i


141

Creating 3D Models Dum Cat e gor y 4

1

Wi te

0

So i

Dum Cat e gor y 5

1

Wi te

0

So i

Dumb Categor y 6

1

Whi t e

0

Sol i d

Dum Cat e gor y 7

1

Wi te

0

So i

Dumb Categor y 8

1

Whi t e

0

Sol i d

Dum Cat e gor y 9

1

Wi te

0

So i

Dum Cat e gor y 10

1

Wi te

0

So i

Dumb Categor y 11

1

Whi t e

0

Sol i d

Dum Cat e gor y 12

1

Wi te

0

So i

Dum Cat e gor y 13

1

Wi te

0

So i

Dumb Categor y 14

1

Whi t e

0

Sol i d

Dum Cat e gor y 15

1

Wi te

0

So i

Level

Col or

Wei ght

Symbol ogy

P ac e Poi nt

48

15

8

So i

Datum Poi nt

50

13

10

Sol i d

Hol e El ement s

15

Whi t e

0

Sol i d

2- D S a ows

12

9

3

So i

L ev e

Co or

We i g t

Sy m o o gy

Mi s ce

aneous

Cat egory

Semi I nt el l i gent Gr aphi cs Ca t ego r y Semi - I nt e Cat egory Semi - I ngel Cat egory Semi - I nt e Cat egory Semi - I nt e Cat egory Se mi - I nt e l Cat egory

i gent

1

51

Wi te

0

So i

l i gent

2

52

Whi t e

0

Sol i d

i gent

3

53

Wi te

0

So i

i gent

4

54

Wi te

0

So i

l i ge nt

5

55

Whi t e

0

Sol i d

P r oj e ct Dat a Manager Noz z e Defaul t Pl acement

Opti ons

Nomi na Pi pi ng Di amet er Sy st e m o f Uni t s Engl i sh Sma i s <= Lar ge i s Tabl e Name De i ne Ta e Suf f i x by End Type

>=

: : 2I N : 14I N :

D036

: Bo t e 5 Femal e 5 Mal e - 5 P r oj e ct Dat a Manager Equi pment Re erence Data ase Management 167

PDS 3D T eory — Apri l 2002 Gr aphi c Commodi t y Li brary

142


Creating 3D Models Approve

:

weg

Tut or i a De f i ni t i on Li br a r y Approve : weg

\ wi n32app\i ngr \ pdeqp\ d at\

z i _ eqpms. i


zi _ t ut i . i

\ wi n32app\ i ngr \ r dusr db \

us_pcdi m. l

\ wi n32app\i ngr \ pdshel l \ l i b\

st _not e.

\ wi n32app\i ngr \ r dusr db \

us_ pj s t .


equi p. c e

Equi pment Physi cal Data Li brar y Appr o ve

:

Pi pi ng P ys i c a Data Li brary Approved : wegl Pi pi ng Desi gn St andar d Note Li brary Approve : weg Pi pi ng J o Spec i i c at i on Ta Li brary Approve : weg

e

Cel l l i br a r y Approve

:

weg

Forms Di r ect ory Locati on Approve : weg

Di s t a nc e Bet we en Two P anes

or C as

\ wi n32app\i ngr \ pdeqp\ P r oj e ct Dat a Manager I nterf erence Envel ope Emul at i on Dat a : 1"

C ec i ng

Number of Emul at ed Cyl i nder s Per 90 Degree Torus 4 Length of Emul ated Cyl i nders f or Cone Lengt o Emu at e Cy i n er s or Semi - E i ps oi

: :

1"

:

1"

The Equipment Modeling Interface is accessed through PD_Shell. This interface allows you to enter the Equipment Modeling graphics environment, create or modify Eden and Tutorial Definition files, print reports and define or edit filenames and locations for libraries.


143

Creating 3D Models 1. At the Plant Design System form, select the

option.

The system displays the Equipment Modeling Options form.

2. Select the

option to enter the graphics environment.

The system displays the Equipment Modeling form listing the available design area numbers and their corresponding descriptions.

3. Select Design Area

144


Creating 3D Models Select the 3D design area to modify and click

.

The system lists the equipment models for the selected design area and their cor responding descriptions.

4. Select Model Select the

to modify and click

.

The system enters the graphics design file.

You can orient equipment items in a 3D design file using the refresh (orientation) tee and the coordinate axis system. The refresh tee provides you with both the active point location and the active orientation. The active point displays where the graphics will be placed while the active orientation displays the graphic's orientation. The term refresh denotes graphics which are temporarily drawn on the screen and can be moved dynamically. The refresh tee appears at the active place point when selecting placement commands. It consists of two lines. 

The primary axis originates at the active place point and is aligned with the equipment item center line.


145

Creating 3D Models 

The secondary axis is aligned perpendicular to the primary axis with its origin at the bisecting point with the primary axis. This axis is used to define the auxiliary orientation.

When placing an equipment item with the refresh tee, you can adjust the orientation by one of the following methods: 

Selecting the reset button () to adjust the orientation 90 ° around the active axis. Keying in a specific angle.



Using the



commands via the coordinate axis system.

The coordinate axis system display consists of a refresh line originating at the active place point and pointing in one of six coordinate directions: North, East, Up, South, West and Down.

If the coordinate axis system display is turned on, the refresh tee appears at the active place point when you select a secondary command such as or . You can confirm the direction of the active axis by viewing the status field. The system displays the directional information using a few simple symbols. **P-IN S-

146

P

-primary axis

S

- secondary axis

**

- indicating the active axis


Creating 3D Models -IN or - indicating the direction the active axis is pointing depending on the active view. -OUT In a specified view (other than Iso), IN points away from you when looking at a model. OUT points toward you when looking at a model. For example when looking at a north view, IN points north (away from you) and OUT points south (toward you). In the example above, the primary axis is the active axis and points IN toward the displayed view. The secondary axis is only visible in the displayed view. Since the primary axis is active, it can be rotated by a command. The refresh tee cannot be displayed on a screen if it is located outside of the screen view. Also, a 3D representation of the orientation axes with their center located on the placement point appears in place of the orientation tee previous to its displacement. This axis is called the Coordinate Axis or the Coordinate System Indicator (CSI).

When activating the orientation tee, the system displays the coordinate axis in its place previous to its displacement. The orientation tee can be manipulated only in the following instances: 

It can be manipulated when the active point is defined using the command. After selecting this command, you can use any of the pocket menu options to manipulate the tee. Angles of rotation cannot be entered with this command.



When placing equipment and components using a form or a parametric tutorial for equipment or component generation and manipulation. Angles of rotation can be keyed in, where positive angles are measured in the counterclockwise direction looking from the direction where the non-rotating axis is pointing. To change the axis to be rotated, select the option. When an equipment or component manipulation command ( , , , , etc.) is active. Angles of rotation for primary or secondary axis cannot be entered in this mode.




147

Creating 3D Models

This section lists the Equipment Modeling commands that are available.

These commands allow you to create, copy, move, delete, rotate and mirror entire pieces of equipment defined either individually or by a fence. You can create equipment using user defined primitives or parametrics.

These commands allow you to add components or equipment items to existing pieces of equipment and also copy, move, delete, rotate, mirror, and modify equipment items.

This command allows you to place nozzles in reference to a datum point or another nozzle. The new nozzle will be added to the same equipment tag owning the referenced datum point or nozzle.

These commands allow you to view or revise data associated with the current project or drawing. This data includes project file data and equipment attributes.

These commands allow you to define the active placement point, the view orientation, and display categories.

These commands perform a variety of manipulations including envelope file generation, datum point manipulation, dimension checking, viewing specific equipment groups, attaching graphics, controlling display categories, reviewing error messages, attaching reference models, and defining saved views.

148


Creating 3D Models

These commands provide support for the primary commands. A Secondary Command will not function unless a primary command is active. These commands are used to orient the screen views, defines precision input, adjust the orientation of the refresh tee, or define the coordinate system.

The (PD_Design) is one module of PDS 3D products. It is specifically intended for the creation and revision of 3D models in the design of the piping and in-line instrumentation within the plant. The resulting piping models can be used for checking interferences, extracting drawings, and generating bills of material. The following illustration shows a typical piping model with reference models attached. The piping model contains fully dimensioned graphics for piping, piping components, instruments, piping specialties, and pipe supports. You can access coordinate points from the reference models and review database attributes.

Piping Model With Attached Reference Models


149

Creating 3D Models Each component in a piping model is linked to a database record which contains non-graphic information about the component. When a component or segment is placed in the model, the system creates a row in the appropriate database table(s). A row represents one instance or record in the database.

Database Attributes Associated with Gra phics

150


Creating 3D Models

The option is used to revise the Model data in the project seed file or a specific piping model. The system activates the following form which enables you to access the modification options.

Select the option for the type of model data to be revised. The following report shows the delivered settings for the Piping Model Data. Proj ect Data Manager Component P acement Ben

De

ect i on Ta

e

:

BEND_DEFLECTION

Commodi t y Name Tabl e

:

COMMODI TY_ I TEM_NAME

Pi pe Lengt

Ta

e

T r es o

:

PI P E_ LENGTH

Segment Pi pe Run Lengt h Threshol d Tabl e We

Type Ta

e

: :

Rei nfor ci ng Wel d Data Modul e Dat a Mo u e

: :

Pi pe Commo i t y Name

:

PI PI NG

Tube Commodi t y Name

:

TUBE

Fi e

We

Sym o

PI PE_RUN_LENGTH

WELD_TYPE_TABLE

F ange Dat a Mo u e

Rei n or c i ng Pa

:

Name

:

I somet r i c Dr awi ng Symbol Name Angul ar Tol er ance

:

( Aut omat ed Component)

Vi ci ni ty To erance

:

0. 500000

: 4.000000 Proj ect Data Manager Pi pi ng Data Contr o

P&I D Component Name Fl ui d Code Update Wei g t Ta

e

:

:

Commo i t y Name

: Of f On


151

Creating 3D Models Br anc

Component Associ ati on or I sometr i c Drawi ngs

Copy Opt i on

:

Appen

:

Hea er

Pre i x

Geometr i c I ndust r y Standard

:

Expanded

Sc e u e T i c nes s Over r i e Opt i on : Lar ger o Over r i e an Spec Syst emof Uni t s f or Nomi nal Pi pi ng Di ameter : Engl i sh Fi e

Name

or Nomi na

Pi pi ng Di ameter

: IN Proj ect Data Manager Physi cal Uni t s Opti ons

I n su at i on Dens i t y

:

Sur ac e Ar e a

t 2

:

Dr y/ Wet Wei ght s

/ t 3

:

lb

Maxi mum Temperat ure

Spec

:

egF Proj ect Data Manager Nozzl e Data Tr ansf er Li st

T er e ar e cur r ent y NO nozz e at t r i ut es se ect e

or t r ans er Proj ect Data Manager Gr a p i c Sy m o ogy

Wei g t s

:

Pi pi ng Commodi t y

: 2

Pi pi ng Spe ci a t y

: 2

I nstr ument

: 2

Pi pi ng/ Tubi ng Pi pe Support

: 2 : 2

Model Symbol ogy Col or

:

:

Si mpl e

Model Category Proj ect Data Manager Gr aphi c Symbol ogy

Nomi na Sma

is

Large i s

152

Pi pi ng Di ameter

- Model Categor y

:

<= 2I N >= 14I N Leve

Co or

Pi pi ng Segment

Not Approved

Smal l

1

Bl ue

Pi pi ng Segment

Not Appr ove

Me i um

11

B ue

Pi pi ng Segment

Not Approve

Large

21

B ue

Pi pi ng Segment

Approved

Smal l

31

Bl ue

Pi pi ng Segment

Appr ove

Me i u m

41

B ue

Pi pi ng Segment

Approve

Lar ge

51

B ue

Pi pi ng/ Tubi ng

Not Approved

Smal l

3

Gr een

Pi pi ng/ Tu i n g

Not Appr ove

Me i u m

13

Gr een

Pi pi ng/Tubi ng

Not Approved

Lar ge

23

Gr een

Pi pi ng/ Tubi ng

Approved

Smal l

33

Gr een

Pi pi ng/ Tu i ng

Appr ove

Me i um

43

Gr een


Creating 3D Models Pi pi ng/ Tu i ng

Approve

Large

53

Green

Pi pi ng Commo i t y

Not Approve

Sma

2

Green

Pi pi ng Commo di t y

Not Appr o ved

Medi um

12

Gr e en


Not Approve

Large

22

Gr een

Pi pi ng Commodi t y

Appr oved

Smal l

32

Gr een


Appr ove

Me i um

42

Gr een


Approve

Large

52

Gr een

Pi pi ng Speci al t y

Not Approved

Smal l

4

Or ange

Pi pi ng Speci a t y

Not Appr ove

Me i um

14

Or ange


Not Approve

Large

24

Orange

Pi pi ng Speci al t y

Approved

Smal l

34

Or ange


Appr ove

Me i u m

44

Or ange


Approve

Large

54

Orange

I nst r ument

Not Approved

Smal l

5

Or ange

I n st r ument

Not Appr ove

Me i um

15

Or ange

I nst r ument

Not Approved

Lar ge

25

Or ange

I nstr ument

Approve

Sma

35

Orange

I n st r ument

Appr ove

Me i um

45

Or ange

I nst r ument

Approved

Lar ge

55

Or ange

Pi pe Support

- Logica

Not Approve

N/ A

7

Vi o et

Pi pe Suppo r t

- P y si c a

Not Appr o ve

N/ A

10

Wi te

Pi pe Support

- Logi cal

Approved

N/ A

37

Vi ol et

Pi pe Suppo r t

- P y si c a

Appr o ve

N/ A

40

Wi te

Mi scel l aneous Gr aphi cs

58

Red

Di agnost i c Marker s

59

Red

Automate

62

Re

63

Red

Component/ Pi pe P acement Mar ers

Model Reconst r uct i on Mar ker s Proj ect Data Manager Sy m o ogy Wei ght s

:

Di agnosti c Mar ers

: 2

Desi gn Check Mar ker s Automate Mo e

: 2

P acement Mar ers

: 2

Re co ns t r uc t i o n Ma r er s

: 2

Fi el d Wel d and I sometr i c Dr awi ng Symbol Symo

Font Numer

Text Hei g t Text Wi dt h Fi e

o r Ma r er s

We

:

2

: 125

: 6" : 6" Sym o

Name

:

I somet r i c Dr awi ng Symbol Name

: Proj ect Data Manager Mat er i a


Ta eo

Opt i ons

153

Creating 3D Models Co mmo i t y Co e L engt

:

Si z e I n e pe n e nt

Ca c u at i on

:

A mos t Pr e ci s e

Bol t Commodi t y Code

:

Pi pi ng J ob Spec

Bo t Di amet e r Uni t s

:

Eng i s

Bol t Lengt h Uni ts

:

Engl i sh

Bol t Roundoff Opti on

:

A t er nat e Gas et Sear c F i e l d F i t L e ngt h

Bol t Commodi t y Name Nut Commodi t y Name Bo t Data Mo u e

O

: 6Q3C97

:

e

: 6Q3C95

: 6Q3C98 BOLT_DATA

Fl ange Dat a Modul e Ta

:

: Of f

Gas et Commo i t y Name

Bo t Lengt

Pref err ed Bol t Length

: :

FLANGE_DATA_ MTO BOLT_LENGTH Pr oj ect Dat a Manager Desi gn Revi ew Label Opti on

Se ect e

La e s

:

T er e ar e NO Desi gn Revi ew La e s Se ect e Pr oj ect Dat a Manager De au t Segment Par ameter s unit _num er f l ui d_code

St andar d Not e Number i s

Undef i ned

<125, 0>

Undef i ned

<220, 0>

Undef i ned

<1064, 0>

Undef i ned

<1056, 0>

No t e Num e r i s

Un e i ne

<1064, 0>

No t e Num e r i s

Un e i ne

<1056, 0>

uni t _ c o e l i ne_sequence_no no mi na _ pi pi ng_ i a

1 00- 3 / 4 I N

pi pi ng_mater_c ass i nsul ati on_purpose

Standar d Note Number i s

i nsu at i on_t i c

0’

nor _oper _pres

0. 000

nor_ op_pres_ uni t s


nor_ oper _t emp

0. 000

nor_ op_t emp_uni t s


nor _dgn_pr es

0. 000

no r _ gn_ pr e s _ uni t s

St a n ar

nor_ dgn_t emp

0. 000

no r _ gn_ t e mp_ uni t s

St a n ar

i nsu at i on_ ensi t y

0

heat _t r aci ng_r eqmt


Undef i ned

<200, 0>


St a n ar

Un e i ne

<210, 0>

eat_t r aci ng_t emp

0

Undef i ned

<160, 0>

desi gn_r esp

154

0"

/ t 3

Not e Num e r i s

egF



Creating 3D Models s upp y _r e sp

St a n ar

Not e Num e r i s

Un e i ne

<160, 0>

c ons t r uc t i on_ r e s p

St a n ar

No t e Num e r i s

Un e i ne

<160, 0>

const r ucti on_st at


Undef i ned

<130, 0>

St a n ar

Not e Num e r i s

Un e i ne

<50, 0>

Not e Num e r i s

Un e i ne

<1064, 0>

No t e Num e r i s

Un e i ne

<1056, 0>

Undef i ned

<1064, 0>

Un e i ne

<1056, 0>

o

_ st a t us

desi gn_area_number a t_ oper_pres

0. 000

a t _ o p_ pr e s_ uni t s

St a n ar

al t _oper _t emp

0. 000

a t _ o p_ t e mp_ uni t s

St a n ar

a t _ gn_ pr e s

0. 000

al t _dgn_pr es_uni t s


a t_ gn_t emp

0.000

a t _ gn_ t e mp_ uni t s

St a n ar

Not e Num e r i s

st eam_out et_ t emp

0. 000

st eam_t emp_uni t s

St andar d Not e

Number i s Undef i ned

<1056, 0>

Standard Note


<340, 0>

St a n ar

Num e r i s Un e i ne

<570, 0 >

t r ai n_ num e r mater_o _const ruct saf ety_ cl ass es i g n_ st a n ar

Not e

ui _ c at e gor y coat i ng_r eqmt s

St andar d Not e


<190, 0>

c ea ni ng_ r e qmt s

St a n a r

Num e r i s Un e i ne

<230, 0>

No t e

package_s yst em_no Proj ect Data Manager De au t Segment Parameters

cont i nue

modul e_no s pec i i c _ gr a vi t y _ a

0. 000

s pec i i c _ gr a vi t y _

0. 000

speci f i c_gravi t y_c

0. 000

vi scosi t y

0. 000

densi t y

0. 000

spec_heat_r ati o

0. 000

s oni c _ ve o ci t y

0. 000

surf ace_roughness

0. 000

t est _syst em_no t est _f l ui d

Standard Note

t est_pr essur e

0. 000


<125, 0>

sc e u e_over r i e Proj ect Data Manager Design Consi stency C ec s


155

Creating 3D Models Data

:

F ow Di r e ct i on Fl ow Cent erl i ne

:

Har :

Hard Check

Outsi e Di ameter : No Check Schedul e/ Thi ckness : No Check Pi pi ng Mat e r i a s C as s : Sof t Check Mat e r i a s o Cons t r uc t i on C as s I nsulat i on Thi ckness : Sof t Check I ns u at i on Pur pos e : To er ances

C ec

:

So t C ec

So t C ec

:

Fl ow Centerl i ne Al i ghment

0. 500000

I n su at i on T i c nes s

1/ 4"

: :

Proj ect Data Manager End Prep Compat i bi l i t i es Bo t e

En

Pr eps

FFFE FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFT BEWG FFTBCSE FF TBCSEWG FFFTBE FFFTBEWG FFF EWG FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFT BEWG FFTBCSE FF TBCSEWG FFFTBE FFFTBEWG RFFE FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG RFFEWG FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG RJ FE RJ FE RJ LFE RJ TBE MRJ TBEWG RJ TBCSE

STFE SGFE SGLFE LTFE LGFE LGLFE SMFE SFFE SFLFE LMFE LFFE LFLFE SGFE STFE STLFE LGFE LTFE LTLFE SFFE SMFE SMLF E LFFE -

156


Creating 3D Models LMFE L MLFE FFLFE FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFT BEWG RFLFE FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFT BEWG RJ LFE RJ FE RJ LFE RJ TBE MRJ TBEWG STLFE SGFE SGLFE LTLFE LGFE LGLFE SMLFE SFFE SFLFE LMLFE LFFE LFLFE SGLFE STFE STLFE Proj ect Data Manager End Prep Compat i bi l i t i es Bo t e

En

Pr eps

LGLFE LTF E LTL FE FF TBCSEWG SFLFE SMFE SMLF E LFLFE LMFE L MLFE FFTBE FFF E F FFEWG RFFE RFF EWG FFL FE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE FFTBEWG FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSEWG

RFTBE FFFE FFFEWG RFFE RFFEWG FFLF E RFLFE FFTBE FFTBEWG RFTBE RFT BEWG RFTBCSE RFTBEWG FFFE F FFEWG RFFE RFFEWG FFLFE RFLF E FF TBE FFTBEWG RFTBE RFTBEWG RFTBCSEWG RJ TBE RJ FE RJ LFE RJ TBE MRJ TBEWG RJ TBCSE MRJ TBEWG RJ FE RJ LFE RJ TBE FFTBCSE FFF E FFF EWG FFT BE FFTBCSEWG -


157

Creating 3D Models FFFE FFFEWG LGLF E FFTBEWG RFTBCSE RFFE RFFEWG RFTBE RFTBCSEWG RFFE RFFEWG RFTBEWG RJ TBCSE RJ FE RJ TBE FFFTBE FFF E FFF EWG FFF TBE FFF TBEWG FFFE F FFEWG FFFTBEWG MJ E MJ E Proj ect Data Manager En

Pr ep Compat i i i t i es

Mal e End Preps BE BE TBE PE SE SWE HCE TBE BE TBE PE SWE HCE MFE MFE MTE FTE MGE FGE MQCE FQCE MFRE FFRE MHE FHE SPE BLE PE BE TBE PE SE SWE FTE HCE 3"FFPE HCE Proj ect Data Manager End Prep Compat i bi l i t i es Femal e End Pr eps SE -

158


Creating 3D Models BE PE SWE BE TBE PE FTE MTE PE FGE MGE FQCE MQCE FFRE MFRE FHE MHE BLE SPE HCE BE TBE PE 3"F FPE Proj ect Data Manager Ref er ence Dat abase Management Mat e r i a / S pec i i c at i on Re er e nc e Dat a as e Appr o ve

:

r a _ t c pr o j

Pi pi ng J ob Specif i cat i on Tabl e Li brary Appr ove

:

weg

. . \ wi n32app\ i ngr \ r us r

\

us _pj s t .

Short Materi al Descri pt i on Li brary Appr oved

:

L ong Mat e r i a Appr oved

wegl

us_shbom. l

. . \ wi n32app\ i ngr \ r dusr db\

us_l gbom. l


us_spbom. l

. . \ wi n32app\ i ngr \ p s e

\ i \

st _not e.

. . \ wi n32app\ i ngr \ p s e

\ i \

Des c r i pt i on L i r a r y

:

wegl

Spec i a t y Mat e r i a Appr oved


:

Des cr i pt i on L i r a r y

wegl

Standard Note Li brar y Appr ove

:

weg

Label Descri pt i on Li brary Appr ove

:

weg

a e s.

Pi pi ng As sem y Li r ar y Approved

:

wegl

. . \ wi n32app\ i ngr\ pdshel l \ l i b\

assembl y.l

Gr a p i c Commo i t y L i r a r y Appr ove

:

weg

Physi cal Data Li brary Appr ove

:

Approved P ysi c a

\ i \

pi p _gcom.

. . \ wi n32app\ i ngr \ r us r

\

us _pc i m.

- U. S. Practi ce

weg

Physi cal Data Li brary

. . \ wi n 32app\ i ngr \ p s e

- DI N

:

Dat a Li r ar y

- Br i t i s


St an ar

159

Creating 3D Models Appr o ve P y si c a

Dat a L i r a r y

Approved P y si c a

P ys i c a

P ys i c a

- I n t er nat i ona

A

- I n t er nat i ona

B

:

Dat a L i r ar y

Appr o ve

- Aust ral i an

:

Dat a L i r ar y

Approved

- JI S

:

Physi cal Data Li brary Appr o ve

- Eur o pe an B

:

Dat a Li r ar y

Appr o ve

- Eur o pe an A

:

Dat a L i r a r y

Approved P ys i c a

:

:

The screen working area is used to display and manipulate graphic information. This information is managed by MicroStation; refer to the MicroStation documentation for details. Refresh gra phics are graphics which are temporarily drawn on the screen.

uses

refresh graphics to display placement aids such as the orientation tee and coordinate system indicator. Graphics are frequently highlighted to provide visual feedback pertaining to the active input. Highlighting is normally followed by an Accept/Reject step allowing you to accept the highlighted graphics as the desired input or to reject the highlighted graphics and select another graphic. This following concepts and terms are common to the

operations.

Piping Segments The centerline routing within a model is represented by geographically connected piping segments. A piping segment defines the geometry of the pipeline and contains the non- graphical data associated with that pipeline. A single piping segment can define changes of direction, but an additional segment is created at a branch point or an attribute break, such as a size change or a spec break. The following illustrates the terminology associated with a piping segment.

160


Creating 3D Models

A pipeline consists of a set of graphically connected piping segments including all the branches.

Active P lac em en t Po int The term active placement point refers to the coordinate location used by the command. It defines the point at which piping and instrumentation are placed. You can use to place a piping or instrument component at an existing, intelligent location in the model, such as a piping or instrumentation connect point, a nozzle, or a piping segment. The system uses the orientation tee to indicate the location of the Active Placement Point.

Coordinate S ys tem Ind ica tor and Orien tation Tee Coordinate Sys tem Ind ica tor The coordinate system indicator is a temporary display symbol which represents the six orthogonal directions (North, South, East, West, Up, and Down) of the coordinate system.

uses the coordinate system indicator to indicate the active coordinate location when  

defining or manipulating a piping segment identifying a point on a piping segment


161

Creating 3D Models  

identifying a component center or connect point sketching a pipeline.

The orientation tee is a temporary display symbol which enables you to orient a component before placement. The orientation tee is composed of two lines:  

a primary axis representing the flow centerline a secondary axis used to orient components which are not symmetrical about the flow centerline (for example, a valve with an operator).

When the command is active, the system displays the orientation tee at the Active Placement Point and displays related information in the screen message fields. P **S-OUT The stars (**) indicate the active axis of rotation (the secondary in the above message). When either axis is rotated such that its orientation is not in the plane of the view, the suffix IN or OUT is displayed next to P (primary) or S (secondary) indicating whether that axis is pointing in or out of that view. For example, when the secondary axis is perpendicular to the screen and oriented toward the designer, the message P S-OUT is displayed. When placing a component with the orientation tee, you can adjust the orientation by pressing or selecting one of the Orientation Control commands.

162


Creating 3D Models

Piping Connec t Points Each component has a center and at least one connect point or pressurized end. A connect point is usually an end of a piping component to which another component or pipe (with compatible properties) is connected. The connect point stores the description of the component at that end. It indicates the flow centerline orientation, and properties such as diameter, end preparation (flanged, welded,...), and rating.

The following rules (in order of priority) are used to determine the assignment of connect point numbers: 1. Connect Point 1 is always at the larger end (NPD). 2. If the ends have the same NPD, but different end preparations, then Connect Point 1 is assigned an end preparation in the following precedence: Bolted, Male, Female. Refer to the PDS Piping Component Data Reference Guide for a detailed explanation of connect point assignments.

The following Piping Design commands are available.

Placement commands enable you to place pipe, piping components, pipe supports, and instrument components. You can also place assemblies (predefined sets of components). These commands can be used at any time in the design process. In the process of creating a piping model you will use a combination of these commands depending on the desired result. A typical approach is to use 

to route the layout of a pipeline and define the attribute data for the pipeline. The attribute data can be defined manually, copied from another segment, or updated from information in the P&ID database.



to place components such as valves, instruments, or commodity overrides along the segment pipeline. to populate the pipeline with fittings and pipe.



The , , and commands automatically change the approval status of piping segments and piping components to not approved during the copy operation.


163

Creating 3D Models You cannot make any of the following changes to approved piping. 

Create a new piping segment in the approved piping.

command by connecting to previously placed,

Place new piping components, instrument components, piping, or tubing in the command by connecting to previously placed, approved piping.  Place new pipe supports in the command by connecting to previously placed, approved piping. command by connecting to  Place new pipe supports in the previously placed, approved piping. 

The commands enable you to move, delete, and rotate existing piping. You can revise individual components, piping segments, or all the elements on a pipeline or defined by a group operation. These commands can be used at any time in the design process to move, modify, or delete a component, a piping segment, or a group of elements such as a pipeline. Any rotation, addition, reconstruction, or deletion of PDS piping components and segments must be done through these commands and not through MicroStation manipulations due to the interdependence of graphic and database information.

These commands revise/append different positional and/or database information on PDS piping components. Any rotation, addition, or reconstruction of PDS piping components must be done through these commands and not through MicroStation manipulations due to the interdependence of graphic and database information. You cannot use MicroStation commands to change piping as they will not update the user data associated with the piping segment or component.

These commands enable you to revise piping segments in the active model. You can add, move, or delete an imbedded vertex for an existing piping segment. These commands cannot be used if the segment has been populated with pipes or components.

164


Creating 3D Models

These commands enable you to move, delete, rotate, and reconstruct existing piping. You can revise a pipeline or those elements defined by an active group. The commands perform both graphical and database revisions.

These commands enable you to review or revise the model data stored in the Design Database and Project Control Database. Each component in a piping model is linked to a database record which contains non-graphic information about the component. When a component or segment is placed in the model, the system creates a row in the appropriate database table. These commands can be used at any time in the design process to review or revise the model data stored in the Design Database.

These commands enable you to review information in the Design Database or review existing report files. You can only view the information you cannot make any changes. You can review data for elements in the active model and attached reference models.

These commands enable you to revise information in the Design Database and define additional information for components. You can only revise information for items in the active model.

These commands enable you to review information related to the model analysis operations. You can also check for interferences within the active model file. Many of these command are dependent on data from the Design Data Management commands. Refer to the Chapter on Interference Detection for more information on detecting and reviewing interference clashes.


165

Creating 3D Models

166


SECTION 6

PDS provides capabilities for distributing data from one part of the design process to another. One aspect of this integration is the transfer and comparison of data between the P&ID task and the Piping task. This section describes the conventions that apply to the loading, updating, and comparison of data between the P&ID Database and the piping model. 

. You can transfer segment data from the P&ID to update the active segment data, to define line attributes while sketching, or to revise a segment attribute or set of attributes.



. You can select a component on the P&ID to define the commodity item to be placed. . You can compare data in the model against data in the P&ID to verify that all the information is in agreement. The easiest way to transfer or review data is to use the graphical data transfer options. This allows you to display the P&ID drawing in a view while working in the model and select items directly from the drawing graphics.

 

PDS also supports transfer by line ID or by identifying an equipment nozzle as the start of a pipeline. Database Requirements ................................................................. P&ID Correlation Table ................................................................ P&ID Graphical Data Transfer Setup ........................................... P&ID Node Numbers .................................................................... Update Segment Data from P&ID ................................................ P&ID Data ..................................................................................... Name From P&ID ......................................................................... P&ID Data Comparison Options...................................................


.167 .168 .174 .176 .177 .179 .180 .180

167

P&ID to Piping Data Transfer

For the P&ID Database to be linked to the Piping Design Database, the two applications must share the same Project Control Database schema. This can be achieved by using the same project number when creating the schematic project and the 3D project. Although the Project Control Database schema must be shared, the P&ID Database schema and the Piping Design Database schema are otherwise independent. The attribute is used to locate the relevant P&ID data within the P&ID Task and Master Database. The unit number should be set in the active segment data to match the Unit Number setting within the P&ID database. Only those P&ID drawings which have been successfully propagated can be referenced for P&ID to Piping data transfer.

The P&ID Correlation Table is an ASCII file used to correlate a particular column or columns in the P&ID segment table of the P&ID Database with a corresponding column in the piping segment table of the Piping Design Database. The P&ID Correlation Table defines which database columns are to be transferred and compared. Any columns not specified in the Correlation Table will not be transferred. The P&ID column numbers required in the Correlation table are from the relational database and are not the P&ID attribute numbers. During the interactive loading of segment data, you can specify that either a complete or partial set of data be considered. The Correlation Table specifies which columns are to be loaded, updated, or compared for both complete and partial data transfer. The Correlation Table is expected to exist in the project directory for the applicable project, (the directory that includes the seed model, seed drawings, etc.) A default Correlation Table is delivered in the PD_Shell product and is automatically copied to the project directory when a new project is created. You can edit the Correlation Table, if required, to add columns to or delete columns from both the complete and partial data transfer processes. An asterisk (*) signifies that data transfer and comparison is applicable for that particular column. You can also add user-defined columns of piping segment data to the Correlation Table. The default Correlation Table is defined as follows: # Segment Data

Mo e

P&I D

Comp ete

Part i a

#I you es i r e t o e au t t e ’ n on- par t i a ’ at t r i ut es ur i ng a par t i a t r ans er o # at a, i n t e par t i a c o umn pl ace a ’ - ’ , ski p at l east one space, and def i ne t he #def aul t val ue. The def aul t val ue wi l l be used whenever an i nteract i ve tr ansf er #occurs, or i f the toggle i s set f or the bat ch update. The compl ete, #part i al and def aul t val ues are supported ONLY i n thi s secti on of t he fi l e. #e xa mp e : at t r i ut e _ one 99 100 * e a u t _ v a ue uni t _number

168

4

1 3


P&ID to Piping Data Transfer uni t _ c o e

5

2

*

mo u e_no

6

79

*

package_s yst em_no

7

81

*

t r ai n_numer

8

23

*

*

f l ui d_code

9

22

*

*

i ne_sequence_no nomi na _ pi pi ng_ i a

1 0 1 1

2 4 1 5 1 6 2 5 2 6

npd_uni t s - 1 pi pi ng_mater_c ass i nsu ati on_purpose

1 2 1 4

*

*

*

*

*

*

*

*

i nsulat i on_t hi ck

15

28

i ns u at i on_ t i c _ uni t s

-1

29

i ns u at i on_ ens i t y

16

30

i nsulat i on_densit y_unit s

-1

31

eat_t r aci ng_r eqmt

17

heat_ t r aci ng_medi a

*

*

*

73

*

*

18

74

*

*

eat_t r aci ng_t emp

19

75

*

*

eat _t raci ng_t emp_uni t s

-1

76

20

60

*

*

const r ucti on_st at

hol d_stat us

21

83

s c e u e_ over r i e

23

66

*

nor _oper _pres

24

39

*

nor_ oper _t emp

25

41

*

a t _oper_pres

26

43

*

a t _oper _t emp

27

45

*

nor_ dgn_pr es

28

47

*

nor _ gn_t emp

29

49

*

al t _dgn_pr es

30

51

*

a t_ gn_t emp

31

53

*

*

st eam_out et_ t emp

32

86

*

mater _of _const r uct

33

61

*

s a e t y _c a ss

34

59

*

esi gn_r esp

37

69

*

const r ucti on_r esp

38

78

*

supp y_resp

39

71

*

coati ng_r eqmt s

40

72

*

cl eani ng_r eqmt s

41

77

*

ui _category

42

84

*

nor _op_pres_uni t s

43

40

*


*

169

P&ID to Piping Data Transfer nor_ op_t emp_uni t s

44

42

*

a t_ op_pres_uni ts

45

44

*

al t _op_t emp_uni t s

46

46

*

nor_ gn_pres_uni t s

47

48

*

nor_ dgn_t emp_uni t s

48

50

*

a t _ gn_ pr e s _ uni t s

49

52

*

a t_ gn_t emp_unit s

50

54

*

st eam_t emp_uni t s

51

87

*

t est _s yst em_no

64

55

*

t est _

65

56

*

66

57

*

ui

t est_pr essur e ### Data ext racte

rom t e Pi pi ng Segment Ta

e

pipi ng_seg, 112

o

t e P&I D Design Data ase:

# upst rm_no e_no pi d_node_number_ a

-

10

pi d_node_number_ b

-

11

ow_ i r e c t i on

-

14

-

21

-

3

-

12

pi pi ng_thi ckness_fl ag

-

68

### Data extr act ed f r omt he

Equi pment Tabl e Dat abase: -

# wns t r m_ no e _ no

# i ne_no_ a e l i ne_number_ l abel # wg_occ_no r awi ng_segment _i n ex_no l i ne _i d # pi pi ng_t

_

ag

equi pment _numer ### Data extr act ed f r omt he

( eq_group,

) of t he P&I D Desi gn 7

Equi pment Nozzl e Tabl e P&I D Desi gn Dat abase: -

nozz e_num er

106

( eq_nozz,

108

) of t he

5

# pi d_seg_occ_no

nozz e_segment _i n ex

-

4

-

2

-

13

# eq_grp_occ_no equi pment_ nozz e_i n ex # no e_ no equi p_nozzl e_node_no ### Data ext racte #pi pi ng_ comp_ t a #

e is t e

e i mi t er t o s i gna

e

pipi ng_comp,

t e i n or mat i on

120

o

t e P&I D

Desi gn Data ase:

e ow e ongs t o

P&I D’ s pi pi ng_comp t abl e and Pi pi ng’ s pdtabl e_34_.

# pi pi ng_ comp_ t a

170

rom t e Pi pi ng Component Ta

e s i gna s t at t e

o

owi ng at t r i ut es

e ong t o p t a

e_ 34.


P&ID to Piping Data Transfer pi pi ng_ c omp_ t a

e

pi pi ng_comp_num er

2

6

aabbcc_c ode

3

9

-

28

8

29

c ommo i t y _ co e_

ag

cmdt y_c ode # opt at t r i ut e i n P&I D i s p ac e

i nt o t e opt i on_ co e at t r i ut e i n Pi pi ng

commo i t y_opt i on_co e

5

27

-

3

# pi d_seg_occ_no comp_segment _i n ex_no # wg_occ_no comp_dr awi ng_i ndex_no

-

2

# generi c_t ag_no speci a t y_generi c_tag_no

-

#any at t ri but es you desi r e to tr ansf er #

e r e.

Yo u

et e r mi ne w i c

#

and pi pi ng pdt abl e_34.

#

app y t o t es e at t r i ut es .

#at t r i ut e name

44

( beyond t hose defi ned above) ar e l i st ed

ar e t r ans er r e

NOTE:

et we en P &I D pi pi ng_ c omp t a

e

Compl ete, par t i al and def aul t do NOT

any t i ng

pi pi ng at t r no attr no

const_ stat us

p&i

3 2

23

eat _t raci ng_me i a

35

3 4 hol d_status 3 3 t _t raci ng_me i a_temp 3 6 openi ng_acti on 3 1 r emar ks 4 6 ### Data ext racte rom t e I nst rument Component Ta

34

eat _t raci ng_r eqmt s

33 41 35 17 20 e

i nstr _comp,

131

o

t e P&I D Desi gn Data ase

#i nstr _comp_t abl e i s t he del i mi t er t o si gnal t he i nformati on bel ow bel ongs t o #

P&I D’ s i ns t r _ c omp t a

e an

Pi pi ng’ s p t a

e_ 67_ .

# i nst r_comp_tabl e si gnal s t hat the fol l owi ng att ri butes bel ong to pdt abl e_67. i nstr _comp_tabl e i nstr ument _t ag_num er

-

5

-

4

-

10

# pi d_seg_occ_no i nst r_segment_ i n ex_no # aa

cc_co e

i nstr _aabbcc_code

# dwg_occ_ no i ns t r _ r a wi ng_ i n ex _no

-

3

#gener i c_t ag_no i nst r_generi c_tag_no #any at t r i ut es you #

e r e.

Yo u

es i r e t o t r ans er

et e r mi ne w i c


eyon

ar e t r ans er r e

80 t os e

e i ne

a ove

ar e

et we en P &I D i ns t r _ c omp t a

i ste e

171

P&ID to Piping Data Transfer #

an

pi pi ng p t a

#

app y t o t es e at t r i ut es .

#att ri but e name

e_ 67.

NOTE:

Comp et e ,

par t i a

( any t hi ng)

pi pi ng

c eani ng_r eqmt s

att r

39

no

an

e au t

o NOT

p&i d att r no

60

const _r esp 32

35

const _st atus

29

24

gn_r esp 31

25

f ai l _act i on_1

28

56

eat _t raci ng_me i a

34

28

eat_t r aci ng_r eqmt s

33

27

30

40

35

29

i nsu ati on_pur pose

36

31

i nsulat i on_t hi ck

37

33

hol d_st atus t _t raci ng_me i a_temp

mo u e_no 41

36

package_s yst em_no

42

38

r emar _2 52

22

s a et y _c as si i c at i on

40

### Dat a ext r act ed f r om

t he

20 Dr awi ng

r awi ng_num er

Tabl e

( dwg,

-

3

-

2

r a wi ng_ t i t e

-

16

net work_address

-

7

pat h_name

-

8

i e_ speci i cat i on

-

5

propagati on_st atus

-

10

appr ova _ i n i t i a s

-

21

approval _date

-

22

r e vi s i on_ i d

-

27

-

29

-

30

-

31

-

4

102 ) of t he P&I D Pr oj ect Dat abase:

#uni t _occ_no uni t _i ndex_number

or_ comment s_ ate f or_desi gn_dat e o r _ c ons t r uc t _ at e t as _name ### Dat a ext r act ed f r om

t he

Uni t Tabl e

unit _num er

-

uni t , 101 ) of t he P&I D Pr oj ect Dat abase: 4

uni t _ c o e -

3

uni t _name

-

### Dat a ext r a ct e

172

(

r om t e Tas

RDB Ta

e

tas _r

5 ,

98

pi d_t ask_name

-

2

pi d_task_rdb_node

-

3

pi _ t as _r

-

4

_pat

o

t e P&I D Pr oj ec t Dat a as e:


P&ID to Piping Data Transfer ### Da t a e xt r a ct e Desi gn Dat abase: # net _t ype_occ_no

r o m t e P I D Se gment Ta

e

pi _ s eg,

pi pi ng_segment _i n ex_no

-

110

o

t e P&I D Des i gn Dat a as e i nc u es t e

dwg_occ_ no

o

### t e P&I D Des i gn Dat a as e i nc u es t e

o

t e pi pi ng c onnec t or t a

2 ( pi pi ng_connect or,

124) of

owi ng:

connect or_ no # wg_ oc c_ no o

( dwg_r ev_dat a,

owi ng:

-

### Data extr acted f r omt he Pi pi ng Connect or Tabl e

t e P &I D

4

### Data ext r act ed f r omt he PI D Dr awi ng Revi si on Data Tabl e ### 103

o

-

4

-

2

e

connect _ wg_occ_no #pi d_seg_occ_no of t he pi pi ng connector t abl e connect_pi _seg_occ_no

-

3

#matchi ng_cr i t eri a i s t he cri t eri a to be used for matchi ng t he P&I D and Pi pi ng #segment s t ogether. #ar e t e

Nodea

( pi pi ng att ri but e

e au t cr i t er i a .

67) and Nodeb

T e mat c i n g cr i t er i a i s

e ine

( pi pi ng att ri but e y

68)

i s t i ng t e

#pi pi ng att r i but e number s separ ated by a space on t he l i ne bel ow. matc i ng_cri ter i a

67

68

#s ear c _ mo e i s t e met o #i s

’ FI RST’

or s ear c i ng

or t e mat c i ng c r i t e r i a.

- stop on t he f i r st match f ound.

#mea ns t o s ear c

t e ent i r e

at a a se

oo i ng

The other opt i on i s or a ma t c .

I

T e

e au t

’ END’ whi ch

mo r e t an o ne mat c

#i s f ound, t he sof t ware eval uat es al l of t he matches for an exact match of t he #t r a ns e r

a t a.

searc _mo e FI RST #excl usi on_cr i t eri a has been a par t of t he submi ssi on process i n t he past . # ave a #c ec

e

t e capa i i t y t o

t e t r ans er

#segment s.

isa

e

e au t t i s va ue.

segment s an

Va ues ar e

’ NO’ t o c ec

’ YES’

t e t r ans er

or isa

We o not e

Thi s opti on can st i l l be modi f i ed at submi ssi on.

ex c us i o n_ c r i t e r i a YES


173


You can select and view an active P&ID while working in a piping model. This enables the graphical transfer of piping segment data by snapping to graphics in the active P&ID. You can also specify a component name for placement by selecting a component in the P&ID.

You can use the following options to select the active P&ID to be displayed. Only one P&ID can be active for the purposes of data transfer. 

You can select a drawing from a list of P&IDs extracted from the Project Control Database. This list of drawings is limited to those P&IDs which have been propagated for the active unit number in the piping model. The applicable drawings are listed in alphanumeric order by drawing number. Since the P&ID Database is unit dependent and the Piping Design Database is design area dependent, one Piping design area may include data from different P&ID units. Therefore, you must specify the correct unit number in the active segment data prior to requesting a list of P&I drawings from the P&ID Database.

174



- You can specify a line ID by identifying piping in the piping model or by accepting the active line id. The system determines the P&ID (or list of drawings) from the line id. It searches the Segment Table of the P&ID Database using the system unique number for the drawing and the line ID for the segment.



- You can specify an equipment number and nozzle number by locating a component connected to a nozzle, by keying in an equipment number and nozzle number, or by snapping to a nozzle in an equipment model. The system determines the P&ID from the equipment number and nozzle number and data in the P&ID Database.


P&ID to Piping Data Transfer You can use the P&I Drawing in the active unit.

option to display information about a selected

Once you select a drawing by any of the described methods, the P&I drawing and the corresponding drawing border are attached as reference files.

A selected screen view is used to display the P&ID. The system stores this view number in the Type 63 data for the piping model.


175


When piping segment data is transferred from the P&ID Database to the piping model, the P&ID node numbers derived from that database are reflected in the model as a form of associativity between the P&ID and the piping model. The following rules dictate how P&ID node numbers are assigned during the creation of piping segments in the model. 

Transferring piping segment data from the P&ID Database by any means results in the P&ID node numbers being stored with the piping segment that is to be created by either the or command.

If you continue creating new piping segments in the model, either by explicitly placing a piping segment or by placing a component that results in the placement of a piping segment, the new piping segments continue to include the P&ID node numbers from the initial piping segment.  If, at any time, you update the piping segment data manually with the option, the P&ID node numbers for the subsequent piping segment is assigned as undefined (blank). 

Using the or option to place a reducing component will not result in the P&ID node numbers being assigned as undefined unless you also use the option. If you place a component after specifying the active placement point with the option, the P&ID node numbers for the subsequent piping segment is derived from those of the connected piping.  The P&ID node numbers are assigned as undefined when you connect to a nozzle, unless the active segment data is then updated from the P&ID Database.  If you place a component after specifying the active placement point with the option, the P&ID node numbers for the subsequent piping segment is assigned as undefined (blank).  If, in the command, you place a piping segment after specifying the active placement point with the option, the P&ID node numbers for the subsequent piping segment are assigned as undefined (blank). 

176



You can update the active segment data by node number, by equipment/nozzle ID, or by snapping to graphics in the active P&ID.

You can specify that the piping segment data transfer be complete or partial on the basis of the Correlation Table. The default mode is complete , and once the piping segment has been created in the model the active mode is restored to complete. In other words, the next operation will revert to complete data transfer, unless you explicitly select partial data transfer. A warning message is displayed if any one of the following conditions occurs in the process of loading the active data from the P&ID Database. 

The piping materials class from the P&ID Database is undefined in the Reference Database



The nominal piping diameter from the P&ID Database is invalid for the piping materials class from the P&ID Database on the basis of the NPD Table in the Piping Specification Table Library



The active nominal piping diameter is invalid for the piping materials class from the P&ID Database on the basis of the NPD Table in the Piping Specification Table Library in partial data transfer, where nominal piping diameter is not loaded



The fluid code from the P&ID Database is invalid for the piping materials class from the P&ID Database on the basis of the Fluid Code Table in the Piping Specification Table Library for a piping materials class where a Fluid Code Table is applicable


177


You can update the active segment data by specifying two P&ID node numbers. This option is provided in both the and commands. You can accept both or either of the two active (previously specified) P&ID node numbers. The P&ID Database is referenced using the P&ID project number. A single table is read from this database using unit number, P&ID node number 'A', and P&ID node number 'B'. Since the P&ID Database is unit dependent and the Piping Design Database is design area dependent, one Piping design area may include data from different P&ID units, each unit being designated by a unique unit number. The order of the P&ID node numbers, as specified by the user, determines the assignment of flow direction in the piping model. By convention, P&ID node number 'A' is at the Active Placement Point. As a part of the data transfer process, the P&ID node numbers are stored in the piping model for subsequent use and to retain the associativity between the segment in the P&ID Database and the segment(s) in the piping model. Likewise, the unique index into the P&ID segment table is stored in the piping model in order to enable the later comparison and update of P&ID node numbers from the P&ID Database into the piping model. It is possible that the P&ID node numbers may be changed by the P&ID propagation process for a specific segment in the P&ID Database as a result of changes to the P&ID.

You can update the active segment data by specifying an equipment number and nozzle number. If you are actively connected to a nozzle in the model, this option automatically searches the P&ID Database using the 'active' equipment number and nozzle number. Otherwise, you must either snap to the appropriate nozzle or key in the equipment number and nozzle number for the appropriate nozzle. This option is provided in both the and commands. The system accesses the P&ID Database using the P&ID project number. A single table is read from this database using the unit number, the equipment number, and the nozzle number. The assignment of flow direction in the piping model is determined by the flow direction at the nozzle end of the segment in the P&ID. As a part of the data transfer process, the P&ID node numbers determined from reading the segment table in the P&ID Database are stored in the piping model for subsequent use and to retain the associativity between the segment in the P&ID Database and the segment(s) in the piping model. Likewise, the unique index into the P&ID segment table is stored in the piping model in order to enable the later comparison and update of P&ID node numbers from the P&ID Database into the piping model. It is possible that the P&ID node numbers may be changed by the P&ID propagation process for a specific segment in the P&ID Database as a result of changes to the P&ID.

178



You can update the active segment data by snapping to graphics in the active P&ID. The system reads a single table from the P&ID Database using the unit number and the attribute linkage from the segment in the P&ID. If you identify a component in the P&ID that is associated with more than one segment, such as a reducer, the active segment data is derived from the segment associated with the connect point nearest the identification point.

The order of the P&ID node numbers determines the assignment of flow direction in the piping model. By convention, P&ID node number A is at the Active Placement Point. As a part of the data transfer process, the P&ID node numbers are stored in the piping model for subsequent use and to retain the associativity between the segment in the P&ID Database and the segment(s) in the piping model. The unique index into the P&ID Segment Table is also stored in the piping model to enable the comparison and update of P&ID node numbers from the P&ID Database into the piping model. The P&ID node numbers may be changed by the P&ID propagation process for a specific segment in the P&ID Database as a result of changes to the P&I drawing.


179


You can update the data for a previously placed piping segment using the command, by specifying two P&ID node numbers. The order of the input of the two P&ID node numbers is used to control the assignment of flow direction in the piping model. P&ID node number 'A' is associated with 'end 1' of the segment, while P&ID node number 'B' will be associated with 'end 2'. As with the previously described option, the piping segment data will be updated based upon the Correlation Table. Likewise, the user has the option to specify that the piping segment data transfer is to be complete or partial on the basis of the Correlation Table. You can also update the data for a previously placed piping segment by snapping to graphics in the active P&ID. You can load the piping segment data for an attribute break, using the command, by specifying two P&ID node numbers. The order of the input of the two P&ID node numbers is used to control the assignment of flow direction in the piping model. P&ID node number A is associated with the end of the piping segment being placed at the attribute break's location, while P&ID node number B is associated with other end of the piping segment being placed. Under user control, the revised piping segment will retain the existing piping segment data, including the P&ID node numbers. The new piping segment is created from the original piping segment with data being transferred from the P&ID Database using those P&ID node numbers specified by the user. This piping segment is created with the 'new' P&ID node numbers. As with the previously described option, the piping segment data is updated based upon the Correlation Table. Likewise, the user has the option to specify that the piping segment data transfer is to be complete or partial on the basis of the Correlation Table. You can also load the piping segment data for an attribute break by snapping to graphics in the active P&ID.

You can use the option on the Place Component form to select the piping or instrument component to be placed by identifying a component in the P&ID. It retrieves the piping commodity name for a piping commodity, the piping component number for a piping specialty, or the instrument component number for an instrument for use in reading from the Reference Database. No other component data is read from the P&ID database.

180



The command is provided as part of the command for the purpose of specifying the data comparison option for piping segments in the model. You have two options with this command. 



the ability to mark a piping segment to have segment data comparisons inhibited (or enabled) in the P&ID Data Comparison Report. This option is intended to assist the user by not reporting extraneous piping segments which do not exist in the P&ID Database and have not been assigned P&ID node numbers in the piping model, i.e. segment data has not been transferred from the P&ID database. Note that the default mode for all piping segments created in the model is to have P&ID data comparisons enabled. Thus it is not necessary for the user to take any action to enable P&ID data comparisons, unless the user had previously and inadvertently designated that P&ID data comparisons be inhibited for a particular piping segment. a rules-based command for the purpose of automatically marking piping segments corresponding to vents, drains, and off-line instrument connections for being optionally ignored in P&ID data comparisons. The option is intended to assist the user by not reporting extraneous piping segments which may not exist in the P&ID Database and usually are not assigned P&ID node numbers in the piping model. These piping segments representing vents, drains, and off-line instrument connections are marked in the user data of the piping segment. Such designations will only have an impact, if the user chooses to have these piping segments excluded from the P&ID Data Comparison Report. The limit for the maximum number of vent/drain valves and instrument connections that can be processed in one piping model is 200 for each (expanded from 100).


181


182


SECTION 7


183

SmartPlant P&ID to PDS Piping Data Transfer

184


SECTION 8

Piping data defined in SmartPlant® P&ID can be transferred to PDS® using the SmartPlant P&ID to PDS Piping Data Transfer capability. The ability to transfer PDS P&ID data to PDS 3D is documented in the PDS documentation and is therefore not covered here.

Piping System Schematic and Physical Representations Although both SmartPlant P&ID and PDS describe the same plant, a one-to-one correspondence between the components in the two models does not always exist. SmartPlant P&ID to PDS piping data transfer is essentially the transfer of data from the SmartPlant P&ID segment table, piping_seg, entity 112 to the PDS piping segment table, pdtable_12_xx. The conceptual definition of a segment is the same in both applications, however that does not mean that there is a one- to-one correspondence between these two tables. For example, the number of segments is not the same, even if the SmartPlant P&ID and PDS piping model exactly match from a design point of view. This situation is caused by the different drafting practices of SmartPlant P&ID and PDS. For example, drains are shown as macro symbols on the SmartPlant P&ID drawing. However, drains are branch segments in the PDS model. Also, process connections to instruments are recorded as instrument signal lines in the SmartPlant P&ID database, but on the PDS side, process connections are piping segments. Due to these differences, the data transfer process requires establishing a logical link between the corresponding segments. This linkage can either be in the form of interactive input from the PDS designer, who can choose a piping segment in a drawing by clicking it, or be a combination of attributes defined as unique criteria in the pid_to_piping file. For more information on attribute mapping, see Mapping Attributes: An Overview (see "Mapping Attributes" on page 197).

Data Transfer i n the Real World When you model a new line in PDS, use the option, and then click a SmartPlant P&ID segment. By doing this, you are establishing the logical link. After this link is established, future data transfers can be fully automated. However, as with most plants, there is a time when SmartPlant P&ID drafting and PDS modeling continues in parallel. The P&IDs are changing while piping modeling continues in PDS. When the designer models a particular pipeline, the equivalent SmartPlant P&ID segments may not yet exist in the SmartPlant database, creating a significant amount of piping that does not have the associative link between SmartPlant P&ID and PDS. This is just one example of how creating and updating links is an ongoing process rather than a one-time effort. For more information about maintaining links between SmartPlant and PDS, see Creating and Maintaining Links (on page 191).


185


186


SECTION 9

You can set up SmartPlant P&ID using a full installation. Full installation works with the full SmartPlant P&ID Installation on the local computer. The software versions supported for SmartPlant P&ID to Piping Data Transfer are: 

Client Computers: Windows XP with Service Pack 2

 

SmartPlant P&ID plant database in Oracle® 9.2 or 10g. You can also use Microsoft SQL Server 2000 Service Pack 3a. SmartPlant P&ID server with Windows XP with Service Pack 2



PDS 8.0 with Windows XP with Service Pack 2

We recommend that you always start with a fresh installation of Windows XP with Service Pack 2. If you must use a computer that already has Windows installed, we recommend that you: 1. Remove any SmartPlant P&ID entries such as Intergraph SmartPlant Attribute Mapper, Intergraph SmartPlant P&ID WorkStation, and SmartPlant Engineering Manager that appear in . 2. Remove PD_Shell and restart your computer. Then verify that the PDSHELL directory and and all the PDS entries in the registry are deleted. 3. Run a registry cleaning utility. 4. If your computer is running Windows XP, install Windows XP Service Pack 2. If you have a customer ID and password, you can access the latest compatibility matrix that explains which Intergraph software is compatible with each operating system, at http://ppocrm.intergra ph.com/ecustomer/star t.swe?SWECmd= Login

(https://crmweb.intergraph.com/ecustomer_enu/start.swe?SWECmd=Start&SWEHo=crmweb.in tergraph.com).

1. Start Oracle Database Configuration Assistant, select the option from the list, and click . 2. Click , and then click . 3. Select the Oracle database version that you want to access. 4. In the box, type the oracle SID name of the SmartPlant database. Click . 5. In the protocol form, accept the default option. Click . 6. In the box, type the P&ID site server name. Accept the default port number 1521. Click . 7. Click to perform the test, a nd then click . 8. To test the service, click and specify a valid username/password combination of the SmartPlant database, and then click . You should see the message. Click .


187

SmartPlant P&ID to PDS Piping Data Transfer 9. In the box, type the name of the database alias to use for the data transfer. The Net Service Name must be exactly the same as it was defined in the SmartPlant database server. Click three times, then click . The Oracle Net8 configuration for a new database alias might be different from one Oracle version to another. Refer to the proper Oracle documentation for further details on a specific Oracle version.  For Oracle 9i configuration, you can refer to the cheat sheet on the Siebel e- customer web site at http://ppocrm.intergra ph.com/ecustomer/start.swe?SWECmd= Login (https://crmweb.intergraph.com/ecustomer_enu/start.swe?SWECmd=Start&SWEHo=crmwe b.intergraph.com). Look for "Technical Tips for PDS System and Project Setup Issues" on the PDS 3D Product Information page. 

You need to install SmartPlant Engineering Manager 4.4, Service Pack 2. Loading SmartPlant Engineering Manager creates an entry in the system PATH variable. For example, "..\..\SmartPlant\Engineering Manager\Program;". 1. Insert the product CD into the CD-ROM drive. If the installation does not start automatically, double-click in the main folder. 2. Click . 3. Click to start the installation wizard. 4. Type your , , and , then click . 5. Verify your , , and , then click . 6. Click to view and read the license agreement. You must have Adobe Reader to view the license agreement. 7. Close the Adobe Reader window, then click to accept the license a greement. 8. Specify the , then click . 9. Verify that the appropriate components are selected, then click . If you want to upgrade your SmartPlant Engineering Manager data, be sure you select to install the SmartPlant Engineering Upgrade Utility. For more information, see Using the SmartPlant Engineering Upgrade Utility in the Sm artPlant P&ID Installation Guide.

10. Accept the default or select a new name, then click . 11. Review your , then click to install SmartPlant Engineering Manager. 12. Click to close the installation wizard.

188



If you are reinstalling SmartPlant Engineering Manager, you must first use the Control Panel application to remove the previous SmartPlant Engineering Manager installation.



Be sure to apply all available SmartPlant Engineering Manager service packs for the version you are installing. For more information, please contact Intergraph Customer Support.


SmartPlant P&ID to PDS Piping Data Transfer 

If you need to install SmartSketch® on the same computer, be sure to install it first. If you require SmartSketch for PDS 7.3 (for example, for the pipe support explorer), SmartSketch 4.0 is the compatible version.



For more information on full installation of SmartPlant Engineering Manager, see The SmartPlant P&ID Installation Guide .

If you need to install SmartSketch® on the same computer, be sure to install it first. If you require SmartSketch for PDS 8.0 (for example, for the pipe support explorer), SmartSketch 4.0 is the compatible version.

SmartPlant P&ID Full Installation 1. Insert the SmartPlant P&ID CD into the CD-ROM drive. If the installation does not start automatically, double-click in the main folder. 2. Click . 3. Click to start the installation wizard. 4. Type your , , and , then click . 5. Verify your , , and , then click . 6. Click to view and read the license agreement. You must have Adobe Reader to view the license agreement. 7. Close the Adobe Reader window, then click to accept the license a greement. 8. Specify the , then click . 9. Verify that the appropriate components are selected, then click . 10. Accept the default or select a new name, then click . 11. Review your , then click to install SmartPlant P&ID. 12. Click to close the installation wizard. For more information on full installation of SmartPlant P&ID, see The SmartPlant P&ID Installation Guide .

If you chose the full installation of SmartPlant P&ID, then you can test the connection with a plant structure that is already configured. 1. 2. 3. 4. 5. 6.

Click . Click . Click and browse to a SmartPlant initialization (.ini) file. Select the file and click . Select the plant structure in the dialog box. Click , and the selected plant with its drawings appears in the Drawing Manager view. If you experience problems connecting to the SmartPlant P&ID site or getting into the plant structure, verify that the site server is running and ask the SmartPlant P&ID administrator Plant Design System 3D Theory

189

SmartPlant P&ID to PDS Piping Data Transfer to set the PDS 3D users as SmartPlant P&ID administrators during this configuration. You need administrator privileges until you start doing restrictions per plant structure. SmartPlant P&ID permissions are handled in SmartPlant Engineering Manager.

190


SECTION 10

Understanding the SmartPlant P&ID to Piping Data Transfer process during PDS project execution helps you make the most of the benefits offered by this feature. Careful use of the procedures in this document, combined with delta training for piping designers and other personnel, produces considerable time savings as opposed to manually checking P&ID against PDS piping data. If you would like to use this feature but need help, Intergraph Process, Power & Marine offers consulting services to guide you. For more information, see the links on the dialog box.


191

SmartPlant P&ID to PDS Piping Data Transfer The key factor in these benefits is creating and maintaining links between the SmartPlant P&ID and the PDS segments. The following flowchart shows the workflow for resolving data transfer discrepancies during the plant design.

PDS Design Considerations 

Use the



When creating a pipeline by copying existing piping, use the command to load the data from SmartPlant P&ID.



When creating a branch using an existing segment or pipe, check whether the branch is shown in SmartPlant P&ID. If it is shown, then use the command to load the data from SmartPlant P&ID. If a branch is not shown on the P&ID – for example, drains and small bore lines – then make sure that pid_id_part_a and pid_id_part_b are completed to match those options for the



192

command often while routing new piping in PDS.


SmartPlant P&ID to PDS Piping Data Transfer header line. Also, verify that the option at the end of the list is selected. You can change this value by using the command. Default transfer modes are set such that during a partial transfer all diameterindependent properties are transferred. This option allows the drain to share the line sequence number, pressure, temperature, and so forth, with the header and still have a different diameter and line number label. This action is controlled in the pid_to_piping file. 

Instrument connections or drains on equipment with no equivalent segment in SmartPlant P&ID, can be excluded from future comparison reports. Simply select the option when you review a comparison report error related to these segments.

Synchronizing P&ID and Piping Data Synchronizing SmartPlant P&ID and PDS piping data should be done only a few times during plant design. The best times to synchronize are when the majority of the P&IDs are completed, revised, or issued. This synchronization involves running a P&ID Segment Data Comparison Report and then resolving any discrepancies and helps to build the association between SmartPlant and PDS that is then maintained throughout the plant lifetime. This synchronization involves running a P&ID Segment Data Comparison Report and then resolving any discrepancies, and is outlined in the flowchart above.

Running a Segment Data Comparison Report Running a Segment Data Comparison Report is the starting point on the flowchart. The results of this report depend on two key factors: 



The matching criteria defined in the pid_to_piping file in the plant directory. For more information, see Map an Ignored Attribute (on page 198) or Map an Unmapped Attribute (on page 198). The setting.

While running this report, the criteria should be node numbers.

setting should be used, and matching

Based on the availability of P&IDs during the initial piping design stage, the number of discrepancies can be very high on the first run. Our experience shows that a piping designer, who has good knowledge of the piping involved and the related P&ID, takes approximately two to four minutes to resolve a discrepancy. Successive uses of this procedure should reduce the numbers of discrepancies. If plant design resources or time do not allow resolving all discrepancies, then you should consider alternative methods to running the Segment Data Comparison Report. One alternative is to change the matching criteria. Matching criteria directs the software to establish associations between SmartPlant P&ID and PDS piping segments based on the value of the attributes specified. For example, the default criteria of node numbers means that node numbers for a PDS piping segment must match with a P&ID segment. If the SmartPlant P&ID to PDS Piping Data Transfer has not been done for a piping segment, then no node number is defined for that segment. This situation generates a discrepancy. If the majority of the piping falls under this category, then the number of discrepancies can be very high. To reduce this number, change the matching criteria to something other than node numbers. Typically, any of the individual properties of a line number


193

SmartPlant P&ID to PDS Piping Data Transfer label such as NPD, line sequence number, insulation purpose, and so forth, can be used. It is better to use as many properties as possible so that they form a unique combination. All properties specified as matching criteria should have some value assigned to them on both sides. Another alternative to running the comparison report is to specify segment search criteria. This method can be used if all instrument connections on equipment or drain lines not shown on the P&ID contain common attributes such as different fluid codes or prefixes to line sequence numbers, and so forth. Another possibility is to use a range of diameters so that small diameter segments can be eliminated.



When setting up data transfer for multiple plants, if the PDS 3D and SmartPlant P&ID plants have the same set of properties and the same intended mapping, then you can copy the file from one plant to another. The Attribute Mapper always verifies that the SmartPlant site in the .mdb file is the same as the map for the selected PDS project. However, if you are not sure if the plants have the same set of properties, we recommend that you copy the delivered file from the folder.



For a project where data transfer was set up to work with an earlier version of SmartPlant P&ID, some attribute mappings have changed. You can use either the new file delivered in the folder or follow the procedure mentioned for in the PDS file. Even if you are going to work with the default attribute mapping, you must start SmartPlant Attribute Mapper at least once. If necessary, you can back up the updated file, delete the changes, and copy a fresh to go through the mapping process again.



1. Copy .mdb and to the PDS project directory. For projects created with version 6.4.1 or later, these files are copied automatically from the folder at the time of project creation. 2. Click to display a list of available PDS projects.

194


SmartPlant P&ID to PDS Piping Data Transfer 

After a relationship between attributes is established, the SmartPlant Attribute Mapper opens. The link between the SmartPlant P&ID plant and the PDS 3D project is established and updated automatically in the SPMap.mdb file.



For more information about mapping attributes, see Map an Unmapped Attribute (on page 198) or Map a n Ignored Attribute (on page 198).

Modification in SmartPlant P&ID The SmartPlant P&ID software generates node numbers during consistency checking. If existing segments on the P&ID are modified, then those node numbers may also be modified. This situation occurs when placing either a branch on an existing segment or a segment break, causing the link between SmartPlant P&ID and PDS to become outdated. In most cases, changes in SmartPlant P&ID mean changes in the piping model. Resolving this type of discrepancy improves the integrity of the design data.

Modification of a PDS Model Physical modification of segments with PDS commands such as , , , and so forth, do not affect SmartPlant P&ID to PDS Piping Data Transfer. All branch component placement commands break the segments and potentially lose links with SmartPlant. While placing drain connections, which are not shown on P&IDs, it is better to use the command on the header segment before placing the drain connection or branch components. Then all three segments are linked with the proper segment in SmartPlant P&ID. After creating the branch drain segment, make sure that the mode attribute is set to for the branch segment. Transfers done after placing a drain require that you use the command three times.


195


196


SECTION 11

SmartPlant P&ID to Piping Data Transfer relies on an attribute map stored in a Microsoft Access database located in the PDS project folder. This map database file is named SPMap.mdb, and contains information about the Smart Plant P&ID site server and plant. The Attribute Mapper utility is used to manipulate this map database. The Attribute Mapper is started from a shortcut provided in the PD_Shell program group named . The Attribute Mapper utility maps, un-maps, or ignores attributes between PDS 3D and SmartPlant P&ID. The Attribute Mapper interface is similar to Windows Explorer in that it displays a tree view on the left side and list view on the right side. Attributes for piping segment, piping component, and instrument tables from the PDS 3D design database are available to map with corresponding SmartPlant P&ID tables, specifically the PipeRun, PipingComp and Instrument tables. The tree view divides attributes into four categories based on map status: , and . For SmartPlant P&ID to PDS 3D data transfer, the same as the status.

, , map status is the

The default map PDS software includes a default map in the PDSHELL\pid folder. This map has a set of attributes that are pre-mapped with known SmartPlant P&ID properties. When you create a new project using PDS software, this map is copied to the project folder. For older projects, the SPMap.mdb file should be manually copied from the PDSHELL\pid folder into the 3D project folder. The default map is functionally equivalent to the pid_to_piping file used for PDS 2D to 3D data transfer with few exceptions. For example, units are not required to map because of the way unit information is stored. This applies to attributes like pressure and temperature. The SPTransferOpt file includes the three options that you can find at the bottom of the pid_to_piping file. For PDS 2D to PDS 3D data transfer, the mapper specifies the database attributes that are considered in order to perform the data transfer. By default, for PDS 2D transfer the mapper is mapping Nodea (piping attribute 67) and Nodeb (piping attribute 68). For SmartPlant P&ID to PDS 3D data transfer, because there are no node numbers in SmartPlant, the mapper is mapping piping attribute pid_index_no (piping attribute 73).

Select li sts Select-listed SmartPlant P&ID properties are transferred based on their text value instead of number. The Attribute Mapper creates a map of PDS codelist entries for every SmartPlant select list used in the mapped properties. For example, fluid code "P" is represented by the PDS 3D codelist entry 25 and by entry 35 in the SmartPlant P&ID select list. When the fluid code property is transferred, the property value changes from 35 in the SmartPlant database to attribute value 25 in the PDS Database. This functionality has removed the requirement of maintaining the same select list and codelist values in SmartPlant P&ID and PDS 3D.


197


This procedure includes only the major steps involved in mapping an attribute. Refer to PDS online Help or documentation for detailed instructions. 1. Open the

utility. For more information, see Establish a

Smar tPlant/PDS Link (on page 194) .

2. Select the category. 3. Select the table in the tree view. 4. Select a PDS attribute in the list view. 

Properties mapped with the use the



Properties mapped with the option set to receive the default value, which you enter in the box, during partial data transfer. Properties mapped with the option set to do not get a default value and do not get transferred during partial data transfer. All properties are transferred during complete data transfer.

 

option set to toggle within PDS.

are transferred when you

This procedure includes only the major steps involved in mapping an attribute. Refer to PDS online Help or documentation for detailed instructions. 1. Open the

utility. For more information, see Establish a

Smar tPlant/PDS Link (on page 194) .

2. Expand the category. 3. Select the table in the tree view. 4. Select a PDS attribute in the list view. 

Properties mapped with the use the



Properties mapped with the option set to receive the default value, which you enter in the box, during partial data transfer. Properties mapped with the option set to do not get a default value and do not get transferred during partial data transfer. All properties are transferred during complete data transfer.

 

198

option set to toggle within PDS.

are transferred when you


SECTION 12

The software compares segment data on the basis of the matching criteria defined in the pid_to_piping correlation table. If no matching criteria are defined, the software compares segment data on the basis of the SmartPlant P&ID node numbers that are common to both the SmartPlant database and the PDS database, or the node numbers and line number labels, depending on what you specify using the available options. The piping segment data is also compared on the basis of the options.

or

data transfer

If a match is found, each attribute value, as specified in the pid_to_piping correlation table and filtered for either complete or partial data transfer, is compared with the corresponding property value in the SmartPlant database. For any pair of corresponding attribute values that differ, the discrepancy is reported in the Segment Data Comparison Report. This report includes a comparison of the flow direction for the PDS piping segment and the SmartPlant P&ID segment by using the P&ID node numbers. If no corresponding segment is found in the SmartPlant database for a PDS piping segment with valid matching criteria, an error is reported. If the search mode is set to in the pid_to_piping file, the software compares all of the SmartPlant P&ID segments that have matching search criteria to the applicable PDS piping segment and uses the SmartPlant P&ID segment that best matches the PDS piping segment for the comparison. Otherwise, the search mode is , and comparison is made with the first P&ID segment that has matching criteria.  

The Segment Data Comparison Report also includes line sequence numbers. Because the data comparisons are performed on the basis of the PDS piping segments, not all segments in the SmartPlant database are checked for matches.

The software creates the following files in the same directory location as the processed model file:   

A report file named model_number .pc (model_number is the number of the model that is extracted from the PDS Project Database.) A non-printable, sorted file named model_number .pci (This file is used by the command.) A non-printable, sorted file named model_number .pca (This file is used by the , , , and commands for the approval of data discrepancies. The .pca file is initially created when you approve a discrepancy, and the file is appended to with each additional approval.)

You can format the title page and the heading for each page of the Segment Data Comparison Report using the \win32app\ingr\pddesign\sample\pid_cmprpt.fmt format file. The remainder of the report is in the following format:


199


Attribute

Value in Model

Value in P&ID

line_number_label

2"A-A5A2F-N55011

2"A-A5A2F-P550107

line_sequence_no

550111

550107

insulation_purpose N P Data in the Segment Data Comparison Report is sorted first by line number label and then by the SmartPlant P&ID node numbers, if applicable.

200


SECTION 13

Matching Criteria PDS uses matching criteria to generate the Segment Data Comparison report. In order to compare segment records, the records must first be matched or correlated. Matching criteria defines the correlating attribute in the PDS 3D database. The default attribute map reserves the pid_index_no attribute for matching criteria. This fact means that the Segment Data Comparison report compares piping segment attributes from the PDS and SmartPlant databases if the pid_index_no in the PDS database matches the unique sp_id in the SmartPlant database.

SmartPlant P&ID Consider the following points when planning for data transfer from a SmartPlant P&ID plant to a PDS 3D project. 

— By default, PDS searches the piping specification based on predefined aabbcc codes. SmartPlant P&ID symbols must have a property mapped to the aabbcc_code attribute in the PDS database. The delivered SmartPlant P&ID piping component symbols have a property called aabbcc_code, which can be viewed and edited in Catalog Manager. Any new symbols must have this value defined, either at symbol creation or later.

— PDS 3D is not capable of handling spaces in the path names to any files. Therefore, this PDS restriction also applies to P&IDs. While creating units and drawings in the SmartPlant P&ID site, take care to avoid creating paths with spaces.  — SmartPlant P&ID stores drawings in a format other than IGDS (MicroStation). These drawings are converted to IGDS format to display in PDS. By default, PDS and MicroStation use a black background, while SmartPlant P&ID uses a white background. When converted to IGDS format, this difference can make some SmartPlant P&ID graphics barely visible on the black background. Consideration should be given to this fact while defining symbology within SmartPlant P&ID plants. SmartPlant P&ID symbology is defined in Options Manager. 

 

 

Two methods exist to manipulate the display so that all of the graphics are clearly visible in their new format: : Turn off the

setting under in PDS. This action displays the drawing using the active color scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID. : Change the .

color of the piping model to a light color by using

— If properties added to the SmartPlant database need to be transferred to PDS, be careful to match attribute type and length on either side. The maximum string length supported by RIS / PDS 3D is 240 characters. If a property has an associated select list in SmartPlant P&ID, then it should have a corresponding codelist in


201








3D. You must run the Attribute Mapper to map new properties if you want the data to transfer. — Even though having the same number and sequence for entries within a codelist or select list is not required, for any mapped attributes, the PDS 3D codelist should have all entries from the SmartPlant P&ID select list. If a new text entry is added to a SmartPlant P&ID select list, the same text entry should be created in the corresponding PDS 3D codelist. The Attribute Mapper must be run after any such change. — PDS uses the c oncept of layers in a piping design to display selected elements of a drawing; whereas, SmartPlant P&ID uses drawing filters. The ExportLayer.xls file defines how the layers in PDS are related to the different drawing objects. The location of this Excel file is defined in Options Manager. You can assign layer numbers between 10 and 63 to item types in order to assure that graphics appear in the designated layers in PDS. Items are named according to filters, which are defined in Filter Manager. For more information, see the topics dealing with layers in the SmartPlant P&ID online Help.

PDS 3D 



202

— A PDS 3D codelist can be a super set of a SmartPlant P&ID select list. This means that a PDS code list can have extra entries not contained in the SmartPlant select list because the data transfer works one way; that is, from SmartPlant P&ID to PDS 3D. — Attributes can be created in PDS 3D independent of the SmartPlant P&ID plant if data transfer is not required. If transfer is required, care should be taken when adding attributes. A SmartPlant database does not distinguish between short and long integers. Any new integer property that is added to such a database must be created as a long integer in the PDS database.


SECTION 14

Updates the active segment data based on information defined in the SmartPlant P&ID. The system verifies the temperature and pressure service limits when loading segment data from the SmartPlant database into an existing piping segment for which data was previously transferred. — Transfers all mapped attributes from the selected SmartPlant P&ID segment into the active PDS segment data. Attributes that are transferred are shown in yellow. Attributes that are not mapped are shown in black. — Transfers those mapped attributes, that have the Partial option chosen during attribute mapping, from the selected SmartPlant P&ID segment into active PDS segment data. Attributes that are transferred are shown in blue. — Updates the active segment data from the SmartPlant P&ID using the segment data attached to the specified Equipment/Nozzle ID.


203


204


SECTION 15

This command searches, selects, and displays the SmartPlant P&ID within the PDS piping design environment. This display enables the graphical transfer of piping segment data by snapping to graphics in the active P&ID. You can also specify a component name for placement by selecting a component in the P&ID. For data transfer purposes, only one P&ID can be active. You can select a P&ID to display from the list of P&IDs extracted from the SmartPlant database. The list of P&IDs is limited to P&IDs for the active unit number in the PDS piping model, or if the active unit number is undefined, then all P&IDs from the SmartPlant database are listed in alphanumeric order by drawing number. The command checks for the existence of SmartPlant P&ID data in the PDS project. If P&ID data is found, then PDS 2D starts the old software component to allow data transfer from P&ID. If the project is PDS 3D only, then the data transfer from SmartPlant P&ID to PDS 3D starts. You can use the following options to select the P&ID to display. — Launches SmartPlant P&ID automation to convert the selected P&ID from its native format to IGDS format. The converted drawing is placed in a temporary folder. The drawing is closed automatically upon exiting the design session. — Converts SI units in SmartPlant P&ID using unit-related codelists from the Standard Note library in PDS. SmartPlant P&ID stores all properties with a unit of measure in SI units. For example, length is stored in meters regardless of your plant settings. The software then checks another property, that determines how you want length values to appear. When a property represents a quantity based on units (for example, pressure, temperature, and so forth) data transfer looks at the active segment data, or type 63 settings, to determine the unit of measure to use. The SI value stored in the database is then converted using unit- related code lists from the Standard Note library. — Uses a codelist map to translate the codelisted attributes. The Attribute Mapper stores mapping of codelist numbers such that their text values match. Data transfer uses this codelist map to translate the codelisted attributes from the database to the PDS database. If the SmartPlant database participates in Workshare environment, then the P&ID list is a combination of the P&IDs owned and subscribed to (that is, published by remote location) by the site.  Use the LocalModelItemLookupTable.sql utility if your connected Workshare satellite experiences performance problems when transferring piping data from SmartPlant P&ID to PDS. This script converts a satellite database view (namely, the T_ModelItemLookup) that references a host table into a local table, allowing the data transfer to proceed without using a DBLink. SmartPlant P&ID uses the DBLink to fetch unique Long IDs from the Host when running from a connected Workshare satellite. If the performance of opening the PID 


205

SmartPlant P&ID to PDS Piping Data Transfer file in PDS is an issue or if maintaining the correlation between SmartPlant P&ID and PDS after the merge is not an issue, then you can run this script to change the lookup for the Long ID from a view to the host to a local query. This utility is delivered as an SQL script to the C:\Program Files\SmartPlant\P&ID Workstation\Program folder and can be executed using any Oracle user interface, such as SQLPlus. Do not use this script if the transferred PDS data will be merged back into a host PDS database because the Long IDs will not be unique at the host. 

206

Because SmartPlant databases are unit-dependent and PDS databases are design areadependent, one PDS piping design area can include data from different SmartPlant units. Consequently, you must specify the correct unit number in the active segment data prior to requesting a list of P&IDs from a SmartPlant database.


SECTION 16

This command specifies a line ID by identifying piping in the PDS piping model or by accepting the active line ID. The system determines the SmartPlant P&ID (or list of P&IDs) from the line ID. It searches the Segment Table of the SmartPlant database using the system-unique number for the drawing and the line ID for the segment. All P&ID segments belonging to the specified line ID are highlighted.


207


208


SECTION 17

This command specifies an equipment number and nozzle number by locating a component connected to a nozzle, by typing in an equipment number and nozzle number, or by placing a data point over a nozzle in a model. The system determines the SmartPlant P&ID from the equipment number and nozzle number and data in the SmartPlant database. All P&ID segments that have the same line ID as the segment connected to the active nozzle are highlighted. Currently, only the first segment coming off the nozzle is highlighted, not the entire line.


209


210


SECTION 18

Displays information about a selected SmartPlant P&ID in the active unit.


211


212


SECTION 19

Displays SmartPlant P&ID display categories. Categories that are currently displayed are highlighted on this dialog box. Selecting a category toggles its setting. P&ID controls display and symbology through the use of drawing filters. The P&ID graphics in the converted IGDS format are not organized into familiar categories such as piping, equipment, or instruments, instead the software displays MicroStation levels 1 through 63 as SmartPlant P&ID drawing filters. Some of the categories are turned off automatically to hide blank label enclosures and inactive heat tracing graphics.


213


214


SECTION 20

Restores the PDS 3D model view in the window where the SmartPlant P&ID is currently displayed.


215


216


SECTION 21

Closes the currently displayed SmartPlant P&ID and restores the PDS 3D model view.


217


218


SECTION 22

Selects the piping or instrument component that you want to place by identifying a component in the SmartPlant P&ID. If the selected instrument has a tag number that does not exist in the Piping Job Specification, the system displays the dialog box with both and options. Select the option, select the shape that you want, and enter the dimensions that are required. This procedure allows the tag number and the property that were mapped in the attribute map to transfer from the SmartPlant to the PDS database. This mechanism also applies to piping specialties.


219

SmartPlant P&ID to PDS Piping Data Transfer Tr ansfer

220


SECTION 23

Compares the existence of user-specified named components between the PDS and the SmartPlant databases in batch mode on the basis of a user-defined list of lines and then generates a report of the results. If a PDS 2D P&ID database exists, then it is used with the PDS model as the basis for comparison. If it does not exist, then the SmartPlant database is used as the basis for comparison. As part of the report, the software includes the database that the comparison was based on. The comparison does not make use of either the P&ID drawing or the PDS piping model. Therefore, the order of components c omponents is not considered in the report. A user-defined list, design area, or model is used to define those items that are included in the report. The user-defined list must have one line ID per line. Whether you create a list or use a design area or model, the list of line IDs used to perform the comparison is included in the report. The comparison considers the entire piperun in both the SmartPlant database and the PDS database. If a line ID is used in multiple SmartPlant SmartPlant P&IDs or is included in multiple PDS models, the complete definition of all P&IDs or models is included in the report regardless of the line-ID option that is selected. The following items are included in the comparison report: 







The named components in the piping design database are included and are compared on the basis of the following following data: 

Tagged piping commodities are compared on the basis of their piping component number



Piping specialties are compared on the basis of their piping component number



Inline instruments are compared on the basis of their instrument component number

Tagged piping commodities in the SmartPlant database that have the following data are included: 

The defined



The

flag is set to by system or by user and the commodity code is is defined

Piping specialties in the SmartPlant database are determined by those piping components that have the following data: 

The

flag is set to by user



The

flag is blank



The

is defined

Instruments in the SmartPlant database are determined by the following criterion: 

Only those instruments that are applicable to the PDS 3D model, such as those requiring dimension definition in the RDB, as determined by an Instrument Correlation List


221

SmartPlant P&ID to PDS Piping Data Transfer Tr ansfer The Instrument Correlation List, which is necessary to define the applicable instruments for transfer, is a user-defined ASCII file in the project folder and is named pid_instrument. With this list you can specify the inclusion or exclusion of SmartPlant P&ID P&ID instruments on the basis of their aabb or aabbcc codes. c odes. You can include or exclude groups of instruments on the basis of the aabb code for that instrument by using the appropriate keyword, either or , followed by the aabb code. You can specify exceptions to the aabb codes on the basis of specific aabbcc codes so that you can exclude from an group, or you can add those entries to an group by adding the exceptions under the line containing the or statement. The character signifies signifies a comment line in this ASCII ASCII file. The following text represents the default Instrument Correlation List that defines the SmartPlant P&ID instruments that are applicable to the PDS 3D model. In this example, the aabb code represents a substring search of the aabbcc code. !Include all control valves I ncl ude ude 7P1 7P1E E ! I nc l ude al l r e l i ef devi c es es I ncl ude ude 7P2C 7P2C ! I ncl ude al l ot her i n- l i ne i nst r ument s I ncl ude ude 7P3C 7P3C ! excep cept f or t he f ol l owi ng 7P3C44 7P3C46 ! Excl ude al l of f - l i ne i nst r ument s Excl Exc l ude 7Q4D ! excep cept f or t he f ol l owi ng 7Q4D21 7Q4D24 7Q4D27 7Q4D28 7Q4D29 7Q4D30 7Q4D31 7Q4D32 7Q4D33 ! Excl ude al al l syst syst em f uncti ons Excl ude 7Q 7Q5A

You can format the title page and a nd the heading for each page of the Named Component Existence report using the win32app\ingr\pddesign\sam win32app\ingr\pddesign\sample\pid_cmprpt.fm ple\pid_cmprpt.fmtt file. The remainder of the report contains the following f ollowing sections: 

222

The list of line IDs that determine the basis for the report



Named components components in the SmartPlant SmartPlant database, that are not in the PDS 3D model, model, are reported with the component number and the drawing number



Named components components in the PDS PDS 3D model model that are not in the SmartPlant SmartPlant database are reported with the component number, the design area number, and the model number


SECTION 24

Some common difficulties that you may encounter are listed here, along with possible solutions.

No Projects on This Site On some systems, you receive the error when you try to connect to the SmartPlant P&ID P&ID site server. As a workaround, you can edit the Microsoft Access file \projectname\project\SPMap.m \projectname\project\SPMap.mdb db directly and add a line in the connection table as follows: is the SmartPlant P&ID plant name



is the complete UNC path to the SmartPlant P&ID plant SPMap.mdb SPMap.mdb file has to be selected

 

is the UNC path to the SmartPlant initialization file is the project name

 

Save changes made to the SPMap.mdb file, and run the

command again.

If a client computer experiences problems connecting to the project, remove the Intergraph SmartPlant Attribute Mapper and Intergraph SmartPlant P&ID Automation components using . Restart the computer and reinstall PD_Shell and SmartPlant P&ID P&ID Integration Tools using the silent installation. Be aware that for f or PDS users to set up the attribute map and perform data transfer, they must have permission to access the SmartPlant server through SmartPlant Engineering Manager.

Display Start PD_Shell, and go to piping. Inside the PDS piping model but before using the command, select one of the two methods below so that all of the P&ID items are clearly visible in order to display properly the converted P&ID within PDS: 

Method 1: Turn off the

setting under . This action displays the drawing using the active color scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.



Method 2: Change the .

color of the piping model model to a lighter color by using

Display by Unit Filter Run the command as with PDS 2D, unless the unit is simply a filter. If not specified, all plant P&IDs are shown. Note that the P&ID Drawing Name is what you see on the data transfer dialog boxes, not the drawing number.

Temperatur Temperatur e/Pressur e/Pressuree Unit Unitss Select lines for piperun and component data for the option. For Pipeline data, four sets of temperature/pressure values with units must be set in the SmartPlant P&ID or you


223

SmartPlant P&ID to PDS Piping Data Transfer Tr ansfer will receive an error about a bout temperature/pressure limits. You can choose the option in the PDS project data manager to prevent that error. When using this option, the lower range of the temperature/pressure values is not checked, thus allowing undefined values in PDS: -9999.

Removing Removing Software from a Silent Installation Configuration For a silent installation, when you accept the option on the PDS component loader dialog box, the following components are installed and the following folders created:     

Intergraph SmartPlant Attribute Mapper Intergraph SmartPlant P&ID Automation, including \Program Files\Common Files\Common Files\Intergraph\RAD (used by SmartPlant P&ID and SmartSketch) \Program Files\Common Files\Intergraph Shared\SmartPlant Shared\SmartPlant \Program Files\SmartPlant Files\SmartPlant

If you need to remove the components for the silent installation and have SmartSketch on the computer, remove SmartSketch and its associated components c omponents first. Continue by removing PD_Shell from the utilities. This action prompts you to confirm deletio n of the Intergraph SmartPlant Attribute Mapper. Select , and confirm the deletion of all shared files. This step does not delete Intergraph SmartPlant P&ID Automation. To remove automation, go to , select from the list, accept its deletion, and confirm deletion of all shared files. Then restart your computer. Before re-installing any software in the client computer, delete the three folders specified above, and any files contained in them.

Known Issues and Limitations The command cannot convert and display a P&ID that has a space in the P&ID file path. Make sure the paths and filenames to the P&IDs have no spaces in them. You get the same result if you use a comma in the P&ID title.  When the P&ID plant hierarchy does not contain the item, an error occurs when snapping to a piping segment or a component in the environment.  You must define the property for a component in SmartPlant P&ID P&ID if you are planning to use use the command for transferring any other component information. The implication is that your piping specifications must be created before drawing the P&IDs if you use this command for any data transfer.  You must dismiss the menu after selecting the P&ID that you want to display. Sometimes Sometimes this form may be hidden, and you must dismiss it before you can transfer data from a pipeline. 



224

Levels settings (that is, displays of drawing filters) are not saved for a SmartPlant P&ID drawing. You must select the correct levels each time that you enter the drawing.


SmartPlant P&ID to PDS Piping Data Transfer Tr ansfer 

If you want to see the P&ID labels and line types correctly, you must map your P&ID fonts to proper MicroStation fonts in one of the .ini files. ISO Plus RDB fonts and borders.txt contain this information. Also, the standard RDB Arial Narrow is mapped to a not-always present MicroStation MicroStation font and causes causes unreadable labels on the screen.


225


226


SECTION 25

This chapter provides information required to understand the terminology and philosophy involved with interference detection. Interference Checker/Manager (PD_Clash) processes a specified design volume for interference clashes. You can check for, review, and revise interferences at any stage of the design process. The first section in this chapter is an overview of the interference management process; it briefly covers the following topics:    

Software setup Interference envelope generation Clash detection Clash management and tracking

The second section is a review of project organization and the different units into which a plant/project can be broken for ease of manipulation. The third section describes how to set up a system to support interference detection. The fourth and final section is a general description of interference envelopes, the various types of interferences (clashes) and what happens during interference detection and management. Interference Checking Process Overview ...................................... 227 Project Organization ...................................................................... 229 Setting Up a System to Support Interference Detection ................ 235 Understanding Interference Envelopes .......................................... 236

The following outlines the basic steps associated with interference detection and management.

Setup (outsi de the Interference Manager modu le) 1. Define data with the .  Volume/Area definitions determine the extent of the project to process. The extent may be physical by defining pre-defined volumes or logical by grouping models in a design area. 

To disable interference checking between certain disciplines, use the toggle when defining the Discipline data.

2. Define interference data with the


.

227

Detecting and Managing Interferences 

The construction tolerance, the necessary space allocated beyond that which is necessary for the component and its insulation, for each discipline is defined with the form.



The action discipline is used to assign responsibility for a clash to a certain discipline. The action discipline is defined using the option on the form. The defined action discipline appears on plots and in the form in the

field on the module.

3. The system accesses the model files to generate envelope files. The envelope files have an .env file extension. 4. The graphical volume for each component is defined by an interference envelope parametric shape definition. This is an Eden module similar to the parametric shape module used to place the component in graphics. Before performing interference detection on newly created or modified interference envelope parametric shape definitions, use the option to generate a MicroStation-type graphic from the interference envelope. The graphics file is named after the envelope with a .til file extension. 5. Verify the consistency between the dates of envelope files and current design files using the option. The results of the verification indicate which envelopes need to be updated. 6. Run the option to compare the envelope files for clashes within the specified area or volume. 7. A volume filter can be set for single runs of interference detection. Only the clashes found within the specified volume are available for review after an interference detection run using this option. 8. For pre-defined volume design areas, the system checks all models within the prevolume. This includes the portion of any model envelope file that encroaches within that volume regardless of its discipline. — OR — For regular design areas, the system defines the volume as that which encompasses all model envelope files within the selected design area. This includes the portion of any model envelope file that encroaches within that volume regardless of its discipline or design area assignment. 9. For the specified area/volume, the system processes all of the portions of model envelopes or pairs of envelopes, for example: Model A vs Model B Model A vs Model C Model A vs Model D Model B vs Model C 228


Detecting and Managing Interferences Model B vs Model D Model C vs Model D 10. When a clash is detected, it is written to the database, and the graphics representing the clashing elements are written to the appropriate marker file. If you checked the entire project, the clashes are written to the project marker file. If you checked a design area, the marker file is named after the design area with the extension which represents the discipline: Piping = 1 Structural = 3 Raceways = 5 Equipment =2

HVAC =4

Architecture = 6

11. The Interference Report is created during the interference detection process and is named after the project or design area, depending on the option selected for interference detection, with an .int file extension. It contains only the unapproved clashes for that run. 12. Edit and review existing clashes, manipulate views, and approve exisiting clashes with the option. This option displays and highlights clashes within a graphics environment, which can then be reviewed, edited or approved. 13. For unsuspected clashes, review envelopes in question using the command. This command generates a report with a .evd file extension. For example, this report contains instances such as when two or more groups of sub-components are contained within one component but are not geometrically connected, in other words do not have overlapping ranges. 14. Clashes can be plotted any time after interference detection using the option. 15. Aside from the Interferences Report, which is automatically generated during interference detection with the option, reporting on the Project Control Data is done using the . Discrimination data and format files are used to generate specific types of reports. This sort of report might include a list of clashes involving the structural discipline, the approval status of those clashes, and the action discipline assigned to these clashes.

As discussed in Chapter 1, PDS uses the following organization to break the plant into smaller units that can be handled more easily. A project is a convenient grouping of all of the items that constitute a plant. The project is the fundamental structure for working in PDS. The project constitutes the entire volume of the project. A design ar ea represents a specified volume or logical area of the project for a specific discipline. Design areas can be used to break up the project into smaller areas for interference checking or reporting. This speeds up processing when only a portion of the project has changed. The models or model components that are not within the area/volume will not be checked. A design ar ea pre-defined volume represents a pre-defined volume of the project for a specific discipline. The volume is defined by using the . Make sure that the pre-defined volume encompasses all the models that you want to be checked. The models or


229

Detecting and Managing Interferences model components that are not within the volume will not be checked. The Prevolume is used to encompass models and model components that might not have been grouped together otherwise, or to define a design area that is smaller than usual. A model is a 3D Microstation file that has a defined discipline and is located within the volume of the project. A model represents a subdivision of the project based on work responsibility, completion of schedules, and computer response time. A volume filter can be used to decrease the volume of a project, area, or pre-defined volume to further decrease the processing time when only a sub-part requires checking or reporting.

This section describes design areas and volumes and how they pertain to interference checking. Running the Interference Checker for an entire project takes considerably longer than running it for a design area. If the project workload is being shared, one of the design area options would be the most efficient. The design area options are less time consuming and create individual sets of reports rather than one set of reports for the entire project. Adhere to using either the option or one of the options for the life of the project for the most consistent results.

Project This option on the form performs clash checking for all of the envelope files defined for the project and creates interference, difference, and batch queue error reports. To specify a smaller volume for a single clash check, set the toggle to On. The dotted rectangle signifies the volume that is processed using the

230

option.


Detecting and Managing Interferences

Piping Des ign Area a nd Des ign Area These options display a list of design areas for the specified discipline that are available for clash checking. After a design area has been selected, the system defines a volume that encompasses all models within the selected design area. It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the defined volume. To specify a smaller volume for a single interference check, set the toggle to On after selecting a design area. The dotted rectangle signifies the volume that is processed using the name of the selected design area is DesA1 .

option. The

Des ign Area an d P iping Des ign Area Pred efine d Volume These options display a list of design areas with pre-defined volumes available for clash checking. After a design area has been selected, the system uses the pre-defined volume (as specified through the ). It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the pre-defined volume. The Interference Checker does not include models or parts of models that are in the selected design area that do not fall within the pre-defined volume.


231

Detecting and Managing Interferences The dotted rectangle signifies the volume that is processed using the option. The name of the selected design area is DesAPreV1 .

If you use Pre-defined Volumes as your method of checking, it is recommended that you run a project wide check at the end of the project to ensure that nothing was missed. However, you should not switch between Pre-defined Volume and Project on a consistent basis.

Volume Filter This option creates a Volume Filter for one run of the Interference Checker. When set to , you can define the low and high Easting, Northing, and Elevation coordinates for one run of the Interference Checker in the following fields. When set to the system will use the default or pre-defined volume.

232


Detecting and Managing Interferences A volume filter can be used to decrease the volume of a project, area, or pre-defined volume to further decrease the processing time when only a sub-part requires checking or reporting. The dotted rectangle signifies the volume that is processed when the Volume Filter has been activated and the volume to be checked has been specified.

Single/Dua l Owners hip of Clas he s PD_Clash can be set up to allow single or dual ownership of clashes. This is very useful when more than one design area needs to own, review, or approve a clash. PD_Clash provides the capability for dual ownership–ownership available to each design area that CONTAINS a component involved in a clash (when interference detection is run on that area) or single ownership–ownership assigned to the first design area to find the clash. Dual ownership does not mean that ownership is automatically given to both design areas when a clash is found. It means that ownership is available to both design areas when interference detection is run on each. Since clashes are stored in the database, reports can still be run on both design areas involved in a clash, even if interference detection has not been run on both design areas. However, clashes are only written to the applicable design area's marker file during the interference detection process for each design area. Therefore, clashes can only be reviewed and approved in design areas on which interference detection has been run. This option does not define ownership assignments once clashes have been found. It acts a filter in the interference-detection process. By default clash checking is done in mode. In this mode, each clash belongs to the design area in which it was first found. When clash checking is done in this mode, clashes involving models that do not belong to the design area being checked are still assigned to that design area.


233

Detecting and Managing Interferences For instance, if design area C were checked for interferences in the mode, the system would compare all models that fall within the specified volume including:



all models against themselves all design area A models against design area B models all design area C models against design area A models



all design area C models against design area B models.

 

All of the clashes would belong to design area C. In the mode, ownership is not based on the first design area to find the clashes but on the design areas which own the components involved in a clash. Interference checking is performed between models belonging to the design area being checked and all other models that fall within the volume of that design area. Clashes that do not involve at least one component from the design area being checked would not be found. For instance, if design area C were checked for interferences in the mode, the system would compare models in design area C with models falling within the specified volume including: 

all design area C models against themselves all design area C models against design area A models



all design area C models against design area B models.



The clashes found involving, for instance, design area C models against design area A models would be owned by design area C. Clashes could be reviewed and approved in design area C and reports could be run on either design area C or design area A. You could not review or approve clashes in design area A until you had run interference detection on it. Clashes that do not involve at least one component from design area C models would not be found.

234



The following project setup considerations are necessary to support interference checking. 1. Load software All PDS servers and workstations must be loaded with the same release of PDS and nucleus software. The PDS software between servers and workstations must be compatible to run correctly. It is highly recommended that you read the Release Notes of the PD_CLASH README file when new releases are issued so that you will be informed of any changes made to the product. The CAD Support person would most likely do this. 2. Set up plot queues. The Interference Manager provides one default and four optional plot queues for different types of plotters. The selection of the plot queue applies to all graphic interference clash plots in a batch process. Multiple queues provide the flexibility in situations that arise which require different plotters for different paper types. This step would be completed by the CAD Support/System or Project Manager. 3. Define discipline responsibilities.  The interference software uses area and model data to locate the models within a specific design area for processing. This is done when the areas and model files are created. The location of the area marker file and model design file are stored by the system using data provided via the . 

Marker files are used by the software to place graphic markers for clashes that are detected during interference checking.

4. Decide on Project or Area processing. Interference checking can be done for the entire project or it can be divided into small portions called design areas. The processing time for an entire project is much greater than for a design area. Also, it is often the case that only a certain design area or set of design areas need to be checked. Once you decide which method to use, either the option or the design area options, remain consistent. The more consistent you are with your option selection, the more consistent the results will be. For example, you might select a design area option and receive the results for one design area. You might correct a few of the interferences and then run interference checking with the option. Remember, the interference checker will only report new clashes, therefore, old clashes would not be reported again although they may still exist in the design area that was first checked. This step would be done by the Interference Manager. 5. Define model graphics. A set of model files for the project must be defined before you can use the .


235


Envelope Builder Piping, equipment, structural, raceway, and HVAC envelope files are created through the PDS Interference Manager module. All Architectural files will have their interference envelope files created within the Architecture product. The envelope builder command performs the following tests to detect the situation where the graphics for a model, that is not associated with the selected design area, encroaches into the volume represented by that design area:  





If the envelope file which corresponds to the model is Up-To-Date with respect to the model, the envelope builder will not re-create the envelope file. If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the model, but it has interference envelopes in the volume of the selected design area, then the envelope file for the model is re-created. If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the model and it does not have any interference envelopes which fall within the volume of the selected design area, then the envelope builder determines if the model has any components which falls in the volume of the selected design area. If so, the envelope file for that model is re-created. Log files are batch queue error reports for the envelope builder data server that contain information regarding any errors. These files have the extension .ebl and are created in the \temp directory on the server or workstation from which the process was submitted. You should review this file.

Envelope Verification The categories: 

command sorts the models being verified into one of the following

Up-To-Date: those interference envelopes that are consistent with respect to the model.



Not Up-To-Date: those interference envelopes that are inconsistent with respect to the model and may require being re-created. This is because either the model has been revised since the interference envelopes were created, or the interference envelope file is non-existent.



Not Mounted: an error occurred while mounting the file system where the model resides.

Any discrepancies found during this verification process indicate problems in the applicable Envelope Builder and will be reported in a file in the \temp directory named after the project or design area with an .evd file extension.

Envelope Diagnostics The command creates MicroStation graphics from the interference envelopes for the model, in a file named . til . This file, placed in the same directory as the model, is used to view the interference envelopes interactively through MicroStation to verify if the envelopes are correct.

236



Once an interference philosophy has been determined, select the option to run the batch . Use your choice of either the Project option or any of the design area options consistently throughout the interference checking process. The option is the largest area of the project and encompasses every model file. options process a smaller division of a project with a limited number of  The model files.  The option allows you to control the volume checked by specifying specific volume coordinates. If not used, the system determines the volume based on the volume of the envelope files in the area being checked (which can vary over the life of a project).  The toggle specifies a smaller volume of any of the options above. 

Once the Interference Manager.

has been run, you can review the clashes interactively with the

The provides a command to check interferences interactively while working in the piping design file. This option only checks one pipeline (or a group) against reference files that have a previously created envelope file. Unlike the Interference Checker, the Piping Design command does not write clash information to the database. It is intended as a quick check for the piping designer.

Interference Checker Input The following are used as input by the PDS Interference Checker:   



The data collected by the forms interface. Interference envelope files which correspond to model volumes or design areas. Information in the Project Control Database. The approval status of each known interference is stored in the Project Control Database. When an interference is approved, it is no longer included in future interference reports. This allows all interferences within a project to be resolved, either by changing the approval status of the interference to Approved or by revising the model. Information in the Material Reference Database. The following database tables can be used to exclude items from interference checking. 

The Component Insulation Exclusion Data table (PDtable_23 1) allows you to completely or partially exclude the insulation of components that are on insulated lines, during interference checking. If this table is not loaded, the insulation thickness is completely included in the component's interference envelope.



The Flange Insulation Exclusion Data table (PD_table 232) provides for partial exclusion of flange insulation thickness from the generation of interference envelopes. This is an optional data table; if no data is defined for this table the insulation thickness is completely included in the component's interference envelope.


237


Interferen ce Chec ker Output The following are generated by running the Interference Checker: 

This report contains all unapproved clashes, sorted first by model combinations then by the type of clash. For instance, all clashes detected between model A and model B are grouped together. A synopsis of the clashes is included at the beginning of the report. This report also includes the model status of any components involved in a clash for the piping, structural, HVAC, and equipment disciplines. This status is that of the model and not of the clash. These reports are named after the project or design area with an .int file extension and are created each time the checker is run. The interference report is created at the location specified with the option. The report begins with a synopsis of all clashes found during interference processing and includes a report of the clashing items within each of the design files represented in the synopsis. PDS I nter f erence Synopsi s

m p i p2 . env Number of cl ashes

= 14

Date: Mo e

’ A’ De si gn F i e Name:

PDS I nt erf erence Report 23- J un- 93

Ti me:

13: 42: 13

X Coor d

Y Coor d

Z Coor d

m p i p2

Ent i r e Desi gn Vol ume I ncl uded I n Report

PDS 3D T eory — Apri

2002 PDS I nt erf erence Cl ashes

No

I t em Name Tabl e

48

2CPI NSTRUMENT me

a e s - 6 I N- 1 C0031- 0

Har / Har Cl ashes Row 6

4194305

E 1’ 3 15/ 16" Pl ant N

2000’ 0" Pl ant

El 0’ 0" Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

El 0’ 0" Pl ant

6

4194306

E 8’

N 2000’ 0" Pl ant

E 0’ 0" Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

E 0’ 0" Pl ant

3

4194306

E 13’ 4 1/ 8" Pl ant

N 2000’ 0" Pl ant

E 0’ 0" Pl ant

"

Not appr oved 48

PI PE i c ’ c as pi pe’ - 1 I N- 1 C0031- 0 " Not appr oved

49

3CPI NSTRUMENT mebl abel s- 6I N- 1C0031- 0

4" P ant

"

Not appr oved 49

PI PE i f c’ cl ash pipe’- 1IN- 1C0031-0 " Not approve

50

238

2CPSPECI ALTY


Detecting and Managing Interferences me

a e s - 6 I N- 1 C0031- 0

"

Not approve 50

PI PE

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

El 0’ 0" Pl ant

3

4194307

E 18’ 4 1/ 4" Pl ant

N 2000’ 0" Pl ant

E 0’ 0" Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

E 0’ 0" Pl ant

3

4194309

E 26’ 8 9/ 16" Pl ant N

2000’ 0" Pl ant

E 0’ 0" Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

E 0’ 0" Pl ant

5

4194305

E 30’ 2 3/ 16" Pl ant N

2000’ 0" Pl ant

E 0’ 0" Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

E 0’ 0" Pl ant

8

4194305

E 31’ 2 3/ 16" Pl ant N

2000’ 6" Pl ant

El - 1’ 1 9/16" Pl ant

5

4194308

E 40’ 2 3/ 16" Pl ant N

1999’ 4" Pl ant

El - 6 " Pl ant

5

4194306

E 40’ 2 3/ 16" Pl ant N

1999’ 10" Pl ant

El 0’ Pl ant

0"

3

4194321

E 22’ 6 1/ 16" Pl ant N

2000’ 0" Pl ant

E 0’ Pl ant

0"

i c ’ c as pi pe’ - 1 I N- 1 C0031- 0 " Not appr oved 51

3CPSPECI ALTY me

a e s - 6 I N- 1 C0031- 0

"

Not appr oved 51


52

T me

a e s - 6 I N- 1 C0031- 0

"

Not appr oved 52


53

PI PE mebl abel s- 6I N- 1C0031- 0

"

Not approve 53


54

pi pesupport mebl abel s- 6I N- 1C0031- 0

"

Not approve 54

PI PE i c c as

pi pe- 1 I N- 1 C0031- 0

"

Not appr oved 55


55

CKS 1constr uct- 6I N- 1C0031- 0

"

Not appr oved



All interferences within the project are graphically represented by markers and are used by the . Each time the Interference Checker detects an interference within the project, a marker is written to one of the marker design files. The project marker file is created in the project directory during project creation. It is named after the project database with a .dgn extension. Area marker files can be created as each piping or equipment design area is defined in the Project Control Database.


239

Detecting and Managing Interferences The interference markers are numbered in the .int report with a system-assigned sequential number starting with 1. Any previously approved markers (interferences) will not be replaced unless the corresponding model items have been graphically modified. 

. If an error is found while running the Interference Checker, the system writes the item name and an error code in a file named after either the project or design area, depending on the option selected to run the , with an .icl file extension. Runtime errors are written to a file with a .err extension.



Each batch job creates a log file which is placed in the \temp directory. Any run time errors will be listed in these log files. The following tables are updated by Interference



Checking: A record is created each time Interference Checking is



run. 

A record is created for each clash in the project. The unique_clash_id uniquely identifies a clash. A record is created each time a clash is



encountered. A record is created for each model item



which is involved in one or more clashes. These records are used by subsequent executions of the Interference Checker and Interference Manager. 

. These files are named by the system as the marker number with the extension .plt and placed in the \temp directory (or you may use the Interference Clash Plot Manager to

specify a different node and directory). The system automatically generates the plots through the PDifc_plot queue.

Interference Manager The interference manager is used to review all interferences in a project or area and revise the approval status of a single interference marker or a group of interference markers.

Clas h Categories The Interference Manager and the reports created by the Interference Checker distinguish between three categories of interference clashes. See the graphics on the following page for examples of clashes.   

240

A clash which exists between actual physical components, equipment, or structures. A clash which e xists between non-physical space envelopes, such as, insulation, maintenance accessways, or safety envelopes. A clash or discrepancy which exists between the user-defined distance and the actual distance of two components in specified disciplines defined using PD_Project. For instance, if piping components are required to be at least 1" away from all structural components but one is found closer, a Construction clash is reported.



Clas h Precedenc e The precedence for reporting clashes is Hard, Soft, and Construction. This results in the interference clash being reported in one of the following categories. The report will contain only the category of clashes with the highest precedence in accordance with the following precedence table: Hard - Hard Hard - Soft Hard - Construction Soft - Soft Soft - Construction Construction - Construction.

Hard - Hard Examp le The following example contains clashes between actual physical components. It would be categorized as a Hard - Hard clash.


241


Hard - So ft Exam ple The following example displays a clash between an actual component and space that has been allocated for maintenance accessways. It would be categorized as a Hard - Soft clash.

The option plots clashes generally by project or design area. Within these choices, you can plot clashes by:     

The clash plot status. The clash approval status. The clash review status. The clash category. The group or individual clash selections from a list of clashes in marker file.

The clash plot files.

option defines a default node and path for future

This is a required step in the Interference Checking Process. Problems could occur later in the process if this step has not been completed.

242



The interferences report is generated automatically during interference detection with the option. You can create user-defined reports on the Project Control Data using the . Discrimination data and format files are used to generate specific types of reports, such as a list of clashes involving the structural discipline, the approval status of those clashes, and the action discipline assigned to these clashes. The interface and process for interference reporting is similar to that used in the PDS Report Manager module.


243


244


SECTION 26

Reporting Process .......................................................................... 245 Maintaining Report Definition Data .............................................. 246 Processing Reports......................................................................... 248 Report Types.................................................................................. 248 Report Format File......................................................................... 249 What Happens When I Report On a Component? ......................... 258 Material Takeoff Reporting (Report Manager).............................. 263 Understanding Implied Items......................................................... 268 Material Takeoff Options .............................................................. 270 Labels in Material Descriptions ..................................................... 273 Material Data Publisher ................................................................. 281

The following outlines the basic steps associated with the Material Take-Off process. 1. Pre-defined report data determines the discrimination data (such as which models to process) and the format (content and layout) of the report. 2. For the specified models (and using any additional discrimination data, such as line size), the system scans the physical elements in the model. 3. The system determines the number of items present in the model by unique commodity code. In addition to the physical elements, it determines any implied items based on configuration of mating components or designations in the Piping Commodity Specification Data (PCD). 4. The system looks up the material descriptions for the located components and implied items in the Material Description Library. 5. The system writes a report of the located and calculated items based on pre-defined report format. There are two main user tasks necessary for creating reports: 

Maintaining the data that defines the format, content and approval status of the reports.



Processing reports by activating the interface to extract data from all of the PDS models, databases, and libraries that are involved in a project.


245

Creating Material Takeoffs and Other Reports

The Report Manager uses both report definition files, such as discrimination data files and format files, along with database records that represent these files to generate reports. The two most important files that must be maintained in a report creation process are the discrimination data file and the format file. The discrimination data file, which defines the search criteria for a report, is maintained interactively with the Report Manager. The format file is generated outside of the interface using an ASCII text editor. There are several sample format files that are delivered with the PDS 3D products. You can use these files as examples for creating format files to meet your specific needs.

The following definitions explain all of the files and records in the reporting process.

Format File The format file is a user-defined, ASCII-text file which contains special indices identifying what data appears in the report, how the data is sorted, and how the data is formatted in the report. A set of basic format files are delivered for several types of reports. Using the option, you can create a database record for each format file so that it can be accessed for report processing. Without the format record, the Report Manager is unable to access format files.

Format Record The format record is a record in the Project Control Database used to name and locate a specific format file. It is called a record to classify it as a block of data that is used for report processing but, it is not an actual file. It is created interactively. There are five format definitions in the format record: 

— Defines a unique number to name the record with up to 24 characters in the Project Control Database. This number is a short name to identify the record of the format file. — Describes the format file with up to 40 characters in the Project Control



Database.   

246

— Defines the file name of the ASCII format file. The system verifies that the file does not already have a record in the project. — Defines the disk location of the format file. This field retains the active setting. — Defines the nodename where the format file is located. This field retains the active setting.



Dis crimina tion Data File The discrimination data file defines the search criteria which is used to limit the report to only the specified database occurrences. It is an ASCII file that is created interactively using the Report Manager. You also create a uniquely-numbered record for each discrimination data file so that it can be accessed for report processing.

Discrimination Data Record The discrimination data record is a record in the Project Control Database used to name and locate a specific discrimination data file. It is called a record to classify it as a block of data that is used for report processing but is not an actual file. It is created using the Report Manager. There are five discrimination data definitions in the discrimination data record: 



— Defines a unique number to name the record with up to 24 characters in the Project Control Database. This number is a short name to identify the record of the discrimination data file. — Describes the discrimination data file with up to 40 characters in the Project Control Database. — Defines the file name of the discrimination data file to reference. The



system verifies that the file does not alr eady have a r ecord in the pr oject.  

— Defines the disk location of the discrimination data file. This field retains the active setting. — Defines the nodename where the discrimination data file is located. This field retains the active setting.

Report Record The report record defines locations for all of the files that are necessary to generate a report, including the report output. (It is called a record to classify it as a block of data that is used for report processing but is not an actual file.) It is created using the Report Manager. There are seven report definitions in the report record: 

— Creates a unique report number in the Project Control Database that acts as a name or identifier for a report record.



— Describes the report file. It is not the title in the actual report. That title is specified in the format file. — Defines the file name of the report output file. Each time a file is regenerated using the same report file, the report output file is overwritten. Change this field to save the old report output file and generate a new one.



  

— Defines the directory for the report output file. — Specifies the nodename for the report output file. — Specifies the record number that contains the address of the report format file to be used. — Specifies the record number that contains the address of the discrimination data to be used.


247


Repo rt Output The Report Manager creates a report using the specified format and discrimination data files and places it in the directory specified.

Since there are reporting capabilities in various PDS modules, the format file, the discrimination data file and the module where the report process is activated determine what type of report is created. For instance, you can create MTO reports with and Drawing reports with the report manager module of . Depending on the definition data used and the module that executes the process, you can create MTO reports, drawing reports, spec reports, table checker reports, project reports, or interference reports. The following section describes the various report types, how they are generated, and their corresponding sample format files:

Various modules in the PDS Suite generate reports. The following section describes the various report types, how they are generated, and their corresponding sample format files:

248



— Generates reports on PDS piping and equipment models involving data from the Design Database, Reference Database, Project Database, and Material Description Libraries. This type of report will also include implied mating data, such as bolts, gaskets, and welds by determining the connectivity of the piping and equipment. Format files used in this type of report primarily use A and B prefixed indices. This report is generated using the



— Generates reports on PDS Piping and Equipment drawing views and drawing files. This report is the same type of report as the MTO report generated by the . Format files used in this type of report primarily use A and B prefixed indices. This report is generated using the .



— Generates reports on the Reference Database and Material Description Libraries. The spec report is used to report on data in the reference database. Format files used to create this type of report primarily use C prefixed indices. This report is generated by the .



— Generates reports on the Reference Database and Material Description Libraries. The table checker report is used to test Eden modules and tables that would be executed by the Piping Commodity items within the Reference Database. Format files used to create this type of report primarily use C prefixed indices. This report is generated by the .


Creating Material Takeoffs and Other Reports 

— Generates reports on the Project Control Database. Format files used in this type of report primarily use D prefixed indices. This report is generated using the .



— Generates reports on the project control database. clash area, clash type, and clash approval along with the search criteria specified in the discrimination data define what interference data is reported. Format files used in this type of report primarily use D prefixed indices. This report is generated using the .

The reporting process is driven by a format file that determines the contents and format of the report. It must be created with a text editor prior to report processing. The format file is a standard ASCII file which contains all the needed criteria for creating the actual report, such as text position, special indices for input into the report, and sorting instructions for the indices.

The format file is based on fields . A field contains a complete description of a given piece of data to be placed in an ASCII report file. Each line of the format file contains the entire description of one field. All fields are independent of each other; if they have a common order in the report, you are responsible for placing these fields in such a way that the orders match in the report. In other words, you are responsible for defining your format file in such a way that your columns and headings will fall under one another. Each line in the format file can contain the following data: Fi el d _Funct i on, Row, Col , Fi el d _Len, Dat a _Type, Fi el d _Type, [ Buf f er ] , [ Rows/ Page] , [ Spaci ng]

(Brackets [] indicate data that is only used for certain field types; all other data is required in every field type.)

Syntax Example


249


Field_Function   

0 Null Field — Used to send a data field (index) to sort on an unreported item. 1 Page Field - All Pages — Places the specified field once on every page of the report. 2 Page Field - First Page Only — Places the specified field once on the first page of the report.

3 Page Field - Last Page Only — Places the specified field once on the last page of the report.  4 Output Field — Places the specified field a variable number of times on every page of the report based on rows/page and spacing.  5 New Page Marker — Forces a new page (form feed) after all the previous statements have been processed. All the lines in the format file after this marker are placed on a new (repeated) page. In other words, this enables you to append a complete format file to the previous format file and use the same data sources and sorting as the previous lines of the format file.  6 Continuous Page Marker — Forces everything after this marker in the format file up to a New Page Marker or the end of file to be continuously output as one page. The specified fields are continuously output without any page divisions. (This code overrides the value for Rows/Page) 

This function can be used to generate an intermediate data file in a fixed form that contains only raw data (without headings and other annotation). This output can then be used as input to your own report generation software. 

  

250

7 Turn On Output Field Appending Control — Forces all output fields after this marker in the format file to begin after the previous output field (above 7) is completed, that is, all output fields will initially begin at the last output fields finishing row. 8 Turn Off Output Field Appending Control — If7 is in effect for an output field this code will turn the effect off making output fields normal. 9 Start of output field loop 10 End of output field loop — Repeats all output fields defined between codes 9 and 10 until out of data or the maximum number of lines per output field has been exceeded by the number of lines of data between the 9 and 10 codes. These options are used to prevent control sorts from breaking to a new page by using the remaining space on the page before proceeding to a new page.



Row Starting line number to be used in placing the field in the report. The maximum number of rows in a report is 66.

Col Starting column number to be used in placing the field within the specified row. The maximum number of columns in a report is 132.

Field_Len The maximum number of characters that a field can occupy for the active row. The starting column plus the field length must not exceed 132. A negative value will truncate a field rather than wrap around a field (default). If the text being placed in the field exceeds the field length, the text is continued on the next row indented one space (col + 1) until it is completed or the page ends.

Data_Type Code used to determine the type of translation required to convert the data to text. (Refer to the index listings to determine the applicable data type for a particular attribute.)      

1 character or '[Am]', where m is the number of characters 2 single precision integer or '[Im]' 3 double precision integer or '[Im]' where m is the number of characters for the integer field 4 single precision decimal (float) or '[Fm.n]' 5 double precision decimal (float) or '[Fm.n]' where m is the total number of characters for the decimal value including the decimal point and n is the number of decimal places

Optional text can precede and/or follow the formatted data type within the quotation marks. ' opt i onal t ext [ For mat ] opt i onal t ext '

[Format] can be any legal FORTRAN format statement that matches an expected output.


251


Field_Type 1. 1 Text Field. Sets the buffer for hard-coded text. 2. 2 Data Field. Sets the buffer for an index number or code used to generate the data to be placed in the field. 3. 3 Generate Date/Time. No buffer required. When the report is generated, the system date and time is placed at the designated row/col position. 4. 4 Generate Page Number. No buffer required. When the report is generated, the system calculates the page number and places the number at the designated row/col position. 5. 5 Generate Date. No buffer required. When the report is generated, the system date is placed at the designated row/col position. A negative value will underline the generated output for the field. (This causes the report to be in a stream line feed file, rather than a stream carriage return file. This may impact an existing interface to a material control system.)

[Buffer] = Field Definition The form of the buffer depends on the value for Field_Type. 

Hard coded text is enclosed in single quotes (').



For MTO reporting, the first character of the index is always A or B. Refer to the description of the indices for MTO Reporting (with implied materials) . For spec reporting, the first character of the index is always C. Refer to the description of the indices for Spec Reporting . These indices are also used for the Table Checker. For project and interference reporting, the first character of the index is always D. Refer to the description of the indices for Project and Interference Reporting .

 

[Rows/Page] This setting is only required for output fields. It indicates the number of vertical spaces (lines) in which to repeat the field contents on a given page. For example, a setting of 20 reserves 20 lines starting from a given row for use in placing the field contents (dependent on spacing). This does not take into account the extended fields due to exceeded field length. This is NOT the total number of times that the field is repeated (that value is based on number of occurrences for the specified attribute); it is only the vertical space allotted for repeating the field on a page.

252



[Spacing] This setting is only required for output fields. It indicates how much space (in rows) is allowable between repeated fields. This is useful for reserving space for extended fields due to exceeded field length. (Rows/Page)/Spacing = the number of times an output field can appear on a page. For example, if Rows/Page=40 and Spacing = 2, 20 occurrences of the specified attribute are placed on a page (until the number of occurrences is reached).

Option al Rep ort Type Line There is an optional line that will determine the type of report the format record creates. It must be the first line of the format file when used. This line contains an integer variable that corresponds to a name in the standard note type 1720 in the Standard Note Library. You can modify the standard note type 1720 to add report types. For instance, the following line would define the report type as Piping Components MTO Report:

Most report formats involve reporting multiple variables for a given component. This is accomplished by using output fields (Field_Type = 2) with the necessary index numbers. Each field is processed independently of the other fields on the report; there are no safeguards to assure that information in different fields corresponds to the same item. Therefore, you are responsible for placing these fields in such a way that the orders match in the report. To ensure that items match, you should make sure that the same number of common items are reported on each page. The Rows/Page divided by the Spacing determines the number of times an output field can appear on a page. Therefore, all the common fields should use identical settings for Rows/Page and Spacing. The S pacing enables you to reserve space for extended fields due to exceeded field length. For example, if you use a Field length of 20 for a field which may be up to 50 characters long, you should set the spacing at 3 to leave adequate space for any If there is no data for the specified output field(s) on a page, that page will not be printed.


253


Different format files are used by the system to generated specific types of reports. The following sections explain all of the delivered sample format files, their delivery locations, and what type of report they generate. In some instances, report output is also included.

Sa mp le MTO Rep ort Forma t Files The following files are provided in the product delivery in win32app\ingr\pdreport\sample directory. 

— This report format includes piping segment data. It demonstrates 'control' sorting and output field 'looping' (field functions 9 and 10). This report format reports a list of piping segments grouped by the Model Builder's alphanumeric description id. The report includes all piping lines that are associated with a specific Model Builder alphanumeric input file. (report type = 687)



— This report format includes data for piping components, pipes, instrument components, gaskets, bolts, nuts, and welds. It demonstrates the use of 'standard' output fields. This report includes each category of data in a fixed area of a repeated report page using 'normal sorting' and 'standard output fields' (field function 4). (report type = 689)



— This report format includes data for piping components, pipes, instrument components, gaskets, bolts, nuts, and welds. It demonstrates the technique for grouping blocks of output fields on the same page of the report. This report format reports data similar to 'piping_a.fmt'. It differs only in that it demonstrates another method to format the data on the repeated page of the report. (report type = 689)



— This report format includes data for piping components, pipes, instrument components, gaskets, bolts, nuts, welds, pipe supports, implied piping components, equipment, and nozzles. It demonstrates the use of different pages of output within one report. This report format reports data similar to 'piping_b.fmt' with the addition of pipe_supports, implied piping components, equipment, and nozzles. It uses 'page break markers' (field function 5) to break each category of data onto a different repeated page of the report. (report type = 689)



— This report format reports the material descriptions for piping components, pipes, instrument components, pipe supports, gaskets, and bolts. This report format uses identical report indices to create two columns to continue data on the same report page. It also uses page breaks to separate the different categories of data onto different repeated pages of the report.

254


Creating Material Takeoffs and Other Reports (report type = 689) 

— This report format reports data similar to 'piping_c.fmt', but without any equipment and nozzle data. This report format uses a 'continuous page marker' (field function 6) to create a report with no page boundaries and continuous output (typically used for creating a neutral file format). It also demonstrates the use of report indices to create a summary of standard notes used in the report. report type = 689)



— This report format includes data for piping components, pipes, instrument components, gaskets, bolts, and pipe supports similar to 'piping_e.fmt'. Each category of data is grouped (using 'global control sorting') under a common line number label for each page of output. It uses 'output field appending' (field functions 7 and 8) to have the different categories of data reported on the same page and column of output. (report type = 689)



— This report format includes data for piping components, pipes, instrument components, gaskets, bolts, and pipe supports similar to 'piping_f.fmt' with the same line number grouping. This report format uses 'output field looping' (field functions 9 and 10) to utilize all of the report page space available. The report includes a line number followed by all components that are associated with that line number label with one or more line number labels being reported per page, depending upon the amount of data and the space available. (report type = 689)



— This report format includes weight and center of gravity data for piping components, pipes, instrument components, gaskets, bolts, pipe supports, implied piping components, and equipment. The output is similar in format to 'piping_e.fmt' and demonstrates the weight and cog calculation reporting indices. (report type = 689)



— This report format reports equipment data (including location data) and nozzle data (including location and orientation data). It demonstrates the full range of equipment and nozzle reporting indices. (report type = 661)



— This format reports weld information, such as the weld number, type and the first and second connect point NPD.



— This format reports project information such as the client and project location and uses information from the Drawing Management Data table and the Drawing Revision Data table for reporting.


255


Sa mp le Sp ec Rep ort Forma t Files The following files are provided in the product delivered in the win32app\pddata\sample\format directory. 

piping_rdb.fmt — This report format includes piping material class data and piping commodity data from the Material Reference Database. It reports the 'partial' (without embedded commodity code labels) material descriptions. (report type = 601)



tbl_chk_1.fmt — This report format includes Table Checker data for one piping material class. It reports the piping commodities with the dimension tables and Piping Eden modules used, including a list of all entries read in the dimension tables. This report also includes a list of all dimension tables and Piping Eden modules that were required for those piping commodities, but not available in the Reference Database. This report format is a combination of the following report formats tbl_chk_2.fmt, tblk_chk_3.fmt, and tbl_chk_4.fmt. It provides full Table Checker output for a specific piping materials class. (report type = 601)



tbl_chk_2.fmt — This report format includes Table Checker data for one piping material class. It reports the dimension tables and Piping Eden modules used by each piping commodity in that piping materials class. (report type = 601)



tbl_chk_3.fmt — This report format includes Table Checker data for one piping material class. It lists all entries read in dimension tables. (report type = 601)



tbl_chk_4.fmt — This report format includes Table Checker data for one piping material class. It includes a list of all dimension tables and Piping Eden modules used by the piping commodities in that piping materials class. This report also includes a list of all dimension tables and Piping Eden modules that were required for those piping commodities, but not available in the Reference Database. (report type = 601)

256



Sa mp le P rojec t Control Repo rt Forma t Files The following examples are delivered in the win32app\pdprojec\sample directory. 

— This format file reports model management data.



— This format file reports orthographic drawing management data. — This format file reports isometric drawing management data.



— This format file reports isometric drawing revision management data.



Sample Interference Report Format File The following example is delivered in the win32app\pdclash\sample directory. 

— This format file reports interference checker data.

Sa mp le P&ID Cons is ten cy Chec k Rep ort Forma t File The following example is delivered in the win32app\pddesign\sample directory. 

— This format file specifies the format of the title page and heading for each page of the P&ID Consistency Check reports. The remainder of the report is predefined by the product.


257


When you place a component the system writes the engineering data for the component to the design database. For the gate valve placed in Chapter 4, the system writes information to the Piping Segment Data table and the Piping Component Data table. When you create a Material Take-Off (MTO) report using the Report Manager the system will use this data and information in the project reference data for reporting.

In addition to the engineering data in the design database, PDS 3D uses the Material Description Library and the material data in the Material Reference Database to provide material descriptions for commodity items and specialty items.

The material description data is made up of four major parts: 1.

- These database tables (211 and 212) contain commodity definitions which enable you to further classify the commodity items defined in the Piping Job Specification. This database information tends to be customer-specific.  Piping Commodity Size-Dependent Material Data (211) The Size-Dependent Data table contains the data for a specific commodity item that is dependent on the commodity code, nominal piping diameter, and schedule/thickness. It

258


Creating Material Takeoffs and Other Reports is used for miscellaneous reporting and interfaces to material control, stress analysis, and isometric drawing extraction. 

Piping Commodity Implied Material Data (212) The Implied Material Data table contains the implied material data for a specific commodity item that is dependent on both the commodity code and nominal piping diameter range. This data is used for generating implied materials for MTO reporting and material control. It is not used for welds, bolts, nuts, or gaskets, but is reserved for other types of implied material, such as caps or stubs, for a specific commodity item. It is also used for reporting the implied components of a commodity item (such as cap screws).

2.

- This library contains the short bill-of-material (BOM) descriptions for all piping commodity items and the description addenda for taps. The short material descriptions can be up to 240 characters in length. 3. - This library contains the long bill-of-material descriptions for all piping commodity items. The long material descriptions can be up to 500 characters in length. 4. - This Library contains the material descriptions for any piping specialties, in-line instruments, or pipe supports which are reported by MTO or material control. These material descriptions are job specific and are accessed by the specialty item's tag number. The specialty material descriptions can be up to 240 characters in length. The material description data in these files is used for reporting and material control and is not required for the interactive placement of symbols in the model. This data is normally accessed during a batch (non-interactive) process.


259


The system uses the commodity code as an index to access the descriptions in the material description libraries. You can use the commodity code defined in the Piping Commodity Specification Data table (Table 202 attribute 18) or a user-defined commodity code defined in the Size-Dependent Material Data table (Table 211 attribute 7).

The source of the commodity code and other processing options for reporting are defined for a model with the form of the . The commodity code represents that set of parameters that completely describe a commodity item, exclusive of nominal piping diameter and thickness. The character length for the commodity code is determined from the character length of the commodity code in the Size Dependent Data table of the database, or from the character length of the commodity code in the Piping Commodity Data table of the database, depending on which is being used to access the material descriptions. The delivered commodity codes use a 10 character code to fully identify the item. The first letter of the commodity code identifies the basic type of component, such as a valve or flange. The remaining characters provide a detailed description of the component. The first character designations are:

260

B

Flanged and Misc. Fittings

Q

Socket End Fittings

D

Fire and Safety Components

R

Tubing Fittings

E

Steam Specialties

S

Socketwelded Fittings


Creating Material Takeoffs and Other Reports F

Flanges

T

Threaded Fittings

G

Flanged Specialties

U

Underground Fittings

H

Strainers

V

Valves

M

Misc. Wetted Components

W

Welded Fittings

N

Misc. Non-Wetted Components

X

Gaskets

O

Tubing and Hose

Y

Bolting

P

Pipe

Refer to the PDS Piping Component Data Reference Guide for a complete listing of the delivered commodity codes. You can use the delivered commodity codes or create your own naming scheme. Regardless of the scheme used, all the codes must be unique and there must be an exact match between the commodity code specified for an item in the Material Reference Database and commodity codes used to define the material descriptions in the Material Description Library.


261


When the system creates a bill of materials for the elements in a model it lists both the items physically defined in the model and any implied items which are associated with the physical items. Implied materials can be defined in any of the following ways. 

Mating Implied Data (gaskets, bolts, and welds) During reporting, the system scans the components and their relationship to determine any mating implied material. The system uses a set of rules to determine the implied materials based on the end conditions of mating components. These rules are described in detail in the Report Manager (PD_Report) Reference Guide . Item definitions for mating implication such as bolts and gaskets are defined in the Piping Commodity Specification Data Table (pdtable_202) of the Specification/Material Reference Database.



Spec Implied Data An asterisk(*) in front of a commodity code in the Piping Commodity Specification Data (PCD) indicates that there is another line item in the PCD for the implied component. For example, a lap joint flange and stub end. The lap joint flange is placed in the model but the stub end is not. However, the stub end will show up in reports. This is a Parent/Child relationship with a one-to-one relation. Parent = option number Child = 5000 + parent option number



Table 212 Implied Data A plus (+) in front of a commodity code in the PCD tells the software to look in table 212 for that commodity code. This method indicates a primary component which has one or more associated implied components. This is a Parent/Child relationship with a one-to-many relation.



262

Commodity codes with neither an * or a + prefix in the PCD, indicate a commodity item that has no associated implied components.



The following is a sample report using the format file piping_a.fmt . It reports on a very simple pipeline containing the component examples covered in Chapter 4 and the connecting pipes.

Material Takeoff reporting (with implied materials) generates reports on PDS piping and equipment models involving data from the Design Database, Reference Database, Project Database, and Material Description Libraries. This type of report also includes implied mating data, such as bolts, gaskets, and welds by determining the connectivity of the piping and equipment. Format files used in this type of report primarily use A and B prefixed indices. This report is generated using The active Piping Materials Class must be defined for a model for MTO processing to work. Before creating an MTO report for a model or set of models, the Piping Materials Class should be set in the active segment data for each model and the setting should be saved with File Design.


263

Creating Material Takeoffs and Other Reports The sample format files for creating MTO reports are: segment.fmt, piping_a.fmt through piping_g.fmt, weight.fmt, equip_a.fmt, and weldno.fmt and are delivered in the win32app\pdreport\sample directory.

r epor t _t ype=689 ! Pi pi ng Component s MTO Repor t 1, 1, 1, - 13, 1, 1, ’ Dat e/ Ti me : ’ 1, 1, 14, - 23, 1, 5 1, 1, 50, - 40, 1, 1, ’ PDS MTO REPORT’ 1, 1, 120, - 6, 1, 1, ’ Page: ’ 1, 1, 127, - 3, 2, 4 2, 3, 10, - 40, 1, 1, ’ Cor por at e Headquar t er s’ 2, 4, 10, - 40, 1, 1, ’ I nt er gr aph Cor por at i on’ 2, 5, 10, - 40, 1, 1, ’ Hunt svi l l e, Al abama 35894- 0001’ 2, 6, 10, - 40, 1, 1, ’ ( 205) 730- 2000’ 2, 3, 90, - 20, 1, 2, B**Q5 2, 3, 110, - 20, 1, 2, B**Q9 2, 4, 90, - 20, 1, 2, B**Q6 2, 5, 90, - 20, 1, 2, B**Q7 2, 6, 90, - 20, 1, 2, B**Q8 1, 8, 1, - 25, 1, - 1, ’ Commodi t y Code’ 1, 8, 27, - 16, 1, - 1, ’ Qt y/ Lengt h’ 1, 8, 45, - 10, 1, - 1, ’ 1s t Si z e’ 1, 8, 57, - 10, 1, - 1, ’ 2nd Si z e’ 1, 8, 69, - 63, 1, - 1, ’ Mat er i al Des cr i pt i on’ 9 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, BI 2G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, BB2G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, B*I 2G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, BT1G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, BX1G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, B** K2G1, 45, 2 7 4, 10, 55, - 50, ’ LI NE NUMBER: [ A30] ’ , - 2, B*S2G1, 45, 2 8 4, 12, 1, - 25, 1, 2, BG8S2, 45, 2 4, 12, 27, - 16, 2, 2, BS, 45, 2 4, 12, 45, - 10, 1, 2, BN49S3, 45, 2 4, 12, 57, - 10, 1, 2, BN- 49S4, 45, 2 4, 12, 69, 63, 1, 2, BM1S5, 45, 2 7 4, 12, 1, - 25, 1, 2, BA12S2, 45, 2 4, 12, 27, - 16, 1, 2, BA22, 45, 2 4, 12, 45, - 10, 1, 2, BA7S3, 45, 2 4, 12, 69, 63, 1, 2, BF1S4, 45, 2 7 4, 12, 1, - 25, 1, 2, B*G2S2, 45, 2 4, 12, 27, - 16, 2, 2, B*O, 45, 2

264


Creating Material Takeoffs and Other Reports 4, 12, 45, - 10, 1, 2, B*L55S3, 45, 2 4, 12, 57, - 10, 1, 2, B*L- 55S4, 45, 2 4, 12, 69, 63, 1, 2, B*K1S5, 45, 2 7 4, 12, 1, - 25, 1, 2, BT13S2, 45, 2 4, 12, 27, - 16, 2, 2, BV, 45, 2 4, 12, 45, - 10, 1, 2, BT2S3, 45, 2 4, 12, 57, - 10, 1, 2, BT23, 45, 2 4, 12, 69, 63, 1, 2, BT21S4, 45, 2 7 4, 12, 1, - 25, 1, 2, BX12S2, 45, 2 4, 12, 27, - 16, 2, 2, BZ, 45, 2 4, 12, 45, - 10, 1, 2, BX4S3, 45, 2 4, 12, 57, - 10, 1, 2, BX5S4, 45, 2 4, 12, 69, 63, 1, 2, BX20S5, 45, 2 7 4, 12, 1, - 25, 1, 2, B**J 7S2, 45, 2 4, 12, 27, - 16, 1, 2, B**O, 45, 2 4, 12, 69, 63, 1, 2, B** M1S3, 45, 2 7 4, 12, 1, - 25, 1, 2, B*P12S2, 45, 2 4, 12, 27, - 16, 2, 2, B*R, 45, 2 4, 12, 45, - 10, 1, 2, B*S11S3, 45, 2 4, 12, 69, 63, 1, 2, B*U1S4, 45, 2 10 5 1, 3, 1, - 13, 1, 1, ’ Dat e/ Ti me : ’ 1, 3, 14, - 23, 1, 5 1, 3, 50, - 40, 1, 1, ’ PDS MTO REPORT’ 1, 3, 120, - 6, 1, 1, ’ Page: ’ 1, 3, 127, - 3, 2, 4 1, 11, 1, - 34, 1, - 1, ’ GRAND TOTALS’ 1, 13, 1, - 15, 1, - 1, ’ Component s’ 1, 13, 20, - 15, 1, - 1, ’ Pi pes ’ 1, 13, 40, - 15, 1, - 1, ’ I nst r ument s’ 1, 13, 60, - 15, 1, - 1, ’ Gasket s’ 1, 13, 80, - 15, 1, - 1, ’ Bol t s ’ 1, 13, 100, - 15, 1, - 1, ’ Pi pe Suppor t s’ 1, 14, 1, - 15, 2, 2, BST 1, 14, 20, - 15, 2, 2, BRT 1, 14, 40, - 15, 2, 2, B*OT 1, 14, 60, - 15, 2, 2, BVT 1, 14, 80, - 15, 2, 2, BZT 1, 14, 100, - 15, 2, 2, B*RT


265


Date/ Ti me : 15-Apr93 Corporat e Headquart ers I ntergraph Corporat i on

PDS MTO REPORT

Page: 1 PDS Proj ect t c pr o j t c101

Hunt svi

e,

A a ama

35894-0001

RoXXon Corp.

205 730- 2000 Commodi t y Code

Nt Qt y/ Length

1st Si ze

2nd Si ze

Proj ect or

Mater i al Descr i pti on

LI NE NUMBER: P403-1/ 2I N- 1C0031-N

PDS 3D Theor y — Apr i l 2002 POCAAAOAAE

1

1/ 2I N

1/ 2I N

PPCAAAOAAE

1

1/ 2I N

1/ 2I N

VAUHAHGAAA

2

1/ 2I N

1/ 2I N

Ni pp e, PE, S- 160, 3" ong, ASTMA106- B Ni ppl e, PE, S- 160, 6" l ong, ASTMA106- B Gat e va ve, CL800, SWE/ FTE, BB, OS&Y, ASTM- A105, t r i m 8, Smi t h 800

LI NE NUMBER: P403-3/ 4I N- 1C0031-N POCAAAOAAE

9

3/ 4I N

3/ 4I N

TPAZVZZAAA

7

3/ 4I N

-

VAUHAHGAAA

9

3/ 4I N

3/ 4I N

Gat e val ve, CL800, SWE/ FTE, BB, OS&Y, ASTM- A105, t r i m 8, Smi t h 800

38- PI - 6

1

3/4I N

3/4I N

*

39- PI - 9

1

3/4I N

3/4I N

*

FAAABAWAAA

2

3I N

LI NE NUMBER: P403- 3I N1C0031- N 3I N

XDAABZZQSG

1

3"

-

4

5/ 8"

3

1

4I N


FAAABAWAAA

6

4I N

4I N

VAABAHCCAA

1

4I N

4I N

YZZZHZZFFF

3/ 4"

Ni pp e, PE, S- 160, 3" ong, ASTMA106- B P ug, MTE, ASTM- A105, ANSI - B16. 11

F ange, CL150, RFFE/ BE, ASTM- A105, ANSI - B16. 5, WN, SSTD bor e Gasket , CL150, G653, 0. 125" t hk, 304 spi r al wnd, gr a ph f i l l ed, CS cent er r i ng, API 601 B31, ASTM- A193- B7 st u s w/ ASTMA194- 2H hvy hex nut s

* F ange, CL150, RFFE/ BE, ASTM- A105, ANSI - B16. 5, WN, SSTD bor e

47 VBABAHCFAA

1

4I N

4I N

G o e va ve, CL150, RFFE, BB, OS&Y, ASTM- A216-WCB, t r i m 8, Crane 143

WAAAAAWAAA

2

4I N

4I N

WRBAAAWAAA

2

4I N

3I N

90 eg LR e ow, S- STD, BE, ASTM- A234- WPB, ANSI B16. 9 Eccent r i c r e ucer, S- STD x S- STD or e, BE, ASTM- A234WPB, ANSI - B16. 9

WTAAAAWAAA

1

4I N

4I N

1s t Si z e

PDS MTO REPORT 2n Si z e

Date/ Ti me : 15-Apr93 Commo i t y Co e

Qt y / L engt

Tee, S- STD, BE, ASTM- A234- WPB, ANSI B16. 9 Page: 2 Mat e r i a

Des c r i pt i on

LI NE NUMBER: P403- 4I N1C0031- N

266


Creating Material Takeoffs and Other Reports PAAAAAWAAA

4’

XDAABZZQSG

4

4"

-

YZZZHZZFFF

32

5/ 8"

3

1

4I N

supp2

8

9/ 16"

4I N

Pi pe, S- STD, BE, ASTM- A53- B Type S

3/ 4"

FAAABAWAAA

11

6I N


FGPBBAWAAA

2

6I N

6I N

GJ GABZZADA

1

6I N

6I N

VAABAHCCAA

4

6I N

6I N

Gas et, CL150, G653, 0.125" t , gr a ph f i l l ed, CS cent er r i ng, API 601 B31, ASTM- A193- B7 st u s w/ ASTMA194- 2H hvy hex nut s *

304

spi ra

wn ,

Fl ange, CL150, RFFE/ BE, ASTM- A105, ANSI - B16. 5, WN, SSTD bor e Or i i ce ange, CL300, RFFE/ BE, ASTM- A105, ANSI B16. 36, WN, one 0. 5" SWE t ap, S- STD bor e Spect ac e an , CL150, RFTBE, ASTM- A516-70, API 590Z1, 0. 75 t

47 VCABAHOBAA

2

6I N

6I N

Check val ve, CL150, RFFE, BC, swi ng, ASTM- A216- WCB, t r i m 8, Paci f i c 180

WAAAAAWAAA

9

6I N

6I N

WADAAAWAAA

1

6I N

6I N

WOAAAAWAFA

1

6I N

4I N

WOBSABQAFA

4

6I N

3/ 4I N

90 eg LR e ow, B16. 9 45 deg LR el bow, B16. 9 We o et , S- STD x A105 Soc o et , CL3000,

WRAAAAWAAA

4

6I N

4I N

Concent r i c r educer , S- STD x S- STD bor e, BE, ASTMA234- WPB, ANSI - B16. 9

WTAAAAWAAA

3

6I N

6I N

PAAAAAWAAA

6I N

XDAABZZQSG

131’ 1 3/16" 12

Tee, S- STD, BE, ASTM- A234- WPB, ANSI B16. 9 Pi pe, S- STD, BE, ASTM- A53- B Type S

6"

-

XDABBZZQSG

1

6"

-

YZZZHZZFFF

80

3/ 4"

4"

YZZZHZZFFF

20

3/ 4"

5"

1

6I N

Gas et, CL150, G653, 0.125" t , gr a ph f i l l ed, CS cent er r i ng, API 601 Gas et, CL300, G653, 0.125" t , gr a ph f i l l ed, CS cent er r i ng, API 601 B31, ASTM- A193- B7 st uds w/ ASTMA194- 2H hvy hex nut s B31, ASTM- A193- B7 st u s w/ ASTMA194- 2H hvy hex nut s *

supp1 Date/ Ti me : 15-Apr93 Commo i t y Co e

Qt y / L engt

1s t Si z e

PDS MTO REPORT 2n Si z e

S- STD, BE, ASTM- A234- WPB, ANSI S- STD, BE, ASTM- A234- WPB, ANSI S- STD, BE, ASTMBE/ SWE, ASTM- A105

304

spi ra

wn ,

304

spi ra

wn ,

Page: 3 Mat e r i a

Des c r i pt i on

LI NE NUMBER: P403- 6I N1C0031- N supp3

1

6I N

Date/ Ti me : 15-Apr93 GRAND TOTALS Components Pi pes 8719


* PDS MTO REPORT

I nst r ument s 2

Page: 4

Gaskets

Bol t s

Pi pe Support s

18

136

3

267


This section discusses the various types of implied items and a few miscellaneous items and how they are reported. It also covers some of the features within the PDS suite of products that are outside of the module. When reporting on components, there are sometimes additional parts necessary to complete that component that are not represented graphically in the piping model or stored in the Piping Design database. These additional components are mating, spec, or table implied items. If an implied item is part of an implied connection, it is called a mating implied item. Otherwise, the naming conventions for implied items are defined by the location where the implied item data is retrieved. The system retrieves these implied items from either the Piping Component Specification Data Table (pdtable_202) or from Piping Commodity Implied Material Data Table (pdtable_212). The following sections explain the mating, spec, and table implied items and how data is retrieved for each:

Mating implied items are found by the system while scanning related mating components and defining the items necessary to complete those connections. The following items termed mating implied .  

Bolts Gaskets

Nuts  Welds 

The form is part of the Pr oject Administrator module, and its setting greatly affect the way mating implied items are reported. For more information on mating implied item reporting see the Material Takeoff Options section.

Commodity codes prefixed by an '*' in Material Description Code field in the Piping Job Specification indicate a primary component that has one associated spec implied item. 



The definition of the spec implied item has the same search parameters as the primary component, except in the following instances: 

The value for the option attribute of the spec implied component is equal to 5000 plus the option value for the primary component.



The definition of the spec implied component can be divided into several NPD ranges.

The output parameters of the spec implied component may differ from those of the primary component in the following instances: 

268

Only the primary component is included in the model depiction; the spec implied component only appears in reports. Plant Design System 3D Theory

Creating Material Takeoffs and Other Reports  

Only the primary component is displayed on an isometric drawing; the spec implied component only appears in the materials list.

The commodity codes prefixed by an '*' are used to define: 

Stub-ends used in conjunction with lap, slip-on, and plate flanges.



Jacketed components when the outer jackets are obtained independently of the internal components.

Both the primary component and the implied item in the following Piping Job Specification example would be reported: ! AABBCC

————Gr een CP———– ————Red CP————- Commodi t y ! Code Opt From To Pr p Rat i ng Sc/ Th TS Fr om To

Nt e l ng PI PI NG 1 2 PI PI NG 5001 2

6 6

301 301 -

Model Geo Mat Wt FF Pr p Rat i ng Sc/ Th TS code

S- STD 5 - - - - - - *PAAAAAWAAA S- STD 5 - - - - - - newcommcode -

PI PE PI PE

TMx Code St d Mod Gr d Cd FC

100 100 142 52 15 - 240 100 100 142 52 15 - -

Commodity codes prefixed by a '+' in the Commodity Code field in the Piping Job Specification indicate the primary component has one or more associated table implied items. The system searches for the definition of the implied item in the Piping Commodity Implied Material Data (pdtable_212), which contains the commodity code of the primary component, the applicable NPD range, and the commodity code of the table implied components. To use this option, pdtable_212 must be loaded. 



The output parameters of the table implied item may differ from those of the primary component in the following situations: 

If only the primary component is included in the model depiction, the table implied items appear only in the report.



If the primary component is displayed on an isometric drawing, The materials list only includes the short description of the primary component. The descriptions of the table implied items are displayed as notes on the drawing, pointing to the primary component. The text for these notes is derived from the short descriptions of the applicable commodity codes. The short description can contain $ symbols to force the text to a new line in the label.

The commodity codes prefixed by a '+' are used to define the following items: – 

Cap screws for valves requiring caps.



Safety covers for required components.



Housings for required components.


269


'+' Ta ble Imp lied Exam ple First, notice the '+' indicating a table implied item in a line taken from the Piping Job Specification. 24 21 CL150 NREQD 5 FWN 35 - 150 52 15 -

6Q2C01 1 3 +FAAABAWAAA -

-

421 CL150 MATCH 5

Secondly, notice the table entries that are related to the primary component, F

! I mpl i ed dat a f or t abl e

212

Sequence= 2

7

Si ng e_Spaci ng

! Comm Co e

3

4

5

6

8

9

10

GFr GTo RFr RTo I mp Co e Qt y FC Not e

! FAAABAWAAA

2

0

0

I MPFLG2A

1. 5

7

-

0

0

I MPFLG2B

0. 5

7

-

0

0

I MPFLG2C

1. 0

7

-

2

1 2 1 2 1 2 2

FAAABAWAAA

2

FAAABAWAAA

2

VAABAHCCAA

0

0

I MPVAL2A

0. 5

7

-

VAABAHCCAA

2

2

0

0

I MPVAL2B

2. 5

7

-

PAAAAAWAAA

2

2

0

0

I MPPI P2 1. 0

7

-

WAAAAAWAAA

2

2

0

0

I MPELB2 2. 0

7

-

WRAAAAWAAA

3

1 2

2

1 0

I MPRED 1. 0

7

-

The form of the specifies the source of commodity information, units for bolt length and diameter, and specifies item names used to reference a commodity item in the Piping Job Specification and Graphic Commodity Library. These options are essential to material takeoff reporting.

270


Creating Material Takeoffs and Other Reports Refer to the Project Administrator Reference Guide for more information on the . Refer to the Reference Data Manager Reference Guide for information on the stud table, bolt length calculations, and the bolt commodity code table.

Operating Sequence 1. Specify the bolt information. — Select the option for the means to determine the reported bolt length. the system uses the preferred bolt length table.



the system rounds up the calculated length by the specified



factor. 

the exact length is used.

— Select the method to be used in calculating bolt length. The bolt length is read from the stud table. The table name can be determined using the rating and table suffix ( ) or using termination type, rating, and table suffix ( ). This also affects bolt lengths for lap joint flanges. Select the method to be used in determining the commodity code for bolts for use in material take-off. or . — Select the system of units for bolt diameter.


271

Creating Material Takeoffs and Other Reports — Select the system of units for bolt length. 2. Select this field to toggle the setting between

or

.

3. Select this field to toggle the setting between Off or On. If this field is On, the system displays a field to input the name. 4.

Select this field to toggle the setting between

or

. For a detailed description and graphical examples of how these options work, see the Size Dependent and Independent Reporting section. When the

option is enabled, the system provides two additional options.

This option specifies the source of the commodity code for reporting implied data from the Piping Commodity Implied Material Data Table. The default option ( ) tells the system to use the commodity code defined in the Piping Commodity Specification Data Table (pdtable_202 attribute 18). The option tells the system to use the commodity code defined in the Piping Commodity Size-Dependent Material Data Table (pdtable_21 1 attribute 7). —This option specifies the source of the commodity code for reporting a component's material description. The default option ( ) tells the system to use the commodity code defined in the Piping Commodity Specification Data Table (pdtable_202 attribute 18). This option will result in a smaller Material Description Library. The option tells the system to use the commodity code defined in the Piping Commodity Size-Dependent Material Data Table (pdtable_21 1 attribute 7). This option will result in a larger Material Description Library. 5. Key in the commodity item names to be used for reporting mating implied materials.

6. Key in the Eden Module names. — This field defines the name of the Eden Module which determines the values for the bolt diameter, the number of bolts per mating, and the bolt extension.

272


Creating Material Takeoffs and Other Reports — This field defines the name of the Eden Module which defines values for flange outside diameter, thickness, and seat depth. 7. Key in the bolt length values. The display of these fields is dependent on the setting for . — This table defines the low and high range for calculated bolt lengths and corresponding preferred or purchased lengths of the bolt. This field is only used if is the active Bolt Roundoff Option. — This field defines the value for the bolt roundoff factor in subunits. This value is only used if is the active Bolt Roundoff Option. 8. Select

to accept any changes to the Material Takeoff options.



The material descriptions for commodity items can be loaded in the Material Description library via neutral files. The neutral file includes a unique Commodity Code followed by at least one space and a description enclosed in single quotes. It also contains the implied material descriptions associated with a commodity item. The following shows a portion of the neutral file used to load the Short Material Descriptions. !

DEFI NE SHORT DESCRI PTI ONS

!

Dat e/ Ti me: Thu Apr

!

Pr oc es se

23

Li r ar y

14: 16:58

1992

/ us r / newpi pe/ r e

at a/ us _s

om.

! Cmdt y Code

====================================Descr i pt i on======================

CHAI N_ 1003

’ C ai nw ee [ 4 00] ’

o per a t or eac

wi t

[ 4 22] o

t ot a

c ai n

e ngt

or

[ 4 26] NPD v a ve wi t

c ommo i t y c o e

CHAI N_ 1005

’ C ai nw ee [ 4 00] ’

o per a t or eac

wi t

[ 4 22] o

t ot a

c ai n

e ngt

or

[ 4 26] NPD v a ve wi t

c ommo i t y c o e

CHAI N_1251

’ Chai nwheel oper ator each wi t h

DAABAXAABE

’ Moni t or, CL150 FFFE, w/ s t a i nl es s s t e el s t e m oc

DAABAXAABF

no s wi t

DACBAXABBC

no s wi t

’ Moni t or, CL150 o ut l e t , [ 427] ,

st ati on t ype,

0. 75" c oup i ng i n

’ Moni t or, CL150 FFFE, w/ s t a i nl es s s t e el s t e m oc

[ 424] of t otal chai n l ength f or val ve wi t h t ag no [ 402]’

FFFE,

4" CL150

i n- et

y

2. 5" NHT st ai n ess st ee

out et

a se , w/ s a pe r t i p noz z e , St a ng BB0309- 2 1’

ˆst ati on t ype

4" CL150

0. 75" coup i ng i n

i n-l et by

2.5" NHT st ai nl ess st eel out l et

as e, w/ og noz z e, St a ng BB0309- 2 1’

êl evat ed t ype, f r ee st andi ng,

4" CL150

i n-l et by

2. 5" NHT st ai nl ess st eel

w/ drai n coupl i ng, w/ shapert i p nozzl e and two reacti on support s, Stang BB2999- ’


273

Creating Material Takeoffs and Other Reports DACBAXABBD

’ Moni t or, CL300 FFFE, s t e el o ut l et , [ 4 27] ,

e evate

type, suppor t e ,

6" CL300

i n- et

y

2.5" NHT st ai n ess

w/ drai n coupl i ng, w/ shapert i p nozzl e, Stang BB3561’

DBAAAXBAAB

’ Fi re y r ant , CL125 hose nozzl es e qui ppe

274

w/ c aps an

FFFE,

5" si ze, counterc oc wi se open,

c ai ns ,

300#, FTE,

4.5" st eamer nozz e, t wo

[ 4 28] , Ame r i c an Dar i ng B- 5 0- B’

DCBGDXEADA

’ Hose r ack, 30- 333’

DDAXCJ DAAA

’ Spr a y s pr i n

FAAAAAWAAA

’ Fl ange, CL150, FFFE/ BE,

FAAAAAWWAA

’ F ange, CL150, FFFE/ BE,

ASTM- A105, ANSI - B16. 5, WN, cement

FAAABADI I A

’ F ange, CL150, RFFE/ BE,

ASTM- A182- F304, ANSI - B16. 5, WN, S-80S

FAAABADI I F

’ Fl ange, CL150, RFFE/ BE,

FAAABADNPF


ASTM- B166-600, ANSI - B16. 5, WN, S- 80S

FAAABAOAAA


ASTM- A105, ANSI - B16. 5, WN, S- 160

FAAABAOABB


ÂSTM- A350-LF2, ANSI - B16. 5, WN, S- 160

bore’

FAAABAOFFH


ASTM- A182-F5, ANSI - B16. 5, WN, S- 160

or e’

FAAABAWAAA


ASTM- A105, ANSI - B16. 5, WN,

FAAABAWABB


ÂSTM- A350-LF2, ANSI - B16. 5, WN,

FAAABAWFFH


ASTM- A182- F5, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAAABAWFFL


ÂSTM- A182-F9, ANSI - B16. 5, WN,

[ 409] | bore t o mat ch| ’

FAAABAWGFD


ASME-SA182- F11, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAAABAWI I A


ASTM- A182-F304, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAAABAWI I F


ÂSTM- A182- F316, ANSI - B16. 5, WN,

[ 409]| bor e t o matc h| ’

FAAABAWNPF


ASTM- B166- 600, ANSI - B16. 5, WN,

FAAABBDAAA


ASTM- A105, ANSI - B16. 5, WN, S- XXS

FAAADAOAAA


FAAADAOFFC


FAAADAWAAA


er , MTE,

2.5"

ˆw/ val ve, wal l mount , r t hand w/ 100 f t hose & f og nozzl e, Powhatan

i

e

c one w/ r u pt u r e

i s c,

304, Gr i nne

ÂSTM- A105, ANSI - B16. 5, WN,

, Mu s i yr e Pr o j e ct o r S- 1 ’


i ne ,

[ 409]| ore t o matc | ’

ore’

ÂSTM- A182- F316, ANSI - B16. 5, WN, S-80S bor e’


or e’

[ 409]| ore t o matc | ’


125

ASTM- A182- F11, ANSI - B16. 5, WN,


or e’

125

[ 409]| ore t o mat c | ’

or e’

Ra f i ni sh, S- 160

125

Ra

bore’

i ni s , S-160

Ra f i ni sh,

ore’



Creating Material Takeoffs and Other Reports FAAADAWFFC


ASTM- A182-F11, ANSI - B16. 5, WN,

125

Ra

FAAADBDFFC



125

Ra f i ni sh, S- XXS bore’

FAABBADI I A



FAABBADI I B


ASTM- A182- F304L, ANSI - B16. 5, WN, S-80S

FAABBADI I F


FAABBAOAAA


FAABBAOABB


ÂSTM- A350-LF2, ANSI - B16. 5, WN, S- 160

bore’

FAABBAOFFC


ASTM- A182-F11, ANSI - B16. 5, WN, S- 160

or e’

FAABBAOFFH


ASTM- A182-F5, ANSI - B16. 5, WN, S- 160

FAABBAWAAA


FAABBAWABB


ASTM- A350- LF2, ANSI - B16. 5, WN,

[ 409]| ore t o mat c | ’

FAABBAWFFC


ASTM- A182- F11, ANSI - B16. 5, WN,

[ 409]| ore t o mat c | ’

FAABBAWFFH




FAABBAWFFL


ASTM- A182- F9, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAABBAWI I A


ASTM- A182-F304, ANSI - B16. 5, WN,

FAABBAWI I B


ÂSTM- A182- F304L, ANSI - B16. 5, WN,

FAABBAWI I F


ASTM- A182-F316, ANSI - B16. 5, WN,

FAABBAWNPF


FAABBBDAAA


ASTM- A105, ANSI - B16. 5, WN, S- XXS

FAABDADI I J


ASTM- A182- F321, ANSI - B16. 5, WN,

FAABDAOAAA


FAABDAOFFC


ASTM- A182- F11, ANSI - B16. 5, WN,

FAABDAWAAA


ASTM- A105, ANSI - B16. 5, WN,

FAABDAWFFC


ÂSTM- A182- F11, ANSI - B16. 5, WN,

FAABDAWFFH


ASTM- A182-F5, ANSI - B16. 5, WN,

FAABDAWI I J

’ Fl ange, CL300, RFFE/ BE, match| ’


i ni s ,

[ 409]| ore t o matc | ’

ore’

ore’

ÂSTM- A182- F316, ANSI - B16. 5, WN, S-80S bor e’

ASTM- A105, ANSI - B16. 5, WN, S- 160


or e’


[ 409]| ore t o matc | ’


or e’

125

125

Ra

i ni s , S-80S

Ra f i ni sh, S- 160

125

125

ÂSTM- A182- F321, ANSI - B16. 5, WN,

[ 409]| bor e t o match| ’

[ 409]| ore t o matc | ’

ÂSTM- B166-600, ANSI - B16. 5, WN,


or e’

Ra

125

125

125

Ra

ore’

[ 409]| ore t o matc | ’

Ra f i ni sh,

Ra

bore’

i ni s , S-160

i ni s ,

ore’

i ni s ,

Ra f i ni sh,

[ 409]| bor e t o mat ch| ’

[ 409]| ore t o matc | ’

[ 409]| bor e t o

275

Creating Material Takeoffs and Other Reports FAADBADI I A



ore’

FAADBADI I F


FAADBAOAAA


ASTM- A105, ANSI - B16. 5, WN, S- 160

FAADBAOABE


ASME- SA105, ANSI - B16. 5, WN, S- 160

FAADBAWAAA


FAADBAWABE


FAADBAWFFC



FAADBAWFFH


ASTM- A182- F5, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAADBAWFFL


ASTM- A182- F9, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’

FAADBAWI I A


ÂSTM- A182-F316, ANSI - B16. 5, WN, S- 80S bore’


or e’

or e’


ASME-SA105, ANSI - B16. 5, WN,

[ 409]| ore t o matc | ’


ÂSTM- A182- F304, ANSI - B16. 5, WN,

[ 409]| bor e t o matc h| ’

The following conventions are used to identify different types of information in the material descriptions:   

ˆ All information to the left of the carat (ˆ) is used in MTO reporting and isometric extraction, but is excluded from Spec reporting. | | Information appearing in |Pipes| indicates information for Spec descriptions only. This information is excluded from the descriptions for MTO reporting and isometric extraction. [] Information appearing in [brackets] indicates a label type from the Label

Description Library. The system uses the label format to determine the information to be included in the material description for MTO reporting and isometric extraction. The label information is never used in Spec reporting. The following label types are provided in the product delivery:

276

Label No

Data in Label

Source of Data

401

Piping sch/thk 1

Pipe

403

Component Sch/thk 1

Component

405

Component sch/thk 1 b

Component

407

Component sch/thk 2

Component

409

Component sch/thk 2 b

Component

411

Component sch/thk 1 x 2

Component

413

Component sch/thk 1 x 2 b

Component

415

Component sch/thk 1 x 3

Component


Creating Material Takeoffs and Other Reports 417

Component sch/thk 1 x 3 b

Component

421

Bonnet length

Component

423

Reinforcing weld size

Component

425

Pad width x pad thick

Component

Attributes for mating implied items, specifically bolts and gaskets, are not stored in the Design Database (dd_projname) where attributes for independent components are stored. You can insert labels in Material Description Library for bolt and gasket entries, but these labels must be classified as labels when they are created. Although data for bolts and gaskets is not recorded in the Piping Component Data Table (pdtable_34_x) in the Piping Design Database (dd_projname), bolt and gasket labels are classified as labels. The system retrieves the bolt and gasket information for reporting using related attributes in the Piping Component Data Table (pdtable_202). Although all of the attributes for piping components are available when you define a bolt or gasket label using the labels option, only the following attributes contain data that is pertinent to bolt and gasket reporting. The following list displays the formattribute/table-attribute relationships which define what data is actually reported from the Piping Component Data Table (pdtable_202):

commodity_name

commodity_name

option_code

option_code

maximum_temp

maximum_temp

cp_1_nom_pip_diam

gcpjrom_nom_diam

cp_1_end_prep

gcp_to_nom_diam

cp_1_outside_diam

gcp_end_prep

cp_1_rating

gcp_rating

cp_1_sch_thk

gcp_sch_thk

table_suffix_green

gcp_table_suffix

cp_2_nom_pipe_diam

rcpjrom_nom_diam

cp_2_outside_diam

rcp_to_nom_diam

cp_2_end_prep

rcp _end_p rep

cp_2_rating

rcp_rating

cp_2_sch_thk

rcp_sch_thk

table_suffix_red

rcp_table_suffix

commodity_code

commodity_code


277

Creating Material Takeoffs and Other Reports model_code

model_code

PDS_sort_code

PDS_sort_code

bend_radius

modifier

geometric_standard

geometric_standard

weight_code

weight_code

fabrication_cat

fabrication_cat

materials_grade

materials_grade

standard_note_no_a

standard_note_no_a

standard_note_no_b

standard_note_no_b

A Label Description Library is delivered in win32app\pdshell\lib\labels. l and should be edited to suit the needs of your project.

The is used to create and revise label data for the PDS 3D modules. The Create Label Attribute Data form allows you to create and define a label. The Line and Item fields are used to define the attributes that make up the label and the order of the attributes within the label.

Set the option at the upper left of the form. 278


Creating Material Takeoffs and Other Reports — used to add a line or item to the label description. — used to delete a selected line or item from the label description. used to revise a selected line or item in the label description.

—

Ins ert Data 1. Set the option to . 2. Set the toggle to or . 3. Select Line or Item to Insert Data Select a line field to create a new line (before or after) the selected line. —OR — Select an item field to create a new item in the current line (before or after) the selected item. The system activates a form that displays the Attribute Data Types. The following form illustrates the display for a dr awing view specific label.

4. Select Option Select


to define the attribute data type for the bolt or gasket label.

279

Creating Material Takeoffs and Other Reports The system displays the attributes for the selected data type.

5. Enter Data Select the attribute to be reported from the form. The system sets the automatically. You can modify the total length and the number of decimal places (if applicable). All of the attributes that apply to gaskets and bolts are listed in the section. —OR — For drawing view specific labels, you can select entered by the user at label creation.

to specify text to be

—OR — Select

and key in the text for a literal expression to be inserted in the label.

—OR — Select

and key in the number of spaces to define spacing between attributes.

6. Repeat the previous step to add additional attribute text information. This allows you to combine attribute values and pre-formatted text. You can only define one user-defined key-in in a specific label. 7. Select one of the options to specify a modifier to the active format. = MicroStation master units, = MicroStation sub units. 8. Select  to accept the specified attribute data.

280



Delete Data 1. Set the option to . 2. Select the line or item to be deleted. 3. Select  to delete the highlighted line or item. When you select a line, the system deletes all the associated items.

Edit Data 1. Set the option to . 2. Select Item to Edit Select the item to be revised. The system displays the attributes definition form for the selected item. The active setting is highlighted or shown in the display fields.

Select an attribute from the form to change the type of data. —OR — 3. Select the places (if applicable). —OR —

option. You can modify the total length and the number of decimal

For drawing view specific labels, you can select entered by the user at label creation.

to specify text to be

—OR — Select

and key in the text for a literal expression to be inserted in the label.

—OR — Select

and key in the number of spaces to define spacing between attributes.

4. Repeat the previous steps to edit additional items. —THEN — Select  to accept the edits.

The Material Data Publisher utility (MDP) allows PDS users to generate relational database tables containing all the material data associated with a PDS model and publish these tables to a new database schema (MTO_PROJNAME). These tables make the model data available for easier reporting outside of PD_Report. The Material Data Publisher uses selection set files to determine what data to publish. The MDP interface allows you to select specific disciplines, model areas, and models within the project to publish, and to save different sets of models in separate selection set files. When the data is published, it can be accessed through ORACLE, SQL, ODBC clients such as Microsoft Access, and other database utilities for reporting, tracking, and ordering. The PDS project to be published must contain at least one piping model before running Material Data Publisher.


281


282


SECTION 27

The PDS Isometric Extraction Software creates piping isometric drawings from 3D piping models created by the Piping Designer.

The software consists of two principal components:  

Intergraph 3D software packages which create input for ISOGEN and perform other functions necessary in final drawing creation. ISOGEN, which draws the piping isometric and places it in a MicroStation design file and

The software allows you to extract isometrics from a 3D plant model: single isometrics interactively or multiple isometrics in a batch mode.


283

Extracting Isometric Drawings The ISOGEN software is designed to be flexible because drawing practices vary from one company to another. The following features of Intergraph's isometric extraction package allow you to specify drawing format:        

User-controlled ISOGEN option switches The capability to use an alternate or foreign text A large set of Intergraph option switches User-controlled attribute breaks shown on drawings A flexible method for generating notes Attribute-driven symbology (solid or dotted lines) User-defined component symbology User-controlled mapping of attributes to the title block.

In addition to the isometric drawing, the software also generates several nongraphic outputs, the most important of which is a completely user-definable MTO neutral file. This neutral file is extremely useful for those who want to combine a material control system with Intergraph's 3D modeling software. The above features are collectively referred to as software customization and are dealt with at length in the PDS ISOGEN Interface Reference Guide . Overview of Isometric Extraction.................................................. 285 Batch Software Organization......................................................... 287

284


Extracting Isometric Drawings

This section outlines the software components and how they are organized for interactively extracting isometrics.


285


The core software module in isometric extraction (both interactive and batch) is the ISOGEN interface. This program reads data from the 3D model files and generates an input file for ISOGEN. ISOGEN knows nothing of PDS or any of its files. It reads only the input file created for it by the ISOGEN interface. While ISOGEN is primarily responsible for generating the drawing graphics (including dimensioning) the ISOGEN interface is responsible for most everything else — including note generation, recognition of attribute changes, defining which symbols to use and so on. The primary input to the ISOGEN interface is an ASCII file named pdsidf.dat. The interface reads from this file the piping and equipment models involved, involved, the output isometric file name, and identification of all of the pipelines in the drawing. The interface also reads in data from the options file. The options file consists of a collection of switches, options and tables that gives you some control over what the ISOGEN interface puts in its output file (called the intermediate intermediate da ta file or ) and therefore what appears in the final drawing. Once this data is read in, the interface collects from the model files all of the components that make up the piping network. Data from the components is then used to form an internal data structure which represents the network. Finally, this network is traversed (the software traces a path through the piping network) network) and records are are generated in the idf. The order of of the records in the idf is in the order of the network traversal. Drawing notes and other features such as bill of material information are dealt with component by component as the network is traversed. If the components in the piping models are not properly connected or other problems exist, the internal data structure will not be properly built and isometric extraction will fail. The HITS report can help you to find problems in the piping model and tell you when the interface software is not working w orking properly.

The Intergraph interface to ISOGEN creates an ASCII data file containing the input to ISOGEN. Since ISOGEN requires the input data to be in binary format, a program named ISOA_BGEN is run to convert this ASCII data file to binary. ISOA_BGEN creates the binary output file FOR036.# which IZOD2 uses to generate the isometric drawing.

ISOGEN takes the binary input file and generates graphics in a 2D MicroStation design file. The graphics consist of the completed isometric drawing. ISOGEN can also generate several nongraphic outputs, including:    

286

An ISOGEN MTO neutral file A parts list (bill of material) A cut pipe report A component VRS sheet number file


Extracting Isometric Drawings The parts list file contains the same bill of material that is shown on the isometric drawing. It is possible to turn the drawing bill of material off and attach the the printed ASCII ASCII file to the drawing drawing instead. The cut pipe report, which shows the length of each piece of pipe in the line, can be useful. The component VRS sheet number file is used by the batch extraction software and is discussed elsewhere.

This section provides an overview of the batch extraction software components and organization. The purpose of this section is to explain to software support personnel how the software works so that problems can be tracked down and reported. The batch extraction software is driven by an executable (pdsidf) and a script file ( batch. sh ( )). When you submit a batch job using the Schedule Batch Job form the batch extraction is submitted to a batch queue named PDisocreate. This queue is created with a job limit of 1 and a priority of 16. You can change these parameters as needed. In order to run batch iso's, a new file located in /usr/bin called pd_iso.sh must define locations for required software. This script is executed from the batch queue and allows the batch extraction process to run on a node other than the one from which it was submitted. The following four variables must be exported: PD_SHELL PD_ISO PD_ISOGEN RIS_PARAMETERS The above variables have the following default settings after the product is installed. PD_SHELL = c:\win32app\ingr\pdshell c:\win32app\ingr\pdshell PD_ISO = c:\win32app\ingr\pdiso\ c:\win32app\ingr\pdiso\ PD_ISOGEN = c:\win32app\ingr\pdisogen\ c:\win32app\ingr\pdisogen\ RIS_PARAMETERS RIS_PARAMETERS = c:\win32app\ingr\ris\parameters c:\win32app\ingr\ris\parameters If the locations for the above variables are different from the default locations. The file c:\win32app\ingr\pd_iso.sh must be edited so that it reflects the current variable location.


287


The input to the batch procedure is an ASCII data file generated by the Batch Environment called the Batch Job Input File. This file is structured as shown.

Figure 9 - 1. Batch input file data structure

The first record in the file contains a file format version number and the name of the Batch Data File from which the Batch Job Input file was generated. The software checks the version number to see if it matches the software version number, and, if it does match, passes the Batch Data File name on to other software modules as needed. The second record is called an option record . The option record contains all of the batch processing options options and revision block data that that was entered into into the BATCH BATCH form. Each option option is separated from the others by at least one space. This record contains c ontains an exclamation point (!) in column 1 which flags it as an option record. The third record holds the name of the default set which was specified in the Create Batch Job Input form. This record also contains an exclamation point in column 1. Subsequent records, which initially contain a space in column 1, hold the area and primary line name for an isometric drawing which will be extracted. After the line is extracted, it is marked by an asterisk (*) in column column 1 to indicate that it has been processed. The drawing records can be repeated r epeated any number of times in the batch job input file. Each time you select the Accept button from the Create Batch Job Input form, you write out a set of drawing records to the batch input file. An example batch job input file is shown below.

Figure Figur e 9 - 2. Example Example Batch Job Input File

When a batch iso job is submitted using the Schedule Batch Job form, the batch job input file name is passed to the pdsidf executable as a parameter. The system then reads the batch job input file and drawing creation begins.

288



Given the options from the batch input file and the identification of the line, two files are created, seed.dat and pdsidf.dat. These are the same two files that are created during interactive extraction. The Project database is accessed to obtain the list of model files, secondary pipeline names, the seed file names, the options file for the piping area, the output file directory, the iso design file name and the extraction number for the drawing. The two files produced are different from f rom the ones produced for interactive extraction. In pdsidf.dat, the first line name name in the line line name list is followed by a backslash and the piping area name. Following the line list is a record that contains the default set name. Next is a record that contains batch processing options. The last record contains the extraction number for the drawing. ski so5 ski so4 ski so6 ski so7 *ski so3 40eqp01 40eqp00 pds sk sk: h: \ pr o j \ i s o\ o\ i s of of i l es \ 380105wc . i * 380105\ ski so\ 1 pr o j N Y Y N * * Y * * 0404- Augug- 1998 1998 * 13 10

In SEED.DAT, the seed iso design file name is followed f ollowed by records containing the plot request file name, the output file directory, the output iso file name, extraction number and number of sections. pds sk sk: h: \ pr oj o j \ i s o\ o\ r ef ef \ i s oc oc . def pds sk sk: h: \ pr oj o j \ i s o\ o\ r ef ef \ i s oc oc . s ed ed pds sk sk: h: \ pr oj o j \ i s o\ o\ r ef ef \ i s oc oc _ s ml . i pds sk sk: h: \ pr oj o j \ i s o\ o\ i s of of i l es 380105 13 1. f i

The ISOGEN interface performs the same function in batch extraction as in interactive extraction. It generates an Intermediate Data File (IDF), which is the input to ISOGEN. In addition to the IDF the interface may also produce an mto neutral file and three files containing text for the drawing title block.


289


Isometrics generated by the batch software are always created one sheet to a design file. The iso design file name is passed to the interface as name.i*. Therefore, the first sheet will be in a file with the extension .i01, the second in .i02 and so on. When isometrics are created in batch, you must set Intergraph options block word 4 to 1. This causes ISOGEN to create a file that identifies which sheet each component in the line is drawn on. This file (called the sheet data file) is used downstream to split up the mto neutral file by sheet and also to prepare the segment summary table for each isometric sheet.

After drawings are created in batch they can be plotted with the IP_IPLOT plotting software. software. To submit a plot, the batch software submits a job j ob to the batch queue named PDisoplot. The job that runs in PDisoplot actually launches the plot. Since the plot jobs are launched from a separate batch queue, you can accumulate the jobs in the queue and release them at some later time. You might also hold the jobs in PDisoplot to prevent normal production plotting queues from getting loaded down with isometric plots.

290


SECTION 28

Designers use the product to create and/or revise orthographic production drawings. drawings. PD_Draw creates creates windows (drawing (drawing views) to the live 3D Models created with PD_Design and the other modeling products. PD_Draw is used to place annotation labels identifying intelligent items and model coordinates, to plot the drawings, and to produce reports r eports for drawings and model data.

The is used to create and revise orthographic production drawings. It can be used by any of the 3D disciplines within PDS for drawing management. A drawing is a sheet or a plot used to describe the design of a model design volume (work area). Many drawings can be created from one model to completely document a design volume. A drawing can contain more than one drawing view of a model or models. A drawing view is a view of a model or models. Each drawing view within a drawing can have a different scale and each label within a drawing can have a different character size. You can create a drawing during any stage of the design process. It consists of the reference model attachments for the model graphics used in the drawing dra wing and the graphics for the drawing itself. The model graphics reside in the design file for that model. These model graphics are attached to the drawing as reference ref erence files through the use of drawing views.


291

Creating Orthographic Drawings

Drawing Manager Features............................................................ Drawing Manager Setup ................................................................ Drawing Seed Data ........................................................................ Using Labels in Drawing ...............................................................

The

292 292 297 301

can be used to:



Create a drawing for any of the PDS 3D disciplines, along with a key plan drawing.



Create multiple drawing views for a given drawing.



Revise definition information for existing drawings or drawing views. Delete drawings and drawing views Place annotation labels on a drawing to identify intelligent items and model coordinates.

    

Create hidden-line-removed model graphics. Plot a drawing or set of drawings. Create a key plan model for the project.

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

Loading PDS 3D products.



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

 

292



A set of model files for the project must be defined before you can use the

.

Refer to the following documents for information on creating and manipulating PDS 3D Models. 

Piping Design Gr aphics Reference Guide



PDS Equipment Modeling Reference Guide



MicasPlus ModelDraft Reference Guide



PE HVAC Modeling Reference Guide



EE Raceway Modeling Reference Guide

Complete the following operations before using the

.

When a project is created, the copies the default drawing category names to the project directory. The name of the copied file is drwcats.txt . You can edit this file to change the names that are displayed for drawing categories. Although you can modify the drawing category names, the meaning of a specific category will not be altered by this change.

The flow arrow symbol for drawing annotation is provided in the cell library win32app\pdshell\cell\drawing.cel . This cell library is copied to the project directory by the as a part of project creation. The attaches this cell library each time you select a drawing for the purpose of drawing annotation. The drawing.cel library in the project directory must be used for any cells, other than the flow arrow, which you intend to use for drawing annotation.

The attach.

uses the following guidelines to determine which drawing border to



The directory and network address for the drawing border is defined in the RDB Management Data with the . This setting is stored in the Project Control Database for access by the .



The file specifications for the drawing borders are determined by the following naming convention. dwgbrd_. drawing_type is the standard note number in Standard Note Type 2000 for drawing types.


293

Creating Orthographic Drawings drawing_size is the text for the standard note value corresponding to the drawing size in the

Standard Note Type 1202. For example, the drawing border name for an 'A' size piping drawing is dwgbrd_2.a .

This table is located in the drawplotsize file and is copied from the PD_Shell delivery directory at the time a project is created. It contains the drawing size standard notation, plot size, the standard text for the size, and the four margins for the cutting edge. An example of a drawplotsize file and definitions of each field follows: ! Dr awi ng Pl ot Si ze Tabl e ! ! Dr awi ng Si ze Cut t i ng Edge Mar gi ns f r om Cut t i ng Edge ( Dr awi Si ze) ! St d Not e Si ze X- l Y- t X- r Y- b ! 1 8. 5" x11" 0. 8125" 0. 625" 2. 125" 0. 625 ( A) 2 11" x17" 1" 0. 6875" 3" 0. 6875" ( B) 3 17" x22" 1. 1875" 0. 75" 3. 75" 0. 75" ( C) 4 24" x36" 1. 375" 0. 8125" 5. 4375" 0. 8125" 5 34" x44" 1. 5625" 0. 875" 6. 875" 0. 875" 6 28" x40" 1. 625" 0. 9375" 5. 625" 0. 9375" 101 840mmx1189mm 56mm 35mm 198mm 35mm ( A0) 102 595mmx840mm 47mm 30mm 193mm 30mm ( A1) 103 420mmx595mm 38mm 27mm 190mm 27mm ( A2) 104 297mmx420mm 33mm 25mm 155mm 72mm ( A3) 105 210mmx297mm 28mm 24mm 65mm 24mm ( A4)

ng

( D) ( E) ( F)



is the standard note, which is referenced from the Standard Note Type 1202, for the drawing size selected.



reflects the actual size of the cutting edge around the border that is associated with the drawing size.

 

defines the horizontal distance from the left cutting edge for composition.



defines the horizontal distance from the right cutting edge for composition.



defines the vertical distance from the top cutting edge for composition.



defines the vertical distance from the bottom cutting edge for composition.



294

is the standard note text for the drawing size.



This section describes and includes the tables from the Default Relational Database Definition, which is stored in the project.ddl file, that are used during the drawing process. These tables are dedicated to the Drawing Manager task. There is interaction between these tables and other various tables in the Project Control Database (PDTABLE_1 12 Design Area Data, for example).

This section describes and includes the tables from the Project Control Database that are affected during the drawing process. Do not edit database definitions except to modify column names. # Dr awi ng Data t a e num e r = 121, n um e r o = 1 , wg_ i n ex _ no

c o umns

24 , i nt e ge r

, i n ex

1

, i ndex

2

2

, drawi ng_no

, char acter( 24)

3

,

r awi ng_ t i t e

, c ar act er 40

4

,

e au t _sca e

, c ar act er 16

5

, a ppr o va l _ i ni t i al s

, c har a c t e r ( 4 )

6

, appr o va _ at e

, i nt e ger

7


, s or t

8

, compl eti on_stat us

, short

9

,

, s t a n ar

not e 35

, s or t

, s t a n ar

not e 1202

10, drawi ng_t ype

, shor t


11,


, c ar ac t er 2

12,

r awi ng_ i e_ spec

, c ar ac t er 14

r a wi ng_ s i z e

13, pat h_name

, char acter ( 36)

14, net wor _ a 15,

, i ndex 3

r ess

, c ar act er 26

oc _ owner

, c ar ac t er 10

16, l ock_status

, short

17,

oc _ at e

, i nt e ger

18, revi si on_date

, i nteger

19, l ast_r ev_i ndex_no

, short

20, r e eas e_ r evi s i o n

, c ar ac t er 2

21, rel ease_date

, i nteger

22, c ec i ng_ st a t us

, s or t

, s t an ar

not e 1610 not e 499


, s or t

, s t an ar

24, st andar d_not e_no_b

, short


# Dr awi ng Vi ew Data t abl e number =

= 122, number of c ol umns


16

295

Creating Orthographic Drawings 1

,

wg_ v i e w_ i n ex _ no

, i nt e ge r

, i n ex

1

2

,

wg_ vi ew_ no

, c ar ac t er 6

, i n ex

2

3

, dwg_vi ew_name

, char acter ( 40)

4

,

, c ar ac t er 16

5

, dwg_i ndex_no

, i nteger

6

, s av e _ vi ew_ name

, c ar a ct e r 6

7

, vi ewi ng_ i r ec t i o n

, s or t

8

, composi t i on_st atus

9

,

10,

wg_ vi ew_ s ca e

, s t an ar

, shor t


wg_vi ew_ x_ ow wg_ vi ew_y_ ow

,

ou

e

,

ou

e

11, dwg_ vi ew_z_ l ow

, doubl e

12,

wg_ vi ew_ x_ i g

,

ou

e

13,

wg_ vi ew_ y_ i g

,

ou

e

14, dwg_vi ew_z_ hi gh 15, v

_ cat egor y_ i n ex

, doubl e , s or t

16, drawi ng_vi ew_t ype

, shor t

# Drawi ng Vi ew Re erence Mo e t a e num e r = 123, n um e r o = 1 , dwg_vi ew_i ndex_no 2

not e 1620

Data c o umns

2 , i nteger

, mo e _ i n ex_ no

, i nt e ger

# Composi t e Dr awi ng Vi ew Data t abl e number = 124, number of c ol umns = 1 , c omp_ wg_ i n ex _ no

15

2

, comp_dwg_vi ew_no

, char acter ( 6)

3

, comp_dwg_vi ew_name

4

, c omp_ wg_ v_ sc a e

, c ar ac t er 16

5

, dwg_i ndex_no

, i nteger

6

,

wg_vi ew_i n ex_a

, i nteger

7

, dwg_vi ew_i ndex_b

, i nteger

8

, dwg_vi ew_i ndex_c

, i nteger

9

,


, i nt e ge r

10, dwg_vi ew_i ndex_e

, i nteger

11,

wg_ v i e w_ i n e x_

, i nt e ge r

12,

wg_vi ew_i n ex_g

, i nteger

13, dwg_vi ew_i ndex_h

, i nteger

14,

wg_vi ew_i n ex_i

, i nteger

15,

wg_vi ew_i n ex_j

, i nteger

, i nt e ge r

, i n ex

1

, char act er ( 40)

# Dr awi ng Revi si on Data t a e num e r = 125, n um e r o = 1 , dwg_i ndex_no

296

c o umns

7 , i nteger

2

, r evi s i o n_ i n ex_ no

, s or t

3

, r evi s i on_ no

, c ar ac t er 2


Creating Orthographic Drawings 4

, r e vi s i on_ at e

, i nt e ger

5

, r evi s i o n_ y

, c ar act er 4

6

, checked_by

, char acter( 4)

7

, r ev_ es cr i pt i on

, c ar ac t er 40

# Dr awi ng Setup Dat a t a e num e r = 126, n um e r o = 1 , r a wi ng_ t y pe

c o umns

7 , s or t

, s t a n ar


2

, drawi ng_si ze

, shor t

3

,

r awi ng_ sc a e

, c ar ac t er 16

4

,

e au t _ pat _ name

, c ar ac t er 36

5

, def aul t _node

, character (26)

6

,

, s or t

7

, a t e r nat e _s ee _ opt

i s ci p i ne_ mas

not e 2000

, s or t # Ref erence Model Di spl ay Category Setup Data

ta

e num e r

= 1 27, num e r o

c o umns

= 6

1

, drawi ng_t ype

2

,

3

, cat egory_mas _a

, i nteger

4

, categor y_mask_b

, i nteger

5

, cat egory_mas _c

, i nteger

6

, c at e gor y _ mas _

, i nt e ge r


, shor t


, s or t

# Pl ott i ng Defaul t Data ta

e num e r

= 1 28, num e r o

c o umns

= 6

1

, i pl ot_i ndex_no

, i nteger

2

, i pl ot_number

, char acter( 24)

3

, i p ot _ es cr i pt i on

, c ar act er 40

4

, i pl ot _ f i l e _s pe c

, c har a c t e r ( 1 4)

5

, pat _ name

, c ar ac t er 36

6

, net work_address

, char acter( 26)

The is used to revise the seed data for a specified drawing or create a report of the RDB data. You can revise both 3D data and drawing data.


297

Creating Orthographic Drawings The option is used to revise the seed data for a selected drawing file. The system activates the following form which provides access to the modification options.

Select the option for the type of drawing data to be revised. The following report shows the delivered settings for the Drawing Data. P r oj ec t Dat a Manager Dr awi ng Category Dat a Level Dr a wi ng Vi ew Spec i i c L a e s

4

Dr awi ng Vi ew I n ent i i c at i on La e s

5

Coordi nat e Label s

7

Di mensi oni ng

9

Re vi s i on T r i ang e s an

298

Re vi s i on C ou s

10

Hol d Cl ouds

11

Report s

8

Mi scel l aneous Dr awi ng Gr aphi cs

3

No n- P ot t e

12

Dr a wi ng Gr a p i c s

Batt ery Li mi t s

36

Matc hl i nes

37

Cent er i nes

38

Dum Detai s

39

Leader Li nes f or Dumb Detai l s

40

Ext ensi on Li nes

41

or Dum Detai s

Di mensi ons f or Dumb Det ai l s

42

Coordi nat es f or Dumb Detai l s

43


Creating Orthographic Drawings Li e L i ne No L a e s

44

Li e Equipment No La e s

45

User - def i ned drawi ng annot ati on category

11

46

User- e i ne

rawi ng annotati on category

12

47


13

48

User- e i ne


14

49

User- e i ne


15

50


16

51

User- e i ne


17

52

User- e i ne


18

53


19

54

User- e i ne

20

55

or Vi ew Numer

1

21

Hi dden Li ne Cat egory f or Vi ew Number

2

22

Hi

or Vi ew Numer

3

23


4

24

Hi

en Li ne Category

or Vi ew Numer

5

25

Hi

en Li ne Category

or Vi ew Numer

6

26


7

27

Hi

en Li ne Category

or Vi ew Numer

8

28

Hi

en Li ne Category

or Vi ew Numer

9

29

Hi dden Li ne Cat egor y f or Vi ew Number

10

30

Hi

or Vi ew Numer

11

31


12

32


13

33

Hi

or Vi ew Numer

14

34


15

35

Da s e

or Vi ew Num e r

1

13

Dashed Hi dden Li ne Cat egory f or Vi ew Number

2

14


3

15

Da s e

or Vi ew Num e r

4

16


5

17

Da s e

Hi

e n L i ne Ca t ego r y

or Vi ew Num e r

6

18

Da s e

Hi


or Vi ew Num e r

7

19


8

20

Da s e

Hi


or Vi ew Num e r

9

56

Da s e

Hi


or Vi ew Num e r

10

57


11

58

Da s e

or Vi ew Num e r

12

59


13

60

Da s e

Hi


or Vi ew Num e r

14

61

Da s e

Hi


or Vi ew Num e r

15

62

Hi


en Li ne Category

en Li ne Category

en Li ne Category

en Li ne Category

Hi

Hi

Hi





299

Creating Orthographic Drawings Pr oj ect Dat a Manager Drawi ng Grap i c Symo ogy Wei ght

Col or s

Revi s i on C ou

0

Wi te

Fl ow Ar r ow

0

Whi t e

Report

0

Wi t e

Di mensi on

Wi t e

Mi scel l aneous

Vi ol et

Fi e

Name

or Nomi na

Symbol Font

FLOARR

Pi pi ng Di ameter 50

C ar a c t e r Si z e o r Report Li ne Spaci ng Factor Maxi mumB an

Name

Li ne

Un e i ne , Un e i ne 0. 500000 3 Pr oj ect Dat a Manager Dr awi ng Label Si zes

Text Hei g t

Text Wi t

1/16"

1/16"

1/ 8"

1/ 8"

1/ 4"

1/ 4"

5/16"

5/16"

3/ 8"

3/ 8"

1/ 2"

1/ 2"

5/ 8"

5/ 8"

11/ 16"

11/ 16"

7/ 8"

7/ 8"

3/ 4"

3/ 4" Pr oj ect Dat a Manager Dr awi ng Annot ati on Li ne Li ne

Cat egory

300

Col or

Batt ery Li mi ts

Wei ght Symbol ogy 0 Sol i d

Mat c

0 So i

Wi te

Cent erl i nes

0 Sol i d

Whi te

Dum Det ai s

0 So i

Wi te

Leader Li nes f or Dumb Det ai l s Ext ensi on Li nes for Dumb Det ai l Di mensi ons or Dum De t ai l s Coordi nates f or Dumb De t ai l s Li e Li n e No La e s

0 Sol i d

Whi te

0 Sol i d

Whi te

0 So i

Wite

0 Sol i d

Whi te

0 So i

Wi te

i n es

Whi te

Termi nat or

Text Si ze 1/ 4", 1/ 4" 1/ 4" , 1/ 4" 1/ 4", 1/ 4" 1/ 4" , 1/ 4" 1/ 4", 1/ 4" 1/ 4", 1/ 4" 1/ 4" , 1/ 4" 1/ 4", 1/ 4" 1/ 4" , 1/ 4"

Text

Spaci ng

Font

Factor

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000


Creating Orthographic Drawings Li e Equi pment No Label s Us er - e i ne r awi ng annot ati on category User - def i ned drawi ng annot ati on category Us er - e i ne r awi ng annot ati on category User - def i ned drawi ng annot ati on category Us er - e i ne r awi ng annot ati on category Us er - e i ne r awi ng annot ati on category User - def i ned drawi ng annot ati on category Us er - e i ne r awi ng annot ati on category Us er - e i ne r awi ng annot ati on category User - def i ned drawi ng annot ati on category

0 So i

Wite

11

0 So i

Wi te

12

0 Sol i d

Whi t e

13

0 So i

Wi te

14

0 Sol i d

Whi t e

15

0 So i

Wi te

16

0 So i

Wi te

17

0 Sol i d

Whi t e

18

0 So i

Wi te

19

0 So i

Wi te

20

0 Sol i d

Whi t e

1/ 4" , 1/ 4" 1/ 4" , 1/ 4" 1/4", 1/ 4" 1/ 4" , 1/ 4" 1/4", 1/ 4" 1/ 4" , 1/ 4" 1/ 4" , 1/ 4" 1/4", 1/ 4" 1/ 4" , 1/ 4" 1/ 4" , 1/ 4" 1/4", 1/ 4"

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

0

0. 0000

Proj ect Data Manager Dr awi ng Hi dden Li ne Symbol ogy Use Def aul t Wei ght Use User Def i ned Symbol ogy Us e De au t Co or

The Label Description Library contains the definitions for all the labels used in the PDS 3D modules. Labels can be placed in the drawing as intelligent graphics with linkages to the design database. You can update existing drawing view specific labels to reflect the latest data in the database. A Label Description Library is delivered in the file win32app\pdshell\lib\labels. l . You can use the to edit the labels to suit the needs of your project.

The following label types are used for annotation in drawings.

Dis playab le Attribu te Labe ls Each type of displayable attribute label has a description in the Label Description Library. This description identifies the label characteristics such as level, color code, style, and font, and the attribute data associated with the label. A displayable attribute label consists of the text and optionally, a leader line, a line terminator, and some label enclosure graphics. This label type is further divided into the following categories. 

Drawing View Specific Label displayable attribute labels for named model items which are placed in a drawing.



Drawing View Identification Label


301

Creating Orthographic Drawings labels with attribute linkages to the Drawing View Data (table 122) that report information about the drawing view such as drawing view name and view scale Drawing View Specific Labels are further divided into subcategories for Piping, SMS, HVAC, and Raceways. Drawing View Specific Labels for Piping and View Independent Labels are divided into sub-ranges for system-defined labels and user labels.

Alph an um eric Labe ls Alphanumeric labels are non-intelligent user-defined labels. Each type of alphanumeric label has a description in the Label Description Library. This description identifies the label characteristics such as level, color code, style, and font. An alphanumeric label consists of the text and optionally, a leader line, a line terminator, and some label enclosure graphics.

Dis playable Attribute Mes s ag e Each type of displayable attribute message has a description in the Label Description Library. Unlike the other label types, the description of a displayable attribute message only contains the attribute data. Therefore, you cannot define label description data such as color, weight, style, and text size for a displayable attribute message. A displayable attribute message has all or part of its text derived from the alphanumeric data that is linked to a specified named item in the model. A displayable attribute message is displayed temporarily at the terminal either as an identification message or as a reporting message. Some of these messages are displayed in the terminal's refresh message fields. Other messages are displayed temporarily in the model. The system does not place any graphics in the model for this type of label. A displayable attribute message can also be used to create a value for another attribute, for example, the Line Number Label attribute.

The is part of the . The following forms show the label definition data used to define the line number label.

302



Label 001 defines the label definition data used to place a line number label in a drawing view.


303


Label 310 defines the structure of the line number label.

304


' '*' Spec Implied Items • 268 [ [Buffer] = Field Definition • 252 [Rows/Page] • 252 [Spacing] • 253 ' '+' Table Implied Example • 270 '+' Table Implied Items • 269 2 2DSetup • 13 3 3D Coordinate Systems • 22 3D Seed Data • 135 3D Setup • 14 A About licensing • 14 About the Reference Database (RDB) • 139 Activating the Orientation Tee • 147 Active Placement Point • 161 Alphanumeric Labels • 302 Analyze Data • 165 Appendix A Troubleshooting • 223 ASCII to Binary Conversion • 286 Attribute Types • 40 B Base Form • 134 Batch Software Organization • 287 Bend Deflection Table • 117 Branch Insertion Tables • 117 C Cells • 293 Choosing Data Transfer Options • 201 Plant Design System 3D Theory

Clash Categories • 240 Clash Precedence • 241 Client/Server Relationship • 38 Code-Listed Attributes • 40 Col • 251 Commodity Code • 102 Commodity Codes • 260 Commodity Item Name Table • 116 Common Tools on Forms • 132 Component Manipulation Commands • 148 Component Revision • 164 Connect Point Data • 78 Coordinate System Indicator and Orientation Tee Coordinate System Indicator • 161 Create Label Attribute Data • 278 Creating 3D Models • 121 Creating and Maintaining Links • 191 Creating Equipment Models • 138 Creating Material Takeoffs and Other Reports • 245 Creating Orthographic Drawings • 291 Creating Piping Models • 149

D Data_Type • 251 Database Definition Files • 41 Database Information • 40 Database Overview • 35 Database Requirements • 168 Define Commands • 148 Definitions • 250 Delete Data • 281 Delivered Reference Data • 76 Design Area and Piping Design Area Predefined Volume • 231 Design Database • 57 Design Review Integrator (PD_Review) • 11 Design Volume Coordinate System • 28 Detecting and Managing Interferences • 227 Dialog Boxes • 128 Diameter Table • 96 Disable Display of P&ID Drawing Command • 217 Discrimination Data File • 247

305

Index Displayable Attribute Label • 304 Displayable Attribute Labels • 301 Displayable Attribute Message • 302 Drawing Borders • 293 Drawing Categories • 293 Drawing Manager (PD_Draw) • 7 Drawing Manager Database Table Information • 295 Drawing Manager Features • 292 Drawing Manager Setup • 292, 293 Drawing Plot Size Table • 294 Drawing Seed Data • 297 Drawing View Specific Labels • 303 DVCS Oriented From Plant North • 31

E Edit Data • 281 EE Raceway Modeling • 11 Equipment Manipulation Commands • 148 Equipment Model Seed Data • 140 Equipment Modeling (PD_EQP) • 4 Equipment Modeling Commands • 148 Equipment Modeling Concepts • 145 Equipment Modeling Environment • 143 Establish a SmartPlant/PDS Link • 194 Examples • 30, 261 Extracting Isometric Drawings • 283 F Fabrication Category • 103 Field_Function • 250 Field_Len • 251 Field_Type • 252 Format File • 246 Format File Syntax • 249 Forms • 130 FrameWorks Plus (FWP) • 4 Functions of PDS Equipment Modeling (PD_EQP) • 139 G Gasket Gap / Table • 99 Generic Physical Data Modules • 108 Generic Tables • 114 Geometric Industry Standard • 102 Graphic Commodity Data and Physical Dimension Data • 87

306

Graphic Concepts for Piping Design • 160 Graphical P&ID Setup Command • 205 Graphics Environment for PDS 3D • 126 Green and Red Connect Point Data • 101

H Hard - Hard Example • 241 Hard - Soft Example • 242 How PDS Works • 91 I Implied Data • 262 Insert Data • 279 Install Oracle • 187 Install SmartPlant Engineering Manager • 188 Install SmartPlant P&ID • 189 Installation • 187 Instrument Component Specification Data • 81 Instruments and Instrument Loops • 3 Interference Checker Input • 237 Interference Checker Output • 238 Interference Checker/Manager (PD_Clash) • 8 Interference Checking Process Overview • 227 Interference Manager • 240 ISOGEN • 286, 290 Item Name and Model Code • 100 L Label Definition Data • 302 Label Description Library • 89 Labels in Material Descriptions • 273 LabelTypes • 301 Level and Symbology Defaults • 125 Level Control and Graphical Symbology • 124 Line Processing (pdsidf) • 289 Load From P&ID Options • 203 M Maintaining Report Definition Data • 246 Map an Ignored Attribute • 198 Map an Unmapped Attribute • 198 Mapping Attributes • 197 Plant Design System 3D Theory

Index Material Data Publisher • 281 Material Description Data • 87 Material Descriptions • 258 Material Takeoff Options • 270 Material Takeoff Reporting (Report Manager) • 263 Materials Grade • 103 Materials Table • 98 Mating Implied Items • 268 Menus • 127 Miscellaneous Commands • 148 Model Data • 165 Model Files • 123, 293 Model Parametric Shape Definitions • 112 Modeling Setup Requirements • 122 Modifier • 102

N Name From P&ID • 180 Name from P&ID Option • 219 Named Component Existence Report Command • 221 Nozzle Manipulation • 148 O Option Code • 101 Optional Report Type Line • 253 Orientation Tee • 162 Output Fields • 253 Overview of Isometric Extraction • 285 P P&ID Correlation Table • 168 P&ID Data • 180 P&ID Data Comparison Options • 181 P&ID Drawing Display Categories Command • 213 P&ID Graphical Data Transfer Setup • 174 P&ID Node Numbers • 176 P&ID to Piping Data Transfer • 167 Palettes • 128 Parametric Shape Definitions • 111 PDS 3D Databases • 39 PDS and the Relational Interface System (RIS) • 36 PDS Isometric Interface (PD_ISO, PD_ISOGEN) • 9


PDS Stress Analysis Interface (PD_Stress) • 7 PDS System Configurations • 37 Physical Data • 113 Physical Data Definitions • 107 Piping Assembly Library • 90 Piping Commodity Data • 100 Piping Commodity Implied Material Data • 84 Piping Commodity Size-Dependent Material Data • 83 Piping Commodity Specification Data • 78 Piping Connect Points • 163 Piping Design Area and Design Area • 231 Piping Design Commands • 163 Piping Design Graphics (PD_Design) • 5 Piping Job Specification • 77 Piping Materials Class Code • 95 Piping Materials Class Data • 77, 94 Piping Model Seed Data • 151 Piping Revision • 165 Piping Segments • 160 Piping Specialty Specification Data • 80 PJS Tables and Functions • 86 Placement Commands • 163 Placement Examples • 118 Placing Components On Existing Segments • 116 Plant Coordinate System • 23 Plotting • 290 Preface PDS • vii Process & Instrumentation Diagram (P&ID) •3 Process Flow Diagram (PFD) • 2 Processing Reports • 248 Project • 230 Project Control Database • 41, 295 Project Engineer HVAC (PE-HVAC) • 10 Project Organization • 15, 229 Project Setup • 12, 122, 292

R Reasoning • 22 Recommended Working Units - English • 20 Recommended Working Units - Metric • 21 Reference Data • 75 Reference Data Manager (PD_Data) • 6 Reference Data Setup • 122 307

Index Reference Database • 69 Report Format File • 249 Report Manager (PD_Report) • 10 Report Output • 248, 263 Report Record • 247 Report Types • 248 Reporting Process • 245 Restore View of Piping Model Command • 215 Review Data • 165 Review P&ID Drawing Details Command • 211 Review/Revise Commands • 148 Revise Data • 165 Revising Linked Models • 195 Revision Commands • 164 Row • 251

S Sample Format Files • 254 Sample Interference Report Format File • 257 Sample MTO Format (piping_g.fmt) • 264 Sample MTO Output • 266 Sample MTO Report Format Files • 254 Sample P&ID Consistency Check Report Format File • 257 Sample Project Control Report Format Files • 257 Sample Spec Report Format Files • 256 Secondary Commands • 149 Seed Files • 122 Segment Data Comparison Report • 199 Segment Vertex Commands • 164 Select P&ID by Line ID Command • 207 Select P&ID Drawing by Nozzle Command • 209 Selecting Options • 131 Setting Up a System to Support Interference Detection • 235 Single/Dual Ownership of Clashes • 233 SmartPlant P&ID to PDS Piping Data Transfer • 183 Spec Access • 94 Specific Physical Data Modules • 108 Specific Tables • 115 Standard Note Library • 89 Sub-Symbol Processor • 106 308

Symbol Processors • 105 System Setup • 12

T Table Access • 103 Tap Properties Data • 82 Temperature Pressure Table • 96 Test the SmartPlant Connection • 189 The Batch Job Input File • 288 The Intergraph Interface to ISOGEN • 286 The ISOGEN Interface • 289 Thickness Equations • 98 Thickness Table • 97 Transfer by Equipment Number and Nozzle Number • 178 Transferring Piping Data • 185 U Understanding Design Areas and Volumes • 230 Understanding Implied Items • 268 Understanding Interference Checking • 237 Understanding Interference Envelopes • 236 Understanding Interference Plotting • 242 Understanding Interference Reporting • 243 Understanding Report Files and Records • 246 Update by Node Number • 178 Update From Active P&I Drawing • 179 Update Segment Data from P&ID • 177 Using Labels in Drawing • 301 V View Windows • 129 Volume Filter • 232 W Weight code • 103 What are the 2D modules? • 2 What are the 3D modules? • 4 What Happens When I Place a Component? • 91 What Happens When I Report On a Component? • 258 What is the Plant Design System? • 1 Working in Three Dimensions • 16 Working Units • 19 Plant Design System 3D Theory

PDS 3D Theory Guide

Recommend Documents