Locus Robotics Ideas Portal
So currently the process is as follows:
The customer to build up the tote-array and fill the 12 bins
Upon scanning the master tote ID, we are sending a putawayjob request
We do expect one putawayjob with 12 sections in that putawayjob - 1 section per bin
In each of these sections, the customer is expected to the put position and color of that bin in order to show that on the robot iPad
What the customer wants:
The customer to build up the tote-array and fill the 12 bins
Upon scanning the master tote ID, they would expect us to send 12 putawayjob requests - 1 for each bin
The customer wants to reply sending 12 putawayjobs - 1 putawayjob per bin
The customer expects not having to send the color/bin in order to show that on the robot iPad. Reasoning is that based on the tote array created, when we get a putawayjob for a specific bin, we should know the position/color.
The customer understands it has to build up a tote-array.
orderjob 001 - tote-array bin 0001 --> the customers expects that based on the tote-array bin number, that we know the position and the corresponding color based on the tote
Upon scanning the mother ID for a 12-bin tote array, we can send 12 putaway requests for the 12 child IDs. The customer would respond with 12 putawayjobs that we will assign to every single postion based on child ID in the putawayjob
|
Problem/opportunity trying to be solved
Geodis in NL has initially problems with the way we manage put-away with tote-arrays. Geodis expects it can send 12 putaway jobs for a put-away with a 12-bin tote-array, but we need 1 putawayjob with 12 sections. That was also within Locus not clear, as we expected it to be similar to outbound with tote-arrays: 1 orderjob for 1 bin of a tote-array.
|
|
|
Quantify the problem/opportunity
There is more manual work to be done in order to still use the tote-arrays designed for putaway of returns as they threat every bin of the tote-array as an individual tote. |
|
|
What is the root cause of the problem/opportunity
We have a restriction to only accept 1 putawayjob with e.g. 12 sections within this putawayjob in case of a 12-bin tote array. Technically they have difficulties to manage that. Right now we are using put-away with the tote-arrays for returns, but they use the tote-array threating every single bin as an individual tote |
|
| Customer need date | Mar 30, 2024 |
| Urgent request | No |
| Report Tag | Deployment |
