Clash

Interference Checker/Manager (PD_Clash)
Users Guide
Document Number DPDS3-PB-200006A DPDS3-PB-200006B DPDS3-PB-200006C Version PDS 7.1 PDS 7.2 PDS 7.3 Date April 2002 February 2003 October 2004 Pages 1-274 275-298 299-314
Copyright
Copyright 1984-2004 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.
Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.2277013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, 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 Huntsville, Alabama 35894-0001
Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification 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.
Trademarks
Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, and PDS are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. ISOGEN is a registered trademark of Alias Limited. Other brands and product names are trademarks of their respective owners.
_ _______________
If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraphs products, services, and direction. Our web address is: http://www.intergraph.com.
If You Need Assistance
Support
For the lasest Support Services information, use a World Wide Web browser to connect to http://www.intergraph.com/ppo/services/support.asp. If you are outside of the United States, please call your local Intergraph office. The most upto-date list of international offices and distributors is available on the web at http://www.intergraph.com.
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

All countries 1-256-730-2000
Training Registration
1-800-766-7701 (U.S. Only) 1-256-730-5400 (Outside the U.S.)
Mailing Address
Intergraph Process, Power & Offshore 300 Intergraph Way Madison, Alabama 35758 U.S.A. You can also reach us by electronic mail at info@intergraph.com.
_ _______________
Documentation 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 Process, Power & Offshore Documentation Manager 300 Intergraph Way Madison, AL 35758
_ _______________
Table of Contents
If You Need Assistance ........................................................................................................ Intergraph Directory ............................................................................................................. Preface ................................................................................................................................................. About this reference material ................................................................................................ General Conventions .................................................................................................................... Keyboard Conventions ......................................................................................................... Terminology ......................................................................................................................... 1. Welcome to Interference Checker/Manager (PD_Clash) ............................................................. 1.1 Interference Checker/Manager Introduction ....................................................................... 1.1.1 2. Project Organization ................................................................................................
Table of Contents
3 3 11 11 13 14 15 17 18 18 19 20 20 21 21 22 23 23 24 24 25 30 30 30 31 33 35 37 39
Interference Detection .................................................................................................................. 2.1 Understanding Design Areas and Volumes ........................................................................ 2.1.1 2.1.2 2.1.3 2.1.4 2.2 Project ..................................................................................................................... Piping Design Area and Design Area ..................................................................... Design Area and Piping Design Area Pre-defined Volume .................................... Volume Filter ..........................................................................................................
Understanding Interference Envelopes ............................................................................... 2.2.1 2.2.2 2.2.3 Understanding Envelope Builder ............................................................................ Understanding Envelope Verification ..................................................................... Understanding Envelope Diagnostics .....................................................................
2.3 2.4 2.5 2.6 2.7 2.8 2.9
Understanding Interference Checking ................................................................................. Understanding Interference Approving ............................................................................... Understanding Interference Plotting ................................................................................... Understanding Interference Reporting ................................................................................ Basic Interference Checklist ................................................................................................ Clash Categories .................................................................................................................. Project Setup ....................................................................................................................... 2.9.1 Redirected Processing .............................................................................................
3.
Interference Management .............................................................................................................
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 3.1 Interference Checker Data ................................................................................................... 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 4. Single/Dual Design Area Ownership ...................................................................... Exclusion of Interferences by Discipline ................................................................ Exclusion of Interferences by Model Status ........................................................... Equipment without/with Insulation ......................................................................... Construction Tolerances for Equipment Envelopes ................................................ 41 43 47 54 56 57 59 60 69 70 72 73 74 75 76 77 81 85 89 90 98 105 108 111 112 114 115 118 118 118 119 121 122 124 127 130
Envelopes ..................................................................................................................................... 4.1 Envelope Builder ................................................................................................................. 4.1.1 Create Project Envelope Files ................................................................................. 4.1.2 Piping Design Area ................................................................................................. 4.1.3 Piping Design Area Predefined Volume ................................................................. 4.1.4 Design Area ............................................................................................................. 4.1.5 Design Area Predefined Volume ............................................................................. Clash Envelopes for Areas with DVCS .............................................................................. 4.1.6 Model ...................................................................................................................... 4.2 4.3 4.4 PDS Clash Detection with Non-PDS Models ..................................................................... Envelope Verification ......................................................................................................... Envelope Diagnostics ..........................................................................................................
5.
Interference Checking .................................................................................................................. 5.1 Interference Checker ........................................................................................................... 5.1.1 5.1.2 5.2 Plot Clashes ............................................................................................................. Interference Checker Output ...................................................................................
Piping Clash Check .............................................................................................................
6.
Interference Managing ................................................................................................................. 6.1 6.2 Interference Approval Manager .......................................................................................... Approval Manager Commands ........................................................................................... 6.2.1 Approve ................................................................................................................... 6.2.1.1 6.2.1.2 6.2.1.3 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.2.7 Select View .............................................................................................. Envelope Diagnostics ............................................................................... Enter Dynamics ........................................................................................
Approve From List .................................................................................................. Checker Run Dates .................................................................................................. Review Clash History ............................................................................................. Create Unapproved Clash Report ............................................................................ Checker Reference Data .......................................................................................... Mass Clash Approval ..............................................................................................
_ _______________
6.3 View Commands ................................................................................................................. 6.3.1 View Commands ..................................................................................................... 6.3.1.1 6.3.1.2 6.3.1.3 Move and Center View ............................................................................ Construct Point ......................................................................................... Distance and Direction .............................................................................
Table of Contents
133 137 139 141 143 145 145 147 148 149 150 151 152 153 154 156 158 159 160 161 162 163 165 167 168 169 170 175 175 176 176 177 179 180 181 184 186
6.3.2 Window Volume ..................................................................................................... Viewing Options ................................................................................................................. 6.3.2.0.1 6.3.2.0.2 6.3.2.0.3 6.3.2.0.4 6.3.2.0.5 6.3.2.0.6 6.3.2.0.7 6.3.3 Set View Orientation ......................................................................................... Update Window ................................................................................................ Rotate About View ............................................................................................ Match Planar Element Command ..................................................................... Rotation 3 Points ............................................................................................... Dialog View Rotation ....................................................................................... Color Shading ...................................................................................................
Render Options ........................................................................................................ 6.3.3.1 6.3.3.2 6.3.3.3 6.3.3.4 6.3.3.5 6.3.3.6 Camera View ............................................................................................ Views ........................................................................................................ Level Symbology On ............................................................................... Level Symbology Off ............................................................................... Form Left/Right Screen ............................................................................ Set/Do Not Set Display Depth for Review Commands ...........................
6.3.4 6.3.5 6.4 6.5
View, More Commands .......................................................................................... Viewing Direction ...................................................................................................
View Depth ......................................................................................................................... File Commands ................................................................................................................... 6.5.1 File Commands ....................................................................................................... 6.5.1.1 6.5.1.2 6.5.1.3 Plot Clashes .............................................................................................. File Design ............................................................................................... Exit ...........................................................................................................
6.6
Element Commands ............................................................................................................ 6.6.1 Analyze ...................................................................................................................
6.7 Setting Commands .............................................................................................................. 6.8 User Commands .................................................................................................................. 6.9 Interference Management Data ........................................................................................... 6.10 Piping Clash Review (in the PD_Design Module) ........................................................... 6.11 Piping Clash Check (in the PD_Design Module) ............................................................. 6.12 Review PDS Clash ............................................................................................................
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Parameters ........................................................................................................................... 7. PDS Interference Plotting ............................................................................................................ 7.1 7.2 8. Interference Plot Manager ................................................................................................... Interference Plot Management Data .................................................................................... 186 189 190 196 197 198 199 201 203 205 207 209 211 212 215 217 219 221 223 226 229 231 232 234 236 238 239 242 245 247
Interference Reporting .................................................................................................................. 8.1 Clash Report Manager Form ............................................................................................... 8.1.1 8.1.2 Using the Report Commands .................................................................................. Report Format Form ................................................................................................ 8.1.2.1 8.1.2.2 8.1.3 Format Creation/Revision Form .............................................................. Format Deletion Form ..............................................................................
Report Discrimination Data Form ........................................................................... 8.1.3.1 Discrimination Data Creation Form ......................................................... 8.1.3.1.1 8.1.3.1.2 Project Administration Form ................................................. Project Search Criteria Form .................................................. 8.1.3.1.2.1 8.1.3.2 8.1.3.3 Define Date/Time ..............................................
Discrimination Data Revision Form ........................................................ Discrimination Data Deletion Form .........................................................
8.1.4
Report Form ............................................................................................................ 8.1.4.1 8.1.4.2 8.1.4.3 8.1.4.4 Report Creation Form .............................................................................. Revise Report Form ................................................................................. Report Deletion Form .............................................................................. Report Approval Form ............................................................................. 8.1.4.4.1 8.1.4.5 Approval/Revision Interface Form ........................................
Report Multiple Submit Form ..................................................................
8.1.5 8.2 9.
Report Management Defaults Form ........................................................................
Interference Report Management Data ...............................................................................
Scheduled Envelope Builder and Clash Detection ....................................................................... 9.1 Create/Revise Envelope Builder/Clash Detection Schedule ............................................... 9.1.1 9.1.2 Delete Envelope Builder/Clash Detection Schedule ............................................... Review Schedule .....................................................................................................
_ _______________
Appendix A: Troubleshooting PD Clash ......................................................................................... A.1 Message Files ............................................................................................................................ A.1.1 Envelope Verification Error Messages ......................................................................... A.2 Tips on Using PD Clash ............................................................................................................ Markers ...................................................................................................................................... Envelope Verification Dates ..................................................................................................... Approval Manager > Enter Dynamics Mode ............................................................................ Structural Database Records ..................................................................................................... Placing Spheres ......................................................................................................................... A.3 Questions & Answers ................................................................................................................ Changing title block units ......................................................................................................... Appendix B: Interference Tables .....................................................................................................
Table of Contents
249 250 251 252 252 252 252 253 253 254 254 255 261 269
Glossary ............................................................................................................................................... Index ....................................................................................................................................................
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002
10
_ _______________
Preface
About this reference material
Interference Checker/Manager is organized by subject and commands on the Interference Checker/Manager interface and graphics environment. It is divided into several sections. Section 1 - provides general information including project organization. Section 2 provides information about understanding envelopes, interference, checking, plotting, and reporting, distributed processing, queue setup, and a PDS Overview. Section 3 briefly explains the Interference Management options. They allow you to access each of the options available in the interference checking process. It also explains the Interference Checker Data command, which defines the way envelope processing and interference detection are done. Section 4 explains the use of the Envelope Builder, Clash Detection with Non-PDS Models, Envelope Verification, and Envelope Diagnostics options. This includes information on creating envelopes which must be done prior to interference checking. It explains Envelope Verification which checks the dates of the model and its corresponding envelope to make sure that the envelope is up-to-date with the model. Envelope Diagnostics and its envelope diagnostics graphics are also explained. Section 5 explains the use of the Interference Checker option for an entire project or for separate design areas. It also contains information on PD_Designs Piping Clash Check command. Section 6 explains the use of the Interference Approval Manager and Interference Management Data options. It also contains information on PD_Designs Piping Clash Review command. Section 7 explains the Interference Plot Manager and the Interference Plot Management Data options used when plotting interference clashes. Section 8 explains the Interference Report Manager and the Interference Report Management Data options. The Interference Report Manager option is used to generate user-defined interference management reports. The Interference Report Management Data option is used to define the network address and pathname in the Project Control Database. Section 9 explains the Scheduled Envelope Build/Clash Detection options used to run envelope generation and clash detection as a batch process. Appendix A - provides troubleshooting information including error messages, tips, and questions and answers.
Preface
Appendix B provides information on tables related to interference checking used in the Interferences class.
11
_ _______________
12
_ _______________
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.
Preface
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.dat to load the ASCII file. Normal Typewriter Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rpt file.
13
_ _______________
Symbols
This document uses the following symbols to represent mouse buttons and to identify special information: <C> <D> <R> <T> Command button Data button (usually the left mouse button) Reset/reject button (usually the right mouse button) 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 CTRL DEL ENTER ESC CTRL+z ESC,k Alternate key Control key Delete key Enter key Escape key To hold down the Control key and press Z. To press the Escape key, then K.
14
_ _______________
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. 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. To key a character string into a text box. 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.
Preface
Double-click
Type Key in
15
_ _______________
16
_ _______________
1. Welcome to Interference Checker/Manager (PD_Clash)
Welcome to Interference Checker/Manager (PD_Clash)
1. Welcome
Interference Checker/Manager (PD_Clash) creates envelope files for all models in the specified project, design area, or for individual models which have an envelope builder specific to each discipline in the Interference Checker/Manager. It also collects envelope data for the models that have envelope files which were previously created by one of the other PDS modules. The checker/manager processes the specified design volume and identifies all of the interference clashes.
17
_ _______________
1.1
Interference Checker/Manager Introduction

The Interference Checker/Manager (PD_Clash) product processes a specified design volume for interference clashes, reviews interferences, and reviews or revises the approval status of interferences. You can check for interferences at any stage of the design process. Also, you can redirect clash checking through a pipe queue to a server or to another workstation on the same LAN.
1.1.1
Project Organization
Since a process plant such as a refinery can be extremely large, PDS uses the following organization to break the plant into smaller units that can be handled more easily. A Project is a convenient grouping of all of the items that constitute a plant. The project is the fundamental structure for working in PDS. The project constitutes the entire volume of the project. A Design Area represents a specified volume of the project for a specific discipline. This volume is defined by the models it comprises. Design volumes can be used to break up the project into smaller areas for interference checking or reporting. This speeds up processing when only a portion of the project has changed. The models or model components that are not within the volume will not be checked. A Design Area Pre-defined Volume represents a pre-defined volume of the project for a specific discipline. This volume is defined by the pre-defined coordinates of High, Low, Easting, Northing, and Elevation. The volume is defined by using the Project Environment Manager. Make sure that the pre-defined volume encompasses all the models that you want to be checked. The models or model components that are not within the volume will not be checked. A model is a 3D Microstation file that has a defined discipline and is located within the volume of the project. A model represents a subdivision of the project based on work responsibility, completion of schedules, and computer response time. A Volume Filter can be used to decrease the volume of a project, area, or pre-define volume to further decrease the processing time when only a sub-part requires checking or reporting. The Project Administrator controls the creation and modification of PDS 3D projects. Each project consists of a project control database, project design database, piping and equipment models, reference models (structural, HVAC, and electrical raceway), a set of drawings, and a collection of reference data. The reference data may be specific to one project or shared by more than one project.
18
_ _______________
2. Interference Detection
This section provides information required to understand the terminology and philosophy involved with interference detection, see: 2.1 Understanding Design Areas and Volumes See Understanding Design Areas and Volumes, page 20 for more information. Understanding Interference Envelopes See Understanding Interference Envelopes, page 23 for more information.
Interference Detection
2.2
2. Basics
2.3
Understanding Interference Checking See Understanding Interference Checking, page 25 for more information. Understanding Interference Approving See Understanding Interference Approving, page 30 for more information. Understanding Interference Plotting See Understanding Interference Plotting, page 30 for more information. Understanding Interference Reporting See Understanding Interference Reporting, page 30 for more information. Basic Interference Checklist See Basic Interference Checklist, page 31 for more information. Clash Categories See Clash Categories, page 33 for more information. Project Setup See Project Setup, page 35 for more information.
2.4
2.5
2.6
2.7
2.8 2.9
19
_ _______________
2.1
Understanding Design Areas and Volumes

This section thoroughly describes design areas and volumes and how they pertain to interference checking. Running the Interference Checker for an entire project takes considerably longer than running it for a design area. Since the project workload is most often being delegated to various disciplines, it is most efficient to use the design area options. These options are less time consuming and create individual sets of reports rather than one set of reports for the entire project. Adhere to using either the Project option or one of the Design Area options for the life of the project for the most consistent results. It is important to decide on a method, either project or a design area option, before doing interference checking. Each clash is recorded only once in either the project seed file or the design area seed file.
2.1.1
Project
This option on the Interference Checker form performs clash checking for all of the envelope files defined for the project and creates interference, difference, and batch queue error reports. To specify a smaller volume for a single interference check, set the Volume Filter toggle to On after selecting a design area. The dotted rectangle signifies the volume that is processed using the Project option.
20
_ _______________
2.1.2 Piping Design Area and Design Area
Understanding Design Areas and Volumes
These options on the Interference Checker form activate a list of piping design areas or a list of disciplines and then a list of design areas from the specified discipline that are available for clash checking. After a design area has been selected, the system defines a volume that encompasses all models within the selected design area. It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the defined volume. To specify a smaller volume for a single interference check, set the Volume Filter toggle to On after selecting a design area.
2. Basics
The dotted rectangle signifies the volume that is processed using the Design Area option. The name of the selected design area is DesA1.
2.1.3
Design Area and Piping Design Area Predefined Volume

These options on the Interference Checker form activate a list of piping design areas or a list of disciplines and then a list of design areas with pre-defined volumes available for clash checking. After a design area has been selected, the system uses the pre-defined volume that has been specified by using the Project Environment Manager. It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the pre-defined volume. The Interference Checker does not include models that are in the selected design area that do not fall within the pre-defined volume. The dotted rectangle signifies the volume that is processed using the Design Area Predefined Volume option. The name of the selected design area is DesAPreV1.
21
_ _______________
2.1.4
Volume Filter
This toggle on the Interference Checker form creates a Volume Filter for one run of the Interference Checker. When set to Volume Filter On, you can define the low and high Easting, Northing, and Elevation for one run of the Interference Checker in the following fields. When set to Volume Filter Off the system will use the default or pre-defined volume.
The dotted rectangle signifies the volume that is processed when the Volume Filter has been activated and the volume to be checked has been specified.
22
_ _______________
2.2
2.2.1
Understanding Interference Envelopes
Understanding Interference Envelopes

Understanding Envelope Builder
Piping, equipment, structural, raceway, and HVAC envelope files are created through the PDS Interference Checker/Manager module. All Architectural files will have their interference envelope files created within the Architecture product. Envelopes for MicroStation files are created through the PD_Clash envelope builder using the generic envelop builder. The envelope building process and its results will vary depending on the way the Interference Checker Data command is defined. The settings that affect envelope building are, Dual or Single Design Area Ownership Exclusion of Interferences by Discipline Exclusion of Interferences by Model Status Insulation Inclusion or Exclusion for Equipment Envelopes Construction Tolerances for Equipment Envelopes The envelope builder command performs the following tests to detect whether or not model graphics, which are not associated with the design area selected, encroach on the volume represented by the design area: If the envelope file that corresponds to the model is up-to-date with respect to the model, the envelope builder will not re-create the envelope file. If the envelope file that corresponds to the model is not-up-to-date with respect to the model, but it has interference envelopes in the volume of the selected design area, then the envelope file for the model is re-created. If the envelope file that corresponds to the model is not-up-to-date with respect to the model and it does not have any interference envelopes that fall within the volume of the selected design area, then the envelope builder determines if the model has any components that falls in the volume of the selected design area. If so, the envelope file for that model is re-created. Log files are batch queue error reports for the envelope builder data server. These files will have the extension .blg and are created on the server or workstation in the c:\temp directory from which it was submitted and contains information regarding the error.
2. Basics
23
_ _______________
2.2.2
Understanding Envelope Verification

The Envelope Verification command sorts the models being verified into one of the following categories: Up-To-Date: those interference envelopes that are consistent with respect to the model. Not-Up-To-Date: those interference envelopes that are inconsistent with respect to the model and may require being re-created. This is because either the model has been revised since the interference envelopes were created, or the interference envelope file is non-existent. Not Mounted: an error occurred while mounting the file system where the model resides.
2.2.3
Understanding Envelope Diagnostics

The interference envelope diagnostics command creates MicroStation graphics from the interference envelopes for the model, model name .til. This file is used to view the interference envelopes interactively. You can view the .til within the Envelope Diagnostics command or through MicroStation to verify if the envelopes are correct. The file is in the same directory as the model. Any discrepancies found during this verification process indicate problems in the applicable Envelope Builder and will be reported in a file in the c:\temp directory named after the project or design area with a .evd file extension.
24
_ _______________
2.3 Understanding Interference Checking
The interference detection process and its results will vary depending on the settings defined on the Interference Checker Data form. These settings include: Dual or Single Design Area Ownership Exclusion of Interferences by Discipline Exclusion of Interferences by Model Status
Understanding Interference Checking
2. Basics
Insulation Inclusion or Exclusion for Equipment Envelopes Construction Tolerances for Equipment Envelopes For more information, see Interference Checker Data, page 41.
Batch Interference Checker

Interference checking can be done for the entire project or be broken up into design areas or model pairs. Since the processing time for an entire project is much greater than for a design area and since it is often the case that only a certain design area or set of design areas needs to be checked, the design area options are usually the most efficient. Once a clash is found, it will always belong to the design area or project marker file in which it was found. It is therefore important to use either the Project option or any of the Design Area options consistently for the life of a project. The Project option processes the largest area of the project and encompasses every model file. The Piping Design Area and Design Area options process a smaller division of a project with a limited number of model files. The Piping Design Area Pre-Defined Volume and Design Area Pre-Defined Volume options process each area to be broken down further specifying specific volume coordinates to limit further the number of model files. The Single/Pair Model Check option allows you to define a single model or pair of models to be checked. The Volume Filter toggle specifies a smaller volume of any of the options above. Once the Interference Checker has been run, you can trouble shoot clashes involving a piping files items by reviewing the clashes interactively with the PD_Design software.
25
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 The PD_Design software runs interference checking interactively through the piping design file. This option can check one pipeline at a time or the active model against reference files that have a previously created envelope file.
Interference Checker Input

The following reports are used as input by the PDS Interference Checker: The data collected by the forms interface. Interference envelope files that correspond to model volumes or design areas. Information in the Project Control Database. The approval status of each known interference is stored in the Project Control Database. When an interference is approved, it will no longer be included in future interference reports. This allows all interferences within a project to be resolved, either by changing the approval status of the interference to Approved or by revising the model.
Interference Checker Output

For a description of every possible user- and system-generated reports, see the Understanding Interference Reporting section. The following report is generate by default during the Interence Checker process: PDS Interference Report This report contains all unapproved clashes, sorted first by model combinations then by the type of clash. For instance, all clashes detected between model A and model B would be grouped together. A synopsis of the clashes is included at the beginning of the report. This report also includes the model status of any components involved in a clash for the piping, structural, HVAC, and equipment disciplines. This status is that of the model and not of the clash. These reports are named after the project or design area with a .int file extension and are created each time the checker is run. The interference report is created on the workstation or server in the directory from which the Interference Checker was submitted unless otherwise specified using the Interference Report Management Data option. The report begins with a synopsis of all clashes found during interference processing and includes a report of the clashing items within each of the design files represented in the synopsis.
26
_ _______________
PDS Interference Synopsis vcpipe1.env Number of clashes = 1 wwpipe1.env Number of clashes = 0 wwpipe1.env eqmdl1.env Number of clashes = 0 eqmdl1.env Number of clashes = 0 vcpipe1.env wwpipe1.env Number of clashes = 0 vcpipe1.env eqmdl1.env Number of clashes = 3
2. Basics
PDS Interference Report Date: Model A Design File Name: 28-Jun-93 Time: 13:43:33
vcpipe1
Entire Design Volume Included In Report No __ 2 Item Name _________ PIPING P601-12IN-1C0031-N Not approved PIPING P603-8IN-1C0031-N Not approved Table _____ 5 Row ___ 524291 X Coord _______ E 28 6" Plant Y Coord _______ N 0 0" Plant Z Coord _______ El 0 0" Plant
524299
E 25 0" Plant
N 3 0" Plant
El 0 0" Plant
vcpipe1
Entire Design Volume Included In Report Model B Design File Name: eqmdl1
Entire Design Volume Included In Report PDS Interference Clashes Hard/Hard Clashes No __ 3 Item Name _________ E90LR P601-12IN-1C0031-N Not approved TEST E90LR P601-12IN-1C0031-N Not approved TEST Table _____ 3 Row ___ 524297 X Coord _______ E 17 0" Plant Y Coord _______ N 10 0" Plant Z Coord _______ El 0 0" Plant
3 4
21 3
3 524298
E 14 0" Plant E 10 0" Plant
N 11 6" Plant N 10 0" Plant
El -1 6" Plant El 0 0" Plant
21
E 10 0" Plant
N 11 6" Plant
El -1 6" Plant
Interference Markers All interferences within the project are graphically represented by markers and are used by the Interference Approval Manager. Each time the Interference Checker detects an interference within the project, a marker is written to one of the marker files. The marker files are created in the project directory during
27
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 project creation. They are named after the project database and have a .dgn file extension. A marker design file is also created as each design area is defined in the Project Control Database. The interference markers are numbered in the .int report with a system-assigned sequential number starting with 1. A marker design file is created for each design area; the name of the file is the same as the area name and the file extension indicates the discipline, for example, 1=piping, 2=equipment, and so forth. Error File. If an error is found while running the Interference Checker, the system writes the item name and an error code in a file named after either the project or design area, depending on the option selected to run the Interference Checker, with a .icl file extension in the c:\temp directory. Run-time errors are written to a file with a .err file. Log files Each batch job creates a log file with a .ilg file extension. Any run-time errors will be listed in these log files in the c:\temp directory. Project Control Database Records The following tables are updated by Interference Checking: Job Data A record is created each time Interference Checking is run. Clash Data Per Project A record is created for each clash in the project. The unique_clash_id uniquely identifies a clash. Interference Clash Data Per Job A record is created each time a clash is encountered. Component Interference Clash Data Per Project A record is created for each model item that is involved in one or more clashes. These records are used by subsequent executions of the Interference Checker and Interference Approval Manager. Clash Plots These files are named by the system as the marker number with the extension .plt and placed in the c:\temp directory; or you can use the Interference Plot Management Data to specify a node and directory. You can also define that the system generates a default or detailed clash. The system automatically generates the plots through the PDifc_plot queue. For more information, see Plot Clashes, page 98. These files can be reviewed interactively through MicroStation, or they can be plotted. The plot shown on the following page is a detailed plot.
28
_ _______________
2. Basics
29
_ _______________
2.4
Understanding Interference Approving

The Interference Approval Manager is used to review all interferences in a project or area and revise the approval status of single interference markers or a group of interference markers.
2.5
Understanding Interference Plotting

The Interference Plot Manager option plots clashes generally by Project or Design Area. Within these choices, you can plot clashes by: The clash plot status. The clash approval status. The clash review status. The clash category. The group or individual clash selections from a list of clashes in marker file. The Interference Plot Management Data option defines a default node and path for future clash plot files. Defining a default node and path is a required step in the Interference Checking Process. Problems could occur later in the process if this step has not been completed.
2.6
Understanding Interference Reporting

The PDS Interference Report is generated automatically during interference detection and reports specifically on clashing items. The Interference Report Manager creates and revises report formats, discrimination data and report files. The interface and process for interference reporting is similar to that used in the PDS Report Manager module. These reports are more specific project-control reports. The Interference Report Management Data option establishes a default node and path for report files.
30
_ _______________
2.7 Basic Interference Checklist
The following list provides the basic steps for building envelopes, checking for interferences, and managing clashes. Project/Area Creation Decide on a Project or Design Area interference philosophy. Interference Checker Data
Basic Interference Checklist
Define the matrix for discipline responsibility and define intra-discipline checking. Also define single or dual responsibility to design areas. Envelope Builder Generate envelope files using the Envelope Builder option. The system generates envelopes files named after the model; they have a .env file extension. Review the batch log file if it is generated. If errors occur, batch queue error reports for the envelope builder data server are stored in c:\temp and named after the project, design area, or model; they have a .blg extension. The file contains a detailed description of the processed files. Envelope Verification Review the verification errors file if it is generated. If errors are found during the verification process, a log file containing detailed information of the errors is generated and named after the project or design area; it has a .err extension. The location of this file is determined by the Interference Report Management Data. If a .err file is generated, it usually indicates that an envelope does not exist, is out of date, or the software is having difficulty accessing the files. It can also indicate problems with individual envelopes. Envelope Diagnostics Use the Envelope Diagnostics to generate and interactively view a MicroStation-type graphics file; it is named after the model and has a .til file extension, and is in the same directory as the model. This file can be viewed using the Create and Review Diagnostics File, or it can be viewed in MicroStation. Review the envelope diagnostics file if it is generated. If errors are found during the diagnostics process, a log file containing detailed information of the errors is generated and stored in c:\temp. It is named after the model and has a .evd extension. Interference Checker Process design areas or the entire project using the Interference Checker command.
2. Basics
31
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 The system generates marker files, which hold all found clashes. These marker files are named after the project or design area. In the case of a design area, the file extension is the number that represents the discipline of the design area. For instance, for a Piping design area, the file extension would be .1. Review the interference report generated by the system named after the project or design area with a file extension of .int.
Interference Approval Manager Review clashes. Approve and unapprove clashes. Plot clashes. Create an unapproved clash report. This file is named after the project or design area with a .mgr file extension.
32
_ _______________
2.8 Clash Categories
The Interference Approval Manager and the reports created by the Interference Checker distinguish between three categories of interference clashes: Hard A clash between actual physical components, equipment, or structures. Soft A clash between nonphysical space envelopes, for example, insulation, maintenance accessways, or safety envelopes.
Clash Categories
Construction A clash or discrepancy between the user-defined distance and the actual distance of two components in specified disciplines defined using PD_Project. For instance, if piping components are required to be at least 1" away from all structural components but one is found closer, a Construction clash is reported.
2. Basics
Clash Precedence
The precedence for reporting clashes is Hard, Soft, and Construction. This results in interference clashes being reported in one of the following categories. The report will contain only the category of clashes with the highest precedence in accordance with the following precedence table: Hard - Hard Hard - Soft Hard - Construction Soft - Soft Soft - Construction Construction - Construction.
Hard - Hard Example

The following example contains clashes between actual physical components. It would be categorized as a Hard - Hard clash.
33
_ _______________
Hard - Soft Example

