Locus Robotics Ideas Portal
front versus back of rack
Problem
In most cases, the putaway bin location for an item is the same as the pick bin location and will use the same LP2bin location mapping. However for larger case putaway, it is common for customers to use gravity flow rack where the case is putaway from the back of the racking and items picked from the front of the racking (e.g., putaway from aisle 2, pick from aisle 1). The bin location in the back has the same bin ID and barcode as the front since it is scanned to verify the item is putaway in the correct location.
Proposed Solution
Provide the ability for Locus to support (2) bin locations for an item. In most cases, the putaway bin location will default to be the same as the pick bin location and related LP2bin location. However for cases where WMS "flags" an item and its pick bin location as having a different putaway bin location (e.g., flow rack), Locus would have a different LP2bin mapping for putaway and maybe have "P" prefix for bin location in Locus or similar to indicate putaway location is different than pick location.
|
Problem/opportunity trying to be solved
In most cases, the putaway bin location for an item is the same as the pick bin location and will use the same LP2bin location mapping. However for larger case putaway, it is common for customers to use gravity flow rack where the case is putaway from the back of the racking and items picked from the front of the racking (e.g., putaway from aisle 2, pick from aisle 1). The bin location in the back has the same bin ID and barcode as the front since it is scanned to verify the item is putaway in the correct location. |
|
|
Quantify the problem/opportunity
Not exactly sure, but expected to be important for Waypoint use cases |
|
|
What is the root cause of the problem/opportunity
A bin can only have a single Locus Point (physical location) in the Locus system. |
