The Shape of the Terrain
A stripped-down map of the data universe every fleet runs on. Not the how-to. Just the lay of the land.
Every fleet operation runs on the same underlying data universe — whether they have mapped it or not. The systems are different. The names are different. The vendors are different. But the structure is the same: four domains, three altitudes, one spine running through all of it. Understanding that structure is the first step toward knowing where your numbers are breaking down — and where your margin is sneaking out the back door.
This is not the how-to. It is the lay of the land. The language you need before the work begins.
The Four Domains
Every piece of data in your fleet operation belongs to one of four domains. They are not software categories — they are questions your operation is always trying to answer.
Most fleet problems — the ones that show up as bad KPIs, unreliable dashboards, or margin you cannot account for — are domain-crossing problems. The maintenance domain is missing data the financial domain needs. The operational domain is generating facts the compliance domain never captures. The domains are supposed to talk to each other. When they do not, the numbers do not align.
The Three Altitudes
Within those four domains, every system in your operation sits at one of three altitudes. Think of it as a flow direction: data is born at the edge, used in the middle, and read at the top.
Most leaders are living at Altitude 3 — watching dashboards — while their Altitude 1 data is broken.
You cannot fix a broken Altitude 1 by improving your Altitude 3 reporting. The flow only goes one direction.
The Spine Connects All of It
The spine is the thread that runs through every domain and every altitude. It is the sequence that makes the whole system coherent — or breaks it.
Asset ID is the thread. Every fact in your data universe — a fuel transaction, a work order, an inspection record, a cost entry — needs to be tied to a unique asset ID to be useful. Without it, the domains are islands. And the dashboard at Altitude 3 is reading from disconnected pools, not a unified system.
What Breaks When the Map Is Wrong
Orphan Data
Facts that were captured but never connected. A fuel transaction with no asset ID. An inspection record that never made it into the CMMS. Data that exists but cannot be used — because it has no home in the spine.
Two-Owner Facts
The same data point maintained in two systems with no sync between them. Asset hours in the telematics system and asset hours in the CMMS — both slightly different, neither authoritative. When two systems own the same fact, it creates friction in your processes.
The Dashboard That Cannot Tell the Story
A clean-looking report built on broken inputs. The availability number looks fine — but it is calculated from work orders that were never closed. The cost per hour looks reasonable — but it is missing half the labour. The dashboard is telling a story the data does not support.
These Are Not Software Problems
They are architecture problems. The fix is not a new tool — it is knowing which system owns which fact, and making sure the handoffs are clean. That is what the map is for.
What This Points Toward
The full architecture maps every system in your operation to its domain and altitude. It names which facts each system owns — and which facts it borrows. It shows where the handoffs are supposed to happen, and where they typically break. It identifies the orphan data and the two-owner conflicts.
It is not a technology audit. It is a data ownership and connection map. And once you have it, the problems that looked like software problems or people problems start to look like what they actually are: architecture problems with known fixes. That is what Base Camp points toward. The build stays in the room — but the language is yours now.
You now speak the language. The next step is finding where your spine is broken — and building the data discipline to fix it at the source.
© 2026 Altitude Assets. All rights reserved. Base Camp™ and the Altitude Method™ are trademarks of Altitude Assets. This material may not be reproduced or redistributed without written permission.