Aeion Fleet + Telematics Provider APIs
If you already have Samsara, Geotab, Verizon Connect, Motive, or other telematics hardware deployed across your fleet, ripping it out to switch to Aeion is unnecessary. Aeion Fleet integrates with telematics provider APIs to consume vehicle data — GPS, OBD-II diagnostics, driver behavior, ELD logs — without changing the underlying hardware. Per-provider integration, dual-system phase-out for gradual migration, or permanent hybrid where premium vehicles stay on legacy telematics and economy vehicles use ELM327 + Bridge.
Supported Telematics Providers
`
Setup Walkthrough — Samsara
```bash
Phase-Out Migration Strategy
`
Hybrid Hardware Strategy
`
FAQ
Samsara imports run as periodic Singularity jobs, not continuous streaming — schedule as often as your workflow needs. Other providers have no native adapter; freshness depends entirely on how you feed the generic telemetry-ingest endpoint.
The Samsara connector makes plain REST calls with no built-in rate-limit backoff or bulk-query batching today — keep import frequency reasonable for your fleet size.
Samsara's Vehicles/Drivers/Safety-Events fields map into Aeion's fleet_vehicles / fleet_drivers / fleet_alerts collections. Other providers have no built-in field mapping — that's on your integration.
There's no dedicated per-provider webhook receiver. The generic telemetry-ingest endpoint is a plain authenticated REST POST (batched, continue-on-error per reading) — it doesn't verify provider webhook signatures itself.
Aeion Fleet works with whatever data actually lands in its collections. If a provider's data isn't imported or mapped, that data simply isn't available to Aeion-native features.
Per-contract expiration timing. Per-fleet vehicle replacement schedule. Per-phase typical 6-18 months.
Per-vehicle ROI analysis. Per-vehicle hardware age. Per-vehicle replacement cost.
Per-fleet absolutely. Per-vehicle per-provider config. Per-Aeion unified view.
Per-tenant credentials encrypted at rest. Per-tenant API token rotation supported. Per-tenant zero-knowledge.
Per-Aeion-Fleet supersets legacy features. Per-vehicle Aeion native + provider hardware.
Samsara's Safety Events entity (harsh-braking/speeding/dashcam-alert type events) imports into fleet_alerts with timestamp, severity, and vehicle/driver reference — video clip playback isn't part of the current connector.
Per-Aeion driver app primary. Per-Samsara driver app can be deprecated. Per-driver one app instead of two.