BIM Clash Detection and Autonomous RFI Routing Matrix
Coordinate autonomous agents to detect 3D BIM model clashes, evaluate severity, and automatically route RFIs to trade contractors.
Apply this template when operationalizing AI agents to streamline Virtual Design and Construction (VDC) workflows. It provides a structured matrix for clash categorization, autonomous RFI authoring, and trade contractor response tracking.
Role: Senior Virtual Design and Construction (VDC) Automation Lead specializing in multi-agent building information model coordination.
Context
- BIM model scope and scale: {{bim_model_scale}}
- Involved trade disciplines: {{trade_disciplines}}
- Clash severity tolerances: {{clash_severity_thresholds}}
- Common Data Environment: {{cde_platform_env}}
- RFI approval hierarchy: {{rfi_approval_chain}}
- Historical clash database: {{historical_resolution_data}}
Task
Construct an autonomous BIM clash detection and RFI resolution matrix that coordinates model-checking agents, spatial reasoning subroutines, and automated RFI distribution across {{trade_disciplines}} within {{cde_platform_env}}.
Method
- Establish geometric collision parameters using tolerances defined in {{clash_severity_thresholds}} for {{bim_model_scale}}.
- Assign agent responsibilities across trade intersections (e.g., MEP vs. Structural, Fire Protection vs. Architectural).
- Map automated conflict analysis against {{historical_resolution_data}} to identify standard engineering solutions.
- Define criteria for autonomous clash clearance without human intervention for minor geometric overlaps.
- Standardize automated RFI generation schemas, including 3D viewport generation, parameter extraction, and cost impact estimation.
- Establish routing workflows matching {{rfi_approval_chain}} for high-severity spatial conflicts.
- Build agent tracking rules for contractor response times, model revision ingestion, and automated clash close-out.
Constraints
- High-severity structural clashes MUST NOT be resolved without sign-off from {{rfi_approval_chain}}.
- Agents MUST reference historical precedents from {{historical_resolution_data}} before drafting new RFIs.
- All generated RFIs and model snapshots must reside exclusively in {{cde_platform_env}}.
- Keep trade categorizations strictly aligned with {{trade_disciplines}}.
Output format
- VDC Multi-Agent Workflow Overview (max 120 words)
- Clash Triage & RFI Routing Matrix (Markdown table with columns: Trade Conflict, Severity Level, Agent Task, Resolution Logic, Generated Artifact, Escalation Role, SLA)
- Autonomous RFI Schema & Metadata Template
- Agent Failure and Human Override Protocols
Self-review
- Ensure every trade listed in {{trade_disciplines}} is represented in the clash matrix.
- Verify clash thresholds strictly match {{clash_severity_thresholds}}.
- Check that RFI routing paths conform to {{rfi_approval_chain}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.