Problem Statement

When a trip remains active on the driver app but has already been force-ended on ETS, offline events (e.g., over-speeding alerts) captured on the device continue to sync with ETS.

• These events get associated with the trip in SD and reports.

• This causes confusion, since the event timestamps are later than the trip end time.

Solution

To prevent post-trip events from being recorded against a force-ended trip:

1. Server Changes (ETS)

   • When ETS receives any trip data from the device after the trip has been force-ended, ETS will send a command to delete all trip and duty data on the device.

2. App Changes (Driver App v6.3.0+)

   • On receiving this command, the driver app will:

     • Gracefully delete all trip and duty related data.

     • Land the driver on the Off Duty screen.

This ensures that no events/alerts are logged against a trip once it is force-ended on the server.

Additional Notes

• Exclusion: This functionality is not supported for Adhoc trips.

• Configurable Property:

  • A message/audio can be played to notify the driver when the trip is force-ended by the server:

    • AUDIO_ALERT_ON_FORCE_TRIP_END_BY_SERVER_COMMAND

Driver App Version: v6.3.0 or above