Clash

Interference Checker/Manager (PD_Clash) User’s Guide Document Number Version Date Pages DPDS3-PB-200006A PDS 7.1 April 2002 1-274 DPDS3-PB-200006B PDS 7.2 February 2003 275-298 DPDS3-PB-200006C PDS 7.3 October 2004 299-314 DPDS3-PB-200006D PDS 8.0 SE November 2005 Cover/Notice DPDS3-PB-200006E PDS 8.0 SE March 2007 315-354

Copyright Copyright © 1984-2007 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 below. For civilian agencies: This was developed at private expense and is “restricted computer software” submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished – rights reserved under the copyright laws of the United States.

Intergraph Corporation 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, PDS, SmartPlant, SmartSketch, FrameWorks, INtools, MARIAN, ISOGEN, and IntelliShip are registered trademarks and SupportModeler and SupportManager are trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

If You Need Assistance________________

If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’sproducts, services, and direction. Our web address is: http://www.intergraph.com.

Support

For the lasest Support Services information, use a World Wide Web browser to connect tohttp://www.intergraph.com/ppo/services/support.asp.

If you are outside of the United States, please call your local Intergraph office. The most up-to-date list of international offices and distributors is available on the web athttp://www.intergraph.com.

Intergraph Directory

The following numbers are only valid in the United States unless otherwise indicated. If youare 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 & Offshore300 Intergraph WayMadison, Alabama 35758U.S.A.

You can also reach us by electronic mail at [email protected].

3

________________

Documentation Contacts

We are constantly working on updates and improvements to the documents and othereducational media. If you have any suggestions on where we can improve the documentationor where you think more information is needed, let us know. You can reach us by:

Mail Intergraph Process, Power & OffshoreDocumentation Manager300 Intergraph WayMadison, AL 35758

4

Table of Contents________________

Table of Contents

If You Need Assistance ........................................................................................................ 3Intergraph Directory ............................................................................................................. 3

Preface ................................................................................................................................................. 11

About this reference material ................................................................................................ 11

General Conventions .................................................................................................................... 13

Keyboard Conventions ......................................................................................................... 14Terminology ......................................................................................................................... 15

1. Welcome to Interference Checker/Manager (PD_Clash) ............................................................. 17

1.1 Interference Checker/Manager Introduction ....................................................................... 18

1.1.1 Project Organization ................................................................................................ 18

2. Interference Detection .................................................................................................................. 19

2.1 Understanding Design Areas and Volumes ........................................................................ 20

2.1.1 Project ..................................................................................................................... 202.1.2 Piping Design Area and Design Area ..................................................................... 212.1.3 Design Area and Piping Design Area Pre-defined Volume .................................... 212.1.4 Volume Filter .......................................................................................................... 22

2.2 Understanding Interference Envelopes ............................................................................... 23

2.2.1 Understanding Envelope Builder ............................................................................ 232.2.2 Understanding Envelope Verification ..................................................................... 242.2.3 Understanding Envelope Diagnostics ..................................................................... 24

2.3 Understanding Interference Checking ................................................................................. 252.4 Understanding Interference Approving ............................................................................... 302.5 Understanding Interference Plotting ................................................................................... 302.6 Understanding Interference Reporting ................................................................................ 302.7 Basic Interference Checklist ................................................................................................ 312.8 Clash Categories .................................................................................................................. 332.9 Project Setup ....................................................................................................................... 35

2.9.1 Redirected Processing ............................................................................................. 37

3. Interference Management ............................................................................................................. 39

5

PDS Interference Checker/Manager User’s Guide - April 2002________________

3.1 Interference Checker Data ................................................................................................... 41

3.1.1 Single/Dual Design Area Ownership ...................................................................... 433.1.2 Exclusion of Interferences by Discipline ................................................................ 473.1.3 Exclusion of Interferences by Model Status ........................................................... 543.1.4 Equipment without/with Insulation ......................................................................... 563.1.5 Construction Tolerances for Equipment Envelopes ................................................ 57

4. Envelopes ..................................................................................................................................... 59

4.1 Envelope Builder ................................................................................................................. 60

4.1.1 Create Project Envelope Files ................................................................................. 694.1.2 Piping Design Area ................................................................................................. 704.1.3 Piping Design Area Predefined Volume ................................................................. 724.1.4 Design Area ............................................................................................................. 734.1.5 Design Area Predefined Volume ............................................................................. 74Clash Envelopes for Areas with DVCS .............................................................................. 754.1.6 Model ...................................................................................................................... 76

4.2 PDS Clash Detection with Non-PDS Models ..................................................................... 774.3 Envelope Verification ......................................................................................................... 814.4 Envelope Diagnostics .......................................................................................................... 85

5. Interference Checking .................................................................................................................. 89

5.1 Interference Checker ........................................................................................................... 90

5.1.1 Plot Clashes ............................................................................................................. 985.1.2 Interference Checker Output ................................................................................... 105

5.2 Piping Clash Check ............................................................................................................. 108

6. Interference Managing ................................................................................................................. 111

6.1 Interference Approval Manager .......................................................................................... 1126.2 Approval Manager Commands ........................................................................................... 114

6.2.1 Approve ................................................................................................................... 115

6.2.1.1 Select View .............................................................................................. 1186.2.1.2 Envelope Diagnostics ............................................................................... 1186.2.1.3 Enter Dynamics ........................................................................................ 118

6.2.2 Approve From List .................................................................................................. 1196.2.3 Checker Run Dates .................................................................................................. 1216.2.4 Review Clash History ............................................................................................. 1226.2.5 Create Unapproved Clash Report ............................................................................ 1246.2.6 Checker Reference Data .......................................................................................... 1276.2.7 Mass Clash Approval .............................................................................................. 130

6

Table of Contents________________

6.3 View Commands ................................................................................................................. 133

6.3.1 View Commands ..................................................................................................... 137

6.3.1.1 Move and Center View ............................................................................ 1396.3.1.2 Construct Point ......................................................................................... 1416.3.1.3 Distance and Direction ............................................................................. 143

6.3.2 Window Volume ..................................................................................................... 145Viewing Options ................................................................................................................. 145

6.3.2.0.1 Set View Orientation ......................................................................................... 1476.3.2.0.2 Update Window ................................................................................................ 1486.3.2.0.3 Rotate About View ............................................................................................ 1496.3.2.0.4 Match Planar Element Command ..................................................................... 1506.3.2.0.5 Rotation 3 Points ............................................................................................... 1516.3.2.0.6 Dialog View Rotation ....................................................................................... 1526.3.2.0.7 Color Shading ................................................................................................... 153

6.3.3 Render Options ........................................................................................................ 154

6.3.3.1 Camera View ............................................................................................ 1566.3.3.2 Views ........................................................................................................ 1586.3.3.3 Level Symbology On ............................................................................... 1596.3.3.4 Level Symbology Off ............................................................................... 1606.3.3.5 Form Left/Right Screen ............................................................................ 1616.3.3.6 Set/Do Not Set Display Depth for Review Commands ........................... 162

6.3.4 View, More Commands .......................................................................................... 1636.3.5 Viewing Direction ................................................................................................... 165

6.4 View Depth ......................................................................................................................... 1676.5 File Commands ................................................................................................................... 168

6.5.1 File Commands ....................................................................................................... 169

6.5.1.1 Plot Clashes .............................................................................................. 1706.5.1.2 File Design ............................................................................................... 1756.5.1.3 Exit ........................................................................................................... 175

6.6 Element Commands ............................................................................................................ 176

6.6.1 Analyze ................................................................................................................... 176

6.7 Setting Commands .............................................................................................................. 1776.8 User Commands .................................................................................................................. 1796.9 Interference Management Data ........................................................................................... 1806.10 Piping Clash Review (in the PD_Design Module) ........................................................... 1816.11 Piping Clash Check (in the PD_Design Module) ............................................................. 1846.12 Review PDS Clash ............................................................................................................ 186

7


Parameters ........................................................................................................................... 186

7. PDS Interference Plotting ............................................................................................................ 189

7.1 Interference Plot Manager ................................................................................................... 1907.2 Interference Plot Management Data .................................................................................... 196

8. Interference Reporting .................................................................................................................. 197

8.1 Clash Report Manager Form ............................................................................................... 198

8.1.1 Using the Report Commands .................................................................................. 1998.1.2 Report Format Form ................................................................................................ 201

8.1.2.1 Format Creation/Revision Form .............................................................. 2038.1.2.2 Format Deletion Form .............................................................................. 205

8.1.3 Report Discrimination Data Form ........................................................................... 207

8.1.3.1 Discrimination Data Creation Form ......................................................... 209

8.1.3.1.1 Project Administration Form ................................................. 2118.1.3.1.2 Project Search Criteria Form .................................................. 212

8.1.3.1.2.1 Define Date/Time .............................................. 215

8.1.3.2 Discrimination Data Revision Form ........................................................ 2178.1.3.3 Discrimination Data Deletion Form ......................................................... 219

8.1.4 Report Form ............................................................................................................ 221

8.1.4.1 Report Creation Form .............................................................................. 2238.1.4.2 Revise Report Form ................................................................................. 2268.1.4.3 Report Deletion Form .............................................................................. 2298.1.4.4 Report Approval Form ............................................................................. 231

8.1.4.4.1 Approval/Revision Interface Form ........................................ 232

8.1.4.5 Report Multiple Submit Form .................................................................. 234

8.1.5 Report Management Defaults Form ........................................................................ 236

8.2 Interference Report Management Data ............................................................................... 238

9. Scheduled Envelope Builder and Clash Detection ....................................................................... 239

9.1 Create/Revise Envelope Builder/Clash Detection Schedule ............................................... 242

9.1.1 Delete Envelope Builder/Clash Detection Schedule ............................................... 2459.1.2 Review Schedule ..................................................................................................... 247

8

Table of Contents________________ Appendix A: Troubleshooting PD Clash ......................................................................................... 249

A.1 Message Files ............................................................................................................................ 250

A.1.1 Envelope Verification Error Messages ......................................................................... 251

A.2 Tips on Using PD Clash ............................................................................................................ 252

Markers ...................................................................................................................................... 252Envelope Verification Dates ..................................................................................................... 252Approval Manager > Enter Dynamics Mode ............................................................................ 252Structural Database Records ..................................................................................................... 253Placing Spheres ......................................................................................................................... 253

A.3 Questions & Answers ................................................................................................................ 254

Changing title block units ......................................................................................................... 254

Appendix B: Interference Tables ..................................................................................................... 255

Glossary ............................................................................................................................................... 261

Index .................................................................................................................................................... 269

9


10

Preface________________

Preface

About this reference material

Interference Checker/Manager is organized by subject and commands on the Interference Checker/Managerinterface 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, andreporting, distributed processing, queue setup, and a PDS Overview.

Section 3 — briefly explains the Interference Management options. They allow you to access each ofthe options available in the interference checking process. It also explains the Interference CheckerData 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 creatingenvelopes which must be done prior to interference checking. It explains Envelope Verification whichchecks the dates of the model and its corresponding envelope to make sure that the envelope is up-to-datewith the model. Envelope Diagnostics and it’s envelope diagnostics graphics are also explained.

Section 5 — explains the use of the Interference Checker option for an entire project or for separatedesign areas. It also contains information on PD_Design’s Piping Clash Check command.

Section 6 — explains the use of the Interference Approval Manager and Interference ManagementData options. It also contains information on PD_Design’s Piping Clash Review command.

Section 7 — explains the Interference Plot Manager and the Interference Plot Management Dataoptions used when plotting interference clashes.

Section 8 — explains the Interference Report Manager and the Interference Report ManagementData options. The Interference Report Manager option is used to generate user-defined interferencemanagement reports. The Interference Report Management Data option is used to define the networkaddress and pathname in the Project Control Database.

Section 9 — explains the Scheduled Envelope Build/Clash Detection options used to run envelopegeneration and clash detection as a batch process.

Appendix A - provides troubleshooting information including error messages, tips, and questions andanswers.

Appendix B — provides information on tables related to interference checking used in the Interferencesclass.

11


12

Preface________________

General Conventions

This document contains many visual cues to help you understand the meaning of certainwords or phrases. The use of different fonts for different types of information allows you toscan the document for key concepts or commands. Symbols help abbreviate and identifycommonly used words, phrases, or groups of related information.

Typefaces

Italic Indicates a system response, which is an explanation of what the software isdoing. For example,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Commandpaths 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 bythe user. For example,

Select first segment of alignment

Bold TypewriterIndicates what you should literally type in. For example,

Key in original.dat to load the ASCII file.

Normal TypewriterIndicates 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 specialinformation:

<C> Command button<D> Data button (usually the left mouse button)<R> Reset/reject button (usually the right mouse button)<T> Tentative button (usually the center mouse button)

Note — Important supplemental information.

Warning — Critical information that could cause the loss of data if not followed.

Technical tip or information — provides information on what the software isdoing 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 theexercises.

Keyboard Conventions

The following list outlines the abbreviations this document uses for keyboard keys anddescribes how to use them in combination. You can make some menu selections through theuse of keyboard accelerators, which map menu selections to key combinations.

ALT Alternate keyCTRL Control keyDEL Delete keyENTER Enter keyESC Escape key

CTRL+z To hold down the Control key and press Z.ESC,k To press the Escape key, then K.

14

Preface________________

Terminology

Click To use a mouse or key combination to pick an item that begins anaction. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by pickingit with your cursor. Selecting does not initiate an action. Afterselecting an item, you click the action you want to affect the item. Forexample,

Select the file original.dat from the list box, then click Delete toremove it from the directory.

In addition, you would select items to define parameters, such asselecting toggle buttons. This also applies to selecting graphicelements 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 designfile. If you are using the CLIX operating system, you tentative-selectby double-clicking with a mouse or pressing <T> on a hand-heldcursor. If you are using the Windows NT operating system, youtentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-heldcursor button twice in rapid succession. This term implies that you areclicking 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 orhand-held cursor.

Type To key a character string into a text box.

Key in To type in data and press ENTER to enter the data and execute thedefault action.

In a dialog box, pressing TAB after keying in data willenter the data and move the cursor to the next field.

15


16

1. Welco

me

Welcome to Interference Checker/Manager (PD_Clash)________________

1. Welcome to InterferenceChecker/Manager (PD_Clash)

Interference Checker/Manager (PD_Clash) creates envelope files for all models in thespecified project, design area, or for individual models which have an envelope builderspecific to each discipline in the Interference Checker/Manager. It also collects envelope datafor the models that have envelope files which were previously created by one of the otherPDS modules. The checker/manager processes the specified design volume and identifies allof the interference clashes.

17


1.1 Interference Checker/ManagerIntroduction

The Interference Checker/Manager (PD_Clash) product processes a specified design volumefor interference clashes, reviews interferences, and reviews or revises the approval status ofinterferences. You can check for interferences at any stage of the design process. Also, youcan redirect clash checking through a pipe queue to a server or to another workstation on thesame LAN.

1.1.1 Project Organization

Since a process plant such as a refinery can be extremely large, PDS uses the followingorganization 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 isthe fundamental structure for working in PDS. The project constitutes the entire volume of theproject.

A Design Area represents a specified volume of the project for a specific discipline. Thisvolume is defined by the models it comprises. Design volumes can be used to break up theproject into smaller areas for interference checking or reporting. This speeds up processingwhen only a portion of the project has changed. The models or model components that arenot within the volume will not be checked.

A Design Area Pre-defined Volume represents a pre-defined volume of the project for aspecific 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 EnvironmentManager. Make sure that the pre-defined volume encompasses all the models that you wantto be checked. The models or model components that are not within the volume will not bechecked.

A model is a 3D Microstation file that has a defined discipline and is located within thevolume of the project. A model represents a subdivision of the project based on workresponsibility, 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 tofurther 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. Eachproject consists of a project control database, project design database, piping and equipmentmodels, reference models (structural, HVAC, and electrical raceway), a set of drawings, and acollection of reference data. The reference data may be specific to one project or shared bymore than one project.

18

2. Basics

Interference Detection________________

2. Interference Detection

This section provides information required to understand the terminology and philosophyinvolved with interference detection, see:

2.1 Understanding Design Areas and Volumes See Understanding Design Areas andVolumes, page 20 for more information.

2.2 Understanding Interference Envelopes See Understanding InterferenceEnvelopes, page 23 for more information.

2.3 Understanding Interference Checking See Understanding Interference Checking,page 25 for more information.

2.4 Understanding Interference Approving See Understanding InterferenceApproving, page 30 for more information.

2.5 Understanding Interference Plotting See Understanding Interference Plotting,page 30 for more information.

2.6 Understanding Interference Reporting See Understanding Interference Reporting,page 30 for more information.

2.7 Basic Interference Checklist See Basic Interference Checklist, page 31 for moreinformation.

2.8 Clash Categories See Clash Categories, page 33 for more information.

2.9 Project Setup See Project Setup, page 35 for more information.

19


2.1 Understanding Design Areas andVolumes

This section thoroughly describes design areas and volumes and how they pertain tointerference checking.

Running the Interference Checker for an entire project takes considerably longer than runningit for a design area. Since the project workload is most often being delegated to variousdisciplines, it is most efficient to use the design area options. These options are less timeconsuming and create individual sets of reports rather than one set of reports for the entireproject. Adhere to using either the Project option or one of the Design Area options for thelife 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 eitherthe 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 theenvelope files defined for the project and creates interference, difference, and batch queueerror reports. To specify a smaller volume for a single interference check, set the VolumeFilter toggle to On after selecting a design area.

The dotted rectangle signifies the volume that is processed using the Project option.

20

2. Basics

Understanding Design Areas and Volumes________________

2.1.2 Piping Design Area and Design Area

These options on the Interference Checker form activate a list of piping design areas or a listof disciplines and then a list of design areas from the specified discipline that are available forclash checking.

After a design area has been selected, the system defines a volume that encompasses allmodels within the selected design area. It then performs an interference check on all modelsand parts of models, including models from all other disciplines, that are in the definedvolume. To specify a smaller volume for a single interference check, set the Volume Filtertoggle to On after selecting a design area.

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 Pre-defined Volume

These options on the Interference Checker form activate a list of piping design areas or a listof disciplines and then a list of design areas with pre-defined volumes available for clashchecking.

After a design area has been selected, the system uses the pre-defined volume that has beenspecified by using the Project Environment Manager. It then performs an interferencecheck on all models and parts of models, including models from all other disciplines, that arein the pre-defined volume.

The Interference Checker does not include models that are in the selecteddesign area that do not fall within the pre-defined volume.

The dotted rectangle signifies the volume that is processed using the Design Area Pre-defined 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 theInterference Checker. When set to Volume Filter On, you can define the low and highEasting, Northing, and Elevation for one run of the Interference Checker in the followingfields. 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 beenactivated and the volume to be checked has been specified.

22

2. Basics

Understanding Interference Envelopes________________

2.2 Understanding InterferenceEnvelopes

2.2.1 Understanding Envelope Builder

Piping, equipment, structural, raceway, and HVAC envelope files are created through the PDSInterference Checker/Manager module. All Architectural files will have their interferenceenvelope files created within the Architecture product. Envelopes for MicroStation files arecreated through the PD_Clash envelope builder using the generic envelop builder.

The envelope building process and its results will vary depending on the waythe Interference Checker Data command is defined. The settings that affectenvelope 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 modelgraphics, which are not associated with the design area selected, encroach on the volumerepresented by the design area:

If the envelope file that corresponds to the model is up-to-date with respect to themodel, 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 themodel, but it has interference envelopes in the volume of the selected design area, thenthe 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 themodel and it does not have any interference envelopes that fall within the volume of theselected design area, then the envelope builder determines if the model has anycomponents that falls in the volume of the selected design area. If so, the envelope filefor that model is re-created.

Log files are batch queue error reports for the envelope builder data server. These fileswill have the extension .blg and are created on the server or workstation in the c:\tempdirectory from which it was submitted and contains information regarding the error.

23


2.2.2 Understanding Envelope Verification

The Envelope Verification command sorts the models being verified into one of thefollowing 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 themodel and may require being re-created. This is because either the model has beenrevised since the interference envelopes were created, or the interference envelope fileis non-existent.

Not Mounted: an error occurred while mounting the file system where the modelresides.

2.2.3 Understanding Envelope Diagnostics

The interference envelope diagnostics command creates MicroStation graphics from theinterference envelopes for the model, model name .til. This file is used to view theinterference envelopes interactively. You can view the .til within the Envelope Diagnosticscommand or through MicroStation to verify if the envelopes are correct. The file is in thesame directory as the model.

Any discrepancies found during this verification process indicate problems in the applicableEnvelope Builder and will be reported in a file in the c:\temp directory named after the projector design area with a .evd file extension.

24

2. Basics

Understanding Interference Checking________________

2.3 Understanding Interference Checking

The interference detection process and its results will vary depending on thesettings defined on the Interference Checker Data form. These settingsinclude:

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 Interference Checker Data, page 41.

Batch Interference Checker

Interference checking can be done for the entire project or be broken up into design areas ormodel pairs. Since the processing time for an entire project is much greater than for a designarea and since it is often the case that only a certain design area or set of design areas needs tobe 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 inwhich it was found. It is therefore important to use either the Project option or any ofthe Design Area options consistently for the life of a project.

The Project option processes the largest area of the project and encompasses everymodel file.

The Piping Design Area and Design Area options process a smaller division of aproject with a limited number of model files.

The Piping Design Area Pre-Defined Volume and Design Area Pre-Defined Volumeoptions process each area to be broken down further specifying specific volumecoordinates to limit further the number of model files.

The Single/Pair Model Check option allows you to define a single model or pair ofmodels 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 apiping file’s items by reviewing the clashes interactively with the PD_Design software.

25


The PD_Design software runs interference checking interactively through thepiping design file. This option can check one pipeline at a time or the activemodel 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 knowninterference is stored in the Project Control Database. When an interference isapproved, it will no longer be included in future interference reports. This allows allinterferences within a project to be resolved, either by changing the approval status ofthe interference to Approved or by revising the model.

Interference Checker Output

For a description of every possible user- and system-generated reports, see the UnderstandingInterference Reporting section. The following report is generate by default during theInterence Checker process:

PDS Interference Report This report contains all unapproved clashes, sorted first bymodel combinations then by the type of clash. For instance, all clashes detectedbetween model A and model B would be grouped together. A synopsis of the clashes isincluded at the beginning of the report. This report also includes the model status ofany components involved in a clash for the piping, structural, HVAC, and equipmentdisciplines. 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 arecreated each time the checker is run. The interference report is created on theworkstation or server in the directory from which the Interference Checker wassubmitted unless otherwise specified using the Interference Report ManagementData option. The report begins with a synopsis of all clashes found during interferenceprocessing and includes a report of the clashing items within each of the design filesrepresented in the synopsis.

26

2. Basics


PDS Interference Synopsis

vcpipe1.env

Number of clashes = 1

wwpipe1.env


wwpipe1.env

eqmdl1.env


eqmdl1.env


vcpipe1.env

wwpipe1.env


vcpipe1.env

eqmdl1.env


PDS Interference Report

Date: 28-Jun-93 Time: 13:43:33

Model ’A’ Design File Name: vcpipe1

Entire Design Volume Included In Report

No Item Name Table Row X Coord Y Coord Z Coord

__ _________ _____ ___ _______ _______ _______

2 PIPING 5 524291 E 28’ 6" Plant N 0’ 0" Plant El 0’ 0" Plant

P601-12IN-1C0031-N

Not approved

2 PIPING 5 524299 E 25’ 0" Plant N 3’ 0" Plant El 0’ 0" Plant

P603-8IN-1C0031-N

Not approved


Date: 28-Jun-93 Time: 13:43:47

Model ’A’ Design File Name: vcpipe1


Model ’B’ Design File Name: eqmdl1


PDS Interference Clashes

Hard/Hard Clashes


__ _________ _____ ___ _______ _______ _______

3 E90LR 3 524297 E 17’ 0" Plant N 10’ 0" Plant El 0’ 0" Plant

P601-12IN-1C0031-N

Not approved

