Logic: Generated when the vehicle is stopped for more than a continuous time period as defined during alert subscription
Use Cases:
Track and manage vehicle stoppage times efficiently.
Monitor and optimize idling periods to reduce fuel consumption.
Logic: Triggered directly from the device in case of sudden acceleration based on pre-configured device setting
Use Cases:
Detect aggressive driving behavior
Promote safe and smooth driving practices.
Logic: Triggered directly from the device in case of sudden braking based on pre-configured device settings.
Use Cases:
Detect harsh braking events.
Monitor driver behavior and provide coaching for safer driving.
Use Cases:
Monitor and discourage aggressive or unsafe turning.
Reduce wear and tear on vehicles through smoother turns.
Logic: Triggered when someone presses the SOS button. Consideration time is typically 2 minutes.
Use Cases:
For emergency situations and immediate response.
Ensure the safety and security of drivers.
Logic: Generated when the vehicle's ignition is toggled based on specific ignition data packets
Use Cases:
Monitor unauthorized ignition events.
Prevent vehicle theft by receiving alerts when the ignition is turned on without authorization.
Logic: Generated based on an external power cut event code sent directly from the device.
Use Cases:
Detects and reports power cut incidents affecting the device.
Ensure continuous device operation and data transmission.
Logic: Generated when the vehicle battery voltage of the device is less than a device-defined threshold.
Use Cases:
Monitor the health of the device's internal battery.
Ensure uninterrupted device operation.
Logic: Generated when the device's battery voltage goes below the battery percentage limit defined by the user.
Use Cases:
Monitor and maintain device battery health.
Receive notifications to replace or recharge device batteries when necessary.
Use Cases:
- Detect accidents and collisions for immediate response.
- Enhance driver safety by alerting authorities in case of accidents.
Logic: Generated when the ignition is on, and the vehicle is stopped for more than a continuous time period as defined during alert subscription.
Use Cases:
Monitor idle times to optimize fuel efficiency.
Identify and reduce unnecessary idling to lower operational costs.
Logic: Triggered when the device sends an alarm directly in response to a power-off event.
- Use Cases:
Detect unauthorized device shutdowns.
Ensure continuous device operation and data collection.
Logic: Generated after the device is disconnected from the external power supply for 5 minutes.
Use Cases:
Detect power disruptions or device tampering.
Enhance security and reduce data loss in case of power interruptions.
Logic: Generated when the vehicle is in motion between start and end times as defined during alert subscription.
Use Cases:
Monitor and record vehicle movements during specific time periods.
Track and report unauthorized vehicle usage outside working hours.
Logic: Triggered directly from the device when the device powers on.
Use Cases:
Detect unauthorized device activation.
Ensure device integrity and data security.
Logic: Generated when any health code (DTC fault code) comes for the first/last time for vehicles with OBD devices.
Use Cases:
Monitor vehicle health and diagnostics.
Receive alerts for potential vehicle issues.
Monitor and maintain vehicle battery health.
Receive alerts for potential vehicle battery issues.
Logic: Generated when the device's battery goes below the battery percentage limit defined by the user
Use Cases:
Monitor and maintain device battery health.
Receive alerts for device battery replacement or charging needs.
Logic: Generated when the vehicle is on a trip, and the current distance from the nearest defined route polyline deviates by a user-defined threshold.
Use Cases:
Monitor route adherence and deviations for better route planning.
Detect and address unauthorized route changes.
Logic: Generated when the vehicle is stopped inside the geofence configured for more than a continuous time period as defined during alert subscription.
Use Cases:
Monitor and optimize vehicle stoppage times within specific geofenced areas.
Enhance security by detecting prolonged stops within designated zones.
Logic: Generated when the distance traveled by a vehicle crosses the input threshold defined by the user.
Use Cases:
Monitor and control excessive vehicle mileage.
Prevent unauthorized vehicle usage or detours.
Logic: Generated whenever a fuel drainage greater than the threshold configured at the tank level is detected
Use Cases:
Detect and prevent fuel theft incidents.
Ensure fuel accountability and reduce operational costs.
Logic: Generated when the vehicle travels a distance less than the threshold in the time period (in minutes) as defined during alert subscription. This alert only works on trips; the vehicle should be on an active trip.
Use Cases:
Monitor and ensure the completion of specific trip distances.
Identify and address incomplete trips or deviations.
Logic: Generated whenever a refueling event greater than the threshold configured at the tank level is detected.
Use Cases:
Track fuel consumption and refueling activities.
Verify fuel expenses and reduce discrepancies.
-
Logic: Generated when the door is opened or closed, and it is sensor-based.
Use Cases:
Monitor unauthorized access to vehicle compartments.
Enhance security by detecting door-related events.
Logic: Generated when the vehicle is being driven at a speed greater than the limit defined inside the geofence configured and for a time period greater than that defined during alert subscription.
Use Cases:
Enforce speed limits within specific geofenced areas.
Ensure safety and compliance within defined zones.
Logic: Generated when the battery percentage is less than the battery threshold defined during alert subscription, specifically for EV vehicles
Use Cases:
Monitor and maintain the battery health of electric vehicles.
Plan and schedule recharging for EVs to avoid battery depletion.