List of Important Alerts with Logic and Different Use-cases

List of Important Alerts with Logic and Different Use-cases

List of Important Alerts 


  1. Geofence Entry / Exit Alert

    1.  Logic: Generated when the vehicle enters or exits any of the geofences created for the account.
    2. Use Cases:
      1.  Ensure vehicles adhere to defined geographical boundaries.
      2. Monitor and report on unauthorized movements of vehicles.

  1.  Stoppage Alert

    1. Logic: Generated when the vehicle is stopped for more than a continuous time period as defined during alert subscription

    2. Use Cases:

      1. Track and manage vehicle stoppage times efficiently.

      2.  Monitor and optimize idling periods to reduce fuel consumption.

  1. Overspeed Alert

    1. Logic: Generated when the vehicle is being driven at a speed greater than the limit defined and for a time period greater than that defined during alert subscription
    2.  Use Cases:
      1. Monitor and discourage over-speeding, promoting safe driving.
      2. Improve fuel efficiency by reducing high-speed driving.

  1. Sudden Acceleration Alert

    1. Logic: Triggered directly from the device in case of sudden acceleration based on pre-configured device setting

    2.  Use Cases:

      1.  Detect aggressive driving behavior

      2. Promote safe and smooth driving practices.


  1.  Sudden Braking Alert

    1.  Logic: Triggered directly from the device in case of sudden braking based on pre-configured device settings.

    2.  Use Cases:

      1.      Detect harsh braking events.

      2.       Monitor driver behavior and provide coaching for safer driving.

  1.  Sharp Turn Alert

    1. Logic: Triggered directly from the device in case of a sharp turn based on pre-configured device settings.
    2.  Use Cases:

      1.    Monitor and discourage aggressive or unsafe turning.

      2.    Reduce wear and tear on vehicles through smoother turns.

  1. SOS Alert

    1.  Logic: Triggered when someone presses the SOS button. Consideration time is typically 2 minutes.

    2. Use Cases:

      1.      For emergency situations and immediate response.

      2.      Ensure the safety and security of drivers.





  1.  Ignition Alert

    1.    Logic: Generated when the vehicle's ignition is toggled based on specific ignition data packets

    2.    Use Cases:

      1.       Monitor unauthorized ignition events.

      2.       Prevent vehicle theft by receiving alerts when the ignition is turned on without authorization.


  1. Device Removal Alert

    1. Logic: If the device is using its internal voltage for 10 minutes, even in a moving condition, this alert is generated
    2. Use Cases
      1.  Prevent device tampering or theft
      2. Monitor unauthorized device removal.


  1.  Power Cut Alert

    1.     Logic: Generated based on an external power cut event code sent directly from the device.

    2.  Use Cases:

      1.       Detects and reports power cut incidents affecting the device.

      2.       Ensure continuous device operation and data transmission.


  1.  Low Battery Voltage Alert

    1. Logic: Generated when the vehicle battery voltage of the device is less than a device-defined threshold.

    2.  Use Cases:

      1.       Monitor the health of the device's internal battery.

      2.       Ensure uninterrupted device operation.


  1.  Device Low Battery Voltage Alert

    1. Logic: Generated when the device's battery voltage goes below the battery percentage limit defined by the user.

    2. Use Cases:

      1.       Monitor and maintain device battery health.

      2.       Receive notifications to replace or recharge device batteries when necessary.





  1. Crash Alert

    1.  Logic: Triggered directly from the device in case of a crash based on pre-configured device settings
    2.  Use Cases:

      1.       - Detect accidents and collisions for immediate response.

      2.       - Enhance driver safety by alerting authorities in case of accidents.


  1. Vehicle Idle Alert

    1.  Logic: Generated when the ignition is on, and the vehicle is stopped for more than a continuous time period as defined during alert subscription.

    2.  Use Cases:

      1.     Monitor idle times to optimize fuel efficiency.

      2.     Identify and reduce unnecessary idling to lower operational costs.


  1.  Power Off Alert

    1.  Logic: Triggered when the device sends an alarm directly in response to a power-off event.

    2.     - Use Cases:

      1.  Detect unauthorized device shutdowns.

      2. Ensure continuous device operation and data collection.


  1.  Shutdown Alert

    1. Logic: Generated after the device is disconnected from the external power supply for 5 minutes.

    2. Use Cases:

      1.      Detect power disruptions or device tampering.

      2.      Enhance security and reduce data loss in case of power interruptions.


  1. Unexpected Movement Alert

    1.  Logic: Generated when the vehicle is in motion between start and end times as defined during alert subscription.

    2.  Use Cases:

      1.  Monitor and record vehicle movements during specific time periods.

      2.   Track and report unauthorized vehicle usage outside working hours.


  1. Power On Alert

    1.  Logic: Triggered directly from the device when the device powers on.

    2.   Use Cases:

      1.  Detect unauthorized device activation.

      2.  Ensure device integrity and data security.


  1.  DTC Alert

    1.  Logic: Generated when any health code (DTC fault code) comes for the first/last time for vehicles with OBD devices.

    2.  Use Cases:

      1.  Monitor vehicle health and diagnostics.

      2.  Receive alerts for potential vehicle issues.






  1.  Vehicle Low Battery Voltage Alert

    1. Logic: Generated when the vehicle battery voltage goes below a user-defined limit for a user-entered duration threshold
    2. Use Cases:
      1. Monitor and maintain vehicle battery health.

      2.  Receive alerts for potential vehicle battery issues.



  1.  Device Low Battery Alert - Configured

    1. Logic: Generated when the device's battery goes below the battery percentage limit defined by the user

    2. Use Cases:

      1. Monitor and maintain device battery health.

      2. Receive alerts for device battery replacement or charging needs.












  1.  Route Deviation Alert

    1. 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.

    2.  Use Cases:

      1. Monitor route adherence and deviations for better route planning.

      2. Detect and address unauthorized route changes.


  1.  Geofence Stoppage Alert

    1. Logic: Generated when the vehicle is stopped inside the geofence configured for more than a continuous time period as defined during alert subscription.

    2. Use Cases:

      1. Monitor and optimize vehicle stoppage times within specific geofenced areas.

      2. Enhance security by detecting prolonged stops within designated zones.






  1.  Distance Traveled Above Set Limit Alert

    1. Logic: Generated when the distance traveled by a vehicle crosses the input threshold defined by the user.

    2. Use Cases:

      1. Monitor and control excessive vehicle mileage.

      2. Prevent unauthorized vehicle usage or detours.


  1.  Fuel Theft Alert

    1. Logic: Generated whenever a fuel drainage greater than the threshold configured at the tank level is detected

    2. Use Cases:

      1. Detect and prevent fuel theft incidents.

      2. Ensure fuel accountability and reduce operational costs.


  1. Trip Distance Covered Alert

    1. 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.

    2.  Use Cases:

      1. Monitor and ensure the completion of specific trip distances.

      2. Identify and address incomplete trips or deviations.



  1. Refuel Alert

    1.  Logic: Generated whenever a refueling event greater than the threshold configured at the tank level is detected.

    2. Use Cases:

      1. Track fuel consumption and refueling activities.

      2. Verify fuel expenses and reduce discrepancies.


    - 




  1. Door Alert

    1. Logic: Generated when the door is opened or closed, and it is sensor-based.

    2. Use Cases:

      1. Monitor unauthorized access to vehicle compartments.

      2. Enhance security by detecting door-related events.

  1.  Overspeed Within Geofence

    1. 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.


  1. Use Cases:

    1. Enforce speed limits within specific geofenced areas.

    2. Ensure safety and compliance within defined zones.


  1.  EV Low Battery Alert

    1. Logic: Generated when the battery percentage is less than the battery threshold defined during alert subscription, specifically for EV vehicles

    2. Use Cases:

      1. Monitor and maintain the battery health of electric vehicles.

      2. Plan and schedule recharging for EVs to avoid battery depletion.


    • Related Articles

    • Different Category of Alerts

      The Alerts Module within Loconav's platform supports various types of alerts, categorized as follows: Auto-Generated Alerts: These alerts are automatically generated by the system but require users to subscribe to start receiving notifications around ...
    • How to subscribe alerts on the dashboard ?

      Configuring Alerts: To set up and configure alerts in Loconav's Alerts Module, follow these steps: 1. Navigate to the "Alerts" module within the dashboard 2. Identify the alert you want to configure. 3. Click on "Set Alert" to start the configuration ...
    • Best Practices and Tips

      Effective Use of the Alerts Module: To make the most of Loconav's Alerts Module, consider the following best practices and tips: 1. Customize Alerts: Tailor alerts to your specific business needs and use cases by configuring condition based alerts. ...
    • Alert History Monitoring & Reporting

      Viewing Alert History: Users can easily access the history of alerts triggered by their vehicles or assets within the Loconav FMS platform. Here's how: Click on the alert listing within the Alerts Module. Use the time period filter to select a custom ...
    • Troubleshooting and FAQ

      Common Issues and Solutions: While Loconav's Alerts Module is designed to provide seamless monitoring, users may encounter common issues. Here are some issues and recommended solutions: Issue 1: Not Receiving Alerts Solution: Check your notification ...