The following example displays a clash between an actual component and space that has been allocated for maintenance accessways. It would be categorized as a Hard - Soft clash.
34
_ _______________
2.9 Project Setup
The following items list specific consideration of which you should be aware during project setup: 1. Load PDS 3D products. It is necessary that all servers and workstations be loaded with the latest release of PDS and nucleus software. The PDS software between servers and workstations must be compatible to run correctly. It is highly recommended that you read the Release Notes of the PD_CLASH README file when new releases are issued so that you will be informed of any changes made to the product. The CAD Support person would most likely do this. 2. Set up plot queues. The Interference Checker/Manager provides one default and four optional plot queues for different types of plotters. The selection of the plot queue applies to all graphic interference clash plots in a batch process. Multiple queues provide the flexibility in situations that arise which require different plotters for different paper types. This step would be completed by the CAD Support/System or Project Manager. 3. Set up Interference Checker queues.
Project Setup
2. Basics
The Interference Checker/Manager provides the option of distributing clash checking with pipe queues. Also, PD_Clash, PD_Shell, and MicroStation must be loaded onto each server or workstation for which a pipe queue has been directed. This step would be completed by the CAD Support/System or the Project Manager. 4. Define discipline responsibilities. Area and model data are used by the interference software to locate the models within a specific design area for processing. This is done when the areas and model files are created. The location of the area marker file and model design file are stored by the system. For the architecture files, the locational data is provided by input from the PDS Project Environment Manager. This step would be done by the Project Administrator. Marker files are used by the software to place graphic markers for clashes that are detected during interference checking. 5. Decide on Project or Design Area processing. Interference checking can be done for the entire project or be broken up into small portions called design areas. The processing time for an entire project is much greater than for a design area. Also, it is often the case that only a certain design area or set of design areas needs to be checked. Once you decide which method to use, either the Project option or the design area options, remain consistent. The more consistent you are with your option selection, the more consistent the results will be. For
35
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 example, you might select a design area option and receive the results for one design area. You might correct a few of the interferences and then run interference checking with the Project option. Remember, the interference checker will only report new clashes, therefore, old clashes would not be reported again although they may still exist in the design area that was first checked. 6. 7. Edit the control script to identify the location of the project data. Set up a project and create the associated project database schema.
Model Files
A set of model files for the project must be defined before you can use the Interference Checker/Manager. The file privileges for the specified files will be verified. Refer to the following documents for information on creating and manipulating PDS 3D Models: Piping Design Graphics Reference Guide PDS Equipment Modeling Reference Guide MicasPlus ModelDraft Reference Guide PE HVAC Modeling Reference Guide EE Raceway Modeling Reference Guide FrameWorks Plus Reference Guide.
36
_ _______________
2.9.1 Redirected Processing
Since interference checking is process intensive, the Interference Checker/Manager allows you to redistribute interference checking to another workstation or server on the LAN. Each workstation involved must have PD_Shell and PD_Clash loaded as (l)ocal or (c)lient. If you are redirecting to a server, the applications may be loaded as (s)erver. The following list describes the three redistribution functions.
Redirected Processing
Redirection Functions
Activation This function consists of starting the interference checking process by selecting the project or area to be checked, setting the plotting node, and submitting the job through a pipe queue. Administration This function consists of assigning pairs of files for comparison and tracking their progress through a process called checkerserver, and reporting clash data to the project database through a process called markerserver. This job is run through a batch queue, PDclash_server. Processing This function consists of processing all interference-checking tasks assigned by the Administration function. Usually, the Activation is done on one workstation and Administration and Processing are done on another workstation/server.
2. Basics
Understanding Redirection Queues

The workstations that are involved in redirected processing are connected by pipe queues. A pipe queue is set up from the workstation that activates the interference checking process to the second workstation/server. The actual administration processing will be handled by the batch queues on the second workstation/server. These are automatically created during software installation. Make sure that all of the pipe queues that will be used during redirected processing are pointing to the correct destinations and not just residing on the workstations from a previous configuration.
Redirection Queues Example

Node 1 (Activation) PDclash_server@node1(Pipe to node2) Sends the interference activation message to Node 2 to begin the Administration function. By default this queue is a batch queue which delegates processing assignments locally. However, it is changed to pipe queue on Node 1 when Administration is to be done on a remote node as illustrated in the Redirected Processing Example.
37
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Node 2 (Administration) PDclash_server@node2(Batch) Receives the activation message from Node 1 to begin Administration and invoke Processing. By default this queue is created automatically at software installation as a batch queue. It is started on Node 2 by the pipe queue of the same name which resides on Node 1, PDclash_server@node1. When processing is complete, it compiles the marker data and creates a report sent by email to Node 1. (Processing) PDclash_checker@node2(Batch) Executes the interference checking assignment. This queue is always a batch queue, and is created automatically at software installation. PDcheck_1@node2(Pipe to local) Is created automatically at software installation. However, when setting up for redirected processing, this queue is not used. Its existence is not required for redirected processing nor will its absence prevent redirected processing.
Redirected Processing Example

In the following example Node 1 performs the Activation, and Node 2, which is the network server, performs the Administration and Processing. For C300 and C400 servers with large amounts of memory (64 MB or more) there is little perceived degradation in system performance for other users of this server on the network.
38
_ _______________
3. Interference Management
This option activates the Interference Management form. It is used to provide access to the Interference commands. These commands build and verify envelope files, process the envelope files for interference clashes, review interferences, report on and plot clashes, and review or revise the approval status of interferences.
Interference Management
3. Management
Commands
Envelope Builder Creates and updates interference envelopes for PDS and non-PDS model files. For more information, see Envelope Builder, page 60. Interference Checker Detects interference clashes in the specified model, design area, project, or volume. For more information, see Interference Checker, page 90. Interference Checker Data Makes the envelope-building process and the interference-detection process more specific. You can specify single or dual design area ownership for use in Interference Approval Manager and Interference Plot Manager. You can specify a discipline matrix used by Interference Checker and Interference Builder to define the combinations of disciplines that are to be checked or specify intra-discipline checking. You can exclude interference detection by model status range and include or exclude equipment insulation during interference detection. You can also define whether or not to consider the construction tolerance for certain equipment envelopes. For more information, see Interference Checker Data, page 41. Interference Approval Manager Reviews and revises interferences on a project or area wide basis. For more information, see Interference Approval Manager, page 112. Interference Management Data Checks the model files and displays the complete file specifications of those files which are interference checkable. For more information, see Interference Management Data, page 180.
39
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Interference Plot Manager Plots interference clashes based upon search criteria using Interference Management data or markers selected interactively. The clashes are given unique plot numbers within the group of interference clashes being plotted. For more information, see Interference Plot Manager, page 190. Interference Plot Management Data Specifies the network address and path name in the Project Control Database to define where the system sends all plot files. For more information, see Interference Plot Management Data, page 196. Interference Report Manager Uses definition data to generate user-defined interference management reports. For more information, see Clash Report Manager Form, page 198. Interference Report Management Data Specifies the network address and path name in the Project Control Database to define where the system sends all Interference Management reports. For more information, see Interference Report Management Data, page 238. Scheduled Envelope Build/Clash Detect Defines a schedule for building envelopes and running clash detection. For more information, see Scheduled Envelope Builder and Clash Detection, page 239.
40
_ _______________
3.1 Interference Checker Data
Interference Checker Data
This option activates the Interference Checker Data form, which allows you to make the envelope-building process and the interference-detection process more specific. The following examples will be better understood once you have read all of the command descriptions. There are many ways to specify the interference-detection process. You can define an interference matrix that specifies which disciplines are checked against each other. For instance, for all Equipment design areas, you can define a matrix that would only check Equipment design areas against Piping design areas and against Equipment design areas. In a different situation, you may decide to use the No Intra Discipline Interference Check command to specify: Models in the specified discipline are NOT checked against each other and are NOT checked internally. Models in the specified discipline are checked against models from all other disciplines. All models from all other disciplines are checked against each other.
3. Management
Along with the No Intra Discipline Interference Check command, you can also specify dual-design area ownership. (See the Single (1) Design Area Ownership / Dual (2) Design Area Ownership discussion on the following pages for more information.) Dual-design area ownership ensures that only the design areas that own a component involved in a clash can own the clash. Therefore, with the combination of No Intra Discipline Interference Check command and dual-design area ownership, the interference-detection process would be as follows: Models in the specified discipline are NOT checked against each other and are NOT checked internally. Models in the specified discipline are checked against models from all other disciplines. The third part of the No Intra Discipline Interference Check command (all models from all disciplines checked against each other) would not be used; dual-design area ownership specifies that a design area can only own a clash if it owns at least one of the conflicting components. The possibilities are limitless. You can combine all of the Interference Checker Data options to specify the exact interference-detection process that is needed.
Commands
Single (1) Design Area Ownership / Dual (2) Design Area Ownership This toggle allows you to detect clashes when more than one design area needs to own, review, or approve a clash. For more information, see Single/Dual Design Area Ownership, page 43.
41
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Exclusion of Interferences by Discipline This option allows you to specify how clashes are to be reported for combinations of disciplines. For more information, see Exclusion of Interferences by Discipline, page 47. Exclusion of Interferences by Model Status This option allows you to specify a low and high model-status range. For more information, see Exclusion of Interferences by Model Status, page 54. Equipment without Insulation / Equipment with Insulation This option allows you to specify whether or not insulation is to be included as a factor in clash detection. For more information, see Equipment without/with Insulation, page 56. Construction Tolerances for Equipment Envelopes This option allows you to enable or disable construction tolerances. For more information, see Construction Tolerances for Equipment Envelopes, page 57.
42
_ _______________
3.1.1 Single/Dual Design Area Ownership
This toggle allows you to detect clashes when more than one design area needs to own, review, or approve a clash. Setting this toggle to Dual (2) Design Area Ownership is useful when more than one design area needs to own, review, or approve a clash. This toggle provides the following capabilities: Dual Ownership Ownership available to each design area that contains a component involved in a clash (when interference detection is run on that area). See Models Checked later in this section for other implications associated with this option. OR
Single/Dual Design Area Ownership
Single Ownership Ownership assigned to the first design area to find the clash. Dual ownership does not mean that ownership is automatically given to both design areas when a clash is found. It means that ownership is available to both design areas when interference detection is run on each. Because clashes are stored in the database, reports can still be run on both design areas involved in a clash, even if interference detection has not been run on both design areas. However, clashes are only written to the applicable design areas marker file during the interference detection process for each design area. Therefore, clashes can only be reviewed and approved in design areas on which interference detection has been run. This is another filter that can be used in conjunction with all other Interference Checker Data options to affect the interference detection process. This toggle does not define ownership assignments once clashes have been found. It acts as another filter in the interference detection process.
3. Management
43
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 By default, clash checking is done in Single (1) Design Area Ownership mode. In this mode, each clash belongs to the design area in which it was first found. When clash checking is done in this mode, clashes involving models that do not belong to the design area being checked are still assigned to that design area. For instance, if design area C were checked for interferences in the Single (1) Design Area Ownership mode, the system would compare all models that fall within the specified volume, including: - All models against themselves - All design area A models against design area B models - All design area C models against design area A models - All design area C models against design area B models.
All of the clashes would belong to design area C. In the Dual (2) Design Area Ownership mode, ownership is not based on the first design area to find the clashes, but on the design areas that own the components involved in a clash. Dual (2) Design Area Ownership is different from Single (1) Design Area Ownership in two aspects: the models that are checked and the clash area ownership.
Models Checked using Dual Area Ownership

Interference checking is performed between models belonging to the design area being checked and all other models that fall within the volume of that design area. Clashes that do not involve at least one component from the design area being checked are not found. For example, when Piping design area A is checked, only clashes that involve at least one item from Piping design area A are reported. Clashes not involving one or both items from a model in Piping design area A are not reported, such as internal equipment, structural, and raceway clashes. Also not reported are clashes only involving other Piping design areas (B, C, and so forth) or clashes involving an item in these other Piping Design Areas and areas from other disciplines. The implication of using Dual (2) Design Area Ownership is that each design area from each discipline must be interference checked to ensure that all clashes are found.
The system ignores the Dual (2) Design Area Ownership setting when checking areas in the Clash discipline, because there are no models in the Clash discipline.
44
_ _______________
Clash Ownership
If design area C were checked for interferences in the Dual (2) Design Area Ownership mode, the system would compare models in design area C with models falling within the specified volume including: - All design area C models against themselves - All design area C models against design area A models - All design area C models against design area B models.
Single/Dual Design Area Ownership
The clashes found involving, for instance, design area C models against design area A models would be owned by design area C. Clashes could be reviewed and approved in design area C and reports could be run on either design area C or design area A. You could not review or approve clashes in design area A until you had run interference detection on it.
3. Management
Clashes that do not involve at least one component from design area C models are not found.
Setup for Clash Management

Consider the following possibilities of using PDS to design a plant: Design by system interference checking by piping design area. Design by geography interference checking by volume (no overlaps in volumes). Design by system or by geography interference checking by volume (with overlaps). Consider a project with the following disciplines as an example. These comments are not limited to these disciplines, but have been restricted to four disciplines to simplify the description: Piping, Equipment, Structural, or Raceway. Consider for the purpose of this description that each discipline consists of three design areas for each discipline. As an example, P1, P2, and P3 are design areas for Piping; E1, E2, and E3 are design areas for Equipment; S1, S2, and S3 are design areas for Structural; and R1, R2, and R3 are design areas for Raceway. For the first option, Design by system interference checking by design area, the discipline matrix must be defined as follows if the dual clash ownership option is to be enabled. Note that each design area must be interference checked.
45
_ _______________
Design Area P1 P2 P3 E1 E2 E3 R1 R2 R3 S1 S2 S3 Inter-Discipline Options in Matrix P-P, P-E, P-S, P-R P-P, P-E, P-S, P-R P-P, P-E, P-S, P-R E-E, E-S, E-R E-E, E-S, E-R E-E, E-S, E-R R-R, S-R R-R, S-R R-R, S-R S-S S-S S-S
This discipline matrix results in the minimum number of comparisons between models in the project, while ensuring that all potential clashes are reported (that is, all possible combinations of models have been checked). With the dual clash ownership option enabled, clashes involving other design areas of the same discipline as the primary design area will not be reported with the primary design area. For example, when checking design area P1 in the previous example, although clashes between design area P1 and design area P2 (and between design area P1 and P3) are reported, clashes that are internal to design area P2 and internal to design area P3, and clashes between design area P2 and design area P3 are not reported. With the discipline matrix described above, clashes reported in two design areas (that is, dual clashes), can only exist within the design areas of a single discipline. In other words, dual clashes can only be intradiscipline clashes. The dual clash ownership option is more applicable where each engineering department is responsible for its clashes and selected interdiscipline clashes. In other words, a centralized interference checking organization does not exist. The user must decide which discipline departments will manage which inter-discipline clashes. In the preceding example, the structural department, although responsible for internal structural clashes, is not responsible for managing any inter-discipline clashes, while the electrical department is only responsible for managing internal electrical clashes and structural-electrical clashes. This setup has a restriction that both the piping design areas and the equipment design areas must be checked independently of each other, although the same department may be responsible for both disciplines.
46
_ _______________
3.1.2 Exclusion of Interferences by Discipline
Exclusion of Interferences by Discipline
This command allows you to define a matrix of discipline combinations for each discipline for envelope-building and interference-detection purposes. If you do not define a matrix for a specific discipline, you can specify whether intra-disciplinary interference detection is turned on for each discipline. You must select one of the three options for each Active Discipline that you define. It is important to remember that all clashes found between all disciplines during an interference checker run, are owned only by the first design area that finds it unless dual-design area ownership has been specified. The default mode is that no discipline matrix is defined and that the Intra Discipline Interference Check command is enabled.
Why Define a Matrix?

Frequently, designers are specifically interested in potential clashes involving models of their own discipline with models from one or more other disciplines. The Discipline Matrix Interference Check command allows designers the flexibility to check only for clashes that fall within the scope of their responsibilities. See the following examples. It is the responsibility of the people defining the interference matrices to ensure that all possible discipline combinations are considered. An Equipment designer may only be responsible for intra-disciplinary (Equipment against itself) clashes and clashes involving Equipment and Structural models. This designer would need to define intra-disciplinary checking for Equipment (Equipment against itself) and Equipment against Structural within the Equipment matrix.
3. Management
47
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 For the Raceway designer, most of the clashes that may be of concern are found between the Structural and Raceway disciplines. The Raceway matrix would limit envelope building and interference detection to only those two disciplines for all Raceway design areas.
A Structural designer only concerned with clashes between and within Structural models would want to specify that only intra-disciplinary checking be performed for all Structural design areas.
It is important not to confuse the function of the Intra Discipline Interference Check command with a matrix that only performs intra-disciplinary checks for a discipline. The Intra Discipline Interference Check command not only checks the specified discipline against itself and each model internally, it checks that discipline against all other disciplines and all disciplines against each other. The Intra Discipline Interference Check command would not be appropriate in this case, since the Structural Designer only wants to find Structural against Structural clashes.
48
_ _______________
A Piping designer may be interested in how Piping is going to affect all disciplines, including Piping. In this case, a Piping matrix that includes all disciplines or the Intra Discipline Interference Check command could be specified for the Piping Discipline.
It is important to remember that all clashes found between all disciplines during an interference checker run are owned only by the first design area that finds it unless dual-design area ownership has been specified.
3. Management
Understanding the Effect of a Matrix

The Discipline Matrix Interference Check command allows you to specify which disciplines are considered for envelope building and interference detection for all design areas within a discipline. In the previous section, Why Define a Matrix?, different discipline-scenarios were presented. To explain how a matrix affects the other interference processes, consider the Equipment matrix. The Equipment designer is only responsible for intra-disciplinary clashes and clashes involving Equipment and Structural models. The matrix would be defined as follows:
49
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 When a matrix is defined, the system only includes models that belong to the disciplines involved in the matrix for interference checking. The responsible engineering discipline, as defined in the Model Data Table (PDtable_113, column 15) of the Project Control Database, is used to determine which models to include in the envelope-building process. All models defined with the responsible engineering discipline of Equipment or Structural are included.
Once the envelopes have been built, the Interference Checker only checks the combinations of disciplines specified in the matrix. Redundant comparisons are not performed.
Reviewing and Modifying Matrices

To review or modify a matrix for a given discipline, first select a discipline from the Primary Discipline field to define the Active Discipline. Next, select a discipline from the Primary Discipline field. In the Against Discipline field, the system highlights the disciplines that the primary discipline will be checked against. Do this for each of the disciplines in the Primary Discipline field in order to see the entire matrix for the active discipline. You can modify the matrix for any or all disciplines; then click Accept.
50
_ _______________
Commands
Intra Discipline Interference Check Allows you to define that the interferencedetection process for the Active Discipline includes all possible combinations for that discipline: Models within the specified discipline are checked against each other and are checked internally. Models within the specified discipline are checked against models from all other disciplines. All models from all disciplines are checked against each other. Select a discipline from the Primary Discipline field. This discipline becomes the Active Discipline. Select the Intra Discipline Interference Check command, and click Accept. You can continue with this two-step process for as many disciplines as necessary. You should specify a matrix for the disciplines that do not require this sort of checking. If a matrix is defined after this command has been specified, the system overrides this command and uses the matrix definition. If the command is specified after a matrix has been defined, the system overrides the matrix and uses the command. The engineering discipline, as defined in the Model Data Table (PDtable_113, column 2) of the Project Control Database is used for determining the discipline of a model for this command.
3. Management
51
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 No Intra Discipline Interference Check Allows you to define that the interference-detection process for the Active Discipline includes the following: Models within the specified discipline are not checked against each other and are not checked internally. Models within the specified discipline are checked against models from all other disciplines. All models from all disciplines are checked against each other. Select a discipline from the Primary Discipline field. This discipline becomes the Active Discipline. Select the No Intra Discipline Interference Check command, and click Accept. You can continue with this two-step process for as many disciplines as necessary. You should specify a matrix for the disciplines that do not require this sort of checking. If a matrix is defined after this command has been specified, the system overrides this command and uses the matrix definition. If the command is specified after a matrix has been defined, the system overrides the matrix and uses the command. The engineering discipline, as defined in the Model Data Table (PDtable_113, column 2) of the Project Control Database is used for determining the discipline of a model for this command. Discipline Matrix Interference Check Allows you to define a discipline matrix for each discipline. Select a discipline from the Primary Discipline field to define it as the Active Discipline. Then select a discipline from the Primary Discipline field to begin defining the matrix. From the Against Discipline field, select all of the disciplines to be checked against the discipline that is highlighted in the Primary Discipline field. You can continue with this two-step process as many times as necessary, and click Accept. The responsible engineering discipline, as defined in the Model Data Table (PDtable_113, column 15) of the Project Control Database is used for determining the discipline of a model for this command. If prompted to... Accept or Select Other Option Select one of the options to enable or disable intra discipline checking and click Accept or select the matrix option. Select Discipline Select a discipline to be the Active Discipline. Do this:
52
_ _______________
Accept Or Select Another Discipline Select all of the secondary disciplines to include in the matrix, and click Accept. Once you have selected the Active Discipline, you cannot change it until you reactivate the Exclusion of Interferences by discipline command.
3. Management
53
_ _______________
3.1.3
Exclusion of Interferences by Model Status

This command specifies a low and high model-status range. Models that fall within this range are not included during the envelope-building process or the interference-checking process. This command normally is used to exclude Temporary or Preliminary models.
The model status for each model is defined using the Project Environment command in the Project Administrator. Defining the model status is part of creating or revising a model. When the Model Status field is selected, the Model Status code list (SN1605) is displayed. This code list can be modified using the Revise option of Standard Note Library Manager command in the Reference Data Manager module. This code list is delivered with the following definitions: 1 11 12 21 Undefined Preliminary Temporary Permanent
The model status for each model is recorded in the Model Data Table (PDtable_113) of the Project Control Database. The range you specify on the Interference Checker Data form is checked against the numbers in the Model Status code list (SN1605). The range you specify is recorded in the Project Control Data Table (PDtable_103) of the Project Control Database and is then used to determine which models are excluded. For instance, if your low range is set to 11 and your high range is set to 12, all of the models that are defined with a model status of Preliminary or Temporary, using the delivered Model Status code list, would not be included during the interference building or checking process.
54
_ _______________
The model status set for models is independent of the model status set for the DesignReview Label Builder. Because the models that fall within the selected range are not included in any interference processing, they are not displayed when you select the Model option within the Envelope Builder or for the Single/Pair Model Check option within the Interference Checker.
Exclusion of Interferences by Model Status
3. Management
55
_ _______________
3.1.4
Equipment without/with Insulation

This command specifies that the Envelope Builder option either excludes or includes insulation based on the equipment attribute value when creating interference envelopes for equipment models. By default, insulation is not added to interference envelopes created for equipment models.
56
_ _______________
3.1.5 Construction Tolerances for Equipment Envelopes
This command enables or disables construction tolerances for the equipment interference envelope types displayed on the form. By default, the construction tolerances for the specific envelopes shown on the form are not considered. Construction clashes representing disabled equipment envelope types are not reported. The envelope types are enabled when they have been selected.
Construction Tolerances for Equipment Envelopes
3. Management
57
_ _______________
58
_ _______________
4. Envelopes
This section provides information on envelopes in the following order: 4.1
Envelopes
Envelope Builder This option activates the Envelope Builder form. It is used to create envelope files for all of the models in the specified project, design area or individual model. See Envelope Builder, page 60 for more information. PDS Clash Detection with Non-PDS Models See PDS Clash Detection with NonPDS Models, page 77 for more information. Envelope Verification This option activates the Envelope Verification form. It is used to verify the integrity of the envelope file and to determine if the creation dates of the envelope files are recent or more recent than the revision dates of the corresponding model files. See Envelope Verification, page 81 for more information. Envelope Diagnostics This option creates and allows you to review MicroStation-type graphics from the interference envelopes for a selected model in a design file. Any previously-created graphics are deleted automatically from the envelope diagnostics file before creating new envelope diagnostic graphics. See Envelope Diagnostics, page 85 for more information.
4.2
4.3
4.4
4. Envelopes
59
_ _______________
4.1
Envelope Builder
This command activates the Envelope Builder form. It is used to create envelope files for all of the models in the specified project, design area or individual model. All structure models must be propagated before you can use the Envelope Builder to create envelope files for the models. Otherwise, the envelopebuilding process will fail and errors messages can occur.
Envelope File
An envelope file contains the basic geometric definition of whatever design object is in the design model. The purpose of the envelope file is to define, for the clash checker, the size, shape, area, volume (which is adjusted to include insulation/fire protection if defined in the model), location, name, and any other information that might uniquely identify a component and its properties. Think of it as an envelope of information surrounding an element or elements. The envelope building process and its results will vary depending on the way the Interference Checker Data command is defined. The settings that affect envelope building are shown below. Dual or Single Design Area Ownership Exclusion of Interferences by Discipline Exclusion of Interferences by Model Status Insulation Inclusion or Exclusion for Equipment Envelopes Construction Tolerances for Equipment Envelopes For more information, see the Interference Checker Data, page 41.
Model Status
The Envelope Builder includes the model status of each component involved in a clash. This status is not that of the clash in which the model is involved, but the status of the components model. Models that are of a status that has been excluded using the Interference Checker Data command are excluded from the model building process. The Interference Checker reports the model status of each component involved in a clash in the interferences report named after the project or design area with the .int file extension. See the Interference Checker Output section of Understanding Interference Checking, page 25, for more information.
60
_ _______________
Exclusion Tables
Exclusion tables are used during envelope generation to make intelligent envelopes. Interference detection then reports more precise clash information. See the Reference Data Manager Reference Guide for detailed information on each of the following tables. COMPONENT INSULATION EXCLUSION DATA (PDtable_231) The Component Insulation Exclusion Data is used to completely or partially exclude the insulation of components on insulated lines with respect to interference checking.
Envelope Builder
For each piping component, piping specialty, or instrument component (excluding pipes) on an insulated line, the Piping Envelope Builder will search the Component Insulation Exclusion Data Table on the basis of the following data to determine whether or not insulation should be completely excluded from that components interference envelope. green nominal piping diameter of the component (range search) red nominal piping diameter of the component (range search) heat tracing requirements (range search) insulation purpose (range search) normal operating temperature (range search) For piping commodities, the Piping Envelope Builder searches for the components commodity name in the Component Insulation Exclusion Data Table using the preceding data.
4. Envelopes
If the piping commodity is defined in the exclusion table for those conditions, the applicable insulation thickness will not be added to the components interference envelope. If the commodity name is not specified in the exclusion table for those conditions, the Piping Envelope Builder searches for the components model code using the same data. If a match for those conditions is found on the basis of model code, the applicable insulation thickness will not be added to the components interference envelope. Otherwise, the insulation thickness will be included in the components interference envelope. For piping specialties and instrument components, the Piping Envelope Builder searches for the components model code in the Component Insulation Exclusion Data Table using the preceding data. If the component is defined in the exclusion table for those conditions, the applicable insulation thickness will not be added to the components interference envelope. Otherwise, the insulation thickness will be included in the components interference envelope.
61
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 The piping segment data (heat tracing requirements, insulation purpose, and normal operating temperature) are determined on the basis of the piping segment that is associated with the first connect point of the applicable component. You must rerun the Envelope Builder before changes to this table are reflected in the envelope file. FLANGE INSULATION EXCLUSION DATA (PDtable_232) The Flange Insulation Exclusion Data provides for partial exclusion of flange insulation thickness from the generation of interference envelopes. The Piping Envelope Builder searches for matching data in this table for each bolted end of each piping component or instrument component on an insulated line that are determined to be insulated. The Piping Envelope Builder searches for matching data on the basis of the following data to determine whether or not insulation should be excluded from the flange outside diameter of that bolted end of the component. nominal piping diameter of the bolted end (range search) heat tracing requirements (range search) insulation purpose (range search) normal operating temperature (range search) If matching criteria is found in the exclusion table for these conditions, the applicable insulation thickness will not be added to the flange outside diameter of the bolted end of that components interference envelope. Otherwise, the insulation thickness will be included in the components interference envelope. You must rerun the Envelope Builder before changes to this table are reflected in the envelope file. The piping segment data (heat tracing requirements, insulation purpose, and normal operating temperature) are determined on the basis of the piping segment associated with the first connect point of the applicable component. The Piping Eden modules for the interference envelopes that are to consider the partial exclusion of insulation from the flange outside diameter of a bolted end, must be revised to accommodate this option. If you do not change any or all of the Piping Eden modules for the interference envelopes, this table will have no impact and the interference envelopes will include complete insulation, when applicable. PIPING CONSTRUCTION TOLERANCE EXCLUSION DATA (PDtable_233) The Piping Construction Tolerance Exclusion Data can be used to completely or partially exclude construction tolerance from being added to interference envelopes. This feature only applies to Piping vs. Piping construction tolerances.
62
_ _______________
Envelope Builder
For each piping or instrument component, excluding pipes, the Piping Envelope Builder searches Table 233 on the basis of the following data to determine whether the Piping versus Piping construction tolerance should be excluded from that components interference envelope. green NPD of the component (range search) red NPD of the component (range search) For piping commodities, the Piping Envelope Builder searches for the components commodity name in the Piping Construction Tolerance Exclusion Data Table using the preceding data. If the piping commodity is defined in the exclusion table for those conditions, the applicable construction tolerance will not be added to the components interference envelope. If the commodity name is not specified in the exclusion table for those conditions, the Piping Envelope Builder will search for the components model code using the same data. If a match for those conditions is found on the basis of the model code, the applicable construction tolerance will not be added to the components interference envelope. Otherwise, the construction tolerance will be included in the components interference envelope. For piping specialties and instrument components, the Piping Envelope Builder searches for the components model code in the Piping Construction Tolerance Exclusion Data Table using the preceding data. If the component is defined in the exclusion table for those conditions, the applicable construction tolerance will not be added to the components interference envelope. Otherwise, the construction tolerance will be included in the components interference envelope.
4. Envelopes
Defining Pipe-like Components

You can define up to 10 piping commodities to be treated as pipe-like components, such as branch nipples or in-line nipple for interference detection. These components can be defined by commodity name in the Commodity Name Table of the Piping Job Specification Table Library. The following entries in the Commodity Name Table are reserved for this purpose.
63
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 51 pipe-like commodity name 1 52 pipe-like commodity name 2 53 pipe-like commodity name 3 54 pipe-like commodity name 4 55 pipe-like commodity name 5 56 pipe-like commodity name 6 57 pipe-like commodity name 7 58 pipe-like commodity name 8 59 pipe-like commodity name 9 60 pipe-like commodity name 10 You can also define up to 10 piping commodities, piping specialties, or instrument components to be treated as pipe-like components for interference detection. These components can be defined by model code in the Commodity Name Table of the Piping Job Specification Table Library. The following entries in the Commodity Name Table are reserved for this purpose. 61 pipe-like model code 1 62 pipe-like model code 2 63 pipe-like model code 3 64 pipe-like model code 4 65 pipe-like model code 5 66 pipe-like model code 6 67 pipe-like model code 7 68 pipe-like model code 8 69 pipe-like model code 9 70 pipe-like model code 10 -
Clash Envelopes for Welds

