Related Articles
Here's a scenario that plays out in multi-depot fleet operations more often than most people want to admit: the board asks for a performance comparison across depots. The operations director asks each depot manager for their numbers. Each depot manager sends a spreadsheet. The spreadsheets are formatted differently, use different metrics as proxies for the same KPIs, and cover different time periods because each depot runs its own reporting cycle. Three weeks later, the board gets a summary that nobody is confident in.
Depot data silos aren't usually the result of bad decisions. They develop over time as each depot optimises locally for its own operational context. A depot acquired through acquisition comes with its own fleet management system. A depot that's been running since the 1990s has processes built around the system that was current in 2008. A newer depot has adopted whatever the central IT team was deploying that year, which may or may not integrate with what came before.
The result is a situation where the same operational concept -- say, "vehicle utilisation rate" -- means different things in different systems. One depot measures utilisation as hours on road per shift. Another measures it as miles per available vehicle per week. A third doesn't track it formally at all; the depot manager keeps a mental model based on experience.
None of this is wrong at the depot level. Each approach may be perfectly suited to the way that depot operates. The problem emerges at the organisational level, when you need to make decisions that require comparing across depots -- decisions like where to allocate spare vehicles, which depot to invest in first, or where the cost reduction opportunity is largest.
When depot data can't be meaningfully compared, the organisation falls back on proxies. Finance looks at cost per site. Operations looks at complaints and breakdowns. Senior leadership looks at whichever depot manager makes the strongest case in the quarterly review.
This isn't catastrophic -- many businesses run this way for years. But it represents a systematic failure to allocate resources to where they'd have the highest impact. In our data, the fleets that move from silo-based to integrated depot reporting typically identify at least one significant reallocation opportunity within the first six months -- a depot that's materially underperforming relative to comparable sites, or a vehicle pool that's undersized for the work it's actually doing.
The cost of not knowing this isn't visible on any report. It shows up as performance that's lower than it should be, across the board, year after year.
"You can't manage what you can't compare. And you can't compare what's measured differently." — ExoFleets Team
The solution is not to mandate a single fleet management system across all depots -- that's a multi-year change programme with significant operational disruption and rarely worth the upheaval. The more practical approach is to build a master data layer that sits above the depot-level systems and normalises the data they produce.
That layer needs to:
The biggest mistake in depot integration projects is leading with the technology decision. Which platform? Which integration tool? Which cloud provider? Those questions matter, but they're the wrong starting point.
The right starting point is: what do we need to be able to compare across depots, and how do we define those metrics precisely enough that the definition is unambiguous in any system? That work -- which is essentially a data governance exercise -- typically takes two to four weeks with the right stakeholders in the room. It produces a metric dictionary that everyone agrees to before a single system is touched.
Once the definitions exist, the integration work has a clear specification. You're not building a general-purpose data aggregation system; you're building something that produces specific, agreed outputs from the data that already exists in your depot systems.
Once depot data is consolidated and comparable, several things become possible that weren't before. Vehicle rebalancing decisions become data-driven rather than negotiated. Depot-level performance reporting becomes consistent, which means depot managers are being measured on the same basis -- which changes conversations significantly. Maintenance cost variation across depots becomes visible, which often reveals that one or two depots are carrying disproportionate maintenance overhead for reasons that are fixable.
None of this requires new data sources. It requires making the data you already have speak the same language.
ExoFleets's Fleet Master Data Hub is designed specifically to integrate multi-depot data into a single, comparable view. Talk to our team about your depot structure.