BIM Collaborate part 2 | Configure clash settings and create an issue

A hard clash is where two or more model objects are occupying the same place in space and the objects overlap each other. There are two methods for viewing clashes of 3D models.

Method 1: Access clashes via a saved view. This is the method you will use in this exercise.

Method 2: Access clashes via the Clash panel. You may use this method after you become familiar with the clash workflow.

Autodesk Online Help resources: Model Coordination; Models in the Viewer; Filter and Investigate Clashes; Issues in Model Coordination

 

Learning objectives:

• View and evaluate clash groups.
• Create and manage issues.

Exercises

Open a saved view

If you did not create a saved view, return to Part 1 of the Autodesk BIM Collaborate exercises.

1. Open the Autodesk Model Coordination module: From the product picker menu, click Model Coordination.
2. Open a saved view:
   1. Verify you are in the correct project (Figure 25, mark 1).
   2. Click Views in the navigation panel to open the Views panel (Figure 25, mark 2).
   3. Verify the active model coordination space for your assigned team (Figure 25, mark 3).
   4. Open a saved view by clicking the view name for (your initials)_MEP vs Struct (Figure 25, mark 4).

 

Open a clash view

Opening the clashes panel allows you to see the clash groupings associated with the disciplinary models chosen.

1. Open a clash view and confirm the default settings:
   1. Click the Clashes icon in the navigation toolbar (Figure 26, mark 1).
   2. Verify that the Primary Model is set to the structural model file (Figure 26, mark 2).
   3. Verify that the Clash With option is set to the MEP model file (Figure 26, mark 3).
   4. Verify that the Group By option is set to object (Figure 26, mark 4).
   5. Verify that the Show Clashes Below option is set to zero (0) inches (Figure 26, mark 5).
   6. Verify that the total number of individual clashes found is 18. (Figure 26, mark 6).
      
      Note: This is not the number of clash groups.

Note: Primary model is colored in red. The model with a clash is colored in green

 

Configure clash settings

Before evaluating clash groups, it is important to know how clash groups are organized based upon the Group By setting.

1. Group model elements by object name: For this exercise we assume you are comparing a structural model to a MEP model using the following settings:

1. 1. Set the Primary model to structural model (Figure 27, mark 1).
   2. Set the Clash With option to the MEP model (Figure 27, mark 2).
   3. Set the Group by Field to Object (Figure 27, mark 3).
   4. Set the Show Clashes Above to zero inches (Figure 27, mark 4).

The clash group tree view explanation is shown in Figure 27, mark 5:

When the primary model is a structural model and Group By is set to object, then the clashes will be grouped by Autodesk Revit structural model categories in alphanumeric order.

Note: Refer to the Online Help for further details on filtering clashes.

2. Group model elements by model properties (Structural): Continuing from the example above, change the group by property.

Set Group By to Structural / Structural Usage (Figure 28, mark 1).

 

The clash group tree view explanation is shown in Figure 28, mark 2.

When the primary model is a structural model and Group By is set to Structural/Structural Usage, then clashes will be grouped more efficiently according to the structural usage property, resulting in fewer clash groups to review and they are sorted in alphanumeric order. This method helps in recognizing patterns of a single root cause.

3. Group model elements by model properties (Mechanical/System): Continuing with the example above, change the following properties.

1. 1. Set the Primary Model to MEP model (Figure 29, mark 1).
   2. Set the Clash With model to the structural model (Figure 29, mark 2).
   3. Set the Group By field to Mechanical/System Classification (Figure 29, mark 3).

The clash group tree view explanation is shown in Figure 29 mark 4.

When the primary model is a MEP model and Group By is set to Mechanical/System Classification, then clashes will be grouped more efficiently according to the classification system property, resulting in fewer clash groups to review and they are sorted in alphanumeric order. This method helps in recognizing patterns of a single root cause.

 

Investigate clash group

After configuring clash settings, the next step is to open a clash group and visually assess what might be the root cause of the clash.

1. Open a clash group: For this exercise, continue using the settings from Figure 29. Note that the total number of individual clashes found is listed at the top of the clash group stack (Figure 30, mark 1).

1. Mark the Undefined clash group (Figure 30, mark 2) to view the clash group in the viewer.
2. To expand the clash group, click the arrow in front of the clash group name.
3. The clash group becomes the focus in the viewing window (Figure 30, mark 3).
4. It is permissible to isolate one of the clashes in the tree view by unmarking the other objects (Figure 31, mark 1).
5. Explore the clash using the View toolbar tools, your scroll-wheel mouse, or the ViewCube.
6. Use the ViewCube and set the view to Front (Figure 31, mark 2).
7. Using the Measure tool (Figure 31, mark 3), measure the amount of overlap between the bottom of the structural beam and the top of the duct (Figure 31, mark 4). Use the Measure tool to set the units of measurement (Figure 31, mark 5).

2. Create an Issue for a real clash to be resolved: When reviewing clashes, models, or views in Model Coordination, you can create an Issue to indicate that something in the design requires investigation. Issues can be created from specific clashes using the Clashes panel, or directly on a model using the Issues panel. The next step is to document the Issue and assign the Issue to the party that is responsible for fixing the Issue.