The clash envelope builder can generate weld clearance envelopes at user defined weld locations in the PDS 3D model. These clearance envelopes can be used to define the spacing needed for weld construction. The criteria used to generate these clearance envelopes are defined in the Weld Clearance Table. Refer to the Weld Clearance Table section in the Reference Data Manager Reference Guide for information on creating this table. When the envelope builder is run on the model, the system scans the pipelines for welds which require a clash envelope based on the Weld Clearance Table. The system adds the clash clearance envelopes based on the following workflow: 1. The system uses the Piping Material Class (PMC) to retrieve the correct Weld Clearance Table, as each Weld Clearance Table is named using the Piping Material Class, i.e. WELD_1C0031. The system uses the weld type and the Nominal Piping Diameter of the weld as input to the Weld Clearance Table to determine the radius increase and the overall length increase for the graphic indicator at the weld.
2.
64
_ _______________
3. The clash envelope builder then uses the output of the Weld Clearance Table to draw the cylinder representing the clash envelope.
Envelope Builder
The weld clearance envelopes are drawn as two shapes, one for each pipe, using the radius increase and overall length increase measurements.
Welds at model limits are a special case. For these welds, the envelope builder places half of the graphic indicator for the weld in each envelope file.
4. Envelopes
The interference checker considers clashes involving weld envelopes as construction type clashes. The weld clearance clash will be considered a more severe clash than the construction / construction type clash. Weld envelopes are regenerated based on the current weld type information each time the envelope builder is run. Therefore, whenever the welds are revised in the model, the Envelope Builder must be run prior to running Interference Detection, to consider the potential impact of the new weld types on the clash envelopes. The weld clearance envelopes will be inserted as additional shapes with a hard-soft type denoting the shape as a construction tolerance shape. The weld clearance is an additional shape at a connect point of an existing component. Note that:
65
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 The weld clearance shape is not considered a separate or independent component. The weld clearance shape has no entry in the database. Interference reporting involving weld clearances will record a construction tolerance clash with the piping component the weld clearance surrounds, rather than a with a (nonexistent) weld clearance entity.
The envelope builder does not generate weld construction tolerance shapes at tap locations. Interactive clash checking in Piping Design will not perform weld construction tolerance checking.
Mechanics
When the envelope option is anything other than Project or Model, a volume is required. This volume can be pre-defined by the user or calculated by the software using the models in the design area. Models in the project that overlap are checked. The envelope file determines overlap when it is current with the model; otherwise, the model file determines overlap. The envelope file is current if it was created since the model was last modified, as recorded in the PDtable_113 of the project database. If no date is stored in the database, the time from the physical model file is used for the comparison. Missing envelope files are recognized as out of date by the software. For structural models, the propagated file time, if it exists, is checked against the envelope file time. If no time is stored in the database for the propagated file, the time of the last modification to the propagated file is checked against the envelope file time. If the envelope file is older, the envelope file will be created. The propagated file times for structural models are updated only when PDS is used to create or regenerate the propagated file. Changing anything in the model outside of PDS does not update the times stored in the PDS the project database. Therefore, the Envelope Builder and Interference Checker will not recognize that the envelope file is out of date if updates were made outside of PDS. If there are model components that are within the same volume represented by the selected design area but are not associated with that design area, the Envelope Builder does one of the following: If the interference envelope is up-to-date for models residing within the volume but not included in the selected design area, the Envelope Builder does re-create interference envelopes.
66
_ _______________
The piping envelope builder does not create insulation envelopes for internal refractory. The range of values, 30 through 39, for insulation purpose is interpreted by the piping envelope builder as internal insulation.
Envelope Builder
If a model or any of its components reside within the volume but not included in the selected design area and the interference envelope for that model either does not exist or is not up-to-date, the interference envelope is recreated.
Application Considerations
For the Model option, the system selects the correct interference envelope builder for each models discipline, including piping, equipment, structural, raceway, HVAC, and PLANTGEN, so envelope files can be created in the Interference Management environment rather than within each disciplines more specific application. For the architectural and userdefined disciplines, the system uses a generic envelope builder. The discipline is determined by the default discipline of the model unless a different Application Type for that model has been specified. The Application Type is defined in the Project Environment Manager on the Create Model Data form within the Project Administrator. This field automatically contains the default discipline of the model but can be changed. For instances, a piping model for circular HVAC ducting can be treated as an HVAC model for clash checking when the Application Type for that model is defined as HVAC. Cutbacks performed in FrameWorks will not be reflected in the envelope. PD_Clash will not report clashes in any situation where the memberlines have a common joint. This may result in clashes not being reported. For example, if a beam is placed by top center on the top of a solid, since the cardinal line matches the outer line of the solid, no clash will be reported.
4. Envelopes
For more information on Application Types, see the Create Model section of the Project Administrator Reference Guide.
67
_ _______________
Commands
Project Creates envelope files for all of the models in the project. See the Create Project Envelope Files, page 69, for more information. Piping Design Area Creates envelope files for all of the models in a piping design area. See the Piping Design Area, page 70, for more information. Piping Design Area Predefined Volume Creates envelope files for all of the models in a design area with the predefined volume defined in the project database. See the Piping Design Area Predefined Volume, page 72, for more information. Design Area Creates envelope files for all of the models in a design area. See the Design Area, page 73, for more information. Design Area Predefined Volume Creates envelope files for all of the models in a design area with the predefined volume defined in the project database. See the Design Area Predefined Volume, page 74, for more information. Model Creates an envelope file for a single model. See the Model, page 76, for more information. Submit Immediately/Delayed Submit Submits or delays submission of the job. When the toggle is set to Delayed Submit, the system will display the following fields and allow you to delay submission until a more convenient time. Include User Defined Disciplines/Exclude User Defined Disciplines Specifies whether to generate envelope files for models in user defined disciplines when generating PDS envelope files.
68
_ _______________
4.1.1 Create Project Envelope Files
This option is used to create envelope files for each of the design files in the entire project. It creates a file with a .env file extension where the model resides for each piping, equipment, structure, HVAC, or electric model file in the project.
Create Project Envelope Files
4. Envelopes
69
_ _______________
4.1.2
Piping Design Area

This option activates a list of piping design areas available for envelope creation. The Envelope Builder creates envelope files for all of the models associated with the selected piping design area. The following tables are used during envelope generation to make intelligent envelopes. Interference detection then reports more precise clash information. See the Exclusion Tables section in the Envelope Builder section and Reference Data Manager Reference Guide for detailed information on each of the following tables. Component Insulation Exclusion Data (231) Flange Insulation Exclusion Data (232) Piping Construction Tolerance Exclusion Data (233) To see the changes, you must re-create envelopes when data is modified.
Field Descriptions
Easting Displays the predefined easting coordinates for the selected design area. Northing Displays the predefined northing coordinates for the selected design area. Elevation Displays the predefined elevation coordinates for the selected design area.
70
_ _______________
Before using this command
Create a design area with a specific volume with the Create Design Area Data option in the Project Environment Manager.
Piping Design Area
4. Envelopes
71
_ _______________
4.1.3
Piping Design Area Predefined Volume

This option activates a list of piping design areas with predefined volumes available for envelope creation. The Envelope Builder creates envelope files for all of the models associated with the selected design area. The system also displays the predefined volume for the selected design area. The Envelope Builder only builds envelopes for the models that are included in the selected piping design area and fall within the predefined volume. Envelopes will not be built for those models that are in the piping design area but outside of the predefined volume. The following tables are used during envelope generation to make intelligent envelopes. Interference detection then reports more precise clash information. See the Exclusion Tables section in the Envelope Builder section and Reference Data Manager Reference Guide for detailed information on each of the following tables. Component Insulation Exclusion Data (231) Flange Insulation Exclusion Data (232) Piping Construction Tolerance Exclusion Data (233) To see the changes, you must re-create envelopes when data is modified.
Field Descriptions
72
_ _______________
4.1.4 Design Area
This option activates a list of design areas available for envelope creation. The Envelope Builder creates envelope files for all of the models associated with the selected design area. The Structural Envelope Builder uses the propagated (frozen) version of the structural model when creating interference envelopes. However, this requires that the model management data is loaded for the sparse structural models through the Project Environment Manager.
Design Area
4. Envelopes
73
_ _______________
4.1.5
Design Area Predefined Volume

This option activates a list of design areas with predefined volumes available for envelope creation. The Envelope Builder creates envelope files for all of the models associated with the selected design area. The system also displays the predefined volume for the selected design area. The Envelope Builder only builds envelopes for the models that are included in the selected piping design area and fall within the predefined volume. Envelopes will not be built for those models that are in the piping design area but outside of the predefined volume. The Structural Envelope Builder uses the sparse version of the structural model when creating interference envelopes. However, this requires that the model management data is loaded for the sparse structural models through the Project Environment Manager.
Field Descriptions

You must have used the Create Design Area Data option of the Project Environment Manager with the Create Interference File option set to On to predefine the volume.
74
_ _______________
Clash Envelopes for Areas with DVCS
Normally, design areas with predefined volumes are based on the Plant Coordinate System (PCS). To build clash envelopes for areas using the Design Volume Coordinate System (DVCS), it is necessary to use the Clash discipline in conjunction with the Design Area Predefined Volume envelope builder command. Refer to the Project Administrator (PD_Project) Reference Guide for more details on DVCS.
Design Area Predefined Volume

Create a Clash discipline, and then create a design area within the Clash discipline. Refer to the Project Administrator (PD_Project) Reference Guide for instructions on creating the Clash discipline and design area.
4. Envelopes
75
_ _______________
4.1.6
Model
This option activates a list of disciplines, piping design areas, and models available for envelope creation. When you select the By Model option, the envelope builder will build an envelope for any model selected, regardless of date.
76
_ _______________
4.2 PDS Clash Detection with Non-PDS Models
PD_Clash can be used to run interference checks on models that are not created with PDS. In PDS, a project can define up to ten engineering disciplines on which clash detection can be run. Under each discipline, areas, and models within the areas, are created and used for interference checking. These disciplines are, 1. 2. 3. 4. 5. 6. Piping Equipment Structural HVAC Raceway Architectural
PDS Clash Detection with Non-PDS Models
7. - 10. User-definable, PLANTGEN or Clash Six of the allowable ten disciplines are predefined by PDS. The other four disciplines are user-definable, that is; you can define up to four additional, non-PDS disciplines that can be used with PDS clash detection. For example, you could have models created with your own, in-house, package; these models can be referred to in PDS models and drawings, for DesignReview sessions, and for clash detection. The models in the four user-definable disciplines need to meet the following guidelines:
4. Envelopes
They must be created outside of PDS, They must be MicroStation-based 3D models, and They must be made part of the PDS project. PLANTGEN can be specified as one or more of the four, user-definable disciplines so that you can check as-built models created with PLANTGEN. One of the four user-defined disciplines can be specified as a Clash discipline, which allows the system to check design areas using the Design Volume Coordinate System. If you need to use the Clash discipline in an existing project that already uses all four user-defined disciplines, you must convert one user-defined discipline to a Clash discipline. Refer to Design Area Predefined Volume, page 74 and the Project Administrator (PD_Project) Reference Guide for more information on the Clash discipline.
77
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 For the first six predefined disciplines, as well as PLANTGEN, PDS calls specific routines for clash detection based on their data structures and requirements. For the four user-defined disciplines that are not specified as PLANTGEN, PDS uses the generic envelope builder, instead of an envelope builder specifically created for the first six disciplines (piping, equipment, structural, HVAC, raceway, and architectural). This generic envelope builder has some limitations which are discussed later in this section. The following disciplines use specific routines to build envelope files: 1. Piping 2. Equipment 3. Structural 4. HVAC 5. Raceway 6. Architectural 7. PLANTGEN 8. 9. 10. The following disciplines use generic routines to build envelope files:
User-defined User-defined User-defined
Creating envelope files in user-defined disciplines

The generic envelope builder creates envelope files for user-defined discipline models within the project or selected area automatically if the Include User Defined Disciplines toggle is set on the Envelope Builder form. You can also select user defined disciplines on the Design Area and Design Area - Pre-defined Volume forms.
Types of elements
The generic envelope builder acknowledges only certain MicroStation elements. Shapes (Type 6) inside Surfaces and Solids (Types 18 and 19) If you model a Complex Shape with a Hole, make sure that the Hole element has the HOLE bit set. Otherwise, the envelope may not generate correctly. Complex Shapes (Type 14) inside Surfaces and Solids (Types 18 and 19) Surfaces (noncapped solid) (Type 18) Solids (capped solid) (Type 19) Cones & Cylinders (Type 23)
78
_ _______________
Cells with nested primitives using types 18, 19, and/or 23 Cells containing only Type 6 Shape elements modelled in such a way that the resulting graphic could otherwise be created as a projected solid. In such cases, the system uses the projected solid to create the envelope. One example would be a cell containing 6 shape elements comprising the faces of a cuboid.
PDS Clash Detection with Non-PDS Models
In this case, the envelope builder would create an envelope based on the projected cuboid solid that the cell resembled. Another example would be 2 hexagonal shapes connected by 6 rectangular shapes, so that the cell resembles a projected hexagon.
In this example, the envelope builder would create an envelope based on the projected hexagonal solid that the cell resembled. Cells containing only Type 6 Shapes, or Type 6 Shape and Type 14 Complex Shapes, forming non-projected solids, such as triangular or truncated pyramids. The system creates envelopes for these cells using a projected solid of minimum thickness (20 UORs) for each planar shape. Projected surfaces or solids Revolved surfaces or solids If you have elements other than these, they will not be used during PDS clash detection.
4. Envelopes
Limitations
For the PDS-supported model types, PDS has access to either database records or MicroStation user data. This allows PDS to track clashes for reporting purposes, associating names with the clashing elements in reports and plots, and for storing the clash approval status of elements (for example, if a clash is deemed acceptable by you). This type of information is not available for user-defined disciplines (exclusive of PLANTGEN). Therefore, the generic envelope builder uses a pseudo-occurrence number for the clashing item. This number is
79
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 made up of the byte and sector location of the MicroStation element. Also, no name label can be associated with the clashing item in clash reports and clash plots. As a result of using the byte and sector of the item, if the clashing item has its position moved in the MicroStation design file (the byte/sector number position, NOT the physical/geographical location in the model), PDS clash detection does not recognize the previously reported clashing item as the same item. It clears the old clash (since the item at the previous byte/sector position is no longer there or the same), and considers the clash a new one. This repositioning of the MicroStation elements (byte and sector number position) occurs when items are deleted, revised with certain commands, and when the model is compressed. This means that if you approved a clash involving an item in a non-PLANTGEN, user-defined discipline, and the byte/sector number for that item was changed, the clash will be reported again, as a new clash, and you will need to reapprove it.
80
_ _______________
4.3 Envelope Verification
Envelope Verification
This option activates the Envelope Verification form. It is used to verify the integrity of the envelope file and to determine if the creation dates of the envelope files are up to date with the system dates of the corresponding model files. A log file is created automatically if any errors are found in any of the interference envelopes and a Warning dialog box appears informing you of the existence of the file. The existence of this file usually indicates problems with the disciplines envelope builder. It is created in the directory and network address specified for Interference Management reports. It is named after the project or design area number with a option is displayed for immediate review of problems when they are found. As a means of isolating problems between the disciplines Envelope Builder and the Interference Checker, the Envelope Verification option verifies the following conditions, and records errors in the .err file: The range of a shape to be completely contained within the range of the applicable components interference envelope. The range of a components interference envelope to be contained within the range of the applicable model. Interference envelopes represented as a hole or void are to be either a cylinder, not including a cone, or a projected shape. Also, the following situations are included in the .err file: Components that contain two or more subcomponents that are not connected. This report entry includes the components primary description and the range of each subcomponent. The range is included since the subcomponents ranges must overlap to be connected. Components which have the same linkage within a model do not have unique identification. This situation is reported as an error and usually indicates that one of the following problems exists: The MicroStation Copy command was used to copy a component in the model. The disciplines model creation product has created a component which does not have a component identification that is unique within that model. The disciplines Envelope Builder has created a components interference envelope with an incorrect component identification such that it is not unique within that model. Use the Envelope Builder option to update the envelope files that are in the Need to be Updated category. The Envelope Builder updates only those envelope files which are out of date.
4. Envelopes
81
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 It is recommended that you verify that all envelope files are available prior to running the Interference Checker. If an envelope is unavailable for a clash session, and clashes involved with this envelope file have already been approved, these clashes will be reset to 1 - unapproved.
Commands
Project Checks all of the envelope files in a project. Piping Design Area Displays a list of piping design areas and allows you to select the design area to be verified. All of the envelope files within the specified piping design area are processed. Piping Design Area Predefined Volume Displays a list of piping design areas with predefined volumes and allows you to select the design area to be verified. All of the envelope files within the specified piping design area are processed. Design Area Displays a list of design areas and allows you to select the design area to be verified. All of the envelope files within the specified design area are processed. Design Area Predefined Volume Displays a list of design areas with predefined volumes and allows you to select the design area to be verified. All of the envelope files within the specified design area are processed. The system places each of the files for the selected option in one of the three status fields as displayed and described below:
82
_ _______________
Envelope Verification
Status Fields
Up to date The interference envelope is up-to-date with the model. The model number is displayed. Needs to be Updated The interference envelope is not up-to-date with the model and must be re-created. Either the model has been reviewed or revised since the interference envelopes were last generated or the interference envelopes do not exist. The model number, the date of the last model file modification, and the envelope file generation date are displayed. Error Mounting File System An error occurred while mounting the file system where the model resides. The model number is displayed. Does NOT Exist An interference envelope has never been created for the model.
4. Envelopes
Commands
Display Error Report This option displays the found during the Envelope Verification process.
83
_ _______________
84
_ _______________
4.4 Envelope Diagnostics
Envelope Diagnostics
This option creates and allows you to review MicroStation-type graphics from the interference envelopes for a selected model in a design file. This generated file has a .til extension. Any previously-created graphics are deleted automatically from the envelope diagnostics file before creating new envelope diagnostic graphics. Construction tolerance envelopes are not included in the graphics display.
About this command

The graphics created by the Envelope Diagnostics command for the interference envelopes match the colors of the interference markers defined in the interference marker file.
Error File (.evd)

Any discrepancies found during this verification process indicate problems in the applicable Envelope Builder and will be reported in a file in the c:\temp directory named after the model with a .evd file extension. This report also contains a list of any pipe-like components within a model. It will exclude any piping or instrument components on the basis of the Piping Construction Tolerance Exclusion Data Table, PDtable_233, of the Material Reference Database defined using the Reference Data Manager.
4. Envelopes
Also, as a means of isolating problems between the Envelope Builder and the Interference Checker, the Envelope Diagnostics option verifies the following conditions and records errors in the .evd file: The range of a shape, to be completely contained within the range of the applicable components interference envelope. The range of a components interference envelope, to be completely contained within the range of the applicable model. Envelope shapes representing holes or voids must be cylinders (right or skewed) or projected shapes. Holes or voids represented by cones are not permitted. The following situations are also included in the .evd file: Components that contain two or more subcomponents that are not geometrically connecteddo not have overlapping ranges. This report entry includes the components primary description and the range of each subcomponent. The range is included since the subcomponents ranges must overlap to be connected.
85
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Components which have the same linkage within a model do not have unique identification. This situation is reported as an error and usually indicates that one of the following problems exists: The MicroStation Copy command was used to copy a component in the model. The disciplines model creation product has created a component which does not have a component identification that is unique within that model. If this problem occurs, it should be reported to Intergraph immediately. The disciplines Envelope Builder has created a components interference envelope with an incorrect component identification such that it is not unique within that model. If this problem occurs, it should be reported to Intergraph immediately.
Commands
Create Diagnostic File Create a diagnostics file for the selected model. Create and Review Diagnostic File Create a diagnostics file and enter a graphics environment to review the file. Review Diagnostic File Review a previously created diagnostics file (displays only if a diagnostics file is available). Also, the envelope display includes model graphics from the reference file that is attached. Envelope display will not include construction tolerances.
86
_ _______________
If prompted to... Select Discipline Do this: Select the discipline for the envelope to be processed, and click Accept. Select the design area for the envelope to be processed, and click Accept. The system displays the available models for the selected discipline and design area. Select Design Area
Select Model
Select the model for the envelope file to be processed, and click Accept. The system displays the available models for the selected discipline and design area.
4. Envelopes
87
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Accept To Create Diagnostics File Select an option to either create or create and review the diagnostics file and click Accept. Never alter the model_name.dgn file.
88
_ _______________
5. Interference Checking
This section provides information on interference checking, including information on the Piping Clash Check Command from the Piping Design module in the following order: 5.1 5.2 Interference Checker See Interference Checker, page 90 for more information. Piping Clash Check Command See Piping Clash Check, page 108 for more information.
Interference Checking
5. Interferences
89
_ _______________
5.1
Interference Checker
This command activates the Interference Checker form. It checks for interference clashes within the specified project volume. You can process the entire active project, a design area, a single model, a pair of models, or a specified volume. The interference detection process and its results will vary depending on the settings defined on the Interference Checker Data form. These settings include: Dual or Single Design Area Ownership Exclusion of Interferences by Discipline Exclusion of Interferences by Model Status Insulation Inclusion or Exclusion for Equipment Envelopes Construction Tolerances for Equipment Envelopes See Interference Checker Data, page 41, for more information.
Exclusion Tables
The following tables are used during envelope generation to make intelligent envelopes. Interference detection then reports more precise clash information. See the Reference Data Manager Reference Guide for detailed information on each of the following tables. Component Insulation Exclusion Data (231) Flange Insulation Exclusion Data (232) Piping Construction Tolerance Exclusion Data (233) Commodity Name Table See the Creating Pipe-like Components for Interference Detection section for more information on how to use the Commodity Name Table in the Piping Job Specification Table Library. If you revise these tables after clashes have been reported or excluded, the system does the following: If selected components are added to a table, the Interference Checker eliminates those false clashes as if you had revised them by revising the piping model itself. If selected components are removed from the table, the Interference Checker reports those clashes as if they had never been excluded.
90
_ _______________
Changes to these tables are not reflected in the results of the Interference Checker until the interference envelopes have been re-created and interfence detection has been rerun.
Clash Category Considerations

The Interference Checker does not report hard vs. soft clashes of piping components when all of the following conditions are met: Both components are in a piping model by default and by assigned responsible discipline. Also, if both components are in piping models where the assigned responsible discipline is HVAC, the hard vs. soft clashes are not reported. Both piping components are in-line components, which are not pipe supports. The two components or a component and a pipe are connected by the same single piping component. The clash is not due to an interference envelope which represents a valve operator of one of the two piping components. The Interference Checker does not report hard vs. construction clashes between a piping support and a horizontal structural beam, in the same manner as for other piping, when the pipe support is flush with the horizontal beam.
False Clashes
The Interference Checker does not report false clashes in the following situations: A female-ended piping component is connected to a male-ended equipment nozzle. Piping is connected to a female-ended equipment nozzle which is insulated. You must re-create equipment interference envelopes so that the nozzle connect point locations are added before false clashes will be eliminated. Two equipment envelopes of the same type, as listed below, are clashing.
5. Interferences
access soft vs. access soft access hard vs. access hard maintenance soft vs. maintenance maintenance hard vs. maintenance operating soft vs. operating soft operating hard vs. operating hard safety soft vs. safety soft safety hard vs. safety hard
91
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 You must re-create equipment interference envelopes so that the envelope type is added to the definition of the equipment interference envelopes before false clashes will be eliminated.
Application Type
The Interference Checker considers the discipline of a model to be that which is defined in the Application Type field on the Create Model Data form in the Project Administrator. If the Application Type is not specified, the discipline in which the model was created is used for interference processing.
Mechanics
The type of option that you select for interference processing, such as the Project or Design Area, is recorded in the clash management data in the Project Control Database. If Access Control is enabled, the initials of the responsible user are written to this database (PDtable_131), enabling you to track who initiated the process. When the volume is predefined or when the volume filter toggle is used, the system records that volume. If the volume is not predefined, the system-calculated volume for the project or design area is recorded in the clash management data. Interference processing requires the following values for the standard note type 1208 in the projects Standard Note Library. o 1 unknown o 2 project mode o 3 design area mode o 4 predefined volume mode The Volume Filter toggle requires the following values for standard note type 1209 in the projects Standard Note Library. o 1 volume filter is inactive o 2 volume filter is active Interference processing requires that the Clash Job Data Table, PDtable_131, in the Project Control Database maintains this data in the following columns: o clash_check_option short o volume_filter_option short o volume_low_x integer o volume_low_y integer o volume_low_z integer o volume_high_x integer o volume_high_y integer o volume_high_z integer
92
_ _______________
Processing Time
Running the Interference Checker for an entire project takes considerably longer than running it for a design area. If the project workload is being shared, one of the design area options would be the most efficient. The design area options are less time consuming and create individual sets of reports rather than one set of reports for the entire project. Adhere to using either the Project option or one of the Design Area options for the life of the project for the most consistent results. When you initiate a batch process using the Interference Checker, the integrity of the marker model is verified. If the marker model is not valid (for instance, if it is copied from the projects seed model using File > Copy), a dialog box appears indicating that the marker file should be re-created. (See Interference Management Data, page 180, for more information.) This must be done in order to continue. No Interference Management data is lost as a result of updating the marker model. Also, if the marker file is already in use, the system displays a lock status message.
Commands
Project Performs clash checking for all of the envelope files defined for the project and creates interference, difference, and batch queue error reports. Piping Design Area Activates a list of piping design areas available for clash checking. After a piping design area has been selected, the system defines a volume that encompasses all models within the selected piping design area. It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the defined volume. To specify a larger or smaller volume for a
5. Interferences
93
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 single interference check, set the Volume Filter toggle to On after selecting a piping design area. Piping Design Area Predefined Volume Activates a list of piping design areas with predefined volumes available for clash checking. After a piping design area has been selected, the system uses the predefined volume that has been specified by using the Project Environment Manager. This volume is displayed on the form. The system then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the predefined volume. The Interference Checker does not include models that are in the selected piping design area that do not fall within the predefined volume. Design Area Activates a list of design areas available for clash checking. After a design area has been selected, the system defines a volume that encompasses all models within the selected design area. It then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the defined volume. To specify a larger or smaller volume for a single interference check, set the Volume Filter toggle to On after selecting a design area. Design Area Predefined Volume Activates a list of design areas with predefined volumes available for clash checking. After a design area has been selected, the system uses the predefined volume that has been specified by using the Project Environment Manager. This volume is displayed on the form. The system then performs an interference check on all models and parts of models, including models from all other disciplines, that are in the predefined volume. The Interference Checker does not include models that are in the selected design area that do not fall within the predefined volume. This command can be used in conjunction with the Clash discipline to check areas using the Design Volume Coordinate System. See Design Area Predefined Volume, page 74 and the Project Administrator (PD_Project) Reference Guide for more information. Single/Pair Model Check Activates a form which allows you to select a single model or a pair of models to be re-checked. It also allows you to define the discipline and design area ownership for each run of this option. This option can only be used if interference checking has already been run on the design area you will select for ownership of clashes. It is used to recheck items that have been revised to avoid rerunning an entire area. You can specify multiple pairs or single models to be checked. An individual report and accompanying clash plots, if applicable, are created for each pair or single run specified. The report and clash plot are uniquely named on the basis of the model index number for the applicable models. The Interference Approval Manager displays the results of the clashes found according to the design area ownership specified for each single or pair. The results are appended to previous interference detection for the design area.
94
_ _______________
Use the Select Design Area Ownership for Clashes command to define ownership for a clash if the models are in more than one design area. Use the Select Models for Clashes command to select the model or models to be included in the interference checking process. You can select one or two models to be included. The pair option only reports interferences that exist between an item in model A and an item in model B. It does not check for interferences that are internal to model A or internal to model B. Plot Clashes Plots interference clashes based upon search criteria using Interference Management data. The clashes are plotted as they are found during the Interference Checking process and are given a unique clash ID and plot number within the group of interference clashes being plotted. See Plot Clashes, page 98, for more information. Submit Immediately/Delayed Submit Submits or delays submission of the job. When the toggle is set to Delayed Submit, the system displays the following fields and allow you to delay submission until a more convenient time.
5. Interferences
Volume Filter Creates a Volume Filter for one run of the Interference Checker. When set to Volume Filter Off the system will use the default or predefined volume. When set to Volume Filter On, you can define the low and high Easting, Northing, and Elevation for one run of the Interference Checker. Only the clashes found within the range of the Volume Filter are available for review after an interference detection run using this option. All clashes are again available for review when interference detection is run for a design area or for the project.
95
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Default Report Active / User Defined Interference Report Defines that either the default report or a user-generated report is created during interference checking. The default report is the Interference Report which has a .int file extension. When the toggle is set to User Defined Interference Report and you place a data point in the provided field, the system displays a list of all of the reports you have created through the Interference Report Manager. The report you select is generated during the interference detection process. If you have not defined a report record consisting of an existing format file and an existing discrimination data file, no reports will be displayed for you to select. You must define the reports first. If you select a user-defined report and Access Control is enabled, the initials for the responsible user are written to the Clash Review History data table, PDtable_135. If a user-defined report accesses a format file containing the DZ10 index, plots are generated automatically during report creation. Clashes are plotted in the order in which they are reported. The Plot Clashes command should not be used in this situation. Generate And Verify Envelopes / Do No Generate And Verify Envelopes Specifies whether to perform envelope creation and verification as a batch job prior to clash detection. Errors found during verification stop the batch job, and must be corrected before clash detection can be run. Refer to Appendix A for a list of Envelope Verification Errors. Print / Delete Submits the generated report output file to the specified print queue and deletes the output file. Print / Save Submits the generated report output file to the specified print queue and saves the output file. Save Saves the output file without printing.
96
_ _______________
Use the Verify Data Integrity of Model diagnostic command to check all piping models. Overlapping pipelines are reported by this check, not by the Interference Checker.
Additionally, you should run the Verify Data Integrity of Model command in FrameWorks Plus to detect overlapping structural members before you create envelope files for structural models. Use the Interference Checker Data command to define the mechanics of the interference checking process. Use the Envelope Verification command to make sure that the envelope files are up to date. Equipment must contain at least one datum point for a clash with the equipment envelope to be reported.
5. Interferences
97
_ _______________
5.1.1
Plot Clashes
This command is used to plot interference clashes based upon search criteria using Interference Management data. The Interference Checker must be run at some point before using this option. If a user-defined report accesses a format file containing the DZ10 index, plots are generated automatically during report creation. Clashes are plotted in the order in which they are reported. The Plot Clashes command should not be used in this situation during the interference-detection process.
Default Plot
Each plot contains the following information: A unique plot number for easy identification within the group of interference clashes being plotted. The model numbers of the components involved in the clash. The clash types of the model. The short version of the clash type is used if it exists in the Standard Note Library, otherwise the long version is used. The models categorized as Model A and Model B. Clashing components are categorized as Model A and Model B in the order of their clash precedence, which is hard, soft, and construction, respectively. When a clash is found between components which both contain insulation where each component could be clashing with the other components insulation, the system randomly defines one component as Model A, hard, and the other as Model B, soft. The design area number corresponding to the model number for each component involved in the clash. The previous item requires a change to the format of the clash plot border for the 5.0 release. You must copy the clash plot border, borderifc.dgn, from the \pd_clash\border product directory into your project directory. This copy is not part of the Automated Upgrade Process because you may not wish to override your existing border file. You must also copy the ifc.i file into your project directory for plotting purposes. It is delivered but the copy is not part of the Automated Upgrade Process. The Review Action from the Clash Review History Data Table (PDtable_135), including the information that the clash has been approved as a real or false clash.
98
_ _______________
The Review Date from the Clash Review History Data Table (PDtable_135). The Review Comments from the Clash Review History Data Table (PDtable_135), as many as 100 characters to the pertinent construction tolerance value, if applicable.
Plot Clashes
5. Interferences
99
_ _______________
100
_ _______________
Detailed Plots
Detailed clash plots include the model representation in addition to the interference envelopes for components other than the two components involved in the clash. All components falling within the clash plots volume and existing in the two applicable models is displayed with the two clashing components and the corresponding interference envelopes. The envelope graphics of the two clashing components are plotted with weight of 4 and a style of dashed. The model graphics of the two clashing components are plotted a weight of 2 and a style of solid. The model graphics of the other components are plotted with a weight of 0 and a style of solid.
Plot Clashes
5. Interferences
101
_ _______________
102
_ _______________
When a plot queue is selected, it is used for all graphic interference clash reports that are being plotted in one batch process.
Plot Clashes
There is a primary discipline called the Action Discipline for every model combination. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take "action" to resolve the clash. The Action Discipline is at the top of each clash so that clashes may be easily sorted and routed to the person responsible for the clashes in that discipline.
Commands
Unplotted Clashes Specifies that only unplotted clashes of the specified types be plotted. Unapproved Clashes Specifies that only unapproved clashes of the specified types be plotted. Unreviewed Clashes Specifies that only unreviewed clashes of the specified types be plotted. Select Markers From List Displays a list of markers for the clash types selected so that you can specify which clashes are plotted.
5. Interferences
103
_ _______________
Select Single Marker / Range of Markers Allows you to select a single marker or a range of markers. Default Clash Plots / Detailed Clash Plots Submits either default or detailed clash plots. See the examples of each in the following sections. Submit Immediately/Delayed Submit Submits or delays submission of the job. When the toggle is set to Delayed Submit, the system displays the following fields for you to specify the submission time.
104
_ _______________
5.1.2 Interference Checker Output
For a detailed description of each type report and record created by the Interference Checker, see the Interference Checker Output section in Chapter 2. The following is an example of the PDS interference clash and sections from its associated reports.
Interference Report
This report contains all unapproved clashes, sorted first by model combinations then by the type of clash. For instance, all clashes detected between model A and model B would be grouped together. A synopsis of the clashes is included at the beginning of the report; it indicates the number of clashes found with each pair checked. This report also includes the model status of any components involved in a clash for the Piping, Structural, HVAC, Equipment, Architecture, or PLANTGEN disciplines. This status is that of the model and not of the clash.
5. Interferences
These reports are named after the project or design area with a .int file extension and are created each time the checker is run. The interference report is created on the workstation or server in the directory from which the Interference Checker was submitted unless otherwise specified using the Interference Report Management Data option.
bccopy
105
_ _______________
Entire Design Volume Included In Report PDS Interference Clashes Hard/Soft Clashes No __ 82 Item Name _________ GAT W38bc0311-4IN-2C0032-HF-2 " Not approved 82 GAT W38bc0311-4IN-2C0032-HF-2 " Not approved 83 FWN W38bc0311-4IN-2C0032-HF-2 " Not approved 83 GAT W38bc0311-4IN-2C0032-HF-2 " Not approved 84 PIPE W38bc0311-4IN-2C0032-HF-2 " Not approved 84 FWN W38bc0311-3IN-2C0032-HF-2 " Not approved 85 GAT **W38bc0311-4IN-2C0032-HF-2 " Not approved 85 GAT **W38bc0311-4IN-2C0032-HF-2 " Not approved 86 FWN **W38bc0311-4IN-2C0032-HF-2 " Not approved 86 GAT **W38bc0311-4IN-2C0032-HF-2 " Not approved 87 PIPE **W38bc0311-4IN-2C0032-HF-2 " Not approved 87 FWN **W38bc0311-3IN-2C0032-HF-2 " Not approved 88 GAT **W38bc0311-4IN-2C0032-HF-2 " Not approved 88 GAT **W38bc0311-4IN-2C0032-HF-2 " 3 6816298 E 1386 9 11/16" PlaN 386 3 5/8" Plant El 12 6" Plant 3 6816291 E 1387 11 5/16" PlaN 386 3 5/8" Plant El 15 6" Plant 3 6816091 E 1310 8 3/4" PlantN 441 3 5/8" Plant El 17 0" Plant 5 6815847 E 1311 2 5/16" PlanN 441 3 5/8" Plant El 18 8 1/4" Plant 3 6816062 E 1306 9 11/16" PlaN 426 3 5/8" Plant El 12 6" Plant 3 6816057 E 1307 11 5/16" PlaN 426 3 5/8" Plant El 14 10 3/16" Plan 3 6816062 E 1306 9 11/16" PlaN 426 3 5/8" Plant El 12 6" Plant 3 6816055 E 1307 11 5/16" PlaN 426 3 5/8" Plant El 15 6" Plant 3 6815855 E 1310 8 3/4" PlantN 401 3 5/8" Plant El 17 0" Plant 5 6815768 E 1311 2 5/16" PlanN 401 3 5/8" Plant El 18 8 1/4" Plant 3 6815826 E 1306 9 11/16" PlaN 386 3 5/8" Plant El 12 6" Plant 3 6815821 E 1307 11 5/16" PlaN 386 3 5/8" Plant El 14 10 3/16" Plan 3 6815826 E 1306 9 11/16" PlaN 386 3 5/8" Plant El 12 6" Plant Table _____ 3 Row ___ 6815819 X Coord _______ Y Coord _______ Z Coord _______ E 1307 11 5/16" PlaN 386 3 5/8" Plant El 15 6" Plant
106
_ _______________
Not approved 89 FWN **W38bc0311-4IN-2C0032-HF-2 " Not approved 89 GAT **W38bc0311-4IN-2C0032-HF-2 " Not approved 3 6816298 E 1386 9 11/16" PlaN 386 3 5/8" Plant El 12 6" Plant 3 6816293
E 1387 11 5/16" PlaN 386 3 5/8" Plant El 14 10 3/16" Plan
5. Interferences
107
_ _______________
5.2
Piping Clash Check

