Fleet Coordination Engineering Guide
When several automated forklifts share one pickup or delivery point, vehicle congestion can reduce throughput even if the fleet has enough capacity. ZCNEST explains how to identify bottlenecks, control task release, and design handoff rules for warehouse pallet movement.

A handoff station is the point where a pallet is collected from or delivered to another process, such as a conveyor, pallet dispenser, storage system, or manual work area. When multiple missions depend on the same point, vehicles may arrive faster than the station can complete transfers.
Do not assume that every queue is caused by insufficient vehicle capacity. The limiting factor may be slow pallet presentation, delayed confirmation signals, a blocked receiving position, operator availability, or a downstream machine that is not ready.
Number of arrivals and completed handoffs per hour.
Waiting time before a station becomes available.
Actual transfer time, including confirmation and recovery.
Frequency of occupied, blocked, or failed handoff positions.
Number of vehicles waiting and the duration of each queue.
CORE 01
Release tasks according to station availability and downstream capacity instead of sending every vehicle as soon as a task is created.
CORE 02
Remove avoidable waiting caused by unclear pallet positioning, late acknowledgements, inconsistent operating procedures, or slow exception resolution.
CORE 03
Define suitable waiting positions and keep queues from blocking intersections, narrow aisles, pedestrian access, or other handoff stations.
If a station can complete only a limited number of transfers in a given period, sending more vehicles toward it will create waiting rather than additional output. The fleet-control strategy should account for station readiness and the expected completion time of the current transfer.
Where software supports it, reserve the handoff position for a specific mission and prevent another vehicle from entering the approach area too early. If the station becomes unavailable, the fleet system should hold or reroute incoming tasks according to agreed rules. The exact options depend on the fleet software and interface design.
How does the fleet system know that a station is ready?
Can a station be reserved for an assigned vehicle or mission?
Where can an AGV wait without blocking other traffic?
What happens when a transfer exceeds its expected duration?
How are urgent missions prioritized without creating uncontrolled congestion?
Software cannot fully compensate for a poorly designed physical transfer. The pickup and delivery position must accommodate the pallet, vehicle approach, fork entry, and any conveyor or machine interface. If pallets arrive inconsistently positioned, the vehicle may require additional alignment attempts or operator intervention.
Standardize pallet orientation, presentation height where relevant, and the point at which the transfer is considered complete. Check whether sensors can reliably detect the pallet and whether the receiving equipment provides an unambiguous ready signal. Where manual workers share the station, define the handoff responsibilities and keep people clear of vehicle movement zones.
If one station regularly causes long queues, evaluate whether the process can be split between multiple handoff positions. Adding another station may help only if space, downstream capacity, and software coordination support the change.
Inbound replenishment, storage putaway, and urgent outbound orders may compete for the same transfer point. Without clear priority rules, vehicles may wait behind low-priority work even when a time-sensitive shipment needs to move.
Define priority categories based on operational requirements, such as dispatch deadlines, production-independent warehouse commitments, or inventory replenishment needs. Test how priority rules affect other tasks; repeatedly pushing routine work to the back of the queue can create a different bottleneck elsewhere.
Use queue and task data to review whether the priority model produces the expected result. The objective is a predictable flow across the complete warehouse process, not simply faster arrival at one station.
Compare station throughput, average and peak queue time, completed missions, blocked-station events, and manual interventions before and after the change. Test normal and peak workloads, as well as station faults and delayed confirmations. A shorter queue is useful only if completed pallet movement and overall process reliability also improve.
Warehouse preparation has a direct impact on AGV forklift selection, integration, commissioning, and acceptance. Before equipment is manufactured or delivered, buyers should confirm the physical layout, pallet specifications, operating workflow, information-system requirements, and site responsibilities. This guide provides a practical checklist for preparing a warehouse automation project.

