OTA delays logic for login trips (Driver delays, employee delays, Traffic delays).

Simple Explanation:

Descriptive Explanation:

The following series of events are in order of them taking place.

To check the OTA delays first we check if the Trip is delayed, then we check for the reason of delay.

A. TRIP_DELAY: Trip is delayed if actual trip end time is greater than [ planned trip end time + Trip end Grace time ]

B. If Trip is delayed:

1. Check for Driver Delay

2. Check for Employee Delay

3. Traffic Delay

Step 1: DRIVER DELAY:

Important - Driver delay is checked only for the first planned employee

[ Driver reporting time at first planned employee pickup > Planned sign in time of first planned employee + Employee Grace Time]   ---> Trip is under Driver Delay

NOTE - If first employee becomes "No-Show":
The Driver delay is checked for the 2nd Planned employee. The delay reason will only be considered for the no show sequence only when system captures the driver reporting time (DRT) for the pick up marked as no show. To understand this in detail, refer to Driver Reporting Time - Current Logic

Step 2: EMPLOYEE DELAY:

If the driver wasn't delayed for the first planned employee then we check the below for each of the employees.

1. [ Driver reporting time at the employee pickup < Planned sign in time of the employee + Employee Grace Time] 

2. [ Actual Pickup time of employee > Planned pickup time of employee + employee grace time]  ---> Trip is under Employee Delay

Step 3: TRAFFIC DELAY:

If the trip doesn't come under either Driver or Employee delay, then it falls under Traffic Delay