Design a real-time freight visibility integration using ELD/telematics data, geofencing, and ETA recalculation

Steps

1. Ingest position pings from ELD or telematics providers (via their REST or streaming APIs) into a position-events stream; normalize fields to a common schema: asset_id, latitude, longitude, speed, heading, and UTC timestamp.
2. Define geofences for origin, destination, intermediate stops, and shipper-defined waypoints; evaluate each incoming position against all active geofences using a point-in-polygon algorithm, and emit ENTER/EXIT events with dwell time calculation.
3. Maintain a rolling actual-path record per shipment and compare cumulative distance and elapsed time against the scheduled route to detect deviations, extended dwell, or missed checkpoints.
4. Feed actual position, speed, and remaining distance into an ETA model — at minimum a distance/average-speed model, optionally augmented with historical lane performance data and live traffic APIs — and recompute ETA on each position update.
5. Publish ETA delta events (e.g., now expected N minutes late) to downstream consumers (TMS, customer notification service, dock scheduling system) only when the delta exceeds a configurable threshold to avoid notification fatigue.
6. Persist the full position history for each shipment to support post-delivery analytics, claims documentation (e.g., proving cold-chain breach location), and carrier performance benchmarking.