Test 8: Find Clashes with Model Coordination

Overview

In this test, you'll use the Model Coordination tools in the Autodesk Construction Cloud web interface to identify and classify clashes between published versions of Revit models -- for example, finding any clashes or interferences between the elements in architectural, structural, and MEP models.

If you've worked with other tools like Navisworks Manage or BIM 360 Glue to perform clash detection on prior projects, you'll find that this new web-based interface offers very similar features.

Steps to Follow

1. Open the Autodesk Construction Cloud web interface at: https://acc.autodesk.com
2. Navigate to CEE 222 - Global AEC Testing 2025 project and switch to the Docs module to view the list of published models.
• Use the pull-down menu in the title bar of the web interface to open the CEE 222 - Global AEC Testing 2025 project, then switch to the Docs module.

• Open the Project Files folder in the navigation bar at the left side of the interface, then open the Cloud Revit Models subfolder.
• View the list of published models.
• Note that the version number increments every time a new version of the model is published.
3. Copy the newest Published version of the Architectural model into the Coordination Space folder to make it available for clash detection.
• Select Arch_Model v2025.rvt from the list of Published models in the Cloud Revit Models folder.
• Click the pull-down menu button in the toolbar at the top of the file list, then choose Copy.

• Select the Coordination Space folder as the destination for the copy.

• Click Copy.
4. Switch to the Autodesk Construction Cloud Model Coordination module.
• Click the module menu button (currently displaying Docs in the title bar) and choose Model Coordination from the menu that appears.

• Important: You must switch to the Model Coordination module to access the clash detection features in the Autodesk Construction Cloud interface. While you can see the Coordination Space folder in the Docs module, you need to switch to the Model Coordination module to complete the next steps.
5. View the list of 3D Model views available in the model coordination space.
• When you open the Model Coordination module, the Models tab displays a list of all the 3D model views from the published models that you've copied into the Coordination Space folder.
• Each model in the list also displays the latest Updated Date -- reporting to you the last time that this model was coordinated (a clash check was run) with the other models in the list.

• This list can be overwhelming, so you'll typically want to create Model Coordination Views -- a set of a few views displaying the specific model elements that you want to check for clashes.
• If you've Navisworks Manage or BIM 360 Glue to perform clash testing, this step is analogous to defining Clash Tests by selecting the model elements to include in the test.
6. Create a Model Coordination View containing the 3D models that you want to Coordinate (compare the elements to detect clashes). We'll start by creating a Model Coordination View to check for clashes with the model text element (displaying your name) that you added in the prior test.
• Select two of the 3D models in the Models list:
• Tenant Improvements - 3D - Furniture -- a 3D model showing the furniture planned for the tenant improvements phase.
• Arch_Model v2025.rvt - 3D - YourName -- a 3D model created to test the elements included in the view that your created in the prior test.
• Click the ‘Open in Viewer’ button to display these models in a new merged view.

• Click the Save View button to save these models as a new Model Coordination View.
• Enter a title for this view that will be easy to recognize -- for example, Name Test - YourName.
• You can set the Privacy to PRIVATE to make this model coordination view visible only to yourself, or PUBLISHED if you'd like to make this model coordination view available for others to use.
• Click Save View.

• Click the X button at the upper right corner of the interface to close this view.
7. Now, we'll use that Model Coordination View to look for clashes between the elements in the models that it includes.
• Click on the Clashes tab in the Model Coordination module interface.
• The Clashes tab displays a matrix showing the number of clashes between the elements included in all of the models included in the coordination space. This matrix can be very overwhelming, so we'll narrow down the list of models using one of the Model Coordination views available.

8. Open the Select a View pull-down menu and choose the Model Coordination View that you created in the previous step -- Name Test - YourName.
• The matrix is reduced to a much more manageable size that displays only the models included in the selected Model Coordination View.
• Next, we'll view the clashes between these models.
9. Click on the orange cell in the row for the Arch_Model v2025.rvt - 3D - Your Name (in the Tenant Improvements.rvt - 3D Furniture column).
• This will display the clashes between the elements in these two models.

• The Arch_Model v2025 - 3D - Your Name is set as the primary model. If the list of clashes is grouped by Object, the clashes will be grouped by the objects that are clashed within the primary model.
• Note that some objects in the primary model may clash with several objects in the Tenant Improvements furniture model.
• And some objects in the primary model may not clash with any objects in the Tenant Improvements furniture model.
10. Check to see if the Model Text element containing your name clashes with any objects in the Tenant Improvements furniture model.
• Click on each of the object groups in the grouped list of clashes.
• If you do find a clash with your Model Text element, click the Not an Issue button at the bottom of the list of clashes.
• Clashes occur whenever objects in the included models overlap.
• Not every clash between model elements is meaningful. Many clashes occur due to modeling inaccuracies or acceptable simplifications that we make during our early modeling stages.
• When a clash is considered acceptable and should be ignored (at this point in your modeling), click the Not an Issue button to exclude it from the list of clashes.
• When a clash is considered important and should be acted upon, you can leave it in the list or click the Issue button to track this clash as an issue that needs resolution.
• Click the X button at the upper right corner of the interface to close this view.
11. Next, let's check for clashes between two published models of the Architectural and Structural elements in this project.
• Open the Select a view menu and choose the Arch ALL vs Structural ALL model coordination view.

• This model coordination view contains all of the objects in the architectural and structural models.
• Click on the orange cell in the Struct Model v2025 row to set the Structural model as the primary model (which allows us to look for clashes by the structural objects that they clash with).
12. We'll start by looking for clashes with one of the Floor objects in the structural model.
• Make sure that the list of clashes is grouped by Object.
• Click on the checkbox for the first clash in the list for Floor [240474].
• Note that this object in the Structural model clashes with many objects in the Architectural model, and all of those objects are highlighted in the view.
• Turn off the checkbox for the Floor [240474] object, so we can focus on individual clashes.
• Turn down the arrow to the right of the checkbox to display a list of all the objects in the Architectural model that this structural floor object clashes with.
• Click on the checkbox to the left of any of the objects in the architectural model.
• As you turn on the checkbox for individual objects, those clashing objects are highlighted in the view.

13. We'll choose to ignore these clashes with the structural Floor object [240474] for now, because these are examples of modeling inaccuracies -- clashes between model objects due to our quick modeling at the early stages of a project.
• While we will want to fix the causes of these clashes in later versions (or ignore them as unimportant), we'll ignore them for now.
• We could mark them as Not an Issue to exclude them from the list, but please DO NOT do that. We want other students to be able to find these clashes too.
14. Next, let's look for another example of a clash that's more significant.
• Use the Group by pull-down menu to group the clashes by Identity Data/Type Name.
• This will group them by their Revit family Type Names.
• Turn on the checkbox to the left of the HSS6x6x0.500 type in the list of clashes.
• Turn down the arrow to the right of the checkbox to display a list of all the objects in the Architectural model that the structural objects of this type clash with.
• These structural objects are diagonal braces, and you'll see that conflict with many of the window and curtain wall elements in the architectural model.

• Use the Group by pull-down menu to group the clashes by Object, then scroll down the list to look for clashes with the HSS-Hollow Structural Section objects.
• Click on the checkbox to the left of HSS-Hollow Structural Section [246760] to highlight the elements that clash with this diagonal brace object.

15. This is an example of a more significant and meaningful clash -- something that you'd probably want to fix (rather than ignore) at this point.
• We could mark these clashes as an Issue and assign them to one of our teammates for resolution, but please DO NOT do that. We want other students to be able to find these clashes too.