What are the different timestamp accuracy checks and how to improve your status accuracy.
C60 employs multiple status logic checks to verify the accuracy of timestamps from producer data, ensuring our analytics precisely represent the producer's business.
Timestamps are one of the most crucial data points collected and utilized in the C60 logistics and margin based dashboards.
The fundamental status checks are designed to:
- Confirm timestamps happen in the proper sequence. (ie: start load occurs before leave plant which occurs before arrive site)
- Ensure delivery phases are within a realistic threshold. (ie: the time it takes for a truck to get loaded and leave the plant is more than 3 minutes and less than 60 minutes)
- Compare the actual delivery durations against planned. (ie: actual travel time to the job site is close to your planned travel time)
The table below details the various status checks applied to each timestamp. When a timestamp matches one or more of the following conditions, C60 flags it as inaccurate.
|
|
Timestamps |
||||
|
# |
Start Load |
Leave Plant |
Arrive Jobsite |
Start Unload |
Leave Jobsite |
|
1 |
= 0 |
= 0 |
= 0 |
= 0 |
= 0 |
|
2 |
= Null or missing |
= Null or missing |
= Null or missing |
= Null or missing |
= Null or missing |
|
3 |
Start Load timestamp is equal to or happens after Leave Plant timestamp. |
Leave Plant timestamp is equal to or happens after Arrive Job Site timestamp. |
Arrive Job Site timestamp is equal to or happens after Start Unload timestamp. |
Start Unload timestamp is equal to or happens after Leave Job Site timestamp. |
Leave Job Site timestamp is equal to or happens before Start Unload timestamp. |
|
4 |
|
Leave Plant timestamp is equal to or happens before Start Load timestamp. |
Arrive Job Site timestamp is equal to or happens before Leave Plant timestamp. |
Start Unload timestamp is equal to or happens before Arrive Job Site timestamp. |
Leave Job Site equal to or happens before Start Load |
|
5 |
|
If loading phase is greater than or equal to 60 minutes. (Leave Plant – Start Load) >= 60 minutes. |
Arrive Job Site timestamp is equal to or happens before Start Load timestamp. |
Start Unload timestamp is equal to or happens before Start Load timestamp. |
Leave Job Site timestamp happens before Arrive Job Site. |
|
6 |
|
Leave Plant happens after Start Unload. |
Arrive Job Site happens after Leave Job Site. |
Start Unload happens before Leave Plant. |
If onsite time is less than 5 minutes. (Leave Job Site – Arrive Job Site) < 5 minutes. |
|
7 |
|
If loading phase is less than 3 minutes. (Leave Plant – Start Load) < 3 minutes. |
If travel phase to job site is less than 2 minutes. (Arrive Job Site – Leave Plant) < 2 minutes. |
If waiting to unload phase is less than 1 minute. (Start Unload – Arrive Job Site) < 1 minute. |
If onsite time is greater than 150 minutes. (Leave Job Site – Arrive Job Site) > 150 minutes. |
|
8 |
|
If loading phase is greater than 60 minutes. (Leave Plant – Start Load) > 60 minutes. |
If travel phase to job site is greater than 180 minutes. (Arrive Job Site – Leave Plant) > 180 minutes. |
If waiting to unload phase is greater than 60 minutes. (Start Unload – Arrive Job Site) > 60 minutes. |
Onsite time is less than 1/10th of the planned unloading time. (Leave Job Site – Arrive Job Site) < 0.1 * planned unloading time. |
|
9 |
|
If loading phase is less than 1/4th the planned loading time. (Leave Plant – Start Load) < 0.25* planned loading time. |
If travel phase to job site is less than 1/4th the planned travel time. (Arrive Job Site – Leave Plant) < 0.25* planned travel time. |
If onsite time is equal to 0 minutes. (Leave Job Site – Arrive Job Site) = 0.
|
Onsite time is 5 times the planned unloading time. (Leave Job Site – Arrive Job Site) > 5 * planned unloading time. |
|
10 |
|
If loading phase is 2.2 times the planned loading time. (Leave Plant – Start Load) > 2.2 * planned loading time. |
If travel phase to job site is 3 times the planned travel time. (Arrive Job Site – Leave Plant) > 3 * planned travel time. |
If unloading phase is 3.5 time longer than planned unloading time. (Leave Job Site – Start Unload) > 3.5 * planned unloading time. |
|
|
11 |
|
|
|
If unloading phase is less than 5.5 minutes. (Leave Job Site – Start Unload) < 5.5 minutes |
|
|
12 |
|
|
|
If unloading phase is greater than 100 minutes. (Leave Job Site – Start Unload) > 100. |
|
When a timestamp meets any of the following criteria, it will appear in the view details page in Customer Cost of Service as "False".

What happens when a timestamp is flagged as "False" or inaccurate?
C60 aims to represent a producers business the best it can with the data available. When a timestamp is inaccurate, C60 does not use these particular timestamps in the analysis of the business. C60 resorts to using the average phase durations from all the valid deliveries to the customer and job site. If there are no valid deliveries to the customer and job site, C60 will use the planned phased value (ie: planned travel time, planned on site time, etc).
How to improve the accuracy of your timestamps.
- Ensure dispatcher are accurately predicting the planned delivery phases when scheduling orders. This includes the planned travel time, unloading/pouring time and planned post pouring wash down time.
- Encourage drivers to manually trigger when they begin to unload and if possible, when they finish unloading.
- Confirm all the tablets and or sensors on the truck are working properly and relaying the proper timestamps to your dispatching system.
- If there are known issues with tablets or sensor, contact your telematics provider to troubleshoot any issues.
- Persuade dispatchers and order takers to accurately map job site geofences.
- Ensure the geofence around the plant(s) encompass the entire plant and stagging area.
- Confirm the planned loading time (the time it takes for a truck to get loaded, slump check and leave the plant) for each plant best represents the actual estimated loading time. The planned loading time is a user setting in the C60 application.