The BIM Collaborate Pro (ABC Pro) service on the Autodesk Construction Cloud has been a very successful product over the last few years, providing design teams the ability to work remotely on Revit models with Cloud Worksharing enabled. However, very few have used the full features that are available in ABC Pro. One of the features included is the Model Coordination module. It can compile models together and run clash detection tests, and as design teams continue to develop their project, it can continue to run clashes automatically and provide valuable information on building elements interfering with each other.
Why not have an extra set of “eyes” to help spot potential issues during the design phase before they become real issues in construction?
Well, quite frankly, it was hard to read the clash results, mainly because there weren’t enough options to filter specific groups of elements. That is until recently. After you select the models and create a view in Model Coordination, the contents of the view can be filtered using the Model Browser. Elements can be filtered by Discipline, Assembly, and Categories. So now you can choose only what you want to see from the clash results.
If you know Revit, then the Disciplines and Categories settings are pretty straightforward in how they relate to the families. The Assembly, on the other hand, is related to the “Assembly Description” parameter that is built into the type properties of some component and system families.
Ideally, if you’re using Design Collaboration and sharing models copied to the “Shared” folder, you can create a coordination space for the folder, which is a default option when setting up Design Collaboration. Each time the models are updated and shared in Design Collaboration, the design team can review the clash results, create Issues, and track their resolution.
But maybe you prefer using the Clash Detective feature in Navisworks?
Model Coordination is great for automating the clash detection tests and offering a “set it and forget it” type of workflow, but Navisworks can use pre-defined clash tests, select elements with rule-based Search Sets, and can generate reports in multiple formats.
Previously, the models copied to the “Shared” folder didn’t contain the parameters from Revit that are commonly used in Search Sets. This appears to be fixed and now you can apply rules set for Category, Function, System Classification, System Type, and anything else available in the element properties.
BUT, you should Append the models in the “Shared” folder from the project connected via Desktop Connector, and not from the Coordination menu.
The models opened from the Coordination menu are intended to view the models and Issues set up from Model Coordination, and they do not contain any of the parameters from Revit.
Could the Model Coordination module be better? Absolutely, but I think it’s improved to the point that design teams can effectively incorporate clash detection into their project workflow. Or, alternatively, you can open the models in Navisworks for more advanced features.
And as Autodesk continues to develop the Autodesk Construction Cloud, Model Coordination is only going to get better in the future.
UPDATE (1/3/24): It took a little while to test this, but back in September, Autodesk introduced Advanced Filters in Model Coordination.
It’s a different workflow, but it gets really close to the custom filter results that you can achieve with Search Sets in Navisworks. And along with the Issues feature, it makes Model Coordination a compelling tool for managing clash interferences.