APPENDIX 1

Clash Check Procedure

CONTENTS
1.0 SCOPE............................................................................................................................................ 3
2.0 INSTRUCTION................................................................................................................................ 3
2.1 Types of Clash Checks................................................................................................................ 3
3.0 SET UP FOR THE INITIAL “WITHIN DISCIPLINE CLASH CHECK”..............................................4
3.1 Set up for the Subsequent “Within Discipline Clash Checks”.....................................................12
4.0 SET UP FOR THE INITIAL “INTER-DISCIPLINE CLASH CHECKS” BY PIPING.........................12
4.1 Set up for the Subsequent “Inter Discipline Clash Checks” By Piping.......................................16
1.0 SCOPE

This document provides instructions on performing Clash Checks using NavisWorks Manage 2009
Version 6.1

2.0 INSTRUCTION

NavisWorks provides tools for checking clashes between all the models in the project. Details are
provided in the following sections.

2.1 Types of Clash Checks

Two types of Clash Checks shall be performed. Those performed within and run by the discipline
concerned and those performed between disciplines and run and managed by the Piping Group.

Within Discipline Clash Check Types File Name

PIPING to PIPING (PI-PI)

PIPING to EQUIPMENT (PI-EQ)
STRUCTURAL to STRUCTURAL (ST-ST)
ELECTRICAL to ELECTRICAL (EL-EL)

Inter-Discipline Clash Check Types File Name

PIPING to STRUCTURAL & CIVIL (PI-ST)

EQUIPMENT to STRUCTURAL & CIVIL (EQ-ST)
ELECTRICAL to PIPING & EQUIPMENT (EL-PI)
ELECTRICAL to STRUCTURAL & CIVIL (EL-ST)

Note Structural Models should include all Building or Architectural Models

Basic Principles – Please Read

NavisWorks Manage Clash Detective works by either clash checking the models highlighted in the
Left hand pane of the “Select” tab against Models highlighted in the Right hand pane of the “Select”
tab.
Or by internally self checking within individual models highlighted in the Left hand pane of the
“Select” tab.

It does not matter how many models are loaded in NavisWorks Manage (they will all appear in both
panes) only those highlighted will be clashed.

For Inter-Discipline Clash Checks the required Model of the discipline to be checked must be
highlighted in the Left pane. All the models of the other discipline that the first model is to be
checked against must be highlighted in the Right pane.
The “Self Intersect” box must be left unchecked under both panes.
For Within Discipline Clash Checks only the required models of the specific discipline in the Left
hand pane need to be highlighted, providing that the “Self Intersect” box is checked under the Left
Hand pane.

Once the first check of any batch is run the results are retained, compared and updated during
subsequent runs.

3.0 SET UP FOR THE INITIAL “WITHIN DISCIPLINE CLASH CHECK”

PIPING to PIPING (PI-PI)

PIPING to EQUIPMENT (PI-EQ)
STRUCTURAL to STRUCTURAL (ST-ST)
ELECTRICAL to ELECTRICAL (EL-EL)

 Each discipline will set up individual NavisWorks Manage Clash models as follows.

 Open Clash Detective from Tools in NavisWorks Manage (not Review)

 From File\Open load All your specific discipline model.dwg’s for the Area or Plant

BATCH / SELECT

 Open the “Select” tab and in the Left hand pane highlight the required model or models to be
self checked.

 Only the highlighted models in the Left hand pane apply to the batch being run. As this is an
internal Self check of a single discipline model do not Highlight anything in the Right hand pane

 Open the “Batch” tab

Note:- Batches can be single or multiple per each NavisWorks nwf file.

 Click the edge of “Test 1” and rename it as “TYPE”-“AREA/MODEL NUMBER”-“mmddyy” Click

outside the rename box to accept the name.

 i.e. PI-PI-TM01-2-02-01-062410

 If using multiple Batches. Open Batch and click Add and another “Test 1” will appear.

 Open “Select” and In the Left pane highlight the additional model or models to be self checked.

 Go back to “Batch” Click the edge of “Test 1” and rename it as “TYPE”-“AREA/MODEL

