AutoNav 2000 connects natively to the telematics stack you already run — Geotab, Samsara, Verizon Connect, Lytx, and 38 more — so route optimization, dispatch automation, and HOS sync sit on top of the same data stream your shop floor already trusts. No middleware. No CSV exports. No rip-and-replace.
Every category below ships native — no middleware, no per-customer professional-services cycle. If your stack is on this list, AutoNav 2000 talks to it on day one.
Don’t see your vendor? Bring it to the demo — the in-house integration team ships two new connectors per quarter, and customer-requested connectors jump the queue.
Directory logos confirm coverage. These rows show the data flows behind them — the two-way sync that lets AutoNav run your dispatch desk instead of just visualizing it.
Engine diagnostics, fault codes, idling events, and zone entries flow into AutoNav in near real time. Outbound, we push planned stops, dispatch notes, and routing exceptions back to MyGeotab so drivers see a single source of truth in the cab. Geotab SDK & Add-In framework both supported.
Hours-of-service, vehicle assignment, and DVIR records stay synchronized with Samsara’s fleet manager so compliance reporting is automatic on both sides. Dashcam triggers (harsh brake, distracted driving) raise dispatch exceptions inside AutoNav within 800 ms.
Vehicle location, ignition state, and Verizon Connect’s custom form submissions (POD capture, condition codes) are mapped into AutoNav stop events. Route progress and ETA deltas post back to Reveal dashboards via our published webhook surface.
Lytx risk events (following distance, lane departure, distracted) generate AutoNav dispatch exceptions with the corresponding clip ID attached. Coaching workflows round-trip: a coaching assignment in AutoNav writes back to Lytx DriveCam so safety managers keep a single ledger.
The “under 48 hours” number is the median across the last 312 audited deployments. Here is exactly what the integration engineering team runs.
A solutions engineer sends a one-page OAuth or API-key request tailored to your provider. You sign in once; we never see the password. Median: 1h 20m.
~ 1 hourAutoNav ingests a sample of live telematics in a sandbox tenant. We validate vehicle IDs, geofence semantics, and HOS rule mapping against your existing schema. Median: 14 hours.
~ 14 hoursA 90-minute change window with your dispatcher live on a screen-share. We flip the data source, replay the last 24 hours of pings, and confirm parity. Median: 6 hours.
~ 6 hoursFor 14 days, the on-call integration engineer watches the connector’s health metrics (latency, error rate, event loss). Any deviation from your baseline triggers a same-day review. Median: 24 hours.
14-day tailPulled from the last 90 days of demos. If yours isn’t here, bring it to the call — we’ll bring the engineer who can answer it.
Yes. The platform ships a documented REST and webhook surface, and our in-house integration team will scope a custom connector on customer-funded timelines. Customer-requested connectors are also reviewed for the quarterly native release — eight of the current 42 started life as one-off builds.
AutoNav only writes back the data your ERP or WMS already accepts — typically orders, stops, and shipment status via REST or flat-file. We support SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365, and Manhattan Scale WMS natively; for everything else, our partner ecosystem includes certified middleware. No schema migrations on your side.
Yes. EU tenants run in Frankfurt or Dublin regions, and we contractually keep all routing decisions, HOS records, and telematics payloads inside the EEA. Cross-border calls to provider APIs are minimized to OAuth refreshes and are documented in our GDPR DPIA template, available under NDA.
Median customer cuts over in 6 weeks, including pilot. The data import tool handles historical stops, customer geocodes, and driver assignments from the major incumbents. More importantly: the integration layer is already connected to your telematics stack, so the longest part of the switch is usually the change-management conversation with your dispatchers, not the platform migration.
ISO 27001 since 2022, SOC 2 Type II renewed annually since 2021, GDPR-compliant EU residency in Frankfurt and Dublin. Our public status page carries 36 months of uptime history. Under NDA, we share the latest SOC 2 report, our penetration-test summary, and the integration-specific control matrix.
The first 15 minutes walk through a sample routing problem on your fleet’s actual telematics feed (no prep required on your side). The second 15 minutes is open Q&A with the solutions engineer, who is empowered to scope a 30-day paid pilot on the call if the fit looks right.
Ready to see your stack on the console?
Book a Live Demo