The basis for proper interdisciplinary coordination is to check if there are any illegal collisions between model elements in the project as https://karnoenergy.com/bim-clash-detection/ does.
If you want to make sure your project doesn’t contain errors that could cause high costs during the implementation phase contact Karno Energy!
Karno Energy’s experienced engineers can help you find the wrong intersection points in your project using the Autodesk Navisworks Manage tool.
The interdisciplinary matching phase should start with the Karno Energy BIM planner developing what is called a “Collision Matrix” which defines the tests that need to be run on the models, including allowable tolerances and collision exceptions.
Then, based on the developed matrix, we at Karno Energy define the tests with certain assumptions and rules in Autodesk Navisworks Manage. After running the collision checker tool, we provide information about the collisions found in the form the customer wants. Possible:
- A file in NWD format with specified tests and detected collisions
- a report in html or excel format,
- import of collisions into BCF Manager and synchronization of the report with a project in the cloud or export of collisions to BCF format
- Transferring the script into xlsx format and providing Dynamo script to detect localization conflicts in Autodesk Navisworks in Autodesk Revit
Karno Energy – IFC Model Collision Detection with BIMvision
Karno Energy’s Clash Detection plugin allows you to detect collisions in the IFC model (architectural, structural, assembly, and complex models).
Clash Detection is a convenient and extremely practical solution that allows you to quickly detect geometric collisions that occur between elements of the same model or between elements of several independent models (in this case, use additionally the Multifile Module plug-in).
Using the Clash Detection plugin, you can easily detect collisions in the IFC model.
Karno Energy – Collision Types
One of Karno Energy’s goals is to minimize the risk of increased costs during implementation. These increased costs result from, among other things, undetected or unacceptable collisions. They should be analyzed at all stages of the project. Projects should also establish (in strategy documents) methods for communicating information about detected, removed, or abandoned collisions. In addition, outline recommendations for conflict management, i.e., a list of procedures for coordinating and resolving conflicts, the need for collision reporting, etc. D. The following is a list of conflicts that occur in projects:
- Standard conflict : non-compliance of the project or its elements with applicable technical and construction regulations, technical standards and requirements of network operators.
An example of such a conflict would be:
- too narrow a doorway width in light of an aisle,
- for close location of a deep well from the site boundary,
- too large a gap between balustrade fill elements,
- lack of expansion joints from walls and ceiling in elevator shafts;
- Collision of the assembly : the element of the object must have the necessary free space, which will allow its assembly. We are talking about this type of collision when it is impossible to install fittings or devices due to lack of sufficient space for safe assembly, the presence of existing or already installed elements;
- hard collision: the overlap or intersection of the geometry of two model elements. These are the easiest to find and cause fewer problems. Such a collision could be, for example, the absence of holes for mechanical installation wires or the intersection of these wires with a cable tray. Serious collisions should be considered at the design stage, since not all collisions need to be dealt with immediately.