NUMBER”-“mmddyy” Click outside the rename box to accept the name.

 Repeat for other Batches

 Do NOT hit “Update” during the initial set up

 Select “Standard” and the rectangular icon below the panes

 Check “Self Intersect” under the Left hand pane

 Select “Hard” from the Type drop down

 Set Tolerance(m) to 0.001

 Select “None” from the Link drop down

RULES
 Open the “Rules” tab

 Check all boxes except “Items in the same file”

 Open “Batch” and highlight the batch to be run

 Open “Select” and click “Start”

RESULTS

 Open the Results Tab

 Under Display, check Auto Zoom, Save Viewpoint, Dim Other and Simulation.

 The First time the Clash Check is run all of the clashes will appear as “New” (Red)

 Before the report is saved ALL Clash’s must be statused as either “Approved” (Green) or “Active”
(Orange). NO Clashes are to left Red
 A Senior Designer must review every “New” Clash and determine whether it is a false “Approved”
clash with no action required or a genuine “Active” clash needing attention.

 Whilst reviewing the Clash’s it is useful to temporarily check “Hide Other” to hide all the
components except those that are clashing.

 The status can be changed by clicking the clash and picking the appropriate status from the drop
down.

 The initial Clash run will produce a large amount of “false” Clashes. However once these are
“Approved” they will not return on subsequent Clash runs and their number will significantly
reduce as the Project progresses.

REPORT

 Check the box’s as shown

 Select “Current Test” in the Report Type dropdown

 Select the “HTML” in the Report Format dropdown

 Click “Write Report”.

 Check that the report name for the current batch is in the format “TYPE”-“AREA/MODEL
NUMBER”-“mmddyy” i.e: PTP-1700-060910 and save the report in the appropriate Discipline
Clash Check\ Clash Reports folder.

 For multiple batches write reports for each of the other batches

 Save As the NavisWorks Manage Clash Model as “AREA/MODEL NUMBER”.nwf in the

Discipline Clash Check\ Clash Model folder.

The Report will contain an .html file together with .jpg’s showing a snap shot of each clash.
Opening the .html file will show the report with embedded snap shots
Inform the Lead that the Clash Check is complete. The Lead will assign designers to resolve all
“Active” (Orange) Clashes before the next clash run.

Whilst it is possible for designers to dynamically view the NavisWorks .nwf clash model it is
recommended that they only use the Clash Reports to view “Active” Clashes to avoid corruption of
the clash model for future clash runs.

Consideration should be given as to whether the permissions to the Inter-Discipline and Discipline
Clash Report folders can be limited to the designated discipline Clash Checkers. Possibly a copy of
those clash models can be made for public access
3.1 Set up for the Subsequent “Within Discipline Clash Checks”

 For subsequent clash checks open the previously saved NavisWorks .nwf Clash Model from
the Discipline Clash Check\ Clash Model folder.

 The Batches and their individual model Selections have been retained from the initial Clash
Check

 Open the Batch tab and hit “Update” All batches will update and produce New Clashes.

 Results will show New Clashes (Red), previously Approved Clashes (Green) and previously
Active Clashes now Resolved (Yellow).

 If there are still any Active Clashes (Orange) unresolved from the previous Clash run do not
continue the check and report to the Lead that previous clashes have not been resolved

 Status any “New” clashes to Approved or Active as described previously

 In Report, uncheck Approved and click “Write Report”. Rename the report with new date as
described previously and save in the appropriate Discipline Clash Check\Clash Reports folder.

 For multiple batches write reports for each of the other batches

 Save the NavisWorks Manage Clash Model – Do not Rename

4.0 SET UP FOR THE INITIAL “INTER-DISCIPLINE CLASH CHECKS” BY PIPING

PIPING to STRUCTURAL & CIVIL (PI-ST)

EQUIPMENT to STRUCTURAL & CIVIL (EQ-ST)
ELECTRICAL to PIPING & EQUIPMENT (EL-PI)
ELECTRICAL to STRUCTURAL & CIVIL (EL-ST)

