Last week there was a big new update to BIM 360 Glue, Joan Allen, Senior Product Manager for BIM 360 Glue talks to us about it in more detail.
One of the many advantages of using cloud-based products and services is the immediate, automatic access to product updates. The Autodesk BIM 360 product team thrives on providing regular, timely updates, often based on direct feedback
from customers. The latest BIM 360 Glue update
– designed and developed in response to customer feedback – provides powerful new clash resolution capabilities, so that you and your team can more efficiently and effectively manage the collaborative project coordination process.
Introducing Clash Status
With anywhere, anytime access to the most recent project models and data, BIM 360 Glue
empowers project teams to quickly identify coordination issues. The latest BIM 360 Glue update enhances this ability by providing tools for tracking and managing active and resolved clashes. There are four new status levels for clashes (Open, Ignored, Closed, and Resolved) so teams can to track progress and focus on resolving the most critical and current coordination issues. Clash Status Clash ID’s and comments are maintained across model versions, ensuring that everyone is working with the most up-to-date information.
Clash Status and Workflow
Here is a breakdown of the new clash status settings, to help you determine how to best apply them to your project coordination workflows:
Ignored – The “ignored” status can be set by model contributors (designers and detailers, typically users with “full” permission) as well as VDC/BIM managers (project admins). This supports a collaborative coordination approach, where model contributors can suggest which clashes should be ignored to the VDC/BIM manager.
Closed – The “closed” status can also be used to mark issues that won’t be resolved during preconstruction coordination. The difference between “closed” and “ignored” is that “closed” provides a more formal level of control for VDC/BIM managers. While other team members can mark a clash as “ignored,” only admins can actually “close” a clash.
Resolved – This is a system-generated status to identify clashes from previous that have been fixed.
Open – This is a system-generated status to identify clashes that are either new or haven’t been ignored, closed, or resolved. If an “open” clash has a notification, markup, or comment, its clash ID will be maintained across subsequent model versions, even if it remains open.
Focus on resolving current coordination issues
In addition to clash status, there are new filtering options that make it easy to focus in on specific clash issues and accelerate clash review. You can filter by clash status to see only Open, Ignored, Closed, or Resolved issues (or any combination, such as Closed and Resolved). You can further refine the display by filtering on notification status, to see only Open clashes you have been notified about, for example.
Status overview at a glance
Communicate with your project team
Filter by status and notification type
The new clash markup tool provides an efficient method for adding a markup directly to a clash result to better communicate the issue and suggested solution.Clash markups are not only available in the clash module, but also in the markups module across the BIM 360 Glue solution (desktop, web, and mobile).
Clash markup view in the clash module
Clash markup view in BIM 360 Glue mobile
We have also updated the measurement tools to automatically calculate the XYZ differences between objects, to make it easier to determine clearances and when reviewing clashes.
Try the new BIM 360 Glue clash resolution features for collaborative, team-based coordination workflows, and let us know if you have any feedback
Joan E. Allen, P.E., is a Senior Product Manager at Autodesk and manages BIM 360 Glue. A graduate of the University of California, Berkeley with a degree in Civil Engineering, Joan is a registered Civil Engineer with over 25 years of experience in construction management and technology for the construction industry.
Follow Joan at @joanallen