We want to develop a way to capture more data points to calculate every aspect of an associates PICK. See 'Problem/opportunity trying to be solved'
Problem/opportunity trying to be solved
Average Task Time today includes the time between an associate's last pick, the time to CONDUCT the pick (or PUT), and the time to PLACE the item in the container and confirm the pick. We'd like to split these out into the following steps:
|
|
Quantify the problem/opportunity
With a more accurately calculated Task Time, we can measure any improvements without having to send a member of Locus to complete a Time Study. |
|
What is the root cause of the problem/opportunity
Not having a time stamp of when a user tag is recognized by an iPad AND not having a timestamp of when the physical SCAN is made. |
|
Customer need date | Jan 1, 2025 |
Urgent request | No |
Report Tag | Data, OSD |
If we have the different data points captured, we would be able to calculate the different parts of the pick time systematically and not have to rely on Locus resources to measure manually which results in extra travel time and cost. Furthermore, manual time studies are not accurate even with the time spent. This was brought up by Cardinal Health who's evaluating Invia and has shared with Locus that this feature is a differentiator. Do we need to provide more specifics on the different data points needed?