pds clash manager.pdf

8/10/2019 PDS Clash Manager.pdf

1/314

Interference Checker/Manager(PD_Clash) Users Guide

Document Number Version Date PagesDPDS3-PB-200006A PDS 7.1 April 2002 1-274DPDS3-PB-200006B PDS 7.2 February 2003 275-298DPDS3-PB-200006C PDS 7.3 October 2004 299-314DPDS3-PB-200006D PDS 8.0 SE November 2005 Cover/Notice


2/314

CopyrightCopyright 1984-2005 Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audiovisual displays; may be used pursuant toapplicable software license agreement; contains confidential and proprietary informationof 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 LegendUse, duplication, or disclosure by the Government is subject to restrictions as set forth insubparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer SoftwareDocumentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of theLicense clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of CommercialComputer Software---Restricted Rights at 48 CFR 52.227-19, as applicable.

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

Intergraph Corporation

Huntsville, Alabama 35894-0001

Warranties and LiabilitiesAll warranties given by Intergraph Corporation about equipment or software are set forthin your purchase contract, and nothing stated in, or implied by, this document or itscontents shall be considered or deemed a modification or amendment of such warranties.Intergraph believes the information in this publication is accurate as of its publicationdate.

The information and the software discussed in this document are subject to changewithout notice and are subject to applicable technical product descriptions. IntergraphCorporation 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 orcopied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software onequipment that is not supplied by Intergraph or its affiliated companies. THE USER OFTHE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TOTHE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

TrademarksIntergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools,MARIAN, and PDS are registered trademarks of Intergraph Corporation. Microsoft andWindows are registered trademarks of Microsoft Corporation. MicroStation is aregistered trademark of Bentley Systems, Inc. ISOGEN is a registered trademark of AliasLimited. Other brands and product names are trademarks of their respective owners.


3/314

If You Need Assistance ________________

If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraphsproducts, 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 Way

Madison, Alabama 35758U.S.A.

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

3


4/314

________________

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


5/314

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


6/314

PDS Interference Checker/Manager Users 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 .................................................................................................. 119

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


7/314

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

6.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 .............................................................................................................. 177

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


8/314


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

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


9/314

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/314


10


11/314

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 of the 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 its 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_Designs Piping Clash Check command.

Section 6 explains the use of the Interference Approval Manager and Interference ManagementData options. It also contains information on PD_Designs 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 network address 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/314


12


13/314

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 identify

commonly used words, phrases, or groups of related information.

Typefaces Italic Indicates a system response, which is an explanation of what the software is

doing. For example,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. 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 Typewriter Indicates an actual file or directory name. For example,

The ASCII report is stored in the layout.rpt file.

13


14/314


Symbols

This document uses the following symbols to represent mouse buttons and to identify specialinformation:

Command button Data button (usually the left mouse button) Reset/reject button (usually the right mouse button) Tentative button (usually the center mouse button)

Note Important supplemental information.

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

Technical tip or information provides information on what the software 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 key

ENTER 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


15/314

Preface ________________

Terminology Click To use a mouse or key combination to pick an item that begins an

action. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by pickingit with your cursor. Selecting does not initiate an action. Afterselect ing 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 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 () 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 () 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/314


16


17/314

1 .W el c om e

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


18/314


19/314

2 .B a si c s

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 and Volumes , page 20 for more information.

2.2 Understanding Interference Envelopes See Understanding Interference Envelopes , 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 Interference Approving , 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


20/314


2.1 Understanding Design Areas andVolumes

This section thoroughly describes design areas and volumes and how they pertain to

interference checking.

Running the Interference Checker for an entire project takes considerably longer than 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


21/314

2 .B a si c s

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 Filter toggle 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


22/314


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


23/314

2 .B a si c s

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


24/314


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


25/314

2 .B a si c s

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:






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 of the 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 of models to be checked.

The Volume Filter toggle specifies a smaller volume of any of the options above.

Once the Interference Checker has been run, you can trouble shoot clashes involving apiping files items by reviewing the clashes interactively with the PD_Design software.

25


26/314


27/314

2 .B a si c s


PDS Interference Synopsis

vcpipe1.envNumber of clashes = 1

wwpipe1.envNumber of clashes = 0

wwpipe1.enveqmdl1.envNumber of clashes = 0

eqmdl1.envNumber of clashes = 0

vcpipe1.envwwpipe1.envNumber of clashes = 0

vcpipe1.enveqmdl1.envNumber of clashes = 3

PDS Interference Report

Da te : 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" PlantP601-12IN-1C0031-NNot approved

2 PIPING 5 524299 E 25 0" Plant N 3 0" Plant El 0 0" PlantP603-8IN-1C0031-NNot approved

PDS Interference Report

Da te : 28-Jun-93 Time: 13:43 :47

Model A Design File Name: vcpipe1


Model B Design File Name: eqmdl1


PDS Interference ClashesHard/Hard Clashes

No Item Name Table Row X Coord Y Coord Z Coord__ _________ _____ ___ _______ _______ _______

3 E90LR 3 524297 E 17 0" Plant N 10 0" Plant El 0 0" PlantP601-12IN-1C0031-NNot 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" PlantP601-12IN-1C0031-NNot 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


28/314

PDS Interference Checker/Manager Users 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


29/314

2 .B a si c s


29


30/314


31/314

2 .B a si c s

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


32/314

PDS Interference Checker/Manager Users 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


33/314

2 .B a si c s

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


34/314


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


35/314

2 .B a si c s

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 graphic

interference 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 of design 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


36/314

PDS Interference Checker/Manager Users 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


37/314

2 .B a si c s

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 the

job 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 a

batch 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 the

batch 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


38/314


39/314

3 .M an a g em en t

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 the

envelope 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


40/314

PDS Interference Checker/Manager Users 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 Manager Form , 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 Management Data , page 238.

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

40


41/314

3 .M an a g em en t

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 check Equipment design areas against Piping design areas and against Equipment design areas.

In a different situation, you may decide to use the No Intra Discipline Interference 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


42/314

PDS Interference Checker/Manager Users 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, see Exclusion 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


43/314

3 .M an a g em en t

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). See Models 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 areas

when 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 areas 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


44/314

PDS Interference Checker/Manager Users Guide - April 2002 ________________ By default, clash checking is done in Single (1) Design Area Ownership mode. In this mode,each clash belongs to the design area in which it was first found. When clash checking is 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 are

found.

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


45/314


46/314

PDS Interference Checker/Manager Users 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-R

E3 E-E, E-S, E-RR1 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 not reported.

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


47/314

3 .M an a g em en t

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


48/314

PDS Interference Checker/Manager Users 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 Discipline

Interference Check command would not be appropriate in this case, since theStructural Designer only wants to find Structural against Structural clashes.

48


49/314


50/314

PDS Interference Checker/Manager Users 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


51/314

3 .M an a g em en t


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 and

uses 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


52/314

PDS Interference Checker/Manager Users 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.

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 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 begin

defining 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 click Accept .

The responsible engineering discipline , as defined in the Model Data Table(PDtable_113, column 15) of the Project Control Database is used for determining 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 intra

discipline checking and click Accept or select the matrixoption.

Select Discipline Select a discipline to be the Active Discipline .

52


53/314

3 .M an a g em en t


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


54/314


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


55/314

3 .M an a g em en t

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


56/314


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


57/314

3 .M an a g em en t

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 specific

envelopes 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/314


58


59/314

4 .E nv el o

p e s

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. See Envelope Diagnostics , page 85 for more information.

59


60/314


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


61/314

4 .E nv el o

p e s

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 resp

pds clash manager.pdf

Documents