Locus Robotics Ideas Portal
We would like to have the option that also for pre-assigned totes we could put a block to not be able to induct totes with a different PACK task location and only can induct more totes with the same PACK task as the orders in the first tote inducted.
Initially the team I was testing with said they were always thought this is restricted already, but that was it. The project manager has escalated this
|
Problem/opportunity trying to be solved
When we induct jobs and we are choosing the jobs that go on the bot, they will always have the same Task.Location for the PACK task. If the customer is inducting jobs that are pre-assigned to totes, we don't currently have a way to prevent the user from inducting multiple jobs on the bot with different PACK locations. That means that at the moment it can happen with jobs with pre-assigned totes. And when that happens, it is indeterminate which drop-off location we go to. It could be any of the locations. |
|
|
Quantify the problem/opportunity
Abbott is currently in deployment and going live in March. They told me they have always been told that we restrict any induction for a different Task.Location for the PACK task. Even in their case of pre-assigned totes. They do have properly showing the PACK task on the induct label, but they would want the system that despite pre-assigned orders to totes that when you induct one drop-off onto the bot, |
|
|
What is the root cause of the problem/opportunity
At the moment we do not restrict the induct of pre-assigned orders to totes and that means that when the inductor makes a mistakes we allow for different PACK tasks on the bot all ending up randomly at one of the inducted PACK task locations where all need to be dropped |
|
| Customer need date | Mar 1, 2025 |
| Urgent request | Yes |
| Report Tag | CSM, Deployment |