This command is part of the Piping Design module but has been included here to provide a more complete scope of PDS interference information. This command enables you to check a piping line for interferences immediately after completing the line. It automatically creates interference envelopes in the workstations memory for any piping in the active model defined by the selected pipeline. It checks any attached reference models for which interference envelope files have been created previously. It also reports any reference models for which interference envelopes have not been created previously. The results of this interactive clash checking is not maintained as a part of the Interference Management data. However, you can use the Piping Clash Review option to review the clashes detected by this command. This command does not affect the interference envelopes created by the Interference Managers Envelope Builder. If prompted to... Identify Pipeline Do this: Snap to a segment or locate a component to identify the pipeline to be processed. Click Accept to process the identified pipeline or click Cancel to reject the pipeline. The system creates interference envelopes for the selected pipeline and checks the volume defined by the pipeline for possible clashes. When finished the system displays the number of clashes detected.
Accept to Check Pipeline
Identify Pipeline or Select Review Option Identify another pipeline as outlined above. OR
108
_ _______________
Select the Piping Clash Review option to review the detected clashes. Select Review Option Select one of the options to review the clash.
Piping Clash Check
Commands
Select View Select this option and identify the screen view to display the active clash. Restore View Select this option to restore the active view(s) to the initial viewing parameters for the clash being checked. Previous/Next Marker Number Select either of these options to review the next/previous marker. The system updates the window coordinates about the clash in the selected view.
5. Interferences
109
_ _______________
110
_ _______________
6. Interference Managing
This section provides information on interference managing, including information on the Piping Designer interference reviewing function, in the following order: Interference Approval Manager See Interference Approval Manager, page 112 for more information. Interference Management Data See Interference Management Data, page 180 for more information. Piping Clash Review (in the PD_Design Module) See Piping Clash Review (in the PD_Design Module), page 181 for more information.
Interference Managing
6. Approval
111
_ _______________
6.1
Interference Approval Manager

This option activates the Interference Approval Manager form. It is used to review all the interferences in a project or area and revise the approval status of any of the interference markers, plot clashes, and create unapproved clash reports.
About this command

When you activate the Interference Approval Manager and select an option, the applicable marker file is verified. If the marker file is not valid (for instance, if it is copied from the projects seed file using File Manager), a dialog box appears indicating that the file should be re-created. This must be done in order to continue. See Interference Management Data, page 180, for more information. No Interference Management data is lost as a result of updating the marker file. Also, if the marker file is already in use, the system displays a lock status message.
Commands
Project Reviews and revises interferences for the active project. Piping Design Area Reviews and revises interferences for a selected piping design area. Design Area Reviews and revises interferences for a selected design area.
112
_ _______________
Interference Approval Manager
You must have run the Interference Checker for the volume to be reviewed or revised.
6. Approval
113
_ _______________
6.2
Approval Manager Commands

These commands allow you to review and approve clashes, review clash history, create reports and review checker reference data. Before running a clash report, and once a clash is approved, you need to completely exit PDS (out of PD_Shell), reenter PD_Clash, then run the report.
Commands
Approve Edits and reviews existing clashes, manipulates views, and approves changes to existing clashes. For more information, see Approve, page 115. Approve From List Approves existing clashes. See Approve From List, page 119. Checker Run Dates Displays the exact date and time that the IFC Checker was run. See Checker Run Dates, page 121. Review Clash History Displays all available information about the clashes. See Review Clash History, page 122. Create Unapproved Clash Report Creates a report containing all clashes found and is sorted by model combination. For more information, see Create Unapproved Clash Report, page 124. Checker Reference Data Reviews Checker Reference Data defined by the Project Data Manager module of Project Administrator including a review of the action and responsible disciplines. This information is for review only. Measure Distance Measures the distance between any two components. Mass Clash Approve Reviews and approves multiple clashes associated with a clash item. For more information, see Mass Clash Approval, page 130.
114
_ _______________
6.2.1 Approve
This command activates the Interference Approval Manager form. It is used to edit and review existing clashes, manipulate views, and approve changes to existing clashes.
Approve
6. Approval
The Action Discipline toggle is only displayed when clashing models are not from the same discipline.
Field Descriptions
Project Name Displays the name of the active project. Design Area Displays the name of the active design area. Date Displays the date the checker was run. The information in this field is set with the Checker Run Dates option. For more information, see Checker Run Dates, page 121. Responsible User: Displays the code number of the responsible user. This field is filled in if access control is set on the project and will be the userid that was keyed in to access the project through access control. Once the clash is approved, the users initials are written to the Clash Review History data table, PDtable_135. Clash Type Describes the current type of clash. This field is the one above the Review Unapproved/Approved Clash toggle. Marker Number Displays the number of the current clash. Select a marker number with the left and right arrows, select the field and key in a marker number, or select the Keyin Marker Number option and key in a marker number. Model and Area Name Displays the names of the models and corresponding design areas that have components involved in a clash.
115
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Item Displays descriptions of the clashing components in the Item fields which are located below the Model fields. The system accesses the user-defined labels in the Label Description Library to create: the primary description, which is displayed on the top line with a limit of 20 characters; and the secondary description, which is displayed on the bottom line and has a limit of 40 characters. These descriptions are defined with the Clash Management Labels option on the Create Label Data form in the Reference Data Manager. Comments: Displays existing comments about the active clash. Select the field, and key in any necessary additional information.
Commands
Review Unapproved Clash Reviews unapproved clashes. Approve Clashes By Item Approves items by clash type. The system displays the Approve by Item A or Approve by Item B toggle and a display list of possible clash types.
Clash Status Approves or unapproves the current clash. Depending on the status of the displayed clash, the Unapprove Clash, Approve Real Clash or the Approve False Clash option will be highlighted. For more information, see Approve From List, page 119. Unapprove Clash changes the status of a clash from approved to unapproved. Approve Real Clash approves the clash as a real clash in the Project Control Database. Approve False Clash approves the clash as a false clash in the Project Control Database. Action Discipline: Displays the Action Discipline for every model combination unless both models are from the same discipline. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take action to resolve the clash. This toggle only appears if there are two different disciplines involved in a clash. Select View Zooms in and updates selected views. Select the option and then select the views that you want to update. Plot Active Clash Plots the clash in the active view immediately, placing the temporary plot files in the c:\temp directory. It either plots default or detailed clashes depending on the way the toggle has been defined using the Project Data Manager
116
_ _______________
module of Project Administrator. You can review this setting using the Checker Reference Data command. The system displays the Plotter Queue list, showing the available plotters. Select a plotter from the list and click Accept to plot the clash.
Approve
6. Approval
Envelope Diagnostics Creates MicroStation-type graphics from the interference envelopes for a selected model in a design file. For more information see the Envelope Diagnostics, page 118. Enter Dynamics Rotates clashes orthogonally or in 3D about a particular view. See the Enter Dynamics section for more information. Restore View Restores the active window. Select the option, and the system automatically updates the active window. Highlight Clash Highlights the active clash in every view. Select the option, and the system automatically highlights the active clash in grey. Keyin Marker Number Defines the marker number of an existing clash. Select the option, and key in a marker number in the Marker Number field. Without Reference Models/With Reference Models Defines that the clash display be with or without reference models. Without Reference Models is the default and shows the clashing elements only. With Reference Models displays the reference files (for example the structural model file and the raceway model file) and highlights the clashing members. If prompted to... Select Clash Type Do this: Set the toggle to the appropriate setting and select the clash types to be approved. Use one of the options described above to edit or examine the existing clashes.
Select Review Option
117
_ _______________
6.2.1.1
Select View
This option activates the Select View form. It is used to zoom in on selected views. The views are updated as they are selected for review. The system can zoom in on the complete interference clash or to the intersection of the interference clash. The system only displays boxes for views that are currently active.
6.2.1.2
This option displays the envelope graphics for immediate review only. However, if there are no <model_no.env> files, the system displays an error message.
6.2.1.3
Enter Dynamics
This option displays the active clash in dynamics. This enables you to rotate clashes orthogonally or in 3D about a particular point. As you place data points in the active view, the clashing objects rotate. Each new data point is used to control the rotational axis and the direction that the clashing objects rotate about the axis. You can see this more clearly with the reference models attached.
118
_ _______________
6.2.2 Approve From List
This option activates the Approve From List form. It is used to approve existing clashes according to clash type. Refer to the Clash Categories article in the Introduction for more information on the types of clashes. When the markers are displayed, they are sorted in order of the clash type and then by the unique clash ID.
Approve From List
6. Approval
Select or Accept for all Types or Exit Select the option to indicate the type of clashes to be approved, and select Accept to accept the clashes. The Clash Marker form displays.
119
_ _______________
Commands
Select Single Marker / Range of Markers Allows you to select a single marker or a range of markers. Select Clash Marker or Exit Select the clash markers to be approved. For the Select Range of Markers option, select the first and last clash marker in the range of makers to be approved.
120
_ _______________
6.2.3 Checker Run Dates
This option activates the Checker Run Dates form. It is used to display the exact date and time that the clashes were detected.
Checker Run Dates
6. Approval
This command only shows the unapproved/approved clashes for the most recent clash detection run. It will show a complete history of the dates for interference checker runs on the area chosen.
121
_ _______________
6.2.4
Review Clash History

This option activates the Review Clash History form. It is used to display all available information about the clashes.
Commands
Marker Number Lists the marker numbers of the clashes. Review User ID Lists the identification number of the user that is assigned through the control shell. Responsible User ID Lists the identification number of the user that is responsible for a particular clash. If prompted to... Select Attribute Do this: Select the attribute that you want to review. The following list describes the attributes of the Review Clash History form.
Select Operating
Select the mathematical operator that meets your requirements. Key in a numerical value to serve as an argument. A typical keyin of responsible_user_no <= 16 displays all clashes with a Responsible User Number of less than or equal to 16.
Specify Attribute Value
122
_ _______________
Accept or Select AND/OR Operating Select Accept to accept and review the clash history. Use the arrow buttons to page through the identified clash data. The system displays the description of previous review runs of any of the existing clashes that meet the argument.
Review Clash History
6. Approval
123
_ _______________
6.2.5
Create Unapproved Clash Report

This option automatically creates an unapproved clash report. This is the same type of report that is created by the Interference Checker, but will include any newly created clashes. The report is named after the project or design area with a .mgr file extension. The interference report is created on the workstation or server in the directory from which the Interference Checker was submitted unless the Interference Report Management Data option was used to define another network address and pathname.
Commands
Print / Delete Submits the generated report output file to the specified print queue and deletes the output file. Print / Save Submits the generated report output file to the specified print queue and saves the output file. Save Saves the output file without printing.
Unapproved Clash Report Example

PDS Interference Report Date/Time: Wed Jul 20 08:59:16 1997 Report on Unapproved Clashes for area: doc Total Number of Unapproved Markers: Marker# 82 Model bccopy bccopy Description GAT GAT 5401 Clash Type Hard versus Soft
124
_ _______________
83 bccopy bccopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy testcopy rlh1 vcpipe1 GAT FWN GAT GAT GAT FWN GAT PIPE FWN PIPE FWN PIPE PIPE GAT PIPE FWN PIPE FWN GAT PIPE FWN PIPE FWN PIPE GAT PIPE FWN PIPE FWN PIPE PIPE GAT PIPE FWN PIPE FWN GAT PIPE E90LR E90LR Hard versus Soft 272 Hard versus Soft 279 Hard versus Soft
Create Unapproved Clash Report
6. Approval
280
Soft versus Soft
281
Soft versus Soft
282
Soft versus Soft
283
Soft versus Soft
284
Soft versus Soft
285
Soft versus Soft
286
Soft versus Soft
287
Soft versus Soft
288
Soft versus Soft
289
Soft versus Soft
290
Soft versus Soft
291
Soft versus Soft
292
Soft versus Soft
293
Soft versus Soft
294
Soft versus Soft
295
Soft versus Soft
389
Hard versus Hard
125
_ _______________
390 rlh1 vcpipe1 rlh1 vcpipe1 rlh1 vcpipe1 rlh1 vcpipe1 rlh1 vcpipe1 rlh1 vcpipe1 rlh1 vcpipe1 E90LR PIPE E45TLR E45TLR E90LR E90LR T T E90LR E90LR FWN FWN E90LR E90LR Hard versus Hard 391 Hard versus Hard 392 Hard versus Hard
393
Hard versus Hard
394
Hard versus Hard
395
Hard versus Hard
396
Hard versus Hard
126
_ _______________
6.2.6 Checker Reference Data
Reviews Checker Reference Data defined by the Project Data Manager module of Project Administrator which is used to specify emulation data for use in analyzing interference envelopes. This information is for review only. During interference detection, the system uses a set of cylinders to emulate the volume of a model graphic. These settings determine the number and size of the cylinders to be used.
Checker Reference Data
6. Approval
Commands
Construction Tolerances Enabled/Disabled Disabled on this form. The setting displayed is the setting that has been set by the Project Data Manager. By default, construction tolerances are disabled for an existing interference marker model. Review Action Discipline Displays the primary discipline called the Action Discipline for every model combination. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take action to resolve the clash. The Action Discipline is at the top of each clash so that clashes may be easily sorted and routed to the person responsible for the clashes in that discipline.
127
_ _______________
Clash Plot Graphics Disabled on this form. The setting displayed is the setting that has been set by the Project Data Manager. It is set to Default to plot the default clash plot graphics or to Detail to specify that the Interference Checker plot more detailed clash plot graphics.
Field Descriptions
Torus Displays the number of cylinders (per 90 degrees) to be used in representing a torus (elbow). Truncated Cone Displays the cylinder length to be used in representing a cone (reducer or valve body). Semi-ellipsoid Displays the cylinder length to be used in representing a semiellipsoid (cap or head). Length and distance entries are in working units (MU:SU:PU format). For these fields the smaller the value the greater the precision and the slower the processing time for interference detection. Slicing Tolerance Displays the thickness of the slice that the software uses to subdivide the shapes in a model to do the internal computations. This should not be confused with Construction Tolerances (sometimes referred to as construction clearances), which are used to maintain distances between items in the model. Because the Slicing Tolerance is related to the size of model items, use caution if you edit this value to a larger number as some small items may be missed.
Interference Marker Symbology Displays the levels, weights and colors defined for the marker. These fields are used to set the design file level for unapproved and approved interference clash markers.
128
_ _______________
Intersection Threshold Defines the amount of overlap allowed before the intersection of two components is considered a clash. Valid Intersection Threshold values are within the range of 20 to 1000 Units of Resolution (UORs). The default value is 20 UORs.
Checker Reference Data
6. Approval
129
_ _______________
6.2.7
Mass Clash Approval

This option activates the Mass Approval Manager form. It is used to approve multiple clashes associated with the same item.
Operating Sequence
1. Select the Mass Clash Approve button. The Interference Mass Approval Manager form displays.
2.
Select or Accept for all Types or Exit Select the types of clashes to review and click Accept. The form displays the clash items sorted by number of clashes.
130
_ _______________
Mass Clash Approval
6. Approval
This list only shows clash items with more than one clash of the selected type. For example, a piece of equipment with two Hard versus Hard clashes and one Hard versus Soft clash would display all three clashes in a listing of All Clash Types, both Hard versus Hard clashes in a listing of Hard versus Hard clashes, and no clashes in a listing of Hard versus Soft clashes. 3. Select Markers for Approval Select the marker to approve. The form displays the individual markers associated with the selected clash item.
131
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 4. Select Markers for Approval Select the clashes to approve. 5. Select the Approve False Clash button or the Approve Real Clash button, depending on the nature of the clashes. Click Accept to approve the selected clashes. The system marks the selected clashes as approved and updates the list of unapproved clashes.
6.
132
_ _______________
6.3 View Commands
These commands provide view manipulations. All of these commands result in modifying what is seen in selected views. These commands only manipulate the view of the model but do not manipulate the actual model.
View Commands
6. Approval
Options
Viewing Modifies the view to define what is seen in it. View More Modifies the view to define what is seen. Viewing Direction Modifies the viewing direction. View Depth Modifies the view depth. Open/Close Allows a view to be opened or closed. The items in the sub-menu are view numbers. The views that are darkened are open. Bottom-to-Top Makes the bottom view fully visible, even if the view is fully obscured before this item is chosen. Cascade Stacks views in numerical order with the lowest numbered view entirely visible and the title bar of each remaining view visible.
133
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Tile Tiles open graphics views. Swap Swaps the screen image between two logical screens. When Swap is chosen, the physical screens are updated with the contents of the previously hidden logical screen. This item is dimmed if your system is configured with dual monitors or if it does not support two virtual screens. Although the Swap command is not dimmed when using a NT workstation, it does not apply. Update Updates a view, all of the views, the right or left view, or the grid displayed on a view. Previous Modifies the screen image to display the previous view. Next Modifies the screen image to display the next view. Copy Copies the content of one view into another specified view. Camera Turns on the camera and defines the camera position and target.
On turns the camera on. Off turns the camera off. Set Up turns on and sets up the camera. Move Camera moves the camera (like focusing the camera at an object and moving around to obtain different views of it). Move Target moves the target (like standing in one position and pointing the camera at different objects). Lens opens the Camera Lens setting box, which is used to set the angles and focal lengths of view camera lenses. Changes take effect only if applied with the Apply button.
134
_ _______________
Render Converts and displays views in one of the following ways: wiremesh, hidden line, filled hidden line, constant, smooth, phong, phong stereo, or phong antialias. Also, FlyThrough activates the FlyThrough Producer setting box, which is used to create simple animations, called sequences, for visualizing 3D models.
View Commands
6. Approval
Levels Defines which levels are displayed in a view. Changes take effect only if applied with the Apply button.
All PDS level control is manipulated using Category Control. Intergraph does not recommend using native Microstation level controls (i.e. on/off, color, line type, etc.) in conjunction with any PDS application.
135
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Rotation Opens the change view rotation box, which is used to control view rotation. Changes take effect only if applied with the Apply button.
136
_ _______________
6.3.1 View Commands
These commands are the basic view modification commands.
View Commands
6. Approval
Commands
Move and Center View Repositions graphics within the same view. Window Volume Defines a window display volume using precision inputs. Window Center Defines a new center point for a window view. Window Area Defines a window viewing area by two data points. Window Origin Defines a window view by the window origin. Refresh Views Refreshes the specified views. Viewing Options Sets the screen display and view control options. Zoom In Changes the magnification to focus on a smaller display area. Zoom Out Changes the magnification to focus on a larger display area. Fit Displays all elements in a selected view. View Equipment Modifies a screen view allowing only the elements making up an equipment item to be displayed.
137
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Window to Named Item Defines a window viewing area about a specified named item.
138
_ _______________
6.3.1.1 Move and Center View
The Move Window and Center command allows you to define a new window center by moving a specified direction and distance from the current window center. You can define any distance and direction, inside or outside the viewing volume.
Move and Center View
6. Approval
Commands
Move to (absolute move) These options define the absolute coordinate for the point in the direction to be defined. Select the direction and type the absolute coordinate or snap to an element to retrieve its corresponding coordinate. Move (delta move) These options define the change in the selected coordinate for the point in the direction to be entered. Select only one of the directions. Construct Point Constructs a new active point using multiple inputs. You can move the point along absolute or delta coordinates. Each input moves the coordinate indicator until you select Accept. Distance and Direction Specifies the exact distance the point will be moved and in what general direction. This option can be used in conjunction with the Construct Point command.
139
_ _______________
Operating Sequence
1. Select View by selecting one of the screen views from the indicators at the top of the form. Specify Window Center by specifying the new window center in the selected screen view. The system updates the selected view with the new window center. OR Select either the Construct Point or the Distance and Direction option.
2.
140
_ _______________
6.3.1.2 Construct Point
This command constructs a new active place point using multiple inputs. It allows you to compute an offset distance or define absolute or delta coordinate values. Each input moves the coordinate indicator until you select Accept to accept the displayed location and send the coordinate location to the active independent command.
Construct Point
6. Approval
Commands
Move to (absolute move) These options define the absolute coordinate for the point in the direction to be defined. Select the direction and type the absolute coordinate or snap to an element to retrieve its corresponding coordinate. Move (delta move) These options define the change in the selected coordinate for the point in the direction to be entered. Select only one of the directions. Distance and Direction Specifies the exact distance the point will be moved and in what general direction. This option can be used in conjunction with the Construct Point command. Compute Offset Allows you to compute an offset.

Select a command which allows the active place point to be moved.
141
_ _______________
Operating Sequence
1. 2. Identify Next Vertex by using the available options to construct a point. Select Accept when the coordinates are correct.
142
_ _______________
6.3.1.3 Distance and Direction
This command moves the active place point a specified or calculated distance in a specified direction or along a defined angle.
Distance and Direction
6. Approval
Settings in the models type 63 data determine the form display for horizontal and vertical angles. For the horizontal angle, the system will display either CCW from East or CW from North. For the vertical angle, the system will display either CCW from Plan or CW from Plan. You can use the Project Data Manager to define the horizontal angle in one of two ways: The angle can be measured as a clockwise offset (looking at a plan view) from North (North=0). (This is the default setting in the delivered seed data.) The angle can be measured as a counterclockwise offset (looking at a plan view) from East (East=0).
Commands
Move to (absolute move) These options define the absolute coordinate for the point in the direction to be defined. Select the direction and type the absolute coordinate or snap to an element to retrieve its corresponding coordinate. Move (delta move) These options define the change in the selected coordinate for the point in the direction to be entered. Select only one of the directions. Horizontal Angle Vertical Angle Type the angles in decimal degrees or select one of the standard angles from the bottom of the form. Negative values are acceptable for both options. The vertical angle is positive for a point above the active point and negative for a point below the active point.
143
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Active Direction The direction is defined by the segment pipe run at the active segment point. Up from Slope The active direction is defined as perpendicular to the sloped direction and in a generally upward direction. In other words, the vertical angle is increased by 90 degrees. Down from Slope The active direction is defined as perpendicular to the sloped direction and in a generally downward direction. In other words, the vertical angle is decreased by 90 degrees. Invert The direction is defined by rotating the horizontal and/or vertical angles about the active flow centerline. The Up from Slope and Down from Slope options specify a point that represents the end of a pipe run normal to a sloped pipe run. These options are intended for use when the previous point is a branch point on a sloped pipe run.
144
_ _______________
6.3.2 Window Volume
The Window Volume command allows you to define a new window volume by moving a specified direction and distance from the current window volume.
Window Volume
6. Approval
Commands
Move to (absolute move) These options define the absolute coordinate for the point in the direction to be defined. Select the direction and type the absolute coordinate or snap to an element to retrieve its corresponding coordinate. Move (delta move) These options define the change in the selected coordinate for the point in the direction to be entered. Select only one of the directions. Construct Point Constructs a new active point using multiple inputs. You can move the point along absolute or delta coordinates. Each input moves the coordinate indicator until you select Accept. Distance and Direction Specifies the exact distance the point will be moved and in what general direction. This option can be used in conjunction with the Construct Point command.
Operating Sequence
1. Select View by selecting one of the screen views from the indicators at the top of the form. Specify Window Volume by specifying the new window view in the selected screen view. The system updates the selected view with the new window volume. OR Select either the Construct Point or the Distance and Direction option.
2.
Viewing Options
This command provides access to a set of options that allow you to manipulate the model views for each screen or window.
145
_ _______________
P&ID Drawing View

The following view commands perform special processing when you select the active P&ID drawing view or PD_Design view. Fit View automatically sets the window area to the extent of the P&ID drawing border. Copy View disables copying the active P&ID drawing view to another model view. However, you can copy another model view to the active P&ID drawing view. This causes the P&ID drawing view to be saved as a named model view, PIDVUE, which can be recalled at a later time. The View Rotation commands preserve the view definition in a saved model view, PIDVUE, when you select the active P&ID drawing view to be rotated. The selected View Rotation command will then restore that view to the saved model view, MDLVUE, and then rotate that named model view about its origin.
146
_ _______________
6.3.2.0.1 Set View Orientation
The Plan View, Iso View, Looking North, Looking South, Looking East, and Looking West commands allow you to set the view orientation to one of the standard viewing directions. You can specify more than one screen with the same view.
Set View Orientation
6. Approval
The default screen orientations are:
Plan View Orients a screen to the plan view orientation. Isometric View Orients a screen to the isometric viewing direction. Looking North Orients a screen view looking north. Looking South Orients a screen view looking south. Looking East Orients a screen view looking east. Looking West Orients a screen view looking west.
147
_ _______________
6.3.2.0.2
Update Window
The Update View commands updates the screen display for a virtual screen or a specified view.
Update Both Updates both (left and right) virtual screens. Update Left Updates the left virtual screen. Update Right Updates the right virtual screen. Update View Updates the selected window view. The system prompts you to select the view to update.
148
_ _______________
6.3.2.0.3 Rotate About View
The Rotate About View commands allow you to rotate a view about the selected axis (X, Y or Z). The angle follows the Right Hand Rule with the thumb pointing toward the positive axis.
Rotate About View
6. Approval
X Axis - Rotates the horizontal axis of a screen view counter-clockwise. Y Axis - Rotates the vertical axis of a screen view counter-clockwise. Z Axis - Rotates the X and Y axes of a screen view counter-clockwise.
149
_ _______________
6.3.2.0.4
Match Planar Element Command

The Match Planar Element command allows you to establish a view normal to a planar element.
150
_ _______________
6.3.2.0.5 Rotation 3 Points
The Rotation 3 Points command allows you to rotate the view orientation so that you are looking normal to the X and Y planes defined by the three points. The first two data points define the X axis. The line between the first and third data points define the Y axis.
Rotation 3 Points
6. Approval
Operating Sequence
1. Enter first point @x axis origin by placing a data point to define the origin of the X axis. Enter second point on x axis by placing a data point to define the positive direction of the X axis. Enter point to define y axis by placing the third data point to define the Y axis. The viewing plane will be parallel to the plane defined by the three data points.
2.
3.
151
_ _______________
6.3.2.0.6
Dialog View Rotation

This command activates the MicroStation View Rotation dialog box which can be used to control view rotation.
Commands
Std. Sets a standard orientation of Top, Bottom, Back, Left, Iso(metric), or Right Iso(metric). View Sets the view for which rotation is displayed. Step Sets the rotation increment in degrees for each click on a "+" or "-" control. "+" control Rotates the view in the positive direction by the specified Step amount. "-" control Rotates the view in the negative direction by the specified Step amount. Apply Applies the displayed rotation to the chosen View.
152
_ _______________
6.3.2.0.7 Color Shading
The Permanent Color Shading and Color Shading options are used to render the contents of a screen view. When you select either of the color shading options the system displays a list of render options.
Color Shading
6. Approval
Select the option for the type of rendering to be performed and select the screen view to be processed. For Permanent Color Shading, select a view number from the form (1-8). The selected view will display with the specified render option until you change it. For Color Shading, place a data point in the screen view to be updated. The rendered view will revert to wireframe display when it is updated.
153
_ _______________
6.3.3
Render Options
Wiremesh
This option renders the contents of a view(s) as a wiremesh display. Wiremesh display is similar to the default wireframe display in that all elements are transparent and do not obscure other elements. In a wiremesh display, however, curved surfaces are represented by a polygonal mesh rather than a simple wireframe. This representation can increase the realism of curved surfaces, although it may also increase the amount of clutter as more lines are displayed for surfaces that would normally be hidden.
Cross-Section
This option renders the contents of a view as a cross-section. If an auxiliary coordinate system (ACS) is active, the cross-section is cut at the X-Y plane of the ACS. Otherwise it is cut at the views active depth (parallel to the view).
Hidden Line
This option renders the contents of a view as a polygon display. In a polygon display, only parts of elements that would actually be visible are displayed. Lines hidden behind objects are removed to create a more realistic representation. MicroStation accomplishes this by decomposing each element into polygons. Hidden line removal processing is much slower than wireframe and wiremesh display, and the processing time is roughly equivalent to the other, more realistic type of rendering.
Filled Hidden Line