3 TEST 21 3 E 14’ 0" Plant N 11’ 6" Plant El -1’ 6" Plant

4 E90LR 3 524298 E 10’ 0" Plant N 10’ 0" Plant El 0’ 0" Plant

P601-12IN-1C0031-N

Not approved

4 TEST 21 3 E 10’ 0" Plant N 11’ 6" Plant El -1’ 6" Plant

Interference Markers All interferences within the project are graphically representedby markers and are used by the Interference Approval Manager. Each time theInterference Checker detects an interference within the project, a marker is written toone of the marker files. The marker files are created in the project directory during

27

PDS Interference Checker/Manager User’s Guide - April 2002________________ project creation. They are named after the project database and have a .dgn fileextension. A marker design file is also created as each design area is defined in theProject Control Database. The interference markers are numbered in the .int report witha system-assigned sequential number starting with 1. A marker design file is created foreach design area; the name of the file is the same as the area name and the file extensionindicates the discipline, for example, 1=piping, 2=equipment, and so forth.

Error File. If an error is found while running the Interference Checker, the systemwrites the item name and an error code in a file named after either the project or designarea, depending on the option selected to run the Interference Checker, with a .icl fileextension 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-timeerrors will be listed in these log files in the c:\temp directory.

Project Control Database Records The following tables are updated by InterferenceChecking:

— 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. Theunique_clash_id uniquely identifies a clash.

— Interference Clash Data Per Job A record is created each time a clash isencountered.

— Component Interference Clash Data Per Project A record is created for eachmodel item that is involved in one or more clashes.

These records are used by subsequent executions of the Interference Checker andInterference Approval Manager.

Clash Plots These files are named by the system as the marker number with theextension .plt and placed in the c:\temp directory; or you can use the Interference PlotManagement Data to specify a node and directory. You can also define that the systemgenerates a default or detailed clash. The system automatically generates the plotsthrough the PDifc_plot queue. For more information, see Plot Clashes, page 98. Thesefiles can be reviewed interactively through MicroStation, or they can be plotted. Theplot shown on the following page is a detailed plot.

28

2. Basics


29


2.4 Understanding InterferenceApproving

The Interference Approval Manager is used to review all interferences in a project or area andrevise 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 futureclash plot files.

Defining a default node and path is a required step in the Interference CheckingProcess. Problems could occur later in the process if this step has not been completed.

2.6 Understanding InterferenceReporting

The PDS Interference Report is generated automatically during interference detection andreports specifically on clashing items.

The Interference Report Manager creates and revises report formats, discrimination dataand report files. The interface and process for interference reporting is similar to that used inthe PDS Report Manager module. These reports are more specific project-control reports.

The Interference Report Management Data option establishes a default node and path forreport files.

30

2. Basics

Basic Interference Checklist________________

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

Define the matrix for discipline responsibility and define intra-discipline checking. Alsodefine single or dual responsibility to design areas.

Envelope Builder

Generate envelope files using the Envelope Builder option. The system generatesenvelopes 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 forthe 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 detaileddescription of the processed files.

Envelope Verification

Review the verification errors file if it is generated. If errors are found during theverification process, a log file containing detailed information of the errors is generatedand named after the project or design area; it has a .err extension. The location of thisfile is determined by the Interference Report Management Data. If a .err file isgenerated, it usually indicates that an envelope does not exist, is out of date, or thesoftware is having difficulty accessing the files. It can also indicate problems withindividual envelopes.

Envelope Diagnostics

Use the Envelope Diagnostics to generate and interactively view a MicroStation-typegraphics file; it is named after the model and has a .til file extension, and is in the samedirectory as the model. This file can be viewed using the Create and ReviewDiagnostics File, or it can be viewed in MicroStation.

Review the envelope diagnostics file if it is generated. If errors are found during thediagnostics process, a log file containing detailed information of the errors is generatedand 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.

31

PDS Interference Checker/Manager User’s Guide - April 2002________________ The system generates marker files, which hold all found clashes. These marker files arenamed after the project or design area. In the case of a design area, the file extension isthe number that represents the discipline of the design area. For instance, for a Pipingdesign area, the file extension would be .1.

Review the interference report generated by the system named after the project ordesign 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 areawith a .mgr file extension.

32

2. Basics

Clash Categories________________

2.8 Clash Categories

The Interference Approval Manager and the reports created by the Interference Checkerdistinguish 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.

Construction — A clash or discrepancy between the user-defined distance and theactual 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 structuralcomponents but one is found closer, a Construction clash is reported.

Clash Precedence

The precedence for reporting clashes is Hard, Soft, and Construction. This results ininterference clashes being reported in one of the following categories. The report will containonly the category of clashes with the highest precedence in accordance with the followingprecedence table:

Hard - HardHard - SoftHard - ConstructionSoft - SoftSoft - ConstructionConstruction - Construction.

Hard - Hard Example

The following example contains clashes between actual physical components. It would becategorized as a Hard - Hard clash.

33


Hard - Soft Example

The following example displays a clash between an actual component and space that has beenallocated for maintenance accessways. It would be categorized as a Hard - Soft clash.

34

2. Basics

Project Setup________________

2.9 Project Setup

The following items list specific consideration of which you should be aware during projectsetup:

1. Load PDS 3D products.

It is necessary that all servers and workstations be loaded with the latest release of PDSand nucleus software. The PDS software between servers and workstations must becompatible to run correctly. It is highly recommended that you read the Release Notesof the PD_CLASH README file when new releases are issued so that you will beinformed of any changes made to the product. The CAD Support person would mostlikely do this.

2. Set up plot queues.

The Interference Checker/Manager provides one default and four optional plot queuesfor different types of plotters. The selection of the plot queue applies to all graphicinterference clash plots in a batch process. Multiple queues provide the flexibility insituations that arise which require different plotters for different paper types. This stepwould be completed by the CAD Support/System or Project Manager.

3. Set up Interference Checker queues.

The Interference Checker/Manager provides the option of distributing clash checkingwith pipe queues. Also, PD_Clash, PD_Shell, and MicroStation must be loaded ontoeach server or workstation for which a pipe queue has been directed. This step would becompleted 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 aspecific design area for processing. This is done when the areas and model files arecreated. The location of the area marker file and model design file are stored by thesystem. For the architecture files, the locational data is provided by input from the PDSProject 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 aredetected 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 smallportions called design areas. The processing time for an entire project is much greaterthan for a design area. Also, it is often the case that only a certain design area or set ofdesign areas needs to be checked.

Once you decide which method to use, either the Project option or thedesign area options, remain consistent. The more consistent you arewith your option selection, the more consistent the results will be. For

35

PDS Interference Checker/Manager User’s Guide - April 2002________________ example, you might select a design area option and receive the resultsfor one design area. You might correct a few of the interferences andthen run interference checking with the Project option. Remember, theinterference checker will only report new clashes, therefore, old clasheswould not be reported again although they may still exist in the designarea that was first checked.

6. Edit the control script to identify the location of the project data.

7. 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 InterferenceChecker/Manager. The file privileges for the specified files will be verified. Refer to thefollowing 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. Basics

Redirected Processing________________

2.9.1 Redirected Processing

Since interference checking is process intensive, the Interference Checker/Manager allowsyou to redistribute interference checking to another workstation or server on the LAN. Eachworkstation involved must have PD_Shell and PD_Clash loaded as (l)ocal or (c)lient. If youare redirecting to a server, the applications may be loaded as (s)erver. The following listdescribes the three redistribution functions.

Redirection Functions

Activation — This function consists of starting the interference checking process byselecting the project or area to be checked, setting the plotting node, and submitting thejob through a pipe queue.

Administration — This function consists of assigning pairs of files for comparison andtracking their progress through a process called checkerserver, and reporting clash datato the project database through a process called markerserver. This job is run through abatch queue, PDclash_server.

Processing — This function consists of processing all interference-checking tasksassigned by the Administration function. Usually, the Activation is done on oneworkstation and Administration and Processing are done on another workstation/server.

Understanding Redirection Queues

The workstations that are involved in redirected processing are connected by pipe queues. Apipe queue is set up from the workstation that activates the interference checking process tothe second workstation/server. The actual administration processing will be handled by thebatch queues on the second workstation/server. These are automatically created duringsoftware installation.

Make sure that all of the pipe queues that will be used during redirectedprocessing are pointing to the correct destinations and not just residing on theworkstations from a previous configuration.

Redirection Queues Example

Node 1

— (Activation)

PDclash_server@node1(Pipe to node2)– Sends the interference activation messageto Node 2 to begin the Administration function. By default this queue is a batchqueue which delegates processing assignments locally. However, it is changed topipe queue on Node 1 when Administration is to be done on a remote node asillustrated in the Redirected Processing Example.

37

PDS Interference Checker/Manager User’s Guide - April 2002________________ Node 2

— (Administration)

PDclash_server@node2(Batch)– Receives the activation message from Node 1 tobegin Administration and invoke Processing. By default this queue is createdautomatically at software installation as a batch queue. It is started on Node 2 bythe pipe queue of the same name which resides on Node 1, [email protected] processing is complete, it compiles the marker data and creates a report sentby 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 softwareinstallation.

PDcheck_1@node2(Pipe to local)– Is created automatically at software installation.However, when setting up for redirected processing, this queue is not used. Itsexistence is not required for redirected processing nor will its absence preventredirected processing.

Redirected Processing Example

In the following example Node 1 performs the Activation, and Node 2, which is the networkserver, performs the Administration and Processing. For C300 and C400 servers with largeamounts of memory (64 MB or more) there is little perceived degradation in systemperformance for other users of this server on the network.

38

3. Man

agem

ent

Interference Management________________

3. Interference Management

This option activates the Interference Management form. It is used to provide access to theInterference commands. These commands build and verify envelope files, process theenvelope files for interference clashes, review interferences, report on and plot clashes, andreview or revise the approval status of interferences.

Commands

Envelope Builder — Creates and updates interference envelopes for PDS and non-PDSmodel files. For more information, see Envelope Builder, page 60.

Interference Checker — Detects interference clashes in the specified model, designarea, project, or volume. For more information, see Interference Checker, page 90.

Interference Checker Data — Makes the envelope-building process and theinterference-detection process more specific. You can specify single or dual design areaownership for use in Interference Approval Manager and Interference PlotManager. You can specify a discipline matrix used by Interference Checker andInterference Builder to define the combinations of disciplines that are to be checked orspecify intra-discipline checking. You can exclude interference detection by modelstatus range and include or exclude equipment insulation during interference detection.You can also define whether or not to consider the construction tolerance for certainequipment envelopes. For more information, see Interference Checker Data, page 41.

Interference Approval Manager — Reviews and revises interferences on a project orarea wide basis. For more information, see Interference Approval Manager, page 112.

Interference Management Data — Checks the model files and displays the completefile specifications of those files which are interference checkable. For moreinformation, see Interference Management Data, page 180.

39

PDS Interference Checker/Manager User’s Guide - April 2002________________ Interference Plot Manager — Plots interference clashes based upon search criteriausing Interference Management data or markers selected interactively. The clashes aregiven unique plot numbers within the group of interference clashes being plotted. Formore information, see Interference Plot Manager, page 190.

Interference Plot Management Data — Specifies the network address and path namein the Project Control Database to define where the system sends all plot files. Formore information, see Interference Plot Management Data, page 196.

Interference Report Manager — Uses definition data to generate user-definedinterference management reports. For more information, see Clash Report ManagerForm, page 198.

Interference Report Management Data — Specifies the network address and pathname in the Project Control Database to define where the system sends all InterferenceManagement reports. For more information, see Interference Report ManagementData, page 238.

Scheduled Envelope Build/Clash Detect — Defines a schedule for building envelopesand running clash detection. For more information, see Scheduled Envelope Builderand Clash Detection, page 239.

40

3. Man

agem

ent

Interference Checker Data________________

3.1 Interference Checker Data

This option activates the Interference Checker Data form, which allows you to make theenvelope-building process and the interference-detection process more specific. The followingexamples 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 aninterference matrix that specifies which disciplines are checked against each other. Forinstance, for all Equipment design areas, you can define a matrix that would only checkEquipment 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 Checkcommand to specify:

Models in the specified discipline are NOT checked against each other and are NOTchecked 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.

Along with the No Intra Discipline Interference Check command, you can also specifydual-design area ownership. (See the Single (1) Design Area Ownership / Dual (2) DesignArea Ownership discussion on the following pages for more information.) Dual-design areaownership ensures that only the design areas that own a component involved in a clash canown the clash. Therefore, with the combination of No Intra Discipline Interference Checkcommand and dual-design area ownership, the interference-detection process would be asfollows:

Models in the specified discipline are NOT checked against each other and are NOTchecked 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 alldisciplines checked against each other) would not be used; dual-design area ownershipspecifies that a design area can only own a clash if it owns at least one of the conflictingcomponents.

The possibilities are limitless. You can combine all of the Interference Checker Dataoptions to specify the exact interference-detection process that is needed.

Commands

Single (1) Design Area Ownership / Dual (2) Design Area Ownership — This toggleallows you to detect clashes when more than one design area needs to own, review, orapprove a clash. For more information, see Single/Dual Design Area Ownership, page43.

41

PDS Interference Checker/Manager User’s Guide - April 2002________________ Exclusion of Interferences by Discipline — This option allows you to specify howclashes are to be reported for combinations of disciplines. For more information, seeExclusion of Interferences by Discipline, page 47.

Exclusion of Interferences by Model Status — This option allows you to specify alow and high model-status range. For more information, see Exclusion of Interferencesby Model Status, page 54.

Equipment without Insulation / Equipment with Insulation — This option allowsyou 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 toenable or disable construction tolerances. For more information, see ConstructionTolerances for Equipment Envelopes, page 57.

42

3. Man

agem

ent

Single/Dual Design Area Ownership________________

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 usefulwhen 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 acomponent involved in a clash (when interference detection is run on that area). SeeModels Checked later in this section for other implications associated with this option.

— OR —

Single Ownership — Ownership assigned to the first design area to find the clash.

Dual ownership does not mean that ownership is automatically given to both design areaswhen a clash is found. It means that ownership is available to both design areas wheninterference detection is run on each.

Because clashes are stored in the database, reports can still be run on bothdesign areas involved in a clash, even if interference detection has not been runon both design areas. However, clashes are only written to the applicabledesign area’s marker file during the interference detection process for eachdesign area. Therefore, clashes can only be reviewed and approved in designareas on which interference detection has been run.

This is another filter that can be used in conjunction with all other Interference CheckerData options to affect the interference detection process.

This toggle does not define ownership assignments once clashes have beenfound. It acts as another filter in the interference detection process.

43

PDS Interference Checker/Manager User’s 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 donein this mode, clashes involving models that do not belong to the design area being checked arestill assigned to that design area.

For instance, if design area C were checked for interferences in the Single (1) Design AreaOwnership 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 designarea 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 intwo 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 beingchecked and all other models that fall within the volume of that design area. Clashes that donot 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 oneitem from Piping design area A are reported. Clashes not involving one or both items from amodel in Piping design area A are not reported, such as internal equipment, structural, andraceway 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 areasfrom other disciplines.

The implication of using Dual (2) Design Area Ownership is that each design areafrom each discipline must be interference checked to ensure that all clashes arefound.

The system ignores the Dual (2) Design Area Ownership setting whenchecking areas in the Clash discipline, because there are no models in theClash discipline.

44

3. Man

agem

ent

Single/Dual Design Area Ownership________________

Clash Ownership

If design area C were checked for interferences in the Dual (2) Design Area Ownershipmode, the system would compare models in design area C with models falling within thespecified volume including:

- All design area C models against themselves- All design area C models against design area A models- All design area C models against design area B models.

The clashes found involving, for instance, design area C models against design area A modelswould be owned by design area C. Clashes could be reviewed and approved in design area Cand reports could be run on either design area C or design area A. You could not review orapprove clashes in design area A until you had run interference detection on it.

Clashes that do not involve at least one component from design area C models 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 notlimited to these disciplines, but have been restricted to four disciplines to simplify thedescription: Piping, Equipment, Structural, or Raceway.

Consider for the purpose of this description that each discipline consists of three design areasfor each discipline. As an example, P1, P2, and P3 are design areas for Piping; E1, E2, and E3are 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 disciplinematrix must be defined as follows if the dual clash ownership option is to be enabled. Notethat each design area must be interference checked.

45

PDS Interference Checker/Manager User’s Guide - April 2002________________ Design Area Inter-Discipline Options in Matrix

P1 P-P, P-E, P-S, P-RP2 P-P, P-E, P-S, P-RP3 P-P, P-E, P-S, P-R

E1 E-E, E-S, E-RE2 E-E, E-S, E-RE3 E-E, E-S, E-R

R1 R-R, S-RR2 R-R, S-RR3 R-R, S-R

S1 S-SS2 S-SS3 S-S

This discipline matrix results in the minimum number of comparisons between models in theproject, while ensuring that all potential clashes are reported (that is, all possible combinationsof models have been checked).

With the dual clash ownership option enabled, clashes involving otherdesign areas of the same discipline as the primary design area will not bereported with the primary design area. For example, when checkingdesign area P1 in the previous example, although clashes between designarea P1 and design area P2 (and between design area P1 and P3) arereported, clashes that are internal to design area P2 and internal to designarea P3, and clashes between design area P2 and design area P3 are notreported.

With the discipline matrix described above, clashes reported in twodesign areas (that is, dual clashes), can only exist within the design areasof a single discipline. In other words, dual clashes can only be intra-discipline clashes.

The dual clash ownership option is more applicable where eachengineering department is responsible for its clashes and selected inter-discipline clashes. In other words, a centralized interference checkingorganization does not exist.

The user must decide which discipline departments will manage whichinter-discipline clashes. In the preceding example, the structuraldepartment, although responsible for internal structural clashes, is notresponsible for managing any inter-discipline clashes, while theelectrical department is only responsible for managing internal electricalclashes and structural-electrical clashes.

This setup has a restriction that both the piping design areas and theequipment design areas must be checked independently of each other,although the same department may be responsible for both disciplines.

46

3. Man

agem

ent

Exclusion of Interferences by Discipline________________

3.1.2 Exclusion of Interferences by Discipline

This command allows you to define a matrix of discipline combinations for each discipline forenvelope-building and interference-detection purposes. If you do not define a matrix for aspecific discipline, you can specify whether intra-disciplinary interference detection is turnedon for each discipline. You must select one of the three options for each Active Discipline thatyou define.

It is important to remember that all clashes found between all disciplinesduring an interference checker run, are owned only by the first design area thatfinds it unless dual-design area ownership has been specified.

The default mode is that no discipline matrix is defined and that the Intra DisciplineInterference Check command is enabled.

Why Define a Matrix?

Frequently, designers are specifically interested in potential clashes involving models of theirown discipline with models from one or more other disciplines. The Discipline MatrixInterference Check command allows designers the flexibility to check only for clashes thatfall within the scope of their responsibilities. See the following examples.

It is the responsibility of the people defining the interference matrices to ensure thatall possible discipline combinations are considered.

An Equipment designer may only be responsible for intra-disciplinary (Equipment againstitself) clashes and clashes involving Equipment and Structural models. This designer wouldneed to define intra-disciplinary checking for Equipment (Equipment against itself) andEquipment against Structural within the Equipment matrix.

47

PDS Interference Checker/Manager User’s Guide - April 2002________________ For the Raceway designer, most of the clashes that may be of concern are found between theStructural and Raceway disciplines. The Raceway matrix would limit envelope building andinterference detection to only those two disciplines for all Raceway design areas.

A Structural designer only concerned with clashes between and within Structural modelswould want to specify that only intra-disciplinary checking be performed for all Structuraldesign areas.

It is important not to confuse the function of the Intra Discipline Interference Checkcommand with a matrix that only performs intra-disciplinary checks for a discipline.The Intra Discipline Interference Check command not only checks the specifieddiscipline against itself and each model internally, it checks that discipline against allother disciplines and all disciplines against each other. The Intra DisciplineInterference Check command would not be appropriate in this case, since theStructural Designer only wants to find Structural against Structural clashes.

48

3. Man

agem

ent

Exclusion of Interferences by Discipline________________ A Piping designer may be interested in how Piping is going to affect all disciplines, includingPiping. In this case, a Piping matrix that includes all disciplines or the Intra DisciplineInterference Check command could be specified for the Piping Discipline.

It is important to remember that all clashes found between all disciplinesduring an interference checker run are owned only by the first design area thatfinds 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 whichdisciplines are considered for envelope building and interference detection for all design areaswithin 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 Equipmentmatrix. The Equipment designer is only responsible for intra-disciplinary clashes and clashesinvolving Equipment and Structural models. The matrix would be defined as follows:

49

PDS Interference Checker/Manager User’s Guide - April 2002________________ When a matrix is defined, the system only includes models that belong to the disciplinesinvolved in the matrix for interference checking. The responsible engineering discipline, asdefined 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 modelsdefined with the responsible engineering discipline of Equipment or Structural are included.

Once the envelopes have been built, the Interference Checker only checks the combinationsof 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 PrimaryDiscipline field to define the Active Discipline. Next, select a discipline from the PrimaryDiscipline field. In the Against Discipline field, the system highlights the disciplines that theprimary discipline will be checked against. Do this for each of the disciplines in the PrimaryDiscipline field in order to see the entire matrix for the active discipline. You can modify thematrix for any or all disciplines; then click Accept.

50

3. Man

agem

ent


Commands

Intra Discipline Interference Check — Allows you to define that the interference-detection process for the Active Discipline includes all possible combinations for thatdiscipline:

— Models within the specified discipline are checked against each other and arechecked internally.

— Models within the specified discipline are checked against models from all otherdisciplines.

— All models from all disciplines are checked against each other.

Select a discipline from the Primary Discipline field. This discipline becomes theActive Discipline. Select the Intra Discipline Interference Check command, andclick Accept. You can continue with this two-step process for as many disciplines asnecessary.

You should specify a matrix for the disciplines that do not require thissort of checking.

If a matrix is defined after this command has been specified, the systemoverrides this command and uses the matrix definition. If the command isspecified after a matrix has been defined, the system overrides the matrix anduses the command.

The engineering discipline, as defined in the Model Data Table (PDtable_113, column2) of the Project Control Database is used for determining the discipline of a model forthis command.

51

PDS Interference Checker/Manager User’s Guide - April 2002________________ No Intra Discipline Interference Check — Allows you to define that theinterference-detection process for the Active Discipline includes the following:

— Models within the specified discipline are not checked against each other and arenot checked internally.

— Models within the specified discipline are checked against models from all otherdisciplines.


Select a discipline from the Primary Discipline field. This discipline becomes theActive Discipline. Select the No Intra Discipline Interference Check command, andclick Accept. You can continue with this two-step process for as many disciplines asnecessary.

You should specify a matrix for the disciplines that do not require thissort of checking.

If a matrix is defined after this command has been specified, the systemoverrides this command and uses the matrix definition. If the command isspecified after a matrix has been defined, the system overrides the matrix anduses the command.

The engineering discipline, as defined in the Model Data Table (PDtable_113, column2) of the Project Control Database is used for determining the discipline of a model forthis command.

Discipline Matrix Interference Check — Allows you to define a discipline matrix foreach discipline. Select a discipline from the Primary Discipline field to define it as theActive Discipline. Then select a discipline from the Primary Discipline field to begindefining the matrix. From the Against Discipline field, select all of the disciplines tobe 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 clickAccept.

The responsible engineering discipline, as defined in the Model Data Table(PDtable_113, column 15) of the Project Control Database is used for determining thediscipline of a model for this command.

If prompted to... Do this:

Accept or Select Other OptionSelect one of the options to enable or disable intradiscipline checking and click Accept or select the matrixoption.

Select Discipline Select a discipline to be the Active Discipline.

52

3. Man

agem

ent


Accept Or Select Another DisciplineSelect all of the secondary disciplines to include in thematrix, and click Accept.

Once you have selected the Active Discipline, you cannot change it until youreactivate the Exclusion of Interferences by discipline command.

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 rangeare 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 theProject 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 NoteLibrary Manager command in the Reference Data Manager module.

