Want to catch a 2 inch clash before it becomes a change order that blows your budget
1
You catch a small clash early by tracking every model change and clash between revisions, pinned to the elements involved, so it is resolved in the model while the crew is still standing by.
add comment
Answers
0
<p>You catch a small clash early by tracking every model change and clash between revisions, pinned to the elements involved, so it is resolved in the model while the crew is still standing by. A clash caught in the model costs about $50, against $5,000 to $50,000 in the field.</p>
<p>Here is how BidLight handles it:</p>
<ul><li>Publish from Revit or Navisworks. Each publish is a versioned snapshot.</li><li>Compare any two revisions element by element, grouped by structural, MEP, envelope and interior, to see what moved.</li><li>Pin the issue to the elements. It carries the sheet and revision it came from.</li><li>The owner sees it in their 6am daily digest.</li><li>Closing it needs proof: a screenshot, a tagged user and the linked model commit.</li></ul>
<p>An unresolved clash can burn $15K to $50K a week in idle field labor. You present a record instead of absorbing a change order.</p>