I saw this post on AUGI the other day, which hits on my primary motivation for starting this blog – creating a place where Navisworks users can come to find more information, a few pearls of wisdom if you like, suggested workflows, interoperability with other products, and so on.
Now I'm not suggesting that I have all the answers, in fact as the guys on AUGI here suggest, if everyone contributed a cool tip or trick, then we could quickly build up a great knowledge base. So if you want to contribute, please use the link on the left and Submit a Tip. Alternatively, if there's an area of the Autodesk construction products you'd like to know more about, why not Suggest a Topic.
One of the tips in this AUGI thread is to create a project template with all of your defined clash tests using an NWF. There is also another method that I believe will achieving the same result, using functionality that you may not be aware of:
Create Search Sets to categorize your project model.
Create a batch of clash tests, defined using Search Sets (in the Select tab), and set test types, tolerances and ignore rules. Name each test so that you can differentiate them.
Export the Clash Tests from the application menu, creating an XML file. This is your clash template file.
Now, whenever you start a new project, after appending all of your models, you can import your clash template file.
This will import the full batch of clash tests (with each clash test pre-defined along with rules etc.) with the added bonus of also importing all of the Search Sets you defined.
NOTE: As your initial tests are defined by Search Sets, they themself are defined by model properties, coming from Revit for example. In order for this workflow to work for you, it assumes that you'll be working on similar projects, with the same authoring applications being used to create the models – without this, the search sets would need to be updated to point to the relevant properties. Either way, as Paul Jordan says, this can save you a ton of time.