How is the vehicle's timeline movement summary computed?

How is the vehicle's timeline movement summary computed?

Vehicle timeline movement summary is not updated in real time (as done in case of vehicle location and motion status).

The movement summary is updated at a minute level interval to determine the motion status of the vehicle for a given minute interval.


The platform can take up to two minutes to update the vehicle timeline movement summary.

So, in worst case scenario, if the user checks the vehicle timeline at 10:00 AM, they’ll be able to see the movement summary details upto 9:58 AM.

Eg:

If a user wants to check the vehicle movement summary for a 5 minute interval from 10:00 AM till 10:05 AM, the system will break down the given time period into 1 minute intervals and checks the motion status for each minute

At the end, the system will summarise the data to present the movement summary


Device data ping frequency

For better accuracy as well as to optimise the device battery utilisation, the following data ping frequency is configured in general for most devices:

  • Device will send data packets at every 10 second interval when the vehicle is MOVING

  • Device will send data packets at every 5 minute interval when the vehicle is STOPPED

Note:

This is not always be true for all devices as the Frequency at which the device sends data to the platform can be configured at device level.


Identifying MOVING or STOPPED motion status

If the vehicle has travelled more than 50 meters in the given 1 minute interval (all data packets in device gps time increasing order) then the vehicle is considered as MOVING for that given time period

If the vehicle doesn’t travel more than 50 meters in the given 1 minute interval, then the vehicle is considered as STOPPED for that given time period.

Haversine distance is computed between all the data packets received in the time interval

Identifying IDLING motion status

If we continuously receive data packets from device such that the vehicle has STOPPED while the IGNITION has been ON for more than Idling Threshold duration (10 mins), we would update the motion status as IDLING

Identifying OFFLINE motion status

Case 1: When the Vehicle is MOVING

If we get no data packet in one minute, while the vehicle is MOVING, then the vehicle motion status is considered as DEVICE OFFLINE for that given time period.


Case 2: When the Vehicle is STOPPED

If we get no data packet from the device as per the defined STOPPED data ping frequency of the device, we’ll consider the motion status DEVICE OFFLINE for the given time duration

For eg: Incase of STOPPED, the device sends data packet at every 5 minute interval (in general). If in case, we don’t get the data packet at the 5th minute interval, we’ll consider the motion status to be DEVICE OFFLINE

Haversine distance between all data points reported based increasing order of gps time during the selected time, as long as vehicle is moving


When the vehicle is stopped, the distance traveled in that minute (due to gps drift or noise) is not included in the overall distance calculation



    • Related Articles

    • How is the vehicle's real time motion status computed?

      Motion Status provides clarity with regards to the vehicle’s movement summary for a given time period. For a vehicle with an active device, the system has 5 different motion status defined, as mentioned below: Moving Stopped Idling Device Offline Low ...

    • Immobilise a Vehicle

      Q. How to Immobilise and mobilise a vehicle on the website? Watch How to Immobilise a Vehicle on web app Q. How to Immobilise and Mobilise a Vehicle (for APP)Watch How to Immobilise a Vehicle on the Mobile APP