Fleet Telematics Bounty
Challenge · Hosted by Hauler. Every fleet we onboard arrives with its telematics in its own shape: mismatched field names, position gaps, counters that reset.
About this open call
What this event is about
Telematics from customer fleets arrives with mismatched field names, hours-long reporting gaps and odometer and fuel readings that disagree with the fuel card. This bounty pays for tooling that normalises and validates a feed before anything downstream is allowed to read it.
What we are looking for
Small data-engineering teams with working code that maps, gap-fills and validates vehicle telemetry from more than one vendor.
Problem statements
Every vendor names it differently
Engine hours, fuel level and ignition state arrive under a different name and a different unit from each telematics box, and the mapping is written by hand per fleet. That hand-written mapping is where most of an onboarding goes, and it breaks quietly the next time a vendor renames a field.
Gaps that read as idling
A vehicle that stops reporting for an hour looks, further down the pipeline, exactly like a vehicle standing still. Distance and fuel get attributed to the wrong leg, and the figure we quote for that lane is wrong in a direction nobody can predict.
Readings that disagree with the pump
Fuel level off the vehicle bus, an odometer that resets after a service, and litres on the fuel card rarely tell the same story for one week of running. We want the disagreement caught and reconciled before it reaches a report a customer reads.
Evaluation criteria
100% weighted total
Timeline
- Jun 22, 2026
Bounty opens
Sample exports from three telematics vendors published alongside the entry form.
- Jul 20, 2026
First fixes accepted
Two entries paid on gap-filling; the field-mapping and fuel-reconciliation problems stayed open.
- Aug 1, 2026
Replay round under way
Entries arriving now are run against a month of our own feeds and scored as they land.
- Oct 21, 2026
Remaining bounties awarded
Accepted fixes are paid and go into the ingest path every fleet is loaded through.
Sponsors & partners
Hauler
Host
Plug and Play
Programme partner
FAQs
Do we get real feeds to work on?
Yes — a month of exports from three vendors, with the gaps, resets and disagreeing readings left in. Nothing in them identifies a driver or a customer.
How is a bounty paid?
Per accepted fix, once your code has run over our own feeds and done better than the mapping we wrote by hand for that vendor. Several entries can be paid out of the same pool.
Does the entry have to be a product?
No. A library, a set of validators or a service all count, provided we can run it ourselves and read back what it flagged and why.
Take part
Submit your entry before the deadline. Every entry is scored against the criteria above.