20/05/2026
Behind the scenes: how we build InteliFleet.
Fleet tracking sounds simple on a slide — dots moving on a map. In practice, building it for industrial sites is a different conversation. Here's how our engineering team thinks about it.
1. Design for the worst signal, not the best.
A fleet platform that only works on clean highways is not a fleet platform. We design for plant gates, weighbridge queues, underground bays, and zones where GPS drops for minutes at a time. Dead-reckoning logic, last-known-state handling, and replay-on-reconnect are baseline expectations, not features.
2. Geofencing is a data model, not a polygon.
Operationally, a geofence is tied to a process — loading bay entry, dispatch gate exit, restricted zone breach. So we model fences as event sources with owners, escalation paths, and audit trails. The map shape is the last 10% of the work.
3. ETA is a promise, so we treat it like one.
Driver analytics, route adherence, halt patterns, and historical segment times all feed ETA. We review the model against actuals, not against itself. If the dashboard says 40 minutes and the truck takes 70, that is a defect, not a forecast.
4. Dashboards are designed for the control room, not the demo.
Our review practice: every screen has to answer one operational question in under five seconds. If a control room operator has to click twice to find out which vehicles are overdue, the screen is wrong.
5. Integration is where projects live or die.
Weighbridge systems, dispatch software, SAP, gate access, fuel management — InteliFleet rarely lives alone. We design APIs and data contracts on day one, not at UAT.
6. Scale is a constraint, not a marketing line.
Our platforms are built for large-scale industrial deployments — thousands of vehicles, sensors, and transactions. That shapes choices in database partitioning, message queues, and how we handle telemetry bursts at shift change.
What we deliberately avoid:
- Features that look good in a pilot but break at fleet-wide rollout.
- Alerts that train operators to ignore alerts.
- Reports nobody opens after week two.
InteliFleet is part of a wider stack — InteliTrack, InteliRide, InteliSafety, InteliAssets — and the same engineering principles apply across all of them. Build for the site, not the slide.
If you run an industrial or government fleet and want to compare notes on what actually works in the field, we are happy to talk.