1. 1. Open the clash group as shown previously in Figure 29 with Group By set to the Mechanical/System classification and expand Undefined as shown previously in Figure 30.
   2. Isolate the first W-Wide flange beam as shown previously in Figure 31 and then zoom in to the selected clash.
   3. Orient the view to a 3D view using the Home icon next to the ViewCube.
   4. Click + Create Issue and select Clash from the menu (Figure 32, mark 1)
   5. Place a pushpin on the model object that requires to be modified by placing your cursor over the ductwork in red and pre-highlighting it, and then click to place the pushpin. Wait for the Issue form to appear on the right side of the screen.

Note: Pushpins represent Issues and are seen by other project members with correct permissions when the model is viewed. We recommend placing the pushpin on the model object that requires modification to resolve the clash. Refer to Online Help for more information on issues.

1. 6. Fill-out the Issue form. Note that the Issue number is automatically generated (Figure 33, mark 1):

1. 1. Enter your initials as a prefix to the Issue name and leave the remaining text as-is by clicking the pencil icon and editing the field (Figure 33, mark 2).
   2. Note that the issue Type is automatically set to: Coordination > Clash (Figure 33, mark 3).
   3. Description: Edit the description by clicking the pencil icon, deleting the existing text description, and typing in your description of the clash along with your proposed solution (Figure 33, mark 4).
   4. Assign the issue to either your instructor or teaching assistant as directed (Figure 33, mark 5).
   5. Assign yourself and your teammates as an Issue watcher (Figure 33, mark 6).
   6. Assign a Due Date that is three business days out (Figure 33, mark 7).
   7. (optional) Assign a root cause (Figure 33, mark 8).
   8. Close out the Issue form by clicking the X in the top-right of the Issue panel.

7. Verify that the Issue you created appears in the Issue panel. Click the Issue icon on the navigation toolbar (Figure 34, mark 1).
8. To re-open the Issue, click the Issue name. The view window will reset to display the Issue that was created.
9. Verify the Activity log by clicking the Activity Log tab (Figure 34, mark 2).
10. To close out the Issue form, click the X in the top-right of the Issue panel.

 

3. Create a “Not An Issue” for a clash that can be ignored: Some clashes can be ignored, such as a light fixture that appears to clash with a ceiling system but is located in the correct position. Removing these clashes from your models and views helps you work through real problems more efficiently. You can remove clashes from your workflow by marking them as 'not an issue'. It is also possible to reactivate these clashes and reclassify them as an Issue.

 

1. 1. Open the Clashes panel and use the settings as shown in Figure 35.
   2. Mark clash group named 1 clash with 1 other model as shown (Figure 35, mark 1).
   3. Orient the view to a 3D view using the Home icon next to the ViewCube and zoom in close to the highlighted object in red.
   4. Click Not An Issue in the bottom-left corner of the screen as shown (Figure 35, mark 2).
   5. Fill-out the form:
      1. Title: Enter your initials as a prefix to the title name and leave the remaining text as-is (Figure 35, mark 3).
      2. Reason: Choose the correct reason as to why the issue can be ignored (Figure 35, mark 4).
      3. Comments: Provide additional details as to why it is not a clash and can be ignored (Figure 35, mark 5).
      4. Click OK to accept and close the form (Figure 35, mark 6).
      5. Click X in the top-right corner to return to the Clashes panel.
   6. Verify Non-Issue appears in the Clashes panel.
      1. Click the Clashes icon (Figure 36, mark 1).
      2. Click the Closed tab (Figure 36, mark 2).
      3. Look up the Non-Issue you just created (Figure 36, mark 3).

 

Strategies for evaluating 3D model clashes

In the previous section you used workflows for performing 3D model coordination. Now you’ll see how to approach model coordination across disciplines in a systematic way for evaluating any project. The coordination matrix below (Figure 37) provides a general sequence to follow for coordinating 3D models for the built environment starting with number one and proceeding towards the highest number. The general idea is that all disciplines should check their own disciplinary model before sharing them with the rest of the team.

Structural coordination sequence explanation

Structural objects should be considered the highest priority in terms of least movable building systems. The higher priority building systems are indicated by a low number value, which is due to the long lead times for structural steel or bar joists as an example. The evaluation of building systems can then proceed with the following disciplinary pairings.

Structure vs Architecture; Structure (2) vs. Bldg. Mech (4); Structure (2) vs. Bldg. Plumb (5); and so on.

Coordination Matrix

 

Answer questions about 3D model coordination:

Answer the following questions using the Model Browser or the Clashes panel.

Questions:

1. Office Building dataset:
   1. Which two disciplinary combinations have the most clashes? ___________________________
   2. How many clashes are there for that combination? ___________________________
   3. How many clashes does the Hydronic Supply system have? ___________________________
2. Medical Laboratory dataset:
   1. Which two disciplinary combinations have the most clashes? ___________________________
   2. How many clashes are there for that combination and for which level of the building? ___________________________
   3. How many clashes are there for that combination for the second floor only? ___________________________
   4. How many clashes does the Joist system have on the second floor only? ___________________________

 

Create an Issue for a real clash to be resolved:

Choose either the office building or medical laboratory dataset and document one hard clash. Use the instructions provided in the exercises for naming conventions and adding description details.

 

Create a Not An Issue for a clash that can be ignored:

Choose either the office building or medical laboratory dataset and document one clash that can be ignored. Use the instructions provided in the exercises for naming conventions and adding description details.