What should i know about the cost of catching changes before the field itemized

1
The savings come from catching each change while it is still a model edit instead of a field fix: a clash caught in the model costs about $50, and the same clash in the field costs $5,000 to $50,000.
support@bidlight.com
asked 2 months agoSupport Team

Answers

0
<p>The savings come from catching each change while it is still a model edit instead of a field fix: a clash caught in the model costs about $50, and the same clash in the field costs $5,000 to $50,000. BidLight keeps one live record inside Revit and Navisworks, so each saving has a source you can point to.</p> <p>Here is where they come from:</p> <ul><li>Meeting time: comparing two revisions element by element answers what changed in about 15 minutes instead of a 90-minute meeting.</li><li>Rework: every publish is a versioned snapshot, so the change shows up before someone installs the old version.</li><li>Field labor: issues are pinned to the elements they concern and owners see them in a 6am digest, so a clash gets fixed while the crew is still elsewhere. An unresolved one can burn $15K to $50K a week in idle field labor.</li><li>Version confusion: about 11 hours a week go to working out which model version is current. The comparison answers it.</li><li>Closed means closed: an issue closes only with a screenshot, a tagged user and the model commit.</li></ul>
support@bidlight.com
answered 1 month agoSupport Team

Your answer

Browse other questions tagged  or  ask your own question.