A warehouse drawing is one of the most important inputs for AGV forklift planning, but it must reflect actual operating conditions. Changes made after the drawing was created, temporary storage areas, rack projections, and equipment installed along travel routes can all affect vehicle movement. Prepare the latest available layout and identify the areas included in the automation scope. Mark receiving points, storage locations, outbound staging, charging areas, transfer stations, restricted zones, and the routes between them. Provide CAD or other suitable layout files with dimensions and a clear coordinate reference. Confirm rack positions, aisle widths, rack heights, columns, doors, and fixed obstructions. Mark pickup and drop-off locations and specify the expected pallet orientation. Identify pedestrian routes, manual forklift traffic, emergency exits, and restricted areas. Record floor joints, gradients, surface changes, and areas requiring further inspection. Where the drawings may be outdated, verify critical dimensions on site. Vehicle selection and route design should be based on the usable space, not only the nominal dimensions shown in a drawing. AREA 01 Verify aisle clearance, floor condition, ramps, doorways, rack geometry, charging locations, and the operating space at each handover point. AREA 02 Document pallet dimensions, weight range, load center, fork entry direction, overhang, and any variation that may affect pickup or placement. AREA 03 Map the movement from origin to destination, identify peak periods, and define how tasks are released, prioritized, completed, and recovered after failure. AREA 04 Confirm the required WMS or WCS interfaces, network access, IT approvals, commissioning access, and responsibilities for testing and acceptance. AGV forklift selection depends on the loads the vehicle must handle, not simply the average pallet in the warehouse. A small number of heavier, taller, or unusually shaped loads can determine the required vehicle configuration. Minimum, typical, and maximum pallet dimensions. Minimum, typical, and maximum loaded pallet weight. Load height, center of gravity considerations, and overhang. Pallet material, bottom-board design, and fork entry requirements. Required pickup and placement heights and the destination rack configuration. Photographs of representative pallets and difficult loads can help the supplier understand the handling conditions. If pallet quality varies significantly, identify that variation early rather than treating every pallet as identical. Before installation, describe how a transport task begins, who assigns the destination, and how the warehouse knows that the movement has been completed. The process may involve a WMS, fleet control system, conveyor, operator, or another handling device. Create a simple workflow for normal operations and a separate process for exceptions. Examples include an occupied destination, a missing pallet, an unavailable pickup point, a blocked route, or a communication interruption. Which system creates and prioritizes each transport task? How are pallet IDs and destination locations exchanged? How is task completion confirmed and recorded? Who responds when an AGV cannot complete a task? How are manual interventions reconciled with warehouse inventory records? The project team should confirm the network and IT arrangements required by the proposed system. This may include wireless coverage, network access, firewall rules, device permissions, logging, and approved remote support methods. Test the actual operating routes and transfer areas rather than relying only on coverage estimates. Review safety arrangements for pedestrian crossings, manual vehicles, staging zones, and emergency access. Establish the site process for isolating equipment, responding to alarms, and recovering failed tasks. Final arrangements should reflect the vehicle's design, site risk assessment, and applicable requirements. Also confirm practical commissioning arrangements, including delivery access, unloading equipment, installation space, power availability, test pallets, representative loads, and access to the customer's IT and warehouse personnel. Acceptance criteria should be agreed before commissioning starts. They should describe measurable results under defined conditions rather than relying on broad statements such as smooth operation or high efficiency. Successful pickup and placement using representative pallets. Required travel and handling performance under the agreed workload. Correct task status exchange with connected warehouse systems. Defined responses to selected faults and blocked locations. Verification of safety functions and operating procedures. Completion of training, documentation, and outstanding issue records. Specify the test conditions, measurement method, and responsibility for resolving failed items. This gives both the customer and supplier a clear basis for determining whether the system is ready for routine operation. Before finalizing the installation schedule, confirm that the latest layout is available, critical dimensions have been verified, pallet data has been collected, workflows are documented, software responsibilities are assigned, network access is approved, safety arrangements are defined, and acceptance criteria are agreed. Any unresolved item should have a named owner and a target completion date.01. Prepare an Accurate Warehouse Layout
Four Preparation Areas Before Installation
Physical Site Conditions
Pallets and Load Specifications
Operating Workflow and Throughput
Software, Network, and Site Access
02. Document the Actual Pallet Handling Requirements
Information to Collect
03. Map the Workflow and Define System Ownership
Questions to Resolve Before Commissioning
04. Check Network, Safety, and Installation Readiness
05. Agree on Acceptance Criteria Before Delivery
Warehouse Readiness Checklist
📖 AGV Forklift Guide — Essential manual for selection and safety.
⚙️ How AGV Systems Work — A deep dive into navigation and logic.
⚖️ AGV vs. AMR Comparison — Choosing the right technology for your facility.
💰 AGV Cost and ROI — Evaluating investment and payback periods.