Sortation with AMRs

The most frequently discussed approach is to use a Vector with a conveyor on top. The Vector docks to input conveyor(s) and then is sent to one or more output conveyor(s) based on the requirements associated with the payload. In addition to a conveyor, other top modules might also be viable. And this exact configuration, with Max and a conveyor, has been pitched with a warm reception to large logistics companies who would use it in cross-dock applications.

In small scale setups, this could be non-integrated and a person could send the bot to its appropriate destination using Whistle.

In large scale, complex setups, this would be a fully integrated system and the data (barcode, LPN, etc) on the payload would be read by a scanner, and the bot's desitnation would be assigned at the time of loading.

There's a space between the two preceeding examples where a simple lookup table could be utilized in an offboard "server", or it could be built into the robots' program. If there is a relatively small number of possible destinations and SKUs, then the SKU code could be read by a sensor on the bot, and that value could be looked up, and a destination assigned based on the SKU.

In addition to the movement and sortation value, there's also value add capabilities such as driving through a dimensioning system between destinations, which is a requested fun tion in cross dock applications.

It also seems like in some cases it might be viable to use an O2 robot with a conveyor on top, as long as the building geometry, payload requirements, and alignment time / reliability / accuracy were in spec for the particular opportunity.