Locus Robotics Ideas Portal
The expectation/request is that when the customer sends an 'update' for an active mission because of short, that the bot travels there (as it does now) but it would also have the show the position/color of the bin of the respective tote array for the picker to know where to put it. In the 'update' it should have all details to know what bin the item should go into because it's still the same mission.
|
Problem/opportunity trying to be solved
This is an issue that occured for Fiege-Burgwedel. On an orderjob the picker had to confirm a short. In that case their WMS would check if that item is available elsewhere, and if yes it would send an 'update' to Locus with the new pick quantity/location. In that case we see the bot to arrive at it's new location, however the iPad doesn't display the color nor the number of the tote array position. This issue was reported in IST-9157/TAC-13392 |
|
|
Quantify the problem/opportunity
This happens every time the teams does a short pick into their tote-arrays. I have no visibility on how often this happens. Right now they are live with a Pilot with a Main Go-Live later this year. But it is very inconvenience. |
|
|
What is the root cause of the problem/opportunity
The tote position and color is determined upon induction. If there is a need to send an update (in case of a short pick), we are not updating to the existing pick as we create a new pick for that shortened one. The old pick is assigned to a location/color, but we have no way at the moment to compare the original pick with the update and assign that same color/position for this new pick. |
|
| Customer need date | Nov 1, 2023 |
| Urgent request | Yes |
| Report Tag | Deployment, CSM |
This one can be closed - fix created already by Nik deployed in production. So we are all good here