Locus Robotics Ideas Portal
First ask - when a user ID is created in Manhattan, this bridges over to Locus with the user ID info (functionality already exists). DHL would like the ability for the barcode that is associated to the Manhattan ID to also be associated to the Locus ID. This means there is no set up for initial user ID and first picks. (Manhattan ID, Manhattan barcode and Locus ID/ barcode would be all the same).
The second part of this is if we can scan user ID barcode and that shows who I am, then scan a locus badge and that automatically pairs the user to that Locus Badge.
|
Problem/opportunity trying to be solved
At large facilities with large turn over at peak season, the time to create ID's for associates with locus is not sustainable. Lot of admin time. Seeing as much as 100% turnover every 2/3 weeks. This is agency/ seasonal workers. |
|
|
Quantify the problem/opportunity
Hours lost every day associated with creating new IDs. |
|
|
What is the root cause of the problem/opportunity
The naming convention of the associate user id in the WMS and Locus ID is not compatible, the user ID and barcode ID do not match each other. So in Locus a user barcode ID is having to be created. Bridge between Manhattan and Locus is in place. |
|
| Customer need date | Jun 30, 2022 |
| Urgent request | No |
