Pds Isogen
Short Description
DGETRETR...
Description
Plant Design System (PDS) ISOGEN
Version 2011 (V12) June 2011 DPDS3-PB-200017H
Copyright Copyright © 1984-2011 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 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.
Contents Preface PDS ................................................................................................................................................. 9 What's New in PDS ISOGEN (PD_Iso) ................................................................................................ 11 Introduction to ISOGEN ............................................................................................................................ 13 Overview of Isometric Extraction .......................................................................................................... 15 The Intergraph Interface to ISOGEN .............................................................................................. 15 ASCII to Binary Conversion ............................................................................................................ 16 ISOGEN .......................................................................................................................................... 16 PDS Environment ...................................................................................................................................... 17 PD Shell ................................................................................................................................................ 17 PD_Shell Form Conventions .......................................................................................................... 19 Batch Processes ............................................................................................................................. 22 Interactive Isometric Extraction ............................................................................................................... 23 Extraction Criteria.................................................................................................................................. 30 Model Files ..................................................................................................................................... 30 Pipeline Names .............................................................................................................................. 31 Iso Design File ...................................................................................................................................... 32 View Isometric Drawing ........................................................................................................................ 34 Conventions and Limitations ................................................................................................................. 36 Extraction Conventions................................................................................................................... 36 Extraction Limitations ..................................................................................................................... 38 Batch Software Organization ................................................................................................................... 41 The Batch Job Input File ....................................................................................................................... 43 Line Processing (pdsidf) ....................................................................................................................... 44 The ISOGEN Interface .......................................................................................................................... 45 ISOGEN - PD_ISO (Batch Software Organization) .............................................................................. 45 Splitting the MTO neutral file (MSPLIT) .......................................................................................... 45 Generating Title Block Input (TBLOCK) ................................................................................................ 46 Filling in the Title Block (STIB) .............................................................................................................. 46 Plotting .................................................................................................................................................. 46 Updating the Project Database (pdsidf) ................................................................................................ 46 Making a Run Log Entry (pdsidf) .......................................................................................................... 46 Investigating Batch Extraction Problems .............................................................................................. 47 Batch Isometric Extraction ....................................................................................................................... 49 Initial Setup Considerations .................................................................................................................. 49 Basic Workflow for Running Batch Isometrics ...................................................................................... 52 Batch Isometric Generation .................................................................................................................. 54 Define Default Sets ......................................................................................................................... 57 Define Project Options.................................................................................................................... 62 Revise Iso Area .............................................................................................................................. 65 List Iso Areas .................................................................................................................................. 66
Plant Design System (PDS) ISOGEN
3
Contents 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 Types of Material List .......................................................................................................................... 230
4
Plant Design System (PDS) ISOGEN
Contents 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 Order of Table Entries ......................................................................................................................... 281
Plant Design System (PDS) ISOGEN
5
Contents 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 FITTINGS-GENERAL ......................................................................................................................... 313
6
Plant Design System (PDS) ISOGEN
Contents 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 Flanges (SKEYs) .......................................................................................................................... 404
Plant Design System (PDS) ISOGEN
7
Contents 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
8
Plant Design System (PDS) ISOGEN
Preface PDS 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
Plant Design System (PDS) ISOGEN
9
Preface PDS
10
Plant Design System (PDS) ISOGEN
Preface PDS
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)
Plant Design System (PDS) ISOGEN
11
SECTION 1
Introduction to ISOGEN 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:
Plant Design System (PDS) ISOGEN
13
Introduction to 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.
14
Plant Design System (PDS) ISOGEN
Introduction to ISOGEN
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
Plant Design System (PDS) ISOGEN
15
Introduction to 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.
16
Plant Design System (PDS) ISOGEN
SECTION 2
PDS Environment 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
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.
Plant Design System (PDS) ISOGEN
17
PDS Environment 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.
18
Plant Design System (PDS) ISOGEN
PDS Environment 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 .
Plant Design System (PDS) ISOGEN
19
PDS Environment 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 or key for the data to be entered into the system. You can also press or to move through a set of key-in fields. Delete --- If you make a mistake while keying in text, press the 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.
20
Plant Design System (PDS) ISOGEN
PDS Environment You can also select the slider and, while pressing , 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 . 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
Plant Design System (PDS) ISOGEN
21
PDS Environment 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 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.
22
Plant Design System (PDS) ISOGEN
SECTION 3
Interactive Isometric Extraction 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.
Plant Design System (PDS) ISOGEN
23
Interactive Isometric Extraction 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.
The system displays the Interactive Isometric Extraction form.
24
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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. 7. Select the Select Line Names Within Models button.
Plant Design System (PDS) ISOGEN
25
Interactive Isometric Extraction 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.
26
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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.
Plant Design System (PDS) ISOGEN
27
Interactive Isometric Extraction 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'} = 'pdssrv:D:\proj\iso\ref\isoc.def'
28
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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
Plant Design System (PDS) ISOGEN
29
Interactive Isometric Extraction 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).
See Also Extraction Criteria (on page 30) Iso Design File (on page 32) Plot Isometric Drawing (on page 33) 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 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.
30
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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).
See Also Extraction by Line Name Substring (on page 31) Extraction by Line ID (on page 32)
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) for more information.
Plant Design System (PDS) ISOGEN
31
Interactive Isometric Extraction
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) The error message file - iso name + .err
32
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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).
Plant Design System (PDS) ISOGEN
33
Interactive Isometric Extraction 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.
34
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction 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. 5. Select the accept button to accept the selected drawing for viewing.
Plant Design System (PDS) ISOGEN
35
Interactive Isometric Extraction 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.
See Also Extraction Conventions (on page 36)
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) Type 63 Information (on page 38)
36
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction
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. If these guidelines are not followed, the line may not extract.
Plant Design System (PDS) ISOGEN
37
Interactive Isometric Extraction
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.
38
Plant Design System (PDS) ISOGEN
Interactive Isometric Extraction
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).
Plant Design System (PDS) ISOGEN
39
Interactive Isometric Extraction
40
Plant Design System (PDS) ISOGEN
SECTION 4
Batch Software Organization 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
Plant Design System (PDS) ISOGEN
41
Batch Software Organization
PD_ISOGEN
See Also The Batch Job Input File (on page 43) Line Processing (pdsidf) (on page 44) The ISOGEN Interface (on page 45) ISOGEN - PD_ISO (Batch Software Organization) (on page 45) Generating Title Block Input (TBLOCK) (on page 46) Filling in the Title Block (STIB) (on page 46) Plotting (on page 46) Updating the Project Database (pdsidf) (on page 46) Making a Run Log Entry (pdsidf) (on page 46) Investigating Batch Extraction Problems (on page 47)
42
Plant Design System (PDS) ISOGEN
Batch Software Organization
The Batch Job Input File The input to the batch procedure is an ASCII data file generated by the Batch Environment called the Batch Job Input File.
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 and revision block data that was entered into the BATCH form. Each option is separated from the others by at least one space. This record contains 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 model 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 1 to indicate that it has been processed. The drawing records can be repeated any number of times in the batch job input file. Each time Accept is selected, from the Create Batch Job Input form, a set of drawing records is written to the batch 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.
Plant Design System (PDS) ISOGEN
43
Batch Software Organization
Line Processing (pdsidf) 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. Type 63 information is read from the first piping model in the area specified in each record of the batch input file. Note that this model may not be the piping model which contains the pipeline being extracted. The two files produced are different from the ones produced for interactive extraction. In pdsidf.dat, the first line name in the 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. skiso5 skiso4 skiso6 skiso7 *skiso3 40eqp01 40eqp00 pdssk:h:\proj\iso\isofiles\380105wc.i* 380105\skiso\1 proj N Y Y N * * Y * * 04-Aug-1998 * 13 1 0 In SEED.DAT, the seed iso design file name is followed by records containing the plot request file name, the output file directory, the output iso file name, extraction number and number of sections. pdssk:h:\proj\iso\ref\isoc.def pdssk:h:\proj\iso\ref\isoc.sed pdssk:h:\proj\iso\ref\isoc_sml.i pdssk:h:\proj\iso\isofiles 380105 13 1.fi
44
Plant Design System (PDS) ISOGEN
Batch Software Organization
The ISOGEN Interface The ISOGEN interface performs the same function in batch extraction as in interactive extraction: generation of the 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. The contents of each of the title block tables file is controlled by a corresponding table in the title block tables file map. The SEGMENT_DATA_TABLE produces a file with the file extension of .seg, the DRAWING_DATA_TABLE produces a file with the extension of .bit and the SHEET_DATA_TABLE produces a file with the extension of .dwg. The title block text files are only produced if the appropriate option is set in the Intergraph options block. Some of the entries in the DRAWING_DATA_TABLE can only be produced when PDSIDF.DAT contains the extra inputs that appear in the file for batch extraction. A title block record map set up for use with batch extraction might not generate a correct output file if it is generated by running the interactive software.
ISOGEN - PD_ISO (Batch Software Organization) As in interactive extraction, in batch extraction, the program ISOA_BGEN must be run immediately prior to IZOD2 in order to convert the ASCII IDF to binary. IZOD2, the ISOGEN image which produces the iso, can then be run to generate the isometric drawings. 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*, and so 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.
Splitting the MTO neutral file (MSPLIT) After IZOD2 runs and creates the sheet data file, Intergraph's MSPLIT executable splits up the mto neutral file so that a separate neutral file is created for each sheet of the drawing. The sheet data file consists of sheet numbers followed by Intergraph database occurrence numbers. MSPLIT assigns each neutral file record to a particular sheet by matching occurrence numbers in the sheet data file with the occurrence number on each record in the mto neutral file. MSPLIT will not work if you have not mapped the Intergraph occurrence anywhere in the neutral file record. MSPLIT is executed by passing the mto neutral file name (without the file extension) and the extraction number as inputs in a foreign command line. Therefore, if the mto file name is test.b and the extraction number for the drawing is 10, the input parameter to MSPLIT would be formed as test 10. MSPLIT then looks for files test.b and test.sht as the input files. The current assignment for the exported variable ISOOPTION is used to obtain the mto neutral file map name. The mto neutral file map must be read so that the field containing the occurrence number can be located in an mto record. When output files are generated by MSPLIT, the output file name contains the extraction number and sheet number. For example, for sheet 2, extraction number 10, the output file name would be test2.b10.
Plant Design System (PDS) ISOGEN
45
Batch Software Organization
Generating Title Block Input (TBLOCK) In the same way that MSPLIT assigns a neutral file record to each sheet in an isometric, Intergraph's TBLOCK assigns segment data to a sheet for the segment data summary. TBLOCK assigns records in the .seg file (produced by the PD_ISO interface) to each sheet. It then sorts the records for each sheet and eliminates duplicates. Finally, TBLOCK assigns each data item in the record a text node number and sends it as output to a new file, which is input to STIB. TBLOCK is also executed by passing the input in a foreign command line. The only input in this case is the isometric file name. The input files are then determined by name plus .seg and name plus .dwg. The title block map name is obtained by reading the options file assigned to ISOOPTION.
Filling in the Title Block (STIB) After all of the input for each sheet has been determined, the executable that actually places text in the drawing title block is run. Intergraph's STIB associates text in an input file with text nodes placed in the design file.
Plotting After drawings are created in batch they can be plotted. You can use IP_IPLOT plotting software. To submit a plot, the batch software submits a job 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.
Updating the Project Database (pdsidf) After a line has been successfully extracted, the project database is updated. The extraction number and date are updated each time a drawing is completed, while the revision block is only updated if you chose to update it in the Create Batch Job Input form when you create the batch job input file.
Making a Run Log Entry (pdsidf) Making an entry into the run log is the last activity performed. The run log file name is formed using the file name of the batch job input file together with the file extension .job. An entry in the log file consists of the drawing spec (piping area plus line name), an error code, a status message, and the date and time that the run completed. This is the same information given to you in a MAIL message when an error occurs.
46
Plant Design System (PDS) ISOGEN
Batch Software Organization
Investigating Batch Extraction Problems Since there are many steps involved in the generation of a completed isometric, there are many ways for the process to fail. When a problem occurs and drawing generation fails, you should follow a systematic procedure to determine the cause of the problem and, if needed, call Intergraph support and log the problem. All files will reside in the isoerr subdirectory in the specified output path location. Here is a suggested procedure: 1. Check the run log (.job file) to get the status code and message. If there is no code or message, the batch procedure itself probably failed or was aborted. In this case, go to Step 4. 2. Consult Appendix A for an explanation of the error determined in Step 1. The explanation of the error might be enough to enable you to resolve it easily. If not, then the explanation should narrow down the possibilities to a certain extraction facility or a certain area within the batch procedure. For example, it could be that the ISOGEN interface failed or that ISOGEN failed. 3. Check for error message files (.err). Sometimes the cause of an error is reported more specifically in the error log. For example, if the ISOGEN interface fails, it might be that the line did not exist in the model. This fact would be reported to you in the error message log. The .err file contains a note in the files list located near the top of the file. This note indicates which file was read for type 63 data. If any of the type 63 data which could affect the iso (for example: MTO Options, Design Monuments, etc.) has been changed, verify that the changes have been made to the file that is being read by PD_ISO. 4. Check the log file for the batch run. Occasionally, error messages are displayed here and are not reported in the error log file. Also, if an error occurs or some module stack dumps, those conditions will be reported in this log. 5. Rerun the line with the DEBUG and VERIFY options enabled. If the above steps do not lead to a resolution of the problem, use the DEBUG and VERIFY options to generate a detailed log file for the run. These options will also cause log files to be generated for the plotting jobs in case there is a problem with plotting. If you cannot determine the cause of the problem, the detailed log and any other pertinent files will need to be sent to Intergraph for an analysis of the problem.
Plant Design System (PDS) ISOGEN
47
Batch Software Organization
48
Plant Design System (PDS) ISOGEN
SECTION 5
Batch Isometric Extraction This chapter describes how to set up and use the ISOGEN interface software for generating isometrics in a batch process. Batch generation of isometrics is intended to be the primary means for generating production drawings on a project. Interactive extraction is intended primarily for testing the PDS interface to ISOGEN and ISOGEN itself. Using batch Isometric extraction, you can Generate multiple drawings in a single job Automatically fill out the drawing title block Automatically submit the completed drawing to the plotter. Everything that is needed to extract an isometric (except for line name) is stored in the Project Control Database at the piping area level. The following are types of area information that can be found in the Project Control Database: Area name Equipment Area Continuation Area User-defined information. Within an iso area, any number of isometric drawings can exist. The following are types of drawing information that can be found in the Project Control Database: The pipeline names that are included in the drawing Revision block data Extraction dates User-defined information. The Project Control Database helps you manage the isometrics produced on a project. For example, you can use the Project Control Database to keep track of when lines need to be extracted and to record and report on drawing issue dates.
See Also Initial Setup Considerations (on page 49) Basic Workflow for Running Batch Isometrics (on page 52) Batch Isometric Generation (on page 54)
Initial Setup Considerations The following procedure outlines the basic steps you should follow to use the batch extraction facility.
Create a batch options file Set up an options file to be used for batch extraction. For information on modifying the options file, see Define Default Sets (on page 57). As part of this set-up, you should also create a Title Block Map that is used in generating title block information. For more information on the Title Block Map, see Mapping Attributes to the Title Block (on page 251).
Plant Design System (PDS) ISOGEN
49
Batch Isometric Extraction Create border and extraction seed files Create the design files that will contain your isometric drawing border and a seed file that will be copied once for each iso produced. The seed file will contain text nodes in the drawing title block. During the extraction process, the software attaches text strings to these nodes so that the title block is automatically filled out. The border file is attached to the seed file as a reference file. Refer to Creating Seed Files for Extraction (on page 247) and Mapping Attributes to the Title Block (on page 251) for details on setting up these files.
Set export variables Set the export variables that define drawing border location and other information that used in various areas of the software for batch extraction. ISOGEN environment variables are defined in the PDS.CMD file. The following is a list of user-defined export variables.
ISOPATH $ENV{'ISOPATH'} = 'node:drive:directory path\'; The exported ISOPATH value is loaded by default into the output path directory slot on the Add Default Set form. It is also used as a default for the output location, Iso output node:Path, when extracting an interactive isometric.
ISOOPTION $ENV{'ISOOPTION'} = 'node:drive:directory path\isoc.def'; The exported ISOOPTION value is loaded by default into the Options File field on the Add Default Set form. It is also used as a default for the options file, Iso Options File, when extracting an interactive isometric.
ISOSEED $ENV{'ISOSEED'} = 'node:drive:directory path\isoc.sed'; The exported ISOSEED value is loaded by default into the Seed File field on the Add Default Set form. It is also used as a default for the seed design file, Iso Seed Design File, when extracting an interactive isometric.
ISOPLOT $ENV{'ISOPLOT'} = 'node:drive:directory path\isoc_sml.i'; The exported ISOPLOT value is loaded by default into the Plot File field on the Add Default Set form. It is also used as a default for the plot parameters file, Iso Seed Plot File, when plotting an interactive isometric.
ISOBORDER $ENV{'ISOBORDER'} = 'node:drive:directory path\isoc.brd'; The exported ISOBORDER value is loaded by default into the Border File field on the Add Default Set form.
ISOBATCH $ENV{'ISOBATCH'} = 'node:drive:directory path\isobat\';
50
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The exported ISOBATCH value is loaded by default into the Batch Job Input File field on the Create Batch Job Input form.
ISOREPORT $ENV{'ISOREPORT'} = 'node:drive:directory path\isorpt'; The exported ISOREPORT value is loaded by default into the Output File field on the Batch Data Reports form.
ISOBATCHQUE $ENV{'ISOBATCHQUE'} = 'PDisovreate'; The exported ISOBATCHQUE value is loaded by default into the Process Queue field on the Schedule Batch Job form.
ISO_ASCII_LOAD $ENV{'ISO_ASCII_LOAD'} = 'node:drive:directory path\isoascii'; The exported ISO_ASCII_LOAD value is loaded by default into the Filename field on the Bulk Load Lines From ASCII File form.
PDISOFONT $ENV{'PDISOFONT'} = 'XX'; The defined font must be a mono-spaced font. The exported font PDISOFONT value defines the font that will be used on the output isometric, both on the body of the iso, and on the MTO on the face of the iso. The defined font must be a mono-spaced font. The delivered font style is 50. Special characters will have some limitations in displaying the font in ISO drawings. For example, the @ (at sign) and ^ (circumflex) characters have limitations. Irrespective of the font being used, the '@' character will result in a 'space' inserted in the drawing in the respective place. However, the '^' character gives different results depending on the font being used. If PDISOFONT=50, ^ is resulted as a degree symbol in the output. If PDISOFONT = 32 is used, the '^' character displays as it is.
SYMDGN, SYMNDX and SYMLIB $ENV{'SYMDGN'} = 'node:directory path\symbol.dgn'; $ENV{'SYMNDX'} = 'node:directory path\symbol.ndx'; $ENV{'SYMLIB'} = 'node:directory path\symbol.lib'; The exported values SYMDGN, SYMNDX and SYMLIB are loaded into the Symbol Design Node:File, Symbol Index Node:File and Symbol Library Node:File fields respectively on the Isometric Symbol Editor form.
ISOUSRREFDIM Variable and Pointing to a Specific FW+ ASCII File This variable overrides the setting for the data file used in generating isometric drawings with references to gridlines or structural columns. $ENV{'ISOUSRREFDIM'}='node:directory path\filespec.dat'; Where: filespec.dat is the name of the gridline reference data file. For example: $ENV{'ISOUSRREFDIM'}='pdsserv1:e:\proj1\project\fw_bldg_a.dat';
Plant Design System (PDS) ISOGEN
51
Batch Isometric Extraction Intergraph option 71 must be enabled before data in the filespec.dat file can be referenced. The following rules apply when using the ISOUSRREFDIM variable: If the variable is set and points to the proper location of a valid gridline reference data file, the file will be used for placing structural references on the isometric drawing. If the ISOUSRREFDIM variable is set incorrectly (for example, typos in the UNCpath or filespec), references are not displayed on the isometric drawing. If the ISOUSRREFDIM variable is not set in the pds.cmd file, gridline dimensions are extracted from the fw_projname.dat file by default. Overriding the default reference dimension file can be useful in situations where a line passes between two buildings and you want to force the dimension from a specific building rather than using the closest dimension point. See Generate FrameWorks Reference Dimension File (on page 107) for more information on the FrameWorks Dimension File.
The MicroStation uconfigure.dat file To avoid problems while using the batch extraction feature, edit the MicroStation configure.dat file and comment out the command line which generates the uconfig.dat file. #do user configure.dat(uconfigure.dat #[ -f $MS_DIR/cfg/uconfigure.dat ] && . $MS_DIR/cfg/uconfigure.dat The problem can occur when a uconfigure.dat file, generated for one project, overrides another project's export statement. This causes the isometric extraction to fail when areas, models, and lines cannot be located.
Basic Workflow for Running Batch Isometrics Define default setups Using the information from pre-defined export variables, define a default setup. A default setup contains the network address, directory and file specification for each of the following: options file seed file plot parameters file output path border file Exported information can be overwritten. For more information on defining a default set, see Define Default Sets (on page 57).
Select project options Select the project options that define values throughout the project. These options include: Iso Name Option - sets the convention for naming iso design files. Drawing Number Option - sets the convention for defining drawing names. Project Default Set - defines the set that is used in bulk load and generating isos Output Path Option - uses the area name in defining the output directory path for isos. The area name is appended to the output path assigned in the default set as sub-directory. For more information on defining project options, see Define Project Options (on page 62).
52
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Add drawings to the newly created iso area For each pipeline that you wish to extract in batch you must first create a drawing. A single piping area will normally contain many drawings; usually one per each pipeline in the design files that comprise the area. When a drawing is created, define the name(s) of the pipeline(s) to be associated with the drawing, the output design filename and drawing number. The data stored for the piping area together with the data stored for a drawing provide all the same inputs you supply when using interactive extraction. In either method, the drawing must be defined matching the format defined in the LINE_ID_DEFINITION section of the options file. You can add drawings to a piping area by either keying in the data or downloading data from an existing model. If data from an existing model is used to define a drawing, the drawing can be created automatically. For more information see Utilities (on page 85).
Generate a Batch Job Input File A Batch Job Input File specifies run options and drawings/line names for isometric generation. When the batch job finishes, the Batch Job Input File can be either be deleted or edited so that it can be resubmitted. For more information on generating a batch job input file, see Create Batch Job Input (on page 109).
Batch Processing Considerations To achieve optimum performance of Piping Isometrics in batch mode, it is necessary to understand how PD_ISO processes a batch job. As the PD_ISO software begins processing in batch mode, it creates an empty MicroStation design file in a temporary directory on the processing machine. Then, a number of piping and equipment models are attached as reference. The quantity of attached models is based on the setting of Intergraph option 60 and the continuation areas as defined through the Batch Isometric environment.
Initiate the Batch Job The batch job is initiated by submitting the Batch Job Input File. A batch job can be submitted either immediately or scheduled for a later time. For more information, see Schedule Batch Job (on page 117).
Figure 1: Initial Workflow for Running Batch Isometrics
Plant Design System (PDS) ISOGEN
53
Batch Isometric Extraction See Also Define Default Sets (on page 57) Define Project Options (on page 62) Revise Iso Area (on page 65) Create Drawing (on page 66) Revise Drawing (on page 70) Delete Drawing (on page 80) List Drawings (on page 83) Utilities (on page 85) Create Batch Job Input (on page 109) Schedule Batch Job (on page 117) Reports (on page 120)
Batch Isometric Generation This section explains how to execute the software that generates isometrics in batch mode. You must have access to an existing PDS Piping model that contains a completed pipeline before an isometric can be generated. Operator Sequence 1. Select a project from the project display field.
The system highlights the project. 2. Select the Isometric Drawing Manager button to enter the extraction environment.
54
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The system displays the Plant Design - Isometric Extraction form and prompts: Initializing Project Control Database. The active project name is also displayed in the field located in the upper left portion of the form.
3. Select the Batch button from the Isometric Extraction form.
The system activates the Batch Environment form.
Plant Design System (PDS) ISOGEN
55
Batch Isometric Extraction 4. Select Option Select one of the appropriate options from the Batch Environment form. Define Default Sets
adds, revises, deletes or copies an isometric extraction default set(s). For more information, see Define Default Sets (on page 57).
Define Project Options
defines a project setup from user-defined default sets, a format for the Iso Name option and the Drawing Number Option, and sets an optional path (by area name) for ISOGEN output. For more information, see Define Project Options (on page 62).
Revise Iso Area
revises the data associated with an existing area. For more information, see Revise Iso Area (on page 65).
Create Drawing
creates a new drawing and adds it into the Project Control Database. A drawing must be added to the Project Control Database prior to extracting it in batch mode. Each time a drawing is added to the Project Control Database, you define which pipelines in the model are included in the isometric drawing. For more information, see Create Drawing (on page 66).
Revise Drawing
revises single or multiple drawings. For more information, see Revise Drawing (on page 70)
Delete Drawing
deletes single or multiple drawings from an iso area. For more information, see Delete Drawing (on page 80).
List Drawing
lists all of the drawings within an iso area. Each listing includes information such as primary line name (secondary and tertiary are optional), drawing number, batch reference number and iso type. For more information, see List Drawings (on page 83).
Utilities
accesses the utilities menu. The utilities are provided to help simplify the loading of drawings and/or areas. For more information, see Utilities (on page 85).
Create Batch Job generates a batch extraction job file. The batch extraction job file Input consists of your inputs for some batch processing options and a list of all the drawings to be processed in a batch run. For more information, see Create Batch Job Input (on page 109).
56
Schedule Batch Job
schedules or submits a batch job for a previously created batch input file. For more information, see Schedule Batch Job (on page 117).
Reports
generates reports on the data in the Project Control Database. For more information, see Reports (on page 120).
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Define Default Sets The Define Default Sets option allows you to add, copy, revise or delete iso extraction default sets. Default sets are used by the extraction software to determine the location of: Option File Seed File Plot File Extracted Isos Border File 1. Select the Define Default Sets button from the Batch Environment form.
The system displays the Isometric Extraction Default Sets form.
Initially, no default set is defined. The section Add Default Set contains the procedure for add default sets. 2. Select the Add button to add a default set. OR Select an existing default set and either the Revise, Delete or Copy button.
The system activates the selected default set and returns to the Batch Environment form.
See Also Add Default Set (on page 58) Revise Default Set (on page 60) Delete Default Set (on page 61) Copy Default Set (on page 61)
Plant Design System (PDS) ISOGEN
57
Batch Isometric Extraction
Add Default Set 1. Select the Add button from the Isometric Extraction Options Sets form.
The system displays the Add Default Set form.
2. Key in a default set tag name.
The system displays the Network Address, Directory and Specification fields with values as defined by the export variables. For more information on export variables, see Initial Setup Considerations (on page 49).
58
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction 3. Key in a default set description.
4. Key in the appropriate information for each field. Option File The fields associated with the options file define the name and location of the option file to be used. Seed File The fields associated with the seed file define the name and location of the seed file to be used. Plot File The fields associated with the plot file define the name and location of the plot file to be used. Output Path The fields associated with the Output Path fields define the location of the iso extraction files. Border File The fields associated with the border file define the name and location of the border file to be used. OR If the export statements are defined in the control shell, the above fields will be loaded automatically. The following are examples of export statements that can be used in the control shell. export ISOPATH=/usr/wp114b/isocert/ export ISOSEED=/usr/wp114b/isocert/isoc.sed export ISOOPTION=/usr/wp114b/isocert/isoc.def export ISOPLOT=/usr/wp114b/isocert/isoc_sml.i export ISOBORDER=/usr/wp114/isocert/isoc.brd 5. Select the accept button. The system adds the new default set to the database and returns to the Isometric Extraction Default Sets form.
Plant Design System (PDS) ISOGEN
59
Batch Isometric Extraction
Revise Default Set The Revise Default Set command allows you to revise an existing iso default set. 1. Select the Revise button from the Isometric Extraction Options Sets form. 2. Select the default set to be revised from the list of default sets.
The system highlights the default set and displays the Revise Default Set form.
3. Select the appropriate fields and key in the new information. Option File The fields associated with the option file define the name and location of the option file to be used. Seed File The fields associated with the seed file define the name and location of the seed file to be used. Plot File The fields associated with the plot file define the name and location of the plot file to be used. Output Path The fields associated with the Output Path fields define the location of the extracted iso files. Border File The fields associated with the border file define the name and location of the border file to be used. 4. Select the accept button.
The system revises the default set, updates the database, and returns to the Isometric Extraction Default Sets form.
60
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Delete Default Set The Delete Default Set command allows you to delete an iso default set. 1. Select the Delete button from the Isometric Extraction Options Sets form. 2. Select the default set to be deleted from the list of default sets.
The system highlights the default set and displays the Delete Default Set form.
Information displayed on this form is for review purposes only. 3. Select the accept button.
The system deletes the default set and updates the database.
Copy Default Set The Copy Default Set command allows you to copy an iso default set. 1. Select the Copy button from the Isometric Extraction Options Sets form. 2. Select the default set to be copied from the list of default sets.
The system highlights the default set and displays the Copy Default Set form.
Plant Design System (PDS) ISOGEN
61
Batch Isometric Extraction
3. Key in a tag name for the new default set. 4. Key in a description for the new default set. 5. Select the accept button.
The system makes a copy of the selected default set with the new tag and description.
Define Project Options The Define Project Options command allows you to define project options such as Iso Name option, Drawing Number option, project default set and output path option. 1. Select the Define Project Options button from the Batch Environment form.
62
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The system displays the Isometric Extraction Project Options form.
2. Iso Name Option Set the Project Default toggle to either By Line ID or By Area and Line ID. By Line ID refers to the line ID as defined in the options file. By Area and Line ID uses the first character of the area name as a prefix to the line ID. Select the Label Number and key in a label number as it exists in the Reference Data Manager's label description library. For more information on the label description library, refer to the PDS Reference Data Manager document. If a label number is defined, it overrides the Project Default toggle setting as the default for the Iso Name Option. 3. Drawing Number Option Set the Project Default toggle to either By Line ID or By Area and Line ID. By Line ID refers to the line ID as defined in the options file. By Area and Line ID uses the first character of the area name as a prefix to the line ID. Select the Label Number and key in a label number as it exists in the Reference Data Manager's label description library. For more information on the label description library, refer to the PDS Reference Data Manager document. If a label number is defined, it overrides the Project Default toggle setting as the default for the Drawing Number Option. 4. Batch Job Options These toggle switch settings define the default switch settings on the Create Batch Job Input form. Refer to Create Batch Job Input (on page 109) for more information on the following toggles. Delete Existing Files / Save Existing Files Do Not Save Details/Save Previous Details
Plant Design System (PDS) ISOGEN
63
Batch Isometric Extraction Submit for Plotting / Do Not Plot Increment Revision Number/Do Not Increment Revision Number 5. Revision Option - This toggle defines if the revision character is a number or a letter. When set to Alphabetic Revision Number, the revision number is shown as a letter in the order of -1 (no revision), A (revision 0), B (revision 1), C (revision 2), and so forth. The alphabetic revision number is displayed on Iso title block, in the .idf (-8 record), and on different forms in the Batch Isometric Extraction wherever applicable. In the database tables pdtable_185 (No_of_Revision) and pdtable_186 (revision_no), the revision character is always displayed as a numeric. 6. Filename Option toggle The Long Filename Available On NT Only setting allows iso filenames up to 24 characters long. This option can only be used with isos on an NT file server. If you are currently running an upgraded 6.3 project you must modify the DDL and database by performing the procedure as described in ~/pdiso/upd_long.txt file. When set to Short Filename, the software only allows iso names up to 14 characters long. 7. Iso File Option toggle The toggle's default setting, Normal MicroStation V7 Design File overrides ISOGEN to override the settings of ISOGEN O.S. 71 in the option file to work as normal settings of 8008 to generate normal isos. When set to Smart MicroStation V7 Design File, ISOGEN overrides the settings of ISOGEN O.S. 71 in the option file to work as the settings of 18018 to generate smart isometrics. Smart isos have linkages on the graphic elements to provide hot spotting capability on the PDS isos published to SPF. 8. Output Path Option toggle The toggle's default setting, Create Iso Files In Output Path, will output iso files to the main output path. Switched from the default setting, this toggle allows batch extracted isometrics to be output to a subdirectory of the main output path (see Revise Default Set (on page 60) for more information on revising default output paths and other project defaults). The subdirectory is named after the area name for the line that is being extracted. This setting is not unique to each default set, but is a project-wide setting. Interactive extraction will continue to be output in the location defined in the interactive screen. 9. Select a project default set. If a project default set is not selected, the software will fail during the extraction process and the bulk loading lines. 10. Select the accept button.
The system returns to the Batch Environment form.
64
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Revise Iso Area 1.
To revise an iso area, select the Revise Iso Area button from the Batch Environment form.
The system displays the Revise Iso Area form with a list of available piping areas.
2. Select an area from the list of areas. Do not select accept until all revisions have been made. The system highlights the selected area and displays it in the appropriate Area field. 3. Select one of the four display buttons located in the lower portion of the Revise Iso Area form. Available options are: Iso Area List updates forms with a list of available iso areas. Equipment Area List
updates forms with a list of available iso areas.
Continuation Area List
allows you to route a pipeline through multiple piping areas and show line continuation from one area to another. For example, consider a line, P-1000, that runs through areas A and B. Area A should be defined as the continuation area for area B and area B should be defined as the continuation area for area A. You may select an area only for pipeline continuation. See Intergraph Option 60 for information concerning how PD_ISO recognizes Continuation Area Data.
User Data
allows you to define up to ten user data attributes that can be mapped to the title block.
The system displays a list of available areas that correspond to the selected Area List button.
Plant Design System (PDS) ISOGEN
65
Batch Isometric Extraction If the User Data button is selected, the system displays the User Data form. To define user data, select the appropriate user data field, key in the user data and select the accept button. 4. Select an area from the list of areas.
The system displays the selected area in the appropriate Area field. 5. Select the accept button once you have revised the iso area.
The system revises the Iso Area and updates the database.
List Iso Areas This option displays a list of all available iso areas. Select the appropriate area(s) and select accept to confirm the selection(s).
Create Drawing The Create Drawing command allows you to create a drawing and add it to an existing iso area. 1. Select the Create Drawing button from the Batch Environment form.
The system displays the Create Drawing form.
2. Key in a piping area name.
If the contents of the Iso Area field are changed, the system clears all the remaining fields. OR Select the Iso Area List button for a list of available iso areas.
66
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The system displays the List Iso Areas form.
3. Select an iso area from the form. 4. Select the accept button.
The system returns to the Create Drawing form with the selected area displayed in the Iso Area field. 5. Select the Type field gadget and select the appropriate isometric drawing type that will be associated with the newly-created drawing. Refer to the section Isometric Types for more information on Type. 6. Select the Line field and key in the primary line ID, as defined in the LINE_ID_DEFINITION of the options file, of the drawing you want to create. The line ID cannot contain embedded blanks or the backslash character.
The system first checks that the line ID you key in is unique. An error message is displayed if the line ID you key in has already been defined. To view a list of currently loaded drawings, select the Drawing List button to activate the List Drawings form. The drawings are listed according to area and line ID.
Once a valid line ID is entered, the system loads the appropriate information into the Drawing Number and Iso Dgn Name fields. If the Line field is changed, the system clears all the remaining fields. The system displays the drawing number in Drawing Number / Iso Dgn Name. The contents of this field depend upon the drawing number option selected in the Define Project Options form. The system displays the isometric design file name. The design file name is used for naming subsidiary files created during the extraction. The contents of this field depend upon the iso name option selected from the Define Project Options form. 7. Complete the following:
Plant Design System (PDS) ISOGEN
67
Batch Isometric Extraction Line 2 (This field is optional.) Key in a secondary line name. This line name identifies a secondary line that will be included in the drawing. The secondary line must be connected to the line identified by the primary line name. Line 3 (This field is optional.) Key in another secondary line ID. The same restrictions apply to Line 3 as to Line 2. Number of Sections This field is usually left blank. When a line leaves a piping area and then returns at some other point, such that the pipeline in the area exists in multiple disconnected sections, then the number of sections should be specified. This field allows you to treat a disconnected pipeline in the model as one line. Sheet numbering is continuous. For example, if a line exists in two sections of a model and section one generates three sheets and section two generates two sheets, then the sheets from section two will be sheets four and five of the line.
This option should not be used to extract lines that are not intentionally disconnected. A line may or may not extract if you attempt to use this field to extract a pipeline not modeled correctly. The next three fields can be used as search criteria when creating batch job input. For more information on batch jobs and search criteria, refer to Create Batch Job Input (on page 109). Batch Reference (The batch reference number is optional.) Key in a batch reference number. The batch reference number allows you to group drawings within the isometric environment. If batch reference numbers are supplied, you can later specify, for example, to extract all drawings in a given area with a given batch reference number. Model Status Key in the model status code. The user-defined model status code helps keep track of drawing status. The following is a list of example codes: N - Line has not been modeled M - Line has been modeled but not checked C - Line has been modeled and checked A - Drawing has been extracted and approved R - Line has been revised since last approved If model status codes are defined in this field, they can be used later when generating a batch job input file. For example, you could designate that all lines in a given area be extracted with a given model status. Model Revised Date Key in a date with the format DD-MMM-YYYY. This date indicates when the lines comprising the drawing have been revised. The Model Revised Date field allows you designate for extraction, all lines that have been revised since the last drawing revision. Extraction Number The system displays the last extraction number for the drawing. The extraction number is incremented by one each time the drawing is extracted. This field could be mapped to a text node near the extraction date text node (see the description of the Extraction Date field). The extraction number helps distinguish between two drawings generated on the same day.
68
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Extraction Date The system displays the last extraction date for the drawing. The extraction date is automatically updated by the system when batch isometrics extraction occurs. This field should be mapped to a text node that lies just outside of the drawing border. This will help indicate when the drawing was generated. Last MTO Date The system displays the date that an MTO neutral file was last generated for the drawing. The MTO date is automatically updated by the system whenever an mto neutral file is generated along with the isometric drawing. Sheets Generated The system displays the number of sheets generated by ISOGEN for the drawing the last time it was extracted. The number of sheets is automatically updated by the system each time the drawing is extracted. Revision block fields Rev By Chk Apv Date Ext Sht Description Each time the revision number is incremented, a new line of data is added to the revision block automatically. Line inputs are specified each time a batch job file is created. Date to Mtl Control Key in a date that indicates when the most recent MTO neutral files were passed to a material control system. This field must be manually updated. Revision Number The system displays the latest revision number of the drawing. The revision number is automatically updated by the system each time a drawing is extracted. When a batch job file is created, you must decide whether or not to increment the revision number during the run. To increment the number, the system increments the field by one. If the Revision Number field is -1, the system assumes that revision zero of the drawing is being generated. 8. After you have completed your inputs to the form, select the accept button.
The system writes the data to the Project Control Database. The Iso Area and Line are the required minimum inputs for the Create Drawing form.
Plant Design System (PDS) ISOGEN
69
Batch Isometric Extraction
Revise Drawing This command activates the Revise Drawing form which allows you to revise single or multiple drawings. You can select either Select by LineId (see "Select Drawings by LineId" on page 71) or Select by Using "Search Criteria" (see "Selecting Drawings Using Search Criteria" on page 72) to open the drawing(s) for revision. 1. Click the Revise Drawing button on the Batch Environment form.
The system displays the Revise Drawing form.
2. To help limit the number of drawings displayed for revision, select the Type field gadget and the appropriate isometric drawing type. 3. Select either the Select Drawings by LineId (on page 71) or Select Drawings by Using "Search Criteria" (see "Selecting Drawings Using Search Criteria" on page 72). Follow the procedures in the appropriate section to select drawings for revision. 4. Select the Accept button.
The system returns to the Revise Drawing form with the selected drawings listed. 5. Select the Accept button and proceed to the section Revising a Single Drawing (on page 75) or Revising Multiple Drawings (on page 78), depending on the number of drawings selected for revision.
70
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Select Drawings by LineId 1. Select the Select By LineId option. 2. Select the Iso Area List button for a list of available iso areas.
The system displays the List Iso Areas form.
3. Select the appropriate iso areas then select the accept button.
The system displays the List Drawings form.
Plant Design System (PDS) ISOGEN
71
Batch Isometric Extraction 4. Select individual drawings with a data point. OR Select all of the listed drawings by selecting the Select All button. OR Cancel all highlighted drawings by selecting the Reset Selections button. 5. Select the accept button.
The system returns to the Revise Drawing form with the selected drawings listed. 6. Select the accept button and proceed to the section Revising a Single Drawing (on page 75) or Revising Multiple Drawings (on page 78), depending on the number of drawings selected for revision.
Selecting Drawings Using Search Criteria 1. Select the Select Using "Search Criteria" option.
The system displays the Search Criteria fields on the Revise Drawing form.
2. To help limit the number of drawings displayed for revision, select the Type field gadget and the appropriate isometric drawing type. 3. Define the search criteria. See Search Criteria (see "Search Criteria for Selecting Drawings" on page 73) for more information.
72
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction 4. Select the accept button and proceed to the section Revising a Single Drawing (on page 75) or Revising Multiple Drawings (on page 78), depending on the number of drawings selected for revision. 5. Select the accept button. The system returns to the Revise Drawing form with the selected drawings listed. 6. Select the accept button and proceed to the section Revising a Single Drawing (on page 75) or Revising Multiple Drawings (on page 78), depending on the number of drawings selected for revision.
Search Criteria for Selecting Drawings The following are search criteria that can be used separately or together to locate a drawing or group of drawings within an iso area. All defined search criteria must be met before a drawing can be included in an isometric extraction. Iso Area Key in the name of the iso area that you want to extract lines from. OR a. Select the Iso Area List button.
The system displays the Iso Areas form.
b. Select the appropriate iso area and click the accept button.
The system returns to the Revise Drawing form with the selected area in the Iso Area field.
If you want to restrict the list further, you must supply additional criteria such as batch reference numbers and drawing numbers. An iso area must be selected before any other search criteria can be defined.Batch Reference
Plant Design System (PDS) ISOGEN
73
Batch Isometric Extraction Key in the batch reference number of the lines you want to extract.
74
To use batch reference numbers as criteria, specify them in individual drawing records when adding drawing records to the Project Control Database. Model Status Code Key in the status code if you want to restrict a list to all lines of a given status. Drawing Number Low / Drawing Number High These commands define, by drawing number, the range of lines to retrieve. Key in a drawing number in each field to identify the range of lines to extract. OR a. Activate a cursor in the Drawing Number Low (or High) field by placing a data point. b. Select the Drawing List button. The system activates the List Drawings form.
c. Select the drawing that will represent the low (or high) drawing number and select the accept button. The system returns to the Create Batch Job Input form with the selected drawing displayed in the Drawing Number Low (or High) field. Model Revised Date Low / Model Revised Date High These commands restrict, by model revision date, the list of lines to retrieve. Key in the model revision date in either the low or high field to restrict the list of lines. Select Subset of All Selections / Select All This toggle allows you to revise further the previously generated list of drawings. If the Select Subset of All Selections option is used, you must select one or more drawings from the list of drawings in the scroll field. If the Select All option is used, all drawings contained in the drawing list are selected. Drawings can still be unhighlighted and highlighted after this option is selected. Review a Drawing The Review a Drawing command allows you to review information on a single drawing. The Select Subset of All Selections / Select All toggle must be set to Select Subset of All Selections before selecting this command. Reset Selections
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The Reset Selections command allows you to reset the list of drawings to be revised.
Display Selections The Display Selections command allows you to view the list of drawings as it is defined by the current search criteria settings.
Review a Drawing (on page 75) Revising a Single Drawing (on page 75) The Review a Drawing command allows you to review information on a single drawing. The Select Subset of All Selections / Select All toggle on the previous form must be set to Select Subset of All Selections before selecting this command.
Revising a Single Drawing If a single drawing is selected for revision, the system displays the Revise Single Drawing form.
1. Revise drawing information by changing the information contained in the following fields. Type Select the Type field gadget and select the appropriate isometric drawing type that will be associated with the drawing. Line 2 (This field is optional.) Key in a secondary line name. This line name identifies a secondary line to be extracted onto the isometric. The secondary line must be connected to the line identified by the primary line name. Line 3 (This field is optional.) Key in another secondary line ID. The same restrictions apply to Line 3 as to Line 2.
Plant Design System (PDS) ISOGEN
75
Batch Isometric Extraction Number of Sections This field is usually left blank. When a line leaves a piping area and then returns at some other point, such that the pipeline in the area exists in multiple disconnected sections, then the number of sections should be specified. This field allows you to treat a disconnected pipeline in the model as one line. Sheet numbering is continuous. For example, if a line exists in two sections of a model and section one generates three sheets and section two generates two sheets, then the sheets from section two will be sheets four and five of the line. This option should not be used to extract lines that are not intentionally disconnected. A line may or may not extract if you attempt to use this field to extract a pipeline not modeled correctly. Batch Reference (The batch reference number is optional.) Key in a batch reference number. The batch reference number allows you to group drawings within an area. If batch reference numbers are supplied, you can later specify, for example, that you want to extract all drawings in a given area with a given batch reference number. Model Status Key in the model status code. The user-defined model status code helps keep track of drawing status. The following is a list of example codes: N - Line has not been modeled M - Line has been modeled but not checked C - Line has been modeled and checked A - Drawing has been extracted and approved R - Line has been revised since last approved If model status codes are defined in this field, they can be used later when generating a batch input file. For example, you could designate that all lines in a given area be extracted with a given model status. Model Revised Date Key in a date with the format DD-MMM-YYYY. This date indicates when the lines comprising the drawing have been revised. The Model Revised Date field allows you designate for extraction, all lines that have been revised since the last drawing revision. Date to Mtl Control Key in a date that indicates when the most recent mto neutral files were passed to a material control system. You must manually update this field. Revision Number
The system displays the latest revision number of the drawing. The revision number is automatically updated by the system each time a drawing is extracted. When a batch job file is created, you must decide whether or not to increment the revision number during the run. To increment the number, the system increments the field by one. If the Revision Number field is -1, the system assumes that revision zero of the drawing is being generated. Drawing Number
The system displays the active drawing number. Iso Dgn Name
The system displays the isometric design file name. The design file name is used to name subsidiary files created during the extraction. The Iso design file name can be changed by selecting the Iso Dgn Name field and keying in a new name.
76
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Extraction Number
The system displays the last extraction number for the drawing. The extraction number is incremented by one each time the drawing is extracted. This field should be mapped to a text node near the extraction date text node (see the description of the Extraction Date field). The extraction number helps you distinguish between two drawings generated on the same day. Extraction Date
The system displays the last extraction date for the drawing. The extraction date is automatically updated by the system when batch isometrics extraction occurs. This field should be mapped to a text node that lies just outside of the drawing border. This will help indicate when the drawing was generated. Last MTO Date
The system displays the date that an MTO neutral file was last generated for the drawing. The MTO date is automatically updated by the system whenever an MTO neutral file is generated along with the isometric drawing. Sheets Generated
The system displays the number of sheets generated by ISOGEN for the drawing the last time it was extracted. The number of sheets is automatically updated by the system each time the drawing is extracted. Revision block fields Rev By Chk Apv Date Ext Sht Description Each time the revision number is incremented, a new line of data is added to the revision block automatically. Line inputs are specified each time a batch job file is created. Up to 60 characters can be entered into the Description field. User Data Select the User Data button to revise previously defined user data. To revise user data, select the appropriate user data field, key in the updated user data and select the accept button. Select Revisions to Delete / Delete Selected Revisions When this toggle is set to Delete Selected Revisions, you can select individual revisions to be deleted. When selected, each revision is highlighted in red. When accept is selected, all red highlighted revisions are deleted. To remove red highlighting from revisions, set the toggle back to Select Revisions to Delete. Select All Revisions to Delete / Delete All Revisions When this toggle is set to Delete All Revisions, all revisions are highlighted in red. When accept is selected, all red highlighted revisions are deleted. To remove red highlighting from revisions, set the toggle back to Select All Revisions to Delete. 2. Once you have completed revising the form, select accept.
Plant Design System (PDS) ISOGEN
77
Batch Isometric Extraction The system writes the revised data to the Project Control Database and returns to the Revise Drawing form. 3. Select exit to return to the Revise Drawing form.
Revising Multiple Drawings If multiple drawings are selected for revision, the system displays the Revise Multiple Drawings form.
78
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction 1. Revise drawing information for all of the listed drawings by changing the information contained in the following fields. A key-in in any of the following fields, followed by the accept button, will result in an update of all drawings listed in the scroll area.
Type Select the Type field gadget and select the appropriate isometric drawing type that will be associated with the drawing. Number of Sections This field is usually left blank. When a line leaves a piping area and then returns at some other point, such that the pipeline in the area exists in multiple disconnected sections, then the number of sections should be specified. This field allows you to treat a disconnected pipeline in the model as one line. Sheet numbering is continuous. For example, if a line exists in two sections of a model and section one generates three sheets and section two generates two sheets, then the sheets from section two will be sheets four and five of the line. This option should not be used to extract lines that are not intentionally disconnected. A line may or may not extract if you attempt to use this field to extract a pipeline not modeled correctly. Batch Reference (The batch reference number is optional.) Key in a batch reference number. The batch reference number allows you to group drawings within an area. If batch reference numbers are supplied, you can later specify, for example, that you want to extract all drawings in a given area with a given batch reference number. Model Status Key in the model status code. The user-defined model status code helps keep track of drawing status. The following is a list of example codes: N - Line has not been modeled M - Line has been modeled but not checked C - Line has been modeled and checked A - Drawing has been extracted and approved R - Line has been revised since last approved If model status codes are defined in this field, they can be used later when generating a batch job. For example, you could designate that all lines in a given area be extracted with a given model status. Model Revised Date Key in a date with the format DD-MMM-YYYY. This date indicates when the lines comprising the drawing have been revised. The Model Revised Date field allows you designate for extraction, all lines that have been revised since the last drawing revision. Date to Mtl Control Key in a date that indicates when the most recent mto neutral files were passed to a material control system. You must manually update this field. Revision Number The system displays the latest revision number of the drawing. The revision number is automatically updated by the system each time a drawing is extracted.
Plant Design System (PDS) ISOGEN
79
Batch Isometric Extraction When a batch job file is created, you must decide whether or not to increment the revision number during the run. To increment the number, the system increments the field by one. If the Revision Number field is -1, the system assumes that revision zero of the drawing is being generated. Revision block fields Rev By Chk Apv Date Ext Sht Description Each time the revision number is incremented, a new line of data is added to the revision block automatically. Line inputs are specified each time a batch job file is created. User Data Select the User Data button to revise previously defined user data. To revise user data, select the appropriate user data field, key in the updated user data and select the accept button. Delete Revision Record(s) Select the Delete Revision Record(s) button to delete all of the revision history entries. After selecting this option, the system prompts: Accept to delete all records. Select the accept button to delete the records. 2. Once you have completed revising the form, select accept.
The system writes the revised data to the Project Control Database and returns to the Revise Drawing form. 3. Select exit to return to the Revise Drawing form.
Delete Drawing This command activates the Delete A Drawing form that allows you to delete single or multiple drawings. You can select either Select by LineId (see "Select Drawings by LineId" on page 71) or Select by Using "Search Criteria" (see "Selecting Drawings Using Search Criteria" on page 72) to select the drawing(s) for deletion. Deleting a drawing will also delete any associated files that were created in the output location as defined in the default set. 1. Select the Delete Drawing button from the Batch Environment form.
The system displays the Delete A Drawing form.
80
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
2. Select the Type field gadget and select the isometric drawing type that is associated with the drawing. 3. Select either the Select by LineId (see "Select Drawings by LineId" on page 71) or Select by Using "Search Criteria" (see "Selecting Drawings Using Search Criteria" on page 72) option, and follow its procedures to select a drawing(s). 4. Select the accept button.
The system returns to the Delete A Drawing form with the selected drawings listed. 5. Select the accept button and proceed to the section Revising a Single Drawing (on page 75) or Revising Multiple Drawings (on page 78), depending on the number of drawings selected for revision.
Plant Design System (PDS) ISOGEN
81
Batch Isometric Extraction
Delete a Single Drawing If a single drawing is selected for deletion, the system displays the Delete A Drawing form that contains drawing information for the selected drawing.
1. Select the accept button to delete the displayed drawing.
The system deletes the drawing and returns to the Delete A Drawing form. If you have never extracted the displayed line with the Increment Revision No toggle option (see Create Batch Job Input (on page 109) for more information), only the database drawing record will be deleted. The isometric file will not be deleted. The system will display a warning message box if this situation occurs.
See Also Delete Drawing (on page 80)
82
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Delete Multiple Drawings If multiple drawings are selected for deletion, the system returns to the Delete A Drawing form which contains a listing of the selected drawings.
1. Select the accept button to delete the displayed drawing.
The system deletes the drawing and returns to the Delete A Drawing form. If any of the lines selected for deletion have never been extracted using the Increment Revision No toggle option (see Create Batch Job Input (on page 109) for more information), only the database drawing records will be deleted. The isometric files will not be deleted. The system will display a warning message box if this situation occurs.
See Also Delete Drawing (on page 80)
List Drawings This command allows you to list all drawings within a piping area. 1. Select the List Drawings command from the Batch Environment form.
Plant Design System (PDS) ISOGEN
83
Batch Isometric Extraction The system displays the List Drawings form.
2. Key in the piping area that contains the drawings you want to list. OR Select the Iso Area List button for a list of available iso areas.
The system displays the List Iso Areas form.
84
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction 3. Select an iso area from the form and select the accept button.
The system returns to the List Drawing form with the selected area displayed in the Iso Area field. The system displays the drawings that are within the selected piping area. If the area does not exist, the system displays an error message.
Utilities Utilities options are used to simplify building and maintaining the Project Control Database and in defining areas and drawing information. 1. Select the Utilities button from the Batch Data Environment form.
The system displays the Utilities form.
See Also Bulk Load Lines (on page 86) Bulk Load Lines from ASCII File (on page 93) Entering the Iso Symbol Editor Environment (on page 97) Delete Drawing Records With Undefined Iso Type (on page 106)
Plant Design System (PDS) ISOGEN
85
Batch Isometric Extraction
Bulk Load Lines The Bulk Load Lines command allows you to load multiple lines by defining a specific model, area or group of line numbers. 1. Select the Bulk Load Lines button from the Utilities form.
The system activates the Bulk Load Lines Form.
2. Select the Iso Type field gadget and select the appropriate isometric drawing type that will be loaded. Refer to Isometric Types (on page 321) for more information on Iso Type. 3. Key in a Default Batch Reference Number.
This field input is optional. 4. Set the Iso Name Option toggle to the appropriate setting. Select the By Project Default setting (By Line Id or By Area and Line ID) to use the project default set previously defined on the Isometric Extraction Project Options form. For more information on defining the project default set, see Define Project Options (on page 62). Select the By Label Number setting to use the label number previously defined on the Isometric Extraction Project Options form. For more information on defining the project default set, see Define Project Options (on page 62). Label number refers to the label number as it exists in the Reference Data Manager's label description library; not the label library referred to in the Files section of the ISOGEN options file. 5. Set the Drawing Number Option toggle to the appropriate setting. Select the By Project Default setting (By Line Id or By Area and Line ID) to use the project default set previously defined on the Isometric Extraction Project Options form. For more information on defining the project default set, see Define Project Options (on page 62). Select the By Label Number setting to use the label number previously defined on the Isometric Extraction Project Options form. For more information on defining the project default set, see Define Project Options (on page 62).
86
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Label number refers to the label number as it exists in the Reference Data Manager's label description library; not the label library referred to in the Files section of the ISOGEN options file. 6. Select the Default Set field to select another default set from the Isometric Extraction Default Sets form.
7. Select a default set from the form, and select the accept button to return to the Bulk Load Lines form. 8. Select one of the following methods of bulk loading lines. Load by Area - creates drawing records for all pipelines in a selected Iso Area. Load by Model - creates drawing records for all pipelines in a selected Iso Model. Load by Line - creates drawing records for selected pipelines within a selected Iso Model.
See Also Load by Area (on page 88) Load by Model (on page 89) Load by Line (on page 90)
Plant Design System (PDS) ISOGEN
87
Batch Isometric Extraction Load by Area After the Load by Area button is selected, the system activates the Bulk Load Lines form and prompts you to select the area(s) that contain the lines to be loaded. 1. Select the appropriate area(s) and select the accept button.
The system loads all lines associated with the selected area(s) and the area definition if it does not currently exist. The following form will be displayed if the ISOGEN software detects any invalid lines. An invalid line occurs when any attribute value defined in the LINE_ID_DEFINITION section of the option file is left blank.
The invalid iso line information, appended with the current time, is saved into ..\temp\ld*****.log after all valid iso lines have been processed. The invalid iso line log file will be appended to until the Bulk Load Lines command is exited.
88
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Load by Model After the Load by Model button is selected, the system activates the Bulk Load Lines form and prompts you to select an area.
1. Select the area that contains the appropriate models.
The system updates the form by displaying a list of available iso models that reside within the selected iso area.
Plant Design System (PDS) ISOGEN
89
Batch Isometric Extraction 2. Select the appropriate iso model(s) and select the accept button.
The system loads all lines associated with the selected model(s). The following form will be displayed if the ISOGEN software detects any invalid lines. An invalid line occurs when any attribute value defined in the LINE_ID_DEFINITION section of the option file is left blank.
The invalid iso line information, appended with the current time, is saved into ..\temp\ld*****.log after all valid iso lines have been processed. The invalid iso line log file will be appended to until the Bulk Load Lines command is exited.
Load by Line After the Load by Line button is selected, the system activates the Bulk Load Lines form and prompts you to select an area. 1. Select the area that contains the appropriate model.
90
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The system updates the form by displaying a list of available iso models that reside within the selected iso area.
2. Select the appropriate iso model and select the accept button.
The system updates the form by displaying a list of available iso lines that reside within the selected iso model.
3. Select the appropriate iso line(s) and select the accept button.
The system loads all selected lines.
Plant Design System (PDS) ISOGEN
91
Batch Isometric Extraction
The following form will be displayed if the ISOGEN software detects any invalid lines. An invalid line occurs when any attribute value defined in the LINE_ID_DEFINITION section of the option file is left blank.
The invalid iso line information, appended with the current time, is saved into ..\temp\ld*****.log after all valid iso lines have been processed. The invalid iso line log file will be appended to until the Bulk Load Lines command is exited.
92
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Bulk Load Lines from ASCII File Since this command does not create ISOGEN areas, the ISOGEN area you are loading lines into must exist before running this command. For more information on creating a 3D piping/ISOGEN area, refer to the section Creating 3D Areas and Models in the PDS Project Setup Technical Reference. 1. Select the Bulk Load Lines From ASCII File button.
The system activates the Bulk Load Lines From ASCII File form.
2. Key in the filename which contains the pipeline information to be loaded. If the export statement is defined in the control shell, the above field will be loaded automatically. For example: export ISO_ASCII_LOAD=/pdssk:/usr/50cert
The system generates a log file using the system filename with a .log file extension. This file contains error or warning messages and also information about which areas and lines, if any, have been added to the database. 3. Select the accept button.
The system checks the file for syntax errors and undefined areas. If no errors are detected, the system adds the lines to the existing ISOGEN areas (as defined in the ASCII file) and returns to the Bulk Load Lines From ASCII File form. If no errors are detected, but warnings occur, the system displays the warning messages and adds the areas and their respective lines to the database.
Plant Design System (PDS) ISOGEN
93
Batch Isometric Extraction If any errors are detected, the system displays the errors and any warnings, and does not update the database.
The following options are only used when warnings and/or errors are detected during the loading process.
Revise File 1. Select the Revise File button to edit the current file using the default editor.
The system creates an editor window based on the text editor defined by the PDEDITOR export variable in the control shell. The following is an example of a typical ASCII file. If Iso Type is not defined, ISOGEN defaults to Fabrication. Refer to Isometric Types (on page 321) for more information on Iso Type. Projectname Begin Area
! required - Begin Area 1
IsoAreaName
! required
#E EquipmentContArea
! optional - up to 5
#C PipeContArea
! optional - up to 10
#Un "Area User Data"
! optional - data must be between double quotes - where n is a number: 1 - 10
"IsoType"
94
! required - must be 1st line, 1st column
! optional literal string double
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction quotes LineId
! required
#L2 LineId2
! optional
#L3 LineId3
! optional
#S NumSections
! optional
#B BatchRefNum
! optional
#M ModelStatusCode
! optional
#Un "Drawing User Data" ! optional - data must be between double quotes - where n is a number: 1 - 10 "IsoType"
! optional literal string double quotes
LineId
! required
#L2 LineId2
! optional
#L3 LineId3
! optional
#S NumSections
! optional
#B BatchRefNum
! optional
#M ModelStatusCode
! optional
#Un "Drawing User Data" ! optional - data must be between double quotes - where n is a number: 1 - 10 End Area Begin Area PIPE01 AF7701PQ End Area
! required - End Area 1 ! Begin Area 2 ! Iso Area Name ! Line ID ! End Area 2
Where the keyword:
Plant Design System (PDS) ISOGEN
95
Batch Isometric Extraction Begin Area End Area #E #C #Un #L2 #L3 #S #B #M !
is the beginning of an area record. is the end of area record. is the continuation equipment areas. is the continuation pipe areas. is user data and a number 1 - 10. is LineId 2. is LineId 3. is the number of sections. is the batch reference number. is the model status code. is a comment line
The keywords listed above must precede any information they are associated with. For example, a batch reference number called steam unit would have to appear in the ASCII file as: #B STEAM_UNIT No spaces are allowed between the # and the letters. KEYWORDS are not case sensitive. For example, Begin Area = BEGIN area = BEGIN AREA, #E = #e User data, #Un, must be enclosed in double quotes. Tabs, spaces and blank lines are allowed anywhere within the file. The project name will be used as a check to verify that the file belongs to the current project. The project name must be on the first line in the first column. Comments may be included on any row by using a !. Anything after the ! up to a newline is considered part of the comment.
Process another file Select the Process another file button to dismiss the displayed warning/error messages and display the Filename and Log Filename fields. Return to step 2, above.
Process "Areas With No Syntax Errors" Select the Process "Areas With No Syntax Errors" button to continue processing areas that have the correct syntax.
Isometric Symbol Editor ISOGEN provides an extensive library of symbols that you can select to map PDS symbol names to isometric drawing symbols. If the drawing symbology for some of these symbols is inadequate, you can redefine them to have new symbology. It is recommended that you copy the provided design files and index files when creating new symbols. These files are the symbol.dgn and symbol.ndx files that are located in the directory ˜/pdiso/dat. The symbol definition process consists of the following steps: 1. Draw the symbol in graphics by using the Symbol Definition Software. 2. Create a symbol library from the graphics generated in step 1. 3. Add the symbol library to the options file. 4. Change the PDS to ISOGEN symbol map, as needed, so that PDS items are mapped to the appropriate ISOGEN SKEY. The working units of the copied symbol.dgn file are defined as the following:
96
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Master Units Sub Units sub units per master unit uor per sub unit
: : : :
M MM 1000 1000
The Data readout accuracy is set to .02. The scale and angle locks and grid display may be turned ON to make symbol construction easier. The following grid setup works well and can be saved using the MicroStation file designed option: GU=0: .10 GR=10
See Also Entering the Iso Symbol Editor Environment (on page 97) Input Area Options (on page 98) Assembling an Isometric Symbol (on page 100) Creating a User-defined Symbol Library (on page 106) Using the Newly-created Symbol Library (on page 106)
Entering the Iso Symbol Editor Environment 1. Select the Iso Symbol Editor button from the Utilities form.
The system displays the Isometric Symbol Editor form.
2. Define the Symbol Design, Symbol Index and Symbol Library fields to define the location of those files. Use the format nodename:path to define the location of each file. For example: mynode:c:\win32app\ingr\pdiso\dat\symbol.dgn.
Plant Design System (PDS) ISOGEN
97
Batch Isometric Extraction You can set the PDS Environment Variables: SYMDGN, SYMNDX and SYMLIB to define default values for these fields.
You can key in the name of a previously-created, symbol index file name by two methods. You can key in the name when revising a symbol that has been defined in a previous session. Also, you can key in the name when adding a new symbol to a 2-D design file that already contains one or more user-defined symbols. If a single index file is not maintained for each design file that contains user-defined symbols, you will have difficulty converting the design file graphics into an ISOGEN symbol library. It is recommended that all symbols be defined in one design file with one corresponding index file. 3. After defining the fields in the previous step, select the Symbol Editor button to enter the MicroStation environment and activate the Isometric Symbol Definition form.
Input Area Options Various components of the isometric symbol can be created and/or revised using the commands in the Input area and the Symbol Origin command located on the Isometric Symbol Definition form.
Old Skey Select the Old Skey field, and key in an old skey for the symbol you are defining. The old skey is an existing symbol key chosen from the Alias ISOGEN Tables (see the appendix). When defining a new symbol, some of the default properties of the new symbol are inherited from the old one. The basic skeleton or connect point geometry of a new symbol may not vary from that of the old symbol. For example, you must not define a new angled fitting based on a straight-through fitting.
98
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction New Skey Select the New Skey field, and key in a new skey. The new skey is the symbol key of the symbol that is currently being defined.
If you leave the new skey blank, the old symbol will be redefined. If the old skey is variable end prep (that is, the old skey ends with the characters **), the symbol will be redefined for all end preps. If the old skey is specified with a specific end prep, only the symbol with that end prep will be redefined. If you specify a new skey, a new symbol of that name will be created. The new skey may end with the characters ** to indicate that the symbol is variable end prep. If the old skey is a valve operator and the new skey is left blank, all valve symbols that currently use that operator symbol will be redefined with the new operator. If the old skey is a valve operator and a new skey is specified, the operator must be explicitly attached to new valve symbols (using the spindle key input field). The new skey must never be the same as one of the old skeys that have been previously defined for ISOGEN.
The system checks the index file to see if the current combination of old and new skey already exists. THEN
If the combination exists, the software recognizes that an existing user-defined symbol definition is being revised. The software will then perform a window area about the redefined symbol graphics that you previously placed in the design file. OR
If the combination does not exist in the index file, the software knows that the symbol is being redefined for the first time.
Symbol Origin If you are revising an existing iso symbol, do not define a symbol origin. The Symbol Origin command defines an area in which the new iso symbol will be created. All iso symbol graphics must be contained within the defined area. Select the Symbol Origin button from the Isometric Symbol Definition form. The symbol origin is the lower left hand corner of a rectangular area in which the new symbol will be drawn. The rectangular area is approximately 20 x 25 mm. Position the rectangular area and place a data point to place it. Once the area is placed, you must draw the iso symbol using only MicroStation Line and Linestring commands.
No circles or closed shapes can be used. Keep the symbol as simple and as symmetrical as possible. Use approximately one-fourth of the block for the right proportion of your new symbol. Do not move or change the area once it is placed.
Spindle Key Spindle Key defines the operator subsymbol that will be attached to this symbol when it is drawn in the isometric. There are 12 existing spindle keys defined in the table in Appendix B: Alias ISOGEN Tables. You can also define new spindles (operators). If the symbol does not require a spindle, this field can be left blank if the symbol does not require a spindle.
Plant Design System (PDS) ISOGEN
99
Batch Isometric Extraction ScaleFactor ScaleFactor is used to scale the plotted shape up or down relative to the dimensions used in drawing the symbol. A value of 100 (which is recommended) will give a scaling factor of 1.
Orientation Orientation is used to define the type of fitting drawn. This number is used for automatically creating a mirror image symbol. Available options include: Symmetrical - none (symbol is symmetrical) Flow Direction Dep - flow direction dependent (for example, check valve) Large to Small Bore - large to small bore (for example, reducer) Flange Start - flange start (for example, has a gasket to the left)
Flow Arrows Flow Arrows defines the flow arrow for the symbol. Available options include: Use Old SKEY - same as the old skey No - never has a flow arrow Yes - has a flow arrow
Dimensions Dimensions control how the fitting or symbol is dimensioned. Available options include: Use Old SKEY - same as the old skey Off - dimensions off On - dimensions on
Lagging/Tracing Lagging/Tracing controls the insulation and heat tracing display on the fitting. Available options include: Use Old SKEY - same as old skey Both Off - both off Lagging On - lagging on Tracing On - tracing on Both On - both on Setting values in option block words 61 and 62 causes ISOGEN to draw insulation and tracing on every component. These symbols definition options enable you to override the options block switches. For example, even though insulation and tracing on components are enabled, the previous options allow you to specify that for a specific component neither value should be displayed.
Assembling an Isometric Symbol The different components that make a user-defined isometric symbol include: Symbol Origin
100
Dynamically displays a drawing symbol area (discussed previously).
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Start Point
The in point of the symbol; analogous to a connect point in PDS terminology. The point where the symbol will connect to adjacent symbols.
End Point
The out point of the symbol. Also, a point where the symbol will connect to an adjacent symbol.
Spindle Point
The point where a valve operator attaches to a symbol. Similar to the symbol origin in the PDS world.
Tap Points
Branch points on a symbol. Points where other piping components can be attached to the symbol. Tap points are not exactly analogous to PDS taps. A redefined symbol will usually have several tap points; however, when a drawing is created normally, only one or two will be used.
Symbol
Symbol graphics consist of the lines and line strings that are always drawn when a symbol is drawn in a drawing.
Lagging
Lagging graphics consist of the lines and line strings that are only drawn when the lagging on the symbol is enabled.
Tracing
Tracing graphics consist of the lines and line strings that are only drawn when the heat tracing on the symbol is enabled.
The following are guidelines that should be used when assembling components into a symbol. 1. In this example, the symbol is created in a coordinate system where the x-axis is horizontal and the y-axis is vertical. The origin of the coordinate system should fall on a point of symmetry of the symbol. Thus, the y-axis will bisect the symbol. The symbol start point will usually fall on the x-axis. 2. The only valid connect point geometries that you can define are the following: End point (for example, caps, plugs, blind flanges) Straight through (for example, valves, flanges) Offset (for example, eccentric reducer, flange) 90 degree change of direction (for example, angle valve) 3-way (for example, 3-way valve) 4-way (for example, 4-way valve) Other geometries must be obtained through the use of fitting taps. This requirement impacts the definition of symbols in the PDS environment. When defining a symbol in PDS, you must consider the ISOGEN symbol to which you will map when selecting the connect point geometry. If any connect point geometry does not map to an ISOGEN connect point geometry, extraction will not be performed properly. Example: In this example, a specialty item that resembles a lateral needs to be defined in both PDS and within ISOGEN, so that it properly extracts to a drawing. Appendix B states that no symbols exist with connect point geometry that satisfies the requirements of the specialty item. (In fact, you can map the specialty item to a TEXX (which is a tee); however, the symbology for a TEXX is not acceptable, and the TEXX cannot be redefined.) In one solution, you can define the basic connect point skeleton of the item in both PDS and ISOGEN as a straight-through component. Although, the branch off the side can be a tap, you
Plant Design System (PDS) ISOGEN
101
Batch Isometric Extraction cannot draw graphics that extend from the ISOGEN symbol for the branch. This is because you cannot force ISOGEN to use a specific tap on the iso symbol. You must define several tap points and allow ISOGEN to choose the one that gives the best graphic representation of the component and connecting piping. 3. When defining graphics that are drawn between the end prep symbols, your symbol definition should not contain any end prep graphics. 4. When defining an offset fitting, the flow should go from top left to bottom right in the symbol coordinate system. For example, an eccentric reducer would be drawn with the large end on the left and the small end on the right, with the flat side down or at the bottom of the symbol. Flanged offset fittings must be created with the end prep graphics drawn integrally with the symbol. 5. If angled fittings consist of two or more legs, all legs of a redefined angled fitting must be identical. When you define the angled fitting, you draw only a single leg. The other legs are created automatically by ISOGEN. The leg that you draw must be symmetrical about the x-axis of the symbol coordinate system. The start point of the leg must be to the left of the y-axis and the end point must be the pivot point or the origin of the symbol. All legs of an angled fitting must have a common pivot point (this requirement excludes redefinition of symbols like the angle block BA**).
6. A symbol can have up to nine tap points. When distributing tap points, observe the following rules. No more than three tap points can be placed on the x axis. No more than three tap points can be placed on the y axis. No more than three tap points can be placed above the x axis. No more than three tap points can be placed below the x axis. No more than three tap points can be placed left of the y axis. No more than three tap points can be placed right of the y axis.
102
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The previously-listed rules are not checked during symbol creation, but are verified when the symbol is written to the symbol library. The symbol will not be written if any of the limits are exceeded. To use tap points that are not on the x or y axis, when the symbol is drawn, observe the following rules: Outer tap points in the y-axis direction must be located at least 5 mm from the y-axis if they are to be used. Outer tap points in the x-axis direction must be located by at least the greater of 5 mm or 10% of the symbol length down the x-axis if they are to be used. When a component with taps in the model is mapped to a symbol without taps, the tap point is assumed to be at the center of the symbol. None of the default ISOGEN symbols have defined tap points. A symmetrical symbol should have symmetrically distributed tap points so that ISOGEN always finds an appropriate tap point no matter how the symbol is oriented in a drawing.
7. Redefined symbols cannot be too large. Otherwise, problems may occur with graphic interferences within the drawings. The amount of space reserved in a drawing for a symbol is always based on that of the old skey. Therefore, you should keep your symbol approximately the same size as the one it is based on. Using this criteria, most symbols should be between 8 and 12 mm long and 4 to 8 mm tall. Sketches of several of the original ISOGEN symbols appear in the appendix, ISOGEN SKEY Dimensions. 8. In redefining a valve operator symbol, you must follow these rules: The start point of the symbol must be the point where the operator attaches to the valve. The operator must be defined on its side with the stem lying along the x-axis and the hand wheel lying along the y-axis. 9. Two alternatives exist for defining pipe supports: The pipe support symbol does not have an orientation (like the default ISOGEN pipe support symbol). In this case, the start and end points of the symbol should be located at the same point. The graphics should be symmetrical about the x-axis.
Plant Design System (PDS) ISOGEN
103
Batch Isometric Extraction The pipe support symbol has an orientation much like a valve operator does. In this case, the symbol definition should take place in two steps. a. Redefine the pipe support so that it consists of only a start point, an end point, and a spindle point all located at the same place. The spindle key for this pipe support should be set so that a valve operator is attached when the symbol is placed. b. Define the valve operator that will actually be the pipe support graphics. With these guidelines, you should select commands from the tutorial and locate the various symbol components. Each tutorial command is described in the following sections.
See Also Start Point (on page 104) End Point (on page 104) Fit Symbol (see "Fit Symbol Command" on page 104) Solid Line (on page 104) Lagging (on page 105) Tracing (on page 105) Spindle (see "Spindle Point" on page 105) Tap Points (on page 105) Accept (on page 105) Clear (see "Clear Command" on page 105) Delete (see "Delete Command" on page 105) Exit (on page 105) Start Point You use this command to specify the start point of the symbol. After you select the command, you must identify the point with either a data point or an XY= key-in. A symbol must contain one and only one start point. The system responds by placing a heavy cross at the point you specify.
You can use the MicroStation view manipulation commands while drawing the symbol graphics. You must cancel out of view commands, however, before making subsequent tutorial selections. You can use the MicroStation element manipulation commands to modify graphics that you place to build the symbol.
End Point Use this command to define the end point of the symbol. After you select the command, you must identify the point with either a data point or an XY= key-in. A symbol must contain one and only one end point. The system responds by placing a heavy cross at the point you specify. Fit Symbol Command The Fit command is used to perform a fit operation on the symbol definition area. Select the Fit command and place a data point in the view to fit the symbol. The system responds by doing a window area about the box that encompasses the current symbol definition.
104
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Solid Line Select this command just prior to drawing symbol graphics with the MicroStation place line and place linestring commands. Symbol graphics can consist of lines and linestrings only. The system responds by setting the line code to solid. Lagging Select this command just prior to drawing insulation graphics using the MicroStation place line and place linestring commands. Insulation graphics can consist of lines and linestrings only. The system responds by setting the line code to long dash. Tracing Select this command just prior to drawing heat tracing graphics using the MicroStation place line and place linestring commands. Heat tracing graphics can consist of lines and linestrings only. The system responds by setting the line code to dot dash. Spindle Point Use this command to define the spindle point of the symbol. After selecting this command, you must identify the point with either a data point or an XY= key-in. A symbol can contain only one spindle point. The system responds by placing a heavy cross at the point you specify. Tap Points Use the Tap Points command to define tap points on the symbol. After you select this command, identify a point with either a data point or an XY= key-in. A symbol can contain up to 9 tap points. The system responds by placing a heavy cross at the point you specify. Accept Choose Accept to indicate that the symbol definition is complete. The system responds by checking your definition to confirm that it contains a start point and end point. The system then adds a new record to the symbol index file. Clear Command Choose Clear to stop work on the current symbol and reinitialize the tutorial. The system responds by erasing all tutorial inputs and a fit operation is performed on the design file. Delete Command Choose Delete to delete the current symbol. The system responds by deleting all of the symbol graphics and any record that may have been written to the symbol index file. Exit Select the Exit command when you are finished redefining symbols. The system responds by closing the symbol index file and deactivating the symbol definition tutorial.
Plant Design System (PDS) ISOGEN
105
Batch Isometric Extraction Creating a User-defined Symbol Library After drawing the symbol graphics with the Symbol Definition Software, you must generate a symbol library. To create the symbol library, select the Update Symbol Library button from the Isometric Extraction Utilities form.
Before Using This Command You must have created a design file containing user-defined symbols, and you must also have the corresponding symbol index file. The system performs the following processes when updating the symbol library. The system verifies that the symbol file (defined in the Isometric Symbol Editor Screen form) exists. If the file does not exist, the system displays an error message and returns to the Isometric Symbol Editor Screen form. The system verifies that the index file (defined in the Isometric Symbol Editor Screen form) exists. If the file does not exist, the system displays an error message and returns to the Isometric Symbol Editor Screen form. The system displays the following messages at the start of each phase of processing. Stroking design file contents... Converting ASCII symbols to binary... Upon completion, the system prompts Symbol library successfully created If any errors are encountered during processing, refer to the log file that is written to the ~/pdiso/dat directory.
Using the Newly-created Symbol Library To use the newly-created symbol library, you must first perform three actions: 1. Edit the options file, and add the binary symbol library file name to the FILES table. Refer to The Options File (see "The Options File - PD_ISO" on page 145) for more information on the FILES table. 2. Edit the NEW_SYMBOL_KEYS table in the options file where necessary. Refer to The Options File (see "The Options File - PD_ISO" on page 145) for more information on the NEW_SYMBOL_KEYS table. 3. Modify the PDS to ISOGEN symbol map so that PDS symbols map to the newly-defined ISOGEN symbols.
Delete Drawing Records With Undefined Iso Type This command deletes all isometric drawings that do not have an associated Type (fabrication, Spool, etc.). If you need to assign a Type to a drawing, one can be assigned by using the Revise Drawing command. All records that have been written to pdtable_185 in the project database must have an assigned iso Type or they cannot be extracted.
106
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Generate FrameWorks Reference Dimension File The FrameWorks Reference Dimension File command allows you to generate an ASCII file that is used by Intergraph option 71 to place reference dimensions in the isometric drawing. For more information on Intergraph option 71 refer to the section, The Options File. The ASCII file contains the names and locations of all structural columns and grids in the PDS project. The created ASCII file is saved to the PDS main project directory and named fw_projname.dat. A single structural data file (ASCII file) is created for the entire project, but you can use options on the Generate FrameWorks ASCII File form to specify the models included in the ASCII file. You can edit the file and split out the information into separate files or you can move the prp files you do not want to process to a different location. You can then add a variable to the pds.cmd file to select which ASCII file to reference when generating isometric drawings. Using unique column and grid label names makes it easier to locate the element in the model. To use this variable, add the following line to the pds.cmd file: $ENV{'ISOUSRREFDUM'} = 'path\file.dat'; where path is the path to the project directory and file.dat is the name of the ASCII file you want to use.
Editing the ASCII File If you have generated the ASCII file and want to use the variable to control which structural columns and grid lines are referenced, you need to edit the file and save the individual structural models (or groups of models) into separate files. The default grid line reference data file is in the project directory and is named fw_projname.dat. Open this file using any ASCII editor. The first column of each line describes the type of data that line contains: 0 - The line contains the name of the structural model and its UORs extents. 1 - The line contains structural column information with the column name and the beginning and end column points in UORs. 2 - The line contains East/West gridline information with the gridline label and beginning and end points in UORs. 3 - The line contains North/South gridline information with the gridline label and beginning and end points in UORs. When splitting the generated file into smaller files, be sure to keep all model information together (that is, cut from one "0" line to the line before the next "0" line).
Structural elements are placed in FrameWorks Plus by using one of ten available cardinal points. Each cardinal point represents a different point on the cross-section of a structural member. For example, an I-beam can be placed using cardinal point 5 (CP5)which is the center of its cross section or it can be placed by CP6 the right-center point on the beam‘s cross-section. The choice of cardinal point takes on additional relevance when using the Isometric Column Reference (Intergraph option 71) because this is the point that the pipeline will use as a reference.
Plant Design System (PDS) ISOGEN
107
Batch Isometric Extraction
In the following graphic, the same pipeline is extracted twice. In the top extraction, column C_25 was placed using CP5 (center-center) while the bottom extraction was placed using CP6 (right-center). In both cases, the referenced column is in the same physical location and the position of the pipeline is unchanged. However, note that the easterly dimension varies by half the thickness of the column.
Since the Structural Column Reference option (Intergraph option 71) references structural elements according to their active cardinal point at the time of placement. It is highly recommended that structural columns be placed by CP5 (center-center). 1. Select the Frameworks Reference Dimension File button from the Isometric Extraction Utilities form.
The system activates the Generate FrameWorks ASCII File form.
The Generated ASCII Filename field displays the nodename and location to which the dimension file will be written. You can specify the name of the file generated by this command. However, the isometric extraction process will always use either the project directory\fw_projname.dat file or the user defined file specified by the environment variable ISOUSRREFDIM. Thus, in order to use a file with a different name, you must either rename the file to project directory\fw_projname.dat or set the environment variable to match the different filename. 2. Specify the set of areas and models to be processed. All Models will process all the FrameWorks Plus models in the project. Selected Areas will process all the models in the selected areas. Selected Models will process only the selected models. 3. Set the Submit Batch Immediately/Delay Batch Submit Time toggle.
108
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Select the Submit Batch Immediately option to run the job immediately. Select the Delay Batch Submit Time to specify a run time for the job. Define the run time by keying in the day of the week (Mon, Tue, etc.), the time and then selecting AM or PM.
4. After the Submit Batch toggle has been set, select the Accept button.
The system generates the FrameWorks ASCII Data file and log file.
Create Batch Job Input To extract isometrics using the batch software, you must create a batch job input file. The batch job file is an ASCII data file that is submitted to the batch extraction software as an input file. You create the batch input file by identifying which lines to create drawings for and setting the options that determine how the job will be processed. Lines can be selected for the batch input file using one of two methods. These include defining search criteria to select large groups of lines and selecting lines by line ID. Once a batch input file is created, it can be scheduled by using the Schedule Batch Job command. Refer to Schedule Batch Job (on page 117) for more information. 1. Select the Create Batch Job Input button from the Batch Environment form.
The system displays the Create Batch Job Input form. When the accept button is selected on this Create Batch Job Input form, line ID records will be written to the batch job input file using this form's current search criteria. Be sure that you do not select accept on this form unless you have set the appropriate search criteria. Select cancel (X) to exit the form without writing line records.
2. Batch Job Input File Key in the batch job input file name. If a file name is not keyed in, the system options to the exported variable ISOBATCH.
The system checks that the existing file is a valid batch job input file and that it was generated from the same Project Control Database.
Plant Design System (PDS) ISOGEN
109
Batch Isometric Extraction If the file already exists the system will display the Overwrite, Append and Review/Edit buttons. Select Overwrite to overwrite the batch input file, or select Append to append the information to the existing batch input file information. Select Review/Edit to display the batch input file in the default editor. The default editor is notepad. You can use the export variable PD_EDITOR to define a different default editor. 3. Default Set Option Select the Default Set Option field to select another default set from the Isometric Extraction Default Sets form.
Select a default set from the form and select the accept button.
The system returns to the Create Batch Job Input form and displays the selected default set and description in the Default Set Option field. 4. Delete Existing Files / Save Existing Files toggle If the Delete Existing Files option is selected, the system will overwrite all miscellaneous files that were created as a result of a previous isometric generation. These files include any ISOGEN output you have enabled using the options file and error message files produced by the ISOGEN software. If the Save Existing Files option is selected, the system will not delete any of the generated miscellaneous files. This toggle will not purge old versions of the MTO neutral files. The batch extraction software uses the extraction number to name the neutral files. Example: The MTO neutral file named as follows: iso name + sheet number + .b + extr number indicates that an MTO file named CW10022.b7 is the MTO neutral file for iso CW1002, sheet 2, from extraction number 7. As shown in the above example, the MTO neutral file generated by the ISOGEN interface is split up into multiple files by the batch extraction software. Each new MTO file contains the material associated with a single isometric drawing sheet. If you choose not to delete the existing files, the existing iso will be copied to "output path"/isolast/.
110
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction 5. Do Not Save Details/Save Previous Details toggle If the Do Not Save Details option is selected, the system ignores any previously added graphics. If the Save Previous Details option is selected, the system adds all manually added MicroStation graphics of the previous isometric drawing version to the new version. Before using the Save Previous Details option, the MicroStation file, edg.exe, must be loaded locally to the workstation that will be used to process the isometric drawings.
The software looks in the output directory (as specified in the area level data) for each drawing sheet as it is produced. If a drawing sheet is found, then all graphics that reside on levels 0 and 60 through 63 are merged into the new version of the drawing. This allows you to add manual details that will be retained from version to version of the drawing. Some changes, particularly those made to the isometric drawing itself, will not be acceptable or correct when merged into a new version of the drawing. 6. Submit for Plotting / Do Not Plot toggle If the Submit for Plotting option is selected, the selected isometric drawings will be submitted for plotting. A Plot Request file name must be specified in the default set. For more information, see Define Default Sets (on page 57). If the Do Not Plot option is selected, none of the isometric drawings will be plotted. 7. Increment Revision Number/Do Not Increment Revision Number toggle If the Increment Revision Number option is selected, the system will update the drawing revision block when an isometric is successfully generated. If you plan to export the isometric drawing documents to PDME (Plant Data Maintenance Environment), the revision toggle must be set to Increment Revision Number. For more information on exporting isometric drawing documents, refer to the PD Project Administrator (PD_Project) Reference Guide. If the Do Not Increment Revision Number option is selected, the system will not update the revision block. You will encounter problems later when attempting to delete a drawing if a revision history does not exist for a drawing. Refer to Delete Drawing (on page 80) for more information about deleting drawings. When the batch job is run, the system will use the inputs for By, Chk, Date and Descr to update the revision block for the drawing in the Project Control Database. 8. By, Chk, Date, Descr To increment drawing revision numbers, key in information to these fields to specify the revision block data. The data will be written back to the Project Control Database only if the isometric is successfully extracted. If you leave the Date field blank, the current date will be used. The Date field allows you to specify an issue date for the isometric that is different from the current date. If, for example, you are extracting a number of drawings over a period of a few days for issue on a given date, you should key in that issue date to this field. Rather than key in Chk initials at extraction time, you might want to update the Project Control Database with Chk and Aprv initials after the drawing has been plotted. Up to 60 characters can be entered into the field "Desc", which will be written to the third line of the Batch Job Input File and, if the batch extraction succeeds, will be written to the table pdtable_186 in the project database. 9. Search Criteria
Plant Design System (PDS) ISOGEN
111
Batch Isometric Extraction Search criteria can be used separately or together to locate a drawing or group of drawings within an iso area. All defined search criteria must be met before a drawing can be included in an isometric extraction. Type Select the Type field gadget and select the appropriate isometric drawing type. Using this option will help limit the number of drawings displayed. Iso Area Key in the name of the iso area that you want to extract lines from. OR i. Select the Iso Area List button. The system displays the Iso Areas form.
ii. Select the appropriate iso area and the accept button. The system returns to the Create Batch Job Input form with the selected area in the Iso Area field.
112
To restrict the list further, you must supply additional criteria such as batch reference numbers and drawing numbers. Batch Reference Key in the batch reference number of the lines you want to extract. To use batch reference numbers as criteria, specify them in individual drawing records when adding drawing records to the Project Control Database. Model Status Code Key in the status code if you want to restrict a list to all lines of a given status. Drawing Number Low / Drawing Number High Drawing Number High and Drawing Number Low define, by drawing number, the range of lines to extract. Key in a drawing number in each field to identify the lines to extract. OR i. Activate a cursor in the Drawing Number Low field by placing a data point. ii. Select the Drawing List button.
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction The system activates the List Drawings form.
iii. Select the drawing that will represent the low drawing number and select the accept button. The system returns to the Create Batch Job Input form with the selected drawing displayed in the Drawing Number Low field. iv. Repeat the above steps for the Drawing Number High field. 10. Do Not Use Model Revised Date / Use Model Revised Date toggle. The Model Revised Date is an attribute of pdtable_185 and works in conjunction with the Use Model Revise Date option for extraction. Select the Use Model Revised Data option to specify that only lines whose Model Revised Date is greater than or equal to the last drawing revision date can be included in the list of lines to extract.
The Model Revised Date attribute is not used when making modifications inside the piping designer (pdtable_113, for example). If you make any changes in the model, this attribute is not used to extract those modified lines. To change the Model Revised Date, select Revise Drawing > Select the iso drawing > Change the Model Revised Date on the Revise Single Drawing form. 11. Once all of the necessary search criteria has been set, select the accept button to begin processing.
If enabled, the system displays the Write to Batch Input File Cancel/Accept form.
12. Select the accept button to begin posting the list to the batch input file. The Write to Batch Input File Cancel/Accept form is an added feature to help prevent new users from writing an unnecessary number of lines to the batch input file. To prevent the form from being displayed, add the following environment variable: In the pds.cmd file, $ENV{’NO_CONFIRM_WRITE_BJ’} = ’anything’; 13. Select By Line ID
Plant Design System (PDS) ISOGEN
113
Batch Isometric Extraction The Select by Line ID button can be used instead of the various search criteria to select lines for the batch input file. It allows you to select individual lines for extraction as opposed to defining different search criteria to select a specific group of lines. a. Select the Select By Line ID button. The system displays the List Iso Areas form.
Select an iso area and the accept button. The system displays a second Create Batch Job Input form which lists all lines contained within the selected iso area.
The Rev No field displays the number of the last extracted revision. If the line has never been extracted, the revision number displays as –1. After the line is extracted the first time with the Increment Revision Number option turned on, the revision number displays as 0. After the second extraction, the revision number displays as 1, and so on. b. Select the lines to be included in the batch file. OR Select the Type field gadget and select the appropriate isometric drawing type. Using this option will help limit the number of drawings displayed for selection. OR
114
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Select the Select All button to include all of the listed files in the batch file. OR Select the Iso Area List button to select a different iso area from the List Iso Areas form. c.
Use the Reset Selection button at any time to cancel all previous line selections. Select the accept button once all of the appropriate lines have been selected. The system activates the third Create Batch Job Input form. The By, Chk, Date and Description fields will be initialized with the input values that were entered in step 8.
d. If necessary, select the By, Chk, Date, and Description fields on the form and key in the appropriate information for each line.
14. 15.
16.
17.
If any of the previously mentioned fields are revised, each line is posted to the batch input file with separate option lines. If the fields are not revised, all of the selected lines will be posted to the batch input file under the same option lines. e. Select the accept button. The system posts the list to the batch input file. Iso Type This field is for review purposes only. It displays the type of drawings that are listed. Iso Area List This button displays the List Iso Areas form. When an Iso area is selected from the form and accepted, the system returns to the Create Batch Job Input form with the iso area in the Iso Area field. Drawing List This button displays the List Iso Areas form. Once an area(s) is selected and accepted, the systems displays the List Drawings form. Select the cancel button to dismiss the form and return to the Create Batch Job Input form. Schedule Batch Job This button displays the Schedule Batch Job form. Refer to the next section, Schedule Batch Job (on page 117), for more information.
Plant Design System (PDS) ISOGEN
115
Batch Isometric Extraction Search Criteria
Type Select the Type field gadget and select the appropriate isometric drawing type. Use this option to help limit the number of drawings displayed. Iso Area Key in the name of the iso area that you want to extract lines from. OR a. Select the Iso Area List button.
The system displays the Iso Areas form.
b. Select the appropriate iso area and click the accept button.
The system returns to the Revise Drawing form with the selected area in the Iso Area field.
116
If you want to restrict the list further, you must supply additional criteria such as batch reference numbers and drawing numbers. An iso area must be selected before any other search criteria can be defined. Batch Reference. Key in the batch reference number of the lines you want to extract. To use batch reference numbers as criteria, specify them in individual drawing records when adding drawing records to the Project Control Database. Model Status Code Key in the status code if you want to restrict a list to all lines of a given status. Drawing Number Low / Drawing Number High These commands define, by drawing number, the range of lines to retrieve.
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction Key in a drawing number in each field to identify the range of lines to extract. OR a. Activate a cursor in the Drawing Number Low (or High) field by placing a data point. b. Select the Drawing List button. The system activates the List Drawings form.
c. Select the drawing that will represent the low (or high) drawing number and select the accept button. The system returns to the Create Batch Job Input form with the selected drawing displayed in the Drawing Number Low (or High) field.
Schedule Batch Job The Schedule Batch Job command allows you to schedule a batch job for isometric extraction. 1. Select the Schedule Batch Job button from the Batch Environment form.
The system activates the Schedule Batch Job form. 2. Batch Input File Key in the name of the batch input file that was previously created using the Create Batch Job Input command from the Batch Environment form. Blank fields in the file specification will be defaulted according to the current default directory.
If the file name does not exist, an error message will be displayed at the bottom of the form. If the file name is valid, the remaining fields in the form will be given default values with the exception of the Run Time fields. 3. System Log File Key in the name of a log file. This field allows you to create a log of the command execution as the job processes in batch. This log is useful when you are having difficulties getting the batch software to operate. It contains a log of all error messages issued by the various software modules used to create an isometric.
Plant Design System (PDS) ISOGEN
117
Batch Isometric Extraction The System log file (.job file) is different from the batch log file (.log file) created by the batch procedure. The system log file is named using the batch input file name together with a file extension of .job. The batch log file contains an entry for each attempted run together with an error code and/or message when the run fails.
All .job and .log files are written to the same directory as the batch job input file. If this is not the case, have your system administrator check the hosts.nqs file to verify write permissions. If the batch job input file name remains the same, the .log file will maintain a cumulative history of each successive run. 4. Job Name Key in a batch job name. This is the name for the batch run which will show up in the batch queue when you key in the qstat PDisocreate command. The default job name is the batch input file name. 5. Process Queue Select one of the queues from the pull down list. The selected batch queue will extract the lines as defined in the batch input file.
The queues displayed in the Process Queue field are chosen first from the queues defined in the PDiso_batch 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 Process Queue list from locally defined queues. Valid queue names include: PDiso_batch, PDiso_bat_1, PDiso_bat_*. 6. Mail Notify Key in the email path of the machine that will be sent a mail message when the batch iso processing completes. A default for this field is provided by your system manager when the iso extraction product is installed on your system. The mail message contains the identification of the batch job input file, the Project Control Database name, a brief error message, and an error code. The error code is explained in more detail in the appendix. 7. Plot Queue Select one of the queues from the pull down list. This field is only displayed if the file defined in the Batch Job Input File field was created with the Submit for Plotting toggle turned on. Refer to Create Batch Job Input (on page 109) for more information on defining batch job input files.
The queues displayed in the Plot Queue 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 Plot Queue list from locally defined queues. If locally defined queues are used, only the pipe queues that are defined will be displayed in the Plot Queue pull down list. To display local device queues, create a pipe queue that points to the device queue. Valid queue names include: PDiso_plot, PDiso_plot_1, PDiso_plt_*. 8. Plot Copies Key in the number of copies to be plotted for each extracted line. 9. Do Not Generate PDME Data / Generate PDME Data
118
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction When set to Generate PDME Data, ISOGEN creates a .p file for each extracted iso sheet in the iso output directory. The resulting .pXX file is used when exporting data to PDME (Plant Data Maintenance Environment). Refer to the Export to PDME command in the PDS Project Administrator document for information. When using this option, Intergraph options 4 (ISOGEN component vs sheet number file) and 20 (Intergraph MTO Neutral File) must be set to 1 (active). 10. Do Not Extract Existing Sheets / Re-Extract Existing Sheets When set to Do Not Extract Existing Sheets, ISOGEN extracts the line and determines the amount of information that will be placed on each sheet and splits them accordingly. When set to Re-Extract Existing Sheets, ISOGEN extracts the line normally. However, unlike the previous toggle setting, the system honors the previous extraction's pagination. Refer to Repeatability (on page 285) for additional information. This toggle should be set to Do Not Extract Existing Sheets if extensive changes are being made to a pipeline. If extensive revisions are made to a line and the previous pagination is honored, the result may be a sheet that contains too much information to decipher. 11. Do Not Save Sheet Extraction Data / Save Sheet Extraction Data When the toggle is set to Save Sheet Extraction Data, the system generates and stores repeating data in the project and design databases. Repeating data includes such information as: traversal startpoint (saved to the project database) and the extracted item's iso sheet number (saved to the design database). Refer to Repeatability (on page 285) for additional information. This toggle should be set to Do Not Save Sheet Extraction Data until the design is stable and your isometrics are ready to be issued for the first time. 12. Verify On / Verify Off toggle Select the Verify On option to turn on batch job verification. Select the Verify Off option to turn off batch job verification.
When verification is on, a log of all system commands executed by the batch extraction procedure is saved in the iso output directory. Do not enable verification when large numbers of isos are being created since the resulting log files will use a large amount of disk space. 13. Debug On / Debug Off toggle Select the Debug On option to enable the debugging logic in the batch job. Select the Debug Off option to disable the debugging logic in the batch job. The debugging logic causes the values of several batch procedure variables to be displayed in the system log file. This option is useful for tracking down problems or submitting problems to Intergraph. 14. Submit Batch Immediately/Delay Batch Submit Time toggle Select the Submit Batch Immediately option to run the job immediately. Select the Delay Batch Submit Time to specify a run time for the job. Define the run time by keying in the day of the week (Mon, Tue, etc.), the time and then select AM or PM.
15. After all fields contain the appropriate information, select the accept button. As described earlier, a batch job log file (containing an entry for each attempted extraction) is created and updated as the batch job executes. Examine this log after the job finishes to see
Plant Design System (PDS) ISOGEN
119
Batch Isometric Extraction that all drawings were successfully completed. When drawings fail, consult the appendix for a more detailed explanation of the error code and message found in the log file. Also, check the .err files produced by the ISOGEN interface to make sure that the drawings do not contain errors. The batch shell marks each entry in the batch job input file as it is processed. Therefore, the batch procedure can be stopped and then restarted at any later time without causing drawings that have already completed to be rerun. If the system goes down and the job is not restarted automatically, it can be restarted using the Schedule Batch Job command. Drawings that have already been created will not be re-executed.
Reports The Reports command allows you to define the report type and to choose whether or not an area or drawing will be included in the report. Before reports can be printed, a pipe queue named PDprint must exist. For information on creating pipe queues for PDS, refer to the section Printer/Plotter Setup in the PD Project Administrator (PD_Project) Reference Guide. 1. Select the Reports button from the Batch Environment form.
The system displays the Batch Data Reports form.
2. Key in the report filename in the Output File field. If the system default variable, ISOREPORT, is exported in the control.sh file, the system will default to that value. For example: ISOREPORT=node:/usr/directory. 3. Choose a report type.
Area Summary creates an area summary report which shows all of the data associated with one or more piping areas. This report lists information such as: Equipment Areas
120
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction
Continuation Areas The Current Default Set User Data
Default (Options) Summary creates an options summary report which shows all default sets. This report lists information such as: ISOGEN Project Options Information on Each Default Set (such as the seed file, plot file, the default output path and border file defined for each default set)
Drawing Summary creates a drawing summary report which shows selected data about each drawing that you are reporting. This reports lists information such as: Drawing Number Revision Number Most Recent Revision Date Drawing Number Number of Sheets Most Recent MTO Date
Drawing Revision History creates a revision history report which shows the revision dates for each revision of the drawings being reported. This report lists information such as: Line Number Type of Isometric Drawing Number List of Drawing Revision Dates (up to the last five)
Search Criteria: The following are search criteria that can be used separately or together to locate a drawing or group of drawings within an iso area. All defined search criteria must be met before a drawing can be included in the report list. If no search criteria is defined, the system generates reports on the entire project control database.
Iso Area Key in the name of the iso area that you want to extract lines from. OR a. Select the Iso Area List button.
Plant Design System (PDS) ISOGEN
121
Batch Isometric Extraction The system displays the Iso Areas form.
b. Select the appropriate iso area and the accept button. The system returns to the Batch Data Reports form with the selected area in the Iso Area field. If you want to restrict the list further, you must supply additional criteria such as batch reference numbers and drawing numbers.
Type Select the Type field gadget and select the appropriate isometric drawing type. Using this option will help limit the number of drawings displayed.
Batch Reference Key in the batch reference number of the lines you want to extract. OR Select the List Drawing button for a list of batch reference numbers. To use batch reference numbers as criteria, specify them in individual drawing records when adding drawing records to the Project Control Database.
Model Status Code Key in the status code if you want to restrict a list to all lines of a given status.
Drawing Number Low / Drawing Number High 1. Drawing Number High and Drawing Number Low define, by drawing number, the range of lines to extract. 2. Key in a drawing number in each field to identify the lines to extract. OR
122
Plant Design System (PDS) ISOGEN
Batch Isometric Extraction a. Activate a cursor in the Drawing Number Low field by placing a data point. b. Select the Drawing List button. The system activates the List Drawings form.
c. Select the drawing that will represent the low drawing number and select the accept button. The system returns to the Batch Data Report form with the selected drawing displayed in the Drawing Number Low field. d. Repeat the above steps for the Drawing Number High field. 3. Model Revised Date toggle field Select the Use Model Revise Date option to specify that only lines whose Model Revised date is greater than the last drawing revision date can be included in the list of lines to extract. 4. Select one of three print options. Print/Delete Print/Save Save
Plant Design System (PDS) ISOGEN
123
Batch Isometric Extraction If the Print/Delete or Print/Save option is selected, the system displays a scroll field that lists available printing queues.
Select a print queue. If there is no queue connected to the client workstation, the system defaults to the Save option. 5. Select the accept button.
The system initiates report generation.
124
Plant Design System (PDS) ISOGEN
SECTION 6
Interpreting the HITS Report - PD_ISO The HITS report is a diagnostic tool generated by the Intergraph interface to ISOGEN. You can use this report to analyze the data collected from the 3-D piping model when a problem extracting an isometric occurs. This report can help you determine whether or not the problem exists in your model, in the ISOGEN interface or in ISOGEN itself. The HITS report filename is formed from the output isometric design filename. Isometric design filename is concatenated with the file extension .h. For example, if the isometric design filename is OWS1101.ISO then the HITS report filename will be OWS1101.h. The report is created in the default directory at the time the iso is created. One of the options in the ISOGEN interface defaults file allows you to generate a HITS report only and not an intermediate data file (IDF). You may not always want to generate an IDF with a HITS report. The run time to generate both an IDF and a HITS report is significantly longer than the run time to generate a HITS report only.
See Also Example HITS Report (see "Example HITS Report - PD_ISO" on page 125) Section 1: Basic Input Data and Raw Design File Data (see "Section 1: Basic Input Data and Raw Design File Data - PD_ISO" on page 129) Section 2: Design File Data Stored by Coordinate (see "Section 2: Design File Data Sorted by Coordinate - PD_ISO" on page 130) Section 3: Tracing Data (see "Section 3: Tracing Data - PD_ISO" on page 131) Section 4: Design File Data Sorted by Topo (see "Section 4: Design File Data Sorted by Topo PD_ISO" on page 131) Section 5: Design File Data in IDF Order (see "Section 5: Design File Data in IDF Order - PD_ISO" on page 138) Using the HITS Report to Solve Problems (see "Using the HITS Report to Solve Problems PD_ISO" on page 143)
Example HITS Report - PD_ISO The following section discusses an example of a HITS report. The HITS report is composed of 5 basic sections. Refer to the following figure for an illustration of each of the five sections.
Plant Design System (PDS) ISOGEN
125
Interpreting the HITS Report - PD_ISO The example HITS report in this section was generated using the following line.
126
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO
Date: 30-MAR-1994 02:03:53 Project Database: pd_stdeng_o43 Model Files: skiso3 skiso1 38eqp01 40eqp01
Plant Design System (PDS) ISOGEN
127
Interpreting the HITS Report - PD_ISO
128
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO
Section 1: Basic Input Data and Raw Design File Data PD_ISO The first section of the HITS report consists of basic input data and raw design data. The basic input data consists of the date the report was executed, project name and a list of model names that were extracted. Each column of the raw design file data is described below. Name
If Intergraph option 61 is set to 1, the name will be the first four characters of the component item name. Otherwise, a generic item name will be output.
occ
The component database occurrence number (excluding the partition number). Note that some PIPE components have an occurrence number greater than 30000. This occurs whenever olet type components are attached to a pipe. The software breaks these pipes into multiple sections. The newly created pieces of pipe receive occurrence numbers in the 30000+ range to distinguish them from the original pipe.
cp#
The connect point number
x,y,z
The coordinate in the design file coordinate system and is not adjusted for the global origin
node
A node number assigned to all connect points other than the origin. A special node number, -1, is reserved for line endpoints. Two connect points that have the same node number are connected to each other in the model.
direct
A direction list number. The direction list number identifies all those connect points that lie together on a straight line.
sect
Section number [always 0]
flags
A bit mask used internally by the software
topo
Topos [always 0]
branch
Branch flag [always 0]
sg_occ
The segment occurrence number. All connect points belong to or are owned by a segment in the piping model. This is the occurrence number of that owner segment.
Plant Design System (PDS) ISOGEN
129
Interpreting the HITS Report - PD_ISO
Section 2: Design File Data Sorted by Coordinate PD_ISO The second section of the HITS report consists of raw design file data for each connect point of the piping components that make up the network that is being extracted. The database search criteria (as defined in the options file LINE_ID_DEFINITION) from section 1 is used to find all of the appropriate segments. Once the segments are found, the software collects all of the components that are attached to the segments. Section 2 is the result of this activity. Section 2 contains several columns of data. Each column is described below: Name
If Intergraph option 61 is set to 1, the name will be the first four characters of the component item name. Otherwise, a generic item name will be output.
occ
The component database occurrence number (excluding the partition number). Note that some PIPE components have an occurrence number greater than 30000. This occurs whenever olet type components are attached to a pipe. The software breaks these pipes into multiple sections. The newly created pieces of pipe receive occurrence numbers in the 30000+ range to distinguish them from the original pipe.
cp#
The connect point number
x,y,z
The coordinate in the design file coordinate system and is not adjusted for the global origin
node
A node number assigned to all connect points other than the origin. A special node number, -1, is reserved for line endpoints. Two connect points that have the same node number are connected to each other in the model.
direct
A direction list number. The direction list number identifies all those connect points that lie together on a straight line.
sect
Section number [always 0]
flags
A bit mask used internally by the software
topo
Topos [always 0 here]
branch
Branch flag [always 0 here]
sg_occ
The segment occurrence number. All connect points "belong to" or "are owned" by a segment in the piping model. sg_occ is the occurrence number of that owner segment. Section 2 is primarily used for examining the amount of data pulled in from the models through the database search criteria. Some of the data for a specific connect point is sometimes useful, particularly the occurrence number.
130
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO
Section 3: Tracing Data - PD_ISO Section 3 of the report, Tracing Data, is a record of the actions the software is taking in building the internal data structure of the piping network. This section is primarily useful to Intergraph for investigating software problems. The last statement in section 3 states how many disconnected sections of piping exist in the network identified in the database search criteria. If the number of sections is greater than 1 then the line is not extracted and the intermediate data file is not generated. ISOGEN does not allow multiple, disconnected sections of piping to be extracted into a single iso. The following is a list of possible reasons why a network might be disconnected and some suggested solutions: 1. The database search criteria identified more than one pipeline and the pipelines are not connected together. The solution here is to change the search criteria so that only the piping that you really want to extract is pulled in. 2. The pipeline being extracted is incomplete and portions of it do not have components on it. The solution is to place all of the components on the line. 3. Although the line is finished, there is a part of it that appears to be connected, but is not. For a line to be considered connected the connect points from two different components must be within 20 uors of each other. In this case you should examine section 2 of the HITS report to find a connect point whose node number is -1 (which indicates that it is a line endpoint) even though you know it should be connected to something. This is usually quite simple when the line is small. When you find the connect point, use the coordinate to view and repair the disconnected graphics. When the line is complicated, you can use section 4 of the HITS report (see the section Tracing Data) to make a sketch that identifies the disconnected point.
Section 4: Design File Data Sorted by Topo - PD_ISO Section 4 of the HITS report is probably the most important one. This section is really a printout of the internal data structure that represents the piping network. This data is organized on the basis of topos.
Plant Design System (PDS) ISOGEN
131
Interpreting the HITS Report - PD_ISO A topo is a construction used to group the data representing the pipeline topology. By definition a topo is a string of piping that starts at a network endpoint or a branch point and ends at a network endpoint or another branch point. A pipeline network may consist of a single topo or dozens of topos depending upon its configuration.
The line in the figure above consists of one topo because it does not contain any branch points. The beginning of the topo is a line endpoint as is the end of the topo.
132
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO The line in the figure above contains two topos due to the branch component in it (the tee). The first topo consists of the line from endpoint 1 to endpoint 2 (the header of the pipeline). The second topo consists of the piping from the center of the tee to line endpoint 3.
The line in the figure above contains three topos because there are two branches in it. The first topo again consists of the line from endpoint 1 to endpoint 4. The second topo consists of the line from connect point 1 of weldolet 1 to endpoint 2. The third topo consists of the line from connect point 1 of weldolet 2 to endpoint 3.
The line in the figure above consists of two topos. One topo is comprised of the line header from endpoint 1 to endpoint 2. The other topo starts at the center of one tee and goes to the center of the other tee. The data in section 4 of the HITS report is sorted primarily by topo number. At the very beginning there are several lines where the topo number is zero. These are component origins which do not receive topo numbers or node numbers they should be ignored. Subsequent to the lines where the topo number is zero are lines for the first, second and subsequent topos. The secondary sort key for the data in section 4 of the report is node number. Thus, within a topo the data is sorted by node number. This results in connect points with the same node number being adjacent to each other in the report. The result is that section 4 of the HITS report contains a trace of each topo of the line. Example 1: The following is an excerpt from a HITS report section 4:
Plant Design System (PDS) ISOGEN
133
Interpreting the HITS Report - PD_ISO Name E90L E90L PIPE PIPE E90L E90L PIPE PIPE GATR GATR PIPE PIPE
cp# 1 2 1 2 2 1 2 1 1 2 1 2
node -1 1 1 2 2 3 3 4 4 5 5 -1
topo 1 1 1 1 1 1 1 1 1 1 1 1
This trace consists of a single topo. The first endpoint is connect point 1 of a 90 degree elbow. Connect point 2 of the elbow is connected to connect point 1 of a pipe. Following this logic, the sequence of components starting from the top is: elbow -> pipe -> elbow -> pipe -> valve -> pipe. This same procedure may be followed to sketch out each network topo. Topo sketches are useful if you are interested only in the sequence of components in a particular region of the line. If you are interested in the entire network, connect the topos together. The topos are connected together by the branch column in section 4 of the report. The branch column is used together with the last column. The last column in section 4 is a report line number. You can see by looking back at Figure 6-1 that the last column starts out at 1 and is incremented for each line in section 4. When the branch column contains a nonzero value then this indicates that the node is a branch point. The value of branch refers you to the line number of the report where the connecting topo begins. Example 2: The following is an excerpt from a HITS report section 4: Name occ# cp# node topo branch PIPE 10 1 -1 1 0 1 PIPE 10 2 1 1 5 2 PIPE 30001 1 1 1 5 3 PIPE 30001 2 2 1 0 4 WOL 15 1 1 2 -2 5 WOL 15 2 3 2 0 6 PIPE 35 1 3 2 0 7 PIPE 35 2 -1 2 0 8
134
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO The network is composed of two topos. Topo 1 is simply two pipes. Topo 2 consists of a weldolet connected to a piece of pipe. Note that the occurrence number of the second pipe in topo 1 indicates the model contains a single pipe which the software split into two at the olet. Figure 6-5 shows the Network for Example 5.
The value for branch at node 1 is 5. Looking at line 5 in the report we see that it is the first line of topo 2. Thus topo 2 connects to topo 1 at node 1. This is confirmed by the fact that the node numbers where topo 2 connects to topo 1 match. That is, the WOL cp1, PIPE (occ 10) cp2, and PIPE (occ 30001) cp1 are all node number 1. The value of branch for cp1 of the WOL is -2. The negative sign indicates that this is a "back pointer". The back pointer is exactly the same as any other branch value except that it (usually) points back to a previous topo rather than forward to a subsequent topo. Note that where two or more topos are connected together the branch numbers must agree. In Example 5 they do. The back pointer on topo 2 points back to line 2 while the forward pointer on topo 1 points to line 5. In Example 2, the branch flag pointed to the start point of the connecting topo. It can also happen that the branch flag points to the endpoint of the connecting topo. In this case you traverse the topo in reverse order. Example 3: Name occ# cp# node topo branch . . . PIPE 10 1 2 3 0 20 PIPE 10 2 21 3 0 21 90E 35 2 21 3 0 22 90E 35 1 22 3 0 23 PIPE 46 1 22 3 0 24 PIPE 46 2 23 3 53 25 PIPE 30003 1 23 3 53 26 PIPE 30003 2 24 3 0 27 . . . PLUG 76 2 -1 7 0 46 PLUG 76 1 10 7 0 47 BLV 82 1 10 7 0 48 BLV 82 2 11 7 0 49 NIPL 103 2 11 7 0 50 NIPL 103 1 12 7 0 51
Plant Design System (PDS) ISOGEN
135
Interpreting the HITS Report - PD_ISO SOL SOL . . .
110 110
2 1
12 23
7 7
0 -25
52 53
In Example 3, topo 3 consists of pipe, elbow, pipe, pipe. Topo 7 is a typical drain assembly plug, block valve, nipple, sockolet. Topo 7 connects to topo 3 at line 53 in the report (the value of branch on line 25 is 53 and the value of branch of line 53 is -25). In this case, the value of branch on topo 3 points to the bottom of topo 7 and the network structure is obtained by moving up topo 3 rather than down (See Figure 6-6).
Example 4: The following data is from section 4 of a HITS report: Name Occ cp# Node Topo Branch 90E 37 1 -1 1 0 1 90E 37 2 1 1 0 2 PIPE 101 1 1 1 0 3 PIPE 101 2 2 1 0 4 FLWN 22 2 2 1 0 5 FLWN 22 1 3 1 0 6 GAT 54 1 3 1 0 7 GAT 54 2 4 1 0 8 FLWN 11 1 4 1 0 9 FLWN 11 2 5 1 0 10 T 36 1 5 1 15 11 T 36 2 6 1 15 12 PIPE 11 1 6 1 0 13 PIPE 11 2 -1 1 0 14 T 36 3 7 2 -11 15 PIPE 12 1 7 2 0 16 PIPE 12 2 -1 2 0 17 In Example 4, the tee is slightly different from the olet type components. Branch flags are set on both connect points 1 and 2 of the T and the node numbers do not match where topo 2 connects to
136
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO topo 1. This is a consequence of the fact that node numbers are not assigned to component origins. See Figure 6-7 which shows the Network for Example 4.
Example 5: Name Occ PIPE 23 PIPE 23 REDE 24 REDE 24 PIPE 13 PIPE 13 SOL 56 SOL 56 PIPE 42 PIPE 42 PIPE 26 PIPE 26
cp# 1 2 1 2 1 2 1 2 1 2 1 2
Node -1 1 1 2 2 -1 3 4 4 -1 5 -1
Topo 1 1 1 1 1 1 2 2 2 2 3 3
Plant Design System (PDS) ISOGEN
Branch 0 1 0 2 7 3 11 4 0 5 0 6 -3 7 0 8 0 9 0 10 -4 11 0 12
137
Interpreting the HITS Report - PD_ISO In Example 5, topo 1 consists of a pipe connected to an eccentric reducer which in turn is connected to another pipe. Notice, however, that the branch flag is set to two different numbers on the reducer. This indicates that the reducer is tapped twice. The branch flag on the first connect point points to the topo connected at the first tap while the branch flag on the second connect point points to the topo connected to the second tap. A tap is always a branch starting point and thus is always the start point of a new topo. Refer to Figure 6-8, which shows the network for Example 5.
If you generate some HITS reports and practice sketching out the pipeline networks, you will become familiar with the report contents and better understand the concepts presented in the examples above.
Section 5: Design File Data in IDF Order - PD_ISO Section 5 of the HITS report contains a record of how the network is traversed as the intermediate data file is being generated. The software examines the network of piping and chooses the best (that is, the one least likely to result in problems from ISOGEN) topo to begin the network traversal on. ISOGEN prefers certain navigation sequences over others and the interface software tries to choose the optimal sequence. ISOGEN also requires that the traversal of the network be branch first order. This means that whenever a branch is encountered in the network, the traversal must head down the branch before continuing down the header. To traverse the network in branch first order manner you start on the header topo and travel connect point by connect point until the value of branch is greater than 0 at some node. When branch is positive then you jump down to the new topo and start traversing it until you come to another branch or to the end. If you encounter another branch then you must jump again to another topo. When the end of the topo is found then you return to the topo from which you jumped and continue tracing.
138
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO Example 6: The following is an example of a network:
In Example 6, topo 1 consists of a header, two pipes, and the run of a tee. Topo 2 consists of a branch, the branch leg of a tee and a branch pipe. Following the rules given above for traversal of the network would yield the following trace:
Step 1 travels from one end of the first pipe to the other. Following the first pipe we travel into the tee. Notice that although the origins do not have node numbers they appear in the traversal whenever a change in direction occurs. This means that, for the tee, the traversal occurs from connect point 1 to the origin in step 2. At this point the branch flag is positive and so a jump occurs to topo 2. On topo 2 we travel from the origin of the tee to connect point 3 (which is the branch connect point) in step 3. In step 4 we travel down a pipe which is the last component on the topo. We then jump back to topo 1 and in step 5 travel from the tee origin to connect point 2. Finally, in the last step we traverse the remaining pipe on topo 1. Refer to the next picture for an illustration of this traversal.
Plant Design System (PDS) ISOGEN
139
Interpreting the HITS Report - PD_ISO The header topo number can be found by examining the first line in the traversal. In this case the first line consists of PIPE occurrence 10. Looking at the network description, observe that PIPE occurrence 10 is on topo number 1. This makes topo 1 the header topo.
In ISOGEN terminology one step in the above trace is termed a component leg. Straight through components like pipe, flanges, and valves consist of one leg. Change of direction components like elbows, angle valves and so on consist of two legs. Branch components like tee's, olets, 3-way and 4-way valves and crosses consist of three or four legs. In Example 9, the last leg of the tee is given a leg number of 4. By definition only 4-way components have a leg 3 (which would correspond to the 2nd branch leg). Branches off from components formed by taps are termed branch legs and are not given a number. Branch legs are treated as other branches are though. When a tapped component is encountered in the network then all the tapped legs must be traced before continuing down the topo. Although olet type components have a different connect point skeleton than tee's do they are treated similarly in the network trace. This is highlighted in the next example:
140
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO Example 7: The following is a network:
The network trace for this network is:
In Example 7, the first leg of the olet goes from connect point 1 to connect point 1. It is analogous to the step with the tee where traversal goes from connect point to the origin. In this case the traversal does not go anywhere and therefore is called a zero length leg. The second leg traverses from cp1 to cp2 analogous to the previous example's traversal from the tee origin to cp3. After the branch topo has been traversed we return to the olet for leg 4 which again goes from cp1 to cp1 another zero length leg. This step is analogous to going from the origin to cp3 in the previous example. Notice also the traversal through the elbow. Since the elbow causes a change of direction, it is traversed in two legs: 1) from cp1 to the origin and 2) from the origin to cp2. Sometimes the traversal of the network requires traveling into the branch leg of a branch component. When this happens the leg numbers are assigned somewhat differently on the branch component.
Plant Design System (PDS) ISOGEN
141
Interpreting the HITS Report - PD_ISO Example 8: The following is a partial network:
In Example 8, a lower numbered topo (topo 4) contains a back pointer to a higher numbered topo (topo 7). Whenever this happens, the traversal will enter branch. The trace for this part of the network would be:
142
Plant Design System (PDS) ISOGEN
Interpreting the HITS Report - PD_ISO In this example, the branch leg of the tee is leg 1 since it is traversed first. Legs 2 and 4 are assigned arbitrarily in this situation and so tracing may go either way (ISOGEN has no preference). Refer to Figure the following figure which shows this network traversal.
Using the HITS Report to Solve Problems - PD_ISO When you have difficulty extracting a line, the first thing you should do in analyzing the problem is to sketch out the network. Often this is enough to identify the problem. If the structure in section 4 of the report is incorrect that is, the topos are not correctly defined and connected or the pointers appear incorrect then ISOGEN's input will be wrong and the drawing will definitely be incorrect. When the data structure represented in section 4 of the report is incorrect then you can conclude that either the interface has a bug or there is a problem in the model. Typical model problems include such things as disconnected sections and overlapping components or pipes. When the modeler has inadvertently placed two pipes on top of each other you will get an error message at the top of the HITS report stating this. The message will also report a node number where the problem was detected. By getting the coordinate of the node you can pinpoint where in
Plant Design System (PDS) ISOGEN
143
Interpreting the HITS Report - PD_ISO the model the problem occurs. This can also occur where the connect points of components overlap each other and are not properly connected. Notice that one of the columns in section 4 of the report is called section. In a correct network all of the topos should have a value of 1 in this column. When the network is composed of multiple disconnected sections, however, some topos will contain a value other than 1. In this case the network for each section should be sketched out. It should be apparent after doing this where the different sections should have been connected in the model and, therefore, where the trouble spot is. Another problem that might occur is that components that should all be colinear are not. This is detected by examining the direction list number. If the direction list changes for example from one pipe to another then a problem exists in the model and the line cannot be extracted properly. Mismatches between the design file and database can also cause iso extraction failures but these types of problems should be trapped and reported adequately in other areas of the software. You should not need to rely on the HITS report to find these kinds of problems. When the data structure in section 4 of the report is correct then the traversal in section 5 should be examined. Even if the network is correct, some other bug can cause the network traversal to fail. Again, if the traversal is incorrect then ISOGEN will definitely fail. When both the network and the traversal are correct, there is most likely a problem with ISOGEN. When ISOGEN is at fault, then one of the following scenarios is true: 1. The drawing appears correct for the most part but some aspect of it is incorrect. When this happens there is usually some option or combination of options that have been enabled that resulted in the problem. The best way to find the cause of the problem is to start with a basic drawing generation setup that contains few "special" options. Then add a few options at a time until the problem is reproduced. Finally, through a process of elimination identify the option that is causing the problem. All failures of this type should be reported to Intergraph. 2. The drawing or one sheet of it is scrambled a total failure. When this happens it is usually the case that disabling options will not result in the drawing working though sometimes it does. The best thing to do when this happens is to try and re-extract a smaller portion of the line if possible. The failure should also be reported to Intergraph. When any sheet of an ISOGEN drawing fails, ALL sheets from the same pipeline may contain errors and are suspect.
144
Plant Design System (PDS) ISOGEN
SECTION 7
The Options File - PD_ISO The options file consists of a set of options and tables that drive the interface to ISOGEN. You can modify the options file to customize the drawings that are produced by ISOGEN. See the appendices for an example of an options file. Information contained in the remainder of this manual assumes that you have knowledge of the following: The PDS database structure PDS Reference Database The Label Description Library Utility The Standard Note Library Material Description Libraries
In This Section 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
Plant Design System (PDS) ISOGEN
145
The Options File - PD_ISO
File Structure The options file is composed of two sets of options and several tables. Each option block and table is preceded in the options file by a keyword that identifies it. The keyword must begin in column 1 and should NOT be surrounded by single quotes. The keywords and data that follow them can appear in any order in the options file. You can put comments to the right of any table entry but not to the right of a keyword. You can also have comments preceding any keyword or following the last entry in a table. Comments either preceding a keyword or following the last table entry must have an exclamation point (!) in column 1 to identify it as a comment. Keywords are always followed by a number - starting in any column - that identifies the number of table entries. It is valid for the number to be zero, indicating that there are no table entries. If the number that precedes a table does not match the number of entries in the table, a warning message is generated at the time the table is read in. Entries in tables consist of a row of numbers and sometimes character strings that are separated by commas ( , ). Character strings that are part of a table entry MUST be surrounded by single quotes (' ') or double quotes (" "). A typical table in the options file might appear as:
Where: TABLE_KEYWORD
is the table key word discussed above.
Nrows
is the number of table entries.
n1, n2, ...
are numbers in the first table entry.
'c1'
is a character string in the first entry.
m1, m2, ...
are numbers in the last table entry.
'cm' is a character string in the last entry. The options file keywords consist of the following: ISOGEN_OPTIONS_BLOCK (on page 147) INTERGRAPH_OPTIONS_BLOCK (on page 149) FILES (see "The Files Table" on page 187) USER_DEFINED_WELDS (on page 188) WELD_PREFIX (on page 189) DETAIL_SKETCH_FACILITY (on page 190) PIPELINE_HEADER (on page 191) ATEXT_SPECIFICATIONS (on page 196) INGR_ATEXT_SPECIFICATIONS (on page 197) LINE_ID_DEFINITION (on page 198)
146
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO TYPE_1_LABELS (on page 199) TYPE_2_LABELS (on page 202) TYPE_3_LABELS (on page 204) START_POINT_NOTES (on page 206) PRIMARY_ORIENTATION_NOTE (on page 210) SECONDARY_ORIENTATION_NOTE (on page 211) END_POINT_COMPONENT_LABELS (on page 208) NOZZLE_NOTE (on page 209) DOTTED_SYMBOLOGY_CODE_LIST_VALUES (on page 212) NOMTO_CODE_LIST_VALUES (on page 213) SHOP_FABCAT_CODE_LIST_VALUES (on page 214) OFFSHORE_FABCAT_CODE_LIST_VALUES (on page 215) MOVABLE_TEXT (on page 216) NEW_SYMBOL_KEYS (on page 219) GENITM_NOTE_FORMAT (on page 219) ALTERNATE_DESCRIPTION_INDEX (on page 220) USER_DEFINED_IMPLIED_ITEM_BOM (on page 221) USER_DEFINED_GENERATED_ITEM_BOM (on page 224) USER_DEFINED_COMPONENT_BOM (on page 226) NON_DIMENSIONED_SUPPORTS (on page 228) When an option in an option block is set to 1, it is enabled.
ISOGEN_OPTIONS_BLOCK The ISOGEN options block is a group of options that are input directly to ISOGEN. These options do not affect the ISOGEN interface, but control the different characteristics of drawing output. However, some options selected in the ISOGEN options block might require that entries be defined in certain of the options file tables in order to work properly. The ISOGEN options block consists of 140 numbers arranged in 10 rows of 14. Each number is referred to as a "word" in the options block. Row 1 contains words 1 through 14, row 2 contains 15 through 28 and so on. The positioning of a number within a word is important. Thus, in editing the options block be sure to keep the units digit of the entry in the same column. Some Intergraph options have multiple switch settings (such as A, B, C, D). Intergraph switch settings are read from right to left (D-C-B-A). For example, if an option is set to 21, 1 represents switch position A and 2 represents switch position B. When setting an option with multiple switches, leading zeroes may be omitted, but trailing zeroes must be included. The following options should not be changed from their default settings. These options are not used in the Intergraph environment. Words
Function
1
Plot length control
7
Drawing control
31
Iso output file
32
Plotter scale factor
Plant Design System (PDS) ISOGEN
147
The Options File - PD_ISO 33
Pipe detailed
43-51
Wastage factors
52
Equipment trim drawings
55-57
Diagnostic printing
58
Clear screen
69
Terminal type identification
79
Site assembly identification
125
Reserved
126
Reserved
129
Interactive editing
131
Test parameter
148
Be careful when changing words 34 (picture scale) and 38 (split control). Values other than the default sometimes result in drawing failure. Be careful modifying words 115 (angular tolerance) and 116 (linear tolerance). Large values of these options can cause sloped lines to be shown incorrectly. The Drawing control option (word 7) must be left at 0. ISOGEN will sometimes fail if forced to put more information on a sheet than it determines it can fit. You can minimize the number of sheets produced by increasing the sheet size. Option 8 (dimension line distance) does not work when it is set to give a dimension standout greater than 25 mm. In general, ISOGEN is more successful with a large sheet size than a small one. You can create virtually any size sheet - including one with a user-defined title block by using the drawing margin options (words 10-13) and the drawing size options (words 14-16). User-defined graphics in reference files must be positioned in drawing margins or in a reserved strip along the bottom of the drawing (option 35) in order for stacking of multisheet drawings to work properly.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
INTERGRAPH_OPTIONS_BLOCK The Intergraph options block is a group of options, numbered in the same way as the ISOGEN options (see the appendix titled Alias ISOGEN Tables), that directly control the actions of the ISOGEN interface. The specific meaning of each option is outlined below:
Plant Design System (PDS) ISOGEN
149
The Options File - PD_ISO
Word
Value
Meaning
1
0
Do not produce the ISOGEN MTO neutral file.
1
Produce the ISOGEN mto neutral file. (isoname.bom)
2
0
THIS OPTION MUST BE SET TO ZERO
3
0
Do not produce the ISOGEN printed parts list.
1
Produce the ISOGEN printed parts list. (isoname.prt)
0
Do not produce the ISOGEN component vrs sheet number file. This setting will not split the MTO neutral file.
1
Produce the ISOGEN component vrs sheet number file, isoname.sed. If the MTO map file includes component occurrence numbers and record types, this setting splits the MTO neutral file by sheet. Neutral files created by the split are named: isoname(sheet#).b(extnum).
0
Do not produce the ISOGEN cut pipe report.
1
Produce the ISOGEN cut pipe report. (isoname.cut)
4
5
When any of options 1-5 are set 0 (not generating a file), the files are in fact still created. However, the command procedures which run ISOGEN delete these files after the drawing is generated. 6
150
0
Disable the "CONNECTION NOT FOUND" message at line endpoints where no connecting component is found.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
7
1
Enable "CONNECTION NOT FOUND" message at line end points where no connecting component is found. (Does not apply to plugs, caps, and blind flanges.) This option can be Used to highlight the fact that no connecting component was found at a line endpoint. When no connecting component is found then implied materials cannot be generated at that endpoint. This option can make checking of the drawings easier.
0
Do not adjust connect point coordinates to the face-of-flange.
Plant Design System (PDS) ISOGEN
151
The Options File - PD_ISO 1
8
9
152
Adjust connect point coordinates to the face-of-flange. In the piping model, component connect points are placed midway through the gasket at flanged connections. When this option is disabled, dimensioning on the iso also goes to the center of the gasket. When the option is enabled, dimensioning is to the face-of-flange.
This Intergraph option has multiple switch settings (such as A, B, C, D). Intergraph switch settings are read from right to left (D-C-B-A). For example, if this option is set to 21, 1 represents switch position A and 2 represents switch position B. When setting an option with multiple switches, leading zeroes may be omitted, but trailing zeroes must be included. Position A
Bolt Length
0
Output bolt lengths in inches in the BOM printed on the iso.
1
Output bolt lengths in millimeters in the BOM printed on the iso.
Position B
Bolt Diameter
0 or blank
Output bolt diameter in the default units (as defined in ISOGEN option switch 41 and Intergraph option 43) in the BOM printed on the iso. When using this setting, AText -359 must be left blank.
1
Output bolt diameter in inches in the BOM printed on the iso. This setting overrides the setting defined with ISOGEN switch 41 (position A). When using this setting, AText -359 should be set to NPD and ISOGEN switch 65 (position B) must be set to 1.
2
Output bolt diameter in millimeters in the BOM printed on the iso. This setting overrides the setting defined with ISOGEN switch 41 (position A). When using this setting, AText -359 should be set to NPD and ISOGEN switch 65 (position B) must be set to 2.
val
Tolerance for considering valve operators and eccentric reducers to be skewed. Val is the maximum direction cosine times 1000. The
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO default value is 10 (or .01). 10
0
The commodity code description includes consideration of component schedule. Therefore, do not append the component schedule to the material description.
1
Commodity code description does not include consideration of schedule. Therefore, the component schedule is appended to the material description. The default value for the component schedule is ‘SCHEDULE‘, but this value can be redefined using INGR_ATEXT_SPECIFICATION 17.
Option 10 is not needed if label description library numbers, which output schedules, are embedded ([ ]) within material descriptions found in the Material Description Library. During extraction, the labels are expanded in the material description. For more information on the Label Description Library and the Material Description Library, refer to the Reference Data Manager document. The material description for an elbow appears as follows in the material description library where label 403 is defined to Output Component Schedule: "WELD ELL BE [403] CS ASTM A234-WPB" At extraction time, the label description library number [403] is expanded so that the description placed in the drawing is: "WELD ELL BE STD WT CS ASTM A234-WPB" These embedded attributes can also be included in the material descriptions for implied items like bolts and gaskets. 11
val
Piping component connection tolerance in UOR. The default value is 20 UOR. The minimum value is 20 UOR if val is set to less than 20. If the space between connect points is greater than the value defined by this option, the pipes/components are not considered connected.
Plant Design System (PDS) ISOGEN
153
The Options File - PD_ISO 12
val
Number of characters after which a line feed should be inserted in instrument tag numbers for display in an instrument bubble. (See also ISOGEN option number 123.) The following example assumes that the instrument tag number is INST-001.
1
When set to 1, a line feed is inserted after the first character.
10
Replace an embedded dash within the tag number with a linefeed.
11
Replace all dashes defined in the instrument tag with line feeds. The following example assumes that the instrument tag number is INST-001-ST.
13
0
Display all valve operators on the isometric regardless of whether or not they are displayed in the piping model.
1
Do not display valve operators on the isometric that are turned off within the model. This option can also be used in conjunction with Intergraph options 59 and 48 that deal with valve operator display and orientation notes.
154
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO 14
0
Generate implied materials. These include bolts, gaskets and field welds.
1
Do not generate implied materials.
This option allows you to do testing without incurring the overhead of generating implied materials. Execution of the ISOGEN interface takes a significantly longer time when bolts and gaskets must be generated. 15
16
0
Spool Numbering On (Uses consecutive numbering)
1
Spool Numbering Off
10
Spool Numbering On (This option uses consecutive numbering with the exception that spool numbering is set back to 1 for each new sheet.)
0
Generate the HITS report and the intermediate data file.
Plant Design System (PDS) ISOGEN
155
The Options File - PD_ISO 1
Generate only the HITS report. When generating only a HITS report an iso cannot be generated since no input to ISOGEN is produced.
2
Generate only the intermediate data file for batch extraction. (DO NOT generate the HITS file) Setting two should only be used with batch extraction. If DEBUG is ON for batch extraction, position A is reset to 0. The HITS file is automatically generated when using interactive extraction.
17
18
0
Continue trying to extract the line if a component is encountered that is not in the PDS to ISOGEN symbol map.
1
Stop extraction if a component is encountered that is not in the PDS to ISOGEN symbol map.
0
Generate coordinates in the DESIGN VOLUME coordinate system.
1
Generate coordinates in the PLANT coordinate system.
3
Generate coordinates in the DESIGN VOLUME coordinate system using large coordinates.
4
Generate coordinates in the PLANT coordinate system using large coordinates. Option 3 or 4 should be used if any coordinate can be outside the range plus or minus 13.3 miles in an English project or plus or minus 21.4 kilometers in a metric project. Coordinate System data is stored in the type 63 data of the piping model. For Interactive Extraction, the software reads the type 63 of the first model entered on the form. For Batch Extraction, the software reads the type 63 data from the first piping model in the area specified in each record of the batch input file.
19
1
THIS OPTION MUST BE SET TO 1.
20
0
Do not generate an Intergraph mto neutral file.
1
Generate an Intergraph mto neutral file. The naming convention: isoname+sheet number.b# (where # is the extraction number) is used when an Intergraph mto neutral file is generated. MTO neutral file generation is discussed in detail in the section The MTO Neutral File Record Map. Intergraph option 4 must be set to 1 in order to generate an mto neutral file.
21
156
0
Do not generate welds in the mto neutral file.
1
Generate welds in the mto neutral file where the welds listed on the mto do not appear on the corresponding isometric sheet.
2
Generate welds in the mto neutral file where the welds listed on the mto appear on the corresponding isometric sheet. As a result, using this option setting slightly increases run time and generates a larger intermediate data file.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO 22
0
Extract by substring of the line name attribute.
1
Extract by equality of the line ID attributes. The meaning of this option is discussed at length in the section Interactive Isometric Generation. Option 22 must be set to 1 when running batch isometric extractions
23
0
Use the system-defined nozzle connection note. The system-defined nozzle connection note is formatted as follows: NOZ: xxx - where xxx is the nozzle tag ITEM: xxx - where xxx is the equipment tag For flanged and female ends: size - rating - facing For male ends: size - facing - SCH
24
1
Use the NOZZLE_NOTE table in the options file to form the nozzle connection note.
0
Generate pipe supports in the intermediate data file.
1
Do not generate pipe supports in the intermediate data file.
Plant Design System (PDS) ISOGEN
157
The Options File - PD_ISO 25
0
Show bare branch weld as a length of pipe - with coordinate label pointing to CP2 of branch weld.
1
Show bare branch weld as a dot - with coordinate label pointing to CP1 of branch weld.
26
158
This Intergraph option has multiple switch settings (such as A, B, C, D). Intergraph switch settings are read from right to left (D-C-B-A). For example, if this option is set to 21, 1 represents switch position A and 2 represents switch position B. When setting an option with multiple switches, leading zeroes may be omitted, but trailing zeroes must be included. Position A
Inspection Number
0
Do not extract inspection numbers.
1
Extract inspection numbers. Do not display blank inspection number.
2
Extract inspection numbers. Display blank inspection numbers as defined by INGR_ATEXT_SPECIFICATION 16 (default as ****).
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
27
28
Position B
Inspection Number Enclosure type
0
bubble (default)
1
rectangle
2
rectangle with arrowed ends
3
rectangle with rounded ends
4
triangle
5
diamond
0
Generate component tags as -37 records in the intermediate data file.
1
Generate component tags as -22 records in the intermediate data file. This option must be set to 1 in order to generate instrument bubbles properly on both in-line and off-line instruments.
0
Do not replace the ISOGEN instrument dial symbol (IDPL or IDFL) with the instrument balloon.
1
Replace the ISOGEN instrument dial symbol with an instrument balloon.
Regardless of which setting is used, the instrument tag number is displayed inside of a circle. 29
0
Do not make off-line instruments no-mto.
Plant Design System (PDS) ISOGEN
159
The Options File - PD_ISO
1
Make all off-line instruments no-mto.
Offline instruments are defined as any instrument mapped to the ISOGEN symbol IDPL or IDFL. 30
160
0
Do not show reinforcing pads in the ISOGEN BOM.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
1
Show reinforcing pads in the ISOGEN BOM.
A reinforcing pad can only be shown in the ISOGEN BOM when the PDS branch component in the model is mapped to the ISOGEN component named TERF. The component in the model should have the commodity code and material description for the reinforcing pad. In PDS reference data, a reinforcing weld (RWeld) is defined as a component; however, ISOGEN software treats an Rweld the same as other welds included as part of a pipe. Therefore, an Rweld will not appear separately in the MTO on the face of the isometric drawing. For example, if the isometric drawing is extracted for any pipe having a branch with an Rweld, then the isometric drawing displays the Rweld symbol the same as that of other welds. In addition, the MTO does not display a description of the Rweld.
Plant Design System (PDS) ISOGEN
161
The Options File - PD_ISO The B file, which is output along with the isometric drawing and reports all the pipes and components, reports the Rweld. 31
0
Do not access the VALOPR table to map PDS symbol names and valve operator names to ISOGEN symbols.
1
Access the VALOPR table to map PDS symbols and valve operators to ISOGEN symbols. This option is provided because there are two ways to map a PDS symbol and valve operator to an ISOGEN symbol. One way is through the VALOPR table described in the section The Valve/Operator Table. The other way is through the PDS-to-ISOGEN symbol map discussed in the section The PDS-to-ISOGEN Symbol Map. When this option is set to 1, the ISOGEN symbol name obtained from the symbol map is replaced by an entry in the VALOPR table if it exists. A reinforcing pad can only be shown in the ISOGEN BOM when the PDS branch component in the model is mapped to the ISOGEN component named TERF. The component in the model should have the commodity code and material description for the reinforcing pad.
32
162
0
Do not generate implied materials from the reference database using table 212.
1
Generate implied materials from the reference database using table 212.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
This option must be enabled (set to 1) in order to generate implied materials in the mto neutral file and/or to generate a note on the drawing for the implied materials. Also, see Intergraph option 45. The generation of implied items from the Implied Material Data Table is triggered by special definitions you make in the reference database. Refer to the Reference Data Manager document for details. Refer to the Material Take-Off Options material i n the Project Administrator’s Reference Guide for more information. Material Takeoff Options that could affect the implied material output on the iso are stored in the type 63 data of the piping model. For Interactive Extraction, the software reads the type 63 of the first model entered on the form. For Batch Extraction, the software reads the type 63 data from the first piping model in the area specified in each record of the batch input file. 33
0
Do not generate chain wheel operators, extension stems or floor stands.
1
Generate chain wheel operators, extension stems and floor stands. Output information is based on the setting of Intergraph option 45. The prefixes for these items are defined by INGR_ATEXT_SPECIFICATIONS 4, 5, and 6. This option must be set in order to generate chain wheel operators, extension stems and floor stands in the mtoneutral file or to generate a note on the drawing. The generation of chain-wheel operators, extension stems and floor stands is triggered by definitions you make in the model for specific valves. Refer to the Piping Design Graphics Reference Guide for details on making these definitions. For these items the material description library is accessed by adding the operator number to the
Plant Design System (PDS) ISOGEN
163
The Options File - PD_ISO following strings:
34
Item
Prefix
Example
Chain Operators
CHAIN_
CHAIN_1001
Extension Stems
XSTEM_
XSTEM_2001
Floor Stands
FSTAND_
FSTAND_3001
0
Do not generate the title block data files.
1
Generate the title block data files. The title block data files are used by the batch extraction software to fill out drawing title blocks. If this option is enabled you must also specify a title block tables File under the FILES section of the options file (refer to Files Table (see "The Files Table" on page 187) for more information).
35
0
Use the design database to expand embedded attributes in bolt or gasket material descriptions. These attributes come from generating component (that is, the flange).
1
Use the spec database to expand embedded attributes in bolt or gasket material descriptions. These attributes come from the spec entry of the applicable gasket or bolt. If this option is set to 1, you can embed attributes from the spec database into material descriptions for bolts and gaskets instead of attributes from the components that generated the bolts and/or gaskets. When this option is set to 1, your label library numbers must refer only to attributes that also exist in table 202 of the spec database.
36
164
0
Do not remove unexpanded attribute specifications from material descriptions.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
1
Remove unexpanded material descriptions from material descriptions.
This option allows you to remove any embedded attribute specifications (labels) that are not expanded when the material description is generated. Thus, if a material description contains labels that refer to unrelated tables, the unused label can be removed from the description. However, labels that cannot be expanded because of error will also be removed - leaving the description incomplete although it may appear complete on the drawing.
Plant Design System (PDS) ISOGEN
165
The Options File - PD_ISO 37
0
Disable use of the alternate index into the material description libraries.
1
Enable use of the alternate index into the material description libraries.
This option allows you to access the material description libraries by using an attribute other than commodity code or specialty tag number. Library access is first attempted using the commodity code or tag number. If no material description is found, the attribute defined in the ALTERNATE_DESCRIPTION_INDEX table (discussed in the section ALTERNATE_DESCRIPTION_INDEX) is used to retrieve a description from the appropriate library. This option also allows you to establish a generic description for instruments, specialties and pipe supports. This can be used as an alternative to creating a material description library entry for each item. 38
166
val
Format of date strings output in the title block text files. Set val as follows:
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
39
40
0 - DD-MMM-YYYY
5 - DD MMM YYYY
1 - DD-MMM-YY
6 - MM/DD
2 - MM/DD/YY
7 - DD/MM
3 - DD/MM/YY
8 - YYYY-MM-DD
4 - MMM DD, YYYY
9 - YY-MM-DD
0
Disable flow arrows on pipe.
1
Enable flow arrows on pipe. Bi-directional flow arrows are also enabled.
0
Assign pipe flow arrows during traversal.
1
Assign pipe flow arrows by segment. When assigned during traversal, the first pipe receives a flow arrow. Arrows are then generated on the first pipes downstream of branch components. When assigned by segment, the first pipe encountered on each segment receives a flow arrow.
41
0
Disable multi-endprep components.
1
Enable multi-endprep components.
This option controls the display of end-prep graphics on components that have more than one end-prep such as the flanged and welded valve shown above.
Plant Design System (PDS) ISOGEN
167
The Options File - PD_ISO 42
0
Disable boxed tag numbers on commodity items.
1
Enable boxed tag numbers on commodity items. This option allows you to show tag numbers on the isometric for commodity items (that is, items other than specialty items, instruments and pipe supports).
168
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO 43
0
Output all bores in inches on the isometric.
1
Reserved for future use
2
Output all bores in millimeters on the isometric.
The settings for Intergraph option 43 should correspond with the settings for ISOGEN Option 41, Position A (Dimensional Units). In order to report the NPD in the BOM in Imperial units on a metric project, or to report the NPD in metric units on an Imperial or mixed project, it is necessary to define the diameter table DB001 in the Piping Job Spec Library. This table is hard-coded in the PD_ISO interface. 44
0
THIS OPTION MUST BE SET TO ZERO.
45
val
These options determine how implied materials from the reference database (other than bolts and gaskets) are handled.
0
Do not generate either a note in the drawing (based upon the GENITM_NOTE_FORMAT table) or an entry in the ISOGEN bill of materials.
1
Generate an entry in the bill of materials, but not a note in the drawing.
Plant Design System (PDS) ISOGEN
169
The Options File - PD_ISO
170
2
Generate a note in the drawing based upon the GENITM_NOTE_FORMAT table, but not an entry in the bill of materials. (This option does not apply to implied items from the spec.)
3
Generate a note in the drawing and an entry in the bill of materials. (This option will not result in a note for implied items from the spec.)
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
Material Takeoff Options that could affect the implied material output on the iso are stored in the type 63 data of the piping model. For Interactive Extraction, the software reads the type 63 of the first model entered on the form. For Batch Extraction, the software reads the type 63 data from the first piping model in the area specified in each record of the batch input file. 46
47
0
Do not label the drawing with segment node numbers.
1
Label the drawing with segment node numbers for those segments where data originated from the P&ID.
0
Do not generate weight information in the BOM on the face of the iso.
1
Generate weight information in the BOM on the face of the iso using Imperial Units (raw weight).
2
Generate weight information in the BOM on the face of the iso using Metric Units (raw weight).
3
Generate weight information in the BOM on the face of the iso using Metric Units (raw weight). Generate dimension information on the face of the iso using Metric Units.
4
Generate weight information in the BOM on the face of the iso using Imperial Units (raw weight). Generate dimension information on the face of the iso using Metric Units.
5
Generate weight information in the BOM on the face of the iso using Metric Units (raw weight). Generate dimension information on the face of the iso using Imperial Units.
6
Generate weight information in the BOM on the face of the iso using Imperial Units (raw weight). Generate dimension information on the face of the iso using Imperial Units.
Plant Design System (PDS) ISOGEN
171
The Options File - PD_ISO Raw weight implies that the insulation of the component is not included. Intergraph option 47 should be used in conjunction with ISOGEN option switch 41. 48
0
Disable secondary orientation notes for valve operators.
1
Enable secondary orientation notes. See also the section SECONDARY_ORIENTATION_NOTE.
49
0
THIS OPTION MUST BE SET TO ZERO.
50
0
Disable induction bend groups.
1
Enable induction bend groups. For Intergraph option 50 to function properly, pipes and pipe bends must be grouped so that they are included in an induction bend group with the Data/Revise/Component Group command from within PD_DESIGN.
172
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO 51
val
Nozzle connection tolerance scaling factor. The default nozzle connection tolerance is 4 mm. The default will be scaled according to the val entered divided by 100. Thus, to double the tolerance set val to 200.
52
0
Do not append the number of nuts per bolt to the material description of bolts.
1
Append the number of nuts per bolt to the material description of bolts. INGR_ATEXT_SPECIFICATIONS ATEXT number 3 allows for a comment to be appended to the numeric value. For example, nuts per bolt.
53
0
THIS OPTION MUST BE SET TO ZERO.
54
0
Use the pipe support tag number as the index into the specialty material description library for pipe supports.
1
Use the pipe support commodity code, which must be upper cased, as the index into the specialty material description library for pipe supports.
Plant Design System (PDS) ISOGEN
173
The Options File - PD_ISO
55
56
174
0
Do not alter extraction criteria case.
1
Convert extraction criteria to Lower-case.
2
This option performs pipeline extractions where attribute data has been stored in a lower-case format in the database. All text generated in the resulting isometric drawings will still be upper-case. Note that when extracting by line ID, and code listed attributes are involved, that the code list set must be stored in lower-case.
0
Form the commodity code for chain operators using the operator type attribute.
1
Form the commodity code for chain operators using the chain operator number.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
57
0
Do not generate labels consisting of segment node numbers.
1
Generate labels consisting of segment node numbers to assist flow sheet checking. However, if the node number is blank, labels will not be generated.
Plant Design System (PDS) ISOGEN
175
The Options File - PD_ISO
58
59
2
Always generate labels consisting of segment node numbers even when the node number is blank. An * is displayed if the node number is blank.
0
Append the bolt length to the material description for bolts.
1
Do not append the bolt length to the material description for bolts.
Position A 0
Display valve operator and primary orientation notes when the valve operator is not in a primary direction.
1
Do not display valve operators and primary orientation notes.
2
Display valve operators and primary orientation notes, whether or not the valve operators are in a skewed direction.
Position B 0
Display skewed pipe support orientation note.
1
Do not display skewed pipe support orientation note. This option is used in conjunction with ATEXT -213 for spindle direction, and the PRIMARY_ORIENTATION_NOTE table. Please refer to Intergraph option 48 for secondary orientation notes.
60
176
0
Search continuation areas defined in the Add Iso Area or Revise Iso
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Area forms for continuation items only. The database partitions of the models contained in the primary area (the area listed in the batch input file) are the only models scanned for the pipeline to be extracted as defined by the LINE_ID_DEFINITION section of the options file. The remaining models that are attached as references are scanned for continuation items, both pipeline and equipment nozzles. If the same pipeline, as defined by the LINE_ID_DEFINITION, continues into another area, a continuation note is displayed on the iso that points to the same line name as the iso being extracted.
1
Search continuation areas for LINE_ID_DEFINITIONs and continuation items. Any items that match the line ID will be included in the output isometric. All of the models from all of the pipeline continuation areas defined in the Revise Iso Area form is scanned for the line to extract. Also, all of the reference models are scanned for continuation items (both pipeline and equipment nozzles). If the same pipeline, a defined by the LINE_ID_DEFINITION, continues into another area, and the area is listed in the Revise Iso Area form, the pipeline is included in the extraction. When set to 1, option 60 increases iso extraction time. It is recommended that option 60 be set to 0 unless the line to be extracted extends across multiple areas.
2
Search all areas of the project for LINE_ID_DEFINITIONs and continuation items ignoring the continuation settings in the Revise Iso Area form. ISOGEN searches every piping model in the project for the pipeline to be extracted and also searches every equipment model for nozzle continuation items. Because there is no direct control over the number of models scanned by the software, setting 2 will take longer to process that setting 0 or 1.
61
0
Generic item names such as COMP, INST, and SUPP will be generated in the HITS file until the last section "Design file data in IDF order" is printed. This section will print four characters of the actual item name from the database.
Plant Design System (PDS) ISOGEN
177
The Options File - PD_ISO
61
178
1
Item names from the database will be generated for all sections of the HITS file. Setting this option to a 1 will increase extraction time by approximately 25%. Intergraph recommends this option be used for debug purposes only.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
Plant Design System (PDS) ISOGEN
179
The Options File - PD_ISO
Word
Value
Meaning
62
1
This Intergraph option has multiple switch settings (such as A, B, C, D). Intergraph switch settings are read from right to left (D-C-B-A). For example, if this option is set to 21, 1 represents switch position A and 2 represents switch position B. When setting an option with multiple switches, leading zeroes may be omitted, but trailing zeroes must be included.
Position PDS Weld Number Display on Iso A 0
Do not display PDS generated weld numbers on isometric drawings.
1
Display PDS generated System Weld Numbers on isometric drawings.
2
Display PDS generated User Defined Weld Numbers on isometric drawings. PDS generated System Weld Numbers are weld numbers at each welded connect point. PDS generated User Defined Weld Numbers are Weld IDs on Segment, defined by label number 355, appended with a dash (-) and the weld number at each welded connect point.
Position Weld Report in the Bill of Materials B 0
Do not report welds in the bill of materials (BOM).
1
Report welds in the bill of materials.
Position Weld Display at Line Name Breaks C 0
Place the weld at the line name break on the sheet containing the component that owns the weld, as set in PD_Design. If weld ownership is not set for connecting components, the weld will be placed on the sheet containing the component that has the higher east, north and elevation coordinate.
1
Place the weld at the line name break on both sheets. The weld is displayed as non-dashed on both isometrics and appears in the BOM and MTO for both lines.
Intergraph option 62, position C, must be set to 1 for ISOGEN option 22 (Field Fit Length) to work properly. Position C is not intended for sheet breaks on a single isometric. ISOGEN option 53, Weld Numbers, must be turned on in order to display the generated weld numbers on isometric. By default, this option generates a normal un-boxed arrowed message. If an enclosure is chosen using ISOGEN option 75, switch position A, only options 1, 2 and 5 should be used. Information on the Drawing and/or the parts list will be as follows: COMMODITY CODE (-20 record): ‘SHOP‘ or ‘FIELD‘ or ‘OFFSHORE‘
180
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO DESCRIPTION (-21 record): ‘Weld Type, Material A, Material B‘ For example:
63
0
Do not calculate the isometric center of gravity and the total isometric weight.
1
Calculate the isometric center of gravity and total isometric weight, excluding no-MTO components.
2
Calculate the isometric center of gravity and total isometric weight, with no-MTO components included. A center of gravity weight library must be defined in the ninth entry under the FILES section of the Options file for option 63 to function properly. Refer to The Files Table (on page 187) for more information.
64
65
66
0
Uses the standard MTO-Neutral file length of 256 bytes.
1
Uses the expanded MTO-Neutral file length of 1024 bytes.
0
Dimensions on supports are determined by the ISOGEN option switches 8, 9 and 40 and the NON_DIMENSIONED_SUPPORTS section of the Intergraph options file.
1
Disable dimensioning for all supports.
0
Do not use the detail sketch facility.
1
Use the detail sketch facility with a static cell library.
2
Use the detail sketch facility with a dynamic cell library. When option 66 is set to 1 or 2, the section DETAIL_SKETCH_FACILITY must exist in the options file. The syntax of this section is similar to the TYPE_2_LABEL section. A note, referring you to the appropriate sketch, will be automatically generated and placed on the iso. ISOGEN switch 71 must be set to 8000 for option 66 to function properly.
67
0
Do not generate shop welds.
1
Generate shop welds.
2
Generate shop welds, but do not generate shop welds at pipe-to-pipe connections.
3
Generate shop welds, but do not generate shop welds at pipe-to-bend connections.
4
Generate shop welds, but do not generate shop welds at pipe-to-pipe and pipe-to-bend connections. The pipe bend must be mapped to record 30 in the PDS to ISOGEN symbol map.
68
Position Start Point A
Plant Design System (PDS) ISOGEN
181
The Options File - PD_ISO 0
Extract drawing even if the original start point from the previous run cannot be used.
1
Stop extraction for a drawing if the original start point from the previous run cannot be used.
Position Spool Number B 0
Spool number will be assigned in the order of numeric value.
1
Spool number will be assigned in the order of alphabetical value.
Position Piece Mark Prefix C 0
Only the spool number, not including the piece mark prefix, will be written back to the design database as the piece mark number.
1
The full piece mark number, including the piece mark prefix and the spool number, will be written back to the design database. This option is used in conjunction with ISOGEN‘s repeatability function. In order to use position B and/or position C of this option, ISOGEN option 109 must be set to 111112. ISOGEN option 39 must be set to 2 in order to have an alphabetical spool number. Please refer to the repeatability functions described in Sections 5 and 15.
69
70
71
0
Do not produce the ISOGEN weld summary report.
1
Produce the ISOGEN weld summary report.
0
Generate isometric limit points (sheet split record) in the intermediate data file (IDF) file as defined in PD_Design
1
Do not generate isometric limit points (sheet split record) in the intermediate data file (IDF). This option allows you to place reference dimensions from a structural column or grid line to one item on the isometric. Before using option 71 you must have an up-to-date FrameWorks Reference Definition File that provides the location of all structural components and grid lines in the project. See Generate FrameWorks Reference Dimension File (on page 107). This option references structural elements according to their active cardinal point at the time of placement. It is highly recommended that structural columns be placed by CP5 (center-center) if it is anticipated that the Iso Structural Reference feature will be used. See Generate FrameWorks Reference Dimension File (on page 107). Since a single reference file is used for the entire project, no structural models can be excluded from being referenced. Hence, there is no selectivity as to what structural column or grid line will be referenced on the iso. The referenced structural element will always be the one nearest to the start of the pipeline being extracted. If a FAIL message appears on the isometric drawing and the .err file is reporting a (35:2012) DATA FAULT, DOUBLEBACK PIPE error, refer to ISOGEN message file errors section of this document for information on the
182
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO nature of this error. This Intergraph option has multiple switch settings (such as A, B, C, D). Intergraph switch settings are read from right to left (D-C-B-A). For example, if this option is set to 21, 1 represents switch position A and 2 represents switch position B. When setting an option with multiple switches, leading zeroes may be omitted, but trailing zeroes must be included. Position Reference Dimension Control A 0
Do not place reference dimensions.
1
Place structural reference dimension at the first component encountered from the start point.
2
Place structural reference dimension at the start point of the pipeline.
Position Reference Location B 0
Reference to the closest column.
1
Reference to the closest horizontal and vertical grid lines ignoring elevation changes.
2
Reference to the closest horizontal and vertical grid lines and display elevation changes.
Position Skew Box Display C 0
References with skewed movements will not be displayed with a skewed box.
1
References with skewed movements will be displayed with a skewed box.
Position Enclosure Type D 0
No enclosure for the reference.
1
Use a rectangle for an enclosure.
2
Use an arrow-ended rectangle for an enclosure.
3
Use an arrow-ended rectangle for an enclosure.
Position Line Style E
72
0
Use the default line type. (short dash line)
1
Use style 1 line type (long dash/short dash line)
2
Use style 2 line type (dash/dot-dot line)
3
Use style 3 line type (dotted line)
4
Use style 4 line type (dash/dot-dot line) This option controls whether fixed length pipe, such as flanged pipe, bell and spigot pipe, etc., will report as one piece or will break at pipe supports or olet branches.
Plant Design System (PDS) ISOGEN
183
The Options File - PD_ISO 0
Break fixed length pipe into pieces when there is a pipe support or olet branch along the pipe.
1
Report fixed length pipe as one piece even when there is a pipe support or olet branch along the pipe. If this option is set to 1, Intergraph option 75 must be set to 1 to list pipe in quantity. If this option is set to 1 and there are olet branches on the flanged pipe, the weldolets (WOL) are mapped to ISOGEN symbol key WTBW and represented with coupling record 126 in the Intermediate Data file (.idf file). For a tee‘d elbow or tee‘d bend, its tapped branch lies in the same direction as one of its legs. Since ISOGEN has a different logic to better display tee‘d elbows and tee‘d bends, use this option to choose between different logics.
73
0
symbol map for elbows and bends with tapping sections. This setting is the default for an elbow or bend with one or more taps.
1
Map a singularly tapped elbow or bend to a tee‘d elbow or tee‘d bend by the TAP NAME defined in the PDS-to- ISOGEN map table. Set ISOGEN switch 122 to 1 to display tap coordinates on the iso.
74
0
Default to display centerline elevation when elevation changes in a pipeline.
1
Display bottom of pipe (B.O.P) elevation when elevation changes in a pipeline. Bottom of pipe elevations are output only at tee intersections and changes in direction, where the pipeline is moving in a vertical plane. Any bottom of pipe elevation not at such points will be ignored. ATEXT –450 has B.O.P. as the default value, but this setting can be changed by the user.
75
This option controls pipes to be listed as either quantity or length on the bill of materials of the isometric drawing. 0
List pipes and pipe lengths on the bill of materials of the isometric drawing. Use this option for normal pipes which have no value defined in the PDS_sort_code attribute and both end preparations as male.
1
List pipes and pipe quantities on the bill of materials of the isometric drawing. Use this option if the PDS_sort_code attribute for the pipe has a value or if there is one end preparation on the pipe that is not male. ISOGEN Option Switch 74 Position 7 must be set to 0.
2
List pipes and pipe lengths on the bill of materials of the isometric drawing. Use this option if the PDS_sort_code attribute for the pipe has a value or if there is one end preparation on the pipe that is not male. ISOGEN Option Switch 74 Position 7 must be set to 1. The PDS_sort_code (table 50, column 16) attribute of the fixed length pipe is defined by having a value in the commodity data in the piping specification. The end connection of the fixed length pipe shown on the isometric drawing respects the end preparation defined in the model.
184
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO 76
This option allows you to specify the source of material description for bolts. This option only affects the source of material description for bolts, not the material description for other components. In addition, it only applies when the Bolt Commodity Code Table is selected in Material Takeoff Options of the Revise Model Data command in Project Data Manager, for the first model in the area, or the model whose type 63 will be used to extract the isometric. Also note that this option does not affect the commodity code reported, only the description for the bolts. 0
Use the commodity code specified in the Source of Material Description command in the Material Takeoff Options form to search for material description for bolts. If set to "System," use the System Commodity Code from the spec to search for material description for bolts. If set to "Size Dependent,‖ use the commodity code from the Bolt Commodity Code Table to search the material description for bolts.
1
When the Commodity Code option is set to "Size Dependent" in the Material Takeoff Options form, use the commodity code from the Bolt Commodity Code Table to search the material description for bolts.
77
This option allows you to specify whether Item Codes and Material Descriptions are converted to uppercase. 0
Convert Item Codes (record –20) and Material Descriptions (record –21) to uppercase in the Bill of Materials on the isometric.
1
No case conversion for Item Codes and Material Descriptions in the Bill of Materials on the isometric. For this option to work properly, it is necessary to make sure the font has uppercase and lowercase letters (for example, font 108), and that the fast font attribute is disabled in the ISOGEN seed file.
2
78
In addition to Item Codes and Material Descriptions, also does no case conversion for all iso labels, records, ATEXTs, Title Block data, and Bill of Materials on the isometric. All text for these displays in the same case (UPPER or lower) as defined by the user. You must use a FONT which supports both upper case and lower case by defining the environment variable PDISOFONT in pds.cmd. See Commands Set in PDS.CMD in the Project Setup Technical Reference Guide for more information on setting environment variables.
Position A 0
Do not check clash detected by PDS Interference Checker.
1
Check and generate a note on extracted item having clash(es) from Interference Checker.
2
Check and output a note on the extracted item with Approved IFC clashes.
3
Check and output a note on the extracted item with all IFC clashes except clashes with Cleared status. The default PDS Interference Checker format is: 'IFC CLASH [UNIQUE_CLASH_ID(132,1)] $[if_approval_status(132,2) defined by standard note 1203]
Plant Design System (PDS) ISOGEN
185
The Options File - PD_ISO $[DISCIPLINE NAME] $[PRIMARY DESCRIPTION] (non-blank) $[SECONDARY DESCRIPTION]' (non-blank) where Unique_clash_id is table 132, column 1. The clash discipline name (table 132, column 8) is 'PIPING', 'EQUIPMENT', and so forth. The primary description (table 134, column 5) is the Item Name in the PDS Interference Report (for example, 'GAT', 'PIPE', and so forth). The secondary description (table 134, column 6) is the secondary description in the PDS Interference Report. '$' is a line separator. The default text 'IFC CLASH' can be changed by using the INGR_ATEXT_SPECIFICATIONS table using index 18 in the option file Position This option allows you to display an RDB conflict message B 0
Do not check for RDB conflict (do not display message).
1
Check and generate a note on extraction item having RDB conflicts. The default RDB note is RDB CONFLICT. The default text can be changed by INGR_ATEXT_SPECIFICATIONS table, index 19 in Options file.
79
This option allows you to get the field fit length in the .b file. 0
Do not adjust pipe length with Fit Field Weld in MTO neutral file.
1
Added extra pipe with the Fit Field Weld in MTO neutral file. The amount of extra pipe is set in ISOGEN Option 22. The original pipe length field is defined by Table 50, Column 22 in the COMPONENT_ATTRIBUTES table of MTO Neutral File Record Map.
80
This option allows you to run standalone Stress Analysis. 0
Do not run standalone Stress Analysis.
1
Run standalone Stress Analysis with extracted ISO line name used as the search criteria.
When using this feature, Intergraph Option 12 in the Stress Option file, Stress Option 12 must be consistent with the line name used to extract ISO. This feature works both in Batch ISO Extraction and Interactive ISO Extraction. Stress Option file must be set in the environment variable STRESSOPTION that can be set in pds.cmd. The Stress output directory can be set in the environment variable STRESSPATH that can be set in pds.cmd. If the environment variable STRESSPATH is not set, stress files will be output to the ISO output directory.
186
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO When Stress and ISO are output to the same directory, ISO‘s .dat, .err, and .h files will be renamed as .dati, erri, and .hi to prevent conflict with Stress files. 82
This option allows you to write the current revision number in the .IDF file. 0
Do not generate record -8 for the current revision number in the IDF file.
1
Generate record -8 for the current revision number in the IDF file.
The Files Table The Files table contains the names of several external files which are used by the ISOGEN interface. The entries in this table are order dependent and must be in the order shown below. All files may be defined as: network address: /directory path/file name. For example: pdscert: /usr/isofiles/symbol.map 1. The PDS to ISOGEN symbol map This table maps PDS component names to ISOGEN symbol names. The format and contents of the table are discussed in more detail in the section PDS-to-ISOGEN Symbol Map. This library is required and must be specified. 2. The ISOGEN user-defined symbol library This is a library of ISOGEN symbols that has either been translated from the VAX (see the README file for translation information) or has been added to those delivered with the ISOGEN product. This library is optional and need not be specified. 3. The label description library This is a library of user-defined labels which are based on database attributes. Creation of library entries is discussed in the PDS Reference Data Manager document. This file specification is redundant in that a label description library is already referenced by piping model files. However, if you specify it here, you can have a separate library that is used specifically for iso extraction and for no other purpose. If this entry is left blank then the library referenced by the piping model file is used instead. 4. The valve / valve operator symbol map (VALOPR table) This file contains a table that can be used to map a PDS valve and valve operator combination to a different symbol than that mapped by valve alone. This table is discussed in the section The Valve/Operator Table. In order to use this file, Intergraph options block option 31 must be set to 1. This is an optional file name. 5. The mto neutral file map This file contains the tables which govern the format of the Intergraph mto neutral file. Refer to The MTO Neutral File Record Map (on page 265) for more information. In order to use this table, Intergraph options block option 20 must be set to 1. 6. Reserved 7. The Title Block Tables File This is an optional file containing tables that govern the generation of text that is to be inserted into a drawing title block by the batch extraction software.
Plant Design System (PDS) ISOGEN
187
The Options File - PD_ISO When you specify this table, you must also enable option 34 in the Intergraph options block. 8. The Notes Table This file is optional and contains data that can be mapped to the title block by the batch extraction software. The table is accessed through the Title Block Tables File. he Notes Table allows you to map data to the title block which is not stored in the database. 9. Center of Gravity Weight Library This is an optional library that generates center of gravity calculations for ISOGEN. For more information on center of gravity calculations, see Center of Gravity Calculation (on page 307). In order to use this library, Intergraph options block option 63 must be set to 1 10. Detail Sketch Facility Cell Library This is a cell library which contains the cells specified in the DETAIL_SKETCH_FACILITY section of the options file. 11. Drawing Definition File This file allows you to customize line weight, size and output level of the data on the isometric drawing. 12. Welds Definition / Format File This file specifies the format of the weld box that will be appear on the isometric drawing. It is also used to define the weld report. 13. Material List Definition File This file allows you to define the format of a STYLE 2 or STYLE 3 Material Take Off. 14. Basic Bending Parameters File This file can be used as a basic set of input to a bending machine. The 14th entry in the FILES section of the options file will contain the name of this file. If the first character of the entry is *, the generated file will be isoname.bnd; where isoname is the name used in creating the isometric design file name. If this entry contains a node, directory and filename, the bending information is appended to that filename for each extracted line. If this entry is left blank, a bending parameters file will not be generated.
USER_DEFINED_WELDS This table allows you to assign a weld symbol to a particular weld type.
ISOGEN, versions 5.0 or later, allow you to create a user-defined weld symbol by using the symbol definition software. Once created, the new weld symbol graphics should be proportionate to other user-defined symbols. The newly created symbol should be mapped to a specific weld type in the USER_DEFINED_WELDS section of the options file. Note that the weld symbol is not mapped in the isomap.tbl file. By using the following table format, you can define which SKEY is used with each weld type. For example, if a weld type codelist number is defined to use the SKEY FFWT, ISOGEN generates the appropriate text and adds extra material as defined in the ISOGEN section of the options file. The format of a table entry is: VTF, VAL1, VAL2, ...,VALn, WELDTYPE, SYM Where:
188
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO VTF
is a number indicating the number of values to follow (maximum of 20 values per line
VAL1-VALn
are the weld type attribute values that VALn will be mapped to the symbol defined (SYM).
WELDTYPE
is a number 1-3 where: 1: SHOP 2: FIELD 3: OFFSHORE
SYM
is the ISOGEN weld symbol name.
If the table is not defined or a weld type code list value is not included in the table, the following action is taken. For more information, see Weld Types and Mapping (on page 292). codelist value (from codelist 1100, Weld Type) 1 = No weld 11-20 = 'WW' (shop weld) else = 'WF' (field fit weld)
Example 1: Generating a user-defined weld from codelist values Show the required entries to generate the following welds: a site weld symbol when codelist value 22 is used. This is a field weld, but does not require extra material to be added. an offshore field fit weld symbol for code list values 30-33 inclusive. a mitre offshore weld symbol for codelist value 40. The format of the table entry is: USER_DEFINED_WELDS 3 1, 22, 2, 'WS' 4, 30, 31, 32, 33, 3, 'WOF' 1, 40, 3, 'WM'
WELD_PREFIX This table is used to add a prefix to an isometric weld number that is contained within an enclosure. The WELD_PREFIX table also allows the prefix to be positioned on the drawing frame as a form of general note about weld identification. The weld prefix may also be included as part of the output in the user-defined weld summary report. The format of a table entry is: WELD_PREFIX 1 #, 'TEXT' Where:
Plant Design System (PDS) ISOGEN
189
The Options File - PD_ISO #
is a number 0 through 3 where: 0 - is a general weld prefix to apply to all weld types 1 - is a shop weld prefix to apply only to fabrication welds 2 - is a site/field weld prefix to apply only to erection welds 3 - offshore weld prefix to apply only to offshore welds
'TEXT'
is the actual prefix to be used If all four prefixes are defined, the general weld prefix (setting 0) will be ignored.
Example 1: Defining a Weld Prefix Determine the table entry that would have all offshore welds have the prefix 'OFFSHORE-' on the iso drawing. The table entry would be: WELD_PREFIX 1 3, 'OFFSHORE-'
DETAIL_SKETCH_FACILITY This table is used to generate a detailed sketch or information note for specific item. Any component meeting the specified value defined in this table generates a defined detail sketch or note. The defined value must exactly match the attribute or label. You can generate general or specific notes for components and spools. The general information note places a note on each isometric sheet of the pipeline. The specific information note only places a note on the specific isometric sheet that contains the item generating the note. You can define up to 300 Detail Sketch Facility table entries. Details are always placed starting in the upper left of the iso drawing. If the line with the -700 record in the MOVEABLE_TEXT section of the options file is removed, the north arrow will display in the upper left and details will appear in the upper right of the iso drawing area. The format of a table entry is: TABLE, COL, LABEL, 'COL VAL', 'DET NAME', SKETCH TYPE Where:
190
TABLE, COL
is the table, column specification of the attribute that will be checked and compared with ‘COL VAL‘.
LABEL
is the label description library number that defines the format of the note that will be checked and compared with ‘COL VAL‘. When using LABEL, TABLE must be set and COL must be 0.
‘COL VAL‘
is the value that when equal to TABLE,COL or TABLE,LABEL will trigger the detail to be placed on the isometric.
‘DET NAME‘
is the name of the detail cell from the cell library (defined by the tenth entry under the files section of the options file) to place on the isometric. For dynamic sketches, the system will override the specified name
SKETCH TYPE
is a number that indicates whether the sketch is static or dynamic. Valid values for sketch type are 0 (static) and 1 (dynamic). Required if Intergraph option 66 is set to 2.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Information Note Entries Two types of information notes are available: General Notes are indicated by a _N at the end of the cell. Specific Notes are indicated by a _S at the end of the cell. All cell names that end with _N or _S are treated as Information Notes and placed accordingly. ATEXT numbers -541 and -542 also effect these criteria. -541 _N is used as the delimiter/identifier in the general note name. -542 _S is used at the delimiter/identifier in the specific note name.
Example 1: Example of the DETAIL_SKETCH_FACILITY Table
PIPELINE_HEADER The pipeline header table is used to generate records in the intermediate data file that cause attribute change graphics to be generated in the isometric drawing. Attribute change graphics can be used at changes in piping materials class, insulation type, and so on, along a pipeline. This table allows you to control the database attributes that are used to generate attribute breaks on the drawing.
This table is also used to generate a note when some database attribute of a component overrides that of the pipeline. For example, a new pipeline might contain an existing valve. This table can be used to generate a note on the drawing that points to the valve and identifies it as existing. The format of a row (or a single entry) in this table is: RECNO, ST, SC, SN, DFLT, PREFIX, CT, CC, CN, PT, PC, PN, IT, IC, IN Where:
Plant Design System (PDS) ISOGEN
191
The Options File - PD_ISO RECNO
is the ISOGEN record number used for an attribute whose value can change along the length of a pipeline. Record numbers from the following table must be used for this item ISOGEN Rec. No.
Attribute
ATEXT No.
-6
Line name
-288
-7
Spool number prefix
n/a
-11
Piping materials class (spec)
-289
-14
Date Record
-250
-15
Insulation type
-290
-16
Heat tracing type
-291
-17
Paint code
-292
-41
User-defined 1
-293
-42
User-defined 2
-294
-43
User-defined 3
-295
-44
User-defined 4
-296
-45
User-defined 5
-297
An entry in the PIPELINE_HEADER table with an ISOGEN record number of -7 is used to define a spool number prefix. If defined, the prefix is used by ISOGEN to form spool number labels in the drawing. When defining spool number prefixes, use a single ? symbol to generate spool numbers only. Use two ? symbols for the spool number prefix to generate spool numbers and sheet numbers. attribute change are preceded by some clarifying text. That text is "MATL," which identifies that the attributes shown are piping materials classes. For information on modifying this text, refer to ATEXT_SPECIFICATIONS (on page 196). The Atext numbers you will need in the ATEXT_SPECIFICATIONS table to change the clarifying text are shown above. In the case of the user-defined attribute changes the default Atexts are blank. In order to generate attribute change graphics in the drawing you MUST define nonblank Atexts that correspond to the ISOGEN record numbers you use. For example, if you want to use ISOGEN record number -41 for a user-defined attribute change then you must define ATEXT number -293 with a nonblank value if you want to see the attribute change on the drawing. The Atext numbers shown above modify only the clarifying text shown with the attributes in the drawing. They do not modify the title block entries for these attributes. Different Atext numbers are used to modify this text. Refer to the appendix , ATEXT Facility - by Number for details. ST, SC
192
is a table, column specification for the segment attribute whose value might change along the pipeline. This attribute specification can be any segment level attribute in the material database. The segment level table
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO is table 12. The specification for piping materials class, for example, would be table 12, column 12. SN
is an optional label description library number that you can use to specify the segment attribute(s) that might change. By using the label description library number rather than ST, SC (above) you can define composite attributes that are combinations of 2 or more database attributes. The label description library holds a definition of each label description library number. The number and its description in the label library can be used to form a text string (a label) that is formed from database columns. You define which columns are used in the label as well as the label format when making a definition in the label library. Iso extraction treats a string based on a label library number as a pseudo attribute. A pseudo attribute can be used to generate attribute breaks just the same as regular database attribute can.
DFLT
is an optional string used to define a default value for an attribute or label. When the attribute defined by ST,SC or SN is undefined (blank) then DFLT will be used. This shows attribute breaks for attributes that you normally do not want to provide values for. If you do not provide a value for this field the string "UNDEFINED" is used for undefined attributes.
PREFIX
is an optional prefix used in forming a note from a database attribute when a component attribute overrides a segment attribute. The override note is formed by appending the database attribute to the prefix defined here. The note formed in this manner points to the appropriate component in the drawing. When the ISOGEN record number for the spool prefix is -7, PREFIX is used as a separator between the spool prefix and the spool number.
CT, CC
is the table, column specification for the component level attribute that can override the pipeline level attribute defined by ST, SC. These items are optional. Some pipeline level attributes cannot be overridden at the component level (pipeline name and piping materials class are examples). When there is no override attribute these items should be set to 0. Attribute specifications for CT, CC apply to the component table (34) in the design database.
CN
is the component level counterpart to SN. If the label generated by CN differs from that generated by SN then an override note will be generated. In order to avoid generating override notes on every component you must either define CN in exactly the same way as SN except for the table and attribute numbers or not use the component override feature.
PT, PC
is the same as CT, CC except that this attribute specification applies to pipe rather than components. Attribute specifications can only refer to table 50 in the design database.
PN
is the same as CN except that it applies to pipe.
IT, IC
is the same as CT, CC except that this attribute specification applies to instruments rather than components. Attribute specifications are from the instrument table (67).
Plant Design System (PDS) ISOGEN
193
The Options File - PD_ISO IN
is the same as CN except that it applies to instruments.
Example 1: Breaking Supply Responsibility Along a Pipeline Since there is no predefined ISOGEN record number for supply responsibility, you must use one of the user-defined records. Record -41 is used in this example. Referring to the database table format, the following database attributes apply: Segment 12, 39 Component - does not apply Pipe - does not apply Instrument - does not apply The table entry would appear as follows: -41, 12, 39, 0, '', 'SUPPLIED BY', 0, 0, 0, 0, 0, 0, 0, 0, 0
Example 2: Changing Construction Responsibility Along a Pipeline As in the previous example, there is no predefined ISOGEN record number for construction responsibility. So, you must use one of the user-defined record numbers. Record -42 is used in this example. The applicable database attributes are: Segment 12, 38 Component - does not apply Pipe - does not apply Instrument 67, 29 The appropriate table entry would be: -42, 12, 38, 0, '', 'CONSTR BY', 0, 0, 0, 0, 0, 0, 67, 29, 0
Example 3: Breaking Composite Attributes by Combining Insulation Purpose and Thickness For this example, we can use ISOGEN record number -15. Since the change that will be shown is made up of multiple attribute changes, we must use the label description library to form a pseudo attribute. Using the label library utility we have defined the following library numbers: 956 - segment insulation purpose and thickness 957 - instrument insulation purpose and thickness The table entry for this case would be: -15, 0, 0, 956, '', '', 0, 0, 0, 0, 0, 0, 0, 0, 957
194
The first entry in the PIPELINE_HEADER table MUST be for line name (using the -6 record). Otherwise, the ISOGEN interface will stop with an error. The attribute that is used for this entry is displayed in the pipeline ID box in the lower right hand corner of the drawing. You can use either the line name attribute (table 12, attribute 2) or the line ID (specified by using table 12, attribute -2) for ST, SC. Refer to LINE_ID_DEFINITION (on page 198) for information on how a line ID differs from a line name. The table entries should be in order of increasing absolute value of ISOGEN record number. Attribute changes in the drawing can be inhibited by either removing the entry for the attribute from this table or by setting the Atext for the clarifying text to blank in the ATEXT_SPECIFICATIONS table. When attributes are specified, the label library number should be 0. When the label library number is specified then the attribute specifications should be 0. The line ID (COL = -2) can be used for the spool prefix.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
ISOGEN word 39 must be set to 0 in order to display spool number labels formed using the spool prefix. If ST is less than 0, the attribute is checked for component overrides but no segment level breaks will be shown in the drawing. When ST is made negative, set RECNO to an undefined record number (such as -99).
Plant Design System (PDS) ISOGEN
195
The Options File - PD_ISO
ATEXT_SPECIFICATIONS This table is used to modify the values of text strings that ISOGEN puts on drawings. A table entry can also "turn off" a text string so that it does not appear. The format of a table entry is: ATEXT number, 'new text' Where: ATEXT number
is one of the ATEXT numbers defined in the appendix, ATEXT Facility - by Number, of the ISOGEN Facilities Guide.
'new text'
is the new text string to be applied to the Atext number. The 'new text' will be used instead of the text defined in Appendix B of the facilities guide.
A particular text string can be turned off by setting its ATEXT value to blank. ATEXT entries -237 " (inch indicator) and -238 ' (foot indicator) are exceptions to the allowance for single or double quote delimiters. These values (" and ') are the default values for the ATEXT entries, and do not need to be specified in the options file. If you do want to specify these values in the options file, use the following syntax: -237, '"' (single quote, double quote, single quote) -238, "'" (double quote, single quote, double quote)
Example 1: Modifying Text Modify the clarifying text that precedes a piping materials class that is generated at a spec change by changing "SPEC" to "MATL". The table entry would be: -289, 'MATL'
Example 2: Modifying Text for an Eccentric Reducer Turn on the "FLAT SIDE DOWN" message that points to eccentric reducers (this message is off by default). Refer to the appendix, ATEXT Facility - by Number, of the ISOGEN Facilities Guide, for further explanation. The table entry would be: -243, 'FLAT SIDE DOWN'
196
The table entries must be in order of increasing absolute value of ATEXT number. That is, -206 should precede -207 and so on. If one specification is out of order then all of the following entries will be ignored. In order to turn off all ISOGEN generated title block data, the following ATEXT specifications can be used: -250, ' ' -253, ' ' -270, ' ' -271, ' ' -272, ' ' -317, ' ' -318, ' ' -400, ' ' -401, ' '
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO -402, ' ' -403, ' ' -404, ' ' -405, ' ' -406, ' ' -407, ' ' -410, ' ' -411, ' '
INGR_ATEXT_SPECIFICATIONS This table is used to modify the values of text strings that PD_ISO puts on drawings. The format of a table entry is: ATEXT number, 'old text', 'new text' Where: ATEXT number
is 1-15
'old text'
is the text string to be substituted.
'new text'
is the new text string to be applied to the Atext number.
The 'old text' value is used if the 'new text' value is left blank or if the INGR_ATEXT_SPECIFICATION record is omitted from the Options file. No value is used if the string 'blank' is assigned as the value of 'new text'. 1,
‘NOT FOUND‘,
" !Used based on Intergraph option 6 and ATEXT -209
2,
‘BOLT LENGTH‘,
" !Used based on Intergraph option 58
3,
'NUTS PER BOLT',
" !Used based on Intergraph option 52
4,
‘CHAIN_‘,
" !Used based on Intergraph option 33, 56
5,
‘FSTAND_‘,
" !Used based on Intergraph option 33
6,
‘XSTEM_‘,
" !Used based on Intergraph option 33
7,
‘HOR‘,
" !Horizontal - Used for an operator in a 2plane ske
8,
‘VOR‘,
" !Vertical - Used for an operator in a 2plane ske
9,
‘DEG‘,
" !Degree - Used for an operator in a 2plane ske
10, ‘E‘,
" !Used with skewed operator orientation notes
11, ‘N‘,
" !Used with skewed operator orientation notes
12, ‘U‘,
" !Used with skewed operator orientation notes
13, ‘W‘,
" !Used with skewed operator orientation notes
14, ‘S‘,
" !Used with skewed operator orientation notes
15, ‘D‘,
" !Used with skewed operator orientation notes
16, ‘****‘
" !Used based on Intergraph option 26 Position A set to 2
Plant Design System (PDS) ISOGEN
197
The Options File - PD_ISO 17, ‘SCHEDULE‘
" !Used based on Intergraph option 10 set to 1‘‘
LINE_ID_DEFINITION This table is used to define the format of the line ID. The line ID is a composite attribute that should be formed from a subset of those attributes which are used to form the line name attribute. The line ID is intended to be a simpler way of referring to a pipeline. The format of a table entry is: ST, SC, 'SUFFX' Where: ST, SC
is the table, column specification for one of the attributes making up the line ID. Any attribute from the segment level (table 12) can be used.
'SUFFX'
is an optional, single character, suffix used to terminate the attribute in the line ID. A null entry (two successive single quotes) is valid.
The line ID itself is formed by linking all the attributes together with their suffixes if defined. The result is the line ID label. In order to use the Display Iso feature from an interactive piping session, this table and column must be set to 12, 3.
Example 1: Defining a Line ID Define a line ID composed of fluid code, sequence number and unit code. The column numbers involved are: Fluid code 12, 9 Sequence no 12, 10 Unit no 12, 4 The table is defined as: 12, 9, '-' 12, 10, '' 12, 4, '' Using the previous line ID, what is the line ID for a line named 16IN-P12002-1C003? Assuming that a single digit unit number follows sequence number in this line number, the line ID would be P-12002. The suffix character defined in the table is used only in generating the text string for display purposes. When inputting line names for extraction every attribute forming the line ID MUST be separated by dashes. For instance, to input the line ID in Example 8 you must key in P-1200-2.
198
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
TYPE_1_LABELS This table is used to generate notes on drawings that point to specific components. This table causes a note to be generated when some database attribute which you define in the table has a value. When the attribute is undefined (that is, does NOT have a value) then no note is generated. When a line is extracted, each component is processed one at a time. This table allows you to generate a note, based on the value of a component's attribute, at the time it is being processed. You can define up to 50 table entry lines for Type 1 Labels. The format of a table entry is: COMP TYPE, TABLE, COL, LDL NO, ENC TYPE (optional) Where: COMP TYPE
is the component type to which the note should apply. Allowable values for component type are: 1 - Commodity item 2 - Specialty item 3 - Pipe 4 - Instrument 5 - Pipe support
TABLE, COL
is the table, column specification for the attribute that should be checked. If this attribute is defined, the note will be generated. An attribute is considered undefined based on its data type as follows: Integer - set to 0 Real - equal to -32768 ASCII - blank or null Coded - 0 or 1 Any attribute that is not undefined is defined and will cause a note to be generated. You can also specify that a Real attribute be considered undefined if it contains the value 0.0. To do this, make the value of TABLE negative in the table (such as use -34 instead of 34 to designate table 34).
LDL NO
is the label description library label number that defines the format of the note that is to appear on the drawing. You must define this note in the label description library as defined in the PDS Reference Data Manager document. If the label references attributes from the database, the attributes must be from the table defined by TABLE or its associated table.
ENC TYPE
is the enclosure type. There are five text-type records that trigger the different enclosures shown below. If an enclosure is not required, use 0 as the enclosure type. Type 1 Enclosure This enclosure type can handle an unlimited
Plant Design System (PDS) ISOGEN
199
The Options File - PD_ISO number of characters on a single line.
Type 2 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 3 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 4 Enclosure This enclosure type can handle a maximum of three characters on a single line. Type 5 Enclosure This enclosure type can handle a maximum of three characters on a single line.
Example 1: Defining Type 1 Labels Define a table entry that would generate a note (without an enclosure) when the REMARKS field attribute for the component is defined. Using the label library utility, we have defined label 910 as shown below:
The attribute referred to is table 34, column 46. The table entry would be: 1, 34, 46, 910
200
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Where: 910 is the label number which defines the exact format of the note to be generated. The note would point to the item (or items) in the drawing that corresponds to the component(s) in the model whose remarks attribute has been defined.
Example 2: Defining Type 1 Labels Define a table entry that would generate a note (without an enclosure) when the standard_note_no_a field attribute for the component is defined. Using the label library utility, we have defined label 913 as shown below:
The attribute referred to is table 34, column 47. The table entry would be: 1, 34, 47, 0 Where: 913 is the label number which defines the exact format of the note to be generated. The note would point to the item (or items) in the drawing that corresponds to the component(s) in the model whose standard_note_no_a attribute has been defined.
The database table defined by TABLE must correspond to the component type identified by COMP TYP. Thus, the following restrictions exist: COMP TYP
Allowable values of TABLE
1
12, 34
2
12, 34
3
12, 50
4
12, 67
5 12, 80 When LDL NO is set to 0 in the table, no note is generated.
Plant Design System (PDS) ISOGEN
201
The Options File - PD_ISO
The note that is defined by LDL NO need not use the attribute that is defined in the table as TABLE, COL. TABLE, COL is only the trigger in the note generation process. A dollar sign ("$") embedded in a label is treated as a line feed by ISOGEN.
TYPE_2_LABELS This table is used to generate notes that point to specific components. Use this table to generate a note whenever a specific attribute (user-defined in the table) is defined with a specific value (also defined by you in the table). Notice the difference between this table and the TYPE_1_LABELS table. Note that generation from the TYPE_1_LABELS table is triggered by an attribute having ANY value. This table is more selective in that you specify the value of the attribute that is to trigger note generation. You can define up to 99 table entry lines for Type 2 Labels. The format of a table entry is: TABLE, COL, ’COL VAL’, LENGTH, LDL NO, ENC TYPE (optional) Where: TABLE, COL
is the table, column specification of the attribute that will be checked and compared with ‘COL VAL‘.
‘COL VAL‘
is the value of TABLE, COL that will trigger note generation. If ‘COL VAL‘ is the same as the value of TABLE, COL then a note will be generated that points to the item.
LENGTH
is an optional specification of the number of characters from the database attribute that should be compared with ‘COL VAL‘. If set to 0, all characters of the attribute will be compared with ‘COL VAL‘.
LDL NO
is the label description library number that defines the format of the note that will be generated when the attribute identified by TABLE, COL has the value ‘COL VAL‘ or the first 1 through LENGTH characters of the attribute are the same as ‘COL VAL‘. If the label references attributes from the database, the attributes must be from the table defined by TABLE or its associated table.
ENC TYPE
is the enclosure type. There are five text-type records that trigger the different enclosures shown below. If an enclosure is not required, use 0 as the enclosure type. Type 1 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 2 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 3 Enclosure This enclosure type can handle an unlimited number of characters on a single line.
202
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Type 4 Enclosure This enclosure type can handle a maximum of three characters on a single line. Type 5 Enclosure This enclosure type can handle a maximum of three characters on a single line.
Example 1: Defining Type 2 Labels Define a table entry that would generate a note (with a type 3 enclosure) that points to all blind flanges. One way to accomplish this would be to check the value of the PDS commodity_name attribute for the string "6Q2C08", the PDS commodity name for a Blind Flange. The appropriate attribute is table 34, column 3. The table entry would be: 34, 3, '6Q2C08', 0, 911, 3 Where 911 is the label description library label number which defines the format of the note. Label 911 is defined as follows:
Plant Design System (PDS) ISOGEN
203
The Options File - PD_ISO Example 2: Defining Type 2 Labels Define a table entry that would generate a note (without an enclosure) when the standard_note_no_a field attribute for the component is defined. Using the label library utility, we have defined label 913 as shown below:
The appropriate attribute is table 34, column 47. The table entry would be: 34, 47, '201', 913, 0 Where 913 is the label description library label number which defines the format of the note.
Refer to notes 2, 3, 4, and 5 under the description of the TYPE_1_LABELS table. These notes also apply to the TYPE_2_LABELS table. To test on code list number values rather than code list text, set LENGTH to 0 and set COLVAL to the code list number. For example, to generate a note when the fabrication category 50(table), 14(col) is 25 use: 50, 14, '25', 0, 986.
TYPE_3_LABELS This table is used to generate a note when the value of a code-listed attribute matches one of the values specified in the table entry. This table is similar to TYPE_2_LABELS except that, rather than being triggered by a single value, a note can be triggered by one of several values. You can define up to 50 table entry lines for Type 3 labels. The format of a table entry is as follows: TYPE, TABLE, COL, LDL NO, NVALS, VAL1, VAL2, ... VALN, ENC TYPE (optional) Where:
204
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO TYPE
is the component type that the note should apply to. Use the following values for TYPE: 1- Commodity item 2- Specialty item 3- Pipe 4- Instrument 5- Pipe Support
TABLE,COL
defines the attribute that triggers note generation.
TABLE
must correspond to TYPE as follows: TYPE
ALLOWABLE TABLES
1
12, 34
2
12, 34
3
12, 50
4
12, 67
5
12, 80
LDL NO
Defines the format of the note to be generated if triggered. If the label references attributes from the database, the attributes must be from the table defined by TABLE or its associated table. If LDL NO is set to 0, the value of TABLE,COL is generated as the note.
NVALS
Defines the number of code list numbers in the list to follow.
VAL1...VALn
Code list numbers that should trigger note generation.
Example 1: Defining Type 3 Labels Show the table entry needed to generate a note when the component fabrication category is set to code list values 5, 7, or 17. The table entry would be: 1, 34, 10, 994, 3, 5, 7, 17 Where:
Plant Design System (PDS) ISOGEN
205
The Options File - PD_ISO Label 994 would define the format of the note that would be generated.
When LDL NO is set to 0 so that the code listed text is generated as the drawing note, the short form of the code list text (that to the left of the "=" in the code list source) can be generated by making COL negative. Therefore, in the previous example, the following would be used to generate the short form of the code list text as the note. 1, 34, -10, 0, 3, 5, 7, 17
START_POINT_NOTES This table is used to generate notes at the beginning of a pipeline. The format of a table entry is as follows: TYPE, TABLE, LDL NO, ENC TYPE (optional) Where: TYPE
Currently, TYPE must be set to 0.
TABLE
TABLE defines the tables that will be referenced by LDL NO as follows:
LDL NO
206
TABLE
Valid tables in label LDL NO
12
SEGMENTS
34
COMPONENTS
50
PIPE
67
INSTRUMENT
Label library number which defines the format of a note to be generated on the first component of the pipeline..
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO ENC TYPE
is the enclosure type. There are five text-type records that trigger the different enclosures shown below. If an enclosure is not required, use 0 as the enclosure type. Type 1 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 2 Enclosure This enclosure type can handle an unlimited number of characters on a single line. Type 3 Enclosure This enclosure type can handle an unlimited number of characters on a single line Type 4 Enclosure This enclosure type can handle a maximum of three characters on a single line. Type 5 Enclosure This enclosure type can handle a maximum of three characters on a single line.
Example 1: Defining Start Point Notes Define a table entry that would generate the line name attribute at the start of a pipeline. The table entry would be: 0, 12, 900, 0 Where: Label 900 returns the line name (T12C2) followed by a dash and the text, "Starts Here".
Plant Design System (PDS) ISOGEN
207
The Options File - PD_ISO
END_POINT_COMPONENT_LABELS This table is used to define the format of notes that are generated at line endpoints when the line endpoint connects on to another pipeline. The note defined by this table is NOT generated at line endpoints that are not connected to other pipelines. The note itself is formed from the attributes of the connecting component. Each entry in the table is used to form one line of the note. Multiline notes are shown as a block of text on the drawing. The format of a table entry is: 'PREFIX', CT, CC, CN, PT, PC, PN, IT, IC, IN The attribute that is used for this entry is displayed in the pipeline ID box in the lower right hand corner of the drawing. You can use either the line name attribute (table 12, column 2) or the line ID (specified by using table 12, attribute -2) for ST, SC. Refer to LINE_ID_DEFINITION (on page 198) for information on how a line ID differs from a line name. Where:
208
'PREFIX'
is a short prefix for the attribute that will be displayed at the line endpoint.
CT, CC
is the table, column specification of the attribute that will be displayed when the connecting component is a commodity item or a specialty item.
CN
is a label description library number that defines the format of the note line when the connecting component is a commodity item or a specialty item. When CN is used then CT should be set to a value that defines the tables referred to in the note description, held in the label library. That is, if the note definition uses table 12 then CT should be set to 12. If the note definition uses table 34, then CT should be set to 34. In generating a line in the line endpoint note either column CT, CC is appended to PREFIX or the line is generated using the label description library note identified by CN. When CT, CC is defined then CN should be 0. When CN is not 0 then CC should be set to zero.
PT, PC
is the table, column specification of the attribute that will be displayed when the connecting item is a pipe. These entries are analogous to CT, CC for components.
PN
is the label description library number that defines the format of the note line when the connecting component is a pipe. PN is analogous to CN for components. When using PN you must set PT to a value that reflects the tables used in the note definition. For example, if the note uses table 12 then PT must be set to 12. If it uses table 50 then PT must be set to 50.
IT, IC
is the table, column specification of the attribute that will be displayed when the connecting item is an instrument. These entries are analogous to CT, CC for components.
IN
is the label description library number that defines the format of the note line when the connecting component is an instrument.
IN
is analogous to CN for components. When using IN you must set IT to a value that reflects the table used in the note definition. For example, if the note uses table 12 then IE must be set to 12. If it uses table 67
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO then IE must be set to 67.
Example 1: Defining Continuation Notes Define the table entries that would generate a continuation note that consists of one line for the connected line's line name. For the note, the applicable database attribute is table 12, column 2. The table entry would be: 'LINE:', 12, 2, 0, 12, 2, 0, 12, 2, 0
Example 2: Defining Continuation Notes Redo example 1 using label description library numbers rather than column numbers. The table entry for the line name would be: '', 12, 0, 951, 12, 0, 951, 12, 0, 951 The label description library number option is useful when you want to display more than one attribute on a single line in the note. CT, PT, and IE are restricted as follows: CT- 12 or 34 PT- 12 or 50 IT- 12 or 67
NOZZLE_NOTE This table is very similar to the END_POINT_COMPONENT_LABELS table except that it is used to form a note when the line endpoint is connected to an equipment nozzle. The primary difference is that with the NOZZLE_NOTE table some lines in the connection note can be generated based on the generic termination type of the nozzle. The format of a table entry is: GEN TYP, TABLE, LDL NO Where: GEN TYP
is a number that indicates those generic termination types for which this note line should be generated. The allowable values of GEN TYP are: -1- to indicate that the note line should be generated for ALL generic termination types. 1- to indicate that the note line should only be generated when the generic termination type of the nozzle is FLANGED. 2- to indicate that the note line should only be generated when the generic termination type of the nozzle is FEMALE. 3- to indicate that the note line should only be generated when the generic termination type of the nozzle is MALE.
TABLE
is the database table from which attributes are taken in defining the label description library entry that is identified by LDL NO. If the attributes defined in the note are from the equipment table then TABLE should be 21. If the attributes used in defining the note are from the nozzle table then TABLE should be 22.
LDL NO
is the label description library number that defines the format of the note.
Plant Design System (PDS) ISOGEN
209
The Options File - PD_ISO Example 1: Defining a Nozzle Connection Note Define a table that generates a nozzle connection consisting of the following lines: Line 1 Equipment item name Line 2 Nozzle tag number Line 3 A line that depends on end prep as follows: A) Flanged - size-rating-facing B) Socket weld - size-rating-facing C) Welded - size-schedule-end prep The appropriate database attributes are: Equipment name table 21, column 2 Nozzle tag table 22, column 2 size table 22, column 4 rating table 22, column 5 end prep table 22, column 6 schedule table 22, column 17 The table would be: -1, 21, 952 -1, 22, 953 1, 22, 954 2, 22, 954 3, 22, 950 A note formed by this table for a flanged nozzle might be: ITEM: 2103-C NOZ: N11 6"-CL150-RFFE If TABLE < 0 (such as -21 or -22) then the line will be appended to the previous line in the table without a linefeed. This allows you to combine attributes from tables 21 and 22 onto a single line in the note block. The Intergraph Options_Block word 23 controls whether the software uses the ISOGEN default nozzle note or the note defined by this keyword.
PRIMARY_ORIENTATION_NOTE This table is used to define valve operators as primary orientation labels. For each operator, it also defines the prefix for the primary orientation label. A table entry is as follows: 'OPER_NAME', 'NOTE_PRFX' Where: OPER_NAME
is the symbol name of the valve operator.
NOTE_PRFX
is the prefix that should be used for primary orientation note.
Example 1: Defining Primary Orientation Notes Define the table entry that would result in a primary orientation note for the valve operator OP_3. The table entry would be: 'OP_3', 'HANDWHEEL'
210
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO The above table entry creates the following note in a drawing:
where 'STEM' is defined by the Atext -213 for the direction of a spindle on a valve. Use Intergraph Option 59 to control the display of the valve operators and primary orientation notes when the orientation is skewed or in a primary axis.
SECONDARY_ORIENTATION_NOTE This table is used to define valve operators that require a secondary orientation in order to install them. For each operator it also defines the prefix for the secondary orientation label. A table entry is as follows: 'OPER_NAME', 'NOTE_PRFX' Where: OPER_NAME
is the symbol name of the valve operator which requires a second orientation.
NOTE_PRFX
is the prefix that should be used for second orientation.
Example 1: Defining Secondary Orientation Notes Define the table entry that would result in a secondary orientation note for the valve operator OP_9. The table entry would be: 'OP_9', 'ORIENT WRENCH' The above table entry creates the following note in a drawing:
The Intergraph Options_Block word 48 controls whether the software uses the ISOGEN default secondary orientation note or the note defined by this keyword.
Plant Design System (PDS) ISOGEN
211
The Options File - PD_ISO
DOTTED_SYMBOLOGY_CODE_LIST_VALUES This table is used to allow the values of certain database attributes to determine whether the piping in the isometric should be shown in dotted symbology. By using this table you can, for example, make all "existing" piping show up in the iso in dotted symbology rather than with solid lines. Only code-listed attributes can be used to determine whether or not a section of piping or a component is to be dotted. Code-listed attributes are displayed as text strings when the Piping Review Attributes command is used. Attributes are displayed as having an integer data type in the database table format. The format of an entry in this table is: ST, SC, CT, CC, PT, PC, IT, IC, VTF, VAL1, VAL2, ... VALn Where: ST, SC
defines a segment level column (from table 12) whose value might cause the piping to be dotted.
CT, CC
defines a component level column (from table 34) whose value might cause a commodity item or specialty item to be dotted.
PT, PC
defines a pipe column (from table 50) whose value might cause a piece of pipe to be dotted.
IT, IC
defines an instrument column (from table 67) whose value might cause an instrument to be dotted.
VTF
is the number of values to follow in the list VAL1 through VALn.
VAL1-VALn
are the values of the code-listed column which will force the symbology to be dotted.
Example 1: Defining Dotted Symbology Determine the table entry that will result in dotted symbology on the isometric when the construction status is "existing". The relevant database attributes are: segment: table 12, column 20 component: table 34, column 32 pipe: table 50, column 27 instrument: table 67, column 29 Looking at the code-list number 130 (the construction status code-list) we can find that the code-list number for "existing" is 3. Thus, the table entry would be: 12, 20, 34, 32, 50, 27, 67, 29, 1, 3 Whenever the value of the segment level attribute matches one of those in the list VAL1 through VALn, all of the components attached to the segment will be drawn with dotted symbology in the isometric. When the value of a component level attribute (defined by CT,CC, PT,PC, or IT,IC) matches a value in the list, only that item will be drawn with dotted symbology.
212
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Example 2: Defining Dotted Symbology Determine the table entry that will result in the dotted symbology on the isometric when the construction status is EXISTING, REVAMPED, RELOCATED, TEMPORARY, DISMANTLE or FUTURE.
NOMTO_CODE_LIST_VALUES This table is very much the same as the DOTTED_SYMBOLOGY_CODE_LIST table except that it is used to imply a status of no-mto based on the value of a code-listed attribute. When a component has a status of no-mto then it does not appear in the ISOGEN bill of materials. This table can be used in addition to the no-mto attribute that explicitly defines a component to be no-mto. Again, only code-listed attributes can be used in this table. Refer to DOTTED_SYMBOLOGY_CODE_LIST_VALUES (on page 212) for information on identifying a code-listed column. The format of an entry in this table is: ST, SC, CT, CC, PT, PC, IT, IC, ST, SC, VTF, VAL1, VAL2, ... VALn Where: ST, SC
defines a segment level column (from table 12) whose value might cause the piping to be no-mto.
CT, CC
defines a component level column (from table 34) whose value might cause a commodity item or specialty item to be no-mto.
PT, PC
defines a pipe column (from table 50) whose value might cause a piece of pipe to be no-mto.
IT, IC
defines an instrument column (from table 67) whose value might cause an instrument to be no-mto.
ST, SC
pipe supports column (from table 80). Pipe supports will appear in the MTO.
VTF
is the number of values to follow in the list VAL1 through VALn.
Plant Design System (PDS) ISOGEN
213
The Options File - PD_ISO VAL1-VALn
are the values of the code-listed column which will force the symbology to be no-mto.
Example 1: Defining Components as No MTO Determine the table entry that would result in all components with the construction status of existing to be no-mto. This example is very similar to the example covered in the section DOTTED_SYMBOLOGY_CODE_LIST_VALUES and requires an identical table entry: 12, 20, 34, 32, 50, 27, 67, 29, 1, 3
SHOP_FABCAT_CODE_LIST_VALUES If the codelist number is not listed in the option file sections for SHOP_FABCAT_CODE_LIST_VALUES or OFFSHORE_FABCAT_CODE_LIST_VALUES, the item defaults to field. This table is used to identify those values of the fabrication category attribute that are to be interpreted as meaning shop. This is necessary because ISOGEN only allows the two options of either shop or field and does not distinguish (as PDS does) between supplier and fabricator of a component. If the codelist number is not listed in the option file sections for "SHOP_FABCAT_CODE_LIST_VALUES" or "OFFSHORE_FABCAT_CODE_LIST_VALUES" the item will default to field. ISOGEN lists shop materials separately from field materials. In erection-only isometrics ISOGEN does not list shop materials. Also, some end-prep graphics are changed to distinguish between connections made in the shop and those made in the field. Field connections are implied when the fabrication category changes from shop to field or vice-versa. The format of the table entry is: VTF, VAL1, VAL2, ... VALn Where: VTF
is a number indicating the number of values to follow.
VAL1-VALn are the values of the fabrication category attribute that are to be interpreted as meaning shop by ISOGEN.
Example 1: Segregating Fabrication Categories Define the table entry that would result in the fabrication categories Contractor supplied, shop fabricated (codelist value 5) and Shop supplied, shop fabricated (codelist value 15) being interpreted as meaning shop by ISOGEN. SHOP_FABCAT_CODE_LIST_VALUES 1 2 5, 15 If needed, more than one row can be made in the table if the number of code-listed values per row exceeds 25.
214
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO Example 2:
OFFSHORE_FABCAT_CODE_LIST_VALUES If the codelist number is not listed in the option file sections for SHOP_FABCAT_CODE_LIST_VALUES or OFFSHORE_FABCAT_CODE_LIST_VALUES, the item defaults to field. The OFFSHORE section is optional and is not required in the options file. Also, refer to Offshore Material Category (on page 235) and Offshore Fabrication Category (on page 292) for related material. The format of the table entry is: VTF, VAL1, VAL2, ... VALn Where: VTF
is a number indicating the number of values to follow.
VAL1-VALn are the values of the fabrication category attribute that are to be interpreted as meaning offshore by ISOGEN.
Example 1: Segregating fabrication categories Define the table entry that would result in the fabrication categories contractor supplied, offshore fabricated (code list value 39) and shop supplied, offshore fabricated (code list value 49) being interpreted as offshore by ISOGEN. The table entry is: OFFSHORE_FABCAT_CODE_LIST_VALUES 1 2, 39, 49
Plant Design System (PDS) ISOGEN
215
The Options File - PD_ISO If needed, more than one row can be made in the table if the number of code-listed values per row exceeds 25.
MOVABLE_TEXT This table allows you to relocate or turn off certain text strings and the north arrow generated by ISOGEN. If an item is not turned off, it can either be moved to its proper position in the drawing title block or moved into a drawing margin so this it is not a part of the plotted drawing. The maximum number of movable text entries is twenty five. This table is also used to set-up/ define a table or matrix of spool numbers that you locate in your drawing. The format of a table entry is: RECNO, X, Y, TXTHGT, XOFF, YOFF, DIR Where: RECNO
216
is the record number of the item to be moved or turned off. When setting up a spool number table you set RECNO to -7. Other valid entries include any of the header record numbers defined for the PIPELINE_HEADER (on page 191) table or one of the following: Recno
Item
-25
System ID for multi-line isometrics
-700
drawing north arrow
-701
(reserved)
-702
sheet number on a drawing
-703
number of sheets on a drawing
X
is the x offset in 1/100ths mm from the bottom left corner of the sheet.
Y
is the y offset in 1/100ths mm from the bottom left corner of the sheet. Use x and y equal to 0 to turn off a text string.
TXTHGT
is the text height of the string being moved in 1/100‘s mm (that is, text in mm X 100). 0 is the default setting as defined in the ISOGEN option switches.
XOFF
is the horizontal distance in 1/100ths mm between spool numbers in a spool number table. XOFF also defines the direction of travel for locating the next table entry in the row. If XOFF is negative the next table entry is to the left, otherwise it is to the right. Should be set to zero if RECNO is not -7.
YOFF
is the vertical distance in 1/100ths mm between spool numbers in a spool number table. YOFF also defines the direction of travel for locating the next table entry in the column. If YOFF is negative then the next entry is located below the current one, otherwise it is located above it. Should be set to zero if RECNO is not -7.
DIR
is a compound number that define the size and filling order of a spool number table as follows:
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
ROWS defines the maximum number of rows in the spool number table. COLS defines the maximum number of columns in the table. TABLE DIRECTION defines the order in which the table is filled with values. If TABLE DIRECTION is set to 0 then rows of the table are filled in succession. If TABLE DIRECTION is set to 1 then columns are filled in succession. This parameter should be set to 0 if RECNO is not -7.
Example 1: Defining Movable Text Define table entries that would turn off the system ID for multi-pipeline isometrics and any title block text generated by -41 through -45 records in the PIPELINE_HEADER table. The following table would accomplish this: -41, 0, 0, 0, 0, 0, 0 -42, 0, 0, 0, 0, 0, 0 -43, 0, 0, 0, 0, 0, 0 -44, 0, 0, 0, 0, 0, 0 -45, 0, 0, 0, 0, 0, 0
Plant Design System (PDS) ISOGEN
217
The Options File - PD_ISO Example 2: Defining Movable Text The following spool table would result from the values XOFF=-700, YOFF=800, and DIR=1003004 (such as Table entry -7, 100, 100, 0, -700, 800, 1003004).
218
Certain ISOGEN text strings like the line name (-6 record) cannot be turned off. Do not set X and Y to 0. You can move these items outside the plotted area of the drawing to eliminate them. Text is justified by the lower, left corner of the string. If the number of spools on an iso sheet exceeds the number of table entries defined for a spool number table then the table is filled and an error message is written to the error file. To position the default spool numbers (that is, where the spool number is surrounded by square brackets) in a spool number table you should not have a -7 entry in the PIPELINE_HEADER table. If you want to position only the number (without the square brackets) then insert an entry into the PIPELINE_HEADER table for the -7 record but set ST, SC, and SN to 0. Also set PREFIX to a blank. If you have defined a spool prefix in the PIPELINE_HEADER table then the entire spool number, including the prefix, will be positioned in the table.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
NEW_SYMBOL_KEYS Certain ISOGEN interface logic depends on the ISOGEN symbol name. When ISOGEN symbols are redefined and renamed, this logic cannot be properly executed. This table allows you to tell the interface software which user-defined symbol your new symbol is based upon so that the special logic can be properly executed. The format of a table entry is: 'SYMBOL KEY', 'OLD SYMBOL KEY' Where: SYMBOL KEY
is the name of your new ISOGEN symbol
OLD SYMBOL KEY
is the name of the ISOGEN symbol upon which your symbol is based
Example 1: >Defining ISOGEN Symbol Keys Define a table entry which indicates that the symbol RVXX has been redefined and named RRVV: 'RRVV', 'RVXX' An entry in this table is only required when the old symbol key (or the symbol upon which your symbol is based) is one of the following CVXX, SVXX, MVXX, HVXX, XVXX, RVXX, IIXX, OPXX, PRXX, DRXX, CTXX or any symbol which you redefine and intend to map to a multi-endprep component in the model.
GENITM_NOTE_FORMAT This table is used to format notes for items that imply materials through the Implied Material Data Table and for valves with chain wheel operators, extension stems or floor stands. This table is enabled by Intergraph option 45. The table can contain up to four entries that are used to format notes. The first entry is for valves with chain wheel operators. The second entry is for valves with floor stands. The third entry is for valves with extension stems. The fourth entry is for the note pointing to a component that generates implied items through the specification database. One note is formatted for each item implied through the specification database. A table entry is a text string as follows: Label Definition Where: The label definition is formed from text together with embedded specifications for attributes pertaining to the implied item. An embedded specification is formed by a number within square brackets (such as [n]). Valid numbers that can be used together with their meanings are: [1]
The item code or commodity code of the implied item.
[2]
The quantity of implied material.
[3]
The material description of the implied material.
[4]
The chain operator number, for chain wheel operators.
Plant Design System (PDS) ISOGEN
219
The Options File - PD_ISO Example 1: Defining General Item Notes Show a note format that would display item code and quantity for an implied item: 'INCL. [2] - [1]' When an implied item is generated through the reference database, the following example note might be generated in the drawing: INCL. 1 - WBAAACFHNB
Example 2: Defining General Item Notes Show an example note format for a chain wheel operator. 'INCL. CHAIN WHEEL OPTR. [1]$WITH [2] CHAIN' The note generated on the iso might be: INCL. CHAIN WHEEL OPTR. CHAIN_3001 WITH 21'-0" CHAIN
The note formats should be defined with upper case characters. A dollar sign ($) embedded within the note will act as a line feed.
ALTERNATE_DESCRIPTION_INDEX This table is used to define which database attributes should be used as a secondary or alternate index into the material description libraries. Intergraph option 37 controls the use of this table. The format of a table entry is: TYPE, TABLE, COL, LDL NO Where: TYPE
is a number that indicates the component type that is to have an alternate index into a material description library. Valid values for type are: 1 - Commodity item 2 - Specialty item 3 - Pipe 4 - Instrument
TABLE, COL
220
5 - Pipe support is the table, column specification of the attribute that is to serve as the alternate index into a material description library. TABLE must correspond to TYPE as follows: TYPE
ALLOWABLE VALUES OF TABLE
1
34
2
34
3
50
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
LDL NO
4
67
5
80
is a label description library number that defines a composite attribute that should be used in place of TABLE, COL for the alternate index.
Example 1: Defining Secondary or Alternate Indices for the Material Description Library Show the table entry that defines the secondary index for a pipe support to be the fixed string "PSUPPORT". The table entry would be: 5, 80, 0, 972 Where: Label 972 returns the string "PSUPPORT". It does not reference any attributes in the database record for the support.
The attribute used as the primary index into the material description libraries is shown for each type below: TYPE
Primary Index (TABLE, COL)
1
34, 8
2
34, 2
3
50, 12
4
67, 2
5 80, 4 It is not possible to define a secondary index for implied materials (bolts and gaskets), for generated items (like the stub end for a lap joint flange) from the spec or for generated items from the Implied Material Data Table.
USER_DEFINED_IMPLIED_ITEM_BOM This table is used with the user-defined material take off feature. For more information, refer to User-Defined BOM / Material Control File (on page 229). Fields defined in this table will write information to the -80:-89 records for bolts and gaskets. The implied items table provides a means to map attributes that are: from the component that caused the item to be generated (e.g. flange pressure). from the spec entry for the implied item (e.g., for the commodity code). from data calculated when the item is generated (e.g. bolt length). The format of an entry in this table is: TYPE, CT, CC, CLBL, PT, PC, PLBL, IT, IC, ILBL, ST, SC, CPF, ITEM, COLUMN, FLAG Where: TYPE defines the type of implied component that the table entry is to apply to.
Plant Design System (PDS) ISOGEN
221
The Options File - PD_ISO TYPE
TABLE ENTRY APPLIES TO
1
Gaskets Only
2
Bolts only
3
Welds only
4
All of the above items
CT, CC defines a table, column specification from a generating component that is to be mapped when the generating component is a COMPONENT or SPECIALTY ITEM. Valid values for CT are 0, 12 and 34. CLBL is the label description library number that defines the note format that will be retrieved and associated with the COLUMN field. PT, PC defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE. Valid values for PT are 0, 12 and 50. PLBL is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field. IT, IC defines a table, column specification from a generating component that is to be mapped when the generating component is an INSTRUMENT. Valid values for IT are 0, 12 and 67. ILBL is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field. ST, SC defines a table, column specification that is to be mapped when the attribute is taken from the reference database entry for the implied item. Valid values for ST are 0 and 202. CPF is a connect point flag. When CPF is set to 1, it indicates that the attribute should be retrieved from the generating item‘ s connect point (that is, the connect point from the item generating the implied material). When this flag is set, CT, PT and IT should be set to 0. CC, PC, and IC should be set to a value selected from the Connect Point Attribute index in the USER_DEFINED_COMPONENT_BOM section. ITEM: When this value is nonzero it indicates that either the attribute to be mapped is data that was generated along with the implied item, or the attribute to be obtained from the spec. Values for item are dependent on the implied item type as shown below. Item Type
Item
Description
ALL
-1
Use ST, SC to obtain the attribute from the reference database.
BOLT
1
Number of bolts
2
Bolt Length in Project Units English for English Project Metric for Metric or Mixed Project
3
Bolt diameter in Project Units English for English Project Metric for Metric or Mixed Project
222
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
GASKET WELD
4
Number of nuts
5
Bolt diameter - English Units
6
Bolt length in English Units
7
Bolt weight in English Units (pounds)
8
Bolt weight in English Units (kilograms)
0 1
Weld ID number
2
Weld Type
3
Material A
4
Material B
COLUMN is a number -80:-89 defined in the MATERIAL LISTING DEFINITION (MLD) file where the value will be displayed on the iso. FLAG is a special flag used to inhibit conversion of code-listed attributes to their ASCII string equivalents.
When information is generated for an item, the item type is determined and one of the previously listed table, column pairs is selected. The selected table, column pair is then used to retrieve an attribute from the database. All pairs need not be defined. If a component data table entry should apply to only one type of item, set the table, column pairs for other types to zero. If the label number is defined as anything other than 0, that value will be used in place of the table, column value or the value from connect point attributes. Example 1: 1, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 0, 1, 0, -80, 0 This table entry maps the gasket size to the -80 record. 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 202, 3, 0, -1, -81, 0 This table entry maps the item name from the reference database for the bolt to the -81 record. 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, -82, 0 T his table entry maps the bolt length to the -82 record. 4, 34, 0, 996, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, -83, 0 This table entry will generate a note to the -83 record when the current item is a bolt or gasket and the generating component is a COMPONENT or SPECIALTY ITEM. Label 996 defines the format of the note that would be generated and in this case the label will output the generating component fabrication category as the note.
Plant Design System (PDS) ISOGEN
223
The Options File - PD_ISO
USER_DEFINED_GENERATED_ITEM_BOM Fields defined in this table write information to the -80 - -89 records for items generated through the reference database (Table 212 Implied Items) and for chain wheel operators. The generated items table provides a means to map attributes that are: from the component that caused the item to be generated. from the reference database entry for the implied item (that is, for the commodity code). The format of an entry in this table is: CT,CC, CLBL, ET,EC, ELBL, PT,PC, PLBL, IT,IC, ILBL, ST,SC, SLBL, CPI, ITEM, COLUMN, FLAG Where:
224
CT, CC
defines a table, column specification from a generating component that is to be mapped when the generating component is a COMPONENT. Valid values for CT are 0, 12 and 34.
CLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
ET, EC
defines a table, column specification from a generating component that is to be mapped when the generating component is a SPECIALTY ITEM. Valid values for ET are 0, 12 and 34.
ELBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
PT, PC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE. Valid values for PT are 0, 12 and 50.
PLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
IT, IC
defines a table, column specification from a generating component that is to be mapped when the generating component is an INSTRUMENT. Valid values for IT are 0, 12 and 67.
ILBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
ST, SC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE SUPPORT. Valid values for ST are 0, 12 and 80.
SLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
CPI
is a connect point identifier that is used to access connect point attributes by connect point color (green or red) rather than by attribute number. When CPI is set (nonzero), CT, ET, PT, IT and ST should be set to zero and CC, EC, PC, and IC should be set to a value selected from the Connect Point Attributes index. CPI
Definition
1
retrieve a green connect point property
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO
ITEM
2
retrieve a red connect point property
ATT
Connect Point Attributes
1
nominal piping diameter
2
outside diameter
3
end preparation
4
schedule/thickness
5
pressure rating
6
stress analysis node number
7
face to center distance
8
bolt type override
9
gasket separation
10
stress intensification
11
head loss factor
12
signal line type (instruments only) where *C represents either CC, EC, PC, or IC
When the value is set to 1 it indicates that the attribute to be mapped is data from the reference database. The value for CC, EC, PC, IC and SC should be set according to the table shown below when ITEM is set to 1. ATTR
Description
1
Generated item commodity code
2
Generated item quantity
COLUMN
is a number -80 - -89 defined in the MATERIAL LISTING DEFINITION (MLD) file where the value will be displayed on the iso.
FLAG
is a special flag that is normally 0 but is set to 1 to inhibit conversion of code-listed attributes to their ASCII string equivalents. When FLAG is set to 1, the code-list number will be placed in the record.
When information is generated for an item, the item type is determined and one of the previously listed table, column pairs is selected. The selected table, column pair is then used to retrieve an attribute from the database. All pairs need not be defined. If a component data table entry should apply to only one type of item, set the table, column pairs for other types to zero. If the label number is defined as anything other than 0, that value will be used in place of the table, column value or the value from connect point attributes.
Example 1: 34, 3, 0, 34, 3, 0, 50, 3, 0, 67, 3, 0, 80, 4, 0, 0, 0, -80, 0 This entry maps the item name of the component that generates some implied material to the -80 record.
Plant Design System (PDS) ISOGEN
225
The Options File - PD_ISO 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 0, 0, 0, 1, -81, 0 This entry maps the generated item quantity to the -81 record. In the case of a chain wheel operator, this entry corresponds to the length of chain.
USER_DEFINED_COMPONENT_BOM Fields defined by this table appear in component, specialty item, pipe, instrument and pipe support records. The format of an entry in this table is: CT,CC, CLBL, ET,EC, ELBL, PT,PC, PLBL, IT,IC, ILBL, ST,SC, SLBL, CPI, COLUMN, FLAG Where:
226
CT, CC
defines a table, column specification from a generating component that is to be mapped when the generating component is a COMPONENT. Valid values for CT are 0, 12 and 34.
CLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
ET, EC
defines a table, column specification from a generating component that is to be mapped when the generating component is a SPECIALTY ITEM. Valid values for ET are 0, 12 and 34.
ELBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
PT, PC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE. Valid values for PT are 0, 12 and 50.
PLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
IT, IC
defines a table, column specification from a generating component that is to be mapped when the generating component is an INSTRUMENT. Valid values for IT are 0, 12 and 67.
ILBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
ST, SC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE SUPPORT. Valid values for ST are 0, 12 and 80.
SLBL
is the label description library number that defines the format of note which will be retrieved and associated with the COLUMN field.
CPI
is a connect point identifier that is used to access connect point attributes by connect point color (green or red) rather than by attribute number. When CPI is set (nonzero), CT, ET, PT, IT and ST should be set to zero and CC, EC, PC, and IC should be set to a value selected from the Connect Point Attributes index.
Plant Design System (PDS) ISOGEN
The Options File - PD_ISO CPI
Definition
1
retrieve a green connect point property
2
retrieve a red connect point property
ATT
Connect Point Attributes
1
nominal piping diameter
2
outside diameter
3
end preparation
4
schedule/thickness
5
pressure rating
6
stress analysis node number
7
face to center distance
8
bolt type override
9
gasket separation
10
stress intensification
11
head loss factor
12
signal line type (instruments only) where *C represents either CC, EC, PC, or IC
ATTR
Description
1
Generated item commodity code
2
Generated item quantity
COLUMN
is a number -80 - -89 defined in the MATERIAL LISTING DEFINITION (MLD) file where the value will be displayed on the iso.
FLAG
is a special flag that is normally 0 but is set to 1 to inhibit conversion of code-listed attributes to their ASCII string equivalents. When FLAG is set to 1, the code-list number will be placed in the record.
When information is generated for an item, the item type is determined and one of the previously listed table, column pairs is selected. The selected table, column pair is then used to retrieve an attribute from the database. All pairs need not be defined. If a component data table entry should apply to only one type of item, set the table, column pairs for other types to zero. If the label number is defined as anything other than 0, that value will be used in place of the table, column value or the value from connect point attributes.
Plant Design System (PDS) ISOGEN
227
The Options File - PD_ISO Example 1: 34, 3, 0, 34, 3, 0, 50, 3, 0, 67, 3, 0, 84, 4, 0, 0, -80, 0 This table entry maps the item name attribute for all component types to the -80 record. 34, 4, 0, 0, 0, 0, 50, 4, 0, 0, 0, 0, 0, 0, 0, 0, -81, 0 This table entry maps the new item name attribute for component types of COMPONENT and PIPE to the -81 record. Nothing is generated in the record for SPECIALTY ITEMS, INSTRUMENTS or PIPE SUPPORTS by this table entry. 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 0, 0, 1, -82, 0 This table entry maps the GREEN nominal pipe size (also referred to as size 1) to the -82 record. Since PIPE SUPPORTS do not have connect point properties, no number is specified for them in the table entry. 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 0, 0, 2, -83, 0 This table entry maps the RED nominal pipe size (also referred to as size 2) to the -83 record. 0, 4, 0, 0, 4, 0, 0, 4, 0, 0, 4, 0, 0, 0, 0, 1, -84, 0 This table entry maps the GREEN schedule (schedule 1) to the -84 record. 12, 14, 0, 12, 14, 0, 12, 14, 0, 12, 14, 0, 0, 0, 0, 0, -85, 0 This table entry maps the insulation purpose attribute from the segment to the -85 record for all items except PIPE SUPPORTS. 12, 22, 0, 12, 22, 0, 12, 22, 0, 12, 22, 0, 0, 0, 0, 0, -86, 1 This table entry maps the paint code CODE_LIST VALUE from the segment to the -86 record. The code-list value is put in the record rather than the attribute itself because FLAG is set to 1 and the attribute being mapped is code-listed. 34, 0, 994, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, -87, 0 This table entry will generate a note to the -87 record when the current item is a component. Label 994 defines the format of the note that would be generated, and in this case the label will output the component fabrication category as the note.
NON_DIMENSIONED_SUPPORTS This feature allows you to select all pipe supports and hangers without dimensioning that are displayed on an isometric. The format of a table entry is: NON_DIMENSIONED_SUPPORTS 1 3, PS1, PS2, PSP1 Where: 1
is the number of lines to follow
3
is the number of values to follow
PS1, PS2, PSP1
are the pipe support model codes that will PS2, be displayed, but not dimensioned.
For more information on other ISOGEN dimensioning features, refer to Dimensioning and Coordinate Output (on page 299).
228
Plant Design System (PDS) ISOGEN
SECTION 8
User-Defined BOM / Material Control File The ISOGEN package allows you to define (within certain limits) the layout and content of the ISOGEN generated Material List and related Material Control File. By making modifications to the Material List Definition (MLD) file and options file you can: Revise the Material List Style. The current basic style with new optional column for weight - Style 1. Placing user-defined data in a column-type layout - Style 2. This style is defined and controlled by the new Material List Definition (MLD) file. MTO list header information is included in the material list definition file (MLD). Placing data in a column-type format (no headings) on a user-defined drawing sheet Style 3. This style will be defined and controlled by the new Material List Definition (MLD) file. The MTO list header information is displayed in the iso border file. Create a user-defined Material Control File. This file is defined and controlled by the new Material List Definition (MLD) file. The MLD file is the 13th entry in the FILES section of the ISOGEN options file. Create a new Offshore Material category. Define optional material accumulation parameters. Select part number ID box format on the plotted isometric Define the Optional output of the Length format of pipes, miscellaneous components and pipe length. Define a full range of Bolt Units (size X length). Revise the format of the cut list. Define welds to be included on the material list. Re-position the tile block. Reserve an area for a user-specified title block.
When using the new user defined formats, it is recommended that several trial runs are done. This way, you can verify that the layout is practical and that the requested data is both valid and available, before committing to project use. Validity checks will be performed on the contents of the MLD file and warning messages output when necessary. Typical checks validate all major headings and all data identifiers. A check is also done to confirm that all mandatory data is included in the file.
See Also User-defined MTO - Related Information (on page 230) Types of Material List (on page 230) Material List Definition File (see "Material List Definition (MLD) File" on page 232) User-Defined Material Control File (see "User-Defined Material Control File (.bom file)" on page 233) Offshore Material Category (on page 235) Transferring Components Between Sort Groups (on page 235) Generating an Optional Format for Length Output (on page 236) Bolt Units (size x length) (on page 236) Generating a Revised Format of the Cut List (on page 237)
Plant Design System (PDS) ISOGEN
229
User-Defined BOM / Material Control File Welds in the Material List (on page 238) Style for Fabricated (Pulled) Bends Output (on page 238) Style for Material List Output (on page 239) Positioning the Title Block (on page 239) MLD File Content (on page 239) MLD File Format Guidelines (on page 241) Style 3 Material List (on page 242) Example User-defined Material List - Style 2 (on page 244) Example User-defined Material List - Style 3 (on page 244)
User-defined MTO - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when creating a user-defined BOM or Material Control file. Related ISOGEN Options (Appendix) ISOGEN Options: 2, 23, 24, 25, 26, 27, 28, 29, 30, 35, 65, 73, 74 Related Intergraph Options (Section 7) Intergraph Option: 8, 10, 14, 22, 29, 30, 33, 36, 37, 45, 47, 50, 52, 54, 56, 62 Related Options File Material (Section 7) USER_DEFINED_COMPONENT_BOM USER_DEFINED_GENERATED_ITEM_BOM Also: The thirteenth entry in the FILES Section of the options file: MLD file (See Chapter 8) Related ISOGEN ATEXT Records (Appendix) -322, -323, -339, -356 - -363, -365, -367, -368 - -378, -415 - -419, -421 - -423, -455
Types of Material List Three types of material lists are available Style 1, Style 2 and Style 3. ISOGEN option switch 23 controls which Style material list is used. The MLD file contains the definition of the content and format of Style 2 and Style 3 Material Lists. Style 1 - Standard Material List To produce a material list identical to those produced prior to the 5.0 ISOGEN software release, turn off the intermediate sub-headings (PIPE, FITTINGS, FLANGES, etc). This can be done by setting the appropriate Atexts to BLANK. This will continue to provide the capability of producing a continuous-type material list. A 4.3 version of the ISOGEN options file can be used without any modifications to produce an iso with the 5.0 software that looks as it did when it was produced with the 4.3 software. Style 2 - User-defined Variation of the Standard Material List Style 3 - User-defined Text and User-positioned Text Only text is output. No headings are output. Style 3 works well for boxed or column type bills of material. The Cut List and Center Line Summary facilities are not available for Style 3.
Basic Contents of a Style 1 Material List
230
Standard form Material List (as currently output and using all current sort criteria) New column for component weight (optional) New section for Offshore materials
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
Revised Cut List (optional) New form of the Bolt size x length output An option for repositioning the title block when Material List on the right is used.
Basic Contents of a Style 2 Material List
User variation of the Style 1 material list User-definable column headings/data content for horizontal layout (done in the MLD file) Extra data attributes available for listing (This can be done by using the 80- 89 record identifiers in the MLD file.) Similar vertical layout to Style 1. (uses the same sort criteria) All options listed for Style 1 Facility for User to change sort group of components. (For example, move Blank Flange from Valve/In-Line Item group to Flange group)
Basic Contents for a Style 3 Material List
Fully user-defined drawing backing sheet (All column, boxes, headings, etc pre-defined in the seed isometric or border file) Three major categories of Materials to be identifiable (For example, FABRICATION, ERECTION, OFFSHORE) No intermediate Material Type headings to be output User-definable data content and data output positions for all material list information in the MLD file Extra data attributes available for listing (This can be done by using the 80- 89 record identifiers in the MLD file Material Listing UP/DOWN facility For example: listing TOP to BOTTOM listing BOTTOM to TOP listing Fab Materials DOWN/ Erec Materials UP listing Erec Materials DOWN/ Fab Materials UP If the Offshore category is used, you are restricted to using a continuous list (Top to Bottom/Bottom to Top) and should use the column for category identification (For example, FAB, EREC, OFF ). Automatic ISO overflow facility (used if there are too many parts for the given backing sheet)
See Also Operating Requirements (on page 232)
Plant Design System (PDS) ISOGEN
231
User-Defined BOM / Material Control File
Operating Requirements The following requirements must be met to successfully use the user-defined BOM / Material Control File functionality. Material List Definition (MLD) File This will be a required entry when using the user-defined bill of materials (Style 2 or Style 3). The options file section titled FILES will require a new entry (the 13th entry) defining the location and name of the user-defined MLD file. Bill of Material Columns. You must define data to be output on the MTO for each component type in the MLD file. This done by using new or existing data identifiers. Existing BOM identifiers are Commodity Code (-20 record) or Commodity Description (-21 record). New BOM identifiers consist of user-defined identifiers: -80 - -89 record types PT-NO, QTY, N.S., WEIGHT, CATEGORY, GROUP The user-defined identifiers can contain anything from the database for a specific component. Three sections (see below) of the Intergraph options file define reported information and the identifier that is associated with that information (-80 - -89 record types) per item type.
The -20 and -21 record types cannot be redefined. You will not be required to output either of these record types on the user-defined BOM, but the .idf file will always contain these two records. Type -80 identifiers, if any, will always follow the -21 record type in the .idf file. User-defined information can be formatted by manipulating the following three sections in the options file. USER_DEFINED_COMPONENT_BOM (on page 226) - used with components, engineered items, pipe, instruments and supports. USER_DEFINED_IMPLIED_ITEM_BOM (on page 221) - used with bolts, gaskets and welds. USER_DEFINED_GENERATED_ITEM_BOM (on page 224) - used with cap screws and chain wheel operators. To generate an entry in the bill of materials for generated items, Intergraph option 45 must be set to 1 or 3.
Material List Definition (MLD) File The options file section titled FILES will require a new entry (the 13th entry) defining the location and name of the user-defined MLD file. The new entry in the FILES section will be verified, mounted and included as a -122 record type in the .idf file. This entry is required when using the user-defined bill of materials. The MLD file allows you to define (with certain limits) the style and content of the following: The Heading content and layout of a PRINTED Style 1 (Weight Heading only) or Style 2 Material List. The column headings, data content definitions and positional coordinates of the main body of a plotted and/or printed Style 2 Material List. The main body of a Style 1 (current style) plotted or printed material list cannot be changed.
232
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
For a Style 2 type Material List the BASIC FORMAT is the same as the current style. The number, position, and content of the various vertical data columns is the part of the list that is user definable. The data content and positional coordinates for all items on a plotted Style 3 Material List.
When using a Style 3 Material List, the option of obtaining a printed list is not available. The layout/data content of a user-specified Material Control File. Because of the current methods used within the ISOGEN program, the quantities included in the Material Control File must be identical to the quantities generated for the Material List. This is because the same accumulation rules are used for both.
User-Defined Material Control File (.bom file) When Intergraph option 1 is set to 1, the MLD file allows you to define the layout and content of the printed Material Control File (M/C File). The Material Control File is intended to be used as a vehicle for data transfer between 'Systems'. There will be several differences in layout when compared with the file generated for a Printed Material List (.prt file).
Basic Requirements for a Material Control File
Allow any width (Not limited to 132 characters). Allow any length of file. No 'Paging' functionality is required. Include any Title Headings/Column Headings (if user-defined) once at the start of the file. Output of lengths in any quantity (QTY) column should be in the format set in ISOGEN option switch 24. Bolts to be included in the file should follow the same rules as the bolts used for the associated material list.
Size and length units are set by ISOGEN option switch 65. Use ATEXT -359 to reformat the size and length information. The ISOGEN software allows you to identify all UNITS used within the M/C file through the use of Unit Identification entries. There is no limit on the number of Unit Identification entries and the format is user-definable. Unit ID entries must be included in the MLD file and immediately follow the MATERIAL-CONTROL-FILE identifier. Any unit id entries will be the first items output in the M/C file. Unit identification entries will not impact the ISOGEN system. Their only purpose is to identify the UNITS used for size and lengths in the M/C interface file. Some typical unit ID entries: UNITS-BORE data UNITS-LENGTH data UNITS-BOLT-DIA data UNITS-BOLT-LENGTH data Where: data identifies the units used in the M/C file. A user-defined Material Control file will be triggered by the identifier MATERIAL-CONTROL-FILE which is located in the MLD file. The definition of the required file (layout/content) will follow the MATERIAL-CONTROL-FILE identifier. The file can be generated either with or without Titles and/or Column Headings.
Plant Design System (PDS) ISOGEN
233
User-Defined BOM / Material Control File The definition of Title Headings, Column Headings and Data Items will use the same basic rules as a Style 2 printed material list. The key identifiers to be used are: PRINTED-M/C-TITLES PRINTED-M/C-COLUMN-HEADINGS PRINTED-M/C-DATA-ITEMS In the case of Data Items, the -39 IDF RECORD IDENTIFIER can be included in the Material Control file, but not on the Material List. This can only be used when using the Material List Non-Accumulation facility (ISOGEN option 74).
Available Data Items for the Material Control File Unique Name
IDF Record Number
PIPELINE-REFERENCE
-6
PIPING-SPEC
-11
PT-NO
-
QTY
-
N.S.
-
ITEM-CODE
-20
DESCRIPTION
-21
WEIGHT
-
CATEGORY
uses ATEXT -376 - 378
GROUP
uses ATEXT -307, -308, -309, -311 - -315, -339, -37580 - -89 (user-defined attributes)
UNIQUE COMPONENT IDENTIFIER
234
-39 Segment and Component Occurrence Numbers
If Unique Name and associated IDF Record Number both exist, either may be used. UNIQUE NAMES with no IDF Record Numbers are shown with a - in the IDF RECORD NUMBER column. When this occurs, you must use UNIQUE NAME. IDF Record Numbers with no UNIQUE NAME are shown with a - in the Unique Name column. When this occurs, use IDF Record Number.
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
Offshore Material Category Any item designated as Offshore will be treated as an ERECTION type item in the drawing, but will be listed on the Material List under a new main heading as defined by ATEXT -371. All materials sorted are within the new heading category. The M/C file will contain a 3 in word 6 of existing component records when the item is designated as Offshore.
Transferring Components Between Sort Groups The MLD file has a TRANSFER feature that will allow you to move components from one sort group to another. The identifier TRANSFER must be followed by any relevant information that would identify the component to be transferred and the new group under which it will be listed. Component identification will be done by record ID numbers. Refer to the Record Identification Numbers listed in Appendix B of this document (35 =Elbow, 100 = pipe). Available sort Group identifiers include: PIPE pipe VALV valves + inline items FITT fittings INST instruments FLAN flanges SUPP supports GASK gaskets MISC miscellaneous components BOLT bolts WELD welds
If you plan to list any of the above Group Identifiers on a Style 2 or Style 3 Material List, ATEXTs -307, -308, -309, -311, -312, -313, -314, -315, -339, and -375 must be set in the options file. The TRANSFER feature cannot be used to transfer flanged pipe (idf record 101) to the PIPE group. The PIPE group only accumulates by length, and flanged pipes and other Fixed Length pipes are reported by quantity (i.e., number of pieces of identical-length pipe) in the FITTING group. A typical entry in the MLD file might be: TRANSFER 107 FLAN Where: 107 is the record ID for BLANK FLANGES and FLAN is the NEW sort group under which Blank Flanges should be listed. Any number of blank characters between record ID and Group identifiers are allowed.
Plant Design System (PDS) ISOGEN
235
User-Defined BOM / Material Control File
Generating an Optional Format for Length Output By default, length output on the Material List for PIPE, MISCELLANEOUS COMPONENTS and CL LENGTH is set to the nearest 1/10 M or 1/10 FT and is formatted: Metric 10.4 M English 10.4 ' ISOGEN option 24 allows for an alternative format to output either in millimeters or feet and inches. Metric 1040 mm (rounded to the nearest mm) English 10'-5" (rounded up to the nearest inch)
Bolt Units (size x length) Option switch 65, Bolting Length in the M/C file, allows you to define bolt length/bolt diameters. Any value set in the last position of ISOGEN option switch 65 is output in the second digit (tens position) of word 2 in the 60 type record in the M/C file. Any value set in the second position of ISOGEN option switch 65 is output in the third digit (hundreds position) of word 2 of the 60 type record in the M/C file. Bolt diameters (in word 2) and bolt lengths (in word 7) of 500 (bolt) records in the M/C file will be generated in the units appropriate to the various ISOGEN switch settings. The Material List also allows an alternative output format for bolts. The alternative output will be used whenever ATEXT -359 is set to any value other than blank. The suggested setting is diameter x length. ISOGEN will always output in a bolt-diameter-by-bolt-length order. Bolt Units will be placed just below the new heading using a program generated text string. The text string is created by using a combination of ATEXTs -330 and -331. Typical Bolt Unit Output: BOLTS DIS x LENGTH (ATEXT -359) (INS x INS) Bolt Descr.
236
(Generated)
3/4 x 2.1/2
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
Generating a Revised Format of the Cut List Modifications made to the current cut list format
ATEXT -322 (Cut) is ignored. ATEXT -323 (Length) is moved up to the top line of the headings. Set ATEXT -361 so that the default text, Ft-Ins, will be positioned below LENGTH when imperial units are being used. Place ATEXT -331(mm) below LENGTH when mixed or metric units are being used. Set zero inches to output as 2'0" and not 2'. The revised layout still has two cut pieces on each line.
Typical layout: PIECE NO.
LENGTH N.S. REMARKS PIECE LENGTH N.S. REMARKS (FT-INS) (INS) NO. (FT-INS) (INS)
New cut list format The new cut list format has a revised layout with only one cut piece per line. To request the new cut list format, use ISOGEN option 2. Typical new layout: PIECE LENGTH NO. (FT-INS)
N.S. END END ITEM (INS) ONE TWO CODE
PIECE LENGTH NO. (FT-INS)
OR N.S. END END ITEM (INS) ONE TWO CODE
Gaps between new heading elements are handled by the ISOGEN software based on either the actual Atext heading or the length of the information items that are printed under each heading. This will be either the standard Atext or any user-modified Atext. When using the new cut list format, you must verify that the total width of the cut list is less than the width of the requested material list. This will prevent the cut list from overflowing onto the drawing section of the isometric. Use ATEXTs -362, -363, -364, -365 when using the new cut list format. If PART NO. is required on the cut list instead of ITEM CODE, ATEXT -364 should be blank and ATEXT -365 set to PART$NO.
The Cut List Remarks Column Current Atexts for cut list REMARKS (-326, -327, -328) are still used. If any of these Atexts are changed, sufficient space should be left between column headings to accommodate data. In the new cut list format layout, multiple remarks are allowed. Each remark is located on a separate line. For example: REMARK
Plant Design System (PDS) ISOGEN
237
User-Defined BOM / Material Control File LOOSE FLG FF WELD Multiple occurrences of the same remark will be output in the form PLD BEND (2) where the last 2 characters are automatically generated.
End One and End Two Columns Entries in these columns describe the operations performed in order to prepare the ends for fabrication. Five ATEXTs (-366 - -370) are available to identify the five basic operations that can be recognized by the ISOGEN system.
For the new cut list format, certain items must be treated as BWs (Butt Welds), but do not have the BW end condition as part of the SKEY. These items include: Flanges (105/106) FLWN - Flange Weld Neck FOWN - Flange Orifice Weld Neck FLSE - LJSE Butt Weld Type All other 105's and 106's to use Square Cut The type of end preparation on pipe is determined by the SKEY of the fitting or by the weld type. For weld types: SKEYS WW, WS, WF, assume BW end preparation.
Welds in the Material List When using INTERGRAPH option 62 and ISOGEN option 64, welds can be added to the Material List. Welds can be displayed in any of the Fabrication/Erection/Offshore sections of the Material List. To list welds in the last position of each section of the Material List, use the heading defined by ATEXT -375. Welds added to the Material List will not be included in the standard M/C interface file. It is a user option in any user-defined M/C file.
Accumulation of welds is controlled by ISOGEN option switch 74. Weld part numbers are not normally indicated on the plotted iso section of the isometric. If needed, ISOGEN option 73 with a Style 3 for weld part numbers can be used to place weld part numbers.
Style for Fabricated (Pulled) Bends Output By using ISOGEN option 23 (position B), the outputs Bend Angle and Bend Radius can be displayed for pulled bends. The following is a typical revised output using the Style 1 and Style 2 Material Lists. Description
NS
QTY
U03 Fabricated (Pulled) Bend 3.0D Bend Radius Angle 85.0
1
1
238
Part numbers less than 10 have a zero included (For example, U03 and not U3). Bend radius messages will use ATEXT -337 for bends expressed in number of diameters. (For example, 3.0D Bend Radius).
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
A bend radius expressed in mm or Ft/Ins uses ATEXT -338 with the actual radius listed. (For example, 450 mm Bend Radius or 1'-6" Bend Radius). ATEXT -374 is used to generate the ANGLE text element in a format such as 85.0 (for an 85 degree angle).
Style for Material List Output When using ISOGEN option switch 23, position A and B, with setting 10 or 11: The current form of output is sorted into the categories, Fab/Erec/Offshore, with sub-groups of Pipe, Flanges, Fittings, etc. within each category. Except for the addition of the new Weld sub-group, there is no change to the Material List that is currently generated. When Using ISOGEN option switch 23, position A and B, with setting 20 or 21: An alternative form of output that has no separate Fab/Erec categories and no sub groups is generated. This creates a continuous Material List with component and welds listed in the order they were found in the intermediate data file (.idf file). This does not apply to Gaskets and Bolts that are accumulated; they are printed in the weld list as the first occurrence of each type.
Positioning the Title Block ISOGEN option 25 allows you to either turn off or reposition the Title Block to the bottom of the Material List. ISOGEN calculates the height of the Title Block and draws a horizontal line between the two vertical lines that form the Material List boundaries. Checks are then made on ATEXTs -317 and -318. If they are not set to blanks and have not been positioned, the CL summary is positioned above the Title Block. ISOGEN option switch 35 reserves an area at the bottom of the Material List.
MLD File Content Heading Definitions for a Style 2 printed material list (ISOGEN MTO neutral file) in the MLD file contain three types of information items: A Heading Title element An associated data item to be listed with the Title element A basic activity identifier. All data items may be identified by either 'NAME' or their .idf file record ID Number. A typical MLD file layout for a Style 2 Printed Material List heading would be:
Plant Design System (PDS) ISOGEN
239
User-Defined BOM / Material Control File PRINTED-MATERIAL-LIST TITLES PAGE ' ' 'Blank' 'Blank' PIPELINE REF :- '-6' PROJECT NO. :- '-9' 'Blank' AREA REF :- '-10' REVISION NO. :- '-8' 'Blank' PIPING SPEC :- '-11' DATE OF RUN :- '-14' 'Blank' 'Blank'
The normal Material List would then be printed. This would be either the normal Style 1 list or any Style 2 list that you have defined. In the previous example: '' is used with the page attribute and indicates a program generated page number. 'Blank' indicates a blank line. Titles will be output at the top of each new page. Number of lines per page will be taken from the existing option switch 63.
Items Available for Output as Part of a Printed Material List Heading Unique Name
IDF Record Number
Pipeline-Reference Drawing
-6
Piping-Spec
-11
Nominal-Class
-12
Nominal-Rating
-12
Date-DMY
-14
Pipeline-Temp
-19
System-Reference Page
-25
Column Headings and Data Content Guidelines for Style 2 Material List
240
Maximum heading width should not exceed 130 characters. There should always be the same number of data items as column headings unless space is left for future data additions. Column headings in the MLD file, must use the exact format of the required listing followed by the relevant data items to be printed. Each name (identifier) must be enclosed in single quotation marks.
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
MLD File Format Guidelines As a general rule, all heading and title formatting must be positioned in the MLD file exactly as it is to be positioned on the printed output. Title elements, other than unique identifiers, can be used with any format. Data item identifiers will be enclosed in single quotation marks. Unique identifiers are used to determine what is defined and must match exactly. These identifiers include: STYLE2-COLUMN-HEADINGS STYLE2-DATA-ITEMS
The format must be headings followed by data items. Blank characters can be used as required. Blank columns are allowed. Use a | character to indicate vertical column positions. Column headings can be any ASCII string. Data items must carry the following: A data item identifier A start position along the horizontal line A justification marker. Data Item Identifiers can be defined by using a Unique Name or, where applicable, the IDF Record Number (For example, 'Item-Code' -30 L or '-20' 30 L). If a separation line is required on the generated Material List to separate the PART NO. column from the rest of the List, a | character should be inserted in the required position on the last line of the column headings. If an indicator is not found, the Material List will be generated without a separation line. A separation line will output on an iso only if ISOGEN switch 18 is set to 0 to plot the isoplot drawing frame. If the PT-NO (part number identifier) column is located at the extreme left or right side of the Material List, ISOGEN will generate the vertical dividing line to separate the part numbers from the remaining items. A | character should be inserted end the end of the last line of the column headings to indicate where the right border line of the Material List is required (For example, two spaces beyond the maximum width of the last data item).
Justification Markers R
Right Justified
L
Left Justified
N
A true number field. If N is used as a decimal number (Real) the decimal point will be positioned in the selected column. If N is not used as a decimal number (Integer), the units digit is positioned in the selected column.
Style 2 and Style 3 Data Item Identifiers The following values are available for use as Data Identifiers in the MLD file for Style 2 and Style 3 MTOs. The allowable justification for each record is also listed.
Plant Design System (PDS) ISOGEN
241
User-Defined BOM / Material Control File Unique Name
IDF Record Number
Allowable Justification
PT-NO
-
L or R
QTY
-
N (fixed)
N.S.
-
L (fixed)
ITEM-CODE
-20
L or R
DESCRIPTION
-21
L (fixed)
WEIGHT
-
N (fixed)
CATEGORY
uses ATEXT -376 - 378
L or R
GROUP
uses ATEXT -307 - -309, -311
L or R
-
-80 - -89 (user-defined attributes)
L (fixed)
-
-39 Only used on Material Control listings, Segment and Component Occurrence Numbers
L or R
When Unique Name and associated IDF Record Number both exist, either may be used. Unique Names with no IDF Record Numbers are shown with a - in the IDF Record Number column (PT-NO, QTY,N.S., WEIGHT). When this occurs, use the Unique Name. IDF Record Numbers with no Unique Name are shown with a - in the Unique Name column. When this occurs, use IDF Record Number.
See Also Style 3 Material List (on page 242)
Style 3 Material List A Style 3 Material List requires a backing sheet (drawing frame) that contains a reserved area for Material List information. The precise format is user-definable, but no column headings are defined in the MLD file. All column headings must already exist in the seed or border design files. Set the margins so that drawing graphics do not overlap the style 3 MTO. For style 3 MTO isometrics, margins (set by ISOGEN options 10, 11, 12 and 13) control the drawing graphics boundaries. This style of output requires two types of information. STYLE3-CONTROLS STYLE3-DATA-ITEMS
Basic Control Information for a Style 3 Material List Unless otherwise stated, where a number is required it will be integer or in real mm's with only one decimal place allowed.
242
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File
Unless otherwise stated, all of the following inputs are mandatory. Define the type of list that will be generated (sectionalized, continuous, etc.). Valid types include: Continuous-Down Continuous-Up Fabrication-Down Fabrication-Up Erection-Down Erection-Up Offshore-Down Offshore-Up Erection/Offshore-Down Erection/Offshore-Up These will be used as either single entries or multiple entries depending on the form of list required. Identify start positions for information using the format: Start-Position XPOS YPOS Where: XPOS and YPOS is the x and y location in the design file Define vertical spacing between each line of horizontal text using the format: VERTICAL-SPACING value Define the maximum number of lines that can be printed before automatic overflow onto another sheet occurs. This number can be defined for the complete list or on a section-by-section basis if the section function is being used. Use the format: MAXIMUM-ENTRIES value Where: value is an integer Define the character height to be used for material list information using the format: TEXT-HEIGHT value Define the level where material list information should be placed (optional). Using the format: DRAWING-LAYER value Where: value is a level 1 - 63 Define character weight (optional). Using the format: TEXT-THICKNESS value Where: value is a weight 0 - 10
Style 3 Data Item Information
Data items must specify a data item identifier and start position information. Identifiers -80 - -89 must carry the maximum number of characters allowed on each print line. Start position is the x position in mm's that identifies the bottom left hand point of the text string to be plotted. All text will be LEFT justified. Example Input: Data Item Identifier Xpos Max char ITEM-CODE 225.0 -80 280 47
See the previous table under the heading Style 2 and Style 3 Data Identifiers for a list of Style 3 Data Identifiers.
Plant Design System (PDS) ISOGEN
243
User-Defined BOM / Material Control File
Example User-defined Material List - Style 2 STYLE2-COLUMN-HEADINGS PART SIZE ITEM COMPONENT QTY BLT BOLT NUTS/ MODEL SCH/ END MATL GEOM NO. (INS) CODE DESC. DIA LNGTH BLT CODE RAT PREP GRADE STD 'blank' STYLE2-DATA-ITEMS 'PT-NO' 2 R 'N.S.' 6 L 'ITEM-CODE' 13 L 11 'DESCRIPTION' 26 L 28 'QTY' 58 N '-80' 79 L 5 !Model Code '-81' 85 L 5 !GCP Sch/Rat '-82' 92 L 5 !End Prep '-83' 97 L 10 !Matl Grade '-84' 107 L 15 !Geo Std '-85' 68 L 10 !Bolt Length '-86' 73 L !Nuts/Bolt '-87' 62 L !Bolt Diameter
Example User-defined Material List - Style 3 Continuous Down Type : STYLE3-CONTROLS START-POSITION 225.0 190.5 VERTICAL-SPACING 4.5 TEXT-HEIGHT 2.5 DRAWING-LAYER 15 CONTINUOUS-DOWN MAXIMUM-ENTRIES 55 TEXT-THICKNESS 2 STYLE3-DATA-ITEMS Typical Data
Fabrication-Down, Erection-Up Type: STYLE3-CONTROLS VERTICAL-SPACING TEXT-HEIGHT TEXT-THICKNESS DRAWING-LAYER MAXIMUM-ENTRIES FABRICATION-DOWN START-POSITION ERECTION_UP START-POSITION STYLE3-DATA-ITEMS | Typical Data
244
4.0 2.5 3 15 37 225.0 190.5 225.0
42.0
Plant Design System (PDS) ISOGEN
User-Defined BOM / Material Control File Split Type: STYLE3-CONTROLS VERTICAL-SPACING 4.0 TEXT-HEIGHT 2.5 TEXT-THICKNESS 2 DRAWING-LAYER 15 FABRICATION-DOWN START-POSITION 225.0 190.5 MAXIMUM-ENTRIES 14 ERECTION_DOWN START-POSITION 225.0 130 MAXIMUM-ENTRIES 14 Offshore_DOWN START-POSITION 225.0 70 MAXIMUM-ENTRIES 7 STYLE 3-DATA-ITEMS Typical Data
Plant Design System (PDS) ISOGEN
245
User-Defined BOM / Material Control File
246
Plant Design System (PDS) ISOGEN
SECTION 9
Creating Seed Files for Extraction To extract and plot isometrics, create a seed design file and a seed plot request file. The seed file names are keyed in at the Interactive Isometric Extraction form and the Define Default Set form (see Interactive Isometric Extraction (on page 23) and Define Default Sets (on page 57) for more information).
See Also Creating the Isometric Seed File (see "Creating an Isometric Seed File" on page 247) Creating a Plot Request File (on page 248)
Creating an Isometric Seed File The isometric seed file is an empty MicroStation design file that the system copies before creating a new isometric. The seed file usually contains a single reference file consisting of the drawing border and title block. To create an isometric seed file: 1. Copy one of the product option files (defaults.dat, mxdefaults.dat, etc.) and set ISOGEN options block word 14 for one of the standard drawing sheet sizes, or words 15 and 16 for a nonstandard sheet size. Setting these option block words defines a box within which your drawing border, title block and the ISOGEN drawing will reside. 2. Set ISOGEN option 3 to 1 so that you can see the corners of the drawing border box when an isometric is created. Also, set the ISOGEN options block word 35 to define the reserved area for the title block.
Plant Design System (PDS) ISOGEN
247
Creating Seed Files for Extraction 3. Set ISOGEN options 10 - 13 to create margins from the edge of the box created in Step 1. All of your user-defined border and title block graphics must be drawn within these margins; one or more of them will probably be quite large. You cannot reserve irregularly shaped areas within the drawing box for your border and title block. You must fit them into the rectangular margin areas. 4. Generate an isometric using the interactive software (see Interactive Isometric Extraction (on page 23) section Interactive Isometric Generation). The iso should be small enough so that only one sheet is generated. 5. Call up the iso in graphics and plot it with the appropriate drawing size. Plot the area that will contain both your user-defined graphics and the ISOGEN drawing. Do not plot a small strip along the bottom of the drawing (approximately 1/8") since you will probably want to move into that area some ISOGEN-generated text strings that cannot be turned off. You do not have to plot an ISOGEN D size drawing with D size dimensions. You can use ISOGEN switches to make any size drawing you wish. You can then scale the drawing to have any plotted size you like. For this reason, experimentation is usually needed to arrive at a suitable combination of ISOGEN and plotting parameters. Examine the plot. There must be sufficient space for your user-defined border and title block graphics. Also, the drawing graphics and text size must be suitable for the plot size. Adjust ISOGEN option 14 or options 15 and 16 to adjust the scale of the drawing. Adjust options 4 and 27 to change the text size. 6. Cycle through Steps 2 through 5 until you are satisfied with the resulting plot.
7.
8. 9. 10.
In general, ISOGEN seems to perform better with a larger drawing area than a smaller one (the drawing area is increased with option 14 or options 15 and 16). Try to find a median between providing ISOGEN a large drawing area and scaling down the drawing for plotting purposes. At some point, scaling down a large drawing results in text that is too small. If the text size cannot be increased, then you will either have to plot with a bigger scale (resulting in a larger drawing) or reduce the ISOGEN drawing area (to reduce the amount of scaling needed at plot time). After completing Steps 1 through 6, create a drawing border in a separate design file. Create a 2D design file for your border and attach the drawing file created above as a reference file. Use the drawing to locate your border and title block. Use the reference file attachment from the border file and attach the new border to the new seed. Place the required text nodes in the new seed file for use with the Title Block Tables file. Turn off the ISOGEN border with ISOGEN word 18.
Creating a Plot Request File The plot request file is a special file used by the plotting software when processing a plot job. It contains values for plotting options and, sometimes, a definition of the plot itself. The format of the plot request is standard IPLOT format.
See Also IPLOT Plot Request Files (on page 249)
248
Plant Design System (PDS) ISOGEN
Creating Seed Files for Extraction
IPLOT Plot Request Files An IPLOT plot request file is necessary if you want to plot isometrics using the IPLOT software. Use the following steps to create an IPLOT plot request file: 1. Copy your isometric seed file and get into the copy in graphics. Set up view 1 to have all of the parameters that you wish to be active for the plotted drawings (that is, turn off text node display, turn on/off levels to be plotted, etc.). Save this set-up with FILE DESIGN. Determine the coordinates, in working units, of the area to be plotted. These should be the lower left and upper right corners of the fence that would have been used for plotting. Write the coordinates down. 2. From the command line prompt, key in the following command to create the IPLOT plot request file: $iplot create "plot parameter filename" -design=design name -queue=queue name region=[x1, y1, x2, y2] -scale=design units:plotter units -view=# where: plot parameter filename
is the plot parameter file to be generated
design
is the design filename created by copying the seed file in step 1 above.
queue
identifies the plot queue on the plot node.
region
identifies the area to plot. Use the coordinates determined from step 1.
design units:
is an option scaling ratio for the plotted area. If you prefer, you may use -XSIZE=x size or -YSIZE=y size instead of the -SCALE= parameter to define the scaling. You may also leave this parameter off if no scaling is needed.
plotter units
#-
view number
border name
is the border filename to be attached as reference file with default logical name IPLOT_R2. The logical name IPLOT_R2 should not be changed.
Example 1: iplot create test.i -design=test.dgn -queue=muxque -region=[0,0,17:0,11:8] -view=1
The system creates the file test.i.
Plant Design System (PDS) ISOGEN
249
Creating Seed Files for Extraction
250
Plant Design System (PDS) ISOGEN
SECTION 10
Mapping Attributes to the Title Block The Title Block Tables Files are used to associate database attribute data and other data with text nodes in an isometric design file. You make this association between attribute data and design file text nodes so the batch iso extraction software can automatically fill out the drawing title block. Intergraph option 34 must be set to 1 before the software will generate the title block data files. You can obtain title block information from several sources using the Title Block Tables File. These sources include database attributes from the line being extracted (for example, piping materials class), data stored within the project control database information (for example, revision block data), from the Notes Table and internally generated information (for example, sheet number). The format of the tables and the table entries in the Title Block Table Files are identical to that of tables and table entries in the iso extraction Defaults file. The format is as follows: The body of the table is preceded by a keyword. Each keyword is followed by a number that defines the number of table entries. The elements of each table entry are separated by commas. The following three tables are used to map attributes to the drawing title block: The text node number cannot be greater than 9999. Also, the number of text nodes in a seed file cannot exceed 250. 1. Notes Table (Table keyword is SEGMENT_DATA_TABLE) You can use this table to identify the attributes that should be summarized in tabular form on each sheet of a multisheet isometric. Usually, data summarized in this form will be from piping segments, but it may also originate from the Notes Table. When the title block for a particular sheet is filled in, only data from segments extracted to that sheet is placed in the title block. 2. Drawing Data Table (Table keyword DRAWING_DATA_TABLE) You can use this table to identify attributes from the first piping segment, the largest piping segment, from the Notes Table or from the project control database. Attributes mapped through this table will appear on every sheet of a multisheet isometric. 3. Sheet Data Table (Table keyword SHEET_DATA_TABLE) You use this table to place the sheet number and number of sheets in each drawing. You can also use this table to append the sheet number onto the drawing number for each sheet, making the drawing number unique for each sheet.
See Also SEGMENT_DATA_TABLE (on page 252) DRAWING_DATA_TABLE (on page 255) SHEET_DATA_TABLE (on page 260)
Plant Design System (PDS) ISOGEN
251
Mapping Attributes to the Title Block
SEGMENT_DATA_TABLE Each sheet of a multisheet iso consists of the piping from one or more segments in the piping model. You can use the SEGMENT_DATA_TABLE to define a summary block of segment information in a drawing title block. The ISOGEN interface uses this table to create an output file containing data for all of the segments that make up the pipeline. Next, ISOGEN creates an output file that identifies which segments appear on each sheet of a multisheet iso. These two files are then used to determine the information that must be summarized on each individual sheet.
Example 1: Suppose that for each sheet of an isometric, you want to summarize, in a table, data from all of the piping segments that appear. Here is an example table for a specific sheet: Piping Spec
1C0031
1C003 1
1C008 0
Design Pressure
150
150
150
Design Temperature
300
300
600
Insulation Type
C
D
C
Insulation Thickness
6"
8"
6"
In this example, there are three segments where the data being summarized is different. This does not mean that the sheet contains only three segments, but that there are only three different segments (where the difference is defined only by the attributes in the table). The segment attributes shown in the table above are: Piping Spec
Table 12,
Column, 12
Design Pressure
Table 12,
Column, 28
Design Temperature
Table 12,
Column, 29
Insulation Type
Table 12,
Column, 14
Insulation Thickness
Table 12,
Column, 15
The purpose of the SEGMENT_DATA_TABLE is to allow you to define all of the attributes that make up a single column in the title block summary table. Once you have defined these attributes, the batch extraction software determines how many columns of actual data are needed based upon the specific segments that appear on each sheet. You must have one table entry in the SEGMENT_DATA_TABLE for each attribute you want to summarize in the Segment Summary Table. An entry in the table has the following form: TBLNO, ST, SC, SN, OFF, LEN, FLAG, NODE, INC Where: TBLNO
252
is a table number that ranges from 1 to 9. You can define up to 9 different tables in your title block. For each different table number you should define
Plant Design System (PDS) ISOGEN
Mapping Attributes to the Title Block the attributes and other information that comprise the table definition. For each table number defined, one output file record is generated for each segment in the pipeline. Therefore, if you use two table numbers and a pipeline contains 10 segments, 20 records are generated in the output file. To eliminate trailing zeros from isometric attributes, create an isometric label for the appropriate attributes (temperature, pressure, etc.) then call the isometric label (instead of the table/column) from the title block mapping file. ST, SC
defines a segment column that will appear in the table. Valid values for ST are 12 and 1.
SN
is a label description library number used to define an attribute or a composite attribute that should appear in the title block table. When SN is specified as a positive value, the label description will be extracted from table 12. ST should be set to 12, and SC should be set to 0. If SN is a negative value, the Notes Table is accessed. Text is then extracted from the Notes Table based on the expanded label description defined by the absolute value of SN. ST is irrelevant. SC is the nth output filed from a Notes Table entry. For additional information, refer to Creating a Notes Table (on page 263).
OFF
is a byte offset (relative to 0) to the start of the field in the output file record. Set OFF as follows:
The minimum offset must be 11. The first 11 bytes of each output record are reserved for the table number and segment occurrence number.
Fields from different table numbers must not overlap. For example, data in table number 1 might be mapped to fields 12 through 100, while data in table number 2 might be mapped to fields 101 through 200. If you do overlap fields, the data might not be sorted properly in the title block.
Do not map any field to an offset greater than 255.
LEN
is the length of the field in the output record. The offset plus length of any field must not exceed 255.
FLAG
is a special sort flag that indicates that the field is to be considered a sort field for purposes of sorting the data prior to placing it in the title block. Set FLAG to: 1
to specify that the field should be sorted in descending order.
-1
to specify that the field should be sorted in ascending order.
When multiple fields are used for sorting the data, the most important sort field should appear in the notes table prior to the least important. NODE
is the initial text node number in the summary table for the attribute. The summary information is mapped to a matrix of text nodes in the seed isometric design file. The size of the matrix needed is not known until after the isometric is extracted. Specify here the lowest text node number for an attribute in the table.
Plant Design System (PDS) ISOGEN
253
Mapping Attributes to the Title Block INC
is the increment for the text node number. Text node numbers for each item in the attribute summary are determined by taking the base node number and adding a multiple of the increment whenever a new column (or row) of data is added.
Example 2: Define the notes table for the data summarized in Example 11.1. Assume that the seed isometric design file has been created with the following set up: Piping Spec
+10
+20
+30
+40
+50
+60
+70
+80
Design Pressure
+11
+21
+31
+41
+51
+61
+71
+81
Design Temperature
+12
+22
+32
+42
+52
+62
+72
+82
Insulation Type
+13
+23
+33
+43
+53
+63
+73
+83
Insulation Thickness
+14
+24
+34
+44
+54
+64
+72
+84
The numbers represent the text nodes that have been placed in the seed design file. Since there are only eight columns of node numbers, at most only eight segments can be summarized in the title block. If there are more than eight different segments on a sheet, some are ignored and not summarized in the title block. T1,he table needed to summarize this information would be: 1,
12,
12,
0,
11,
6,
1,
10,
10
!piping spec
1,
12,
28,
0,
17,
4,
0,
11,
10
!design pressure
1,
12,
29,
0,
21,
4,
0,
12,
10
!design temperature
1,
12,
14,
0,
25,
2,
0,
13,
10
!insulation type
1,
12,
15,
0,
27,
4,
0,
14,
10
!insulation thickness
The first entry in the table maps the piping spec to column 12 for a length of 6 bytes. The piping spec field is a sort key that alphabetizes the columns of data in the table so that they appear in alphabetical order by spec name. The beginning node number for spec is 10 and each new column of data has an increment of 10. In this example, the first spec is placed at node 10, the second at 20, the third at 30 and so on. If you put an attribute like segment npd in a table such as the one in Example 2, a typical line could generate a large number of columns or rows in the summary table. A better solution might be to use a different TBLNO for this type of attribute and summarize in a separate table on the drawing.
Example 3: Summarize the data shown in Example 2 in one table. Summarize all of the npds and line names shown on a sheet in separate tables. The following notes table would accomplish this:
254
1,
12,
12,
0,
11,
6,
1,
10,
10
!piping spec
1,
12,
28,
0,
17,
4,
0,
11,
10
!design pressure
1,
12,
29,
0,
21,
4,
0,
12,
10
!design temperature
Plant Design System (PDS) ISOGEN
Mapping Attributes to the Title Block 1,
12,
14,
0,
25,
2,
0,
13,
10
!insulation type
1,
12,
15,
0,
27,
4,
0,
14,
10
!insulation thickness
2.
12,
11,
0,
31,
6,
1,
100, 1
!npd
3,
12,
-2,
0,
37,
8,
-1,
150, 1
!line id
In this example, the fields defined in tables 2 and 3 do not overlap the fields defined in table 1. If the seed isometric design file contains only text nodes 100, 101, and 102 for npds, only the three largest sizes on the sheet are displayed. This happens because FLAG is set to 1 indicating that the npd field is a sort field.
DRAWING_DATA_TABLE You can use the Drawing Data Table to define attributes that should be placed in every drawing sheet title block. Data that you can place in every title block can originate from the first segment of the pipeline processed by the ISOGEN interface, from the largest npd segment of the pipeline, from the Notes Table, from the project control database, or it can be an internally generated attribute. An entry in the drawing data table consists of the following: SOURCE, TBL, COL, NUM, FLAG, NODE where: SOURCE
is the source of the attribute that is to be mapped to the title block. Set the value of SOURCE to one of the following:
TBL, COL
1
if the atribute is from the first segment of the pipeline.
2
if the attribute is from the largest npd segment of the pipeline.
3
if the attribute is from the Project Database.
4
if the attribute is one of the special items as defined in the description of TBL, COL that follows.
5
if the attribute is from the Notes Table accessed with attributes from the first piping segment.
6
if the attribute is from the Notes Table accessed with attributes from the largest piping segment.
defines the specific attribute that you want to map to the title block. The exact interpretation of TBL, COL depends upon SOURCE as follows: SOURCE is 1 or 2 TBL, COL is the database table, column pair of the attribute to map.
Plant Design System (PDS) ISOGEN
255
Mapping Attributes to the Title Block SOURCE is 3 TBL, COL identifies the attribute to retrieve from the Project Control Database. The following index must be used for TBL, COL. Set TBL to 1 for data from the area level of the file (that is, any data which appears in the Revise Iso Area form while in the batch iso environment). Set the value of COL as follows: COL
Data Item for TBL = 1
1
Piping area
2-21
Model design files
22
Options file
23
Seed isometric file
24
Plot request form
25
Output file directory
26
Iso design file name option
27
Drawing number option
90-99
User data 1 through 10
Set TBL to 2 for data from the drawing level of the file (that is, any data from the Revise Drawing form while in the batch iso environment). Set the value of COL as follows: COL
256
Data Item for TBL = 2
Plant Design System (PDS) ISOGEN
Mapping Attributes to the Title Block 1
Piping area
2
Primary line id
3
Secondary line id 1
4
Secondary line id 2
5
Drawing number
6
Batch reference
7
Iso file name
8
Model status code
9
Model revised date
10
Current extraction date
11
Current extraction number
12
Number of sheets from previous extraction
13
Date MTO neutral file was generated
14
Date MTO was sent for Material Control
15
Current revision number
16
Revision block Revision number
17
Revision block By initials
18
Revision block Chk initials
19
Revision block approval initials
20
Revision block issue date
21
Revision block extraction number
22
Revision block number of sheets
23
Revision block Description
65
Number of Sections
90-99
User data item 1 through 10
Set TBL to 101 for project description data (as in the project.ddl file). Set the value of COL as follows: COL
Data Item for TBL = 101
2
project number
3
project name
4
job number
5
company name
6
plant name
SOURCE is 4 Set the value of COL as follows for special items:
Plant Design System (PDS) ISOGEN
257
Mapping Attributes to the Title Block COL
Data Item for TBL = 101
1
Project Database name
2
Mto neutral file name
3
Options file name
SOURCE is 5 or 6 TBL should be 1. COL defines which value to return from an entry in the Notes Table. For more information, refer to Creating a Notes Table (on page 263). NUM
NUM functions differently depending upon SOURCE as follows: SOURCE is 1 or 2 NUM is a label library number used to define composite database attributes as an alternative to TBL, COL. When NUM is defined COL should be 0. TBL should be set to 1. The label must refer only to segment table 12. SOURCE is 3 NUM defines which revision level to return data from. NUM
Revision level for TBL=2, COL=16-23
0
Current revision
1
Revision prior to the current revision
2
Revision prior to that for NUM = 1
3
Revision prior to that for NUM = 2
4
Revision prior to that for NUM = 3
5
Revision prior to that for NUM = 4
6
Revision prior to that for NUM = 5
If the value of NUM is such that the revision that it identifies is less than 0, no output is generated. When the batch run option INCREMENT REVISION NUMBER is in effect, the current revision number is one plus the latest revision number stored in the project database Table 185 Column 17. If the option is not in effect, the current revision number is the latest revision number stored in the project database Table 185 Column 17. SOURCE is 4 NUM must be 0 SOURCE is 5 or 6 NUM is a label library label that, when expanded, becomes the input into the Notes Table. TBL must be 1. Refer to Creating a Notes Table (on page 263)for more information.
258
Plant Design System (PDS) ISOGEN
Mapping Attributes to the Title Block FLAG
When SOURCE is 1 or 2, you should set FLAG to 1 if you want to inhibit the conversion of code-listed attributes to their text-string equivalents. For other values of SOURCE, FLAG should be set to 0.
NODE
is the text node number to which the attribute should be mapped.
Example 1: 1, 12, 0, 951, 0, 5 Maps the string defined by label number 951 to text node number 5. Label 951 is expanded using attributes from the first piping segment of the pipeline. 3, 2, 91, 0, 0, 97 Maps the first user data field for a drawing to text node 97. 3, 1, 22, 0, 0, 96 Maps the defaults file stored at the area level in the Batch Data File to text node number 96. 4, 0, 3, 0, 0, 95 Maps the options file used for the current extraction to text node number 95. 6, 1, 3, 979, 0, 11 Maps the 3rd output field from a Notes Table record to text node number 11. The Notes Table record key is defined by label library label number 979, which is expanded using attributes from the largest piping segment in the pipeline.
Example 2: Mapping Values to Title Blocks It is possible to map a value that is not stored in the database to the title block of an iso using the Title Block Table, isoc.blk, in conjunction with the Notes Table, isoc.note. When entries contain a source of 5 or 6 in the DRAWING_DATA_TABLE section of the Title Block Table, isoc.blk, as shown below, the system references the Notes Table, isoc.note, for the data to use on the text node of the iso title block. Examples of a Title Block Table isoc.blk and the Notes Table, isoc.note, are shown below. Title Block Table entry: isoc.blk DRAWING_DATA_TABLE 2 5, 1, 1, 992, 0, 12 5, 1, 1, 982, 0, 15 Notes Table entries: isoc.note 1C0031 >150# CS 2C0032 >300# CS SS >Stainless Steel CS >Carbon Steel In the example above, the line containing 5, 1, 1, 992, 0, 12 uses label 992. Label 992 is defined as Table 12, Column 12 (piping_materials_class). The system reads Table 12, Column 12 and extracts the data. For instance, the extracted data might be piping_materials_class 1C0031. The system then compares 1C0031 with the Notes Table and prints the corresponding value of 150# CS on text node 12. If the piping materials class value is 2C0032, 300# CS is placed on text node 12. Likewise, the line containing 5, 1, 1, 982, 0, 15 uses label 982. Label 982 is the attribute value defined for the Materials of Construction Class. The system reads the attribute value and extracts it. For instance, the extracted data might be CS. The system then
Plant Design System (PDS) ISOGEN
259
Mapping Attributes to the Title Block compares CS with the Notes Table and prints the corresponding value, Carbon Steel, on text node 15. If the extracted data is SS, Stainless Steel is placed on text node 15. When there is no match in the Notes Table for a specific piping materials class entry, the error message 'Notes table look-up failed' is displayed in the .err file.
SHEET_DATA_TABLE You can use the Sheet Data Table to map the sheet number and number of sheets into the drawing title block and to append the sheet number to the drawing number prior to its placement in the title block. A table entry is defined as follows: SOURCE, TBL, COL, FLAG, NODE where: SOURCE
TBL, COL
is the data item source. Set the value of SOURCE as follows: SOURCE
Attribute source
0
Internally generated attribute
3
Attribute from the Project Database
identifies a data item only when SOURCE is set to 3. (Use TBL=2, COL=5 to specify the drawing number.) For each sheet in the isometric, the sheet number is appended to the data item before it is placed in the title block. If SOURCE is set to 0, TBL and COL must also be set to 0.
FLAG
identifies internally generated attributes. FLAG is also used to append the sheet number to the attribute defined by TBL, COL. Set the value of FLAG as follows: FLAG
Data item
1
Sheet number when SOURCE = 0
2
Number of sheets when SOURCE = 0
-1
Append sheet num to attribute defined by TBL, COL
-2
Append sheet num prefixed by a "-"
Sheet number and number of sheets can also be located in a title block using the MOVABLE_TEXT table in the options file. However, that method will not result in correct sheet numbers when a multi-section isometric is extracted. NODE
is the text node number to which the attribute should be attached.
Example 1: Develop the table to map sheet number and number of sheets to the title block. Show the entry needed to append the sheet number to the drawing number for each sheet. The table needed to accomplish this would be: 0, 0, 0, 1, 160 !sheet number 0, 0, 0, 2, 161 !number of sheets 3, 2, 5, -1, 200 !drawing number
260
Plant Design System (PDS) ISOGEN
Mapping Attributes to the Title Block
Plant Design System (PDS) ISOGEN
261
Mapping Attributes to the Title Block
262
Plant Design System (PDS) ISOGEN
SECTION 11
Creating a Notes Table This section describes how to create a Notes Table. A Notes Table is a user-defined table that you can use to map nondatabase attributes into an iso drawing border during batch iso extraction. The table consists of one input together with a variable number of outputs. The input to the table is either a fixed string, such as "PROJECT DATA", or is derived from segment level database attributes. During a batch run, a table input is determined by expanding a label library number that you define in the Title Block Map (refer to DRAWING_DATA_TABLE (on page 255) and SEGMENT_DATA_TABLE (on page 252) for more information). The label is used as the key or index into the notes table. The table is searched until a match is found with the key. When a match is found, one of the table outputs is mapped to a text node. You define which output is mapped to which text node in the Title Block Map.
Table Format The Notes Table is an ascii data file you create with the text editor. In the file one record or line is an entry. The number of table entries is unlimited. A single entry is limited, however, to 256 bytes or characters. The key and table outputs are separated from each other with the greater than (>) character. For more information, refer to DRAWING_DATA_TABLE (on page 255). The format of a table entry is: TBL INPUT > OUTPUT1> OUTPUT2> ... >OUTPUTn
Example 1: PROJECT DATA > PROJECT ABC> ANYWHERE, USA> REFINERY EXPANSION> 6368-20 The key for this table entry is the fixed string "PROJECT DATA". The outputs are the strings "PROJECT ABC", "ANYWHERE, USA", "REFINERY EXPANSION", and "6368-10". U50-A10> RED The input for this table entry is U50-A10 (unit 50 - area 10). The only output is the string "RED".
See Also Using the isoc.note File (on page 264)
Plant Design System (PDS) ISOGEN
263
Creating a Notes Table
Using the isoc.note File The notes file, isoc.note, in conjunction with the title block tables file, isoc.blk allows you to map a value, not stored in the database, to the title block. The files isoc.note and isoc.blk are delivered examples of a Notes file and a Title Block Tables file. Example Title Block Table entry: Example DRAWING_DATA_TABLE entry: 2 5, 1, 1, 992, 0, 12 5, 1, 1, 982, 0, 15 Example Notes Table entry: 1C0031 >150# CS 2C0032 >300# CS SS >Stainless Steel CS >Carbon Steel Entries in the DRAWING_DATA_TABLE section of the Title Block Tables file that have a source of 5 or 6 cause the software to search the Notes Table for information to output onto a text node in the iso title block. For more information, see DRAWING_DATA_TABLE (on page 255). In the previous example, line 5, 1, 1, 992, 0, 12 uses label 992 (table 12, column 12; piping material class) to define search/access criteria that will be used to search line segments in the piping model. The output of the piping model segment search is used as input to the Notes Table (see previous example). If the value returned from the search was piping material class 1C0031, it would be used as input into the Notes Table. The resulting output of piping material class 1C0031 would be 150# CS. The software would then place the output value, 150# CS, on text node 12. If the piping material class had been 2C0032, the resulting text on text node 12 would be 300# CS. Any other piping material class found as a result of the search would output an error Notes table look-up failed. This is because the input value is not in the Notes Table. The second line in the Title Block Table entry (5, 1, 1, 982, 0, 15) will write a note to text node 15 on the iso if the Materials of Construction Class attribute value stored with the line segment is SS or CS. If SS is returned from the search of the previously mentioned Title Block Table Entry, "Stainless Steel" would be placed on text node 15. If CS was returned, "Carbon Steel" would be placed on text node 15.
264
Plant Design System (PDS) ISOGEN
SECTION 12
The MTO Neutral File Record Map The MTO neutral file record map consists of a set of tables that is used to format records in the MTO neutral file. A record is generated in the MTO neutral file for each component that is MTO-able in the extracted pipeline. The neutral file record length can be either the standard 255 byte or the expanded 1024 byte depending on the setting of Intergraph option 64. The format of a record in the neutral file varies depending on the type of component that generates the record. The following record types may exist in a neutral file: Commodity item record Pipe record Engineered item record Instrument item record Pipe support record Implied bolts record Implied gasket record Implied weld record Generated item record While each of these record types can have several fields that contain the same data, each can also contain additional data that is unique to its type (for example, number of bolts in the bolt record). The neutral file map tables tell the iso extraction software which design database attributes to place in each record and where to place them. The map is composed of four tables: 1. Common data table (Table keyword is COMMON_RECORD_DATA) The common data table defines attributes that are to be placed into each record regardless of the type of the record. 2. Component data table (Keyword is COMPONENT_ATTRIBUTES) The component data table defines the attributes that are to be placed into commodity item, pipe, specialty item, instrument and support record types. 3. Implied item table (Keyword is IMPLIED_ITEMS) The implied item table defines the attributes that are to be placed into bolt, gasket and weld type records. 4. Generated item table (keyword is GENERATED_ITEMS) The generated item table defines the attributes that are to be placed into the records of items that generated through the reference database. The tables themselves are similar to options file tables in that the body of a table is preceded by a keyword that identifies the table. The keyword is followed by a number that indicates the number of table entries. One row or line constitutes a table entry. One table entry defines a neutral file record field. Each table is discussed in detail in this section.
See Also COMMON_RECORD_DATA (on page 266) COMPONENT_ATTRIBUTES (on page 269) IMPLIED_ITEMS (on page 272) GENERATED_ITEMS (on page 275)
Plant Design System (PDS) ISOGEN
265
The MTO Neutral File Record Map
COMMON_RECORD_DATA Fields defined in this table appear in every neutral file record. An entry in this table has the following form: TABLE, COL, OFFSET, LENGTH, FLAG Where: TABLE, COL
is the table, column specification for an attribute that is to be mapped into every record. When TABLE is set to 12, COL defines a segment level attribute that is to be mapped to a neutral file. Set TABLE to -1 and set COL as shown in the index below for a special data item mapped in the record.
266
TABLE
COL
Special data item mapped to the record
-1
1
component occurrence number
-1
2
segment occurrence number
-1
3
commodity code
-1
4
commodity item material description
-1
5
record type (required)- see note below
-1
6
RESERVED FOR LATER USE
-1
7
file units - see note below
-1
8
specialty item material description
-1
9
instrument item material description
-1
10
pipe support item material description
-1
11
generated item material description
-1
12
dry component center of gravity X coordinate -reported in sub-units
-1
13
dry component center of gravity Y coordinate reported in sub-units
Plant Design System (PDS) ISOGEN
The MTO Neutral File Record Map -1
14
dry component center of gravity Z coordinate reported in sub-units
-1
15
wet component center of gravity X coordinate -reported in sub-units
-1
16
wet component center of gravity Y coordinate -reported in sub-units
-1
17
wet component center of gravity Z coordinate -reported in sub-units
-1
18
model name
-1
19
area name
-1
20
partition number
Set TABLE to -2 and set COL as shown in the following index for drawing data from the project database to appear in every record. TABLE
COL
Special data item mapped to the record
-2
1
piping area
-2
2
primary line ID
-2
3
secondary line ID 1
-2
4
secondary line ID 2
-2
5
drawing number
-2
6
batch reference
-2
7
iso file name
-2
8
model status code
-2
9
model revised date
-2
10
current extraction date
-2
11
current extraction number
-2
12
number of sheets from previous extraction
Plant Design System (PDS) ISOGEN
267
The MTO Neutral File Record Map -2
13
date MTO neutral file was generated
-2
14
date MTO was sent for Material Control
-2
15
current revision number
-2
16
current revision block revision number
-2
17
current revision block By initials
-2
18
current revision block Chk initials
-2
19
current revision block Approval initials
-2
20
current revision block issue date
-2
21
current revision block extraction number
-2
22
current revision block number of sheets
-2
23
current revision block description
When TABLE is set to -2, the following restrictions apply:
This feature is for batch extraction only.
The title block table file (isoc.blk) must be provided in the options file (isoc.def). Any value to be reported must also be included in the title block file.
Intergraph option 64 should be set to 1 if any of the sums of the pair OFFSET1+LENGTH1 is larger than 256.
The data in the output MTO neutral file isoname[sht#].b[ext#] will be the same in every line of the file.
The commodity code can be mapped through this table or through the component level tables. It should be mapped here when commodity codes are size dependent.
The record type is a simple character string as follows:
Intergraph options 20 and 34 should both be set to 1 for all of these special items (mostly from project database tables 185 and 186) to be included in the MTO neutral file.
COMP PIPE ENGR INST SUPP GASK
268
for commodity items for pipe for specialty items for instruments for pipe supports for gaskets
Plant Design System (PDS) ISOGEN
The MTO Neutral File Record Map BOLT for bolts WELD for welds GENR for generated items
File units is a simple character string as follows: ENGL for English units MIX for mixed units METR for all Metric units
Can also use COL=-2 to obtain the line ID rather than the line name. Generated items consist of chain wheel operators and items implied through the reference database.
OFFSET
Is the offset (relative to 0) in the record for the start of the field.
LENGTH
Is the length of the data item‘s field. The sum of offset + length must not exceed the length of the output record (255 characters).
FLAG
Is a special flag that is normally 0 but is set to 1 to inhibit conversion of code-listed attributes to their ASCII string equivalents. When FLAG is set to 1, the code-list number will be placed in the record.
Example: 12, 12, 14, 6, 0
maps the piping materials class into EVERY MTO neutral file record starting at output field 15 (offset 14) for 6 bytes.
12, -2, 4, 10, 0
maps the line id (defined in the defaults file) into EVERY MTO record starting at output field 5 for 10 bytes.
-1, 1, 20, 8, 0
maps the component database occurrence number into EVERY record starting at output field 21 for 8 bytes. Note that for implied materials this is the occurrence number of the GENERATING component.
-1, 5, 0, 4, 0
maps the record type of each record into output field 1 for 4 bytes.
COMPONENT_ATTRIBUTES Fields defined by this table appear in component, specialty item, pipe, instrument and pipe support records. An entry in the table has the following form: CT, CC, ET, EC, PT, PC, IT, IC, ST, SC, CPI, OFFSET, LENGTH, FLAG CT, CC
defines a table, column specification for the case when the current item that is generating a neutral file record is a component. Valid values for CT are 0, 12 and 34.
ET, EC
defines a table, column specification for the case when the current item is a specialty item. Valid values for ET are 0, 12 and 34..
PT, PC
defines a table, column specification for the case when the current item is a pipe. Valid values for PT are 0, 12, and 50..
IT, IC
defines a table, column specification for the case when the current item is an instrument. Valid values for IT are 0, 12, 67..
Plant Design System (PDS) ISOGEN
269
The MTO Neutral File Record Map ST, SC
defines a table, column specification for the case when the current item is a pipe support. Valid values for ST are 0, 12, and 80. When the MTO neutral file record is being generated for an item then its type is determined and one of the entity, attribute pairs above is chosen for purposes of fetching an attribute from the database. Not all pairs in the above set need to be defined. If a component data table entry should apply only to one type of item, set the entity, attribute pairs for other types to zeroes.
CPI
is a connect point identifier. It is used to access connect point attributes by connect point color (green or red) rather than by attribute number for the COMPONENT_ATTRIBUTES table. CPI is also used by the IMPLIED_ITEMS table when set to 1 to indicate that the attribute will be retrieved from the connect point of the item generating the implied material. When set to 1, CPI is used by the IMPLIED_ITEMS table to indicate that the attribute will be retrieved from the connect point of the item generating the implied material. When CPI is set (nonzero), CT, ET, PT, IT, and ST should be set to zero and CC, EC, PC, and IC should be set to one of the values shown in the following index.
270
CPI
Means
1
retrieve a green connect point property
2
retrieve a red connect point property
Index
Connect Point Attributes
1
nominal piping diameter
2
outside diameter
3
end preparation
4
schedule/thickness
5
pressure rating
6
stress analysis node number
7
face to center distance
8
weld number
9
weld type
Plant Design System (PDS) ISOGEN
The MTO Neutral File Record Map 10
gasket gap
11
stress intensification factor
12
head loss factor
13
inspection number
OFFSET
is the offset into the neutral file record to the start of the field.
LENGTH
is the length, in bytes, of the field.
FLAG
is a special flag that is normally 0 but is set to 1 to inhibit conversion of code-listed attributes to their ASCII string equivalents. When FLAG is set to 1, the code-list number will be placed in the record.
If lap joint flanges are mapped to ISOGEN record number 106 to generate both the stub and flange in the ISOGEN material list, a separate record generated is in the MTO neutral file for the stub as well (refer to the section The PDS-to-ISOGEN Symbol Map (on page 277).) The MTO record for the stub is generated by overlaying attributes from the reference database entry for the stub onto the database record for the flange and then applying the COMPONENT_ATTRIBUTES table to this temporary occurrence.
Example 1: 34, 3, 34, 3, 50, 3, 67, 3, 80, 4, 0, 53, 6, 0 This table entry maps the item name attribute for all component types into the neutral file record starting at column 53 for 6 bytes. 34, 4, 0, 0, 50, 4, 0, 0, 0, 0, 0, 60, 6, 0 This table entry maps the new item name attribute for component types of COMPONENT and PIPE. Nothing is generated in the record for SPECIALTY ITEMS, INSTRUMENTS or PIPE SUPPORTS by this table entry. 0, 1, 0, 1, 0, 1, 0, 1, 0, 0, 1, 66, 8, 0 This table entry maps the GREEN nominal pipe size (also referred to as size 1) into the neutral file record. Since pipe supports do not have connect point properties, no number is specified for them in the entry. 0, 1, 0, 1, 0, 1, 0, 1, 0, 0, 2, 74, 8, 0 This table entry maps the RED nominal pipe size (also referred to as size 2) into the neutral file record. 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 1, 94, 6, 0 This table entry maps the GREEN schedule (schedule 1) into the neutral file record. 12, 14, 12, 14, 12, 14, 12, 14, 0, 0, 0, 118, 2, 0 This table entry maps the insulation purpose attribute from the segment into the neutral file record for all items except pipe supports. 12, 27, 12, 27, 12, 27, 12, 27, 0, 0, 0, 126, 2, 1 This entry maps the paint code CODE-LIST VALUE from the segment into the MTO neutral file record. The code-list value is put in the record rather than the attribute itself because FLAG is set to 1 and the attribute being mapped is code-listed.
Plant Design System (PDS) ISOGEN
271
The MTO Neutral File Record Map Example 2: The following is an example of how to set the COMPONENT_ATTRIBUTES to extract item inspection number and inspection numbers for item connect point one. 34, 121, 34, 121, 50, 59, 67, 128, 80, 38, 0, 96, 4, 0 !item insp key 34, 122, 34, 122, 50, 60, 67, 129, 0, 0, 0, 100, 4, 0 !cp1 insp key
IMPLIED_ITEMS Fields defined in this table appear in neutral file records for bolts, gaskets and welds. The implied items table provides a means to map attributes that are: from the component that caused the item to be generated (for example: flange pressure rating) from the spec entry for the implied item (for example: for the commodity code) from data calculated when the item is generated (for example: bolt length) An entry in this table has the following form: TYPE, CT, CC, PT, PC, IT, IC, ST, SC, CPF, ITEM, OFFSET, LENGTH, FLAG TYPE
defines the type of implied component that the table entry is to apply to. TYPE
TABLE ENTRY APPLIES TO
1
Gaskets only
2
Bolts only
3
Welds only
4
All of the above items
CT, CC
defines a table, column specification from a generating component that is to be mapped when the generating component is a COMPONENT or SPECIALTY ITEM. Valid values for CT are 0, 12 and 34..
PT, PC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE. Valid values for PT are 0, 12 and 50..
IT, IC
defines a table, column specification from a generating component that is to be mapped when the generating component is an instrument. Valid values for IT are 0, 12 and 67..
ST, SC
defines a table, column specification that is to be mapped when the attribute is taken from the reference database entry for the implied item. The only valid values for ST are 202 and 0..
CPF
the attribute will be retrieved from the connect point of the item generating the implied material. When set other than zero, CT, PT and IT should be set to 0. CC, PC and IC should be set to one of the values shown in the following Connect Point Attributes index.. Index
272
Connect Point Attributes
Plant Design System (PDS) ISOGEN
The MTO Neutral File Record Map
ITEM
1
nominal piping diameter
2
outside diameter
3
end preparation
4
schedule/thickness
5
pressure rating
6
stress analysis node number
7
face to center distance/pipe length
8
weld number
9
weld type
10
gasket gap
11
stress intensification factor
12
head loss factor
13
inspection number
When this value is other than zero, it indicates that either the attribute to be mapped is data that was generated along with the implied item, or the attribute is to be obtained from the spec. Values for item are dependent on the implied item type as shown below. Item Type
ITEM
Description
ALL
-1
Use ST,SC to obtain the attribute from the spec database
BOLT
1
Number of bolts
2
Bolt length in Project Units English for English Project Metric for Metric or Mixed Project
3
Bolt diameter English for English Project Metric for Metric or Mixed Project
4
Number of nuts
5
Bolt diameter in English Units
6
Bolt length in English Units
7
Bolt weight in English Units (pounds)
8
Bolt weight in English Units (kilograms)
9
Bolt diameter in Metric Unit (mm)
10
Bolt length in Metric Unit (mm)
GASKET WELD
0 1
Plant Design System (PDS) ISOGEN
Weld ID number
273
The MTO Neutral File Record Map 2
Weld Type
3
Material A
4
Material B
OFFSET
is the offset into the neutral file record to the start of the field.
LENGTH
is the length, in bytes, of the field.
FLAG
is a special flag used to inhibit the conversion of code-listed attributes to the ASCII string equivalents.
You cannot map attributes for a weld from the reference database into the neutral file record. However, you can use a component TYPE of 4 (for ALL implied items) when mapping attributes from the spec for bolts and gaskets. In the case of a weld the field will be left blank. Two welds may be generated on olet-like components. The first weld, which corresponds to the weld that attaches the olet to the header, is given the size from the header pipe as a safe estimate of the weld size. The second weld, which corresponds to the point where the branch pipe attaches to the olet, is given the branch pipe size. No welds are generated at branch welds. Branch welds are defined as those components that are mapped to the ISOGEN symbol TESO. The reason for this is that the component itself represents a weld and it is generated in the neutral file. One weld is generated at a reinforcing pad. The weld represents the attachment of the pad to the header pipe. The reinforcing pad component represents the attachment of the branch pipe to the header.
Example: This table entry maps the gasket size into the neutral file record starting at output field 67 for 8 bytes. 1, 0, 1, 0, 1, 0, 1, 0, 0, 1, 0, 66, 8, 0 This table entry maps the item name from the reference database for a bolt into the neutral file record. 2, 0, 0, 0, 0, 0, 0, 202, 3, 0, -1, 53, 6, 0 This table entry maps the bolt length into the neutral file record. 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 127, 8, 0 This table entry maps the inspection number for welds, bolts and gaskets into the MTO neutral file record. 4, 0, 13, 0, 13, 0, 13, 0, 0, 1, 0, 51, 4, 0
274
Plant Design System (PDS) ISOGEN
The MTO Neutral File Record Map
GENERATED_ITEMS Fields defined in this table appear in neutral file records for items generated through the reference database and for chain wheel operators. The generated items table provides a means to map attributes that are: from the component that caused the item to be generated from the reference database entry for the implied item (for example: for the commodity code) An entry in this table has the following form: CT, CC, ET, EC, PT, PC, IT, IC, ST, SC, CPI, ITEM, OFFSET, LENGTH, FLAG Where: CT, CC
defines a table, column specification from a generating component that is to be mapped when the generating component is a COMPONENT. Valid values for CT are 0, 12 and 34.
ET, EC
defines a table, column specification from a generating component that is to be mapped when the generating component is a SPECIALTY ITEM. Valid values for ET are 0, 12 and 34.
PT, PC
defines a table, column specification from a generating component that is to be mapped when the generating component is a PIPE. Valid values for PT are 0, 12 and 50..
IT, IC
defines a table, column specification from a generating component that is to be mapped when the generating component is an instrument. Valid values for IT are 0, 12 and 67..
ST, SC
defines a table, column specification from a generating component that is to be mapped when the generating component is a pipe support. Valid values for ST are 0, 12 and 80.
CPI
the attribute will be retrieved from the connect point of the item generating the implied material. When set other than zero, CT, PT and IT should be set to 0. CC, PC and IC should be set to one of the values shown in the following Connect Point Attributes index..
CPI
Means
1
retrieve a green connect point property
2
retrieve a red connect point property
Index
Connect Point Attributes
Plant Design System (PDS) ISOGEN
275
The MTO Neutral File Record Map
ITEM
1
nominal piping diameter
2
outside diameter
3
end preparation
4
schedule thickness
5
pressure rating
6
stress analysis node number
7
face to center distance/pipe length
8
weld number
9
weld type
10
gasket gap
11
stress intensification factor
12
head loss factor
13
inspection number
When this value is set to 1 it indicates that the attribute to be mapped is data from the reference database. The value for CC, EC, PC, IC, and SC should be set according to the table shown below when ITEM is set to 1.
Attr.
Description
1
Generated item commodity code
2
Generated item quantity
OFFSET
is the offset into the neutral file record to the start of the field.
LENGTH
is the length, in bytes, of the field.
FLAG
is a special flag used to inhibit the conversion of code-listed attributes to the ASCII string equivalents.
Example: 34, 3, 34, 3, 50, 3, 67, 3, 80, 4, 0, 0, 53, 6, 0 This entry maps the item name of the component that generates some implied material into the MTO neutral file record at offset 53 for 6 bytes. 0, 2, 0, 2, 0, 2, 0, 2, 0, 2, 0, 2, 75, 8, 0 This entry maps the generated item quantity into the MTO neutral file record at offset 75 for 8 bytes. In the case of a chain wheel operator, this entry corresponds to the length of chain.
276
Plant Design System (PDS) ISOGEN
SECTION 13
The PDS-to-ISOGEN Symbol Map You can use the PDS-to-ISOGEN symbol map table to tell the ISOGEN interface software which ISOGEN graphics symbol to use for a specific PDS component when it generates the Isometric drawing. The table is composed of 9 columns of data that are position-dependent (that is, the data must appear in specific columns in the table). You can add comments to the table by placing an exclamation point (!) in column 1. A table entry consists of one row of data. The format for a table entry is as follows: PDS Item name (see "The PDS Item Name" on page 278):
Columns 2-7, left justified
ISOGEN symbol name (see "The ISOGEN Symbol Name" on page 278):
Columns 9-12, left justified
ISOGEN record number (see "The ISOGEN Record Number" on page 279):
Columns 14-16, right justified
Number of connect points (on page 279):
Columns 18-19, right justified
Tap name (see "Tapped Component Record Number" on Columns 21-24, left justified page 280): Tap record number (see "Tapped elbows" on page 279): Columns 26-28, right justified PDS operator name (see "PDS Valve Operator Name" on Columns 30-35, left justified page 280): end prep low (see "End Prep Low and End Prep High" on Columns 37-40, right justified page 281): end prep high (see "End Prep Low and End Prep High" on page 281):
Columns 42-45, right justified
See Also The PDS Item Name (on page 278) The ISOGEN Symbol Name (on page 278) The ISOGEN Record Name (see "The ISOGEN Record Number" on page 279) Number of Connect Points (on page 279) Tapped Component Name (on page 279) Tapped Component Record Number (on page 280) PDS Valve Operator Name (on page 280) End Prep Low and End Prep High (on page 281) Order of Table Entries (on page 281)
Plant Design System (PDS) ISOGEN
277
The PDS-to-ISOGEN Symbol Map
The PDS Item Name The PDS item name is the primary index into the table. Each PDS item that exists in a pipeline must have an entry for it in this table. As each component is processed, the table is searched for a corresponding table entry or entries.
The ISOGEN Symbol Name The ISOGEN symbol name is the primary output from the symbol map table. All of the ISOGEN symbols available with ISOGEN are shown in Appendix B. Look especially at the notes at the end of the appendix. The symbol names are generally four characters in length. The first two characters identify the type of symbol and the last two identify the end preparation. For many symbols, the end prep characters are double asterisks (**). The ** indicate that the symbol may end in one of the following sets of characters: BW FL SC SW CP PL -
indicating buttweld ends indicating flanged ends indicating threaded ends indicating socket weld ends indicating compression ends indicating plain ends
You can carry the variable end prep notation into the symbol map by substituting the characters XX for the characters **. For example, the ISOGEN symbol name for a ball valve is BV** and the table entry would be BVXX. When a line is extracted, the XX is converted to one of the end prep codes shown above based on the end prep of the component in the model. When you map a PDS component to an ISOGEN component, you must be sure that the connect point skeletons (that is, configuration or geometrical arrangement of the connect points) are the same. You cannot, for example, map a gate valve (whose connect points lie on a straight line) to an elbow (whose connect points define a 90-degree change-of-direction). The basic connect point skeletons handled by ISOGEN are: end point component (plug, blind flange) straight-through component (gate valve, flange) offset component (eccentric reducer) return component (u bend) change-of-direction component (elbow, angle valve) single branch component (tee, olet, 3-way valve) double branch component (cross, 4-way valve)
278
The change-of-direction components for elbows are not restricted to 90-degree changes of direction. Other change-of-direction components, such as 2-way valves, are restricted. The tee components TESO and TEXX can have variable angle changes of direction. Other branch components, such as 3-way valves, must have 90-degree changes in direction.
Plant Design System (PDS) ISOGEN
The PDS-to-ISOGEN Symbol Map
The ISOGEN Record Number Another primary output from the symbol map table is the ISOGEN record number. It is critical that the ISOGEN record match the component type identified by the symbol name. ISOGEN record numbers are defined in Appendix B. The symbols in Appendix B are grouped by component type. The component type is identified at the top of the first page of each group of symbols. For example, a CV** is an instrument while a VG** is a valve. Appendix B, Record Identification Numbers, shows that the record number for an instrument In Leg is 90. The record number for a valve is 130. The PDS symbol for a lap joint flange represents two components: the flange ring and the stub. You can generate either one or two components in the isometric when you extract the line. If the ISOGEN record number for the lap joint is set to 105, only one component (one entry in the BOM) is generated. If the ISOGEN record number is set to 106, the ISOGEN interface automatically generates a component representing the stub. In this case, you must have an entry in the reference database for the stub. The spec access data for the stub is identical to that for the flange except that the option code is that of the flange plus 5000.
Number of Connect Points Another table output is the number of connect points for the component. This number does not include taps that the symbol may have. It is used both for identifying closure components (plugs, caps, blinds) and for processing tapped components. It is most important that this number be correct for components that may be tapped. The number of connect points is also used to distinguish tee type components (which have three connect points) from branch weld type components (which have two connect points). The number of connect points must be correct for these types of components. Incorrect values will cause incorrect entries in the bill-of-material and/or cut pipe report.
Tapped Component Name The tapped component name is used in special situations. When it is used, the ISOGEN symbol key is taken from this field, rather than the ISOGEN symbol key field.
See Also Tapped elbows (on page 279) Olets attached to fittings (on page 280)
Tapped elbows An elbow is one of the components that ISOGEN considers special. Because it is special, you may not redefine it to add tap points as you can with most other symbols. This results in the need for special handling of tapped elbows. Symbol keys exist for elbows that have a single tap (see Appendix B). For an elbow that is tapped in the model, the symbol key that is passed to ISOGEN is taken from the tapped component name field of the table. Since there are no symbol keys for elbows with more than one tap, you will not be able to extract a doubly tapped elbow.
Plant Design System (PDS) ISOGEN
279
The PDS-to-ISOGEN Symbol Map
Olets attached to fittings Normally, olet type components are used as branch or tee-type components. However, sometimes an olet is attached to a fitting such as a reducer. ISOGEN does not allow the normal olet type fittings to be used in this case and so you must match an olet attached to a component to a different symbol (you must use one of the coupling components). In this situation, connect point 1 of the olet will be attached to a tap. Whenever an olet is found to be connected to a tap, then the symbol key that is passed to ISOGEN is taken from the tapped component name field (rather than the ISOGEN symbol name field).
Tapped Component Record Number The tapped component record number corresponds to the tapped component name just as the ISOGEN record number corresponds to the ISOGEN symbol name. For a tapped elbow, the record number changes from 35 to 70. For the olet attached to a component, the record number changes from 40 to 126. Example 1: Show the required ISOGEN table entries needed to map socket weld GAT valves to the ISOGEN symbol VTSW, flanged GAT valves with the operator OP_100 to the symbol VTFL and all other GAT valves to the symbol VV**.
PDS Name
ISG Name
ISG Rec
NO CP
GAT
VTFL
130
2
GAT
VTSW
130
2
GAT
VVXX
130
2
TAP Name
TAP Rec
PDS Order
End Low
End High
OP_100
1
199
400
429
The table entries must be defined in the same order as shown above.
PDS Valve Operator Name The PDS valve operator name is an optional table input. This input is used when it is defined in the model and when it is defined in this table. When a component has a valve operator, the valve operator name from the model is compared to the valve operator name in the table (if it is defined). If they are the same, the table entry is checked further. If they are not the same, the table entry is rejected. If the valve operator is not defined in the table, then it is not considered in the table lookup.
280
Plant Design System (PDS) ISOGEN
The PDS-to-ISOGEN Symbol Map
End Prep Low and End Prep High The end prep low and end prep high table entries define an end prep range, a range of end preparation values, which makes component end prep an optional table input. If the end prep range is defined, the component's end prep is checked to see whether or not it falls within the range defined by end prep low and high. If it does fall within the range, a match has occurred and the table entry is accepted. If it does not, the table entry is rejected. If no range is defined, the components end prep is not considered in the table lookup.
Order of Table Entries Due to the manner in which the table lookup is performed, it is necessary to put the most restrictive table entries prior to the least restrictive. Entries should be in the following order in the table: 1. Entries with PDS name, operator name and end prep range. 2. Entries with PDS name and either valve operator name or end prep range. 3. Entries with only PDS name and neither valve operator or end prep range. When table entries are placed in the above order, the software can choose the proper table entry, for each case.
Plant Design System (PDS) ISOGEN
281
The PDS-to-ISOGEN Symbol Map
282
Plant Design System (PDS) ISOGEN
SECTION 14
The Valve / Operator Table The valve / operator table is used to map a PDS valve and valve operator to an ISOGEN symbol different from the one mapped by the valve item name alone. This enables you to take better advantage of the variety of valve symbols that are defined within ISOGEN. It also gives you more flexibility in how you map PDS symbols to user-defined ISOGEN symbols. A valve / operator table is an ASCII file created with the editor. The format of the table is as follows: m,n 'VALV1', 'VALV2', ... 'VALVn', 'OPER1', 'SYM11', 'SYM12', ... 'SYM1n', 'OPER2', 'SYM12', 'SYM22', ... 'SYM2n', . . . . . . . . . . . . 'OPERm', 'SYMm1', 'SYMm2', 'SYMmn' Where: m-
is the number of rows in the table or the number of operators.
n-
is the number of columns in the table or the number of valves.
'VALVp'-
is the pth column heading in the table where p is less than or equal to n.
‘OPERq‘-
is the qth row heading in the table where q is less than or equal to m.
‘SYMpq‘-
is the table entry corresponding to VALVp and OPERq.
Example 1: Develop an example valve / operator table. 4, 2 'GATR', 'GAT', 'OP_3', 'VTXX', 'VVXX', 'OP_5', 'VKXX', 'VDXX', 'OP_9', 'VSXX', 'VNXX', 'OP_11', 'VGXX', 'VPXX'
You do not need to define every table entry with a value for SYMpq. If VALVp and OPERq should not map to a new symbol, make the table entry a blank (''). Every entry in the table, except for m and n, must be surrounded by single quotes and separated by commas. Otherwise, an error will occur when the table is read in. Each valve defined in the VALOPR table must still be defined in the PDS to ISOGEN symbol map. When a valve and operator map to a new symbol in the VALOPR table, the new symbol must have the same ISOGEN record number as the one defined for the valve in the PDS-to-ISOGEN symbol map. For example, you can map a PDS symbol named GLOR to an ISOGEN symbol named VVXX with an ISOGEN record number of 130. However, you cannot map the GLOR with an operator
Plant Design System (PDS) ISOGEN
283
The Valve / Operator Table
284
symbol of OP_3 to the ISOGEN symbol CVXX, because CVXX is an instrument with an ISOGEN record number of 90. Intergraph option 31 must be enabled in order for the VALOPR table to be accessed. The capability provided by this table is similar to that provided through the PDS to ISOGEN symbol map. If you are mapping valves and valve operators to ISOcan notGEN symbols, then using the VALOPR table is much more efficient than having multiple records in the PDS to ISOGEN symbol map. If, however, you are utilizing the end prep range in the symbol map, you should also use the PDS operator name which is input in the symbol map to map valves and valve operators. The reason for this is that references to the VALOPR table overlay references to the PDS to ISOGEN symbol map. That is, VALOPR table access occurs subsequent to the lookup in the PDS to ISOGEN symbol map.
Plant Design System (PDS) ISOGEN
SECTION 15
Repeatability ISOGEN's Repeatability facility allows isometric drawings to be re-extracted. When a drawing is re-extracted, its repeating data is recalled for purposes of extracting the isometric after modifications have been made in the piping model. Repeating data includes: The Iso's Traversal Start point - (saved to the project database) The Extracted Item's Iso Sheet Number - (saved to the design database) The extracted Item's Piecemark Number Repeatability can be enabled and disabled via the Schedule Batch Job (on page 117) form.
See Also Repeatability - Related Information (on page 285) Repeatability Restrictions (see "Repeatability Restrictions and Limitations" on page 285) Extraction Information in the Database (on page 286) Determining the Traversal Start Point (on page 287) Determining Sheet Split Points (on page 288) Determining Spool Split Points (on page 288)
Repeatability - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when using the repeatability feature. Related ISOGEN Options (Appendix B) 38, 108, 109 Related Intergraph Options (Section 7) 4, 68 Related Options File Material (Section 7) NONE Related ISOGEN ATEXT Records (Appendix B) NONE
Repeatability Restrictions and Limitations The following is a list of restrictions, limitations and rules that must be followed to ensure success when using the repeatability facility. Since there is only one place in the piping design file for sheet and spool numbers, repeatability will only be supported for one type of isometric. Split points placed in piping will be ignored during re-extraction. Implied items are not saved in the database and have no record kept that identifies the sheet to which they apply. Therefore, implied items will always be re-extracted on the same sheet as the item which implied them. The ISOGEN software will decide if a sheet will break at a flange. All bolts and gaskets for the flange will be on the same sheet as the flange.
Plant Design System (PDS) ISOGEN
285
Repeatability
The repeatability facility should not be used if the design is not stable or if extensive changes are being made to a pipeline. If extensive revisions are made to a line and repeatability is used, the result may be a sheet that contains too much information to decipher. If this situation occurs, it may be necessary to disable repeatability and extract the drawing normally so that it can be repaginated. Commands that maintain the old database record are preferred during piping design after the option to use repeating isometrics has been used. Delete Component deletes the database record, and there is no way of knowing the sheet to which it belongs. This is especially true if the item prior to it is on sheet 1, and the item after it is on sheet 2. If you plan on re-extracting an isometric drawing, it must first be extracted with ISOGEN option 108 set to 1 or 2. Once set, this option will not allow pipe splits. When a line is re-extracted, items with a sheet number of 0 will be placed on the same sheet as the item just prior to it. When a line is re-extracted, items that were added before the previous traversal start point will be placed on sheet one. It will not be possible for a multi-sheet iso to contain only disconnected pipelines. For example, if sheet 1 has two notes CONT ON DRG 2, drawing 2 will connect these ends. If an entire sheet is deleted, the sheet numbering will be incorrect when re-extracting a drawing. For example, the initial extraction generates three sheets. A redesign is done and the second sheet is deleted. When this line is re-extracted, it will produce two sheets since blank sheets cannot be output. New spool numbers will not be generated when additional piping is added to the drawing. Since new spool numbers are not identified by ISOGEN, the spool number in the design database will not be updated when extracting with existing sheets.
Extraction Information in the Database Extraction information, depending on its classification, is written to either the project or design database.
See Also Extraction Information in the Project Database (on page 286) Extraction Information in the Design Database (on page 287)
Extraction Information in the Project Database Re-extraction information saved to the project database includes the original start traversal point, section number, entity, component occurrence and segment occurrence numbers. The project database table pdtable_189 contains re-extraction information. The following is the format for the table, pdtable_189. # Isometric Drawing Re-Extraction Data table number = 189 , number of columns = 8 1 , drawing_indx_no , integer 2 , section_no , short 3 , start_traversal_X , integer 4 , start_traversal_Y , integer 5 , start_traversal_Z , integer 6 , start_entity , short 7 , start_comp_occ, integer 8 , start_seg_occ , integer
286
Plant Design System (PDS) ISOGEN
Repeatability
Extraction Information in the Design Database When the repeatability is used and the option Save Sheet Extraction Data has been set, existing columns in the design database will be updated in tables 34, 50, 67, and 80. These columns include: iso_dwg_index_no , integer isometric_sheet_no , character(2) piece_mark_no , character(10) Where: iso_drawing_index_no
will be the number in table 185 column 1 of the project database.
isometric_sheet_number
will be the number of the sheet on which the item appears.
piece_mark_no
will be the number of the spool on which the item appears.
When a component belongs to a spool that starts on a different sheet, the piece_mark_no value is reported as a three digit number in the format: xyy. Where x is the iso sheet number on which the spool starts and yy is the component's spool number (on the x sheet). Only shop items can receive piece mark numbers. All field items are assigned a piece_mark_no of 0.
Determining the Traversal Start Point When using the repeatability function, the ISOGEN software will determine the traversal start point for the extraction. In order of highest priority, the following is a list of rules for determining a traversal point. 1. Compare the start_entity and start_comp_occ with each item that has been determined to be an end point. If a match occurs, use this as the start point. End point marked as -1, or -2 for a cap, is a valid start point. End points marked as -3 for pipe support are not considered as a valid start point. Refer to Section 4: Design File Data Sorted by Topo (see "Section 4: Design File Data Sorted by Topo - PD_ISO" on page 131) for more information. 2. The original start component is not an endpoint. Compare the start_seg_occ with each item that has been determined to be an end point. If one end matches, use this end point as start point. If two ends match, pick the end that is the closest to the last traversal start point. 3. The original start component and segment occurrence are not considered endpoints. The last start point component exists, but it is no longer an end point. Choose the end point that is closest to the original start component.
Intergraph option switch 68 can be used to stop the extraction process if the original start item cannot be used. The ISOGEN software will generate informational-type messages that show the decision process that lead to selecting a traversal start point.
Plant Design System (PDS) ISOGEN
287
Repeatability
Determining Sheet Split Points A sheet split location is determined by comparing the current isometric_sheet_no (sheet number) with the previous item sheet number (excluding sheet 0). Split point location is saved and output after the .idf file has completed and all split locations have been determined. Sheet split locations will be determined using the following rules: Sheet numbers that are 0 will not be considered for sheet split records. Unless otherwise stated, they will not be considered as a sheet change. When a component is processed and that component has a sheet number different from previously processed components, a sheet split record is created. Until a new sheet number is read, all processed components will be output to that sheet.
An informational-type message will be output if the previous item's sheet number was set to 0 and the current sheet number is a new sheet. This reminds you to verify that all items were put on the correct sheet. The message will include the occurrence number of the item with sheet set to 0. A message to be used by the piping software is output in the MTO format. Error and Warning messages concerning sheet splits are output to the end of idf generation.
Correcting Incorrect Splits If an item has a 0 in the isometric_sheet_no column of the database, it is treated as either an additional item or the previous item was deleted and replaced with a new item. In this situation, a general rule has been established: Items whose sheet number is set to 0 will be output on the previous item's sheet. Such that, when a starting item has its sheet number set to zero, the item would appear on sheet number 1. If necessary, this situation can be corrected by setting the isometric_sheet_no of the appropriate item to the correct sheet number in the design database. If more than one item in a series of items have sheet numbers set to 0, find the item that should start the new sheet and change the isometric_sheet_no to the correct number.
Determining Spool Split Points Like sheet split points, a spool split location is identified by comparing current piece_mark_no (spool number) with previous item's spool number (excluding spool number 0). Location of the split between spools will be saved and output after the .idf file has been generated and all split locations have been determined. Items with spool number 0 will be placed on the current spool being processed. The spool split locations are determined using the following rules: Sheet numbers that are 0 are not considered for sheet split records. Unless otherwise stated, they are not considered as a sheet change. When a component is processed and has a sheet number different from previously processed components, a sheet split record is created. Until a new sheet number is read, all components processed will be output to that sheet. An informational-type message will be output if the previous item's spool number was set to Blank and the current spool number is a new spool. This reminds you to verify that all items were put on the correct spool. The message will include the occurrence number of the item with spool set to 0. A message to be used by the piping software is output in the MTO format.
288
Plant Design System (PDS) ISOGEN
SECTION 16
Welds The following is a list of weld features available in the ISOGEN software: Delivered weld symbols Dotted weld symbols User-defined weld symbols Codelist values for standard notes 180 and 1100 Weld type and mapping Offshore fabrication category Unique weld numbering User-defined weld prefix User-defined weld summary report Welds listed in the bill of materials
A weld type defined as codelist value 2 will be interpreted as a no weld connection. This can be used when a weld is not wanted on match lines or pipe and pipe bends. All PDS applications recognize codelist value of 2 (from codelist 1100: weld type) as a no weld connection. For pipe bends, change skey PB to PBBW designates to the ISOGEN software that the connection is a butt weld. ISOGEN will automatically place a shop weld symbol at the connection and include the correct data in the cut list. The delivered map file will not change (set to PB by default).
See Also Weld Enhancements - Related Information (on page 290) Delivered Weld Symbols (on page 290) Dotted Weld Symbols (on page 291) User-defined Weld Symbols (on page 291) Codelist Values for Standard Note 180 and 1100 (on page 291) Weld Types and Mapping (on page 292) Offshore Fabrication Category (on page 292) Unique Weld Numbering (on page 292) User-defined Weld Prefix (on page 293) The Weld Summary Report (on page 293) Welds Listed in the Bill of Materials (on page 297)
Plant Design System (PDS) ISOGEN
289
Welds
Weld Enhancements - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when creating a Weld Enhancement. Related ISOGEN Options (Appendix ) 22, 53, 54, 74, 75 Related Intergraph Options (Section 7) 62, 69 Also: The twelfth entry in the FILES Section of the Options File: Weld Definition Report Format File (WDF) (See Chapter 8) Related Options File Material (Section 7) USER_DEFINED_WELDS OFFSHORE_FABCAT_CODE_LIST_VALUES WELD_PREFIX Related ISOGEN ATEXT Records (Appendix ) -414, -415, -416, -417, -418, -419, -421, -422, -423, -457
Delivered weld symbols SKEYs for Existing Weld Types
290
Description
SKEY
Field Fit
WF (Can add extra length to pipe)
Weld Mitre
WM
Weld Mitre field fit
WMF
Offshore Weld
WO
Offshore Weld Field Fit
WOF
Workshop
WW
Site
WS
Erection Weld Connection
XX (Where XX would be for fitting with SW, SC, CP)
Plant Design System (PDS) ISOGEN
Welds
Dotted Weld Symbols Dotted weld symbols cannot be redefined, and are intended for internal program use only. They are automatically selected when the need for a dotted weld is detected by the ISOGEN software. Dotted welds should be used when: a dotted pipeline continuation situations occurs dealing with a pipeline that has a special status of dotted open ends of a pipeline terminate with a welded end New Dotted SKEYs for Weld Symbols Description
SKEY
Workshop
WWD
Site
WSD
Field Fit
WFD
Weld Mitre
WMD
Weld Mitre
WMFD
Offshore Weld
WOD
Offshore Weld Field Fit
WOFD
Erection Weld Connection on fittings with SW, SC, XXD CP
User-defined Weld Symbols The following is a list of guidelines that must be followed when creating a new weld symbol. Mitre welds cannot be redefined. All other weld symbols can be user-created. New weld symbols can be generated just as any other user-defined symbol with the Isometric Symbol Editor, located under the Utilities option. Refer to Entering the Iso Symbol Editor Environment (on page 97) for more information.
Codelist Values for Standard Note 180 and 1100 When the ISOGEN software is used to segregate offshore welds and identify mitre welds, standard note tables 180 and 1100 should be revised to accommodate this functionality. Changes to these tables will allow you to define which items will be in the offshore category of the bill of materials. Making revisions to standard notes 180 and 1100 will also allow different graphics symbologies of weld connections (offshore, mitre.). For more information, see Weld Types and Mapping (on page 292).
Plant Design System (PDS) ISOGEN
291
Welds
Weld Types and Mapping To define a weld type (shop, field, offshore) and weld symbology, revise the options file table USER_DEFINED_WELDS. This allows you to create a weld symbol and identify those weld-type codelist numbers (CL 1000) that will have a different weld symbol on the isometric drawing. It is also possible to map the weld symbol (existing or user-defined) to the appropriate weld-type codelist number by revising the USER_DEFINED_WELDS section. For more information, see USER_DEFINED_WELDS (on page 188).
When the USER_DEFINED_WELDS section is not added to the options file, the following are true: Shop welds (WW SKEY) and field fit welds (WF SKEY) are the only available types of welds. Shop welds are given fabrication codelist value numbers 11 through 20 inclusive. No Weld is given fabrication codelist value 1. Field fit welds are given all other fabrication codelist value numbers with the exception of 1, and 11 through 20.
Offshore Fabrication Category The ISOGEN software offers and optional feature for segregating offshore fabrication category in the bill of materials. The OFFSHORE_FABCAT_CODE_LIST_VALUES section in the options file is used in the same way as the Shop FABCAT section. For more information, see OFFSHORE_FABCAT_CODE_LIST_VALUES (on page 215). If the codelist number is not listed in the option file sections for SHOP_FABCAT_CODE_LIST_VALUES or OFFSHORE_FABCAT_CODE_LIST_VALUES the item will default to field.
Unique Weld Numbering The ISOGEN software has the ability to display unique weld numbers from the piping database and display them on the isometric drawing. Since a PDS-generated weld number is eight characters long, the weld number is an arrowed message. If an enclosure is chosen for weld numbering (see ISOGEN option 75), it must be one of the following: diamond ended box round ended box rectangular box If an enclosure is not chosen, the default will generate a normal arrowed message with no box that points to the weld.
292
Plant Design System (PDS) ISOGEN
Welds
User-defined Weld Prefix The ISOGEN software allows the addition of weld prefix when using weld numbering. A weld prefix may be used: As a prefix to the actual weld number on the isometric in a box. The box shape to be set in Isogen option 75. As a form of general note about weld identification when positioned on the drawing frame. As part of the output in the user-defined weld summary report to identify each weld. For more information, see WELD_PREFIX (on page 189).
The Weld Summary Report A printed weld summary report is generated by setting Intergraph option 69. A new file name in the FILES Table (refer to The Files Table (on page 187)) of the options file is required if a user-defined format of the weld summary report is to be used. The designated file can be used for both the weld summary on the isometric drawing and the printed weld summary file. This optional file is referred to as the Weld Definition File (WDF) and is the twelfth entry in the FILES Table of the options file. The WDF file allows you to specify, within certain limits, the style and content of: The headings and data content of an alternative weld box to the normal weld box that is generated using ISOGEN option switch 53.
Any alternative box's output on the isometric in the same position as the normal weld box will be located in the bottom right corner of the isometric drawing area. The headings and data content of the weld summary report. If the Intergraph option to generate a weld summary report is set to 1 and the WDF file name is undefined, a Warning Error will be issued and the weld summary report will not be created. The report file name will be isoname.wXX where XX is the revision number.
See Also Weld Definition File Format (on page 293) Example WDF File (on page 296)
Weld Definition File Format The Weld Definition File (WDF) allows the user to: Define the format of an alternative weld box displayed on the isometric drawing Define a backing sheet on the drawing frame Define the format of the Weld Summary Report As a general rule, all heading and title formatting must be positioned in the file exactly as it is positioned on the printed output. Title elements, other than unique identifiers, can be used with any format. Data item identifiers will be enclosed in single quotation marks. Unique identifiers will be used to determine what is defined and must match exactly. These identifiers include: WELD-BOX-HEADINGS WELD-BOX-DATA-ITEMS WELD-INFO-CONTROLS WELD-INFO-DATA-ITEMS WELD-SUMMARY-TITLES
Plant Design System (PDS) ISOGEN
293
Welds WELD-SUMMARY-COLUMN-HEADINGS WELD-SUMMARY-DATA-ITEMS
Weld Boxes - Alternative Style Available formats for Weld boxes include headings, box data items, controls and information data items. There is no imposed limit on the width of the user-defined weld box. Although, keep in mind that the weld box takes up space in the isometric drawing area. Therefore, the width should be kept to an absolute minimum. Blank characters can be used as required. Blank columns are allowed. Use the | character to indicate vertical column positions. Weld box headings can be any ascii string. Weld box data items must carry: a data item identifier a start position along the horizontal line a justification marker
Weld Box Data Item Identifiers: Identifier
ATEXT Used
WELD-NO
-414, -415, -416
WELD-CAT
-414, -415, -416
N.S. WELD-TYPE
-417, -418, -419,-421, -422,-423
Weld Box Justification Markers R
Right Justified
L
Left Justified
C
Center Justified
Weld Boxes - Using a Backing Sheet When this form of weld information output is used, a design file (drawing frame) must be provided. The design file must contain an area that can receive weld information. The format is user definable, but no column headings are defined. All column headings must already exist in the design file. This style of output requires two types of information: Basic Weld Control Information Weld Data Item Information
294
Plant Design System (PDS) ISOGEN
Welds Basic Weld Control Information
Unless otherwise stated, where a number is required it will be integer or in real mm's with only one decimal place allowed. Unless otherwise stated, all of the following inputs are mandatory. Define the form of list to be output by entering one of the following. CONTINUOUS-DOWN CONTINUOUS-UP Define start positions for information using the format: START-POSITION XPOS YPOS Where: XPOS and YPOS is the x and y location in the design file. Define the vertical spacing between each line of horizontal text on the welding list using the format: VERTICAL-SPACING value Define the maximum number of lines that can be printed before automatic overflow onto another sheet occurs using the format: MAXIMUM-ENTRIES value Where: value is an integer Define the character height used for weld information using the format: TEXT-HEIGHT value Define the level where weld information should be placed. (Optional) Use the format: DRAWING-LAYER value Where: value is a level 1 - 63. Define the weight of characters output. (Optional) Use the format: TEXT-THICKNESS Where: value is a weight 0 - 10.
Weld Data Item Information Data items must carry a data item identifier and start position information ( The x position in mm's locates the bottom left hand point of the text string to be plotted. All text will be LEFT justified). Weld Box Data Item Identifiers
Identifier
ATEXT Used
WELD-NO
-414, -415, -416
WELD-CAT
-414, -415, -416
N.S. WELD-TYPE
-417, -418, -419,-421, -422,-423
Weld Summary Report The weld summary report page length is controlled by ISOGEN option switch 63. When generating this report three sections of data are required in the WDF file. These include:
Plant Design System (PDS) ISOGEN
295
Welds
The printed weld summary title definitions (WELD-SUMMARY-TITLES) This section can contain two types of information Heading titles Data items to be listed with the title Unique identifiers available for title information: PIPELINE-REFERENCE PIPING-SPEC DATE-DMY PAGE
The column heading definitions (WELD-SUMMARY-COLUMN-HEADINGS). This section can be any ascii string. The data definitions to be listed in each column (WELD-SUMMARY-DATA-ITEMS) Refer to the previous definition of Weld Box Data Item for the format of this section.
Single quotation marks (' ') used with PAGE attribute indicates program generated page number. 'Blank' indicates a blank line. The overall width of the weld summary report should not exceed 130 characters.
Example WDF File An example for an alternative weld list in the WDF file: WELD-BOX-HEADINGS | Weld | Weld | N.S. | Weld | Welder | | No | Cat | mm | Type | ID | WELD-BOX-DATA-ITEMS 'WELD-NO'4 R 'WELD-CAT' 10 L 'N.S.' 17 L 'WELD-TYPE' 25 L
An example for user defined backing weld list in the WDF file: WELD-INFO-CONTROLS CONTINUOUS-DOWN START-POSITION 225.0 80.5 VERTICAL-SPACING 4.5 MAXIMUM-ENTRIES 20 TEXT-HEIGHT 2.5 DRAWING-LAYER 16 TEXT-THICKNESS 2 WELD-INFO-DATA-ITEMS 'WELD-NO' 225.0 'WELD-CAT' 235.0 'N.S.' 245.0 'WELD-TYPE' 260.0
296
Plant Design System (PDS) ISOGEN
Welds An example for a user defined weld summary report in the WDF file: WELD-SUMMARY-TITLES WELD SUMMARY PAGE ' ' 'Blank' PIPELINE REF: 'PIPELINE_REFERENCE' 'Blank' PIPING SPEC : 'PIPING-SPEC' WELD-SUMMARY-HEADINGS Weld Weld N.S. Weld Welder No Cat mm Type ID ____ ____ ____ ____ ______ WELD-SUMMARY-DATA-ITEMS 'WELD-NO'8 R 'WELD-CAT' 17 L 'N.S.' 26 L 'WELD-TYPE' 37 L
Welds Listed in the Bill of Materials For welds listed in the BOM: Intergraph option 62 controls material pointers for welds. The commodity code will be SHOP, FIELD or OFFSHORE. The description will be weld type, material grade A and material grade B.
Plant Design System (PDS) ISOGEN
297
Welds
298
Plant Design System (PDS) ISOGEN
SECTION 17
Dimensioning and Coordinate Output The following is a list of related elements within the ISOGEN software that may be manipulated to change dimensioning/coordinate output. Related ISOGEN Options (Appendix ) 9, 41, 66, 80, 81, 119 Related Intergraph Options (Section 7) NONE Related Options File Material (Section 7) NONE Related ISOGEN ATEXT Records (Appendix ) -455
See Also Dimensioning Features (on page 300) Coordinate Features (on page 301)
Coordinate and Dimensioning Features - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated to change dimensioning/coordinate output. Related ISOGEN Options (Appendix B) 9, 41, 66, 80, 81, 119 Related Intergraph Options (Section 7) NONE Related Options File Material (Section 7) NONE Related ISOGEN ATEXT Records (Appendix B) -455
Plant Design System (PDS) ISOGEN
299
Dimensioning and Coordinate Output
Dimensioning Features ISOGEN's dimensioning features allows you to: Dimension Valve Centerlines Suppress Branch Dimensioning String Dimensioning Gaskets Included In Flanged Component Dimensions USA Style Dimensioning Non-Dimensioned Supports ISOGEN option 119 controls vertical dimensions/elevations. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Dimensioning Valve Centerlines This feature dimensions valves with certain bores and/or end conditions dimensioned to their centerline only, using string or composite dimension types. This is controlled by ISOGEN option 80 and 81. Centerline dimensioning on valves will only work with valves that have a spindle point define. Refer to Entering the Iso Symbol Editor Environment (on page 97) for information on defining a spindle point. ISOGEN option 80 defines the end type that will be dimensioned to the item's centerline. ISOGEN option 81 determines the upper size limit of valves that will be dimensioned to their centerline. All diameters that exceed the value specified by switch 81 are dimensioned normally. ISOGEN options 80 and 81 provide the complete definition of valves which will be dimensioned to their centerline. Units of input for the size limit are defined with ISOGEN 41. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Suppressing Branch Dimensioning This feature suppresses branches and tee bends/elbows with certain bores and/or number of components. Units of input for the size limit are defined by ISOGEN option 41. ISOGEN option 81 determines the upper size limit of branches whose dimensioning will be suppressed. All branch sizes that exceed the value specified by switch 81 are dimensioned normally. ISOGEN option 81 also determines the upper limit of components in a branch run that will have dimensioning suppressed. A branch run that exceeds the number of defined components is dimensioned normally. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
String Dimensioning This feature allows pipeline components to be dimensioned individually. ISOGEN option 9 flags individual dimensions to be output for every component in the pipeline. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
300
Plant Design System (PDS) ISOGEN
Dimensioning and Coordinate Output Gaskets Included in Flanged Component Dimensions This feature allows dimensioned flanged components to include gaskets (if present) in the dimension. Leader lines from adjoining flanges are displayed, while dimension leader lines from valve ends are not displayed. ISOGEN option 9 flags dimensioning to include gasket thickness. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
USA Style Dimensioning This feature displays the dimension on top of the dimension line. ISOGEN option 9, causes dimensions to be displayed on top of the witness line (USA style).
Coordinate Features ISOGEN's coordinate features allow you to: Extend Witness Lines Display Elevations at Bend/Elbow Intersections Display Elevations at Branch Intersections Display Split Point Coordinates ISOGEN option 119 controls vertical dimensions/elevations. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Extend Witness Line This feature allows elevations/coordinates to be output along an extended witness line at bends/elbows. ISOGEN option 66, displays elevations/coordinates along extended witness lines. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Display Elevation at Bend/Elbow Intersections This feature allows you to: Suppress Elevations at bend/elbow intersections Partial set of coordinates at bend/elbow intersections Only the coordinates that have changed A full set of coordinates at bend/elbow intersections. ISOGEN option 66 is used to define the Display Elevation at Bend/Elbow Intersections feature. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Display Elevations at Branch Intersections This feature allows you to: Suppress elevations at branch intersections Display a partial set of coordinates at a branch intersection Display only the coordinates that have changed Display a full set of coordinates at branch intersections
Plant Design System (PDS) ISOGEN
301
Dimensioning and Coordinate Output ISOGEN option 66 is used to define the Display Elevation at Branch Intersections feature. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
Split Point Coordinate Display This feature allows a full set of coordinates at iso split points to be grouped with a continuation note. ISOGEN option 66 is used to define the Display Elevation at Branch Intersections feature. See Alias ISOGEN Tables (see "Appendix: Alias ISOGEN Tables" on page 353) for more information.
302
Plant Design System (PDS) ISOGEN
SECTION 18
Detail Sketch and Information Note Facility The Detail Sketch Facility allows pre-defined detail sketches (MicroStation cells) to be automatically selected and positioned on the isometric drawing. In addition, a cross reference is added to the referenced item on the plotted pipeline. The Information Note Facility automatically selects general or specific notes (MicroStation cells) and positions them on the isometric drawing in the same manner as detail sketches. The initial information note is placed in the lower left corner of the drawing with additional notes being placed to the right along the bottom of the drawing. Information notes and detail sketch cells can be placed on the same drawing.
See Also Detailed Sketch and Entries in the DDF (see "Detail Sketch Entries in the DDF" on page 304)
Plant Design System (PDS) ISOGEN
303
Detail Sketch and Information Note Facility
Detail Sketch/Information Note Facility - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when using the Detail Sketch Facility.
Related ISOGEN Options (appendix) 71, 92
Related Intergraph Options (Section 7) 66
Related Options File Material (Section 7) DETAIL_SKETCH_FACILITY Also: The tenth entry in the FILES section of the options file: cell library. This entry defines the microstation cell library that contains the detail/note cells. The eleventh entry in the FILES section of the options file: DDF file. This entry in the options file defines the DDF (Data Definition File) that will be used to determine graphic parameters for the detail sketch/note.
Related ISOGEN ATEXT Records (appendix) -456, -541, -542
Detail Sketch Entries in the DDF This is an example of the portion of the Data Definition File (DDF) that pertains to the Detail Sketch facility. DETAIL-SKETCH FILE-FORMAT DXF SKETCH-SIZE 50 50 CROSS-REFERENCE 35 5 ALPHA TEXT-HEIGHT 3 TEXT-THICKNESS 2 DRAWING-LAYER 1 Where: DETAIL-SKETCH
is the section header in the DDF.
FILE_FORMAT DXF
determines the format of the detail. This line is ignored by PD_ISO.
SKETCH-SIZE 50 50
determines the X-Y size of the detail on the iso. The value is in either millimeters or inches (determined by ISOGEN switch 92).
CROSS-REFERENCE 35 determines the X-Y cross reference position on the detail in 5 either millimeters or inches (determined by ISOGEN switch 92), and the character type of the cross reference text. ALPHA
304
Plant Design System (PDS) ISOGEN
Detail Sketch and Information Note Facility TEXT-HEIGHT 3
determines the text height for the cross reference identifier.
TEXT-THICKNESS 2
determines the weight of the text for the cross reference identifier.
DRAWING-LAYER 1
determines the level for the cross reference identifier text.
For more information about the DDF, refer to Isometric Presentation (on page 309).
Information Note Entries in the DDF This is an example of the portion of the DDF that pertains to the Information-Note facility. INFORMATION-NOTE FILE-FORMAT DXF NOTE-SIZE 50 20 Where: INFORMATION-NOT is the section header in the DDF. E FILE-FORMAT DXF
determines the format of the note cell. This line is ignored by PD_ISO.
NOTE-SIZE
determines the X-Y size of the detail on the iso. The value is in either millimeters or inches (determined by ISOGEN switch 92).
Dynamic Detail Sketch Rather than use a pre-defined cell in the cell library, dynamic detail sketches are generated as snapshots of the component from the model during isometric extraction. For each item that matches the search criteria specified in the DETAIL_SKETCH_FACILITY, the system creates a temporary design file containing only a single component. The system processes the design file with RVHL using a resolution of 3000 and translates the 3D file into a 2D file. Prior to cell creation a rectangular box is added to match the SKETCH_SIZE specified in the .ddf file, and the graphics are scaled to fit the box. The generated cell is assigned a unique name by incrementing from DYN0 (DYN1, DYN2, DYN3, etc.) and added to any static cells in the specified detail sketch cell library. The system creates a cell for the component in question using an isometric view of the model graphics. The orientation of the isometric view is determined by ISOGEN option 42. Therefore, the orientation of the component in the sketch will match the orientation of the line relative to drawing north. Because the dynamic sketches are fitted to the SKETCH_SIZE, you should move the cross references to one of the corners to reduce the possibility of the sketch obscuring the cross reference.
Plant Design System (PDS) ISOGEN
305
Detail Sketch and Information Note Facility Example SKETCH-SIZE 50 50 CROSS-REFERENCE 47 1 ALPHA
Connect Point Data You can define label 987 in the label description library to append port information to the generated dynamic sketch. For example, if you define label 987 as follows, the system will append P1 to port 1 of a multiport component, P2 to port 2, and so forth. **************** Label Type = 987 **************** Label Name = Dynamic Sketch Port P Attribute Data 1 - 'P' **************************************************
306
Plant Design System (PDS) ISOGEN
SECTION 19
Weight Display The Weight Display Facility allows the weight stored in the Design database for each component to be extracted from the 3D model and listed on the isometric material list. Total weight can be generated for the pipeline, for the Fabrication (Shop) components, for the Erection (Field) components, and for Offshore components. Spool weight can be generated for Spool isometrics.
See Also Weight Display - Related Information (on page 307)
Weight Display - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when using the Weight Display Facility. Related ISOGEN Options (appendix) 41 Related Intergraph Options (Section 7) 47, 63 Related Options File Material (Section 7) NONE Related ISOGEN ATEXT Records (appendix) -352, -353, -354, -355, -379, -380, -381 Weight will be interpreted as: Unit weight of a component Weight per length of a pipe/tube Where: length is a foot in Imperial Units, and a Meter in Metric units A Warning Message will be output to the error file when weight has not been recorded in the design database for a pipe/component (35:1111) Warning - Component(s) with no Weight found
Center of Gravity Calculation Before Calculating the Iso Center of Gravity 1. Generate an ISAM center of gravity weight library. From Windows File Manager or the DOS prompt, run the ~\pdiso\bin\bldwtlib.exe executable to generate or update an ISAM weight library. Once initialized, bldwtlib prompts you to input an ASCII weight library neutral file. The default, weight_lib.neu, is located in the ~\pdiso\examples directory and contains entry definitions and example data that can be referenced to make a custom weight library neutral file. After a weight library neutral file is defined, you are prompted to enter a name or use the default name, cog_weight.l, for the resulting ISAM weight library. By default, the file is written to the examples directory.
Plant Design System (PDS) ISOGEN
307
Weight Display 2. Set Intergraph option 63 to 1. 3. Edit the ISOGEN options file. Define the name of the ISAM center of gravity library under the ninth entry of the FILES category. This is the library that will be used to make center of gravity calculations. For example, '~\pdiso\examples\cog_weight.l' !COG WEIGHT LIBRARY Define the center of gravity entry in the MTO record map, which is the fifth entry of the FILES category. For example, '~\pdiso\examples\cogmto.tbl' !MTO RECORD MAP
308
If the Debug switch on the Submit Batch Job form is set to on, a center of gravity report file, .cog, is written to the output directory. If the Verify on the Submit Batch Job form is set to on, additional Intergraph information about each component is added to the center of gravity report file. In the STIB data file (used to place drawing title block text), center of gravity x, y and z coordinates are assigned as node numbers 908, 909 and 910 respectively.
Plant Design System (PDS) ISOGEN
SECTION 20
Isometric Presentation ISOGEN's Presentations feature allows you to customize the presentation of a generated isometric drawing. ISOMETRIC-DEFINITION is the identifier used when defining information for Isometric Presentations. When using the user-defined formats, it is your responsibility to ensure (by doing trial runs) that the specified options are practical and produce the required isometric presentation before committing to project use. The drawing definition file (DDF) contains user-defined requirements that determine the final plotted isometric presentation. The DDF file is the eleventh entry in the FILES section of the options file. In addition to containing isometric presentation information, the DDF also contains Detail Sketch definition data (DETAIL-SKETCH). Subsection identifiers for user-defined presentation features include: PIPELINE-ATTRIBUTES PIPELINE-ATTRIBUTES-SPECIAL PIPELINE-ATTRIBUTES-DOTTED BEND/ELBOW-REPRESENTATION FITTINGS-GENERAL FITTINGS-SPECIAL FITTINGS-UNDIMENSIONED-BRANCHES MISC-ITEMS LAYER-NAMES An example data definition file is located at the end of this section. The DDF uses the following conventions: Must be an ascii character file. All identifiers (Main and Sub-section) plus all data attributes must start in position one on a new line. No spaces are allowed in any identifier or attribute name. Use of any of the subsection identifiers is optional. Program defaults will be used as required.
See Also Isometric Presentation - Related Information (on page 310) PIPELINE-ATTRIBUTES (on page 310) PIPELINE-ATTRIBUTES-SPECIAL (on page 311) PIPELINE-ATTRIBUTES-DOTTED (on page 312) BEND/ELBOW-REPRESENTATION (on page 312) FITTINGS-GENERAL (on page 313) FITTINGS-SPECIAL (on page 314) FITTINGS-UNDIMENSIONED-BRANCHES (on page 315) MISC-ITEMS (on page 316) LAYER-NAMES (on page 316) Program Defaults (on page 317) Example Drawing Definition File (on page 317)
Plant Design System (PDS) ISOGEN
309
Isometric Presentation
Isometric Presentation - Related Information The following is a list of related elements within the ISOGEN software that may be manipulated when defining a isometric presentation.
Related ISOGEN Options (appendix) NONE
Related Intergraph Options (Section 7) NONE
Related Options File Material (Section 7) NONE The eleventh entry in the FILES Section of the Options File: Data Definition File (DDF) (See Chapter 8)
Related ISOGEN ATEXT Records (Appendix B) NONE
PIPELINE-ATTRIBUTES The PIPELINE-ATTRIBUTES section of the DDF allows you to define the following characteristics for a plotted pipeline (Pipe, Elbows, Bends, Tees, Crosses, etc.): N.S. (Bore Units) OBN.S. Range Plotted Pipe Thickness Layer (Level) number Color
Attribute/Data Identifiers Bore Units
N.S. Data
Data = INCH or MM
N.S. Range
N.S.RANGE min and max bore
min/max bores may be stated in either Integer or Real (such as, 1 1.0 1.5 10 10.0)
Thickness
THICKNESS data 1 data 2
data 1 = Integer number representing required thickness. data 2 = Actual Thickness (width) of plotted line in mm (Real Number).
Layer
310
LAYER data
data is an Integer identifying the required Layer (Level) to which the Pipeline is to be assigned.
Plant Design System (PDS) ISOGEN
Isometric Presentation Color
COLOUR number
Number is an integer identifying the color of the pipeline, as defined in the color tables. The default color numbers are: 0 = white 1 = blue 2 = green 3 = red 4 = yellow 5 = violet 6 = orange
Example PIPELINE-ATTRIBUTES Input: PIPELINE-ATTRIBUTES N.S. INCH N.S.RANGE 0 2 THICKNESS 2 0.65 LAYER 1 COLOUR 3 N.S.RANGE 2.5 6 THICKNESS 2 0.95 LAYER 3 COLOUR 3 N.S.RANGE 8 * THICKNESS 4 1.25 LAYER 5 COLOUR 3
Guidelines for Defining PIPELINE-ATTRIBUTES Input:
Any number of Spaces are allowed between the attribute identifier and data items. All lines must start in position one. Allow space for a maximum of five N.S. RANGE records. Use of LAYER is optional. If LAYER is not set, the ISOGEN default LAYER set will be used. An * is allowed in last maximum bore position to signal that there is no maximum bore limit. THICKNESS data 1 attribute is used to define required line weight in plotfile output. THICKNESS data 2 is used by the ISOPLOT module of ISOGEN when positioning Messages along the pipeline. N.S. INCH keyword must always be in capital letters.
PIPELINE-ATTRIBUTES-SPECIAL The PIPELINE-ATTRIBUTES-SPECIAL section of the DDF is used in the same way as the PIPELINE-ATTRIBUTES feature except that the attributes set only apply to pipeline sections designated Special Status. Special Status is recognized when attribute status is set to DOTTED or NO-MTO.
Plant Design System (PDS) ISOGEN
311
Isometric Presentation
PIPELINE-ATTRIBUTES-DOTTED The PIPELINE-ATTRIBUTES-DOTTED section of the DDF allows you to define thickness, layer, color, and style attributes for the following three categories of dotted representation. Dotted Special Status (SPECIAL-STATUS; such as Dotted, NO-MTO Items) Dotted Pipeline Continuations (PIPELINE-CONTINUATION) Dotted items at isometric Split Points (DRAWING-SPLIT-POINTS)
Example PIPELINE-ATTRIBUTES-DOTTED Input: PIPELINE-ATTRIBUTES-DOTTED SPECIAL-STATUS THICKNESS 1 0.1 LAYER 5 COLOUR 4 PIPELINE-CONTINUATION THICKNESS 1 0.1 LAYER 5 COLOUR 4 DRAWING-SPLIT-POINTS THICKNESS 1 0.1 LAYER 5 COLOUR 4
Guidelines for Defining PIPELINE-ATTRIBUTES-DOTTED Input:
The SPECIAL-STATUS, PIPELINE-CONTINUATION or DRAWING-SPLIT-POINT identifiers may be included in any order following the main section identifier. Use the THICKNESS and LAYER data as described for PIPELINE-ATTRIBUTES. N.S.RANGE or Bore Units are not allowed in this section. Dotted representation is the same for all bores. When specifying the N.S. Range, enter the data in all capital letters as INCH or MM. If a PIPELINE-ATTRIBUTES-SPECIAL section is included in the file, any setting for SPECIAL-STATUS found in this section will be ignored. Use of LAYER is optional. If LAYER is not set, the ISOGEN default LAYER setting will be used. Care should be taken when specifying the THICKNESS data for any of these Dotted categories. All three categories can involve the plotting of Dotted Fittings that may look unacceptable if thickness for Dotted representation is too thick.
BEND/ELBOW-REPRESENTATION The BEND/ELBOW-REPRESENTATION section of the DDF allows you to define Elbows and Bends to be either Round or Square when displayed on the isometric drawing.
Example BEND/ELBOW-REPRESENTATION Input: BEND/ELBOW-REPRESENTATION BEND data ELBOW data Where: data can be set to either SQUARE or ROUND. If no setting is defined, ROUND is used as the default.
312
Plant Design System (PDS) ISOGEN
Isometric Presentation
FITTINGS-GENERAL The FITTINGS-GENERAL section of the DDF allows you to define attributes for all Fittings. These attributes include: N.S. (Bore Units) N.S. Range Plotted Fitting (Component) Thickness Layer (Level) number Fitting Scale (Plotted size of fittings) (to be applied to standard ISOGEN symbols) Color
Attribute/Data Identifiers Include: Bore Units
N.S. Data
Data = INCH or MM
N.S. Range
N.S.RANGE min and max bore
min/max bores may be stated in either Integer or Real (such as, 1 1.0 1.5 10 10.0)
Thickness
THICKNESS data 1 data 2
data 1 = Integer number representing required thickness. data 2 = Actual Thickness (width) of plotted line in mm (Real Number).
Layer
LAYER data
data is an Integer identifying the required Layer (Level) to which the Fitting is to be assigned.
Scale
SCALE data
data is a two- or three-digit Integer that represents an increase or decrease to the basic 100% standard symbol size for all types of fittings.
Color
COLOUR number
Number is an integer identifying the color of the pipeline, as defined in the color tables. The default color numbers are: 0 = white 1 = blue 2 = green 3 = red 4 = yellow 5 = violet 6 = orange
Example FITTINGS-GENERAL Input: FITTINGS-GENERAL N.S. INCH N.S.RANGE 0 2 THICKNESS 2 1.5 LAYER 20 SCALE 100 COLOUR 4 N.S.RANGE 2.5 6 THICKNESS 3 1.75 LAYER 20 SCALE 150 COLOUR 4 N.S.RANGE 8 * THICKNESS 4 2.0 LAYER 20 SCALE 200 COLOUR 4
Plant Design System (PDS) ISOGEN
313
Isometric Presentation
FITTINGS-SPECIAL This FITTINGS-SPECIAL section of the DDF allows you to define Thickness, Layer, Scale, or Color attributes for specific types of components. The settings presented in this section will override the Fittings-General settings for the selected types of components.
Definable Attributes Include: THICKNESS LAYER SCALE COLOUR Data requirements for the previous attributes are the same as the data requirements for FITTINGS-GENERAL. Any of the previous attributes can be set for a specific type of component. But, if FITTINGS-SPECIAL attributes are not defined, ISOGEN defaults to the FITTINGS-GENERAL. For example: If LAYER 40 was the only special attribute set for INSTRUMENTS, it would be used for all INSTRUMENTS (all bores), but any Thickness and / or Scale attributes would be used from the FITTINGS-GENERAL section. Whenever a Scale attribute is set in this section, the Scale factor will not be used as a direct scale to the standard symbol. It will instead be used as a Multiplier to any Scale set in the FITTINGS-GENERAL section. For example: Scale 150 set in Fittings-General Scale 75 set in Fittings-Special Scale to be used on nominal Fitting type is 150 x 0.75 = 113 (to nearest whole number).
Example FITTINGS-SPECIAL Input: FITTINGS-SPECIAL INSTRUMENTS LAYER 30 (Put all Instruments on Layer 30) OLETS SCALE 75 (Olets to be scaled down) SUPPORTS THICKNESS 4 2.0 COLOUR 4 (All Supports to be plotted yellow)
314
Plant Design System (PDS) ISOGEN
Isometric Presentation Fitting type identifiers OLETS INSTRUMENTS SUPPORTS WELDS COUPLINGS CAPS UNIONS FLANGES FILTERS PIPE-BLOCKS SAFETY-DISC TRAPS REDUCERS VALVES VALVES-ANGLE VALVES-3WAY VALVES-4WAY NOZZLE END-CONNECTORS HYGENIC-CONNECTORS MISC-COMPONENTS MISC-COMPONENT-PLUG MISC-COMPONENT-RESTRICTOR MISC-COMPONENT-SLIPPLATE MISC-COMPONENT-SLIPRING MISC-COMPONENT-SPECBLIND
FITTINGS-UNDIMENSIONED-BRANCHES The FITTINGS-UNDIMENSIONED-BRANCHES of the DDF section allows you to vary the Thickness, Layer, Scale, and Color of any component that is included in any Undimensioned Branch. Attributes/Data identifiers are the same as the attributes/data identifiers for FITTINGS-GENERAL.
Example FITTINGS-UNDIMENSIONED-BRANCHES Input: FITTINGS-UNDIMENSIONED-BRANCHES N.S. INCH N.S.RANGE 0 1 THICKNESS 1 1.0 LAYER 10 SCALE 60 COLOUR 3 N.S.RANGE 1.5 2 THICKNESS 2 1.5 LAYER 10 SCALE 75 COLOUR 3 These parameters should only be used when the Branch Dimension Suppression facility is being used (ISOGEN option switch 81). It will be up to you to verify that any N.S.RANGE set in the FITTINGS-UNDIMENSIONED-BRANCHES section matches the Bore range set in Option Switch 81. All Pipe fittings (Elbows, Tees, etc.) are plotted the same thickness as a tube.
Plant Design System (PDS) ISOGEN
315
Isometric Presentation
MISC-ITEMS The MISC-ITEMS section in the DDF allows you to set the Thickness, Layer, and Color data for the following types of miscellaneous items that appear on an isometric drawing: DIMENSION-TEXT DIMENSION-LINES ISO-TEXT FRAME-TEXT SKEWS HATCHING LAGGING TRACING FRAME WELD-BOX SPEC-BREAKS MATERIAL-LIST (Styles 1 nd 2 only)
Example MISC-ITEMS Input: MISC-ITEMS DIMENSION-TEXT THICKNESS 2 0.8 LAYER 22 COLOUR 4 DIMENSION-LINES THICKNESS 1 0.6 LAYER 23 COLOUR 4 SKEWS THICKNESS 2 0.8 LAYER 25 COLOUR 4 HATCHING THICKNESS 1 0.6 LAYER 25 COLOUR 4 Any undefined attribute uses the ISOGEN defaults.
LAYER-NAMES The LAYER-NAMES section in the DDF allows you to issue standard Names to any layer number used in any of the other sections.
Example LAYER NAMES Input: LAYER-NAMES 10 '10' 12 '12' Where 10 is the Layer Number and the text 22 '22' within the '' is the Layer Name. 10 '10'
is the layer number is the layer name
Because Microstation LAYERS are numbers, NAMES must be the same as the LAYER. Up to 50 names can be defined.
316
Plant Design System (PDS) ISOGEN
Isometric Presentation
Program Defaults The table below shows the program default settings for THICKNESS and LAYER for the various elements that are used in the generation of a plotted isometric drawing.
Element
Default Thickness
Default Layer
Pipeline (including Elbows, Tees, etc.)
3 (0.6 mm)
1
All Fittings
2 (0.25 mm)
2
All drawing Text and 1 (0.1 mm) 3 other miscellaneous items
1 (0.1 mm)
3
Drawing Frame, Frame text, Weld Box, etc
1 (0.1 mm)
4
Dotted items
1 (0.1 mm)
5
Material List
1 (0.1 mm)
6
Example Drawing Definition File ISOMETRIC-DEFINITION PIPELINE-ATTRIBUTES N.S. INCH N.S.RANGE 0 2 THICKNESS 2 0.65 LAYER 7 COLOUR 3 N.S.RANGE 2.5 6 THICKNESS 2 0.95 LAYER 29 COLOUR 3 N.S.RANGE 8 * THICKNESS 4 1.25 LAYER 30 COLOUR 3 PIPELINE-ATTRIBUTES-DOTTED DRAWING-SPLIT-POINTS THICKNESS 2 0.35 LAYER 19 COLOUR 4 SPECIAL-STATUS THICKNESS 2 0.65 LAYER 8 COLOUR 4 PIPELINE-CONTINUATION THICKNESS 2 0.35 LAYER 9 COLOUR 4 FITTINGS-GENERAL N.S. INCH N.S.RANGE 0 2 THICKNESS 2 0.30 LAYER 7 SCALE 105 COLOUR 4 N.S.RANGE 2.5 * THICKNESS 2 0.35 LAYER 7 SCALE 110 COLOUR 4 FITTINGS-SPECIAL INSTRUMENTS THICKNESS 2 0.30 LAYER 10 SCALE 115 COLOUR 4 NOZZLE THICKNESS 2 0.30 LAYER 11 COLOUR 4 CAPS THICKNESS 3 0.85 LAYER 38 COLOUR 4 COUPLINGS THICKNESS 3 0.65 LAYER 37 COLOUR 4 VALVES THICKNESS 2 0.30 LAYER 12 SCALE 180 COLOUR 4 FLANGES THICKNESS 2 0.30 LAYER 31 SCALE 120 COLOUR 4 UNIONS THICKNESS 2 0.30 LAYER 35 SCALE 110 COLOUR 4 OLETS THICKNESS 4 0.70 LAYER 34 SCALE 110 COLOUR 4 WELDS THICKNESS 2 0.30 LAYER 32 SCALE 130 COLOUR 4 REDUCERS THICKNESS 3 0.60 LAYER 33 SCALE 120 COLOUR 4 VALVES-ANGLE THICKNESS 2 0.30 LAYER 13 SCALE 180 COLOUR 4 VALVES-3WAY THICKNESS 2 0.30 LAYER 14 SCALE 150 COLOUR 4
Plant Design System (PDS) ISOGEN
317
Isometric Presentation VALVES-4WAY THICKNESS 2 0.30 LAYER 15 SCALE 150 COLOUR 4 SUPPORTS THICKNESS 4 0.90 LAYER 36 SCALE 130 COLOUR 4 PIPE-BLOCKS THICKNESS 2 0.30 LAYER 39 COLOUR 4 SAFETY-DISC THICKNESS 2 0.30 LAYER 40 COLOUR 4 FILTERS THICKNESS 2 0.60 LAYER 41 SCALE 280 COLOUR 4 TRAPS THICKNESS 2 0.60 LAYER 42 SCALE 180 COLOUR 4 END-CONNECTORS THICKNESS 2 0.30 LAYER 50 SCALE 120 COLOUR 4 HYGENIC-CONNECTORS THICKNESS 4 0.70 LAYER 50 SCALE 300 COLOUR 4 MISC-COMPONENTS THICKNESS 2 0.30 LAYER 49 SCALE 180 COLOUR 4 MISC-COMPONENT-RESTRICTOR THICKNESS 2 0.30 LAYER 44 COLOUR 4 MISC-COMPONENT-SLIPPLATE THICKNESS 2 0.30 LAYER 45 COLOUR 4 MISC-COMPONENT-SLIPRING THICKNESS 2 0.30 LAYER 46 SCALE 250 COLOUR 4 MISC-COMPONENT-SPECBLIND THICKNESS 2 0.30 LAYER 47 COLOUR 4 MISC-COMPONENT-PLUG THICKNESS 2 0.30 LAYER 48 COLOUR 4 FITTINGS-UNDIMENSIONED-BRANCHES N.S. INCH N.S.RANGE 0 2 THICKNESS 2 0.65 LAYER 43 SCALE 300 COLOUR 4 BEND/ELBOW-REPRESENTATION BEND ROUND ELBOW ROUND MISC-ITEMS DIMENSION-TEXT LAYER 16 COLOUR 4 DIMENSION-LINES LAYER 17 COLOUR 4 ISO-TEXT LAYER 20 COLOUR 4 FRAME-TEXT LAYER 21 COLOUR 4 SKEWS LAYER 22 COLOUR 4 HATCHING LAYER 23 COLOUR 4 LAGGING LAYER 24 COLOUR 4 TRACING LAYER 25 COLOUR 4 FRAME LAYER 26 COLOUR 4 WELD-BOX LAYER 27 COLOUR 4 SPEC-BREAKS LAYER 28 COLOUR 4 MATERIAL-LIST LAYER 18 COLOUR 4 LAYER-NAMES 1 '1' 2 '2' 3 '3' 4 '4' 5 '5' 6 '6' 7 '7' 8 '8' 9 '9' 10 '10' 11 '11' 12 '12' 13 '13' 14 '14' 15 '15' 16 '16' 17 '17' 18 '18' 19 '19'
318
Plant Design System (PDS) ISOGEN
Isometric Presentation 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
'20' '21' '22' '23' '24' '25' '26' '27' '28' '29' '30' '31' '32' '33' '34' '35' '36' '37' '38' '39' '40' '41' '42' '43' '44' '45' '46' '47' '48' '49' '50'
Plant Design System (PDS) ISOGEN
319
Isometric Presentation
320
Plant Design System (PDS) ISOGEN
SECTION 21
Isometric Types Isometric Type definitions allow more flexibility with the line name definition. By using Types feature, you can track drawing records more accurately and efficiently. Isometric Types also allow you to store the same line name multiple times in the database, each time as a different Type. For example, line ABC can be stored twice, once as Fabrication Type and once as Spool Type. The Type attribute creates a unique database entry.
Isometric Types and Code List 1900 Isometric Types are supported by Code List 1900. Code List 1900, as delivered, contains 3 types. These types include: Fabrication Spool Stress The following is an example of Code List 1900. C1900 ; 1900, Iso Type ; NOTE: In editing this codelist set, do not change the meaning ; of existing codelist values. Some data displays require that only ; values to the left of the "=" sign be shown; other reports require ; that only values to the right of the "=" sign be displayed. 1 = 'Fabrication' (Default Setting) 2 = 'Spool' 3 = 'Stress' You can add more options, if needed, to Code List 1900. For an example of setting isometric types, refer to Bulk Load Lines (on page 86). The Isometric Type is a new column in pdtable_185 of the Project Database. All records MUST have an Isometric Type, or they will not extract. Batch Input files contain Type information when they are created on ISOGEN software version 5.0 or later. Batch Input files created prior to 5.0 will extract, but a error message will be output that states that the batch input file is out of date, and needs to be replaced.
Plant Design System (PDS) ISOGEN
321
Isometric Types
322
Plant Design System (PDS) ISOGEN
APPENDIX A
Appendix: Warning and Error Messages This section lists the warning and error messages that are issued by the various components of the iso extraction software and suggested corrective action when that is possible. Please refer to the section entitled Software Organization for a discussion of the each of the components and how they are related.
Intergraph Interface to ISOGEN The messages that are issued by the Intergraph interface to ISOGEN are, for the most part, recorded in an error message file that is created along with the intermediate data file (the input file to ISOGEN) when errors occur. If no errors occur, then an error file is not created. Some messages generated in the file are not written to the screen as they only contain additional data on a reported error. There are three categories of messages issued by the software: Information - An error occurred that can result in other errors later on. Warning - An error occurred that can result in a problem on the drawing. The drawing should be checked. Error - An error occurred that is serious enough to cause extraction to abort. The drawing is not produced.
Information Messages I1 - The Graphic Commodity Library does not exist or an error occurred when it was opened. This message indicates a problem with the graphic commodity library. Make sure that it is properly attached to the primary (the first) model design file. If there is doubt then you should enter the file in graphics and try to place any component. Iso extraction requires read access to the file.
I3 - Error opening Material Descriptions Library. This message indicates a problem with the material description library. The proper file should be attached to the primary (first) model file via the RDB software. Iso extraction requires read access to the file.
I4 - Error opening Specialty Material Descriptions Library. This message is the same as I3 except that it pertains to the piping specialty and instrument material descriptions library. Note that if this library is not successfully opened then specialty items will NOT receive material descriptions in the iso bill-of-material. If the file exists and is properly attached make sure that your process has read access to it.
I5 - Error accessing the Label Descriptions Library. The label description library should be properly attached to the primary (first) model file via the RDB software. If this has been done, then a quick test using the drawing
Plant Design System (PDS) ISOGEN
323
Appendix: Warning and Error Messages annotation commands might uncover the problem. Make sure that your process has read access to the file.
I6 -Note file not defined I8 - Unrecognized key read from MTO Neutral File record map. This message occurs when the software encounters an unexpected record in the neutral file map. Usually, this indicated that the number of table entries to follow (the number following each keyword) is incorrect.
I9 - Unrecognized key read from options file. This message occurs when the software encounters an unexpected record in the options file. All keywords are followed by a number that indicates the number of records to follow until the next keyword. If this number is incorrect then this message will result.
I10 - An error occurred while reading the PDS to ISOGEN symbol map. Some difficulty occurred while the PDS-to-ISOGEN symbol map file was being read in. Check the symbol map file that is defined in the options file for mistakes.
I11 - Error reading in complete PDS to ISOGEN symbol map. The internal buffer used for holding the PDS to ISOGEN map has been filled by entries from the map file and some have thus been ignored. Contact Intergraph with this problem.
I13 - Physical data library not read. This message indicates that the physical data library for the current component could not be read by the mto software for generating bolts and gaskets. If bolt/gasket generation has failed on the current component then this message indicates that the most likely reason is that an error occurred while trying to read the physical data library. If no bolts/ gasket generation failure occurred then the message might be ignored.
I14 - Unrecognized key read from title block tables file This message indicates that an unexpected record was encountered in the title block tables file. It will usually indicate that the number of entries to follow value (on a record following a keyword) is incorrect.
I16 - Intergraph option 34 reset to zero Intergraph option 34 applies only to batch extraction. When interactive extraction is run, this option is ignored.
324
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages I17 - Intergraph option 16 reset to 0 I18 - Check number of lines entry in the options file. I19 - Error accessing specialty material descriptions library I20 - Error accessing the specified material description library I21 - Error accessing the specified label description library I22 - Error opening the label description library I23 - The last start point is chosen to be the traversal start point Table: 3 Component Occ: 4195082 Segment Occ: 4194661
I24 - Alternate index is used to read material description library. The material description is not found with the default primary key, item code. The alternate index, defined in the ALTERNATE_DESCRIPTION_INDEX table in the option file, is used to find the material description.
I25 - No existing sheet and no last start point for section 1 Iso extraction will continue as the first time
Warning Messages W1 - Error computing valve oper or reducer orientation. An error occurred in the calculations to orient a valve operator or an eccentric reducer. In both cases the connect point orientations should be checked in graphics to confirm that they are correct.
W2 - Segment column is undefined. In checking for an attribute change at a segment endpoint the attribute being checked has gone from being defined with a value to being undefined (blank). The attributes defined in the PIPELINE_HEADER table in the options file should be checked and defined with a value as needed.
W3 - Error forming label from label library. An error has occurred in creating a note or label using the label description library. The label (whose label number is also printed in the message) should be checked using the label description library software.
W4 - Invalid LINE ID format - LINE ID ignored. A line ID that is either incorrect in format or contains invalid data has been input. Check the format of the line ID against the definition in the options file. Remember that each attribute that is part of the line ID must be separated from the others by a dash ( - ). An example of invalid data in the line ID might be a fluid code that does not exist in the fluid code codelist.
Plant Design System (PDS) ISOGEN
325
Appendix: Warning and Error Messages W5 - Error reading in extraction criteria. An error has occurred reading in the line identification inputs from the input file. This might indicate a problem in the software that creates the input file.
W6 - Mo del design file not found. This message indicates that the model design file read in from the input file either does not exist or that your process does not have read access to it.
W7 - Error reading the Label Description Library. This message probably indicates that the label definition for a specific label does not exist in the label description library opened by the software. Make sure that the primary (first) model design file has the proper library attached or that the proper library is defined in the options file.
W8 - ISOGEN key is undefined in PDS - ISOGEN map. This message indicates that an entry in the PDS to ISOGEN symbol map exists for the PDS component but that the ISOGEN symbol name in the table does not. Make sure that the table contains the ISOGEN symbol name for the component in question.
W9 - Could not locate item in PDS to ISOGEN symbol map. This message indicates that the PDS symbol in question could not be located in the PDS to ISOGEN symbol map.
W10 - No-mto attribute has illegal value. The no-mto attribute on a component, pipe, or instrument has a value other than 0 or 1. Set the attribute to a legal value.
W11 - Error forming nozzle note. An error has occurred forming the nozzle connection note generated at equipment nozzles. Check the label description library labels in the library if you are using the NOZZLE_NOTE table in the options file. Also review the nozzle entity to make sure that everything looks fine. If the failure occurs with the default nozzle note then report the problem to Intergraph.
W12 - The coordinate system option is invalid. Coordinate system is set to PLANT. The coordinate system defined in the options file is incorrect so it was set to a default value. Check the option specified in the options file.
W13 - Material description has been truncated. The material description generated from the material description library and the label description library has exceeded the maximum size allowed for in the software and was truncated. Contact Intergraph.
W14 - Error reading Specialty Material Description Library. An error occurred retrieving the material description for a piping specialty, instrument or support from the specialty description library. An error message is generated in the iso bill-of-material.
326
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages W15 - Error reading the Material Description Library. An error occurred retrieving the material description for a commodity item. An error message is generated in the iso bill-of- material.
W16 - Error attaching the design file . W17 - Error accessing A/N Commodity Library. An error has occurred searching the alphanumeric commodity library either for an implied material item or for a size dependent commodity code. Check the library to see whether or not the item that is being searched on exists.
W20 - Header record attribute is undefined. Each entry in the PIPELINE_HEADER table in the options file defines a "Header record" for ISOGEN. These header records simply define the initial value for certain attributes at the start of the line (that is, spec name, insulation type, and so on). This message is warning you that for some header record defined in the PIPELINE_HEADER table the value for it from the database is undefined. You must either define the attribute in the database or remove the header record entry from the table.
W23 - An error occurred while generating implied materials. Bolts, a gasket, or a weld will NOT be generated in the drawing and/or the mto neutral file. Some error resulted in no implied materials. Check the error message file for details of the problem.
W25 - Error loading spec attributes for implied component. An error has occurred while attempting to overlay attributes from the spec for a stub onto the database record for a lap-joint flange. This overlaying must be performed just prior to generation of the material description so that attributes embedded in the material description for the stub can be generated properly. Make sure that the spec contains a valid entry for the stub. The spec search is performed by using the same data as for the lap joint flange except that the option code is set to the flange option code plus 5000.
W26 - Maximum number of implied items exceeded. A component generates too many implied items from the Material Description Library and an internal buffer has overflowed. Contact Intergraph to have the buffer size increased.
W27 - The Material Description Library is required in order to generate implied materials. Some materials might be missing from the MTO neutral file. A component indicates that implied material should be generated from the Material Description Library but the library is either not attached to the model or the library that is attached does not exist.
W28 - Error accessing the Material Description Library for implied materials. A component indicates that implied material should be generated from the Material Description Library but none was found. Check to make sure that the library contents are correct.
Plant Design System (PDS) ISOGEN
327
Appendix: Warning and Error Messages W29 - Title block tables file not found. The title block tables file identified in the FILES section of the options file does not exist. This file identifies those attributes that are to be placed in the drawing title block. When this file does not exist no text can be placed in the title block.
W30 - Error opening title block tables file. This message indicates that the title block tables file exists, but that for some reason it could not be opened. Check that your process has proper VMS access to the file.
W31 - Error opening segment data file. File will not be created. The file holding title block attributes generated from the SEGMENT_DATA_TABLE (in the title block tables file) could not be opened. No title block data will be generated.
W32 - Error opening STIB input file. File will not be created. The file holding title block attributes generated from the DRAWING_DATA_TABLE (in the title block tables file) could not be opened. No attributes generated by this table will appear in the title block.
W33 - Error opening sheet specific title block data file. The file holding title block attributes generated from the SHEET_DATA_TABLE (in the title block tables file) could not be opened. No attributes generated by this table will appear in the title block.
W34 - Error opening MTO Neutral File - file will not be created. An error occurred when creating a new mto neutral file. Make sure that your process has write access to the default directory.
W35 - MTO record map not found. The mto record map, specified in the options file, cannot be located. Check the file spec in the options file and make sure that your process has read access to the file.
W36 - Valve/Operator file does not exist. A valve/ operator table has been specified in the options file, but it could not be found while attempting to open it.
W37 - Notes File not found. A Notes File has been specified in the options file, but it could not be located when an attempting to open it.
W38 - Error opening the Notes Table. An error occurred while attempting to open the Notes Table. Make sure that your process has read access to the file.
W39 - Notes Table lookup failed. A Notes Table record whose input matches the current one could not be located. The current key is printed out. Check the Notes Table to ensure that the input has a corresponding record.
328
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages W40 - The number of components exceeds the limit of the maximum allowed number of components in a multiple bolt-through. W41 - Error retrieving component from linkage. Cannot determine second orientation for operator. An error has occurred while scanning the design file for a valve operator that requires a second orientation. This is probably an Intergraph software problem.
W42 - User Symbol Library not found. The user symbol library, specified in the options file, cannot be found or the current extraction process does not have privilege to access it.
W43 - Bolt-thru component encountered at a loop closure W44 - The last start point is chosen to be the traversal start point The segment occurrence is different with that of the last start point Old - Table: 3 Component Occ: 4195082 Segment Occ: 4194661 New - Table: 3 Component Occ: 4195082 Segment Occ: 4194662
W45 - Error locating segment for logical pipe support W46 - Error computing pipe support orientation. An error occurred in the calculation to pipe support. The connect point orientations should be checked in graphics to confirm that they are correct.
W47 - Detail sketch directory not found W48 - Detail Drawing definition file not found W49 - Weld Definition Format file not found W50 - Error retrieving weld numbers W51 - Very short pipe encountered W52 - Enclosure type is invalid W53 - Label: $1 in triangle box exceeds maximum length of two W54 - Label: $1 in diamond box exceeds maximum length of three W55 - Overlapping components were detected. Refer to the HITS report for details.
Plant Design System (PDS) ISOGEN
329
Appendix: Warning and Error Messages W56 - Two end points match the last start point segment occurrence The end closest to the last start point is the chosen start point Old - Table: 3 Component Occ: 4195082 Segment Occ: 4194661 New - Table: 3 Component Occ: 4195334 Segment Occ: 4194661
W57 - Only one end point matches the last start point segment occurrence This end point is chosen to be the traversal start point Old - Table: 3 Component Occ: 4195082 Segment Occ: 4194661 New - Table: 3 Component Occ: 4195334 Segment Occ: 4194661
W58 - No end point matches the last start point segment occurrence The end closest to the last start point is the chosen start point Old - Table: 3 Component Occ: 4195082 Segment Occ: 4194661 New - Table: 3 Component Occ: 4195334 Segment Occ: 4194661
W59 - Components from spool 1 on sheet 2 were deleted Refer to sheet 4 for the updated spool 3
W60 - Cannot access material listing definition file W61 - Intergraph option 15 is 0 Spool number generation will be based on ISOGEN switch 39
W62 - The last component on sheet 1 was added prior to this extraction Partition: 8 Table: 3 Occ: 32 120
W63 - Cannot access Bending Parameters file W64 - Error in rotation matrix for pipe support. Pipe support in Model attachment number . W65 - Error opening PDME neutral file. File will not be created. . W66 - No component was encountered. The start point will be referenced for Structural Dimension. W67 - FrameWork Ascii file not found in the project directory. W70 - Outside diameter is zero in design database. No B.O.P. elevation reported at this time. Partition: 26 Table: 3 Occ: 52 208 When the outside diameter is zero in the design database, the outside diameter is not assigned in the physical data EDEN module. The software will not try to calculate the bottom of the pipe elevation at the component with zero outside diameter.
330
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages
Error Messages E2 - Error reading type 63 element from design file. The primary model file (the first model file input) does not contain the proper type 63 elements. Check the file with EDG and/or attempt to work in it in graphics.
E3 - Error opening input data file - pdsidf.dat. An error occurred when attempting to open the input file to the ISOGEN interface. Check to make sure that file pdsidf.dat exists in the default VMS directory.
E4 - Error retrieving project information E5 -Invalid primary model file - file does not exist E6 - No valid model design file specified. Of the list of design files input to the ISOGEN interface none were considered valid. Refer to error messages generated previous to this one for more detail.
E7 - Invalid extraction criteria is defined in Intergraph options block word 22. Valid values are 0 or 1. The extraction criteria defined in the options file INTERGRAPH_OPTIONS_BLOCK is invalid. Correct the options file.
E8 - No extraction criteria defined. No extraction criteria specified in the input file to the ISOGEN interface was found to be valid. Correct the inputs for identification of the lines to extract.
E9 - First header record must be a line name id (-6) record. Modify the PIPELI NE_HEADER table in the extraction options file. The first entry in the PIPELINE_HEADER table in the options file must always be a -6 record for the line name or line id. Correct the table in the options file.
E10 - Error opening intermediate data file. An error has occurred in creating an output file in the default directory. Make sure you have write access to it.
E11 - Broken pipes exceed the maximum allowed 100 occurrences. There are more than 100 pipes broken with the branch weld or pipe support for the extracted pipeline. Reduce the number of pipes broken and contact Intergraph to get the maximum allowed broken pipes increased.
E12 - Error retrieving type 63 elements. An error has occurred in retrieving the primary (first) model file type 63 elements. Check the file with EDG and make sure that you can work in the file in graphics.
Plant Design System (PDS) ISOGEN
331
Appendix: Warning and Error Messages E13 - Error opening Standard Notes Library. An error has occurred in opening the standard notes library that is specified in the primary model file type 63 data. Check that the library is properly attached with the RDB software.
E14 - Error opening spec database. An error has occurred initializing the spec database. Make sure that it is properly attached to the primary (first) model file using the RDB software.
E15 - Number of connect points exceeded internal limit of 2000 connect points. The maximum number of connect points per extraction is 2000. Break the line into two separate line names and re-extract the line as two separate isometrics.
E17 - Attempted to pop nonexistent tap stack entry. This message indicates an internal software problem that should be reported to Intergraph. When it does occur it should only be in connection with lines that contain tapped components.
E18 - Internal stack limit exceeded. This message indicates an internal software problem that should be reported to Intergraph. When it does occur it should only be in connection with lines that contain tapped components.
E19 - Error opening mto tables file. An error has occurred while trying to open the mto neutral file map that is specified in the options file. Check the file specification in the options file and make sure you have read access to the file.
E20 - Error reading mto tables file. An error has occurred while trying to read an entry in the mto neutral file map. Check that the table entries have the correct format.
E21 - Error reading database occurrence. An error has occurred in trying to read a record from the database base on a design file linkage. This error indicates potentially serious problems in the model. It is strongly recommended that the model be analyzed to determine the extent of the problem and to correct the situation.
E22 - Internal table lookup error for IDF record numbers. The record number taken from the PDS to ISOGEN symbol map for a component does not exist in an internal table. Check the PDS to ISOGEN symbol map to make sure that it contains only those record numbers allowed by ISOGEN.
E23 - Environment variable ISOOPTION not defined or file does not exist E24 - Error opening ISOGEN options file. The options file exists but it could not be opened. Make sure that proper access to the file exists.
332
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages E25 - Error reading iso extraction options file. An error has occurred while reading an entry in the options file. Make sure that options file entries have the proper format. If the return code is -998 then this error indicates that a options file table has exceeded the maximum allowable size. In this case you should reduce the number of table entries and contact Intergraph to get the table size increased.
E26 - Error opening PDS to ISOGEN symbol map. An error has occurred while opening the PDS to ISOGEN symbol map. Check the options file entry to make sure that the file is properly specified.
E27 - Error reading the PDS to ISOGEN symbol map - No valid entries defined in the table. The PDS to ISOGEN symbol was successfully read but no valid entries were found in the table.
E28 - Error opening valve/operator file. An error has occurred while opening the valve / valve operator symbol map. Check the options file to make sure that the file is properly specified.
E29 - Error reading size of valve/operator table. The first entry in the valve / valve operator table is a record that contains the number of rows and columns in the table. An error has occurred while attempting to read these values. Check that the format of the table is correct.
E30 - Valve/operator table is too large. The valve / valve operator table is larger than the maximum currently allowed by the software. Reduce the table size and contact Intergraph to get the maximum size increased.
E31 - Error reading valve/operator table values. An error has occurred while reading the body of the valve / valve operator table. This usually indicates that the table sizes defined in the first record of the file are incorrect.
E32 - Error initializing the piping design database E33 - No components were found that match the database search criteria. Either the line name substrings or line ID‘s that were specified in the input do not identify any lines that exist in the input model files. Check the inputs to make sure that they are correct and agree with the line name or attributes that make up the line id.
E34 - Invalid node or path for iso design file E35 - Internal error generating material pointer. An internal software error has occurred in generating a material pointer for an olet type component. If the software were allowed to continue the bill-of-material would be generated incorrectly. Contact Intergraph if you receive this error.
E36 - Internal error generating material pointer for downstream component. This error is the same as error number E35.
Plant Design System (PDS) ISOGEN
333
Appendix: Warning and Error Messages E37 - Transformed coordinate exceeds the maximum. This error is caused from a coordinate that is too large to pass to ISOGEN. All coordinates are transformed to the output coordinate system (as controlled by the Intergraph options block) and then converted to 1/100‘s of millimeters for ISOGEN. This value must fit within a 4 byte integer. This limitation results in a maximum coordinate value of 21,474 meters, or 70,450 feet or approximately 13.3 miles.
E38 - Internal error generating component item code. An error occurred while generating the item code for a stub (from a lap joint flange). Contact Intergraph if you get this error message.
E39 - Error accessing spec for implied item. An occurred while attempting to read the spec database entry for a stub. Check that the entry exists in the database. The stub spec entry should have the same lookup parameters as the flange except that the option code should be the flange option code plus 5000.
E41 - Error title block tables file E42 - Error opening project database E43 - Error reading database record E44 - Error reading database record E45 - Line is composed of multiple disconnected sections. This error results from trying to extract a pipeline that is either incomplete or incorrect and exists in the model in multiple unconnected pieces. It is not enough for all the segments to be connected. There must be components on top of the segments that are connected.
E46 - Line does not contain a valid traversal start-point. This error occurs when the ISOGEN interface finds it impossible to obey ISOGEN rules for traversal of the pipeline network. The only work-around is to split the pipeline into two smaller sections and then extract the sections individually.
E47 - Number of sections does not match specified value. For pipelines that are intentionally disconnected (for example, the line leaves the piping area, goes into the rack and then re-enters the area somewhere else) then you must specify the number of disconnected sections for the line in the Batch Data File. When the number of sections you specify does not match the number encountered in the model, this error occurs. Check the model to determine whether the Batch Data File or the model is incorrect.
E48 - Invalid section number. Invalid inputs have been passed to the ISOGEN interface for multi-section pipelines in pdsidf.dat. Report this error to Intergraph.
334
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages E49 - Component does not have an entry in the PDS to iso symbol map. (This error does not apply to ISOGEN.)
E51 - Induction bend stack limit exceeded. An internal data structure overflowed while processing a line containing induction bends. Report this error to Intergraph.
E52 - Error initializing DFPI Model number: $1 E53 - Error retrieving component from linkage: cannot determine cog for mto neutral file E54 - Error retrieving component from linkage: cannot process offset geometry component E55 - Error retrieving component from linkage: cannot process offset geometry component E56 - Error retrieving component from linkage: cannot process 180 degree turn E57 - Total number of segments exceeds the maximum number of segments E58 - Check the number of table entries specified against the actual number of table entries. Also, check the format of each table entry E59 - Error retrieving the graphic commodity library name E60 - Error initializing the piping project database E61 - Error accessing the standard note library name E62 - Error accessing the piping specification database name E63 - An internal table size limit has been exceeded E64 - No model was found with the specified discipline E65 - No components were found that match the database search criteria E66 - Unable to locate component’s user data E67 - Error initializing the project database E68 - Error reading model $1 from the database E69 - Error mounting design file $1$2 E70 - Error reading the last traversal start point Section Number: 1 Drawing Index Number: 150
Plant Design System (PDS) ISOGEN
335
Appendix: Warning and Error Messages E71 - Line extends over the maximum limit of 256 design file. E72 - The chosen starting point is not the last traversal start point Stop extraction because Intergraph option 68 is set to 1 Old - Table: 3 Component Occ: 4195082 Segment Occ: 4194661 New - Table: 3 Component Occ: 4195334 Segment Occ: 4194661
E73 - Error opening piping job specification table library . E75 - Error updating symbol library. E76 - Error stroking elements to ascii file. E77 - Error locating drawing file. E78 - Error locating index file. E79 - Error locating library path. E80 - Error - $1 not found. E81 - Error - Drawing and Index file must be specified. E82 - Error - Drawing, Index and Library files must be specified. E83 - Extraction Failed: Possibly caused by Olet owned by branch.
ISOGEN The error messages issued by ISOGEN (through IZOD2) are directed to two places. Errors issued by ISOGEN proper are directed to the ISOGEN message file. This file is either named in the options file or has the same name as the output iso file name with an extension of .msg. Errors generated by the Intergraph design file interface are directed to a file named IZOD2.ERR. When IZOD2 is run through the delivered command procedures then IZOD2.ERR is appended to any error message file created by the ISOGEN interface - pdsidf.
ISOGEN message file errors (35:2003 ) - WELD NUMBERS HAVE CAUSED DATA OVERFLOW An internal buffer for weld data has overflowed. Try a manual split of the pipeline into more sections.
(35:2004 ) - INPUT DATA OVERFLOW The pipeline is too big. It must be extracted in smaller sections.
336
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages (35:2005 ) - TEE OFF TEE GREATER THAN 20 DEEP This message indicates that the piping network being extracted contains branches which are too deeply nested for ISOGEN to handle. A branch off from the pipeline header is level 1. A branch off from the level 1 branch is level 2. A branch off from a level 2 branch is a level 3 branch. The maximum level branch that ISOGEN can handle is a level 20 branch.
(35:2007 ) - TEE IN SKEW ISOGEN has detected an internal inconsistency. Check the resulting drawing.
(35:2008 ) - DATA FAULT SKEW Same as 35:2007
(35:2009 ) - SKEW WITH NO CONTENTS Same as 35:2007
(35:2010 ) - FITTING WITH OFFSET NOT IN LINE WITH PIPE The offset of a fitting is not in line with an adjacent item. This is possibly a program or input data error. Check the resulting drawing.
(35:2011 ) - ANGLE FAIL Unacceptable pipeline direction detected. This is possibly a program or input data error. Check the resulting drawing.
(35:2012 ) - DATA FAULT ISOGEN detected a problem in some internal data. This is possibly a program or input data error. Check the resulting drawing.
(35:2012 ) - DATA FAULT, DOUBLEBACK PIPE Occasionally, doubleback pipe errors can be erroneously generated. This occurs when the extracted pipeline and the grid line or structural column are located in the same place. In this case, there will be one dimension to the structural element and the FAIL message will appear on the face of the iso. This can occur regardless if the isometric extracts with no other errors. In the following graphic, pipeline and Grid Line 3 are coincident with one another. This is interpreted by the ISOGEN software as a pipeline that doubles back on itself which results in the FAIL message on the isometric drawing.
Plant Design System (PDS) ISOGEN
337
Appendix: Warning and Error Messages If the reference point on the pipe resides in the same plane as the structural component or grid line, a FAIL message will appear on the isometric and the .err file will report a doubleback pipe error. This error is a result of the manner in which the ISOGEN software interprets the .idf file and should be ignored.
(35:2013 ) - DATA FAULT UP DOWN Same as 35:2012
(35:2014 ) - DATA FAULT EAST WEST Same as 35:2012
(35:2015 ) - DATA FAULT NORTH SOUTH Same as 35:2012
(35:2016) - DATA OVERFLOW, DRAWING REJECTED, TOO MUCH DATA, TRY SMALL ER SPLIT Too much data is being put onto too small a sheet. Either insert some manual pipeline splits or use a larger paper size.
(35:2017 ) - MESSAGE FAIL An error has occurred positioning messages on the drawing. This is caused by too many messages. Manually splitting the drawing might get around the problem.
(35:2018 ) - SHAPE FAIL Drawing generation has failed. It might succeed if viewed from another direction.
(35:2019 ) - DRAWING HEIGHT EXCEEDS ALLOWED 999 MM The maximum drawing height is 999 mm.
(35:2020 ) - TOO MANY COORDINATES IN FITTINGS Too many user-defined fittings have caused an internal array to overflow. Reduce the size of the user symbol library.
(35:2021 ) - TOO MANY FITTINGS Same as 35:2020.
(35:2023) - WARNING, PAPER SIZE > A1 OR AD - THIS MAY PRODUCE UNACC EPTABLE RESULTS. Too large a paper size might result in unacceptable drawings.
(35:2025 ) - CHECK ISOGEN considers that the drawing layout requires checking to make sure that it is satisfactory.
(35:2026 ) - FAIL ISOGEN considers that the drawing has failed in one of the stages of setting it up for plotting.
338
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages (35:1001) - OVER 200 ALTERNATIVE TEXT RECS. FOLLOWING DATA IGNORED. MORE THAN 200 TEXT RECORDS - DEFAULT TABLE USED. ISOGEN allows a maximum of 200 ATEXT‘s. Anything more will be ignored.
(35:1002 ) Same as 35:1001.
(35:1003 ) Same as 35:1001.
(35:1004 ) - FITTING NOT FOUND - DEFAULT SHAPE USED A fitting shape key cannot be located. The non-category component is place of the one specified.
(35:1009 ) - OVERFLOW IN DATA - PIPELINE REJECTED The pipeline is too big, causing an internal buffer to overflow. Manual splitting of the drawing or a larger sheet size might solve the problem.
(35:1015 ) - INVALID ITEM/ DESCRIPTION POINTER An mto pointer in the intermediate data file points to an item that doesn‘t exist. This is an Intergraph interface error.
(35:1016 ) - ITEM CODE WIDTH ERROR - APPENDED TEXT LOST An item code is larger the value specified in the ISOGEN options block.
(35:1018 ) - NO FITTING DETAILS EXIST FOR FITTING CODE An internal table lookup failed. This is an ISOGEN bug.
(35:1019 ) - FITTINGS OVERLAP WHICH CANNOT BE CUT BACK Coordinates of adjacent components overlap and the fittings can be trimmed (that is, a flanged valve).
(35:1020) - INSUFFICIENT LENGTH ON OVERLAPPING FITTINGS TO ALLOW CUTBA CK Adjacent fittings which can be trimmed overlap, but not enough for the required cutback.
(35:1021) - RUN ABORTED. THE WIDTH OR HEIGHT (EXCLUDING BORDERS, MATERIAL LIST, ETC) IS LESS THAN 50 MM. THIS IS NOT ENOUGH ROOM FOR THE IS OMETRIC. The drawing size is too small or the margins are too large.
(35:1022) - THE MATERIAL CODE IS TOO WIDE AND HAS BEEN CHANGED FROM — TO— The material code has been trimmed to the maximum allowable length.
(35:1026 ) - ERROR - UNABLE TO OPEN INTERMEDIATE DATA FILE Usually this indicates that you have forgotten to execute the ASCII to binary conversion program. The ASCII output generated by the ISOGEN interface must be converted to binary (using DATCON.COM) before executing IZOD2.
Plant Design System (PDS) ISOGEN
339
Appendix: Warning and Error Messages (35:1027) - WARNING - ILLEGAL SCALE FACTOR FOUND FOR LINE FLOW ARROW DEFAULT SCALE 8 USED The scale factor used for the pipeline flow arrow was set to an invalid value.
(35:1029 ) - WARNING - NO POSITION GIVEN FOR RECORD ID. This message indicates an error in the ISOGEN interface.
(35:1030 ) - ERROR - OVERFLOW IN TEXT POSITIONING ARRAY The maximum number of text positioning records has been exceeded in the intermediate data file. Reduce the number of drawing annotations.
(35:1031 ) - ERROR - OVERFLOW IN PIPELINE HEADER ARRAY The maximum number of pipeline header attributes has been exceeded. Reduce the numbers of entries in the options file PIPELINE_HEADER_TABLE.
(35:1032) - WARNING - ONLY NEW FORMAT SPEC BREAK ALLOWED ON SYSTEM ISOME TRICS. SET SPEC BREAK SWITCH TO NEW FORMAT. The ISOGEN option controlling the spec break format must be set to 1.
(35:1033) - ERROR - OVERFLOW IN PIPELINE HEADER DATA (PIPELINE REJEC TED) An internal array holding pipeline header data has overflowed.
(35:1034 ) - ERROR - OVERFLOW IN USER DEFINED SPOOL NAME ARRAY Too many spools have been defined in the isometric.
(35:1035) - WARNING - USER DEFINED SPOOL NAME EXCEEDS MAX OF 30 -ONLY F IRST 30 WILL BE OUTPUT AT FRAME POSITION. A user defined spool name is too large.
(35:1036) - WARNING - USER PREFIXED SPOOL NAME EXCEEDS MAX OF 30 -ONLY F IRST 30 WILL BE OUTPUT AT FRAME POSITION. A user prefixed spool name is too large.
(35:1037 ) - ERROR - OVERFLOW IN PIPELINE HEADER DATA ON SYSTEM ISO A system isometric is composed of too many pipelines.
(35:1038) - WARNING - USER DEFINED FITTING NEW KEY ALREADY EXISTS -OLD SH APE USED. The new shape key (skey) for a user defined symbol already exists within ISOGEN. Another symbol name must be chosen.
(35:1039 ) - ERROR - USER DEFINED FITTING OLD KEY NOT FOUND The old shape key (skey) for a user defined symbol does not exist. An existing symbol key must be used for the old skey.
340
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages (35:1040 ) - ERROR - USER DEFINED FITTING OLD KEY NOT SET A user defined symbol does not have an old shape key (skey) defined for it. User defined symbols must have an old or existing shape key as part of the definition of the new symbol.
(35:1041 ) - WARNING - USER DEFINED FITTING SPINDLE KEY NOT FOUND The spindle key specified for a user defined ISOGEN fitting cannot be found.
(35:1042 ) - ERROR - OVERFLOW IN USER DEFINED FITTING ARRAY An internal buffer has overflowed due to too many user defined components.
(35:1043 ) - ERROR - OVERFLOW IN FITTING SHAPE ARRAY An internal buffer has overflowed due to too many user defined symbols.
(35:1044) - WARNING - OVERFLOW IN USER POSITIONED TABLE FOR RECORD ID An internal buffer has overflowed due to too many user positioned title block records.
(35:1045) - ERROR - USER TEXT POSITIONED OUTSIDE DRAWING FOR RECORD ID - TE XT OUTPUT AT DRAWING ORIGIN. Bad user defined text coordinates have been specified.
(35:1048) - WARNING - ONLY 30 CHARACTERS ALLOWED IN PIPELINE NAME ON CUT PIPE SUMMARY. The pipeline name in the cut pipe summary report cannot exceed 30 characters.
(35:1052) - WARNING - OVERFLOW IN CUT PIPE REPORT ARRAY, ONLY 2000 ENTRIE S ALLOWED. The maximum cut pipe report size has been exceeded.
(35:1053) - WARNING - OVERFLOW IN USER DEFINED OFFSET FITTINGS, ONLY 100 ENT RIES ALLOWED. The maximum of 100 user defined offset fittings has been exceeded.
(35:1054 ) - WARNING - INSTRUMENT NAME RESTRICTED TO TWO LINES. Instrument tag numbers are restricted to two lines.
(35:1055 ) - WARNING - INSTRUMENT NAME EXCEEDS BALLOON SIZE. An instrument tag number is larger than the balloon size specified in the ISOGEN options block.
(35:1056 ) - ERROR - UNABLE TO OPEN USER FITTING FILE ISOGEN is unable to open the user defined symbol library. Check that the file exists and that ISOGEN has read access to it.
Plant Design System (PDS) ISOGEN
341
Appendix: Warning and Error Messages (35:1057) - ERROR - UNABLE TO POSITION SUPPORT/COMMENTS FROM COORDINATES GIVEN - ATTA HAS NOT BEEN DIMENSIONED, CHECK POSITION ON DRA WING. ISOGEN was unable to position a pipe support and its comment.
(35:1058) - WARNING - SPLIT POINT POSITIONED AT LINE/BRANCH END - SPLIT POINT IGNORED. A user defined split point was placed at an endpoint of the pipeline.
(35:1059) - WARNING - SPLIT POINT HAS BEEN POSITIONED INCORRECTLY - SPLIT POINT HAS BEEN REPOSITIONED. ISOGEN has rejected a user defined split point and repositioned it.
(35:1060) - WARNING - TAP OFF POINT CONNECTED TO STANDARD FITTING -TAP OF F SHOWN FROM FITTING CENTER. A tap is called for on a fitting that is not user defined. The tap point is taken to be the center of the fitting.
(35:1061) - WARNING - NO DIRECTION GIVEN FOR UNDEVELOPED FITTING TAP - D IRECTION ASSUMED FROM FITTING COORDINATES. ISOGEN cannot determine a direction of a fitting tap. A default direction is assumed. Cut lengths have been suppressed for pipe not in the material list, check isometric drawing.
(35:1062) - WARNING - PIPE CONFLICT (PIPE ON/OFF MATERIAL LIST) - CHECK CUT LI ST. ISOGEN is unable to position comments using the given coordinates.
() (NEW) - WARNING - BATCH INPUT FILE CREATED WITH EARLIER VERSION OF PD_ ISO BATCH INPUT FILE VERSION: BATCH DATA VER 4.0 Iso types are not represented in a batch input file created prior to PD_ISO version 5.00.00.05. You should recreate all batch input files using a PD_ISO version greater than 5.00.00.05.
(35:1099) (New) - ERROR - UNABLE TO POSITION COMMENT USING COORDINATES GIVEN COMMENT RECORD CO-ORDS ARE ***** ***** ***** CHECK LOCAT ION OF COMMENT ON DRAWING ISOGEN is unable to position ‘skey‘ using the given coordinates.
(35:1101) (New) - ERROR - UNABLE TO POSITION ’skey’ USING CO-ORDINATES GIVEN ’skey’ RECORD CO-ORDS ARE ***** ***** ***** CHECK POSITION ON DRAWI NG ISOGEN has received an unacceptable position for ‘skey‘ symbol.
(35:1104) (New) - ERROR - UNACCEPTABLE POSITION FOR ’skey’ SYMBOL ’skey’ RECOR D CO-ORDS ARE ***** ***** ***** SYMBOL NOT ON DRAWING
342
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages (35:1120) – WARNING – WELD NUMBER REPEATABILITY REQUESTED - NO HIGHEST WELD NUMBER RECORD(S) IN IDF - NO NEW WELD NUMBER(S) ALLOCATED USED Weld numbers are loaded from PD_Design when the ISOGEN Option Switch for Repeatability, 109, is set to 1. This message can be ignored.
Design File Interface Error Messages E1 - Error opening IZOD2 error file For some reason the error file created by the design file interface could not be opened. Check to make sure that you have write access to the current default directory.
E2 - Logical name ISOSEED is not defined or the iso seed file does not exist This error message can only be generated when a wildcard character is used in the output design file name. When this is the case then IZOD2 copies the seed file itself for each sheet that is generated. If the logical name is not defined or the file does not exist then the file cannot be copied.
E3 - Isodesign file not found This error message is issued when the output design file cannot be found. It can only be issued when the output design file name does not contain a wildcard character. In this case the output file must be created prior to executing IZOD2.
E5 - Error opening the isometric design file An error has occurred in opening the output iso design file for block i/o. Verify that the file is not already open, that you have write access to the file and that the file is a design file.
E6 - Error creating new iso design file An error has occurred in copying the seed iso file to a new iso design file. This error can only be issued when the output iso file name contains a wild card character.
E8 - Error opening the isometric design file This message is the same as E5, except that it is only issued when the iso design file name contains a wild card character.
E9 - Error writing graphics to design file This message indicates that a write operation to the design file could not be completed successfully.
Plant Design System (PDS) ISOGEN
343
Appendix: Warning and Error Messages
Batch Extraction Software Error Messages The following error codes may be reported in the batch extraction log file:
1 - Cannot Mount Batch Input File When this error is encountered, verify the following: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up.
2 - Error Initializing Project DBS Verify that you have access the Database Server.
3 - Error Initializing Piping DBS Verify that you have access the Database Server.
4 - Error Initializing Job Spec DBS Verify that you have access the Database Server.
5 - Error Reading Project Options (Default Set) System was trying to read the Project Options from the database server.
6 - Error Mounting Working Directory Probable Reason: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up.
7 - Error Changing To Working Directory Check Your directory privileges.
8 - Error Creating Temp Sub-Directory in Check Your directory privileges.
9 - Error Opening Batch Input file An error occurred when the batch command procedure attempted to open the batch job input file. Make sure that the file protections on the file are such that the command procedure can open the file.
10 - Record Too Long In Batch Input File See the log files for the specific record (line) is causing the problem.
11 - Batch Input File Version Invalid: The batch input file was created with a previous software version and the format is no longer valid.
344
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages 12 - Error Reading Batch Input File An error has occurred reading a record from the batch job input file. Look in the batch log file to determine the cause of the problem.
13 - Error Writing To Batch Input File The command procedure does not have write access to the output file directory that was specified by the selected default set. The process under which batch isos are executing must have write access to the output file directory. The line may have been successfully processed. See the log files to verify successful processing.
14 - Invalid Default Set Line In Batch Input file Refer to the logs file to determine cause of this problem.
15 - Error Changing To Master Work Directory Check Batch Login privileges for write access to the specified temp directory.
16 - Work Directory: Check Batch Login privileges for write access to the specified temp directory.
17 - Error Changing To Working Sub-directory Check Batch Login privileges for write access to the specified temp directory.
18 - Cannot Mount Output Iso Directory (ISOPATH) Most common reasons for this error: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up. Also, for interactive extraction, verify that the Environment variable ISOPATH, in control.sh is set to a valid directory.
19 - Error Moving To Output ISO Directory Check Batch Login privileges for write access to the output path specified by the selected default set.
20 - Error Changing To Directory Check Batch Login privileges for write access to the specified temp directory.
21 - Error Deleting Temp Sub-Directory Check Batch Login privileges for write access to the specified temp directory.
22 - Error Renaming pdsidf.dat Or pdsidf.err One or both of these files could not be renamed to isoname.dat or isoname.err.
23 - Error Starting ’Iso Interface’ Process When this error is encountered, check the following: 1. Verify that the ISO software has been installed.
Plant Design System (PDS) ISOGEN
345
Appendix: Warning and Error Messages 2. Verify that there are not too many process running on the workstation. 3. Verify that the system has enough memory.
24 - Error Returned From batch.sh See the log files for more information.
25 - Error Copying/Adding To pdsidf.dat The command procedure does not have write access to the output file directory specified in the selected default set. The process under which batch isos is executing must have write access to the output file directory.
26 - Error Opening/Reading/Closing sheets.tmp An error has occurred reading a record from the batch job input file. Look in the batch log file to determine the cause of the problem.
27 - Invalid Options String Check the default set through ‘Revise Default Set‘. There might have been an error setting up the Default Set when it was first defined.
28 - Error Writing To Batch Log The command procedure does not have write access to the output file directory specified in the selected default set. The process under which batch isos are executing must have write access to the output file directory.
29 - Error Opening/Closing Batch Log An error has occurred reading a record from the batch job input file. Look in the batch log file to determine the cause of the problem.
31 - Fatal Error In batch.sh When this error is encountered, check the following: 1. Verify that the ISO software has been downloaded. 2. Verify that there are not too many process running on the workstation. 3. Verify that the system has enough memory.
32 - Unable To Obtain Local Node Name Check to see if the workstation‘s node name has been correctly set up. Consult your system administrator.
33 - Error Creating Directory In Check Batch Login privileges for write access to the specified temp directory.
34 - Unable To Save Previous Files In Check Batch Login privileges for write access to the specified temp directory.
35 - Unable To Create Error Directory Check Batch Login privileges for write access to the specified temp directory.
346
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages 36 - Unable To Save In Error Directory Check Batch Login privileges for write access to the specified temp directory.
37 - Serious Interface Error Refer to the log files to determine the cause of the problem. The Problem Line should be run with Debug & Verify turned on. Contact Intergraph system support and send them all of the generated files.
38 - Error Returning From ’Iso Interface’ See the log files for more information.
42 - Error Starting batch.sh This error is usually caused by either a memory or input/output problem. When this error is encountered, check the following: 1. Verify that the ISO software has been downloaded. 2. Verify that there are not too many process running on the workstation. 3. Verify that the system has enough memory.
43 - Error in starting (exec call) batch.sh The batch.sh cannot be found. Verify that the PD_ISO environment variable in the control.sh has been defined properly. This file should be located in .\winapp32\ingr\pdiso\bin.
45 - Project Name Format Invalid In Batch Input file Check if the Project Name in Batch Input File is present or a valid one.
46 - Error In Executing Ksh Command An error occurred when starting another process. When this error is encountered, check the following: 1. Verify that the ISO software has been downloaded. 2. Verify that there are not too many process running on the workstation. 3. Verify that the system has enough memory.
48 - Run Aborted - Job Log May Have More Info See the log files for more information.
49 - Problem Line Not Processed After Restart of Iso Interface There was a problem with a line. The Iso Interface was re-executed to avoid a crash, the problem line was not processed after restarting the Iso Interface
50 - Error in calling system An error occurred when starting another process. When this error is encountered, check the following: 1. Verify that the ISO software has been downloaded. 2. Verify that there are not too many process running on the workstation. 3. Verify that the system has enough memory.
Plant Design System (PDS) ISOGEN
347
Appendix: Warning and Error Messages 51 - Could Not Open pdsidf.dat An error has occurred reading a record from the batch job input file. First, verify that the file exists. If the file exists, look in the batch log file to determine the cause of the problem.
52 - Could Not Open seed.dat An error has occurred reading a record from the batch job input file. First, verify that the file exists. If the file exists, look in the batch log file to determine the cause of the problem.
53 - Area Not Found In Project When this error is encountered, verify that: 1. the database server is running. 2. the area name has been altered in the batch input file. 3. the project area was not deleted before the batch job was submitted.
54 - Area/Line Not Found In ISO Database When this error is encountered, verify that: 1. the database server is running. 2. the line ID has not been altered in the Batch Input file. 3. the line was not deleted before the batch job was submitted.
55 - No Model Found for Area When this error is encountered, verify that: 1. the database server is running. 2. the model name has not been altered in the Batch Input file. 3. the model was not deleted before the batch job was submitted.
56 - Project Defaults Not Set When this error is encountered, verify that: 1. the database server is running. 2. the default set name has not been altered in the Batch Input file. 3. the default set was not deleted before the batch job was submitted.
57 - Error Reading Project Option File Names When this error is encountered, verify that: 1. the database server is running. 2. the default set name has not been altered in the Batch Input file. 3. the default set was not deleted before the batch job was submitted.
58 - Cannot Close File An error was encountered in closing a file.
59 - Unable To Process Area/Line Refer to the log files for more detailed information.
348
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages 60 - Error Reading Drawing Revision Records When this error is encountered, verify that: 1. the database server is running. 2. the line ID has not been altered in the Batch Input file. 3. the line ID name was not deleted before the batch job was submitted.
61 - Error Updating Drawing Record Verify that the database server is running.
62 - Defaults Set Not Found When this error is encountered, verify that: 1. the database server is running. 2. the default set name has not been altered in the Batch Input file. 3. the default set was not deleted before the batch job was submitted.
64 - Error Updating Drawing Revision Record Verify that the database server is running.
65 - Error writing to file The command procedure does not have write access to the output file directory specified in the selected default set. The process under which batch iso‘s is executing must have write access to the output file directory.
66 - Error Mounting Iso Seed Design File (ISOSEED) When this error is encountered, verify the following: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up.
67 – Iso Design File Name Not Defined There is no value in the Iso Dgn Name field for the drawing that is being extracted. The solution is to manually revise the drawing to enter a file name or to bulkload the line again.
68 - Error Initializing Microstation message The First Design File in the Current Area being processed could not be initialized by Microstation.
69 - Error Mounting Iso Plot File (ISOPLOT) When this error is encountered, verify the following: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up. 3. Check if the /etc/exports file of the remote node contain the path to be mounted.
70 - Error Exporting Environment Variable Check the amount of available workstation memory.
Plant Design System (PDS) ISOGEN
349
Appendix: Warning and Error Messages 71 - Error Mounting Output Directory When this error is encountered, verify the following: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up.
72 - Error Mounting Border File (ISOBORDER) When this error is encountered, verify the following: 1. Check if the Node/path/file exists. 2. Find out if the remote node is up.
73 - Unexpected Error From JOBCTL An error has occurred in creating input for the ISOGEN interface using data from the batch job input file. This error should only occur if the batch job input file is out of sync with the Batch Data File. The two files can get out of sync if lines are deleted after they have been added to a batch job input file.
75 - Abnormal Database Error (See System Log) See the Log files for more information.
99 - Fatal Error while running the Batch Job: batch.sh See the Log files for more information.
101 - Intermediate File Does Not Exist A fatal error has occurred in the generating the intermediate file from the ISOGEN interface. Look in the error log produced by the interface to determine the cause of the problem.
102 - Error Generating Binary IDF File An error has occurred in converting the intermediate data file produced by the ISOGEN interface to binary. This usually indicates an earlier problem in the ISOGEN interface. Look at the error log produced by the interface to determine the cause of the problem.
103 - Isometric Seed File Does Not Exist The isometric seed file specified in the Batch Data File does not exist. Either create the seed file or change the file specification in the Batch Data File.
104 - Error Running ISOGEN Interface (ISOGEN) A fatal error running ISOGEN has occurred. Look at the error log produced by the ISOGEN interface and also at the ISOGEN message file. Error messages generated by the Intergraph design file interface will be written to the error log. Error messages generated by ISOGEN will be written to the message file.
110 - Error Splitting The MTO Neutral File When the ISOGEN interface produces an mto neutral file, the batch software automatically splits it into several files, each containing the mto data for a single sheet. This error is generated when splitting up the neutral file fails. Make sure that your MTO record map maps component occurrence numbers into the neutral file.
350
Plant Design System (PDS) ISOGEN
Appendix: Warning and Error Messages 115 - Error Generating Title Block Text An error has occurred while attempting to determine which segment attributes should be placed in the title block of each isometric sheet. Make sure that you have properly set your Title Block Table File. Contact Intergraph for help if you cannot solve the problem.
120 - Iso Sheets File Not Found or Unreadable An error occurred when the batch command procedure tried to open the file that contains the number of isometric sheets generated by ISOGEN. This error indicates an Intergraph software problem.
121 - Error Reading Iso Sheets File An error occurred while trying to read the number of iso sheets from a file produced by ISOGEN. This error indicates an Intergraph software problem.
122 - Error Updating Number Of Sheets Error updating number of sheets An error occurred while updating the number of drawing sheets for a multi-section pipeline. Refer to the batch (DCL) log file to determine the cause of the problem.
123 - Error Opening STIB Input File An error occurred while trying to create an input file for STIB. This error probably indicates an Intergraph software error.
124 - Error Filling Out Title Block By STIB An error has occurred while STIB was attempting to fill out the drawing title block. Make sure that your seed iso design file has plenty of space for both the drawing graphics and the text that is inserted by STIB. Also make sure that the disk holding the batch run directory has plenty of contiguous space. STIB creates a 500 block temporary work file that must be contiguous.
125 - Error Getting Previous Manual Details An error occurred while attempting to move manual details from a previous version of a drawing to the latest. Refer to the batch (DCL) log file to determine the cause of the problem.
130 - Plot Software Does Not Exist Could not find the Plot Software (IP_IPLOT). If the plotting software is not loaded, set the plot option to No and rerun the iso. If attempting to perform a batch process, this error could also indicate that you do not have access to the requested queue. Verify that the requested queue name is available to the processing node‘s batch login.
131 - Plot Seed File Does Not Exist The isometric seed file specified in the Batch Data File does not exist. Either create the seed file or change the file specification in the Batch Data File.
132 - Error Opening Or Writing Plot Job File An error has occurred creating a command procedure to launch an IPLOT plot job. This error is probably due to an Intergraph software problem. Refer to the batch (DCL) log file to determine the cause.
Plant Design System (PDS) ISOGEN
351
Appendix: Warning and Error Messages Error occurred while creating the Plot Meta File: Check if there is enough memory space.
133 - Error Generating Plot Meta File Error occurred while creating the Plot Meta File. Verify that the system has enough memory.
134 - Error Submitting A Job To ISO_PLOT An error occurred submitting a job to launch an IPLOT plot. Make sure that the plot queue ISO_PLOT is properly set up.
135 - Batch Submitting Error Code: 0x10000XXX An error has occurred in submitting a batch job where XXX is an error return code listed in the ˜0batch0batchapi0batchapi.h file. For example, the return code 0x10000025 is defined as BATCH_ERROR_NO_ACCOUNT_MAPPING (025) IN THE ntbatchapi.h file. In this case, you would verify that your account is mapped correctly in the Intergraph Batch Manager. If the account password has been changed and the password in Account Mapping has not been updated since the account was mapped to the valid user, the batch job will still be reported as, Batch Job Submitted Successfully. The invalid password is not be detected by Batch Services until the batch job is started.
352
Plant Design System (PDS) ISOGEN
APPENDIX B
Appendix: Alias ISOGEN Tables Tables of Intermediate File Records Record ID No.
Purpose
-1
Overflow text record
Remarks
(Used with all types of text records)
-3
Text for Isometric Title Block
-4
Special key input (That is, in-line items given a -4 key is treated in the special way that Alias instruments are.)
-5
Spare
-6
Pipeline Reference
-7
Spare
-8
Revision Identifier
-9
Project Identification (Code Number)
-10
Batch Reference (Zone Name)
-11
Piping Specification Name
-12
Nominal Pressure Rating (Class)
-13
Line Type Identifier
-14
Date of Data Transfer
-15
Insulation Specification
-16
Tracing Specification
-17
Painting Specification
-18
Spare
-19
Spare
-20
Item Code
-21
Item Description
-22
Tag Number and Hanger Name
-23
Hanger Tail Reference (ATTA CREF)
Plant Design System (PDS) ISOGEN
Pipeline Header Information
353
Appendix: Alias ISOGEN Tables Record ID No.
Purpose
-24
Spare
-25
New Pipeline Reference (Used to indicate start of new pipeline on multi-pipeline plot.)
-26
Specification Change Identifier
-27
Spare
-28
Spare
-29
Spare
-30
Connection Comment - Continued ON
-31
Connection Comment - Connected TO
-32
HCON/TCON = OPEN (Not used by PDS)
-33
HCON/TCON = CLOS
Remarks
End Connection Type (such as a cap, blind plug, etc.) -34
HCON = VENT (Not used by PDS)
-35
HCON = DRAN (Not used by PDS)
-36
Unset HREF or IREF Indicator (But only when HCON or TCON is not set to OPEN, CLOS, VENT, DRAN or SCRD) -36 is used to disable ―No Connection ...‖ notes from being displayed. (See also Intergraph Option 6)
-37
Comment on spool, fitting, or hanger
-38
Drawing Split Point Indicator ( + + + + )
-39
Spare
-40
Skewed spindle directions or skewed ecc reducer flat directions
-51 -52 -53
This block (-51 to -60)
-54 -55 -56 -57 -58
RESERVED
is reserved for internal Isodat processing.
-59 -60
354
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables Record ID No.
Purpose
-67
Intergraph Weld Number Record Key
-80 to -90
User-defined Bill of Material Records
-100
Intermediate data transfer file name
-101
Schema plot file name (For drug frame)
-102
Isometric plot file prefix
-103
New/alternative symbol file names
-104
Material Control file name
-105
Message file name (Error and plot confirmation messages)
-106
PDMS error system file name
Remarks
(This is not user-definable) -107
PDMS > ISOGEN (This is not user-definable)
-108
Printed Parts List file name
-109 to
Spare
-200 -201
-500
Reserved for ATEX - foreign language or other alternative text on isometric (Title Information, End Conditions, etc.) (Full details are available on a separate list)
-501 -502
Reserved for new or alternative to fitting shape definitions. (Full details to be provided later.)
Plant Design System (PDS) ISOGEN
355
Appendix: Alias ISOGEN Tables
Record Identification Numbers Spool and In-Line Fitting Records Please refer to the appendix, ISOGEN SKEY Dimensions, for further details. Spool /Fitting Type
Record ID Numbers
Remarks
In Leg
First Branch Leg
Second Branch Leg
Out Leg
Bend
30
-
-
31
Elbow
35
-
-
36
O'let
40
41
-
42
Plus a 0 record
Tee
45
46
-
47
Plus a 0 record
Cross
50
51
52
53
Plus a 0 record
Reducer (Con/Ecc)
55
-
-
-
Plus a 0 record
Tee Reducer (Con/Ecc)
60
61
-
62
Plus a 0 record
Reducing Flange
65
-
-
-
Plus a 0 record
Tee Bend/Elbow
70
71
-
72
Plus a 0 record
Angle Valve
75
-
-
76
3 Way Valve
80
81
4 Way Valve
85
86
Instrument
90
91
82
Plus a 0 record
87
88
Plus a 0 record
92
93
A straight through type instrument only has 90 & 93 record ID Numbers. Instrument Dials only have a 90 record.
356
Pcom (Misc. Pipe Component)
95
-
-
96
Pipe (Tube)
100
-
-
-
Fixed Length Pipe
101
-
-
-
Pipe Block (Fixed Length)
102
-
-
-
Pipe Block (Variable Length)
103
-
-
-
Flange
105
-
-
-
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables Spool /Fitting Type
Record ID Numbers
Remarks
Lap Joint Stub End
106
-
-
-
blank Flange (Blind)
107
-
-
-
Gasket
110
-
-
-
Bolt
115
-
-
-
Weld
120
-
-
-
Cap
125
-
-
-
Coupling
126
-
-
-
Union
127
-
-
-
Valve
130
-
-
-
Trap
132
-
-
-
Vent
134
-
-
-
Filter
136
-
-
-
User Positioned Comment
149
-
-
-
Pipe Hanger/Support
150
-
-
-
180 to 199 inc.
-
-
-
0
-
-
-
999
-
-
-
Bore Record End of File Marker
Used to define position
Reserved for internal ISODAT processing
Option Switches This is a brief summary of the option switches operated by the 140-word options block. Recommended default values for each option are shown, together with either a list of alternatives or an indication of appropriate data values. Full details (where appropriate) can be found in Chapters 3 or 4. Any standard settings (Std. is =) indicated on the following pages are default settings from Alias; these settings are required to produce a 'STANDARD' isometric drawing. You can make various alternative settings to meet specific project requirements. For any switch with multiple switch settings−such as A, B, C, D, E−the switches read from right to left, as shown below. Leading 0s (zeros) can be omitted, but trailing 0s must be included.
The following ISOGEN options must not be changed from their delivered settings.
Plant Design System (PDS) ISOGEN
357
Appendix: Alias ISOGEN Tables ISOGEN Option Number
Function
1
Plot length control
7
Drawing control
31
Iso output file
32
Plotter scale factor
33
Pipe detailed
43-51
Wastage factors
52
Equipment trim drawings
55-57
Diagnostic printing
58
Clear screen
69
Terminal type identification
79
Site assembly identification
125
Reserved
126
Reserved
129
Interactive editing
131
Test parameter
See Also Option Switches 02-06 (on page 359) Option Switch 8 (on page 362) Option Switch 9 (on page 364) Option Switches 10-19 (on page 365) Option Switches 20-29 (on page 367) Option Switches 30-38 (on page 372) Option Switch 39 (on page 373) Option Switch 40 (on page 376) Option Switch 41 (on page 377) Option Switch 42 (on page 378) Option Switches 40-59 (see "Option Switches 40-49" on page 379) Option Switches 60-65 (on page 381) Options Switches 67-72 (see "Option Switches 67 - 72" on page 383) Option Switch 73 (on page 383) Option Switch 74 (on page 385) Option Switch 75 (on page 386) Option Switch 76-79 (see "Option Switches 76 - 79" on page 388) Option Switches 80-89 (see "Option Switches 80 - 89" on page 389) Option Switches 90-99 (on page 392) Option Switches 100-109 (on page 393) Option Switches 110-119 (on page 395) Option Switches 120-140 (on page 397)
358
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Option Switches 02-06 Isometric Facility
Word #
Cutting List
2
Switch Position A
B
C
D
E Cut Marks
3
File Marker or Data
Parameter Value Options
0
Suppress cut pipe list and cut pipe numbers. (default)
1
Generate cut piece numbers and a cut pipe list.
2
Cut piece numbers start at 1 on each sheet.
0
Use old style (limited information) cut piece list. (default)
1
Use new style (full information) cut piece list.
0
Generate numeric cut piece identifiers. (default)
1
Generate alphabetic cut piece identifiers.
0
Generate standard cut lengths only. (default)
1
Generate supplementary output of cut lengths in decimal inches format in the REMARKS column of the new style cut piece list. This setting only applies when using Imperial Units.
0
Calculate branch cut length to actual branch connection point.
0
Std. is = 0 for no cut marks. or set:
Plant Design System (PDS) ISOGEN
1
For plotted cut marks. (Position relative to drawing frame to be based upon margin dimension.)
3
For characters 3.5 mm high.
4
For characters 4.2 mm high.
5
For characters 4.9 mm high.
1
Calculate branch cut length to centerline of main pipeline in all situations.
359
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data
B
C
Isometric Facility Dimension LineStandout Distance
Word # 8
Switch Position
Parameter Value Options
2
USA for date plotted in the format: 04/14/88
3
For no plotted date.
0
Use the date from the IDF file record (-14).
1
Use the computer system date (taken at run time).
0
Output 2-digit year.
1
Output 4-digit year.
File Marker or Data Parameter Value Options Data < 11
Default to use Standard Dimension Line Standouts (see below). Only used if options 40 and 118 are not set.
Data > 11
Where a value is set to the required basic standout distance in whole mm‘s. Standard Dimension Line Standouts: For SMALL drawing text, set ISOGEN Word 4 to 1. A) String/Composite Dimension Standout = 12mm. B) Messages/Support & Reference Dimension Standout = 6mm C) Overall Dimension Standout = 18mm For MEDIUM text, set Word 4 to 0. A) String/Composite Dimen. Standout = 14mm. B) Messages/Support & Reference Dimension Standout = 7mm C) Overall Dimension Standout = 21mm
360
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options For LARGE text, set ISOGEN Word 4 to 2. A) String/Composite Dimen. Standout = 16mm. B) Messages/Support & Reference Dimension Standout = 8mm C) Overall Dimension Standout = 24mm For EXTRA LARGE text, set Word 4 to 3. A) String/Composite Dimen. Standout = 18mm. B) Messages/Support & Reference Dimension Standout = 9mm C) Overall Dimension Standout = 27mm For EXTRA LARGE text, set Word 4 to 4. A) String/Composite Dimen. Standout = 20mm. B) Messages/Support & Reference Dimension Standout = 10mm C) Overall Dimen. Standout = 30mm For EXTRA LARGE text, set Word 4 to 5. A) String/Composite Dimen. Standout = 22mm. B) Messages/Support & Reference Dimension Standout = 11mm C) Overall Dimension Standout = 33mm For EXTRA LARGE text, set Word 4 to 3. A) String/Composite Dimen. Standout = 18mm. B) Messages/Support & Reference Dimension Standout = 9mm C) Overall Dimension Standout = 27mm For EXTRA LARGE text, set Word 4 to 4. A) String/Composite Dimen. Standout = 20mm. B) Messages/Support & Reference Dimension Standout = 10mm C) Overall Dimen. Standout = 30mm
Plant Design System (PDS) ISOGEN
361
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options For EXTRA LARGE text, set Word 4 to 5. A) String/Composite Dimen. Standout = 22mm. B) Messages/Support & Reference Dimension Standout = 11mm C) Overall Dimension Standout = 33mm
Option Switch 8 Isometric Facility Dimension LineStandout Distance
Word # 8
Switch Position
File Marker or Data Parameter Value Options Data < 11
Default to use Standard Dimension Line Standouts (see below). Only used if options 40 and 118 are not set.
Data > 11
Where a value is set to the required basic standout distance in whole mm‘s. Standard Dimension Line Standouts: For SMALL drawing text, set ISOGEN Word 4 to 1. A) String/Composite Dimension Standout = 12mm. B) Messages/Support & Reference Dimension Standout = 6mm C) Overall Dimension Standout = 18mm For MEDIUM text, set Word 4 to 0. A) String/Composite Dimen. Standout = 14mm. B) Messages/Support & Reference Dimension Standout = 7mm C) Overall Dimension Standout = 21mm
362
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options For LARGE text, set ISOGEN Word 4 to 2. A) String/Composite Dimen. Standout = 16mm. B) Messages/Support & Reference Dimension Standout = 8mm C) Overall Dimension Standout = 24mm For EXTRA LARGE text, set Word 4 to 3. A) String/Composite Dimen. Standout = 18mm. B) Messages/Support & Reference Dimension Standout = 9mm C) Overall Dimension Standout = 27mm For EXTRA LARGE text, set Word 4 to 4. A) String/Composite Dimen. Standout = 20mm. B) Messages/Support & Reference Dimension Standout = 10mm C) Overall Dimen. Standout = 30mm For EXTRA LARGE text, set Word 4 to 5. A) String/Composite Dimen. Standout = 22mm. B) Messages/Support & Reference Dimension Standout = 11mm C) Overall Dimension Standout = 33mm For EXTRA LARGE text, set Word 4 to 3. A) String/Composite Dimen. Standout = 18mm. B) Messages/Support & Reference Dimension Standout = 9mm C) Overall Dimension Standout = 27mm For EXTRA LARGE text, set Word 4 to 4. A) String/Composite Dimen. Standout = 20mm. B) Messages/Support & Reference Dimension Standout = 10mm C) Overall Dimen. Standout = 30mm
Plant Design System (PDS) ISOGEN
363
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options For EXTRA LARGE text, set Word 4 to 5. A) String/Composite Dimen. Standout = 22mm. B) Messages/Support & Reference Dimension Standout = 11mm C) Overall Dimension Standout = 33mm
Option Switch 9 Isometric Facility Dimensions On Drawing
Switch Word # Position 9
A
B
C
D
File Marker or Data Parameter Value Options 0
Std. is = 0 for isometric with dimensions.
1
For isometric without any dimensions.
2
For Support dimensions only.
3
For COMPOSITE dimensions.
4
FULL STRING dimensioning, ALL components dimensioned
0
Do not include gasket thickness in flanged component dimension
1
Include gasket thickness in flanged component dimension.
0
Dimension displayed in a broken dimension line.
1
USA-style dimensioning, dimension displayed above dimension line.
0
Dimensions turned 90 degrees, rather than being arrowed out
1
0 and 1 at Beta test stage Feb. 2001
E
364
0
Normal component dimensions
1
Dimensions to show additional allowances
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Switch Word # Position
File Marker or Data Parameter Value Options
F
G
H
I
2
Dimensions to include additional allowances (Spool isometrics only)
0
Combined pipe and bend dimensions
1
Separate pipe and bend dimensions
0
For single dimensioning
1
For double dimensioning (Imperial and metric)
0
Angle/3 Way/4 Way valves and instruments dimensioned using message
1
Angle/3 Way/4 Way valves and instruments dimensioned normally
0
Full jacket dimensioning
1
Jacket dimensioning suppressed
Option Switches 10-19 Isometric Facility Drawing Margin
Word #
Switch Position
File Marker or Data Parameter Value Options
10
5
Std. is = 5 mm for left hand margin dimension. Or set:
data 11
5
Alternative value for left margin. Std. is = 5 mm for right hand margin dimension. Or set:
data 12
5
Alternative value for right margin. Std. is = 5 mm for top margin dimension. Or set:
data
Plant Design System (PDS) ISOGEN
Alternative value for top margin.
365
Appendix: Alias ISOGEN Tables
Isometric Facility
Word # 13
Switch Position
File Marker or Data Parameter Value Options 5 data
Drawing Size
14
2
Std. is = 5 mm for bottom margin dimension. or set: Alternative value for bottom margin. Std. is = A2 paper size (420 x 594 mm) Or set:
1
For A1 paper size (594 x 841 mm)
3
For A3 paper size (297 x 420 mm)
4
For A4 paper size (210 x 297 mm) Or set:
5
For AD paper size (22‖ x 34‖)
6
For AC paper size (17‖ x 22‖)
7
For AB paper size (11‖x17‖)
8
For AA paper size (8.5‖ x 11‖)
9
For AE size drawings (33‖ x 44‖)
10
For A0 size drawings (841 mm x 1189 mm) Or set:
15
data
New value for drawing height in mms
16
data
New value for drawing width in mms Non-standard drawing sizes are controlled by Option Switches 15 and 16, which, if set, override any setting in Option Switch 14.
Flow Arrows
17
0
Std. is = 0 for fluid flow arrows on selected in-line components. Or set:
Frame Control
18
1
To suppress fluid flow arrows.
0
Std. is = 0 for standard Isoplot drawing frame. Or set:
1 Falling Lines (Slope)
366
19
To suppress standard Isoplot drawing frame. Used to control how falling sections of pipeline are actually to be defined on the iso.
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options 0
Std. is = 0 to define falling sections of pipeline in terms of an angle (i.e., FALL 1.5°). Or set:
1
To define falling sections in terms of a falls ration (i.e., FALL 1:60).
2
To define falling sections in terms of a falls percentage (i.e., FALL 2%). This value is always output as a whole percentage.
3
To define falling sections in terms of grads (i.e., FALL 1 GRAD).
4
To define falling sections in terms of an incline (i.e., FALL 3/16' PER FT).
5
To define falling sections in terms of an incline (i.e., FALL 16 MM PER M).
6
To suppress falling line indication.
Option Switches 20-29 Isometric Facility Sloping Pipeline
Word #
Switch Position
File Marker or Data Parameter Value Options
20
Indication Limit
Plant Design System (PDS) ISOGEN
5
Used to define the falls definition cut off point (i.e., to control what degree of steepness should be treated as a fall and what should not). In this case, the section concerned is surrounded by the normal box enclosure.
367
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options data
Std. is = 5 degrees or ratio of 1:11 or 9 percent or 5 gradients or 1" per ft (Imperial) or 88 mm per meter depending upon which key word is set as the first parameter. (All these are approx. = to 5°.) or set: To the required value for the desired cut-off value of the previous switch (19). If the correct parameter for Switch 19 is set then:For 9 degree. cut-off, enter 9. For 1:6 cut-off, enter 6. For 16% cut-off, enter 16. For 10 grad. cut-off, enter 10. For 2" per foot cut-off, enter 2. For 166 mm per cut-off, enter 166. The default cut-off value is 5 ° or its equivalent as indicated above.
Isometric Type
21
0
Std. is = 0 for combined isometrics (Fab and Erec information.). Or set:
Loose Flange And Field Fit Weld Allowance
1
For Erection isometrics only.
2
For Fabrication isometrics only.
6
For individual Spool isometrics.
7
For no isometrics from an ISOGEN run.
22
Used to control the amount of extra pipe that is added to both the Cut Length dimensions and the Material List at Loose Flange and Field Fit Weld (FFW) positions. A/B/C
data
Value used for field welds Standard is 150 mm. Values are in mm.
368
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options
D/E/F
data
Value used for offshore welds Standard is 0 mm. Values are in mm.
G/H/I
data
Value used for shop weld allowance Standard is 0 mm. Values are in mm. This value is only applied to Shop Test Welds. Intergraph Option Switch 62 (Weld Number Display), position C, must be set to 1 for ISOGEN 22 to work properly.
Plotted Material List Control
23
This option allows control of the material list on the iso and the style of the material control file. (Material control file generation controlled by Intergraph Option 1.) A
B
C
D
0
Material list plotted
1
Material list not plotted
Blank or 0 No action 1
This is a sorted STYLE 1 list. Individual part numbers and Pulled Bends are given a ‗U‘ number . (See ATEXT -356) Gaskets and Bolts are accumulated. Welds are given W or B numbers. (See ATEXT -357 & -358)
2
This is a sorted STYLE 2 list . Individual part numbers and Pulled Bends are given a ‗U‘ number. (See ATEXT -356) Gaskets and Bolts are accumulated. Welds are given W or B numbers. (See ATEXT -357 & -358)
Blank or 1 STYLE 1 Material list (default) 2
STYLE 2 Material list
3
STYLE 3 Material list
Blank or 0 Old Style of Material Control File (default) 1
Plant Design System (PDS) ISOGEN
New Style of Material Control File.
369
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position E
File Marker or Data Parameter Value Options Blank or 0 Sectionalized form of Material List with title for each group of components (default). 1 Continuous form of Material List. No headings other than those set in the Material Definition file by the user. (No separate FAB / EREC sections. No component subgroup headings.) Components are continued to be sorted into Groups. Horizontal list is drawn across the Material List after each group of components. Category identifiers (ATEXT -376, -377, -378) and Group identifiers (ATEXT -307, -308, - 309, -311 through -315) are both available for use in any user-specified column position.
Material List Type/Length Units
Material List Position & Title Block Position
24
25
Metric or Imperial Units used with this option are governed by ISOGEN option 41, Dimensional Units. A
0
Produce a material list on a per drawing basis with length units to the nearest 1/10 meter or 1/10 foot (default). This position must be set to 0.
B
0
Output pipe length in a x.xM or x.x' format. (for example, 10.4M or 10.4') (default)
1
Output pipe length in a x MM or x' x" format. (for example, 1040 MM or 10' 5")
2
Output pipe length in a x.xxx M or x.xxx' format. (for example, 1.040 M or 10.510')
0
Material List on left side of isometric drawing. The title block is located in the bottom right corner of the drawing area.
1
Material List on right side of isometric drawing. The title block is located in the bottom right corner of the drawing area.
0
Place title block in the bottom right corner of the drawing area. (default)
1
Place Title block at the bottom of the material list.
2
Do not place a title block.
A
B
370
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility
Word #
Switch Position
File Marker or Data Parameter Value Options Check ATEXTs -317 and -318. If they are not blank and have not been positioned by the user, the Cut List SUMMARY is positioned above the title block.
Material List Descriptions
26
A
B
Material List Text Size
27
0
Std. is = 0 to have item descriptions listed or set:
1
To suppress item descriptions.
0
Std. is = 0 to have blank lines inserted following single line Material List entries.
1
Suppress blank lines following single line entries. This setting may make the Material List shorter.
0
For characters 2.5 mm high (default setting).
1
For characters 2.1 mm high.
2
For characters 2.8 mm high. (Only controls text on isometric picture.)
3
For characters 3.5 mm high.
4
For characters 4.2 mm high.
5
For characters 4.9 mm high. Setting 5 is not recommended.
Material List Item Code Length
28
Material List Line Spacing
29
data
Controls number of characters in item code. The minimum item code length is 1 character.
100
Controls line spacing on material list. Std. is = 100. or set:
data
Plant Design System (PDS) ISOGEN
Alternative value to increase/decrease in the ratio data/100/ (i.e., 105 to obtain 105/100 increase).
371
Appendix: Alias ISOGEN Tables
Option Switches 30-38 Isometric Facility Material List Output
Picture Scale
Word #
Switch Position
File Marker or Data Parameter Value Options
30
Controls how overflow material list are split. 0
For automatic overflow onto a second material list width plotted alongside the normal one. (default)
1
Creates an isometric that contains only the material list extension.
2
Creates an overflow iso for the material list. The second iso is given the same number as the first sheet, but appends a suffix (A, B, C, etc.).
10
Same as 0 except that DRG 1 of 1 is added to single sheet isometrics.
11
Same as 1 except that DRG 1 of 1 is added to single sheet isometrics.
12
Same as 2 except that DRG 1 of 1 is added to single sheet isometrics.
34
Used to enlarge or diminish the isometric picture image size while keeping the frame size constant. Size alters in proportion to the number entered and 100. 100
Std. is = 100. or set:
data Drawing and Material List Reserved Area
35
Used to define a section along the bottom of the isometric sheet that is to be reserved for user use in both the Drawing Area and Material List Area. A/B/C
372
Alternative value to increase/ decrease picture scale in the ratio to data/100.
data
Enter a value in mms equal to the depth of reserved area that is required along the bottom of the iso above the lower frame line in the drawing area. When specified, this area always is left blank.
Plant Design System (PDS) ISOGEN
Appendix: Alias ISOGEN Tables
Isometric Facility Material List Output
Word #
Switch Position
File Marker or Data Parameter Value Options
30
Controls how overflow material list are split. D/E/F
data
Enter a value in mms equal to the depth of reserved area that is required along the bottom of the iso above the lower frame line in the Material List area. When specified, this area is always left blank. (Measured from the same place as Drawing Reserve Area) Checks to make on ATEXT -317 and -318. If they are not blank and have not been positioned by the user, the CL SUMMARY is positioned above the Material List Reserve Area.
1
Drawing Stacking Arrangement
Drawing Split Control
Std. is = 1 for 1 frame high stacking.
36
data
37
0
Std. is = 0 for plotting along the paper.
1
For plotting across the paper.
38
Alternative value for variations on this (i.e., 2 for 2 frame high stacking, or 3 for 3 frame high stacking , etc.).
Controls drawing. splitting (i.e., the average amount of information to be shown on one drawing). 100
Std. is = 100 for 100%.
data
A number >100 to increase content or 100 to increase the branch scale. Value
View more...
Comments