This code list is delivered with the following definitions:

1 Undefined11 Preliminary12 Temporary21 Permanent

The model status for each model is recorded in the Model Data Table (PDtable_113) of theProject Control Database.

The range you specify on the Interference Checker Data form is checked against thenumbers in the Model Status code list (SN1605). The range you specify is recorded in theProject Control Data Table (PDtable_103) of the Project Control Database and is then used todetermine 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 modelsthat are defined with a model status of Preliminary or Temporary, using the delivered ModelStatus code list, would not be included during the interference building or checking process.

54

3. Man

agem

ent

Exclusion of Interferences by Model Status________________

The model status set for models is independent of the model status set for theDesignReview Label Builder.

Because the models that fall within the selected range are not included in any interferenceprocessing, they are not displayed when you select the Model option within the EnvelopeBuilder or for the Single/Pair Model Check option within the Interference Checker.

55


3.1.4 Equipment without/with Insulation

This command specifies that the Envelope Builder option either excludes or includesinsulation based on the equipment attribute value when creating interference envelopes forequipment models. By default, insulation is not added to interference envelopes created forequipment models.

56

3. Man

agem

ent

Construction Tolerances for Equipment Envelopes________________

3.1.5 Construction Tolerances for EquipmentEnvelopes

This command enables or disables construction tolerances for the equipment interferenceenvelope types displayed on the form. By default, the construction tolerances for the specificenvelopes shown on the form are not considered. Construction clashes representing disabledequipment envelope types are not reported. The envelope types are enabled when they havebeen selected.

57


58

4. En

velop

es

Envelopes________________

4. Envelopes

This section provides information on envelopes in the following order:

4.1 Envelope Builder — This option activates the Envelope Builder form. It is used tocreate envelope files for all of the models in the specified project, design area orindividual model. See Envelope Builder, page 60 for more information.

4.2 PDS Clash Detection with Non-PDS Models See PDS Clash Detection with Non-PDS Models, page 77 for more information.

4.3 Envelope Verification — This option activates the Envelope Verification form. Itis used to verify the integrity of the envelope file and to determine if the creationdates of the envelope files are recent or more recent than the revision dates of thecorresponding model files. See Envelope Verification, page 81 for more information.

4.4 Envelope Diagnostics — This option creates and allows you to reviewMicroStation-type graphics from the interference envelopes for a selected model in adesign file. Any previously-created graphics are deleted automatically from theenvelope diagnostics file before creating new envelope diagnostic graphics. SeeEnvelope Diagnostics, page 85 for more information.

59


4.1 Envelope Builder

This command activates the Envelope Builder form. It is used to create envelope files for allof the models in the specified project, design area or individual model.

All structure models must be propagated before you can use the EnvelopeBuilder to create envelope files for the models. Otherwise, the envelope-building process will fail and errors messages can occur.

Envelope File

An envelope file contains the basic geometric definition of whatever design object is in thedesign 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 themodel), location, name, and any other information that might uniquely identify a componentand its properties. Think of it as an envelope of information surrounding an element orelements.

The envelope building process and its results will vary depending on the waythe Interference Checker Data command is defined. The settings that affectenvelope building are shown below.






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. Thisstatus is not that of the clash in which the model is involved, but the status of the component’smodel. Models that are of a status that has been excluded using the Interference CheckerData command are excluded from the model building process.

The Interference Checker reports the model status of each component involved in a clash inthe interferences report named after the project or design area with the .int file extension. Seethe Interference Checker Output section of Understanding Interference Checking, page 25, formore information.

60

4. En

velop

es

Envelope Builder________________

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

COMPONENT INSULATION EXCLUSION DATA (PDtable_231)

The Component Insulation Exclusion Data is used to completely or partially exclude theinsulation of components on insulated lines with respect to interference checking.

For each piping component, piping specialty, or instrument component (excluding pipes) onan insulated line, the Piping Envelope Builder will search the Component InsulationExclusion Data Table on the basis of the following data to determine whether or not insulationshould be completely excluded from that component’s 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 component’scommodity name in the Component Insulation Exclusion Data Table using the preceding data.

If the piping commodity is defined in the exclusion table for those conditions, theapplicable insulation thickness will not be added to the component’s interferenceenvelope.

If the commodity name is not specified in the exclusion table for those conditions, thePiping Envelope Builder searches for the component’s model code using the same data.If a match for those conditions is found on the basis of model code, the applicableinsulation thickness will not be added to the component’s interference envelope.

Otherwise, the insulation thickness will be included in the component’s interferenceenvelope.

For piping specialties and instrument components, the Piping Envelope Builder searches forthe component’s model code in the Component Insulation Exclusion Data Table using thepreceding data. If the component is defined in the exclusion table for those conditions, theapplicable insulation thickness will not be added to the component’s interference envelope.Otherwise, the insulation thickness will be included in the component’s interference envelope.

61

PDS Interference Checker/Manager User’s Guide - April 2002________________ The piping segment data (heat tracing requirements, insulation purpose, and normal operatingtemperature) are determined on the basis of the piping segment that is associated with the firstconnect point of the applicable component.

You must rerun the Envelope Builder before changes to this table arereflected in the envelope file.

FLANGE INSULATION EXCLUSION DATA (PDtable_232)

The Flange Insulation Exclusion Data provides for partial exclusion of flange insulationthickness from the generation of interference envelopes.

The Piping Envelope Builder searches for matching data in this table for each bolted end ofeach piping component or instrument component on an insulated line that are determined tobe insulated.

The Piping Envelope Builder searches for matching data on the basis of the following data todetermine whether or not insulation should be excluded from the flange outside diameter ofthat bolted end of the component.

nominal piping diameter of the bolted end (range search)




If matching criteria is found in the exclusion table for these conditions, the applicableinsulation thickness will not be added to the flange outside diameter of the bolted end of thatcomponent’s interference envelope. Otherwise, the insulation thickness will be included inthe component’s interference envelope.

You must rerun the Envelope Builder before changes to this table arereflected in the envelope file.

The piping segment data (heat tracing requirements, insulation purpose, and normal operatingtemperature) are determined on the basis of the piping segment associated with the firstconnect point of the applicable component.

The Piping Eden modules for the interference envelopes that are to consider the partialexclusion of insulation from the flange outside diameter of a bolted end, must berevised to accommodate this option. If you do not change any or all of the PipingEden modules for the interference envelopes, this table will have no impact and theinterference 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 partiallyexclude construction tolerance from being added to interference envelopes. This feature onlyapplies to Piping vs. Piping construction tolerances.

62

4. En

velop

es


For each piping or instrument component, excluding pipes, the Piping Envelope Buildersearches Table 233 on the basis of the following data to determine whether the Piping versusPiping construction tolerance should be excluded from that component’s interferenceenvelope.

green NPD of the component (range search)

red NPD of the component (range search)

For piping commodities, the Piping Envelope Builder searches for the component’scommodity name in the Piping Construction Tolerance Exclusion Data Table using thepreceding data.

If the piping commodity is defined in the exclusion table for those conditions, theapplicable construction tolerance will not be added to the component’s interferenceenvelope.

If the commodity name is not specified in the exclusion table for those conditions, thePiping Envelope Builder will search for the component’s model code using the samedata. If a match for those conditions is found on the basis of the model code, theapplicable construction tolerance will not be added to the component’s interferenceenvelope.

Otherwise, the construction tolerance will be included in the component’s interferenceenvelope.

For piping specialties and instrument components, the Piping Envelope Builder searches forthe component’s model code in the Piping Construction Tolerance Exclusion Data Tableusing the preceding data. If the component is defined in the exclusion table for thoseconditions, the applicable construction tolerance will not be added to the component’sinterference envelope. Otherwise, the construction tolerance will be included in thecomponent’s interference envelope.

Defining Pipe-like Components

You can define up to 10 piping commodities to be treated as pipe-like components, such asbranch nipples or in-line nipple for interference detection. These components can be definedby commodity name in the Commodity Name Table of the Piping Job Specification TableLibrary. The following entries in the Commodity Name Table are reserved for this purpose.

63

PDS Interference Checker/Manager User’s 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 instrumentcomponents to be treated as pipe-like components for interference detection. Thesecomponents can be defined by model code in the Commodity Name Table of the Piping JobSpecification Table Library. The following entries in the Commodity Name Table arereserved 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 weldlocations in the PDS 3D model. These clearance envelopes can be used to define the spacingneeded for weld construction. The criteria used to generate these clearance envelopes aredefined in the Weld Clearance Table. Refer to the Weld Clearance Table section in theReference 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 weldswhich require a clash envelope based on the Weld Clearance Table. The system adds the clashclearance envelopes based on the following workflow:

1. The system uses the Piping Material Class (PMC) to retrieve the correct WeldClearance Table, as each Weld Clearance Table is named using the Piping MaterialClass, i.e. WELD_1C0031.

2. The system uses the weld type and the Nominal Piping Diameter of the weld as input tothe Weld Clearance Table to determine the radius increase and the overall lengthincrease for the graphic indicator at the weld.

64

4. En

velop

es


3. The clash envelope builder then uses the output of the Weld Clearance Table to drawthe cylinder representing the clash envelope.

The weld clearance envelopes are drawn as two shapes, one for each pipe, using theradius increase and overall length increase measurements.

Welds at model limits are a special case. For these welds, the envelopebuilder places half of the graphic indicator for the weld in each envelopefile.

The interference checker considers clashes involving weld envelopes as construction typeclashes. 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 informationeach time the envelope builder is run. Therefore, whenever the welds arerevised in the model, the Envelope Builder must be run prior to runningInterference Detection, to consider the potential impact of the new weld typeson the clash envelopes. The weld clearance envelopes will be inserted asadditional shapes with a hard-soft type denoting the shape as a constructiontolerance shape. The weld clearance is an additional shape at a connect pointof an existing component. Note that:

65

PDS Interference Checker/Manager User’s Guide - April 2002________________ The weld clearance shape is not considered a separate or independentcomponent.

The weld clearance shape has no entry in the database.

Interference reporting involving weld clearances will record aconstruction tolerance clash with the piping component the weldclearance surrounds, rather than a with a (nonexistent) weld clearanceentity.

The envelope builder does not generate weld construction tolerance shapes attap locations.

Interactive clash checking in Piping Design will not perform weld constructiontolerance checking.

Mechanics

When the envelope option is anything other than Project or Model, a volume is required. Thisvolume can be pre-defined by the user or calculated by the software using the models in thedesign area. Models in the project that overlap are checked. The envelope file determinesoverlap 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 inthe PDtable_113 of the project database. If no date is stored in the database, the time from thephysical model file is used for the comparison. Missing envelope files are recognized as out ofdate by the software.

For structural models, the propagated file time, if it exists, is checked against the envelope filetime. If no time is stored in the database for the propagated file, the time of the lastmodification to the propagated file is checked against the envelope file time. If the envelopefile is older, the envelope file will be created.

The propagated file times for structural models are updated only when PDS isused to create or regenerate the propagated file. Changing anything in themodel outside of PDS does not update the times stored in the PDS the projectdatabase. Therefore, the Envelope Builder and Interference Checker will notrecognize that the envelope file is out of date if updates were made outside ofPDS.

If there are model components that are within the same volume represented by the selecteddesign area but are not associated with that design area, the Envelope Builder does one of thefollowing:

If the interference envelope is up-to-date for models residing within the volume but notincluded in the selected design area, the Envelope Builder does re-create interferenceenvelopes.

66

4. En

velop

es

Envelope Builder________________ If a model or any of its components reside within the volume but not included in theselected design area and the interference envelope for that model either does not exist oris not up-to-date, the interference envelope is recreated.

The piping envelope builder does not create insulation envelopes forinternal refractory. The range of values, 30 through 39, for insulationpurpose is interpreted by the piping envelope builder as internalinsulation.

Application Considerations

For the Model option, the system selects the correct interference envelope builder for eachmodel’s discipline, including piping, equipment, structural, raceway, HVAC, andPLANTGEN, so envelope files can be created in the Interference Management environmentrather than within each discipline’s more specific application. For the architectural and user-defined disciplines, the system uses a generic envelope builder.

The discipline is determined by the default discipline of the model unless a differentApplication Type for that model has been specified. The Application Type is defined in theProject Environment Manager on the Create Model Data form within the ProjectAdministrator. This field automatically contains the default discipline of the model but canbe changed. For instances, a piping model for circular HVAC ducting can be treated as anHVAC model for clash checking when the Application Type for that model is defined asHVAC.

Cutbacks performed in FrameWorks will not be reflected in the envelope.PD_Clash will not report clashes in any situation where the memberlines havea 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 linematches the outer line of the solid, no clash will be reported.

For more information on Application Types, see the Create Model section ofthe Project Administrator Reference Guide.

67


Commands

Project — Creates envelope files for all of the models in the project. See the CreateProject Envelope Files, page 69, for more information.

Piping Design Area — Creates envelope files for all of the models in a piping designarea. See the Piping Design Area, page 70, for more information.

Piping Design Area Predefined Volume — Creates envelope files for all of themodels in a design area with the predefined volume defined in the project database. Seethe 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 theDesign Area, page 73, for more information.

Design Area Predefined Volume — Creates envelope files for all of the models in adesign area with the predefined volume defined in the project database. See the DesignArea Predefined Volume, page 74, for more information.

Model — Creates an envelope file for a single model. See the Model, page 76, formore 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 fieldsand allow you to delay submission until a more convenient time.

Include User Defined Disciplines/Exclude User Defined Disciplines — Specifieswhether to generate envelope files for models in user defined disciplines whengenerating PDS envelope files.

68

4. En

velop

es

Create Project Envelope Files________________

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. Itcreates a file with a .env file extension where the model resides for each piping, equipment,structure, HVAC, or electric model file in the project.

69


4.1.2 Piping Design Area

This option activates a list of piping design areas available for envelope creation. TheEnvelope Builder creates envelope files for all of the models associated with the selectedpiping 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 DataManager 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

4. En

velop

es

Piping Design Area________________

Before using this command

Create a design area with a specific volume with the Create Design Area Data option in theProject Environment Manager.

71


4.1.3 Piping Design Area Predefined Volume

This option activates a list of piping design areas with predefined volumes available forenvelope creation. The Envelope Builder creates envelope files for all of the modelsassociated with the selected design area. The system also displays the predefined volume forthe selected design area.

The Envelope Builder only builds envelopes for the models that are includedin 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 areabut outside of the predefined volume.


See the Exclusion Tables section in the Envelope Builder section and Reference DataManager 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. En

velop

es

Design Area________________

4.1.4 Design Area

This option activates a list of design areas available for envelope creation. The EnvelopeBuilder 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 modelwhen creating interference envelopes. However, this requires that the model managementdata is loaded for the sparse structural models through the Project Environment Manager.

73


4.1.5 Design Area Predefined Volume

This option activates a list of design areas with predefined volumes available for envelopecreation. The Envelope Builder creates envelope files for all of the models associated with theselected design area. The system also displays the predefined volume for the selected designarea.

The Envelope Builder only builds envelopes for the models that are includedin 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 areabut outside of the predefined volume.

The Structural Envelope Builder uses the sparse version of the structural model when creatinginterference envelopes. However, this requires that the model management data is loaded forthe sparse structural models through the Project Environment Manager.

Field Descriptions





You must have used the Create Design Area Data option of the Project EnvironmentManager with the Create Interference File option set to On to predefine the volume.

74

4. En

velop

es

Design Area Predefined Volume________________

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 AreaPredefined Volume envelope builder command. Refer to the Project Administrator(PD_Project) Reference Guide for more details on DVCS.


Create a Clash discipline, and then create a design area within the Clash discipline. Refer tothe Project Administrator (PD_Project) Reference Guide for instructions on creating theClash discipline and design area.

75


4.1.6 Model

This option activates a list of disciplines, piping design areas, and models available forenvelope creation. When you select the By Model option, the envelope builder will build anenvelope for any model selected, regardless of date.

76

4. En

velop

es

PDS Clash Detection with Non-PDS Models________________

4.2 PDS Clash Detection with Non-PDSModels

PD_Clash can be used to run interference checks on models that are not created with PDS. InPDS, a project can define up to ten engineering disciplines on which clash detection can berun. Under each discipline, areas, and models within the areas, are created and used forinterference 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 areuser-definable, that is; you can define up to four additional, non-PDS disciplines that can beused 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, forDesignReview 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 thatyou 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 VolumeCoordinate System. If you need to use the Clash discipline in an existingproject that already uses all four user-defined disciplines, you must convertone user-defined discipline to a Clash discipline.

Refer to Design Area Predefined Volume, page 74 and the ProjectAdministrator (PD_Project) Reference Guide for more information on theClash discipline.

77

PDS Interference Checker/Manager User’s Guide - April 2002________________ For the first six predefined disciplines, as well as PLANTGEN, PDS calls specific routines forclash detection based on their data structures and requirements. For the four user-defineddisciplines 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 hassome limitations which are discussed later in this section.

The following disciplinesuse specific routines tobuild envelope files:

The following disciplinesuse generic routines tobuild envelope files:

1. Piping2. Equipment3. Structural4. HVAC5. Raceway6. Architectural7. PLANTGEN8. User-defined9. User-defined10. User-defined

Creating envelope files in user-defineddisciplines

The generic envelope builder creates envelope files for user-defined discipline models withinthe project or selected area automatically if the Include User Defined Disciplines toggle isset on the Envelope Builder form. You can also select user defined disciplines on the DesignArea 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 Holeelement has the HOLE bit set. Otherwise, the envelope may notgenerate 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

4. En

velop

es

PDS Clash Detection with Non-PDS Models________________ 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 resultinggraphic could otherwise be created as a projected solid. In such cases, the system usesthe projected solid to create the envelope. One example would be a cell containing 6shape elements comprising the faces of a cuboid.

In this case, the envelope builder would create an envelope based on the projectedcuboid solid that the cell resembled.

Another example would be 2 hexagonal shapes connected by 6 rectangular shapes, sothat the cell resembles a projected hexagon.

In this example, the envelope builder would create an envelope based on the projectedhexagonal 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 systemcreates envelopes for these cells using a projected solid of minimum thickness (20UORs) 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.

Limitations

For the PDS-supported model types, PDS has access to either database records orMicroStation user data. This allows PDS to track clashes for reporting purposes, associatingnames with the clashing elements in reports and plots, and for storing the clash approval statusof elements (for example, if a clash is deemed acceptable by you). This type of information isnot available for user-defined disciplines (exclusive of PLANTGEN). Therefore, the genericenvelope builder uses a pseudo-occurrence number for the clashing item. This number is

79

PDS Interference Checker/Manager User’s Guide - April 2002________________ made up of the byte and sector location of the MicroStation element. Also, no name label canbe 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 movedin the MicroStation design file (the byte/sector number position, NOT thephysical/geographical location in the model), PDS clash detection does not recognize thepreviously reported clashing item as the same item. It clears the old clash (since the item atthe previous byte/sector position is no longer there or the same), and considers the clash a newone. This repositioning of the MicroStation elements (byte and sector number position)occurs when items are deleted, revised with certain commands, and when the model iscompressed.

This means that if you approved a clash involving an item in a non-PLANTGEN, user-defineddiscipline, and the byte/sector number for that item was changed, the clash will be reportedagain, as a new clash, and you will need to reapprove it.

80

4. En

velop

es

Envelope Verification________________

4.3 Envelope Verification

This option activates the Envelope Verification form. It is used to verify the integrity of theenvelope file and to determine if the creation dates of the envelope files are up to date with thesystem dates of the corresponding model files.

A log file is created automatically if any errors are found in any of the interference envelopesand a Warning dialog box appears informing you of the existence of the file. The existenceof this file usually indicates problems with the discipline’s envelope builder. It is created inthe directory and network address specified for Interference Management reports. It is namedafter the project or design area number with a option is displayed for immediate review ofproblems when they are found.

As a means of isolating problems between the discipline’s Envelope Builder and theInterference 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 applicablecomponent’s interference envelope.

The range of a component’s interference envelope to be contained within the range ofthe applicable model.

Interference envelopes represented as a hole or void are to be either a cylinder, notincluding 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. Thisreport entry includes the component’s primary description and the range of eachsubcomponent. The range is included since the subcomponents’ ranges must overlap tobe connected.

Components which have the same linkage within a model do not have uniqueidentification. This situation is reported as an error and usually indicates that one of thefollowing problems exists:

— The MicroStation Copy command was used to copy a component in the model.

— The discipline’s model creation product has created a component which does nothave a component identification that is unique within that model.

— The discipline’s Envelope Builder has created a component’s interference envelopewith an incorrect component identification such that it is not unique within thatmodel.

Use the Envelope Builder option to update the envelope files that are in theNeed to be Updated category. The Envelope Builder updates only thoseenvelope files which are out of date.

81


It is recommended that you verify that all envelope files are available prior torunning the Interference Checker. If an envelope is unavailable for a clash session,and clashes involved with this envelope file have already been approved, theseclashes 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 selectthe design area to be verified. All of the envelope files within the specified pipingdesign area are processed.

Piping Design Area Predefined Volume — Displays a list of piping design areas withpredefined volumes and allows you to select the design area to be verified. All of theenvelope files within the specified piping design area are processed.

Design Area — Displays a list of design areas and allows you to select the design areato 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 predefinedvolumes and allows you to select the design area to be verified. All of the envelope fileswithin the specified design area are processed.

The system places each of the files for the selected option in one of the three status fields asdisplayed and described below:

82

4. En

velop

es

Envelope Verification________________

Status Fields

Up to date — The interference envelope is up-to-date with the model. The modelnumber is displayed.

Needs to be Updated — The interference envelope is not up-to-date with the modeland must be re-created. Either the model has been reviewed or revised since theinterference 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 filegeneration date are displayed.

Error Mounting File System — An error occurred while mounting the file systemwhere the model resides. The model number is displayed.

Does NOT Exist — An interference envelope has never been created for the model.

Commands

Display Error Report — This option displays the found during the EnvelopeVerification process.

83


84

4. En

velop

es

Envelope Diagnostics________________

4.4 Envelope Diagnostics

This option creates and allows you to review MicroStation-type graphics fromthe interference envelopes for a selected model in a design file. Thisgenerated file has a .til extension. Any previously-created graphics aredeleted automatically from the envelope diagnostics file before creating newenvelope diagnostic graphics.

Construction tolerance envelopes are not included in thegraphics display.

About this command

The graphics created by the Envelope Diagnostics command for theinterference envelopes match the colors of the interference markers defined inthe interference marker file.

Error File (.evd)

Any discrepancies found during this verification process indicate problems in the applicableEnvelope Builder and will be reported in a file in the c:\temp directory named after the modelwith a .evd file extension.

This report also contains a list of any pipe-like components within a model. It will excludeany piping or instrument components on the basis of the Piping Construction ToleranceExclusion Data Table, PDtable_233, of the Material Reference Database defined using theReference Data Manager.

Also, as a means of isolating problems between the Envelope Builder and the InterferenceChecker, the Envelope Diagnostics option verifies the following conditions and recordserrors in the .evd file:

The range of a shape, to be completely contained within the range of the applicablecomponent’s interference envelope.

The range of a component’s interference envelope, to be completely contained withinthe range of the applicable model.

Envelope shapes representing holes or voids must be cylinders (right or skewed) orprojected 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 geometricallyconnected–do not have overlapping ranges. This report entry includes the component’sprimary description and the range of each subcomponent. The range is included sincethe subcomponents’ ranges must overlap to be connected.

85

PDS Interference Checker/Manager User’s Guide - April 2002________________ Components which have the same linkage within a model do not have uniqueidentification. This situation is reported as an error and usually indicates that one of thefollowing problems exists:

— The MicroStation Copy command was used to copy a component in the model.

— The discipline’s model creation product has created a component which does nothave a component identification that is unique within that model. If this problemoccurs, it should be reported to Intergraph immediately.

— The discipline’s Envelope Builder has created a component’s interference envelopewith an incorrect component identification such that it is not unique within thatmodel. 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 graphicsenvironment to review the file.

