AutoNav 2000 replaces fragmented routing tools, paper logs, and brittle spreadsheets with one platform that cuts average route miles by 18%, reduces dispatcher overhead, and ships with 42 telematics integrations out of the box. Built by fleet operators, running the dispatch desk for 1,847 fleets across North America and Europe.
AutoNav 2000 consolidates the three jobs that used to live in three tools: route optimization across multi-stop, multi-driver shifts; live dispatch automation with exception handling; and a single telematics + ELD integration surface. Each capability ships with named, measurable outcomes — not dashboards.
Plan morning and evening runs against live traffic, driver hours-of-service, vehicle capacity, and customer time windows in a single pass. The routing engine is built and maintained by a team led by two former Google Maps and HERE Technologies principal engineers — the same engine that processed 9.4 billion routing decisions in the trailing twelve months.
Auto-dispatch assigns the next best driver, fires playbooks on stalled runs and missed ETAs, and escalates only the exceptions that need a human. Dispatchers stop chasing spreadsheets and start running the desk — which is why our customers consistently reduce dispatcher headcount overhead in the first two quarters.
Native, bidirectional integrations with 42 telematics and ELD providers — including Geotab, Samsara, Verizon Connect, and Lytx — live in under 48 hours. No middleware, no CSV shuffling, no second vendor to reconcile. SOC 2 Type II certified since 2021, with full GDPR-compliant EU data residency in Frankfurt and Dublin.
AutoNav 2000 ships native, bidirectional connectors for the four anchor ELD and telematics platforms most fleets already operate, plus 38 more across fuel cards, TMS, WMS, payroll, and driver mobile. Connectors are maintained by our integration engineering team in Chicago and Frankfurt — no middleware, no Zapier chains, no nightly CSV drops.
Live in under 48 hours for the four anchor providers above. Full provider matrix with auth scopes and webhook contracts is published at /integrations.
The engine solves a constrained vehicle routing problem (CVRP) at the stop level — not the route level — pairing every stop's hard window, service time, and skill tag against the available vehicle and HOS clock. Departure sequence is recomputed every 90 seconds against live traffic and live order intake.
Customer receiving windows, dock-hour restrictions, urban low-emission zones, and HOS-mandated breaks are modeled as first-class constraints rather than penalties. Missed windows cost the engine objective score; the planner surfaces the cheapest feasible plan that hits every committed time.
Route plans are scored against projected paid hours, return-to-base mileage, and cubic-capacity utilization. The engine surfaces a load-balanced plan set so dispatchers can pick the variant that fits the fleet's actual labor budget — not the cheapest paper route.
Independent audit by Frost & Sullivan (Q3 2024) across 312 customer deployments. Baseline = each fleet's prior 90-day planned-route mileage on their previous planning tool. Result = an average 18.4% reduction in planned route mileage after 60 days on AutoNav 2000, with a 4.3-month average payback period.
Three operations directors, three measurable outcomes, and the trust strip our procurement teams get asked about most.
"We retired four planning tools and a 14-person nightly routing desk inside two quarters. Dispatchers now run exception management, not sequence planning. The mileage delta showed up in week three."
"The time-window modeling alone paid for the contract. We stopped missing receiver windows at Publix and Kroger, and our claims rate dropped 31% in the first cold chain."
"Samsara + Geotab data was inside our dispatch console by day two. The routing engine actually respects our technician skill tags, which is the first time a planning tool has done that without a manual override layer."
