Description
Advanced Driver Assistance System (hereinafter ADAS) helps drivers to be more focused on the road. ADAS is typically integrated into a vehicle's hardware and equipment as an embedded system. But we will review a case where trackers are the foundation and primary source for this functionality, meaning the event is generated on the tracker side, and is passed to the platform as a ready event to be displayed as a notification or counted in reports.
This kind of system usually facilitates complex algorithms and artificial intelligence. It monitors and analyses the video signal for dangerous and undesirable events.
The platform will alert if it detects any of the following events:
- Lane Departure Warning
- Forward Collision Warning
- Headway Monitoring Warning
- Peds in danger zone
- Peds Collision Warning
- Traffic sign recognition
The above-mentioned event tracking allows for monitoring the driver's rest, their traffic violations, aggressive driving, or simply unpleasant situations on the roads. This helps to reduce the risk of accidents, control and improve drivers' qualifications, and consequently decrease the risks of rule violations within the provided service or work. It also helps to anticipate unforeseen expenses related to fines and vehicle maintenance.
Settings
As the events are generated on the tracker side, the settings of this rule type are simple. Just select the needed events.
Geofence:
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.
Map button:
Shows bound geofences on the map.
The platform specifics
- The "ADAS" alert has no reset timer, meaning the alert event will occur every time an ADAS event comes in. This is different in comparison to many other rules of the platform which have the reset timer.
- 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 ADAS 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.
Notifications
Emergency notification:
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.
Push notifications:
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.
SMS notifications:
List of recipients for SMS notifications when the event occurs.
Email notifications:
List of recipients for email notifications when the event occurs.
Schedule
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.
Event reports
To view the dates when the events were received, you can build the "Report on all events" report.
