Summary

The Travel Summary provides information at the driver and truck levels. Select either Driver or Truck in the dropdown menu to view the information by driver or by truck.

The data elements displayed in the table are the following:

• Driver/Truck -
  • Driver - The first and last name of the Eclipse user logged into the app.
  • Truck - The vehicle selected in app or the device name in iOS general settings.
• Total Distance Traveled - Total distance in miles this driver traveled for the specified time period.
• Total Time Traveled -  Total time it took for the driver to complete his deliveries -- including both moving and stopped time.
• Idle Time - Total time the truck was idle*.
• Days - The total number of days during the selected date range where the driver/truck was active.
• Stops - The total number of stops made during the selected date range.
• Average Speed - The average speed (in mph) when the truck was moving.
• Max Speed - The maximum speed (in mph) reached at any point during the selected time period.

By default, idle time is defined as the truck being stopped for at least 5 minutes but not to exceed an hour. You can change the min and max values on the Settings tab. For more information, click here.

The Alerts table will display both Issues and general Activity. More information on setting up alerts and utilizing the tables feature can be found here.

To search for a specific Driver or Device, you can enter the driver name or device name in the search box and click the search icon.

The Mileage By State section shows total mileage for each state traveled in for the selected time period and branch.

The Completed Manifest table displays detailed information about each manifest completed in Deliver.

• Manifest - Manifest number that was completed in the Deliver App. If manifests were combined in app they will appear as separate listing on the table.
• Driver - Displays the drivers name and device/truck used to make the delivery.
• Start Time - This is the time where either the manifest was auto started in the app or when the driver manually started the route.
• End Time - This is the time when the manifest was removed from the device (either through completing the take me home or completing the last stop).
• Start Odometer - The odometer reading entered in app when beginning the route.
• End Odometer - The ending odometer calculated by number of miles driven during route (the route is completed either through completing the take me home or completing the last stop).
• Route ID (Route Customers Only) - When the manifest is created in Route, we assign a Route ID. If the Route ID field is blank, either the manifest was created in Eclipse or it was created in Route but then edited in Eclipse. This is included in the Export only.

Note: If you are not capturing odometer readings in app, these values will be blank.

The Completed Stops table displays detailed information about each individual stop on a manifest.

• Manifest - Manifest number that was completed in the Deliver. If manifests were combined in app they will appear as separate listing on the table.
• Driver - Displays the drivers name and device/truck used to make the delivery.
• Stop - Stop number (this is the stop number as it appears in Eclipse).
• Plan Time - The first estimated time we calculated for the stop when the manifest started (the estimated time gets updated throughout the route so this is a snapshot of that first time).
• Actual - The time the driver completes the stop.
• Requested Time - This could be a specific time or a requested time window.
• Arrived At - The time the driver arrives at the stop (this is calculated when the driver enters a 0.2 mile of the delivery address - if the driver never enters the geofence, this field will be blank).
• Departed At - The time the driver leaves the 0.2 mile geofence of the delivery address (if the driver never enters the geofence, this field will be blank).
• Stop Time - The amount of time the driver stayed with the 0.2 mile geofence (if the driver never enters the geofence, this field will be blank).

Note: You can filter stops based on if they were on-time or late. A stop is considered on-time if the actual time is before or at a specific requested time or if the actual time is before or within the requested time window.  If the branch level settings "Use Arrival Time for Late Stops" is enabled, the Arrived At time will be use instead of the actual time. This only applies to orders with a requested time.

The Stop Times table displays the average stop time for each ship-to customer. The stop time is calculated using the Arrived At and Departed At values in the Completed Stops table.

Note: A customer will only appear in the table if the driver breaks the 0.2 mile geofence for their delivery address.

• Customer - Name of the ship-to customer.
• Address - The first recorded address for this customer.
• Stop Time - Average stop time for all stops made to this ship-to customer.

Customer: Ship-to Customer Name. Row data will be based on this customer's deliveries

# of Deliveries: Number of deliveries (stops) over selected time period

Avg # Orders: Average number of orders per delivery

Avg # Items: Average number of items per delivery

Avg Revenue: Average sales per delivery

Avg Profit: Average profit per delivery. Profit is Sales - COGS by default. Note, this can be changed to use COMM-COST in the Innovo Deliver Profit Cost Eclipse control file.

Stop Time: Average time the driver spent within 0.2 mi of the customer's ship-to address

Ship Via: Ship Via from Manifest header. Row data will be based on this Ship Via

# of Deliveries: Number of deliveries (stops) over selected time period

Avg # Orders: Average number of orders per delivery

Avg # Items: Average number of items per delivery

Avg Revenue: Average sales per delivery

Avg Profit: Average profit per delivery. Profit is Sales - COGS by default. Note, this can be changed to use COMM-COST in the Innovo Deliver Profit Cost Eclipse control file.

Stop Time: Average time the driver spent within 0.2 mi of the each customer's ship-to address

Driver: The first and last name of the Eclipse user logged into the app

Stops Per Day: Average number of stops delivered each day

Order $ Per Day: Sales per day

Profit Per Day: Profit (Sales - COGS) per day. Note, this can be changed to use COMM-COST in the Innovo Deliver Profit Cost Eclipse control file.

Avg $ Per Stop: Average sales per stop

Avg Profit Per Stop:  Average profit per stop. Profit is Sales - COGS by default. Note, this can be changed to use COMM-COST in the  Innovo Deliver Profit Cost Eclipse control file.

Total Order $ Per Line: Average line item dollar amount across all stops (excludes transfers and purchase orders)

Total Transfer $ Per Line: Average transfer line item dollar amount across all stops

Total PO $ Per Line: Average purchase order line item dollar amount across all transfers

Distance Per Day: Total miles driven while active with a manifest per day

Time Per Day: Total hours and minutes driven while active with a manifest per day

In order for your driver to receive a score, you must assign points to the metrics that are important to your company. To access the point system, click on the gear icon located under the Driver Scorecard heading.

The driver will receive a percentage of the points based on the number of stops on a route. Use the slider to assign points until the total number of points equals 100. Some metrics can be rated higher than others while other metrics can be left at zero points. Only those metrics with points assigned will be reported on.

The Scorecard can be setup per branch or can be set up at the All Branches level. If setup at the All Branches level, each branch will then toggle on the Use All Branches option.  

As the driver earns points for completing tasks along their route, they will be deducted a percentage of points for each violation. For example, let's say you have the safe driving metric assigned to 20 points. If you have a manifest with 20 stops and 3 speeding violations, the driver would receive 17 points for that metric as each violation would be worth 1 point. Now if you have a manifest with 15 stops and 3 speeding violations, the driver would receive 16 points for that metric as each violation would be worth 1.33 points (20/15).  

NOTE - For the requested time metric, we use the number of stops with a requested time instead of the total number of stops. For example, if there are only 4 stops with a requested time on a 20-stop route, each stop is worth 5 points.

This table will display an average score for each driver based on the date filter (e.g. Last 90 Days). To view detailed information for each driver, click on the driver name and you will see actual scores for each manifest.

• Score: Average score per all manifests within the specified date filter
• Issues: Total number of issues  
• Driver: The first, last name and email address of the Eclipse user logged into the app
• Total Distance Traveled - Total distance in miles this driver traveled for the specified time period
• Total Time Traveled -  Total time it took for the driver to complete his deliveries -- including both moving and stopped time
• Routes: Total number of manifests completed
• Stops: Total number of stops completed
• Late: Total number of stops that missed the requested deliver time

The Driver Issues table will display the total number of violations for all drivers or the individual driver if one is selected from the table. Only those metrics assigned a point value and have a violation will appear on the table.