AGVHub
AGV System Architecture and Infrastructure
How is an AGV system structured? Overview of components, communication, and integration – from simple setups to enterprise solutions.
Reading time: 6 min
Overview
The infrastructure of an AGV system can vary greatly depending on requirements. From simple standalone solutions to fully integrated enterprise systems, there are different levels of expansion.
Variant 1: Standalone (Sensors Only)
The simplest form – AGVs operate independently with their own sensors.
Standalone Operation
No networking – each AGV operates autonomously
Characteristics
- No central control – each AGV decides independently
- Simple collision avoidance via sensors
- Suitable for: 1-3 vehicles, simple routes, low complexity
- Limitation: No optimization, no central overview
Variant 2: With Fleet Manager
Central coordination via a fleet manager with MQTT communication.
Central Fleet Control
Fleet Manager
MQTT / VDA 5050
AGV 1
AGV 2
AGV 3
AGV n
Characteristics
- Central order distribution and route planning
- Deadlock prevention through coordinated paths
- Real-time visualization of all vehicles
- VDA 5050 for cross-manufacturer communication
- Suitable for: 3-20 vehicles, complex layouts
Components
| Component | Function |
|---|---|
| Fleet Manager | Distribute orders, calculate routes, resolve conflicts |
| MQTT Broker | Message routing between components |
| AGVs | Execute transport orders, report status |
Variant 3: Enterprise (With ERP Integration)
Full integration into corporate IT with SAP/ERP connection and OAuth authentication.
Enterprise Integration
SAP / ERP
WMS
OAuth 2.0 / SSO
API Gateway
Fleet Manager
MQTT / VDA 5050
Characteristics
- ERP Integration: Orders directly from SAP/WMS
- OAuth 2.0 / SSO: Secure authentication via corporate IdP
- API Gateway: Central interface for all systems
- Audit Logs: Traceability of all actions
- Suitable for: 10+ vehicles, corporations, regulated industries
Security Architecture
| Layer | Component | Security |
|---|---|---|
| Application | Dashboard, API | OAuth 2.0, RBAC |
| Transport | MQTT, REST | TLS 1.3, mTLS |
| Network | WiFi, LAN | VLAN, Firewall |
| Vehicle | AGV | Certificates, Secure Boot |
Comparison of Variants
| Criterion | Standalone | With Fleet Manager | Enterprise |
|---|---|---|---|
| Vehicle Count | 1-3 | 3-20 | 10+ |
| Central Control | |||
| ERP Integration | Optional | ||
| OAuth / SSO | |||
| Complexity | Low | Medium | High |
| Cost | $ | $$ | $$$ |
Which Variant Fits Me?
Standalone
- Pilot project
- Single transport route
- Minimal budget
With Fleet Manager
- Multiple vehicles
- Complex routes
- Scaling planned
Enterprise
- SAP/ERP in place
- IT security requirements
- Corporate standards