Locus Robotics Ideas Portal
All totes should be allowed to be inducted. Once Go is selected then the bot should identify any dupe totes. or it should commence its journey, complete the correct totes and return with any duplicates
|
Problem/opportunity trying to be solved
Currently the dupe tote process is confusing for customers based on the way it inducts then flags a dupe tote. (Examples attached show the variances of a duptote induction for the first and second tote in the mission) |
|
|
Quantify the problem/opportunity
Every customer with duptote functionality will see the process differ from the initial to further Inductions. John lewis have reported individually that colleagues are confused and dont feel the process is well thought through. |
|
|
What is the root cause of the problem/opportunity
Locus net process needs to be evaluated to understand a consistent journey |
|
| Customer need date | Dec 1, 2023 |
| Urgent request | No |
| Report Tag | Deployment |
Both requests are considered bugs in duptote functionality. Can you please create TAC tickets for them?
Thank you for detailed examples Andy