Fleet software that turns telematics into a decision
Samsara or Geotab already tells you where every truck is. The harder question is what each one cost you this month, and your dashboard was never built to answer it.
What fleet operators are actually buying
5 things that decide this
- 01A telematics feed is raw material, not an answer. Samsara and Geotab report GPS pings and engine codes; turning that into cost per asset is a separate build most fleets never get to.
- 02ELD compliance is a floor, not a strategy. The mandate forces hours-of-service logging, but it says nothing about fuel burn, idle time or which truck is quietly losing money.
- 03Maintenance stays reactive because the data that would make it predictive sits in three systems that do not talk: the ELD, the fuel card, and a spreadsheet someone updates on Fridays.
- 04The fleet manager's real question is which asset to replace next, and no off-the-shelf dashboard ranks trucks by total cost of ownership.
- 05Your telematics provider stays the sensor layer. New software should sit on top of it and answer the cost and maintenance questions it was never built for.
The API gives you data. Nobody built the math
Samsara and Geotab both expose solid APIs. Location, fuel level, engine fault codes, hours of service, all available in near real time. Most fleets stop there, because pulling the feed is the easy 80% and the last 20% is where the value actually sits.
Cost per asset is not a field the telematics vendor sends you. It comes from a fuel card, a maintenance invoice, a lease payment and the ELD's mileage log. Each system spells the vehicle ID differently. Nobody builds that join, so the manager estimates instead.
The fix is to treat the telematics feed as an input, not the product. Pull it in alongside fuel, maintenance and lease data, and key everything to one asset record. Then the report can answer which truck to replace next instead of stopping at where it is right now.
- 01Key every data source to one canonical asset ID, not the ID each vendor happens to use.
- 02Store fault codes and maintenance history against the asset, not the work order alone.
- 03Separate idle time from downtime. They cost differently and get fixed differently.
- StreamSamsara or Geotab pushes the raw feed.
- MatchFault code joined to this asset's history.
- CostFuel, maintenance and lease added in.
- FlagThis truck costs more than its replacement.
- ActA work order or a retirement decision, logged.
A telematics dashboard stops at step one. Cost per asset needs every step after it.
What a fleet build actually has to solve
Telematics integration that survives a provider switch
Samsara and Geotab APIs each have their own asset model, and a fleet that mixes providers across depots needs one internal schema both feeds map onto. Build to the schema, not to either vendor's shape.
ELD data that satisfies the mandate and feeds the report
Hours-of-service logs exist for compliance, but the same timestamps show which routes run long and which drivers hit the same delay every week. One capture, two uses.
Cost per asset, joined across four systems
Fuel card, maintenance invoice, lease payment and mileage rarely share a key. We build the asset record that ties them together, so total cost of ownership is a query instead of a spreadsheet.
Maintenance that moves ahead of the breakdown
Fault codes and usage patterns flag a likely failure before it strands a load. TankAware runs this pattern on petroleum sites: predictive alerts on IoT data, tied to a work order with an owner.
A fault code is a fact. A repair decision is judgment
Most fleet dashboards stop at the alert. A fault code fires, a light turns red, someone gets a notification. What it does not say: is this the third fault on a truck due for retirement, or the first fault on one with years left?
That judgment needs history: every prior fault, every repair cost, every day the truck sat idle waiting on a part. Most fleets have that history scattered across a maintenance shop's system, a fuel card portal and the telematics dashboard, none of which reference each other.
TankAware solves the same shape of problem on petroleum sites. It flags an anomaly against a site's own history, not a fleet-wide average, and turns the flag into a work order with an owner. A fleet build needs that same discipline, aimed at an asset instead of a tank.
- Compare a new fault against this asset's own repair history, not a fleet average.
- Turn a flagged fault into an assigned work order, never a dashboard badge alone.
- Track whether a repair actually resolved the underlying pattern or just the symptom.
Sensor-to-decision systems we have shipped
The stack behind fleet and telematics work
Integrations
Platform
Controls
What fleet operators ask us first
01Can you integrate with Samsara or Geotab?
Yes. Both expose APIs for location, fuel, engine faults and hours-of-service data. The integration work maps each provider's asset model onto one internal schema, so a fleet running both is not maintaining two separate reports.
02How do you turn telematics data into cost per asset?
By joining the telematics feed to fuel card, maintenance and lease data against one canonical asset ID. Most fleets never build that join, so cost per asset stays a spreadsheet estimate instead of a live number.
03Does this replace our ELD or telematics provider?
No. Samsara and Geotab stay the sensor layer, capturing location and engine data. We build the reporting and decision layer on top: cost, maintenance history and predictive alerts, connected by API.
04Can predictive maintenance actually predict a breakdown?
It can flag a deviation from an asset's own pattern early enough to schedule a repair. That is narrower than predicting an exact failure date, and more honest. TankAware runs this pattern on IoT sensor data across remote sites, comparing each site against its own baseline rather than a fleet-wide average.
05What does a first piece of work with you look like?
Scoping calls cost nothing. Bring the report you wish existed: cost per asset, a maintenance backlog ranked by risk, or one dashboard that replaces three spreadsheets. Going into your existing telematics setup to answer it precisely is a paid two-week diagnostic, and it ends in a fixed price.
