AI for MEP Design — routing review
AI for MEP Design — routing review reads a Revit MEP model and evaluates routing decisions against the firm’s design standards for duct sizing, pipe slopes, hanger spacing, maintenance clearance, and code-required separations. It walks the model element by element, pins flags to Revit element IDs with rule citations, and is available now as a Labs engagement under MSA + Appendix.
- MEP routing reviewed against the firm’s design standards element by element in the live Revit model.
- Each flag pins to the Revit element ID and cites the specific routing rule it misses.
- Re-runs on routing revisions diff against the prior review to show what changed.
From senior-engineer-by-eye to read-the-model.
Workflow today
-
01
MEP routing locks
Week 0. A junior MEP engineer routes ducts, pipes, and cable trays in Revit. They rely on experience and a PDF or SharePoint copy of the firm’s standard, not per-element checks. Slopes, hanger spacing, and clearance to structure or ceilings drift from the template details as deadlines compress.
Week 0 -
02
Senior engineer reviews by eye
Week 1+. A senior engineer opens the same Revit model and walks systems in 3D and section views, reviewing routing visually. They spot obvious issues but miss edge cases like local low points, tight access clearances, or inconsistent offsets. Review notes land as screenshots and redlines, and senior hours disappear into first-pass linting.
Week 1+ -
03
Issues come back to junior
Week 2+. The senior engineer’s comments return to the junior via meetings, email, or markup clouds. Each note lacks full context: no rule citation, no explicit element list, and no quick way to filter by system or level. The junior spends hours hunting elements, re-routing, and re-issuing sheets, and design intent drifts from the original MEP standard.
Week 2+ -
04
Clash detection runs late
Week 3+. Only after routing stabilises does the team export to Navisworks and run clash detection. Coordination meetings focus on hard clashes that could have been avoided if routing decisions matched the firm’s standards earlier. The separate MEP clash review workflow then triages clashes that sit on top of already-compromised routing choices.
Week 3+
Workflow with VitruAI
-
01
Run the agent on the MEP model
Day 1, ~30 min. Through the VitruAI + Revit integration, the routing-review agent reads the live Revit MEP model and the firm’s design standard codified into machine-readable rules. It ingests duct and pipe systems, slopes, offsets, hanger families, and clearance requirements without exporting to IFC or Navisworks, and prepares a routing review pass.
Day 1, ~30 min -
02
Agent flags routing decisions
Day 1. The agent evaluates each route segment and fitting against the standard and flags decisions that miss the rule set. Each issue pins to the Revit element ID, cites the violated rule, and proposes a remediation such as changing slope, rerouting around structure, or adjusting hanger spacing. Where relevant, it can cross-reference upstream data from workflows like mechanical drawing PDF parsing to keep intent aligned.
Day 1 -
03
MEP engineer reviews flagged decisions
Day 1–2. The MEP engineer works through the flagged routing decisions inside Revit, accepting, deferring, or remapping each suggestion. Senior engineers focus on judgment calls—system strategy, redundancy, and coordination with architecture—instead of scanning for every missed slope or clearance. The team can still run downstream clash detection and pair it with the dedicated MEP routing agent for deeper rule coverage.
Day 1–2 -
04
Re-runs on revisions
Ongoing. After each routing revision, the engineer re-runs the agent on the updated Revit model. The workflow diffs against the prior review so only new or resolved issues appear, reducing noise. This keeps routing aligned with the firm’s standard as design iterates and feeds cleaner models into MEP clash review and Navisworks-based coordination.
Ongoing
FAQs
-
Can AI design MEP systems?
Tools marketed as AI for MEP design that generate routing, such as Augmenta, focus on first-pass layout and sizing. VitruAI’s routing-review workflow takes that generated or manually drafted routing in Revit and checks it against your firm’s standards element by element. It is a review layer that sits alongside layout-generation tools rather than replacing the engineer’s design decisions.
-
What is MEP design automation?
MEP design automation is an umbrella term that covers layout generation, equipment sizing, clash detection, and rule-based routing review. In VitruAI’s stack, the focus is on routing review against firm-specific standards, calibrated per Labs engagement so your duct, pipe, and cable tray decisions match your own details. You can pair this with the dedicated MEP routing agent and downstream MEP clash review workflows for a fuller pipeline.
-
How do I automate MEP routing review in Revit?
You automate routing review in Revit by installing the VitruAI add-in and enabling the routing-review workflow against your project’s MEP model. The agent reads ducts, pipes, and fittings directly from Revit, compares them to your codified routing rules, and flags issues with pinned element IDs and rule citations. Results can then be coordinated with Navisworks via the VitruAI + Navisworks integration if you already run clash detection there.
-
How does this differ from clash detection?
Clash detection, whether in Revit or Navisworks, finds geometric conflicts between models after routing locks. Routing review evaluates the routing decisions themselves—slope, hanger spacing, clearance, and accessibility—before or alongside clash detection so many conflicts never appear. You still run your standard MEP clash review workflow, but on cleaner routing that already aligns with firm standards.
-
When does this ship as a productised release?
The AI for MEP design routing-review workflow is available now as a Labs engagement under MSA + Appendix. Labs customers work directly with the VitruAI team to codify their routing standards and tune the agent against live Revit projects. Broader productised packaging follows that Labs work but is not date-announced; firms interested today join via the waitlist.