Fleet And IoT¶

MYConnect treats fleet tracking as an operating layer, not a separate map product. Vehicle telemetry becomes more valuable when it is connected to jobs, depots, drivers, customers, geofences, exceptions, and support diagnostics.

Core Capabilities¶

• Device registry and provisioning.
• SIM, model, assignment, installation, and replacement records.
• HTTP telemetry ingest and raw diagnostics.
• Latest vehicle state and device health.
• Live map and vehicle status list.
• Trip replay by vehicle, driver, job, or time range.
• Geofences, utilization, alerts, and evaluator readiness.

Operational Uses¶

• Locate active vehicles quickly.
• See offline or no-data vehicles before customers complain.
• Replay completed trips during disputes.
• Link arrival, departure, and route evidence to a job timeline.
• Help owners understand utilization and idle assets.

flowchart LR
    Device["Device or mobile location"] --> Ingest["Telemetry ingest"]
    Ingest --> Normalize["Normalize payload"]
    Normalize --> Latest["Latest vehicle state"]
    Normalize --> Replay["Trip replay"]
    Latest --> Fleet["Fleet map and list"]
    Replay --> Job["Job timeline"]
    Latest --> Alerts["Geofence, idle, offline alerts"]

Current Build Proof¶

The current build has local route evidence for /devices, /fleet, and /fleet/live-map, including device operations, latest state, replay, geofences, utilization, alerts, tenant scope, and browser smoke evidence.