Sönmez Design logo
TR|EN

BIM · Coordination · 6 min read

How are architectural, structural, electrical and mechanical designs coordinated in one model?

Short answer: Architecture and engineering coordination is achieved by preparing the architectural, structural, electrical and mechanical models in Revit on the same grid and level system and combining them regularly in Navisworks. Clashes are reported, decided on in weekly meetings and fixed in the relevant model. Problems such as beam–duct, column–door or cable tray–sprinkler conflicts are solved before they reach the site.
Convention and conference center project, Sönmez Design

Why is coordination part of design?

Architectural decisions in a building are not independent of engineering decisions. Ceiling height depends on beam depth and on the size of the duct running above the ceiling; the façade rhythm depends on column spacing; the location of wet rooms depends on service shafts. When these decisions are taken in separate offices at different times, conflicts surface on site. In a shared model, each discipline sees the others' decisions while the design is still evolving.

01Shared gridgrids, levels02Discipline modelsarch, structure, MEP03FederationNavisworks04Clash reportpriority, owner05Decisionmodel update
Diagram — Coordination is not a one-off check but a cycle repeated throughout design.

The most common clashes

ClashConsequenceDesign solution
Beam – ventilation ductCeiling drops or duct is reducedBeam depth, duct route and ceiling level are decided together
Column – door or windowOpenings shrink, the façade suffersGrid spacing is set together with the façade rhythm
Wet room – beamDrain pipes cannot pass with the required slopeWet rooms are stacked and shaft positions fixed early
Cable tray – sprinklerRemoval and reinstallation on siteCeiling-void zones are allocated to each discipline

How coordination works

  1. BIM Execution Plan: coordinate system, file structure, LOD targets and meeting frequency are agreed at the start.
  2. Discipline models: each team builds its own Revit model and sees the others as links.
  3. Federation: models are combined in Navisworks at regular intervals and clash-tested with rule sets.
  4. Meeting: clashes are prioritised; decisions and owners are recorded.
  5. Update: the relevant model is corrected and checked again in the next cycle.

Decisions for the architect

  • Floor-to-floor height and ceiling level: set early, leaving room for service zones.
  • Shafts and plant rooms: placed within the plan diagram rather than squeezed in later.
  • Façade and grid: set up together with the structural system.
  • Wet rooms: stacked vertically between floors wherever possible.

These decisions are even more critical in tall, crowded spaces; we give examples in our article on convention and conference center design.

FAQ

Frequently asked questions

Which software is used for clash detection?

Discipline models are usually combined in Autodesk Navisworks and clash-tested with rule sets. Basic interference checks can also be run inside Revit.

How often should coordination take place?

It depends on project size; during the construction-drawing stage, weekly or fortnightly cycles are common.

What if architecture and engineering are in different offices?

Coordination is still possible, but a BIM Execution Plan becomes even more important for shared coordinates, file exchange and decision tracking.

Does coordination increase cost?

It requires extra effort during design, but usually lowers total cost by reducing rework, lost time and change orders on site.

At which LOD is coordination carried out?

Construction drawings are usually coordinated at LOD 300–350, and installation coordination at LOD 400.

Let's coordinate architecture and engineering in one team.

We deliver architectural design together with the structural, electrical and mechanical disciplines in a shared Revit model. You can browse our projects.

Website designed by Sönmez HOS Group