Dashboard Go to Guide: Trip Analytics Dashboard

This dashboard shows various information captured through our core product - Track and Trace. Most of the important data points are captured in this dashboard which were not possible to capture by the client before subscribing FT such as transit time, activity-wise TAT splits, repeat trucks etc. This dashboard gives insights to clients on their overall logistics movement like what is the average distance traveled by our trucks, what are average TATs for various activities in the journey of the trip and so on and so forth. It also summarizes alerts data at branch level, transporter level as well as consignee level. It helps the client understand what are the major types of alerts generated on their trips. Was there a lot of time wasted in a long stoppage? Was there detention on the trips? at the origin? at destination? This is one the most informative dashboards and will give insights on challenges faced by the trips.

Definitions/Logics: 

Loading Time:

Origin Geofence Exit- Origin Entry time, 

If Origin Entry time is not available then Origin Geofence Exit - Trip Creation Time.

Unloading Time:

Destination Geofence Exit - Destination Geofence Entry

If entry/exit not available then Last Ping Inside Destination - First Ping Inside Destination

Stoppage Time:

When average speed less than 3km/hr, then time between two pings will added in stoppage time.

Running Time:   When average speed is greater than 3km/hr, then time between two pings will added in Running time. Corresponding distance is called Running Distance.

Transit Time: Sum total of Running Time and Stoppage Time. Corresponding distance is called Transit Distance.

Total Distance: The distance estimated by Freight Tiger ETA Engine based on the origin, destination and waypoints associated with the trip.

Distance Traveled: The distance obtained by adding the haversine distance between all the pings received for the trip.

Consented Trip: When the consent process is completed for a trip, it will show as a consent accepted for that trip else as consent pending.

Note: The haversine formula determines the great-circle distance between two points on a sphere given their longitudes and latitudes.

Airtel: Diver will receive a call and he has to press 1 to complete the consent process.

Jio: Driver will receive a message and he has to reply with ‘Y’ to complete the consent process.

Vodafone/Idea: Driver will receive a phone number in a text message and driver has to give a missed call on that number to complete the consent process.

Mode of Closure: It defines the way a trip closes, There are four types of Mode of Closure.

Auto Closed: Trip fulfills the defined Auto closure logic.

Manual: If the trip doesn’t fulfill the Auto closure logic and the CT team confirms the unloading with the driver then they will manually close the trip.

API Closure: A trip is closed through this mode by different means: 1. If the trip doesn’t fulfill the Auto closure logic and vehicle returns to plant and a new trip is made on the same vehicle/phone number then the previous trip will be closed, 2. If user calls the close trip API then the trip will be closed and marked as API closed Trip.

Auto Termination: If the trip doesn’t fulfill the Auto closure logic then the trip will be auto terminated as per the defined hard auto termination limit.

Delayed Dispatch: If a Trip has a Detention at Origin alert then this Trip will be marked as Delayed Dispatch. You can configure the Detention at Origin alert settings as per your requirement.

Delayed Delivery: If a Trip has a STA breach alert then the Trip will be marked as Delayed Delivery.

Tab 1: Summary & Tracking

Under this tab you will be able to see how the total trips created MTD, Tracking%, Consent%(sim supported network includes Airtel,Jio,Idea & Vodafone), Average distance traveled, Average Running time,Average Stoppage time,Average Loading time,Average Unloading time.

FAQs answered in this tab:

• How many trips are tracked by GPS, SIM, SIM/GPS combination etc

• How many Sim/GPS trips actually got tracked?

• How many trips are currently open and for how long are they open?

• MoM trend of Mode of closure? If Auto closure% is increasing or not?

• Consignees whose Auto closure% is poor?

• MOM trend of Trip created, trend of tracking%, trend consent% etc. If tracking is going up or down?

• MOM trend of Journey time (Loading time, Running time, stoppage time, unloading time), You can also filter this trend on different distance traveled buckets and check for a specific set of trips. If there is an increasing or decreasing trend?

• MOM trend of  average and median of Loading time and Unloading Time.

• Daily trend of Trips created, Tracking% and consent%. If on a particular day the metrics are compromised? Next question: What went wrong?

• Trend of Trips created, Tracking% and consent% branch wise and Top 10 transporters.

• Consent% basis the shift of plant. To identify if a particular shift is more efficient.

• How many vehicles are repeating trips, which are more efficient and how many of the total trips got tracked of these repeat vehicles etc.

Tab 2: At Origin

Under this tab you will get information about how efficiently your material gets loaded in the vehicle. You can compare loading time for different plants, by different shifts of day etc.

FAQs answered in this tab:

• MOM trend of average and median of loading time.

• Which plant is more efficient in loading material?

• MOM trend of average and median loading time for different plants.

• Does a specific set of vehicles impact the overall loading time?

• Is a specific shift lagging behind in loading material?

• If the dispatch orders are more in a particular shift, does it affect my loading time?

Tab 3: In-Transit

Under this tab you can see all the metrics related to the in-transit period of a trip. You can compare the running and stoppage time trend by plants, by transporters, by routes etc. You can also see for which transporters more alerts are getting generated or for which particular routes more alerts are getting generated.

FAQs answered in this tab:

• Trend of running and stoppage time. Does stoppage/running time have a downward trend?

• How does trip distance impact the vehicle running and stoppage time?

• Is a particular set of trips/transporters impacting the overall stoppage time?

• Plants wise trend of stoppage time and running time.

• Trends of alerts raised during vehicle in-transit like long stoppage, route deviation, transit delay etc.

• Which transporters cater to maximum alerts?

• For which lanes maximum alerts got raised?

• What is the average stoppage and running time for a particular lane?

• What is the average duration of the alert by laness, by transporters, by plants etc?

• Is a particular transporter delivering material faster than other transporters?

Tab 4: At-Destination

Under this tab you can measure all the metrics once a vehicle enters the destination geofence. You can figure out which are the top 10 unloading locations, which vehicles are under detention currently, trend of unloading time etc.

FAQs answered in this tab:

• What is the trend of unloading time? Is it increasing or decreasing?

• Is a particular set of consignees detain vehicles more frequently?

• What is the trend of unloading time for Top 10 consignees?

• Does a particular geofence entry time impact the unloading time?

• For which consignees detention at destination alert more frequently got raised? What is the average detention alert duration time?

• What are the top 10 unloading locations?

• Do vehicles of a particular plant get detained more frequently than others?