Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Revit MEP 2017 Finds More Clashes Than Navisworks Manage 2017

kempbillton
Contributor

Revit MEP 2017 Finds More Clashes Than Navisworks Manage 2017

kempbillton
Contributor
Contributor

So we just got Navisworks Manage 2017 in our office, which includes the 'Clash Detective' feature... It's a nice alternative to Revit MEP's 'Interference Check' because Revit can struggle with finding a good view for your interference (e.g. it could be a clash right next to where you're looking on the screen, but it takes you to the Roof Plan. Good one!)... It's also nice to see the 3D clash with rendering. 

 

But after going through and adding insulation to all the hydronic and domestic water piping in the model, and adding insulation to the ductwork, I've found that Manage will show very few (or sometimes none) of the clashes that Revit will pick up. Manage can say 0 clashes, and Revit will pick up 250 of them!

 

Note: I pick all the same categories in both programs (e.g. pipe fittings, pipe, pipe insulations... vs duct fittings, duct, duct accessories), and Manage still doesn't seem to find anywhere near as many as Revit.

 

Anyone else experienced issues with this?

0 Likes
Reply
Accepted solutions (1)
1,138 Views
6 Replies
Replies (6)

USJM05000
Advocate
Advocate

Navisworks provides options for ignoring conflicts that are _not_ of interest.  Check if anything on the Clash Detective Rules tab or the Select tab Settings area for that particular Clash Test might be excluding clashes of interest.

 

Joe M in WV

0 Likes

kempbillton
Contributor
Contributor
Accepted solution

Joe,

 

Thanks for the input! I checked it out- and we actually don't have anything checked under Rules.

 

I figured it out though- the best way to explain is by example:

A duct appeared on the Second Floor at 11'-0".... But in reality it was actually referencing the First Floor at 25'-0"!! So Revit was picking up all these clashes because we weren't running the test by floor/level. In Manage we had run the tests by floor and, if something isn't actually associated with the First Floor then it won't appear in a Second Floor test!!

 

0 Likes

USJM05000
Advocate
Advocate

Good catch!  Other issues when testing by Level are vertical elements passing through multiple Levels and elements grouped in the "No Level" catagory.

 

Setting up and clash testing by Search Sets seems to minimize unexpected/undesired results.  Obviously Search Sets are also dependent on quality of received models.  However, Search Sets have the flexibility to overcome a significant number of authoring inconsistencies.

 

Rules are a tremendous help in minimizing time spent on spatial coordination.  Definitely worthwhile learning about Clash Rules for frequent and/or advanced use of Clash Detective.

 

Regards,

 

Joe M in WV

0 Likes

kempbillton
Contributor
Contributor

I'm still very new to Manage, and actually to Navisworks in general.

 

For whatever reason, the duct and pipe insulations are only showing up in <No Level> ... and when I Include those in the Select tab, it seems to show clashes ANYWHERE that insulation is causing a clash...

example:

I have a test set up to only check Duct & Pipe clashes on the 1st Floor... but now that my insulation for duct and pipe are included on No Level, its showing clashes up on the 2nd and 3rd floors!

 

Under the Select tab, I have selected on 'Selection A' ONLY "1st Floor: Ducts, Accessories, Fittings" and then Duct Insulation from <No Level> ... 'Selection B' I have ONLY "1st Floor: Pipes, Accessories, Fittings' and then Pipe Insulation from <No Level> ... and yet I'm seeing clashes from multiple floors!

0 Likes

USJM05000
Advocate
Advocate

For Level specific clash testing, try exporting dedicated NWC Level specific NWC files for each ASMEP model.  Then append or merge all the various level models into one combined (federated) master model.  Clash testing the level specific files will not include elements from other levels, regardless of how the models were authored.

 

Its a lot more maintenance to work this way but helps to keep things sorted.  It also makes it possible to utilize separate combined (federated) models for each level, which can improve response time in large projects.

 

By Level NWCs.JPG

 

 

Joe M in WV

0 Likes

kempbillton
Contributor
Contributor

Thanks for your help and input!

0 Likes