Revit MEP Duct & Pipe Modelling Best Practice: Routing, Slope, Clash Avoidance

Revit MEP is the dominant BIM authoring tool for Indian commercial projects. Properly used, it delivers coordinated drawings, clash detection, BOQ extraction, and energy-model integration in one toolchain. Poorly used, it creates bloated models that crash on networked drives and fail to coordinate with structure or architecture.

This guide covers practical Revit MEP duct + pipe modelling — the conventions, gotchas, and clash-avoidance discipline that separate productive teams from struggling ones.

Working in shared coordinates

Before any duct or pipe is drawn, the linked architectural and structural files must be at correct coordinates. This means:

1. Architect publishes shared coordinates (a single project base point, north arrow, level datums)

2. MEP team imports the linked architecture with “Acquire Coordinates” — this aligns Revit’s project base point to the architect’s

3. MEP team uses the same shared coordinates when linking back to architecture or coordinating with structure

Without shared coordinates, every MEP team works in their own world; clash detection becomes meaningless. Spend the 15 minutes early — it saves 15 hours later.

Level datums + system definitions

For each MEP system (HVAC supply, return, exhaust, sanitary, vent, fire, etc.), define:

1. System type in Revit (e.g. “Supply Air”, “Return Air”, “Cold Water Supply”)

2. System color for visual distinction

3. System abbreviation for tags (HVS, HVR, CWS, etc.)

4. Default fitting style (round vs rectangular, pressure class)

5. Default insulation thickness + material

Standard system list per MEPCON convention:

  • HVS — HVAC supply air
  • HVR — HVAC return air
  • HVE — HVAC exhaust
  • CHS / CHR — chilled water supply / return
  • CWS / CWR — condenser water supply / return
  • HWS / HWR — hot water supply / return (DHW)
  • SAN — sanitary drainage
  • VENT — plumbing vent
  • FW — fire water
  • HYD — fire hydrant

Duct + pipe sizing in Revit

Revit can size dynamically using built-in or 3rd-party tools:

Built-in Revit sizing

  • Apply “Duct/Pipe Size” tool to a routing run
  • Specify max velocity, max pressure-drop per 100 m
  • Revit iteratively sizes each segment

For typical office HVAC:

  • Supply velocity max 7-8 m/s in mains, 5-6 m/s in branches
  • Return velocity max 6 m/s
  • Pressure drop ≤ 0.8 Pa/m (1.2 Pa/m max for branches)

For chilled water:

  • Velocity 1.5-2.0 m/s in mains, 1.0-1.2 m/s in branches
  • Pressure drop ≤ 250 Pa/m

3rd-party sizing (CAMS for HVAC, etc.)

More sophisticated; can apply standardised duct sizing tables (ductulator) or pipe-friction tables. Often required for non-standard fluids or unusual systems.

Slope handling

Slope is critical for plumbing drainage:

  • Soil/waste pipes: 1:50 to 1:100 (NBC 2016)
  • Vent pipes: typically 1:200 (small slope)
  • Storm/rainwater: 1:50 minimum
  • Hot water recirculation: 1:200 (small drainage in case of failure)

In Revit:

1. Set the “Slope” property on the pipe segment

2. Revit automatically maintains the slope along the run

3. Place a fitting at top of vertical drops

4. Cleanout fittings at every 30 m horizontal + every direction change > 45°

Visual sanity check: pipes should clearly drop in the elevation; if the run is horizontal, the slope was not applied or was applied to the wrong system.

Family library + content

A well-organised Revit MEP project depends on a curated family library:

Discipline Critical families
HVAC ducts Standard rectangular + round, including transitions, elbows, takeoffs
HVAC fittings Diffusers (square, linear), grilles, registers
Pipes Standard PVC + GI + copper at all sizes
Pipe fittings Elbows (90°, 45°, sweep), tees, reducers, unions, valves
Cleanouts Branch cleanouts, line cleanouts
Equipment AHU, FCU, VAV box, fan-coil, chiller, pump, water tank

Building a project family library takes 40-80 hours initial; saves 200+ hours/year afterwards. Use Autodesk’s free MEP Content (revit-content.autodesk.com) as a starting point + customize for Indian standards.

Clash detection workflow

After modelling, before plotting, run Navisworks clash detection:

1. Import all linked models (arch, struct, MEP-A/B/C disciplines)

2. Run “Hard Clash” — find all places where 2 elements occupy the same space

3. Run “Soft Clash” — find within-clearance issues (3D fittings need access; not just collision)

4. Filter by discipline — focus on MEP-vs-structure, MEP-vs-arch, MEP-vs-MEP

5. Resolve in priority order — structural collisions first; arch second; MEP-vs-MEP third

6. Iterate through 3-5 cycles until clash count drops to acceptable level (<10 clashes per discipline pair)

For Indian commercial: typical project has 2,000-5,000 clashes initially; reduces to 50-100 after 4-6 iterations of Navisworks runs + Revit fixes.

BIM 360 + cloud collaboration

Modern Indian projects use:

  • BIM 360 (Autodesk Construction Cloud) — Revit cloud workshare
  • Procore / Aconex — submittal + RFI tracking integrated with model
  • Bluebeam Revu — model markup + drawing review

Cloud workshare reduces the “who has the latest model” question significantly; for distributed Indian + international project teams, it’s standard.

LOD progression

LOD (Level of Detail/Definition) per BIM Forum LOD Specification:

Stage LOD Description
Concept LOD 100 Mass model, no detail
Schematic LOD 200 Generic equipment, approximate sizing
Design Development LOD 300 Specific equipment, accurate sizing
Construction Documents LOD 350 Coordinated with other disciplines
Construction LOD 400 Fabrication-ready details
As-built LOD 500 Verified field information

For tender drawings: LOD 350 minimum. For construction shop drawings: LOD 400.

Five common Revit MEP mistakes

1. No shared coordinates. MEP team works in their own world; clash detection meaningless.

2. Equipment placed without insulation thickness applied. Resulting model under-clashes; on-site clearance insufficient.

3. Slope not set on drainage pipes. Pipe runs horizontal; commissioning failure.

4. Wrong system type assigned. “Supply Air” used for return — color codes wrong; tag confusion.

5. No central family library. Each project rebuilds from scratch; wastes 40-80 hours per project.

Quick checklist

  • [ ] Shared coordinates established between architect, structure, MEP
  • [ ] All MEP systems defined with correct types + colors
  • [ ] Insulation thickness applied to ducts and pipes
  • [ ] Slope set on all drainage pipes (1:50 to 1:100)
  • [ ] Equipment placed with operational clearance respected
  • [ ] Navisworks clash detection run; clashes resolved in 3-5 iterations
  • [ ] LOD progression matches project stage
  • [ ] BIM Execution Plan documented (per ISO 19650)
  • [ ] Family library curated and accessible to whole team

References: BIM Forum LOD Specification 2024; ASHRAE BIM Guideline (2017); ISO 19650:2018 (BIM Information Management); Autodesk Revit MEP User Guide; Navisworks Manage User Guide.

[Disclosure block, Legal notice — auto-included by article template]

Leave a Comment

Your email address will not be published. Required fields are marked *

Exit mobile version