MEP Clash Review
MEP Clash Review takes the clash report from Navisworks, BIM 360, or Solibri and triages it: real spatial conflicts vs tolerance noise, urgent vs deferrable, and who owns the fix across disciplines. It reads the federated Revit model alongside the report and returns a ranked review list, available now as a Labs engagement under MSA + Appendix.
- Noise filtered from the clash report so the team reviews only real conflicts and meaningful coordination issues.
- Each clash receives clear owner assignment across mechanical, electrical, plumbing, structural, and architectural teams.
- Re-runs on model revisions diff against the prior list so only clashes with changed status flag for review.
From triage-by-eye to triage-by-agent.
Workflow today
-
01
Clash report runs
Day 0, the coordination lead runs Navisworks Manage, BIM 360 Coordinate, or Solibri on the federated Revit set. The clash report drops with 4,000+ issues across mechanical, electrical, plumbing, structural, and architectural models. Exported HTML, XML, or BCF views then drive screenshots and ad‑hoc lists for later meetings.
Day 0 -
02
BIM Coordinator triages by hand
Day 1–3, the BIM Coordinator steps through each clash group, opens the associated views, and decides whether it is a real conflict or just tolerance noise from tight clearance rules. They mark urgent clashes that block duct mains or risers, defer minor hanger conflicts, and copy IDs into Excel. Senior staff lose hours to repetitive mep clash review decisions.
Day 1–3 -
03
Coordination meeting absorbs the rest
By Week 1, the design-team coordination meeting spends most of its time walking ambiguous clashes. Structural vs architectural ownership gets debated, and MEP routing changes stall while the team scrolls through screenshots. Decisions land in spreadsheets or email threads instead of the clash environment, which slows structural and architectural coordination.
Week 1 -
04
Re-run, re-triage
In Week 2+, the team re-runs Navisworks or BIM 360 after model updates and receives a fresh clash set with new IDs. The prior triage work does not carry over, so the Coordinator restarts the review from scratch. Meetings repeat the same conversations about ownership and priority, and the cost of each coordination cycle grows with every model revision.
Week 2+
Workflow with VitruAI
-
01
Run the Clash Review Agent on the clash report
On Day 1, the team exports the Navisworks, BIM 360, or Solibri clash report and points the Clash Review Agent at both the report and the federated Revit model. The agent reads clash geometry, element metadata, and view context across linked models. It respects the same worksharing structure the team already uses for Revit integration, including discipline worksets and shared coordinates.
Day 1, ~30 min -
02
Agent classifies and prioritises
Within ~1 hour, the agent classifies each clash as real conflict, tolerance-based noise, or acceptable overlap based on firm-specific rules. It assigns priority bands such as urgent, scheduled, or deferrable and tags discipline ownership across mechanical, electrical, plumbing, structural, and architectural. The output is a ranked list that feeds directly into existing MEP routing and MEP routing review workflows.
Day 1, ~1 hour -
03
Coordinator reviews flagged decisions
Day 1–2, the BIM Coordinator focuses only on low-confidence classifications and owner assignments that the agent marked as ambiguous. They review side-by-side model views for edge cases, such as tight soffits or congested shafts, and override decisions where project context demands it. High-confidence items move straight to discipline leads, which shortens coordination meetings and keeps senior engineers on design rather than list-sorting.
Day 1–2 -
04
Re-runs on model revisions
On each new model drop, the agent re-runs against the updated clash report and diffs the results against the prior triage. Only clashes with changed status, ownership, or priority appear for re-review. Carried-forward decisions stay intact, so coordination meetings focus on genuinely new issues instead of rehashing resolved conflicts, and mep clash review becomes a continuous, light-touch process instead of a weekly reset.
Ongoing
MEP Clash Review — common questions
-
Does this replace Navisworks?
No, Navisworks, BIM 360 Coordinate, and Solibri remain the tools that run geometric clash detection on the federated model. VitruAI’s agent sits on top of those outputs and triages the resulting report into real conflicts, noise, and priorities. It treats Navisworks integration and other detection tools as inputs, not competitors.
-
How does the agent decide what’s noise?
Noise classification is calibrated per Labs engagement against your firm’s tolerance conventions and historical clash reports. The agent learns from past decisions on what you previously closed as acceptable overlap or coordination by note, rather than applying a generic industry rule. Each deployment ships with a calibration pass so the triage reflects your actual practice on mep clash review, not a template from another firm.
-
Does this work on the federated cloud workshare (BIM 360 / ACC)?
Yes, the agent reads federated cloud models from BIM 360 or ACC in the same way it reads local Revit files. It works against the coordinated sets you already publish for clash detection and respects linked-model structures, shared coordinates, and view templates. The same pipeline that underpins Revit integration and BIM 360 / ACC integration carries into clash triage.
-
When does this ship as a productised release?
MEP Clash Review is on the roadmap and available now as a Labs engagement under MSA + Appendix for firms that already run structured coordination cycles. Productisation follows once three or more design-partner deployments have validated the triage rule pack across different project types. Early partners help shape edge-case handling for complex structural and architectural coordination and dense MEP routing review zones such as riser banks and plant rooms.