twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

BIM 360 Model Coordination Update – June 19, 2019

PaulW_ADSK
June 19, 2019

The June 19, 2019 update for Model Coordination introduces property-based clash grouping and adds support for IFC files from MagiCAD for Revit.

Property-based Clash Grouping

The latest release of Model Coordination uses inherent BIM object data to create meaningful groups of clash data. Format specific options for Revit (RVT), AutoCAD (DWG) and IFC, such as System Name, Layer and Type Name, greatly increase user efficiency when classifying and assigning clashes for action.

Format Specific Grouping Options

Based on the model format you choose to group clashes by, will determine which options you can further group by. This includes:

Revit (RVT)

  • Object
  • System Name
  • Type Name

AutoCAD (DWG)

  • Object
  • Layer

IFC

  • Object
  • ifcSystem
  • Type Name

IFC Support from MagiCAD for Revit

Building on IFC support introduced earlier this month, Model Coordination can now work with IFC files exported from MagiCAD for Revit.

MktoForms2.loadForm(“//app-ab10.marketo.com”, “572-JSV-775”, 2332);

#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
width:0px;
}
#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;
}
#Email{
width: 75%!important;
}
#LblEmail{
width: 84px!important;
}
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol{
margin-top: 10px;
width: 100%;
}

Subscribe to email digests.

Featured Links

PaulW_ADSK

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.

2 Comments

View by:
Most Recent Oldest
  1. AvatarDMMakarov

    Wow
    It is great

  2. Avatarantonio.alonso@crtkl.com

    Hi Paul, when an issue coming from a clash is created on Model Coordination, the person that receives the notification and clicks in the link can only see one Revit model (one Revit link is attached, not two), which is not useful because you do not see the proper clash and makes the whole process very difficult for the Revit Users. Do you know if Autodesk is working on fixing this?

'