From Beyond Design
How to resolve coordination issues with BIM 360 Glue
Some people working with or implementing BIM 360 Glue ask us about best practice for managing clashes with BIM 360 Glue. Ultimately the goal is not to manage clashes but to resolve the issues causing these. Have this in mind when working through the process outline below, as it focuses not on individual objects clashing but about issues. For example, a single duct in the wrong location can cause 100 or more clashes. 100 clashes, but really just a single issue. And issues are what your design teams need to focus on for resolution. So here's how you do that with BIM 360 Glue.
Start by running your clash analysis. Use the visual heatmap to identify problematic areas in your model (here's a quick video of how this works). Did you know you can get a quick metric using the 'Overview' link of all clashes? It also lets you drill down further using the automatic grouping of clashes based on the originating models, e.g. mechanical model vs. structural. This is crucial as you cannot handle 3008 clashes this week and the grouping is the divide & conquer tool that helps you tackle it.Now you don't see single items clashing, but rather groups, e.g. a duct clashing with 3 other objects. The number in brackets tells how many objects the one you have selected is clashing with. And this also gives you the single issue to resolve.
- Create a markup for this issue. To keep track of issues, setup
folders (Open, Pending and Closed). Move this markup to the open folder.
As you move through the process ultimately all markups should end up in
the Resolved folder.
- Notify the relevant design team of at least the clash, so they can
resolve the issue. If you have some particular instruction which you
didn't add in your comments it will be useful to also notify of the
markup. It is crucial to notify them of the clashes as they can then use
the Clash Pinpoint feature inside their design application to locate
and resolve the problem.
After the design teams upload new versions of the model verify if the issue has been resolved. If true move the markup to the Closed folder, if not move to the Pending folder. You can use the Pending folder to bring up all unresolved issue for review during the next coordination meeting.
- Rinse and repeat.