How to identify adhoc trips created by the system.

Step 1: Search the planned trip ID which was supposed to be completed and open the trip history as given below:

Step 2: In the trip sheet history check for cab details being changed. In this example the cab was changed from "Cab A" to "Cab B" on 19/04/2024 at 08:16 Hrs and then changed from "Cab B" to "CAB C" on 19/04/2024 at 08:22 Hrs.

When the vehicle vehicle was changed from "Cab A" to "CAB B" the trip was sent to the "Cab B IMEI".

Step 3: Search "Cab B" on the dashboard and select the date same as the planned trip IDs date. Check if any adhoc trip is created for "Cab B". Once you find the adhoc trip, please press on view route and then open "Device Health".

Step 4: Check when was the planned trip displayed on "Cab B IMEI" and was the device contacting to the server at the time when the trip was started. In this example, in the device audit for "Cab B IMEI" the planned trip ID: 206906 was displayed in the driver device at 08:21 Hrs as the device was not contacting to the server before 08:21 Hrs.

When the planned trip started on Cab B device IMEI the device was not contacting to the server due to which the trip status was not started in ETS and the system allowed to change the cab at 08:22 Hrs.

Note: In the given example when the cab was changed for planned trip ID: 206906 the device for Cab B, it was not contacting to the server due to which the same was not updated in the driver device, and when the device had sent data to the server there was no trip assigned to Cab B which already started the planned trip in the device, due to which the system had created a new ad-hoc trip ID: 206958 for Cab B.

How to avoid creation of Adhoc trips in the system?

1. Avoid making last minute changes to a trip.
2. When making changes to a trip, make sure that both devices mapped to the vehicles are contacting to the server so that the trip is removed from the previous cab.
3. When you get below warning message, please make sure that the previous cabs device is contacting to the server.

How to solve cases where the system created an adhoc trip and the planned trip got expired?

Step 1: Go to Billing-> Incomplete trips-> Select date and vendor.

Step 2: Select the option "Matching Adhoc Trip Found" and under actions, click on "Assign".

Note: In cases where the cab is added/updated by system, the planned trip status will be shown in progress and a corresponding ad-hoc trip will created in the system with the employee details.

For these cases, please delete one of the trips and consider the other for billing.

Reasons for cab data being updated by the system:

1. The device was not contacting to the server when the cab was removed from the tripsheet due to which when the device sends the trip start data am adhoc trip is created along with changing the planned trip status to trip in progress.

2. 

For example if Vehicle A with IMEI A is allocated to a trip but Vehicle B is currently running on IMEI A.

The trip will display in IMEI A with Vehicle B and if the trip is started in Vehicle B the details will be changed by the system and the planned trip will be started along with a corresponding adhoc trip.

This is because the below commands are sent at the same time to the server.

Planned trip start command.

Vehicle change command after the trip started in the system.