• Revit

Spatial coordination for BIM for MEP systems

Describe the importance of running a clash test for the MEP system in Autodesk Navisworks Manage, pushing clash information to Revit, updating the live model, and verifying clash resolution.


00:03

When implementing BIM for MEP systems, the spatial coordination stage helps to ensure seamless integration across disciplines.

00:12

In this stage, after the initial layout of the MEP networks is generated,

00:18

clash detection is conducted on the Revit coordination model to identify conflicts between the MEP system and the architectural model.

00:28

Clash detection is performed using Autodesk Navisworks Manage or Model Coordination in Autodesk Construction Cloud (ACC).

00:38

Each solution plays a key role in efficient streamlining of project development.

00:43

The key difference between Navisworks Clash Detection and Model Coordination lies in their workflows,

00:50

level of automation, accessibility, and collaboration features.

00:55

Model Coordination provides automated workflows with limited preparatory work, as well as visual results in the clash matrix.

01:03

However, Navisworks allows for more file types and clearance detection, an important factor in constructability and safety considerations.

01:13

Navisworks Manage is best used when more advanced, detailed clash detection is needed during more complex coordination workflows.

01:22

Typically, it is used by BIM Managers or Coordinators who need a deep level of control over clash detection and reporting.

01:30

Clash detection in Navisworks Manage is a manual, highly customizable process

01:37

that allows users to define clash rules, filter clash results, and create clash reports.

01:43

Users can run hard, soft, and clearance clashes with specific tolerances.

01:49

It also supports clash grouping, rule-based filtering, and prioritization,

01:54

and it integrates with TimeLiner, Quantification, and other Navisworks tools.

01:59

It also supports a wide range of file formats, including IFC, RVT, DWG, NWC, NWD and many other authored formats.

02:12

The results yield detailed insights, listing clashes by location, element ID, and interference distance.

02:20

In contrast, Model Coordination provides cloud-based, automatic clash detection on models as soon as they are uploaded to ACC.

02:29

There is no need to set up clash detection tests manually, and the intuitive interface makes collaboration easy.

02:37

Model Coordination enables real-time issue tracking, clash grouping,

02:42

and makes assignment of issues seamless because it works within BIM 360 Coordinate or Autodesk Build,

02:49

and it integrates with Autodesk Docs for file management and issue tracking.

02:54

All of this makes Model Coordination best used for broader teams early in the design phase.

03:01

In addition, Model Coordination provides rule-based filtering and object exclusions

03:06

without the requirement of maintaining selection sets as in Navisworks.

03:11

Filters can be saved to views, whilst object exclusions are applicable to the coordination space.

03:17

Also, the clash grid highlights areas requiring attention based on model division, rules, and issue definition.

03:27

Users can define multiple views and fine-tune the clash matrix without the need to redefine selection sets or refresh clash tests.

03:37

Once any detailed clash information is back in Revit from either tool,

03:42

teams can immediately make changes to resolve conflicts directly within the live model.

03:48

And after updates are made, clash detection is re-run to verify that all conflicts have been successfully resolved.

03:56

This iterative process ensures a coordinated and clash-free design while maintaining project integrity.

04:03

By leveraging Navisworks Manage, Model Coordination, and Revit,

04:08

teams streamline coordination, minimize rework, and enhance project efficiency, paving the way for smooth execution in the next project phase.

Video transcript

00:03

When implementing BIM for MEP systems, the spatial coordination stage helps to ensure seamless integration across disciplines.

00:12

In this stage, after the initial layout of the MEP networks is generated,

00:18

clash detection is conducted on the Revit coordination model to identify conflicts between the MEP system and the architectural model.

00:28

Clash detection is performed using Autodesk Navisworks Manage or Model Coordination in Autodesk Construction Cloud (ACC).

00:38

Each solution plays a key role in efficient streamlining of project development.

00:43

The key difference between Navisworks Clash Detection and Model Coordination lies in their workflows,

00:50

level of automation, accessibility, and collaboration features.

00:55

Model Coordination provides automated workflows with limited preparatory work, as well as visual results in the clash matrix.

01:03

However, Navisworks allows for more file types and clearance detection, an important factor in constructability and safety considerations.

01:13

Navisworks Manage is best used when more advanced, detailed clash detection is needed during more complex coordination workflows.

01:22

Typically, it is used by BIM Managers or Coordinators who need a deep level of control over clash detection and reporting.

01:30

Clash detection in Navisworks Manage is a manual, highly customizable process

01:37

that allows users to define clash rules, filter clash results, and create clash reports.

01:43

Users can run hard, soft, and clearance clashes with specific tolerances.

01:49

It also supports clash grouping, rule-based filtering, and prioritization,

01:54

and it integrates with TimeLiner, Quantification, and other Navisworks tools.

01:59

It also supports a wide range of file formats, including IFC, RVT, DWG, NWC, NWD and many other authored formats.

02:12

The results yield detailed insights, listing clashes by location, element ID, and interference distance.

02:20

In contrast, Model Coordination provides cloud-based, automatic clash detection on models as soon as they are uploaded to ACC.

02:29

There is no need to set up clash detection tests manually, and the intuitive interface makes collaboration easy.

02:37

Model Coordination enables real-time issue tracking, clash grouping,

02:42

and makes assignment of issues seamless because it works within BIM 360 Coordinate or Autodesk Build,

02:49

and it integrates with Autodesk Docs for file management and issue tracking.

02:54

All of this makes Model Coordination best used for broader teams early in the design phase.

03:01

In addition, Model Coordination provides rule-based filtering and object exclusions

03:06

without the requirement of maintaining selection sets as in Navisworks.

03:11

Filters can be saved to views, whilst object exclusions are applicable to the coordination space.

03:17

Also, the clash grid highlights areas requiring attention based on model division, rules, and issue definition.

03:27

Users can define multiple views and fine-tune the clash matrix without the need to redefine selection sets or refresh clash tests.

03:37

Once any detailed clash information is back in Revit from either tool,

03:42

teams can immediately make changes to resolve conflicts directly within the live model.

03:48

And after updates are made, clash detection is re-run to verify that all conflicts have been successfully resolved.

03:56

This iterative process ensures a coordinated and clash-free design while maintaining project integrity.

04:03

By leveraging Navisworks Manage, Model Coordination, and Revit,

04:08

teams streamline coordination, minimize rework, and enhance project efficiency, paving the way for smooth execution in the next project phase.

Was this information helpful?