1

False Notifications of Idling and Parking

Topic: False Notifications of Idling and Parking

I've noticed in the past few weeks that the system does not collect information about online/offline status of the unit while generating a notification.

Its mean that the notification will be triggered irrespective of its status.

For example, unit went offline when its ignition was on at '0' speed, and remained offline till 15 minutes. In the above case, the system will trigger a notification that the unit is in idling state for the last 15 minutes. But in reality, it wasn't.

After that, unit comes online and upload all the black box messages to the server. Then we come to know that the unit was actually moving at the same time when the notification about 'Idle for 15 minutes" was triggered.

I know, the data will be correct in the reports but we are counting the number of notification triggers for collecting information. And the managers who are receiving mobile notifications through mobile app, they make quick decisions on the basis of the notifications they receive.

Same situation occurs in the parking notification.

So, is there any possibility to restrict the notification when the unit is offline/does not send any data for the specified time period to the server?

I think this issue must be resolved ASAP because it is giving false information to the users/managers.

I need your help to solve this issue.

Thank you

2

False Notifications of Idling and Parking

Re: False Notifications of Idling and Parking

Dear ifleet.pk,

what I say might contradict your vision, but I believe that notifications that are triggered in the cases that you describe are not false.

ifleet.pk wrote:

For example, unit went offline when its ignition was on at '0' speed, and remained offline till 15 minutes. In the above case, the system will trigger a notification that the unit is in idling state for the last 15 minutes. But in reality, it wasn't.

When we receive the first message with the ignition on and the 0 speed it is a trigger for us that idling has started and we start counting the number of minutes (or even hours) that are set as allowed for idle. Once we get a message with the speed > 0 until the max allowed idle time is reached, we interrupt this counting and no idling is recorded. Otherwise, when the max allowed time is reached and there is no message with the speed >0 or any message at all is received, we trigger a notification.

For the system in cases when it makes operations with the online data it is impossible to say whether there was no idling unless there are messages from the device that can support this fact. In your case there were no messages for 15 min and that's why the notification appeared.

---

You can also look at this issue from a different perspective: let's assume that there is a device that sends data each 15 min and the max allowed idle time is set for 10 min. In this case again the system will trigger a notification of idling as soon as it receives a message with the 0 speed and max allowed time reaching 10 min. However, the actual idling could have been only for 1 min, but we cannot know that for sure as receive messages that rare.

Maria Starikova,
Wialon Hosting Product manager, Gurtam