Definition / Description
The Driver Swipe Missing alert is triggered when a vehicle begins its journey without the driver scanning their RFID or iButton card at the start of the trip. The system checks for the driver’s authentication within a predefined time (default 120 seconds). If the card is not detected within this duration, the alert is generated. This helps fleet managers ensure accountability, prevent unauthorized driving, and maintain accurate driver-trip association.
How to Configure
- Select the relevant Company and Branch.
- Under Based On, choose Object, Object Type or Object Group.
- Select the Object for which the alert should apply.
- Enter an Alert Name (e.g., “Driver Swipe Missing”).
- From the Alert Type dropdown, select Driver Swipe Missing.
- Set the Duration (default: 120 seconds).
- In the Text field, enter a descriptive message such as “Driver swipe missing – card not detected.”
- Configure Valid Day(s):
- Everyday – for all days.
-
- Custom – select specific days as needed.
- Set Valid Time From / To (e.g., 00:00 to 23:59).
- Select the Timezone.
- Set the Severity Level – Low, Medium, or High.
- Choose the Action to be taken when the alert is triggered: SMS, Email, Notification, Buzzer or Immobilize
- Click Save to complete the configuration.
Example / Use Case
A Driver Swipe Missing alert is triggered when a vehicle starts moving, but the driver has not scanned their card within the configured duration (e.g., 120 seconds). This ensures that every trip is logged under an authenticated driver, enhancing safety, accountability, and compliance.
When Based On: Object, Object Group, or Object Type
- Object: Select individual vehicles where driver authentication is required.
- Object Group: Apply the alert to a group of vehicles equipped with driver identification devices.
- Object Type: Apply the alert to a vehicle type category that supports driver card scanning.
Action: The selected notification or action must be configured. (eg., SMS, Email, Notification, Buzzer or Immobilize).
- SMS: SMS is supposed to be configured while creating an Admin, Reseller or a Company’s account. After which you can add the number for whom you want to send the notification of an alert.
- Email: Email is supposed to be configured while creating an Admin, Reseller or a Company’s account. You can enter the email addresses for whom you want to send the alert notification via email.
- In-App Notification: You can select the Sound of the notification and Users who you want to receive the alert notification.
- Buzzer: For the buzzer to ring, a sensor connection must be established while adding an Object.
- Immobilize: In order to immobilize the object, when this alert is triggered it is important to enable the checkbox of Immobilization while creating an Admin, Reseller or a Company’s account and an Immobilization sensor attachment is also required, which can be done while adding an Object.
- Queue: The wait time after the alert triggered it will immobilize the vehicle.
Eg: When the vehicle gets out of the geofence, the queue is the duration for which immobilize command will be sent, until it is executed.