"Clash detection allows for the effective identification, inspection and reporting of interferences in a 3D project model."
Navisworks use the Clash Detective tool for to permit clash detection. It can help you to reduce the risk of human error during model inspections. It can also be used as a one-off 'sanity check' for a completed design work, or it can be used as an ongoing audit check of the project.
You can conduct clash tests between traditional 3D geometry (triangles), and laser-scanned point clouds or you can combine the Clash Detective functionality with other Autodesk Navisworks tools:
- Linking Clash Detective and Object Animation together gives you the ability to automatically check interferences between moving objects. For example, linking a Clash Detective test to an existing animation scene would automatically highlight clashes for both static and moving objects during the animation, for example, a crane rotating through the top of a building, a delivery lorry colliding with a workgroup, and so on.
- Linking Clash Detective and TimeLiner together enables the time-based clash checks on the project. See Select Items for Testing for further details on time-based clashing.
- Linking togetherClash Detective, TimeLiner, and Object Animation enables clash testing of fully animated TimeLiner schedules.
Clash Detective also allows you to create custom clash tests via Exported clash tests. If you have a common set of clash tests that you reuse on multiple projects, you can turn them into a custom clash test. Once installed as a custom clash test, the entire batch of tests can be selected and run directly from the Select Tab. The results from all tests in the batch are combined and presented as the results of the custom clash test. The name of each test in the batch is displayed in the Description field of the results.
Custom clash tests are an excellent way to roll out a standardized set of tests across an organization. They allow the expertise of "power" users to be reused by everyone. Finally, they can be seen as a way of implementing object intelligence. For example, a custom clash test could be written that checked for compliance with a local building code based on object information and properties defined in a particular CAD system.
And last, but not least - there is report functionality. For instance, you may need a report that will enable planners to adjust the project schedule in their 3rd party scheduling software.
For time-based clashes, it may be helpful to include in the report additional information about each static package in the clash. This information can be set up in the Options Editor by using the Smart Tags definitions.
As always, please share any feedback, comments or suggestions you may have.