How did we catch a 170k mistake before it was made
1
BidLight catches a costly design change by comparing each new publish with the last one, so a change made after the set was issued shows up before the crew builds it.
add comment
Answers
0
<p>BidLight catches a costly design change by comparing each new publish with the last one, so a change made after the set was issued shows up before the crew builds it. Most teams find these gaps at closeout, when they are real losses.</p>
<p>Here is how BidLight keeps it a near miss:</p>
<ul><li><strong>Publish the model, not a snapshot in an email.</strong> Revit and Navisworks publishes become versioned snapshots with author and milestone.</li><li><strong>Compare against what the field has.</strong> Differences list element by element, by category.</li><li><strong>Pin the conflict.</strong> Issues attach to the elements, with the sheet and revision.</li><li><strong>Name an owner.</strong> They see it in the 6am digest.</li><li><strong>Close with proof.</strong> A screenshot, a tagged user and the linked model commit.</li></ul>
<p>The saving is the gap. A clash caught in the model costs about $50. Caught in the field it costs $5,000 to $50,000, and it can burn $15K to $50K a week in idle labour.</p>