This option renders the contents of a view as a filled polygon display. A filled polygon display is identical to a polygon display except that the polygons are filled with element color. This creates an interesting cartoon-like effect that may be useful in some circumstances, particularly if the hardware can display only a limited number of colors.
Constant Shading
This option renders the contents of a view as a constant shaded model. In a constant shaded model, each element is displayed as one or more polygons filled with a single (constant) color. The color is computed once for each polygon from the element color, material characteristics, and lighting configuration (see 3D concepts in the users guide). Curved surfaces are decomposed into a mesh of polygons. Each polygon is shaded with a single color and surfaces appear tiled.
154
_ _______________
Smooth Shading
This option renders the contents of a view as a smooth (Gouraud) shaded model. In smooth shaded models, the appearance of curved surfaces is more realistic than in constant shaded models because polygon color is computed at polygon boundaries and color is blended across polygon interiors. This gives surfaces a smooth appearance.
Render Options
6. Approval
Phong Shading
This option renders the contents of a view as a Phong shaded model. This is the most realistic type of rendering supported by MicroStation. In a Phong shaded model, the color of each pixel is recomputed. Phong shading is useful for producing high-quality images when speed is not critical and very exact lighting effects are desired. If light sources are close to the objects being rendered, such as a spotlight shining on a home, Phong shading may be the only way to see the exact location of the light beam. Large numbers of computations slow display time considerably. In most instances, Phong shaded models are very similar to smooth shaded models and do not justify the increased processing time.
Stereo
This option renders the contents of a view as a 3D image. It creates a stereo pair of images and merges the two images into a single image, which you can view by wearing red/blue glasses. Put on the red/blue glasses making sure that the red lens is over the left eye and the blue lens is over the right eye. View the image with your eyes level and square to the screen.
155
_ _______________
6.3.3.1
Camera View
This option activates options used to define the target, position, and clipping planes for a view camera.
Camera Setup
This option lets you set the target, position, and clipping planes for a view camera and turn on the camera for the view. The camera lens is set with the Camera Lens option. To define the camera target use a data point. The point becomes the focal point (center) of the view. Objects beyond the target point will appear smaller due to the nature of the perspective projection. Objects in front of the target point will appear larger and may be excluded from the viewing pyramid. Place a data point to define the camera position. A dynamic pyramid displays to show the viewing volume with the camera at the pointer location. Place a data point to define the front clipping plane (display depth). Any elements or portions of elements in front of this plane are not displayed. Place a final data point to define the back clipping plane (display depth). Any elements or portions of elements beyond this plane are not displayed, but the view is turned on.
156
_ _______________
Camera Position
This option lets you set the position of a view camera without changing the camera target. This is like focusing the camera at an object and moving around to obtain different views of the object.
Camera View
6. Approval
Camera Target
This option lets you set the target of a view camera without changing the camera position. This is like standing in one position and moving the camera to view different targets.
Camera Lens
This option activates the camera lens settings display list. This list lets you set the angles and focal lengths of view camera lenses. The camera lens settings displayed are for the view chosen from the view number option.
Angle/Focal Length
The lens angle for the camera of the chosen view can be specified in degrees or as the lens focal length in millimeters (mm). You can also specify the lens by choosing a standard lens from the Standard option menu. The angles and focal lengths of the standard lenses are:
Standard Lens Fisheye Extra Wide Wide Normal Portrait Telephoto Telescopic Angle 93.3 74.3 62.4 46.0 28.0 12.1 2.4 Focal Length (mm) 20 28 35 50 85 200 1000
Camera Off
This option turns the camera view off.
157
_ _______________
6.3.3.2
Views
The Views commands allow you to manipulate views between two specified windows.
Copy View copies a selected view display from one window to another. Swap View option allows you to change from either the right or left screen display. View On option activates eight view options which correspond to the window views (1-4) on the right screen and window views (5-8) on the left screen. View Off option allows you to select and place a data point in the window view(s) to turn specified views(s) off.
158
_ _______________
6.3.3.3 Level Symbology On
This command provides the option to enable the display of reference models with the active reference model symbology.
Level Symbology On
6. Approval
159
_ _______________
6.3.3.4
Level Symbology Off

This command provides the option to disable the display of reference models with the active reference model symbology.
160
_ _______________
6.3.3.5 Form Left/Right Screen
Form Left/Right Screen
The Form Right Screen / Form Left Screen toggle sets forms to be automatically displayed on the right (front) screen or the left (back) screen. This option is only relevant for dual-screen configurations.
6. Approval
161
_ _______________
6.3.3.6
Set/Do Not Set Display Depth for Review Commands

The Set/Do Not Set Display Depth for Review Commands toggle can be used to inhibit the changing of display depths when using viewing commands.
162
_ _______________
6.3.4 View, More Commands
View, More Commands
6. Approval
Commands
Update Left Updates the screen display for the left virtual screen. Update Right Updates the screen display for the right virtual screen. Update All Updates the screen display for both left and right virtual screens. Update View Updates the screen display for the selected window view. Align View Aligns two views so that they display the same volume. Copy View Copies one view to another view. View On Turns on selected screen views. View Off Turns off selected screen views. View Toggle Turns On or Off the display of any of the eight screen views. Move Up Moves you (pans) up in the selected view. Move Down Moves you (pans) down in the selected view.
163
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Move Left Moves you (pans) left in the selected view. Move Right Moves you (pans) right in the selected view. Level Symbology On Displays reference models with the active reference model symbology. Level Symbology Off Disables the displays reference models with the active reference model symbology. Weight Display Toggle Toggles the line weight in the selected view to 0 or to the weight of the graphic symbology of the graphics within the view. Grid On/Off Toggles the grid on and off in the selected view.
164
_ _______________
6.3.5 Viewing Direction
Viewing Direction
6. Approval
Commands
Plan View Orients a screen view to the plan view orientation (Top). Iso View Orients a screen view to the isometric viewing direction. South Elevation Orients a screen view looking south. North Elevation Orients a screen view looking north. West Elevation Orients a screen view looking west. East Elevation Orients a screen view looking east. Rotate View - Element Rotates a view to align it with an existing planar element. Rotate View - Absolute Rotates a view to a specific orientation. Rotate View - Relative Rotates a view counterclockwise about its center. Rotate about Z Axis Rotates view about the Z axis. Rotate about X Axis Rotates view about the X axis. Rotate about Y Axis Rotates view about the Y axis. Rotate View by 3 Points Rotates a view as specified by data points.
165
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Match Planar Element Rotates a view to align it with an existing planar element. Dialog View Rotation Activates the MicroStation View Rotation dialog box.
166
_ _______________
6.4 View Depth
View Depth
6. Approval
Commands
Set Active Depth Sets the active depth; type the working unit value (relative to the current active depth) of displacement. Set Display Depth Specifies the front and back of a range in a 3D view to be displayed along the Z axis. Set Active Depth - Absolute Sets the active depth along the Z axis for a specified view. Set Display Depth - Absolute Sets the display depth for a view. Specify the front and back values which are the distances along the view Z axis from the global origin to the front and back planes of the desired view cube. Set Active Depth - Relative Sets the display depth for the active view, where depth is the distance, in working units, to move the active depth along the Z axis. Set Display Depth - Relative Sets the display depth for a view. Specify the front and back values which are the relative distance along the view Z axis from the front and back planes of the existing view cube to the front and back planes of the desired view cube. Show Active Depth Displays the active depth for a specified view. Show Display Depth Shows the display depth for a specified view.
167
_ _______________
6.5
File Commands
These commands provide file manipulations. These commands allow you to plot interference, compress the design file, save the active MicroStation and PDS parameters, and exit the graphics session.
Commands
File Allows you to to plot clashes, save the active MicroStation and PDS parameters and exit the graphics session. Print Print, is available only on Windows NT. If you are running PDS on MicroStation version 5.0, the Print command provides access to the MicroStation Print command. If you are running PDS on MicroStation 95, the Print command provides access to the MicroStation Plot command. Compress Design Compresses the design file. Exit Exits the design file.
168
_ _______________
6.5.1 File Commands
These commands allow you to plot and diagnose problems in design files. They also allow you to define the active options for the file and what reference models are attached and displayed.
File Commands
6. Approval
Commands
Plot Clashes Prints default or detailed clash plots. See Plot Clashes, page 170 for more information. File Design Saves the active MicroStation and PDS parameters. Exit Exits the graphics environment and saves all changes to the design file.
169
_ _______________
6.5.1.1
Plot Clashes
This option activates the Plot Clashes form. It is used to automatically plot interference clashes based upon search criteria using Interference Management data. The Interference Checker must be run at some point before using this option.
Default Plot
Each plot contains the following information: A unique plot number for easy identification within the group of interference clashes being plotted. The model numbers of the components involved in the clash. The clash types of the model. The short version of the clash type is used if it exists in the Standard Note Library, otherwise the long version is used. The models categorized as Model A and Model B. Clashing components are categorized as Model A and Model B in the order of their clash precedence, which is hard, soft, and construction, respectively. When a clash is found between components which both contain insulation where each component could be clashing with the other components insulation, the system randomly defines one component as Model A, hard, and the other as Model B, soft. The design area number corresponding to the model number for each component involved in the clash. The previous item requires a change to the format of the clash plot border for the 5.0 release. You must copy the clash plot border, borderifc.dgn, from the PD_Clash product directory into your project directory. This copy is not part of the Automated Upgrade Process because you may not wish to override your existing border file. You must also copy the ifc.i file into your project directory for plotting purposes. It is delivered but the copy is not part of the Automated Upgrade process. The Review Action from the Clash Review History Data Table (PDtable_135), including the information that the clash has been approved as a real or false clash. The Review Date from the Clash Review History Data Table (PDtable_135). The Review Comments from the Clash Review History Data Table (PDtable_135), as many as 100 characters to the pertinent construction tolerance value, if applicable.
170
_ _______________
Plot Clashes
6. Approval
171
_ _______________
Detailed Clash Plots

Detailed clash plots include the model representation in addition to the interference envelopes for components other than the two components involved in the clash. All components falling within the clash plots volume and existing in the two applicable models is displayed with the two clashing components and the corresponding interference envelopes. The envelope graphics of the two clashing components are plotted with weight of 4 and a style of dashed. The model graphics of the two clashing components are plotted a weight of 2 and a style of solid. The model graphics of the other components are plotted with a weight of 0 and a style of solid. By default, plots include the two clashing items. If detailed plots are required, revise the marker file with Project Administrator > Project Data Manager.
172
_ _______________
Plot Clashes
6. Approval
173
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 There is a primary discipline called the Action Discipline for every model combination. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take "action" to resolve the clash. The Action Discipline is at the top of each clash so that clashes may be easily sorted and routed to the person responsible for the clashes in that discipline. When a plot queue is selected, it is used for all graphic interference clash reports that are being plotted in one batch process.
Commands
Unplotted Clashes Specifies that only unplotted clashes of the specified types be plotted. Unapproved Clashes Specifies that only unapproved clashes of the specified types be plotted. Unreviewed Clashes Specifies that only unreviewed clashes of the specified types be plotted. Default Clash Plots / Detailed Clash Plots Submits either default or detailed clash plots. See the examples of each in the following sections. Submit Immediately/Delayed Submit Submits or delays submission of the job. When the toggle is set to Delayed Submit, the system displays the following fields for you to specify the submission time.
174
_ _______________
6.5.1.2 File Design
The File Design command allows you to save the active parameters defined in the current design session. This command saves: MicroStation parameters such as active views and active display volumes It also saves the screen location of the Piping Designer base form.
File Design
6. Approval
6.5.1.3
Exit
The Exit command is used to exit the graphics environment. Exiting a design file does NOT save the active parameters set in the file. To save the active parameters, you must use the File Design command. Select the Exit command to exit a design file and save the changes.
175
_ _______________
6.6
Element Commands
The Element pull-down provides the Analyze command .
6.6.1
Analyze
The Analyze option opens the Element Information settings box, which is used to change the attributes of an element(s) and review design file data associated with them, such as geometry and database attributes. DO NOT use the Analyze command to change any properties of a PDS element. This feature should be used only as an investigative tool in PDS applications. It is permissible to use this command on non-intelligent, user-defined elements in the model file; however, use of this command should be limited to those elements. When the Analyze command is active and a single graphics element is selected, the displayed data pertains to that element. Use the Next command to display data on any nested elements. The element type is shown in the title bar. The type number is shown in the upper left corner of the settings box.
Refer to the MicroStation Users Guide for more information on the Analyze command.
176
_ _______________
6.7 Setting Commands
The Settings commands provide the ability to modify rendering, fonts and colors used during a graphics session.
Setting Commands
6. Approval
Command Groups
Colors Modifies the colors used in the graphics environment. Use the File Design command from the File palette to save your settings before exiting the design file. Each tile in the color palette represents a color in the active color table. To modify a color, you must first select it. The selected color has an enlarged tile in which its index number (0-255) is displayed. The view background color is in the lower right corner of the palette, denoted by "B." Double-clicking a tile opens the Modify Color dialog box, which is used to modify the color. Fonts Opens the Fonts setting box. To see a type sample for a font, select in the list box.
177
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Rendering Opens the Rendering Settings box, which is used to adjust rendering settings. It controls distance cuing, which determine how atmospheric fading is set in the view. You can also set the Fog Color in this dialog box, which can be used to create a realistic atmospheric haze.
178
_ _______________
6.8 User Commands
These commands provide access to PDS help and to the user preferences and button assignment that are specific to your system.
User Commands
6. Approval
Help
Displays Help for the PDS 3D products.
User Preferences
The User Preferences command changes things that apply only to your system such as how memory is used on your system, how windows are displayed, how various items on the screen are laid out and behave, how reference files are attached by default, and so on. As the name implies, you can adjust these settings to suit your preferences.
Button Assignments
The Button Assignments command changes digitizing tablet or mouse button assignments. You can change the 3D Data and 3D Tentative buttons assignments, as well as 10 cursor button assignments for cursor button menus.
179
_ _______________
6.9
Interference Management Data

This option activates the Interference Management Data form. It is used to display the complete file specifications of the Interference Management models and the project and design areas where applicable. It displays only those areas owned and controlled by interference management data.
The form also highlights and allows you to re-create any marker file that has an incorrect data structure or has become corrupted. For example, if you have manually copied the projects model seed file as the interference management model, you have the option to revise the model with the correct data structure.
Field Descriptions
Marker File Node Name Displays the node name of the location of the marker file. Marker File Path Name Displays the path name where the marker file resides.
180
_ _______________
6.10 Piping Clash Review (in the PD_Design Module)
This option locates and reviews those interference clashes that have been reported for the active model. It is only available in the PD_Design module but is included here to provide the full scope of PDS clash review information. It can be used to help identify and correct interference clashes. This option operates similarly to the Interference Manager option in the Interference Checker/Manager module including the ability to revise any Interference Management data in the active piping model. As you review the clashes, the system highlights the two components involved in the clash.
Piping Clash Review (in the PD_Design Module)
6. Approval
Field Descriptions
Project Name Displays the name of the active project. Design Area Displays the name of the active design area. Date Displays the date the checker was run. The information in this field is set with the Checker Run Dates option in the Interference Checker/Manager module. Clash Type Describes the current type of clash. This field is the first field on the left. Clash Status Displays the clash status as approved or unapproved. Marker Number Displays the number of the current clash. Select a marker number with the left and right arrows, select the field and key in a marker number, or select the Keyin Marker Number option and key in a marker number.
181
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Model / Area Name Displays the names of the model files and the design area that have components involved in a clash. Item Displays descriptions of the clashing components in the Item fields which are located below the Model fields. The system accesses the user-defined labels in the Label Description Library to create: the primary description, which is displayed on the top line with a a limit of 20 characters; and the secondary description, which is displayed on the bottom line and has a limit of 40 characters. These descriptions are defined with the Clash Management Labels option on the Create Label Data form in the Reference Data Manager. Comments: Displays existing comments about the active clash.
Commands
Clashes Unapproved / Clashes Approved Displays either unapproved or approved clashes. Plot Clashes Select this option to immediately plot the clash being reviewed. The system generates temporary plot files in the c:\temp directory. This option uses the last-used queue or the default queue if nothing has been plotted during the current session. Select View Select this option and identify the screen view to display the active clash. Restore View Select this option to restore the selected view to its original viewing parameters. Keyin Marker Number Select this option and key in a marker number. The system updates the window coordinates about the clash in the selected view.
Field Descriptions
Clash Type Describes the current clash type (such as hard/hard or hard/soft). Status Displays the approval status of the current clash. Marker Number Displays the number of the current clash. Select a marker number with the left and right arrows, select the field and key in a marker number, or select the Keyin Marker Number option and key in a marker number.
182
_ _______________
Model / Area Displays the names of the models and the design files associated with the clashing components. Item Displays descriptions of the clashing components. If prompted to... Select Review Option Do this: Set the toggle to Review Unapproved Clashes or Review Approved Clashes to determine the type of clashes to review.
Piping Clash Review (in the PD_Design Module)
6. Approval
183
_ _______________
6.11
Piping Clash Check (in the PD_Design Module)

This command checks a pipeline or user-defined active groups for interferences immediately after completing the line. It automatically creates interference envelopes in memory for any piping in the selected pipeline or active group. It checks any attached reference models for which interference envelope files have been created previously. It also reports any reference models for which interference envelopes have not been created previously. The results of this interactive clash checking is not maintained as a part of the Interference Management data. However, you can use the Piping Clash Review option to review the clashes detected by this command. Construction tolerances and angular tolerances (tolerance for recognizing horizontal beams for determining when piping is legitimately resting on steel) are considered during the interference checking process. The sparse version of the structural model is used when creating interference envelopes. Model management data must be loaded for the sparse structural models through the Project Environment Manager. This command does not affect the interference envelopes created by the Interference Managers Envelope Builder.
Commands
Select View Identifies the screen view to display the active clash. Restore View Restores the active view(s) to the initial viewing parameters for the clash being checked. Previous/Next Marker Number Reviews the next/previous marker. The system updates the window coordinates about the clash in the selected view. If prompted to... Do this:
Identify Pipeline or Define Active Group Snap to a segment or locate a component to identify the pipeline to be processed or use the Define Active Group command to identify define the items to be processed. Accept to Check Pipeline Select Confirm ( ) to process the identified pipeline or select Cancel (X) to reject the pipeline.
Identify Pipeline or Select Review Option Identify another pipeline as outlined or select the Piping Clash Review option to review the detected clashes.
184
_ _______________
Piping Clash Check (in the PD_Design Module)
6. Approval
Select Review Option
Select one of the options to review the clash.
185
_ _______________
6.12
Review PDS Clash

The Review PDS Clash command edits and reviews existing clashes and approves existing clashes.
Parameters
Project Name Displays the active project name. Design Area Displays the active design area name. Clash Type Displays the clash type. Date Displays the date and time the clashes were detected. Unapprove Clash Changes the status of the clash from approved to unapproved. Approve Real Clash Approves the clash as a real clash in the Project Control Database. Approve False Clash Approves the clash as a false clash in the Project Control Database. Review Unapproved Clash / Review Approved Clash Specifies if you want to review approved or unapproved clashes. Clash Marker Displays the number of the current clash. Select a marker number with the left and right arrows; or, select the field and key in a marker number.
186
_ _______________
Item A Displays the model name and the corresponding design area that has the one item of the clash. The descriptions of the clashing component display below the model name and design area. Item B Displays the model name and the corresponding design area that has the one item of the clash. The descriptions of the clashing component display below the model name and design area. Comments Displays existing comments about the active clash. You can also select the field and type in any additional information. Highlight Clash Highlights the clash in the selected view. Select View Zooms in and updates the selected view. Click Select View then select the view you want to update.
Review PDS Clash
6. Approval
187
_ _______________
188
_ _______________
7. PDS Interference Plotting
This section provides information on interference plotting, including information on managing the plot files, in the following order: Interference Plot Manager Interference Plot Management Data
PDS Interference Plotting
7. Plot
189
_ _______________
7.1
Interference Plot Manager

This option activates the Interference Plot Manager form. It is used to plot interference clashes based upon search criteria using Interference Management data. The Interference Checker must be run at some point before using this option.
Default Plot
Each plot contains the following information: A unique plot number for easy identification within the group of interference clashes being plotted. The model numbers of the components involved in the clash. The clash types of the model. The short version of the clash type is used if it exists in the Standard Note Library, otherwise the long version is used. The models categorized as Model A and Model B. Clashing components are categorized as Model A and Model B in the order of their clash precedence, which is hard, soft, and construction, respectively. When a clash is found between components which both contain insulation where each component could be clashing with the other components insulation, the system randomly defines one component as Model A, hard, and the other as Model B, soft. The design area number corresponding to the model number for each component involved in the clash. The previous item requires a change to the format of the clash plot border for the 5.0 release. You must copy the clash plot border, borderifc.dgn, from the PD_Clash product directory into your project directory. This copy is not part of the Automated Upgrade Process because you may not wish to override your existing border file. You must also copy the ifc.i file into your project directory for plotting purposes. It is delivered but the copy is not part of the Automated Upgrade process. The Review Action from the Clash Review History Data Table (PDtable_135), including the information that the clash has been approved as a real or false clash. The Review Date from the Clash Review History Data Table (PDtable_135). The Review Comments from the Clash Review History Data Table (PDtable_135), as many as 100 characters to the pertinent construction tolerance value, if applicable.
190
_ _______________
7. Plot
191
_ _______________
Detailed Plots
Detailed clash plots include the model representation in addition to the interference envelopes for components other than the two components involved in the clash. All components falling within the clash plots volume and existing in the two applicable models is displayed with the two clashing components and the corresponding interference envelopes. The envelope graphics of the two clashing components are plotted with a line weight of 4 and a style of dashed. The model graphics of the two clashing components are plotted with a line weight of 2 and a style of solid. The model graphics of the other components are plotted with a weight of 0 and a style of solid. When a plot queue is selected, it is used for all graphic interference clash reports that are being plotted in one batch process. There is a primary discipline called the Action Discipline for every model combination. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take "action" to resolve the clash. The Action Discipline is at the top of each clash so that clashes may be easily sorted and routed to the person responsible for the clashes in that discipline.
192
_ _______________
7. Plot
193
_ _______________
Commands
Unplotted Clashes Specifies that only unplotted clashes of the specified types be plotted. Unapproved Clashes Specifies that only unapproved clashes of the specified types be plotted. Unreviewed Clashes Specifies that only unreviewed clashes of the specified types be plotted. Approved Real Clashes Specifies that only approved real clashes be plotted. Approved False Clashes Specifies that only approved false clashes be plotted. Select Markers From List Displays a list of markers for the clash types selected so that you can specify which clashes are plotted.
194
_ _______________
Default Clash Plots / Detailed Clash Plots Submits either default or detailed clash plots. See the examples of each in the following sections. Submit Immediately/Delayed Submit Submits or delays submission of the job. When the toggle is set to Delayed Submit, the system displays the following fields for you to specify the submission time.
7. Plot
195
_ _______________
7.2
Interference Plot Management Data

This option activates the file specification fields. They are used to define the specific network address and path name in the Project Control Database where the system sends all Interference Management plot files. If this option is not used, the system will put the plot files in the directory where the Interference Checker/Manager was initiated.
Field Descriptions
Node Name Key in or accept the network address where the Interference Management plot files are sent. File Path Key in or accept the path name where the files are placed.
196
_ _______________
8. Interference Reporting
This section provides information on interference reporting, including information on managing the report files. 8.1 8.2 Clash Report Manager Form on page 198. Interference Report Management Data on page 238.
Interference Reporting
8. Reports
197
_ _______________
8.1
Clash Report Manager Form

This command activates the Clash Report Manager form. It is used to generate reports from the Project Database with the report definition data. The Clash Report Manager stores the report record and location records for each discrimination data file and format file in the Project Control Database. The numbered records are used to locate ASCII files on their specified nodes.
Commands
Report Format Creates, revises, copies, or deletes only the record of a format file. Report Discrimination Data Creates, revises, copies, or deletes the record of a discrimination data file. The chosen action is also performed on the actual report discrimination data file. Report Creates, revises, deletes, approves, or multi-creates report records used to define or generate reports. Report Management Data Creates a Project Control Database record of the default node name and path for the report definition files. This option is primarily used for setup.
198
_ _______________
8.1.1 Using the Report Commands
Understanding Report Files and Records
The Clash Report Manager uses the discrimination data files, format files, and database records that represent these files to generate reports. The following definitions explain all of the files and records in the reporting process.
Using the Report Commands
Format File and Record

The format file is a user-defined, ASCII file which must be created with a text editor outside of the Clash Report Manager. It contains special indices identifying what data appears in the report and how the data is sorted. It also defines how the data is formatted in the report. Without the format file(s), Clash Report Manager reports cannot be processed. A set of basic format files is delivered for each type of reporting. Using the Report Format option, you can create a numbered record for each format file so that it can be accessed for report processing. The format record is a record in the Project Control Database used to name and locate a specific format file. Unlike the format file, the format record is created interactively. It is called a record to classify it as a block of data that is used for report processing but is not an actual file.
8. Reports
Discrimination Data File and Record

The discrimination data file limits the report to only the specified database occurrences. It is an ASCII file that is created interactively using the Clash Report Manager. The discrimination data record is a record in the Project Control Database used to name and locate a specific discrimination data file. There is a uniquely-numbered record for each discrimination data file so that it can be accessed for report processing. This is the same way that the format record is used to access a format file.
Report Output and Record

The Clash Report Manager creates a report using the specified format, discrimination, and search criteria data files, and places it in the specified directory on the specified node. The report record names or defines locations for all of the files that are necessary to generate a report, including the report output. (It is called a record to classify it as a block of data that is used for report processing but is not an actual file.)
199
_ _______________
Group Workflow
There is a definite workflow for at least the first time you create a report. First, use the Report Management Data option to specify defaults for the node name and path of the report definition files. By defining the defaults first, you can prevent keying in a node name and path on each form. If you want to use a different node name or path than the defined default, simply place a data point in that field and key in the modification. The following steps can be done in any order: create your format record, discrimination data record, and discrimination data file using the Report Format and Report Discrimination Data options. Reports cannot be generated until the format file, the discrimination data file, and their corresponding records have been established. Finally, use the Report option to create the actual report.
200
_ _______________
8.1.2 Report Format Form
When you choose the Report Format option from the Report Manager form, the Report Format form is displayed.
Report Format Form
8. Reports
This form enables you to create, copy, revise, or delete a record of the location of the format file in the project control database. An option is also provided that enables you to copy a record and its corresponding ASCII format files. The format file defines the data that will be reported and the way in which that data will be displayed. Reports cannot be generated unless a format file exists and a record of the files location has been entered into the project control database.
Options
Create Displays the Format Creation/Revision form, which enables you to add a new record of a format file in the project control database. For more information, see Format Creation/Revision Form, page 203. Copy Displays the Format Creation/Revision form, which copies the record of an existing format file from the project control database along with the corresponding ASCII format file. For more information, see Format Creation/Revision Form, page 203. Revise Displays the Format Creation/Revision form, which modifies a record of an existing format file in the project control database. For more information, see Format Creation/Revision Form, page 203.
201
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Delete Displays the Deletion form, which deletes an existing record of a format file from the project control database. If the record of the format file is deleted, reporting cannot be performed. For more information, see Format Deletion Form, page 205.
202
_ _______________
8.1.2.1 Format Creation/Revision Form
When you choose Create, Copy, or Revise from the Report Format form, the Format Creation/Revision form is displayed.
Format Creation/Revision Form
This form creates or revises a record in the project control database; this record defines the location of a format file. The format file itself defines the contents and format of the report. Both the location specification and the format file must exist to report on PDS data.
8. Reports
Field Descriptions
Number A unique number of up to 24 characters. Specifies the short name in the project control database used to identify the record of the format file. Description A description of up to 40 characters for the format file. File Specification The file name of the format file to reference. Path The disk location of the format file. This field retains the active setting. Node The nodename of the system on which the format file is located. This field retains the active setting.
Before Using this Form

You must have created an ASCII format file. A set of basic format files is delivered with the PD_Report product in the /pdreport/sample directory. The file for MTO reporting is named piping_#.fmt.
203
_ _______________
Operating Sequence
1. Select Create, Copy, or Revise. A list of available records displays for copy or revision. To create a database record, go to Step 3. 2. Select Report Format From the displayed list, select the record to be copied or revised. Then click Accept. Key-in fields are displayed for you to specify the required database information. 3. Specify Report Format Data Type information in each of the displayed fields, taking care to press return in each field. Then click Accept. The project control database is updated.
204
_ _______________
8.1.2.2 Format Deletion Form
When you choose Delete, the Deletion form is displayed.
Format Deletion Form
8. Reports
This form deletes a report record from the project control database and canoptionally delete the associated file. This form is used with format files and their database records, discrimination data files and their database records, and search criteria files and their database records.
Fields and Options

