Definition of Clash Detection?
Clash detection in Building Information Modeling (BIM) is a process used to identify and address conflicts between different design components within a construction project.
The Causes of the Clashes:
There are several factors that can lead to clashes in BIM:
Lack of Coordination: Different teams working on separate models without proper communication can cause design elements to intersect unintentionally. Design Changes: Frequent updates or modifications to the design can lead to inconsistencies and overlaps between different components. Complexity of Design: Highly complex and detailed projects are more prone to clashes due to the sheer number of components and their interactions. Human Error: Mistakes made during the modeling process can result in elements being placed incorrectly, leading to clashes. Incomplete Information: Incomplete or inaccurate data in the models can cause misalignment and conflicts between different systems. By conducting clash detection, these issues can be identified and resolved early in the design process, ensuring a more efficient and error-free construction phase.
When we do Clash Detection?
Several key stages of a construction project that we do clash detection:
After Major Design Changes During Design Coordination Meetings: regularly based on agreement in Execution Plan Before Construction Begins: to minimize on-site clashes and ensure a smooth build process. Throughout Construction: Periodically performing clash detection during construction can help address any on-site adjustments or changes and keep the project on track. How to do clash detection?
Some applications used for clash detection in BIM:
Autodesk Navisworks: Widely used for its powerful clash detection capabilities and integration with other Autodesk products Solibri Model Checker: Known for its advanced model checking and compliance control features. Trimble Tekla BIMsight: A collaboration tool that includes clash detection features, especially useful for teams using Tekla software. BIM Track: A cloud-based platform that offers clash detection along with issue tracking and project management features. Revizto: Combines clash detection with real-time issue tracking and project coordination tools. MagiCAD: An MEP design add-in for Revit and AutoCAD that includes clash detection capabilities. Fuzor: A VDC-focused platform that offers clash detection and management tools compatible with various file formats.
What is Clash Acceptance/Tolerence?
Clash acceptance, or clash tolerance, refers to the predefined criteria used to determine which clashes in a BIM (Building Information Modeling) project are considered acceptable and which need to be resolved.
Examples:
Structural Clashes: 0 mm tolerance (no physical overlaps) MEP (Mechanical, Electrical, Plumbing) Clashes: ±10 mm tolerance Soft Clashes (Clearance): Minimum 50 mm clearance for maintenance access Implementing clear clash acceptance/tolerance criteria helps prioritize critical issues, reduce unnecessary rework, and maintain project efficiency. Does this help clarify things?
What are the types of Clashes?
there are three main types of clashes that can occur:
Hard Clashes: These occur when two components physically intersect or occupy the same space. For example, a pipe running through a beam is a hard clash. These are the most straightforward type of clash to identify and resolve. Soft Clashes: Also known as clearance clashes, these occur when components are too close to one another and don't have the required spatial or geometric tolerances. For example, an HVAC unit that needs space for maintenance access might not have enough clearance. Soft clashes often require adjustments to ensure proper installation and maintenance. Workflow Clashes: These involve scheduling and sequencing issues, where different teams or trades might have conflicting timelines or work sequences. For instance, if one team's work needs to be completed before another team can start, and there is a scheduling conflict, it is considered a workflow clash. Clash Acceptence Matrix
This matrix helps project teams evaluate and manage clashes systematically, ensuring consistency and clarity throughout the project.
Here's a breakdown of what a clash acceptance matrix typically includes:
Clash Category: Different types of clashes (e.g., hard, soft, workflow) that the matrix will address. Element Types: The specific elements involved in the clash, such as structural components, mechanical systems, electrical conduits, etc. Tolerance Levels: Defined tolerance levels for each type of clash. This includes acceptable dimensional overlaps or clearances for different elements. Priority Levels: The priority assigned to resolving each type of clash, based on its impact on the project. Higher-priority clashes may involve critical components that require immediate attention. Resolution Strategy: Suggested approaches or steps to resolve each type of clash. This could include design adjustments, coordination meetings, or changes in construction sequences. Acceptance Criteria: Specific criteria for what is considered an acceptable clash versus an unacceptable one. This includes considerations for safety, cost, maintenance, and project requirements. Responsibility: Assigning responsibility to the relevant team or individuals for resolving each clash type. This ensures accountability and efficient resolution. Examples:
Clash Detection and VR
Potential of VR for Architecture Student
We can do this using Twinmotion as well.
Clash Detection in Revit and Naviswork
Lecture 5: Clash Detection