Dynamic queue positioning and congestion management controls

During peak, the dramatic increase of orders and bots at a site can have unintended negative consequences including issues with bot positioning, traffic flow bottlenecks, collisions, etc. that need to be urgently addressed and resolved either remotely by Locus support or a Locus team member on site. My idea of dynamic queue positioning can allow the bots to behave as if a different map (queue positions) were pushed if a certain threshold of picks are going to a particular location.

While on site at UPS Westchester during their peak week, ~50 different map iterations were pushed. The majority of these changes were adjustments to the number of queue heads and congestion management at a particular location at a given time, and the resulting traffic controls required. This is due to the asymmetrical nature of the waves released, and the physical positions of the high movers. If the customer can anticipate the high-moving SKUs for us, we can set the traffic flow and queue positioning in advance and set the solution to "kick-in" as needed. Hours of Locus/customer manpower can be saved every day and the site can operate dynamically without the need to worry about reverting back to a stable map version post-peak.

Very large numbers of picks going to only a few certain SKUs every day.