See the table below for definitions of all columns in the "Route Analytics" report. How to extract reports
Column |
Name |
Definition |
|---|---|---|
A |
DC ID |
Distribution center ID |
B |
DC Name |
Distribution center name |
C |
DC Time Zone |
Local DC time zone |
D |
Route ID |
Unique route identifier (auto-generated with SDK and CSV imports, assigned on server API imports) |
E |
Route Name |
Name or number of the route |
F |
Planned Route Start Date |
Planned route start date in local DC time zone (formatted as YYYY-MM-DD) |
G |
Planned Route Start Timestamp |
Planned route start timestamp in local DC time zone (formatted as YYYY-MM-DD HH:MM:SS) |
H |
Driver ID |
Driver ID that was detected to have driven the route (might differ from originally assigned or currently assigned driver) |
I |
Driver Name |
Driver name that was detected to have driven the route (might differ from originally assigned or currently assigned driver) |
J |
Driver Groups |
Driver Group Name the driver belongs to. If the driver does not belong to any groups, this field is blank. |
K |
Is Digital Route |
Indicates whether this route was fully digitized. A breakdown of the different flags that build up to this KPI follows: 1) Driver Trace Passed, 2) Driver Click Score Passed, 3) Hardware Trace Passed. |
L |
Digital Route: Driver Trace Passed |
Indicates whether this route: 1) Started and ended at the indicated locations (these can be distribution centers, cross-docking locations, or arbitrary locations and their geofence), 2) There were no data gaps that could be attributed to poor driver behavior (turning off the phone, the app or location services), 3) There was driving detected outside of the start and end geofences |
M |
Digital Route: Driver Click Score Passed |
Indicates whether this driver had a passing Driver Click Score above 85%. |
N |
Digital Route: Hardware Trace Passed |
Indicates whether there were any data issues detected (excessive jitter) or excessive data gaps that could not be attributed to poor driver behavior. We're always improving our algorithms, so if you think a particular route wasn't digitized due to bad driver behavior, please contact our support. |
O |
Imported Customers Count |
The number of customers originally imported |
P |
Real-Time Sequencing Enabled |
Indicates whether the route had real-time sequencing enabled |
Q |
Customers with Confident Locations Count |
Number of customers in route with confident locations |
R |
Customers with Unconfident Locations Count |
Number of customers in route with unconfident locations |
S |
Customers with Unknown Locations Count |
Number of customers in route with missing/blank locations |
T |
Successful Customers Count |
Total count of customers that were marked as successfully serviced |
U |
Failed Customers Count |
Total count of customers that were marked as failed serviced |
V |
Try Again Later Customers Count |
Total count of customers that the driver indicated they will come back later |
W |
Mixed Status Customers Count |
Total count of customers that had mixed failed, success or try again later clicks |
X |
Total Visited Customers Count |
Total count of customers that had a stop detected within 150m/450ft of the customer location if the customer had a confident location |
Y |
Total Unvisited Customers Count |
Total count of customers that did not have a stop detected within 150m/450ft of the customer location if the customer had a confident location |
Z |
Reattempt Authorizations Count |
Total number of authorizations issued from the supervisor to come back to a customer during the route |
AA |
Total Clicks at Confident Locations |
Total driver clicks that were at a customer with a confident location (including warehouse and reattempts) |
AB |
Total Clicks at Unconfident Locations |
Total driver clicks that were at a customer with an unconfident location (mostly new Customers/POS) |
AC |
Total Clicks at Unknown Locations |
Total driver clicks that were at a customer with an unknown location |
AD |
Actual Route Departure Time |
Date and time of departure of the route start location. It will only be detected if the driver logs in inside the start location geofence. |
AE |
Actual Route Arrival Time |
Date and time of arrival to the route end location. It will only be detected if the driver finalizes the route inside the end location geofence. |
AF |
Driver Click Score |
Driver Click Score. For details, refer to: |
AG |
Total Customers Clicked |
The total amount of customers marked in the driver application as visited, whether it was successful or failed (this does not mean the driver actually went to these customers) |
AH |
Total Visits Clicked with Distance Measured |
The total number of visits clicked in the driver application, whether it was successful or failed that Foxtrot Systems was able to establish a distance from the click to the customer based on partial learnings or the actual customer location. Depends on the customer confidence, please look at the per attempts repo for details. |
AI |
Total Clicks at Customer |
Visits clicked that were able to have a distance to the customer calculated (this depends on the maturity of the location learning of each customer and an acceptable click adherence radius of 150m/450 ft is used if it's possible to calculate a distance) |
AJ |
Total Sequence Adhered Clicks |
Number of customers clicked made following the sequence suggested by Foxtrot Systems |
AK |
Total Sequence Not Adhered Clicks |
Number of customers clicked made without following the sequence suggested by Foxtrot Systems |
AL |
Total Sequence Adhered Clicks with No Decision |
Number of customers clicked that could not be measured if it was consistent with the sequence or not |
AM |
Total Sequence Forgiven Clicks |
Number of customers en route that we counted as “adhered” to the Foxtrot Systems sequence regardless of the real visit order |
AN |
Sequence Adherence |
Indicates adherence to Foxtrot Systems' live sequence suggestions. For more information, please refer to: |
AO |
Planned Foxtrot Driving Meters |
Planned meters to be driven for the most optimal route valid at the time the route was imported |
AP |
Total Driven Meters |
Actual meters driven from route start location geofence to route end location geofence |
AQ |
Planned Foxtrot Driving Seconds |
Planned seconds to be driven for the most optimal route valid at the time the route was imported |
AR |
Total Driven Seconds |
Actual seconds driven from the route start location geofence to the route end location geofence |
AS |
Planned Foxtrot Journey Seconds |
Planned total journey seconds for the most optimal route valid at the time the route was imported |
AT |
Total Journey Seconds |
Actual total journey seconds from the route start location geofence to the route end location geofence. Considers driving time and service times. Only visible for Driver Trace Passed routes. |
AU |
Total Stops Count |
Total number of stops that were detected (includes authorized and unauthorized stops and excludes traffic stops) |
AV |
Total Stop Time Seconds |
Total seconds that stops were detected (includes authorized and unauthorized stops and excludes traffic stops) |
AW |
Total Authorized Stops Count |
Number of times the driver stopped further of 150m/450ft of any of the planned customers or away from the planned route start and end locations (this only uses confident locations, so some stops might be at unconfident customer locations that haven't matured yet to confident) |
AX |
Total Authorized Stops Seconds |
Number of seconds the driver stopped further of 150m/450ft of any of the planned customers or away from the planned route start and end locations (this only uses confident locations, so some stops might be at unconfident customer locations that haven't matured yet to confident) |
AY |
Total Unauthorized Stops Count |
Number of times the driver stopped further of 150m/450ft of any of the planned customers or away from the planned route start and end locations (this only uses confident locations, so some stops might be at unconfident customer locations that haven't matured yet to confident) |
AZ |
Total Unauthorized Stops Seconds |
Number of seconds the driver stopped further of 150m/450ft of any of the planned customers or away from the planned route start and end locations (this only uses confident locations, so some stops might be at unconfident customer locations that haven't matured yet to confident) |
BA |
Total Data Gaps Count |
The number of times Foxtrot Systems detected gaps in the data. This can be due to poor hardware, poor driver behavior (turning off the phone or app), and/or lack of GPS signal (tunnels, tall buildings, etc) |
BB |
Total Data Gaps Seconds |
The number of seconds Foxtrot Systems detected gaps in the data. This can be due to poor hardware, poor driver behavior (turning off the phone or app), and/or lack of GPS signal (tunnels, tall buildings, etc) |
BC |
Customers with Additional Visits |
Number of customers that were visited more than one time during the execution of the route |
BD |
Total Additional Visits |
Total number of additional visits to customers in a route |
BE |
Additional Visits With Final Result Success |
Number of customers that resulted in a successful service after being visited more than one time |
BF |
Driver Marked Route Start Timestamp |
Driver marked route start timestamp in local DC time zone. Formatted as YYYY-MM-DD HH:MM:SS |
BG |
Driver Marked Route Start Latitude |
Driver marked route start location latitude |
BH |
Driver Marked Route Start Longitude |
Driver marked route start location longitude |
BI |
Driver Marked Route End Timestamp |
Driver marked route end timestamp in local DC time zone. Formatted as YYYY-MM-DD HH:MM:SS |
BJ |
Driver Marked Route End Latitude |
Driver marked route end location latitude |
BK |
Driver Marked Route End Longitude |
Driver marked route start location longitude |
BL |
End Terminus Changed |
Indicates whether the route ended at the planned end terminus or not. If this is true, all planned data is blanked out. |
BM |
Planned Total Waiting Time Seconds |
The time between the estimated arrival and the next time window. The time window(s) specified constrains the route in a way that generates this waiting time. |
BN |
Stem Start Duration (seconds) |
The duration in seconds from the departure warehouse event (planned start) to the first delivery attempt or first authorized stop (nearby a planned customer) in the route, whichever comes first. If the route did not start or, did not end in the planned location, or the route does not have visit clicks, the value will be blank. |
BO |
Stem Start Distance (meters) |
The driven distance in meters from the departure warehouse event (planned start) to the first delivery attempt or first authorized stop (nearby a planned customer) in the route, whichever comes first. If the route did not start or, did not end in the planned location, or the route does not have visit clicks, the value will be blank. |
BP |
Stem End Duration (seconds) |
The duration in seconds from the last delivery attempt or last authorized stop (nearby a planned customer) in the route, whichever comes last. If the route did not start or, did not end in the planned location, or the route does not have visit clicks, the value will be blank. |
BQ |
Stem End Distance (meters) |
The driven distance in meters from the last delivery attempt or last authorized stop (nearby a planned customer) in the route, whichever comes last. If the route did not start or, did not end in the planned location, or the route does not have visit clicks, the value will be blank. |
BR |
Beta: GPS Spoofer Suspected |
This is a Beta feature. We are working on improving it and would love your feedback — please contact Service Desk. Contains whether Foxtrot believes the driver used a GPS spoofer to fool us in order to increase their click score and/or their sequence adherence metrics. The classification is as follows:
|