Alerts Configurations

Alert Name

Alert Type

Definition

Long Stoppage (Live)

Continuous

"If vehicle speed is less than 3km/hr between 2 pings then it is categorized as a stoppage in this interval. If continuous stoppage is observed for next x hours then it will be categorised as long stoppage. 

Alert is raised only if vehicle is in transit and not at origin/destination/known place

x can be configured basis 3 total trip distance buckets. (0-100km, 100-300km, 300+km).

Customer Can choose the time interval to raise alert

Imp - Long stoppage alert is raised only when trip is in transit. For alert at origin and destination we should configure detention alert

Route Deviation (Live)

Continuous

"If the minimum perpendicular distance between origin-destination google path and the location ping at any given point of time is greater than the threshold then it's a route deviation. 

System will check for max top 3 google suggested routes and if distance is greater than the threshold from all 3 routes then only alert will be raised

Min threshold for deviation is customizable at CBD

Overspeeding (Live)

Continuous

"If a vehicle is driving above a threshold speed for continuous x minutes

Max speed and x is customizable

Night Driving (Live)

Continuous

Alert is raised if a vehicle is driving in a certain time interval for minimum of x minutes 

Time interval and x is customizable"

E-Way bill expiry (Live)

Discrete

Alert Creation - 

From Z minutes before expiry (12:00 am) check for the ETA of the trips, if trip is tracked then ETA>E-Waybill Expiry Time + Y then raise an alert, if trip is not getting tracked then raise an alert irrespective of last known ETA. 

AT 23:59 pm check for the ETA of the trips, if trip is tracked then ETA>E Waybill Expiry Time then raise an alert, if trip is not getting tracked then raise an alert irrespective of last known ETA. 

Y is configurable at CBD level, it’s delay buffer in minutes

Untracked (Live)

Continuous

If there are 0 pings received for a trip since creation then it will be categorised as untracked trip.

Alert to be raised once x hours have passed since trip creation.

X is customizable at company level

Tracking Interrupted (Live)

Continuous

Trips where at least 1 ping is received since trip creation and the next ping is not received in the last x hours.

x can be customised at CBD level

Continuous Driving (Live)

Continuous

If a vehicle is driving for x hours without taking a continuous break of Y hour 

x,y to be configurable at CBD level"

Transit Delay (Live)

Continuous

If the current ETA for a trip is greater than the STT or the initial ETA at the time of trip start.

If STT is provided then raise alert if ETA>Trip Creation TIme +STT+ 30 min

If STT is not provided raise alert if ETA>ETAinitial + 30 min

30 min is configurable and should be set to loading time of a plant

Detention (Live)

Continuous

Long Stoppage at Origin/Destination/Known Place

Low Battery (Live)

Continuous

if at any moment device battery charge is below Y% then raise an alert for Low Battery - <Location Source>.

Alert to get closed if battery is above x+5%

STA Breached

Continuous

Alert Creation 

Step 1

If STA is provided when a trip is created then take STA as is If not provided then compute proxy Standard Transit Time (STT) basis the average truck speed set by company and total trip distance. (Here trip distance will be google distance)

STT = Google Distance / Speed

Step 2 Compute STA Date Time

Once the trip is created geofence exit time is not present so whenever trips is created initial STA will always be computed on Trip creation time, later if we get the origin geofence exit time then STA will be revised based on origin geofence exit

STA (initial) = Trip Creation + Loading Buffer + STT

STA (Origin Exit) = Origin Exit Time + STT

Round Off ( Default setting is No ) - If customer says when a trip is created before 6 pm today then the vehicle can reach by EOD of STA day (11:59 pm) and if the trip is created before 6 pm then the vehicle can reach on or before STA date time. Hour of trip creation is optional

If Roundoff is Set As No  - Then STA is computed as in step 2

If Roundoff is Set As Yes - Then STA = Date(STT + Reference Time) + 23:59:59 

Eg if STT is 24 hour and trip is started/created at 6 pm on 10 July then  STA will be 11 July 23:59:59

Multiple Trips On Common Asset

Discrete

When a new trip is created then check for the following

1. A same open trip exist with the same vehicle number

2. A same open trip exist with the same mobile number

3. A same open trip exist with the same portable device

4. A same open trip exist with the same gps device

5. A same open trip exist with the same driver app

• If above case holds then send the notification email/SMS to configured emails/numbers

  1. If the previous open trip is within the same company then send notification to Internal and external stakeholders

  2. If the previous open trip is of another company then send notification to Internal stakeholders only 

Trip Validation Failure

Continuous

• User can define multiple validation rules on trip data along with time to evaluate rule from trip creation e.g 

  • Rule Name - EWB missing

  • Condition  - EWB is null or EWB = 000

  • Time = 60 min from trip creation

• If the rule evaluates to true after the defined time duration then the alert will be raised

• As soon as the conditions becomes false or trip closes then the alert will be closed

• We can set as many rules to raise alerts

• At any given time only 1 alert will be in progress mentioning all the failed rules