Mechanical, electrical, and plumbing modeled to LOD 300, federated with architectural and structural, clash-resolved before tender. BOQs and equipment schedules generated directly from the model — no spreadsheet drift, no surprise variations.
Ducts that hit beams, conduit routes that block plumbing, plant rooms that won't fit the equipment ordered — every clash found after tender is a variation, a delay, and an RFI cycle.
When MEP quantities live in spreadsheets instead of being extracted from the model, they go stale within a week of any design change. Tender prices reflect the wrong scope.
Three discipline models that never federate, three sets of drawings that don't agree, three Navisworks reports nobody acts on. "MEP coordination" becomes a line item, not an outcome.
Mechanical, electrical, and plumbing modeled in Revit MEP, federated weekly with the architectural and structural models in Navisworks. Every clash resolved before tender release, every quantity extracted from the model, every schedule live-linked.
Most projects treat MEP coordination as a phase at the end. We federate from the first design week — small clashes resolved when they cost minutes, not when they cost shop-drawing redo.
A + S + MEP teams start modeling at the same time off a shared coordination model. No "wait for architecture to finish" handoff.
Every Tuesday we federate in Navisworks and run automated clash detection. New clashes are logged, owned, and dated for resolution.
Clashes resolved through BIM Collaboration Format issues — every closed clash has a Revit edit log attached, no verbal-only fixes.
By tender release the federated model has zero priority-1 or priority-2 clashes. The drawing set extracts from the same model — nothing to "match up" later.
90,000 m² across two buildings — Visitors Pavilion plus the Operational Building (OMC). MEP federated with architectural across both blocks. Complex plant rooms, shared services backbone, AHU coordination through long-span structure — clash-resolved before contract tender.
Mechanical (HVAC, plumbing, fire), Electrical (power, lighting, low-voltage), and Plumbing/Sanitary services modeled in Revit MEP at coordination LOD (typically 300), then federated weekly with architecture and structure in Navisworks. The deliverables are: a clash-free 3D model, BCF-tracked issue resolution, equipment schedules extracted from the model, single-line diagrams that match the model, and pipe/duct routing that respects ceiling voids, raceways, and access requirements. The clean LOD 300 model is what gets handed to the contractor for fabrication-stage detailing.
LOD 300 has duct/pipe runs sized correctly with the right fittings, equipment in correct locations, and no clashes — this is what tender documents and BoQ extract from. LOD 400 adds: fabrication-ready connections (welded vs flanged, hanger details), insulation thicknesses with cladding allowance, bracket and support hangers as discrete elements, and fabrication-stage spool drawings. Most Saudi projects hand LOD 300 to the MEP subcontractor and let them author LOD 400 in their own shop-drawing process. We can author LOD 400 directly when the contractor doesn't have BIM capability in-house.
Yes. Delivered on 12+ projects to date. The deliverable includes: spool drawings with welds/flanges marked, hanger and support locations as discrete model elements with structural attachment specs, single-line diagrams synchronized with the model, and BoQ tied to model elements via shared parameter mapping. We can output to MagiCAD for piping fabrication, or directly to fabrication CAM via IFC export when the manufacturer's pipeline supports it.
MagiCAD for HVAC piping fabrication and pressure drop calculations (loved by mechanical contractors in Saudi). DDS-CAD when an electrical contractor wants schematic+model in lock-step. CYME for low-voltage cable routing on large estates. For specialty items: Pulsim for plumbing pressure analysis, Trace 700 for HVAC load calculations, Dialux for lighting analysis. We pull all of these back into the federated Revit MEP model so the federated coordination model stays as the single source of truth.
Risers are the highest-stakes coordination zone — every floor's plumbing, electrical, and HVAC main feeds compete for shaft space, and any change late in the project cascades through every floor. Our approach: dedicated riser model in early stage Programming, sized to floor plate constraints with 20% spare capacity, then locked. Every floor authors against that locked riser. Quarterly checkpoints federate the floors back to the riser to verify nothing drifted. This is how we kept 7,950 m² across 6 floors at Aleen 152 clash-free at riser level.
Drop your details — a senior BIM lead will reach out.
60 seconds — name, email, scope brief.
A senior BIM lead reads your scope and replies — bilingual EN/AR.
Real conversation. EIR + BEP scope outline. ISO 19650 aligned.