Skip to main content
BIM SERVICE · CLASH + COORDINATION

Every conflict resolved before tender release.

Federated clash detection across architectural, structural, and MEP models. Navisworks-driven, BCF-tracked, weekly cadence. Site rework gets caught at the model — when it costs minutes, not when it costs RFIs and variations.

  • 55+ projects coordinated
  • Navisworks Manage
  • BCF 2.1 workflow
  • ISO 19650-2 certified
WHY IT MATTERS

Site rework is what BIM was invented to prevent. Skip clash detection and you forfeit every other BIM benefit.

  1. 01

    Variations multiply

    A 2 cm duct clash discovered on site becomes a variation order. Discovered in Navisworks, it becomes a 5-minute model edit. The cost difference is 1000×.

  2. 02

    RFI floods drown progress

    Without federated coordination, contractors raise RFIs for every conflict they hit. Each takes days to resolve. The model is supposed to answer most of those questions before they're asked.

  3. 03

    Coordination drawings lie

    When clash detection isn't the source of truth, coordination drawings get manually patched and stop matching the model. Three disciplines, three documents, none agreeing.

WHAT WE DELIVER

Federation, detection, resolution, repeat.

BIM coordination is a weekly cadence, not a single deliverable. We run it as a managed service from LOD 200 through tender: federate models, detect clashes, log issues, drive resolution, re-run. Every closed clash has an audit trail.

  • Federated Navisworks model — A + S + MEP combined weekly, version-controlled
  • Clash detection matrix — priority-1 (hard clashes), priority-2 (clearance), priority-3 (advisory)
  • BCF 2.1 issue log — every clash owned, dated, resolved, signed off
  • Weekly clash report — open / resolved / aged, by discipline + zone
  • Coordination drawings — plenum sections + plant room layouts extracted from federated model
  • Pre-tender clash-clean sign-off — zero P1, zero P2 before tender release
  • Service penetration coordination — sleeved openings sized in structural before pour
  • Constructability review — buildability assessment from the coordinated model
OUR APPROACH

A cadence, not a phase.

Clash detection that runs once at the end of design is theatre. We run it weekly from LOD 200 onwards so clashes never accumulate.

  1. 01

    Coordination kickoff

    BIM Execution Plan sets clash matrix, tolerance rules, priority definitions, BCF workflow. Everyone agrees on what counts as a clash before anyone draws.

  2. 02

    Weekly federation

    Tuesday: pull latest A/S/MEP models, federate in Navisworks, run automated clash detection. New clashes hit the log by Wednesday.

  3. 03

    BCF-driven resolution

    Each clash assigned to an owning discipline, with a target resolution date. Resolution happens in Revit; closure is logged with the edit reference.

  4. 04

    Tender-clean sign-off

    Before tender release the federated model has zero priority-1 or 2 clashes. Tendering contractors get a coordinated set — not three uncoordinated discipline sets.

CLASH DETECTION · FAQ

Clash detection — common questions.

What clash detection tools do you use?

Navisworks Manage is our primary clash detection engine — it federates Revit, Civil 3D, Tekla, and IFC models in a single environment and runs rule-based clash sets. We use Solibri Office for IFC-only workflows when a contractor's discipline doesn't author in Revit. BIM 360 / ACC Coordinate runs cloud-based clash detection that integrates directly with the CDE for issue assignment. For specialty work (e.g., MEP-against-MEP fine clearances), we author custom clash rules per project, not just the out-of-box defaults.

What's a 'priority 1' vs 'priority 2' clash?

Industry convention varies, but Design Zone uses: Priority 1 — hard physical clash (steel beam through MEP duct, pipe through structural slab). Must be resolved before tender. Priority 2 — soft clash or clearance violation (MEP equipment with no maintenance access, services in ceiling void with no room for insulation). Resolved before LOD 400. Priority 3 — design-intent issue (architectural finish doesn't match MEP grille position). Resolved as design polish. We track all three in the BCF issue log but only Priority 1 + 2 zero-out is required to advance the LOD gate.

How often should clash detection run on a project?

Weekly federation runs through Coordination phase (after LOD 200 is reached) — that's the core cadence. Daily runs as the project approaches a tender milestone. Monthly check after handover to verify the contractor isn't introducing new clashes during fabrication-stage detailing. Run frequency matters: if you wait until LOD 300 to run clash detection, the issues are 5x more expensive to resolve than if caught at LOD 200. The federation calendar gets written into the BEP at project start.

Do you support BCF (BIM Collaboration Format) workflows?

Yes — BCF is how we exchange clash issues between Navisworks (where they're detected) and Revit (where they get resolved). The standard contains the clash location, viewpoint, screenshot, and assigned discipline. We use BCF 2.1 (the most widely supported version) for Revit↔Navisworks and BCF 3.0 when supported by the contractor's tooling. BCF integration with BIM 360 issue management means the issue auto-tracks status: open → assigned → in-progress → ready-for-verification → closed. No manual spreadsheets.

Can you train our team on clash detection?

Yes — Design Zone is an Autodesk Authorised Training Centre (ATC). Standard offerings: Navisworks Manage 2-day intensive (workspace, federation, clash sets, BCF), Revit MEP Coordination 3-day (model setup for clash, working with federated models), and BIM 360 Issue Management 1-day (project setup, BCF round-tripping). Custom programs available — most clients want a project-specific workflow walkthrough rather than the generic curriculum. Training delivered in EN or AR. Discounts for cohorts of 5+.

START YOUR PROJECT

Tell us about your project.

Drop your details — a senior BIM lead will reach out.

What happens next
  1. 1

    You send the inquiry

    60 seconds — name, email, scope brief.

  2. 2

    We respond within 24 hours

    A senior BIM lead reads your scope and replies — bilingual EN/AR.

  3. 3

    30-min consultation call

    Real conversation. EIR + BEP scope outline. ISO 19650 aligned.

24hResponse
55+Projects
60+Specialists
Quick inquiry · 60 seconds
Your data stays with us