Reference Guide
PDS ISOGEN
March 2000
DEA5040B0
For PDS version 06.04.01.**
All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties.
The information and the software discussed in this document are subject to change without notice and should not be considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility 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.
Trademarks
Intergraph is a trademark of Intergraph Corporation. MicroStation is a trademark of Bentley Systems Inc., an Intergraph affiliate.
Copyright
2000 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 and trade secret law and may not be provided or otherwise made available without proper
authorization.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of Commercial Computer Software — Restricted Rights at 48 CFR 52.227-19, as applicable.
Unpublished — rights reserved under the copyright laws of the United States.
Intergraph Corporation
If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’s products, services, and direction. Our web address is:
http://www.intergraph.com
Telephone Support
All Intergraph products are delivered with a 30-day warranty for full coverage of physical media.
In the United States, call Intergraph’s standard support number at 1-800-633-7248 from 7:00 AM to 7:00 PM CST, Monday through Friday, except holidays.
If you are outside of the United States, please call your local Intergraph office. The most up-to-date list of international offices and distributors is available on the web at http://www.intergraph.com.
Please have the following information available when you call: The product’s serial number. This can be found on the license agreement or by using the About command in the product. Your name and telephone number.
The product’s name.
Your CPIN number and service number. A brief description of the problem.
Intergraph Directory
The following numbers are only valid in the United States unless otherwise indicated. If you are outside the United States, please call your local Intergraph office.
Intergraph General Information
U.S. — 1-800-345-4856 Canada — 1-800-461-5297 All countries — 1-256-730-2000
Customer Response Center (U.S. Only)
Customer Support — 1-800-633-7248
U.S. Customer Care Center — 1-888-779-3824 FAX — 1-800-239-2972
Training Registration (U.S. Only)
1-800-240-3000
Regional Sales Information (U.S. Only)
1-800-240-1000
Mailing Address
Intergraph Corporation
Huntsville, Alabama 35894-0001 U.S.A.
Educational Media Contacts
We are constantly working on updates and improvements to the documents and other educational media. If you have any suggestions on where we can improve the documentation or where you think more information is needed, let us know. You can reach us by:
Mail Intergraph Corporation
Manager, PBS Documentation GD3006 Huntsville, AL 35894-0001 FAX PBS Documentation 1-256-730-3300 Electronic Mail [email protected]
Table of Contents vii
__________________________________________________________________________________________________________________________________________________
Table of Contents
If You Need Assistance ... iii
Intergraph Directory ... iv
Preface ... xiii
General Conventions ... xv 1. Introduction to ISOGEN ... 1 - 1 1.1 Overview of Isometric Extraction ... 1 - 3 1.1.1 The Intergraph Interface to ISOGEN ... 1 - 3 1.1.2 ASCII to Binary Conversion ... 1 - 4 1.1.3 ISOGEN ... 1 - 4 2. PDS Environment ... 2 - 1 2.1 PD Shell ... 2 - 2 2.1.1 PD_Shell Form Conventions ... 2 - 5 2.1.2 Batch Processes ... 2 - 8 3. Interactive Isometric Extraction ... 3 - 1 3.1 Extraction Criteria ... 3 - 9 3.1.1 Model Files ... 3 - 9 3.1.2 Pipeline Names ... 3 - 10 3.2 Iso Design File ... 3 - 12 3.3 Plot Isometric Drawing ... 3 - 14 3.4 View Isometric Drawing ... 3 - 17 3.5 Conventions and Limitations ... 3 - 19 3.5.1 Extraction Conventions ... 3 - 19 3.5.2 Extraction Limitations ... 3 - 20 4. Batch Software Organization ... 4 - 1 4.1 The Batch Job Input File ... 4 - 3 4.2 Line Processing (pdsidf) ... 4 - 4 4.3 The ISOGEN Interface ... 4 - 5 4.4 ISOGEN ... 4 - 5 4.4.1 Splitting the MTO neutral file (MSPLIT) ... 4 - 6
4.5 Generating Title Block Input (TBLOCK) ... 4 - 6 4.6 Filling in the Title Block (STIB) ... 4 - 6 4.7 Plotting ... 4 - 7 4.8 Updating the Project Database (pdsidf) ... 4 - 7 4.9 Making a Run Log Entry (pdsidf) ... 4 - 7 4.10 Investigating Batch Extraction Problems ... 4 - 7 5. Batch Isometric Extraction ... 5 - 1 5.1 Initial Setup Considerations ... 5 - 3 5.2 Basic Workflow for Running Batch Isometrics ... 5 - 7 5.3 Batch Isometric Generation ... 5 - 9 5.3.1 Define Default Sets ... 5 - 13 5.3.1.1 Add Default Set ... 5 - 15 5.3.1.2 Revise Default Set ... 5 - 18 5.3.1.3 Delete Default Set ... 5 - 20 5.3.1.4 Copy Default Set ... 5 - 21 5.3.2 Define Project Options ... 5 - 22 5.3.3 Revise Iso Area ... 5 - 25 5.3.4 List Iso Areas ... 5 - 27 5.3.5 Create Drawing ... 5 - 28 5.3.6 Revise Drawing ... 5 - 33 5.3.7 Delete Drawing ... 5 - 46 5.3.8 List Drawings ... 5 - 54 5.3.9 Utilities ... 5 - 56 5.3.9.1 Bulk Load Lines ... 5 - 57 Load by Area ... 5 - 60 Load by Model ... 5 - 62 Load by Line ... 5 - 64 5.3.9.2 Bulk Load Lines from ASCII File ... 5 - 67 5.3.9.3 Isometric Symbol Editor ... 5 - 71 Entering the Iso Symbol Editor Environment ... 5 - 72 Input Area Options ... 5 - 73 Assembling an Isometric Symbol ... 5 - 76 Creating a User-defined Symbol Library ... 5 - 83 Using the Newly-created Symbol Library ... 5 - 84 5.3.9.4 Delete Drawing Records With Undefined Iso Type ... 5 - 85 5.3.9.5 Generate FrameWorks Reference Dimension File ... 5 - 86 5.3.10 Create Batch Job Input ... 5 - 89 5.3.11 Schedule Batch Job ... 5 - 100 5.3.12 Reports ... 5 - 104 6. Interpreting the HITS Report ... 6 - 1
Table of Contents ix
6.1 Example HITS Report ... 6 - 2 6.2 Section 1: Basic Input Data and Raw Design File Data ... 6 - 12 6.3 Section 2: Design File Data Sorted by Coordinate ... 6 - 13 6.4 Section 3: Tracing Data ... 6 - 14 6.5 Section 4: Design File Data Sorted by Topo ... 6 - 15 6.6 Section 5: Design File Data in IDF Order ... 6 - 22 6.7 Using the HITS Report to Solve Problems ... 6 - 26 7. The Options File ... 7 - 1 7.1 File Structure ... 7 - 2 7.2 ISOGEN_OPTIONS_BLOCK ... 7 - 4 7.3 INTERGRAPH_OPTIONS_BLOCK ... 7 - 6 7.4 The Files Table ... 7 - 42 7.5 USER_DEFINED_WELDS ... 7 - 45 7.6 WELD_PREFIX ... 7 - 47 7.7 DETAIL_SKETCH_FACILITY ... 7 - 48 7.8 PIPELINE_HEADER ... 7 - 50 7.9 ATEXT_SPECIFICATIONS ... 7 - 56 7.10 INGR_ATEXT_SPECIFICATIONS ... 7 - 58 7.11 LINE_ID_DEFINITION ... 7 - 59 7.12 TYPE_1_LABELS ... 7 - 60 7.13 TYPE_2_LABELS ... 7 - 63 7.14 TYPE_3_LABELS ... 7 - 66 7.15 START_POINT_NOTES ... 7 - 68 7.16 END_POINT_COMPONENT_LABELS ... 7 - 70 7.17 NOZZLE_NOTE ... 7 - 72 7.18 SECONDARY_ORIENTATION_NOTE ... 7 - 74 7.19 DOTTED_SYMBOLOGY_CODE_LIST_VALUES ... 7 - 75 7.20 NOMTO_CODE_LIST_VALUES ... 7 - 77 7.21 SHOP_FABCAT_CODE_LIST_VALUES ... 7 - 78 7.22 OFFSHORE_FABCAT_CODE_LIST_VALUES ... 7 - 80 7.23 MOVABLE_TEXT ... 7 - 81 7.24 NEW_SYMBOL_KEYS ... 7 - 84 7.25 GENITM_NOTE_FORMAT ... 7 - 85 7.26 ALTERNATE_DESCRIPTION_INDEX ... 7 - 87 7.27 USER_DEFINED_IMPLIED_ITEM_BOM ... 7 - 89 7.28 USER_DEFINED_GENERATED_ITEM_BOM ... 7 - 92 7.29 USER_DEFINED_COMPONENT_BOM ... 7 - 95 7.30 NON_DIMENSIONED_SUPPORTS ... 7 - 98 8. User-Defined BOM / Material Control File ... 8 - 1 8.1 Types of Material List ... 8 - 2 8.1.1 Operating Requirements ... 8 - 4 8.2 Material List Definition (MLD) File ... 8 - 6 8.3 User-Defined Material Control File (.bom file) ... 8 - 7 8.4 Offshore Material Category ... 8 - 9 8.5 Transferring Components Between Sort Groups ... 8 - 9 8.6 Generating an Optional Format for Length Output ... 8 - 10 8.7 Bolt Units (size x length) ... 8 - 10
8.8 Generating a Revised Format of the Cut List ... 8 - 11 8.9 Welds in the Material List ... 8 - 13 8.10 Style for Fabricated (Pulled) Bends Output ... 8 - 13 8.11 Style for Material List Output ... 8 - 13 8.12 Positioning the Title Block ... 8 - 14 8.13 MLD File Content ... 8 - 14 8.14 MLD File Format Guidelines ... 8 - 15 8.14.1 Style 3 Material List ... 8 - 17 8.15 Example User-defined Material List - Style 2 ... 8 - 19 8.16 Example User-defined Material List - Style 3 ... 8 - 19 9. Creating Seed Files for Extraction ... 9 - 1 9.1 Creating an Isometric Seed File ... 9 - 1 9.2 Creating a Plot Request File ... 9 - 3 9.2.1 IPLOT Plot Request Files ... 9 - 3 10. Mapping Attributes to the Title Block ... 10 - 1 10.1 SEGMENT_DATA_TABLE ... 10 - 3 10.2 DRAWING_DATA_TABLE ... 10 - 7 10.3 SHEET_DATA_TABLE ... 10 - 12 11. Creating a Notes Table ... 11 - 1 11.1 Using the isoc.note File ... 11 - 2 12. The MTO Neutral File Record Map ... 12 - 1 12.1 COMMON_RECORD_DATA ... 12 - 2 12.2 COMPONENT_ATTRIBUTES ... 12 - 4 12.3 IMPLIED_ITEMS ... 12 - 6 12.4 GENERATED_ITEMS ... 12 - 9 13. The PDS-to-ISOGEN Symbol Map ... 13 - 1 13.1 The PDS Item Name ... 13 - 1 13.2 The ISOGEN Symbol Name ... 13 - 1 13.3 The ISOGEN Record Number ... 13 - 2 13.4 Number of Connect Points ... 13 - 3 13.5 Tapped Component Name ... 13 - 3 13.5.1 Tapped elbows ... 13 - 3 13.5.2 Olets attached to fittings ... 13 - 4 13.6 Tapped component record number ... 13 - 4 13.7 PDS Valve Operator Name ... 13 - 4 13.8 End Prep Low and End Prep High ... 13 - 5 13.9 Order of Table Entries ... 13 - 5
Table of Contents xi
14. The Valve / Operator Table ... 14 - 1 15. Repeatability ... 15 - 1 15.1 Repeatability Restrictions and Limitations ... 15 - 2 15.2 Extraction Information in the Database ... 15 - 3 15.3 Determining the Traversal Start Point ... 15 - 4 15.4 Determining Sheet Split Points ... 15 - 4 15.5 Determining Spool Split Points ... 15 - 5 16. Welds ... 16 - 1 Delivered weld symbols ... 16 - 2 16.1 Dotted Weld Symbols ... 16 - 2 16.2 User-defined Weld Symbols ... 16 - 3 16.3 Codelist Values for Standard Note 180 and 1100 ... 16 - 3 16.4 Weld Types and Mapping ... 16 - 3 16.5 Offshore Fabrication Category ... 16 - 4 16.6 Unique Weld Numbering ... 16 - 4 16.7 User-defined Weld Prefix ... 16 - 4 16.8 The Weld Summary Report ... 16 - 5 16.8.1 Weld Definition File Format ... 16 - 5 16.8.2 Example WDF File ... 16 - 9 16.9 Welds Listed in the Bill of Materials ... 16 - 10 17. Dimensioning and Coordinate Output ... 17 - 1 17.1 Dimensioning Features ... 17 - 1 17.2 Coordinate Features ... 17 - 3 18. Detail Sketch and Information Note Facility ... 18 - 1 18.1 Detail Sketch Entries in the DDF ... 18 - 2 18.2 Information Note Entries in the DDF ... 18 - 3 19. Weight Display ... 19 - 1 19.1 Center of Gravity Calculation ... 19 - 2 20. Isometric Presentation ... 20 - 1 20.1 PIPELINE-ATTRIBUTES ... 20 - 3 20.2 PIPELINE-ATTRIBUTES-SPECIAL ... 20 - 4 20.3 PIPELINE-ATTRIBUTES-DOTTED ... 20 - 4 20.4 BEND/ELBOW-REPRESENTATION ... 20 - 5 20.5 FITTINGS-GENERAL ... 20 - 5 20.6 FITTINGS-SPECIAL ... 20 - 6 20.7 FITTINGS-UNDIMENSIONED-BRANCHES ... 20 - 7 20.8 MISC-ITEMS ... 20 - 8 20.9 LAYER-NAMES ... 20 - 8 20.10 Program Defaults ... 20 - 9
20.11 Example Drawing Definition File ... 20 - 10 21. Isometric Types ... 21 - 1 Appendix A: Warning and Error Messages ... A - 3 A.1 Intergraph Interface to ISOGEN ... A - 4 A.1.1 Information Messages ... A - 5 A.1.2 Warning Messages ... A - 8 A.1.3 Error Messages ... A - 15 A.2 ISOGEN ... A - 22 A.2.1 ISOGEN message file errors ... A - 22 A.2.2 Design File Interface Error Messages ... A - 31 A.3 Batch Extraction Software Error Messages ... A - 32 Appendix B: Alias ISOGEN Tables ... B - 3 Appendix C: Example Documents ... C - 3 C.1 The Options File (#/dat/isoc.def) ... C - 4 C.2 Label Library Label Definitions ... C - 9 C.3 HITS Report (.h file) ... C - 28 C.4 Intermediate Data File (.idf file) ... C - 37 C.5 Interface Error Log (.err file) ... C - 54 C.6 MTO Neutral File (.b# file) ... C - 57 C.7 ISOGEN Message File (.msg file) ... C - 59 C.8 ISOGEN Printed Parts File (.prt file) ... C - 60 C.9 ISOGEN Component versus Sheet Number File (.sed file) ... C - 62 C.10 ISOGEN Cut Pipe Report (.cut file) ... C - 63 C.11 Title Block Table (.bit, .seg and .dwg files) ... C - 64 Appendix D: PDS Database Table Formats ... D - 3 D.1 Piping Design Database Table Format ... D - 4 D.2 Specification/Material Reference Database Table Format ... D - 11 Appendix E: ISOGEN SKEY Dimensions ... E - 3 Glossary ... GL - 58 Index ... IN - 58
Preface xiii
__________________________________________________________________________________________________________________________________________________
Preface
Document Purpose
This document is a reference guide for Intergraph Corporation’s PD ISOGEN software package. You can use the PD ISOGENTMsoftware to generate piping isometric drawings from 3D models created by PDS. The ISOGEN product is one part of the overall Intergraph Plant Design System.
This document is designed as a reference for the PD ISOGEN software. It includes explanations and examples of the operation of all the facilities that make up the software package. Use this guide when you need to reference a specific product function.
Document Prerequisites / Audience
This document is intended for both beginning and advanced users. The beginning user should:
be familiar with an Intergraph workstation
have Intergraph and MicroStation operating experience have PDS Piping operating experience.
The advanced user should:
have a good understanding of basic Windows commands and text editors knowledge of Intergraph software such as EDG and relational databases be capable of modifying the PDS 3D RDB
have a good understanding of the general PDS environment.
Related Documents/Products
MicroStation32 software is required to operate in the PDS 2D Graphics software. Information about MicroStation 32 capabilities can be found in the following documents:
MicroStation 32 Reference Guide MicroStation 32 User’s Guide
Intergraph Corporation’s Relational Interface System (RIS)TMis required to operate PDS ISOGEN, along with a relational database management system (RDBMS) supported by RIS. Currently, these include Informix, Oracle, and Ingres. Information about RIS
Relational Interface System (RIS) Reference Manual Relational Interface System (RIS) Operator Training Guide
For more information on related aspects of the PD ISOGEN products, consult the following documents:
Project Administrator Reference Guide Piping Design Graphics Reference Guide
Additional Information
The following informational files are delivered with the PDS ISOGEN software in the /usr#/ip32/isogen directory.
File Name Contents
README Describes changes and additions to the product since the last version. Lists the names and dates of the files in the current release. For a fixes release, the files which have been modified are appended to the top of the initial file to provide a history of all changes to the product. Includes Comments and Trouble Report numbers which describe what problems have been fixed. Provides special notices to the customer. Lists any exceptions made to the certification. product.def Lists all dependencies and related parts for the product.
Preface xv
__________________________________________________________________________________________________________________________________________________
General Conventions
This document contains many visual cues to help you understand the meaning of certain words or phrases. The use of different fonts for different types of information allows you to scan the document for key concepts or commands. Symbols help abbreviate and identify commonly used words, phrases, or groups of related information.
Typefaces
Italic Indicates a system response, which is an explanation of what the software is doing. For example,
The text is placed in the viewing plane.
Bold Indicates a command name, parameter name, or dialog box title. Command paths are shown using an arrow between command names. For example,
Choose File > Open to load a new file.
Sans serif Indicates a system prompt or message, which requires an action be taken by the user. For example,
Select first segment of alignment
Bold Typewriter
Indicates what you should literally type in. For example, Key in original.datto load the ASCII file.
Normal Typewriter
Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rptfile.
Symbols
This document uses the following symbols to represent mouse buttons and to identify special information:
<C> Command button
<D> Data button (usually the left mouse button)
<R> Reset/reject button (usually the right mouse button) <T> Tentative button (usually the center mouse button)
Note — Important supplemental information.
Warning — Critical information that could cause the loss of data if not followed.
Technical tip or information — provides information on what the software is doing or how it processes information.
Map or path — shows you how to get to a specific command or form.
More information — indicates there is additional or related information.
Need a hint — used with activities and labs, provides a tip or hint for doing the exercises.
Keyboard Conventions
The following list outlines the abbreviations this document uses for keyboard keys and describes how to use them in combination. You can make some menu selections through the use of keyboard accelerators, which map menu selections to key combinations.
ALT Alternate key
CTRL Control key
DEL Delete key
ENTER Enter key
ESC Escape key
CTRL+z To hold down the Control key and press Z. ESC,k To press the Escape key, then K.
Preface xvii
Terminology
Click To use a mouse or key combination to pick an item that begins an action. For example,
Click Apply to save the changes.
Select To mark an item by highlighting it with key combinations or by picking it with your cursor. Selecting does not initiate an action. After selecting an item, you click the action you want to affect the item. For example,
Select the file original.dat from the list box, then click Delete to remove it from the directory.
In addition, you would select items to define parameters, such as selecting toggle buttons. This also applies to selecting graphic elements from the design file. For example, Select the line string to define the graphic template.
Tentative-select To place a tentative point on an existing graphic element in a design file. If you are using the CLIX operating system, you tentative-select by double-clicking with a mouse or pressing <T> on a hand-held cursor. If you are using the Windows NT operating system, you tentative-select by pressing a left-button, right-button chord.
Double-click To select and execute a command by clicking the mouse or hand-held cursor button twice in rapid succession. This term implies that you are clicking the data button (<D>) as part of a menu or dialog box action. For example,
Double-click on the file original.dat to load it into the new surface.
Drag To press and hold the data button (<D>) while moving the mouse or hand-held cursor.
Type To key a character string into a text box.
Key in To type in data and press ENTER to enter the data and execute the default action.
In a dialog box, pressing TAB after keying in data will enter the data and move the cursor to the next field.
Introduction to ISOGEN 1 - 1
__________________________________________________________________________________________________________________________________________________
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:
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.
Introduction to ISOGEN 1 - 3
__________________________________________________________________________________________________________________________________________________
1.1
Overview of Isometric Extraction
This section outlines the software components and how they are organized for interactively extracting isometrics.
__________________________________________________________________________________________________________________________________________________
1.1.1
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 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 material information are dealt with component by component as the network is traversed.
If the components in the piping models are not properly connected or other problems exist, the internal data structure will not be properly built and isometric extraction will fail. 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.
__________________________________________________________________________________________________________________________________________________
1.1.2
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.
__________________________________________________________________________________________________________________________________________________
1.1.3
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 material) A cut pipe report
A component VRS sheet number file
The parts list file contains the same bill of material that is shown on the isometric drawing. It is possible to turn the drawing bill of material off and attach the 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.
PDS Environment 2 - 1
__________________________________________________________________________________________________________________________________________________
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.
__________________________________________________________________________________________________________________________________________________
2.1
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 double-clicking teh PD_Shell icon. 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.
This form identifies the active project(s) and provides access to all the PDS functions.
Options
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.
PDS Environment 2 - 3
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 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 DesignReview and to review data from a DesignReview 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.
Other Fields
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.
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 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.
PDS Environment 2 - 5
__________________________________________________________________________________________________________________________________________________
2.1.1
PD_Shell Form Conventions
The following Conventions describe how to respond to the various buttons, lists, and prompts that make up the environments. The display size of forms and dialog boxes in the non-Microstation graphics environment are
independent of the size of the workstation’s display system. Most forms contain the same basic features: buttons, fields, text, and other gadgets. In general, anything you find on a form is called a gadget.
Selecting Options
You move through the PD Shell forms by selecting function buttons or other gadgets from the form. Select means to place the screen cursor (which appears as an arrow) on top of a screen gadget and press <D>.
For most of the forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button. You use the select action to select functions, access other forms, activate data fields, toggle buttons, select from lists, scroll through data displayed on the screen, and so on.
The following summarizes other basic actions you use in the environments: Enter — When keying in any data in a key-in field, press the <ENTER> or <Tab> key for the data to be entered into the system. You can also press <ENTER> or <Tab> to move through a set of key-in fields. Delete — If you make a mistake while keying in text, press the <Delete> key to erase character(s) to the left of the cursor.
Common Tools on the PD Shell Forms
There are many gadgets in the environments that are common to most or all of the forms. The following describes these tools.
Standard Commands
The PD Shell forms have a set of standard buttons in the upper right corner of most of the form windows. The available commands vary from form to form depending on the type of operation.
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.
You can also select the slider and, while pressing <D>, slide the button up or down the bar. The items scroll through the window as you move the button. The size and position of the button on the scroll bar is an indication of the number of lines and the relative position within the list.
All commands that display a list of design areas or models order the list alphanumerically by the design area number or model number in ascending order.
In some forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button.
PDS Environment 2 - 7
Key-in Fields
Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark gray. You can select a key-in field and key in a new value. A bar cursor appears in the active key-in field. Key in your input, and press <Return>. To change a field, reselect the field and key in the new information. Key-in fields have a maximum number of characters depending on the item that is being defined.
If you select a key-in field for a code-listed attribute, the system activates a form that lists the code list values for the selected field.
MicroStation requires lowercase characters for the file specification and path name of all design files. Therefore, the system automatically converts any input for the file specification and path name of a design file (such as a model or drawing) to lowercase before loading into the Project Control Database. Display-List Boxes
A display-list box is located at the end of some key-in fields. It lets you select data from a list instead of keying in information. For example, there is a display list associated with the
Authorization key-in field shown. At the end of the field, there is a small box with horizontal dashes. When you select this display list box with the screen cursor, an associated list of valid input values displays. Select an item from the list to enter its value into the field.
Shift Left and Shift Right buttons
At the bottom of some key-in and display fields, there are two buttons marked with arrows. These buttons are called shift left and shift right buttons.
Often, you can key in more characters than a field display shows. Shift Left moves the text display to the front of the field; Shift Right moves the text display to the end of the field.
Toggle
A toggle field on a screen menu enables you to select one of two possible choices, one of which is always displayed. Place a data point on the toggle field to toggle between the two choices.
Roll-Through List
A roll-through list shows one choice at a time of a list that can be several items long. Place a data point on the roll-through list to scroll through the available options. The option displayed is active.
Standard Window Icons
When using this software in the CLIX environment, you can press <D> along the edge of a form or any area not occupied by a button, key-in field, or other gadget, to display a box of icons. You can manipulate form windows just like any other workstation window.
The following list defines the available window icons. Collapse/Restore Repaint Pop-to-bottom Modify/Resize Pop-to-top Restore Size __________________________________________________________________________________________________________________________________________________
2.1.2
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.
Interactive Isometric Extraction 3 - 1
__________________________________________________________________________________________________________________________________________________
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.
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.
2. Select the Interactive button.
The system displays the Interactive Isometric Extraction form.
3. If you know the information, keyin the appropriate Model Numbers and Line Names and proceed to step 10. Otherwise, continue with this procedure.
Interactive Isometric Extraction 3 - 3
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.
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, page 3 - 10 . 9. Once 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.
The system also generates an iso design file name based on the first pipeline name and places it in the Iso Design File field.
Interactive Isometric Extraction 3 - 5
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\filenamefor 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.
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 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 iso’s 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’
Interactive Isometric Extraction 3 - 7
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 status form. See Appendix A Error Messages for detailed descriptions of each error and warning message.
15. To plot an isometric drawing using the Plot button, refer to Plot Isometric Drawing, page 3 - 14 .
16. To view an isometric drawing using the View Graphics button, refer to View
Interactive Isometric Extraction 3 - 9
__________________________________________________________________________________________________________________________________________________
3.1
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 Pipeline Names
– Generation by Line Name Substring – Generation by Line ID
Iso Design File
__________________________________________________________________________________________________________________________________________________
3.1.1
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
If the model number that you specify does not exist, the software displays an error message at the bottom of the form. Press <RETURN> to proceed.
If the model number is invalid, the software displays the message Error Retrieving Model and the fully expanded filename is displayed in the input field.
A filename is considered invalid if it does not exist in the project database.
__________________________________________________________________________________________________________________________________________________
3.1.2
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, page 7 - 1 for more information.
For each method, you identify the network of piping to extract by specifying piping segment attributes. Piping segments usually correspond only to sections of piping and NOT to an entire piping system (unless the line is trivial).
Extraction by Line Name Substring
When extracting by line name substring you should key in any substring of the full PDS line name that uniquely identifies the pipeline you want to include in the iso. This is the default way of identifying pipelines to extract as defined in the LINE_ID_DEFINITION section of the defaults.dat file.
Example 1:
If the line name is 6IN-OWS10111-1C0031 then a substring that you might use to identify this line is OWS10111.
You probably would not want to use 1C0031 since it is the spec name component of the line name and would probably identify more than one line in the model. Likewise, you would probably not want to use 6IN-OWS10111 since you may want to extract sections of the line that are not 6" NPD or because multiple 6" sections are connected together by sections that are not 6".
Do not extract by line name substring if lines that are similarly named exist together in the models that you are extracting from. This situation exists, for example, when the substring you want to use is also a substring of another line name.
Interactive Isometric Extraction 3 - 11
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, page 3 - 11 for more information.
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, page 7 - 59 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).
__________________________________________________________________________________________________________________________________________________
3.2
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. Since UNIX 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
The ISOGEN mto neutral file - iso name + .bom
The ISOGEN message file - iso name + .msg
Interactive Isometric Extraction 3 - 13
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, page 7 - 1 for more information). Their contents are discussed in more detail in the sections entitled Options File and Isometric Seed File.
__________________________________________________________________________________________________________________________________________________
3.3
Plot Isometric Drawing
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 keyin 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
Interactive Isometric Extraction 3 - 15
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, page 9 - 1 .
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.
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.
7. 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. 8. 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, Tue, etc.), the time and then select AM or PM.
9. 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.
Interactive Isometric Extraction 3 - 17
__________________________________________________________________________________________________________________________________________________
3.4
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.
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.
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.
Interactive Isometric Extraction 3 - 19
__________________________________________________________________________________________________________________________________________________
3.5
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. A brief summary of these items is also provided below.
__________________________________________________________________________________________________________________________________________________
3.5.1
Extraction Conventions
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.
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.
__________________________________________________________________________________________________________________________________________________
3.5.2
Extraction Limitations
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.
Interactive Isometric Extraction 3 - 21
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.
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.
Bolt Length at Thru-bolted Components with a Sheet or Iso Line
Name Break
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).
