What happens when a warehouse fleet gets a single dispatch brain.
Two pilot deployments showing how Botpylon's congestion-aware dispatch changed specific operations numbers for a mid-size 3PL and a mixed AMR/AGV e-commerce fulfillment center. Both operators are synthetic pseudonyms. Results reflect pilot deployment modeling against real floor geometry types.
TriCore Fulfillment
Mid-size third-party logistics operator running 85 autonomous mobile robots across two fulfillment floors. Robots from two different vendors, no unified dispatch layer.
The Problem
TriCore Fulfillment was operating 85 AMRs from two different vendors across two interconnected warehouse floors. Each vendor's fleet management software ran independently, dispatching to its own robots with no awareness of the other vendor's fleet positions or task assignments.
Cross-floor aisle intersections became the failure point. Robots from Vendor A and robots from Vendor B both received individually-optimal paths that converged on the same high-frequency aisles at the same time. With no cross-vendor coordination, stop-and-wait queues formed at those intersections during every peak shift period.
The measured impact: 23% robot idle time per shift attributable to inter-vendor congestion at 4 chronic aisle intersections. The operations team was aware of the hotspots but had no mechanism to coordinate dispatch across vendor boundaries without manual intervention.
Implementation
Botpylon connected to both vendors' fleet management APIs and the existing WMS via standard REST connectors. Integration was completed in 4 business days. Both robot fleets were ingested into the unified floor graph without changes to robot firmware or vendor software configurations.
The floor graph immediately identified the 4 chronic intersection hotspots from the first 48 hours of telemetry data. Path weights were calibrated for those intersections, and the optimizer began routing the two fleets to avoid simultaneous convergence on them during peak shift hours.
What Changed
After 8 weeks of live Botpylon dispatch, TriCore's operations team reported the following changes versus the pre-Botpylon baseline period.
reduction in peak congestion events per shift at chronic aisle intersections
reduction in pick-path travel time per order line across both floors
estimated payback period vs dispatch labor and congestion-related delays
integration time from API access to live unified dispatch across both robot fleets
Cascadia Commerce
E-commerce fulfillment brand running a 140-unit mixed fleet of autonomous mobile robots and automated guided vehicles across a single large distribution center floor in Tempe, AZ.
The Problem
Cascadia Commerce had invested heavily in a mixed AMR/AGV fleet intended to handle both high-velocity SKU picking (AMRs, free-path navigation) and heavy-tote transport to packing stations (AGVs, fixed-lane navigation). On paper, the two robot types complemented each other. In practice, the collision avoidance systems created cascading stop events.
AMRs, when encountering AGVs in or near their fixed lanes, would trigger collision avoidance halts. Nearby AMRs, reading the stopped robots as obstacles, would halt in turn. In peak periods with 140 active robots, these stop cascades could immobilize 15-25 robots simultaneously, sometimes for 3-5 minutes before the system self-cleared. Fleet utilization had plateaued at 68% despite the hardware investment.
Implementation
Botpylon deployed fleet adapters for both robot types: a REST-based adapter for the AMR fleet controller and an MQTT adapter for the AGV control system. The unified floor graph modeled AGV fixed lanes as time-gated corridors, with Botpylon predicting AGV lane occupancy windows and routing AMR dispatch to avoid simultaneous AMR-AGV lane boundary crossings.
Integration across both robot categories was completed in 6 business days. The two-vendor deployment required no firmware changes on either robot type and no reconfiguration of the existing WMS task feed.
What Changed
Fleet utilization recovered 23 percentage points from existing hardware with no additional robot purchases. The operations team attributed the improvement to the elimination of stop-cascade events, which had been absorbing roughly 18-22% of active robot time per peak shift prior to Botpylon deployment.
reduction in stop-cascade events per shift after Botpylon unified dispatch activation
fleet utilization rate, up from 68% before Botpylon coordination
utilization increase recovered from existing hardware investment, no new robots required
robot categories unified under a single Botpylon dispatch session: AMR and AGV
Tell us your floor. We'll show you a model.
Share your floor plan, robot vendor mix, and current utilization data. We'll model what Botpylon dispatch would change on your specific layout before you commit to a deployment.
Request Demo