Why does a cable tray show as clashing in navisworks and how do i confirm which
1
A cable tray usually clashes in Navisworks because two trades modelled it at different times and neither saw the other's change.
add comment
Answers
0
<p>A cable tray usually clashes in Navisworks because two trades modelled it at different times and neither saw the other's change. One export got published, the tray moved or a duct got rerouted, and the federated model now shows a conflict that may not exist in the field.</p>
<p>Confirm the real conflict and the owner like this:</p>
<ol><li>Publish from Revit and Navisworks so the export is versioned, not overwritten.</li><li>Diff the new export against the last one element by element. That tells you what moved and when, so a phantom clash from a stale copy drops out.</li><li>Open the clash and check both elements are in the current commit. If they are, it is a real conflict.</li><li>Pin the issue to the element itself, not to a screenshot in someone's inbox.</li><li>Assign the tagged owner, then close only with proof: screenshot, tagged user and the model commit that fixed it.</li><li>Check the 6am digest to confirm the owner sees it and it is not sitting idle.</li></ol>
<p>The reason it matters: a clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000. An unresolved one burns $15K to $50K a week in idle field labour. Catching it before the crew mobilises is the whole saving.</p>