Trip States

Trip States

There are 7 pre-defined states of a trip. A trip can be in any one of these states at any given time.  These are:


  • Requested

  • New

  • Ongoing

  • Delayed

  • Completed

  • Unsuccessful

  • Cancelled




Creating a trip without vehicle assignment

Whenever a trip is created without assigning a vehicle to it, it is updated as REQUEST.


The  trip state is updated as NEW whenever

  • A vehicle is assigned to a ‘Trip Request’ or,

  • A trip is created with an assigned vehicle


Creating a trip with vehicle assignment

Whenever a trip is created with vehicle assigned to it, the trip state is updated as a NEW.

When a vehicle is assigned to a trip in REQUEST state, the trip state for the given trip is also updated as NEW.


Starting a Trip

A NEW trip is marked as Started, when the vehicle departs the starting location (source) geofence (based on geofence exit alert) within the ‘Trip Monitoring Time Period’ and the trip state is updated as ONGOING.


Delayed Trip

For an ONGOING trip, if the vehicle doesn’t arrive at the destination on or before its ‘Scheduled Arrival Time’ then the trip is updated as DELAYED.


Completing a Trip

Once the vehicle reaches the destination (based on geofence entry alert), after departing from the source,  within the defined trip monitoring time period, the trip is updated as COMPLETED.


Unsuccessful Trip

There can be multiple reasons for a trip to be marked as Unsuccessful.


  1. If the vehicle didn’t depart from the source location within the trip monitoring time period, then the trip is considered as UNSUCCESSFUL with the reason as ‘FAILED TO START’

  1. If the vehicle, after departing from source, didn’t arrive at the destination within the defined trip monitoring time period, the trip is updated as UNSUCCESSFUL with the reason as ‘TRIP TRACKING WINDOW EXPIRED’

  1. Incase the vehicle departs from the source and then returns back to source (instead of reaching the destination) then also the trip is considered as UNSUCCESSFUL with the reason as ‘VEHICLE RETURNED BACK TO SOURCE’


Note:

With regards to UNSUCCESSFUL trip with the reason as ‘VEHICLE RETURNED BACK TO SOURCE’:


  • The vehicle might return back to source due to some on ground issues, vehicle breakdown etc.

  • This is configurable, ie, it can be ensured that trips for an account are not updated as UNSUCCESSFUL with the reason as ‘VEHICLE RETURNED BACK TO SOURCE’ when the vehicle returns back to source. Instead, such trips will remain in ONGOING or DELAYED state

  • This doesn’t work in case of round trips, ie, where the start location (source) is same as the end location (destination). In such as case, the trip will be updated as COMPLETED if the vehicle returns back to the source within the trip monitoring time period.


Cancelled Trip

Cancellation is usually carried out in cases where the trip is not accounted for. It is generally used by enterprise clients where they have an Invoice number generated against the trip but don’t want to bill it or account for the trip at their end.


A user can manually cancel a trip from the platform. A canceled trip is not included in any existing report or analytics related to trips, except where specified.


Trip Request

A fleet manager can create a trip on the platform without assigning a vehicle to the trip. This is helpful in keeping track of the trip orders without assigning any vehicle in advance.


Eg:

A fleet manager has received an order for delivery that is scheduled at the end of next week. The fleet manager would want to keep a track of the order while they might not be able to assign a vehicle to the trip that is too far ahead in the future.


Using the trip request feature, a fleet manager can create a trip without assigning a vehicle to it. Later on, when the vehicle availability is confirmed, they can assign a vehicle to the trip as needed.


Trips under REQUEST state also work as per the defined Trip Monitoring logics. 


  • If no vehicle is assigned to the trip within the given time period, the trip will be updated as UNSUCCESSFUL with reason ‘TRIP REQUEST EXPIRED’


  • At times, the fleet manager might not want to fulfill the given trip request and can reject it. Rejected trip requests are also updated as UNSUCCESSFUL with reason ‘TRIP REQUEST REJECTED’


Note:

The user can also cancel a trip request, if needed (instead of rejecting it).

​


    • Related Articles

    • Trip related alerts and notifications

      Apart from the updated trip tracking logics, we have also introduced proactive trip notifications to the fleet managers, to help them track their trips better. Available trip related notifications to the FM 1. Proactive Notifications Trip About to ...

    • Manual actions on trips

      A user can take various manual actions to update the trip state. Manual actions by the user are different from the GPS enabled actions taken by the platform Various Manual Actions Manual Start Trip Manual End Trip Manually update the ...

    • What does the platform do while monitoring a trip?

      While monitoring a trip, the system will look to check and update: When does the trip actually start at When does the trip actually end at Updating the Trip states, as per vehicle movement Notifications and alerts related to vehicle movement on the ...

    • Trips Related Report

      List of Reports New trip report A. Overview New Trip Report tells you the list of all the trips that are under NEW trip state in a date range set by the user, ie, the trips that have been created by the user in the Trips module that are yet to start. ...

    • Trip Completion %

      Trip Completion % denotes the current completion rate of the trip. Trip Completion % is calculated as the rate of Distance traveled by the vehicle in the direction of the planned route destination to the overall scheduled/estimated distance of the ...