Number/Description Displays the 24-character short name and the 40-character description of a report record in the project control database. Delete File/Do Not Delete File Determines whether the associated file is deleted. When set to Delete File, the database record is deleted along with the associated file. When set to Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format From the displayed list, select the database record to be deleted.
205
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept. The specified record is deleted. If specified, the associated file is also deleted.
206
_ _______________
8.1.3 Report Discrimination Data Form
When you select Report Discrimination Data from the Report Manager form, the Discrimination Data form is displayed.
Report Discrimination Data Form
8. Reports
This form creates, copies, revises, and deletes a discrimination data file from the specified directory. The associated record in the project control database is also copied, revised, or deleted as needed. A discrimination data file is an ASCII file that designates which models will be included in a report. That is, discrimination data specifies the scope of the report. The project control database record specifies the name and location of the discrimination data file that is to be associated with a specific report.
Options
Create Displays the Discrimination Data Creation form, which creates a new discrimination data file. The associated project control database record is also created. Copy Displays the Discrimination Data Revision form, which copies an existing data file. The associated project control database record is also copied. Revise Displays the Discrimination Data Revision form, which modifies discrimination data. You can use this option to revise the contents of the discrimination data file, the location of the discrmination file, and the associated record in the project control database.
207
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Delete Displays the Deletion form, which deletes a discrimination data file as well as its associated record in the project control database. For more information, see Discrimination Data Deletion Form, page 219.
208
_ _______________
8.1.3.1 Discrimination Data Creation Form
This option activates the Discrimination Data Creation form. This form is used to create a discrimination data file in the specified directory and its record in the Project Control Database. This form may also be used to specify segment and component search criteria, using the corresponding buttons near the bottom of the form. If you use this form to specify search criteria data, and you specify search criteria data using the Report Search Criteria command form, the data specified using the Report Search Criteria command form will take precedence.
Discrimination Data Creation Form
After including any models or search criteria to the discrimination data file, make sure to select the final Accept. This step could be forgotten because Accept has already been selected on the model and search criteria selection forms, but the final Accept is necessary to actually create the discrimination data file.
8. Reports
Commands
Discipline Extent Predefines the disciplines of the clashes to be reported with the clash report. All disciplines are reported by default. Using this option, you can select the disciplines to include from a list of the active projects discipline. For example, if you select the Piping discipline, only clashes which involve at least one piping component are reported. Geographic Extent Predefines the volume of the clashes to be reported with the clash report by selecting one of the following options. Active Project includes all clashes within the volume of the entire project. Select by Design Area Ownership includes all clashes within the volume of the selected design areas. The clashes are selected on the basis of the primary design area for either component A or component B in the Clash Data Per Project Table, (PDtable_132).
209
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Select by Models includes all clashes within the volume of the selected models. The clashes are selected on the basis of the model number for either component A or component B in the Clash Data Per Project Table, PDtable_132. Interference Search Criteria Predefines the extent of clashes to be reported with the clash report by specifying search criteria for any of the clash management data within the Project Control Database. See Project Search Criteria Form, page 212 for more information.
Field Descriptions
Number Key in a unique number to name the discrimination data record with up to 24 characters in the Project Control Database. This number is a short name to identify the record of the discrimination data file. Description Key in a description of the discrimination data file with up to 40 characters in the Project Control Database. File Specification Key in the filename of the discrimination data file to reference. The system verifies that the file does not already have a record in the project. File Path Displays the disk location of the discrimination data file. This field retains the active setting. File Node Displays the node name where the discrimination data file is located. This field retains the active setting. Clash Area Select the clash area on which to report from a list of all possible design areas where interference checking can be performed. This information is part of the search criteria for reporting and must be defined. It can be modified by selecting the related attribute in the tables where it exists. Clash Approval Select the clash approval from a list of three approval categories. This information is part of the search criteria for reporting. Clash Type Select the clash type from a list of available clash types. This information is part of the search criteria for reporting. Review Action Selects the Review Action on which to report from a list of all possible actions on the basis of the Clash Review History Data Table (PDtable_135). The clash report must include the unique clash id in order for the clashes to be reported.
210
_ _______________
8.1.3.1.1 Project Administration Form Discipline Extent
Project Administration Form
Predefines the disciplines of the clashes to be reported with the clash report. All disciplines are reported by default. Using this option, you can select the disciplines to include from a list of the active projects discipline. For example, if you select the Piping discipline, only clashes which involve at least one piping component are reported.
Geographic Extent
Predefines the volume of the clashes to be reported with the clash report by selecting one of the following options. Active Project includes all clashes within the volume of the entire project. Select by Design Area Ownership includes all clashes within the volume of the selected design areas. The clashes are selected on the basis of the primary design area for either component A or component B in the Clash Data Per Project Table, (PDtable_132). Select by Models includes all clashes within the volume of the selected models. The clashes are selected on the basis of the model number for either component A or component B in the Clash Data Per Project Table, PDtable_132.
8. Reports
211
_ _______________
8.1.3.1.2
Project Search Criteria Form

This option activates the Project Search Criteria form. It is used to define the criteria used when creating a report.
Field Descriptions
Select Table to define search criteria: Selects the table that holds the attributes that relate to the specific data occurrences to restrict for reporting. After a table is selected, you select specific attributes within that table. For each of the selected attributes, you set the search criteria with logical operators for the rows of data within the selected table or related tables. The related tables are listed in the bottom field. Search Criteria which will affect data retrieved from above Table: Displays the tables that are associated to the selected table by predefined relationships between attributes. These tables, therefore, affect the actual data that is reported from the selected table. Remember that the search criteria defined in the selected table in the top field, and all related tables in the bottom field, is what actually affects the data that is retrieved. This can result in a very narrow search criteria for the report. Since this field is meant to inform you of the tables that affect the data retrieved from the attributes you specify, it is a read-only field.
Commands
Clear All Search Criteria Removes any previously defined project search criteria. If prompted to... Select Option Do this: Select the table to define the search criteria and click Accept to accept the highlighted table.
212
_ _______________
The system activates the Search Criteria form with a list of attributes for the selected table and an Interference Clash Per Job display list.
Project Search Criteria Form
For any date attribute selected, the system displays the Define Date/Time form. See the Define Date/Time section for more information.
8. Reports
Select Attribute
Select the attribute to be restricted. The system displays the selected attribute in a separate field and displays a list of operators.
Select Operator
Select an operator to define the search criteria. The system displays the selected operator and prompts you to key in an attribute value.
Enter Attribute Value
Key in the attribute value. For a substring search, key in a string to appear anywhere within the attribute value (do not use wild cards) or select a value from a codelisted form, then select the value and click Accept. The system validates the input and displays the defined search criteria in the Interference Clash Data Per Job field.
Accept or Select And/Or Operator
213
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Select AND to specify an additional condition or select OR to specify an alternative condition or click Accept to accept the defined search criteria.
214
_ _______________
8.1.3.1.2.1 Define Date/Time
Date attributes, when used in the search-criteria selection process, activate the Define Date/Time form. It is used to define the search criteria date and time. The operator, which you select on the Project Search Criteria, form defines the dates on which to report before, after, or equal to the date selected on this form.
Define Date/Time
8. Reports
Field Descriptions
Time Offset Modifies the currently set date, which is displayed in the Date/Time Setting fields, to an earlier or later date and time. Modification of any of the fields in the Time Offset field results in an immediate update of the Date/Time Setting field. Weeks Modifies the number of weeks defined in the Date/Time Setting field. Days Modifies the number of days defined in the Date/Time Setting field. Hours Modifies the number of hours defined in the Date/Time Setting field. Minutes Modifies the number of minutes defined in the Date/Time Setting field. Date/Time Setting Defines the date and time that is used along with the operator set on the Project Search Criteria form to set the search criteria for the report. Month Defines the month used as search criteria. You can move from month to month with the month switch set where the name of the month is displayed. Day Defines the day used as part of the search criteria. Year Defines the year used as part of the search criteria. Hr Defines the hour used as part of the search criteria.
215
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Min Defines the minutes used as part of the search criteria. PM/AM Defines the time of day used as part of the search criteria.
Commands
Before/After Modifies the Date/Time Setting fields with the data specified in the Time Offset fields to before or after its current setting. Now Sets the defined date and time to the setting for the current date and time on the system. Today Sets the defined date to the setting for the current date on the system. Yesterday Sets the defined date to the day before the current date on the system. Tomorrow Sets the defined date to the day after the current date on the system. If prompted to... Select Operator Do this: Select an operator to define the search criteria. The system displays the selected operator and activates the Define Date/Time form.
216
_ _______________
8.1.3.2 Discrimination Data Revision Form
This option activates the Discrimination Data Revision form. It is used to copy or revise a discrimination data file from the specified directory and its record from the Project Control Database. First, the system displays the Record Number display list. When the desired discrimination data file is selected and confirmed, the system then displays the discrimination data identification fields. These fields are used to define the record.
Discrimination Data Revision Form
8. Reports
Commands
Discipline Extent Predefines the disciplines of the clashes to be reported with the clash report. All disciplines are reported by default. Using this option, you can select the disciplines to include from a list of the active projects discipline. For example, if you select the Piping discipline, only clashes which involve at least one piping component are reported. Geographic Extent Predefines the volume of the clashes to be reported with the clash report by selecting one of the following options. Active Project includes all clashes within the volume of the entire project. Select by Design Area Ownership includes all clashes within the volume of the selected design areas. The clashes are selected on the basis of the primary design area for either component A or component B in the Clash Data Per Project Table, (PDtable_132). Select by Models includes all clashes within the volume of the selected models. The clashes are selected on the basis of the model number for either component A or component B in the Clash Data Per Project Table, PDtable_132. Interference Search Criteria Predefines the extent of clashes to be reported with the clash report by specifying search criteria for any of the clash management data within the Project Control Database. See the Project Search Criteria Form, page 212 section for more information.
217
_ _______________
Field Descriptions
Number Key in a unique number to name the discrimination data record with up to 24 characters in the Project Control Database. This number is a short name to identify the record of the discrimination data file. Description Key in a description of the discrimination data file with up to 40 characters in the Project Control Database. File Specification Key in the filename of the discrimination data file to reference. The system verifies that the file does not already have a record in the project. File Path Displays the disk location of the discrimination data file. This field retains the active setting. File Node Displays the nodename where the discrimination data file is located. This field retains the active setting. Clash Area Select the clash area on which to report from a list of all possible design areas where interference checking can be performed. This information is part of the search criteria for reporting and must be defined. It can be modified by selecting the related attribute in the tables where it exists. Clash Approval Select the clash approval from a list of three approval categories. This information is part of the search criteria for reporting. Clash Type Select the clash type from a list of available clash types. This information is part of the search criteria for reporting.
218
_ _______________
8.1.3.3 Discrimination Data Deletion Form
Discrimination Data Deletion Form
8. Reports
Fields and Options

Operating Sequence
219
_ _______________
220
_ _______________
8.1.4 Report Form
When you select Report from the Report Manager form, the Report form is displayed.
Report Form
8. Reports
This form creates, revises, and deletes report records and report files. A report record holds specifications for a report; these specifications include the report name, the report description, and which format file, discrimination data file, and search criteria data file to use to generate a report. The report name is not the title that is printed on the report; the title is included in the format file. At the end of each report, a parameters page is included that contains the following information: Report Output The report number, report title, report creation/revision date, and report node, path, and file name. Format The report format number, description, and node, path, and file name. Discrimination Data The report discrimination data number, description, and file location (network address, path, and file name). The following discrimination data is also included: list of model numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting sequence. Search Criteria The report search criteria number, description, and file location (node, path, and file name. The following search criteria data is also included: list of model numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting sequence.
221
_ _______________
Options
Create Displays the Report Creation form, which creates a report record and generates a report. For more information, see Report Creation Form, page 223. Revise Displays the Revise Report form, which regenerates a report from an existing or revised report record. For more information, see Revise Report Form, page 226. Delete Displays the Deletion form, which deletes an existing report record and the corresponding report. For more information, see Report Deletion Form, page 229. Approve Displays the Report Approval form, which approves an existing report. For more information, see Report Approval Form, page 231. Multi-Create Displays the Report Multiple Submit form, which submits multiple reports to the printer. For more information, see Report Multiple Submit Form, page 234.
222
_ _______________
8.1.4.1 Report Creation Form
When you select Create from the Report form, the Report Creation form is displayed.
Report Creation Form
8. Reports
Use this form to create a report record and to generate a report. Because report records are stored in the project control database, you can use them repeatedly as needed.
Fields and Options

Report Number The 24-character number that uniquely identifies the record of the report file in the project control database. This is sometimes referred to as the report file short name. Report Title The 40-character descriptive name of the report file. This is not the title in the actual report, but is rather the title of the report record. The title of the report is contained in the format file. Report File Spec The name of the report output file (up to 14 characters). Report File Path The disk location for the report output file. This field retains the active settings, and it is automatically populated if you have specified this data on the Report Management Dataform. For more information, see Report Management Defaults Form, page 236. Report Node The name of the system on which the report output file will be located. This field retains the active settings, and it is automatically populated if you have specified this data on the Report Management Data form. For more information, see Report Management Defaults Form, page 236.
223
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 Report Format File The name of the format file to be used to generate the active report. When you select this field, a list of available format files is displayed. Select the appropriate format file, and click Accept. Report Discrimination File The name of the discrimination data file to be used to generate the active report. When you select this field, a list of available discrimination data files is displayed. Select the appropriate discrimination data file, and click Accept. Report Search Criteria The name of the search criteria data file to be used to generate the active report. When you select this field, a list of available search criteria files is displayed. Select a search criteria file, and click Accept. Select this field a second time to specify a different search criteria file. To clear a specification, click Accept without selecting a file. If the report discrimination data selected for the active report has search criteria data defined within it, and you specify a search criteria in this field, the search criteria specified in the Report Search Criteria field takes precedence over the search criteria contained in the discrimination data. Revision Number The revision number (up to three characters) for the report. Last Revision Number The revision number of the last report generated. This is a read-only field; you cannot edit it. Revised By The user (up to five characters) who checked the report. This field is optional. Revision Description The description (up to 40 characters) of the report revision. This field is optional. Print/Delete Submits the report output file to the specified print queue and then deletes the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Print/Save Submits the report output file to the specified print queue and saves the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Save Saves the report output file without printing the report. Submit Immediately/Submission is Delayed Specifies when the report will be processed. When this toggle is set to Submission is Delayed, additional fields display for you to specify the date and time that the report is to be generated.
224
_ _______________
Operating Sequence
1. From the Report form, select Create. The Report Creation form is displayed. 2. Specify Report Data Key in the report record information. Then select the appropriate report format file, discrimination data file, and search criteria data file. 3. Select the appropriate print/save/delete option, and select a queue if the report is to be printed. Specify whether the report is to be generated now (Submit Immediately) or later (Submission is Delayed). If you choose delayed submission, specify the date and time that the report is to be submitted. Click Accept to save the report file.
Report Creation Form
4.
5.
8. Reports
225
_ _______________
8.1.4.2
Revise Report Form

When you select Revise from the Report form, the Revise Report form is displayed.
This form revises an existing report record and generates a report from the project control database. An option is also provided to update (in some cases) the report record without generating a report output file. Similarly, you can choose to generate an updated report output file without updating the report record.
Fields and Options

Report Number The 24-character number that uniquely identifies the record of the report file in the project control database. This is sometimes referred to as the report file short name. Report Title The 40-character descriptive name of the report file. This is not the title in the actual report, but is rather the title of the report record. The title of the report is contained in the format file. Report File Spec The name of the report output file (up to 14 characters). Report File Path The disk location for the report output file. This field retains the active settings. Report Node The name of the system on which the report output file will be located. This field retains the active settings. Report Format File The name of the format file to be used to generate the active report. When you select this field, a list of available format files is displayed. Select the appropriate format file, and click Accept. Report Discrimination File The name of the discrimination data file to be used to generate the active report. When you select this field, a list of available discrimination data files is displayed. Select the appropriate discrimination data file, and click Accept.
226
_ _______________
Report Search Criteria The name of the search criteria data file to be used to generate the active report. When you select this field, a list of available search criteria files is displayed. Select a search criteria file, and click Accept. Select this field a second time to specify a different search criteria file. To clear a specification, click Accept without selecting a file. If the report discrimination data selected for the active report has search criteria data defined within it, and you specify a search criteria in this field, the search criteria specified in the Report Search Criteria field takes precedence over the search criteria contained in the discrimination data. Revision Number The revision number (up to three characters) for the report. Last Revision Number The revision number of the last report generated. This is a read-only field; you cannot edit it. Revised By The user (up to five characters) who checked the report. This field is optional. Revision Description The description (up to 40 characters) of the report revision. This field is optional. Print/Delete Submits the report output file to the specified print queue and then deletes the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Print/Save Submits the report output file to the specified print queue and saves the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Save Saves the report output file without printing the report.
Revise Report Form
8. Reports
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will be processed. When this toggle is set to Delayed Submit to Batch, additional fields display for you to specify the date and time that the report is to be generated. Revise Data Only/Revise Report and Data Specifies revision of the report data only (Revise Data Only) or revision of the report data and the report output file (Revise Report and Data). To revise the report specification without updating the report output file, make the necessary changes, set this toggle to Revise Data Only, and click Accept. To revise the report output file only, set this toggle to Revise Report and Data without modifying any of the fields, and click Accept. To modify both the report file and the report output file, make the necessary changes, set this toggle to Revise Data Only, and click Accept. If you update any field other than Report Number and Report Title, this toggle is automatically set to Revise Report and Data, and the report output file is generated.
227
_ _______________
Operating Sequence
1. From the Report form, select Revise. The Report Creation form is displayed with a list of available report files. 2. Select Report From the displayed list, select the report to be revised. Then click Accept. The fields update to display the selected report file specifications. 3. Revise Report Information Update the report record information as needed. 4. Select the appropriate print/save/delete option, and select a queue if the report is to be printed. Specify whether the report is to be generated now (Submit Immediately) or later (Submission is Delayed). If you choose delayed submission, specify the date and time that the report is to be submitted. Click Accept to save the report file.
5.
6.
228
_ _______________
8.1.4.3 Report Deletion Form
Report Deletion Form
8. Reports
Fields and Options

Operating Sequence
229
_ _______________
230
_ _______________
8.1.4.4 Report Approval Form
When you select Approve from the Report form, the Report Approval form is displayed.
Report Approval Form
Use this form to select a report to approve. Approving a report means that a database attribute is set from not approved (the default) to approved. This approval status provides a way for you to flag reports that you have run and verified that the output data is valid. When a report is revised, the approval status is automatically reset to not approved.
8. Reports
Options
Number The 24-character unique name (as called short name) of the report record. Description The 40-character description of the report record.
Operating Sequence
1. From the Report form, select Approve. The Report Approval form is displayed. 2. From the displayed list, select a report to approve. Then click Accept. The Approval form is displayed. For more information, see Approval/Revision Interface Form, page 232.
231
_ _______________
8.1.4.4.1
Approval/Revision Interface Form

The Approval form is displayed as part of the workflow for approving reports. First you specify the report to be approved on the Report Approval form. When you click Accept, the Approval/Revision Interface form is displayed.
The first time a report is approved, only the Approved By field is active. All other fields are purely informational. The data displayed in these fields is read from the Revise Report form.
Fields and Options

Report Number The 24-character number that uniquely identifies the record of the report file in the project control database. This is sometimes referred to as the report file short name. Report Description The 40-character descriptive name of the report file. Approved By The initials (up to five characters) of the person who approved the report. Revision Number The revision number (up to three characters) for the report. This field is read-only; you cannot edit it. Revised By The initials (up to five characters) of the person who last revised the report. This field is read-only; you cannot edit it.
232
_ _______________
Revision Description Displays a short description of the revision. This field is read-only; you cannot edit it.
Approval/Revision Interface Form
Checked By The initials (up to five characters) of the person who ran the report with the revised information. This field is read-only; you cannot edit it.
Operating Sequence
1. On the Report Approval form, click Accept. The Approval/Revision Interface form is displayed. 2. Specify Approval/Revision Data Key in user initials in the Approved By field. Then click Accept.
8. Reports
233
_ _______________
8.1.4.5
Report Multiple Submit Form

When you select Multi-Create from the Report form, the Report Multiple Submit form is displayed.
Use this form to submit multiple reports at the same time.
Fields and Options

Number The 24-character number that uniquely identifies the record of the report file in the project control database. This is sometimes referred to as the report file short name. Description The 40-character descriptive name of the report file. Print/Delete Submits the report output file to the specified print queue and then deletes the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Print/Save Submits the report output file to the specified print queue and saves the report output file. When you select this option, a list of available print queues is displayed. Click on a queue to select it. Save Saves the report output file without printing the report. Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will be processed. When this toggle is set to Delayed Submit to Batch, additional fields display for you to specify the date and time that the report is to be generated.
234
_ _______________
Operating Sequence
1. From the Report form, select Multi-Create. The Report Multiple Submit form is displayed. 2. Select Reports for Submission From the displayed list, select the reports to submit. Highlighed reports are selected; select a highlighted report to remove the highlight and to not submit the report. 3. Select the appropriate print/save/delete option, and select a queue if the report is to be printed. Specify whether the report is to be generated now (Submit to Batch Immediately) or later (Delayed Submit to Batch). If you choose delayed submission, specify the date and time that the report is to be submitted. Click Accept to submit the reports.
Report Multiple Submit Form
4.
5.
8. Reports
235
_ _______________
8.1.5
Report Management Defaults Form

When you select Report Management Data from the Report Manager form, the Report Management Defaults form is displayed.
This form creates a record in the project control database of the node name and path of the report definition files. This option is used primarily for setup.
Fields
Report Path Specifies the default path of the report output files. It is recommended that you not send output reports to your systems temporary (that is, tmp or temp) directory. Report Node Specifies the default node name of the system on which report output files are located. Report Format Path Specifies the default path of the format files. Report Format Node Specifies the default node name of the system on which format files are located. Report Discrimination Data Path Specifies the default path of the discrimination data files.
236
_ _______________
Report Discrimination Data Node Specifies the default node name of the system on which discrimination data files are located. Report Search Criteria Data Path Specifies the default path of the report search criteria data files. Report Search Criteria Data Node Specifies the default node name of the system on which report search criteria data files are located.
Report Management Defaults Form
Operating Sequence
1. From the Report Manager form, select Report Management Data. The Report Management Defaults form is displayed. 2. Accept or Exit In the fields provided, key in the default paths and node names for the report output files, format files, discrimination data files, and search criteria data files. Then click Accept.
8. Reports
237
_ _______________
8.2
Interference Report Management Data

This option activates file specification fields. They are used to define the specific network address and path name in the Project Control Database where the system sends reports with the following file extensions: .err - files generated by Envelope Verification .int - files generated by Interference Checker .mgr - files generated by Approval Manager > Create Unapproved Clash Report If this option is not used, the system puts the reports in the directory where the Interference Checker/Manager was initiated.
Field Descriptions
Node Name Key in or accept the network displayed address where the Interference Management reports are sent. File Path Key in or accept the path name where the reports are placed.
238
_ _______________
9. Scheduled Envelope Builder and Clash Detection
The Scheduled Envelope Build/Clash Detection option is used to specify a periodic schedule for running the Envelope Builder and Interference Checker.
Scheduled Envelope Builder and Clash Detection
Before Using This Command

To write schedule data to a hard disk location, confirm the directory path exists and that you have permission to write files to the directory. When running on the Windows NT operating system, Scheduled Envelope Build/Clash Detection uses the at utility in conjunction with the Schedule Service. For the at utility to be available, the schedule service must be running. It is suggested that this service be set to start automatically. To do this, select Services from the Control Panel program group. You must be an administrator (or have administrative privileges) to submit a job to the at scheduler. This is a Windows NT restriction, not a PDS restriction.
9. Scheduled Envelope Build / Clash Detection
Select Schedule from the list of services, and click Startup to define the startup option. (Select Task Scheduler on Windows 2000.)
239
_ _______________
Set the Startup Type to Automatic. Click OK on the Service dialog box, and click Start on the dialog box to start the schedule service if it is not already running. The logon user (system account or "this account") will impact how you set the account mapping in NT Batch Manager. For additional information, see the System Administrator Responsibilities section of the PDS Project Setup Technical Reference (DEA5067). For Windows 2000, the Task Scheduler service must be run as the system account. If you want scheduled jobs to run as a specific user account you should set the AT Service Account. Open Task Scheduler. On the Advanced menu, click AT Service Account. Click This Account, and then type the user account that will run tasks that are scheduled by using the at command. In the Password and Confirm Password fields, type the correct password for the account.
Scheduled Envelope Build/Clash Detection does not perform a build/detection at the time it is created. Instead, command files are created to alert the system to perform a build/detection at a specified time of day. The command files are launched by the system scheduler utility (at on Windows NT).
240
_ _______________
Scheduled Envelope Builder and Clash Detection
Operating Sequence
1. Select Option. Select Scheduled Envelope Build/Clash Detect from the Interference Management form. The Scheduled Build Envelope/Clash Detection form is displayed. 2. Select the required option. Create Creates a scheduled envelope/clash batch job. See page 242. Revise Revises an existing envelope/clash batch job. See page 242. Delete Deletes a scheduled envelope/clash batch job. See page 245. Review Schedule Reviews previously defined envelope/clash schedules. See page 247.
241
_ _______________
9.1
Create/Revise Envelope Builder/Clash Detection Schedule

These options are used to create or revise a schedule for running the Envelope Builder and Interference Checker on a periodic basis. You can establish multiple scheduled jobs for each project. This operation is the same as running Interference Checker with the toggle set to Generate and Verify Envelopes. At the scheduled time, Envelope generation is run for all the models defined by the area/volume. If there are no errors in envelope generation the clash check is processed for the area/volume.
Field Descriptions
Shell Script The Shell Script field is filled in automatically using the convention envclash_<archival_index_no>. Number Type up to 24 alphanumeric characters for the name of the envelope build/interference check schedule. Description Type up to 40 alphanumeric characters for the description of the envelope build/interference check schedule. File Specification and Path Type the file name and directory path for the Envelope Builder/Interference Checker Data file. This file defines the time of day for the build and check, the frequency of the build and check, and the settings for the interference check.
242
_ _______________
Create/Revise Envelope Builder/Clash Detection Schedule
Operating Sequence
1. Select Option. Select the Create or Revise option from the Scheduled Build Envelope/Clash Detection form. For the Revise option, a list of all scheduled build/check batch jobs for the active project is displayed.
2.
Select Schedule. Select the schedule to be revised; then choose the Confirm button. The Scheduled Build Envelope/Clash Detection Creation/Revision form is displayed showing the information about the selected scheduled build/check batch job.
3.
Specify Envelope/Clash Data. Type the following information to define an Envelope Builder/Interference Checker schedule for the active project. Number Description File Specification Path
243
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 4. Accept Information. Choose the Confirm button to accept the specified information. A form is displayed to define the schedule frequency and time. 5. Select Option. Select the frequency of the build/check batch job: Daily, Weekly, or Monthly. A set of fields is displayed to type the day and time.
6.
Select the day of the week/month, and set the time of day (hours and minutes) for the build/check batch job. Then choose the Confirm button. A form is displayed to define the Interference Checker options.
7.
Select Option. Select the appropriate Interference Checker options. Refer to Interference Checking, page 89 for information on these options.
8.
Choose the Confirm button. A set of Envelope Builder/Interference Checker Command files is created. The file specification for the script is formed automatically as follows: envclash_<archival_index_no> If the time of the scheduled archive is changed, a new at entry is created and the old entry must be deleted.
244
_ _______________
9.1.1 Delete Envelope Builder/Clash Detection Schedule
The Delete option deletes an existing Envelope Builder/Clash Detection schedule file.
Delete Envelope Builder/Clash Detection Schedule
Operating Sequence
1. Select Option.
Select the Delete option from the Scheduled Envelope Builder/Clash Detection form. A list of build/check schedules for the active project is displayed. 2. Select Envelope/Clash Schedule File. Select the build/check schedule to be deleted; then choose the Confirm button. 3. Accept to Delete Envelope/Clash Data. Choose the Confirm button to delete the selected schedule. A warning is displayed with instructions to delete the schedule.
245
_ _______________
246
_ _______________
9.1.2 Review Schedule
The Review Schedule option lists all scheduled envelope/clash jobs for the active project and displays the following basic data. archival number frequency of build/check time of day for build/check network address for build/check
Review Schedule
Operating Sequence
1. Select Option. Select the Review Schedule option from the Scheduled Build Envelope/Clash Detection form. The Review Envelope Build/Clash Detection Schedule form is displayed. 2. Cancel Review Schedule. Choose the Cancel button to display the Scheduled Build Envelope/Clash Detection form.
247
_ _______________
248
_ _______________
Appendix A:
Troubleshooting PD Clash
Appendix A Troubleshooting PD Clash

This section provides information on troubleshooting PD Clash, including the following: A.1 A.2 A.3 Message Files Tips Questions & Answers
A.Troubleshooting
249
_ _______________
A.1
Message Files
The PDS 3D products share common message files contained in the win32app\ingr\pdshell\msg directory. pdsmc.msg - command field messages pdsme.msg - error and warning messages pdsmp.msg - prompts and messages pdsms.msg - status messages.
250
_ _______________
Appendix A:
Envelope Verification Error Messages
A.1.1
Envelope Verification Error Messages

When running envelope file verification, you might encounter one or more of the following error messages. ERROR - component # range not within design range Reason: There is an invalid component with a range from -2147483648 to 2147483647 (which is the entire design volume). Recovery: Look for this component in the .evd file and delete it. Then go into MicroStation and fence rotate the model by 0 degrees or find the offending element and correct it. ERROR - duplicate linkages Reason: There are components with duplicate linkages. Recovery: Go into the design file and run diagnostics. ERROR - shape # range not within component # range Reason: There is an invalid shape with range outside of component valid range. Recovery: Look for this component in the envelope file and delete it. Go into MicroStation and fence rotate the model by 0 degrees. ERROR - Unable to open XXX Reason: The system cannot find the file or cannot read the file. Recovery: Make sure the system where the file resides is turned on and the file has read permissions. WARNING - component # has disjoint shapes Reason: A component has been placed, but the shapes are not connected. Recovery: This can be OK, but check your file to make sure this is what you intended. WARNING - envelope file is empty Reason: The design file is empty or there is a problem with the design file. Recovery: Check the log file and any errors and check the model file for problems.
A.Troubleshooting
251
_ _______________
A.2
Tips on Using PD Clash
Markers
Situation
Sometimes, when a clash is detected, the offending item is moved, and interference detection is rerun, the area index numbers get reset to 0 in the project database.
Resolution
There are only three things that can set an interference marker to 0: One of the models involved in the clash has been reassociated with a different area, or The volume coordinates for the predefined volume get redefined so that the clash (from the first run) that used to reside within the original volume now lies outside the newly defined volume. In both of these cases, the clash will be picked up on the next run, on the area within which the clash lies. It will have the same marker number, and all clash history will be intact. The other way marker numbers can be set to 0 is if an envelope file that existed on a previous run does not exist on subsequent runs or if the file is corrupted. For example, a .env file is manually deleted and does not get clash checked on a rerun. If the clash has been previously reported, its area_index_no will be set to 0 until the next run where the .env file is left to be checked and updated.
Envelope Verification Dates

Envelope verification shows you at what times the model (on your workstation) and envelope (on the server) files were created. To ensure that the dates are correct, be sure the time clocks are set to the same time in both places.
Approval Manager > Enter Dynamics Mode

With Reference Models Toggle
When you are checking clashes in the dynamic mode, be sure and toggle With Reference Models/Without Reference Models to with. With Reference Models must be turned on in order to get the true dynamic clash display. Otherwise, the display looks as though nothing is happening.
252
_ _______________
Appendix A:
Tips on Using PD Clash
With the Select View Option

When dynamically reviewing clashes, be sure that Review Clash is checked in order to see the true dynamic clash display. If Window to Clash is used instead, the display window is collapsed around the clash, altering the view depth. You will not be able to see all of the clash because it exceeds the windows view depth.
Structural Database Records

ModelDraft and FrameWorks Plus
There are two records in the database: one for the actual model and one for the propagated model. The Model Status Type for the .dgn file should be set at 1. For the propagated model in ModelDraft, and for the frozen views in FrameWorks, the Model Status Type should be set at 2.
Placing Spheres
Situation
Spheres placed with the Microstation Place Sphere command will generate invalid envelopes. The generated envelopes are flat disks instead of spheres. The affected envelope builders include the generic envelope builder used for non-PDS models and any other PDS envelope builder which creates envelopes for spheres placed with the Microstation Place Sphere command.
Resolution
A surface of revolution with a 180 degree arc creates a spherical envelope.
A.Troubleshooting
253
_ _______________
A.3
Questions & Answers
Changing title block units

How can I change the title block on the drawing border?
You have very few options on the border file. You may make a few changes, such as, changing the name in the title block, changing the size of the font, adding a logo, and so forth. But you cannot change the size of the title block, rearrange the border, or anything like that. Hands off! Changing the units changes the units for the entire .dgn file and may cause plots to be the wrong size for the plotter paper.
254
_ _______________
Appendix B:
Interference Tables
Appendix B Interference Tables

This section provides database information for easy reference during the Interferences course. It includes information on how interference checking affects and is affected by various tables, and it includes tables from the Project Control Database and the Material Reference Database. The following tables are from the Project Control Database and the Material Reference Database, which are delivered in \win32app\ingr\pdshell\ddl.
Project Control Database

Do not revise the following database definition other than to change column names.
# Project Control Data
table number = 103 , number of columns = 29 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, product_version_no report_path report_node report_format_path report_format_node report_filter_path report_filter_node piping_eden_path piping_eden_node eden_table_path eden_table_node piping_spec_path piping_spec_node assembly_path assembly_node model_builder_path model_builder_node design_review_path design_review_node std_note_lib_path std_note_lib_node eqp_eden_path eqp_eden_node tdf_table_path tdf_table_node clash_report_path clash_report_node clash_plot_path clash_plot_node , , , , , , , , , , , , , , , , , , , , , , , , , , , , , short character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26)
B. Tables
255
_ _______________
# Engineering Discipline Data table number = 111 , number of columns = 5 1 2 3 4 5 , , , , , discipline_indx_no discipline_name intra_disc_ifc_flg discipline_mtrx_a discipline_mtrx_b , , , , , short character(20) short integer integer
# Design Area Data table number = 112 , number of columns = 15 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, discipline_indx_no area_index_no area_name area_description volume_low_x volume_low_y volume_low_z volume_high_x volume_high_y volume_high_z interference_mode area_lock_owner area_lock_status area_lock_date clash_rpt_index_no , , , , , , , , , , , , , , , short short character(10) character(40) integer integer integer integer integer integer short character(10) short integer integer
# Model Data table number = 113 , number of columns = 17 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, 17, model_index_no discipline_indx_no area_index_no partition_no model_no model_description model_file_spec path_name network_address lock_owner lock_status lock_date verification_date revision_date responsible_disc model_type model_status , , , , , , , , , , , , , , , , , integer short short short character(10) character(40) character(14) character(36) character(26) character(10) short integer integer integer short short short , index 1
, standard note 1605
256
_ _______________
Appendix B:
###################################################
Interference Tables
Job Data (PDtable_131) One record is created per clash run (unique_sequence_no). This table tracks discipline, area, and other data. The env_creation_date is not currently used. Presently there is no difference between unique_sequence_no and system_unique_no, although there may be in the future.
################################################### # Interference Management Data # Clash Management Data table number = 131, number of columns = 7 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, system_unique_no discipline_indx_no area_index_no unique_sequence_no completion_date control_user_no env_creation_date clash_check_option volume_filter_opt volume_low_x volume_low_y volume_low_z volume_high_x volume_high_y volume_high_z , , , , , , , , , , , , , , , integer short short integer integer short integer short short integer integer integer integer integer interger , index 1
, standard note 1208 , standard note 1209
###################################################
Clash Data per Project (PDtable_132) One record is created per clash per project (unique_clash_id). A unique clash number is generated, which is never deleted or reused. Tracks current status of clash with the: clash type, plot date, review date, approved/unapproved, etc.
################################################### # Clash Data Per Project table number = 132, number of columns = 16 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, unique_clash_id if_approval_status comp_a_unique_id comp_b_unique_id model_index_no_a model_index_no_b discipline_index_a discipline_index_b recent_clash_type recent_plot_date recent_review_date recent_sequence_no area_index_no action_discipline recent_seq_no_b area_index_no_b , , , , , , , , , , , , , , , , integer short integer integer integer integer short short short integer integer integer short short integer short , index 1 , standard note 1203
, standard note 1204 , index 2
B. Tables
257
_ _______________
###################################################
Clash Data per Job (PDtable_133) A new record is created each time a run is made, and it points to unique_clash_id entry in PDtable_132. For example, when a clash is found during a run, a record is written to this table. Each time the same clash is found in subsequent runs, an additional record is written to the table. The recent_sequence_no points to unique_sequence_no in PDtable_131 generated for that clash run. Clash type and volume ranges of clashing components are tracked.
################################################### # Clash Data Per Job table number = 133, number of columns = 16 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, system_unique_no unique_clash_id unique_sequence_no clash_type comp_a_range_x_lo comp_a_range_y_lo comp_a_range_z_lo comp_a_range_x_hi comp_a_range_y_hi comp_a_range_z_hi comp_b_range_x_lo comp_b_range_y_lo comp_b_range_z_lo comp_b_range_x_hi comp_b_range_y_hi comp_b_range_z_hi , , , , , , , , , , , , , , , , integer integer integer short integer integer integer integer integer integer integer integer integer integer integer integer , , , , index 1 index 2 index 3 standard note 1204
, index 4
###################################################
Component Clash Data per Project (PDtable_134) One record is created per project per clashing model item. It is never reused or deleted. Multiple clashes experienced by a single component are tracked. Therefore, if a component clashes with 6 different items, only one entry appears in PDtable_134, and all other clashes are indexed to this entry.
################################################### # Component Clash Data Per Project table number = 134, number of columns = 7 1 2 3 4 5 6 7 , , , , , , , unique_comp_id comp_table_number comp_row_number model_index_no primary_descript secondary_descript comp_model_status , , , , , , , integer short integer integer character(20) character(40) short , index 1
258
_ _______________
Appendix B:
###################################################
Interference Tables
Clash Review History Information (PDtable_135) One record is created per clash when it is reviewed after a run. Each time this clash is reviewed by the Interference Manager, the record in PDtable_135 is updated. If the same clash is present on the next run, a new record is created in Table 135 with the same unique_clash_id. If a clash is never reviewed in the Interference Manager, a record for that clash will not be created in PDtable_ 135.
################################################### # Clash Review History Information table number = 135, number of columns = 8 1 2 3 4 5 6 7 8 , , , , , , , , system_unique_no unique_clash_id review_date review_user_no responsib_user_no action review_comment approval_method , , , , , , , , integer integer integer short short short character(100) short , index 1
###################################################
Clash Plot History Information (PDtable_136) One record is created per clash plot.
################################################### # Clash Plot History Information table number = 136, number of columns = 4 1 2 3 4 , , , , system_unique_no unique_clash_id plot_date plot_user_no , , , , integer integer integer short , index 1
###################################################
Material Reference Database

