Pds Isogen

(1)

Plant Design System (PDS)

ISOGEN

Version 2011 (V12)

June 2011

(2)

Copyright

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 and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) 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

Terms of Use

Use of this software product is subject to the End User License Agreement ("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 number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or 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 is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

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.

(3)

Plant Design System (PDS) ISOGEN

3

4 Plant Design System (PDS) ISOGEN

Create Drawing ... 66 Revise Drawing ... 70 Delete Drawing ... 80 List Drawings ... 83 Utilities ... 85

Interpreting the HITS Report - PD_ISO ... 125

Example HITS Report - PD_ISO ... 125

Section 1: Basic Input Data and Raw Design File Data - PD_ISO ... 129

Section 2: Design File Data Sorted by Coordinate - PD_ISO ... 130

Section 3: Tracing Data - PD_ISO ... 131

Section 4: Design File Data Sorted by Topo - PD_ISO ... 131

Section 5: Design File Data in IDF Order - PD_ISO ... 138

Using the HITS Report to Solve Problems - PD_ISO ... 143

The Options File - PD_ISO ... 145

File Structure ... 146

ISOGEN_OPTIONS_BLOCK ... 147

INTERGRAPH_OPTIONS_BLOCK ... 149

The Files Table ... 187

USER_DEFINED_WELDS ... 188 WELD_PREFIX ... 189 DETAIL_SKETCH_FACILITY ... 190 PIPELINE_HEADER ... 191 ATEXT_SPECIFICATIONS ... 196 INGR_ATEXT_SPECIFICATIONS ... 197 LINE_ID_DEFINITION ... 198 TYPE_1_LABELS ... 199 TYPE_2_LABELS ... 202 TYPE_3_LABELS ... 204 START_POINT_NOTES ... 206 END_POINT_COMPONENT_LABELS ... 208 NOZZLE_NOTE ... 209 PRIMARY_ORIENTATION_NOTE ... 210 SECONDARY_ORIENTATION_NOTE ... 211 DOTTED_SYMBOLOGY_CODE_LIST_VALUES ... 212 NOMTO_CODE_LIST_VALUES ... 213 SHOP_FABCAT_CODE_LIST_VALUES ... 214 OFFSHORE_FABCAT_CODE_LIST_VALUES ... 215 MOVABLE_TEXT... 216 NEW_SYMBOL_KEYS ... 219 GENITM_NOTE_FORMAT ... 219 ALTERNATE_DESCRIPTION_INDEX ... 220 USER_DEFINED_IMPLIED_ITEM_BOM ... 221 USER_DEFINED_GENERATED_ITEM_BOM ... 224 USER_DEFINED_COMPONENT_BOM ... 226 NON_DIMENSIONED_SUPPORTS ... 228

User-Defined BOM / Material Control File ... 229

User-defined MTO - Related Information ... 230

(5)

Plant Design System (PDS) ISOGEN

5

Operating Requirements ... 232

Material List Definition (MLD) File ... 232

User-Defined Material Control File (.bom file) ... 233

Offshore Material Category ... 235

Transferring Components Between Sort Groups ... 235

Generating an Optional Format for Length Output ... 236

Bolt Units (size x length) ... 236

Generating a Revised Format of the Cut List ... 237

Welds in the Material List ... 238

Style for Fabricated (Pulled) Bends Output ... 238

Style for Material List Output ... 239

Positioning the Title Block ... 239

MLD File Content ... 239

MLD File Format Guidelines ... 241

Style 3 Material List ... 242

Example User-defined Material List - Style 2 ... 244

Example User-defined Material List - Style 3 ... 244

Creating Seed Files for Extraction ... 247

Creating an Isometric Seed File ... 247

Creating a Plot Request File ... 248

IPLOT Plot Request Files ... 249

Mapping Attributes to the Title Block ... 251

SEGMENT_DATA_TABLE ... 252

DRAWING_DATA_TABLE ... 255

SHEET_DATA_TABLE ... 260

Creating a Notes Table ... 263

Using the isoc.note File ... 264

The MTO Neutral File Record Map ... 265

COMMON_RECORD_DATA ... 266

COMPONENT_ATTRIBUTES ... 269

IMPLIED_ITEMS ... 272

GENERATED_ITEMS ... 275

The PDS-to-ISOGEN Symbol Map ... 277

The PDS Item Name ... 278

The ISOGEN Symbol Name ... 278

The ISOGEN Record Number ... 279

Number of Connect Points ... 279

Tapped Component Name ... 279

Tapped elbows ... 279

Olets attached to fittings ... 280

Tapped Component Record Number ... 280

PDS Valve Operator Name ... 280

End Prep Low and End Prep High ... 281

(6)

6 Plant Design System (PDS) ISOGEN

The Valve / Operator Table ... 283

Repeatability ... 285

Repeatability - Related Information... 285

Repeatability Restrictions and Limitations ... 285

Extraction Information in the Database ... 286

Extraction Information in the Project Database ... 286

Extraction Information in the Design Database ... 287

Determining the Traversal Start Point ... 287

Determining Sheet Split Points ... 288

Correcting Incorrect Splits ... 288

Determining Spool Split Points ... 288

Welds ... 289

Weld Enhancements - Related Information ... 290

Delivered weld symbols ... 290

Dotted Weld Symbols ... 291

User-defined Weld Symbols ... 291

Codelist Values for Standard Note 180 and 1100 ... 291

Weld Types and Mapping ... 292

Offshore Fabrication Category ... 292

Unique Weld Numbering ... 292

User-defined Weld Prefix ... 293

The Weld Summary Report ... 293

Weld Definition File Format ... 293

Example WDF File ... 296

Welds Listed in the Bill of Materials ... 297

Dimensioning and Coordinate Output ... 299

Coordinate and Dimensioning Features - Related Information ... 299

Dimensioning Features ... 300

Coordinate Features ... 301

Detail Sketch and Information Note Facility ... 303

Detail Sketch/Information Note Facility - Related Information ... 304

Detail Sketch Entries in the DDF ... 304

Information Note Entries in the DDF ... 305

Dynamic Detail Sketch ... 305

Weight Display ... 307

Weight Display - Related Information ... 307

Center of Gravity Calculation ... 307

Isometric Presentation ... 309

Isometric Presentation - Related Information ... 310

PIPELINE-ATTRIBUTES ... 310

PIPELINE-ATTRIBUTES-SPECIAL ... 311

PIPELINE-ATTRIBUTES-DOTTED ... 312

BEND/ELBOW-REPRESENTATION ... 312

(7)

Plant Design System (PDS) ISOGEN

7

FITTINGS-SPECIAL ... 314 FITTINGS-UNDIMENSIONED-BRANCHES ... 315 MISC-ITEMS ... 316 LAYER-NAMES ... 316 Program Defaults ... 317

Example Drawing Definition File ... 317

Isometric Types ... 321

Appendix: Warning and Error Messages ... 323

Intergraph Interface to ISOGEN... 323

Information Messages ... 323

Warning Messages ... 325

Error Messages ... 331

ISOGEN ... 336

ISOGEN message file errors ... 336

Design File Interface Error Messages ... 343

Batch Extraction Software Error Messages ... 344

Appendix: Alias ISOGEN Tables ... 353

Tables of Intermediate File Records ... 353

Record Identification Numbers ... 356

Option Switches ... 357 Option Switches 02-06 ... 359 Option Switch 8 ... 362 Option Switch 9 ... 364 Option Switches 10-19 ... 365 Option Switches 20-29 ... 367 Option Switches 30-38 ... 372 Option Switch 39 ... 373 Option Switch 40 ... 376 Option Switch 41 ... 377 Option Switch 42 ... 378 Option Switches 40-49 ... 379 Option Switches 60-65 ... 381 Option Switches 67 - 72 ... 383 Option Switch 73 ... 383 Option Switch 74 ... 385 Option Switch 75 ... 386 Option Switches 76 - 79 ... 388 Option Switches 80 - 89 ... 389 Option Switches 90-99 ... 392 Option Switches 100-109 ... 393 Option Switches 110-119 ... 395 Option Switches 120-140 ... 397 Symbol Keys ... 399 Caps (SKEYs) ... 400 Couplings (SKEYs) ... 401 Crosses (SKEYs) ... 401

Elbows and Bends (SKEYs) ... 402

Fixed Length Pipes (SKEYs) ... 404

(8)

8 Plant Design System (PDS) ISOGEN

Inline Filters (SKEYs) ... 405

Instruments (SKEYs) ... 406

LJSE Type Flanges (SKEYs) ... 408

Miscellaneous Items (SKEYs) ... 408

Miscellaneous Pipe Components (SKEYs) ... 409

Olets (SKEYs) ... 410

Operators (SKEYs) ... 411

Other End Connections (SKEYs) ... 412

Reducers (SKEYs) ... 412 Tees (SKEYs) ... 414 Traps (SKEYs) ... 415 Unions (SKEYs) ... 415 Valves (SKEYs) ... 415 Vents (SKEYs) ... 417 Welds (SKEYs) ... 417 What is AText ... 417

Using Alternative Text ... 418

Grouping of ATexts Listings ... 420

Appendix: Example Documents ... 447

Options File (#/dat/isoc.def) ... 447

Label Library Label Definitions ... 453

HITS Report (.h file) ... 466

Intermediate Data File (.idf file) ... 475

Interface Error Log (.err file) ... 498

MTO Neutral File (.b# file) ... 501

ISOGEN Message File (.msg file) ... 503

ISOGEN Printed Parts (.prt file) ... 503

ISOGEN Component vs Sheet Number File (.sed file) ... 506

ISOGEN Cut Pipe Report (.cut file)... 507

Title Block Table (.bit, .seg and .dwg files) ... 507

Appendix: PDS Database Table Formats ... 511

Piping Design Database Table Format ... 511

Specification/Material Reference Database Table Format ... 519

Appendix: ISOGEN® SKEY Dimensions ... 523

Index ... 571

(9)

Plant Design System (PDS) ISOGEN

9

This document provides command reference information and procedural instructions for the Plant Design System (PDS) ISOGEN 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 - PDS Project Setup Technical Reference

 DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide  DPDS3-PB-200026 - Pipe Supports Modeler Reference Guide

 DPDS3-PB-200028 - Piping Design Graphics (PD_Design) Reference Guide  DPDS3-PB-200030 - Project Administrator (PD_Project) Reference Guide  DPDS3-PB-200033 - Project Engineer HVAC (PE-HVAC) Reference Guide  DPDS3-PB-200034 - Reference Data Manager (PD_Data) Reference Guide  DPDS3-PB-200035 - 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 Project Creation 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 - PDS Reference Data Auditing Tool  DPDS3-PE-200048 - Pipe Supports Explorer Utility  DPDS3-PE-200050 - Batch Services Quick Start Guide  DPDS3-PE-200051 - Batch Services User's Guide

Preface PDS

(10)

(11)

Plant Design System (PDS) ISOGEN

11 What's New in PDS ISOGEN (PD_Iso)

The following changes have been made in PDS ISOGEN. Version 2011 (V12)

 A new setting has been added for Intergraph option switch 75. A value of 2 has been implemented to allow reporting of length for flanged pipe on the bill of materials of the isometric drawing. For more information, see INTERGRAPH_OPTIONS_BLOCK (on page 149). (P2 PB: 49254)

 Iso File Option toggle has been added to Define Project Options to allow ISOGEN to override the settings of ISOGEN O.S. 71 in the option file. For more information, see Define Project Options (on page 62).

 New utility to check for SMART ISOs. (CR PB: 113205)

 Added Size and System Commodity codes to *.b* file. (CR PB:117372)  Added support for option 71=18 (smart dgn). (CR PB:111065)

 Added option to report both commodity codes on Iso. (CR PB:96668)  Depict multi-end prep pipes and components. (CR PB:8848)

 Flanged Pipe now reported in length with flanged pipe graphic. (CR PB:24963)  Increased Max Number of Components to 1200. (CR PB:37096)

 Added Ingr Option Block switch to option 75 - flanged pipe. (CR PB:49254)

 Added ability to use symbol keys 'FPGL' & 'FPPF' for fixed length pipes. (CR PB:61658)  Added Mixed End Prep Representation for Record 101 pipe. (CR PB:71868)

(12)

(13)

Plant Design System (PDS) ISOGEN

13 S

E C T I O N

1

The PDS Isometric Extraction Software creates piping isometric drawings from 3-D piping models created by the PDS modeling packages.

The software consists of two principal components:

Introduction to ISOGEN

(14)

14 Plant Design System (PDS) ISOGEN

 ISOGEN, which draws the piping isometric and places it in a MicroStation design file, and  Intergraph 3-D software packages which create input for ISOGEN and perform other functions

necessary in final drawing creation.

The software allows you to extract isometrics from a 3-D plant model: single isometrics interactively or multiple isometrics in a batch mode.

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 couple a material control system with Intergraph's 3-D modeling software.

The above features are collectively referred to as software customization and are dealt with at length in this document. You will find reference information needed for customization in the appendices.

(15)

Plant Design System (PDS) ISOGEN

15 Overview of Isometric Extraction

This section outlines the software components and how they are organized for interactively extracting isometrics.

The Intergraph Interface to ISOGEN

The core software module in isometric extraction (both interactive and batch) is the ISOGEN interface. This program reads data from the 3-D 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, 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 data file or idf) and therefore what appears in the final drawing. Once this data is read in, the interface collects from the model files all of the components that make up the piping network. Data from the components

(16)

16 Plant Design System (PDS) ISOGEN

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) and records are generated in the idf. The order of the records in the idf is in the order of the network traversal. Drawing notes and other features such as bill of materials 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. See the section Interpreting the HITS Report for more information. The HITS report can help you to find problems in the piping model and tell you when the interface software is not working properly.

ASCII to Binary Conversion

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

ISOGEN takes the binary input file and generates graphics in an 2D MicroStation design file. The graphics consist of the completed isometric drawing. ISOGEN can also generate several

nongraphic outputs, including:  An ISOGEN MTO neutral file  A parts list (bill of materials)  A cut pipe report

 A component VRS sheet number file

The parts list file contains the same bill of materials that is shown on the isometric drawing. It is possible to turn the drawing bill of materials off and attach the printed ASCII file to the 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.

(17)

Plant Design System (PDS) ISOGEN

17 S

E C T I O N

2

The PDS 3D software supports a variety of applications. All the supported applications use a common interface that is controlled by the PD Shell program. This ensures consistency across applications and minimizes the amount of time required to learn the product.

The PDS 3D modules provide a simple user interface through extensive use of forms. The modules also provide an on-line Help capability for easy access to information while working in the product.

The PDS 3D software uses available nucleus tools such as MicroStation and FORMS. It supports standard software such as NFS, NQS, and RIS required to set up data across a network. This design facilitates the use of non-PDS tools such as relational databases and third party software. The PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraph's Network Licensing System.

PD Shell

The PD Shell program provides access to the various functions that are associated with the PDS 3D Modules. You can access the Plant Design System Environment form by clicking Start > All Programs > PD_Shell > PD_Shell. This executes a control script that defines all of the

environment variables that are needed to run the product, and it identifies the location of the product files. These files can be located on the workstation or a server on the network. See pds.cmd for more information on this file. The script also activates the Plant Design System Environment form.

(18)

18 Plant Design System (PDS) ISOGEN

To make colors easier to read on flat screens and projectors, a zip file with modified color for PDS forms is delivered as alternatecolorfb.zip.

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

Schematics Environment — Provides access to the PDS 2D modules that are used to create and modify piping and instrumentation diagrams, process flow diagrams, and instrumentation database records.

Equipment Modeling — Provides access to the Equipment Modeling module, which provides an interactive graphics environment that is used to create and revise equipment model graphics and database information.

FrameWorks Environment — Provides access to the FrameWorks module, which provides an environment that is used to create and revise structural models, create and revise structural drawings, and propagate structural models.

Piping Designer — Activates an interactive command environment that is used to create piping and in-line instrumentation in the model; revise existing model graphics and database information; and verify the integrity of the data in the model.

Electrical Raceway Environment — Provides access to the Electrical Raceway module, which provides an interactive environment that is used to create and revise raceway models and access raceway utilities.

Piping Design Data Manager — Provides access to a set of options that are used to verify the integrity of the graphic and database information that is associated with a model.

Piping Model Builder — Enables you to create piping graphics from a nongraphics environment. This module is used with PD_Design to create an accurate 3D model of the piping network. Pipe Support Designer — Activates an interactive command environment that is used to create pipe supports in the model, and revise existing pipe support model graphics and database information.

(19)

Plant Design System (PDS) ISOGEN

19

Pipe Stress Analysis — Activates a set of forms that are used to extract information from piping models for input to third-party pipe stress analysis products.

Interference Manager — Activates a set of forms that are used to check for interferences among project models and to control approved interferences.

Isometric Drawing Manager — Activates a set of forms that are used to extract isometric drawings from piping models and to review or plot the created isometric drawings.

Drawing Manager — Activates a set of forms that are used to create and manipulate drawings and drawing views; provide access to the interactive graphics environment for drawings; and provide access to a plot manager and vector hiddenline manager.

DesignReview Integrator — Activates a set of forms that are used to extract information to form label files for use in SmartPlant Review and to review data from a SmartPlant Review session. Report Manager — Activates a set of forms that are used to create and revise report format files and report on information in a project including Material Take-Off reports.

Project Administrator — Provides access to a set of forms that are used to create a project, create and revise project files, define project seed data, and control the project.

Reference Data Manager — Provides access to a set of forms that are used to control the reference data for a project including Piping Job Specification data, Graphic Commodity Data, Alphanumeric Commodity Data, Standard Note Library, Label Description Library, and Piping Assembly Library.

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

If access control has been defined, you must key in a valid user ID as defined by your system manager to gain access to the projects. Refer to Access Control Manager, page 467, for more information on using access control.

If access control has not been defined, no entry is required for this field. Password — Key in the password for the specified user ID.

Project List Field — Displays the defined projects for the network and allows you to select the active project. The system lists all the defined PDS projects (2D-only, 3D-only, and 2D & 3D). An error is displayed if you select an option that is incompatible with the active project. For example, if the active project is a 2D-only project, you cannot access the Interference Manager module. If access control has been defined, only those projects for which you have some level of access are displayed.

Message Area — Displays prompts and messages that are associated with the active process. Error messages are displayed in red.

PD_Shell Form Conventions

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

Selecting Options

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

(20)

20 Plant Design System (PDS) ISOGEN

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

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

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

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

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

Common Tools on the PD Shell Forms

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

Standard Commands

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

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

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

The Top button exits the active form and returns control to the top form of the active branch.

The Cancel button cancels or exits from the active form. Control returns to the immediately preceding form in the hierarchy.

The Accept button accepts a selection or operation. Depending on the active form or option, the active form remains active so that you can repeat a similar operation or control returns to the preceding form. The Restart button clears any key-in fields on the form that have values you can modify.

Scrolling List

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

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

(21)

Plant Design System (PDS) ISOGEN

21

You can also select the slider and, while pressing <D>, slide the button

up or down the bar. The items scroll through the window as you move the button. The size and position of the button on the scroll bar is an indication of the number of lines and the relative position within the list. All commands that display a list of design areas or models order the list alphanumerically by the design area number or model number in ascending order.

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

Command Purpose

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

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

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

Display-List Boxes A display-list box is located at the end of some key-in fields. It lets you select data from a list instead of keying in information. For example, there is a display list associated with the

Authorization key-in field shown. At the end of the field, there is a small box with horizontal dashes. When you select this display list box with the screen cursor, an associated list of valid input values displays. Select an item from the list to enter its value into the field.

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

(22)

22 Plant Design System (PDS) ISOGEN

Shift Left and Shift Right

buttons

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

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

Roll-Through List A roll-through list shows one choice at a time of a list that can be several items long. Place a data point on the roll-through list to scroll through the available options. The option displayed is active. Standard Window Icons When using this software in the CLIX environment,

you can press <D> along the edge of a form or any area not occupied by a button, key-in field, or other gadget, to display a box of icons. You can

manipulate form windows just like any other workstation window.

The following list defines the available window icons.



Collapse/Restore



Repaint



Pop-to-bottom



Modify/Resize



Pop-to-top



Restore Size

Batch Processes

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

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

When you submit a batch process the system sends an e-mail message to the mail path of the default login reporting the job's completion status and any error log information. The batch process e-mail functionality is optional.

(23)

Plant Design System (PDS) ISOGEN

23 S

E C T I O N

3

This section explains how to execute the software that generates isometrics interactively. You can extract only a single isometric at a time using the interactive modules. Also, this mode of extraction is intended primarily for testing purposes. Many extraction facilities are not available using interactive extraction.

You must have access to an existing PDS Piping model that contains a completed pipeline before an isometric can be generated.

Operator Sequence

1. After accessing the PDShell form, select a project from the scroll area.

The system highlights the project.

Select the Isometric Drawing Manager button to enter the ISOGEN environment.

Interactive Isometric Extraction

(24)

24 Plant Design System (PDS) ISOGEN

The system displays the Plant Design - Isometric Extraction form and prompts: Initializing

Project Control Database. Also, the active project name is displayed in the field located in the

upper left portion of the form.

2. Select the Interactive button.

(25)

Plant Design System (PDS) ISOGEN

25

3. If you know the information, key-in the appropriate Model Numbers and Line Names and

proceed to step 10. Otherwise, continue with this procedure. 4. Select the Select Model Numbers button.

The system displays an Interactive Isometric Extraction form that lists all of the piping and

equipment models within all of the areas from the active project.

5. Select the models from the scroll area that contain the lines that are to be extracted. OR

Select the Select All button to select all of the areas and models listed in the scroll area. OR

Select the Reset Selection button to cancel all of the previous model selections. Up to eight models can be selected for extraction.

6. Once all of the appropriate models have been selected, select accept.

The system returns to the initial Interactive Isometric Extraction form.

If necessary, you can select the Reset Model Numbers button to clear selections in the Model Number and Line Name fields.

(26)

26 Plant Design System (PDS) ISOGEN

The system displays an Interactive Isometric Extraction form that lists all of the lines

contained in the selected models. There may be a slight delay while the system searches for

the selected lines.

8. Select the line names from the scroll area that are to be extracted. OR

Select the Select All button to select all of the lines listed in the scroll area. OR

Select the Reset Selection button to cancel all of the previous line selections.

Up to eight lines can be selected for extraction. All lines to be extracted must be connected in the piping model. For more information about extractions using pipeline names, see Pipeline Names (on page 31).

9. After all of the appropriate lines have been selected, select the accept button to return to the initial Interactive Isometric Extraction form.

The system returns to the initial Interactive Isometric Extraction form with the selected

models and pipeline names in their respective fields.

(27)

Plant Design System (PDS) ISOGEN

27 The system also generates an iso design file name based on the first pipeline name and places

it in the Iso Design File field.

If necessary, you can select the Reset Line Names to clear selections in the Line Name fields. You can also select the Reset Model Numbers button to clear selections in the Model Number and Line Name fields.

10. Iso Output Node:Path

Select the Iso Output Node:Path field and key in the nodename:path where the ISOGEN output files will be stored. The default is set to nodename:/login directory.

 The key-in fields: Iso Output Node:Path, Iso Options File and Iso Seed Design File will accept a network address.

 Each should be entered as nodename:drive:\directory path\filename for example: 111jn:C:\win32app\ingr\dat\defaults.dat.

 To change the default settings for the Iso Output Node:Path field, edit the ISOPATH export statement.

 Edit the pds.cmd file located in ~\pdiso\bin. For example, a typical ISOPATH export statement in the pds.cmd file might be:

$ENV{'ISOPATH'}='PDSNT:C:\users\iso\isofiles\\'; 11. Iso Design File

Select the Iso Design File field and key in the ISOGEN design file. By default, the first pipeline name is displayed with a .iso extension.

The .iso extension will generate multi-sheet isometrics into a single design file. Replacing the .iso extension with a .i* extension allows the software to generate multi-sheet isometrics into separate design files where the * will be replaced with a number.

(28)

28 Plant Design System (PDS) ISOGEN

For example, if the model in the Interactive Isometric Extraction form was changed to 400104wc.i*, the resulting design files would be 400104wc.i01, 400104wc.i02,, etc. This procedure will allow you to take advantage of ISOGEN's plotting capabilities as described in the section Plot Isometric Drawing.

The most recently processed iso, displayed in the Iso Design File, becomes the first selection on the list of available isos when the Plot or View Graphics command is selected.

12. Iso Options File

Select the Iso Options File field and key in the nodename:path where the ISOGEN options file is located.

If you key in an options filename and the file does not exist, an error message is displayed at the bottom of the form.

The options file contains switches, options and tables that drive the Intergraph interface to ISOGEN. This file allows you to customize isos to your standard practice.

The default is set to nodename:/pathname. The default value is delivered in the options file and can be altered by exporting the ISOOPTION variable.

13. Iso Seed Design File

Select the Iso Seed Design File field and key in the nodename:path where the ISOGEN seed design file is located.

If you key in a seed filename and the file does not exist then an error message is displayed at the bottom of the form.

The iso seed design file is a 2-D design file that is copied to create an empty design file into which the isometric is drawn by ISOGEN.

The default is set to nodename:/path name/iso seed file. The default value is determined when the ISOSEED export variable is defined.

To change the default settings for the Iso Options File and Iso Seed Design File fields, edit the ISOSEED and ISOOPTION export statements in the PDS.CMD file. The following are examples of typical ISOSEED and ISOOPTION export statements as they would appear in the defaults.dat file.

export ISOSEED=$ENV{'ISOSEED'} = 'pdssrv:D:\proj\iso\ref\isoc.sed' export ISOOPTION=$ENV{'ISOOPTION'} =

(29)

Plant Design System (PDS) ISOGEN

29

14. Select the accept button to accept the information displayed in the form and to initiate the iso

extraction process.

The system displays the message Creating ISOGEN Intermediate File and then Creating

ISOGEN Isometric. When the process is complete, the system displays the PD ISOGEN

Status form.

The ISOGEN Status form displays processing information, warning messages and error messages. Use the scroll bar and buttons to scroll through the information displayed on the

(30)

30 Plant Design System (PDS) ISOGEN

status form. Error Messages appendix provides detailed descriptions of each error and warning message.

15. To plot an isometric drawing using the Plot button, refer to Plot Isometric Drawing (on page 33).

16. To view an isometric drawing using the View Graphics button, refer to View Isometric Drawing (on page 34).

Extraction Criteria

The following sections contain information specific to defining extraction criteria which must be defined prior to initializing an isometric extraction. The following extraction criteria are covered in this section:

 Model Files (on page 30)  Pipeline Names (on page 31)

 Generation by Line Name Substring (see "Extraction by Line Name Substring" on page 31)

 Generation by Line ID (see "Extraction by Line ID" on page 32)  Iso Design File (on page 32)

Model Files

Key in the names of the PDS Piping, Equipment Modeling and/or Pipe Support files that should be considered for iso extraction. Up to eight model numbers can be input. Equipment model numbers must be specified in order to generate nozzles on the isometric.

The first model number entered is treated as the primary file and therefore must be a Piping model. Any RDB data accessed during iso extraction is obtained from the primary model (through its type 63 data).

The RDB data that is accessed by the Iso Extraction Software and that must be properly attached to the primary file includes:

 Specification Material Database  Graphic Commodity Library  Physical Dimension Library  Piping Job Spec Tables Library  Standard Notes Library

 Material Descriptions Library

 Specialty and Instrument Descriptions Library  Label Description Library

 Miscellaneous data stored within the model itself

If the model number that you specify does not exist, the software displays an error message at the bottom of the form. Press <RETURN> to proceed.

If the model number is invalid, the software displays the message Error Retrieving Model and the fully expanded filename is displayed in the input field.

(31)

Plant Design System (PDS) ISOGEN

31

A filename is considered invalid if it does not exist in the project database.

Pipeline Names

Key in the pipe lines that are to be extracted into a single iso. Up to 8 lines can be specified. The lines you specify must be connected together in the Piping Model files. That is, these pipelines must be a network of piping segments. In order for the lines to be connected, the segments that form those lines must also be connected. You cannot specify multiple disconnected piping sections (such as, vessel trim piping).

Pipelines can be identified for extraction in two ways: extraction by line name substring and extraction by line id (see the section Conventions and Limitations). The method you use depends upon the options selected and set in the iso extraction options file. Refer to The Options File (see "The Options File - PD_ISO" on page 145) for more information.

For each method, you identify the network of piping to extract by specifying piping segment attributes. Piping segments usually correspond only to sections of piping and NOT to an entire piping system (unless the line is trivial).

Extraction by Line Name Substring

When extracting by line name substring you should key in any substring of the full PDS line name that uniquely identifies the pipeline you want to include in the iso. This is the default way of identifying pipelines to extract as defined in the LINE_ID_DEFINITION section of the defaults.dat file.

Example 1:

If the line name is 6IN-OWS10111-1C0031 then a substring that you might use to identify this line is OWS10111.

You probably would not want to use 1C0031 since it is the spec name component of the line name and would probably identify more than one line in the model. Likewise, you would probably not want to use 6IN-OWS10111, since you may want to extract sections of the line that are not 6" NPD or because multiple 6" sections are connected together by sections that are not 6".

Do not extract by line name substring if lines that are similarly named exist together in the models that you are extracting from. This situation exists, for example, when the substring you want to use is also a substring of another line name.

Example 2:

If the line that you want to extract is 8IN-OWS1011-1C0031, and you use the substring OWS1011, you are also specifying that you want to extract 6IN-OWS10111-1C0031 because OWS1011 is a substring of OWS10111.

To ensure that you are extracting the correct line:

 specify a larger substring of the line name for the line you want to extract.

In the case above, that larger substring may be -OWS1011-. By including the dashes the substring specified is no longer a substring of 6IN-OWS10111-1C0031.  specify the line ids of the lines you want to extract. Refer to Extraction by Line ID (on page

(32)

32 Plant Design System (PDS) ISOGEN

Extraction by Line ID

When extracting by line ID you key in the line ID of the lines that you want to extract. The line ID is a user defined collection of database attributes that can be used to refer to pipelines by other than their line names.

To extract by line ID, you must select the proper option in the Options File AND you must know the line ID definition as specified in the options file (refer to LINE_ID_DEFINITION (on page 198) for information on defining the line ID). To extract a line by its line ID, key in the attributes that make up the line id and separate them by dashes.

Example 3:

One simple definition of the line ID might be fluid code followed by line sequence number. This definition allows you to refer to the line without the NPD or spec name components the line name. Thus, OWS-1011 will refer to line 6IN-OWS1011-1C0031 while OWS-10111 will refer to line 8IN-OWS10111-1C0031.

When specifying the line ID of a line to extract, both the embedded dashes and the ORDER of the attributes is important. Thus in the example above, neither OWS1011 (because the dash is missing) or 1011-OWS (because the order is incorrect) would suffice if the line ID is defined as fluid code followed by line sequence number.

The difference between extracting by line ID and extracting by line name substring is that pipeline sections that are extracted are identified by EQUALITY of the line ID attributes rather than by SUBSTRING of the line name attribute. This method of identifying lines avoids the problems that can occur with line name substrings (provided that the line id definition is sufficient to uniquely identify pipe lines).

Iso Design File

Key in the name of the output isometric design file. This file need not exist prior to running the software. If the file does exist, the software replaces it with a new file when the current iso is extracted.

To specify that each isometric sheet is to be drawn in its own design file, you can insert an asterisk (*) as a wild card character in the output iso filename. When a wildcard character is inserted in the filename, the software replaces it with a digit as each iso sheet is generated. If more than 9 sheets are generated then the letters a - z are used for replacement of the wildcard.

You may also use an asterisk (*) in the output file name's extension. If you do this, the asterisk is replaced by two digits. For example, if you key in test.i*, sheet 1 will be in file test.i01, sheet 2 will be in test.i02, and so on. Because file names cannot have more than 14 characters, the iso design file name is truncated to a maximum of 14 characters.

Using more than one fixed character together with an asterisk is not recommended. MicroStation requires that all design file names be in lower case.

If an invalid iso filename is keyed in, an error message is displayed in the message field. The name portion of this file specification (excluding any wild card character) is used by the software to name several other files that are generated at the same time as the isometric model number. These include:

 The Intermediate data file - iso name + .idf  The Hits file - iso name + .h

 The Intergraph mto neutral file - iso name + sheet no. + .b# (where: # is the number of times the line has been extracted)

(33)

Plant Design System (PDS) ISOGEN

33

 The ISOGEN mto neutral file - iso name + .bom

 The ISOGEN message file - iso name + .msg  The ISOGEN printed parts list - iso name + .prt

 The ISOGEN component vrs sheet file - iso name + .sed  The ISOGEN cut pipe report - iso name + .cut

These files are all generated in the Iso Output Node:Path unless they are switched off by option selections (refer to The Options File (see "The Options File - PD_ISO" on page 145) for more information). Their contents are discussed in more detail in the sections entitled Options File and Isometric Seed File.

The Plot Isometric button allows you to choose one or several generated isometric files for plotting.

1. To plot an isometric drawing, select the Plot button from the Interactive Isometric Extraction form.

The system displays the Interactive Isometric Extraction form.

2. Select one of the queues from the Queue Name pull down list.

The queues displayed in the Queue Name field are chosen first from the queues defined in the pdiso_plot portion of the queue_descript file (located in the project directory). If no queues are defined in the queue_descript file, the system generates a Queue Name list from locally defined queues.

If locally defined queues are used, only the pipe queues that are defined will be displayed in the Queue Name pull down list. To display local device queues, create a pipe queue that points to the device queue.

3. Select the Plot Copies field and key in the number of copies that will be plotted.

4. Select the Iso Seed Plot File field and key in the nodename:path where the seed plotting parameters file exists. The default is defined in the ISOPLOT export variable. For more information on defining ISOGEN export variables, see Initial Setup Considerations (on page 49).

(34)

34 Plant Design System (PDS) ISOGEN

An example plot parameter file is delivered, but it should be modified before it can be used or a print queue called laser must exist. For more information on modifying the plot queue, see Creating Seed Files for Extraction (on page 247) .

5. Select the subdirectories that contain the drawings you want to plot. Select each subdirectory individually from the Sub-Directories field.

The system highlights the selected subdirectories.

OR

Select the Select All Sub-Directories button to select all of the available subdirectories. OR

Select the Reset Selected Sub-Directories to cancel any of the previously made selections. 6. Once you have defined a list of subdirectories, select the Display Iso Drawings button. 7. The system searches the previously defined list of subdirectories and displays a listing of the

available drawings, their creation dates and the subdirectories to which they belong. 8. Select an isometric drawing(s) to plot. Use the scroll bar and buttons to view all available

drawings. OR

Select the Select All button to select all of the listed drawings for plotting.

The system highlights the selected drawing(s).

OR

Select the Reset Selections button to cancel any of the previously made selections. 9. Submit Batch Immediately/Delay Submit Time toggle

Select the Submit Immediately option to run the job immediately.

Select the Delay Submit Time to specify a run time for the job. Define the run time by keying in the day of the week (Mon, Tues, etc.), the time and then select AM or PM.

10. Select the accept button to accept the selected drawings for plotting.

The system submits the selected drawing(s) to the plotter. As each drawing is processed, the

messages Processing Drawings and Selected Drawings Submitted to Plotter appear in the

message field.

View Isometric Drawing

The View Isometric Drawing button allows you to view generated graphics in the MicroStation environment. If you are unfamiliar with the MicroStation working environment, refer to the MicroStation Reference Guide for more information.

1. To view an isometric drawing, select the View Graphics button from the Interactive Isometric Extraction form.

(35)

Plant Design System (PDS) ISOGEN

35 The system searches the Iso Output Node: Path (as defined earlier in the Interactive

Isometric Extraction) and displays the Interactive Isometric Extraction form.

2. Select the subdirectories that contain the drawing you want to view. Select each subdirectory individually from the Sub-Directories field.

The system highlights the selected subdirectories.

OR

Select the Select All Sub-Directories button to select all of the available subdirectories. OR

Select the Reset Selected Sub-Directories to cancel any of the previously made selections. 3. Once you have defined a list of subdirectories, select the Display Iso Drawings button.

The system searches the previously defined list of subdirectories and displays a listing of the

available drawings, their creation dates and the subdirectories to which they belong.

4. Select an isometric drawing to view. Use the scroll bar and buttons to view all available drawings.

The system highlights the selected drawing.

(36)

36 Plant Design System (PDS) ISOGEN

The system displays the message Initializing MicroStation in the message field and displays

the isometric drawing. MicroStation will automatically attach the bar and panel menus.

6. Select the exit button to exit the MicroStation environment and return to the View Isometric Drawing form.

Conventions and Limitations

Some situations that occur commonly can be handled in more than one way by the iso extraction software. To deal with these, a set of conventions, described below, has been adopted. Other situations that can arise simply cannot be handled by the extraction software as it is currently written.

Extraction Conventions

This section describes the following list of extraction conventions: Olet Type Branches (on page 37)

End-Point Components (on page 37)

Implied Materials at Line Name Changes (on page 37) Pipe Supports (on page 37)

(37)

Plant Design System (PDS) ISOGEN

37 Olet Type Branches

Olet type branch components (such as olets, branch-welds, and occasionally half couplings) can be owned by the header or branch pipeline in the 3-D model. By convention, when this type of branch is extracted, the branch component is assigned to the header pipeline. Thus, when the branch line is extracted, the branch component will be drawn dotted, no-mto and it will not appear in the BOM. However, you can specify that the branch component is assigned to the branch line. This depends on the position of the Header/Branch toggle on the Piping Data Control Form (accessed through Project Administrator). For more information on the Piping Data Control Form, see the section entitled Piping Data Control in the PD Project Administrator Reference Guide.

It is NOT necessary that the piping segment in the model, under the branch component, have the same line name as the header.

End-Point Components

When a pipeline in the model changes name at a multi-connect point component then that component is "owned" by more than one line. When this occurs, the component is always assigned to the pipeline attached to connect point 1 of the component. For example, if three different lines come together and join at a tee, the tee component will extract onto, and show up in the B.O.M. of, the line at connect point 1 of the tee. When the other two lines are extracted, the tee will show up as dotted, nomto and will not appear in the B.O.M. (Notice that it is NOT necessary that piping segments in the model be "broken" in any way to achieve the above result.)

Implied Materials at Line Name Changes

When a pipeline name changes at a flanged connection, the bolts and gaskets generated at that point may be assigned to either of two lines. In this situation, the bolts and gaskets are assigned to the flange having the higher east, north and elevation coordinate. This arbitrary assignment prevents the implied materials from being generated twice. (It is possible to override this assignment; refer to the PDS Piping Design Graphics Reference Guide for details.)

Pipe Supports

Pipe supports in the 3-D model may be attached anywhere along the length of a pipe except at either of the end-points. They may also be attached to the origin (connect point 0) of any component as well as to a component tap. You may have multiple supports connected to a component origin, but there should be at most one support attached to a component tap. When a support is connected to a tap, there must NOT be any other piping attached to the component at that tap. In general, supports should NOT be located at component connect points other than as outlined above. The one exception to this rule is that supports may be located at the same point as an olet branch (or branches) along a length of pipe.

(38)

38 Plant Design System (PDS) ISOGEN

Type 63 Information

Type 63 data is read from the first model entered on the form for Interactive Extraction. When using Batch Extraction, Type 63 data is read from the first piping model in the area specified in each record of the batch input file.

Standard Note Codelist Values

When isometric drawings are extracted, codelisted attributes are generally resolved into the appropriate values on the iso. However, the codelist values for standard_note_no_a and

standard_note_no_b (Piping Notes) are not resolved on the iso, because of the potential length of the text strings involved. Instead, the number of the standard note from codelist 499 (Piping Notes) is displayed on the iso in a TYPE_2_LABEL. For more information on codelists and standard notes, please refer to the Reference Data Manager Reference Guide.

Extraction Limitations

This section describes the following list of extraction limitations: Branch Nesting (on page 38)

System Isometrics (on page 38)

Tapped Piping Components (on page 38) Flanged Pipe (on page 39)

Branch Nesting

There is a limitation on the branch nesting depth that a pipeline may have. The first branch off from a line is level 1. If this branch in turn has a branch, then that branch would be level 2. ISOGEN will currently handle pipelines that contain up to twenty levels of branching. If a pipeline contains more than twenty nested branches, the extraction will fail. This limitation effectively limits the size of the largest system type isometric that can be extracted. This generally does not pose a problem for single pipeline fabrication type isometrics. Note, that the ISOGEN interface identifies a traversal sequence that minimizes the number of nested branches in most cases.

System Isometrics

Spool Numbering is not supported for system-type isometrics.

Tapped Piping Components

ISOGEN requires that traversal of a pipeline never enter a component through a tap. Rather, in traversing the line, ISOGEN requires first traveling through a component and then traversing "out" the tap. It is possible to create a pipeline in the 3-D model that would require the ISOGEN interface to illegally traverse into a tap. You can avoid this situation by NOT joining components through taps. For example, a segment of pipe that begins at a component tap should not end at a tap on different component. If this situation cannot be avoided, change the line name somewhere and extract the network in two sections.

Other limitations having to do with tapped components include: (1) Elbows and pipe bends must not have more than one tap. It is possible to create a model where an elbow is tapped more than once, but this configuration will not extract. (2) Tapped tee's cannot be extracted using ISOGEN when the components are joined through taps.

(39)

Plant Design System (PDS) ISOGEN

39 Flanged Pipe

Purchased length or fixed length FPIPE reports on the iso BOM as a quantity rather than a length of pipe.

Taps that are placed on flanged pipe will not extract.

Refer to Intergraph option 72 for settings that impact flanged pipe.

When a line name change or sheet break occurs between a flange and a bolt-thru component, bolt length reports may not be accurate. The accuracy of a bolt length report is based on how the system scans the line and also the exact location of the break point. This limitation exists because ISOGEN only receives information for the first continuation item at a sheet break.

It is recommended that sheet/line breaks not be made between flanges on thru-bolted

components. If a break must be placed between thru-bolted components, the correct bolt length can be generated if the attribute change is made at CP2 of either flange (the non-bolted end).

(40)

(41)

Plant Design System (PDS) ISOGEN

41 S

E C T I O N

4

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.cmd. 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. These parameters can be modified as needed.

In order to run batch isometrics, the pd_iso.cmd file, located in ~\pdiso\bin, 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 three variables are read from the Windows registry:

 PD_SHELL  PD_ISO

(42)

42 Plant Design System (PDS) ISOGEN

 PD_ISOGEN

Pds Isogen

Plant Design System (PDS)

ISOGEN

Plant Design System (PDS) ISOGEN

3

Contents

4

Plant Design System (PDS) ISOGEN

Plant Design System (PDS) ISOGEN

5

6

Plant Design System (PDS) ISOGEN

Plant Design System (PDS) ISOGEN

7

8

Plant Design System (PDS) ISOGEN

Plant Design System (PDS) ISOGEN

9

List of PDS Documentation

Preface PDS

Plant Design System (PDS) ISOGEN

11

What's New in PDS ISOGEN (PD_Iso)

Plant Design System (PDS) ISOGEN

13

S

E C T I O N

1

Introduction to ISOGEN

14

Plant Design System (PDS) ISOGEN

Plant Design System (PDS) ISOGEN

15

Overview of Isometric Extraction

The Intergraph Interface to ISOGEN

16

Plant Design System (PDS) ISOGEN

ASCII to Binary Conversion

ISOGEN

Plant Design System (PDS) ISOGEN

17

S

E C T I O N

2

PD Shell

18

Plant Design System (PDS) ISOGEN

Plant Design System (PDS) ISOGEN

19

PD_Shell Form Conventions

Selecting Options

20

Plant Design System (PDS) ISOGEN

Common Tools on the PD Shell Forms

Standard Commands

Plant Design System (PDS) ISOGEN

21

22

Plant Design System (PDS) ISOGEN













Batch Processes

Plant Design System (PDS) ISOGEN

23

S

E C T I O N

3

Operator Sequence

The system highlights the project.

Interactive Isometric Extraction

24

Plant Design System (PDS) ISOGEN

The system displays the Plant Design - Isometric Extraction form and prompts: Initializing

Project Control Database. Also, the active project name is displayed in the field located in the

upper left portion of the form.

Plant Design System (PDS) ISOGEN