Review Diagnostic File — Review a previously created diagnostics file (displays onlyif a diagnostics file is available). Also, the envelope display includes model graphicsfrom the reference file that is attached.

Envelope display will not include construction tolerances.

86

4. En

velop

es

Envelope Diagnostics________________


Select Discipline Select the discipline for the envelope to be processed,and click Accept.

Select Design Area Select the design area for the envelope to be processed,and click Accept.

The system displays the available models for theselected discipline and design area.

Select Model Select the model for the envelope file to be processed,and click Accept.

The system displays the available models for theselected discipline and design area.

87


Accept To Create Diagnostics FileSelect an option to either create or create and review thediagnostics file and click Accept.

Never alter the model_name.dgn file.

88

5. Interferen

ces

Interference Checking________________

5. Interference Checking

This section provides information on interference checking, including information on thePiping Clash Check Command from the Piping Design module in the following order:

5.1 Interference Checker See Interference Checker, page 90 for more information.

5.2 Piping Clash Check Command See Piping Clash Check, page 108 for moreinformation.

89


5.1 Interference Checker

This command activates the Interference Checker form. It checks for interference clasheswithin the specified project volume. You can process the entire active project, a design area, asingle model, a pair of models, or a specified volume.

The interference detection process and its results will vary depending on thesettings defined on the Interference Checker Data form. These settingsinclude:






See Interference Checker Data, page 41, for more information.

Exclusion Tables


See the Reference Data Manager Reference Guide for detailed information on each of thefollowing 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 moreinformation on how to use the Commodity Name Table in the Piping Job Specification TableLibrary.

If you revise these tables after clashes have been reported or excluded, the system does thefollowing:

If selected components are added to a table, the Interference Checker eliminates thosefalse clashes as if you had revised them by revising the piping model itself.

If selected components are removed from the table, the Interference Checker reportsthose clashes as if they had never been excluded.

90

5. Interferen

ces

Interference Checker________________

Changes to these tables are not reflected in the results of the InterferenceChecker until the interference envelopes have been re-created and interfencedetection has been rerun.

Clash Category Considerations

The Interference Checker does not report hard vs. soft clashes of piping components whenall of the following conditions are met:

Both components are in a piping model by default and by assigned responsiblediscipline. Also, if both components are in piping models where the assignedresponsible 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 singlepiping component.

The clash is not due to an interference envelope which represents a valve operator ofone of the two piping components.

The Interference Checker does not report hard vs. construction clashes between a pipingsupport and a horizontal structural beam, in the same manner as for other piping, when thepipe 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 nozzleconnect point locations are added before false clashes will be eliminated.

Two equipment envelopes of the same type, as listed below, are clashing.

access soft vs. access softaccess hard vs. access hardmaintenance soft vs. maintenancemaintenance hard vs. maintenanceoperating soft vs. operating softoperating hard vs. operating hardsafety soft vs. safety softsafety hard vs. safety hard

91


You must re-create equipment interference envelopes so that the envelope typeis added to the definition of the equipment interference envelopes before falseclashes will be eliminated.

Application Type

The Interference Checker considers the discipline of a model to be that which is defined inthe Application Type field on the Create Model Data form in the Project Administrator. Ifthe Application Type is not specified, the discipline in which the model was created is usedfor interference processing.

Mechanics

The type of option that you select for interference processing, such as the Project or DesignArea, is recorded in the clash management data in the Project Control Database. If AccessControl 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 recordsthat volume. If the volume is not predefined, the system-calculated volume for the project ordesign area is recorded in the clash management data.

Interference processing requires the following values for the standard note type 1208 in theproject’s Standard Note Library.

o 1 unknowno 2 project modeo 3 design area modeo 4 predefined volume mode

The Volume Filter toggle requires the following values for standard note type 1209 in theproject’s Standard Note Library.

o 1 volume filter is inactiveo 2 volume filter is active

Interference processing requires that the Clash Job Data Table, PDtable_131, in the ProjectControl Database maintains this data in the following columns:

o clash_check_option shorto volume_filter_option shorto volume_low_x integero volume_low_y integero volume_low_z integero volume_high_x integero volume_high_y integero volume_high_z integer

92

5. Interferen

ces


Processing Time

Running the Interference Checker for an entire project takes considerably longer than runningit for a design area. If the project workload is being shared, one of the design area optionswould be the most efficient. The design area options are less time consuming and createindividual sets of reports rather than one set of reports for the entire project. Adhere to usingeither the Project option or one of the Design Area options for the life of the project for themost consistent results.

When you initiate a batch process using the Interference Checker, the integrityof the marker model is verified. If the marker model is not valid (for instance,if it is copied from the project’s seed model using File > Copy), a dialog boxappears indicating that the marker file should be re-created. (See InterferenceManagement Data, page 180, for more information.) This must be done inorder to continue. No Interference Management data is lost as a result ofupdating the marker model. Also, if the marker file is already in use, thesystem displays a lock status message.

Commands

Project — Performs clash checking for all of the envelope files defined for the projectand creates interference, difference, and batch queue error reports.

Piping Design Area — Activates a list of piping design areas available for clashchecking. After a piping design area has been selected, the system defines a volume thatencompasses all models within the selected piping design area. It then performs aninterference check on all models and parts of models, including models from all otherdisciplines, that are in the defined volume. To specify a larger or smaller volume for a

93

PDS Interference Checker/Manager User’s Guide - April 2002________________ single interference check, set the Volume Filter toggle to On after selecting a pipingdesign area.

Piping Design Area Predefined Volume — Activates a list of piping design areas withpredefined volumes available for clash checking. After a piping design area has beenselected, the system uses the predefined volume that has been specified by using theProject Environment Manager. This volume is displayed on the form. The systemthen performs an interference check on all models and parts of models, includingmodels from all other disciplines, that are in the predefined volume.

The Interference Checker does not include models that are in the selected piping designarea that do not fall within the predefined volume.

Design Area — Activates a list of design areas available for clash checking. After adesign area has been selected, the system defines a volume that encompasses all modelswithin the selected design area. It then performs an interference check on all modelsand parts of models, including models from all other disciplines, that are in the definedvolume. To specify a larger or smaller volume for a single interference check, set theVolume Filter toggle to On after selecting a design area.

Design Area Predefined Volume — Activates a list of design areas with predefinedvolumes available for clash checking. After a design area has been selected, the systemuses the predefined volume that has been specified by using the Project EnvironmentManager. This volume is displayed on the form. The system then performs aninterference check on all models and parts of models, including models from all otherdisciplines, that are in the predefined volume.

The Interference Checker does not include models that are in the selected design areathat do not fall within the predefined volume.

This command can be used in conjunction with the Clash discipline to check areasusing the Design Volume Coordinate System. See Design Area Predefined Volume,page 74 and the Project Administrator (PD_Project) Reference Guide for moreinformation.

Single/Pair Model Check — Activates a form which allows you to select a singlemodel or a pair of models to be re-checked. It also allows you to define the disciplineand design area ownership for each run of this option.

This option can only be used if interference checking has already beenrun on the design area you will select for ownership of clashes. It isused to recheck items that have been revised to avoid rerunning an entirearea.

You can specify multiple pairs or single models to be checked. An individual report andaccompanying 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 numberfor the applicable models.

The Interference Approval Manager displays the results of the clashes foundaccording to the design area ownership specified for each single or pair. The results areappended to previous interference detection for the design area.

94

5. Interferen

ces


Use the Select Design Area Ownership for Clashes command to define ownership fora 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 beincluded in the interference checking process. You can select one or two models to beincluded.

The pair option only reports interferences that exist between an item inmodel A and an item in model B. It does not check for interferences thatare internal to model A or internal to model B.

Plot Clashes — Plots interference clashes based upon search criteria usingInterference Management data. The clashes are plotted as they are found during theInterference Checking process and are given a unique clash ID and plot number withinthe group of interference clashes being plotted. See Plot Clashes, page 98, for moreinformation.

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 andallow you to delay submission until a more convenient time.

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, andElevation for one run of the Interference Checker.

Only the clashes found within the range of the Volume Filter areavailable for review after an interference detection run using this option.All clashes are again available for review when interference detection isrun for a design area or for the project.

95

PDS Interference Checker/Manager User’s Guide - April 2002________________ Default Report Active / User Defined Interference Report — Defines that either thedefault report or a user-generated report is created during interference checking. Thedefault 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 pointin the provided field, the system displays a list of all of the reports you have createdthrough the Interference Report Manager. The report you select is generated duringthe interference detection process.

If you have not defined a report record consisting of an existing format file andan existing discrimination data file, no reports will be displayed for you toselect. You must define the reports first.

If you select a user-defined report and Access Control is enabled, the initialsfor 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, plotsare generated automatically during report creation. Clashes are plotted in theorder in which they are reported. The Plot Clashes command should not beused 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 toclash detection.

Errors found during verification stop the batch job, and must becorrected before clash detection can be run. Refer to Appendix A for alist of Envelope Verification Errors.

Print / Delete — Submits the generated report output file to the specified print queueand deletes the output file.

Print / Save — Submits the generated report output file to the specified print queue andsaves the output file.

Save — Saves the output file without printing.

96

5. Interferen

ces



Use the Verify Data Integrity of Model diagnostic command to check all pipingmodels. Overlapping pipelines are reported by this check, not by the InterferenceChecker.

Additionally, you should run the Verify Data Integrity of Modelcommand in FrameWorks Plus to detect overlapping structural membersbefore you create envelope files for structural models.

Use the Interference Checker Data command to define the mechanics of theinterference checking process.

Use the Envelope Verification command to make sure that the envelope files are up todate.

Equipment must contain at least one datum point for a clash with the equipmentenvelope to be reported.

97


5.1.1 Plot Clashes

This command is used to plot interference clashes based upon search criteria usingInterference Management data. The Interference Checker must be run at some point beforeusing this option.

If a user-defined report accesses a format file containing the DZ10 index, plotsare generated automatically during report creation. Clashes are plotted in theorder in which they are reported. The Plot Clashes command should not beused 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 clashesbeing 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 inthe Standard Note Library, otherwise the long version is used.

The models categorized as Model A and Model B. Clashing components arecategorized as Model A and Model B in the order of their clash precedence, which ishard, soft, and construction, respectively.

When a clash is found between components which both containinsulation where each component could be clashing with the othercomponents’ insulation, the system randomly defines one component asModel A, hard, and the other as Model B, soft.

The design area number corresponding to the model number for each componentinvolved in the clash.

The previous item requires a change to the format of the clash plotborder for the 5.0 release. You must copy the clash plot border,borderifc.dgn, from the \pd_clash\border product directory into yourproject directory. This copy is not part of the Automated UpgradeProcess because you may not wish to override your existing border file.

You must also copy the ifc.i file into your project directory for plottingpurposes. It is delivered but the copy is not part of the AutomatedUpgrade 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

5. Interferen

ces

Plot Clashes________________ The Review Date from the Clash Review History Data Table (PDtable_135).

The Review Comments from the Clash Review History Data Table (PDtable_135), asmany as 100 characters to the pertinent construction tolerance value, if applicable.

99


100

5. Interferen

ces

Plot Clashes________________

Detailed Plots

Detailed clash plots include the model representation in addition to the interference envelopesfor components other than the two components involved in the clash.

All components falling within the clash plot’s volume and existing in the two applicablemodels is displayed with the two clashing components and the corresponding interferenceenvelopes.

The envelope graphics of the two clashing components are plotted with weight of 4 anda style of dashed.

The model graphics of the two clashing components are plotted a weight of 2 and astyle of solid.

The model graphics of the other components are plotted with a weight of 0 and a styleof solid.

101


102

5. Interferen

ces

Plot Clashes________________ There is a primary discipline called the Action Discipline for every model combination. TheAction Discipline is defined using the Project Administrator and indicates the jobresponsibility or who should take "action" to resolve the clash. The Action Discipline is at thetop of each clash so that clashes may be easily sorted and routed to the person responsible forthe clashes in that discipline.

When a plot queue is selected, it is used for all graphic interference clashreports that are being plotted in one batch process.

Commands

Unplotted Clashes — Specifies that only unplotted clashes of the specified types beplotted.

Unapproved Clashes — Specifies that only unapproved clashes of the specified typesbe plotted.

Unreviewed Clashes — Specifies that only unreviewed clashes of the specified typesbe plotted.

Select Markers From List — Displays a list of markers for the clash types selected sothat you can specify which clashes are plotted.

103


Select Single Marker / Range of Markers — Allows you to select a single marker ora range of markers.

Default Clash Plots / Detailed Clash Plots — Submits either default or detailed clashplots. 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 foryou to specify the submission time.

104

5. Interferen

ces

Interference Checker Output________________

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

Interference Report

This report contains all unapproved clashes, sorted first by model combinations then by thetype of clash. For instance, all clashes detected between model A and model B would begrouped together. A synopsis of the clashes is included at the beginning of the report; itindicates the number of clashes found with each pair checked. This report also includes themodel 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 notof the clash.

These reports are named after the project or design area with a .int file extension and arecreated each time the checker is run. The interference report is created on the workstation orserver in the directory from which the Interference Checker was submitted unless otherwisespecified using the Interference Report Management Data option.


Date: 3-Jun-94 Time: 10:41:35

Model ’A’ Design File Name: bccopy

105



PDS Interference Clashes

Hard/Soft Clashes


__ _________ _____ ___ _______ _______ _______

82 GAT 3 6815819 E 1307’ 11 5/16" PlaN 386’ 3 5/8" Plant El 15’ 6" Plant

W38bc0311-4IN-2C0032-HF-2 "

Not approved


W38bc0311-4IN-2C0032-HF-2 "

Not approved

83 FWN 3 6815821 E 1307’ 11 5/16" PlaN 386’ 3 5/8" Plant El 14’ 10 3/16" Plan

W38bc0311-4IN-2C0032-HF-2 "

Not approved


W38bc0311-4IN-2C0032-HF-2 "

Not approved

84 PIPE 5 6815768 E 1311’ 2 5/16" PlanN 401’ 3 5/8" Plant El 18’ 8 1/4" Plant

W38bc0311-4IN-2C0032-HF-2 "

Not approved

84 FWN 3 6815855 E 1310’ 8 3/4" PlantN 401’ 3 5/8" Plant El 17’ 0" Plant

W38bc0311-3IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved

87 PIPE 5 6815847 E 1311’ 2 5/16" PlanN 441’ 3 5/8" Plant El 18’ 8 1/4" Plant

**W38bc0311-4IN-2C0032-HF-2 "

Not approved

87 FWN 3 6816091 E 1310’ 8 3/4" PlantN 441’ 3 5/8" Plant El 17’ 0" Plant

**W38bc0311-3IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

106

5. Interferen

ces

Interference Checker Output________________

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved


**W38bc0311-4IN-2C0032-HF-2 "

Not approved

107


5.2 Piping Clash Check

This command is part of the Piping Design module but has been included here to provide amore complete scope of PDS interference information.

This command enables you to check a piping line for interferences immediately aftercompleting the line. It automatically creates interference envelopes in the workstation’smemory for any piping in the active model defined by the selected pipeline. It checks anyattached reference models for which interference envelope files have been created previously.It also reports any reference models for which interference envelopes have not been createdpreviously.

The results of this interactive clash checking is not maintained as a part of the InterferenceManagement data. However, you can use the Piping Clash Review option to review theclashes detected by this command.

This command does not affect the interference envelopes created by theInterference Manager’s Envelope Builder.


Identify Pipeline Snap to a segment or locate a component to identify thepipeline to be processed.

Accept to Check Pipeline Click Accept to process the identified pipeline or clickCancel to reject the pipeline.

The system creates interference envelopes for theselected pipeline and checks the volume defined by thepipeline for possible clashes. When finished the systemdisplays the number of clashes detected.

Identify Pipeline or Select Review OptionIdentify another pipeline as outlined above.

— OR —

108

5. Interferen

ces

Piping Clash Check________________ Select the Piping Clash Review option to review thedetected clashes.

Select Review Option Select one of the options to review the clash.

Commands

Select View — Select this option and identify the screen view to display the activeclash.

Restore View — Select this option to restore the active view(s) to the initial viewingparameters for the clash being checked.

Previous/Next Marker Number — Select either of these options to review thenext/previous marker. The system updates the window coordinates about the clash inthe selected view.

109


110

6. Ap

pro

val

Interference Managing________________

6. Interference Managing

This section provides information on interference managing, including information on thePiping Designer interference reviewing function, in the following order:

Interference Approval Manager See Interference Approval Manager, page 112 formore information.

Interference Management Data See Interference Management Data, page 180 formore information.

Piping Clash Review (in the PD_Design Module) See Piping Clash Review (in thePD_Design Module), page 181 for more information.

111


6.1 Interference Approval Manager

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

About this command

When you activate the Interference Approval Manager and select an option, the applicablemarker file is verified. If the marker file is not valid (for instance, if it is copied from theproject’s seed file using File Manager), a dialog box appears indicating that the file should bere-created. This must be done in order to continue. See Interference Management Data, page180, for more information. No Interference Management data is lost as a result of updatingthe marker file. Also, if the marker file is already in use, the system displays a lock statusmessage.

Commands

Project — Reviews and revises interferences for the active project.

Piping Design Area — Reviews and revises interferences for a selected piping designarea.

Design Area — Reviews and revises interferences for a selected design area.

112

6. Ap

pro

val

Interference Approval Manager________________


You must have run the Interference Checker for the volume to be reviewed or revised.

113


6.2 Approval Manager Commands

These commands allow you to review and approve clashes, review clashhistory, 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), reenterPD_Clash, then run the report.

Commands

Approve — Edits and reviews existing clashes, manipulates views, and approves changes toexisting 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. SeeChecker Run Dates, page 121.

Review Clash History — Displays all available information about the clashes. See ReviewClash History, page 122.

Create Unapproved Clash Report — Creates a report containing all clashes found and issorted by model combination. For more information, see Create Unapproved Clash Report,page 124.

Checker Reference Data — Reviews Checker Reference Data defined by the Project DataManager module of Project Administrator including a review of the action and responsibledisciplines. 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. Ap

pro

val

Approve________________

6.2.1 Approve

This command activates the Interference Approval Manager form. It is used to edit andreview existing clashes, manipulate views, and approve changes to existing clashes.

The Action Discipline toggle is only displayed when clashing models are notfrom 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 withthe Checker Run Dates option. For more information, see Checker Run Dates, page121.

Responsible User: — Displays the code number of the responsible user. This field isfilled in if access control is set on the project and will be the userid that was keyed in toaccess the project through access control. Once the clash is approved, the user’s initialsare written to the Clash Review History data table, PDtable_135.

Clash Type — Describes the current type of clash. This field is the one above theReview Unapproved/Approved Clash toggle.

Marker Number — Displays the number of the current clash. Select a marker numberwith the left and right arrows, select the field and key in a marker number, or select theKeyin Marker Number option and key in a marker number.

Model and Area Name — Displays the names of the models and corresponding designareas that have components involved in a clash.

115

PDS Interference Checker/Manager User’s Guide - April 2002________________ Item — Displays descriptions of the clashing components in the Item fields which arelocated below the Model fields. The system accesses the user-defined labels in theLabel Description Library to create: the primary description, which is displayed on thetop line with a limit of 20 characters; and the secondary description, which is displayedon the bottom line and has a limit of 40 characters. These descriptions are defined withthe Clash Management Labels option on the Create Label Data form in theReference Data Manager.

Comments: — Displays existing comments about the active clash. Select the field, andkey 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 adisplay list of possible clash types.

Clash Status — Approves or unapproves the current clash. Depending on the status ofthe displayed clash, the Unapprove Clash, Approve Real Clash or the Approve FalseClash option will be highlighted. For more information, see Approve From List, page119.

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

Action Discipline: — Displays the Action Discipline for every model combinationunless both models are from the same discipline. The Action Discipline is definedusing the Project Administrator and indicates the job responsibility or who shouldtake action to resolve the clash. This toggle only appears if there are two differentdisciplines involved in a clash.

Select View — Zooms in and updates selected views. Select the option and thenselect the views that you want to update.

Plot Active Clash — Plots the clash in the active view immediately, placing thetemporary plot files in the c:\temp directory. It either plots default or detailed clashesdepending on the way the toggle has been defined using the Project Data Manager

116

6. Ap

pro

val

Approve________________ module of Project Administrator. You can review this setting using the CheckerReference Data command.

The system displays the Plotter Queue list, showing the available plotters. Select aplotter from the list and click Accept to plot the clash.

Envelope Diagnostics — Creates MicroStation-type graphics from the interferenceenvelopes for a selected model in a design file. For more information see the EnvelopeDiagnostics, 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 systemautomatically updates the active window.

Highlight Clash — Highlights the active clash in every view. Select the option, andthe system automatically highlights the active clash in grey.

Keyin Marker Number — Defines the marker number of an existing clash. Select theoption, and key in a marker number in the Marker Number field.

Without Reference Models/With Reference Models — Defines that the clash displaybe with or without reference models. Without Reference Models is the default andshows the clashing elements only. With Reference Models displays the reference files(for example the structural model file and the raceway model file) and highlights theclashing members.


Select Clash Type Set the toggle to the appropriate setting and select theclash types to be approved.

Select Review Option Use one of the options described above to edit orexamine the existing clashes.

117


6.2.1.1 Select View

This option activates the Select View form. It is used to zoom in on selected views. Theviews are updated as they are selected for review. The system can zoom in on the completeinterference clash or to the intersection of the interference clash.

The system only displays boxes for views that are currently active.

6.2.1.2 Envelope Diagnostics

This option displays the envelope graphics for immediate review only. However, if there areno <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 clashesorthogonally or in 3D about a particular point.

As you place data points in the active view, the clashing objects rotate. Each new data point isused to control the rotational axis and the direction that the clashing objects rotate about theaxis. You can see this more clearly with the reference models attached.

118

6. Ap

pro

val

Approve From List________________

6.2.2 Approve From List

This option activates the Approve From List form. It is used to approve existing clashesaccording to clash type. Refer to the Clash Categories article in the Introduction for moreinformation on the types of clashes.

When the markers are displayed, they are sorted in order of the clash type and then by theunique clash ID.

Select or Accept for all Types or ExitSelect the option to indicate the type of clashes to be approved, and select Accept toaccept the clashes.

The Clash Marker form displays.

119


Commands

Select Single Marker / Range of Markers — Allows you to select a single marker ora range of markers.

Select Clash Marker or Exit — Select the clash markers to be approved. For theSelect Range of Markers option, select the first and last clash marker in the range ofmakers to be approved.

120

6. Ap

pro

val

Checker Run Dates________________

6.2.3 Checker Run Dates

This option activates the Checker Run Dates form. It is used to display the exact date andtime that the clashes were detected.

This command only shows the unapproved/approved clashes for the most recent clashdetection run. It will show a complete history of the dates for interference checker runs on thearea chosen.

121


6.2.4 Review Clash History

This option activates the Review Clash History form. It is used to display all availableinformation 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 throughthe control shell.

Responsible User ID — Lists the identification number of the user that is responsiblefor a particular clash.


Select Attribute Select the attribute that you want to review. Thefollowing list describes the attributes of the ReviewClash History form.

Select Operating Select the mathematical operator that meets yourrequirements.

Specify Attribute Value Key in a numerical value to serve as an argument. Atypical keyin of responsible_user_no <= 16displays all clashes with a Responsible User Number ofless than or equal to 16.

122

6. Ap

pro

val

Review Clash History________________

Accept or Select AND/OR OperatingSelect Accept to accept and review the clash history.Use the arrow buttons to page through the identifiedclash data.

The system displays the description of previous reviewruns of any of the existing clashes that meet theargument.

123


6.2.5 Create Unapproved Clash Report

This option automatically creates an unapproved clash report. This is the same type of reportthat is created by the Interference Checker, but will include any newly created clashes. Thereport is named after the project or design area with a .mgr file extension. The interferencereport is created on the workstation or server in the directory from which the InterferenceChecker was submitted unless the Interference Report Management Data option was usedto define another network address and pathname.

Commands

Print / Delete — Submits the generated report output file to the specified print queueand deletes the output file.