Do not revise the following database definition other than to change column names.
B. Tables
259
_ _______________
###################################################
Component Insulation Exclusion Data (PDtable_231) This table allows you to completely or partially exclude the insulation of components that are on insulated lines, during interference checking. If this table is not loaded, the insulation thickness is completely included in the components interference envelope.
################################################### # Component Insulation Exclusion Data table number = 231, number of columns = 13 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, system_unique_no commodity_name model_code gcp_npd_from gcp_npd_to rcp_npd_from rcp_npd_to heat_tracing_from heat_tracing_to insul_purpose_from insul_purpose_to nor_oper_temp_from nor_oper_temp_to , , , , , , , , , , , , , integer character(6) character(6) short short short short short short short short double double
, , , ,
standard standard standard standard
note note note note
200 200 220 220
###################################################
Flange Insulation Exclusion Data (PD_table 232) This to define the applicable insulation thickness to be added to the flange outside diameter of the bolted end of that components interference envelope. If this table is not loaded, the insulation thickness is completely included in the components interference envelope.
################################################### # Flange Insulation Exclusion Data table number = 232, number of columns = 9 1 2 3 4 5 6 7 8 9 , , , , , , , , , system_unique_no bolted_npd_from bolted_npd_to heat_tracing_from heat_tracing_to insul_purpose_from insul_purpose_to nor_oper_temp_from nor_oper_temp_to , , , , , , , , , integer short short short short short short double double
, , , ,
note note note note
200 200 220 220
260
_ _______________
Glossary
absolute path name The sequence of directories, beginning with the root directory (/) that locates a file. See also path name and relative path name. The plane in a 3-D design upon which you can place elements and perform manipulations. The process which is displayed in the Process ID field; it controls the message fields, the menus, and the keyboard. The active process has a highlighted window icon strip. Software designed to meet specific needs, unlike system software which runs other software. A method of processing data which collects a series of operations into a group (or batch) and executes the group in a continuous stream without user intervention. A queue, or channel for moving requests, created through NQS. A batch queue handles scheduling for processes submitted through the Batch options screen menu. A point on a pipeline which separates piping segments so that they can be assigned different segment parameters. A branch point allows for placement of branch components. The button located in the upper right corner of a form containing a red X or the word cancel. Select the cancel button to exit the form or option. A permanent association of elements that can be stored and placed as a group, and then manipulated as individual elements. A column data type that stores alphanumeric character data.
Glossary
Glossary
active depth
active process
application software
batch processing
batch queue
branch point
cancel button
cell
character client
In network operations, a node which accesses data or performs a function on the remote resource (usually a server). All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. An attribute of a database table. A group of columns defines a table in a database. Instructions from the user to perform a function on specified data. A button that appears in the upper right corner of a form and contains a green check mark or the word confirm. Select the confirm button to initiate a specified option.
column
command confirm button
261
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 coordinate coordinate system The location of a point along the X, Y, or Z axis. A geometric relation used to denote the location of points in the design cube. The most common coordinate system is the rectangular coordinate system, whereby points are located by traversing the X, Y, and Z axes of the design cube. Normally, coordinate systems have their origin defined as 0,0,0, though this is not required. Other coordinate systems are used to more easily express the coordinates of specific geometric entities. For example, you can use a spherical coordinate system to help define points on a sphere, and you can use a cylindrical coordinate system to help define points on a cylinder. An ordered set of absolute or relative data values that specify a location in a coordinate system. The image files written by System V for a number of reasons, the most common of which are memory violations, illegal instructions, bus errors, and user-generated quit signals. The pointer that the user moves on the screen to indicate an item or area. The mouse button used to place data points and tentative points, to accept previously selected elements, and to select commands from forms and menus. The field on a screen used to accept user-supplied data. Also known as key-in field. A point placed by pressing the data button on the mouse. Data points select commands from the panel menus and Menu Bar, place elements, identify and accept elements, and activate windows and perform window manipulations. A collection of comprehensive informational files having predetermined structure and organization that can then be communicated, interpreted, or processed by a specific program. The part of the database that is made of rows and columns and contains information about the project and design elements. The predetermined value of a parameter that is automatically supplied by the system or program whenever a value is not specified by the user. To remove, destroy, eliminate, or erase. A separating mark or space; a character or sequence of contiguous characters that mark the end of a string of characters. A nonaddressable component of a network, that is, a component onto which a user cannot log, for example, tape drive, disk drive, and floppy disk.
coordinates
core files
cursor data button
data entry field
data point
database
database table
default
delete delimiter
device
262
_ _______________
directory display-list box A file that contains the names of other files.
Glossary
A small box with horizontal dashes located at the end of a form key-in field. When selected, a list of the data available for that field is displayed. Input can then be selected from the list with a data point instead of keying in the information. The set of acceptable values for a value within a component. Another term for the dynamic function that attaches the cursor to an element so you can see it move. A term used in plane surveying that describes an east, or positive, difference in longitude. An object (project, drawing, element, and so forth.) of interest about which information is stored; a relational database table. See interference envelope. A UNIX path name that tells the system where to locate a file. A user-defined name given to an interactively created file. The name should be relevant to the contents of the file. An interface or screen menu designed with the I/FORMS product. Because many of the screen menus in the application software are built with I/FORMS, you must have the FORMS_S product on your workstation. The name of the entire path or directory hierarchy to a file, including the file name. See also relative path name. A portion of a form, such as a button, a field, or a checklist, that responds to information. Gadgets can display default values or act as data entry areas. The first items of information in a file which precede any actual data. The header contains information on the structure and contents of the file. A classified structure with superiors (roots) and subordinates (dependents) for grouping files or commands. A pictorial representation or image; a symbol that graphically identifies a command. A relational database management system supported by RIS. A relational database management system supported by RIS. An equipment modeling primitive or parametric component that is used in conjunction with or instead of model graphics for interference checking. Interference envelopes are given different levels and display symbology to distinguish them from primitives.
Glossary
domain dragging
easting
entity
envelope file file specification filename
form
full path name
gadget
header
hierarchy
icon
Informix Ingres interference envelope
263
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 invert elevation isometric The lowest point on the internal diameter of the pipe. Relating to or being a drafting system characterized by three equal axes at right angles; a view in which the horizontal lines of an element are drawn at an angle to the horizontal and all verticals are projected at an angle from the base. An attribute (column) in a table which is chosen as the access vehicle to individual rows of the table. The field on a screen used to accept user-supplied data. Also known as a data entry field. A point on an element, including vertices, to which you can snap. A word recognized by the software that provides access to a certain function. The strip at the top of the screen that contains icons for selecting commands. The area that appears in the MicroStation Command Window when you are working in a design file. It is divided into the Command Status field, the Current Command field, the Prompt field, and the Key-in field. A graphic representation or schema. An interconnection of host computers and workstations that enables them to share data and control. The term network can mean the devices that connect the system, or it can mean the connected system. Network File System, the system that provides access to data that is distributed among machines through an interconnection of host computers and workstations. NFS allows you to mount a remote resource to your local workstation so you can access the data as though it were local. NFS is usually used to access centralized data on a server. Any addressable device (such as a workstation or a server) that is connected to a network. The network enables the connected nodes to share data and system control. The hard-wired Ethernet address assigned to each node when it is manufactured. It is necessary for each node to identify and communicate with another node in the network. A name, or alias, that can be assigned to the node address of a device on a network. A term used to describe a north coordinate location in the plant coordinate system.
key
key-in field
keypoint keyword
menubar
message area
model network
NFS
node
node address
node name
northing
264
_ _______________
nozzle A special equipment modeling primitive that contains the connection point to piping. This point does NOT include a gasket allowance, but rather represents the face-of-flange coordinate. NQS Network Queuing System, the software package that allows you to define network-wide batch and device queues. Use of NQS involves setting up local resource queues on the system(s) where the resources reside and setting up pipe queues on the systems that are to have access to the resources. A relational database management system supported by RIS. In coordinate geometry, the point where the x, y, and z-axes intersect. The point at which the coordinate system is placed. A view which is a projection of the model onto a plane along lines which are orthogonal to the plane. A property whose value determines the characteristics or behavior of something.
Glossary
Glossary
Oracle origin origin point orthogonal view
parameter
path
A sequence of directories leading to a file or a sequence of menus leading to a command. The sequence of directories leading to a file. See also absolute path name and relative path name. Plant Design System A controlled channel for moving requests to batch or device queues on remote systems and for receiving status and/or data in response. To identify a specific element, or indicate a specific point in the design file. A spatial element in geometry that may or may not have a boundary, but is level, having no elevations or depressions, and is three-dimensional. Reference Database. A collection of reference data containing information relative to industry design codes, vendors catalog data, job specifications, commodity libraries, graphics symbology, label descriptions, report formats and other information of a similar manner. The sequence of directories leading from the current directory to a particular file. See also path name and absolute path name. To turn; to change the angular orientation; to transform by revolution about a specific axis.
path name
PDS pipe queue
place data point plane
RDB reference database
relative path name
rotate
265
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 row A unit of related information in a table. One collection of column values for a table. The animation dynamic that enables you to specify the position of a data point while the element changes as you move the cursor. A description of the overall structure of the rulebase or database. A file that outlines the overall logical structure of a rule base or a database. In network operations, the node which maintains common data or performs a common task needed by clients. All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. Language developed by IBM for creating, modifying, and querying relational databases. The symbology of an element such as continuous dashes, dash-dot, solid, and so forth. The skin of a three-dimensional geometric element. The display style of an element, including color, style, and weight. A collection of data for quick reference, either stored in sequential locations in memory or printed as an array of rows and columns of data items of the same type. To switch; to change between two alternatives. A name that provides access to an account on the system. Data, either entered by the user or determined by the software, that are stored in an attribute. A quantity that may assume any one of a set of values. A quantity possessing both magnitude and direction, generally represented as a line. Vectors can be manipulated geometrically and are represented as a coordinate triple (x,y,z). The defined area of vision on a screen. A view allows you to see a prescribed volume of the design cube. Views are created with their own x, y, and z axes. The x,y plane of the view is parallel to the screen, while the z-axis can be thought of as coming straight out of the view towards you. The view axes maintain this relationship regardless of the rotation with respect to the design cube. See also active depth. External memory for a computer that can be used as if it were an extension of the computers internal memory. The software uses virtual memory to store data. This means that unneeded files and data, stay on the disk until they are called for. Because the internal processing memory stores a minimal amount of data, the software can perform processing more quickly. rubberbanding schema schema file server
Structured Query Language SQL style
surface symbology table
toggle user name values
variable vector
view
virtual memory
266
_ _______________
working directory The directory from which you are accessing files.
Glossary
Glossary
267
_ _______________
268
_ _______________
Index
A action discipline 116 active project 209, 211, 217 align view 163 analyze 176 data piping clash check 108, 184 review 181 application considerations 67 type 92 Approval form 232 approval manager approve 115 approve from list 119 checker reference data 127 checker run dates 121 create unapproved clash report 124 plot clashes 170 review clash history 122 approve 115 from list 119 graphics environment 114 approving reports 232 area window 137 B basic interference checklist 31 batch envelope builder 239 interference checker 239 interference checking 25 bottom-to-top 133 button assignments 179 C camera 134 lens 157 off 157 position 157 setup 156 target 157 view 156 cascade 133 center window 137 checker reference data 127 run dates 121 checklist basic interference 31 clash categories 33 category considerations 91 checker PD_Design 108 discipline 75 history review 122 management setup 45 ownership 45 dual 45 plot management 196 plotting 98 precedence 33 clash check 184 schedule 239 color shading 153 colors 177 component insulation exclusion data 61 compress design 168 constant shading 154 construct point 141 construction tolerance exclusion data 62 tolerances for equipment envelopes 42 construction clash category 33 copy 134 report discrimination data 217 view 163 create envelope builder schedule 242 interference checker schedule 242 unapproved clash report 124 cross-section 154
Index
Index
269
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 D default plot 98 report active 96 defining pipe-like components 63 delete envelope builder schedule 245 interference checker schedule 245 design area 21, 73 pre-defined volume 21 predefined volume 74 understanding 20 design area ownership 41, 209, 211, 217 design area ownership 43 dialog view rotation 152, 166 discipline 116 clash 75 extent 209, 217 matrix 47 discipline matrix 52 display depth set for review commands 162 distance and direction 143 dual design area ownership 41, 43 dual ownership of clashes 45 E east elevation 165 element commands 176 enter dynamics 117, 118 envelope 59 builder 23, 60 design area 73 predefined volume 74 model 76 piping design area predefined volume 72 piping design area 70 project 69 schedule 239 create 242 delete 245 review 247 revise 242 diagnostics 24, 85, 117, 118 verification 81 envelope (continued) verifications 24 envelopes 23 equipment insulation 42 error messages 250 error messages 251 exclusion by discipline 47 exclusion tables 61, 90 exit 168, 169, 175 F false clashes 85, 91, 116, 181 FAQs 249 file 168 commands 168, 169 design 169, 175 envelope 60 marker 252 user-defined envelope 77 filled hidden line 154 fit 137 flange insulation exclusion data 62 fonts 177 forms left/right screen 161 G geographic extent 209, 211, 217 grid on/off 164 H hard clash category 33 help 179 hidden line 154 highlight clash 117 I IFCMGR enter dynamics 118 envelope diagnostics 118 select view 118 input 26 insulation 42 exclusion data 61, 62 interference approval manager 30, 112, 114
270
_ _______________
interference (continued) checker 89, 90 design area 21 pre-defined volume 21 input 26 output 26, 105 PDS interference report 26 PD_Design 108 piping design area 21 pre-defined volume 21 plot clashes 98, 190 project 20 schedule 239 create 242 delete 245 review 247 revise 242 checker data 41 commands 39 detection 19 exclusion by discipline 47 introduction 19 management clash categories 33 data 180 interference checker input 26 output 26 managing 111 markers 27 matrix 52 commands 51 modifying 50 process 49 reviewing 50 understanding 49 why define 47 model status ranges 42 plot management data 196 plot manager 190 plotting 189 report management data 238 reporting 197 understanding 30 understanding 19 units 18 interference check 184 interference search criteria 210, 212, 217 intra discipline interference check 47, 51 introduction 18 interference checker summary 18 management clash categories 33 project organization 18 setup 35 iso view 165 isometric view 147 item window in 137 K key-in marker number 117 L lens 157 level symbology off 160, 164 on 159, 164 levels 135 looking east 147 north 147 south 147 west 147 M magnify 137 markers 252 match planar element 150, 166 matrix 47, 52 measure distance 114 model 76 files 36 status 60 modify interference matrix 50 move and center view 137, 139 down 163 left 164 right 164 up 163 window 139
Index
Index
271
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 N next 134 no intra discipline interference check 51 non-PDS models 77 north elevation 165 O open close 133 output 26 interference checker 105 ownership 41 design area 43 of clashes 45 P PDS review clash 186 PDS interference report 26 PDtable_135 96 PDtable_231 61 PDtable_232 62 PDtable_233 62 permanent color shading 153 phong shading 155 piping clash check 108, 184 review 181 construction tolerance exclusion data 62 design area 70 predefined volume 72 plan view 147, 165 planar element match 150 plot 196 active clash 116 clashes 98, 169, 170, 190 discipline extent 209, 217 geographic extent 209, 211, 217 management data interference 196 plots default 98 plotting understanding 30 precedence clash 33 precision input construct point 141 precision input (continued) distance and direction 143 previous 134 print 168 processing interference checker distribution 37 project 20, 69 organization 18 search criteria 212 date 215 time 215 setup 35 project.ddl 255 Q questions 249 queue redirected processing examples 37 queues 37 R real clash 116, 181 redirected processing 37 queues 37 redistribution functions workstation classifications 37 reference models, with/without 117 refresh views 137 render 135 options 153 rendering 178 report clash report management data 238 discrimination data copy 217 revise 217 unapproved clash report 124 reporting 197 design area ownership 209, 211, 217 reports PDS interference report 26 restore view 117 review clash history 122 envelope builder schedule 247 interference checker schedule 247 interference matrix 50
272
_ _______________
review (continued) PDS clash 186 revise envelope builder schedule 242 interference checker schedule 242 report discrimination data 217 rotate 3 points 151 about view (x,y,z) 149 view about x axis 165 about y axis 165 about z axis 165 absolute 165 by 3 points 165 element 165 relative 165 rotation 136 S schedule envelope builder 239 interference checker 239 select view 116, 118 select by models 210, 211, 217 set active depth 167 absolute 167 relative 167 display depth 167 absolute 167 relative 167 view orientation 147 set display depth 162 settings commands 177 setup 35 shading color 153 show active depth 167 display depth 167 single design area ownership 41, 43 smooth shading 155 soft clash category 33 south elevation 165 stereo 155 swap 134 T table insulation exclusion data component 61 flange 62 piping construction tolerance exclusion 62 tables 255 exclusion 61 tile 133 tips on PD Clash 249 tips on using PD Clash 252 tools review PDS clash 186 troubleshooting 249 typefaces 13 U understanding design areas 20 interference approving 30 checking 25 envelopes 23 plotting 30 reporting 30 interferences 19 volumes 20 update 134 all 163 left 163 right 163 view 163 window 148 user commands 179 defined envelope files 77 defined interference reports 96 preferences 179 utilities review PDS clash 186 V view commands 133 depth 167 manipulations 158 more 163 off 163 on 163 rotation 152, 166 toggle 163
Index
Index
273
_ _______________
PDS Interference Checker/Manager Users Guide - April 2002 view (continued) update 148 viewing options 145 viewing direction 165 viewing options 137, 145 camera view 156 color shading 153 dialog view rotation 152 form screen 161 match planar element 150 rotate about view 149 rotation 3 points 151 set view orientation 147 update window 148 views 158 volume filter 22, 95 window 145 volumes understanding 20 W weight display toggle 164 west elevation 165 window area 137 center 137 move 139 named item 137 origin 137 update 148 volume 137, 145 wiremesh 154 with/without reference models 117 Z zoom in 137 out 137
274

Users Guide Addendum
February 2003
DPDS3-PB-200006B
For PDS version 07.02.00.** This document supplements DPDS3-PB-200006A.
PDS Interference Checker/Manager Users Guide Addendum February 2003
Table of Contents
Clash Categories (replaces 2.8)................................................................................ 277 Exclusion of Interferences By Discipline (replaces 3.1.2)....................................... 279 PDS Clash Detection with Non-PDS Models (replaces 4.2) ................................... 287 Interference Tables (replaces Appendix B) ............................................................. 291
276
Clash Categories (replaces 2.8)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 3334 in the PDS 7.1 version of the document). The following information has been added: Clash subtypes See the following text for details.
The Interference Approval Manager and the reports created by the Interference Checker distinguish among three main categories of interference clashes: Hard A clash between actual physical components, equipment, or structures. Soft A clash between nonphysical space envelopes, for example, insulation, maintenance accessways, or safety envelopes. Construction A clash or discrepancy between the user-defined distance and the actual distance of two components in specified disciplines defined using PD_Project. For instance, if piping components are required to be at least 1" away from all structural components but one is found closer, a Construction clash is reported. In addition to these categories, clash plotting and reporting display various clash subtypes according to the particular disciplines and envelope types involved, such as Fireproofing versus Insulation or Hard versus Soft Operating.
Clash Precedence
The precedence for reporting clashes is Hard, Soft, and Construction. This results in interference clashes being reported in one of the following categories. The report will contain only the category of clashes with the highest precedence in accordance with the following precedence table: Hard - Hard Hard - Soft Hard - Construction Soft - Soft Soft - Construction Construction - Construction. Note: The clash subtypes used in clash plotting and reporting do not affect the clash precedence listed here. For example, a clash of subtype Fireproof-Insulation would still be considered a Hard-Soft clash when determining precedence.
277
Hard - Hard Example

The following example contains clashes between actual physical components. It would be categorized as a Hard - Hard clash.
Hard - Soft Example

The following example displays a clash between an actual component and space that has been allocated for maintenance accessways. It would be categorized as a Hard - Soft clash.
278
Exclusion of Interferences By Discipline (replaces 3.1.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 4753 in the PDS 7.1 version of the document). The following information has been added: Added Clash discipline information to Discipline Matrix Interference Check option See the following text for details.
This command allows you to define a matrix of discipline combinations for each discipline for envelope-building and interference-detection purposes. If you do not define a matrix for a specific discipline, you can specify whether intra-disciplinary interference detection is turned on for each discipline. You must select one of the three options for each Active Discipline that you define. Note: It is important to remember that all clashes found between all disciplines during an interference checker run, are owned only by the first design area that finds it unless dual-design area ownership has been specified. The default mode is that no discipline matrix is defined and that the Intra Discipline Interference Check command is enabled.
Why Define a Matrix?

Frequently, designers are specifically interested in potential clashes involving models of their own discipline with models from one or more other disciplines. The Discipline Matrix Interference Check command allows designers the flexibility to check only for clashes that fall within the scope of their responsibilities. See the following examples. Caution: It is the responsibility of the people defining the interference matrices to ensure that all possible discipline combinations are considered. An Equipment designer may only be responsible for intra-disciplinary (Equipment against itself) clashes and clashes involving Equipment and Structural models. This designer would need to define intra-disciplinary checking for Equipment (Equipment against itself) and Equipment against Structural within the Equipment matrix.
279
For the Raceway designer, most of the clashes that may be of concern are found between the Structural and Raceway disciplines. The Raceway matrix would limit envelope building and interference detection to only those two disciplines for all Raceway design areas.
A Structural designer only concerned with clashes between and within Structural models would want to specify that only intra-disciplinary checking be performed for all Structural design areas.
280
Caution: It is important not to confuse the function of the Intra Discipline Interference Check command with a matrix that only performs intra-disciplinary checks for a discipline. The Intra Discipline Interference Check command not only checks the specified discipline against itself and each model internally, it checks that discipline against all other disciplines and all disciplines against each other. The Intra Discipline Interference Check command would not be appropriate in this case, since the Structural Designer only wants to find Structural against Structural clashes. A Piping designer may be interested in how Piping is going to affect all disciplines, including Piping. In this case, a Piping matrix that includes all disciplines or the Intra Discipline Interference Check command could be specified for the Piping Discipline.
281
Note: It is important to remember that all clashes found between all disciplines during an interference checker run are owned only by the first design area that finds it unless dual-design area ownership has been specified.
Understanding the Effect of a Matrix

The Discipline Matrix Interference Check command allows you to specify which disciplines are considered for envelope building and interference detection for all design areas within a discipline. In the previous section, Why Define a Matrix?, different discipline-scenarios were presented. To explain how a matrix affects the other interference processes, consider the Equipment matrix. The Equipment designer is only responsible for intra-disciplinary clashes and clashes involving Equipment and Structural models. The matrix would be defined as follows:
282
When a matrix is defined, the system only includes models that belong to the disciplines involved in the matrix for interference checking. The responsible engineering discipline, as defined in the Model Data Table (PDtable_113, column 15) of the Project Control Database, is used to determine which models to include in the envelope-building process. All models defined with the responsible engineering discipline of Equipment or Structural are included.
Once the envelopes have been built, the Interference Checker only checks the combinations of disciplines specified in the matrix. Redundant comparisons are not performed.
Reviewing and Modifying Matrices

