(and how to avoid the pain)
When it comes to BIM federation, no other subject is so core to the matter as geolocation.
If you’ve ever heard:
- “The model is in the wrong place,”
- “The architect’s model doesn’t line up with civil,” or
- “Nothing matches the survey,”
…you’ve met a geolocation problem.
In BIM, geolocation is simply making sure everyone is building their model in a common real-world reference, so models, surveys, and coordinates align. When it’s wrong, teams burn time “nudging” models around, and small errors become expensive confusion later.
What “geolocation” actually means (plain English)
Geolocation is the rules for where the model sits in the real world and how it is oriented.
At a minimum, it answers:
- Where is this project on the planet? (coordinate system / origin)
- Which way is north? (orientation)
- How do elevations relate to reality? (levels and datums)
The symptoms (how you know you’ve got a problem)
Geolocation issues usually show up as:
- The model falls apart when attempting BIM federation
- Models from different disciplines don’t overlay properly
- The model is kilometres away from the survey or aerial
- Elevations are off (e.g., floors don’t match ground)
- Coordination sessions get stuck on “moving models” instead of solving design
- People start using phrases like “just shift it to match” (that’s a red flag)
Why this breaks BIM so often
Geolocation fails for three predictable reasons:
1) Nobody owns it
If there isn’t a named person/team responsible for setting and distributing the coordinates, everyone “does their best” and the project drifts.
2) Survey and design datums get mixed up
You can have multiple coordinate references in play:
- survey control
- design grid
- construction setout
- GIS / asset coordinates
If these aren’t clearly declared and mapped, models will never quite agree in the BIM federation environment.
3) Teams use different tools and workflows
Civil, architecture, structure, and building services often use different platforms. Even within Revit, small differences in how teams handle project base points / shared coordinates can cause big alignment headaches.
The real cost (what it does to programme + risk)
When geolocation is wrong, you pay for it in:
- rework (models remade or remodelled)
- coordination churn (clashes that aren’t real)
- delayed issue packs (because the set is never “settled”)
- site risk (incorrect setout assumptions, confusion between drawings and model)
Even worse: teams lose trust in the model and revert to PDFs and screenshots — which defeats the point of BIM.
A simple way to avoid it (a checklist that works)
You don’t need a PhD in BIM. You need a clear decision and a repeatable process.
Step 1 — Decide the coordinate “truth”
Pick the authoritative reference:
- Survey control (common for infrastructure and existing sites), or
- Design grid (sometimes used early for buildings)
Write it down. Put it in the BEP / project notes.
Step 2 — Nominate an owner
One person/team owns geolocation. They:
- publish the coordinate info
- confirm updates
- verify incoming models are aligned
Step 3 — Distribute a “starter pack”
At minimum:
- a control point / benchmark description
- orientation (true north vs project north)
- base file(s) (survey, civil surface, or agreed reference model)
- one-page “how to link without breaking it” notes for each discipline
Step 4 — Verify early (not at the end)
Do a quick federation check as soon as each discipline has a first model:
- confirm alignment
- confirm elevation
- confirm orientation
- confirm units
Catching this in week 1 saves weeks later.
Step 5 — Lock it before coordination ramps up
Once agreed, treat coordinates as “controlled.” Changes happen only with:
- a clear reason
- a communicated update
- a re-check of all linked models
Common trap: “Just move it until it matches”
This creates a false sense of alignment. You can make the models overlay visually while quietly breaking:
- levels
- rotations
- exported coordinates
- downstream drawing references
If you hear “just shift it,” pause and ask: “What’s the authoritative reference?”
When you should bring in help
If any of these are true, it’s worth getting a specialist involved early:
- multiple organisations + multiple platforms
- scan-to-BIM / as-built work
- civil + building integration
- strict deliverables / standards requirements
- repeated “model is in the wrong place” issues
If your project is losing time to “moving models around,” send your situation — I’ll tell you the simplest way to establish a stable coordinate approach and stop the churn.
https://baumass.co.nz/contact
Next steps for your project
If you want this solved without drama, focus on:
- Coordinate truth
- Named owner
- Early federation check
- Controlled changes
That’s it.
Need a practical geolocation setup that works across disciplines and tools? Send your situation and I’ll help you stabilise it quickly.
https://baumass.co.nz/get-in-touch
Related services:
Authored by Gideon Botes, Baumass DE — 22+ years in electrical design, drafting, BIM & DE leadership (11+ years substation design, Africa & New Zealand), former BIM Manager/CAD Team Leader. Specialising in capability building for New Zealand and Australian electrical/infrastructure teams. Learn more about my background.