Clash Detection Workflow with Autorun and Constant Update of Issues

[m.meligy]

Hello developers and users,

I would like to start a new thread here about a workflow for clash detection in Solibri, specifically for handling large scale projects with large amounts of data and models.

My intention is to have a streamlined system of ongoing checking based on clash detection rules covering all models and, on one hand, a semi automated (with a quick visual check) system of creating and updating issues and, on the other hand, the ability of tracking the number of collisions between the models throughout the development of the project, preferably visualized on a matrix.
This could theoretically be executed in one of these two approaches:

Approach A: Using clash detection matrix (SOL/245/1.2) with two hierarchy levels (1. Model and 2. Ifc Entity) and combining this with autorun to automatically create the slides for grouped issues on the category level.

Here are the problems I am facing with this approach:

1. Once these issues are created and exported to bcf or excel, there is absolutely no way to know how many collisions exist within this issue - the number is only shown under “Issue Details” before the report (bcf/excel) is created but never in the report itself
2. The results on the category level (2nd layer from the matrix hierarchy: Ifc Entity) are never repeated, for example if walls and beams from different models collide, the results are always packed under the first instance the collision is found, even if the colliding components are in different models completely (see thread: https://society.solibri.com/post/12880)

Approach B: Using the general intersection rule (SOL/1/5.0) and creating as many rules as I need to cover all the cells of the matrix from, i.e. all the possible combinations of the project models, then autorun to create the issues.

Here are the problems I am facing with this approach:

1. Again the same problem with approach A - no possibility to extract the amount of collisions after creating the report
2. Manually creating the matrix on excel, which is a lot of formatting work, that eventually will be only used for one project and could not be standardized without repeating most of the work. Also tracking the number of collisions in each issue throughout the project will be -not impossible- nevertheless very hard.

I believe that the matrix template does not behave the way it is expected, or am my missing something in the logic of the workflow?
Does anyone use a streamlined system of checking and tracking collisions, or is there no way around manually going through the results every time?

This is an open question to both developers and users, please feel free to share your feedback, if this problem at all relevant to you.

Kind regards,
Mahmoud

[m.meligy]

Perhaps to summarize the problem in one question: Is there any way in Solibri to systematically record how many clashes exist on the category level (problem/issue type) after creating the presentation?

[Matti]

One way to is to use Result Summary Report. The new version of the Solibri supports reporting each issue and component to Excel. For the issues you can report the issue category or all the categories. This way you can systematically record how many clashes exist on the category level.
See: https://help.solibri.com/hc/en-us/articles/23765489465367-Result-Summary-Template-Keys