Skip to content
Case study · MEP BIM coordination

Multi-family apartment block: coordinated services before site

MEP modeling and weekly clash coordination for a multi-storey residential block, so ductwork, pipework and drainage were resolved in the model rather than on site.

  • Client: MEP engineering consultant
  • Sector: residential
  • Delivered: LOD 350 models + clash reports
  • Duration: 10 weeks
Student union hostel captured for Scan to BIM
LOD 350Mechanical, electrical, plumbing
Model · coordination · reportsCoordination reports each week
About the project

Tight ceiling voids, repeated floors

An MEP consultant was designing services for a mid-rise apartment block with repeated typical floors and very little ceiling depth. Every corridor carried ductwork, sprinkler mains and drainage in the same zone.

The contractor wanted clashes closed before prefabrication of risers and corridor modules, which meant a coordinated model ahead of the construction programme.

What we delivered

  • MEP BIM models at LOD 350
  • Federated coordination model
  • Weekly clash reports
  • Coordinated corridor sections
  • Riser layouts
  • Builder’s work openings
  • Shallow ceiling voids

    Ducts, sprinklers and drainage competed for the same few hundred millimetres.

  • Several design teams

    Architecture, structure and services changed in parallel.

  • Prefabrication dates

    Riser modules had to be released on a fixed programme.

Have a building to capture? Send your point cloud and scope. We reply with an approach and quote within one working day.

Our process

From brief to coordinated model in six steps

How the work was planned, modeled, checked and handed over.

  1. 01

    Brief & standards

    Scope, LOD, template and naming agreed at kick-off.

  2. 02

    Model set-up

    Shared coordinates, levels, grids and worksets created.

  3. 03

    Modeling

    Each discipline modeled to the agreed level of detail.

  4. 04

    Coordination

    Federated model checked and clashes grouped by level and trade.

  5. 05

    Review & update

    Comments resolved and models updated between meetings.

  6. 06

    Issue

    Models, reports and sheets issued in the client’s formats.

Our solution

One coordinated model, updated weekly

Typical floors were coordinated first and then repeated, while unique levels such as the podium and roof plant were handled individually.

  • 0+Clashes resolved
  • 0 wksModel to sign-off
  • 0Riser redesigns on site
  • Typical floor first

    One fully coordinated typical floor became the template for the rest.

  • Grouped clash reports

    Clashes grouped by level, zone and trade so each team saw its own list.

  • Live meeting support

    Models updated between weekly coordination meetings.

  • Builder’s work drawings

    Openings through slabs and walls issued from the coordinated model.