Configuration option: add additional base Putaway config option of LIFO --> Unload in reverse order of induction onto the bot.
Putaway Method: Optimal Putaway Path --> Putaway path is optimal based on most efficient travel path.
Putaway Method: LIFO, reverse loading --> Putaway path is created based on unloading in reverse order that the bot was loaded.
Problem/opportunity trying to be solved
Current functionality of Putaway is to send the bot on the optimal putaway path only regardless of how the cases were put onto the bot. This is not a huge problem for the Origin bot, as there are typically not a large number of cases on the bot. As a result, the user does not have to "Dig" through a pile of cases to find the first case on the Optimal Putaway Path. As we move toward new use case opportunities in Putaway for the Max, this "Dig" method becomes much more strenuous and time consuming. If I have 100 different cases on a Max bot, and we are using this Optimal Putaway Path, "Dig" method, the user would be spending excessive time and exertion searching for the correct case--lifting multiple heavy cases off of the bot and onto the ground--operations would not accept this. In this instance, it is much more efficient and beneficial for operations, to have the robot "Dance" instead of the user "Dig". The robot is loaded with cases 1,2,3,4 and the putaway path chosen if configured for LIFO Putaway is unloading in 4,3,2,1. This decreases the human interaction time with the robot by a large amount as they do not have to search for a particular case -- they know that the case in need is one of the ones on top of the pile for example. |
|
Quantify the problem/opportunity
Utilizing the Max for putaway to bring Locus bots into many different types of DCs represents a huge potential gain for our business. If the max was to be used during putaway with large quantities of mixed cases (e.g., lean time replenishment to top of locations in down time), this functionality would be essential for operations to consider it. Operations that I have worked with have had this requirement previously even when it required a person to "Dance" (LIFO, non optimal putaway path), but the fact that in this case our Max bot will be doing the "Dance" for them, and the human interaction is simply taking one or a few cases off the top of the bot and sending it on its way makes this solution all the more enticing for ops. 1 - Significantly decreases strain on the teammate from digging through cases to hunt for the particular case. 2 - Significantly decreases teammate time spent interacting with the bot hunting for the particular case. 3 - Allows Max bot to be a viable solution for large quantity, mixed case putaway. |
|
What is the root cause of the problem/opportunity
Root opportunity is expanding the types of clients that would be willing to use the Max in their warehouse. This problem does not affect the Origin bot as the total quantities on the bots during putaway does not warrant a huge amount of search time from the user as they look for a particular case during putaway. This will not be the case with the max. |
|
Customer need date | Jun 7, 2023 |
Urgent request | No |
Thank you Mitchell. Jesse Mendenhall's working on the putaway use cases and this is very helpful.