twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

BIM 360 Model Coordination Update – April 29, 2019

April 29, 2019

The April 29, 2019 release introduces comprehensive issue review capability within Model Coordination – connecting the workflow of finding and assigning clashes to project members, and then reviewing and editing the issue details in context of multiple models with preserved clash highlighting.

Issues side panel within the Model Coordination viewer

Details of assigned clashes can now be reviewed within Model Coordination, in context of a multi-model view. Objects involved in the clash will have their color highlighting preserved.

Issue details can be edited within Model Coordination, add attachments, update the status and communicate with other project members via the Activity thread comments.

The viewer displays pushpins for all issue types associated with the loaded models. Adding additional models into the viewer can provide more context, and corresponding clashes and issues will be loaded dynamically.

When viewing a clash issue, if any clashing models are not currently loaded, you will be prompted to automatically load them into the viewer. When viewing a non-clash type issue within Model Coordination, unrelated models will appear ghosted (hidden) in the viewer.

Introduction of Assigned Clashes tab in Model Coordination

The Assigned clashes tab provides a list of issues associated with clashes (Coordination > Clash type) including status, assignee and due date. It further provides a link back to the multi-model view, with preserving clash highlighting.

Creation of Coordination > Clash type issues when assigning clashes

Differentiating assigned clashes from Design type issues will help in filtering and populate the coordination-specific Project Home dashboard cards, providing summary and trend insights into the coordination status of the project.

MktoForms2.loadForm(“//”, “572-JSV-775”, 2332);

#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
#mktoForm_2332 > div.mktoButtonRow > span > button{
color: #fff;
background-color: #1858A8 !important;
background-image: none !important;
border: 0px !important;
#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoLogicalField.mktoCheckboxList.mktoHasWidth.mktoRequired, #mktoForm_2332, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField
{width: 100%!important;}
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoOffset,#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
display: none;
width: 75%!important;
width: 84px!important;
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol{
margin-top: 10px;
width: 100%;

Subscribe to email digests.

Featured Links


Paul is a Sr. Product Manager in Autodesk Construction Solutions leading the group building model coordination workflows across Autodesk Construction Cloud. Paul was part of the Navisworks acquisition in 2007 and has been in software development for 20 years.

1 Comment

View by:
Most Recent Oldest
  1. AvatarYan.ZepfKGZH2

    Hi, just wondering how accurate are these clash results in comparing with the Navisworks clash results? can we replace Navisworks for clash analysis?