How does bidlight stop clashes from turning into idle crew rework
1
BidLight stops it by tracking every model change and clash between revisions, pinned to the elements, so you catch problems while they are still cheap. A clash caught in the model costs about $50.
add comment
Answers
0
<p>BidLight stops it by tracking every model change and clash between revisions, pinned to the elements, so you catch problems while they are still cheap. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000 while the crew stands by.</p>
<p>Here is the workflow:</p>
<ul><li>Publish from Revit or Navisworks. Each publish is a versioned snapshot, and any two revisions compare element by element by category.</li><li>Read the 6am digest. It lists the issues assigned to you and anything due soon.</li><li>See who changed what and when, without a long meeting to find out.</li><li>Resolve each issue with proof. Closing one needs screenshots, a sign-off and the linked model commit, so nothing gets marked done without evidence.</li></ul>
<p>Issues are pinned to the elements they concern and carry the sheet and revision they came from, instead of being scattered across email and Bluebeam. You fix the problem in the model, and the crew keeps working.</p>