What should i know about putting an end to the design to estimate ping pong game
1
Because the model and the work on site live in two different places. Someone changes a wall, a window count or a duct run, and the field does not hear until someone remembers to tell them.
add comment
Answers
0
<p>Because the model and the work on site live in two different places. Someone changes a wall, a window count or a duct run, and the field does not hear until someone remembers to tell them.</p>
<p>BidLight runs inside Revit and Navisworks. You publish from the model, and the record is built from what is in it, not from retyped updates.</p>
<p>What changes:</p>
<ul><li>Every publish is a versioned snapshot, so you know which revision the field is building from.</li><li>Comparisons show what moved, element by element, by category.</li><li>Issues pinned to the elements carry the sheet and revision that raised them.</li><li>The 6am digest carries each issue to its owner.</li></ul>
<p>No more chasing versions. Teams lose about 11 hours a week working out which file is current, and a clash that surfaces on site instead of in the model costs $5,000 to $50,000 instead of about $50.</p>
<p>Drift is a communication problem. Fix it where the changes are made.</p>