The routing engine and dispatch console that run your operation.
AutoNav 2000 replaces fragmented routing tools, paper logs, and brittle spreadsheets with one operations layer. Buyers at 1,847 fleets see an average of 18.4% fewer planned route miles and a measurable drop in dispatcher overhead — verified across 312 audited deployments in 2024.
Five surfaces. One operations layer.
Every surface shares the same routing graph, the same dispatch state, and the same audit trail — so a route change in the engine is visible to the driver in the cab and to the analyst in the dashboard within seconds. The five surfaces below are the operational core procurement evaluators map to their existing tool stack.
-
01
Routing Engine
A constraint-based optimizer that ingests orders, vehicle specs, driver hours-of-service, traffic, and customer windows — and returns a feasible, costed plan in under 180ms p95. In-house team led by two former Google Maps and HERE Technologies principal engineers.
-
02
Dispatch Console
A control-room surface for dispatch leads — exception-first queues, drag-to-reassign, live ETAs, and one-click re-optimization when reality drifts from the plan. Designed for shift-long operator comfort on a 27" or larger monitor.
-
03
Telematics Integrations
Native, two-way connectors to 42 telematics and ELD providers — Geotab, Samsara, Verizon Connect, Lytx and more — live in under 48 hours. Vehicle position, fault codes, and HOS flow back into the routing engine automatically.
-
04
Driver App
A minimal, offline-tolerant Android and iOS app for the cab — turn-by-turn, manifest sync, proof-of-delivery capture, and exception reporting. Drivers spend less time fighting the app and more time driving.
-
05
Analytics
Auditable outcome reporting — planned vs. actual miles, on-time performance by depot, exception Pareto, and per-customer cost-to-serve. Every number ties back to a decision ID in the routing engine, so finance and ops speak the same language.
The numbers behind the console.
Every figure below is a single-source-of-truth fact a technical evaluator can verify — against our public status page, the G2 review record, the Frost & Sullivan benchmark study, or a SOC 2 audit report.
42 integrations, live in under 48 hours.
A working manifest of named connectors — not decorative logos. If your existing telematics, ELD, TMS, or fuel-card stack appears below, the integration is already shipped and supported in production.
What happens to our dispatch data, telematics history, and driver workflows on day one?
This is the question that determines whether a procurement evaluation becomes a six-month stall or a 30-day close. The short version: your data stays yours, the migration runs in parallel with your current tool, and drivers keep doing what they were already doing until you cut over — not a minute before.
Data residency and ownership
Every byte you load into AutoNav 2000 is yours to export, in full, at any point in the contract — including after termination, with a 60-day read-only window. US customers default to our Chicago region; EU customers can elect full data residency in either Frankfurt or Dublin, with GDPR-compliant processing and a published sub-processor list. We are ISO 27001 certified since 2022 and renew SOC 2 Type II annually.
Parallel-run migration
No customer has been asked to cut over on day one since 2017. The default rollout is a 30-day parallel run: AutoNav 2000 plans and dispatches against the same orders as your existing system, the dispatch lead reconciles both plans side-by-side, and we cut over when the new plans match or beat the old ones on the metrics you care about. Telematics history imports as a one-time job via the existing provider's API — typically overnight, with a reconciliation report on the morning of go-live.
Switching cost and contractual posture
Standard contracts are annual with a 90-day out clause for the first year — if the platform hasn't earned its seat by the end of Q1, you can leave for a pro-rated refund. Average payback period across our customer base is 4.3 months, per the Frost & Sullivan benchmark study (Q3 2024). The demo is the right place to walk through your specific stack — book 30 minutes and we'll show you the connectors live, on your data.
Before and after AutoNav 2000.
The fragmented baseline below is what we most often replace: a planning spreadsheet, two or three disconnected point tools, paper driver logs, and an after-the-fact BI dashboard that no one on the dispatch floor trusts. The right column lists the AutoNav 2000 state with the audited metric that maps to each failure mode.
Spreadsheets, paper logs, point tools.
- Route planning Manual spreadsheet optimization run once overnight; stale by 10 a.m.
- Dispatch desk Two monitors, four browser tabs, a printed manifest binder, and a group chat for exceptions.
- Telematics data One-way export from the ELD provider; never reaches the routing plan.
- Driver comms Phone calls and paper manifest updates; POD photos live on the driver's phone until end-of-day.
- Outcome reporting Monthly BI pull nobody reconciles to actual route decisions.
One operations layer, end-to-end.
- Route planning −18.4% planned miles vs. baseline, audited across 312 deployments in 2024.
- Dispatch desk Exception-first console, drag-to-reassign, one-click re-plan; ~30% dispatcher overhead reduction reported across mid-market customers.
- Telematics data 42 native, bi-directional integrations; live in under 48 hours.
- Driver comms Offline-tolerant Driver App on Android & iOS; POD captured and reconciled in real time.
- Outcome reporting Decision-level provenance — every number ties back to a routing decision ID.