Print / Save — Submits the generated report output file to the specified print queue andsaves the output file.


Unapproved Clash Report Example

PDS Interference ReportDate/Time: Wed Jul 20 08:59:16 1997

Report on Unapproved Clashes for area: doc

Total Number of Unapproved Markers: 5401

Marker# Model Description Clash Type

82 bccopy GAT Hard versus Softbccopy GAT

124

6. Ap

pro

val

Create Unapproved Clash Report________________ 83 bccopy GAT Hard versus Soft

bccopy FWN

272 testcopy GAT Hard versus Softtestcopy GAT

279 testcopy GAT Hard versus Softtestcopy FWN

280 testcopy GAT Soft versus Softtestcopy PIPE

281 testcopy FWN Soft versus Softtestcopy PIPE


283 testcopy PIPE Soft versus Softtestcopy GAT

284 testcopy PIPE Soft versus Softtestcopy FWN








292 testcopy PIPE Soft versus Softtestcopy GAT




389 rlh1 E90LR Hard versus Hardvcpipe1 E90LR

125

PDS Interference Checker/Manager User’s Guide - April 2002________________ 390 rlh1 E90LR Hard versus Hard

vcpipe1 PIPE

391 rlh1 E45TLR Hard versus Hardvcpipe1 E45TLR


393 rlh1 T Hard versus Hardvcpipe1 T


395 rlh1 FWN Hard versus Hardvcpipe1 FWN


126

6. Ap

pro

val

Checker Reference Data________________

6.2.6 Checker Reference Data

Reviews Checker Reference Data defined by the Project Data Manager module of ProjectAdministrator which is used to specify emulation data for use in analyzing interferenceenvelopes. This information is for review only.

During interference detection, the system uses a set of cylinders to emulate the volume of amodel graphic. These settings determine the number and size of the cylinders to be used.

Commands

Construction Tolerances Enabled/Disabled — Disabled on this form. The settingdisplayed 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 ActionDiscipline for every model combination. The Action Discipline is defined using theProject Administrator and indicates the job responsibility or who should take action toresolve the clash. The Action Discipline is at the top of each clash so that clashes maybe 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 thathas been set by the Project Data Manager. It is set to Default to plot the default clashplot graphics or to Detail to specify that the Interference Checker plot more detailedclash plot graphics.

Field Descriptions

