Clash Detection Analysis

What This Skill Does

The Clash Detection Analysis skill provides a robust framework for identifying spatial and logical conflicts within Building Information Modeling (BIM) workflows. Leveraging the ifcopenshell library and spatial indexing, this skill automates the detection of geometry intersections, clearance violations, and workflow sequencing issues between various IFC entities. It allows users to pinpoint problematic areas early in the design cycle, significantly reducing the financial burden and schedule delays associated with field-level rework. The tool categorizes conflicts into hard clashes, soft clashes, and workflow-specific anomalies, providing a comprehensive report that assists engineers and project managers in maintaining design integrity.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/datadrivenconstruction/clash-detection-analysis

Ensure your local environment has ifcopenshell, numpy, and scipy pre-installed to support the underlying geometric analysis engines. Once installed, the skill exposes the ClashDetector class, enabling programmatic access to model validation routines.

Use Cases

• Pre-construction Review: Automatically scan MEP systems against structural components to ensure pipes and ducts do not intersect load-bearing members.
• Clash Reporting: Generate structured data exports (JSON or DataFrames) containing exact GlobalIds, severity ratings, and 3D coordinate locations of every identified conflict.
• Design Coordination: Use the soft clash detection feature to verify that maintenance clearance requirements around HVAC equipment are preserved throughout the model.
• Sequence Validation: Analyze time-based workflow clashes by cross-referencing IFC element data with construction scheduling inputs.

Example Prompts

1. "Analyze the current project model and identify all hard clashes between plumbing pipes and structural beams. Provide a summary of the top 5 most severe intersections."
2. "Perform a clearance check for all AHU units in the building model. Identify any soft clashes where maintenance access is blocked by architectural partitions."
3. "Can you export a CSV report of all identified clashes, including element types and their spatial coordinates, for the latest structural revision?"

Tips & Limitations

• Performance: For extremely large models, utilize the bounding box filter before performing precise polygon intersection calculations to save compute time.
• Geometry Accuracy: Ensure your IFC file contains accurate Brep representations; if the file contains only primitive placeholders, the accuracy of detection may be limited.
• Memory Usage: The geometric caching mechanism stores meshes in memory. For massive projects, consider processing the model in subsets or floors to avoid memory overflows.