Understanding the Data
The On-Time Delivery Performance app is designed to help users analyze performance metrics for their packages. It is important to note that this is not the exact On-Time Performance calculated by UPS.
On-Time Performance is calculated in Intelligent Logistics as follows:
First, we identify the date the package is in the carrier’s possession, which is referred to as In Carrier Possession Date/Time (ICPD). This is often the Origin scan, but sometimes the carrier will perform a Pick-up scan. Either way, to start the clock for OTP we need to find the earliest event when the carrier had possession. This is not the date the label was printed, and is also not necessarily the Pick-up date the carrier provides.
The next step is to determine what the Carrier Commitment Cutoff Date (CDCD) is as defined by the carrier. This is the date and time the carrier commits to deliver. For UPS, we connect with their Time In Transit API to determine the CDCD. We use the ICPD in the API call, along with the service, destination, etc.
The next step is to calculate the Gross On-time Performance (GOTP). The GOTP indicates if delivery was on-time, regardless of the circumstances. Quite simply, was the Delivery Date/Time (DD) on or before the CDCD.
There are four possible values for GOTP:
- On-Time
- Late
- Early
- Not Applicable
If DD was after CDCD, then it is Late. If CDCD was on the same day as DD, and DD time is on or before CDCD, then it is On-time. Early means the DD was a day or more earlier than the CDCD.
Net On-time Performance’s (NOTP) goal is to determine if the carrier was able to meet their delivery commitment, factoring in circumstances within their control.
There are three possible values for NOTP:
- On-Time
- Late
- Not Applicable
For example, if the carrier mis-sorts a package, leading to a delay that causes the package to be delivered after the delivery commitment, then that package is late because the delay was under the carrier’s control. However, if weather leads to a delay that causes the package to be delivered after the delivery commitment, then that package is not considered late, and is therefore flagged as On-time. So ultimately, the purpose of NOTP is to judge how the carrier performed to their delivery commitment.
One additional factor in NOTP is if the package was picked up in time, meaning was it before the Carrier Pick-up Cut-off Date/Time (CPCD). The CPCD essentially means did it make it to a carrier hub in time for them to process the package to meet the CDCD. If it was too late to the hub, the carrier cannot make the CDCD since their equipment/trucks/planes might have already departed. So the CPCD is factored into the NOTP, and if the package was late to the hub, it doesn’t count against the carrier, and thus would show as On-Time.
Reason for Late Carrier Delivery (RLCD) is determined whenever GOTP is late. It helps the user understand why NOTP is either late or on-time.
Not-Applicable in either GOTP or NOTP indicates the information available on the record isn’t sufficient to perform the calculation. Sometimes this is due to a bad address on the Ship From or Ship To. If an address has a bad postal code/city combination, the Time In Transit API won’t return a CDCD.
Below are some examples:
| Gross On-time Performance | Net On-time Performance | Carrier Delivery Commitment Date/Time | Delivery Date/Time | Late By | Reason For Late Carrier Delivery | Transit Exception Type |
| On-Time | On-Time | 1/5/2022 17:00 | 1/5/2022 16:49 | |||
| Early | On-Time | 1/5/2022 17:00 | 1/4/2022 15:18 | |||
| Late | Late | 1/5/2022 17:00 | 1/5/2022 21:15 | Time | Delivery Date Commitment Missed | |
| Late | Late | 1/5/2022 17:00 | 1/6/2022 1:07 | Date | Delivery Date Commitment Missed | |
| Late | On-Time | 1/5/2022 17:00 | 1/7/2022 8:48 | Date | Uncontrollable Exception Occurred | Customs/Import/Export |
| Late | On-Time | 1/5/2022 17:00 | 1/6/2022 11:15 | Date | Uncontrollable Exception Occurred | Recipient Unavailable |
How to Use this Application
The On-Time Delivery application provides several options for users to analyze carrier performance by means of the visual chart, table data, and pivot view.
Visual Chart
By selecting the first button within the Chart View, the Standard Chart, users can create a visual representation of their carrier's performance.
To recreate the chart shown above, click on the Settings gear above the chart and set the following parameters:
Delivery Schedule In-Time: Package was delivered on or before the Initial Scheduled Delivery Date/Time, regardless of fault
Delivery Schedule On-Time: Package was delivered on (not before or after) Initial Scheduled Delivery Date/Time
There are many options available within the Measures. Experiment with the data points below to create your own custom view:
Continuing with the parameters we've already established in the first example, a user can leverage the Aggregate View by clicking on the second button above the chart. Click into each row to expand the data and view more details.
To add more layers to this view, refer to the Chart Settings button. Select additional Dimensions to add more rows to the aggregate view. Select additional Measure to add more columns.
The Flattened View will display the data in horizontally, based on the settings the user has selected in the Chart Settings button. To leverage this view, select the third button above the chart.
The Heat Map provides a unique perspective of the data in map form. Select the fourth button above the chart to utilize this view.
Note the drop-downs shown above the Heat Map:
In the example below, we are filtering by Net On-Time Delivery - Late Due to Exception, Ship-to: State/Region. This view illustrates where packages are experiencing exceptions that are leading to a late delivery.
Table View
The On-Time Delivery application provides a wide range of tracking and exception data to support the user's reporting and analytics. The Gross On-Time Hour Variance column is a tool that can help users gain insight into how late or early a particular package was delivered.
In the examples below, we can see that some packages were delivered only one minute after the CDCD. The user can refer to this column when analyzing their carrier's metrics to determine how to best categorize these shipments.
Pivot View
The Pivot View provides a summary of the totals reflected within the table data. In addition to the filter drop-downs shown above the Pivot, users can select from several column options within the Pivot Settings.
In the example below, we've elected to see the data displayed by Carrier Service and Delivery Month. Column reflect the total On Time, Late by Day, Late by Time, and Late Due to Exception: