Service · BIM & Clash
Federated coordination, ruthlessly resolved.
BIM execution plans, clash logs and federated model coordination that survive field handover - not the QA-stage snapshot. Calibrated to the contractor pool you actually procure with, across MENA, EU and US hyperscale builds.
- LOD 350-400 capable
- Platform-neutral · ACC · Revizto · Navisworks
- Hyperscaler-audit ready
- Pool-calibrated · MENA · EU · US
- NDA-first
- 0+
The headline is the resolved count. The win is the ones sequence-tested out before mobilisation.
- 0%
Autodesk benchmark for disciplined federation. We measure it on every retainer, not just the pitch deck.
- 0dn
30 MW colo precedent. Each early catch is a week the contractor keeps and the operator bills against.
- 0×
Drawing redline vs field change order vs commissioning re-route. Same defect, three prices.
The problem
Clash-free on screen does not mean buildable on site.
Federated BIM is now mature; the discipline around it is not. Across MENA, EU and US hyperscale builds, coordination teams declare a model 'clash-free' in the QA review, hand off, and then watch half those resolutions surface again on site - because nobody tested them against installation sequence, crew skill, or the actual contractor pool that just won the tender.
Same clash. Same trade. Different phase.
- 1×Federation· Modelled revision
Two clicks in Revit. The clash log absorbs it. UFCM™ operates here.
- 8×Construction· Field change order
Pipe hung, tray racked. Crews idle while the RFI cycle runs.
- 22×Commissioning· Re-route + re-energise
Power on, tenant inbound. Re-route is now a board-level event.
UFCM™ operates at the cheap side of the curve. Every clash resolved in federation lives at 1× for a few weeks before the same defect costs 8×.
Average cost and schedule erosion per RFI on a US construction project. Navigant Consulting via NAVFAC. A disciplined federation prevents hundreds of these per build.
The escalation is exponential, not linear. A clash log that looks resolved in week 8 of detail design can re-surface in week 32 of construction at eight times the cost - and the contractor pool will not absorb it on goodwill. Federation has to be cheap; field rework never is.
Deliverables
A federated model that holds up to install.
Every BIM & Clash engagement ships six artefacts. Each is tied to a specific milestone in the federation cadence and arrives on a published week.
- 01Anchor
BIM Execution Plan (BEP)
A BEP written for the contractor pool you actually procure with - not a generic ISO 19650 boilerplate. LOD targets per discipline, federation cadence, naming convention, owner-of-truth matrix, and the explicit handover protocol that day-one trade installers will read from.
PDF + Revit / ACC templatesWk 1 - 02
Federated coordination model
MEP, electrical, cooling, structural, fire and cabling federated on a single weekly cadence. Native files plus neutral exports (NWC / IFC / SMC) so any contractor in the pool can open, mark up, and contribute - regardless of their preferred platform.
Native + NWC / IFC / SMCWk 3 - 03
Live clash register
Every clash logged by trade-pair, severity, sequencing impact, gate, and resolution week. Not a screenshot. A live sheet your project manager, your contractor and your hyperscaler tenant audit from - same numbers, same revision, same week.
Revizto · ACC · Navisworks live sheetWk 3+ - 04
Sequencing test report
Every resolved clash re-tested against installation sequence, crew skill and access logistics. Where the resolution creates a buildability problem, we flag it and re-coordinate before the model is signed off as field-ready.
PDF + 4D snippetWk 5 - 05
Field handover pack
What the trade contractor actually receives on day one of mobilisation. Model views per install priority, sequencing call-outs on top-30 critical clashes, RFI pre-empt notes, and the named coordinator they call when reality diverges from the model.
PDF + model views + RFI pre-emptsWk 6 - 06
Site retainer playbook
If you keep us on through construction: weekly clash-resolution cadence, RFI triage protocol, change-order forensics, and a live RFI-prevention scorecard the operator and investor read from quarter to quarter.
Live sheet + weekly cadenceLive
Method
Four gates. One federated model.
BIM & Clash uses our Upterix Federated Coordination Matrix (UFCM™) methodology - four sequential gates, six disciplines, one live clash register that survives field handover.
We do not just check for spatial clash. Every coordinated resolution is evaluated against installation sequence, crew skill and access logistics - would resolving this on screen create a buildability problem on the slab? The federated handover model is the product, not the QA snapshot. If the trade installer's day one is uneventful, federation worked.
AI-hall density that breaks traditional discipline boundaries — where cooling × electrical × IT coordinate at LOD 400 across the same physical metre, not in separate plant rooms.
Eight disciplines × five phases, calibrated against federated-model handovers on hyperscale builds across MENA, EU and US.
ISO 19650-compliant BIM Execution Plan with full information-delivery schedule.
- ISO 19650 BIM Execution Plan (BEP)
- BIMForum LOD specification table
- COBie-aligned information-delivery schedule
Gate by gate · what each verdict means
A federation can pass three gates and fail one. Most do.
“Coordination ends not when the model is clean, but when the trade contractor's first day on site is uneventful.”
Gate 1 - BEP fit-for-pool. The first failure mode is structural and quiet: a BEP authored for a Tier-1 European GC, then handed to a mixed-pool tender list whose BIM maturity varies contractor by contractor. LOD targets land on a subcontractor who cannot deliver them. The federation cadence assumes a stack the trade team does not run. Day one of detail design the document is already wrong - and nobody notices for six weeks.
Gate 2 - Federation discipline. Most BIM consultancies stop here. A disciplined federation, clean weekly clash reviews, an owner-of-truth matrix that is actually consulted, naming conventions that hold under pressure. This is where the QA gate signs off and the bills get paid. It is also where the real trouble starts: a model can be flawlessly federated and still be unbuildable on the slab.
Gate 3 - Sequencing test. Every coordinated resolution gets re-tested against install order, crew skill and access logistics. Would a tray re-route conflict with seismic bracing? Would a busbar re-routing leave no install window once CRAH units are placed? Would the slab penetration sequence work backwards from the energise plan? These questions do not show up in Navisworks - they show up on the slab, three months later, as RFIs.
Gate 4 - Handover viability. The moment the trade contractor opens the federated model on day one of mobilisation and tries to install. If they cannot find install priorities, sequencing notes, RFI pre-empts and a named coordinator inside the handover pack, the federation effectively ended at sign-off - not at install. We grade every engagement against all four gates and publish the verdict to the operator. Pass three, fail one - we say so. It is the only honest way to declare a federation field-ready.
UFCM™ · Federated Coordination Matrix
Who owns federation, at every phase.
Six disciplines on the vertical. Four design-to-construction phases on the horizontal. Each cell names the owner of federation and the cadence we hold to. Coordination accountability is explicit before kickoff - not improvised at the QA gate.
- Upterix lead
- Engineer of Record
- Construction Manager
- Trade contractor
- advisory
- monthly
- weekly
- daily
Cell intensity = cadence. Upterix takes lead ownership where coordination accountability is highest - typically cooling and cabling at IFC and through construction, where the model meets the field.
UFCM™ · Live clash register
Not a screenshot. A live sheet.
Every clash in your federation is logged by trade-pair, severity, sequencing impact, gate and resolution week. Your project manager, your contractor and your hyperscaler tenant audit from the same sheet, the same revision, the same week.
Specimen below is anonymised from a 60 MW colo build, rev 14. Every row links to a drawing reference, an RFI pre-empt, and the named resolver who closes it.
- 2 crit
- 2 high
- 2 med
- C-014CRITBusbar ⇄ Cable traySequencing blocks crane lift window on Hall A· Wk 4
- C-027CRITCRAH return ⇄ Structural slabRe-route needs anchor relocation, drift > 180mm· Wk 5
- C-041HIGHGPU PDU ⇄ Cold-aisle containmentInstall sequence incompatible with energise plan· Wk 5
- C-058HIGHFM-200 piping ⇄ MEP corridorPipe penetration conflicts with cable tray run· Wk 6
- C-072MEDSprinkler basket ⇄ ToR switchSpacing under NFPA-13 minimum for row 12· Wk 6
- C-089MEDSlab penetration ⇄ Rack alignmentDrift exceeds 200mm on row 7, re-survey required· Wk 7
Six of 1,200+ on a typical 30 MW build · audit-ready
UFCM™ · Engagement cadence
Week by week. With the handover marked.
- Wk 1Wk 1
BEP authored to the pool
Contract-specific LOD targets, federation cadence, owner-of-truth matrix and naming convention. Sized to the actual BIM maturity of the contractors on your tender list, not the generic ISO 19650 boilerplate.
- Wk 2Wk 2
Federation kickoff
First weekly clash review. Disciplines federate on a single cadence: MEP, electrical, cooling, structural, fire, cabling. Owner-of-truth is in force from day one - not negotiated later.
- Wk 3Wk 3
Discipline coordination
Continuous federation at LOD 350. Live clash register populated by trade-pair and severity. RFI pre-empts logged against every critical resolution before the gate review.
- Wk 4Wk 4
Top-30 sequencing test
Every critical and high-severity clash is re-tested against install order, crew skill and access logistics. Resolutions that create buildability problems are re-coordinated, not deferred to the field.
- Wk 5Wk 5
Handover dry-run · Day -7
Site team walked through the federated model. Install priorities reviewed face-to-face. RFI pre-empts annotated. Named coordinators introduced before mobilisation, not after the first standup.
- Wk 6Wk 6
Field handover · Day 0
Trade contractor opens the model and starts installing. Field handover pack shipped: model views per install priority, top-30 sequencing call-outs, RFI pre-empts and the named coordinator they call when reality diverges.
- Wk 7+Wk 7+
Live RFI triage · Day +7 onward
Weekly standup with the site team. Live clash resolution in days, not sprints. RFI-prevention scorecard maintained quarter to quarter. Retainer trigger - or graceful handoff when the federation outlives the engagement.
Commercial terms
Three engagement weights. Range-priced.
- 01Health-check· 2 weeks$20-30Kfixed-fee
- BEP review + federated-model sanity audit
- Top-30 clash triage
- Findings memo with recommended cadence
- 02Coordination engagement· 6-12 weeks$80-140Kfixed-fee
- BEP authoring + federation kickoff + sequencing test
- Live clash register through to handover
- Field handover pack on Day 0
- Pool calibration across MENA · EU · US
- 03Build retainer· 4-6 months typical$30-45K / mofixed-fee
- Live RFI triage in days, not sprints
- Weekly clash resolution standup with site team
- Quarterly RFI-prevention scorecard
- Outcome-priced option on demonstrably avoided RFIs, capped
+ Includes- Named lead coordinator
- Warranty on in-scope envelope
- Graceful handoff at retainer end
All tiers — outcome-priced option available (5–15 % of demonstrated rework avoided, capped). Insurance-backed assurance on Comprehensive.
Why us, here
Coordination calibrated to the pool you actually procure with.
BIM maturity is not uniform across MENA, EU and US. The federation that worked on your last build will not survive the next contractor pool unless someone re-tunes it - and most consultancies will not.
“Coordination ends not when the model is clean, but when the trade contractor's first day on site is uneventful.”
Every hyperscale procurer eventually discovers the same thing the hard way: a BEP that works for a Tier-1 European GC fails on a mixed-pool Gulf tender list, and a BEP that works for a Riyadh megaproject does not survive an Irish data centre with three different specialist subcontractors. BIM maturity varies contractor by contractor, region by region. We calibrate the federation to whom you actually procure with - not to a generic ISO 19650 boilerplate written for nobody.
Calibration starts before kickoff. We read your tender list, score each contractor's BIM maturity against the LOD target you need, and rewrite the BEP cadence and stack assumptions to land on people who can actually deliver. The federation cadence assumes the platform your trade team runs. The owner-of-truth matrix names roles your contracts can enforce.
Through construction, we hold the federation against the field reality - which is where most consultancies disengage. RFI triage in days, not sprints. Live clash resolution by a named coordinator. Sequencing test re-runs when the actual crew on site differs from the planned crew. The federation outlives the kickoff because someone owns it daily, not monthly.
We are not a BIM software reseller, a training shop, or an audit-and-deliver consultancy. We do not push Revizto licences or run weekend Navisworks workshops. The product is coordination that survives field handover - measured against the trade contractor's first uneventful day on site, and against the operator's first quarterly review.
What you get when you sign.
- Duration
- 6-16 weeks · build retainer optional
- Team
- 1 senior lead + 2 discipline coordinators
- Platforms
- ACC · Revizto · Navisworks · native files at handover
- Handover
- Model views + install priorities + RFI pre-empts + named callback
- Liability
- Coordination warranty on agreed in-scope envelope
- Outcome-pricing
- Available on demonstrably avoided RFIs · capped
How we compare
Coordination, not BIM-services.
The market is crowded with offshored BIM bureaus selling federation as a deliverable. Six questions tell you whether you are buying coordination or a screenshot.
- 01Federation cadenceTypical BIM bureau
Whatever the EoR documents - usually monthly, paper-driven, drifts after kickoff.
Upterix coordinationWeekly, enforced, with a named owner-of-truth per discipline.
- 02Clash-log ownershipTypical BIM bureau
Bureau owns the sheet. You see screenshots. Handover is a final PDF.
Upterix coordinationYou own the live sheet from day one. Audit-ready every revision.
- 03Sequencing testTypical BIM bureau
Not in scope. Coordination ends at the QA gate.
Upterix coordinationEvery critical resolution re-tested against install order, crew skill and access.
- 04Platform postureTypical BIM bureau
Bureau's preferred stack, often locked inside their tenant.
Upterix coordinationYour stack: ACC, Revizto, Navisworks. Native files at handover.
- 05Field handoverTypical BIM bureau
Model files and a viewer licence. Site team figures it out.
Upterix coordinationPack with install priorities, RFI pre-empts and a named coordinator on call.
- 06Liability postureTypical BIM bureau
Service-level only. Misses absorbed by the EoR or the contractor.
Upterix coordinationCoordination warranty. We fund field correction inside the in-scope envelope.
FAQ
Six questions every procurement call asks.
If you do not see your question, the answer is in the engagement letter - we do not hide commercials behind a discovery call.
Yours. Platform-neutral by charter. We work natively in ACC, Revizto and Navisworks and hand back source files in the format your team already runs. We do not resell licences and do not earn commissions on any BIM stack - so platform choice is a coordination decision, not a sales conversation.
You do, completely. Native source files transfer with the full review history attached - every clash log entry, every owner-of-truth verdict, every RFI pre-empt. The model is your asset from day one. We hold the cadence; we never hold the data.
LOD 350 for coordination, LOD 400 for prefabricated zones - electrical skids, cooling modules, MEP racks. Higher LOD across the whole model is wasted effort that slows the federation and inflates fees; lower fails the sequencing test. The LOD plan is in the BEP, signed before kickoff.
Coordination warranty. If a missed clash sits inside the agreed in-scope envelope, we fund the field correction up to a cap defined in the engagement letter. The cap is typically a multiple of the fixed-fee scope, set transparently against your project value. It is the only insurance posture we know of in this category - and the reason our retainers renew.
On demonstrably avoided RFIs against a pre-agreed baseline. We set the baseline at kickoff - either an industry benchmark for your build size, or your own historical RFI volume from a prior comparable project. We then share in the savings, capped at a multiple of the fixed-fee. The formula is in the engagement letter; no surprises in the closing invoice.
One senior lead plus two discipline coordinators for a typical 30 MW build, scaling with hall count and build phase. The lead has authored a BEP and run federation through construction on a hyperscale project before - not their first build. We staff to RFI volume, not headcount benchmarks, and we name the team in the proposal so you know who shows up.
Coordination that survives the first day on site.
Start with a Rapid Audit - five days, USD 5,000, fixed. We score your federation against UFCM™ Gate 1 and tell you exactly which contractor-pool calibrations are missing before you lock the BEP. Walk away with a memo your project board can act on, with or without us.