Torus — Displays the number of cylinders (per 90 degrees) to be used in representing atorus (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 semi-ellipsoid (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 theslower the processing time for interference detection.

Slicing Tolerance — Displays the thickness of the slice that the software uses tosubdivide the shapes in a model to do the internal computations. This should not beconfused with Construction Tolerances (sometimes referred to as constructionclearances), which are used to maintain distances between items in the model.

Because the Slicing Tolerance is related to the size of model items, use cautionif you edit this value to a larger number as some small items may be missed.

Interference Marker Symbology — Displays the levels, weights and colors definedfor the marker. These fields are used to set the design file level for unapproved andapproved interference clash markers.

128

6. Ap

pro

val

Checker Reference Data________________ Intersection Threshold — Defines the amount of overlap allowed before theintersection of two components is considered a clash. Valid Intersection Thresholdvalues are within the range of 20 to 1000 Units of Resolution (UORs). The defaultvalue is 20 UORs.

129


6.2.7 Mass Clash Approval

This option activates the Mass Approval Manager form. It is used to approve multipleclashes 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

6. Ap

pro

val

Mass Clash Approval________________

This list only shows clash items with more than one clash of the selectedtype. For example, a piece of equipment with two Hard versus Hardclashes and one Hard versus Soft clash would display all three clashes ina listing of All Clash Types, both Hard versus Hard clashes in a listingof Hard versus Hard clashes, and no clashes in a listing of Hardversus 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


4. Select Markers for Approval

Select the clashes to approve.

5. Select the Approve False Clash button or the Approve Real Clash button, dependingon the nature of the clashes.

6. Click Accept to approve the selected clashes.

The system marks the selected clashes as approved and updates the list of unapprovedclashes.

132

6. Ap

pro

val

View Commands________________

6.3 View Commands

These commands provide view manipulations. All of these commands result in modifyingwhat is seen in selected views. These commands only manipulate the view of the model butdo not manipulate the actual model.

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 areview numbers. The views that are darkened are open.

Bottom-to-Top — Makes the bottom view fully visible, even if the view is fullyobscured before this item is chosen.

Cascade — Stacks views in numerical order with the lowest numbered view entirelyvisible and the title bar of each remaining view visible.

133

PDS Interference Checker/Manager User’s 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 logicalscreen.

This item is dimmed if your system is configured with dual monitors or if it does notsupport two virtual screens. Although the Swap command is not dimmed when using aNT workstation, it does not apply.

Update — Updates a view, all of the views, the right or left view, or the grid displayedon 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 movingaround to obtain different views of it).

–Move Target moves the target (like standing in one position and pointing the cameraat different objects).

–Lens opens the Camera Lens setting box, which is used to set the angles and focallengths of view camera lenses. Changes take effect only if applied with the Applybutton.

134

6. Ap

pro

val

View Commands________________ Render — Converts and displays views in one of the following ways: wiremesh,hidden line, filled hidden line, constant, smooth, phong, phong stereo, or phongantialias. Also, FlyThrough activates the FlyThrough Producer setting box, which isused to create simple animations, called sequences, for visualizing 3D models.

Levels — Defines which levels are displayed in a view. Changes take effect only ifapplied with the Apply button.

All PDS level control is manipulated using Category Control. Intergraph doesnot recommend using native Microstation level controls (i.e. on/off, color, linetype, etc.) in conjunction with any PDS application.

135

PDS Interference Checker/Manager User’s Guide - April 2002________________ Rotation — Opens the change view rotation box, which is used to control viewrotation. Changes take effect only if applied with the Apply button.

136

6. Ap

pro

val

View Commands________________

6.3.1 View Commands

These commands are the basic view modification commands.

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 anequipment item to be displayed.

137

PDS Interference Checker/Manager User’s Guide - April 2002________________ Window to Named Item — Defines a window viewing area about a specified nameditem.

138

6. Ap

pro

val

Move and Center View________________

6.3.1.1 Move and Center View

The Move Window and Center command allows you to define a new window center bymoving a specified direction and distance from the current window center. You can defineany distance and direction, inside or outside the viewing volume.

Commands

Move to (absolute move) — These options define the absolute coordinate for the pointin the direction to be defined. Select the direction and type the absolute coordinate orsnap to an element to retrieve its corresponding coordinate.

Move (delta move) — These options define the change in the selected coordinate forthe point in the direction to be entered. Select only one of the directions.

Construct Point — Constructs a new active point using multiple inputs. You canmove the point along absolute or delta coordinates. Each input moves the coordinateindicator until you select Accept.

Distance and Direction — Specifies the exact distance the point will be moved and inwhat general direction. This option can be used in conjunction with the ConstructPoint command.

139


Operating Sequence

1. Select View by selecting one of the screen views from the indicators at the top of theform.

2. Specify Window Center by specifying the new window center in the selected screenview. The system updates the selected view with the new window center.

— OR —

Select either the Construct Point or the Distance and Direction option.

140

6. Ap

pro

val

Construct Point________________

6.3.1.2 Construct Point

This command constructs a new active place point using multiple inputs. It allows you tocompute an offset distance or define absolute or delta coordinate values. Each input movesthe coordinate indicator until you select Accept to accept the displayed location and send thecoordinate location to the active independent command.

Commands




Compute Offset — Allows you to compute an offset.


Select a command which allows the active place point to be moved.

141


Operating Sequence

1. Identify Next Vertex by using the available options to construct a point.

2. Select Accept when the coordinates are correct.

142

6. Ap

pro

val

Distance and Direction________________

6.3.1.3 Distance and Direction

This command moves the active place point a specified or calculated distance in a specifieddirection or along a defined angle.

Settings in the model’s type 63 data determine the form display for horizontal and verticalangles. For the horizontal angle, the system will display either CCW from East or CW fromNorth. For the vertical angle, the system will display either CCW from Plan or CW fromPlan.

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



Horizontal Angle Vertical Angle — Type the angles in decimal degrees or select oneof the standard angles from the bottom of the form. Negative values are acceptable forboth options. The vertical angle is positive for a point above the active point andnegative for a point below the active point.

143

PDS Interference Checker/Manager User’s Guide - April 2002________________ Active Direction — The direction is defined by the segment pipe run at the activesegment point.

Up from Slope — The active direction is defined as perpendicular to the slopeddirection and in a generally upward direction. In other words, the vertical angle isincreased by 90 degrees.

Down from Slope — The active direction is defined as perpendicular to the slopeddirection and in a generally downward direction. In other words, the vertical angle isdecreased by 90 degrees.

Invert — The direction is defined by rotating the horizontal and/or vertical anglesabout the active flow centerline.

The Up from Slope and Down from Slope options specify a point thatrepresents the end of a pipe run normal to a sloped pipe run. These options areintended for use when the previous point is a branch point on a sloped piperun.

144

6. Ap

pro

val

Window Volume________________

6.3.2 Window Volume

The Window Volume command allows you to define a new window volume by moving aspecified direction and distance from the current window volume.

Commands



Construct Point — Constructs a new active point using multiple inputs. You canmove the point along absolute or delta coordinates. Each input moves the coordinateindicator until you select Accept.


Operating Sequence

1. Select View by selecting one of the screen views from the indicators at the top of theform.

2. Specify Window Volume by specifying the new window view in the selected screenview. The system updates the selected view with the new window volume.

— OR —

Select either the Construct Point or the Distance and Direction option.

Viewing Options

This command provides access to a set of options that allow you to manipulate the modelviews for each screen or window.

145


P&ID Drawing View

The following view commands perform special processing when you select the active P&IDdrawing 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. Thiscauses the P&ID drawing view to be saved as a named model view, PIDVUE, whichcan 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 selectedView 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. Ap

pro

val

Set View Orientation________________

6.3.2.0.1 Set View Orientation

The Plan View, Iso View, Looking North, Looking South, Looking East, and LookingWest commands allow you to set the view orientation to one of the standard viewingdirections. You can specify more than one screen with the same view.

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

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 selectthe view to update.

148

6. Ap

pro

val

Rotate About View________________

6.3.2.0.3 Rotate About View

The Rotate About View commands allow you to rotate a view about the selected axis (X, Yor Z). The angle follows the Right Hand Rule with the thumb pointing toward the positiveaxis.

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

150

6. Ap

pro

val

Rotation 3 Points________________

6.3.2.0.5 Rotation 3 Points

The Rotation 3 Points command allows you to rotate the view orientation so that you arelooking normal to the X and Y planes defined by the three points. The first two data pointsdefine the X axis. The line between the first and third data points define the Y axis.

Operating Sequence

1. Enter first point @x axis origin by placing a data point to define the origin of the Xaxis.

2. Enter second point on x axis by placing a data point to define the positive directionof the X axis.

3. Enter point to define y axis by placing the third data point to define the Y axis. Theviewing plane will be parallel to the plane defined by the three data points.

151


6.3.2.0.6 Dialog View Rotation

This command activates the MicroStation View Rotation dialog box which can be used tocontrol view rotation.

Commands

Std. — Sets a standard orientation of Top, Bottom, Back, Left, Iso(metric), or RightIso(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. Ap

pro

val

Color Shading________________

6.3.2.0.7 Color Shading

The Permanent Color Shading and Color Shading options are used to render the contentsof a screen view. When you select either of the color shading options the system displays alist of render options.

Select the option for the type of rendering to be performed and select the screen view to beprocessed.

For Permanent Color Shading, select a view number from the form (1-8). Theselected 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 renderedview 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 issimilar to the default wireframe display in that all elements are transparent and do not obscureother elements. In a wiremesh display, however, curved surfaces are represented by apolygonal mesh rather than a simple wireframe. This representation can increase the realismof curved surfaces, although it may also increase the amount of clutter as more lines aredisplayed for surfaces that would normally be hidden.

Cross-Section

This option renders the contents of a view as a cross-section. If an auxiliary coordinatesystem (ACS) is active, the cross-section is cut at the X-Y plane of the ACS. Otherwise it iscut 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, onlyparts of elements that would actually be visible are displayed. Lines hidden behind objectsare removed to create a more realistic representation. MicroStation accomplishes this bydecomposing each element into polygons. Hidden line removal processing is much slowerthan wireframe and wiremesh display, and the processing time is roughly equivalent to theother, more realistic type of rendering.

Filled Hidden Line

This option renders the contents of a view as a filled polygon display. A filled polygondisplay 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 shadedmodel, 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, materialcharacteristics, and lighting configuration (see 3D concepts in the user’s guide). Curvedsurfaces are decomposed into a mesh of polygons. Each polygon is shaded with a single colorand surfaces appear tiled.

154

6. Ap

pro

val

Render Options________________

Smooth Shading

This option renders the contents of a view as a smooth (Gouraud) shaded model. In smoothshaded models, the appearance of curved surfaces is more realistic than in constant shadedmodels because polygon color is computed at polygon boundaries and color is blended acrosspolygon interiors. This gives surfaces a smooth appearance.

Phong Shading

This option renders the contents of a view as a Phong shaded model. This is the most realistictype of rendering supported by MicroStation.

In a Phong shaded model, the color of each pixel is recomputed. Phong shading is useful forproducing high-quality images when speed is not critical and very exact lighting effects aredesired. If light sources are close to the objects being rendered, such as a spotlight shining ona 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, Phongshaded models are very similar to smooth shaded models and do not justify the increasedprocessing time.

Stereo

This option renders the contents of a view as a 3D image. It creates a stereo pair of imagesand merges the two images into a single image, which you can view by wearing red/blueglasses. Put on the red/blue glasses making sure that the red lens is over the left eye and theblue 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 viewcamera.

Camera Setup

This option lets you set the target, position, and clipping planes for a view camera and turn onthe 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 theview. Objects beyond the target point will appear smaller due to the nature of the perspectiveprojection. Objects in front of the target point will appear larger and may be excluded fromthe viewing pyramid.

Place a data point to define the camera position. A dynamic pyramid displays to show theviewing volume with the camera at the pointer location.

Place a data point to define the front clipping plane (display depth). Any elements or portionsof elements in front of this plane are not displayed.

Place a final data point to define the back clipping plane (display depth). Any elements orportions of elements beyond this plane are not displayed, but the view is turned on.

156

6. Ap

pro

val

Camera View________________

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

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 andfocal 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 lensfocal length in millimeters (mm). You can also specify the lens by choosing a standard lensfrom the Standard option menu. The angles and focal lengths of the standard lenses are:

Standard Lens Angle Focal Length (mm)

Fisheye 93.3 20Extra Wide 74.3 28Wide 62.4 35Normal 46.0 50Portrait 28.0 85Telephoto 12.1 200Telescopic 2.4 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) onthe 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 turnspecified views(s) off.

158

6. Ap

pro

val

Level Symbology On________________

6.3.3.3 Level Symbology On

This command provides the option to enable the display of reference models with the activereference model symbology.

159


6.3.3.4 Level Symbology Off

This command provides the option to disable the display of reference models with the activereference model symbology.

160

6. Ap

pro

val

Form Left/Right Screen________________

6.3.3.5 Form Left/Right Screen

The Form Right Screen / Form Left Screen toggle sets forms to be automatically displayedon the right (front) screen or the left (back) screen. This option is only relevant for dual-screenconfigurations.

161


6.3.3.6 Set/Do Not Set Display Depth for ReviewCommands

The Set/Do Not Set Display Depth for Review Commands toggle can be used to inhibit thechanging of display depths when using viewing commands.

162

6. Ap

pro

val

View, More Commands________________

6.3.4 View, More Commands


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 User’s 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 modelsymbology.

Level Symbology Off — Disables the displays reference models with the activereference model symbology.

Weight Display Toggle — Toggles the line weight in the selected view to 0 or to theweight 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. Ap

pro

val

Viewing Direction________________

6.3.5 Viewing Direction


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 User’s 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. Ap

pro

val

View Depth________________

6.4 View Depth


Commands

Set Active Depth — Sets the active depth; type the working unit value (relative to thecurrent active depth) of displacement.

Set Display Depth — Specifies the front and back of a range in a 3D view to bedisplayed along the Z axis.

Set Active Depth - Absolute — Sets the active depth along the Z axis for a specifiedview.

Set Display Depth - Absolute — Sets the display depth for a view. Specify the frontand back values which are the distances along the view Z axis from the global origin tothe front and back planes of the desired view cube.

Set Active Depth - Relative — Sets the display depth for the active view, where depthis 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 frontand back values which are the relative distance along the view Z axis from the front andback planes of the existing view cube to the front and back planes of the desired viewcube.

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 toplot interference, compress the design file, save the active MicroStation andPDS parameters, and exit the graphics session.

Commands

File — Allows you to to plot clashes, save the active MicroStation and PDSparameters and exit the graphics session.

Print — Print, is available only on Windows NT. If you are running PDS onMicroStation version 5.0, the Print command provides access to the MicroStationPrint command. If you are running PDS on MicroStation 95, the Print commandprovides access to the MicroStation Plot command.

Compress Design — Compresses the design file.

Exit — Exits the design file.

168

6. Ap

pro

val

File Commands________________

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 whatreference models are attached and displayed.

Commands

Plot Clashes — Prints default or detailed clash plots. See Plot Clashes, page 170 for moreinformation.

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 interferenceclashes based upon search criteria using Interference Management data. The InterferenceChecker must be run at some point before using this option.

Default Plot








The previous item requires a change to the format of the clash plotborder for the 5.0 release. You must copy the clash plot border,borderifc.dgn, from the PD_Clash product directory into your projectdirectory. This copy is not part of the Automated Upgrade Processbecause you may not wish to override your existing border file.

You must also copy the ifc.i file into your project directory for plottingpurposes. It is delivered but the copy is not part of the AutomatedUpgrade process.


The Review Date from the Clash Review History Data Table (PDtable_135).


170

6. Ap

pro

val

Plot Clashes________________

171


Detailed Clash Plots



The envelope graphics of the two clashing components are plotted with weight of 4 anda style of dashed.

The model graphics of the two clashing components are plotted a weight of 2 and astyle of solid.


By default, plots include the two clashing items. If detailed plots are required, revise themarker file with Project Administrator > Project Data Manager.

172

6. Ap

pro

val

Plot Clashes________________

173

PDS Interference Checker/Manager User’s Guide - April 2002________________ There is a primary discipline called the Action Discipline for every model combination. TheAction Discipline is defined using the Project Administrator and indicates the jobresponsibility or who should take "action" to resolve the clash. The Action Discipline is at thetop of each clash so that clashes may be easily sorted and routed to the person responsible forthe clashes in that discipline.


Commands




Default Clash Plots / Detailed Clash Plots — Submits either default or detailed clashplots. See the examples of each in the following sections.


174

6. Ap

pro

val

File Design________________

6.5.1.2 File Design

The File Design command allows you to save the active parameters defined in the currentdesign 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.

6.5.1.3 Exit

The Exit command is used to exit the graphics environment. Exiting a design file does NOTsave the active parameters set in the file. To save the active parameters, you must use the FileDesign 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 changethe attributes of an element(s) and review design file data associated with them, such asgeometry 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 ispermissible to use this command on non-intelligent, user-defined elements in themodel 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 displayeddata 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 cornerof the settings box.

Refer to the MicroStation User’s Guide for more information on the Analyze command.

176

6. Ap

pro

val

Setting Commands________________

6.7 Setting Commands

The Settings commands provide the ability to modify rendering, fonts and colors used duringa graphics session.

Command Groups

Colors — Modifies the colors used in the graphics environment. Use the File Designcommand 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 acolor, you must first select it. The selected color has an enlarged tile in which its indexnumber (0-255) is displayed. The view background color is in the lower right corner ofthe palette, denoted by "B."

Double-clicking a tile opens the Modify Color dialog box, which is used to modify thecolor.

Fonts — Opens the Fonts setting box. To see a type sample for a font, select in the listbox.

177

PDS Interference Checker/Manager User’s Guide - April 2002________________ Rendering — Opens the Rendering Settings box, which is used to adjust renderingsettings. It controls distance cuing, which determine how atmospheric fading is set inthe view. You can also set the Fog Color in this dialog box, which can be used to createa realistic atmospheric haze.

178

6. Ap

pro

val

User Commands________________

6.8 User Commands

These commands provide access to PDS help and to the user preferences and buttonassignment that are specific to your system.

Help

Displays Help for the PDS 3D products.

User Preferences

The User Preferences command changes things that apply only to your system such as howmemory is used on your system, how windows are displayed, how various items on the screenare laid out and behave, how reference files are attached by default, and so on. As the nameimplies, 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 cursorbutton assignments for cursor button menus.

179


6.9 Interference Management Data

This option activates the Interference Management Data form. It is used to display thecomplete file specifications of the Interference Management models and the project anddesign areas where applicable. It displays only those areas owned and controlled byinterference management data.

The form also highlights and allows you to re-create any marker file that has an incorrect datastructure or has become corrupted. For example, if you have manually copied the project’smodel seed file as the interference management model, you have the option to revise themodel 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. Ap

pro

val

Piping Clash Review (in the PD_Design Module)________________

6.10 Piping Clash Review (inthe PD_Design Module)

This option locates and reviews those interference clashes that have been reported for theactive model. It is only available in the PD_Design module but is included here to providethe full scope of PDS clash review information. It can be used to help identify and correctinterference clashes. This option operates similarly to the Interference Manager option inthe Interference Checker/Manager module including the ability to revise any InterferenceManagement data in the active piping model.

As you review the clashes, the system highlights the two components involved in the clash.

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

Clash Status — Displays the clash status as approved or unapproved.


181

PDS Interference Checker/Manager User’s Guide - April 2002________________ Model / Area Name — Displays the names of the model files and the design area thathave components involved in a clash.

Item — Displays descriptions of the clashing components in the Item fields which arelocated below the Model fields. The system accesses the user-defined labels in theLabel Description Library to create:

— the primary description, which is displayed on the top line with a a limit of 20characters; and

— the secondary description, which is displayed on the bottom line and has a limit of40 characters.

These descriptions are defined with the Clash Management Labels option on theCreate 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 approvedclashes.

Plot Clashes — Select this option to immediately plot the clash being reviewed. Thesystem generates temporary plot files in the c:\temp directory. This option uses thelast-used queue or the default queue if nothing has been plotted during the currentsession.

Select View — Select this option and identify the screen view to display the activeclash.

Restore View — Select this option to restore the selected view to its original viewingparameters.

Keyin Marker Number — Select this option and key in a marker number. The systemupdates 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.


182

6. Ap

pro

val

Piping Clash Review (in the PD_Design Module)________________ Model / Area — Displays the names of the models and the design files associated withthe clashing components.

Item — Displays descriptions of the clashing components.


Select Review Option Set the toggle to Review Unapproved Clashes orReview Approved Clashes to determine the type ofclashes to review.

183


6.11 Piping Clash Check (in thePD_Design Module)

This command checks a pipeline or user-defined active groups for interferences immediatelyafter completing the line. It automatically creates interference envelopes in memory for anypiping in the selected pipeline or active group. It checks any attached reference models forwhich interference envelope files have been created previously. It also reports any referencemodels for which interference envelopes have not been created previously.

The results of this interactive clash checking is not maintained as a part of the InterferenceManagement data. However, you can use the Piping Clash Review option to review theclashes detected by this command.

Construction tolerances and angular tolerances (tolerance for recognizing horizontal beams fordetermining when piping is legitimately resting on steel) are considered during theinterference 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 ProjectEnvironment Manager.

This command does not affect the interference envelopes created by theInterference Manager’s 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 theclash being checked.

Previous/Next Marker Number — Reviews the next/previous marker. The systemupdates the window coordinates about the clash in the selected view.


Identify Pipeline or Define Active GroupSnap to a segment or locate a component to identify thepipeline to be processed or use the Define ActiveGroup command to identify define the items to beprocessed.

Accept to Check Pipeline Select Confirm (√) to process the identified pipeline orselect Cancel (X) to reject the pipeline.

Identify Pipeline or Select Review OptionIdentify another pipeline as outlined or select the PipingClash Review option to review the detected clashes.

184

6. Ap

pro

val

Piping Clash Check (in the PD_Design Module)________________

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

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

Approve False Clash – Approves the clash as a false clash in the Project ControlDatabase.

Review Unapproved Clash / Review Approved Clash – Specifies if you want toreview approved or unapproved clashes.

Clash Marker – Displays the number of the current clash. Select a marker numberwith the left and right arrows; or, select the field and key in a marker number.

186

6. Ap

pro

val

Review PDS Clash________________ Item A – Displays the model name and the corresponding design area that has the oneitem of the clash. The descriptions of the clashing component display below the modelname and design area.

Item B – Displays the model name and the corresponding design area that has the oneitem of the clash. The descriptions of the clashing component display below the modelname and design area.

Comments – Displays existing comments about the active clash. You can also selectthe 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 selectthe view you want to update.

187


188

7. Plo

t

PDS Interference Plotting________________

7. PDS Interference Plotting

This section provides information on interference plotting, including information onmanaging the plot files, in the following order:

Interference Plot Manager

Interference Plot Management Data

189


7.1 Interference Plot Manager

This option activates the Interference Plot Manager form. It is used to plot interferenceclashes based upon search criteria using Interference Management data. The InterferenceChecker must be run at some point before using this option.

Default Plot








The previous item requires a change to the format of the clash plotborder for the 5.0 release. You must copy the clash plot border,borderifc.dgn, from the PD_Clash product directory into your projectdirectory. This copy is not part of the Automated Upgrade Processbecause you may not wish to override your existing border file.

You must also copy the ifc.i file into your project directory for plottingpurposes. It is delivered but the copy is not part of the AutomatedUpgrade process.


The Review Date from the Clash Review History Data Table (PDtable_135).


190

7. Plo

t

Interference Plot Manager________________

191


Detailed Plots



The envelope graphics of the two clashing components are plotted with a line weight of4 and a style of dashed.

The model graphics of the two clashing components are plotted with a line weight of 2and a style of solid.



There is a primary discipline called the Action Discipline for every model combination. TheAction Discipline is defined using the Project Administrator and indicates the jobresponsibility or who should take "action" to resolve the clash. The Action Discipline is at thetop of each clash so that clashes may be easily sorted and routed to the person responsible forthe clashes in that discipline.

192

7. Plo

t

Interference Plot Manager________________

193


Commands




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 sothat you can specify which clashes are plotted.

194

7. Plo

t

Interference Plot Manager________________ Default Clash Plots / Detailed Clash Plots — Submits either default or detailed clashplots. See the examples of each in the following sections.


195


7.2 Interference Plot Management Data

This option activates the file specification fields. They are used to define the specific networkaddress and path name in the Project Control Database where the system sends all InterferenceManagement plot files. If this option is not used, the system will put the plot files in thedirectory where the Interference Checker/Manager was initiated.

Field Descriptions

Node Name — Key in or accept the network address where the InterferenceManagement plot files are sent.

File Path — Key in or accept the path name where the files are placed.

196

8. Rep

orts

Interference Reporting________________

8. Interference Reporting

This section provides information on interference reporting, including information onmanaging the report files.

8.1 Clash Report Manager Form on page 198.

8.2 Interference Report Management Data on page 238.

197


8.1 Clash Report Manager Form

This command activates the Clash Report Manager form. It is used to generate reports fromthe Project Database with the report definition data. The Clash Report Manager stores thereport record and location records for each discrimination data file and format file in theProject Control Database. The numbered records are used to locate ASCII files on theirspecified 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 adiscrimination data file. The chosen action is also performed on the actual reportdiscrimination data file.

Report — Creates, revises, deletes, approves, or multi-creates report records used todefine or generate reports.

Report Management Data — Creates a Project Control Database record of thedefault node name and path for the report definition files. This option is primarily usedfor setup.

198

8. Rep

orts

Using the Report Commands________________

8.1.1 Using the Report Commands

Understanding Report Files and Records

The Clash Report Manager uses the discrimination data files, format files, and databaserecords that represent these files to generate reports. The following definitions explain all ofthe files and records in the reporting process.

Format File and Record

The format file is a user-defined, ASCII file which must be created with a text editor outsideof the Clash Report Manager. It contains special indices identifying what data appears in thereport 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 basicformat files is delivered for each type of reporting.

Using the Report Format option, you can create a numbered record for each format file so thatit can be accessed for report processing. The format record is a record in the Project ControlDatabase used to name and locate a specific format file. Unlike the format file, the formatrecord is created interactively. It is called a record to classify it as a block of data that is usedfor report processing but is not an actual file.

Discrimination Data File and Record

The discrimination data file limits the report to only the specified database occurrences. It isan 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 andlocate a specific discrimination data file. There is a uniquely-numbered record for eachdiscrimination data file so that it can be accessed for report processing. This is the same waythat 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, andsearch 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 areport, including the report output. (It is called a record to classify it as a block of data that isused 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 ReportManagement Data option to specify defaults for the node name and path of the reportdefinition files. By defining the defaults first, you can prevent keying in a node name andpath 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 datarecord, and discrimination data file using the Report Format and Report Discrimination Dataoptions. Reports cannot be generated until the format file, the discrimination data file, andtheir corresponding records have been established.

Finally, use the Report option to create the actual report.

200

8. Rep

orts

Report Format Form________________

8.1.2 Report Format Form

When you choose the Report Format option from the Report Manager form, the ReportFormat form is displayed.

This form enables you to create, copy, revise, or delete a record of the location of the formatfile in the project control database. An option is also provided that enables you to copy arecord and its corresponding ASCII format files.

The format file defines the data that will be reported and the way in which that data will bedisplayed. Reports cannot be generated unless a format file exists and a record of the file’slocation has been entered into the project control database.

Options

Create — Displays the Format Creation/Revision form, which enables you to add anew record of a format file in the project control database. For more information, seeFormat Creation/Revision Form, page 203.

Copy — Displays the Format Creation/Revision form, which copies the record of anexisting format file from the project control database along with the correspondingASCII format file. For more information, see Format Creation/Revision Form, page203.

Revise — Displays the Format Creation/Revision form, which modifies a record of anexisting format file in the project control database. For more information, see FormatCreation/Revision Form, page 203.

201

PDS Interference Checker/Manager User’s Guide - April 2002________________ Delete — Displays the Deletion form, which deletes an existing record of a format filefrom the project control database. If the record of the format file is deleted, reportingcannot be performed. For more information, see Format Deletion Form, page 205.

202

8. Rep

orts

Format Creation/Revision Form________________

8.1.2.1 Format Creation/Revision Form

When you choose Create, Copy, or Revise from the Report Format form, the FormatCreation/Revision form is displayed.

This form creates or revises a record in the project control database; this record defines thelocation 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.

Field Descriptions

Number — A unique number of up to 24 characters. Specifies the short name in theproject 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 fieldretains the active setting.

Before Using this Form

You must have created an ASCII format file. A set of basic format files is delivered with thePD_Report product in the ˜/pdreport/sample directory. The file for MTO reporting is namedpiping_#.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 eachfield. Then click Accept.

The project control database is updated.

204

8. Rep

orts

Format Deletion Form________________

8.1.2.2 Format Deletion Form

When you choose Delete, the Deletion form is displayed.

This form deletes a report record from the project control database and canoptionally deletethe 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 databaserecords.

Fields and Options

Number/Description — Displays the 24-character short name and the 40-characterdescription 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


From the displayed list, select the database record to be deleted.

205


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

orts

Report Discrimination Data Form________________

8.1.3 Report Discrimination Data Form

When you select Report Discrimination Data from the Report Manager form, theDiscrimination Data form is displayed.

This form creates, copies, revises, and deletes a discrimination data file from the specifieddirectory. The associated record in the project control database is also copied, revised, ordeleted as needed.

A discrimination data file is an ASCII file that designates which models will be included in areport. That is, discrimination data specifies the scope of the report. The project controldatabase record specifies the name and location of the discrimination data file that is to beassociated with a specific report.

Options

Create — Displays the Discrimination Data Creation form, which creates a newdiscrimination data file. The associated project control database record is also created.

Copy — Displays the Discrimination Data Revision form, which copies an existingdata file. The associated project control database record is also copied.

Revise — Displays the Discrimination Data Revision form, which modifiesdiscrimination data. You can use this option to revise the contents of the discriminationdata file, the location of the discrmination file, and the associated record in the projectcontrol database.

207

PDS Interference Checker/Manager User’s Guide - April 2002________________ Delete — Displays the Deletion form, which deletes a discrimination data file as wellas its associated record in the project control database. For more information, seeDiscrimination Data Deletion Form, page 219.

208

8. Rep

orts

Discrimination Data Creation Form________________

8.1.3.1 Discrimination Data Creation Form

This option activates the Discrimination Data Creation form. This form is used to create adiscrimination data file in the specified directory and its record in the Project ControlDatabase. 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 searchcriteria data using the Report Search Criteria command form, the dataspecified using the Report Search Criteria command form will takeprecedence.

After including any models or search criteria to the discrimination data file, make sureto select the final Accept. This step could be forgotten because Accept has alreadybeen selected on the model and search criteria selection forms, but the final Accept isnecessary to actually create the discrimination data file.

Commands

Discipline Extent — Predefines the disciplines of the clashes to be reported with theclash report. All disciplines are reported by default. Using this option, you can selectthe disciplines to include from a list of the active project’s discipline. For example, ifyou select the Piping discipline, only clashes which involve at least one pipingcomponent are reported.

Geographic Extent — Predefines the volume of the clashes to be reported with theclash 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 theselected design areas. The clashes are selected on the basis of the primary design areafor either component A or component B in the Clash Data Per Project Table,(PDtable_132).

209

PDS Interference Checker/Manager User’s Guide - April 2002________________ Select by Models includes all clashes within the volume of the selected models. Theclashes are selected on the basis of the model number for either component A orcomponent B in the Clash Data Per Project Table, PDtable_132.

Interference Search Criteria Predefines the extent of clashes to be reported with theclash report by specifying search criteria for any of the clash management data withinthe Project Control Database. See Project Search Criteria Form, page 212 for moreinformation.

Field Descriptions

Number — Key in a unique number to name the discrimination data record with up to24 characters in the Project Control Database. This number is a short name to identifythe record of the discrimination data file.

Description — Key in a description of the discrimination data file with up to 40characters 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 fieldretains 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 designareas where interference checking can be performed. This information is part of thesearch criteria for reporting and must be defined. It can be modified by selecting therelated 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. Thisinformation is part of the search criteria for reporting.

Review Action — Selects the Review Action on which to report from a list of allpossible 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 clashesto be reported.

210

8. Rep

orts

Project Administration Form________________

8.1.3.1.1 Project Administration Form

Discipline Extent

Predefines the disciplines of the clashes to be reported with the clash report. All disciplinesare reported by default. Using this option, you can select the disciplines to include from a listof the active project’s discipline. For example, if you select the Piping discipline, only clasheswhich 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 ofthe following options.


Select by Design Area Ownership includes all clashes within the volume of the selecteddesign areas. The clashes are selected on the basis of the primary design area for eithercomponent 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 clashesare selected on the basis of the model number for either component A or component B in theClash Data Per Project Table, PDtable_132.

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 usedwhen creating a report.

Field Descriptions

Select Table to define search criteria: — Selects the table that holds the attributes thatrelate 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, youset the search criteria with logical operators for the rows of data within the selectedtable or related tables. The related tables are listed in the bottom field.

Search Criteria which will affect data retrieved from above Table: — Displays thetables that are associated to the selected table by predefined relationships betweenattributes. These tables, therefore, affect the actual data that is reported from theselected table. Remember that the search criteria defined in the selected table in the topfield, and all related tables in the bottom field, is what actually affects the data that isretrieved. 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 fromthe attributes you specify, it is a read-only field.

Commands

Clear All Search Criteria — Removes any previously defined project search criteria.


Select Option Select the table to define the search criteria and click Accept toaccept the highlighted table.

212

8. Rep

orts

Project Search Criteria Form________________ The system activates the Search Criteria form with a list ofattributes for the selected table and an Interference Clash Per Jobdisplay list.

For any date attribute selected, the system displays the Define Date/Timeform. See the Define Date/Time section for more information.

Select Attribute Select the attribute to be restricted.

The system displays the selected attribute in a separatefield and displays a list of operators.

Select Operator Select an operator to define the search criteria.

The system displays the selected operator and promptsyou to key in an attribute value.

Enter Attribute Value Key in the attribute value. For a substring search, key ina string to appear anywhere within the attribute value(do not use wild cards) or select a value from a code-listed form, then select the value and click Accept.

The system validates the input and displays the definedsearch criteria in the Interference Clash Data Per Jobfield.

Accept or Select And/Or Operator

213

PDS Interference Checker/Manager User’s Guide - April 2002________________ Select AND to specify an additional condition or selectOR to specify an alternative condition or click Acceptto accept the defined search criteria.

214

8. Rep

orts

Define Date/Time________________

8.1.3.1.2.1 Define Date/Time

Date attributes, when used in the search-criteria selection process, activate the DefineDate/Time form. It is used to define the search criteria date and time. The operator, whichyou 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.

Field Descriptions

Time Offset — Modifies the currently set date, which is displayed in the Date/TimeSetting fields, to an earlier or later date and time. Modification of any of the fields inthe 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 seton 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 tomonth 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 User’s 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 theTime 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 thesystem.

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.


Select Operator Select an operator to define the search criteria.

The system displays the selected operator and activates the DefineDate/Time form.

216

8. Rep

orts

Discrimination Data Revision Form________________

8.1.3.2 Discrimination Data Revision Form

This option activates the Discrimination Data Revision form. It is used to copy or revise adiscrimination data file from the specified directory and its record from the Project ControlDatabase. First, the system displays the Record Number display list. When the desireddiscrimination data file is selected and confirmed, the system then displays the discriminationdata identification fields. These fields are used to define the record.

Commands

Discipline Extent — Predefines the disciplines of the clashes to be reported with theclash report. All disciplines are reported by default. Using this option, you can selectthe disciplines to include from a list of the active project’s discipline. For example, ifyou select the Piping discipline, only clashes which involve at least one pipingcomponent are reported.

Geographic Extent — Predefines the volume of the clashes to be reported with theclash report by selecting one of the following options.


Select by Design Area Ownership includes all clashes within the volume of theselected design areas. The clashes are selected on the basis of the primary design areafor 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. Theclashes are selected on the basis of the model number for either component A orcomponent B in the Clash Data Per Project Table, PDtable_132.

Interference Search Criteria — Predefines the extent of clashes to be reported withthe clash report by specifying search criteria for any of the clash management datawithin the Project Control Database. See the Project Search Criteria Form, page 212section for more information.

217


Field Descriptions

Number — Key in a unique number to name the discrimination data record with up to24 characters in the Project Control Database. This number is a short name to identifythe record of the discrimination data file.

Description — Key in a description of the discrimination data file with up to 40characters 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 fieldretains the active setting.

File Node — Displays the nodename where the discrimination data file is located. Thisfield retains the active setting.

Clash Area — Select the clash area on which to report from a list of all possible designareas where interference checking can be performed. This information is part of thesearch criteria for reporting and must be defined. It can be modified by selecting therelated 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. Thisinformation is part of the search criteria for reporting.

218

8. Rep

orts

Discrimination Data Deletion Form________________

8.1.3.3 Discrimination Data Deletion Form



Fields and Options



Operating Sequence



219




220

8. Rep

orts

Report Form________________

8.1.4 Report Form

When you select Report from the Report Manager form, the Report form is displayed.

This form creates, revises, and deletes report records and report files. A report record holdsspecifications 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 areport.

The report name is not the title that is printed on the report; the title is includedin the format file.

At the end of each report, a parameters page is included that contains the followinginformation:

Report Output — The report number, report title, report creation/revision date, andreport 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 filelocation (network address, path, and file name). The following discrimination data isalso included: list of model numbers (with discipline), volume (if applicable), searchcriteria (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 ofmodel 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 andgenerates a report. For more information, see Report Creation Form, page 223.

Revise — Displays the Revise Report form, which regenerates a report from anexisting or revised report record. For more information, see Revise Report Form, page226.

Delete — Displays the Deletion form, which deletes an existing report record and thecorresponding 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 multiplereports to the printer. For more information, see Report Multiple Submit Form, page234.

222

8. Rep

orts

Report Creation Form________________

8.1.4.1 Report Creation Form

When you select Create from the Report form, the Report Creation form is displayed.

Use this form to create a report record and to generate a report. Because report records arestored 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 thereport file in the project control database. This is sometimes referred to as the reportfile short name.

Report Title — The 40-character descriptive name of the report file. This is not thetitle in the actual report, but is rather the title of the report record. The title of the reportis 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 theactive settings, and it is automatically populated if you have specified this data on theReport Management Dataform. For more information, see Report ManagementDefaults Form, page 236.

Report Node — The name of the system on which the report output file will belocated. This field retains the active settings, and it is automatically populated if youhave specified this data on the Report Management Data form. For more information,see Report Management Defaults Form, page 236.

223

PDS Interference Checker/Manager User’s Guide - April 2002________________ Report Format File — The name of the format file to be used to generate the activereport. When you select this field, a list of available format files is displayed. Selectthe appropriate format file, and click Accept.

Report Discrimination File — The name of the discrimination data file to be used togenerate the active report. When you select this field, a list of available discriminationdata 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 togenerate the active report. When you select this field, a list of available search criteriafiles 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 aspecification, click Accept without selecting a file.

If the report discrimination data selected for the active report has searchcriteria data defined within it, and you specify a search criteria in thisfield, the search criteria specified in the Report Search Criteria fieldtakes precedence over the search criteria contained in the discriminationdata.

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 aread-only field; you cannot edit it.

Revised By — The user (up to five characters) who checked the report. This field isoptional.

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 thendeletes the report output file. When you select this option, a list of available printqueues is displayed. Click on a queue to select it.

Print/Save — Submits the report output file to the specified print queue and saves thereport output file. When you select this option, a list of available print queues isdisplayed. 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 beprocessed. When this toggle is set to Submission is Delayed, additional fields displayfor you to specify the date and time that the report is to be generated.

224

8. Rep

orts

Report Creation Form________________

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

4. 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 timethat the report is to be submitted.

5. Click Accept to save the report file.

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 controldatabase. An option is also provided to update (in some cases) the report record withoutgenerating a report output file. Similarly, you can choose to generate an updated report outputfile without updating the report record.

Fields and Options


Report Title — The 40-character descriptive name of the report file. This is not thetitle in the actual report, but is rather the title of the report record. The title of the reportis contained in the format file.


Report File Path — The disk location for the report output file. This field retains theactive settings.

Report Node — The name of the system on which the report output file will belocated. This field retains the active settings.

Report Format File — The name of the format file to be used to generate the activereport. When you select this field, a list of available format files is displayed. Selectthe appropriate format file, and click Accept.

Report Discrimination File — The name of the discrimination data file to be used togenerate the active report. When you select this field, a list of available discriminationdata files is displayed. Select the appropriate discrimination data file, and click Accept.

226

8. Rep

orts

Revise Report Form________________ Report Search Criteria — The name of the search criteria data file to be used togenerate the active report. When you select this field, a list of available search criteriafiles 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 aspecification, click Accept without selecting a file.

If the report discrimination data selected for the active report has searchcriteria data defined within it, and you specify a search criteria in thisfield, the search criteria specified in the Report Search Criteria fieldtakes precedence over the search criteria contained in the discriminationdata.


Last Revision Number — The revision number of the last report generated. This is aread-only field; you cannot edit it.

Revised By — The user (up to five characters) who checked the report. This field isoptional.

Revision Description — The description (up to 40 characters) of the report revision.This field is optional.




Submit to Batch Immediately/Delayed Submit to Batch — Specifies when the reportwill be processed. When this toggle is set to Delayed Submit to Batch, additionalfields 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 dataonly (Revise Data Only) or revision of the report data and the report output file (ReviseReport and Data). To revise the report specification without updating the reportoutput file, make the necessary changes, set this toggle to Revise Data Only, and clickAccept. To revise the report output file only, set this toggle to Revise Report andData without modifying any of the fields, and click Accept. To modify both the reportfile and the report output file, make the necessary changes, set this toggle to ReviseData 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 thereport 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.


5. 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 timethat the report is to be submitted.


228

8. Rep

orts

Report Deletion Form________________

8.1.4.3 Report Deletion Form



Fields and Options



Operating Sequence



229




230

8. Rep

orts

Report Approval Form________________

8.1.4.4 Report Approval Form

When you select Approve from the Report form, the Report Approval form is displayed.

Use this form to select a report to approve. Approving a report means that a database attributeis set from not approved (the default) to approved. This approval status provides a way foryou to flag reports that you have run and verified that the output data is valid. When a reportis revised, the approval status is automatically reset to not approved.

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 youspecify the report to be approved on the Report Approval form. When you click Accept, theApproval/Revision Interface form is displayed.

The first time a report is approved, only the Approved By field is active. All other fields arepurely informational. The data displayed in these fields is read from the Revise Report form.

Fields and Options


Report Description — The 40-character descriptive name of the report file.

Approved By — The initials (up to five characters) of the person who approved thereport.

Revision Number – The revision number (up to three characters) for the report. Thisfield is read-only; you cannot edit it.

Revised By — The initials (up to five characters) of the person who last revised thereport. This field is read-only; you cannot edit it.

232

8. Rep

orts

Approval/Revision Interface Form________________ Checked By — The initials (up to five characters) of the person who ran the report withthe revised information. This field is read-only; you cannot edit it.

Revision Description — Displays a short description of the revision. This field isread-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.

233


8.1.4.5 Report Multiple Submit Form

When you select Multi-Create from the Report form, the Report Multiple Submit form isdisplayed.

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 reportfile in the project control database. This is sometimes referred to as the report file shortname.

Description — The 40-character descriptive name of the report file.




Submit to Batch Immediately/Delayed Submit to Batch — Specifies when the reportwill be processed. When this toggle is set to Delayed Submit to Batch, additionalfields display for you to specify the date and time that the report is to be generated.

234

8. Rep

orts

Report Multiple Submit Form________________

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.


4. Specify whether the report is to be generated now (Submit to Batch Immediately) orlater (Delayed Submit to Batch). If you choose delayed submission, specify the dateand time that the report is to be submitted.

5. Click Accept to submit the reports.

235


8.1.5 Report Management Defaults Form

When you select Report Management Data from the Report Manager form, the ReportManagement Defaults form is displayed.

This form creates a record in the project control database of the node name and path of thereport 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 system’stemporary (that is, tmp or temp) directory.

Report Node — Specifies the default node name of the system on which report outputfiles 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 whichformat files are located.

Report Discrimination Data Path — Specifies the default path of the discriminationdata files.

236

8. Rep

orts

Report Management Defaults Form________________ Report Discrimination Data Node — Specifies the default node name of the systemon which discrimination data files are located.

Report Search Criteria Data Path — Specifies the default path of the report searchcriteria data files.

Report Search Criteria Data Node — Specifies the default node name of the systemon which report search criteria data files are located.

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 outputfiles, format files, discrimination data files, and search criteria data files. Then clickAccept.

237


8.2 Interference Report ManagementData

This option activates file specification fields. They are used to define the specific networkaddress and path name in the Project Control Database where the system sends reports withthe 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 InterferenceChecker/Manager was initiated.

Field Descriptions

Node Name — Key in or accept the network displayed address where the InterferenceManagement reports are sent.

File Path — Key in or accept the path name where the reports are placed.

238

9. Sch

edu

led

En

velop

e Bu

ild /

Clash

Detectio

n

Scheduled Envelope Builder and Clash Detection________________

9. Scheduled Envelope Builderand Clash Detection

The Scheduled Envelope Build/Clash Detection option is used to specify a periodicschedule for running the Envelope Builder and Interference Checker.

Before Using This Command

To write schedule data to a hard disk location, confirm the directory path exists and that youhave permission to write files to the directory.

When running on the Windows NT operating system, Scheduled Envelope Build/ClashDetection uses the at utility in conjunction with the Schedule Service. For the at utility to beavailable, the schedule service must be running. It is suggested that this service be set to startautomatically. To do this, select Services from the Control Panel program group.

You must be an administrator (or have administrative privileges) to submit ajob to the at scheduler. This is a Windows NT restriction, not a PDSrestriction.

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 onthe 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 theaccount mapping in NT Batch Manager. For additional information, see theSystem Administrator Responsibilities section of the PDS Project SetupTechnical Reference (DEA5067).

For Windows 2000, the Task Scheduler service must be run as the systemaccount. If you want scheduled jobs to run as a specific user account youshould set the AT Service Account.

Open Task Scheduler. On the Advanced menu, click AT ServiceAccount.

Click This Account, and then type the user account that will run tasksthat are scheduled by using the at command.

In the Password and Confirm Password fields, type the correctpassword for the account.

Scheduled Envelope Build/Clash Detection does not perform a build/detectionat the time it is created. Instead, command files are created to alert the systemto perform a build/detection at a specified time of day. The command files arelaunched by the system scheduler utility (at on Windows NT).

240

9. Sch

edu

led

En

velop

e Bu

ild /

Clash

Detectio

n

Scheduled Envelope Builder and Clash Detection________________

Operating Sequence

1. Select Option.

Select Scheduled Envelope Build/Clash Detect from the Interference Managementform.

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

241


9.1 Create/Revise EnvelopeBuilder/Clash Detection Schedule

These options are used to create or revise a schedule for running the Envelope Builder andInterference Checker on a periodic basis. You can establish multiple scheduled jobs for eachproject.

This operation is the same as running Interference Checker with the toggle set to Generateand 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 thearea/volume.

Field Descriptions

Shell Script — The Shell Script field is filled in automatically using the conventionenvclash_<archival_index_no>.

Number — Type up to 24 alphanumeric characters for the name of the envelopebuild/interference check schedule.

Description — Type up to 40 alphanumeric characters for the description of theenvelope build/interference check schedule.

File Specification and Path — Type the file name and directory path for the EnvelopeBuilder/Interference Checker Data file. This file defines the time of day for the buildand check, the frequency of the build and check, and the settings for the interferencecheck.

242

9. Sch

edu

led

En

velop

e Bu

ild /

Clash

Detectio

n

Create/Revise Envelope Builder/Clash Detection Schedule________________

Operating Sequence

1. Select Option.

Select the Create or Revise option from the Scheduled Build Envelope/ClashDetection form.

For the Revise option, a list of all scheduled build/check batch jobs for the activeproject 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 displayedshowing 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 Checkerschedule for the active project.

NumberDescriptionFile SpecificationPath

243


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 thebuild/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 filespecification 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 createdand the old entry must be deleted.

244

9. Sch

edu

led

En

velop

e Bu

ild /

Clash

Detectio

n

Delete Envelope Builder/Clash Detection Schedule________________

9.1.1 Delete Envelope Builder/Clash DetectionSchedule

The Delete option deletes an existing Envelope Builder/Clash Detection schedule file.

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

edu

led

En

velop

e Bu

ild /

Clash

Detectio

n

Review Schedule________________

9.1.2 Review Schedule

The Review Schedule option lists all scheduled envelope/clash jobs for the active project anddisplays the following basic data.

archival numberfrequency of build/checktime of day for build/checknetwork address for build/check

Operating Sequence

1. Select Option.

Select the Review Schedule option from the Scheduled Build Envelope/ClashDetection 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 Detectionform.

247


248

A.T

rou

blesh

oo

ting

Appendix A: Troubleshooting PD Clash________________

Appendix A Troubleshooting PDClash

This section provides information on troubleshooting PD Clash, including the following:

A.1 Message Files

A.2 Tips

A.3 Questions & Answers

249


A.1 Message Files

The PDS 3D products share common message files contained in thewin32app\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

A.T

rou

blesh

oo

ting

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 followingerror 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 intoMicroStation and fence rotate the model by 0 degrees or find the offending element andcorrect 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 MicroStationand 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 readpermissions.

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.

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 areaindex 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) thatused 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 doesnot exist on subsequent runs or if the file is corrupted. For example, a .env file is manually deleted anddoes not get clash checked on a rerun. If the clash has been previously reported, its area_index_no willbe 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 bothplaces.

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/WithoutReference Models to with. With Reference Models must be turned on in order to get the true dynamic clashdisplay. Otherwise, the display looks as though nothing is happening.

252

A.T

rou

blesh

oo

ting

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 dynamicclash display. If Window to Clash is used instead, the display window is collapsed around the clash, alteringthe view depth. You will not be able to see all of the clash because it exceeds the window’s 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 ModelStatus Type for the .dgn file should be set at 1. For the propagated model in ModelDraft, and for the frozenviews 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 generatedenvelopes are flat disks instead of spheres. The affected envelope builders include the generic envelope builderused for non-PDS models and any other PDS envelope builder which creates envelopes for spheres placed withthe Microstation Place Sphere command.

Resolution

A surface of revolution with a 180 degree arc creates a spherical envelope.

253


A.3 Questions & Answers

Changing title block units

How can I change the title block on thedrawing 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 plotsto be the wrong size for the plotter paper.

254

B. T

ables

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 ReferenceDatabase, which are delivered in \win32app\ingr\pdshell\ddl.

Project Control Database

Do not revise the following database definition other than to change columnnames.

# Project Control Data

table number = 103 , number of columns = 29

1 , product_version_no , short2 , report_path , character(36)3 , report_node , character(26)4 , report_format_path , character(36)5 , report_format_node , character(26)6 , report_filter_path , character(36)7 , report_filter_node , character(26)8 , piping_eden_path , character(36)9 , piping_eden_node , character(26)10, eden_table_path , character(36)11, eden_table_node , character(26)12, piping_spec_path , character(36)13, piping_spec_node , character(26)14, assembly_path , character(36)15, assembly_node , character(26)16, model_builder_path , character(36)17, model_builder_node , character(26)18, design_review_path , character(36)19, design_review_node , character(26)20, std_note_lib_path , character(36)21, std_note_lib_node , character(26)22, eqp_eden_path , character(36)23, eqp_eden_node , character(26)24, tdf_table_path , character(36)25, tdf_table_node , character(26)26, clash_report_path , character(36)27, clash_report_node , character(26)28, clash_plot_path , character(36)29, clash_plot_node , character(26)

255

PDS Interference Checker/Manager User’s Guide - April 2002________________ # Engineering Discipline Data


1 , discipline_indx_no , short2 , discipline_name , character(20)3 , intra_disc_ifc_flg , short4 , discipline_mtrx_a , integer5 , discipline_mtrx_b , integer

# Design Area Data


1 , discipline_indx_no , short2 , area_index_no , short3 , area_name , character(10)4 , area_description , character(40)5 , volume_low_x , integer6 , volume_low_y , integer7 , volume_low_z , integer8 , volume_high_x , integer9 , volume_high_y , integer10, volume_high_z , integer11, interference_mode , short12, area_lock_owner , character(10)13, area_lock_status , short14, area_lock_date , integer15, clash_rpt_index_no , integer

# Model Data


1 , model_index_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , partition_no , short5 , model_no , character(10)6 , model_description , character(40)7 , model_file_spec , character(14)8 , path_name , character(36)9 , network_address , character(26)10, lock_owner , character(10)11, lock_status , short12, lock_date , integer13, verification_date , integer14, revision_date , integer15, responsible_disc , short16, model_type , short17, model_status , short , standard note 1605

256

B. T

ables

Appendix B: Interference Tables________________ ###################################################

Job Data (PDtable_131) One record is created per clash run (unique_sequence_no). Thistable 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 , system_unique_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , unique_sequence_no , integer5 , completion_date , integer6 , control_user_no , short7 , env_creation_date , integer8 , clash_check_option , short , standard note 12089 , volume_filter_opt , short , standard note 120910, volume_low_x , integer11, volume_low_y , integer12, volume_low_z , integer13, volume_high_x , integer14, volume_high_y , integer15, volume_high_z , interger

###################################################

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


1 , unique_clash_id , integer , index 12 , if_approval_status , short , standard note 12033 , comp_a_unique_id , integer4 , comp_b_unique_id , integer5 , model_index_no_a , integer6 , model_index_no_b , integer7 , discipline_index_a , short8 , discipline_index_b , short9 , recent_clash_type , short , standard note 120410, recent_plot_date , integer11, recent_review_date , integer , index 212, recent_sequence_no , integer13, area_index_no , short14, action_discipline , short15, recent_seq_no_b , integer16, area_index_no_b , short

257

PDS Interference Checker/Manager User’s Guide - April 2002________________ ###################################################

Clash Data per Job (PDtable_133) A new record is created each time a run is made, and itpoints to unique_clash_id entry in PDtable_132. For example, when a clash is found during arun, a record is written to this table. Each time the same clash is found in subsequent runs, anadditional record is written to the table. The recent_sequence_no points tounique_sequence_no in PDtable_131 generated for that clash run. Clash type and volumeranges of clashing components are tracked.

#################################################### Clash Data Per Job


1 , system_unique_no , integer , index 12 , unique_clash_id , integer , index 23 , unique_sequence_no , integer , index 34 , clash_type , short , standard note 1204 , index 45 , comp_a_range_x_lo , integer6 , comp_a_range_y_lo , integer7 , comp_a_range_z_lo , integer8 , comp_a_range_x_hi , integer9 , comp_a_range_y_hi , integer10, comp_a_range_z_hi , integer11, comp_b_range_x_lo , integer12, comp_b_range_y_lo , integer13, comp_b_range_z_lo , integer14, comp_b_range_x_hi , integer15, comp_b_range_y_hi , integer16, comp_b_range_z_hi , integer

###################################################

Component Clash Data per Project (PDtable_134) One record is created per project perclashing model item. It is never reused or deleted. Multiple clashes experienced by a singlecomponent are tracked. Therefore, if a component clashes with 6 different items, only oneentry appears in PDtable_134, and all other clashes are indexed to this entry.

#################################################### Component Clash Data Per Project


1 , unique_comp_id , integer , index 12 , comp_table_number , short3 , comp_row_number , integer4 , model_index_no , integer5 , primary_descript , character(20)6 , secondary_descript , character(40)7 , comp_model_status , short

258

B. T

ables

Appendix B: Interference Tables________________ ###################################################

Clash Review History Information (PDtable_135) One record is created per clash when it isreviewed after a run. Each time this clash is reviewed by the Interference Manager, the recordin PDtable_135 is updated. If the same clash is present on the next run, a new record iscreated in Table 135 with the same unique_clash_id. If a clash is never reviewed in theInterference Manager, a record for that clash will not be created in PDtable_ 135.

#################################################### Clash Review History Information


1 , system_unique_no , integer , index 12 , unique_clash_id , integer3 , review_date , integer4 , review_user_no , short5 , responsib_user_no , short6 , action , short , standard note 12057 , review_comment , character(100)8 , approval_method , short , standard note 1207

###################################################

Clash Plot History Information (PDtable_136) One record is created per clash plot.

###################################################

# Clash Plot History Information


1 , system_unique_no , integer , index 12 , unique_clash_id , integer3 , plot_date , integer4 , plot_user_no , short

###################################################

Material Reference Database

Do not revise the following database definition other than to change columnnames.

259

PDS Interference Checker/Manager User’s Guide - April 2002________________ ###################################################

Component Insulation Exclusion Data (PDtable_231) This table allows you to completely orpartially exclude the insulation of components that are on insulated lines, during interferencechecking. If this table is not loaded, the insulation thickness is completely included in thecomponent’s interference envelope.

###################################################

# Component Insulation Exclusion Data


1 , system_unique_no , integer2 , commodity_name , character(6)3 , model_code , character(6)4 , gcp_npd_from , short5 , gcp_npd_to , short6 , rcp_npd_from , short7 , rcp_npd_to , short8 , heat_tracing_from , short , standard note 2009 , heat_tracing_to , short , standard note 20010, insul_purpose_from , short , standard note 22011, insul_purpose_to , short , standard note 22012, nor_oper_temp_from , double13, nor_oper_temp_to , double

###################################################

Flange Insulation Exclusion Data (PD_table 232) This to define the applicable insulationthickness to be added to the flange outside diameter of the bolted end of that component’sinterference envelope. If this table is not loaded, the insulation thickness is completelyincluded in the component’s interference envelope.

###################################################

# Flange Insulation Exclusion Data


1 , system_unique_no , integer2 , bolted_npd_from , short3 , bolted_npd_to , short4 , heat_tracing_from , short , standard note 2005 , heat_tracing_to , short , standard note 2006 , insul_purpose_from , short , standard note 2207 , insul_purpose_to , short , standard note 2208 , nor_oper_temp_from , double9 , nor_oper_temp_to , double

260

Glo

ssary

Glossary________________

Glossary

absolute path name The sequence of directories, beginning with the root directory (/) thatlocates a file. See also path name and relative path name.

active depth The plane in a 3-D design upon which you can place elements and performmanipulations.

active process The process which is displayed in the Process ID field; it controls themessage fields, the menus, and the keyboard. The active process has ahighlighted window icon strip.

application software Software designed to meet specific needs, unlike system software whichruns other software.

batch processing A method of processing data which collects a series of operations into agroup (or ‘‘batch’’) and executes the group in a continuous stream withoutuser intervention.

batch queue A queue, or channel for moving requests, created through NQS. A batchqueue handles scheduling for processes submitted through the Batchoptions screen menu.

branch point A point on a pipeline which separates piping segments so that they can beassigned different segment parameters. A branch point allows forplacement of branch components.

cancel button The button located in the upper right corner of a form containing a red X orthe word cancel. Select the cancel button to exit the form or option.

cell A permanent association of elements that can be stored and placed as agroup, and then manipulated as individual elements.

character A column data type that stores alphanumeric character data.

client In network operations, a node which accesses data or performs a function onthe remote resource (usually a server). All network operations (database,NFS, NQS) between two or more nodes establish a client/serverrelationship.

column An attribute of a database table. A group of columns defines a table in adatabase.

command Instructions from the user to perform a function on specified data.

confirm button A button that appears in the upper right corner of a form and contains agreen check mark or the word confirm. Select the confirm button to initiatea specified option.

261


coordinate The location of a point along the X, Y, or Z axis.

coordinate system A geometric relation used to denote the location of points in the designcube. The most common coordinate system is the rectangular coordinatesystem, whereby points are located by traversing the X, Y, and Z axes of thedesign cube. Normally, coordinate systems have their origin defined as0,0,0, though this is not required. Other coordinate systems are used to moreeasily 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 acylinder.

coordinates An ordered set of absolute or relative data values that specify a location in acoordinate system.

core files The image files written by System V for a number of reasons, the mostcommon of which are memory violations, illegal instructions, bus errors,and user-generated quit signals.

cursor The pointer that the user moves on the screen to indicate an item or area.

data button The mouse button used to place data points and tentative points, to acceptpreviously selected elements, and to select commands from forms andmenus.

data entry field The field on a screen used to accept user-supplied data. Also known askey-in field.

data point A point placed by pressing the data button on the mouse. Data points selectcommands from the panel menus and Menu Bar, place elements, identifyand accept elements, and activate windows and perform windowmanipulations.

database A collection of comprehensive informational files having predeterminedstructure and organization that can then be communicated, interpreted, orprocessed by a specific program.

database table The part of the database that is made of rows and columns and containsinformation about the project and design elements.

default The predetermined value of a parameter that is automatically supplied bythe system or program whenever a value is not specified by the user.

delete To remove, destroy, eliminate, or erase.

delimiter A separating mark or space; a character or sequence of contiguouscharacters that mark the end of a string of characters.

device A nonaddressable component of a network, that is, a component onto whicha user cannot log, for example, tape drive, disk drive, and floppy disk.

262

Glo

ssary

Glossary________________

directory A file that contains the names of other files.

display-list box 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. Inputcan then be selected from the list with a data point instead of keying in theinformation.

domain The set of acceptable values for a value within a component.

dragging Another term for the dynamic function that attaches the cursor to an elementso you can see it move.

easting A term used in plane surveying that describes an east, or positive, differencein longitude.

entity An object (project, drawing, element, and so forth.) of interest about whichinformation is stored; a relational database table.

envelope file See interference envelope.

file specification A UNIX path name that tells the system where to locate a file.

filename A user-defined name given to an interactively created file. The name shouldbe relevant to the contents of the file.

form An interface or screen menu designed with the I/FORMS product. Becausemany of the screen menus in the application software are built withI/FORMS, you must have the FORMS_S product on your workstation.

full path name The name of the entire path or directory hierarchy to a file, including the filename. See also relative path name.

gadget A portion of a form, such as a button, a field, or a checklist, that responds toinformation. Gadgets can display default values or act as data entry areas.

header The first items of information in a file which precede any actual data. Theheader contains information on the structure and contents of the file.

hierarchy A classified structure with superiors (roots) and subordinates (dependents)for grouping files or commands.

icon A pictorial representation or image; a symbol that graphically identifies acommand.

Informix A relational database management system supported by RIS.

Ingres A relational database management system supported by RIS.

interference envelope An equipment modeling primitive or parametric component that is used inconjunction with or instead of model graphics for interference checking.Interference envelopes are given different levels and display symbology todistinguish them from primitives.

263


invert elevation The lowest point on the internal diameter of the pipe.

isometric Relating to or being a drafting system characterized by three equal axes atright angles; a view in which the horizontal lines of an element are drawn atan angle to the horizontal and all verticals are projected at an angle from thebase.

key An attribute (column) in a table which is chosen as the access vehicle toindividual rows of the table.

key-in field The field on a screen used to accept user-supplied data. Also known as adata entry field.

keypoint A point on an element, including vertices, to which you can snap.

keyword A word recognized by the software that provides access to a certainfunction.

menubar The strip at the top of the screen that contains icons for selectingcommands.

message area The area that appears in the MicroStation Command Window when you areworking in a design file. It is divided into the Command Status field, theCurrent Command field, the Prompt field, and the Key-in field.

model A graphic representation or schema.

network An interconnection of host computers and workstations that enables them toshare data and control. The term network can mean the devices that connectthe system, or it can mean the connected system.

NFS Network File System, the system that provides access to data that isdistributed among machines through an interconnection of host computersand workstations. NFS allows you to mount a remote resource to your localworkstation so you can access the data as though it were local. NFS isusually used to access centralized data on a server.

node Any addressable device (such as a workstation or a server) that is connectedto a network. The network enables the connected nodes to share data andsystem control.

node address The hard-wired Ethernet address assigned to each node when it ismanufactured. It is necessary for each node to identify and communicatewith another node in the network.

node name A name, or alias, that can be assigned to the node address of a device on anetwork.

northing A term used to describe a north coordinate location in the plant coordinatesystem.

264

Glo

ssary

Glossary________________

nozzle A special equipment modeling primitive that contains the connection pointto piping. This point does NOT include a gasket allowance, but ratherrepresents the face-of-flange coordinate.

NQS Network Queuing System, the software package that allows you to definenetwork-wide batch and device queues. Use of NQS involves setting uplocal resource queues on the system(s) where the resources reside andsetting up ‘‘pipe queues’’ on the systems that are to have access to theresources.

Oracle A relational database management system supported by RIS.

origin In coordinate geometry, the point where the x, y, and z-axes intersect.

origin point The point at which the coordinate system is placed.

orthogonal view A view which is a projection of the model onto a plane along lines whichare orthogonal to the plane.

parameter A property whose value determines the characteristics or behavior ofsomething.

path A sequence of directories leading to a file or a sequence of menus leading toa command.

path name The sequence of directories leading to a file. See also absolute path nameand relative path name.

PDS Plant Design System

pipe queue A controlled channel for moving requests to batch or device queues onremote systems and for receiving status and/or data in response.

place data point To identify a specific element, or indicate a specific point in the design file.

plane A spatial element in geometry that may or may not have a boundary, but islevel, having no elevations or depressions, and is three-dimensional.

RDB Reference Database.

reference database A collection of reference data containing information relative to industrydesign codes, vendor’s catalog data, job specifications, commodity libraries,graphics symbology, label descriptions, report formats and otherinformation of a similar manner.

relative path name The sequence of directories leading from the current directory to a particularfile. See also path name and absolute path name.

rotate To turn; to change the angular orientation; to transform by revolution abouta specific axis.

265


row A unit of related information in a table. One collection of column values fora table.

rubberbanding The animation dynamic that enables you to specify the position of a datapoint while the element changes as you move the cursor.

schema A description of the overall structure of the rulebase or database.

schema file A file that outlines the overall logical structure of a rule base or a database.

server In network operations, the node which maintains common data or performsa common task needed by clients. All network operations (database, NFS,NQS) between two or more nodes establish a client/server relationship.

Structured QueryLanguage SQL

Language developed by IBM for creating, modifying, and queryingrelational databases.

style The symbology of an element such as continuous dashes, dash-dot, solid,and so forth.

surface The skin of a three-dimensional geometric element.

symbology The display style of an element, including color, style, and weight.

table A collection of data for quick reference, either stored in sequential locationsin memory or printed as an array of rows and columns of data items of thesame type.

toggle To switch; to change between two alternatives.

user name A name that provides access to an account on the system.

values Data, either entered by the user or determined by the software, that arestored in an attribute.

variable A quantity that may assume any one of a set of values.

vector A quantity possessing both magnitude and direction, generally representedas a line. Vectors can be manipulated geometrically and are represented asa coordinate triple (x,y,z).

view The defined area of vision on a screen. A view allows you to see aprescribed 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 thez-axis can be thought of as coming straight out of the view towards you.The view axes maintain this relationship regardless of the rotation withrespect to the design cube. See also active depth.

virtual memory External memory for a computer that can be used as if it were an extensionof the computer’s internal memory. The software uses virtual memory tostore data. This means that unneeded files and data, stay on the disk untilthey are called for. Because the internal processing memory stores aminimal amount of data, the software can perform processing more quickly.

266

Glo

ssary

Glossary________________

working directory The directory from which you are accessing files.

267


268

Ind

ex

Index________________

Index

Aaction discipline 116active project 209, 211, 217align view 163analyze 176

datapiping clash

check 108, 184review 181

applicationconsiderations 67type 92

Approval form 232approval manager

approve 115approve from list 119checker reference data 127checker run dates 121create unapproved clash report 124plot clashes 170review clash history 122

approve 115from list 119graphics environment 114

approving reports 232area

window 137

Bbasic interference checklist 31batch

envelope builder 239interference checker 239interference checking 25

bottom-to-top 133button assignments 179

Ccamera 134

lens 157off 157position 157setup 156target 157view 156

cascade 133center

window 137checker

reference data 127run dates 121

checklistbasic interference 31

clashcategories 33category considerations 91checker

PD_Design 108discipline 75history review 122management

setup 45ownership 45

dual 45plot management 196plotting 98precedence 33

clash check 184schedule 239

colorshading 153

colors 177component

insulation exclusion data 61compress design 168constant shading 154construct point 141construction

toleranceexclusion data 62

tolerances for equipment envelopes 42construction clash category 33copy 134

report discrimination data 217view 163

createenvelope builder schedule 242interference checker schedule 242unapproved clash report 124

cross-section 154

269

PDS Interference Checker/Manager User’s Guide - April 2002________________ Ddefault

plot 98report active 96

defining pipe-like components 63delete

envelope builder schedule 245interference checker schedule 245

designarea 21, 73

pre-defined volume 21predefined volume 74understanding 20

design areaownership 41, 209, 211, 217

design area ownership 43dialog view rotation 152, 166discipline 116

clash 75extent 209, 217matrix 47

discipline matrix 52display depth

set for review commands 162distance and direction 143dual design area ownership 41, 43dual ownership

of clashes 45

Eeast elevation 165element

commands 176enter dynamics 117, 118envelope 59

builder 23, 60design area 73

predefined volume 74model 76piping

design areapredefined volume 72

piping design area 70project 69schedule 239

create 242delete 245review 247revise 242

diagnostics 24, 85, 117, 118verification 81

envelope (continued)verifications 24

envelopes 23equipment

insulation 42error

messages 250error messages 251exclusion

by discipline 47exclusion tables 61, 90exit 168, 169, 175

Ffalse clashes 85, 91, 116, 181FAQs 249file 168

commands 168, 169design 169, 175envelope 60marker 252user-defined envelope 77

filled hidden line 154fit 137flange

insulation exclusion data 62fonts 177forms

left/right screen 161

Ggeographic extent 209, 211, 217grid on/off 164

Hhard clash category 33help 179hidden line 154highlight clash 117

IIFCMGR

enter dynamics 118envelope diagnostics 118select view 118

input 26insulation 42

exclusion data 61, 62interference

approvalmanager 30, 112, 114

270

Ind

ex

Index________________ interference (continued)

checker 89, 90design area 21

pre-defined volume 21input 26output 26, 105

PDS interference report 26PD_Design 108piping

design area 21pre-defined volume 21

plot clashes 98, 190project 20schedule 239

create 242delete 245review 247revise 242

checker data 41commands 39detection 19exclusion by discipline 47introduction 19management

clash categories 33data 180interference checker

input 26output 26

managing 111markers 27matrix 52

commands 51modifying 50process 49reviewing 50understanding 49why define 47

model status ranges 42plot management data 196plot manager 190plotting 189report management data 238reporting 197

understanding 30understanding 19units 18

interference check 184interference search criteria 210, 212, 217intra discipline interference check 47, 51

introduction 18interference

checker summary 18management

clash categories 33project

organization 18setup 35

iso view 165isometric

view 147item

window in 137

Kkey-in

marker number 117

Llens 157level

symbologyoff 160, 164on 159, 164

levels 135looking

east 147north 147south 147west 147

Mmagnify 137markers 252match

planar element 150, 166matrix 47, 52measure distance 114model 76

files 36status 60

modify interference matrix 50move

and center view 137, 139down 163left 164right 164up 163window 139

271

PDS Interference Checker/Manager User’s Guide - April 2002________________ Nnext 134no intra discipline interference check 51non-PDS models 77north elevation 165

Oopen

close 133output 26

interference checker 105ownership 41

design area 43of clashes 45

PPDS

review clash 186PDS interference report 26PDtable_135 96PDtable_231 61PDtable_232 62PDtable_233 62permanent color shading 153phong shading 155piping

clashcheck 108, 184review 181

construction tolerance exclusion data 62design

area 70predefined volume 72

plan view 147, 165planar element

match 150plot 196

active clash 116clashes 98, 169, 170, 190discipline extent 209, 217geographic extent 209, 211, 217management data

interference 196plots

default 98plotting

understanding 30precedence

clash 33precision input

construct point 141

precision input (continued)distance and direction 143

previous 134print 168processing

interference checker distribution 37project 20, 69

organization 18search criteria 212

date 215time 215

setup 35project.ddl 255

Qquestions 249queue

redirected processingexamples 37

queues 37

Rreal clash 116, 181redirected processing 37

queues 37redistribution functions

workstation classifications 37reference

models, with/without 117refresh

views 137render 135

options 153rendering 178report

clash report management data 238discrimination data

copy 217revise 217

unapproved clash report 124reporting 197

design area ownership 209, 211, 217reports

PDS interference report 26restore

view 117review

clash history 122envelope builder schedule 247interference checker schedule 247interference matrix 50

272

Ind

ex

Index________________ review (continued)

PDS clash 186revise

envelope builder schedule 242interference checker schedule 242report discrimination data 217

rotate3 points 151about view (x,y,z) 149view

about x axis 165about y axis 165about z axis 165absolute 165by 3 points 165element 165relative 165

rotation 136

Sschedule

envelope builder 239interference checker 239

selectview 116, 118

select by models 210, 211, 217set

active depth 167absolute 167relative 167

display depth 167absolute 167relative 167

view orientation 147set display depth 162settings

commands 177setup 35shading

color 153show

active depth 167display depth 167

single design area ownership 41, 43smooth shading 155soft clash category 33south elevation 165stereo 155swap 134

Ttable

insulation exclusion datacomponent 61flange 62

piping construction tolerance exclusion 62tables 255

exclusion 61tile 133tips on PD Clash 249tips on using PD Clash 252tools

review PDS clash 186troubleshooting 249typefaces 13

Uunderstanding

design areas 20interference

approving 30checking 25envelopes 23plotting 30reporting 30

interferences 19volumes 20

update 134all 163left 163right 163view 163window 148

usercommands 179defined envelope files 77defined interference reports 96preferences 179

utilitiesreview PDS clash 186

Vview

commands 133depth 167manipulations 158more 163off 163on 163rotation 152, 166toggle 163

273

PDS Interference Checker/Manager User’s Guide - April 2002________________ view (continued)

update 148viewing options 145

viewingdirection 165

viewing options 137, 145camera view 156color shading 153dialog view rotation 152form screen 161match planar element 150rotate about view 149rotation 3 points 151set view orientation 147update window 148views 158

volumefilter 22, 95window 145

volumes understanding 20

Wweight

display toggle 164west elevation 165window

area 137center 137move 139named item 137origin 137update 148volume 137, 145

wiremesh 154with/without reference models 117

Zzoom

in 137out 137

274

Interference Checker/Manager (PD_Clash) User’s Guide Addendum February 2003 DPDS3-PB-200006B For PDS version 07.02.00.** This document supplements DPDS3-PB-200006A.

PDS Interference Checker/Manager User’s Guide Addendum – February 2003

276

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

277

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 User’s Guide (pp 33-34 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.


278

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.

279

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 User’s Guide (pp 47-53 in the PDS 7.1 version of the document).


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


280

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.

281

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.


282

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:

283

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.


284

Commands Intra Discipline Interference Check — Allows you to define that the interference-

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


285

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.



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.



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.


286

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.


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.


Accept Or Select Another Discipline Select all of the secondary disciplines to include in the matrix, and click Accept.

Note: Once you have selected the Active Discipline, you cannot change it until you reactivate the Exclusion of Interferences by discipline command.

287

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 User’s Guide (pp 77-80 in the PDS 7.1 version of the document).


• 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


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.





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


288

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.

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:

The following disciplines use generic routines to build envelope files:

1. Piping

2. Equipment

3. Structural

4. HVAC

5. Raceway

6. Architectural

7. PLANTGEN

8. User-defined

9. User-defined

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

289

Types of elements The generic envelope builder acknowledges only certain MicroStation elements.


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.





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

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.


290

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




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

291

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 User’s Guide (pp 255-260 in the PDS 7.1 version of the document).


• 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


1 , product_version_no , short2 , report_path , character(36)3 , report_node , character(26)4 , report_format_path , character(36)5 , report_format_node , character(26)6 , report_filter_path , character(36)7 , report_filter_node , character(26)8 , piping_eden_path , character(36)9 , piping_eden_node , character(26)10, eden_table_path , character(36)11, eden_table_node , character(26)12, piping_spec_path , character(36)13, piping_spec_node , character(26)14, assembly_path , character(36)15, assembly_node , character(26)16, model_builder_path , character(36)17, model_builder_node , character(26)18, design_review_path , character(36)19, design_review_node , character(26)20, std_note_lib_path , character(36)21, std_note_lib_node , character(26)22, eqp_eden_path , character(36)23, eqp_eden_node , character(26)24, tdf_table_path , character(36)25, tdf_table_node , character(26)26, clash_report_path , character(36)


292

27, clash_report_node , character(26)28, clash_plot_path , character(36)29, clash_plot_node , character(26)30, mdl_status_low_dr , short , standard note 160531, mdl_status_high_dr , short , standard note 160532, mdl_status_low_ic , short , standard note 160533, mdl_status_high_ic , short , standard note 160534, area_owner_opt_ic , short35, eqp_insul_opt_ic , short36, eqp_con_tol_opt_ic , short37, clash_rpt_index_no , integer38, report_search_path , character(36)39, report_search_node , character(26)40, sup_tdf_table_path , character(36)41, sup_tdf_table_node , character(26)

# Engineering Discipline Data


1 , discipline_indx_no , short2 , discipline_name , character(20)3 , intra_disc_ifc_flg , short4 , discipline_mtrx_a, integer5 , discipline_mtrx_b, integer

# Design Area Data


1 , discipline_indx_no , short2 , area_index_no , short3 , area_name , character(10)4 , area_description , character(40)5 , volume_low_x , integer6 , volume_low_y , integer7 , volume_low_z , integer8 , volume_high_x , integer9 , volume_high_y , integer10, volume_high_z , integer11, interference_mode , short12, area_lock_owner , character(10)13, area_lock_status , short14, area_lock_date , integer15, clash_rpt_index_no , integer

293

# Model Data


1 , model_index_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , partition_no , short5 , model_no , character(10)6 , model_description , character(40)7 , model_file_spec , character(14)8 , path_name , character(36)9 , network_address , character(26)10, lock_owner , character(10)11, lock_status , short12, lock_date , integer13, verification_date , integer14, revision_date , integer15, responsible_disc , short16, model_type , short17, model_status , short , standard note 1605

###################################################

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


1 , system_unique_no , integer , index 12 , discipline_indx_no , short3 , area_index_no , short4 , unique_sequence_no , integer5 , completion_date , integer6 , control_user_no , short7 , env_creation_date , integer8 , clash_check_option , short , standard note 12089 , volume_filter_opt , short , standard note 120910, volume_low_x , integer11, volume_low_y , integer12, volume_low_z , integer13, volume_high_x , integer14, volume_high_y , integer15, volume_high_z , integer


294

###################################################

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


1 , unique_clash_id , integer , index 12 , if_approval_status , short , standard note 12033 , comp_a_unique_id , integer4 , comp_b_unique_id , integer5 , model_index_no_a , integer6 , model_index_no_b , integer7 , discipline_index_a , short8 , discipline_index_b , short9 , recent_clash_type , short , standard note 120410, recent_plot_date , integer11, recent_review_date , integer , index 212, recent_sequence_no , integer13, area_index_no , short14, action_discipline , short15, recent_seq_no_b , integer16, area_index_no_b , short

###################################################

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


1 , system_unique_no , integer , index 12 , unique_clash_id , integer , index 23 , unique_sequence_no , integer4 , clash_type , short , standard note 12045 , comp_a_range_x_lo , integer6 , comp_a_range_y_lo , integer7 , comp_a_range_z_lo , integer8 , comp_a_range_x_hi , integer9 , comp_a_range_y_hi , integer10, comp_a_range_z_hi , integer

295

11, comp_b_range_x_lo , integer12, comp_b_range_y_lo , integer13, comp_b_range_z_lo , integer14, comp_b_range_x_hi , integer15, comp_b_range_y_hi , integer16, comp_b_range_z_hi , integer17, env_pair_type , short , standard note 1204

###################################################

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


1 , unique_comp_id , integer , index 12 , comp_table_number , short3 , comp_row_number , integer4 , model_index_no , integer5 , primary_descript , character(20)6 , secondary_descript , character(40)7 , comp_model_status , short

###################################################

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


1 , system_unique_no , integer , index 12 , unique_clash_id , integer , index 23 , review_date , integer4 , review_user_no , short5 , responsib_user_no , short6 , action , short , standard note 12057 , review_comment , character(100)8 , approval_method , short , standard note 1207


296

###################################################

Clash Plot History Information (PDtable_136) One record is created per clash plot.

################################################### # Clash Plot History Information


1 , system_unique_no , integer , index 12 , unique_clash_id , integer3 , plot_date , integer4 , plot_user_no , short

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 component’s interference envelope.

################################################### # Component Insulation Exclusion Data


1 , system_unique_no , integer2 , commodity_name , character(6)3 , model_code , character(6)4 , gcp_npd_from , short5 , gcp_npd_to , short6 , rcp_npd_from , short7 , rcp_npd_to , short8 , heat_tracing_from , short , standard note 2009 , heat_tracing_to , short , standard note 20010, insul_purpose_from , short , standard note 22011, insul_purpose_to , short , standard note 22012, nor_oper_temp_from , double13, nor_oper_temp_to , double

297

###################################################

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 component’s interference envelope. If this table is not loaded, the insulation thickness is completely included in the component’s interference envelope.

################################################### # Flange Insulation Exclusion Data


1 , system_unique_no , integer2 , bolted_npd_from , short3 , bolted_npd_to , short4 , heat_tracing_from , short , standard note 2005 , heat_tracing_to , short , standard note 2006 , insul_purpose_from , short , standard note 2207 , insul_purpose_to , short , standard note 2208 , nor_oper_temp_from , double9 , nor_oper_temp_to , double


298

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

Interference Checker/Manager (PD_Clash) User’s Guide Addendum October 2004 DPDS3-PB-200006C For PDS version 07.03.00.** This document supplements DPDS3-PB-200006B.

PDS Interference Checker/Manager User’s Guide Addendum – October 2004

300

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

301

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 User’s Guide (pp 287-290 in the PDS 7.2 version of the document).


• 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


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.





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


302

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.

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:

The following disciplines use generic routines to build envelope files:

1. Piping

2. Equipment

3. Structural

4. HVAC

5. Raceway

6. Architectural

7. PLANTGEN

8. User-defined

9. User-defined

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


303

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.





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

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


304

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




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.

305

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.


306

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 User’s Guide (pp 115-117 in the PDS 7.1 version of the document).


• 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 user’s initials are written to the Clash Review History data table, PDtable_135.

307

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.


308

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.


309

Select Clash Type Set the toggle to the appropriate setting and select the clash types to be approved.

Select Review Option Use one of the options described above to edit or examine the existing clashes.


310

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 User’s Guide (p. 251 in the PDS 7.1 version of the document).


• Error messages and warnings regarding invalid direction vectors, point locations, and lengths/radii.


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.

311

ERROR: - conic primary vector invalid


ERROR: - conic secondary vector invalid


ERROR: - torus primary vector invalid


ERROR: - torus secondary vector invalid


ERROR: - projected shape primary vector invalid


ERROR: - projected shape secondary vector invalid


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


ERROR: - semi ellipsoid secondary vector invalid


ERROR: - semi ellipsoid center point not within component range


ERROR: - revolved shape primary vector invalid


ERROR: - revolved shape secondary vector invalid


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.


312

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


WARNING: - cylinder center point not within 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


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


WARNING: - conic radius 2 less than 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


313

WARNING: - torus ellipse radius less than 20 UORs


WARNING: - semi ellipsoid primary radius less than 20 UORs


WARNING: - semi ellipsoid secondary radius less than 20 UORs


WARNING: - cylindrical string radius less than 20 UORs"



314

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

Interference Checker/Manager (PD_Clash) User’s Guide Addendum March 2007 DPDS3-PB-200006F For PDS 8.0 SE This document supplements DPDS3-PB-200006E.

PDS Interference Checker/Manager User’s Guide Addendum – March 2007

316

Table of Contents Exclusion of Interferences by Discipline (replaces 3.1.2) ........................................317 Construction Tolerances for Equipment Envelopes (replaces 3.1.5) .......................326 Envelope Builder (replaces 4.1) ...............................................................................327 Piping Design Area (replaces 4.1.2) .........................................................................337 Interference Checker (replaces 5.1) ..........................................................................338 Review PDS Clash (replaces 6.12)...........................................................................347 Setting InterPlot Parameters for Clash Plotting........................................................349 Revise Report Form (replaces 8.1.4.2) .....................................................................350

317

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 User’s Guide (pp 279-286 in the PDS 7.2 version of the document).


• Clarifications on the interactions among the Intra Discipline Interference Check, No Intra Discipline Interference Check, and Discipline Matrix Interference Check options.


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.

Tech Tip: 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.


318

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.

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.

319

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.

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.


320

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.

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.

321

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:

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.


322

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.

323

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.


— All models from all disciplines can be checked against each other, according to the settings for each discipline.

If you set the Intra Discipline Interference Check option for the selected discipline, any other discipline with the Discipline Matrix Interference Check option set will not be checked.

If you set the Intra Discipline Interference Check option for the selected discipline, any other discipline with the Intra Discipline Interference Check option or the No Intra Discipline Interference Check option set will be checked.

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.

Tech Tip: You should specify a matrix for the disciplines that do not require this sort of checking.




324

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.


— All models from all disciplines can be checked against each other, according to the settings for each discipline.

If you set the No Intra Discipline Interference Check option for the selected discipline, any other discipline with the Discipline Matrix Interference Check option set will not be checked.

If you set the No Intra Discipline Interference Check option for the selected discipline, any other discipline with the Intra Discipline Interference Check option or the No Intra Discipline Interference Check option set will be checked.

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.

Tech Tip: You should specify a matrix for the disciplines that do not require this sort of checking.



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.

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.

325

Caution: Defining a matrix for the selected discipline overrides the settings for the other disciplines in the matrix.

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.


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.


Accept Or Select Another Discipline

Select all of the secondary disciplines to include in the matrix, and click Accept.

Note: Once you have selected the Active Discipline, you cannot change it until you reactivate the Exclusion of Interferences by discipline command.


326

Construction Tolerances for Equipment Envelopes (replaces 3.1.5) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (p. 57 in the PDS 7.1 version of the document).


• Note regarding non-physical envelopes See the following text for details.

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.

Note: If you want non-physical envelopes to be checked, you must enable equipment construction envelopes, even if you do not set construction tolerance ON in Interference Checker Data.

327

Envelope Builder (replaces 4.1) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (pp 186-187 in the PDS 7.1 version of the document).


• Note about using clash review with structural models See the following text for details.

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.

Note: If you want to review clashes involving structural models in the clash approval manager, you must propagate all the structural models. Refer to the FrameWorks Plus documentation set for more details on propagating structural models.

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.

Tech Tip: 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.






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 component’s 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


328

extension. See the Interference Checker Output section of Understanding Interference Checking, page 25, for more information.

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.

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 component’s interference envelope.

green nominal piping diameter of the component (range search)

red nominal piping diameter of the component (range search)




For piping commodities, the Piping Envelope Builder searches for the component’s commodity name in the Component Insulation Exclusion Data Table using the preceding data.

If the piping commodity is defined in the exclusion table for those conditions, the applicable insulation thickness will not be added to the component’s interference envelope.

If the commodity name is not specified in the exclusion table for those conditions, the Piping Envelope Builder searches for the component’s 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 component’s interference envelope.

Otherwise, the insulation thickness will be included in the component’s interference envelope.

For piping specialties and instrument components, the Piping Envelope Builder searches for the component’s 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 component’s interference envelope. Otherwise, the insulation thickness will be included in the component’s interference envelope.

329

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.

Note: 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)




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 component’s interference envelope. Otherwise, the insulation thickness will be included in the component’s interference envelope.

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

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


330

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.

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 component’s 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 component’s 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 component’s interference envelope.

If the commodity name is not specified in the exclusion table for those conditions, the Piping Envelope Builder will search for the component’s 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 component’s interference envelope.

Otherwise, the construction tolerance will be included in the component’s interference envelope.

For piping specialties and instrument components, the Piping Envelope Builder searches for the component’s 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 component’s interference envelope. Otherwise, the construction tolerance will be included in the component’s interference envelope.

331

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.

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


332

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.

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

3. The clash envelope builder then uses the output of the Weld Clearance Table to draw the cylinder representing the clash envelope.

The weld clearance envelopes are drawn as two shapes, one for each pipe, using the radius increase and overall length increase measurements.

333

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

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.

Note: 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:

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.

Note: The envelope builder does not generate weld construction tolerance shapes at tap locations.

Note: 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,


334

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.

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

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.

Tech Tip: 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.

Application Considerations For the Model option, the system selects the correct interference envelope builder for each model’s discipline, including piping, equipment, structural, raceway, HVAC, and PLANTGEN, so envelope files can be created in the Interference Management environment rather than within each discipline’s 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.

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

335

More Info: For more information on Application Types, see the Create Model section of the Project Administrator Reference Guide.

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.


336

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.

337

Piping Design Area (replaces 4.1.2) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (pp 70-71 in the PDS 7.1 version of the document).


• Reference to the Mechanics subsection of the Envelope Builder section

• Removed Easting, Northing, and Elevation field descriptions See the following text for details.

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)

Note: To see the changes, you must re-create envelopes when data is modified. For information on creating envelopes, refer to Envelope Builder, page 326. The Mechanics subsection contains information on re-creating envelopes.

Before using this command Create a design area with a specific volume with the Create Design Area Data option in the Project Environment Manager.


338

Interference Checker (replaces 5.1) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (pp 90-97 in the PDS 7.1 version of the document).



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.

Tech Tip: The interference detection process and its results will vary depending on the settings defined on the Interference Checker Data form. These settings include:






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.

339

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.

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

Note: You must re-create equipment interference envelopes so that the nozzle connect point locations are added before false clashes will be eliminated.


340

Two equipment envelopes of the same type, as listed below, are clashing.

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

Note: 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 project’s 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 project’s Standard Note Library.

o 1 volume filter is inactive o 2 volume filter is active

341

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

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.

Note: 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 project’s 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.


342

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

343

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.

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


344

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.

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.

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

Note: Selecting the same model for Model A and Model B will generate false clashes. If you want to run the command on only one model, specify that model in the Model A field.

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.

345

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.

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.

Tech Tip: 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.

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.

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

Tech Tip: 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.

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


346

Note: The Generate and Verify Envelopes option is disabled for the Single/Pair Model Check command. This option should only be used with projects and areas.

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.


Before using this command 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.

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

347

Review PDS Clash (replaces 6.12) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (p 186-187 in the PDS 7.1 version of the document).



The Review PDS Clash command edits and reviews existing clashes and approves existing clashes.

Note: In order to review clashes involving structural models, the structural models must be propagated. Please refer to the FrameWorks Plus documentation set for more details on propagating models.

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.


348

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.

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.

349

Setting InterPlot Parameters for Clash Plotting The clash plotting commands use the InterPlot command line to generate plots. The ifc.i text file provides a method for specifying the parameters to be used with the InterPlot command line when plotting clashes. A default ifc.i file is delivered in the ..\win32app\ingr\PDCLASH\plot\ folder. You can use a different set of parameters for each project by creating an ifc.i file in the project folder and specifying the parameters you want to use for that project.

ifc.i File Example This section lists a typical ifc.i file. For detailed information about the parameters used in the ifc.i file, please refer to the documentation delivered with InterPlot. # IPLOT settings file view=1 units=inches mirror=off rendering_attributes=NONE pen_table=NONE feature_table=NONE paper_size=letter display[iplot_all]=[construction, dimension, enter_data, pattern, points, text_nodes, weight, file] nodisplay[iplot_all]=[level_symbology, width] fast[iplot_all]=[font, curve] nofast[iplot_all]=[text, cell] levels[iplot_master]=[1, 64] nolevels[iplot_master]=[2-63] rotation=90.000000 data_rescale=1.000000,1.000000


350

Revise Report Form (replaces 8.1.4.2) Note: The information in this section supersedes the information in the corresponding section of previous versions of the Interference Checker/Manager User’s Guide (p 226-228 in the PDS 7.1 version of the document).


• Changed “Revise Data Only” to “Revise Report and Data” in the last sentence of the Revise Data Only/Revise Report and Data toggle description.


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

351

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.

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


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.


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


352

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 Report and Data, and click Accept.

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

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.

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


353

Index building envelopes, 327 clash

exclusion by discipline, 317 clashes

plotting, 349 reviewing, 347

construction tolerances for equipment envelopes, 326

design area building envelopes, 337

discipline matrix, 317 Envelope Builder, 327 envelopes

building, 327 building by design area, 337 building by piping design area, 337 equipment, 326

equipment construction tolerances, 326

exclusion

by discipline, 317 integrated commands

Review PDS Clash, 347 interference

exclusion by discipline, 317 Interference Checker command, 338 interferences

reviewing, 347 InterPlot

parameters for clash plotting, 349 Piping Design Area command, 337 plotting

clashes, 349 reports

revising, 350 Review PDS Clash command, 347 Revise Report Form, 350 revising

reports, 350


354

Documents

Clash