The Setup is similar to the Initial “Within Discipline” Procedure with the following
exceptions.

 From File\Open Load or Append All the model.dwg’s for All disciplines for the Area or the
Plant.

BATCH / SELECT

 For larger Projects a separate NavisWorks Manage model should be setup for each Area,
each with the 4 batches named above.

 Open the “Select” tab and in the Left pane highlight the specific Discipline model to be checked.

 In the Right Pane highlight All of the other specific discipline models to be checked against
 Open the “Batch” tab

 Click the edge of “Test 1” and rename it as “TYPE”-“AREA/MODEL NUMBER”-“mmddyy” Click

outside the rename box to accept the name.

 i.e. PI-ST-TM01-2-02-01-062410

 Open Batch and click Add and another “Test 1” will appear.

 Open “Select” and In the Left pane highlight the next specific discipline model or models to be
checked.

 In the Right pane highlight the All of the next discipline models to be checked against.

 Go back to “Batch” Click the edge of “Test 1” and rename it as “TYPE”-“AREA/MODEL

NUMBER”-“mmddyy” Click outside the rename box to accept the name.

 i.e. EL-PI -TM01-3-02-01-062410

 Repeat for other Batches

 Do NOT hit “Update” during the initial set up

 Select “Standard” and the rectangular icon below the panes

 UN-Check “Self Intersect” under the both panes

 Select “Hard” from the Type drop down

 Set Tolerance(m) to 0.001

 Select “None” from the Link drop down

 Open “Batch” and highlight the batch to be run

 Open “Select” and click “Start”

RESULTS

 Review and status all New (Red) Clashes as described previously

 Penetration clashes with platforms should be statused as “Active”(Orange) Structural will

provide a hole in the platform which will “Resolve”(Yellow) the Clash on the next run.

 Penetration clashes with Building Walls should be statused as “Approved”. Building

Penetrations are provided as required by the Building Vendor

REPORT

 Wright individual batch reports as described previously and save them in the Project Inter-
Discipline Clash Check\Clash Reports folder.

 Save As the Area NavisWorks Manage Clash Model as AREA or MODEL NUMBER.nwf
in the Inter-Discipline Clash Check\Clash Model folder.

 Inform the Lead that the Clash Check is complete. The Lead will Inform the Project
Manager who will distribute the Reports and request that all disciplines must resolve all
“Active” (Orange) Clashes before the next clash run.

To Avoid corruption of the Inter-Discipline Clash Model consideration should be given as to whether
the permissions on this Model can be limited to the designated Piping Clash Checker. Possibly a
copy of this model can be made for public access.

4.1 Set up for the Subsequent “Inter Discipline Clash Checks” By Piping

 For subsequent clash checks open the previously saved NavisWorks .nwf Clash Model from
the Project Inter-Discipline Clash Check\Clash Model folder.

 The Batches and their individual model Selections have been retained from the initial Clash
Check

 Open the Batch tab and hit “Update” All batches will update and produce New Clashes.

 Results will show New Clashes (Red), previously Approved Clashes (Green) and previously
Active Clashes now Resolved (Yellow).

 If there are still any Active Clashes (Orange) unresolved from the previous Clash run do not
continue the check and report to the Lead and Project Manager that previous active clashes have
not been resolved

 Status any “New” clashes to Approved or Active as described previously

 In Report, uncheck Approved and click “Write Report”. Rename the report with new date as
described previously and save in the Project Inter-Discipline Clash Check\Clash Reports folder.

 For multiple batches write reports for each of the other batches

 Save the NavisWorks Manage Clash Model – Do not Rename

Whilst it is possible for designers to dynamically view the NavisWorks .nwf clash model it is
recommended that they only use the Clash Reports to view “Active” Clashes to avoid corruption of
the clash model for future clash runs.

Consideration should be given as to whether the permissions to the Inter-Discipline and Discipline
Clash Report folders can be limited to the designated discipline Clash Checkers. Possibly a copy of
those clash models can be made for public access