+1 (409) 800-6601
contact@virtualbuildingstudio.com
The fastest way to bury a real clash is to report it next to thousands of harmless ones. Many of them end with a clash report that's so long the foremen skim it and close it. This happens because of the test setup. A blanket test compares each model to every model, so teams get every overlap Navisworks finds, even the harmless ones. Coordinators spend their week digging through the noise instead of fixing real clashes.
A good MEP clash detection matrix removes that problem at the source. It shows coordinators which trades to compare how to sort them and how much overlap to ignore. The first step is to see why raw results fail.
The Problem with Unfiltered Clash Detection in BIM
A healthy coordination run hands each trade a short list of conflicts it can fix. Raw Navisworks tests usually miss that mark. Clash Detective compares geometry and nothing else, so coordinators must supply the judgment. Without that judgment, the Clash Detection Workflow buries real problems under hundreds of harmless ones.
Combining architectural, structural and MEP models without rules multiplies three predictable problems:
- Placeholder duplicates: Architectural families hold fixtures and diffusers that overlap the subcontractor’s models. They also contain placeholder duplicates.
- Insulation and jacketing: Tests may treat insulation as physical geometry. This creates apparent clashes between pipes and ducts even when sufficient clearance exists.
- Missing openings: At the start, slabs and walls have no cutouts, so every riser and stack shows a conflict. They are a problem when slabs and walls lack cutouts.
That sound costs more than the model. Bad project data and not talking well are connected to 48% of redo work in U.S. Construction, which costs $31.3 billion according to a 2018 Autodesk and FMI survey The people who took the survey also said they spent 35% of their time, on work that does not help, like fixing problems and correcting mistakes. Some companies send this sorting out to MEP clash detection services when the amount is too much for their own team to handle.
Constructability issues vs. tolerance noise
The first step to cutting the noise is to share a definition of a real problem. Installation is impossible or redesign is necessary: a real constructability problem. A 36-inch chilled water pipe crossing a post-tension transfer girder is one. So is a sloped sanitary line cutting through primary ductwork at a mechanical room exit.
Tolerance noise is anything a crew would fix with a hanger adjustment on site. Flex duct brushing a conduit and a hanger touching a stud both qualify. So does a conduit bundle edging a fraction of an inch into a non-critical ceiling buffer. MEP coordination for contractors works only when every trade agrees on this line before testing starts. Drawing that line consistently takes a trade ranking, which comes next.
Establishing the Trade Spatial Hierarchy (The Rules of Gravity)
Telling real conflicts from noise needs a priority order that every trade accepts. The rule is simple: the trade that can move least gets the space first. Physics and code decide who that is, not seniority on the project. Coordinators record the order in an MEP Coordination Matrix that later drives every test. Rank the trades from least to most flexible:
- Structural framing and post-tension slabs: Structure stays fixed, so nobody notches or offsets it without a structural engineer’s stamped approval.
- Gravity plumbing and sanitary drainage: Waste and storm lines shall have continuous slope of 1/8 to 1/4 inch per foot, depending on the pipe size.
- Large primary HVAC ductwork: Wide trunks need deep ceiling space, and every transition adds fan energy and sheet metal cost.
- Pressurized pipework: Chilled water, fire protection, and domestic supply can offset around obstacles with elbows. Sprinkler lines win over domestic branches because code sets their coverage.
- Electrical cable trays and conduit: Generally, more flexible than structural elements, gravity drainage, and major HVAC distribution systems. Branch conduits can often be rerouted in the field when necessary.
Teams that bring in MEP coordination and clash detection support usually lock this order in at kickoff. The ranking becomes the first column of your MEP trade priority matrix. It says who moves, and tolerances say how far apart trades must stay.
Defining Hard vs. Soft Clash Tolerances by Trade Interface
The ranking decides who moves, and the tolerances decide when a conflict is worth bringing up. A BIM clash tolerance table gives a number to each pair of trades to check against. True overlaps are clashes. Soft clashes are clearance issues such as a pipe getting too close to a valve handle. Navisworks refers to these test types as Hard and Clearance and in each one the tolerance field works differently. A hard test skips overlaps that're smaller than the tolerance. A clearance test will show anything that's closer, to the tolerance.
Start with the values and change them to fit your project specifications.
Insulation needs its own handling. Navisworks includes an Insulation Thickness rule for clearance tests, which drops pipes that already have enough room for their jacketing.
Phased setup: core and shell vs. interior fit-out
Tolerances also depend on timing, since early models cannot support fit-out precision. Split the tests into three batches:
- Core and shell: Core and shell will be tested against risers, shafts, mechanical room mains, and busways at the tolerances.
- Interior fit-out: Interior fit-out will be tested for branch ducts, VAV boxes, sprinkler lines, cable tray branches, and ceiling framing.
- Maintenance validation: For access zones around dampers, valves and equipment run clearance tests last.
Firms that provide MEP BIM coordination services usually run these as separate batches. Each trade then sees only the conflicts that match its current milestone. Once phases and tolerances are agreed, the matrix needs to live inside Navisworks as repeatable tests.
Configuring Automated Search Sets in Navisworks Manage
A tolerance table on paper does nothing until each row becomes a test. Each row of the MEP Coordination Matrix becomes one test pair, and Search Sets let coordinators build those pairs. A Selection Set freezes specific objects, so it breaks when a subcontractor re-exports a model. A Search Set stores a rule instead, such as Category equals Ducts, and finds new geometry when models update.
Base the rules on three Revit properties:
- Category: Ducts, Pipes, Cable Trays.
- System Type: Supply Air, Sanitary, Chilled Water.
- Reference Level: Level 02, Level 03.
Agree on these parameters with every modeling team before the first export. Consistent naming then lets coordinators build sets like MEP_HVAC_SupplyDuct_L02 in minutes.
Export the finished sets to XML and import them on the next project. The batch feature in Clash Detective works the same way for tests, so a coordinator can load dozens of pairs such as TEST_STRUC_vs_HVAC-DUCT in one step. Combined, these exports make a Navisworks clash matrix template that can be reused. Full-spectrum MEP BIM services Providing firms maintain this library in a shared folder so that every project begins with the same rules. Tests are only worth doing if the results get to the right person. That means clustering the next job.
Clash Grouping and Issue Tracking Workflows
Running the tests is the easy part. Triage takes most of the effort, because a long list of single pins overwhelms the foremen who must act on it. Coordinators fix this by combining related pins into one issue.
Group clashes the way a superintendent walks the site:
- By run: Eight sprinkler branches crossing one cable tray become a single issue.
- By level and grid: Tag each issue with an intersection such as L03_Grid_F4-G5, so fabricators know where to look.
- By zone: Isolate mechanical rooms and electrical rooms so one contractor can close a plant room in a single pass.
This structure is where MEP coordination for contractors pays off, since foremen see only their own zone.
Round-tripping issues through BCF
There’s still a way, to the people who model the grouped issues. The open BIM Collaboration Format, BCF includes the camera view, element IDs, assignee, due date and status of each issue. Coordinators shove it into Revizto, Procore or Autodesk Construction Cloud and trade modelers open the issue within their software. This is where the MEP BIM coordination services providers usually put the deadlines so that each issue has a deadline. The end of a Clash Detection Workflow is the modeler closing the issue where the fix was made not in a spreadsheet.
Conclusion
A matrix turns coordination from a cleanup job into a planned process. Rank the trades, set tolerances, build search sets, group the results and track every fix through BCF. Each step removes noise before it reaches the foreman. Teams that want an experienced partner for the heavy lifting can bring in MEP clash detection services. Pairing the matrix with MEP BIM services from modeling through coordination keeps data consistent at every handoff.
Clash fatigue isn’t a personality trait; it’s a setup problem. Fix It Now!
