Customer (Nike) would like the ability to send a single orderjob for the entire robots worth of work. This process is used in a similar fashion during current Locus Putaway workflows at Toyota and Bella Canvas
These customers will be utilizing a shelf with multiple positions and a single standard tote for each positions that an order occupies, so we can assume that the entire site is only using the one configuration.
The customer will send us a orderjob new, in which they include a ToteID and different Orderjob Tasks, that will also include a JobTask ID with a custom field that will indicate the position of the Order on the shelf. The attached example is using Custom3 for the OrderJob New.
There would be a requirement that for the entire site one orderjob will be assigned per robot and the position picker is disabled when this functionality is being used.
The process at induct will look like:
Robot Pulls up to an induct position and displays the customer configured induction Screen.
The user will Scan a single LPN associated to an Orderjob ID.
LocusNet will identify the Orderjob associated to the LPN and place the specific OrderID to the locations on the robot established by the Custom field being sent by Customer WMS.
The Robot Screen will then display the Green “Go” button.
The user will select GO and the bot will proceed to it’s first pick.
Problem/opportunity trying to be solved
Increase induct productivity at Nike |
|
Quantify the problem/opportunity
Nike physically uses ToteArrays for picking, but inducts individual orders via paper slips into tote array. This increases induction time. |
|
What is the root cause of the problem/opportunity
Nike attempts to optimize robot missions outside of Locus. |
|
Customer need date | Mar 29, 2024 |
Urgent request | Yes |
Report Tag | CSM |