Locus Robotics Ideas Portal
Currently locus is only considering 3 fields when considering if it should roll up the task or not (robotid, toteid, and itemno). The request is to create a configurable value that will be considered for rollup. The use case here is a customer that picks both eaches and cartons. The customer will often send this information in a custom field. If we leveraged that custom field to decide if it should be rolled up or not it would allow the customer to leverage task rollup but still have eaches and cartons picked as separate lines from the robot UI perspective.
|
Problem/opportunity trying to be solved
Currently locus is only considering 3 fields when considering if it should roll up the task or not (robotid, toteid, and itemno). The request is to create a configurable value that will be considered for rollup. The use case here is a customer that picks both eaches and cartons. The customer will often send this information in a custom field. If we leveraged that custom field to decide if it should be rolled up or not it would allow the customer to leverage task rollup but still have eaches and cartons picked as separate lines from the robot UI perspective. |
|
|
Quantify the problem/opportunity
This can make certain customers utilizing Task Roll Up more productive |
|
|
What is the root cause of the problem/opportunity
DHL Pataskala (Wella) was having issues with a bot stopping at a pick locations but the picker would have to execute the pick several times during one stop. After implementing Task Roll Up, it did not work well due to the fact that they utilize a custom field |
|
| Customer need date | May 2, 2024 |
| Urgent request | No |
| Report Tag | CSM |
