If my mep sub works in navisworks and never opens our portal how does he close h
1
Your sub never has to leave Navisworks. BidLight runs inside it, so he publishes straight from the federated model and works his issues right there. Here is the loop: 1.
add comment
Answers
0
<p>Your sub never has to leave Navisworks. BidLight runs inside it, so he publishes straight from the federated model and works his issues right there.</p>
<p>Here is the loop:</p>
<ol><li>He opens Navisworks and works the federated model like he already does.</li><li>The issues assigned to him show up pinned to the element they concern. No hunting through Teams, email or Bluebeam for the one he needs.</li><li>He fixes it, then closes it with proof: a screenshot, his tagged user and the model commit that fixed it.</li><li>He publishes a new export. BidLight versions it and compares it element by element, so the team sees what actually changed.</li><li>The 6am digest tells every owner what they still own, so nothing goes quiet.</li></ol>
<p>That last part is where the money is. A clash caught in the model costs about $50. The same one found in the field runs $5,000 to $50,000. An unresolved one can burn $15K to $50K a week in idle field labour. Getting your sub to close issues where he already works keeps clashes in the model instead of the field.</p>