BIM coordination

A federated model, a clash register that closes, and coordinated sections issued per trade before installation starts.

BIM coordination

Clashes are resolved in the model, on a schedule, and the ceiling void is cleared before a hanger goes up.

Who this is for Main and EPC contractors, technical offices, and owners who need one coordinated source of geometry.

Price this scope

What you receive

Federated model, by zone

Architectural, structural and MEP models assembled to one coordinate system and split into zones a team can actually review.

Clash register that closes

Every clash carries an owner, a zone, a proposed resolution and a status. The register is issued with the model, not instead of it.

Coordinated service sections

Ceiling-void and service-corridor sections issued per trade, at the levels the installer will actually set out from.

Model-based quantities

Quantity extraction straight from the model for a tender BoQ, with the extraction rules written down so a figure can be traced.

As-built model and asset data

The model maintained through construction and handed over with COBie asset data the facility team can load.

BIM execution plan

Naming, levels of information need, the review protocol and the common data environment, agreed before anyone models anything.

The scope, at a glance

  • Revit modelling

    Architectural, structural and MEP modelling in Autodesk Revit.

  • Steel detailing

    Steel detailing models in Tekla Structures: fabrication-ready.

  • Clash detection

    Multi-discipline clash detection in Navisworks, with a register that closes.

  • 4D and 5D integration

    4D construction sequencing and 5D quantity and cost integration.

  • Shop drawings and as-built

    Shop drawings, fabrication drawings and as-built models.

  • BIM Execution Plan

    BIM Execution Plan (BEP) and ISO 19650 implementation across the team.

  • Scan-to-BIM

    Point cloud to BIM for renovations and verification of what is on site.

  • Quantity take-off

    Quantity take-offs (QTO) extracted directly from the model, to XLSX, CSV or PDF.

  • Accurate and coordinated Clash-free models cut errors and rework.
  • Time and cost savings 4D/5D planning and model take-offs drive better decisions.
  • Quality and reliability Standards-based delivery to ISO 19650.
  • Collaborative delivery One source of truth for the whole project.

A federated model, a clash register that closes, and coordinated sections issued per trade before installation starts.

How it is produced

01

Set-up before modelling

Shared origin, naming, and the level of information need per stage are fixed first. Retrofitting them onto a live model is what makes coordination expensive.

02

Clashes are run by zone, on a cycle

A dated cycle per zone, with a report each round, so the register shrinks on a schedule rather than at the end.

03

Resolutions are engineered, not deferred

A route change is checked against the discipline that owns it before it is proposed, because a clash moved is not a clash closed.

04

One model feeds every output

Quantities, energy zones, credit evidence and the as-built all come from the same geometry, so they cannot drift apart.

Software

  • Revit
  • Navisworks Manage
  • Autodesk Construction Cloud
  • Solibri
  • Dynamo
  • Recap

Standards and codes

  • ISO 19650
  • COBie
  • IFC 4

What the deliverable is

  • RVT
  • IFC 4
  • NWD / NWC
  • Coordinated PDF sets
  • COBie XLSX
  • BCF issue exchange

Deliverables

Pick a discipline and tick what you need. Send the selection and its indicative budget range appears on screen and arrives in your inbox.

Price this scope
Deliverables Unit
Federated model + clash detection, LOD 300 per m²
MEP coordination model, LOD 350 per m²
MEP coordination: hospital / data centre per m²
Clash detection round + report per round
Scan-to-BIM as-built, architectural + structural per m²
Revit family / content creation per family
BIM execution plan and standards setup lump sum
Ongoing coordination retainer per month

Questions clients ask

We already have consultant models. Do you rebuild them?

No. We federate what exists and report what is missing for coordination. Rebuilding is only proposed where a model cannot carry the level of detail the trade needs.

What level of development do you work to?

It is set per stage and per system in the execution plan. Coordination of a ceiling void needs LOD 350 for the services and LOD 300 for the structure around them.

How is a clash counted as closed?

When the geometry is changed in the model that owns it and the next run no longer reports it. A note in the register is not a closure.

Can you work inside our own CDE and templates?

Yes, and that is the usual arrangement on a dedicated-team engagement. We work to your standards and hand everything back at closeout.

Rendering of the pavilion at dusk.

A question that is not here?

Ask the engineer who would run your project. Send the drawings and the answer comes back in writing.

Send us one package.

Send a package and you get a scope, a fixed price and a delivery date within two working days.

Selected work

Built, modelled, delivered.