Locus Robotics Ideas Portal
Pick UPH |
Putaway CPH |
Putaway UPH |
Total UPH |
|
EBURLI |
115 |
3 |
18 |
133 |
MTAVER |
98 |
15 |
255 |
353 |
|
Problem/opportunity trying to be solved
In this case Nike wants to be able to see the UPH by user ID / employee for Picking and Putaway processes.
|
||||||||||||||||
|
Quantify the problem/opportunity
Managers will be able to find out the Productivity from their employees at anytime, also able to see which functions they are performing vs UPH target. |
||||||||||||||||
|
What is the root cause of the problem/opportunity
Not able to see this information. The Managers need to run different reports to be able to get this information. |
||||||||||||||||
| Customer need date | Jul 3, 2023 | |||||||||||||||
| Urgent request | No | |||||||||||||||
| Report Tag | OSD | |||||||||||||||
Picking and putaway data are now available in LocusHub
Martin - I don't see this as urgent. We use urgent for:
New features we have to commit to in order to sign the deal
Critical feature blocking site productivity
Feature missed in COO and now blocking deployment.
Please confirm I'm reading this correctly.