Overview#
Dispatchers and fleet managers need to know where their vehicles are, not where they were five minutes ago. The Telemetry Providers module connects to major fleet and emergency services telemetry platforms, pulling GPS positions, engine diagnostics, fault codes, and fuel data into a single monitoring interface that stays current regardless of which provider each vehicle reports to.
This is particularly relevant for public safety agencies running mixed fleets across multiple vendors, and for EMS and fire departments where vehicle readiness directly affects response capability.
Key Features#
-
Multi-Provider Support: Connect to Samsara, Geotab, ZOLL Data, Tyler NewWorld, 10-8 Systems, and AngelTrack simultaneously. Each provider is configured independently with its own sync schedule and data preferences.
-
Vehicle Mapping: Map provider vehicles to internal units using automated matching algorithms (VIN-based, name similarity) with confidence scoring. Manual mapping handles vehicles that cannot be auto-matched, and mappings update as fleet composition changes.
-
Real-Time Telemetry Monitoring: Track vehicle positions, speed, fuel levels, engine status, odometer readings, and diagnostic data with freshness indicators showing whether data is current (under 30 seconds), stale (30 seconds to 5 minutes), or offline (over 5 minutes).
-
Fault Management: Track and manage vehicle diagnostic trouble codes with severity classification (critical, warning, informational). Acknowledge faults with notes, dismiss false positives, track resolution progress, and export fault reports for fleet maintenance planning.
-
Flexible Sync Options: Configure automatic sync at intervals from 5 to 300 seconds, trigger manual on-demand syncs, or use real-time streaming where supported. Monitor sync status including success rates, error counts, and data freshness across your fleet.
-
Fleet Health Dashboard: Visual overview showing provider status, total mapped vehicles, data freshness distribution, and active fault counts. Quickly identify connectivity issues and vehicles requiring attention before they affect operational readiness.
Supported Providers#
| Provider | Primary Use | Key Capabilities |
|---|---|---|
| Samsara | Enterprise Fleet | GPS, fuel, diagnostics, driver safety, reverse geocoding |
| Geotab | Fleet Management | GPS, EV data, trips, faults, battery health |
| ZOLL Data | EMS | EMS metrics, dispatch integration, fleet status |
| Tyler NewWorld | Public Safety | AVL, CAD integration, multi-agency support |
| 10-8 Systems | Emergency Services | Police, Fire, EMS AVL tracking |
| AngelTrack | EMS/Fire | CAD integration, multi-provider support |
Use Cases#
- Law enforcement agencies tracking patrol vehicle positions in real time across a mixed fleet reporting to different telemetry providers.
- Emergency medical services monitoring ambulance readiness, fuel levels, and fault codes before shift changes to prevent in-service failures.
- Fire departments integrating multiple CAD systems and telemetry providers into a single operational picture for dispatch optimisation.
- Critical infrastructure operators with large mixed vehicle fleets managing predictive maintenance through centralised fault tracking.
Open Standards#
- SAE J1939: Heavy-vehicle serial bus diagnostic standard whose fault codes (Suspect Parameter Numbers and Failure Mode Identifiers) are ingested and normalised from Samsara and Geotab feeds into the unified fault store.
- OBD-II / SAE J1979 (ISO 15031): On-board diagnostics standard for light and medium vehicles; Diagnostic Trouble Codes sourced from OBD-II channels are parsed, severity-classified, and surfaced alongside J1939 faults.
- ISO 8601: Date and time representation standard used consistently across all provider adapters for timestamp parsing and storage of position and fault records.
- OAuth 2.0 (RFC 6749): Authorisation framework used by provider adapters that require token-based authentication (such as Tyler NewWorld CAD) to obtain and refresh bearer tokens before each API session.
- ISO 3779 (VIN): Vehicle Identification Number standard underpinning the automated VIN-based matching algorithm that maps provider vehicles to internal fleet units.
- OAuth 2.0 and JWT Bearer Token: Token-based authentication protects typed, auditable read and write workflows across the platform.
- WebSocket (RFC 6455): Full-duplex protocol used to broadcast real-time telemetry position updates and fault alerts to PSAP and fleet health dashboards as data arrives from providers.
Getting Started#
- Add Provider: Select your telemetry provider and enter service credentials and configuration settings.
- Test Connection: Validate connectivity, authentication, and data access before enabling the integration.
- Map Vehicles: Review auto-match suggestions and manually map any remaining vehicles to internal units.
- Configure Sync: Set appropriate sync intervals based on operational needs and provider capabilities.
- Monitor Fleet: Use the fleet health dashboard to track telemetry freshness, faults, and provider status.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14