• Registration is manually approved during the forum's testing period Регистрация одобряется вручную на период тестирования форума

Coordinating sprinkler head locations around beams and ductwork in MagiCAD

web3d

Administrator
Staff member
On a sprinkler layout review, head positions that looked fine in the open ceiling start colliding once the main ducts, deep beams, and light fixtures are in. I can shift heads manually, but I’m trying to avoid a cycle where every architectural move triggers a full recheck and missed coverage.

How do you coordinate sprinkler head locations around beams and ductwork in MagiCAD/Revit while keeping the layout reviewable?

  • Which linked-model changes do you treat as a reason to rerun the sprinkler checks?
  • How do you flag heads that need attention without losing the original design intent?
  • Do you coordinate branch routing and head moves together, or handle them in separate reviews?
  • What information helps the mechanical and fire-protection teams resolve a conflict quickly?

Id welcome practical examples of checks or coordination habits that have caught problems before issue. How do you keep the model useful for both design and review?
 
I’ve been through that exact loop on MagiCAD/Revit jobs. Heads look perfect in an empty ceiling, then the deep beams, mains, and lights land and everything collides.

I keep a dedicated FP coordination 3D view with filters: sprinklers, structure, HVAC (mains and large branches only), lights. MagiCAD coverage check plus Revit interference on those categories, not a full-model smash. I also keep a clean RCP overlay so reviewers can still read the original grid without fighting 3D clutter.

I rerun checks when linked models change ceiling height, beam depth or location, main duct size/route, or light positions in the same plane. Partition moves that break spacing get a rerun too. Small branch tweaks or furniture usually wait.

I never overwrite the first layout. I add a shared parameter (Original / Needs move / Coordinated) and colour-filter it. Comments hold the reason (“beam 450 mm, shift 300 mm west, coverage still OK”). Design intent stays visible; only the coordinated heads move.

Heads and branch routing go together. Moving a head without the pipe usually creates a second clash later. I lock coverage first against architecture/structure, then pull MagiCAD pipes with the head, then one more clash pass against ducts.

What actually speeds resolution: a cropped 3D screenshot, clear dimension to the obstruction, NFPA-style note (obstruction depth vs. head distance), proposed new point, and whether neighbouring heads still cover. Room, level, and grid help the mech guy find it in thirty seconds.

Habit that has saved us: freeze architecture/structure at a named milestone, run MagiCAD coverage + interference the same day, and walk clashes live with both teams. Catching a beam-and-duct sandwich before issue is cheaper than a site RFI.

The model stays useful if you keep view templates split (design vs review), don’t explode every accessory into the coordination view, and treat MagiCAD products as the source of truth instead of generic placeholders. That way the layout stays reviewable even while coordination is still moving.
 
Back
Top