1. Clash detection
   
2. Property (IDS) validation
   
3. Distance checking 
   

Do you want to advance your knowledge about this subject? Go to our BIMcollab Academy and enroll in the BIMcollab Zoom conflicts.

Clash detection 

Setup a clash rule

1. Start BIMcollab Zoom with a Zoom license
   
2. Connect to a project on BIMcollab Nexus or load a set of models manually
   
3. Select the Conflicts panel
   
4. All conflict rules must be added to a conflict rule set.
   Expand 'Local' or 'Shared' and select an existing set. If no conflict rule set is present yet, create a new one by clicking the [+] button, or right clicking on 'Local' or 'Shared' and choosing 'Add conflict rule set'.
   It will be automatically selected once created
   
    
   
   
5. Click the [+] button again to start creating a new conflict rule, or right click the conflict rule set and choose 'Add conflict rule'
   
    
   
   
6. While creating a new conflict rule you can edit the following fields:
   
1. Name
   Give your rule a clear and unique name. The name can later be appended to issue titles to make them better searchable in BIMcollab.
2. Source set
   Define a set of components which will be used as your source set by filtering them out by defining rules. Each rule exists of:
1. An Element type you want top add to the set (e.g. walls, doors, columns)
   
2. A Property, Operator and Value to be used to filter out elements with a specific property value
   
3. The action which defines if the elements found should be added or removed from the set
   

Test your set by clicking on the Show selected set button . The result will be shown in the 3D view

3. Target set
   Define a set of components which will be used as your target set the same way as with the source set.
4. Include Parts
   
    Choose whether sub-components are included in your conflict rule. You’ll find this checkmark under the conflict rules section for both source and target sets.
   

   Sub-components are individual parts of a larger composition. This is common in assemblies like curtain walls made up of parts, and container elements like spaces or building storeys. Working with sub-components can have a big impact in your conflicts results. 
5. Type
   Determine if you want to check for Clashes, Duplicates, distances, or all
6. Tolerances
   You can customize the clash detection process by overriding the default tolerances related to the size and volume of clash boxes. This allows you to set minimum thresholds for the size or volume of detected clashes that will be included in the results. By adjusting these settings, you can filter out minor or insignificant clashes, ensuring that only relevant conflicts are highlighted for review.
7. Minimum distance 
   Define the minimum distance between source and target elements. This is only relevant for distance checking. 
   
8. Include conflicts from a single:
   Determine whether the clash result includes conflicts where the clashing elements are within the same model, system, or component.
9. Description
   Provide the rule with a clear description so it's purpose is easily identifiable
   
   
   

7. Click OK to save the conflict rule

8. Execute the conflict rule (set)

1. Double-click or use the Run button to execute a selected rule (set)
   
2. Right-click to run on components in My view
   
   
   

9.The results of the clash test can then be found in the results panel.

10.  After running a conflict rule, the number of results will be displayed on the same line.  Alternatively, instead of a number, you might see a check mark   indicating "check passed" if no conflicts were detected, or a null symbol   indicating that "no applicable components" were found. If you encounter the null symbol, you may need to load the correct models or adjust the rule accordingly. 

 

The shared conflicts includes conflict rules for clash detection, distance checking and IDS specification for property validation.

Grouping

By default, conflicts are grouped together by source component, the nearest grid position, and the story level. To change this click 'Change grouping settings' .

View modes

By default clashes are displayed using the schematic mode. The user can choose between a number of view modes which determines how the issue is displayed, by clicking the 'Change clash view mode' button .

1. Regular: Display the two clashing components
   
2. Selected: Display the two clashing components and select them
   
3. Schematic: Display the two clashing components transparent and highlight the clashing area
   

Additionally, you can place a section box around the clashing components, which is useful for recreating an issue within a modeling application. You can also enable the floor plan if it provides additional context for the issue generated from the result.

Generating Issues

When connected to a project on BIMcollab Nexus

When connected to a project on BIMcollab Nexus, you can report conflicts as Smart Issues to easily track their status. This can be done from either the conflict results panel or the 3D window. You have the option to report issues individually or combine multiple conflicts into one issue. You can handle issues using the buttons at the top of the results section or by right-clicking on each result or result group. 

 Report: Change status from Unhandled or Ignored to Reported. 

 Ignore: Change status from Unhandled to Ignored

 Mark as new: Change status from Reported or Ignored to Unhandled

Make sure you are connected to the correct BIMcollab space and project before generating the issues.

In offline mode

Without connecting to BIMcollab Nexus, you can still report conflicts, but they will be offline issues without any link to BIMcollab Nexus or tracking capabilities. To do this, simply select one or more results in the list and click 'Batch Generate Issues.'