To review or modify a matrix for a given discipline, first select a discipline from the Primary Discipline field to define the Active Discipline. Next, select a discipline from the Primary Discipline field. In the Against Discipline field, the system highlights the disciplines that the primary discipline will be checked against. Do this for each of the disciplines in the Primary Discipline field in order to see the entire matrix for the active discipline. You can modify the matrix for any or all disciplines; then click Accept.
283
Commands
Intra Discipline Interference Check Allows you to define that the interferencedetection process for the Active Discipline includes all possible combinations for that discipline: Models within the specified discipline are checked against each other and are checked internally. Models within the specified discipline are checked against models from all other disciplines. All models from all disciplines are checked against each other.
284
Select a discipline from the Primary Discipline field. This discipline becomes the Active Discipline. Select the Intra Discipline Interference Check command, and click Accept. You can continue with this two-step process for as many disciplines as necessary. Note: You should specify a matrix for the disciplines that do not require this sort of checking. Caution: If a matrix is defined after this command has been specified, the system overrides this command and uses the matrix definition. If the command is specified after a matrix has been defined, the system overrides the matrix and uses the command. The engineering discipline, as defined in the Model Data Table (PDtable_113, column 2) of the Project Control Database is used for determining the discipline of a model for this command. No Intra Discipline Interference Check Allows you to define that the interference-detection process for the Active Discipline includes the following: Models within the specified discipline are not checked against each other and are not checked internally. Models within the specified discipline are checked against models from all other disciplines. All models from all disciplines are checked against each other. Select a discipline from the Primary Discipline field. This discipline becomes the Active Discipline. Select the No Intra Discipline Interference Check command, and click Accept. You can continue with this two-step process for as many disciplines as necessary. Note: You should specify a matrix for the disciplines that do not require this sort of checking. Caution: If a matrix is defined after this command has been specified, the system overrides this command and uses the matrix definition. If the command is specified after a matrix has been defined, the system overrides the matrix and uses the command. The engineering discipline, as defined in the Model Data Table (PDtable_113, column 2) of the Project Control Database is used for determining the discipline of a model for this command. Discipline Matrix Interference Check Allows you to define a discipline matrix for each discipline. Select a discipline from the Primary Discipline field to define it as the Active Discipline. Then select a discipline from the Primary Discipline field to begin defining the matrix. From the Against Discipline field, select all of the disciplines to be checked against the discipline that is highlighted in the Primary Discipline field. You can continue with this two-step process as many times as necessary, and click Accept.
285
If the discipline matrix is set for the Clash discipline, select the appropriate modeling disciplines for the Primary and Against Disciplines for the clashes to be reported. For example, to report piping-piping clashes in the Clash discipline, set the Active Discipline to Clash, the Primary Discipline to Piping, and the Against Discipline to Piping. The responsible engineering discipline, as defined in the Model Data Table (PDtable_113, column 15) of the Project Control Database is used for determining the discipline of a model for this command. If prompted to... Accept or Select Other Option Do this: Select one of the options to enable or disable intra discipline checking and click Accept or select the matrix option. Select a discipline to be the Active Discipline. Select all of the secondary disciplines to include in the matrix, and click Accept.
Select Discipline Accept Or Select Another Discipline
Note: Once you have selected the Active Discipline, you cannot change it until you reactivate the Exclusion of Interferences by discipline command.
286
PDS Clash Detection with Non-PDS Models (replaces 4.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 7780 in the PDS 7.1 version of the document). The following information has been added: SmartSolids and Bsplines in Types of Elements section See the following text for details.
PD_Clash can be used to run interference checks on models that are not created with PDS. In PDS, a project can define up to ten engineering disciplines on which clash detection can be run. Under each discipline, areas, and models within the areas, are created and used for interference checking. These disciplines are, 1. Piping 2. Equipment 3. Structural 4. HVAC 5. Raceway 6. Architectural 7. - 10. User-definable, PLANTGEN or Clash Six of the allowable ten disciplines are predefined by PDS. The other four disciplines are user-definable, that is; you can define up to four additional, non-PDS disciplines that can be used with PDS clash detection. For example, you could have models created with your own, in-house, package; these models can be referred to in PDS models and drawings, for DesignReview sessions, and for clash detection. The models in the four user-definable disciplines need to meet the following guidelines: They must be created outside of PDS, They must be MicroStation-based 3D models, and They must be made part of the PDS project. PLANTGEN can be specified as one or more of the four, user-definable disciplines so that you can check as-built models created with PLANTGEN. Note: One of the four user-defined disciplines can be specified as a Clash discipline, which allows the system to check design areas using the Design Volume Coordinate System. If you need to use the Clash discipline in an existing project
287
that already uses all four user-defined disciplines, you must convert one userdefined discipline to a Clash discipline. Refer to Design Area Predefined Volume, page 74 and the Project Administrator (PD_Project) Reference Guide for more information on the Clash discipline. For the first six predefined disciplines, as well as PLANTGEN, PDS calls specific routines for clash detection based on their data structures and requirements. For the four user-defined disciplines that are not specified as PLANTGEN, PDS uses the generic envelope builder, instead of an envelope builder specifically created for the first six disciplines (piping, equipment, structural, HVAC, raceway, and architectural). This generic envelope builder has some limitations which are discussed later in this section. The following disciplines use specific routines to build envelope files: 1. Piping 2. Equipment 3. Structural 4. HVAC 5. Raceway 6. Architectural 7. PLANTGEN 8. 9. 10. User-defined User-defined User-defined The following disciplines use generic routines to build envelope files:
Creating envelope files in user-defined disciplines

The generic envelope builder creates envelope files for user-defined discipline models within the project or selected area automatically if the Include User Defined Disciplines toggle is set on the Envelope Builder form. You can also select user defined disciplines on the Design Area and Design Area - Pre-defined Volume forms.
288
Types of elements
The generic envelope builder acknowledges only certain MicroStation elements. Shapes (Type 6) inside Surfaces and Solids (Types 18 and 19) Note: If you model a Complex Shape with a Hole, make sure that the Hole element has the HOLE bit set. Otherwise, the envelope may not generate correctly. Complex Shapes (Type 14) inside Surfaces and Solids (Types 18 and 19) Surfaces (noncapped solid) (Type 18) Solids (capped solid) (Type 19) Cones & Cylinders (Type 23) Cells with nested primitives using types 18, 19, and/or 23 Cells containing only Type 6 Shape elements modeled in such a way that the resulting graphic could otherwise be created as a projected solid. In such cases, the system uses the projected solid to create the envelope. One example would be a cell containing 6 shape elements comprising the faces of a cuboid.
In this example, the envelope builder would create an envelope based on the projected hexagonal solid that the cell resembled. Nested cells that can be interpreted as a projected solid (that is, nested cells with only SHAPEs forming a projected solid.) are also processed in this manner.
289
Cells containing only Type 6 Shapes; or Type 6 Shapes, Type 15 Ellipses, and Type 14 Complex Shapes and forming non-projected solids, such as triangular or truncated pyramids. The system creates envelopes for these cells using a projected solid of minimum thickness (20 UORs) for each planar shape. Any nested cells satisfying this condition are also processed. Other element types irrelevant to clashes, such as Types 7, 17, 22, and 33 (Text, TextNode, PointString, and Dimension respectively) are tolerated and ignored. SmartSolids set to display as Surfaces, rather than Wireframes. After performing Change smart solid display with the SURFACES option (instead of wireframe), the resulting cell will have the following types of elements in it: If necessary, some Type 14s (complex shapes) If necessary, some Type 24s and other nested elements (BSPLINE surfaces) Some Type 38s (SmartGeometry). These types of cells are also processed. Bsplines Projected surfaces or solids Revolved surfaces or solids If you have elements other than these, they will not be used during PDS clash detection.
Limitations
For the PDS-supported model types, PDS has access to either database records or MicroStation user data. This allows PDS to track clashes for reporting purposes, associating names with the clashing elements in reports and plots, and for storing the clash approval status of elements (for example, if a clash is deemed acceptable by you). This type of information is not available for user-defined disciplines (exclusive of PLANTGEN). Therefore, the generic envelope builder uses a pseudo-occurrence number for the clashing item. This number is made up of the byte and sector location of the MicroStation element. Also, no name label can be associated with the clashing item in clash reports and clash plots. As a result of using the byte and sector of the item, if the clashing item has its position moved in the MicroStation design file (the byte/sector number position, NOT the physical/geographical location in the model), PDS clash detection does not recognize the previously reported clashing item as the same item. It clears the old clash (since the item at the previous byte/sector position is no longer there or the same), and considers the clash a new one. This repositioning of the MicroStation elements (byte and sector number position) occurs when items are deleted, revised with certain commands, and when the model is compressed. This means that if you approved a clash involving an item in a non-PLANTGEN, userdefined discipline, and the byte/sector number for that item was changed, the clash will be reported again, as a new clash, and you will need to reapprove it.
290
Interference Tables (replaces Appendix B)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 255260 in the PDS 7.1 version of the document). The following information has been added: Updated table listings See the following text for details.
This section provides database information for easy reference during the Interferences course. It includes information on how interference checking affects and is affected by various tables, and it includes tables from the Project Control Database and the Material Reference Database. The following tables are from the Project Control Database and the Material Reference Database, which are delivered in \win32app\ingr\pdshell\ddl.
Project Control Database

Note: Do not revise the following database definition other than to change column names.
# Project Control Data
table number = 103 , number of columns = 41 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, product_version_no report_path report_node report_format_path report_format_node report_filter_path report_filter_node piping_eden_path piping_eden_node eden_table_path eden_table_node piping_spec_path piping_spec_node assembly_path assembly_node model_builder_path model_builder_node design_review_path design_review_node std_note_lib_path std_note_lib_node eqp_eden_path eqp_eden_node tdf_table_path tdf_table_node clash_report_path , , , , , , , , , , , , , , , , , , , , , , , , , , short character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36) character(26) character(36)
291
27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41,
clash_report_node clash_plot_path clash_plot_node mdl_status_low_dr mdl_status_high_dr mdl_status_low_ic mdl_status_high_ic area_owner_opt_ic eqp_insul_opt_ic eqp_con_tol_opt_ic clash_rpt_index_no report_search_path report_search_node sup_tdf_table_path sup_tdf_table_node
, , , , , , , , , , , , , , ,
character(26) character(36) character(26) short short short short short short short integer character(36) character(26) character(36) character(26)
, , , ,
note note note note
1605 1605 1605 1605
# Engineering Discipline Data table number = 111 , number of columns = 5 1 2 3 4 5 , , , , , discipline_indx_no discipline_name intra_disc_ifc_flg discipline_mtrx_a, discipline_mtrx_b, , short , character(20) , short integer integer
# Design Area Data table number = 112 , number of columns = 15 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, discipline_indx_no area_index_no area_name area_description volume_low_x volume_low_y volume_low_z volume_high_x volume_high_y volume_high_z interference_mode area_lock_owner area_lock_status area_lock_date clash_rpt_index_no , , , , , , , , , , , , , , , short short character(10) character(40) integer integer integer integer integer integer short character(10) short integer integer
292
# Model Data table number = 113 , number of columns = 17 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, 17, model_index_no discipline_indx_no area_index_no partition_no model_no model_description model_file_spec path_name network_address lock_owner lock_status lock_date verification_date revision_date responsible_disc model_type model_status , , , , , , , , , , , , , , , , , integer short short short character(10) character(40) character(14) character(36) character(26) character(10) short integer integer integer short short short , index 1
################################################### Job Data (PDtable_131) One record is created per clash run (unique_sequence_no). This table tracks discipline, area, and other data. The env_creation_date is not currently used. Presently there is no difference between unique_sequence_no and system_unique_no, although there may be in the future. ###################################################
# Interference Management Data
# Clash Management Data table number = 131, number of columns = 15 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, system_unique_no discipline_indx_no area_index_no unique_sequence_no completion_date control_user_no env_creation_date clash_check_option volume_filter_opt volume_low_x volume_low_y volume_low_z volume_high_x volume_high_y volume_high_z , , , , , , , , , , , , , , , integer short short integer integer short integer short short integer integer integer integer integer integer , index 1
293
################################################### Clash Data per Project (PDtable_132) One record is created per clash per project (unique_clash_id). A unique clash number is generated, which is never deleted or reused. Tracks current status of clash with the: clash type, plot date, review date, approved/unapproved, etc. ###################################################
# Clash Data Per Project table number = 132, number of columns = 16 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, 14, 15, 16, unique_clash_id if_approval_status comp_a_unique_id comp_b_unique_id model_index_no_a model_index_no_b discipline_index_a discipline_index_b recent_clash_type recent_plot_date recent_review_date recent_sequence_no area_index_no action_discipline recent_seq_no_b area_index_no_b , , , , , , , , , , , , , , , , integer short integer integer integer integer short short short integer integer integer short short integer short , index 1 , standard note 1203
, standard note 1204 , index 2
################################################### Clash Data per Job (PDtable_133) A new record is created each time a run is made, and it points to unique_clash_id entry in PDtable_132. For example, when a clash is found during a run, a record is written to this table. Each time the same clash is found in subsequent runs, an additional record is written to the table. The recent_sequence_no points to unique_sequence_no in PDtable_131 generated for that clash run. Clash type and volume ranges of clashing components are tracked. ###################################################
# Clash Data Per Job table number = 133, number of columns = 17 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, system_unique_no unique_clash_id unique_sequence_no clash_type comp_a_range_x_lo comp_a_range_y_lo comp_a_range_z_lo comp_a_range_x_hi comp_a_range_y_hi comp_a_range_z_hi , , , , , , , , , , integer integer integer short integer integer integer integer integer integer , index 1 , index 2 , standard note 1204
294
11, 12, 13, 14, 15, 16, 17,
comp_b_range_x_lo comp_b_range_y_lo comp_b_range_z_lo comp_b_range_x_hi comp_b_range_y_hi comp_b_range_z_hi env_pair_type
, , , , , , ,
integer integer integer integer integer integer short
################################################### Component Clash Data per Project (PDtable_134) One record is created per project per clashing model item. It is never reused or deleted. Multiple clashes experienced by a single component are tracked. Therefore, if a component clashes with 6 different items, only one entry appears in PDtable_134, and all other clashes are indexed to this entry. ###################################################
# Component Clash Data Per Project table number = 134, number of columns = 7 1 2 3 4 5 6 7 , , , , , , , unique_comp_id comp_table_number comp_row_number model_index_no primary_descript secondary_descript comp_model_status , , , , , , , integer short integer integer character(20) character(40) short , index 1
################################################### Clash Review History Information (PDtable_135) One record is created per clash when it is reviewed after a run. Each time this clash is reviewed by the Interference Manager, the record in PDtable_135 is updated. If the same clash is present on the next run, a new record is created in Table 135 with the same unique_clash_id. If a clash is never reviewed in the Interference Manager, a record for that clash will not be created in PDtable_ 135. ###################################################
# Clash Review History Information table number = 135, number of columns = 8 1 2 3 4 5 6 7 8 , , , , , , , , system_unique_no unique_clash_id review_date review_user_no responsib_user_no action review_comment approval_method , , , , , , , , integer integer integer short short short character(100) short , index 1 , index 2
295
################################################### Clash Plot History Information (PDtable_136) One record is created per clash plot. ###################################################
# Clash Plot History Information table number = 136, number of columns = 4 1 2 3 4 , , , , system_unique_no unique_clash_id plot_date plot_user_no , , , , integer integer integer short , index 1
Material Reference Database

Note: Do not revise the following database definition other than to change column names. ################################################### Component Insulation Exclusion Data (PDtable_231) This table allows you to completely or partially exclude the insulation of components that are on insulated lines, during interference checking. If this table is not loaded, the insulation thickness is completely included in the components interference envelope. ###################################################
# Component Insulation Exclusion Data table number = 231, number of columns = 13 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10, 11, 12, 13, system_unique_no commodity_name model_code gcp_npd_from gcp_npd_to rcp_npd_from rcp_npd_to heat_tracing_from heat_tracing_to insul_purpose_from insul_purpose_to nor_oper_temp_from nor_oper_temp_to , , , , , , , , , , , , , integer character(6) character(6) short short short short short short short short double double
, , , ,
note note note note
200 200 220 220
296
################################################### Flange Insulation Exclusion Data (PD_table 232) This to define the applicable insulation thickness to be added to the flange outside diameter of the bolted end of that components interference envelope. If this table is not loaded, the insulation thickness is completely included in the components interference envelope. ###################################################
# Flange Insulation Exclusion Data table number = 232, number of columns = 9 1 2 3 4 5 6 7 8 9 , , , , , , , , , system_unique_no bolted_npd_from bolted_npd_to heat_tracing_from heat_tracing_to insul_purpose_from insul_purpose_to nor_oper_temp_from nor_oper_temp_to , , , , , , , , , integer short short short short short short double double
, , , ,
note note note note
200 200 220 220
297
Index
clash categories, 277 detection non-PDS models, 287 exclusion by discipline, 279 matrix, 279, 282 modify, 283 review, 283 tables, 291 database tables, 291 exclusion by discipline, 279 interference categories, 277 detection non-PDS models, 287 exclusion by discipline, 279 matrix, 279, 282 modify, 283 review, 283 tables, 291 matrix, 279, 282 modify clash matrix, 283 interference matrix, 283 non-PDS models clash detection, 287 interference detection, 287 review clash matrix, 283 interference matrix, 283
298

Users Guide Addendum
October 2004
DPDS3-PB-200006C
For PDS version 07.03.00.** This document supplements DPDS3-PB-200006B.
PDS Interference Checker/Manager Users Guide Addendum October 2004
Table of Contents
PDS Clash Detection with Non-PDS Models (replaces 4.2)....................................301 Approve (replaces 6.2.1)...........................................................................................306 Envelope Verification Error Messages (replaces A.1.1) ..........................................310
300
PDS Clash Detection with Non-PDS Models (replaces 4.2)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 287290 in the PDS 7.2 version of the document). The following information has been added: Clash Detection with Pelican Forge models See the following text for details.
PD_Clash can be used to run interference checks on models that are not created with PDS. In PDS, a project can define up to ten engineering disciplines on which clash detection can be run. Under each discipline, areas, and models within the areas, are created and used for interference checking. These disciplines are, 1. Piping 2. Equipment 3. Structural 4. HVAC 5. Raceway 6. Architectural 7. - 10. User-definable, PLANTGEN or Clash Six of the allowable ten disciplines are predefined by PDS. The other four disciplines are user-definable, that is; you can define up to four additional, non-PDS disciplines that can be used with PDS clash detection. For example, you could have models created with your own, in-house, package; these models can be referred to in PDS models and drawings, for DesignReview sessions, and for clash detection. The models in the four user-definable disciplines need to meet the following guidelines: They must be created outside of PDS, They must be MicroStation-based 3D models, and They must be made part of the PDS project. PLANTGEN can be specified as one or more of the four, user-definable disciplines so that you can check as-built models created with PLANTGEN. Note: One of the four user-defined disciplines can be specified as a Clash discipline, which allows the system to check design areas using the Design Volume Coordinate System. If you need to use the Clash discipline in an existing project
301
that already uses all four user-defined disciplines, you must convert one userdefined discipline to a Clash discipline. Refer to Design Area Predefined Volume, page 74 and the Project Administrator (PD_Project) Reference Guide for more information on the Clash discipline. For the first six predefined disciplines, as well as PLANTGEN, PDS calls specific routines for clash detection based on their data structures and requirements. For the four user-defined disciplines that are not specified as PLANTGEN, PDS uses the generic envelope builder, instead of an envelope builder specifically created for the first six disciplines (piping, equipment, structural, HVAC, raceway, and architectural). This generic envelope builder has some limitations which are discussed later in this section. The following disciplines use specific routines to build envelope files: 1. Piping 2. Equipment 3. Structural 4. HVAC 5. Raceway 6. Architectural 7. PLANTGEN 8. 9. 10. User-defined User-defined User-defined The following disciplines use generic routines to build envelope files:
Creating envelope files in user-defined disciplines The generic envelope builder creates envelope files for user-defined discipline models within the project or selected area automatically if the Include User Defined Disciplines toggle is set on the Envelope Builder form. You can also select user defined disciplines on the Design Area and Design Area - Pre-defined Volume forms. Types of elements The generic envelope builder acknowledges only certain MicroStation elements. Shapes (Type 6) inside Surfaces and Solids (Types 18 and 19)
302
Note: If you model a Complex Shape with a Hole, make sure that the Hole element has the HOLE bit set. Otherwise, the envelope may not generate correctly. Complex Shapes (Type 14) inside Surfaces and Solids (Types 18 and 19) Surfaces (noncapped solid) (Type 18) Solids (capped solid) (Type 19) Cones & Cylinders (Type 23) Cells with nested primitives using types 18, 19, and/or 23 Cells containing only Type 6 Shape elements modeled in such a way that the resulting graphic could otherwise be created as a projected solid. In such cases, the system uses the projected solid to create the envelope. One example would be a cell containing 6 shape elements comprising the faces of a cuboid.
In this example, the envelope builder would create an envelope based on the projected hexagonal solid that the cell resembled. Nested cells that can be interpreted as a projected solid (that is, nested cells with only SHAPEs forming a projected solid.) are also processed in this manner. Cells containing only Type 6 Shapes; or Type 6 Shapes, Type 15 Ellipses, and Type 14 Complex Shapes and forming non-projected solids, such as triangular or truncated pyramids. The system creates envelopes for these cells using a projected solid of minimum thickness (20 UORs) for each planar shape. Any nested cells satisfying this condition are also processed. Other element types irrelevant to clashes, such as Types
303
7, 17, 22, and 33 (Text, TextNode, PointString, and Dimension respectively) are tolerated and ignored. SmartSolids set to display as Surfaces, rather than Wireframes. After performing Change smart solid display with the SURFACES option (instead of wireframe), the resulting cell will have the following types of elements in it: If necessary, some Type 14s (complex shapes) If necessary, some Type 24s and other nested elements (BSPLINE surfaces) Some Type 38s (SmartGeometry). These types of cells are also processed. Bsplines Projected surfaces or solids Revolved surfaces or solids If you have elements other than these, they will not be used during PDS clash detection. Clash Detection with Pelican Forge Models If you are using Pelican Forge SupportModeler with PDS, you can use envelope files generated in the Pelican Forge software for clash detection, instead of envelope files generated using the generic envelope builder. To do so, you should run the Pelican Forge envelope builder from within the Pelican Forge environment before using PDS to generate the other envelope files for clash detection. Also, when generating envelopes in PDS, you should set the User Defined Disciplines toggle on the Envelope Builder form to Exclude User Defined Disciplines. If you use the generic envelope builder to generate envelope files for the Pelican Forge models, the envelope files will not contain the object descriptions that appear in the files generated by the Pelican Forge envelope builder. To use Pelican Forge envelope files, you must set the enviroment variable PDS_PF_DISCIPLINE to the Pelican Forge discipline number or discipline name from pdtable_111. Please refer to the Project Setup Technical Reference for more information on setting environment variables. Limitations For the PDS-supported model types, PDS has access to either database records or MicroStation user data. This allows PDS to track clashes for reporting purposes, associating names with the clashing elements in reports and plots, and for storing the clash approval status of elements (for example, if a clash is deemed acceptable by you). This type of information is not available for user-defined disciplines (exclusive of PLANTGEN). Therefore, the generic envelope builder uses a pseudo-occurrence number for the clashing item. This number is made up of the byte and sector location of the MicroStation element. Also, no name label can be associated with the clashing item in clash reports and clash plots.
304
As a result of using the byte and sector of the item, if the clashing item has its position moved in the MicroStation design file (the byte/sector number position, NOT the physical/geographical location in the model), PDS clash detection does not recognize the previously reported clashing item as the same item. It clears the old clash (since the item at the previous byte/sector position is no longer there or the same), and considers the clash a new one. This repositioning of the MicroStation elements (byte and sector number position) occurs when items are deleted, revised with certain commands, and when the model is compressed. This means that if you approved a clash involving an item in a non-PLANTGEN, userdefined discipline, and the byte/sector number for that item was changed, the clash will be reported again, as a new clash, and you will need to reapprove it.
305
Approve (replaces 6.2.1)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (pp 115117 in the PDS 7.1 version of the document). The following information has been added: Sort by Model Pair/Sort by Clash ID toggle See the following text for details.
This command activates the Interference Approval Manager form. It is used to edit and review existing clashes, manipulate views, and approve changes to existing clashes.
Note: The Action Discipline toggle is only displayed when clashing models are not from the same discipline.
Field Descriptions
Project Name Displays the name of the active project. Design Area Displays the name of the active design area. Date Displays the date the checker was run. The information in this field is set with the Checker Run Dates option. For more information, see Checker Run Dates, page 121. Responsible User: Displays the code number of the responsible user. This field is filled in if access control is set on the project and will be the userid that was keyed in to access the project through access control. Once the clash is approved, the users initials are written to the Clash Review History data table, PDtable_135.
306
Clash Type Describes the current type of clash. This field is the one above the Review Unapproved/Approved Clash toggle. Marker Number Displays the number of the current clash. Select a marker number with the left and right arrows, select the field and key in a marker number, or select the Keyin Marker Number option and key in a marker number. Model and Area Name Displays the names of the models and corresponding design areas that have components involved in a clash. Item Displays descriptions of the clashing components in the Item fields which are located below the Model fields. The system accesses the user-defined labels in the Label Description Library to create: the primary description, which is displayed on the top line with a limit of 20 characters; and the secondary description, which is displayed on the bottom line and has a limit of 40 characters. These descriptions are defined with the Clash Management Labels option on the Create Label Data form in the Reference Data Manager. Comments: Displays existing comments about the active clash. Select the field, and key in any necessary additional information.
Commands
Sort by Model Pair / Sort by Clash ID Determines the order in which clashes are displayed. Note: If you change this toggle while reviewing clashes, the clash list is reset, and the first clash in the list displays. Review Unapproved Clash Reviews unapproved clashes. Approve Clashes By Item Approves items by clash type. The system displays the Approve by Item A or Approve by Item B toggle and a display list of possible clash types.
Clash Status Approves or unapproves the current clash. Depending on the status of the displayed clash, the Unapprove Clash, Approve Real Clash or the Approve False Clash option will be highlighted. For more information, see Approve From List, page 119. Unapprove Clash changes the status of a clash from approved to unapproved. Approve Real Clash approves the clash as a real clash in the Project Control Database.
307
Approve False Clash approves the clash as a false clash in the Project Control Database. Action Discipline: Displays the Action Discipline for every model combination unless both models are from the same discipline. The Action Discipline is defined using the Project Administrator and indicates the job responsibility or who should take action to resolve the clash. This toggle only appears if there are two different disciplines involved in a clash. Select View Zooms in and updates selected views. Select the option and then select the views that you want to update. Plot Active Clash Plots the clash in the active view immediately, placing the temporary plot files in the c:\temp directory. It either plots default or detailed clashes depending on the way the toggle has been defined using the Project Data Manager module of Project Administrator. You can review this setting using the Checker Reference Data command. The system displays the Plotter Queue list, showing the available plotters. Select a plotter from the list and click Accept to plot the clash.
Envelope Diagnostics Creates MicroStation-type graphics from the interference envelopes for a selected model in a design file. For more information see the Envelope Diagnostics, page 118. Enter Dynamics Rotates clashes orthogonally or in 3D about a particular view. See the Enter Dynamics section for more information. Restore View Restores the active window. Select the option, and the system automatically updates the active window. Highlight Clash Highlights the active clash in every view. Select the option, and the system automatically highlights the active clash in grey. Keyin Marker Number Defines the marker number of an existing clash. Select the option, and key in a marker number in the Marker Number field. Without Reference Models/With Reference Models Defines that the clash display be with or without reference models. Without Reference Models is the default and shows the clashing elements only. With Reference Models displays the reference files (for example the structural model file and the raceway model file) and highlights the clashing members.
If prompted to...
Do this:
308
Select Clash Type Select Review Option
Set the toggle to the appropriate setting and select the clash types to be approved. Use one of the options described above to edit or examine the existing clashes.
309
Envelope Verification Error Messages (replaces A.1.1)

Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager Users Guide (p. 251 in the PDS 7.1 version of the document). The following information has been added: Error messages and warnings regarding invalid direction vectors, point locations, and lengths/radii. See the following text for details.
When running envelope file verification, you might encounter one or more of the following error messages. ERROR - component # range not within design range Reason: There is an invalid component with a range from -2147483648 to 2147483647 (which is the entire design volume). Recovery: Look for this component in the .evd file and delete it. Then go into MicroStation and fence rotate the model by 0 degrees or find the offending element and correct it. ERROR - duplicate linkages Reason: There are components with duplicate linkages. Recovery: Go into the design file and run diagnostics. ERROR - shape # range not within component # range Reason: There is an invalid shape with range outside of component valid range. Recovery: Look for this component in the envelope file and delete it. Go into MicroStation and fence rotate the model by 0 degrees. ERROR - Unable to open XXX Reason: The system cannot find the file or cannot read the file. Recovery: Make sure the system where the file resides is turned on and the file has read permissions. ERROR: - cylinder primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - cylinder secondary vector invalid Reason: The secondary direction vector has a value outside the range of 0.999 to 1.001.
310
ERROR: - conic primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - conic secondary vector invalid Reason: The secondary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - torus primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - torus secondary vector invalid Reason: The secondary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - projected shape primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - projected shape secondary vector invalid Reason: The secondary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - projected shape point X not within component range, where X is a number (1, 2, 3) Reason: The specified point on the shape is not within the component range. ERROR: - semi ellipsoid primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - semi ellipsoid secondary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - semi ellipsoid center point not within component range Reason: The specified point on the shape is not within the component range. ERROR: - revolved shape primary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - revolved shape secondary vector invalid Reason: The primary direction vector has a value outside the range of 0.999 to 1.001. ERROR: - point X not within component range, where X is a number (1, 2, 3). Reason: -- The specified point on the shape is not within the component range.
311
When running envelope file verification, you might encounter one or more of the following warning messages. WARNING - component # has disjoint shapes Reason: A component has been placed, but the shapes are not connected. Recovery: This can be OK, but check your file to make sure this is what you intended. WARNING - envelope file is empty Reason: The design file is empty or there is a problem with the design file. Recovery: Check the log file and any errors and check the model file for problems. WARNING: - connect point X not within component range, where X is a number (1, 2, 3 ...) Reason: The specified point on the shape is not within the component range. WARNING: - cylinder center point not within component range Reason: The specified point on the shape is not within the component range. WARNING: - cylinder length less than 20 UORs Reason: The specified length is less than the minimum of 20 UORs. WARNING: - cylinder radius less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - conic center point 1 not within component range Reason: The specified point on the shape is not within the component range. WARNING: - conic center point 2 not within component range Reason: The specified point is not within the component range. WARNING: - conic radius 1 less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - conic radius 2 less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - toroid center point not within component range Reason: The specified point is not within the component range. WARNING: - torus radius less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs.
312
WARNING: - torus ellipse radius less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - semi ellipsoid primary radius less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - semi ellipsoid secondary radius less than 20 UORs Reason: The specified radius is less than the minimum of 20 UORs. WARNING: - cylindrical string radius less than 20 UORs" Reason: The specified radius is less than the minimum of 20 UORs.
313
Index
approval manager approve, 306 Approve command, 306 clash detection non-PDS models, 301 error messages, 310 interference detection non-PDS models, 301, 306 non-PDS models clash detection, 301 interference detection, 301 warning messages, 312
314

Clash

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Clash

Uploaded by

Copyright:

Available Formats

Interference Checker/Manager (PD_Clash)

Restricted Rights Legend

Warranties and Liabilities

If You Need Assistance

Intergraph General Information

2.3 2.4 2.5 2.6 2.7 2.8 2.9

Interference Management .............................................................................................................

Piping Clash Check .............................................................................................................

6.3.4 6.3.5 6.4 6.5

View, More Commands .......................................................................................... Viewing Direction ...................................................................................................

Element Commands ............................................................................................................ 6.6.1 Analyze ...................................................................................................................

Report Multiple Submit Form ..................................................................

Report Management Defaults Form ........................................................................

Interference Report Management Data ...............................................................................

More information indicates there is additional or related information.

Welcome to Interference Checker/Manager (PD_Clash)

Interference Checker/Manager Introduction

Understanding Design Areas and Volumes

Understanding Design Areas and Volumes

Design Area and Piping Design Area Predefined Volume

Understanding Interference Envelopes

Understanding Interference Envelopes

Understanding Envelope Verification

Understanding Envelope Diagnostics

Understanding Interference Checking

Batch Interference Checker

Interference Checker Input

Interference Checker Output

Understanding Interference Checking

E 14 0" Plant E 10 0" Plant

N 11 6" Plant N 10 0" Plant

El -1 6" Plant El 0 0" Plant

Understanding Interference Checking

Understanding Interference Approving

Understanding Interference Plotting

Understanding Interference Reporting

Basic Interference Checklist

Hard - Hard Example

Hard - Soft Example

Understanding Redirection Queues

Redirection Queues Example

Redirected Processing Example

Interference Checker Data

Single/Dual Design Area Ownership

Models Checked using Dual Area Ownership

Single/Dual Design Area Ownership

Setup for Clash Management

Exclusion of Interferences by Discipline

Why Define a Matrix?

Exclusion of Interferences by Discipline

Understanding the Effect of a Matrix

Reviewing and Modifying Matrices

Exclusion of Interferences by Discipline

Exclusion of Interferences by Discipline

Exclusion of Interferences by Model Status

Exclusion of Interferences by Model Status

Equipment without/with Insulation

Construction Tolerances for Equipment Envelopes

Defining Pipe-like Components

Clash Envelopes for Welds

Create Project Envelope Files

Piping Design Area

Piping Design Area

Piping Design Area Predefined Volume