Fleet Management System (FMS) Role
The FMS is the traffic controller for the AGV fleet. It:
- Dispatches missions to individual vehicles
- Manages traffic conflicts and deadlock prevention
- Monitors vehicle state (location, battery, faults)
- Routes charging based on battery state and vehicle availability
- Interfaces with WMS/WCS/ERP for task generation
Fleet Sizing Formula
Required vehicles = (Trips/hr x Round-trip cycle time in hrs) / Fleet efficiency factor
Fleet efficiency factor: 0.80 (accounts for charging, traffic, faults)Example: 20 trips/hr, 6-minute cycle time = (20 × 0.10) / 0.80 = 2.5 → round up to 3 vehicles minimum.
Add vehicles for peak capacity, charging overhead, and availability buffer.
Software Integration
WMS / WES / WCS Integration
- REST API is standard interface for WMS/WES/WCS/MES/ERP/SAP
- FMS receives work orders from WMS; returns completion confirmations
- VDA 5050 is the open standard protocol for AGV/AMR communication (vendor-independent); as of 2026, confirmed adopters include Seegrid (full compliance 2026), BlueBotics, Rockwell Automation/Otto Motors, and MiR (Source: Research - VDA5050 AMR Interoperability Standard 2026)
Plant Floor Integration
- Industrial Ethernet protocols: EtherNet/IP, PROFINET, OPC UA
- Used for integration with PLCs, conveyors, dock doors, charging stations
- I/O matrix must be documented before installation
Multi-Fleet / Multi-Vendor
- Single FMS can manage up to 300+ vehicles across mixed fleets
- VDA 5050 support enables vendor-neutral orchestration
- Multi-fleet orchestration software is the fastest-growing segment in AMR/AGV software (138% annual growth per Interact Analysis, 2024)
Communication Infrastructure
| Layer | Technology |
|---|---|
| Vehicle-to-FMS | WiFi (802.11) or private wireless (5G) |
| FMS-to-WMS | REST API |
| FMS-to-PLC/conveyor | EtherNet/IP, PROFINET, OPC UA |
| Multi-vendor vehicle protocol | VDA 5050 |
5G private networks enable ultra-low latency and higher bandwidth for dense fleets. Still emerging for brownfield sites; WiFi remains dominant in current installs.
Acceptance Testing Requirements
Before go-live, FMS acceptance tests should verify:
- Braking performance under full load at maximum speed
- Task lifecycle (mission creation, dispatch, completion, confirmation)
- Deadlock recovery behavior
- Charging strategy execution
- E-stop response across all zones
- Integration handshake with WMS (order receipt, task close, exception handling)
Operational Scale Benchmarks
| Fleet Size | Complexity Level |
|---|---|
| 1-10 vehicles | Pilot / small operation |
| 10-50 vehicles | Mid-scale DC |
| 50-150 vehicles | Large distribution center |
| 150-300+ vehicles | High-throughput fulfillment or large manufacturing |
Vendor Landscape
Top 5 vendors (North America) holding ~45-50% of AGV revenue: Daifuku, Dematic (KION), Toyota Material Handling, Jungheinrich, Swisslog.
Key 2025 developments:
- KION + NVIDIA partnership: AI-powered digital twin for warehouse optimization
- KION unveiled AI-powered driverless forklifts using simulation-based training and imitation learning
- Toyota partnered with Gideon (Zagreb) for AMR software deployment, signaling shift from fixed-path AGVs
Worked Example: Dematic ATOM/EMS Control System (CSS-0000-13.9, 2024)
Source-derived from vna-agv-site-readiness-specs-dematic-jungheinrich-2024. A concrete AGV control-system architecture:
- Upper level: ATOM / ATOM GL (fleet manager + 2-D traffic control + job management) and EMS, alongside WMS/WCS (E’wms / E’wcs), on Microsoft SQL. Server sized by a points model (Small <=20 / Medium 21-50 / Large 51+ points -> 8/16/32 GB RAM); validated to Windows Server 2022 / SQL Server 2022; redundancy via active-passive cluster.
- Vehicle controller: Advantech UNO-2484G fanless PC on 10-36 VDC, Windows 10 IoT LTSC; SICK LD/NAV300 + 3-D scanners and SICK Flexisoft safety; GDU touchscreen HMI.
- Messaging: per-vehicle traffic/job data over UDP (ports 2100/2111/2160/2172/2232); bandwidth is light (a few small UDP packets/sec plus a ~1 MB alarm file per vehicle per hour) - the network constraint is latency and roaming, not throughput. See PLC-WCS Integration for the I/O and PLC interfaces.