About Collision Check

Explains the concept of the collision check.

Collision detection makes your work easier as it detects and locates collisions of any combination with just a click. The collision check distinguishes between collisions and area violations. A collision occurs when two or more components overlap. In order to specify mounting distances, minimum distances can be defined for pipes, air ducts and cable trays.

An area violation exists if a component is within a minimum distance but does not cause a collision. Intersections with operating or installation spaces are reported as area violations. Intersections of installation spaces with connected systems or their fixings are only reported for consoles.

You can set the collision check for your application: From a simple check of two system classes in one project to a complex check of system classes and categories across several linked projects, there is almost no situation that cannot be covered. The configuration of each column can be saved separately for future collision checks.

With the help of the collision check, you provide a reliable collision-free model for project collaboration.

In the collision check settings, it is possible to define minimum distances to pipes, ducts or cable trays. In the settings, you can also exclude pending or already accepted void proposals from the collision check and specify that directly connected components are considered non-colliding. All results of the collision check appear in the Issues and tasks tab and can be edited individually.