Why Mixed-Fleet Orchestration Is Becoming a Core Intralogistics Challenge

Manufacturing plants and large warehouses are moving beyond single-robot pilots. A single site may need tote replenishment, pallet transfers, line-side delivery and conveyor handoffs at the same time. Under-ride, flatbed, roller-conveyor and fork-equipped mobile robots each solve a different part of that workflow. The challenge is no longer selecting one fast vehicle. It is orchestrating a mixed fleet under one set of operational rules.

1. Start with capability-based assignment

Vehicle capability is defined by more than rated payload. Picking method, load-carrier compatibility, interface height, turning radius, positioning tolerance and safety envelope all matter. If the control layer treats every vehicle as the same generic robot, assignments will eventually fail at the station rather than on the route.

A stronger approach is a task-oriented capability matrix. Before optimizing distance or battery level, the system should determine which vehicles can actually perform the required pickup, transport and handoff. It can then compare travel distance, congestion, charge state, workload and delivery windows within that feasible set.

Illustration: capability-based vehicle assignment

2. Govern conflict points, not just obstacles

Mixed fleets make traffic management more complex. Vehicles differ in footprint, acceleration and turning behavior. Narrow aisles, intersections, door zones, lift lobbies and conveyor interfaces become shared resources. More obstacle sensors do not by themselves prevent peak-hour deadlocks.

Projects should identify high-frequency conflict points and define reservation, yielding, buffering and timeout-release rules. Traffic priorities should follow production rhythm, but they must never bypass safety interlocks or station-occupancy constraints. Effective orchestration is about using limited right-of-way in a controlled sequence.

Illustration: governing mixed-traffic conflict points

3. Station handoff defines whether the fleet works

Many systems perform well in simulation and struggle at the physical handoff. The problem is often inconsistent load positioning, incomplete conveyor handshakes, or business orders that do not specify what should be picked, where it should be delivered, and which station confirms completion.

A mixed fleet therefore needs explicit task semantics. An order should include the load-carrier type, handoff action, station state, eligible vehicle types, exception path and completion confirmation. Roller-conveyor interfaces depend on timing and signal handshakes; under-ride and flatbed vehicles depend on standardized carriers; fork vehicles depend on fork height, pallet integrity and safety distance.

Illustration: completing a station handoff

4. Standard interfaces are a foundation, not the whole boundary

VDA 5050 provides a common language for vehicle, master-control and order-execution communication. That reduces repeated integration work, but a standard transport interface does not automatically make a project interoperable.

Each site still needs to define vehicle capabilities, station protocols, task states, exception codes and safety policies above the transport layer. Acceptance should focus on business outcomes: rule-based assignment, consistent station exchange, explainable degraded modes and recovery from network loss, material shortages, human occupation or vehicle faults.

Conclusion

Mixed-fleet orchestration is not simply connecting more robots to one dashboard. It means converting vehicle differences into computable capabilities, turning traffic conflicts into governed resources, and expressing station handoffs as traceable business states. For Chengdu Heli Intelligent, a product portfolio covering under-ride, flatbed, roller-conveyor, fork and collaborative mobile robots becomes valuable when combined with load-carrier standardization, station integration, WMS/MES connectivity and site-level safety engineering.