The Fatigue Driving rule is a crucial feature of the telematics platform that utilizes tracker cameras to detect and alert dispatch in case of driver fatigue. Timely identification of driver fatigue is vital for accident prevention, reducing losses, and ensuring employee well-being. By analyzing various parameters and utilizing tracker cameras, tracker-camera systems can detect signs of drowsiness or fatigue in drivers. Once detected, an alert is sent to the dispatch, enabling prompt action to address the situation, such as arranging rest breaks or providing necessary support. Implementing the Fatigue Driving rule with tracker cameras enhances road safety, protects drivers' health, and promotes responsible driving practices.
Whenever the event is generated from the device side and sent towards the platform, it gets indicated via user interface alerts, email or SMS.
As this rule is based on hardware configuration, there is not much to configure in the rule itself.
Fill out the section if the rule needs to work only inside/outside of the selected geofences.
Bind zone to rule:
Enables geofence rule binding.
Shows bound geofences on the map.
The platform specifics
- The "Fatigue driving" alert has a 5-second reset timer, meaning the alert event will not occur more often than once every 5 seconds. If this type of event occurs in time the rule has been waiting for the reset, this event will be omitted by the platform, including the reports.
- In this rule type, users have the flexibility to select multiple trackers which they wish to receive notifications from. The only requirement is that the selected trackers must support Fatigue driving events and the feature must be integrated on the platform for given trackers. This means that users can choose multiple compatible trackers to receive notifications from, allowing them to monitor harsh driving events across various vehicles or devices in a convenient way.
- Whenever the platform identifies a hardware event of this type from a packet of tracker data with no valid coordinates in it, the platform counts the event as a valid one and displays it regardless of whether the event occurred within or outside the bound geofences. The logic of the Inside/Outside radio buttons is also ignored in this case. This behaviour is due to the fact that showing a controversial event once more is better than omitting it.
is used for important events. A message on the screen and the sound signal can only be disabled by clicking on the notification. Please note, some browsers can block notification sound until user activity is recorded on the page.
Receive push notifications on the mobile app and web interface.
Add geofence name to the notification:
Adds names of the specified geofences to the notification text. This option is available only when the "Inside" geofence binding radio button is selected on the "Settings" tab.
List of recipients for SMS notifications when the event occurs.
List of recipients for email notifications when the event occurs.
Set a schedule for when the rule will run. If your schedule indicates that the event should not run some day or time period, it will not appear as a notification in the user interface, and notifications via SMS or email will not be sent. Additionally, you can choose a default template for quick scheduling.
To view the dates when the events were received, you can build the "Report on all events" report.